<< Solved >> BCM94352Z not working with BlueToolFixup

[Bustycat]

Does it matter where we place BlueToolFixup? Comments I found seem to indicate the order should be as follow:

1. BlueToolFixup
2. BrcmFirmwareData
3. BrcmPatchRAM3

Add BlueToolFixup by dhinakg · Pull Request #12 · acidanthera/BrcmPatchRAM

BlueToolFixup forces BlueTool to skip attempting a firmware update, allowing for some Broadcom¹ chipsets² to work on Monterey. It also properly sets the transport. As Monterey is a beta, this is st...

github.com

BlueToolFixup has known issues with macOS 12+ · Issue #1821 · acidanthera/bugtracker

As detailed in #1669, Apple has been actively working on the Bluetooth stack in macOS Monterey. Recent betas have broken the approach BlueToolFixup used to enable Bluetooth for non-native Broadcom ...

github.com

Is there any official statement about the order for Monterey?

 

[jb11381]

I was having problems after installation too. No Bluetooth, most of my USB ports stopped working (mapped when I upgraded to 11.3), no WiFi, and none of my other drives were visible..... I disabled BcrmBluetoothInjector, installed BlueToolFixup (2.6.1) and put kexts in order of BcrmFirmwareData, BcrmPatchRAM3, BlueToolFixup and rebooted. Boot took a little longer than normal, but all good.

 

[ricky84]

at least I leave my old usb bt dongle and I've bought a new pci ex card that is currently working great ootb. No more stress with additional kext or similar.

 

[emarvericks]

I have a usb asus BCM20702A0, I fixed the problem with only BlueToolFixup kext 2.6.1., in OC / kexts and then with Opencore Configurator / open / confing plist, and in the kernel section you drag and mark enable BlueToolFixup from the Kexts folder. and reboot works perfectly

 

[gulios]

so, i've checked again that KP and there was a problem with "ExecutablePath".
I don't know why but when i opened config via OpenConfigurator it was empty.
I've set executablePath, disabled rest BT kexts and left just BlueToolFixup kext 2.6.1
Reboot and it works

 

[beelzebozo]

so, i've checked again that KP and there was a problem with "ExecutablePath".
I don't know why but when i opened config via OpenConfigurator it was empty.
I've set executablePath, disabled rest BT kexts and left just BlueToolFixup kext 2.6.1
Reboot and it works

Can confirm that I only needed BlueToolFixup kext 2.6.1 and it now works for me as well. I dragged in my kexts folder into Kernel section.

 

[dziny]

I'm in the same boat as the poster above - only BlueToolFixup kext 2.6.1 was needed. Previously on Big Sur the bluetooth USB dongle has worked without any kexts.

 

[beelzebozo]

Can confirm that I only needed BlueToolFixup kext 2.6.1 and it now works for me as well. I dragged in my kexts folder into Kernel section.

View attachment 532595

View attachment 532597

One issue that I found is that enable/disable Bluetooth doesn't work atm via Bluetooth preferences. I suggest to not toggle it off or you will need to restart to enable again.

 

[pastrychef]

One issue that I found is that enable/disable Bluetooth doesn't work atm via Bluetooth preferences. I suggest to not toggle it off or you will need to restart to enable again.

Are Continuity features working? Are you using a DW1560?

 

[Bustycat]

Not sure about if someone else also got the same issue, but the Bluetooth dongle is still recommended on tonymacx86 Buyer’s Guide.