[WARNING] Clover update r4586 deletes OsxAptioFix3Drv-64.efi

[MysticalOS]

If you run installer like normal and do not do custom install to manually select OsxAptioFix3Drv-64.efi with this clover update, it completely removes OsxAptioFix3Drv-64.efi without warning which may leave you unbootable because you won't have it's replacement installed. Fortunately I always do smart thing and have a backup USB to emergency boot with a stable version of clover in case these things happen.

r4586 is stable, once you load AptioMemoryFix-64.efi (which is meant as replacement for OsxAptioFix3Drv-64.efi).

See https://www.tonymacx86.com/threads/...ptiofix3drv-64-efi.255174/page-2#post-1771018 further in thread for what's happening and how to avoid it going forward.

 

[Gigamaxx]

If you run installer like normal with this clover update, it completely removes OsxAptioFix3Drv-64.efi without warning which may leave you unbootable. It doesn't remove it because it's no longer needed, it just removes it period and makes you freeze on next boot if your system relied on it. Fortunately I always do smart thing and have a backup USB to emergency boot with a stable version of clover in case these things happen.

r4586 is stable, once you put OsxAptioFix3Drv-64.efi back where it belongs though.

Is it replacing it with a different version or aptiomemoryfix? Does it happen when you use customize option and select it?

 

[MysticalOS]

Custom option no longer even has v3 in install package at all, probably why it removed it. maybe deprecated or maybe accidentally omitted.
it did not replace it with another one. post install system froze like it normally would without memory remapping. So I used backup USB clover to boot and restore missing file.

Looks like someone else noticed it too
https://sourceforge.net/p/cloverefiboot/tickets/484/

 

[vulgo]

Possible explanation. The new ApfsDriverLoader driver only works with AptioMemoryFix?

Edit: Pulled from Clover ISO 4586 drivers in the image, boots fine

 

[Gigamaxx]

Interesting, I’ve found sometimes when loading a newer version of clover with rc scripts the EFI backups folder takes the old one. Sometimes they may conflict with drivers or config. Maybe removing EFI backup folder before loading it would work?

 

[MysticalOS]

I suspect it doesn't mess with it if you were using one of other fixes still included in package

but if you were using fix3 it removed it cause it's no longer supported by package. a user just doing a strait shot upgrade wouldn't know better and install a diff version of aptio fix so I see some issues for a few users, thus the warning.

 

[apt.dogcow]

If I don’t have a USB emergency to hand how can I get this back up and running. It’s booting to clover then no further from main drive or recovery partition.

 

[Gigamaxx]

If I don’t have a USB emergency to hand how can I get this back up and running. It’s booting to clover then no further from main drive or recovery partition.

Only hope maybe hit space bar once and select verbose, safe mode or single user and follow the prompts.

 

[apt.dogcow]

What’s the location of where OsxAptioFix3Drv-64.efi should go? Going to attempt to connect my SSD to a my MacBook Pro and restore a previous version in the EFI partition.

 

[Gigamaxx]

What’s the location of where OsxAptioFix3Drv-64.efi should go? Going to attempt to connect my SSD to a my MacBook Pro and restore a previous version in the EFI partition.

Clover/Drivers64efi folder.