Search results

Success! Used a separate SSD as a test disk to iron out all the kinks. Started with building OC 0.6.3 EFI folder, verified that it booted both Catalina and the Big Sur USB installer. I then installed Big Sur from USB to my test SSD and checked for stability. Made a few modifications to my...

Hehe, who can remember? It was long ago

@Stork Thank you so much for the guide! I've ordered the same MB + i7 8086K. Can you please share your EFI folder + SSDT's to make my life (and probably others who'll copy this build) easier once it arrives? :mrgreen:

Update went smoothly, which only deepens the confusion. It looks like it wasn't injecting the kexts and by forcing it from the clover menu, it worked. I'm now using the same setup I was using before, which wouldn't boot. So strange.

Not I'm back at 10.3.3 and about to try the update again. Here goes nothing...

I was finally able to boot into macOS. Here's how: 1. I was desperate and thought maybe because I had 2 drives with clover, there was some kind of collision. So I erased them both and tried to boot from USB installer. Didn't work. 2. I re-flashed my BIOS because I read that it was the only way...

r4411

Tried some of those combinations...still getting error loading kernel cache.

Have already tried those. But not with the config.plist you provided. I'll give it a try. Appreciate your help!

I attached the current EFI folder to my previous post. Edit : I deleted NullCPU Kext. No change.

Tried it with a new clover USB boot drive I created. Now getting this: Edit: Attached is the new EFI folder of the boot drive

Thanks for joining Sir! I tried the config.plist. Same "does printf work??" I keep NullCPUPowerManagement.kext because it's necessary for the x79 platform to have working power management (As far as I know). I could boot without it (before this current saga began), but the cpu would run 10-20...

When booting without -v I get a No Entry Sign. I tried slide=0, cpus=1, busratio=32. Tried safe mode, not injecting kexts etc. This really is weird. If only I could somehow get access to the drive, I'd replace the APFS.efi...

I have 4x4 GB of memory. Took out 2 sticks and booted with 8GB, thought maybe it would change something...Didn't. I keep seeing this. Can't get past it.

Windows boots perfectly, of course, but can it be a hardware issue? What does this error refer to anyway?

Yes :) Each drive is independent with its own clover. I tried unplugging the other drive and boot only with the NVME I wanted to update. Same deal. Tried the other way, unplugging the NVME and booting the other (supposedly untouched) drive. Same deal. Unplugged the computer for 30 min. Tried...

Hey Draque, Each drive is independent with its own clover. I tried unplugging the other drive and boot only with the NVME I wanted to update. Same deal. Tried the other way, unplugging the NVME and booting the other (supposedly untouched) drive. Same deal. Unplugged the computer for 30 min...

Thank you for answering! I have tried both of your suggestions. Didn't make a dent. Also, what confuses me even more, why would changing the APFS.efi file on one partition affect all boot drives, even though I'm booting to totally different drives?

Had a perfectly working 10.3.3 system. Updated via App Store. Before rebooting, I updated the APFS.efi file in clover. I don't know what could have happened, but now I can't boot to any macOS system. I have one nvme 960 evo and one 840 evo both with different versions of macOS. None will boot...

Had a perfectly working 10.3.3 system. Updated via App Store. Before rebooting, I updated the APFS.efi file in clover. I don't know what could have happened, but now I can't boot to any macOS system. I have one NVMe 960 EVO and one 840 EVO both with different versions of macOS. None will boot...