Toggle sidebar Toggle sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
macOS 14.3 (23D56) with KDK_14.3_23D5051b.pkg OTA update works like a charm with OCLP 1.4.0n on MP5,1 | RX580 | 990 Pro NVMe 😍 (and MacMini's, iMacs and MBP's 11,X 12,X also OTA from 14.2.1 to 14.3 all without problems)

Update: KDK_14.3_23D56.pkg is released also!
 
Last edited:
  • Like
Reactions: MacRumors3590, hvds, luckyduke23 and 2 others
Imac 11,2; OCLP 1.3.0
 

Attachments

  • bevor.png
    bevor.png
    92.3 KB · Views: 130
  • sonoma 14.3.png
    sonoma 14.3.png
    122.6 KB · Views: 125
  • Like
Reactions: K two
BuffyzDead said:
For similar bluetooth problems when I upgraded to Sonoma from Ventura on both a 2011 and 2010 iMac.
This is what I did to get bluetooth back.
Download Ben Baker's Hackintool.app. Use the app to edit NVRam directly. Look for the entries:
bluetoothExternalDongleFailed
bluetoothActiveControllerInfo
bluetoothInternalControllerinfo
Delete all the entries, and wait for the NVRam to refresh itself. At least one of the entries (bluetoothExternalDongleFailed) should come back with value of <00>. If not, repeat deleting the entries.

For me bluetooth worked again when I performed the above steps, bluetooth settings will show all previously paired devices, and auto connect to them just as before the update.
Click to expand...
Could you please clarify "...and wait for the NVRam to refresh itself". Do the named entries / values *spontaneously regenerate themselves without user input, or do I need to restart? If no restart is required, can I just wait for the relevant window in Hackintool to repopulate those entries? Thanks for guidance.
MacPro5,1 / RX580 / 14.2.1 / OCLP 1.3.0 - clean install on Samsung 970 / Highpoint 7101A (slot 1 for the 970 - other slots empty). Everything apparently working fine with the exception of BT. Yes I did the install with a USB 2 hub as suggested on github page and elsewhere to ostensibly address this BT issue. (BT works fine in Ventura and Big Sur, each installed on separate physical drives with OCLP on this machine; problem is unique to this Sonoma install.)
 
Last edited:
I will be opening up my iMac 11,3 (mid-2010). Wifi was the ancient Atheros. Should I replace that with something else and if so, what would be a good replacement? Thanks.
 
miuipower said:
Hello, good evening, I have Sonoma 14.2.1 installed with oclp and I have problems with the Bluetooth, it is activated and a few seconds later it is deactivated. Any fix for this, thank you.

Does anyone solve this problem with oclp? impossible to use magic mouse and keyboard
Click to expand...
I have had this issue (actually the only one I've had so far) installing 14.2 and 14.2.1 with oclp on my Macbook Pro 2009. I thought it would be a permanent one as the hw was old but it turned out that after a few usage/reboots it just started working. I was intrigued by what had triggered the "fix". I happened to reinstall 14.2 and then completely reinstall 14.2.1 (initially I had upgraded from Ventura to 14.2 to 14.2.1) and every time the problem would reappear. NVRAM and SMC resetting wouldn't solve the issue but *every time* after a few boots and pairing tries somehow the bluetooth icon would white out and bluetooth discovery and pairing work fine. I don't know still what may trigger this, maybe the bluetooth daemon just needs the computer on for a significant time on the first boot(s) to establish itself and was shutting down too quickly as I noticed the issue. So my advice is, well, just be patient, work on your computer, do some normal boots, try enabling bt from time to time and bluetooth will eventually work and stay on. I know this sounds like lifting and dropping a MacIIe a few inches to make it work if you know this lore, but that's it.
 
Last edited:
ethylmertz said:
Could you please clarify "...and wait for the NVRam to refresh itself". Do the named entries / values *spontaneously regenerate themselves without user input, or do I need to restart? If no restart is required, can I just wait for the relevant window in Hackintool to repopulate those entries? Thanks for guidance.
MacPro5,1 / RX580 / 14.2.1 / OCLP 1.3.0 - clean install on Samsung 970 / Highpoint 7101A (slot 1 for the 970 - other slots empty). Everything apparently working fine with the exception of BT. Yes I did the install with a USB 2 hub as suggested on github page and elsewhere to ostensibly address this BT issue. (BT works fine in Ventura and Big Sur, each installed on separate physical drives with OCLP on this machine; problem is unique to this Sonoma install.)
Click to expand...
No Restart needed. I don't have that tool in front on me anymore but I recall it was fairly intuitive to use. ...while it was about 3 months ago, when I updated from Ventura to Sonoma, I do recall that there was no restart required to use that tool.
 
I recall in the past using dosdude1 patcher updating from High Sierra to Mohave we had to disable S.I.P. to patch the system and re-enable it after upgrading an unsupported Mac. I'm wondering if that's the case here? So my 2015 17,1 iMac is currently running Sonoma v.14.2.1 (build 23C71). Jessiee's Flying tutorial and he touched on it but nothing definitive.
Does anyone have S.I.P. enabled that will allow the boot picker to load? used OCLP v.1.3.0 and KDK_14.2_23C63.

Thanks again to dortania and all the developers for putting together and testing OCLP so we can continue running current OS's on unsupported Mac.
Shout out to dosdude1 as well!

This is not my everyday driver.
 
Last edited:
Hey Everyone,

I'm new to this thread but not to macrumors or OpenCore. I currently have Monterey running on my 2011 iMac 12,1 but I keep being asked to update to Sonoma. I am running the 6750m that came in the iMac so it will have many of the issues people are discussing in this thread if I do update.

I know it is counter intuitive to the thread, but obviously related... Is there a way to prevent OpenCore from finding Ventura/ Sonoma and only finding Safari updates, or do I have to block all updates by disabling SIP? It's more of a nuisance to me, but if I were to give this iMac to a family member I would not want them to accidentally update and have issues.

Thanks!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back