GUIDE How to Fix Reboot Loop when installing or Updating to macOS Sonoma 14.4 and Later

How to Fix Reboot Loop when installing or Updating to macOS Sonoma 14.4 and Later​

This guide covers fixing the reboot loop when performing a clean installation of macOS Sonoma 14.4 or updating an existing version of macOS to macOS Sonoma 14.4. By following this guide, you'll be able to do a clean install and/or update to macOS Sonoma 14.4 successfully on your non-Apple computer.

Overview​

macOS Sonoma is the current and latest macOS version from Apple for their Mac lineup. Recently, Apple announced macOS Sonoma 14.4 (23E214) which has major changes and with this update, a lot of things have been changed. Once again, the WiFi stacks are changed which has brought a new issue on Legacy Macs as well as non-Apple computers.

A major issue has been seen with this update. If you have ever attempted to clean install or update to macOS Sonoma 14.4, you might have noticed that once the second stage of the installation and/or update finishes, the system enters the boot loop state and if you are updating it to macOS Sonoma 14.4 instead of a clean install, you'll notice that the macOS does not get updated to 14.4 but the system remains still to 14.3 or the existing version and the macOS Installer Volume is still present. This is because the update package was fully not processed by the system.

This does not seem to be a potential bug but a new must-have requirement and a lot of non-Apple users are impacted due to this major update release. Luckily, there is a fix for it and that is too easy. Whether you're doing a clean install or updating to macOS Sonoma 14.4, the fix is universal and involves the same procedure for both cases. In addition, the fix works for both, i.e. Clover and OpenCore as Clover also uses OpenCore as a boot medium.

The guide is tested and reported to be working on macOS Sequoia as well.

To fix the issue, follow the steps below:

1. Ensure you're running the latest OpenCore 0.9.9 and the related kexts are up to date. See Updating OpenCore and Kexts for more information.
2. Mount your ESP.
3. Open your config.plist using any XML editor from the EFI/OC directory.
4. Set the SecureBootModel to Disabled instead of Default under the Misc>Security section of your config.plist.
5. Save your config.plist.
6. Restart your system for the applied changes to take effect. It is recommended to reset NVRAM twice at least.

Now you can continue with the installation and if you're updating to macOS Sonoma 14.4, you can continue with the update.

 

[EliteMacx86]

So please guide how can i fix this, please modify the efi and give ne so we can install

Are you booting via USB or the boot drive itself?

 

[a3nk17]

Booting through Pendrive,I'm still facing errors please guide,I attached the EFI please modified if necessary Thanks

 

[a3nk17]

please help boss

 

[a3nk17]

Hi PLease guide me the solution what I do?

 

[henkiew]

I had the same issue as described by @heniox.
The upgrade was acting correct as described in this article.
After ressetting NVRAM a couple of times I still had no luck.
After preparing for a new install and resetting my NVRAM one more time "the next day" it just started like normal and i'm on 14.4.1.
Is there already a known reason for this? And will it be solved in OC 1.0.0?
And the recommended setting for `SecureBootmodel` default is still working after the upgrade. My model is set to MacPro7,1 but there are settings for the used model I think I never used. Should I? And is that maybe the reason of the error?
• j160 --- MacPro7,1 (December 2019). Minimum macOS 10.15.1 (19B88)

 

[EliteMacx86]

Hi PLease guide me the solution what I do?

What problem are you having now?

 

[EliteMacx86]

I had the same issue as described by @heniox.
The upgrade was acting correct as described in this article.
After ressetting NVRAM a couple of times I still had no luck.
After preparing for a new install and resetting my NVRAM one more time "the next day" it just started like normal and i'm on 14.4.1.
Is there already a known reason for this? And will it be solved in OC 1.0.0?

Probably, because sometimes, the NVRAM does not get reset properly until the caps are drained off.

And the recommended setting for `SecureBootmodel` default is still working after the upgrade.

The recommended settings for SecureBootModel is Disabled to fix the error.

My model is set to MacPro7,1 but there are settings for the used model I think I never used. Should I? And is that maybe the reason of the error?
• j160 --- MacPro7,1 (December 2019). Minimum macOS 10.15.1 (19B88)

As you no longer have the issue, you're good!

 

[TripleYoThreat]

Can anyone explain 'why' this is required for the 14.4 install? so odd.

and is a real mac instructed to disable it's 'SecureBootModel' or T2 chip for the update?

 

[EliteMacx86]

Can anyone explain 'why' this is required for the 14.4 install? so odd.

and is a real mac instructed to disable it's 'SecureBootModel' or T2 chip for the update?

Cause, its not an real Apple hardware

On real Mac, you don't need to disable anything.