Hi, koush, I have several android phones. After installing universal adb driver, it appears adb only recognizes one devices at a time (adb devices).
So let me explain more detail.
I have Phone A and Phone B, no matter which plugs in the last, device manager always shows an unknown device . And phone A and phone B can successfully be accessed seperately.

P.S. I use Windows 7

my device hardware ids

;PRO 5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0002

unless it doesn't get detected in Adb/neither in Fastboot mode thanks
in advance

Unfortunately it is not working for me as there is still no response from my Xiaomi redmi note 4 phone.

Hello, could you help me, I need a universal mathematical driver for the System and applications, capable of changing the characteristics of the System and applications based on mathematical formulas and adjusting the mathematical values of values including constants, the System Windows and it applications. Regards.

Hi, Koush,

Can you compile with native support for Windows 10?

Thanks!

Can i get a download for Mac system of AdB driver

ffxdgb

Instead of maintaining multiple HardwareID for all known Android devices just use 2 (for adb and fastboot interfaces) lines for each platform:

[ClockworkMod.NTx86]
%SingleAdbInterface% = USB_Install, USB\Class_ff&SubClass_42&Prot_01
%SingleBootLoaderInterface% = USB_Install, USB\Class_ff&SubClass_42&Prot_03

[ClockworkMod.NTamd64]
%SingleAdbInterface% = USB_Install, USB\Class_ff&SubClass_42&Prot_01
%SingleBootLoaderInterface% = USB_Install, USB\Class_ff&SubClass_42&Prot_03

From http://adb.clockworkmod.com it downloads .msi.exe instead .msi.

i just installed the universal adb driver i need support for samsung j1 and where do i need to use code

I have a pull request that is 3 years old that hasn't been merged or closed. Is there someone else maintaining this project?

...because it's not possible with UniversalAdbDriver installed under Win7 64-bit to assign your android_winusb.inf to the "HTC One" in device manager by clicking "Have Disk": the error messagebox that pops up after selecting the android_winusb.inf reads: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

On a side-note, there are two different download links floating around the webs, http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi and http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi --- both have different file-sizes, I've tried them both but what's the difference here?

On another side-note, I've seen screenshots on some blog post about UAD where "ClockwordMod" is showing up as a vendor in Windows' "Select the device driver you want to install for this hardware" dialog's long listing of manufacturers and drivers --- but it never shows up in there for me, for both versions of the msi.

(Needless to say, for both versions of the msi prior to installing, I unplugged my phone, after installed I restarted both the Windows machine and the phone.)

Sorry, any idea how to fix this? Need a full log?
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.

I have tried to install the ADB driver in Windows for a Galaxy S2 with a "SlimKat" custom ROM on it. With the current version of the installer, the phone is not recognized, and the driver is not activated.

But I found a simple workaround to make Windows install the driver for the device nevertheless:

1. In the windows device information, look for the USB ids the phone uses. In my case there were the strings "USB\VID_18D1&PID_D002" and "USB\VID_18D1&PID_D002&REV_0226".
2. In the file android_winusb.inf from the installer, locate some lines that contains the same VID_* id in the section [ClockworkMod.NTx86] and/or [ClockworkMod.NTamd64].
   In my case I found these lines:
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D001
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
3. Duplicate these lines and change them to hold the ids determined in step 1:
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D002
   %SamsungGalaxyNexusADBInterface% = USB_Install, USB\VID_18D1&PID_D002&REV_0226
4. Save the file (you may need to be admin) and install the driver. This worked for my phone.

Is it possible to add this workaround to the readme file?

Thanks!

it is not working for samsung j1 ace

Could you please add the Kurio device support ?
The devices are these ones : http://www.kurioworld.com/k/uk/parents/products/

%SingleAdbInterface% = USB_Install, USB\VID_2922&PID_0C02
%CompositeAdbInterface% = USB_Install, USB\VID_2922&PID_0C02&MI_01

Thanks!

i opened the vysor app and connected my phone via usb but it says theres no device connected. what should i do

I need that

Hello, i'm stuck in the boat of trying to use a rockchip provided ADB driver, and I was wondering if you could include the .inf entries for these devices as well

the driver is in this zip: http://minix.com.hk/downfile/RK_DriverAssitant.zip

