macOS 14 Sonoma on Unsupported Macs Thread

[Riot Nrrrd]

I've never ever used Bluetooth mice and/or keyboards since 2008 starting using the Mac Pro 3.1. I'm really attached to any of my hardwired connections, even for my home network (UniFi) my Call of Duty is: can it be wired, just do it.

Just to be clear, my keyboard & mouse are wired.

Last night as a test, on another machine (Late 2012 Mac mini running Sonoma 14.7 via OCLP) I tried to “discover” a Bluetooth Magic Keyboard with fresh batteries installed.

Despite being right next to the computer the Bluetooth discovery in System Settings just sat there spinning and spinning … and eventually the system froze! I power-cycled it and it came back up saying it had panicked … guess it’s a good thing I got my wired keyboard working, it looks like Bluetooth is broken with this combo of system, Sonoma and OCLP. 🤷‍♂️

 

[m4v3r1ck]

Just to be clear, my keyboard & mouse are wired.

Apologies, misread / -interpreted your posts.

guess it’s a good thing I got my wired keyboard working, it looks like Bluetooth is broken with this combo of system, Sonoma and OCLP. 🤷‍♂️

+1 for the wired (FTW) combo!

On my Mac Pro 5.1, Sonoma 14.7.3 updated to the Final Release 14.7.3 (Build 23H417) at last, patched with OCLP 1.5.0. For me, macOS Sonoma and OCLP 2.2.0 hasn't been a pleasant ride either.

Seems there is no KDK for this latest build, at least it did not download it. Perhaps an OCLP 1.5.0 / 2.2.0 issue as mentioned above in this thread?

See all the crashes of Bluetooth / WindowServer in my Console after final reboot into PRE-patched macOS Sonoma 14.7.3 Build 23H417 at 18H04:

This resulted in a constant re-login screen after each WindowServer crash and stalled mouse/keyboard, even hard wired:

After a 'few' re-login windows and crashes of WindowsServer (13) I was able to patch the new update with OCLP 1.5.0. Final result after patching macOS Sonoma 14.7.3 (Build 23H417)

Now I need to iron out the mismatch of the OCLP build:

Thanks for your input/remarks, and good luck mastering your macOS Sonoma 14.7.3!

Cheers

 

[Riot Nrrrd]

Now I need to iron out the mismatch of the OCLP build:

m4v3r1ck Yikes!!! That's a lot of crashes ...

I'm typing this on my 2012 Mac mini still running Sonoma 14.7 atm, I don't see any bluetoothd crashes even though the system panicked last night after trying to search for Bluetooth devices for awhile.

What do you mean by "mismatch of the OCLP build"? Do you mean the commit info being for 1.5.0 but your Booted Patcher Version is 2.2.0? Yeah, all of mine in the App -> Statistics window say 2.2.0.

Needless to say, I am nervous about touching this 2012 Mac mini after my experience with the Sonoma 14.7.3 update on the 2013 Mac Pro. I don't want to upgrade and have my keyboard & mouse stop working, and need to go buy another USB hub ...

 

[loby]

Does anyone know when the next 2.30 build is going to be released?

