Google Android USB and ADB Driver

I am looking for guidance or a definitive answer to the following. I want to use the Google Android USB driver and modify android_winusb.inf to support any number of Android devices. I was able to successfully add the HTC Evo tablet, but when I try to add LG (Optimus) or Samsung (Indulge, Admire), the driver seems to work fine, but ADB does not see it.

Can you make a Google Android driver for any Android phone? If so ... how?

I tried a lot of permutations of %SingleAdbInterface% and %CompositeAdbInterface% with variations of the Vendor and Product identifiers.

+36
android windows adb inf
Mar 14 '12 at 19:55
source share
9 answers

You need to change 3 things to make the Google USB driver work on any Android phone in any Windows:

  • Add device id to android_winusb.inf file
  • Digital sign of a modified driver
  • Add the device vendor id to the adb_usb.ini (no longer required)

and here are the details:

1. Add the device identifier to the android_winusb.inf file

format to add:

 ;Comment usually the device name %SingleAdbInterface% = USB_Install, USB\; here you put VID and PID %CompositeAdbInterface% = USB_Install, USB\; same as above but add the MI 

Before proceeding, VID is the identifier of the USB provider.

How to get vid and pid: they are in the drivers that you combine; but if you do not have a driver for the device, you can get it by opening the device manager; then right-click the device - select properties - in the new dialog, go to the "Information" tab> in the "Properties" menu, select "Equipment Identifiers". for example, you see something like:

hid

 USB\VID_2207&PID_0000&REV_0222&MI_01 USB\VID_2207&PID_0000&MI_01 

take this value for composite adb device and delete MI for one adb device, you will get

 ;MSI WindPad Enjoy 7 plus %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000 %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&REV_0222&MI_01 ; 

copy this 2 lines of TWICE, once to the [Google.NTx86] section, and another to the [Google.NTamd64] section.

REPEAT for each device you want to support

Now additional editing for the [Lines] section: edit

 [Strings] ProviderName = "Google, Inc." SingleAdbInterface = "Android ADB Interface" CompositeAdbInterface = "Android Composite ADB Interface" SingleBootLoaderInterface = "Android Bootloader Interface" WinUSB_SvcDesc = "Android USB Driver" DISK_NAME = "Android WinUsb installation disk" ClassName = "Android Device" 

To:

 [Strings] ProviderName = "Google, Inc." SingleAdbInterface = "MSI ADB Interface" CompositeAdbInterface = "MSI Composite ADB Interface" SingleBootLoaderInterface = "MSI Bootloader Interface" WinUSB_SvcDesc = "MSI USB Driver" DISK_NAME = "MSI WinUsb installation disk" ClassName = "MSI Tablet" 

2. Digital sign of the modified driver:

Although the original google usb driver was signed by google, changing android_winusb.inf will not allow you to install it on Windows 8, displaying an error message hasherror

 The hash file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. 

This is only in Windows 8. Windows 7 or earlier does not display this error message. You need to restore the directory file (possibly using the Windows SDK) and sign

Workaround: workaround for internal binding - verification of signature as a string: either temporarily or permanently:

temporarily

Go to the upper or lower corner of the screen on the left to open the charms panel and press the settings button.

select "Change PC Settings"

select "General"

Scroll down and click "Restart Now" in the "Advanced Launch" section.

Click "Troubleshoot. Click" Advanced Options. "Click" Windows Startup Options. "Click" Restart. "

or

run cmd and type:

 shutdown -o -r -t 0 

then after restarting, select "Disable driver forced signing" from the list. install the driver before rebooting.

Constantly:

press Window + Q

find cmd

right click cmd

select start as administrator from action bar

enter cmd:

 bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS bcdedit -set TESTSIGNING ON 

3. Add the device provider identifier to the adb_usb.ini white list (no longer required):

adb used to hardcode the whitelist of supported vendor identifiers. If your device was not listed, then adb completely ignored it. In order for adb recognize such devices, users had to manually add their vendor identifiers to %USERPROFILE%\.android\adb_usb.ini - one identifier per line.

on the command line:

 echo 0x2207 >> "%USERPROFILE%\.android\adb_usb.ini" 

Fortunately, Google removed VendorID filtering in later adb versions. Therefore, this step is no longer required.

Finally, you can test the installation:

 adb kill-server adb start-server adb devices 

and enable debugging in the developer settings on the Android device

