MP 1,1-5,1 Bluetooth does not work after installing Ventura with OCLP.

[Komyea]

Make sure your connections to the Bluetooth Wifi Cards are Correct + make sure the antenna connectors were not damaged & insulate any wires that are open and dangling.

Then do an NVRAM clear - reboot - hold down [CMD]+[OPT] + P+R for the time of (4) chimes
Download the latest OC - Then do a OCLP rebuild & Install.
This worked for me.

I'll try swapping out the extension cables that came with the kit however I've tried NVRAM clear and no luck as well as re-running the post install patches.

 

[Komyea]

Make sure your connections to the Bluetooth Wifi Cards are Correct + make sure the antenna connectors were not damaged & insulate any wires that are open and dangling.

Then do an NVRAM clear - reboot - hold down [CMD]+[OPT] + P+R for the time of (4) chimes
Download the latest OC - Then do a OCLP rebuild & Install.
This worked for me.

yes, tried all of this before making a post. did not resolve the challenge.

 

[culser]

yes, tried all of this before making a post. did not resolve the challenge.

this post is large, i believe there was a solution to your problem w/ ventura not working after installing BT, found in the previous posts.

 

[Komyea]

this post is large, i believe there was a solution to your problem w/ ventura not working after installing BT, found in the previous posts.

if you're referring to the kext solution, it appears that it's not listed in my plist so unfortunately that won't work for me.

 

[aceaceace]

Thanks !!
Bluetooth fixed by clearing NVRAM that is all it needed.
power down reboot - while booting hold these 4 keys [CMD]+[OPT] + P+R for 3 chimes and Bluetooth works now on iMac 27" mid-2011 Mac 12,2 Sonoma 14.1 + OpenCore Legacy Patcher 1.2.0 + maxed out memory to 32GB + 2TB SSD
Able to connect to Bluetooth magic mouse and keyboard again. Awesome !! Love OCLP

 

[Outface]

I hope I’m posting this in the right place—if not, feel free to move it.

After weeks of trial and error, I finally got my BCM94360CD (upgraded Bluetooth and WiFi module) working again on my Mac Pro 5,1 under Sonoma 14.7.4 with OCLP 2.2.0—without any USB 2.0 lane.

What I did:


• I used two SSDs:
• One to install High Sierra, which I kept.
• One for the Sonoma system I’m using now.
• I completely erased both disks, including the EFI partitions.


• I installed High Sierra on one disk (set the date to 2017, unplugged the internet connection, and formatted the disk as Mac OS Extended (Journaled)).


• I installed OCLP 0.6.8 on this disk.


• Then, I installed Ventura on the second SSD (booting OCLP from the High Sierra disk).


• I installed OCLP 2.2.0 on the Ventura disk → still no Bluetooth after rebooting into Ventura with OCLP 2.2.0.


• I upgraded to Sonoma 14.7.4 → still no Bluetooth.


• I booted into Sonoma, installed OCLP 2.2.0 without rebooting and installed OCLP 1.4.3, rebooted and applied Root Patches.


• It automatically installed KDK Build 23H420 → after rebooting, Bluetooth was back!


• I then simply upgraded from OCLP 1.4.3 to 2.2.0 again, and Bluetooth still works.


It was a confusing process, but it’s finally working!
I also took a screenshot of my kexts and system info—hope it helps.

Kind regards,

Stephan Deutsch

 

[Outface]

Update to my post above: We have now identified why applying the root patches with OCLP 1.4.3 and subsequently updating to OCLP 2.2 restored Bluetooth.

OCLP 1.4.3/1.5 forced legacy UHCI/OHCI into the primary Boot/System Kernel Collections. The equivalent KDK requirement is missing from the modular OCLP 2.x USB11 patchset, which can split IOUSBHostFamily/AppleUSBHub from the restored UHCI/OHCI plugins.

A one-method source fix has now been live-tested on a MacPro5,1 with macOS 15.7.9. Full technical report and source links:

https://forums.macrumors.com/threads/oclp-2-2-0-macpro-5-1-wifi-but-no-bluetooth-on-sequoia.2448535/post-34743943

The affected code path applies to Ventura and newer; live testing has so far been performed only on macOS 15.7.9.

Outface S.D.

 

[kkinto]

Hey @Outface - I lost functional bluetooth somewhere along the way with Sequoia and OCLP. At one point there was a 'fix' which involved removing a spoof kext worked and it always worked just fine when booted in Mojave.

