macOS Sonoma 14.5 third installation stage infinite reboot (with EFI from 14.4.1)

[El'Xsanori Leo]

Hello. Today I ended up updating my working macOS Sonoma 14.4.1 installation in an unsuccessful re-installation of 14.5. The problem was that after the update via install app I couldn't boot into black screen installation stage (the system just kept rebooting into unmodified 14.4.1 before showing the left time). Updating via USB broke my system entirely, so I decided to reinstall everything. But, after passing the setup and first black screen installation stage with the time left label I got the infinite rebooting again. There is no kernel panic, no suspicious lines in the -v log (I haven't yet made it to create a log file). Could you help me, please? What exactly should I do to catch the error? Thank you very much for any help!

UPD. Very similar to https://dortania.github.io/OpenCore...g/extended/kernel-issues.html#stuck-on-ramrod, but it is not actually stuck, it just normally triggers the shutdown event, plus I managed to boot into the installer GUI

 

[leesurone]

Hello. Today I ended up updating my working macOS Sonoma 14.4.1 installation in an unsuccessful re-installation of 14.5. The problem was that after the update via install app I couldn't boot into black screen installation stage (the system just kept rebooting into unmodified 14.4.1 before showing the left time). Updating via USB broke my system entirely, so I decided to reinstall everything. But, after passing the setup and first black screen installation stage with the time left label I got the infinite rebooting again. There is no kernel panic, no suspicious lines in the -v log (I haven't yet made it to create a log file). Could you help me, please? What exactly should I do to catch the error? Thank you very much for any help!

UPD. Very similar to https://dortania.github.io/OpenCore...g/extended/kernel-issues.html#stuck-on-ramrod, but it is not actually stuck, it just normally triggers the shutdown event, plus I managed to boot into the installer GUI

Usually after 14.0 we have to disable all Wifi and Bluetooth kexts temporarily and set Misc/ Security/ SecureBootModel in the config.plist to Disabled (from Default) or the system will stick in a reboot pattern. Make sure to reset NVRAM after you make the changes and cross your fingers and toes.

 

[El'Xsanori Leo]

Usually after 14.0 we have to disable all Wifi and Bluetooth kexts temporarily and set Misc/ Security/ SecureBootModel in the config.plist to Disabled (from Default) or the system will stick in a reboot pattern. Make sure to reset NVRAM after you make the changes and cross your fingers and toes.

Unfortunately, that didn't help. I have no physical WiFi, only Ethernet en0. I tried disabling my only BlueToolFixup kext (which btw didn't affect updating from 14.3 to 14.4.1 on my PC), disabling SecureBootModel (which is by default set to j160 in my case of MacPro7,1 SMBIOS). Also I have my NVRAM reset, I do it every time I change config.plist

 

[leesurone]

Unfortunately, that didn't help. I have no physical WiFi, only Ethernet en0. I tried disabling my only BlueToolFixup kext (which btw didn't affect updating from 14.3 to 14.4.1 on my PC), disabling SecureBootModel (which is by default set to j160 in my case of MacPro7,1 SMBIOS). Also I have my NVRAM reset, I do it every time I change config.plist

Zip and upload your EFI folder so we can see how you have it configured. I'm sure someone will be able to help

 

