Contribute
Register

macOS High Sierra 10.13 Supplemental Update

Status
Not open for further replies.
You should check your Clover bootlog.

Just read through the whole thing. Can't say I understand a lot of it, but nothing jumped out at me as wrong or errors or anything like that.

My feeling is that the various installers (app store, USB stick, Apple download) are crashing (and rebooting) before (or at) the part where they try to make the "Install macOS" partition, but I can't think what could be causing that.
 
Flawless update for me as well :)

How I applied it :
- Uninstall NVidia Webdrivers
- Copy new apfs.efi in EFI
- Install the update (downloaded from apple website, didn't work through the app store)
- Reboot to OSX Install
- Reboot to regular OSX
- Installed new Nvidia Webdrivers
- Ran Toleda's ./audio_cloverALC-130_v0.3.command

Everything work ! :)

Please Tonymacx86, you should attach the new apfs.efi in the first post, it will be easier for other :)

Thanks to all

where do I get the new apfs.efi from?
 
Just checked to be sure. Nope.
Make sure scan entries in GUI is true.
Code:
<key>GUI</key>
<dict>
...
<key>Scan</key>
<true/>
...
</dict>
Working NVRAM either hardware or emulated when you start the installer app. IgnoreNVRAMBoot is set to false.
Code:
<key>Boot</key>
<dict>
...
<key>IgnoreNVRAMBoot</key>
<false/>
...
</dict>
 
ok, thanks, so I just replace the file and thats it?
 
After this last supplemental update, I see 2 issues.
1. Glitchy UI performance (Nvidia Titan X)
2. Cannot upgrade Clover from version 4220 to version 4243.

Anyone else experiencing the same issues?
 
Have you tried removing EmuVariableUefi-64.efi from your /EFI/Clover/drivers64UEFI folder? I had to do that on both my desktop and laptops to get the Hight Sierra Installer to finish.

-bth

**Also, once update is complete, and you are booted into the updated OS, don't forget to put EmuVariableUefi-64.efi back into /EFI/Clover/drivers64UEFI folder. Then install new Nvidia web driver... and reboot. I made the mistake of NOT doing this, and my hackintosh would not boot. Had to manually copy EmuVariableUefi-64.efi back into /EFI/Clover/drivers64UEFI using terminal from Restore partition. All good now. Lesson here is pay attention to the little details so you don't hose yourself :banghead:
 
Make sure scan entries in GUI is true.
Code:
<key>GUI</key>
<dict>
...
<key>Scan</key>
<true/>
...
</dict>
Working NVRAM either hardware or emulated when you start the installer app. IgnoreNVRAMBoot is set to false.
Code:
<key>Boot</key>
<dict>
...
<key>IgnoreNVRAMBoot</key>
<false/>
...
</dict>

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.
 
Have you tried removing EmuVariableUefi-64.efi from your /EFI/Clover/drivers64UEFI folder? I had to do that on both my desktop and laptops to get the Hight Sierra Installer to finish.

-bth

@bthall, I forgot to mention that in my post, I don't have the EmuVariableUefi-64.efi in my Clover setup.

All resolved now, I sort of followed Violet Dragon's advice about creating pen drive although I didn't bother using it.

I just re-dowloaded macOS High Sierra which I think Apple updated to macOS 10.13 (17A405) and ran that install over my current install (which took about 25mins) and now I'm up to date.

Solved !

thanks Violet Dragon.
 
All resolved now, I sort of followed Violet Dragon's advice about creating pen drive although I didn't bother using it.

I just re-dowloaded macOS High Sierra which I think Apple updated to macOS 10.13 (17A405) and ran that install over my current install (which took about 25mins) and now I'm up to date.

Solved !

Quick addendum to jst say "me too". I tried and tried almost everything to get around this error,
even resorting to booting into recovery mode, terminal, and making the directory structure that
was missing and.. nada.

I suspect _very_ heavily, that this is, indeed, an APFS "issue". I did a timemachine, clean install
onto HFS+J, installed the patch via app store on top and .. it jst worked. no problems. annoying
as all hell but.. yeah. Solved (ish)
 
Status
Not open for further replies.
Back
Top