i'm curious as to whether this is entirely possible. I think all of the minix devices share common grounds

included is the android_winusb.inf as listed at the end of this post

;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 08/27/2012,7.0.0000.00001
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat

[ClassInstall32]
Addreg = AndroidWinUsbClassReg

[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1

[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64

[Google.NTx86]

;Google Nexus One
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01

;Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E23
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E24&MI_01

;Google Nexus 7
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E41
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01

;Google Nexus Q
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_2C11

;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01

;rockchip
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0011&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0013&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0014&MI_01

[Google.NTamd64]

;Google Nexus One
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01

;Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E21
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E23
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E24&MI_01

;Google Nexus 7
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E41
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E42&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01

;Google Nexus Q
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_2C10
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_2C11

;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01

;rockchip
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0011&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0013&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0014&MI_01

[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT

[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall

[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys

[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install

[WinUSB_Install]
KmdfLibraryVersion = 1.9

[USB_Install.HW]
AddReg = Dev_AddReg

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"

[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles

[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"

[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll

[DestinationDirs]
CoInstallers_CopyFiles=11

[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64

[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1

[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2

[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"

Hi Sir,
could you please add the support for moto e model .

I added vysor to chrome and installed the ADB drivers. Did not get to use it. Then my scanner is giving "The scan cannot be performed because another program or computer is using the networked HP imaging device. 8,[(0, 18, -2147467259)]". I have no reason to believe the Adb driver is causing this, but the standard procedure is to uninstall the stuff you installed since it last worked. So I go looking for the driver in Windows 10 device manager. Then I realize I don't know enough to find the driver. I read some of the issues and realize I have some work to do to figure this out. Or in other words, no good deed goes unpunished. You do a great thing, and then someone asks you to do more work, for free.

USB\VID_1F3A&PID_1002&REV_0233&MI_01
USB\VID_1F3A&PID_1002&MI_01

Thanks!

It looks like you already have the vendor id. The PID is new. I ended up using Samsung's ADB driver.
Hard Kernel has a modded google driver, but it is unsigned, or rather the signature doesn't work after the modifications.

VID_18D1
PID_0002
Serial number: BABABEEFBABABEEF

http://com.odroid.com/sigong/nf_file_board/nfile_board_view.php?keyword=&tag=&bid=22

BTW, thanks for posting such an awesome project.

I tested with a Verizion version of the Asus Nexus 7 (2nd gen). The driver did install, but the ADB device manager was not detecting it. I uninstalled the Universal Driver for the device and replaced with the latest version of the Google driver and now it is working as expected.

Android 4.4.2

Build #KVT49L

Hello,

I want to be able to connect my Samsung Note 3 (ha3g) while in TWRP recovery mode. I previously had Samsung drivers installed, which was not detecting the device, so I un-installed it and installed
UniversalADBDriver. But I am still not able to get the device to be recognized (Yellow !)
I tried picking ADB, ADB Composite, and Samsung Android Interface from the list but in all cases I see the Yellow !
I read on a forum that Samsung doesn't yet support Android drivers for Windows 10, is that got to do anything with UniversalADBDriver ? or am I missing something else ? (I am a bit confused here!)

I'm trying to get adb to connect to this ProScan PLT7650 tablet I have, and it hasn't been working, even with this universal driver. I've tried adding the AdbInterface ids:

;ProScan plt-7650
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0012&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0012&REV_0310&MI_00

but that didn't seem to fix it. Could we have support for this device added? I can try to get any more info that you need.

VID_0BB4&PID_061A&MI_01

;PRO 5
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0002

USB\VID_413C&PID_B11B&REV_????&MI_01
USB\VID_413C&PID_B11B&MI_01

I checked out the source code and tried to sign the driver. (I'm trying to add the HP Slate 7, which HP doesn't provide a driver -_-).

SignTool is giving me and "File not Found" error. I tried loading the certificate in my personal store and replacing Private for Personal in the script but nada.

The included certificate is the public one, right? So it cannot be used to sign the driver.

Can I just pull request the modified .inf?

Please let us know when can we have an ARM64 version for Windows on ARM OS. We can help you test We have Windows on Rasberry Pi setup. Please pursue it we at Windows on Rasberry Pi community will be glad to extend support in testing your drivers and tools for ARM64.