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

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

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.

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.

 

[heniox]

Hi everyone,
I have a problem with SecureBootModel. When set to Disabled only one entry Windows can boot. Any other entries like macOS or Install macOS, although present in the OC boot menu cannot be booted. With the SBM set to Default Windows and Sonoma 14.3.1 boot correctly. Of course 14.4 shows the above described behaviour. What may wrong with my setup (OC-0.9.9 kext updated). Is something missing in my config.plist?
Thanks for any help.

 

[EliteMacx86]

Hi everyone,
I have a problem with SecureBootModel. When set to Disabled only one entry Windows can boot. Any other entries like macOS or Install macOS, although present in the OC boot menu cannot be booted. With the SBM set to Default Windows and Sonoma 14.3.1 boot correctly. Of course 14.4 shows the above described behaviour. What may wrong with my setup (OC-0.9.9 kext updated). Is something missing in my config.plist?
Thanks for any help.

Attach your EFI to check.

 

[heniox]

Attach your EFI to check.

OK, I solved it by adding:
UEFI - Qirks - DisableSecurityPolicy = TRUE

 

[Striker]

OK, I solved it by adding:
UEFI - Qirks - DisableSecurityPolicy = TRUE

It worked only by making DisableSecurityPolicy = TRUE?, or you changed the SecureBootModel too?

 

[heniox]

It worked only by making DisableSecurityPolicy = TRUE?, or you changed the SecureBootModel too?

I've changed SecureBootModel to Disabled, first of all, but it wasn't enough. After some reading the Open Core Guide I came to conclusion that changing that UEFI Quirk may help. And it did.
I have not tried the option only with changed quirk.

 

[Striker]

I've changed SecureBootModel to Disabled, first of all, but it wasn't enough. After some reading the Open Core Guide I came to conclusion that changing that UEFI Quirk may help. And it did.
I have not tried the option only with changed quirk.

Ohk, I thought you tweaked only UEFI Quirk. However, tweaking only UEFI Quirk won't fix the issue. Disabling the SecureBootModel is the key to get the issue fixed

 

[a3nk17]

Hello, Here is my efi please help I'm able to boot 14.3.1, but when I update to 14.4.1 it stuck and Karnal panics, and stuck at bootstraps fails sometimes and after restart it's stuck not able to boot into installation either I updated the all the kext also..! please guide here is the image also

 

[EliteMacx86]

Hello, Here is my efi please help I'm able to boot 14.3.1, but when I update to 14.4.1 it stuck and Karnal panics, and stuck at bootstraps fails sometimes and after restart it's stuck not able to boot into installation either I updated the all the kext also..! please guide here is the image also

This is not the KP but a prohibited sign as the system cannot find the root device.

 

[a3nk17]

This is not the KP but a prohibited sign as the system cannot find the root device.

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