- #Usb vid_0a5c&pid_21e1&rev_0112 how to#
- #Usb vid_0a5c&pid_21e1&rev_0112 driver#
- #Usb vid_0a5c&pid_21e1&rev_0112 Bluetooth#
BCM20702A1-0a5c-21e6.hcdįinally, let's back up a directory, make sure what think is there is actually there, and copy it into cd lsīCM20702A1-0a5c-21e6.hcd BCM20702A1_001.002. app/ g4wb12ww.exe cp BCM20702A1-0a5c-21e6.hcd /lib/firmware/brcm/ Gcc -O2 -march=native hex2hcd.c -o hex2hcd
Remote: Total 8 (delta 1), reused 8 (delta 1), pack-reused 0 Remote: Compressing objects: 100% (7/7), done. Now we need to put this in a form that the linux kernel expects, so that's where hex2hcd comes git clone git:///jessesung/hex2hcd.git hex file, so this line is awesome to see:Ĭopy that file out of the directory structure into a place that's easier to work cp app/Win64/BCM20702A1_001.002. lsīCM20702A1_001.002. app/ g4wb12ww.exe
#Usb vid_0a5c&pid_21e1&rev_0112 Bluetooth#
This device is also known as: Broadcom 20702 Bluetooth 4.0 Adapter, Broadcom 20702 Bluetooth, BlueSoleil Generic Bluetooth Driver.
#Usb vid_0a5c&pid_21e1&rev_0112 driver#
I happen to know from my research that the firmware files are. Download USBVID0A5C&PID21E1 device driver for Windows 7, XP, 10, 8, and 8.1. HKR,%DeviceRemoteWakeSupported%,0x00010001,1ĪddService=bcbtums,BCBTUMS_Service_Inst, BTWSECFL_EventLog_Inst %BRCM20702Thinkpad.DeviceDesc%=RAMUSB21E6, USB\VID_0A5C&PID_21E6 20702 non-UHE Lenovo Japan I use vi, but hopefully you know your editor well enough to do the equivalent, and you'll find something like this: That "DeviceDesc" looks important, so we'll search for that in the. inf are plaintext files, so let's look in there. Well, I don't want to poke around in binary files too much, but I know that. I notice that the firmware expected to be loaded has "0a5c-21e6" in the name, and the usb ID of the bluetooth hardware is "0a5c:21e6" so let's poke around and see if we can find anything with that name:įind app/ -name "*0a5c*" -o -name "*0A5C*" Now to see if we can find the important bits in here. lots of output, all extracted to an "app/" directory. To do that, you'll first need to get innoextract (see or search for innoextract g4wb12ww.exe I went to the Lenovo support site, downloaded the bluetooth driver file (currently located at but of course, this link will not always be valid), and poked around a bit in its contents. Saturday, receiving a device on your bluetooth driver. Hp elitebook 8470p is 14 inch laptop powered by up to intel core i7-3720qm quad-core processor with integrated intel hd graphics 4000 video card or discrete amd radeon hd 7570m with 1gb dedicated. There were a few results with links to different firmware that someone had already obtained from some mysterious source, and vague references about "get it from your Windows system" and such, but well, I don't have a Windows system. Hardware ids, usbvid 0a5c&pid 21e1&rev 0112 usbvid 0a5c&pid 21e1. I notice that the firmware expected to be loaded has '0a5c-21e6' in the name, and the usb ID of the bluetooth hardware is '0a5c:21e6' so let's poke around and see if we can find anything with that name: find app/ -name '0a5c' -o -name '0A5C' Hmm, no output.
#Usb vid_0a5c&pid_21e1&rev_0112 how to#
Sure enough, /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd did not exist.Īfter a bit of research, I determined that nobody had already written clear instructions on just how to obtain the needed firmware. Nov 24 13:37:35 liberty kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2 Calibre 0.9.I recently was presented with a Thinkpad T430s containing a Broadcom BCM20702 bluetooth chip, and bluetooth wouldn't work at all on it.īus 003 Device 009: ID 0a5c:21e6 Broadcom Corp.