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

[Ugurk]

That’s my problem, as you stated OCLP has root patches usb1.1 so don’t know why the wifi Bluetooth card isn’t being recognised. The wifi card is fine just the Bluetooth card isn’t showing up properly. You recommended two options one being plugging it into a usb2 hub internally and the other being running a cable out the back and plug it in. Either I don’t know how to do. If you can be kind enough to show me how each of those can be done I would extremely be indebted to you. Thanks in advance.
Ps- I’ve read the posts that were in the links however they are for versions before Ventura and are for cards before Bluetooth 4.2. My upgrade kit is both wifi and Bluetooth cards on the same card.
PPS- I’m in the emergency department atm. I cut my thumb something shocking with a circular saw like a goose so I’m texting from the emergency ward waiting to get stitched up

 

[MacNB2]

Thank you for the guidance however I’m not exactly sure how to go about doing as you recommended. Is there a guide showing step by step how to do it? It’s really strange coz before purchasing the upgrade kit I was assured that there wasn’t anything else I would need to do in order to get the card to work

Where ever you bought your "upgrade kit" from probably never mentioned unsupported Macs.

The way OCLP App is structured (i.e. a canned App), there's not a lot config changes you can do.
You basically choose the Mac for which you wish create an OpenCore config. Normally you would do that on the actual Mac where you wish to install OpenCore and the Root Patches. It will then scan your H/W and create an appropriate config.

I assume you have read their site here.
Another good source is MrMacintosh. Here's a generic Video tutorial for installing Ventura on an unsupported Mac.

 

[Ugurk]

Where ever you bought your "upgrade kit" from probably never mentioned unsupported Macs.

The way OCLP App is structured (i.e. a canned App), there's not a lot config changes you can do.
You basically choose the Mac for which you wish create an OpenCore config. Normally you would do that on the actual Mac where you wish to install OpenCore and the Root Patches. It will then scan your H/W and create an appropriate config.

I assume you have read their site here.
Another good source is MrMacintosh. Here's a generic Video tutorial for installing Ventura on an unsupported Mac.

Yes I’ve done the research regarding the upgrade of wifi and Bluetooth cards for unsupported macs. It was the recommendation of the OCLP regarding which wifi Bluetooth cards to upgrade too. However there was no mention of how complex it would be. I guess for some people it’s straight forward and for others not so straight forward. Is there a guide showing how to reroute the usb1.1 to the 2.0 internal hub or wire it from the outside to the internal board as suggested above?

 

[MacNB2]

PPS- I’m in the emergency department atm. I cut my thumb something shocking with a circular saw like a goose so I’m texting from the emergency ward waiting to get stitched up

Ouch ! Wishing you speedy recovery. May be should focus on the your injury first.

That’s my problem, as you stated OCLP has root patches usb1.1 so don’t know why the wifi Bluetooth card isn’t being recognised. The wifi card is fine just the Bluetooth card isn’t showing up properly. You recommended two options one being plugging it into a usb2 hub internally and the other being running a cable out the back and plug it in. Either I don’t know how to do. If you can be kind enough to show me how each of those can be done I would extremely be indebted to you. Thanks in advance.
Ps- I’ve read the posts that were in the links however they are for versions before Ventura and are for cards before Bluetooth 4.2. My upgrade kit is both wifi and Bluetooth cards on the same card.

There are guides on this site to show how to wire a USB Hub internally on a cMac Pro (one in my signature) specially for BT+WiFI card combo.
Not sure why your Root patches for USB1.1 are not working.

 

[Ugurk]

Ouch ! Wishing you speedy recovery. May be should focus on the your injury first.



There are guides on this site to show how to wire a USB Hub internally on a cMac Pro (one in my signature) specially for BT+WiFI card combo.
Not sure why your Root patches for USB1.1 are not working.

Do you think doing a clean install of Ventura 13.5 will fix the issue?

 

[Ugurk]

Th

Do you think doing a clean install of Ventura 13.5 will fix the issue?

anks for the best wishes too

 

[MacNB2]

Do you think doing a clean install of Ventura 13.5 will fix the issue?

Unlikely.
You can try :
- uninstall Root patches (via OCLP App)
- rebuild and install OCLP onto your EFI
- Attach external wired USB keyboard & Mouse
- Reboot and whilst holding CMD+Opt+P+R keys till your hear 2 chimes (i.e. NVRAM reset)
- Reboot to the new rebuilt OpenCore EFI
- Install Root patches and reboot

