How to fix: Error device not found with ADB.exe

Android

Android Problem Overview


In cmd when I try to do the command:

adb shell

it shows device not found error. Can someone help me please. It'll be appreciated.

Android Solutions


Solution 1 - Android

Don't forget to go to your device and enable Settings->Developer Options->USB debugging.

Solution 2 - Android

Try any of the following solutions. I get errors with adb every now and then. And one of the following always works.

Solution 1
Open command prompt as administrator and enter

  1. adb kill-server
  2. adb start-server

Solution 2
Install drivers for your phone if you're not testing on emulator.

Solution 3
Open android sdk manager and install "Google USB Driver" from extras folder. (attached screenshot)

Android SDK Google USB Driver missing

Solution 4
Go to settings > Developer Options > Enable USB Debugging.
(If you don't see Developer Options, Go to Settings > About Phone > Keep tapping "Build number" until it says "You're a developer!"

Enable USB Debugging

Solution 3 - Android

It depends on windows system but usually:

  1. you go to system properties
  2. look at hardware devices
  3. Right click on the yellow (has to be yellow if it's driver problem) icon representing your mobile device
  4. select property
  5. Then go on the driver tab
  6. select update driver
  7. choose the bottom selection find on local computer
  8. then choose manually
  9. From the windows opened look for driver disk the bottom right button
  10. Choose the driver from the folder <sdk>\extras\google\usb_driver\i386 (or amd64 for and).
  11. Remember to uncheck the show only compatible hardware.
  12. Then choose the driver
  13. When windows warn your about possible incompatibility go on.

For my mobile it works, but depend on your mobile if it work or not.

Hope this help, bye.

Solution 4 - Android

If you installed Eclipse have Android SDK, go to DDMS. If the list device display "?????????"

you do adb kill-server and then adb start-server.

Please make sure you install USB driver and enable debug mode.

Solution 5 - Android

Another issue here is that you likely need to turn off "connect as media device" to be able to connect with adb.

Solution 6 - Android

For me, I have to Revoke USB debugging authorizations in Developer Options. Here is the steps:

  1. Turn off USB Debugging,
  2. Revoke USB debugging authorizations,
  3. Plug the cable back in,
  4. Turn on USB Debugging

Solution 7 - Android

I solved:

Just turn off USB debugging and re-enable debugging it immediately

Solution 8 - Android

On my G2 I had to select PTP instead of MTP mode to get the connection to work.

Solution 9 - Android

I had this problem suddenly crop up in Windows 7 with my Nexus One - somehow the USB drivers had been uninstalled. I ran android-sdk/SDK Manager.exe, checked Extras/Google USB Driver and installed it. Then I unplugged the phone and plugged it back in, and ran "adb devices" to confirm the phone was attached.

This doesn't work for all phones, just the ones listed here: http://developer.android.com/sdk/win-usb.html

Solution 10 - Android

Developer options

  • USB Debug

if you can not see developer option, go to about. build version and click build version until developer options in unlock.

Solution 11 - Android

Try changing USB port. Try restarting adb server.

Solution 12 - Android

I have a Droid 3 (Verizon). I went to Motorola here and found the driver for the device 'Motorola ADB Interface' which was showing in device manager. It's kind of a big download for just the driver, but during installation it found it and installed correctly.

Solution 13 - Android

I switched to a different USB port and it suddenly got recognized...

Solution 14 - Android

How about:

Settings -> System -> Developer options -> Debugging -> turn on toggle for Wireless ADB debugging

or:

Revoke USB debugging authorizations

and try from the scratch.

Solution 15 - Android

Just wanted to provide a simple answer here. I am just messing with an old Android device for the first time doing these root and unlock procedures. I received an error like this one when an adb push "..." "/sdcard/" command failed, and the key was that my device was in the bootloader screen. Booting to recovery then allowed me copy over the file(s), and I presume the normal OS would as well.

Solution 16 - Android

This worked for me, my AVG anti virus was deleting my adb.exe file. If you have AVG try:

  1. opening the program
  2. go to options
  3. go to the virus vault and click on it
  4. find your adb program, click on it, and press RESTORE at the bottom This will move the file back to its original place. However, unless you turn off the AVG it will delete the file again.
    After this android studio located the file. Good luck.

Solution 17 - Android

I found my solution from this similar thread by enabling USB tethering on my LG G6 (requires data saver to be turned off)

Go to: Settings -> Tethering & networks -> switch on USB tethering

Solution 18 - Android

For completeness, I've just had a case here I had to change my USB cable. Guess the one I had was for charging only, accursed thing.

Solution 19 - Android

On my Sony Xperia XZ1 Compact on Oreo I had to switch USB mode to MIDI to get it working. Only after this my Windows recognised Android ADB, however it couldn't autoinstall driver. I opened Device Manager and installed the Google USB Driver for the ADB.

Solution 20 - Android

To solve this problem,

Add adb folder to your windows path (system veriable)

This solves the problem

Solution 21 - Android

In my case I needed to swap the ends of the cable connecting my device to the computer...

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionMethodManXView Question on Stackoverflow
Solution 1 - AndroidrmtheisView Answer on Stackoverflow
Solution 2 - AndroidChiragMSView Answer on Stackoverflow
Solution 3 - AndroidGuaido79View Answer on Stackoverflow
Solution 4 - AndroidTai TranView Answer on Stackoverflow
Solution 5 - AndroidliamvictorView Answer on Stackoverflow
Solution 6 - AndroidchozView Answer on Stackoverflow
Solution 7 - AndroidMzhda SaeedView Answer on Stackoverflow
Solution 8 - Androiduser6591924View Answer on Stackoverflow
Solution 9 - AndroidSarah NorthwayView Answer on Stackoverflow
Solution 10 - AndroidCorreoView Answer on Stackoverflow
Solution 11 - AndroidSailesh LimbuView Answer on Stackoverflow
Solution 12 - AndroidSimon_WeaverView Answer on Stackoverflow
Solution 13 - AndroidchenopView Answer on Stackoverflow
Solution 14 - AndroidMichał Dobi DobrzańskiView Answer on Stackoverflow
Solution 15 - AndroidPysisView Answer on Stackoverflow
Solution 16 - AndroidLejacque Gillespie View Answer on Stackoverflow
Solution 17 - AndroidWilliam HumphriesView Answer on Stackoverflow
Solution 18 - AndroidIanView Answer on Stackoverflow
Solution 19 - AndroidKaligulaView Answer on Stackoverflow
Solution 20 - AndroidOkonkwo Clovis SaintianoView Answer on Stackoverflow
Solution 21 - AndroidFriendly-RobotView Answer on Stackoverflow