This should restart the ADB server and device list. If the driver is working properly, the device must be specified.

+83
Mar 25 '13 at 7:01
source share

Can you give us a better description and example of what you are doing? Because all I need to do is put a line there for the device, and then save the file. Now just plug in your device and it works.

I usually use something similar to this line:

 ; ;some name for the phone (this seems to be arbitrary) %CompositeAdbInterface% = USB_Install, THE_HARDWARE_ID 

What I am doing is:

  • connect the device to the computer.
  • Go to the device manager.
  • Right click on the device you have connected.
  • Go to properties. Then select Hardware Ids.
  • Then enter the value indicated here.
  • Now add it to the line created in android_winusb.inf .
  • Unplug your device and plug it back in
  • Return to device manager
  • Right-click on the device and click the Update or Install Driver button.
  • Select your computer search for driver.
  • Select the directory Your_Android_SDK_Directory/extras/google/usb_driver/
  • Click ok

It seems like it always works for me, is that what you do? Or does it even help?

+8
Mar 14 '12 at 20:01
source share

Find the following file

C:\Users\ [your name] \.android\adb_usb.ini

And make the following changes:

 # ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT. # USE 'android update adb' TO GENERATE. # 1 USB VENDOR ID PER LINE. 0x2207 

I added 0x2207 to the file. This number is part of the equipment identifier, which can be found in the device hardware information section.

Mine was:

USB\VID_2207&PID_0010&MI_01

(I tried to run android update adb but did nothing.)

+7
Nov 14
source share

Answer 1 worked fine for me. I tested it on a new MID 10 tablet. Here are the lines that I added in the .inf file and it was installed without problems:

 ;Google MID %SingleAdbInterface% = USB_INSTALL, USB\Vid_18d1&Pid_0003&MI_01 %CompositeAdbInterface% = USB_INSTALL, USB\Vid_18d1&Pid_0003&Rev_0230&MI_01 
+1
Jun 29 2018-12-12T00:
source share
  • edit android_winusb.inf
  • Sign the driver
  • change adb

I also installed the universal adb driver from http://adbdriver.com/ and it works.

0
May 2 '14 at 10:18
source share

For my Azpen A727, the Windows driver is installed correctly, so only step 3 of Mohammad’s answer is needed.

0
Aug 23 '14 at 7:15
source share

It looks like the Google USB drivers have been updated to support Glass out of the box, so while you are using the latest drivers, you should have access to Glass through ADB. In my specific situation, I connected Glass to my machine around the middle of 2014, but did nothing with it. Now, when I tried to connect to it, I would not notice that it appeared in ADB, despite the fact that it appeared in the device manager. After much trial and error, I found out that I had to:

  • Log into device manager
  • Right-click "Android ADB Interface" under "SAMSUNG Android Phone".
  • Click "Uninstall." BE SURE "Removed driver software for this device."
  • Disconnect and reconnect Google Glass.

Then I was able to reinstall the driver using a regular Windows update. This made him search for the latest driver. Not sure why it has not been updated before, but I hope this helps someone who is still not up to the task.

0
Jan 19 '15 at 10:12
source share

Driver for Huawei not found. Therefore, I used the universal ADB driver:

  • Download this :
  • Extract ADBDriverInstaller and run the file. Make sure you connect the device via USB to the computer.
  • A window will appear.
  • Click Install.
  • A dialog box will appear. He will ask you to click the Restart button.

Before this read this link :

(The above. in brief, says to press Restart button in the dialog box. Select Troubleshoot. Select Advance Option. Select Startup Setting. Press Restart. After system been restarted, on the appearing screen press 7)

  • When the PC restarts, run the ADBDriverInstaller file ADBDriverInstaller . Select your device from the options. Click Install.

And it's done :)

0
Jul 13 '16 at 8:00
source share

instead of modifying the adb_usb.ini file, I made changes to the android_winusb.inf file in the android-sdk \ extras \ google \ usb_driver \ directory myself, and it worked for the Q88 MID tablet, but I copied both the [Google.NTamd64] and [Google. NTx86]

 ;Google MID Q88 %SingleAdbInterface% = USB_INSTALL, USB\VID_18D1&PID_0003&MI_01 %CompositeAdbInterface% = USB_INSTALL, USB\VID_18D1&PID_0003&REV_0230&MI_01 
-one
Apr 30 '13 at 20:09
source share



All Articles