Resolving Bluetooth Hardware Failures in OCLP
A Bluetooth address showing as NULL with a Firmware Version of v0 means the OS cannot communicate with the Bluetooth chip, often due to a driver mismatch after swapping hard drives between different MacBook Pro sub-models.
The Fix:
- Reset NVRAM: This is the most common fix for 'NULL' addresses. Hold Cmd+Opt+P+R on boot for two chimes.
- Identify the Card: Your chip is a BCM_4350C2. This is a Broadwell-era card. In OCLP settings, ensure Modern Wireless patches are selected.
- Re-apply Root Patches: Since the drive was swapped from a different machine, the current root patches might be for the old machine's hardware. Open OCLP, revert root patches, reboot, and then install them again for the current hardware.
- Check Internal Cable: Since the Mac was recently opened for a keyboard replacement, the tiny Bluetooth/Wi-Fi flex cable might be loose. If software fixes fail, have your tech guy double-check the connection.
Original Question: "MacBookPro/BlueTooth Issue"
The keyboard on my old MacBookPro was going wonky so I took it to my tech guy to get replaced. As it turned out he had another MBP, same model (different/newer/series) and suggested just swapping the hard drive.
Turns out there was enough of a difference between the 2 machines that he needed OCLP to make it work.
I had used BlueTooth after the swap but at some point since it has stopped working. I can no longer activate it.
I've done shit loads of reading and trouble shooting but I still can't solve this. It's really vexing me.
I know it's likely asking a lot but any help/advice would surely be appreciated.
MBP A1502 Mid-2014 running Monterey
Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0
Product ID: 0x0001
Supported services: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: PCIe
Vendor ID: 0x004C (Apple)
[link] [comments]
Post a Comment