Jump to content

Bluetooth Firmware Uploader


EMlyDinEsH

Recommended Posts

Hello everyone, thank you EMlyDinEsh for the work here and solving our wireless problems  :-P

 

I am not sure if I am supposed to write here; as many of you mentioned, Mavericks BT accessory detection is not the same anymore and sometimes not working properly.

 

I purchased this combo card AzureWave NB290H (using BCM43225HMB chip) but never tried it on Mountain Lion... went straight to Mavericks.

 
I see inside the kext's plist that my card is not mentioned; my vendor ID is 0x13D3 (5075 decimal) and device ID is 0x3295 (12949 decimal).
 
Although the BT device seems detected OK by the vanilla system, I cannot "see" or "pair" any BT accessories at all, either mouse or keyboard (Apple/Logitech).
 
I address this to you with the hope you can guide me if you have any ideas, as to:
 
a--if it makes sense to add this device/vendor to BTFirmwareUploader kext;
b--if using your BTFirmwareUploader on vanilla installation/kexts, will produce any results.
 
It's reported that this AzureWave NB290H (BCM43225HMB chip) card works out-of-the-box but not for me, with regard to Bluetooh... I've been battling with this BT device for days now.
 
Please note that with vanilla Apple kexts, the BT device is detected but upon each reboot, it takes time to be activated, i.e. the menubar on the right shows a broken B icon and 2-3 mins later, max, it appears. Turn BT off option is disabled. Dunno if others face the same issue.
 
By adding the device/vendor ID in the Info.plist of the BroadcomBluetoothHostControllerUSBTransport plugin in IOBluetoothFamily.kext, I have active BT device upon each reboot immediately and I can now "turn off".
 
However, by no means I can link to any BT accessory, mouse or keyboard and there is nothing I can inject in my DSDT, hence my turn to EMlyDinEsh's kext for assistance.
 
Many, many thanks.
Link to comment
Share on other sites

Hi all, i own a AW-CEH123H and i just updated SO to Yosemite. Using version 2.5.2 Bluetooth works but it's not stable, after cold or warm boot it may not work, but when it works (about 80% of the time) it's flawless. With version 2.6 Bluetooth doesnt pair any mouse/keyboard, doesn't work at all.

 

 

EDIT. I checked again the firmware uploaded at System Info. With version 2.6 I have firmware v14 4096, but with version 2.5.2 I have firmware v14 5575, that's the difference I can see. With the same chipset the firmware loaded on original BT is also different, it's posted some pages before.

Link to comment
Share on other sites

hello,

I just upgrade to Yosemite.

With Mavericks BTFirmwareUploader 2.6 worked fine without any problem.


In Yosemite I can not pair with your wireless keyboard or Magic Mouse and the firmware is not updated as often correctly, but often shows v14 c4096 instead of c5546.

Link to comment
Share on other sites

 

Hello everyone, thank you EMlyDinEsh for the work here and solving our wireless problems  :-P

 

I am not sure if I am supposed to write here; as many of you mentioned, Mavericks BT accessory detection is not the same anymore and sometimes not working properly.

 

I purchased this combo card AzureWave NB290H (using BCM43225HMB chip) but never tried it on Mountain Lion... went straight to Mavericks.

 
I see inside the kext's plist that my card is not mentioned; my vendor ID is 0x13D3 (5075 decimal) and device ID is 0x3295 (12949 decimal).
 
Although the BT device seems detected OK by the vanilla system, I cannot "see" or "pair" any BT accessories at all, either mouse or keyboard (Apple/Logitech).
 
I address this to you with the hope you can guide me if you have any ideas, as to:
 
a--if it makes sense to add this device/vendor to BTFirmwareUploader kext;
b--if using your BTFirmwareUploader on vanilla installation/kexts, will produce any results.
 
It's reported that this AzureWave NB290H (BCM43225HMB chip) card works out-of-the-box but not for me, with regard to Bluetooh... I've been battling with this BT device for days now.
 
Please note that with vanilla Apple kexts, the BT device is detected but upon each reboot, it takes time to be activated, i.e. the menubar on the right shows a broken B icon and 2-3 mins later, max, it appears. Turn BT off option is disabled. Dunno if others face the same issue.
 
By adding the device/vendor ID in the Info.plist of the BroadcomBluetoothHostControllerUSBTransport plugin in IOBluetoothFamily.kext, I have active BT device upon each reboot immediately and I can now "turn off".
 
However, by no means I can link to any BT accessory, mouse or keyboard and there is nothing I can inject in my DSDT, hence my turn to EMlyDinEsh's kext for assistance.
 
Many, many thanks.

 

 

Your device does not need any patches so don't use my kext and just inject your device ids to Broadcom Bluetooth kext which should make it work. Also try to delete bluetooth plist and reboot then try to pair.

Link to comment
Share on other sites

I have your same card... I can't use BT, does someone know any solution?

 

hello everybody, 

i just order today this combo card for my dell E7440 with 10.9.5:

http://www.ebay.com/itm/111433272063?_trksid=p2059210.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

 

did somebody already use this card? 

thank

 

What is the device id for this bluetooth? 

Link to comment
Share on other sites

hello,

 

I just upgrade to Yosemite.

 

With Mavericks BTFirmwareUploader 2.6 worked fine without any problem.

 

 

In Yosemite I can not pair with your wireless keyboard or Magic Mouse and the firmware is not updated as often correctly, but often shows v14 c4096 instead of c5546.

 

Can you PM me details and System log when it shows up as 4096 instead 5546?

  • Like 2
Link to comment
Share on other sites

Hi all, i own a AW-CEH123H and i just updated SO to Yosemite. Using version 2.5.2 Bluetooth works but it's not stable, after cold or warm boot it may not work, but when it works (about 80% of the time) it's flawless. With version 2.6 Bluetooth doesnt pair any mouse/keyboard, doesn't work at all.

 

 

EDIT. I checked again the firmware uploaded at System Info. With version 2.6 I have firmware v14 4096, but with version 2.5.2 I have firmware v14 5575, that's the difference I can see. With the same chipset the firmware loaded on original BT is also different, it's posted some pages before.

 

PM me your system log and ioreg file with my kext installed. Also tell me how did you install my kext?

Link to comment
Share on other sites

 

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

 

Your device also does not need patches to firmware according to windows driver, so don't use my kext. Just inject the device ids in Broadcom kext to make it work.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...