Develop Reference

"adb devices" command returns no devices

I am just getting started in Android development, and am trying to get Eclipse (running on Windows 7) to recognise my phone so that I can use it for debugging. However, my phone does not seem to be recongised by Eclipse or by running "adb devices" from a command line.
Here's what I've tried:
I've tried both MTP (media device) and PTP (camera) transfer modes (similar questions on Stack Overflow have been resolved by using PTP).
I've ensured that USB debugging is turned on in my phone's settings.
I've manually installed a driver in Device Manager, by choosing "Update Driver Software" and selecting the .inf file in sdk\extras\google\usb_driver (which I had to modify by hand to include my device).
I've tried a Nexus 4 phone, a Nexus 7 tablet, and a Motorola Moto G phone. Behaviour is identical for all three devices.
I've tried the "Universal ADB driver", in case it behaves differently to the Google driver, but it doesn't behave any differently.
I've rebooted, I've reinstalled drivers, I've tried adb kill-server followed by adb start-server, etc.
No matter what combinations of the above I try, "adb devices" lists nothing. When I look in the Windows Device Manager, I can see "Android Composite ADB Interface" listed under the "Android Device" node, so I believe I have installed the driver correctly. I am logged in as an Administrator, so it's not a permissions thing either. I've tried every answer to every single similar question on Stack Overflow, but nothing works. I've been pulling my hair out all day and am close to running out of hair... any ideas appreciated.
EDIT: It just occurred to me what could be causing this. I am running 64-bit Windows 7, but 32-bit Java. Because I have 32-bit Java installed on my PC, I installed the 32-bit SDK. Would that explain this behaviour? Should I be running 64-bit Java? The only reason why I didn't is because 32-bit Java is installed by my company's group policy...
EDIT2: I have now noticed that when I plug an Android device in, and look at its Device ID in Device Manager, the device ID does not end in "&MI_01". When I plug the device into another Windows 7 PC, the device ID does end in "&MI_01". I believe this is why "adb devices" is not able to detect the device. Any idea why one PC would see a different device ID to another, with the only difference being the "&MI_01"?

Did you install your phone USB-driver?
and can you check it on device manager is installed or not? you can download your usb driver from yur phone company website.
After you install your phone usb driver , I think the problem is solved

I think the main reason is because the computer does not recognize your phone as below 1 device used to debug code, even usb device.
You can try to do the following:
- Turn up the window update
- Uninstall driver for usb connection from your phone to your computer
- Go to the homepage of the mobile device, download driver for usb connection to the computer and then reinstall the driver

Try Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Download
After downloading extract .rar file into a folder.
Go to Device Manager, right click on Android phone and click to update driver. On next screen , give path of extracted folder and install it.
You can install with msi file also. Download .msi

Finally found the answer. I was missing a file called usb.inf from C:\Windows\inf. Not sure how on earth files just go missing from yours Windows directory...

Android Device not recognized by adb

