Sidebar 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.
Hello!

I've an iMac 12,2 (2011, 27",500 Gb SSD, Xeon processor at 3,2GHz, 32GB Ram, Nvidia GeForce GTX 770M patched with Nick[D]vB BIOS). I'm really happy with it,

I've installed Sonoma 14.2 (coming from Monterey). Both with OCLP (now with OCLP 1.3).

The main issue that I have at this moment is that the Bluetooth doesn't work. I can activate the toggle control in the Settings, but it remains activated for less than 5 seconds and then the toggle turns to off by itself.

My BT card is the original one (I'm looking for an upgrade following the guide in the iMac subforum), but I can not afford a new card at the moment.

If I take a look at the System Info, in the BT it shows this:
Captura de pantalla 2023-12-11 a las 21.37.51.png


Is there anything that I can try to make the BT work again? (I know that I will not have Apple Watch Unlock or Continuity).

In Monterey everything was fine. Any help or hint will be truly appreciated.

Greets from Barcelona
 
Last edited:
hvds said:
Though Sonoma 14.2 and OCLP 1.3.0 releases probably will become available soon, tried 14.2 RC2 on MBP5,2.
Updated OTA from an earlier 14.2 beta. Works well, thank you developers!

Using latest 1.3.0n (from 26Nov, see https://github.com/dortania/OpenCore-Legacy-Patcher where the full commit history is found, scroll down to description and read, in "build and run from source" a link to the ready-built OCLP nightly app is found).
Always amazing to see how involved the automatic KDK handling is. The OCLP team had to implement it since Apple removed some code from delivered macOS, necessary to do the root patching on many legacy machines. Ethernet cable plugged in to the MBP5,2. Also wired keyboard and mouse connected via USB2 hub. WLAN and internal keyboard/trackpad become available after root patching.

I have 14.2 RC2 also on my MBP11,1 production machine, on an external SSD. MBP11,1 needs root patches but no KDKs ("KDK-less").
Click to expand...
MBP11,1: installed from USB installer 14.2 release (which is same build as RC2) using OCLP 1.3.0 release. To external SSD first for verification.
The final boot did not proceed due to a WS crash, so booted in safe mode. Removed notorious two files from /Library/Extensions manually, then normal boot worked and I applied the root patches.
Running fine.

Next time I'll remove these files prior to installation (unless I forget...) **. OCLP can act on these files only during root patching if I understand correctly (and it does, now files are in place again). These files present, while root patches not yet applied, causes problems.
Don't know how OCLP could automate this **. I guess it is specific to "KDK-less" patching.

Edit - one more exercise. Removed the two files while running the patched system. Continues running well. Next boot works but graphics acceleration is gone. Restored the files from the trash can, boot again and graphics acceleration is back. No miracles.

Edit2 - stupid me! ** reverting the root patches does remove also those files, as coded in OCLP resources/sys_patch/sys_patch.py (see _clean_auxiliary_kc). When always executing the revert before updating the OS, all is fine. Makes sense before OTA updating anyway because of download size, but also before updating by USB installer, at least in the MBP11,1 case.

Thank you far-sighted developers!
 

Attachments

  • Bildschirmfoto 2023-12-11 um 22.40.34.png
    Bildschirmfoto 2023-12-11 um 22.40.34.png
    89.8 KB · Views: 58
  • WS crash 142 130.txt
    37.6 KB · Views: 33
Last edited:
  • Like
Reactions: olad, mikelets456, K two and 1 other person
Mac (see signature) successfully updated to MacOS 14.2 / OCLP 1.3.0...MBP will follow after a week or so....

Update:
as usual I updated the KDKs manually before updating to OCLP 1.3.0 (and deleted all old KDKs). After the update to 14.2. OCLP asked to do the post patching which worked well even if Wifi was not yet working by then.
 
Last edited:
MBP 9,1 (Mid 2012 15" non-retina) updated to 14.2.

First did the upgrade to OCLP 1.3.0 which updated the EFI and root patches. Then ran the update from system settings. Everything went smoothly for a change, no safe boot needed. :)
 
  • Like
Reactions: macinfo, mwidjaya and luckyduke23
TurboCaca said:
Is there anything that I can try to make the BT work again?
Click to expand...
I had similar issues with Bluetooth on my 2012 MacBook Pro after installing Sonoma. Bluetooth had worked for me on Monterey and Ventura before my first Sonoma install.

The method posted by kinwin in post #2024 of this thread worked for me - using the Hackintool application to delete all the existing Bluetooth entries in NVRAM.
 
  • Like
Reactions: Marfan-58
Furka said:
Currently updating a 2012 Mini to 14.2. We will see the results ...
Click to expand...
All has done correctly and Sonoma 14.2 is running now. Tomorrow I will try to import photos from iPhone in Pages, use of mic from iPhone, camera continuity etc. The system is not slow, surprisingly. I have a MBP 13 from 2012 that is sooo slower than the Mini, and I do not understand why. While the Mini has a double core i5 at 2,5Mhz and 16 Gb of Ram, the MBP 13 has an i7 at 2,9Mhz and 8Gb of Ram. Perhaps the speed of the Samsung HD is the question, vs the Kingston unit on the MBP ...
 
macOS 14.2 (23C64) with KDK_14.2_23C64.pkg works like a charm with OCLP 1.3.0 release on MP5,1 | RX580 | 990 Pro NVMe 😍 (MacMini's, iMacs and MBP's 11,X 12,X also OTA from 14.1.2 to 14.2 as expected) Great Work OCLP Dev Team love it!
 
  • Like
Reactions: K two
A few observations on the macOS 14.2 OTA update atop 14.1.2 and OCLP v.1.3.0. update. When updating from RC2, Software Update might ignore your Mac because RC2 and the release version have identical Build Numbers (23C64); also during installation the progress bar may stall at 7/8ths for over a minute or so, then give an obvious WindowServer crash, into a Charcoal screen for another minute or more, only to finish the remaning 1/8th progress into the '9 minutes remaining' screen. Upon completion the Mac boots into 14.2 and OCLP requests the root-patches be installed. This being a Haswell Mac. By NOT intervening and with PATIENCE the macOS upgrade completed and the Mini runs as intended. YMMV :cool:
be patient.jpg👏
 
Last edited:
TurboCaca said:
Hello!

I've an iMac 12,2 (2011, 27",500 Gb SSD, Xeon processor at 3,2GHz, 32GB Ram, Nvidia GeForce GTX 770M patched with Nick[D]vB BIOS). I'm really happy with it,

I've installed Sonoma 14.2 (coming from Monterey). Both with OCLP (now with OCLP 1.3).

The main issue that I have at this moment is that the Bluetooth doesn't work. I can activate the toggle control in the Settings, but it remains activated for less than 5 seconds and then the toggle turns to off by itself.

My BT card is the original one (I'm looking for an upgrade following the guide in the iMac subforum), but I can not afford a new card at the moment.

If I take a look at the System Info, in the BT it shows this:
View attachment 2323690

Is there anything that I can try to make the BT work again? (I know that I will not have Apple Watch Unlock or Continuity).

In Monterey everything was fine. Any help or hint will be truly appreciated.

Greets from Barcelona
Click to expand...

I had 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.
 
MacGeekYYC said:
I had similar issues with Bluetooth on my 2012 MacBook Pro after installing Sonoma. Bluetooth had worked for me on Monterey and Ventura before my first Sonoma install.

The method posted by kinwin in post #2024 of this thread worked for me - using the Hackintool application to delete all the existing Bluetooth entries in NVRAM.
Click to expand...

kinwin said:
I had 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...
Wow - finally unstuck Bluetooth (BCM94360CD) on my cMP 5,1 using this method. Apple Watch isn't working to unlock my screen. Hmmm... anyone got this working on their cMP 5,1 and have some hints on how you got it to work?
 
JedNZ said:
Wow - finally unstuck Bluetooth (BCM94360CD) on my cMP 5,1 using this method. Apple Watch isn't working to unlock my screen. Hmmm... anyone got this working on their cMP 5,1 and have some hints on how you got it to work?
Click to expand...
Works like a charm in my Mac Pro 5,1. Have you tried to deactivate it and activate again?
 

Attachments

  • incoming-934F828F-FF4D-4B9F-807E-11D33A2AF9CB.PNG
    incoming-934F828F-FF4D-4B9F-807E-11D33A2AF9CB.PNG
    30.2 KB · Views: 43
My Mac Pro 5.1 had the same bluetooth issue, I tried all mentioned above and did not solve.

Since I have a Majave macOS on another drive, I booted it instead and after detected the bluetooth, then restarted and choose Sonoma .... (Dual boots ?) , and now managed to get the bluetooth working ..
 
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