Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

marioliv66@

macrumors member
Original poster
Oct 2, 2017
66
7
France
Sometimes I lose Bluetooth on my MacPro.

Hello everyone, I was looking at the different solutions to put BigSur on my Mac Pro 2009 4.1> 5.1. I was going to apply the "Easy to install package" from h9826790 ...
Only, I just came across this subject of @tsialex and @TECK evoking his bluetooth problem.

Currently on my Mac Pro, I am running Mojave 10.14.6 with the Bootrom 144.0.0.0.0. and it sometimes happens to me (let's say, two or three times a year) that my Mac, when starting up, no longer recognizes my Bluetooth Magic Mouse (with batteries).
I have generally worked around the problem by restarting the Mac several times (and restarting the mouse) and zapping the NVRAM.
Last week, I did it when I woke up from the Mac, the mouse was no longer responding. After restarting and restoring NVRAM, everything is back to normal.

So far I always thought of a fleeting problem between the mouse and the Mac, maybe even due to the age of the mouse (over 10 years old) and as I don't use other devices. Bluetooth, not sure if it does with other gear.

But there, or I had a doubt, it was while reading the messages in the links above, I thought to myself that this could perhaps come from a Bootrom which was starting to be corrupted.

In the idea of installing BigSur, I wanted to make a backup of my current Bootrom. I downloaded ROMTool, I thought this utility could do backups, but before doing anything stupid someone could tell me what step to take to make a backup? I only read two options "Dump system ROM" and "Flash system ROM".

Do you think my bluetooth problem is the Iceberg submerged part of a probable corrupted ROM? What would be the other signs?

Thanks for your help.
 
This is tricky, could be/could not. Can even be more than one problem simultaneously, like NVRAM fragmentation/corruption and BT hardware problems.

I'll send you a PM later today with instruction on how to get everything needed for a diagnose (plus how to correctly dump a BootROM, it's not just open ROMTool and do it). Please wait for my PM before doing anything.
 
Hello @tsialex , thanks for your help. I just read this link where you broach the subject of Mac Pro 2009 (firmware Netkas forum / MacEFIROM tools which is my case) with OpenCore.

I come up against the language barrier (everything goes through google translation lol) and with the technical terms, I'm afraid of misunderstanding :).

First, I will wait for your PM and leave BigSur aside (with Opencore and Clover) to be sure that my BootROM and my Mac are safe.
 
At the moment I have exactly the same problem with my Mac Pro. Lately it has started "losing" Bluetooth after every 2-3 boots. The fix for me is simple — delete /Library/Preferences/com.apple.Bluetooth.plist file and reboot.

I've asked @tsialex for the help with my BootROM, so will flash the reconstructed version soon and report here if it helped the problem or not.

By the way, test installed Big Sur, and upon the very first boot — no Bluetooth. Deleted preferences plist, rebooted, Bluetooth was working again. So it's not OS version dependant in my case.
 
  • Like
Reactions: 0488568 and TECK
At the moment I have exactly the same problem with my Mac Pro. Lately it has started "losing" Bluetooth after every 2-3 boots. The fix for me is simple — delete /Library/Preferences/com.apple.Bluetooth.plist file and reboot.

I've asked @tsialex for the help with my BootROM, so will flash the reconstructed version soon and report here if it helped the problem or not.

By the way, test installed Big Sur, and upon the very first boot — no Bluetooth. Deleted preferences plist, rebooted, Bluetooth was working again. So it's not OS version dependant in my case.
Added a scan for the bluetoothActiveControllerInfo into my diagnostic signatures since I noticed that it's one of the NVRAM variables that are not being erased for some people.

Your Mac Pro has it duplicated four times plus the absolutely scary 29 MemoryConfig settings instead of one for each DIMM.