My Android device isn't recognized by eclipse nor adb anymore.
My OS is Windows 7 64-bit, and I'm using a Nexus 4 with Stock Android 4.4.2.
Here are some details on the problem:
Yesterday I could run Android Projects from eclipse on my device with no problems. The only thing that I did on eclipse, which could have caused this problem, was installing the v7 appcompat support library from a resource to eclipse using this guide on developers.android (https://developer.android.com/tools/support-library/setup.html).
The device is still recognized as a normal multimedia drive in Windows when it's not in debug mode.
The device is in Developers mode and in Debug mode when I try to run an Android Project in eclipse or try to see if it's recognized by adb using adb devices in the console.
The Google USB drivers have been installed through the ADK Manager
The USB OEM drivers for Windows have already been installed according to the tutorial on the android-developers site (see: https://developer.android.com/tools/extras/oem-usb.html)
I tried to restart adb by using the commands adb kill-server and adb start-server, and again checked if the devices was recognized by using adb devices. The device was still not listed on the console.
Restarting windows & eclipse did not fix this problem.
What's the solution to this problem?
UPDATE: Thanks for the replies, the problem is solved (for now).
I tried the following suggestions in this order:
I restarted my device - this did not fix the problem
I set my device to PTP mode - this fixed the problem.
So I reset my device to MTP mode & debug mode again to check if it still would be recognised by adb for some reason. It definitly doesn't get recognised by adb when it's in MTP-mode. I don't know how it got recognised some days ago, because I never setmy device to PTP-mode. Anyway, the solution to my problem is that my Nexus 4 must be in PTP-Mode and of course in debug-mode to get recognised by adb.
I didn't try any other suggestions since my problem got solved with my current drivers.

Generally, I think your USB connection should be set to use MTP (Media Transfer), however, I couldn't get my computer to recognize my device (Nexus 4). Oddly, setting the USB connection to Camera got it working for me.

I recently had this issue (but before that debug over wifi was working fine) and since none of the above answers helped me let me share what I did.
Go to developer options
Find Select USB configurations and click it
Choose MTP (Media Transfer Protocol)
Note: If it's set to this option chose another option such as PTP first then set it to MTP again.
UPDATE:
PTP stands for “Picture Transfer Protocol.” When Android uses this protocol, it appears to the computer as a digital camera.
MTP is actually based on PTP, but adds more features, or “extensions.” PTP works similarly to MTP and is commonly used by digital cameras.

I also faced the same problem and tried almost everything possible from manually installing drivers to editing the winusb.inf file. But nothing worked for me.
Actually, the solution is quite simple. Its always there but we tend to miss it.
Prerequisites
Download the latest Android SDK and the latest drivers from here. Enable USB debugging and open Device Manager and keep it opened.
Steps
1) Connect your device and see if it is detected under "Android Devices" section. If it does, then its OK, otherwise, check the "Other devices" section and install the driver manually.
2) Be sure to check "Android Composite ADB Interface". This is the interface Android needs for ADB to work.
3) Go to "[SDK]/platform-tools", Shift-click there and open Command Prompt and type "adb devices" and see if your device is listed there with an unique ID.
4) If yes, then ADB have been successfully detected at this point. Next, write "adb reboot bootloader" to open the bootloader. At this point check Device Manager under "Android Devices", you will find "Android Bootlaoder Interface". Its not much important to us actually.
5) Next, using the volume down keys, move to "Recovery Mode".
6) THIS IS IMPORTANT - At this point, check the Device Manger under "Android Devices". If you do not see anything under this section or this section at all, then we need to manually install it.
7) Check the "Other devices" section and find your device listed there. Right click -> Update drivers -"Browse my computer..." -> "Let me pick from a list..." and select "ADB Composite Interface".
8) Now you can see your device listed under "Android Devices" even inside the Recovery.
9) Write "adb devices" at this point and you will see your device listed with the same ID.
10) Now, just write "adb sideload [update].zip" and your are done.
Hope this helps.

It may sound silly but in my case the USB cable was too long (even if good quality). It worked with my tablet but not with the phone.
To check this, if you run on Linux run lsusb to make sure that your device is at least officially connect to the usb port.

Try use PdaNet. you can download it from here
It installs missing drivers when you plugin your device.
Obviously make sure you "debug usb" option in "developers options" is on.
Another thing, it's important to uninstall any device's installed driver before using it.

