Clover update stopped working system

[GreyWolfRon]

@Edhawk
I found the way to have disk1 default.

I was able to change the default boot option via Apple -> System Preferences -> Startup Disk to disk1.

So that issue is solved.

Now I can reboot and walk away and it boots right up the the Sonoma login splash!

 

[GreyWolfRon]

@Edhawk

Here is my up to date EFI file.

 

[Edhawk]

There is an alternative method for setting the default startup disk, undertaken from the OC boot screen/picker list.

Simply highlight the icon or name of the drive you want to boot automatically (after the timeout has completed) press and hold the 'Crtl' key then press the Enter/Return key. The icon below the macOS drive icon or name will change from an upward pointing arrow to a circular arrow. MacOS will boot and the next time you boot or restart your system the same drive will be used automatically.

This method doesn't work after a ResetNvram process, it has to be redone. But pressing two keys is hardly a chore!

I will have a look at your EFI and see about answering some of your other questions shortly.

 

[Edhawk]

When setting up macOS Sonoma to use a Broadcom WiFi card, you need to do a bit more than add and delete some kexts.

You also need to Disable System Integrity Protection (SIP) and Apple Mobile File Integrity (AMFI).
Then you need to run the OpenCore Legacy Patcher Modern WiFi root patches, so the old kexts from Ventura will work in macOS Sonoma.

See this guide for the process of getting a Fenvi card working in Sonoma.

Fenvi T919 and Broadcom wifi back in Sonoma with OCLP

Note: macOS Sonoma 14.4 breaks OCLP patch Post 418 (page 42). Good morning. My wifi is Fenvi T919. I know that it is not the ideal situation that many of us want to have the system as vanilla as possible, but what the OCLP team has achieved is amazing. I have followed TO THE LETTER the...

www.tonymacx86.com

 

[Edhawk]

To dual boot Mojave and Sonoma is a fairly easy fix. You don't need another EFI, you simply need to edit your current Sonoma booting config.plist, so the older APFS drivers used in Mojave & Catalina are allowed to be used.

1. You need to open your config.plist in your preferred Plist Editor, I use ProperTree.
2. Navigate to the UEFI section.
3. Then within the APFS sub-section, you need to edit the MinDate and MinVersion entries to allow Mojave to boot.

This table from the Dortania OpenCore guide shows the MinDate and MinVersion entries required for High Sierra, Mojave and Catalina.



OpenCore defaults to Big Sur or newer, so only these three older versions of macOS require edits to the config.plist.

The screenshot below shows the current settings for the UEFI > APFS section in your config.plist.



This is how it would look after adding the MinDate & MinVersion entries for Mojave.



With this change you can delete the Clover EFI from your 1TB drive, and just use OpenCore to boot in to Mojave and Sonoma. Both OS's should show an icon on the OC desktop, without any further input on your part.

The EFI attached below has a config.plist that has been edited as shown above.

Try it on a spare USB pen drive and see if it allows you to boot Mojave from your other drive.

 

[GreyWolfRon]

To dual boot Mojave and Sonoma is a fairly easy fix. You don't need another EFI, you simply need to edit your current Sonoma booting config.plist, so the older APFS drivers used in Mojave & Catalina are allowed to be used.

1. You need to open your config.plist in your preferred Plist Editor, I use ProperTree.
2. Navigate to the UEFI section.
3. Then within the APFS sub-section, you need to edit the MinDate and MinVersion entries to allow Mojave to boot.

This table from the Dortania OpenCore guide shows the MinDate and MinVersion entries required for High Sierra, Mojave and Catalina.

View attachment 576034

OpenCore defaults to Big Sur or newer, so only these three older versions of macOS require edits to the config.plist.

The screenshot below shows the current settings for the UEFI > APFS section in your config.plist.

View attachment 576037

This is how it would look after adding the MinDate & MinVersion entries for Mojave.

View attachment 576038

With this change you can delete the Clover EFI from your 1TB drive, and just use OpenCore to boot in to Mojave and Sonoma. Both OS's should show an icon on the OC desktop, without any further input on your part.

The EFI attached below has a config.plist that has been edited as shown above.

Try it on a spare USB pen drive and see if it allows you to boot Mojave from your other drive.

I copied your build to a USB stick, I deleted the EFI off of disk0 and rebooted from the USB. At the boot choices, I selected the disk0 and it went immediately to a circle with a diagonal line through it (where the Apple logo normally is) and froze.

 

[GreyWolfRon]

@Edhawk ,

I am looking for the AirportBrcmFixup.kext file. It is the only file I am missing to check the WiFi issue. I was able to find something on Github but it did not include the Kext. Any ideas?

 

[Edhawk]

The circle with the line through it (prohibited sign) is usually caused by the boot loader not being able to find the USB drive. Try another port. Make sure that XhciPortLimit quirk is enabled in your config.plist.

AirportBrcmFixup.kext can be downloaded from the Acidanthera Github repository lined below.

Releases · acidanthera/AirportBrcmFixup

An open source kernel extension providing a set of patches required for non-native Airport Broadcom Wi-Fi cards. - acidanthera/AirportBrcmFixup

github.com

For future reference, don't ever delete a working EFI from a drive until you are sure the one on the USB you are testing works without any issues.

If you do, make sure you have a copy of the working EFI on another USB pen drive, so you can still boot in to macOS without having to recreate the EFI.

 

[GreyWolfRon]

The circle with the line through it (prohibited sign) is usually caused by the boot loader not being able to find the USB drive. Try another port. Make sure that XhciPortLimit quirk is enabled in your config.plist.

AirportBrcmFixup.kext can be downloaded from the Acidanthera Github repository lined below.

Releases · acidanthera/AirportBrcmFixup

An open source kernel extension providing a set of patches required for non-native Airport Broadcom Wi-Fi cards. - acidanthera/AirportBrcmFixup

github.com

For future reference, don't ever delete a working EFI from a drive until you are sure the one on the USB you are testing works without any issues.

If you do, make sure you have a copy of the working EFI on another USB pen drive, so you can still boot in to macOS without having to recreate the EFI.

I have a working config.plist in an EFI folder on a second USB drive for a "Just in Case" issue.

I was able to reboot and boot from the disk1 with no issues. Just when I try the disk0 that, that happens.

I will check the XhciPortLimit quirk is re enabled and try again. I disabled it after I did mo portmapping.

 

[Edhawk]

If you have a USB port map, I would check it is correct. As the prohibited sign doesn't normally appear when you have a correctly configured USBPorts.kext or USBMap.kext. Assuming you were using one of the active ports from the USB map when the error occurred.