macOS 14 Sonoma on Unsupported Macs Thread

[Ready-for-Apple]

I booted up an old iMac running HighSierra paired and reset my MagicMouse using factory reset all connected Apple devices via Click Bluetooth Shift Option in Menubar.

Suddenly the mouse is recognized without any issues and works like charm.

Hope this helps.

So your solution is to have another Mac or partition with High Sierra to do the reset?🫤
Would be great to have the possibility to reset directly in Sonoma or by third party app.

 

[deeveedee]

Since the option "Reset Bluetooth module" is not available anymore in Sonoma ...

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.

 

[rehkram]

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.

I seem to recall that there are APFS versioning incompatibilities running Big Sur on a drive shared with later macOS versions? I might be misremembering though. Someone will know.

Edit, later: I was thinking of High Sierra's APFS, not Big Sur's, see @deeveedee's post below.

 

[JimmyT72]

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

 

[deeveedee]

I seem to recall that there are APFS versioning incompatibilities running Big Sur on a drive shared with later macOS versions? I might be misremembering though. Someone will know.

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).

 

[deeveedee]

Anyone have any suggestions?

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?

EDIT: and as @K two always reminds us, did you reset NVRAM before attempting the new installation?

 

[JimmyT72]

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?

EDIT: and as @K two always reminds us, did you reset NVRAM before attempting the new installation?

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.

 

[dogen]

I just upgraded my Ventura Mac Pro 5,1 to Sonoma 14.4.1 and I am getting those same NVMe controller crashes every day or so. Anyone know if there is a solution? I am using a WD SN740 512gb blade in a "xqjtech" PCIe 3.0 4x card from Amazon. Was working fine with Ventura.

I notice on the NVMeFix github page it says:
NOTE: NVMeFix supports up to macOS Sonoma (14), but some features might not be available on newer versions as of now, like the timeout panic fix.

And then there is a boot-arg parameter:
nand-io-timeoutms: Timeout for NVMe requests in ms, 35 s by default

I wonder if changing this would help... or if that note means 14.4.1 no longer works with this "timeout panic fix".

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?

 

[jon8214]

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

 

[PropClear]

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

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.

 

[Serqetry]

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?

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.

 

[madmind]

Is your interface linked to internal usb or pcie usb 3 card?

It's linked to the internal.

 

[PropClear]

It's linked to the internal.

Try to link to USB 3.0 pcie card if you have one!

 

[amaze1499]

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

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?

 

[madmind]

Try to link to USB 3.0 pcie card if you have one!

Ive tried that, but still no difference. I've actually tried connecting through a USB hub as well, with the same results.

 

[PropClear]

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)

 

[Jumme_Cph]

Do you mean delete revpatch=sbvmm (NVRAM > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102)? Clever.

Would this need to be manually edited after each OCLP > "Build and Install Open Core"?

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.."..

 

[deeveedee]

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.

 

[Jumme_Cph]

You're referenced a post from Oct 2023. OCLP development has been very dynamic. Be sure that old posts are still relevant.

It's regarding avoiding Software Update to suggest Sonoma from lower versions. Should still apply.

 

[deeveedee]

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."

 

[Jumme_Cph]

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.

 

[deeveedee]

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?

 

[Jumme_Cph]

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.

 

[thegdn]

wonderfully simple process...
macbookpro6,2 14.5 beta 1, 1.5.0n
great work Devs!

 

[chevyboy60013]

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.