How to Install Android ADB Interface Drivers Windows 10 Win 8, 7, XP / Vista 28 Android Debug Bridge (ADB) is one of the toolkits included in the Android SDK package that facilitates communication between your Android device and the computer. SAMSUNG_USB_Driver_for_Mobile_Phones.zip (15.3MB) The USB Driver for Windows is available for download in this page. You need the driver only if you are developing on Windows and want to connect a Samsung android device to your development environment over USB. Manually installing Android ADB USB Driver. This tutorial explains how to install the Android ADB USB driver manually. Follow it if the automatic installation fails. If yon don't have Android SDK installed, please. Select 'Android ADB Interface' from the list of device types.
I waste a lot of time trying to successfully install the ADB driver for my tablet in Windows 8.1. So here I will post what I did, in case anyone has the same problem.
IvanRFIvanRFAndroid Adb Interface Driver Download
8 Answers
UPDATE: Post with images ➤ English Version | Versión en Español
If Windows fails to enumerate the device which is reported in Device Manager as error code 43:
- Install this Compatibility update from Windows.
- If you already have this update but you get this error, restart your PC (unfortunately, it happened to me, I tried everything until I thought what if I restart...).
If the device is listed in Device Manager as Other devices -> Android but reports an error code 28:
- Google USB Driver didn't work for me. You could try your corresponding OEM USB Drivers, but in my case my device is not listed there.
- So, install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0 | Official site (v1.5.51.0)
- Restart the computer (very important)
- Go to Device Manager, find the Android device, and select Update Driver Software.
- Select Browse my computer for driver software
- Select Let me pick from a list of device drivers on my computer
- Select ADB Interface from the list
- Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yes to continue.
- Done!
By doing this I was able to use my tablet for development under Windows 8.1.
Note: This solution uses Samsung drivers but works for other devices.
Post with images =>English Version | Versión en Español
IvanRFIvanRFUse the awesome 'Universal ADB (Android Debug Bridge) Driver for Windows':https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEHhttps://github.com/koush/UniversalAdbDriver
- Windows 8 compatible
- comes signed, so does not require you to turn off windows driver signature checks
Tested under Win8.1.1 x64.
There is lots of stuff on this topic, each slightly different. Like many users I spent hours trying them and got nowhere. In the end, this is what worked for me - I.e. installed the driver on windows 8.1
In my extras/google/usb_driver is a file android_winusb.inf
I double clicked on this and it 'ran' and installed the driver.
I can't explain why this worked.
I had the following problem:
I had a Android phone without drivers, and it could not be recognized by the Windows 8.1. Neither as phone, neither as USB storage device.
I searched Device manager.
I opened Device manager, I right click on Android Phone->Android Composite Interface.
I selected 'Update Driver Software'
I choose 'Browse My Computer for Driver Software'
Then I choose 'Let me pick from a list of devices'
I selected 'USB Composite Device'
A new USB device is added to the list, and I can connect to my phone using adb and Android SDK.
Also I can use the phone as storage device.
Good luck
The most complete answer I have found is here:http://blog.kikicode.com/2013/10/installing-android-adb-driver-in.html
I'm copying the complete answer below.
For some reason I just couldn't get my machine to recognize Xperia J in Windows 8.1 64-bit. Even after installing latest Sony PC Companion (2.10.174). Device Manager kept showing yellow exclamation mark to an 'Android'.
Here's the solution, but I don't promise it will work on your device!
1. Find out your device's VID and PID
Open Device Manager, right-click that Android with yellow exclamation mark and click Properties.Go to Details tab.In Property, select Hardware Ids.Right-click the value and click Copy.Paste the value somewhere.
2. Download Android USB Driver
Run Android SDK Manager.Expand Extras, tick Google USB Driver, click Install packages.After installation, look for the driver location by hovering mouse over Google USB Driver. The location will appear in the tooltip.
3. Modify android_winusb.inf
Go to the usb driver location, for example in the above picture it is c:Androidandroid-studiosdkextrasgoogleusb_driverMake a backup copy of android_winusb.infOpen android_winusb.inf with a text editor. Notepad is fine but Notepad++ is better, it will syntax highlight the inf file!Look for [Google.NTx86], and insert a line with your device's hardware ID that you copied above, for example
Look for [Google.NTamd86], and insert the same lines, for example:
Save the file.
4. Disable driver signing
Run Command Prompt as an administratorPaste and run the following commands:
Restart Windows.
5. Install driver
Open Device Manager, right-click that Android with yellow exclamation mark and click Update Driver Software.Click Browse my computer for driver software.Enter or browse to the folder containing android_winusb.inf, eg: C:Androidandroid-studiosdkextrasgoogleusb_driverClick Next.The driver will install.Run adb devices to confirm your device is working fine.
6. Re-enable driver signing
Run Command Prompt as an administratorPaste and run the following commands:
Restart Windows.Run adb devices to reconfirm!
this worked for me, in my latest Micromax Yu Yuphoria!just download the installer and install it
karthikeayankarthikeayanIf all other solutions did not work for your device try this guide how to make a truly universal adb and fastboot driver out of Google USB driver. The resulting driver works for adb, recovery and fastboot modes in all versions of Windows.
Alex P.In Windows 7, 8 or 8.1, in Devices Manager:
- Select tree 'Android Device': remove 'Android Composite ADB Interface' [х]
- Press on main root of devices tree and call context menu (by right mouse click) and click on 'Update configuration'
- After updating your device should appear in 'Other devices'
- Select your device, call context menu from it and choose 'Update driver' and perform this updating
protected by Community♦Jul 10 '14 at 13:30
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Not the answer you're looking for? Browse other questions tagged androidwindowsdriveradbwindows-8.1 or ask your own question.
Has anyone been successful with hooking up a Samsung Galaxy with ADB running on Win XP Pro SP3? Links to already existing threads or tutorials related to this would be much appreciated! Thanks!
mobilekidmobilekid6 Answers
Install Samsung New PC Studio that comes with the CD. It includes Windows drivers
Make sure that in your phone settings:
'Settings > Applications > Development > USB Debugging' is checked
'Settings > About phone > Additional Settings > Mass store' is NOT checked- In android-sdk-windowsusb_driverandroid_winusb.inf add the following lines under [Google.NTx86] if you're using a 32-bit operating system. Otherwise add them under [Google.NTamd64] if you have a 64-bit operating system:
Connect your phone, in device manager you should see an Unknown device. Right click and say update driver, select android-sdk-windows/usb_driver directory. Android Bootloader Interface will be installed.
If your device isn't listed when you say adb devices in command prompt, type adb kill-server
(For the following steps, I assume that you are using Google Android SDK 1.5 R3 or above)
In order to get your Windows XP recognize the Samsung Galaxy Android phone so you can develop on device , you have to do the following:
refer to http://developer.android.com/guide/developing/device.html
Add the following to your android-sdk-windowsusb_driverandroid_winusb.inf:
under [Google.NTx86] add:
under [Google.NTamd64] add:
tplaner- Go to http://www.samsung.com/kies.
- Download and install kies(it will install the drivers)
Many people dislike kies. But this is the easiest way of getting the drivers installed.
It may be a problem with the phone if the drivers and adb are installed correctly see this thread adb doesn’t see phone device (Galaxy Apollo) for some more info on it
I was experiencing massive issues getting adb to work for my phone. It had been working at one stage prior to a firmware update (Now on Android 4.0.4 on a UK Samsung Galaxy s2 i9100) and it randomly stopped working. Im on XP 64 and it may only be an issue for 64 bit operating systems.
Usb debugging had always been set, the drivers were installed, but adb would not work.
Numerous help guides all seem to concentrate on getting the correct drivers to install with kies or with extracted drivers from kies only but this was largely not my problem (or the drivers with kies for the samsung s2 no longer allow adb?)My phone is rooted with superuser and busybox only but otherwise has completely standard firmware (had been rooted and was unrooted when android 4.0.4 was upgraded).
So starting from a point with the drivers installed I can connect to my phone as an MTP, as a Camera, as a Mass Storage device and with Kies. I have Kies installed and have had it reinstall the drivers multiple times but this should probably work fine without Kies and just the latest drivers installed as available from here http://forum.xda-developers.com/showthread.php?t=961956. I have a device listed in Device Manager 'Samsung Android ADB Interface' with driver version '2.9.505.831' but no ADB.
It appeared I had an issue with the uart connection on my phone (as shown in the phoneutil screen) and also I needed to be able to install the adb interface driver from the google sdk.
I was able to do neither of these using the standard methods/guides I was able to find elsewhere.
To change the uart setting back to pda and the usb connection back to pda the special code *#7284# no longer works on the Samsung Galaxy s2 i9100 Android 4.0.4 (or at least not for me)I had to download the bettercut apk (which I may very well had to pirate because I couldn't find it in the market) and made a shortcut to phoneutil manually
bettercut > new shortcut > no > all activities > phoneutil
There you can change the settings to modem and back to pda (when connected in modem mode xp listed a new device '7 CDS's' which would not install).
After that I had to install the google driver from the sdk (adt-bundle-windows-x86_64sdkextrasgoogleusb_driver)
And to allow Windows XP 64 to install the drivers you need to edit 'android_winusb.inf' to add the samsung galaxy as a valid device.
I added the following lines to [Google.NTx86] and [Google.NTamd64].
android_winusb.inf
I found instructions to add a device USBVID_04E8&PID_6860&MI_00 however this did not match my phone, I needed to manually determine the device ID and add it myself before windows would let me install the drivers.
Device Manager > Samsung Android Phone > Samsung Android ADB Interface > Properties > Details > Matching Device ID
And the phone ADB interface had the following ID USBVID_04E8&PID_6860&adb
Which I added as above (if your phone doesnt match you would need to do this too I think). I then updated the driver for 'Samsung Android ADB Interface' using the 'Android Bootloader Interface' which I can now select from the Google SDK Driver.
Install 'Android Bootloader Interface' from google SDK.
I then was able to reinstall the 'Samsung Android ADB Interface' driver as before or the 'Android Composite ADB Interface' from the google SDK and ADB started working (as tested with ADB Devices, mine is now listed, woot!).
So i think the problem was mainly the lack of the Android Bootloader Interface driver, with the UART thing possibly having some effect?
However I did have adb working BEFORE i decided to re-root my phone (only discovered it stopped working when I couldn't use ADB Explorer however I am failry certain I had used it not 10 minutes before). So why it stopped working I haven't a clue. I am pretty certain nothing changed on my pc, so perhaps setting the uart mode back and forcing the drivers to reinstall was enough to fix it. However maybe adb no longer works for the standard samsung drivers and you need to install the drivers from the sdk too?
Id be interested to know if there are other folk in the same boat, if they have any idea what happened.