Fundamentally, the issue has to do with not being able to get MTP+ADB working while for example PTP+ADB may work. In my case when I plugged Nexus 5, windows 7 will install only MTP driver completely ignoring ADB. I couldn't find a good solution for this problem anywhere else so here I provide steps (some of the steps I copied from other sources):
0) Unplug Nexus 5. Make sure you selected MTP and ADB.
1) Make sure that sdk\extras\google\usb_driverandroid_winusb.inf in Google SDK had the following lines (in two places in that file):
;Google Nexus (generic)
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
NOTE: VID_18D1 is Google VID, PID_4EE2 is PID for MTP+ADB, MI_01 means that ADB is on interface 1 (MTP is on interface 0).
You can check what is on what interface by plugging Nexus 5 into a Linux system and typing lsusb.
2) first delete all installed Google USB drivers. One good tool is called USBDeview and can be find at the following location:
http://www.nirsoft.net/utils/usb_devices_view.html
Download the tool and run it (there is no need to install it). Take a look at the colored status indicator on the far-left of the USBDeview window. Green indicates the the device functions properly. Pink means the device can unplug and works properly (although it may not actually work properly). Red indicates a disabled USB device. Gray (circled, below) means the device is installed, but not connected.
Second, remove all gray items with the words “Google”, “Linux”, “ADB”, or “Android” in the title.
3) Now delete old cached Google *.inf files. Open a Windows Explorer and navigate to the C:\Windows\INF directory. Somewhere in there there is an "oemN.inf" file (where N is a number that will vary on your system) that is a copy of the android_usb.inf -- the thing to do is to find which file and remove it. Windows keeps a cache of the INF files here and what we found is that sometimes an older cached copy is used instead of a newer version.
One simple way to find which one using the Windows Explorer:
- In the explorer's Search box, enter "androidwinusb86.cat" without the quotes.
- Typically the search will be empty because no filename has this pattern.
- Go to Tools/Folder Options, click Search Tab and click Always search file name and contents. Click Apply
- Search again. This time it should list a few files such as "oem90.inf" (you'll have one or more, with different numbers).
Now use the Windows Explorer and delete the "oemNN.*" files that matched above (only those with androidwinusb in them.).
4) We now want to disable installation of MTP by windows before windows discovers ADB. Now search for wpdmtp.* files in the same directory. Presence of these files will force install MTP disregarding ADB class in the same (composite) device. Move these files out of \inf folder
5) plug in the device again. This time, both MTP and Android ADB driver installation will fail.
6) Find Other devices in the Device Manager and when expanded it should show Nexus 5 and MTP. Right click and update Nexus 5 by navigating to the sdk\extras\google\usb_driver\android_winusb.inf.
Move wpdmtp.* files back to \inf folder. Right click MTP device and update.
7) If necessary, confirm on your Nexus 5 that this PC has access to the phone.
8) If everything went as expected you should see in Device Manager the following:
Expand Android Device. Right click Android Composite ADB Interface, select Properties, choose tab Details, under Property select Hardware Ids. You should see USB\VID_18D1&PID_4EE2&MI_01
Expand Portable devices. Right click Nexus 5, select Properties, choose tab Details, under Property select Hardware Ids. You should see USB\VID_18D1&PID_4EE2&MI_00

With USB connected, on android device Settings > Developer options > Revoke USB debug authorizations USB Debug. Remove the USB and connect again, then "Allow USB debugging".

For those people to whom none of the answers worked, try closing the chrome://inspect/#devices tab in Chrome if it is open. This worked for me.

Go to prompt command and type "adb devices". If it is empty, then make sure you allowed for "MTP Transfer" or similar and you enabled debugging on your phone.
To enable debugging, follow this tutorial:
https://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android.htm
Then type "adb devices" again. If a device is listed in there, then it should work now.

Set your environmental variable Path to point to where the adb application is at: [directory of sdk folder]\platform-tools

Enabling Developer mode by tapping on Build Number 7 times worked for me.

Make sure you are connecting with a USB and not a lightning cable. I had this problem trying to connect using a cord with lightning cables on both ends and it would not list the device. But switching to a USB to lightning cable worked.

Check that the USB cable is indeed capable of transferring data. Some cheaper ones, especially those meant to charge non-phone/computer devices, might only support charging.
You can verify this by checking if the device shows up as mountable file system. In Linux, you can also use the command lsusb to check if it's being detected.

Find drivers for your device and install them
That will be the end of your device not detected problems
Windows have driver problems, sometimes messed by overriding the existing driver
You can also try uninstalling driver from Win7 and reinstalling

For those facing problem after upgrading their android device to android 10, same PTP Mode option will work as prescribed by user3135185

I tried all these, but nothing worked. Finally, I changed my old data connection USB-c cable, to a new one. Maybe with updates of windows/android studio, the older USB-c protocols are no longer recognized for transfer.

