macOS High Sierra 10.13 Supplemental Update

[vulgo]

Thanks to the above help, I ended up cleaning up my config.plist quite a bit (lots of cruft from previous hardware configurations). My "Scan" key had a <dict> full of junk, instead of a simple <true/>.

My "Boot" key didn't have the "IgnoreNVRAMBoot" key at all (although, I assume default is false), but I stuck it in as false anyway.

Alas, I'm still in the same situation: no "Install macOS" partition to boot from during install.

If it was just a matter of Clover not seeing the partition, wouldn't I at least see it in "disktutil list"? It isn't there either. It really looks like it's not getting created at all.

Clover is hardcoded with file paths to the installer bootloader

// OS X installer paths
STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"

or the installer can set a path in NVRAM which Clover can parse and show an entry for

 

[spotcatbug]

Clover is hardcoded with file paths to the installer bootloader

// OS X installer paths
STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"

or the installer can set a path in NVRAM which Clover can parse and show an entry for

Whoa, yeah, "macOS Install Data" is there at the root of my boot drive! However, there is no boot.efi in there. Here's what's inside "macOS Install Data":

drwxr-xr-x@  8 root  wheel     272 Oct 10 15:58 .
drwxr-xr-x  46 root  wheel    1632 Oct 10 16:49 ..
-rw-r--r--   1 root  wheel     389 Oct 10 15:58 InstallInfo.plist
drwx------   5 root  wheel     170 Oct 10 15:58 Locked Files
-rw-r--r--   1 root  wheel     332 Oct 10 15:58 OSInstallAttr.plist
-rwxr-xr-x   1 root  wheel  241792 Oct  3 01:34 brtool
-rw-r--r--   1 root  wheel     181 Oct 10 15:57 index.sproduct
-rw-r--r--   1 root  wheel     514 Oct 10 15:58 minstallconfig.xml

I guess I'm going to try deleting that directory and installing again - I've been fiddling so much - who knows?

edit: I removed the directory and tried installing again (from the Apple download linked in the OP). Didn't work. Ended up with the same "macOS Install Data" folder with the same contents.

 

[wstrohm]

Appreciate your response, but my primary computer is bricked altogether; it will not boot on a known good 10.12.6 SSD which contains the 10.12.6 install program from Apple, and with that SSD in my primary computer, it will also NOT boot on a 10.12.6 Unibeast USB drive, which is recognized as a USB drive, but not bootable.

What I have tried:
1. Clearing CMOS and resetting the F22A Gigabyte H170N BIOS, with the options that have always worked on that same BIOS revision.
2. Played with moving a High Sierra 850 EVO SSD (non-bootable now) into my Sierra computer and booting the Sierra computer on its primary 840 EVO SSD, followed by saving needed data from the HS SSD to the Sierra SSD.
3. Reformatted the 850 EVO SSD and CCC'd the entire contents of the Sierra 840 EVO SSD onto the erased 850 EVO SSD. Then moved the 850 EVO SSD back into the primary, bricked computer. Removed the remaining SSD in the High Sierra computer and attempted to boot on the newly-loaded 850 EVO. Result was the same as original: constant re-booting.

Note that I used CCC version 5.0.3, which is capable of cloning EFI folders in addition to the main folder, which I did confirm. I did have trouble with erasing and partitioning the 850 EVO SSD from the HS computer, i.e. there was always a 312 MB volume remaining on the partitioned/erased SSD. Perhaps that is causing the problem, although at one time the HS computer was working fine on its primary SSD after updating with the "Supplementary update." But now I cannot even go back to Sierra 10.12.6, no matter what I do!

 

[Utamaru]

No. The uninstall script won't run in recovery mode (you can however perform equivalent steps manually in the Recovery Partition Terminal utility). To just run the script though, you need to have remote terminal access over SSH. All you need to do is:

- be able to boot to a black screen or the looping screen clear with IOConsoleUser debug message - basically as long as the machine doesn't spontaneously reboot you should be able to SSH in as long as you previously enabled remote login in Sharing preferences (you should always do this as soon as you have a bootable system)
- from another machine, SSH to your target machine
- as root, unpack the nvidia uninstall package like so - pkgutil --expand /Library/PreferencePanes/NVIDIA\ Driver\ Manager.prefPane/Contents/MacOS/NVIDIA\ Web\ Driver\ Uninstaller.app/Contents/Resources/NVUninstall.pkg /tmp/foo
- as root run the uninstall script like so - /tmp/foo/Scripts/postinstall 0 0 /
- reboot and at the Clover boot screen hit spacebar and select the nv_disable option before choosing Boot with selected options
- edit your Clover config.plist to remove either the nvda_drv=1 boot arg or NvidiaWeb system parameter (whichever one you were using)
- reinstall the WebDriver (if that is your aim) by rebooting this time with SIP enabled CsrActiveConfig = 0x0 (if you can't boot with SIP enabled for some reason try booting with SIP enabled in Safe Mode - this worked for me

For thous of you who did not uninstall Nvidia WebDrivers and install the update and stuck in boot loop, this is how i solved my problem from Single User mode.

 

[send2moran]

For thous of you who did not uninstall Nvidia WebDrivers and install the update and stuck in boot loop, this is how i solved my problem from Single User mode.

did you manage to install the new drivers ( 378.10.10.10.15.117) without the loop problem ?

 

[rudimania]

Downloaded and installed the update package.
At boot disabled "Allow untested kexts"
Booted from the installer
Rebooted "allow untested kexts"
Installed the updated driver
Voila~works Thanks Rotting for figuring this out and wolfie81 for asking the question.

I tried your instructions and still had problems with a kernel panic. Had to restore with time machine again. Not sure what I missed. But that my restored 12.13.0 works fine

 

[erroruser]

I tried your instructions and still had problems with a kernel panic. Had to restore with time machine again. Not sure what I missed. But that my restored 12.13.0 works fine

try this it worked for me https://www.tonymacx86.com/threads/...pplemental-update.233897/page-17#post-1600000

 

[leshnikov]

It worked smoothly for me. I did those steps:
1. Uninstall the Nvidia Web Driver through the control panel.
2. Mount the EFI-Partition and replace the apfs.efi in /EFI/Clover/drivers64UEFI/ with the new one: apfs.efi.zip
3. Start downloading the update and restart.
4. When you see the Clover menu, choose Mac OS Install not Mac OS. If you do that, you will end up on the same version as before.
5. When your Computer restarts and you are able to lock back in, go and start downloading and install the new Nvidia Web Driver.
6. Restart and it should work.
New Nvidia Web. Driver: https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.15.117.pkg
Hope you succeed

Thank you! This should be pinned somewhere in the beginning. Everything went smoothly, works like a charm!

 

[griftopia]

apfs.efi is changed from 748.1.46 to 748.1.47. Here is the new file.

Does this have any significance for Clover/EFI UEFI64 drivers.
Should we take the new file and replace the old one?
If so, should we do it *before* or *after* applying update?

Don't want to have a situation where I install update and laptop cannot see my APFS drive.

 

[griftopia]

No, I just downloaded it not installed it. It was waiting for restart and I didn't want to restart. Now it shows update and update all.

Which is why I never download mac os updates from AppStore but always manually. Have been burnt before