MacOS Mojave doesn't show up in the Clover menu anymore

[playerslayer123]

There has been another thread about it and I've tried following the suggested troubleshooting steps.
A user suggests

In recovery/installer, maybe try something along these lines

diskutil apfs list

but I thought in order to go to use diskutil commands I need to be able to access the diskutility program of the partition I'm trying to fix, don't I? Well, since it doesn't show up in the clover menu at all I don't understand how I'm supposed to do that.

 

[Edhawk]

You need to check which drivers are present in your /CLOVER/drivers/UEFI folder.

• For APFS formatted drives you need to have ApfsDriverLoader.efi present, not a specific apfs.efi driver.
• For HFS+ formatted drives you need to have HFSPlus.efi or VBoxHfs.efi present, not both.

If you boot with your macOS Installation USB drive, as if you were going to reinstall macOS. You can access Disk Utility and Terminal as part of the installation process. This may allow you to rectify any issues you may have introduced to your macOS drive.

But here is a cautionary note: You need to know what you are doing before you start messing with either application. As you are just as likely to cause issues to your setup undertaking 'fixes', than you are to resolve your current issue, especially if you aren't sure what each command you enter will do.

 

[playerslayer123]

You need to check which drivers are present in your /CLOVER/drivers/UEFI folder.

• For APFS formatted drives you need to have ApfsDriverLoader.efi present, not a specific apfs.efi driver.
• For HFS+ formatted drives you need to have HFSPlus.efi or VBoxHfs.efi present, not both.

a thing I forgot to ask:
/CLOVER/drivers/UEFI folder is how the folders on the USB installer are called, whereas the ones on the disk containing MacOS are called /CLOVER/drivers64UEFI

So this solution is about adding/deleting files on the USB installer and completely reinstalling MacOS and losing my files, right? or can this be done while keeping my files?

 

[Edhawk]

What I am suggesting is that you check to see which files are already in the /CLOVER/drivers64UEFI folder.

If the ones I mentioned are not present add them to the folder.

If both an apfs.efi and ApfsDriverLoader.efi are present, remove the apfs.efi driver. As that is a specific version of the APFS driver, which will only work with a specific version of the APFS implementation.

The ApfsDriverLoader.efi loads the relevant driver for the version of macOS you are using.

There is no need to completely reinstall macOS. This is a simple boot loader fix.

Also if your CLOVER folder contains a drivers64UEFI folder you are probably using an old version of Clover. Since Clover_r4986 (or there about) Clover has used a new folder structure, which did away with the drivers64 and drivers64UEFI folders and replaced them with a /CLOVER/drivers/BIOS, which replaced the drivers64 folder and /CLOVER/drivers/UEFI, which replaced the drivers64UEFI folder.

If upgrading the Clover version the old and new folders can be present, but Clover looks to the drivers folder first and only falls back to the old folders if there is nothing present in the UEFI or BIOS folders.

Old CLOVER folder structure:


Newer CLOVER folder Structure:


Contents of new /CLOVER/drivers folder:


I would recommend you upgrade your Clover version to Clover_r5119 or r5120. These were the last two versions where OC didn't take control of the boot process. Both versions work really well with Mojave and Catalina. A copy of Clover_r5119 is attached.

When updating your Clover version I would recommend creating the Bootloader on a spare USB pen drive, leaving your current setup in place. After installing the new version of Clover to the EFI partition on the USB drive. Editing the CLOVER folder contents to match your system requirements. I would boot from the USB drive, to check that the new version works as expected.

If it doesn't boot macOS, you will have your original bootloader in place that can be used to boot back in to macOS to fix any issues with the new Clover setup.

You don't overwrite the existing Clover EFI folder until the new version works. Logically it would be wise to keep a copy of the original Clover EFI folder to hand, in case you need to revert to the old one in the future.