Download and install Moborobo software on your computer.
Connect your device with USB debugging through USB cable.
Now open moborobo and it will connect to your android.
Stay connected, now your device should recognize as adb devices and get
listed.

Android 4.2.2 Device Offline

I've read several users having similar problems, but none of the solutions I've found have solved my issue.
I have several Nexus devices running Android 4.2.2 and they all show up as offline and none of them show a prompt when I plug them in.
I already tried:
unplugging/plugging them in
switching off/on usb debugging
restarting computer, nexus devices and the adb server
reinstalling drivers and even switching drivers to Samsung ADB drivers
Confirmed I'm running adb 1.0.31
Made sure my path points to adb.exe
Deleted any old adb.exe files on my entire computer

if you have properly installed adb and you tried all of the remedies mentioned at above the listen to my remedy:
The reason to appearing "device offline" in android 4.2.2 is that android has a security feature in 4.2.2 that create a whitelist of usb ports that can be used as debugging port.
After plugging deivce in usb and entering the command "adb devices" a popup window will be raised in your device and ask you to accept the connection:
After accepting RSA fingerprint of you usb you can now issue the "adb devices" again and see the device is no longer offline,
If you dont see the popup window, the reason is your adb version is old, your adb version must ne at least 1.0.31 (you can see the version using the command "adb version"). if version is older than 1.0.31 then update your platform-tools package using latest updates from google. You can find the latest version in sdk-repository. find platform-tools*.zip associated with your OS and download from https://dl-ssl.google.com/android/repository/platform-tools*.zip .
for example version 19.0.1 of platform-tools can be downloaded using these links:
For linux: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-linux.zip
For windows: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-windows.zip
For MacOSx: https://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-macosx.zip
that's it

Finally found the answer. I had installed "SnapPea", which apparently ships its own ADB.exe. It was somehow getting in the way. Uninstalling this poorly written software and rebooting fixed the issue.
As an Android developer, this type of thing is scary. Was it sending everything I did to a home server somewhere? Why should any software install ADB on a customer's computer?
This is probably the reason Google had to add this security measure in the first place...

I got the same problem and it was just my ADT Eclipse plugin wich was out of date.
I install all the updates and everything went ok.
I don't know if its the same for you, sometimes we just forgot to put the updates...

For me it was working, but a minute later (upon reconnecting the usb cable) the device was 'offline'. I got it 'online' again by disabling and then re-enabling the USB Debugging option in the developer settings of the device.

Android 4.2.2 adb can't find devices

With the new update to 4.2.2 to my Galaxy Nexus and Nexus 7, I can't find both my devices under adb.
These are the steps I took:
Updated to 4.2.2
Updated ADT and SDK through the SDK Manager
Checked ADB version, it's at 1.0.31
Restarted PC and Tablet and Phone numerous times
When I run adb devices, it's just blank. I have the same issue on Windows 8 and on Ubuntu 12.10, but on Ubuntu it shows my device and it says offline.
Are there any other steps I can take?

From the adb docs
When you connect a device running Android 4.2.2 or higher to your
computer, the system shows a dialog asking whether to accept an RSA
key that allows debugging through this computer. This security
mechanism protects user devices because it ensures that USB debugging
and other adb commands cannot be executed unless you're able to unlock
the device and acknowledge the dialog. This requires that you have adb
version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher)
in order to debug on a device running Android 4.2.2 or higher
So, unplug, wait, replug in the cable, and hit ok (on modal dialog that appears on your device)
If you hit cancel, the device will show up as offline via adb devices

Try pre-installing the drivers for your devices. Make sure, under Windows, that your device is recognized in the System control panel first.
I use Windows 7 and my Galaxy Nexus wouldn't be recognized by the system until I installed the device drivers before plugging them in. From the comments, this works on Windows 8 as well.
Galaxy Nexus drivers
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Goto Manual & Drivers > Software
Nexus 7
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2

