ADB No Devices Found

Question

I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed "Android SDK Tools", "Android SDK Platform-tools", and Google USB Driver. I have checked the setting on my Nexus 10 for "Unknown Sources".

When I run "adb devices" from the command terminal, it doesn't list any devices. I attempted to follow this recommendation, because it was identical to a suggestion I had previously found here on Stack Overflow. After following those steps, "adb devices" still returns an empty list and to make it worse, when I connect my Nexus 10 to my PC, Windows doesn't show any folders within the device.

I have undone the steps in that link, along with everything else I have done so far, as well as uninstalling my Nexus 10 from Device Manager and reinstalling it, but I am still not seeing any folders in the device.

Is there anything I am missing to get my device to show up in ADB devices?

What can I do to get Windows to see the folders within the device?

Answer 1

My problem I must enable ADB debugging in charge only mode

Answer 2

Maybe there is something wrong with your usb cable, change a usb cable and try.

Answer 3

If USB Debugging is already enabled but adb devices is hanging, or not responding, try going into the developer settings on the Andriod device, disabling USB Debugging, and then re-enabling it again.

This process can sometimes help a (Windows or other) machine to pick up adb commands again.

Answer 4

I was using a Samsung phone with Android 10. It was detecting earlier but stopped detecting on Windows 10 after I factory data reset the Android 10 phone. Though It was normally detected on Windows 11 PC.

When I dig a little deeper, in android phone settings inside developer options there is a configuration named Default USB Configuration [Settings -> Developer Options -> Default USB Configuration]. When I select that option, There were several options that came and none of them was selected by default.

I tried selecting one option after the other and when I selected the USB Tethering option; than android device started detecting.

Answer 5

Every time this happens to me I need to go into Developer Options on my G6 and set the USB Configuration as "midi"

Answer 6

As well as the usual settings (enable USB debugging) I also had to select Enable OEM unlock in the Developer options.

This supposedly makes the device less secure, but it's your device and you know what you want to do.

Once checked the device behaved as expected and appears in the adb devices list.

You can always reverse all these settings once you're finished.

Answer 7

There could be two reasons why adb devices command is not working for you. Either your phones USB drivers are not installed properly or you have not enabled USB debugging mode.

I created a tool that makes installing USB drivers a one click thing.

1. Just connect your phone in USB debugging mode to PC.

2. Run my tool

It will detect and install drivers specific to your phone and also install the latest ADB & Fastboot binaries with it.

The tool is available at my GitHub Repo

Answer 8

problem : device is not appearing in vscode and ABD interface - no driver found

Solution:

1. Enable USB debugging in mobile.

2. Connect your mobile and laptop using USB cable

3. go to https://developer.android.com/studio/run/win-usb click on the "Click here to download the Google USB Driver ZIP file (ZIP)"

4. go to device manager -> other devices -> right click on ADB device and click update driver software. Select "Browse my computer for Driver Software" Select "Let me pick from list of Device drivers on my computer" double click "show all devices" Click on "Have Disk" option. Select the driver path android-sdk-windows\extras\google\usb_driver .Select android_winusb.inf file select Android ADB interface -> click next Click Yes to install, close the window upon success.

   Now you will see the device appearing in VSCODE.

Answer 9

At first Thanks @rmsyk's post.

For my issue and after long time suffering with Meizu C9 Pro witch require just android ADB drivers (no special drivers) referring to manufacturer and it solved in my Windows 7 PC by the bellow steps.

1. Make Sure to

   • Install latest version of ADB & Fastboot with the needed drivers.
   • Enable Developer options & USB Debugging.
   • Enable Media File Transfer (MTP Mode).

2. Manually replace C:\Users\USERNAME\.android with the folder included here ,Then kill process 'adb.exe' if found from Windows Task Manager and use adb devices and finally my device listed successfully and just confirm the PC as trusted.

Notes:

1. Android Studio was uninstalled in earlier time and also i tried to reinstall but was not a solution at all.
2. Tried adb kill-server & adb start-server but was not a solution too.

Answer 10

The device may not be visible for debugging if it is in MTP mode. Some devices only work in PTP mode (or even in "charging only" mode).

This can be changed in Settings > Developer Options > Networking > Default USB configuration > PTP.

Also, you'll get a notification on your android device asking you for confirmation about USB configuration setting change and to allow it.

Note: You can turn on developer options by following the link below: enable developer options

Answer 11

Here's a new addition to the check-list.

Check that your anti-virus has not blocked/vaulted the adb.exe in platform-tools directory.If you cant find the adb.exe in the SDK "platform-tools" directory, then its likely that it has.

C:\Users\\AppData\Local\Android\Sdk\platform-tools\adb.exe

I use AVG, and it had vaulte dit because it thought it was an IDP.Generic virus. You can add it as an exception to allow it to run, and restore it from the vault.

My symptoms were that android-studio "tools"->Connection Assistant would recognize the usb-device in the list, but an adp restart button would remain grey. As it couldn't find the exe, but it didnt complain, just hung.

Its only when i manually tried to bounce the adp process via the command line , that I saw the adp.exe was missing.

Hopefully this will save someone else a lot of time.

Answer 12

Confirm you have the correct platform SDK tools

For Windows 10, had to manually download the latest platform SDK tools from Android as the version supplied through Visual Studio 2017 EMDK for Xamarin was not sufficient. Everything else except adb.exe devices worked.

https://developer.android.com/studio/releases/platform-tools

After the platform tools were manually downloaded, device showed up regardless of USB configuration (charging, MTP, etc.)

Installing an emulator device at this stage is also helpful to see whether the problem is with adb or your physical device.

List of devices attached
12345D1234      device
emulator-5554   device

