Been using Apple's BlueTooth KB and Trackpad perfectly on both Metal and non-Metal Macs since OCLP v.0.0.23. Also have two third-party BlueTooth KBs, they too function with OpenCanopy w/o fail. That "wireless" KB may be the culprit, not OpenCore. 🧐
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
Just updated my 2012 5,1 cMP to Sonoma 14.3 beta 3 using OCLP 1.4.0n. Upgrade was trouble free 
That’s good to hear!
I have the apple A1314 keyboard. IMac 11,3
Maybe my problem has to do with my Bootcamp partition.
Before I patched my computer, I was running high Sierra and Bootcamp Window without any problems with the keyboard.
Actually, I was now able with a good timing to enter the boot picker with this keyboard. and use it on Sonoma , but then not on Windows in Bootcamp. When paired to Windows , I cannot use it in Sonoma.
And when I get the wrong timing, it goes directly to oclp boot picker and then the keyboard does not work in this boot picker.
I also have a MacBook Pro 2012 with Bootcamp and Sonoma. And on that MacBook, I can even start windows in the oclp bootpicker,
On IMac I can start Windows only in classic bootpicker.
On both computers in the classic bootpicker it says Windows and boots.
And in OCLP bootpicker it’s called Windows Legacy, and there it’s only the MacBook which boots windows, the iMac returns back to the same boot picker screen
Well, it all sounds complicated, but maybe somebody is here who can help me, maybe I can just edit something in my EFI manually?
It is very hard to find something by searching Google, that’s why I try to find help here.
Thank you
I have one test volume on my MBP6,2 that has been upgraded from Monterey to Ventura and then Sonoma via OTA - no issues. Since our experiences with OCLP greatly depend on our MacModel, it's not surprising that the need to use a USB Installer vs. OTA upgrade will vary.
I solved Apple Bluetooth Keyboard not shared between MacOS and Bootcamp after patching.
I manually edited values in keychain.
Here's the link which helped:
nelsonaloysio.medium.com
I manually edited values in keychain.
Here's the link which helped:
How to share Bluetooth devices among Linux/MacOS/Windows systems
Bluetooth devices depend on a pairing key to connect to other machines. And for those who have to work on different operating systems on a…
I'm having some issues getting Sonoma to install on my Mac Mini (late 2012) with OCLP. I did a recovery boot and installed Catalina then downloaded the latest OCLP version (1.3) and made the boot key for Sonoma 14.2. Everything seemed to be going ok and it got through the initial install and then did the reboot to do the second part. However it seems to crap out during this second part and says that there was an error preparing the update. I've tried resetting the PRAM and rebooting a few times. Sometimes it seems to get a little further than others, but it always seems to fail. Any ideas? I had Sonoma 14.1 running before on this Mac so I know it can work.
Interestingly when I went to erase the hard drive to try from scratch again it was named Macintosh HD - Data - Data - Data - Data - Data. I'm assuming it just appends the word DATA each time I tried to do a reinstall.
EDIT: I just had the same thing happen trying to reinstall Catalina. I'm wondering if my hard drive isn't dying? Or maybe the ram (although the ram tester came back good).
Interestingly when I went to erase the hard drive to try from scratch again it was named Macintosh HD - Data - Data - Data - Data - Data. I'm assuming it just appends the word DATA each time I tried to do a reinstall.
EDIT: I just had the same thing happen trying to reinstall Catalina. I'm wondering if my hard drive isn't dying? Or maybe the ram (although the ram tester came back good).
Last edited:
Could I ask if Bluetooth is working on this install? I have essentially the identical cMP 12-core w/ Radeon RX580 / 8GB. Sonoma 14.2.1 / OCLP 1.3.0 clean install on PCIe Samsung 970. Bluetooth crashes within a few seconds when I try to enable it in Settings. WiFi works fine. Ventura / Monterey / Big Sur on this machine (on separate drives or volumes)— Bluetooth works fine. Any thoughts appreciated.Just updated my 2012 5,1 cMP to Sonoma 14.3 beta 3 using OCLP 1.4.0n. Upgrade was trouble free
Seen this many times and have commented on this before. What has worked here is to delete the container completely (which means all recovery and boot partitions. Then erase the disk and install again.
Have never had the need to work out why this happens, but it seems to me that sometimes there are maybe some codebits left on partitions that cause this error and confuses OCLP. Especially when there has been multiple partitions. Anyway, I have had 100% success with this procedure. Good luck.
Last edited:
I've installed Sonoma previously on my 2012 Mac Mini with no problems but I think I did see that error once when doing a Ventura install. When it rebooted for the second part, if it did not boot from the EFI partition, then Sonoma install partition then you may have received an error. You need to hold down the Option key after rebooting, select EFI, then Sonoma install. This page mentions the procedure in step 18:
How to Install macOS Sonoma (or Sequoia) on Unsupported Macs, for Security Improvements - The Mac Security Blog
Using the latest version of macOS is always best from a security standpoint. But if your Mac is several years old, there's a good chance that macOS Sonoma won't run on it. Thankfully, there's an app for that.
I think the hard drive is probably the issue. It's the only thing that makes sense since the RAM test I did seems to have passed.
It is not fun to replace if it is like mine i have two drives and the bottom drive is not easy to replace.
I have a iMac late 2015 that refuses to work correctly on anything but Monterey if i use OCLP on it to go higher it just bogs down so i am putting Monterey back on it and selling it off lol
I have a MacBook Air 2012 running Catalina and I'm about to upgrade to Sonoma. The question is, should I completely erase my flash drive before installing Sonoma or can I upgrade to Sonoma and keep all of my files and apps on the drive?
People tend to have the best luck with clean installs, but as discussed above, depending on the device and your own prowess, an upgrade over your existing Catalina install may work too. You can also create a separate volume for Sonoma and install it there, and then use the migration assistant to transfer all of your files and apps to your Sonoma install. Finally, assuming that you have a lot free space on your SSD, it will be good for you to keep a separate volume running Catalina on your machine, since that is the last, official Apple supported OS for your device.
Whichever road you opt for, I would make sure that you have a Time Machine backup and a different, separate backup for your files and data before embarking on the OCLP adventure. 😉
Last edited:
@TimmuJapan Now why didn't I think about partitioning the drive and having both Catalina and Sonoma 
Thanks for that info. You seem to know much about this topic. Do you mind answering these questions? My 2012 MBAir only has 4 GB of RAM (can't be upgraded). Is that enough to run Sonoma? Also, I see people updating their Macs using a USB stick. I'm trying to find out if I need to go that route or can I just install without the stick? Thanks!
Thanks for that info. You seem to know much about this topic. Do you mind answering these questions? My 2012 MBAir only has 4 GB of RAM (can't be upgraded). Is that enough to run Sonoma? Also, I see people updating their Macs using a USB stick. I'm trying to find out if I need to go that route or can I just install without the stick? Thanks! 
Hey all, I haven't really been able to get a solid answer from reading current posts so I wanted to find out, as of Open Core 1.3.0 (current release) which is the more stable OS to upgrade to: Ventura, or Sonoma? Since I'm asking about both it didn't seem to matter which thread I asked on. Currently still on Monterey (official supported OS) for this iMac 17,1, but considering more what to do now as almost all the Apple Apps now, no longer get updates on Monterey anymore.
Up to you, but for a iMac 17,1 my choice would be 100% Sonoma, in my opinion you'll be quite happy with Sonoma and also good to go for the next month / years... (for Recovery to work may choose OCLP 1.4.0n)
The best answer is in my opinion ., create a separate partition and test it on your hardware as you will find in this forum lots of different experiences for everyone how stable it is,
if in doubt do a test run.
Thank you for writing this, @edzuper!
For me, who has the same iMac as you (but perhaps with different components, look at my signature), yours is further confirmation to never test the Beta versions of macOS again.
Since Big Sur, OS Betas have become unpredictable. Regardless, unless you are a Developer who needs to test your own software or you are an OCLP Developer, it makes no sense to install the Beta versions of macOS.
I'll tell you more: for our iMacs it wouldn't even make sense to install Sonoma, but it would be right to stop at macOS Ventura. With Ventura, in fact, everything works and works perfectly, as if our iMac were 100% supported. With Sonoma, instead, we have problems that we don't notice and small visible problems that, even if they are small, still bother us. Furthermore, Sonoma differs very little from Ventura.
However, despite my desire to experiment, at least I am satisfied with the macOS 14.x official versions and before installing the new ones I always wait for OCLP to have solved the problems that the new versions almost always introduce.
Hoping for a little guidance.
Longtime user of OCLP. MBP Late 2013. Kepler GPU. OLCP 1.3.0.
Was on happily Monterey, but at some point upgraded to Ventura. Started to experience crashes, but it was managable.
But then there was a power cut, and for some inexplicable reason, when I started up my machine, it was upgrading itself to Sonoma.
What the hell.
From that point forward, unusable. Cascading crashes that end with even Finder crashing. Random.
Would have rolled back to Ventura if I could. Created new Ventura volumes. Migration Assistant won't work going backwards in OS's.
Carbon Copy Cloned the Sonoma drive. Tried to reinstall Sonoma. Crashes just the same.
I'm facing a manual reconstruction of all my data, apps and frameworks, etc. Unless I can get to the bottom of why Sonoma is crashing like crazy under OCLP.
Anyone have any thoughts?
Longtime user of OCLP. MBP Late 2013. Kepler GPU. OLCP 1.3.0.
Was on happily Monterey, but at some point upgraded to Ventura. Started to experience crashes, but it was managable.
But then there was a power cut, and for some inexplicable reason, when I started up my machine, it was upgrading itself to Sonoma.
What the hell.
From that point forward, unusable. Cascading crashes that end with even Finder crashing. Random.
Would have rolled back to Ventura if I could. Created new Ventura volumes. Migration Assistant won't work going backwards in OS's.
Carbon Copy Cloned the Sonoma drive. Tried to reinstall Sonoma. Crashes just the same.
I'm facing a manual reconstruction of all my data, apps and frameworks, etc. Unless I can get to the bottom of why Sonoma is crashing like crazy under OCLP.
Anyone have any thoughts?
Has anyone else been getting very frequent kernel panics? I am on a 13" 2014 MBP with Sonoma 14.2 and the latest OCLP and root patches. (I have FeatureUnlock set to Disabled.) Kernel panics are happening more often than not during the nighttime. I deleted all third party kernel extensions, zapped PRAM, and reset SMC.
13" 2015 MBP i7 16GB OEM Apple 256GB SSD OCLP 1.3.0 Sonoma 14.2.1 OCLP with all defaults (FeatureUnlock = Enabled) and root patches. Fairly heavily used daily driver. Runs perfect. No kernel panics.
Additional installs are VirtualBox, realVNC, chargeLimitor, HPSmart, Turbotax, iWorks, Brave browser.
Only problem encountered was hang on the last step on the install. Had to reboot in safemode to get past. Here are prior posts ( post link #1563 #3103 )
Since you have 1TB SSD, using an aftermarket NVMe SSD adapter? I tried a cheap one and a number of problems. Went back to Apple OEM SSD.