see if that helps

 

[Ugurk]

i finally resolved the issue and wrote about it here https://forums.macrumors.com/thread...oth-card-upgrade-option.2395871/post-32362544.

 

[tonton_max]

hello, I've also encountered issues with bluetooth (bcm943602cdp) on my MacPro4,1 flashed to 5,1 on Ventura, bluetooth was working on Monterrey and lower but still disabled in Ventura.

After several tries, I've been able to fix my issue by disabling Bluetooth-Spoof.kext in OCLP (initially default settings without modifications) by using OpenCore Configurator (more user friendly than editing an xml file).

It now works like a charm in Ventura.
Hoping than this trick could help some other peoples

note : ventura is installed on an nvme drive

 

[SemoTech]

hello, I've also encountered issues with bluetooth (bcm943602cdp) on my MacPro4,1 flashed to 5,1 on Ventura, bluetooth was working on Monterrey and lower but still disabled in Ventura.

After several tries, I've been able to fix my issue by disabling Bluetooth-Spoof.kext in OCLP (initially default settings without modifications) by using OpenCore Configurator (more user friendly than editing an xml file).

It now works like a charm in Ventura.
Hoping than this trick could help some other peoples

note : ventura is installed on an nvme drive

View attachment 2256373

Ventura eliminates USB 1.0 and the Bluetooth connection to the MB will force the on-board controller default to USB 1.0

The workaround without messing with drivers is to just use a USB 2.0 hub (unpowered), connect it to a rear USB port and then connect the USB data wires from the internal (upgraded) Bluetooth to a short USB cable and into the 2.0 Hub. Works a treat!

 

[tonton_max]

for me, no need for that, the USB 1.1 driver from OCLP is enough

 

[SemoTech]

for me, no need for that, the USB 1.1 driver from OCLP is enough

True, but the hardware fix is also more "future proof" and faster to keep up, as Apple removes more and more of the drivers and OCLP developers struggle to patch things...

 

[MacNB2]

for me, no need for that, the USB 1.1 driver from OCLP is enough

...until you boot into Recovery or try to do a full install. Then OCLP cannot help you as the macOS is not yet patched to enable the USB 1.0 support. You will be forced to use an external USB 2.0 hub and a wired keyboard and mouse.

 

[MacNB2]

True, but the hardware fix is also more "future proof" and faster to keep up, as Apple removes more and more of the drivers and OCLP developers struggle to patch things...

That's exactly what I did in this project.

 

[SemoTech]

That's exactly what I did in this project.

Nice! Has there been any fix / solution for the need to reboot the cMP multiple times (or not able to sleep) when using a flashed Gigabyte Titan Ridge TB3 card?

 

[MacNB2]

Nice! Has there been any fix / solution for the need to reboot the cMP multiple times (or not able to sleep) when using a flashed Gigabyte Titan Ridge TB3 card?

Sorry no idea.
Did you check the 1st post here regarding configuring OpenCore Manually and setting up Thunderbolt ?

 

[SemoTech]

Sorry no idea.
Did you check the 1st post here regarding configuring OpenCore Manually and setting up Thunderbolt ?

No worries. I was pondering buying the Gigabyte TB3 Card but am holding off until there is confirmation of the sleep fix and no need to reboot once for each TB3 device connected... May have to wait a while

 

[howardc64]

Hi there,
I've been looking for a solution for a week all over the net to have Bluetooth working on my MB Pro 8.1 ( early 2011 ) with MacOS Ventura installed thanks to OCLP with no luck.

What bothered me was that, when i first tried OCLP on a 2nd partition ( with High Sierra on the primary partition ), Bluetooth was working perfectly fine... Therefor, I couldn't understand ( or accept ) why Bluetooth could not work with a clean instal of Ventura ( even tho the issue is explained on github by the fact that the USB 1.1 support got dropped for pre 2013 MBPros ).

After a few tests, i managed to have Bluetooth functional under Ventura
Here is how to do it:
- Under your actual OS (High Sierra for me ), install OCLP
- Build a USB stick with Ventura
- Create a 2nd partition on your main HDD or SSD ( not a volume! )
- Follow all the process to install Ventura on the 2nd partition
- Boot from the Ventura partition
- Under Ventura, erase the High Sierra partition with Disk Utility
- Use the "restore" tool from Disk Utility on the freshly erased High Sierra partition
- Select the Ventura partition as source
- Reboot on the "new" Ventura partition
- Launch OCLP and run again the "Build and install OpenCore" option
- Select your main HDD / SSD to be able to boot without the USB stick