Just though Id share my experience, I had -
Unplugged and re plugged in the device
Installed the correct platform tools
Installed the correct Android bridge Turned USB debugging on and off
and on and off an...
Tried WiFi but it said it was offline
etc. etc.
What fixed it for me was changing the device connection from Mass Storage to MTP. To do so, with the phone unplugged you go into -
"Settings" -> "Storage" -> Click the menu Button -> "USB computer
connection" -> "Media device (MTP)"
Hope this helps some one from going crazy!
Thanks,
Ash.

I tried everything mentioned here and in other posts. It wasn't the cable, the USB port, rebooting the PC or Nexus 7, killing and starting adb or enabling/disabling USB Debugging.
It was due to the 4.2.2 OTA update, I simply replaced the \platform-tools\ folder, as described here: Android ADB device offline, can't issue commands
Download the updated platform-tools: http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip

adb wait-for-device
works for me. Just unplug your usb device, run this command, and while it's waiting, plug your device in, then it will just work. :)

Here is what I did (Galaxy S4 4.2.2):
go to Settings => about this device => click several times on "Version number", that is to say something like "JDQ39.I9505XXBHYTGKDD" (not android version or anything else) ; here you will see that Google or Samsung have a lot of humour as you have to click until multiple times until having a toast displaying "You are at few clicks from being a developer" ; after something like 10 clicks, you have a toast "You are a developer"
Go "Development options" (in the "More" tab (rigjt tab of settings menu)) ; be sure that "USB debugging" is checked.
And it works ! Eclipse can see your S4(or any other device) 4.2.2 !

I had this problem today and fixed it by rebooting the Tab2 while leaving it plugged into the laptop/eclipse

Check if you have installed android-adb-tools in Ubuntu. If you do, the adb tool may be old. Uninstall and make an alias to the latest adb tool you download with the ADB plugin. To check the adb version do "adb version" if it's 1.0.29 is the old, the latest and working for Android 4.2.2 is 1.0.31.
I made a lot of stuff until i realized this.

going to Developer Options and checking USB Debugging solved it for me

My solution used on cm10.1 nightly build on droid bionic, was after updating the newest usb drivers, using the Mass storage option (instead of the MTP option for USB computer connection), then unchecking and rechecking in developer options, "ADB over network" option. Then it did the RSA pop up dialog.

For me the best solution was:
Update the Android SDK via the SDK-Manager. Removing the '.android' folder in my usr directory ( Windows 7 ) and re-plugging the device back in. Worked flawlessly due to the ADB RSA key issue. I had an older version of ADB that I stashed into c:\windows\system32\ due to not wanting to install an entire freakin SDK when all I wanted was a command prompt. Good ol' Google, the new Microsoft.

You may use an old version of adb.exe. Update platform-tools.
You may have to set a new path to adb.exe as well.

In case it helps someone else arriving here, I had this problem with a ZTE phone.
I tried installing the driver based on the offical list here but in Device Manager the driver was marked as not installed correctly.
In the end I found the way to make this work was:
Press Menu Button
Choose "Connect to PC"
Choose "Default connect type"
Choose "Install Driver"
Plug in phone and on PC select option to install the driver
Then change "Default connect type" to "PC software"
After doing this I was able to do:
adb kill-server
adb start-server
adb devices
and view my device.

It's working on windows 8 using Android 4.4.2
Reset your phone,
go to setting->about phone-> seven time click on build number.
go to back and go to developer options check USB debugging.
go to windows 8 start menu click on profile picture and click change profile picture.
Select devices and on Download over metered connections.
Connect your phone via cable your PC and wait.

Cannot connect Nexus One Phone to Android adb

I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet.
(I have Windows XP)
Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site:
http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears.
On the Eclipse console, I get the following message:
[2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great.
I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.

I had this same problem. To get it working, do the following:
Close Eclipse
Open Task Manager and kill the adb.exe program.
Re-open Eclipse (Eclipse will automatically restart the adb.exe service)
Run adb devices from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.

It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices again. You can also check your system logs for errors - run compmgmt.msc and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.

Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.

Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem..
link text

I had this same problem. Do the following:
Plug your phone into your computer and:
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module

I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.

Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.