[El'Xsanori Leo]

Zip and upload your EFI folder so we can see how you have it configured. I'm sure someone will be able to help

Nevermind, I have this tricky thing booted Maybe it helped editing the config from Debian instead of Windows, but I finally got to the macOS GUI and even fixed the "your screen recording cannot be saved" problem (it was caused by the QuickTime not added to the list of applications, which have access to the screen recording, by default). So, the solution for my PC was to disable sbm editing the config file from Linux. I am not sure it will help with upgrading macOS, but it worked for installing it. Also, I did not have to disable the bt kext, but maybe that's because I have a USB dongle

 

[leesurone]

Nevermind, I have this tricky thing booted Maybe it helped editing the config from Debian instead of Windows, but I finally got to the macOS GUI and even fixed the "your screen recording cannot be saved" problem (it was caused by the QuickTime not added to the list of applications, which have access to the screen recording, by default). So, the solution for my PC was to disable sbm editing the config file from Linux. I am not sure it will help with upgrading macOS, but it worked for installing it. Also, I did not have to disable the bt kext, but maybe that's because I have a USB dongle

Awesome, there are three bluetooth kexts needed for intel bluetooth and it's been recommended that those be disabled, your situation though was unique.

 

[El'Xsanori Leo]

Approved. The only two things needed to successfully update my ryzentosh are disabling SecureBootBodel and resetting NVRAM. BlueToolFixup in sole does not affect this process. Tested on Sonoma to Sequoia jump.

 

[Archibald]

Hello. Today I ended up updating my working macOS Sonoma 14.4.1 installation in an unsuccessful re-installation of 14.5. The problem was that after the update via install app I couldn't boot into black screen installation stage (the system just kept rebooting into unmodified 14.4.1 before showing the left time). Updating via USB broke my system entirely, so I decided to reinstall everything. But, after passing the setup and first black screen installation stage with the time left label I got the infinite rebooting again. There is no kernel panic, no suspicious lines in the -v log (I haven't yet made it to create a log file). Could you help me, please? What exactly should I do to catch the error? Thank you very much for any help!

UPD. Very similar to

https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#stuck-on-ramrod​

, but it is not actually stuck, it just normally triggers the shutdown event, plus I managed to boot into the installer GUI
papa's scooperia​

Has anyone experienced similar issues with macOS installation, particularly with the transition from 14.4.1 to 14.5? What troubleshooting steps or logs should I check to identify the root cause of the infinite rebooting?

 

[Edhawk]

From memory, updating macOS Sonoma to 14.4 was a nightmare for most users, even those with real Macs. 14.4.1 was released within 2-3 weeks of 14.4 to fix a lot of the issues. But some weren't fixed until 14.5.

14.4.1 and 14.5 required a number of new kexts, updating OpenCore to 0.9.9 (March 2024) or with 14.5 to OC 1.0.0 (May 2024).

Which version/release of OpenCore are you using?
Are you using releases of the latest kexts?

We currently have no idea what you are using to boot your Hack, or for that matter what components are used to create your Hack. So the information and the two questions above are as good as it will get, until you provide some solid information on what you are using, i.e a copy of your current EFI folder would be good with details of the main components in your Hack.

Adding the Hack component details to your signature would be helpful.

 

[Rayankaa]

Nevermind, I have this tricky thing booted Maybe it helped editing the config from Debian instead of Windows, but I finally got to the macOS GUI and even fixed the "your screen recording cannot be saved" problem (it was caused by the QuickTime not added to the list of applications, which have access to the screen recording, by default). So, the solution for my PC was to disable sbm editing the config file from Linux. I am not sure it will help with upgrading macOS, but it worked for installing it. Also, I did not have to disable the bt kext, but maybe that's because I have a USB dongle

Could you share your EFI please I have same problem infinite restart and I have no idea to fix it thankyou

 

[Rayankaa]

Nevermind, I have this tricky thing booted Maybe it helped editing the config from Debian instead of Windows, but I finally got to the macOS GUI and even fixed the "your screen recording cannot be saved" problem (it was caused by the QuickTime not added to the list of applications, which have access to the screen recording, by default). So, the solution for my PC was to disable sbm editing the config file from Linux. I am not sure it will help with upgrading macOS, but it worked for installing it. Also, I did not have to disable the bt kext, but maybe that's because I have a USB dongle

 

[Rayankaa]

Approved. The only two things needed to successfully update my ryzentosh are disabling SecureBootBodel and resetting NVRAM. BlueToolFixup in sole does not affect this process. Tested on Sonoma to Sequoia jump.

here my EFI