Answer 13

If you're at all familiar with Linux use that instead of Windows. On a Raspberry Pi, do

apt-get install android-tools-adb andoid-tools-fastboot

There are no special USB drivers needed, it just works. Android is based on Linux so you're working more in native mode. Many of the problems I see here are Windows problems. osx may have advantages over Windows here too. Adb and fastboot both have man (manual) pages which are accessible from Linux.

Original question: I see no devices in adb when the phone's in fastboot mode, adb and fastboot seem to be mutually exclusive, you can only use one or the other at a time. USB debugging has to be on.

Answer 14

This situation seems to arise with some ADB drivers. I have encountered the same thing with a couple of Google devices and installing the Universal ADB windows driver has fixed it for me every time.

Answer 15

Easy way to install ADB drivers

I always use ADB Driver Installer for installing adb drivers for any mobile. You only need to click on Install button. and all set!

If your device is not listed here, then you can check enable your developer setting, check your USB cable.

Answer 16

I have found a solution for my case.

1. Go to Tools->Layout Inspector.
2. Press Restart button a few times.

I have no idea how it connect with ADB but it works.

Answer 17

If you have enabled Developer Options and USB Debugging for a Nexus, the win-usb supposedly works.

One tell-tale sign whether your driver is right is if it's got ADB in the name in Device Manager.

For my Galaxy line, I had a driver installed, but it wasn't the ADB driver.

For many non-Nexus Androids, the win-usb driver will not work. Instead, you will need to install one of the OEM drivers: https://developer.android.com/studio/run/oem-usb.html

This finally got me an ADB compatible driver, and after switching to PTP adb finally was able to find my device.

Answer 18

I have a Motorola Razr and I was having trouble identifying my device. What I did was:

1 - From the command prompt (as an administrator) -> adb kill-servers

2 - Downloaded Motorola Device Manager here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

3 - I waited until the installation was complete.

4 - From the command prompt (as an administrator) -> adb devices

Answer 19

Also in android studio you can via the SDK manager install the google USB drivers and you' should be set after this.

Answer 20

For my Nexus 6P downloading drivers from Google helped resolved the issue. Here is the URL with documentation. And here you can download the driver itself.

P.S. I saw some people advice to download some drivers from random places on internet. While this might help it's too dangerous in my mind to download unknown drivers from unofficial places. So the one from Google worked well for me :)

Answer 21

To have ADB in MTP mode

If you don't find any ADB device (nothing with exclamation mark) in the device manager (with all developers settings on phone checked), do this:

In Device Manager :

UpdateDriver->Manuel Install->Search on my computer->Select from installed driver list -> then select the one with the word usb in it (not MTP).

Edit: after that, you'll then have 2 or 3 peripheral, one for USB and one for ADB, install adb driver using usual method (see first answers)

Answer 22

There's obviously a ton of different problems that could be causing this (and a ton of different solutions to go along with those problems). So think about all the solutions!

If you've gotten this phone and computer pair to work together before, but they aren't working any more, it might be a specific program on your computer rather than a problem on your phone. Some programs install/use their own adb, and only one of these can connect to your phone at a time. I think this makes a race condition, so sometimes it'll connect fine.

Some programs that run adb:

HTC Sync Manager - uninstall this.

chrome://inspect - lets you view localhost on your phone. Just close the window when you're done with it.

Answer 23

Normally SDB will download the driver in the **android-sdk-windows\extras\google\usb_driver** path

Here are the steps that worked for me:

1. Enable USB debugging.
2. Do to device manager, right click on ADB device and click update driver software.
3. Select "Browse my computer for Driver Software"
4. Select "Let me pick from list of Device drivers on my computer"
5. Click on "Have Disk" option.
6. Select the driver path **android-sdk-windows\extras\google\usb_driver** (path of sdk) 7.Select 1st driver out of list of drivers shown.

And hopefully, it will work.

Answer 24

I still get this once in a while and it usually works if I unplug it and plug it back in a different port. I'm on Linux but had the same thing happen on Windows before.

Answer 25

Make sure to Enable USB debugging in Settings -> Developer options

Also, run "adb devices" after getting into the platform tools folder in the Android SDK (unless you have that folder on your system path already), otherwise the command won't be found.

Answer 26

For Windows, just end all the processes related to Blue stacks or any such emulator if you are using.

Worked for me.

Answer 27

GoTo DeviceManager, then right click on the android device and click uninstall driver. Unplug and plug the device back...then a pop will come on your device while your pc installs the required drivers. Click "allow" on the popup. You can see your device when you type "adb devices" in command prompt.

Answer 28

Have you had an android update recently? I updated to Lollipop and all the sudden I had no adb devices. Boo! I spent awhile trying a few things to no avail. Then I went into my developer options and lo and behold, "USB debugging" had been turned off. Silly Google. After turning it back on, it immediately showed up and I'm back in business!

Answer 29

You have to download the drivers from the SDK manager (extras → Google USB Driver)

Then you have to install the USB driver in Windows (it works for me in Windows 8.1):

(Copy and paste from http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver:)

1. Connect your Android-powered device to your computer's USB port.
2. Right-click on "Computer" from your desktop or Windows Explorer, and select "Manage".
3. Select "Devices" in the left pane.
4. Locate and expand "Other device" in the right pane.
5. Right-click the device name (such as Nexus S) and select "Update Driver Software." This will launch the "Hardware Update Wizard".
6. Select "Browse my computer for driver software" and click "Next." Click "Browse" and locate the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
7. Click "Next" to install the driver.

Answer 30

Installing Samsung Kies and using their tool to reinstall device drivers, is what finally worked for me with my Galaxy S3 and Tab S 8.4