And voila...

I know it's not what we can call a "clean" install but, at least, it is a solution to have Bluetooth work with Ventura installed thanks to OCLP on an old mac book pro.

The only downside is that, if you switch Bluetooth off, you cannot switch it back on without rebooting.

I hope this post will help.

Big up to all the people behind OCLP for the amazing work done !!!!!

Apple Magic2 Kbd and Mouse was working fine after installing+setting up Ventura (started from OCLP Monterey which started DosDude Catalina) Then PRAM reset and BT is gone. I did the following path

• Booted High Sierra on a USB drive
• Ran OCLP 0.6.8 on HS and installed OCLP into USB EFI. NOTE need to download OCLP on newer than HS Safari browser.
• USB EFI boot back into Ventura on internal drive
• Ventura comes up. BT restored
• Remove HS made OCLP USB EFI and follow on boots using ventura made OCLP in internal drive EFI partition works fine (This partition now says Macintosh HD - Data and has HS icon)
• Remade OCLP on Ventura and installed into internal drive EFI. No change and BT still works. Macintosh HD - Data Partition name and HS icon remained.

System Info -> Bluetooth screen



I guess the solution is to make a OCLP EFI boot USB dongle on HS and let it boot once to reinstall something on the BT chip PRAM wiped out?

 

[Macschrauber]

You can dump the firmware (so the nvram gets saved, too) in that working state.

And if BT stops working you can flash the firmware back (so the nvram gets saved back, too).

Nvram is stored in the firmware spi chip as well.

I made a tool to read, store and analyse the Mac Pro firmware (link in my signature). If you have a dump of a working against non working nvram, we can compare it to nail it down to a specific variable setting.

 

[howardc64]

You can dump the firmware (so the nvram gets saved, too) in that working state.

And if BT stops working you can flash the firmware back (so the nvram gets saved back, too).

Nvram is stored in the firmware spi chip as well.

I made a tool to read, store and analyse the Mac Pro firmware (link in my signature). If you have a dump of a working against non working nvram, we can compare it to nail it down to a specific variable setting.

Thanks. Looks like a great tool. Unfortunately didn't work for my iMac 11,1 (approved kext, rebooted, admin passwd etc) Tool went into generic mode. Screen pic + log (added txt extension for attachment) attached.

I guess for now I'll live with a High Sierra made USB OCLP EFI BT firmware installer/initializer if/when its lost (like PRAM reset)

 

[Macschrauber]

oops, I was completely aware that this was an iMac as you posted in the MacPro forum.
IM11,1 to be precise.

I only let my tool flash Mac Pro 4,1 and 5,1 - as I can't test other machines.

Bricks with flashing could be possible and I do not want to be responsible for such.

Anyway, if we knew what SPI flash chip is exactly in the IM11,1 the Dumper could at least read the firmware of this particular machine.


edit: just got data from iMac 11,2 - possible that the iMac 11,1 is using the same SPI chip. This gets into the next update of the Dumper.

To test some stuff I will start a conversation with @howardc64 not to bloat the thread.

 

[culser]

MP 5.1 2009 OC 1.01 Monterey 12.6, Boot 144 + / Broadcom BT Wifi Card w/ Adapter - 4.2.

After installing a Broadcom wifi bluetooth card, i still cannot turn on BT, and has limited hardware specs.
The WiFi has specs but cannot connect to local wifi, it attempts but cannot connect.
I have tried clearing NVRAM ( waited 2 chimes ) , OCLP says no further Patches Required.

other issues showing up: computer won't sleep

Please advise

 

[culser]

Opps
I got it, figured it out.
Had to redo clearing NVRAM
rebuild OCLP.

all set ..

 

[Komyea]

I installed a BCM943602CDP (I no longer had the one it came with) into my 5,1 which has Ventura installed using OCLP and I can't seem to connect any devices. It "seems" to connect but then almost immediately disconnects the device. I rolled back to Monterey and had the same issue so I went back to Ventura. Is there anyone I can do to fix this?

If not, is there an iMac wifi card that will work with Ventura? I've tried resetting bluetooth in terminal along with deleting plist to no avail.



Any information is greatly appreciated.

 

[culser]

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.