<< Solved >> Fail to boot after upgrading from Clover r4910 to r5033...

I am on macOS 10.14.5. After upgrading from Clover r4910 to r5033 my hackintosh fail to boot. It goes into black screen after entry of the boot option. What might be causing this anomaly? Also, since Clover installer is an pkg file, is it possible to manually recover the clover back to an older version via external drive? Thanks.

This is how I fixed it. I install Clover r5033 to an USB stick on my macbook pro and checked OsxAptioFix3Drv.efi in custom installation section. Then I place the OsxAptioFix3Drv.efi into my EFI disk via Windows 8 bootable stick.

aeroxy said:

What might be causing this anomaly?

Click to expand...

The directory structure has changed.
But the most likely cause is the lack of a memory fix driver, the Clover installer will delete it if you do not specify it when you install.

aeroxy said:

is it possible to manually recover the clover back to an older version via external drive?

Click to expand...

Each time that you update Clover a copy of your /EFI folder is saved to the system disk in /EFI-Backups.

P1LGRIM said:

The directory structure has changed.
But the most likely cause is the lack of a memory fix driver, the Clover installer will delete it if you do not specify it when you install.



Each time that you update Clover a copy of your /EFI folder is saved to the system disk in /EFI-Backups.

Click to expand...

Thx, but since I am booting from Windows, I cannot visit the system disk. Is there another method to replace EFI to a correct one?

aeroxy said:

Thx, but since I am booting from Windows, I cannot visit the system disk. Is there another method to replace EFI to a correct one?

Click to expand...

Your USB boot disk same as when you installed.

I'm on the process of updating to the latest Clover build as well and notice the changes. I cannot find the AptioMemoryFix from the new Clover though. This is what is working for my build. I tried the 2/3 fix before but they don't work.
I think I'll stick with my old Clover.

My USB boot disk was from three years ago and was on an old Clover that doesn't support 10.14.5...

aeroxy said:

My USB boot disk was from three years ago and was on an old Clover that doesn't support 10.14.5...

Click to expand...

Typically however you installed is also your path to recovery and a boot disk is the easiest way. If you don't have a boot disk or another mac to make one or edit what is on your EFI folder then you are up the creek.

hackmefrancis said:

I'm on the process of updating to the latest Clover build as well and notice the changes. I cannot find the AptioMemoryFix from the new Clover though. This is what is working for my build. I tried the 2/3 fix before but they don't work.
I think I'll stick with my old Clover.

Click to expand...

I'm on my phone and I forget exactly how the new directory structure in the clover folder is structured but if I remember right there are two new folders. One is labeled "bios" and the other "drivers". The "drivers" folder is meant to replace the UEFIDrivers64 folder. That folder is left in place, even though it is not accessed, and usually a copy of the drivers you had installed will be left in there. If Clover didn't copy them to the new "drivers" folder, because of how you chose to install, you can always copy them over yourself.

Hope that makes sense, I will check later and revise this as needed. Pretty much the same except different.

Just to say that reading the readme's that the new Clover puts into the UEFi drivers directory I read it as they should go into the BIOS folder! which dont seem right. If someone can properly interpret what the readme's mean, it might be worth putting that on here.

Installing v5033 does not remove the earlier folder structure. All the drivers are now 64 bit and reside in /EFI/CLOVER/drivers/UEFI/. Since the old folder is not deleted, you can copy the AptioMemoryFix-64.efi (and rename it to aptiomemoryfix.efi if you wish) to the UEFI folder.