Updated to 10.14.5 - Clover UEFI does not even launch now

[Careless]

[SOLVED TEMPORARILY - SEE END OF POST]

 

Upgrading from Mojave 10.14.4, I did not make any changes to my Clover EFI folder. The version BEFORE upgrade was r4920, and latest necessary kexts to boot 10.14.5 were already installed and working for me on 10.14.4, so everything was ready to go.

 

10.14.4 worked fine with no issues for a while now, with the latest Clover and kexts.

 

Upon installing macOS update, after completing the grey progress bar / apple logo screen, the computer rebooted and now Clover is not loading, and I am greeted with this screen:

 

 

It's just a black screen with a solid cursor. No mouse input, no keyboard input, nothing else loads. Left it there for a while- no progress.

 

to be clear: CLOVER DOES NOT LOAD if I select the UEFI 'Clover HDD' entry on my boot selection list. it shows the screen above

 

I then created a bootable USB via my hackintosh laptop using the Mojave Installer and installed Clover UEFI on the ESP of the bootable USB, and then overwrote the EFI folder with my known good EFI folder backup.

 

result: CLOVER DOES NOT LOAD if I select 'UEFI: Bootable USB' entry on my boot selection list. it shows the same screen above.

 

 

 

I then attempted to create a bootable legacy CLOVER USB via windows:

result: CLOVER BOOTS as LEGACY USB.

 

The resulting Clover is indeed r4920 as it should be, but it does NOT list any of the MacOS partitions, I am trying now again with APFS loader for legacy .

 

 

I cannot boot into UEFI Shell either on USB or on Clover drive.

 

I tried EasyUEFI to redirect the UEFI entries to the SHELL-X64.efi file so that I can perhaps inspect the UEFI boot table to see if there is something wrong:

result: Shell does not boot. Same screen as above.

 

What is the possibility that the UEFI table in my bios suddenly corrupted?
If possible, why does my Windows Boot Manager entry seem to work fine?

 

Anyone ever experience something similar?

 

 

----------------------------------------------------------------------------

 

[SOLVED TEMPORARILY]

 

The problem lies with ApfsDriverLoader.efi

 

I managed to fix the issue by doing the following:

• Boot into Windows 10
• Used UFS Explorer Standard Trial version to browse the newly updated, but unbootable MacOS 10.14.5 to retrieve the apfs.efi file from /usr/standalone/i386/apfs.efi
• Used Explorer++ opened with Administrator Privileges to access EFI partition on MacOS drive:
  • Remove ApfsDriverLoader.efi
  • Replace with apfs.efi from macOS drive in previous step.
• Reboot using MacOS EFI partition that was just modified
• Successfully booted and typed this post update

 

It seems there may be an issue with ApfsDriverLoader-64.efi.
Has anyone experienced anything similar?

 

I am going to try again now with the latest version, which I believe I tried already- but perhaps it needed to do one final last load for some reason before being able to use the loader file and report back.

Edited May 22, 2019 by Careless

[Careless]

----------------------------------------------------------------------------

UPDATE 2 - [SOLVED!]
----------------------------------------------------------------------------

 

So the problem seems to lie within whatever version ApfsDriverLoader-64.efi I was using prior to update, or perhaps the OS needed to load one last time to enable some sort of permission for accessing the apfs.efi file from the /usr/standalone/i386/ folder that I am unaware of???

Either way, I am marking this solved at this point- just update your ApfsDriverLoader-64.efi in your drivers64UEFI folder with the latest (2.0.7 release as of this post)

https://github.com/acidanthera/AppleSupportPkg/releases

 

I just dumped all the files in the Driver folder within the latest zip into my drivers64UEFI and removed apfs.efi from my previous "Update 1" edit, and it booted with no issues.