Universal Android Usb Driver Windows 10

11 views

Skip to first unread message

Karmen Mcarthun

unread,

Aug 3, 2024, 3:49:26 PM8/3/24

to dragdioplette

Unlike some others, my Android SDK setup went smoothly on my new Windows 7 Pro 64 bit machine. However, I am currently hung up on installing the android usb drivers. What is the current state of this issue? There has been some discussion of this problem on the web but no consensus is immediately apparent.

The Android USB driver page for Windows is very misleading, IMHO. It doesn't mention that it doesn't work for all Android devices. It turns out that for certain devices you need to go to the manufacturer's website for the USB drivers, NOT use the generic Android USB driver.

For example, in my case the generic Android USB driver would not work for my Sony Ericsson X10a. I forget the exact error message, but the Windows Device Manager would not recognize the driver software as being valid for the device. But after I downloaded the X10a USB driver from the Sony Ericsson developer website, the Windows Device Manager was happy with it. Then I was able to install my Android development apps on the device and debug via Eclipse/DDMS.

I had the same problem - with OEM drives and Android SDK drivers too. Finally what helped me was:Device Manager - Update Drives Software - Browse my computer for driver software - Let me pick from a list of device drivers on my computer - Have Disk - Browse for file android_winusb.inf (in sdk folder) - Android ADB

I tried all this solutions but nothing worked. Finally i found that i need to connect my device as camera and not as media device in phone under "USB PC Connection" in settings and i got it worked. But really it is a long struggle... :) For more details, see this link..

I found this, which isn't really universal since it defines a bunch of specific device IDs to identify them and is outdated anyway. There's also this pull request posted on that project's GitHub page and also another repo containing a dead link to already singed driver (or more precisely, signed INF that identifies ADB interface by the universal compatible ID).

So what are my options? Anyone found such a driver/INF that can be just installed and forgotten about or do I have to go the signing the modified android_winusb.inf with self-signed certificate route if I don't want to disable driver signature enforcement and such?

So far, my phone has used like 6 different device IDs to identify itself and under certain circumstances, I even have to re-install the official driver/INF for it to work again and confirming that I do want it installed, even if device ID doesn't match.

Thanks, I didn't look in system winusb.inf and manufacturer supplied INF must have been downloaded from Windows Update, placing the entry in Device Manager that usually appears under Universal Serial Bus devices under a different category, so I didn't realize it was already supported out-of-the-box.

I use Win10 versions 1809 and 1909 on my two machines. Depending on the software currently running on the phone, hardware ID differs, so who knows which is the "right" one. Vendor ID is always VID_0FCE, as should be.

That problem requiring re-install was actually encountered when putting the phone in fastboot mode. I suspect a conflict happened due to an old entry having a different compatible ID (adb vs fastboot and the fact that fastboot ID is missing from winusb.inf), but the same vendor and device ID. The ID when in fastboot mode is constant, but otherwise it seems to depend on the OS running, even though it should be constant as well as long as we're talking about the same phone model, in this case Xperia E3.

I did some cleaning up in Device Manager and removed two drivers that were downloaded from Windows Update for ADB, so now I have phone's entries under Universal Serial Bus devices, not under some custom categories like before. I also added USB\Class_FF&SubClass_42&Prot_01 ID to the list of Prevent installation of devices that match any of these devices ID group policy, so the OS won't try "updating" them. Manually installing ADB Device through update wizard in Device Manager while phone is in fastboot mode also works and makes it visible to fastboot utility.

The device ID when in fastboot mode is VID_0FCE&PID_0DDE, so that *.inf couldn't help the OS detect it as compatible with the driver. But you can still set it for use with fastboot mode by manually selecting it in driver update wizard.

It's good that at least for ADB mode, it works out of the box either way. Though by default settings, OS might still see fit to download "drivers" from Windows Update, even though no specialized driver is usually involved since it's all just about the .inf file identifying and setting up the device to be driven using winusb.sys.

