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.