16-inch MacBook Pro Bluetooth issue

Well that looked very promising and thanks for sharing. I ran these commands but it doesn't fix my internal bluetooth. I even bought the external bluetooth 2.0 "mushroom" receiver but that doesn't work for me either.

Getting fed up with this and almost ready to bring this thing back to the store, if they accept it..

If you read `nvram` manual, you'll notice that there is an option to set firmware variables from a file, namely, the -f option. Would be interesting to try to import from a known good configuration (that maybe someone else could export)

% nvram --help
nvram: (usage: no such option as --)
nvram [-x] [-p] [-f filename] [-d name] [-c] name[=value] ...
-x use XML format for printing or reading variables
(must appear before -p or -f)
-p print all firmware variables
-f set firmware variables from a text file
-d delete the named variable
-c delete all variables
name=value set named variable
name print variable
Note that arguments and options are executed in order.

Personally, it was another huge pain in the ***, but I completely cleaned the mac and went back to Mojave.

Still have the -3903 log entry on Bluetooth Explorer though, but everything thing else is as normal as it can be

Do the values for bluetoothInternalControllerInfo and bluetoothActiveControllerInfo match on your system, when you invoke 'nvram -p' command?

If they don't, try the following:

sudo nvram bluetoothActiveControllerInfo=VALUE_OF_BLUETOOTH_INTERNAL_CONTROLLER_INFO
sudo reboot

Also, you could also try deleting bluetooth.plist file again and perform factory reset of bluetooth module that was listed earlier this thread.

sudo rm /Library/Preferences/com.apple.Bluetooth.plist

On first glance they match, but bluetoothActiveControllerInfo actually has two extra pairs of zeros:

bluetoothActiveControllerInfo	%96%00%ac%05%00%00%00%00%00%00%14}%da%17%987
bluetoothInternalControllerInfo	%96%00%ac%05%00%00%00%00%14}%da%17%987

I set bluetoothActiveControllerInfo to the value of bluetoothInternalControllerInfo and rebooted but after reboot it's back to the old value, so I don't think that actually matters. Also did the reset though the debug menu and removal of the .plist file, but no functional internal bluetooth. Thanks for the help though!

Hi, glad I've found this thread here as I have the exact same issue. I'm waiting on my BT2.0 dongle (tried 2 other without success) and in the meantime, I tried the latest trend here. I have the exact same result as seen here. Is there anything else I can try to unlock the internal BT dongle and have it working again?

objc[1084]: Class PipeInfo is implemented in both /System/Library/PrivateFrameworks/WPDaemon.framework/Versions/A/WPDaemon and /usr/sbin/bluetoothd. One of the two will be used. Which one is undefined.
[bluetoothd][netPrefChanged] ###### Sharing Dictionary doesn't exist
2020-11-24 16:26:52.609 bluetoothd[1084:22841] Error: [AppleBluetoothHIDDeviceGen2][_setEventService:]Couldn't copy BD_ADDR
2020-11-24 16:26:52.610 bluetoothd[1084:22841] Error: [AppleBluetoothHIDDeviceGen2][_setEventService:]Couldn't copy BD_ADDR
2020-11-24 16:26:52.613 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:26:52.613 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:26:52.746 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:26:52.746 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:26:52.747 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:27:19.656 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:27:19.656 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:27:19.711 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:27:19.712 bluetoothd[1084:22841] [setSystemPreference] syncs returns false
2020-11-24 16:27:19.712 bluetoothd[1084:22841] [setSystemPreference] syncs returns false

Thanks for the detailed steps here. Unfortunately, I've tried for over 15 mins with the dongle that "bricked" the system without any success. Again, I'm still waiting on another dongle to test (third time's a charm I hope!) and hopefully, will be able to unbrick it. If not, I'll have to go to the Apple Store I guess...

That is a real DOS that we have here. I could see people walking in the Apple store with this dongle, bricking MBP one after the other... /sarcasm.

I have exactly the same issue. I had accidentally plugged in a USB Bluetooth dongle when I was testing a USB Hub I had for a project. Not realise it would nuke the Internal Bluetooth!

Same here. :-(

This was not my device, but I can ask if my friend who had this problem has time on next weekend to break his mac again xD I have doubts that he is willing to try this again tho..

Yeah sure, here it is.

I have just noticed it says 2018, even though this is the refresh model, I just got it a few weeks ago CTO from apple.

AntiHawk's solution worked for me as well. Looks like you need BT 2.0 Dungle for this, 4.0 didn't work.