Xperia Manufacturer offers Emma to flash a device.
Emma dosn't use fastboot mode, flashmode is used instead.
Emma does use a Gordons Gate driver ggsomc.sys, signed by 'Sony Mobile Communications AB'.
-devices/get-started/flash-tool/download-flash-tool/

It looks like clearing old entries in Device Manager that was setup by INF file that came with those drivers from Windows Update, deleting said drivers, setting up fastboot device entry using device update wizard and picking built-in ADB Device helped with the issue of the said device entry for fastboot mode being reset under certain circumstances.

What I have tried:After some Googling I found several guides telling me to add the devices hardware id to googles driver "android_winusb.inf" under [Google.NTx86] and [Google.NTamd64].

I couldn't update the ADB driver on Windows 10. When I tried installing the generic Google ADB driver by clicking on "Browse my computer for driver software" and choosing the driver folder, Windows ignored the drivers, saying there were no drivers found.

The missing step is to continue guiding Windows after clicking on "Browse my computer for driver software". When selecting the folder with the driver, click on the "Let me pick from a list of device drivers on my computer". Select "Show all devices", then "Have Disk". This defaults to drive A: --- navigate to the folder with the extracted USB drivers, probably named usb_driver. You'll then be able to choose "Android ADB Interface" and install the driver.

I had similar problems, adb devices didn't list any devices once I'd upgraded to Windows 10. I happened to have an Intel-powered Android phone connected over USB. I ended up removing the Intel-specific Android Driver (downloaded yesterday, version 1.9 which doesn't explicitly support Windows 10) and then used the universal Android USB driver following the steps described in the following article (using Device Manager and removing the previous driver). For good measure I disconnected and reconnected the USB cable after removing the previous driver and before selecting the replacement driver.

My computer has several possible matches in Device Manager when I selected choose the driver manually. I checked each one until I found what seemed to be the relevant one i.e. the Universal Driver, then from the list I picked the Android USB Driver. As you have a different device, you may need to pick a different device driver from the list.

Google's adb driver works fine with any Android phone. It's Microsoft policy to forbid class drivers so each vendor is required to provide same driver with different hardware ID and to pay money for Windows Logo program and signing process.

I've tried to debug on my S4 without the driver installed, but Eclipse can't recognize it and doesn't show it as being online (shown in the included screenshot). Eclipse does recognize the Nexus 4 AVD I created, but not my S4. I have enabled Developer options and have USB debugging checked in my phone's settings.

That fixed my problem, it seems to work now. At first, it didn't make a difference, but I went into Developer options in the Settings menu and unchecked/rechecked the USB Debugging box. Then my phone gave me the option of allowing my PC to run apps on it. And it all worked from there.

I'm sorry I thought you had a dell tablet your probably better off in a Samsung forum the drivers I linked are for the Dell Venue 7 / 8 not the Samsung. You need Samsung drivers not Dell sorry I read your post wrong. Best of luck.

I have a Samsung phone, but I need a driver for my Dell PC. The driver should work for all manufacturers of Android devices, but needs to be specific to Dell computers. But the Dell website apparently changed where to find it.

I have a dell venue 7 3g I have downloaded the drivers but when I try to fastboot it just says waiting for decices .please help I want unlock the boot loader.I have android SDK fastboot and abd drivers everuthing ,I go to cmd type fast boot oem devices it just shows waiting for devices.please help me.

The Lexmark Universal Print Driver provide users and administrators with a standardized, one-driver solution for their printing needs. Instead of installing and managing individual drivers for each printer model, administrators can install the Lexmark Universal Print Driver for use with a variety of both mono and color laser printers and multi-function devices.

The Job Accounting option allows an organization to track print jobs for accounting purposes by associating the print job with specific account information, including a user name or ID, an account code, and a department code. This enables the tracking of the number of print jobs from different users or departments, and the billing of those print jobs to a specific account. By associating print jobs with specific account information, quotas can be enforced on the print jobs that users can submit.

With only one package to manage, testing and internal certification of print drivers is simplified by the use of the Lexmark Universal Print Driver packages. Time spent on installation, both on servers and workstations, is greatly reduced, and hard drive space formerly occupied by many product-specific drivers is now diminished significantly.