Great find! The option is still available in Big Sur, so having another APFS volume with BS could eliminate the need to go back to HS.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Edit, later: I was thinking of High Sierra's APFS, not Big Sur's, see @deeveedee's post below.
Last edited:
Good morning,
I have a late 2009 21.5" Imac (10,1) currently running Ventura 13.6 and trying to install Sonoma 14.4.1 utilizing OCLP 1.4.3 and a USB installer. Everything is fine until I get to rebooting while holding the alt/option key. click on the USB EFI Boot icon and then the 'install Sonoma' icon. So far so good, but before it takes me to the recovery screen I get the forbidden sign (circle with diagonal thru it) and the wording "support.apple.com/mac/startup".
I'm using a wired keyboard and mouse and have already tried a different USB and downloading a second time the installer.
Can'f find this problem in the troubleshooting section of Github.
Anyone have any suggestions?
Thanks in advance, Jim
I have a late 2009 21.5" Imac (10,1) currently running Ventura 13.6 and trying to install Sonoma 14.4.1 utilizing OCLP 1.4.3 and a USB installer. Everything is fine until I get to rebooting while holding the alt/option key. click on the USB EFI Boot icon and then the 'install Sonoma' icon. So far so good, but before it takes me to the recovery screen I get the forbidden sign (circle with diagonal thru it) and the wording "support.apple.com/mac/startup".
I'm using a wired keyboard and mouse and have already tried a different USB and downloading a second time the installer.
Can'f find this problem in the troubleshooting section of Github.
Anyone have any suggestions?
Thanks in advance, Jim
Big Sur, Monterey, Ventura and Sonoma co-exist without issues. I think it might be High Sierra that you're thinking about. I have BS, M, V and S all on a single drive / container (separate APFS volumes) booting from the same Open Core EFI (post-install patches applied with different versions of OCLP based on my preferences).
Are you certain that you are booting with the OCLP-1.4.3-generated EFI for your Mac Model? Some things to check:
- If you built Open Core EFI on a separate Mac, did you select the right MacModel target in OCLP settings?
- If you have one version of Open Core EFI installed on the USB and another on your SSD, are you certain that you are booting with the correct OC EFI?
I did build the open core EFI (USB) on the same mac that I am planning to upgrade and it did have the same host (10,1).
Also the built OCLP on this Imac is 1.4.3. Could it still be different between the USB and the computer. And I did confirm that I was booting from the USB EFI and not the computer EFI.
Will reaet NVRAM and try again.
Thanks for mentioning NVMeFix. My 2013 MBA 6,2 has panicked almost daily since installing 14.4.1, which I mentioned in an earlier post. I reboot daily to stay ahead of it. It did occur to me it might be an NVMe issue. I'm hoping the next update will fix it without necessitating NVMeFix. Do you know if it's necessary to compile it with developer tools?
Hi all, seem to have a major issue with a MacBook Air 6,2 and a Mac mini3,1, have been trying to install sonoma on them both, and did have them working however went to try and start both of them yesterday and neither would boot, they both stuck on The progress bar. I tried the fix on dordinas site and again didn’t start so I thought I would try and reinstall a copy of ML I had to allow me to wipe the drives. That didn’t do anything either. I’m now stuck with 2 macs that I can wipe, restore or install any OS on.
Anyone any pointers?
For info these are not the only macs I have with sonoma on I have on a 5,2 Air and also a 7,1 iMac. Both of those have no issues.
To me it seems like I have corrupted the main efi on them, they both single chime however.
Thanks
Anyone any pointers?
For info these are not the only macs I have with sonoma on I have on a 5,2 Air and also a 7,1 iMac. Both of those have no issues.
To me it seems like I have corrupted the main efi on them, they both single chime however.
Thanks
Tried an NVRam & PRam reset? After that try to boot an OCLP bootstick, it always make sense to have ab OCLP bootstick configured and matching your mac hardware for safety reasons. Your hardware should be not a problem with sonoma - choose oclp 1.4.3 or better 1.5.0n if you familiar with nightly oclp builds, as always use dortania's docu.
Well, I believe NVMeFix is just a kext that gives MacOS better compatibility with 3rd party NVMe drives and controllers that Apple doesn't officially support. You shouldn't need to compile anything, I think it works on any Mac or Hackintosh with OpenCore. But when I install OCLP on my MacPro with an NVMe PCIe card in it, it automatically installs NVMeFix so you might already have it.
In that scenario you described, are you booting from an USB stick? Do the volumes in question appear in disk utility? What volumes show up in boot picker?
Ive tried that, but still no difference. I've actually tried connecting through a USB hub as well, with the same results.
OK strange was worth a try... (May also check the firmware of your device etc., i don't think that it's an oclp related issue)
Can you guys specify exactly how much of the config file to edit out? Im on iMac 11.1 and no matter what part I edit out, it hangs shortly, then reboots "Your computer restarted because of a problem.."..
You've referenced a post from Oct 2023. OCLP development has been very dynamic. Be sure that old posts are still relevant.
EDIT: if you really want to delete revpatch=sbvmm in your OC config.plist, there's a single NVRAM property to delete using your preferred plist editor. When you manually edit the config.plist, it is a good idea to use Open Core's ocvalidate. If what I'm describing sounds foreign to you, then learn about Open Core before manually editing the config.plist.
Last edited:
It's regarding avoiding Software Update to suggest Sonoma from lower versions. Should still apply.
Ok. If you understand how the Open Core config.plist is structured, then deleting the NVRAM property revpatch with assignment sbvmm should be something that you understand. If you don't understand how the config.plist is structured, I'm reluctant to give steps as they might simply lead to other things that you don't know how to manually maintain. It's important to understand manual editing, because you'll need to manually edit after every new OCLP "Build and Install Open Core."
You're probably trying to be helpful. Lead to what "other things", exactly..?
I removed those 2 lines from the config on at least 4 different iMacs without problems, to prevent the Sonoma update. For some reason it's not working on this 11.1 model.
You give me too much credit. Did you run ocvalidate after making the changes?
No, I always just reboot and it worked flawlessly.
EDIT: Reinstalled the machine completely, now it works. Thanks.
Last edited:
I just purchased a 2017 MacBook Pro 2 thunderbird 3 model from someone at my job who needed the money to get his personal vehicle out of impound, think it is pretty crappy the city towed his vehicle when we were providing assistance for the eclipse event in Chicago, but that's for another place. Got it for $200.00 in mint condition. Just wondering if there is any known issues updating it to Sonoma, with the intel iris plus graphics 640. It supports Ventura, so I wouldn't think there would be any problems doing Sonoma, especially since I got 14.4.1 running on my mid 2010 MacBook Pro and it works very nicely. Just figured it might be a good idea to have a newer more modern MacBook Pro and he needed help to get his vehicle out of impound...... good time to have extra cash on me.
I think I remember seeing a post a while back suggesting that if a Mac natively supports Ventura, Sonoma won't need as much patching depending on the mac as a lot of the drivers may still be in. Sonoma. Kind of like Monterey on a Mac that natively supports Big Sur, it needs OCLP to boot but it doesn't need to be root patched. Not sure if Ventura and Sonoma officially share the same type of thing, but I thought I saw something suggesting it was similar,.