Android Won’t Connect to Windows Over ADB? Fix It in 3 Easy Steps

Kannon Yamada Updated 19-11-2019

Is ADB not detecting your device? If Android is unable to connect over the Android Debug Bridge (ADB), fixing it only requires three basic procedures.


We’ll show you how to get it working again.

ADB Can’t Find Your Device? Here’s the Fix

Sometimes, Android USB devices won’t connect to a Windows system. Failed ADB connections usually have one root cause: bad Android USB drivers that load in place of the right ones. Windows doesn’t make it easy to remove the wrong drivers, unfortunately.

But before attempting to troubleshoot an ADB connection, you must first enable USB debugging on your phone What Is USB Debugging Mode on Android? Here's How to Enable It Need to allow USB Debugging on your Android? We explain how to use debugging mode for pushing commands from your PC to your phone. Read More if it’s not on already. When turned on, USB debugging gives you direct access to the file system of an Android device from a desktop computer. Without debugging enabled, it’s only possible to interact with your phone’s media storage, such as the SD card or a specially formatted media directory.

If you’ve already met the requirements, fixing the problem takes about five minutes and three basic steps:

  1. Connect your Android device and PC via USB and remove the ADB drivers. Then disconnect your device.
  2. Run a USB-driver eliminating utility, such as USBDeview, to kill all unnecessary Android drivers.
  3. Install Koush’s Universal ADB Driver.

We’ll go over each step in turn. Here’s the software you need:


Download: Nirsoft USBDeview (Free)
Download: Koush’s Universal ADB Driver (Free)

Step 1: Connect Your Device and Uninstall the Current Driver

First, connect your Android device to your computer via USB. This step allows your device to display in Windows’s Device Manager. Open this by typing Device Manager into the Start menu to search for it.

This image is of the Windows 10 device manager in the Search window

Next, in the Device Manager, remove your currently displayed Android ADB driver. To remove it, right-click on the category that contains your phone—this might be LeMobile Android Device, Portable Devices, or something similar.


Under this, you’ll see the Android Composite ADB Interface driver. Right-click this to bring up the context menu, then select Uninstall.

android device inside of Windows 10 device manager

Make sure to check the box for Delete the driver software for this device.

remove bad usb drivers for adb


Now you can disconnect your Android device from your PC. Doing this prevents the same incompatible driver from loading upon reconnecting the Android device. While technically not required, we recommend doing this because it will show you the driver causing the issue, in case it somehow reloads itself.

Step 2: Remove Bad ADB Drivers

The Nirsoft USBDeview utility comes as a zipped executable. That means you must unzip it and it doesn’t require installation. This utility may show up as malware in a virus scan, but rest assured that it’s safe.

After unzipping the file, open the extracted folder and run the executable utility inside it. USBDeview displays the total number of installed USB drivers on your computer, both connected and disconnected.

Look for the colored status indicator at the far-left of the USBDeview window. There are four colors. Each represents a different status:

  • Green indicates that the device is connected and that it functions properly.
  • Pink means the device can unplug and works properly (although in reality, it may not actually work properly).
  • Red indicates a disabled USB device.
  • Gray means the device is installed, but not connected.

USBDeview elimintes drivers for USB devices in Windows

Now, remove all gray items with the words “Google”, “Linux”, “ADB”, or “Android” in the title. When troubleshooting this issue, we typically remove every item that’s not green.

Removing a device driver means that you’ll need to reinstall drives for that USB device if you want to use it again. Fortunately, most of the time Windows automatically installs USB devices, so it’s not a big deal.

Step 3: Install the Universal Driver

Koush’s Universal ADB Driver works for every Android device, no matter how niche. After installing it, you should be able to assign the right driver to your phone.

Manually Install a USB ADB Driver

To do a manual install, first run the executable package for Koush’s Universal ABD Driver you downloaded earlier, which installs the driver to your computer.

Second, plug your Android device into your PC via USB. The correct USB drivers should load. You can check by going to Device Manager in Windows as discussed earlier. If there is a different driver listed than what you saw in the first step, chances are you have the correct USB driver loaded now.

android device located in windows 10 device manager

In the Device Manager, locate the new ADB/USB driver. This will likely be under your phone’s name in the Portable Devices section, but Android devices can appear in different locations in Device Manager. You may need to check each possible device class (such as Android Phone or Samsung) in the Device Manager before you find yours.

If you can’t find it, sometimes you’ll need to check the notification shade on your Android device for additional steps. This allows you to authorize a specific computer to connect to your device beyond charging purposes.

Once you find it, right-click on your device and choose Update Driver. From the resulting menu, choose Browse my computer for driver software, then Let me pick from a list of device drivers on my computer.

Here, you will see a list of compatible drivers. Choose one of these (starting at the top if fine). If it fails, repeat the process by going down the list to locate another driver that works.

android ADB interface in Windows 10

Install the Universal ABD Driver Instead

If you can’t get the right driver installed using the above method, you will need to perform a manual installation in order for Koush’s driver to work. Thankfully, the Device Manager lets you hand-pick a driver from your computer instead of browsing from a list.

Instead of selecting Let me pick from a list of device drivers on my computer in the previous step, hit the Browse button and manually find the directory where you installed Koush’s drivers.

The location in File Explorer should be something like this:

C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\

You may need to search for the folder if you don’t see it there. Once you select the right location, hit Next and Windows will install the drivers. From now on, whenever you connect your Android device with ADB enabled, Koush’s drivers will load in place of the ones that failed to work.

Finally, restart your computer and attempt to connect over ADB again. You should have success at this point.

Still Not Able to Connect to ADB?

If you still can’t connect to ADB, your device might have a deeper problem either at the firmware or hardware level. Major hardware issues include the following:

  • A damaged USB port on your computer or smartphone
  • Defective firmware on your smartphone, usually caused by a custom ROM
  • A damaged or defective charging cable

For example, I once owned a Nexus tablet that intermittently disconnected from the computer. Even after replacing the micro-USB port, the tablet continued to malfunction. The cause of disconnection turned out to be a buggy custom ROM. While custom ROMs are great for reviving old hardware, they introduce another layer of complexity that often causes issues.

There are many potential causes for a device that refuses to connect through ADB. Try various cables and ports on your computer to troubleshoot the problem. Our guide to fixing an Android phone that won’t charge Your Android Phone Won't Charge? Here Are 7 Fixes to Try Find that your Android phone won't charge? Follow these tips to figure out why and get it working again. Read More has some tips that can also help poor connections.

EasyTether Problems: Unable to Connect by ADB

Some people who use both a Mac and Android try to share their internet connection over a USB interface using the EasyTether app. However, we don’t recommend this. The app costs money and free methods exist that are both superior and easier to use. See our guide on how to USB tether with Android How to Connect Mobile Internet to Your PC via Tethering With data tethering, you can use your mobile internet on your PC, laptop, or tablet. All you need is an Android phone! Read More for better ways.

For example, in newer versions of Android, Google offers native Bluetooth and USB tethering. If your phone has a dual-antenna design, you can even create a hotspot using a Wi-Fi connection.

If EasyTether (or any USB tethering app) fails, the best fix is trying to find the correct driver as outlined above. That means finding the incorrect ADB driver that Windows installed and swapping it out for something that works.

That may require additional troubleshooting steps, so we only recommend these apps for older Android devices that don’t support the latest in tethering technology.

Universally Good ADB Drivers

Now you know what to do when ADB is not working. This method of purging bad Android USB drivers and installing Koush’s drivers works for every Android device we’ve tried it on. It’s a bit ridiculous that Google never released a universal ADB driver for Android devices, despite the issues that many users continue to experience.

Now that you’ve got it set up, check out the best apps that utilize ADB on Android 6 Android ADB Apps for Powerful Features Without Root Want to get more control over your Android device? Try these apps that let you use ADB functionality without rooting. Read More .

Related topics: Android Rooting, Android Tips, Drivers, Troubleshooting, Wi-Fi Tethering.

Affiliate Disclosure: By buying the products we recommend, you help keep the site alive. Read more.

Whatsapp Pinterest

Leave a Reply