I'm genuinely surprised that your Mac Pro still boots.

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
243907        0x3B8C3         BIOS version: MP51.88Z.F000.B00.1904121248
524288        0x80000         UEFI PI Firmware Volume, volume size: 524288, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
768195        0xBB8C3         BIOS version: MP51.88Z.F000.B00.1904121248
1048576       0x100000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1064960       0x104000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1065216       0x104100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1077504       0x107100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1085696       0x109100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1114112       0x110000        UEFI PI Firmware Volume, volume size: 16384, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1130496       0x114000        UEFI PI Firmware Volume, volume size: 49152, header size: 1, revision: 0, GUID: 153D2197-29BD-44DC-59AC-887F70E41A6B
1130752       0x114100        Intel x86 or x64 microcode, sig 0x000106a5, pf_mask 0x03, 2018-05-11, rev 0x001d, size 12288
1143040       0x117100        Intel x86 or x64 microcode, sig 0x000206c0, pf_mask 0x13, 2009-08-20, rev 0x-ffea, size 8192
1151232       0x119100        Intel x86 or x64 microcode, sig 0x000206c2, pf_mask 0x03, 2018-05-08, rev 0x001f, size 11264
1179648       0x120000        UEFI PI Firmware Volume, volume size: 196608, header size: 1, revision: 0, Variable Storage, GUID: FFF12B8D-7696-4C8B-85A9-2747075B4F50
1179688       0x120028        NVRAM start of the 1st VSS stream
1179766       0x120076        NVRAM MemoryConfig type: (j)
1188490       0x12228A        NVRAM bluetoothActiveControllerInfo
1189438       0x12263E        NVRAM MemoryConfig type: (g)
1191486       0x122E3E        NVRAM MemoryConfig type: (h)
1193534       0x12363E        NVRAM MemoryConfig type: (i)
1196117       0x124055        NVRAM MemoryConfig type: (g)
1198165       0x124855        NVRAM MemoryConfig type: (h)
1200213       0x125055        NVRAM MemoryConfig type: (i)
1202366       0x1258BE        NVRAM MemoryConfig type: (g)
1204414       0x1260BE        NVRAM MemoryConfig type: (h)
1206462       0x1268BE        NVRAM MemoryConfig type: (i)
1208615       0x127127        NVRAM MemoryConfig type: (g)
1210663       0x127927        NVRAM MemoryConfig type: (h)
1212711       0x128127        NVRAM MemoryConfig type: (i)
1214864       0x128990        NVRAM MemoryConfig type: (g)
1216912       0x129190        NVRAM MemoryConfig type: (h)
1218960       0x129990        NVRAM MemoryConfig type: (i)
1221207       0x12A257        NVRAM MemoryConfig type: (g)
1223255       0x12AA57        NVRAM MemoryConfig type: (h)
1225303       0x12B257        NVRAM MemoryConfig type: (i)
1227532       0x12BB0C        NVRAM MemoryConfig type: (g)
1229580       0x12C30C        NVRAM MemoryConfig type: (h)
1231628       0x12CB0C        NVRAM MemoryConfig type: (i)
1233722       0x12D33A        NVRAM bluetoothActiveControllerInfo
1233847       0x12D3B7        NVRAM SIP state, type: (w)
1234332       0x12D59C        NVRAM bluetoothActiveControllerInfo
1234499       0x12D643        NVRAM MemoryConfig type: (g)
1236547       0x12DE43        NVRAM MemoryConfig type: (h)
1238595       0x12E643        NVRAM MemoryConfig type: (i)
1245255       0x130047        NVRAM start of the 2nd VSS stream
1245302       0x130076        NVRAM MemoryConfig type: (j)
1254026       0x13228A        NVRAM bluetoothActiveControllerInfo
1254974       0x13263E        NVRAM MemoryConfig type: (g)
1257022       0x132E3E        NVRAM MemoryConfig type: (h)
1259070       0x13363E        NVRAM MemoryConfig type: (i)
1343518       0x14801E        HardwareID Base_xx: 19
1343538       0x148032        bzip2 compressed data, block size = 100k
1345188       0x1486A4        HardwareID 11-digits SSN: xxxxxxxx20G
1345205       0x1486B5        HardwareID 3-digit HWC model: 20G
1376256       0x150000        UEFI PI Firmware Volume, volume size: 2686976, header size: 1, revision: 0, EFI Firmware File System, GUID: 7A9354D9-0468-444A-CE81-0BF617D890DF
1416827       0x159E7B        BIOS version: MP51.88Z.F000.B00.1904121248
1614976       0x18A480        Apple NVMe EFI Module
4063232       0x3E0000        UEFI PI Firmware Volume, volume size: 65536, header size: 1, revision: 0, GUID: E3B980A9-5FE3-48E5-929B-2798385A9027
4128768       0x3F0000        UEFI PI Firmware Volume, volume size: 65536, header size: 0, revision: 0, Apple Boot Volume, GUID: 04ADEEAD-61FF-4D31-BAB6-64F8BF901F5A
4128867       0x3F0063        BootBlock version: AAPLEFI1.88Z.0005.I00.1010071430
4194000       0x3FFED0        HardwareID MLB/LBSN: J5xxxxxxx1LTC, BuildDate: 09xxxx09xxxx
 
I updated my initial thread.

I wrote back the reconstructed ROM, I had to reboot Big Sur twice and Bluetooth was visible. I will wait few days and report back to see if the issue makes surface again. Thank you @tsialex for your help!

@cdf @h9826790 I think we should keep a close eye on this. I will report back if I lose again Bluetooth, if this happens, this is clearly an issue with OC and/or Big Sur, we cannot blame it on ROM fragmentation.
 
Last edited:
Hello @tsialex, I haven't had a bluetooth problem yet, but it only happened to me two to three times in the year before, it was not regular (I specify that I am with 10.14.6, I have not installed BigSur).
 
  • Like
Reactions: tsialex
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.