Bluetooth Firmware Uploader

[EMlyDinEsH]

Hi, after few reboot it's difficult to pair again my mouse, i have also Windows 10 installed that i use often too.

 

I see, i have an update to fix this dual boot problem. I'll update those details by tomorrow with a new version, so wait for that to try.

[Falanx]

What about BCM94321? Is this card working?

[Haravikk]

Thanks a bunch for providing this, it's working beautifully for me!

 

One (possibly silly?) question though; do I need to keep this kext installed after it's succeeded, or can I discard it? i.e - if it's changing firmware, then is just a one-time deal and that's it?

[lisai9093]

Thanks a bunch for providing this, it's working beautifully for me!

 

One (possibly silly?) question though; do I need to keep this kext installed after it's succeeded, or can I discard it? i.e - if it's changing firmware, then is just a one-time deal and that's it?

Firmware is needed for every boot and wake/sleep cycle. So this kext must always be loaded.

[RichieRoo]

Hi chaps

 

I saw EMlyDinEsH's earlier post which said that the Bluetooth on his card only worked after a 'warm' reboot, but not after a cold startup. I have exactly the same issue with my BCM94352 (both WIFI and Bluetooth are working great otherwise).

 

I can't see the solution. Could you point me in the right direction.

 

Thanks. Keep up the great work.

[lisai9093]

Hi chaps

 

I saw EMlyDinEsH's earlier post which said that the Bluetooth on his card only worked after a 'warm' reboot, but not after a cold startup. I have exactly the same issue with my BCM94352 (both WIFI and Bluetooth are working great otherwise).

 

I can't see the solution. Could you point me in the right direction.

 

Thanks. Keep up the great work.

This is what this kext for. Install it and everything solved.

[tomwho]

Anyone using AzureWave AW-CEH123H/ BCM943225HMB and not able to see the hardware in the System Info; it could be the whitelist in the BIOS. I had the issue using this one with HP Pavilion N15-204TX where the Wifi worked out of the box in Windows 8.1 and OS X 10.9.5 dual boot mode but could not detect the Bluetooth device in both. The solution is to defeat the while list disabling in BIOS by

 

-  Taping Pin 51 on the AW-CEH123H if  Bluetooth is whitelisted 

-  Taping Pin 20 if Wi-Fi is whitelisted

 

then use the plain vanilla Apple BT drivers applying the BT Firmware upload kext here  and the 5Ghz unlock patch. Rebooting the machine and Wifi (2.4 Ghz/5Hhz with Airdrop and Wake-on-lan) as well as Bluetooth works fine now. Thanks to  various members contributing here.

 

Here relevant System Info from my OS X 10.9.5 . 

Bluetooth:

--------------

       Chipset: 20702A3

  Firmware Version: v14 c5270

  Bluetooth Power: On

  Discoverable: On

  Connectable: Yes

  Auto Seek Keyboard: On

  Auto Seek Pointing: On

  Remote wake: On

  Vendor ID: 0x13D3

  Product ID: 0x3404

  HCI Version: 0x6

  HCI Revision: 0x1496

  LMP Version: 0x6

  LMP Subversion: 0x220E

  Device Type (Major): Computer

  Device Type (Complete): Mac Portable

  Composite Class Of Device: 0x38010C

  Device Class (Major): 0x01

  Device Class (Minor): 0x03

  Service Class: 0x1C0

 

Bluetooth can also be enabled/disabled from the OS

       

Wi-Fi

-------

Software Versions:

  CoreWLAN: 4.3.3 (433.48)

  CoreWLANKit: 3.3.2 (332.36)

  Menu Extra: 9.3.2 (932.35)

  System Information: 9.0 (900.8)

  IO80211 Family: 6.4 (640.36)

  Diagnostics: 3.0 (300.40)

  AirPort Utility: 6.3.2 (632.3)

  Interfaces:

en1:

  Card Type: AirPort Extreme  (0x14E4, 0x2123)

  Firmware Version: Broadcom BCM43xx 1.0 (6.30.223.154.65)

    Locale: FCC

  Country Code: US

  Supported PHY Modes: 802.11 a/b/g/n/ac

  Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 144, 149, 153, 157, 161, 165

  Wake On Wireless: Supported

  AirDrop: Supported

  Status: Connected

 

 

Hope this confirmation helps here someone  like me ( who struggled with it for a month ) and tried in vain to find a ROM BIOS whitelist hack without any success.

Edited October 22, 2014 by tomwho

[MadJawa]

Anybody got Handoff to work with BCM94352? Continuity (phone calls on desktop) works for me, but I can't get Handoff to work, it says unsupported in System info

[headkaze]

I have an Azureware CE123H and I dual boot into Yosemite / Windows 8.1. I cannot get wifi to work under Windows 8.1. It can see access points but connection always fails. Is it possible this firmware update can cause a problem in Windows?

 

EDIT: Nevermind; the default driver in Windows 8.1 does not work. You need to install a newer driver such as broadcom_wireless_lan_7_10_96_0_win8_1_driver.zip

[dlhxr]

I have a realteck bluetooth but with Azurewave vendor id. Is it possilble to work?

 

Detailed information is following.

 

Realtek Bluetooth 4.0 + High Speed Chip

USB\VID_13D3&PID_3410&REV_0200

Port_#0006.Hub_#0003

 

Edit:

 

I add the VID and PID by myself. I saw the log in the verbose mode. The BTFirmwareUploader says successfully patch the firmware and the PID and VID in the log is the same as my bluetooth.

 

However, at the last period of booting, the error log keeps bumping and bumping.

10/23/14 10:54:31.000 AM kernel[0]: BTFirmwareUploader :: Broadcom Standalone Bluetooth controller found
10/23/14 10:54:31.000 AM kernel[0]: Bluetooth Firmware Uploader v2.6 Final Copyright (c) 2012-2014 EMlyDinEsH (OSXLatitude).
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: [IOBluetoothHCIController][staticBluetoothTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x4000 
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][DeviceRequestCompleteHandler] -- Received 0xE000404F (kIOUSBPipeStalled) -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][DoDeviceReset] -- thread_call_enter1 (mReEnumerateOrResetThread) -- reEnumerateOrReset (0xffffff80d6c7be10) = 2 --  returned FALSE -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrResetThreadEntry] -- entering -- param0 = 0xffffff801da74000, param1 = 0x2 -- 0x4000
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- entering -- reEnumerateOrResetIn = 2 -- this = 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- in our workloop -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- parameter is valid -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- reEnumerateOrReset = 2 -- 0x4000 ****
10/23/14 10:54:31.000 AM kernel[0]: [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- calling myHub->ReEnumerateDevice() -- gEnumerateCounter = 1 
10/23/14 10:54:31.000 AM kernel[0]: [IOBluetoothHostControllerUSBTransport][ReEnumerateOrReset] -- exit; error = 0x0000 (kIOReturnSuccess)
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][ReEnumerateOrResetThreadEntry] -- exiting -- 0x4000
10/23/14 10:54:31.000 AM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
10/23/14 10:54:31.000 AM kernel[0]: **** [IOBluetoothHCIController][ProcessBluetoothTransportShowsUpActionWL] -- Connected to the transport successfully -- 0xf680 -- 0x0000 -- 0x4000 ****
10/23/14 10:54:31.822 AM sharingd[223]: 10:54:31.822 : SDStatusMonitor::kStatusBluetoothPowerChanged
10/23/14 10:54:31.823 AM sharingd[223]: 10:54:31.822 : SDStatusMonitor::kStatusBluetoothPowerChanged