Your email address will not be published. Required fields are marked *

  1. Mike
    January 1, 2020 at 6:40 pm

    Thanks for providing this information, my issue wasn't that I couldn't connect but rather I couldn't get my emulator to work. Going through the steps in this article was the fix for me, much appreciated.

  2. Masutin
    December 18, 2019 at 10:47 pm

    Not sure if my problem got published, I solved it, coincidentally or not, by pressing the keys for Download mode in S6310 - Vol-, Home, Power, and waiting for a few vibrations (you need one for Download), i.e. not using that mode. Still, related or not, I can't install APKs via ADB now.

    • kannon
      December 19, 2019 at 6:25 pm

      Are you using Odin? What error code are you getting when you try to sideload through ADB?

  3. Anarghya S
    November 20, 2019 at 12:51 am

    Got to chrome://flags/#interest-feed-content-suggestions then disable this and relaunch the chrome. It worked for me.

    • Kannon Yamada
      November 20, 2019 at 8:50 pm

      How does this fix ADB issues?

  4. Bryan
    August 25, 2018 at 11:44 pm

    I have a G4 H811 (tmo) and have tried a variety of drivers discussed here, on different computers, but ADB always shows my phone and says "offline"
    I do have USB debugging on and OEM unlock checked. it shows debugging in the notification bar but I never get to the place where on my phone I have to allow the computer RSA code to access my phone. only get "allow USB connection".

    any help?

    • Kannon Y
      August 26, 2018 at 12:19 am

      Hey Bryan, the comment below yours mentions probably the first step everyone should take: IMMEDIATELY after connecting your smartphone to your computer via USB, check the smartphone's notifications tray to see if there's a prompt to connect through "transfer data" (not all phones offer this option because sometimes it's mislabeled as another connection option).

      That should actually be the first thing that everyone does, because very few phones actually automatically connect unless this basic step is taken.

      • Bryan
        August 26, 2018 at 1:36 pm

        (I tried replying before but don't see my reply, so forgive me if I am making a double post.)
        I tried your suggestion but the only prompt I ever get is "allow USB connection". I have tried not allowing, to see if it tries the RSA prompt but no luck. I have tried allowing USB connection and selecting each option (charge only, MTP,PTP,midi), no luck. I have tried turning off USB debugging and back on again, no luck.
        it always shows the device ID in "ADB devices" but says "offline".
        I think it is some simple problem with the phone, not windows drivers/software. I have tried several different ADB composite drivers and USB device drivers.
        I have much experience with G3 rooting, downgrading, TWRP... but this G4 is really frustrating me!
        I need to first unlock the bootloader (which is supposed to be simple on the tmo h811), then install TWRP, then supersu. but can't even get to 1st base with the boot loader without ADB access.
        I'll appreciate any other suggestions. it MUST be some simple phone setting somewhere!

        • Kannon Yamada
          August 26, 2018 at 5:49 pm

          Sorry that your comment got lost! We need to improve our comment system. :-(

          AFAIK, ADB does not require root access and it also does not require an unlocked bootloader. Although an unlocked bootloader is virtually a requirement because there's not much you can do with a phone that has a locked bootloader.

          Can I ask what kind of debug bridge interface you're using? Like, are you using the official development kit (like Android Studio) or are you using something like Minimal ADB and Fastboot (which I HIGHLY recommend over the official software).

          Another question: Forgive me for asking this question, but did you try manually changing the ADB driver? There are multiple drivers that you can install. Oftentimes, if you are unable to establish ADB, you might need to toggle the driver until you find the right one. I outline this process in the article, but it can be confusing because it's not at all intuitive. A lot of people are afraid to change the driver because of the possibility for system instability. I have yet to find someone who has made their computer unbootable using this method though.

          Anyway, please read Step 3 in the article for more details. (if you have not yet fully read this step)

        • Bryan
          August 26, 2018 at 11:43 pm

          Kannon there was no repy button on your last post, so this may be out of order.
          - I am using Minimal ADB and Fastboot
          - I have tried 2 different LG ADB drivers (2014 and 2016 dates) and 3 clockworkmod drivers (android ADB interface, android composite ADB interface and LG android interface). all have the same results- device ID and device offline.
          - I rebooted my PC after each driver change.
          I must ask: if the windows driver was the problem, would it show my device ID? it seems to see the phone fine but the phone seems to be rejecting access.
          on the phone I have USB debugging on, and OEM unlock bootloader checked.
          I have tried turning USB debugging off and back on, rebooting my phone.
          I am near giving up. if we find the solution, i'm sure it will surprisingly simple. but I am becoming doubtful about finding it. (as I also mentioned, I have tried on 3 different (windows 7) PC's.
          thanks for all your attention to this!!

    • Kannon Yamada
      August 27, 2018 at 12:25 am

      It sounds like you've tried pretty much everything that you need to have done.

      To answer your question, I have experienced issues where the wrong ADB driver gets loaded by default and trying different drivers gets ADB working. To clarify, each one of these drivers would partially function. That may not be the case though because it seems that your ADB connection is correctly reading your device ID, which implies that the correct driver package has been loaded.

      I can't remember ever NOT getting ADB working even on super obscure devices. So for a device like the LG G4 which IIRC was the LG version of the Nexus 5X (or something like that) it should absolutely be working unless you've got an issue with the ADB software itself. I found a post on XDA where the developer found a workaround for this issue though. But if I post an external link it's going to delay my response to you. Can you please email me and I'll send you the instructions? Go to our About page and my email is available there (kyamada at makeuseof dot com)

      the fact that you have tried this on three different computers also suggests you have used a freshly downloaded copy of Minimal ADB and Fastboot, so this is really a long shot. I'll keep think about this issue. This has gotta be really frustrating for you. ADB really sucks. :-(

    • Kannon Yamada
      August 27, 2018 at 2:44 am
  5. m.krelik
    April 17, 2018 at 11:05 pm

    If your having issues, you should seriously try connecting to CHARGE ONLY first, that made the driver install work for me.
    Kinda annoying me ever troubleshoot guide I go to for an issue wants you to install a program without throwing in some simple suggestions that may work first.

    • rich.E
      June 22, 2019 at 1:10 pm

      Thanks for this, it enabled the Universal driver installation (finally!)

  6. Alexyu
    September 10, 2017 at 11:57 pm

    First, thanks for the explanations and answers. Concerning connecting Android phones to Windows PCs, even after reading your explanation (and many others) I still have a fundamental question, specially including the universal ADB driver -- but let me state it as an operational one:

    When connecting an Android phone (in my case, 3 different Samsung Galaxy models) to a Windows PC FOR THE FIRST EVER TIME, are these the correct steps?
    1) Don't check anything on the PC (it's a just-installed system, with no previous phone connection);
    2) Install the Koush Universal ADB driver;
    3) Install Samsung's drivers using their 'Samsung USB Drivers For Mobile Phones.exe (';
    4) Switch on "USB Debugging" on the phone;
    5) Connect the phone to the PC using a USB cable (for connection, not charging only);
    6) Depending on the phone model, the connection mode/protocol may have to be defined now (because newer models seem to only allow this definition when USB is actually connected), but what should it be: MTP? PTP? Kies?
    7) The PC should 'find' the new device(s) and install appropriate drivers (but, which ones should be pointed to: the Koush ADB or the Samsung drivers)?

    I'll be reinstalling this system (to get rid of several accumulated problems), so the above WILL be true; it's a dual-boot XP Pro SP3 / Win 7 Ultimate system, so I'm sure there is no 'physical' problem with the USB cable, since the same one is used, on the same USB port (non-hub) on both XP & 7 -- but, currently, I'm able to connect the phones on both systems, with different degrees of 'precariousness', but on XP the MyPhoneExplorer app works fine, and on W7 not, so I hope to get this sorted out.

    As the basis for my doubts, is the whole "device management" idea, here: The 'devices' involved seem to include "Samsung Android phones" with "Samsung Android ADB interfaces", "mobile USB serial ports", "Android UMS composite USB devices", "ADB interfaces" with "Samsung Android composite ADB interfaces", "Samsung Android USB Modems", "Samsung mobile Modems" and "Samsung mobile USB Modems", and many others (probably, many of them as a result of several reinstalls over time)... My main doubt is: Conceptually, what could/should be the 'devices' involved (or by what names should they appear)?

    Hopefully, if the installation order I've listed above is correct, I should be rid of these problems on reinstall -- but, since I remember having many problems with this over time, I'd appreciate to hear your opinions on this -- and, again, thanks for your site and attention.

    • Kannon Yamada
      September 11, 2017 at 1:40 am

      Well, I greatly appreciate your expansive and detailed explanation of the problem. I will do my best to assist.

      ADB drivers are generally related to the SoC (system-on-a-chip). The SoC combines a lot of features that were previously separate from one another, like the processor, southbridge, etc... One function that got rolled into the SoC is the software that dictates how a smartphone interfaces with a computer using the Android Debug Bridge (ADB). So, more or less, those driver packages that you must choose from are related to a specific Exynos or Qualcomm Snapdragon derivation.

      I believe if you choose manual installation, Windows will display compatible device driver packages. It should not render your system unbootable if you try different driver packages, since these drivers are probably written for the SoC that the phone is based on.

      The names of the driver packages, unfortunately, will be different for you than they are for me. I have ADB'd many, many devices and the package that most often works for me is anything having the word "composite" in it. But even that is a total crap-shoot. The sad truth is that ADB is not a well troubleshot method and it's fraught with complications.

      To clarify, once you select "Update Driver" from device manager, it's important to note that it's absolutely necessary to choose "Let me pick from a list of available drivers on my computer" because this option will only show compatible drivers. It's when you force install an incompatible driver that your system may experience instability.

      Regarding file transfer method, if you don't have file transfer as an option (some phones do not for some crazy reason), I've found that photo transfer works in its absence. It may not be the same for you.

      Let me know if you have any other questions. By the way, our thread tracking is awful. If you want help over email, find my email address from our about page ( and write me. I may not respond immediately, but I'll try to get back to you as fast as I can.

      • Alexyu
        September 11, 2017 at 2:03 am

        Thanks for the quick reply -- and I'll try to treply right away, so hopefully you'll still see it right away.

        I appreciate your comments, and hate to sound ungrateful, but my two main doubts still remain:

        - Are the 7 'steps' I listed, for connecting an Android phone to a Windows PC FOR THE FIRST EVER TIME, correct? If not, what are the ones you'd follow?

        - During installation, which device drivers should Windows be pointed to: the Koush ADB or the Samsung ones? Actually, I'm still in doubt if they're 'the same thing' or 'different things' (or, in other words: Are they competitors or complementary, for installing the connection)?

        Sorry if your reply did cover this -- but, if it did, I wasn't able to understand that, since there should be no "update driver" in this process, since it's a 'first-time install' all the way...

        • Kannon Yamada
          September 11, 2017 at 2:12 am

          Those 7 steps are more or less about right (I don't see anything that would obviously cause a problem). Koush's driver package is a roundup of ADB drivers, so you can install it and the Samsung package. However, Samsung should have different ADB drivers for each one of its phones.

          I do not know which of the drivers Windows should be pointed to. I used to use Koush's drivers as a backup to the official ADB package. But now I don't even bother with the official.

          Also, whether or no the driver works for you depends on your phone. I unfortunately don't know which one will work. However, I can say that all of the drivers are compatible -- the problem is that probably only one of them will work. And you have to try each one until the device registers in ADB (I assume you're using the check device command in ADB). I'm unaware of any easier method. However, you might want to try the one with "composite" in the title.

          By the way, I use ADB Minimal instead of the SDK to run ADB:

          It's the easiest method of getting ADB working.

        • Alexyu
          September 11, 2017 at 2:41 am

          I can see why you say that "[y]our thread tracking is awful": There is no "REPLY" button on your latest posting, so I"m 'reply'ing to my own previous comment; hope that works...

          Whoa, whoa! NOW we seem to be getting to the parts I don't understand, so forgive me if I'm talking silly: I still don't understand if ADB is a type of driver, a device, or what -- but, most assuredly, I had no idea that one had to "use a command in ADB" to "register a device" (what device: The phone, the storage, the modem, or what? I had the idea that ADB itself was 'a device', as I said), much less "the check device command" (and I haven't the slightest idea, how, when or why I should "use a command in ADB": I thought one 'pre-installed' the ADB drivers and the Samsung drivers on Windows, and it would then do whatever was necessary to install the connection to an Android phone... :-(

          More: If we're talking about using the Koush 'universal' ADB driver, but now you said you "use ADB Minimal instead of the SDK to run ADB", I'm even more confused: What SDK, what's "ADB Minimal ", and why are you using it instead of the Universal ADB??

          And more: You said that "probably only one of the[e (Samsung?) drivers] will work, and [I] have to try each one until the device registers in ADB"; I thought the phone devices registered in Windows Device Management, not ADB (I assumed ADB itself did, too; is that quite wrong?). I know Win7 can try all the drivers in a (sub)directory it's pointed to, to see if any are compatible with the device it's currently trying to install, but in XP you have to try them all by yourself (I remember that, when installing a Sony-Ericsson phone in the past, thee were 5 or 6 drivers to install until Windows was satisfied) -- but, since that process is automatic, and there are no "composite" in the names of any of the drivers listed, what ARE you talking about?

          Sorry for so many ineptly formed queries, but maybe they help indicate the depth of the doubts I'm struggling through.

  7. Raphael Awoseyin
    August 19, 2017 at 11:19 pm

    I have tried everything, including your proposal, to get adb to "see" my LG Stylo 2 Plus (K535T) running Android 7.0 in recovery mode to no avail. If I just plug the device to my Windows 10 and I type

    adb devices

    the device is listed.
    But if I now reboot into recovery mode, that's it: ADB would no longer see it, but fastboot does. That is,

    adb devices

    does not list any device, but

    fastboot devices

    lists the device.

    I would appreciate any help.

    • hikaru
      September 10, 2017 at 1:53 pm

      same with me here please anyone help

      • Kannon Yamada
        September 10, 2017 at 5:47 pm

        I just responded to the original question. Recheck the thread to see it.

    • hikaru
      September 10, 2017 at 1:59 pm

      anyway, have you found a way to fix it?

    • Kannon Yamada
      September 10, 2017 at 5:47 pm

      I'm not sure what I'm just now getting notification of this message. I'm sorry for not getting back to you earlier.

      More or less, your phone has a mainstream SoC. That means that the trick is getting recognized by Windows. Windows does not always automatically choose the correct driver package. If you don't get ADB after running through the steps in this article, you should try to manually pick the right driver package after installing the Universal Driver executable.

      I've found that there are normally three or four available drivers that are compatible. Try each of these and see if ADB works.

      • hikaru
        September 10, 2017 at 7:24 pm

        Ah, thanks anyway

        • Kannon Yamada
          September 10, 2017 at 10:20 pm

          Let me restate the question: Are you having problems with Fastboot running instead of ADB inside the recovery environment? Fastboot is an alternative to the recovery. FB IIRC uses a minimal set of drivers and I don't think it exactly replicates ADB.

          But more or less, if you check devices using ADB and no device shows up, then the chances are that Windows is not loading the right ADB drivers.

  8. new 2017 tablets}
    March 1, 2017 at 2:48 am

    I was actually at CES this year in Vegas and had the chance to check out a ton of awesome producs, I'm super excited about Samsung new 2017 tablets I'm always up on all the newest hottest tech stuff that is coming out! Thanks for the read and the comment! I look forward to your next article.


  9. Vineet Arora
    December 14, 2016 at 8:57 pm

    Thanks a Ton man, I'd been trying to solve this issue since past 10 days, but your compilation just solved the issue within seconds,

    • Kannon Yamada
      December 14, 2016 at 9:38 pm

      I've been there. It took a long time to get the steps completely right. Glad it helped you!

  10. Beatrice
    December 9, 2016 at 6:03 pm

    Hi! I've just switched from my old Samsung Galacy Trend Plus to a new Lenovo Vibe B... Unfortunately I've tried many solutions, including yours, and installing different Lenovo official apps like LeTools (which i really didn't figured out if it really does something) LenovoServiceBridge, and some strange assistant in chinese. No result at all! I really need to activate ADB in order to check my apps from Android Studio on a real phone. (I intend to do the project to finish university in Android too) Do you have any other solution for this? At least for installing an app created by me on the phone?

    • Kannon Y
      December 9, 2016 at 10:20 pm

      I have further refined some of the steps in this tutorial. I'll try to edit them in right now. Can I ask what happens when you go into Device Manager and change the drivers associated with your device? What kind of drivers do you see available?

    • Kannon Y
      December 9, 2016 at 10:50 pm

      I'm sorry about that. There are a few things that I didn't mention in the article. First, you must have ADB enabled on your device before any of these steps will work. But the title was "ADB not working" so I assumed everyone have already enabled ADB. (I'm pretty sure you have enabled this.)

      Second, if you manually change drivers, it would be helpful to know what kind of driver options showed up. If I have read the specs correctly, your phone should use MT6735M ADB drivers:

      But before you install those, please let me know what kind of driver options show up when you manually try to change drivers.

  11. robert Romero
    October 26, 2016 at 7:37 pm

    THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!! I was googling like crazy for hours trying to find a solution to this problem. Yours is the ONLY one that worked!!

    • Kannon Yamada
      October 26, 2016 at 7:48 pm

      Thanks for letting me know it worked for your Robert!

      The real secret sauce is the universal ADB driver package. I believe there are several now available. In the future, if you have a device that just doesn't work over ADB, Google around for some alternative universal driver packages.

  12. Martin Clark
    September 17, 2016 at 2:10 pm

    On Windows 10, a doogee X5Max (Android 6) can be accessed by USB, with a lot of hammering between charging and MTP. So far, Nexus 5X (Android 7) doesn't work. Nothing wrong with the cable, as ADB and Fastboot were used to flash the standard images. It's a dumb Windows and dumb Google thing.

  13. Flemming Knudsen
    September 6, 2016 at 9:17 am

    On my Windows 10 PC I don't have the checkbox to delete the driver software for this device. Windows insists that the Windows driver is the correct driver

  14. Robert
    September 2, 2016 at 5:50 pm

    I am getting so pissed off at this that I am seriously about ready to go all Office Space on the damn thing.

    I have a Note 4, have been able to view and transfer files up until a couple hours ago. No new updates, no new anything. All of a sudden, either the files/folders simply do not appear in Windows 10 File Explorer, or only some of the do, or I get weird icons that look like a hard drive with a blue four-square Windows logo. And no matter how it displays, I can't get to the files I used to be able to get to.

    The steps above do not work. At all. I've done everything, from every site I could find, and not a goddamn thing has worked.

    I hate hate hate hate hate hate hate this piece of shit!!!

    • Tina Sieber
      September 7, 2016 at 9:06 am

      That really sucks, Robert. You probably tried this, but just in case you didn't, please do: Reboot Windows, reboot Android, check the cable. Works wonders. Sometimes. Good luck!

      If you found a fix in the meantime, please give us a quick update what worked for you. Thank you!

  15. JPB
    September 1, 2016 at 4:00 pm

    I am Desperatly trying to Install this driver BUT Win 7 64bit sias it cannot install as its not 64bit driver, I can only see MTP and WPD drivers even if I un-select Compatible Drives, with the Microsoft / LGE driver dominant , I have a LG G3 Device AKA LG-D855 with Android 5 L 21 In Debug mode.

    The Android SDK Driver also sais "It is Not Compatible" Like the Koush’s Universal ADB Driver, does the same with a Qualcomm MSM8974AC Snapdragon 801 Chipset.

    • Tina Sieber
      September 7, 2016 at 9:09 am

      Did you try to disable Driver Signature Enforcement before installing the driver?

      I described the process in this article with a screenshot:

      "Windows 10: Press the keyboard shortcut Windows key + I to open the Settings menu, then go to Update and Security > Recovery. Under Advanced Startup, click Restart Now.

      On the reboot screen, choose Troubleshoot > Advanced options > Startup Settings > Restart. You’ll find yourself on the Startup Settings screen. Here, choose option number 7: Disabled driver signature enforcement."

      Good luck!

  16. Eyal Kattan
    June 11, 2016 at 6:08 am


    Tried to follow the steps to the letter but my W10 keeps installing the regular Samsung Mobile Composite Device driver automatically (no unidentified device)

    Any idea what am I missing?



  17. Jon
    June 7, 2016 at 4:25 pm

    Thanks! This finally solved my problem... I had a ton of ADB drivers/Samsung Drivers, etc loaded that must have been conflicting with each other and this article finally solved my issue with connecting my S7 Edge with the Universal ADB Driver.

    • Kannon Yamada
      June 8, 2016 at 12:51 am

      Thanks for letting me know Jon! I'm glad it worked out.

  18. Bill
    May 16, 2016 at 10:45 pm

    I've gone round and round with this for two days trying different drivers for my Kycera HydroAir C6745

    Nothing works, even the drivers off of Kyocera's site, although they don't list that particular phone all the packages seem to be the same for similar phones.

    My cable is good... If i choose to connect as a media device I can transfer files between my PC an the phone and other phones at will. I'm trying to use a particular program "MyPhoneExplorer" and it actually works via WIFI so the program doesn't seem to be the issue. When connecting via USB I get a "no USB device connected" error message on this program only.

    I have debugging enabled in the developer options and have restarted both the phone and the computer multiple times after making changes, uninstalling/reinstalling different drivers (when they will actually install) etc.

    Koush's universal driver will not complete installation... I get an error that a program couldn't complete and the installer backs out. I found an earlier version of the same .msi package that is about half the size and it installs but doesn't work.

    Attempting to install the drivers from the GitHuh master package manually gives "this driver doesn't apply to your device" (or words to that effect) no matter which option I choose.

    I have used USBDeview multiple times to uninstall any drivers that look remotely like Android as you describe, even those that install every time I connect the phone via USB.

    Many of the drivers I've tried look to be the same as the one in the master package on GitHub (from the link given) and again, that particular .msi installation will not complete, although a couple of other supposed universal packages.installers have completed with no help.

    I'm running the latest XP and service pack and have experience with these kinds of issues, installing drivers, troubleshooting software installation and issues, etc.... although android is fairly new to me I have SOME experience there as well.

    I do have the Android SDK installed and saw something about a driver there and am about to locate that one but I expect it will not work either and that I'm doing something else wrong or am missing a basic step somewhere, although I've rechecked every step multiple times.... as is generally the case when I have this much trouble and make this much effort in a mostly continuous session.

    I'm stumped.

    • Kannon Yamada
      May 16, 2016 at 11:32 pm

      Can I ask what version of Android your phone has installed?

      Do you get any notifications once you connect your phone to the computer? For example, you might get the option to connect via MTP (media transfer protocol) or another option. Some phones do not initiate an ADB capable connection by default. They load MTP or something similar. The trick is that some phones can connect only over the photo transfer protocol. It doesn't make any sense, but that might solve your problem.

      The concern here, though, is that Koush's driver won't install. I recommend restarting your computer in safe mode and reattempting installation of those drivers. Sometimes the issue can be caused by antivirus software or malware.

      • Bill
        May 17, 2016 at 12:01 am

        Thanks so much foe getting back to me so soon!

        Ah, I didn't turn off my antivirus when installing this version of Koush’s driver although I did with the other one. I think I'll do that before proceeding.

        Android version is 5.1.1

        Processor is Qualcomm MSM8916

        Software is 1.01AT

        Hardware is 1010

        Baseband is a long number and I'll beat it in if you need it as is the Kernel

        Build number is LMY 47V

        I have several options to connect and mostly have tried the suggested "charge only: option however I've also tried "media device (MTP)" (which allows me to transfer files between PC and phone)

        I haven't tried as a "picture device (PIP)" except once so maybe I'll try it again.

        Note that the Kyocera drivers when installed give options to open using several MS office programs and printer options but I deleted that driver from the PC.

        Note also that USB tethering to use as a mobile hotspot also works as normal.

        I do have several USB cables that are compatible and may try them however data seems to work other than for this particular program so a cable issue seems unlikely.

        I'm going to disable the AV and make another attempt to install the driver via the .msi package and I'll get back to you.

        One thing that has me stumped is when attempting to manually install the drivers using different methods I get a "not compatible with you device" message and it refuses to install. Seems like I saw something in my travels the last couple of days about modifying the driver to list a particular device )I'm assuming with notepad" but that's beyond my scope unless it's as simple as editing an .ini file or something similar.... Just to give an idea of my level of capability, I can do basic scripts or charge obvious values as well as changing very basic settings in the registry (very cautiously, of course).

        • Kannon Yamada
          May 17, 2016 at 12:27 am

          There is a good chance that XP is causing the issue. It may be that Koush no longer supports XP. Although last I heard, it did support it.

          Regarding manually editing an .INI file -- I do not know about this method. It's the first I've heard of it for ADB drivers, although it is a common method that people use to get incompatible drivers working with several Adobe products.

        • Bill
          May 17, 2016 at 4:35 am

          I had a long reply typed out with a bunch of relevant details but the captcha screwed up and I lost the whole thing.

          Condensed version:

          With the A V disabled there is still no help. ... the installed nearly completed and then backed out as before saying a program failed to complete.

          USBDeview confirmed nothing was installed

          I reinstalled the Kyocera package from their site and USBDeview confirms there are drivers including an ADB driver (and shows it to be "vendore specific" as expected) but it still does not work.

          Device Manager shows a problem "device not working correctly" however attempting to reinstall by pointing at the Kyocera driver doesn't work as it's an installer and there is no access to install manually and attempting to install any of the raw packages (.inf file and .dll and .cat as raw files) as is normal shows a "not relevant to your device" error.

          I read something in the last couple of days about a driver being installed but to open the win 32 file and do some pointing or something so I'll have to retrace to find that article.

          I had other relevant info to report but lost it due to the captcha issue.

          I'll attempt to post this and then I'm going to take a break from this problem for a while to tend to other matters but I'm very curious as to what the solution turns out to be as I do believe this to be solvable given the totality of the relevant info.

          In the absence of anyone giving promising ideas to pursue now in reply, I'll get back to you when/if I figure it out when I return to it in a while.

          thanks for the help...

        • Kannon Yamada
          May 17, 2016 at 12:37 pm

          I'm sorry about that. The Captcha system is kind of hard to see. I've lost many a comment to it as well.

          ADB basically sucks. It requires that multiple processes, hardware, and drivers function properly. If any one of the links in the chain is weak, the whole chain won't hold up. That's definitely what's happening right now. At least one component is not properly configured. Changing any individual component might break additional ADB requirements, further complicating issues. It's extremely difficult to troubleshoot. At this point, I suggest borrowing a friend's laptop or desktop and seeing if you can somehow get ADB working on their system.

          Also, thank you for the additional details. My best guess is that XP is somehow causing the problem. However, if XP is NOT causing the issue, it may simply be a driver issue. Your particular system-on-a-chip (after Googling) is the Snapdragon 415. ADB drivers are based on the chip, not so much on the phone itself. Although that is not a hard rule. Sometimes ADB drivers work across different devices and sometimes they do not. When they do work they are always based on the same SoC.

          I just read that Snapdragon 415 doesn't have a native method of booting into the eMMC module. I find this hard to believe because it would mean the Snapdragon 415 is not reachable through ADB.

          I found an XDA post on the Kyocera HydroAir which states that a USB driver does not exist. The poster put together his own USB driver (I'm assuming he also means ADB) but it requires manual installation:

          That is kind of dangerous to do and can brick your computer. But if you are desperate and know how to backup your system (or remove a bad from Safe Mode) you might want to give it a try.

          I'm having trouble wrapping my head around the possibility that Kyocera didn't release ADB drivers for this device. It just doesn't seem possible.

        • Bill
          May 17, 2016 at 6:39 pm


          After trying all of the drivers on Kyocera's site last night I gave up until their tech support was available via live chat this morning. Chatting with two different agents it was obvious they would be no help. So...

          ...I retraced my steps and found the tutorial on the tracerplus (whatever that is) webpage entitled "Customize ADB driver for your Android device".

          (I'd give the URL but don't know if it's allowed however a search on the term or similar terms should find it)

          Followed the steps which show how to modify the generic Google Android ADB driver to recognize you device.
          It seems intimidating but basically you just connect your device (in my case the Kyocera phone) and look for the alert in Device Manager, and copy the hardware ID in the properties from the dropdown box, then add those values in the same format as what is already in the .inf file that comes with the driver.

          My hardware IDs listed were:



          I simply added this in the .inf file as a new devicein both the 32 bit and 64 bit sections of the driver .inf file:

          ;Kyocera Hydro Air
          %SingleAdbInterface% = USB_Install, USB\VID_0482&PID_0a6a
          %CompositeAdbInterface% = USB_Install, USB\VID_0482&PID_0a6a&MI_01
          %SingleAdbInterface% = USB_Install, USB\VID_0482&PID_0a6a&Rev_0100
          %CompositeAdbInterface% = USB_Install, USB\VID_0482&PID_0a6a&MI_01

          I installed the driver manually, plugged in my phone and opened "MyPhoneExplorer" and chose "connect". the phone gave a dialog asking if I wanted to allow USB debugging from this computer this time or always and I chose "always".

          The program recognized the phone and now works over the USB connection.

          Note that I simply added those values to the .inf file in the driver package and left it in the folder with the other files (.cat files and such). The only thing I did was add those values as per the tutorial.

        • Bill
          May 17, 2016 at 6:44 pm

          Also note that due to formatting on the page my example isn't exactly as is in the file however when you look at the Google .inf file you'll see the proper format.

  19. Akshay
    March 1, 2016 at 4:01 am


    When i connect my Lenovo A6000 to laptop with windows 10 it is showing exclamation mark in device manager under Other Devices. But it is working fine when i connect to laptop with windows 7.
    Same cable, same mobile.
    From cmd when i run >adb devices it is not listing the devices.

    Please let me know what needs to be done.

    Thanks in advance.

  20. Anonymous
    February 1, 2016 at 2:42 pm

    here just a hardware id of android is to be place on android .inf file thats it..

  21. UTMX
    January 18, 2016 at 1:19 pm

    Yes i installed koush's universal adb driver and i restarted my pc after that i connected my phone via usb and opened device manager and i saw a exclamation marked device under other devices named as adb interface then i selected update driver
    1st i selected for windows to automatically search for drivers it said windows did not find a driver for your hardware
    2nd attempt i selected let me pick a device driver from the list but not a single one worked
    3rd attempt i selected the directory c:program files (x86)/clockworkmod/universal adb driver it said windows did not find a driver for your hardware
    4th attempt i selected the directory c: only instead of the full path it said windows found the driver named adb composit device driver but encountered a problem while updating the driver it said that file not specified
    My phone specs
    Brand lava
    Model iris alfa l
    Hardware media tek mt 6582
    Kernel architecture armv7I
    Android 5.0
    My pc win 8.1 x64
    Still looking forward for ur help

    • Kannon Yamada
      January 19, 2016 at 2:23 am

      The ADB drivers are SoC dependent. Your phone uses a MediaTek 6582, so you might be able to find ADB drivers for that particular SoC. I saw ADB drivers for the Lava Iris Alfa I around, but I couldn't be sure these weren't malware. There's an XDA thread where they discuss ADB drivers for that particular chip -- you might want to read about it here:

  22. UTMX
    January 14, 2016 at 4:16 pm

    When i try to install the driver manually it says Windows found the driver but encountered a problem while updating the driver. My kind request for help and a reply ASAP

    • Kannon Yamada
      January 14, 2016 at 4:47 pm

      Have you installed Koush's universal ADB driver? Try restarting your computer and then manually selecting the driver again. If that fails, can you specify your device?

  23. gbsr
    December 25, 2015 at 8:45 am

    Windows says it can't find the driver, even after installing Universal ADB and pointing it to the right directory.

    • Kannon Yamada
      December 27, 2015 at 5:30 pm

      Have you tried manually selecting the driver, rather than letting Windows automatically selecting it?

      • gbsr
        December 28, 2015 at 7:31 am

        After uninstalling all drivers and re-installing them, it turns out that why it couldn't find it properly after (re)install was because I had a USB-cable that only carried current, not data. Or, in my case, I had 3 of them.

        Eventually got a hold of a cable that carried data and the driver installed properly.
        Thanks for the article, helped a lot :)

        • Kannon Yamada
          December 28, 2015 at 5:21 pm

          Argh. I'm sorry about that. I should mention the first step is making sure the port and cable work properly. Charging cables are among the most common cause of ADB failure.

  24. Dhaval Soneji
    December 12, 2015 at 9:54 pm


    • Ivan de la Jara
      March 25, 2016 at 11:10 pm

      Every single OS need drivers to manage peripherals...

  25. Evgeny
    November 29, 2015 at 6:12 pm

    Windows 10 + Xiomi Redmi Note 2 - unsuccessfull.

  26. Shashi
    November 28, 2015 at 7:31 pm

    One plus one and Windows 10.. this method doesnt seem to work.

  27. FX Bayu Anggara
    November 13, 2015 at 6:40 am

    Thank you very much, works with HTC phone in WIndows 10

  28. Anonymous
    November 2, 2015 at 10:18 pm

    After fighting with win 10 and trying to install the marshmallow ota update, I took your advice and installed Koushs universal usb.
    I finally got it installed and it's booting up now.
    Thank you so much

    • Kannon Yamada
      November 3, 2015 at 12:31 pm

      Thanks for letting me know! I haven't tried this method yet on Windows 10. There's not a lot of driver management differences between the two operating systems, but the more people who report success, the better. Enjoy Marshmallow. It made a big difference on my Nexus 9.

  29. Anonymous
    October 3, 2015 at 1:06 pm

    Well it seems this method doesn't work on Sony Xperia M4 Aqua (android 5.0) and using PC with Windows 10.

    My smartphone shows up in device manager under "Portable Devices" as "Xperia M4 Aqua".
    I uninstalled drivers, deleted entries with usb deview, but when I plug in my device PC automatically installs drivers.
    I disabled automatic driver installation from Windows Update, but that seems doesn't help as it still installs drivers.
    P.S. And by the way - in the first step when "Confirm Device Uninstall" dialog box appears I don't have an option to check "Delete the driver software for this device".

  30. Anonymous
    September 27, 2015 at 5:19 pm

    My Samsung I8552 was debugged well on Windows 7 using OEM USB driver from Samsung. On Windows 10, I try many things with no success included your instructions :(

  31. Anonymous
    September 20, 2015 at 5:35 am

    Thank you! Worked perfectly, where as every QBKing77 video that I've used in the past before moving to Windows 10 no longer proved effective, and with all the "Download this, download that."

    That universal driver and manual installation FINALLY got my cmd to see my adb device sideload.


    • Kannon Yamada
      September 21, 2015 at 11:18 pm

      You're very welcome. Koush's universal driver really saved the day.

  32. Anonymous
    September 14, 2015 at 4:40 pm

    Wow thanks. I was a bit sceptic but it worked like a charm!

    • Kannon Yamada
      September 15, 2015 at 12:34 am

      Thanks for the reply Hans! Enjoy ADB!

  33. Anonymous
    August 31, 2015 at 12:52 pm

    i downloaded asus driver asus android adb interface but i am getting exclamation mark on android adb interface and it says device cannot start code 10 error please help me

    • Kannon Yamada
      August 31, 2015 at 3:36 pm

      It may have been the wrong driver. The ADB driver has more to do with the SoC inside of the phone than the name of it. Sometimes manufacturers stick different SoCs into the same model of phone (mainly Samsung). Have you tried uninstalling the driver and reinstalling? Or perhaps finding the ADB drivers direct from your manufacturer?

  34. Anonymous
    August 4, 2015 at 1:55 pm

    Hey kannon , I did all the steps( not the 1st one for following reason) but after removing all other drivers as instructed and installing the universal adb driver no drivers are loading automatically installing when I plug in usb. Moreover I cannot even update it manually from device manager because there is no device or android phone or LG option or any adb option to select. What do I do now? See the image as to know what it looks like [Broken URL Removed]

    • Kannon Yamada
      August 31, 2015 at 3:42 pm

      I'm sorry for the late reply Yash. It appears that we are not getting notifications of comments on a regular basis.

      You probably already fixed the problem on your own, but have you tried restarting the computer? Attached hardware should automatically be detected by the OS. If it doesn't have the driver (or can't download it), the device will show up as undetected in Device Manager.

      If no device is detecting that's an issue with the operating system. Here's some tips on fixing the issue:

  35. Anonymous
    July 22, 2015 at 9:27 pm

    I cannot not enable usb debugging, because my phone won't boot past the loading screen.

    • Anonymous
      July 22, 2015 at 9:29 pm

      I have a Moto G btw.

    • Kannon Yamada
      July 22, 2015 at 9:31 pm,6720,9050

      You have to factory rest your phone, if your phone can't be booted at all.

      • Anonymous
        July 22, 2015 at 10:13 pm

        I did that already. Am I screwed?

        • Kannon Yamada
          July 22, 2015 at 10:49 pm

          People have recovered from situations like this (restore from backup failed). However, it sounds as if you have already modified your phone using a custom ROM. Is this true? In that case, you are best served asking this question from within the thread on XDA where they discuss the ROM.

        • Anonymous
          July 22, 2015 at 10:56 pm

          No. But am trying to reinstall the OS with a ROM, am assuming that is what I need to do. I will ask on the XDA thread.

  36. Anonymous
    June 17, 2015 at 6:10 pm

    This post saved my day..thank you so much :)

    • Kannon Yamada
      September 15, 2015 at 12:35 am

      You're very welcome Roslyn! Thanks for letting me know it worked!

  37. Rehan
    May 24, 2015 at 9:11 pm

    Hi Kannon,

    I have Yu Yureka android phone( lollypop version).. I am facing a problem in connecting my device as removable disk. Whenever i connect my phone to PC it shows under portable device. Actually i have my data i want to recover it back but recovery software doesn't recognize my phone under portable device.. Please help me out to connect my phone as a removable disk not under portable device.

    • Kannon Y
      May 24, 2015 at 9:32 pm

      I'm assuming you need to connect your device as ADB and not as a media device in order to run the recovery software (this is always the case).

      Android uses two different sets of drivers for media devices and ADB devices. If your device is getting detected as MTB then it's almost certainly being caused by your device not having ADB debugging enabled. For most Lollipop phones, to enable ADB debugging, you have to enable Developer Mode. To enable Developer Mode, you must go to Settings --> About Phone --> start tapping on "Build number" (which is located at the bottom of the menu). Tapping on it a bunch of times will eventually enable Developer Mode, which is a new category which shows up in your Settings menu.

      Then go back to Settings, locate the new option "Developer" (something or other) and then enable USB Debugging Mode (or something that sounds similar). You can then get your device detected using ADB.

  38. sai karthikeya josyula
    May 11, 2015 at 9:17 am

    my lenovo a6000 ph got bricked and struked up at lenovo logo...iam note able enter in boot menu by presiing 3 buttons simultaniously...and also my ph is not getting detected by adb ...please help me..i have a backup of my rom with me...plz help me as soon as possible.....waiting for ur reply

    • Kannon Y
      May 17, 2015 at 2:14 am

      Your phone isn't getting detected by ADB because you likely cannot enable ADB from within settings -- because your device is bricked. Have you attempted a reset from the bootloader? If you're unmodified, that is.

    • Anonymous
      June 19, 2015 at 5:41 pm

      Hi Sai,
      How did you managed to resolved the mobile. I do have the same problem. Let me have your guidance.

  39. Thomas Bry
    May 1, 2015 at 8:04 pm

    Thank you very much for your help, i have finally did configure the driver for my huawei tablet, now i just need to update the OS

  40. Sanju
    April 7, 2015 at 2:24 pm u by any chance know how to by pass the Allow USB debugging RSA fingerprint option that pops up on the phone when you connect it to a computer. I cannot accept on the phone since my screen is broken.Any ideas please?

    • Kannon Y
      April 9, 2015 at 4:03 am

      Can you use an OTG mouse? If you have an OTG adapter cable I believe you can convert any USB mouse (or almost any) into an Android mouse.

      Unfortunately you won't be able to pair a Bluetooth mouse because the broken touchscreen will prevent authentication.

      Most devices have OTG capabilities, but a rare few do not.

  41. Tomer
    March 30, 2015 at 8:25 am

    Actually I saw it's GT-i9100T and not GT-i9100

    I've submitted my question with all the information needed. Thanks a lot!

  42. Tomer
    March 22, 2015 at 6:18 am

    GT-I9100, and I have CM11 installed

    • Kannon Y
      March 29, 2015 at 3:15 am

      That's definitely not an exotic driver. Can you submit your question to ?

      I'll do my best to find the answer for this one. Please include as many details as possible. The more details, the more likely it'll get published.

  43. Tomer
    March 20, 2015 at 8:48 am

    I'm trying to flash a kernel via Odin 3.7, but after I press START it writes 'Can't open the serial (COM)'.
    Iv'e tried your method of reinstalling the driver but it didn't solve the problem.
    Do you have any idea what else sould I try?


    • Kannon Y
      March 21, 2015 at 8:23 pm

      You can't simultaneously run Kies and get ADB at the same time.

      You have to set Kies to not run automatically.

    • Tomer
      March 22, 2015 at 12:07 am

      I didn't have Kies installed, only the universal ADB drivers.

      When I DID install Kies, it didn't recognize my device and I couldn't cancel this option (although the computer did recognize my device as MTP).

    • Kannon Y
      March 22, 2015 at 2:26 am

      What device do you have? It could be a matter of an exotic driver.

  44. Muad
    March 17, 2015 at 2:55 pm

    You saved my day !! Thanks so much

  45. Jacold
    March 16, 2015 at 11:34 pm

    On Moto G 2nd gen this not works for me (but this is funny, because on laptop works at default drivers). Factory reset don't remove ringtone bug, but converting mp3 to ogg and throwing this file in Ringtones folder in internal memory works.

    Anyway, thanks for tutorial.

    • Kannon Y
      March 17, 2015 at 12:44 am

      Sorry it didn't work. Sometimes you might need to disable media storage (MTP). It will show up in your context menu on the Android device. It goes without saying that you will also need to enable ADB in Android for it to work.

  46. Ravi Ram
    March 16, 2015 at 1:14 pm

    Awesome! Thanks for taking time to post this. I had the same issue when I connected my Samsung galaxy s4 mini (running kitkat) and your solution fixed it!.

    Also disappointed on why google has not handled this issue gracefully.

  47. Roy Youdale
    February 23, 2015 at 11:52 pm

    Thank you so much for your simple, clear and above all effective advice. This works!
    Best wishes,

  48. June Real
    February 22, 2015 at 3:08 am

    Installing Koush’s Universal ADB Driver resolved the issue. Thank you so much.

  49. moto_modx
    February 18, 2015 at 12:08 pm

    Never mind, I am able to get it installed via android sdk google driver, and adding the device id of my phone in to generic driver. That worked.
    the website that you posted does not list that phone itself.


  50. moto__modx
    February 17, 2015 at 6:23 pm


    I tried all methods and drivers on web. But I never got ADB driver for TCL ALCATEL J636D+. Its even not there on manufacturers website. Dont know how to make it work.

    Suggest if you have an idea.

    • Kannon Y
      February 17, 2015 at 7:00 pm

      The method outlined in this article should work for you. However, the USB drivers for Windows can be found here:

      You have a Qualcomm chipset.

      There's always the possibility that your version of Windows does not support the drivers. That's rarely the case, however.

  51. Abhishek Dev
    February 1, 2015 at 7:44 am

    Bro, it didn't work for me... My phone is Android One - Micromax AQ4501..

  52. Iain Toward
    January 7, 2015 at 9:28 am

    I think the problem I have with my tablet is that it is one of the cheaper Chinese ones and they don't come with the normal configuration settings like my galaxy S4. The tablets are now selling in the UK for £60 and come with 32mb ram and 4.42 kit kat. You cant argue at the price or quality but its impossible to find the manufacturer or get driver updates. File transfer has to be done via TF SD card which is OK really. Its just minor problems which give me a reason to moan. lol. The solution will be out there, its just difficult to find. Thanks for your help and info.

  53. Matty
    January 1, 2015 at 6:41 pm

    I am completely lost on this issue.
    My partners phone (galaxy s3) will connect to laptop no problems... with current configuration.
    My phone, however (samsung galaxy s4), will not.
    I keep getting usb device not recognized.
    Interstingly, I had brief success with playing about with the usb settings.
    *#0808# then selected CP instead of AP.
    This worked fine and allowed the phone to be recognised and I could browse the contents of my . For about 3 minutes, until I opened kies and tried to connect that way.
    Now I'm back to square one with a phone that will not connect to or be recognised by the laptop.
    Interestingly again, my partner can connect with kies and without kies.
    No further tinkering with USB settings on my phone has allowed me to connect.
    Any clues ???

    • Iain Toward
      January 2, 2015 at 12:17 pm

      I had the same problem with my S4 and Windows 8.1. I installed the new Kies 3 and that solved the problem (drivers again) eventually after rebooting both of them. Sometimes Windows recognizes the S4 without opening Kies, sometimes it doesn't, odd. As you can see from my last post, I'm sick of trying to connect androids to Windows 8.1.

    • Kannon Y
      January 2, 2015 at 10:22 pm

      Sometimes the phone or tablet will itself request permission to connect via ADB. This usually involves just checking a box on the Android device. Other times, you will need to disable MTP or media access, which is different from having access via the debug bridge. I don't think you can simultaneously have ADB and media access.

  54. Iain Toward
    January 1, 2015 at 2:19 pm

    I have a tablet running android 4.42 and my PC runs windows 8.1. I connect via usb but windows does not recognise the tablet at all. I've set the debugging option and installed the Koush USB drivers but I have not had the option to use them because the PC will not recognise the tablet. It just runs through a routine of making loads of noises, like its trying to identify the usb source , this goes on for ever but nothing else happens. What can I do. Help!

  55. Vinu
    November 22, 2014 at 10:04 am

    never mind, i got it detected by adb :) when under devices, Google Nexus ADB>update driver>let me pick> usb adb.

    • Kannon Y
      November 25, 2014 at 12:59 am

      Glad you found it. By the way, HTC only just released the official USB drivers for the Nexus 9.

      I have an N9, too. It's super buggy and sometimes suffers from overheating -- but I like it a lot, for some reason.

    • Vinu
      November 27, 2014 at 5:40 am

      I actually write for a tech website, so HTC sent us a Nexus 9 test unit. Yup its fun to use, but it didn't have the latest firmware updates because the N9 being a test unit. The tablet gets hot unnecessarily for any small work. I expected better on the back too.

      Since you got the proper commercial Nexus 9, try the Google updates. I've got lot of feedback the latest updates simmers down the heating issue. And the back could have been better. Ok did you feel any strain on your hand when you started to use it first time in portrait mode, or for prolonged use? This is something i came across and no1 talks abt it.

    • Kannon Y
      November 29, 2014 at 6:59 pm

      That's really great! I had to pay for mine.

      There were a lot of QC problems, aside from serious bugginess with firmware. Voice recognition was spotty with the screen off.

      I suspect that HTC and NVIDIA failed to pay licensing fees for the always-on listening capabilities (Qualcomm and a few software companies dominate voice recognition patents on mobile) and so there's a third or fourth hidden core in the Denver chipset. I'm waiting for the microscoped SoC to get published.

      The update seems to have reduced temps by a small amount. I get 71-72c after browsing and watching video, randomly. Before the temps were in the high 70s. It could just be confirmation bias on my part. I've been using it in low-drain mode and the temps are very reasonable when it underclocks, though.

      I didn't get hand-strain, but it depends on how users hold the thing. One-handed, with fingers wrapping around the back -- major hand-strain. One-handed with fingers on the bezel, no hand-strain. For gaming, two-handed, no strain.

      Here's my review (share yours, too, if you'd like):


  56. Vinu
    November 22, 2014 at 9:52 am

    Hey ive got a Nexus 9, and ive done all the steps mentioned above. Infact Koush USB drivers already existed in my PC, and it even shows Google Nexus ADB Interface under devices, but adb doesn't detect when i hit the adb devices command under adb shell. Any suggestions?

  57. Ankit
    November 21, 2014 at 7:19 pm

    I tried your way in my windows xp sp3 with moto x (2013). but this is not working please help..

    • Kannon Y
      November 25, 2014 at 1:00 am

      Hello Ankit, I would try using the instructions supplied by Vinu, below. If that doesn't work, let me know what you've tried and I'll do my best to help.

  58. ilan
    November 17, 2014 at 3:12 pm

    Kannon - You are a canon. After spending 4 hrs. on this, your enlightening post saved the day. Thanks a million!

    • Kannon Y
      November 25, 2014 at 1:00 am

      Ilan, thank you. I'm glad my post was able to help!

  59. xmnboy
    November 13, 2014 at 2:09 am

    On Windows 8.1 (probably Windows 8, as well) it works better if you use the following procedure after installing the Koush universal driver:

    -- Choose "Browse my computer for driver software" (as shown in blog)
    -- DO NOT locate the driver by pointing to a directory
    -- INSTEAD, choose the second option: "let me pick from a list of device drivers on my computer"
    -- locate the "Android Device" in the list (this is the Koush driver)
    -- wait for the list of "models" to appear, it can take a while to populate
    -- select the first one in the list ("Android Composite ADB Interface")
    -- answer "Yes" to the "Update Driver Warning"

    Now your ADB driver will be installed.

    It doesn't matter which ADB driver you choose from the list because the Windows USB driver for ADB connections is the same for all Android devices, it's just the device IDs that change. By using this procedure you're overriding the device ID matching and just using an ID for another device. In the end, there is only one USB driver binary that works with all your devices.

    You may need to do this again when you connect another Android device (from a different manufacturer) if it has IDs that are not in the Koush driver that you originally installed.

    Likewise, if you had installed the Google or Samsung or some other Android USB device driver for ADB, you could have selected that ADB * driver from the available drivers and it would have worked.

    Took a long time to figure this out, but so glad I did because now I can quickly and reliably add new devices for debug!

    • Kannon Y
      November 13, 2014 at 11:24 pm

      This is my fault and I am very sorry for causing the issue.

      I went ahead and updated the article to reflect this. I should have suggested that users manually locate Koush's drivers AFTER normal means fail.

      I'm glad that you figured it out. And thank you very much for letting me know about the issue.

    • Matt
      February 16, 2015 at 3:19 pm

      This worked for me. Thanks a mill.

  60. Anonymous
    November 10, 2014 at 5:07 am

    Thanks so much for the response. The issue is the drivers don't show up in the list of options and even if I manually browse to the location Windows won't let me select them, saying there are no compatible drivers in that location :/

    • Kannon Y
      November 10, 2014 at 6:00 am

      This would be the only time I've heard of Koush's drivers not working. There are other errors which could cause this, but I can't think of any at the moment.

      Have you tried installing the USB or ADB drivers for your particular device and then manually installing them? What kind of smartphone do you have?

  61. duck888
    November 9, 2014 at 12:15 am

    Thought I left a comment earlier but not seeing it so I'll toss it out again. Having a ton of issues with this and have tried all of the above in addition to countless other things. Pleeeease help!

  62. duck888
    November 8, 2014 at 8:39 pm

    I'm having a very similar issue to another user above. Have been working on it for days, and have diligently tried every step above to a T, along with many other methods. Windows still installs a default driver that does not work, and doesn't allow me to manually select any other drivers. This is driving me crazy, any additional assistance you can offer would be GREATLY appreciated.

    • Kannon Y
      November 10, 2014 at 3:59 am

      Hello Duck888, in this case you would need to manually install the driver.

      Once you install the Koush drivers, they're on your hard drive (and should be the only ones available). If you have taken care of the requirements (like setting USB-debugging to "on" and so on), you would just go to device manager, find the connected device and right clicking on it.

      Then you would go to update driver and browse my computer for drive software.

      Then you would choose "Let me pick from a list of device drivers on my computer".

      You should see a list of compatible drivers which all hail from Koush's driver package. You should be able to install any one of these, but if it doesn't work, just repeat the process.

  63. pmshah
    September 2, 2014 at 3:10 am

    Only time I have had any kind of problems is with Win XP Systems. On win 7 Ultimate I didn't install any drivers at all. I simply switched the Android device , 2 Samsung phones (Android 2.3 and 4.4.4) and Nexus 7 (2012) tablet, to debug mode and then connected them (one at a time) to the PC. Win 7 automatically installed the correct drivers and the external storage was visible for drag and drop.

    So far as I am concerned Samsung's Kies is a major culprit. The newer versions simply wouldn't recognise the older devices !

    • KiesHater
      September 2, 2014 at 2:51 pm

      Do you use something else instead of Kies?

    • Kannon Y
      September 5, 2014 at 2:27 am

      I've always had trouble on all Window systems, but only after connecting several Android devices. I'm told that ADB drivers tend to be poorly designed and oftentimes conflict with one another. But I would guess that Windows XP is a particularly problematic beast! Thanks for the comment!

  64. DonGateley
    August 31, 2014 at 2:45 am

    Thanks, Kannon. No I didn't explicitly delete anything. I relied on the Device Manager context menu.

    I think I fixed it. When I plugged the phone in all I got was an entry in Device Manager under "Other Devices" named "Galaxy Nexus" with a question mark. I used "Update Driver" from the context menu and selected "Browse my computer for driver software" then "Let me pick from a list..." It did some searching and there was an entry for manufacturer "SAMSUNG..." and the model "Samsung Android ADB Interface." Selecting that and hitting Next gave me caution about verification. I hit "Yes" to continue and it installed.

    Now I have my Samsung ADB Interface back. Whew! In the process I seem to have lost the MPT driver under "Portable Devices" but I'll worry about that later.

    Thanks for the response. I got verbose here in case anyone else has the same problem.

  65. DonGateley
    August 31, 2014 at 1:04 am

    Windows 7, Galaxy Nexus. This failed for me in a bad way. After uninstalling and deleting the ADB driver that was there, unplugging the phone, getting rid of the stuff with USBDview, installing the downloaded driver package and plugging in the phone, absolutely nothing happens. No driver installation occurs. Phone says "USB Debugging Connected" but computer doesn't see it.

    I reran the universal driver installer and used it to remove the drivers. Re-installed the stock drivers for my Galaxy Nexus, plugged it in and still no drivers install.

    I now have _no_ ADB drivers. How can I repair this serious loss?

    • Kannon Y
      August 31, 2014 at 1:23 am

      Sorry about the problems. Did you erase the drivers from within the system32 directory or did you use Device Manager to uninstall the driver? I would avoid directly removing drivers from the system32 directory as a small error can cause serious problems.

      You will need to manually install the drivers if it's not working. Koush specifically mentioned that his driver works with the Galaxy Nexus. The driver "update" process (in Windows 8, but also for Windows 7 IIRC) appear in the following order:

      1.) Uninstall driver (from context menu)
      2.) Browse my computer for driver software.
      3.) Let me pick from a list of device drivers on my computer. (NOTE: this option is not particularly visible. Look a little down on the page to find this option).
      4.) Select the device driver you want to install for this hardware.

      Several options will show up here. Some of these are Koush's drivers.

      Some other things to think about: Did you try plugging in your device, going into device manager and uninstalling the driver? You need to tick the box for removing the driver from your system.

      I would also try restarting the computer if Windows 7 fails to pick the device up.

      Hope that helps! Let me know if there's anything else that goes wrong. I'll do my best to help. Good luck.

  66. Sandro
    August 31, 2014 at 12:56 am

    Thank you so much for the article. It's funny that I was having the exact issue with my Samsung Galaxy phone yesterday and spent several hours trying to find a fix - to no avail... I'll try this method tomorrow

  67. DonGateley
    August 30, 2014 at 9:46 pm

    Windows 7. On phone USB plugin the system always installs drivers from "preconfigured driver folders" and if it can't find them it looks to the internet. If you skip that you go back to the "preconfigured" search and never get a chance to manually install Koush's drivers. Whatever it finds it installs and won't let you update to Koush's drivers saying that "The best driver software for your device is already installed."

    Looking at Driver File Details from right clicking on the installed ADB drivers they come from C:windowssystem32 and its DRIVERS subdirectory. Deleting those does no good because the search on plugin always replaces them with something from somewhere that it then considers the "best driver software."

    How do I really install Koush's drivers from "ClockworkModUniversal Adb Driver"? Is there any way to tell the system to stay the hell out of the way and let me install what I want?

  68. Andy
    August 30, 2014 at 7:23 pm

    Thanks a lot. For some reason my Nexus 7 and home PC haven't been on speaking terms lately.

  69. Amrish
    August 30, 2014 at 4:46 pm

    Thank you so much... I was having issues with my Nexus 4 MTP connection. I searched everywhere on net, but none of the solution worked for me. This one worked but remember for MTP you need to disable the USB debugging mode.