I have a MacBook 2015 and the 2.30 night beta’s graphic performance is the best I have seen so far on Sonoma, but on occasion, power management still needs a little work (see spikes on CPU temps. on occasion (a second spike high every once in a while). Other than that, running well on the beta. Tempted to try Sequoia again as 2.2.0 and older versions did not do well.

Thanks Team for your hard work!!!

 

[m4v3r1ck]

@m4v3r1ck Yikes!!! That's a lot of crashes ...

Absolute, the worst anomaly I encountered using OCLP since macOS Monterey.

What do you mean by "mismatch of the OCLP build"? Do you mean the commit info being for 1.5.0 but your Booted Patcher Version is 2.2.0? Yeah, all of mine in the App -> Statistics window say 2.2.0.

Yes, exactly. I first noticed the difference after checking the tab App, after watching Mr. Macintosh latest OCLP video.

Needless to say, I am nervous about touching this 2012 Mac mini after my experience with the Sonoma 14.7.3 update on the 2013 Mac Pro. I don't want to upgrade and have my keyboard & mouse stop working, and need to go by another USB hub ...

I feel for you. Being nervous about any update is a no-go mood. I have had the same after my endeavor updating OCLP to 2.2.0 before updating macOS Sonoma 14.7.1 to 14.7.2. Specially now with the WindowsServer / Bluetooth crashes PRE-patching, this will be my last update for a while for now.

Again, thanks for your replies and enjoy your weekend.

 

[xboxbml]

I tried to update my 2012MBP from 15.2 to 15.3 inside Settings/standard "OTA" method, but that would just NOT work. I'd click on the Update Now button and it would just sit there. Went to work and came home and tried to click in more info and it would proceed to next screen I think then would start to download but just sit there all day. Really bad. I finally got tired of messing with it and just built a 15.3 stick and did it that way. Not sure what the issue is. Oh well. I might actually load Sonoma back on this thing. That seemed to be more responsive system wise. I repasted my 2015 MBP yesterday. Gonna do the 2012 now..

 

[xboxbml]

Well, after the 2012 15.3 update I noticed the BT had disabled itself. I enabled it on the menu bar and eventually it came back on and I connected my AirPods Pro 2 and used them fine. It kinda scared me cuz the first time I updated this thing OCLP1.5/Sequoia 15.0 I think, the BT disabled and would never come back, even after a Catalina reload. I ended up replacing the Airport card back then. Anyway this morning I then turned if off and re-pasted the CPU/GPU and fired it back up. BT disabled again in menu bar. Turned back on and the switch went blue but the symbol never did. I shut down. I'm gonna load Catalina back on it to see if that works. If it does, I might put Sonoma back on it and NOT Sequoia. If it still doesn't work, I'm not replacing the Airport card again.Wifi works so who cares I guess. This is just basically a desktop at this point anyway that only I play with.

 

[xboxbml]

Yeah, OCLP/Sequoia did it again. My Bluetooth is fried again. Catalina didn't bring it back. SMC/PRAM reset no change. I guess I live without BT on this thing. I'm not putting another BT module in this.. Already did it once for this issue. At least the wifi still works..

 

[internetzel]

Anyway this morning I then turned if off and re-pasted the CPU/GPU and fired it back up.

I'd suspect this to be the cause for Bluetooth failing; for example some solder points and/or connectors might not make good contact any more, so any movement/bending in that area might cause the problem.

 

[xboxbml]

I'd suspect this to be the cause for Bluetooth failing; for example some solder points and/or connectors might not make good contact any more, so any movement/bending in that area might cause the problem.

No it wasn't.. it started failing right after the 15.3 update...was fine before that. Did the same thing before several weeks ago..

 

[Kevo]

No it wasn't.. it started failing right after the 15.3 update...was fine before that. Did the same thing before several weeks ago..

Have you tried the nvram fixes that have been posted previously in this thread IIRC. I don't recall which update I had a problem with, but at some point with late Sonoma or early Sequoia I needed to delete some NVRAM settings with hackintool to fix my bluetooth on my mid 2012 MBP.

 

[xboxbml]

Have you tried the nvram fixes that have been posted previously in this thread IIRC. I don't recall which update I had a problem with, but at some point with late Sonoma or early Sequoia I needed to delete some NVRAM settings with hackintool to fix my bluetooth on my mid 2012 MBP.

I reloaded Catalina from scratch...no OCLP

 

[m4v3r1ck]

macOS 14.7.4 Build 23H420 is available in OCLP 2.2.0. / macOS update

 

[coasterOneEightThree]

The update to 14.7.4 took a very long time here on the MacPro3,1. This time I first downloaded the update file (over 13 GB) and then installed it. At first, the progress in the installation app was fast, with an indicated time of 59 minutes. However, it very quickly went down to 28 minutes and then remained at this level for a very long time. Suddenly there was a restart and the actual installation procedure began. This also took some time. I can only advise everyone to be patient and not to cancel too early ...

 

[deeveedee]

Smooth OTA upgrade of my HackBookPro6,2 from Sonoma 14.7.3 -> 14.7.4. Applying root patches with OCLP 2.2.0. Safari 18.3 working well in Sonoma.

 

[m4v3r1ck]

Yes, exactly. I first noticed the difference after checking the tab App, after watching Mr. Macintosh latest OCLP video.

Got the Commit/Booted versioning sorted out by - thanks to OCLP Discord server - installing the OpenCore-Patcher.pkg.

All my macOS instances (12/13/14/) are running fine now.

 

[kuoshen]

Hello everyone.
I would like to report a successful install of 14.2.1 on my iMac 12,2 (27-inch, mid-2011) using OCLP 1.3.0.
Almost everything works fine for me except some minor issues as follows.

1. Missing icons in menu bar which is fixed by changing wallpaper.
2. Green tint on camera when using photo boot app which is fixed by running FaceTime app at the same time as photo boot app.
3. Bluetooth not turning on which is fixed by PRAM reset.
4. Photos app crash when editing portrait pics, no fix.
5. "There don't appear to be any additional photos" message when opening photos>people>review more photos, no fix.
6. Graphics glitching when opening notes app, no fix. Some artifacts left even after closing notes app which can be fixed by running another app on top of glitched part of screen.

Above are very minors issues which I can totally ignore because they don't affect the work I do with my machine. With what I need, this is somewhat stable for me. Thanks again to the amazing devs and testers of OCLP and Sonoma on Unsupported Macs.

Note: In my SSD, I have 3 MacOS volumes.
1. Sonoma - Somewhat stable and I am currently using as my daily driver.
2. Ventura - Very stable, used to be my daily driver.
3. Big Sur - Most stable so I use this as my fallback just in case things get messed up in Ventura or Sonoma.

Hi, A big thank you to the Opencore Legacy Patcher folks!

After 4 years, I finally migrated my iMac 2011 27" mid-2011 with Quadro KM2100M GPU from Big Sur 11.4 to Sonoma 14.7.4 using Opencore Legacy Patcher 2.2.0 with Opencore 1.0.1.

Some brief points:
1. I installed Sonoma over Big Sur and it rebooted 6 times before I got the Sonoma GUI screen. At 18 mins after the first reboot, there was an on screen error - issue with the Startup disk selection by the Migration Assistant. I closed the window and selected restart from the top menu bar. The rest of the install was uneventful.

2. Notes displayed graphical glitches and artifacts on screeen - outside the Notes window. I searched this thread and found 2 posting of this glitch. Above it the last posting. Notes was working fine with Big Sur and the only thing I had done before migrating the iMac 2011 to Sonoma was to draw a few sketches on my iPad Pro Notes, which synched to the Notes on the iMac in Sonoma. Deleting the notes with the sketches fixed the issue completely. I used the Notes on iCloud running on Safari to delete the sketches on the Notes as the graphical glitches made working with the native Notes app impossible.

3. I also injected NightShiftEnabler.kext back into my Opencore boot EFI to get Night Shift menu back for my display. Reading Dortania's OCLP guide, I understand it could have been done with FeatureUnlock but I couldn't figure out if it should be set to Enable or Partial, so I just reused the old kext.

4. Every thing else is working fine! Great job guys!

Hope someone finds this useful.

 

[Giovamille959]

macOS 14.7.4 Build 23H420 is available in OCLP 2.2.0. / macOS update

Very smooth OTA upgrade for my MBP8,1 13” late2011 from Sonoma 14.7.2 to 14.7.4 with OCLP 2.2.0. Safari 18.3 is running OK too. Thank you developers!

 

[makra]

MBP 10,2 and 14,3 upgraded flawlessly to 14.7.4

 

[ivansebastiant]

Hi, A big thank you to the Opencore Legacy Patcher folks!

After 4 years, I finally migrated my iMac 2011 27" mid-2011 with Quadro KM2100M GPU from Big Sur 11.4 to Sonoma 14.7.4 using Opencore Legacy Patcher 2.2.0 with Opencore 1.0.1.

Some brief points:
1. I installed Sonoma over Big Sur and it rebooted 6 times before I got the Sonoma GUI screen. At 18 mins after the first reboot, there was an on screen error - issue with the Startup disk selection by the Migration Assistant. I closed the window and selected restart from the top menu bar. The rest of the install was uneventful.

2. Notes displayed graphical glitches and artifacts on screeen - outside the Notes window. I searched this thread and found 2 posting of this glitch. Above it the last posting. Notes was working fine with Big Sur and the only thing I had done before migrating the iMac 2011 to Sonoma was to draw a few sketches on my iPad Pro Notes, which synched to the Notes on the iMac in Sonoma. Deleting the notes with the sketches fixed the issue completely. I used the Notes on iCloud running on Safari to delete the sketches on the Notes as the graphical glitches made working with the native Notes app impossible.

3. I also injected NightShiftEnabler.kext back into my Opencore boot EFI to get Night Shift menu back for my display. Reading Dortania's OCLP guide, I understand it could have been done with FeatureUnlock but I couldn't figure out if it should be set to Enable or Partial, so I just reused the old kext.

4. Every thing else is working fine! Great job guys!

Hope someone finds this useful.

hi,

thankyou for notes your shared.

do i have to make usb installer macos or i can use OCLP directly from imac 12,2 ? now im monterey. thankyu

 

[rehkram]

hi,

thankyou for notes your shared.

do i have to make usb installer macos or i can use OCLP directly from imac 12,2 ? now im monterey. thankyu

The OCLP documentation recommends making a USB installer, particularly when going from a major version (Monterey) to a higher major version (Sonoma). So that is what I would do in your case.

Having said that, for minor version updates I usually download the installer using OCLP to ~/Applications and run it from there.

 

[kuoshen]

Hi,

This is about fixing Bluetooth on a Mac Mini 5,1 running Sonoma 14.7.3.

Background: I picked up a Mac Mini 5,1 mid-2011 with 2.3GHz with dual-core i5 with the intention to run it headlessly as a media server, photo archive, file server, torrent client, etc to replace an aging 14-year old WD MyBook Live NAS. The Mac Mini cost me $30 but came without any HDD or SSD but the seller assured me everything was working.

1. Fitted the MacMini5,1 with an SSD. With OCLP 2.2.0, I installed MacOS Sonoma 14.7.2 using an external HDD running on Thunderbolt 1 (and wired keyboard and mouse), and later upgraded it to 14.7.3 using OTA. Installed OpenCore to disk on the EFI partition. Installed Plex Media Server (runs fine) and attempted to configure it to run headlessly.

2. This is where I tried to use SleepAid to see if it was going to Sleep and Waking up fine. But the app kept crashing so I went into console and discovered bluetoothd process kept crashing and restarting and crashing again - over the few days it has accumulated almost 50 entries in Console's Crash Report. Having only had it running with screen sharing, I never tried the Bluetooth. When I tried to get Bluetooth working, it just wouldn't turn on. On System Information, Bluetooth would show up blank and the status bar at the bottom had the little spining wheel on the right. Often, it would crash System Information.

3. To debug further, I disabled the loading of the BlueToolFixUp.kext by setting the Enable to false in the config.plist in the EFI partition. This is where it got interesting. This time the Bluetooth still didn't work but System Information would now show Bluetooth with chipset BCM_4350C2 and under the USB section, it would read "Broadcom Bluetooth Download Device" with Vendor ID 0x05ac and Product ID 0xf007.

4. I looked into Acidanthera's repo (https://github.com/acidanthera/BrcmPatchRAM) but did not find any matching Bluetooth firmware with that Vendor ID and Product ID.

5. Googling. I found this;

GUIDE - How to Flash Broadcom Bluetooth Firmware

How to Flash Broadcom Bluetooth Firmware An EliteMacx86 Exclusive Guide - This guide describes how to flash Broadcom Bluetooth Firmware on macOS and is applicable to both, built-in and external USB Adapter. By following this guide, you'll be able to flash the firmware for your Broadcom...

elitemacx86.com

<< Solved >> - Bluetooth stopped working after updating to 10.15.1 (BCM943602CS)

The only positive I see is that the Apple Broadcom Built-in Bluetooth, is at least recognised as such. You never know, maybe it isn't totally bricked. It wasn't recognised as such until i chose the drivers (i mentioned before). Without drivers it's listed as Broadcom Bluetooth Download Device...

www.tonymacx86.com

So it turns out the Product ID 0xF007 means that the Broadcom Bluetooth device is in Device Firmware Upgrade (DFU) mode. Not sure how it got into that mode. Since I only installed Sonoma and nothing else.

6. Followed the instructions in the postings above, I install dfu-util with Homebrew. Googled for the actual Vendor and Product ID for my Bluetooth controller on Macmini5,1. Found it here https://linux-hardware.ru/?probe=0156afc704 as Vendor ID: Product ID as 05ac:8281.

7. Extracted the 20702_8281.dfu file inside my Big Sur install on an old MBP from IOBluetoothFamily.kext in folder /System/Library/Extensions.

8. Using the 8281 Product ID from step 6. and it also helped that 20702_8281.dfu was also listed as removed on the Monterrey section of the Dortania's OpenCore Legacy Guide.

9. Using dfu-util, I flashed the firmware onto the Bluetooth card: dfu-util -R -D 20702_8281.dfu. Firware download was successful.

10. I re-enable BlueToolFixUp.kext on the EFI partition. And rebooted with my fingers crossed.

11. It worked. On System Information ... USB section, it now shows: Bluetooth USB Host Controller. Product ID 0x8281, Vendor ID 0x05ac, version 1.56. In the Bluetooth section of System Information, it shows Chipset BCM_20702A3, Firmware version v156 c5916 but oddly, Address is NULL.

12. Bluetooth is working. Connected to Logitech K380 keyboard, a set of earpods too. More importantly, AirDrop works!!! And so does WiFi. No more bluetoothd crash reports in Console. Still testing the Sleep and Wake functions - seem to work or now. Also, the Bluetooth firmware survived a few reboots.

Hope someone finds this helpful.