I had upgraded my PCI card to a BCM94360CDP (not ideal according to Tsialex). At some point it stopped working with an upgrade (either OCLP or Sequoia but I forget which) and I had to abandon the idea of bluetooth forever. All indications pointed to the fact that it plugs into the USB port of the motherboard. It also no longer worked in Mojave either! I did not have access to another card nor could I find the recommended 'dongle' alternative and so I left it. The bluetooth card is properly recognised by OCLP and my Mac (system infor) but will not otherwise work (ie its not "null") while the wifi works just fine and always did.

Every now and again I tried asking various AI's but really always got to same point - your 1.1 USB doesn't work and somehow OCLP is not patching that like it does for the factory card (so if I'd not 'upgraded' my original card it might be working under OCLP!). They basically confirmed @tsialex's diagnosis in post #8. I was not able to do the hardware work myself and I couldnt get one of the recommended dongles and my CD (noP) card bought never arrived so I gave up.

So my question is: would this apply to my situation? And if so, how do I do this? I read your post, followed the github link but there I cant go forward as I have absolutely no clue what to do next!

My problem it seems is the USB OHCI/UHCI, not the controller.

Thanks.

 

[Outface]

Hey @Outface - I lost functional bluetooth somewhere along the way with Sequoia and OCLP. At one point there was a 'fix' which involved removing a spoof kext worked and it always worked just fine when booted in Mojave.

I had upgraded my PCI card to a BCM94360CDP (not ideal according to Tsialex). At some point it stopped working with an upgrade (either OCLP or Sequoia but I forget which) and I had to abandon the idea of bluetooth forever. All indications pointed to the fact that it plugs into the USB port of the motherboard. It also no longer worked in Mojave either! I did not have access to another card nor could I find the recommended 'dongle' alternative and so I left it. The bluetooth card is properly recognised by OCLP and my Mac (system infor) but will not otherwise work (ie its not "null") while the wifi works just fine and always did.

Every now and again I tried asking various AI's but really always got to same point - your 1.1 USB doesn't work and somehow OCLP is not patching that like it does for the factory card (so if I'd not 'upgraded' my original card it might be working under OCLP!). They basically confirmed @tsialex's diagnosis in post #8. I was not able to do the hardware work myself and I couldnt get one of the recommended dongles and my CD (noP) card bought never arrived so I gave up.

So my question is: would this apply to my situation? And if so, how do I do this? I read your post, followed the github link but there I cant go forward as I have absolutely no clue what to do next!

My problem it seems is the USB OHCI/UHCI, not the controller.

Thanks.

Hi, yes, this could apply to your situation, although I cannot guarantee it because your card is not exactly the same model as mine.

My MacPro5,1 has an upgraded BCM94360CD combo card. The Wi-Fi part of this card uses PCIe, while its Bluetooth component is a BCM20702B0 connected through the Mac Pro’s internal USB path. It appears in macOS as BRCM20702. Therefore, my successful test was also performed with an upgraded Wi-Fi/Bluetooth card, not with the original factory Bluetooth card.

Your BCM943602CDP has a different Bluetooth component, but its Bluetooth connection also uses USB. If it is attached through one of the MacPro5,1’s legacy USB 1.1 controllers, the OCLP problem I identified could affect it as well.

UHCI and OHCI are the legacy USB host-controller interfaces and their associated drivers. Therefore, what you describe as an OHCI/UHCI problem is precisely the area addressed by my change. The patch is not specific to the BCM20702 Bluetooth chipset. It changes how OCLP installs the legacy USB 1.1 driver stack, keeping the downgraded IOUSBHostFamily and AppleUSBHub together with the restored UHCI/OHCI plug-ins in the primary Boot/System Kernel Collections.

There is, however, an important distinction regarding Mojave. This source change only affects OCLP root patching on Ventura and newer. It does not patch Mojave. If Bluetooth is also unavailable when Mojave is booted completely natively, without OpenCore, there may be an additional hardware problem involving the card, adapter, internal USB cable or motherboard connection. If Mojave is being booted through the OCLP/OpenCore EFI, injected Bluetooth kexts or spoofing could still affect it.

Regarding how to apply the fix: the GitHub link contains a proposed source-code change, not a downloadable installer or an official OCLP release. I built and tested OCLP from the modified source with the exact matching KDK. I am not distributing a custom binary.

For this to become straightforward and safe for regular users, the OCLP developers need to review and incorporate the change into an official OCLP build. Until that happens, using it requires building OCLP from the modified source and should be considered experimental.

So the short answer is: yes, the fix could apply to your BCM943602CDP because its Bluetooth component also depends on the legacy USB path. However, only the BCM94360CD/BCM20702B0 combination in my MacPro5,1 has been tested so far, and the fact that Bluetooth also fails in Mojave may indicate a second, separate issue.