Step by step instruction to install adb usb driver on Windows


#1

Start from opening Device Manager on Windows

Refer the link and open the Device Manager.

Connect Dragonboard 410C to Windows PC

There are two USB Type A connectors (the two big regular USB connectors) and one micro USB connector.
To use adb from your Windows PC, you need to connect the Host PC with micro USB connector.

You need to unplug anything it is connected on the the USB Type A connector, such as, mouse or keyboard and etc, to use micro USB connector for adb.
Download adb usb driver for Windows

We have uploaded revised adb usb driver which will recognize DragonBoard 410C.

Installing adb usb driver on Windows

After confirming the DragonBoard 410C is connected with Windows PC with microUSB cable, turn on the DragonBoard by connecting AC adaptoer to it.

The Device Manager on Windows should show this screen.


USB drivers
Dragonboard410c not getting recognized o windows10 machine
#2

If you see any place to improve the procedure then feel free to post below (or send me a PM).
:slight_smile:


#3

sir, i know this is not the correct thread for my problem but i really need help. Earlier when i bought, this board’s led were working i.e. lighting up and the there was no display on the monitor. now the leds also don’t light up and there is no display and response from the dragon board 410c. Please help me to get started and getting this board to work.

Abhishek Anand
10abhishekanand@gmail.com


#4

Hi,
@Akira Tsukamoto, i have click the “adb usb driver windows DB410C”,but the link is not available,can you help me ?


#5

Right now I am a Windows 8.1 user and have this issue too, I solved in that way.

1 - After installing the Google USB Drivers…

2 - Navigate to the <Path_To_Android>\Sdk\extras\google\usb_driver

3 - Open the file “android_winusb.inf”

4 - Search on Google.NTx86 and paste the text below

[Google.NTx86]

;Qualcomm SURF/FFA
%SingleAdbInterface% = USB_Install, USB\VID_05C6&PID_9025
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D

;Qualcomm Devices
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9024&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9015&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9018&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9029&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9031&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9037&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9035&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9053&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9039&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_904E&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903A&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903F&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9022&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_902D&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_901D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903B&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9042&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9044&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9046&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9059&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9060&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9064&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9065&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9082&MI_05
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9084&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9098&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_909A&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9020&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B4&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B6&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B8&MI_04

5 - Repeat the above step to Google.NTamd64 as show in the text below

[Google.NTamd64]

;Qualcomm SURF/FFA
%SingleAdbInterface% = USB_Install, USB\VID_05C6&PID_9025
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D

;Qualcomm Devices
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9092&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9025&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9024&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9015&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9018&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9029&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9031&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9037&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9035&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9053&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9039&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_904E&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903A&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903F&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9022&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_902D&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_901D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_903B&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9042&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9044&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9046&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9059&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9060&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9064&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9065&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9082&MI_05
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9084&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9098&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_909A&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9091&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_9020&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B4&MI_03
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B6&MI_04
%CompositeAdbInterface% = USB_Install, USB\VID_05C6&PID_90B8&MI_04

6 - Follow the Akira steps to update the driver (this guide, top of the discussion)

6.1 - If you have a signature error and could not install use this steps in the link below (have to restart for the changes to apply)
http://www.craftedge.com/tutorials/driver_install_windows8/driver_install_win8.html

6.2 - After restarting, do again the step 6

7 - Open a terminal and insert “adb devices” command (without double quotes). You should see your device if connected and NOT in fastboot mode, remember to check the dip-switches.

Resources
Reference Document http://www.embedded101.com/Blogs/David-Jones/entryid/745/Dragonboard-410C-Android-Hello-World-Setup-
Driver Signature http://www.craftedge.com/tutorials/driver_install_windows8/driver_install_win8.html
http://www.technipages.com/enable-disable-device-driver-signing


#6

Sorry, one more detail, the USB Drivers VIDs are from the Coursera Internet of Things Specialization Course and the first resource of my response.


#7

@Anonymous link to “adb usb driver windows DB410C” is now fixed.

Rangel (@issaiass) Thanks for posting the workaround!


#8

Hello

I still have problems with getting adb to work. When I tried to follow this instruction and right click on ADB interface
it will not give me an option to updates drivers. My dip switches are all in 0 positions is that ok?

Cheers
Mateusz Jaszczuk


#9

What is the Windows version? Are there any errors? What are the available options? A screen shot of the Device Manager when you do the right click will be very helpful.


#10

Where does the android_winusb.inf file go once I download the file?

I’ve tried to use device manager to install it from a directory on my C:, but the Windows 10 Device Manager responds it already has the most current driver for a MTP Device or MTP USB Device. I don’t know how to associate the android_winusb.inf to the Snapdragon board 410c. Any suggestions would be most appreciated?


#11

@wahsabii The android_winusb.inf file should be installed as part of the driver installation, not really downloaded manually.


#12

Are you not able to install the driver using the instructions above? Why download the inf file manually?