PocketMagic

PocketMagic

Where Technology meets magic


Android
47 Posts
BlackBerry
4 Posts
Electronics
69 Posts
Hardware
123 Posts
High Voltage
49 Posts
Image processing
2 Posts
iPhone
4 Posts
Linux
2 Posts
Nuclear
20 Posts
Optics
11 Posts
Photography
7 Posts
Photoshop
3 Posts
Research
19 Posts
Reviews
18 Posts
Robotics
8 Posts
Security
7 Posts
Software
76 Posts
Symbian
2 Posts
Tubes
20 Posts
Windows
3 Posts
Windows Mobile
11 Posts

Top Articles!       See PocketMagic on Facebook


Building a robot – Part 2 | 8904 Views | Rate 66.95
Building a robot – Part 2
uRADMonitor - Online Radiation monitoring station | 16144 Views | Rate 66.71
uRADMonitor - Online Radiation monitoring station
Bluetooth and iOS - Use Bluetooth in your iPhone apps | 22155 Views | Rate 65.35
Bluetooth and iOS - Use Bluetooth in your iPhone apps
NMEA GPS Library for AVR Microcontrollers | 5843 Views | Rate 50.81
NMEA GPS Library for AVR Microcontrollers
Programmatically Injecting Events on Android - Part 2 | 6583 Views | Rate 46.69
Programmatically Injecting Events on Android - Part 2
Simple Switched power Supplies | 19162 Views | Rate 46.29
Simple Switched power Supplies
Capacitor Discharge Microspot Welder / Cutter | 13238 Views | Rate 38.94
Capacitor Discharge Microspot Welder / Cutter
Coil Winding machine counter with Atmega8 and Reed relay | 988 Views | Rate 38
Coil Winding machine counter with Atmega8 and Reed relay

 
  

Android adb error: “device not found” on Ubuntu


By Radu Motisan Posted on June 2nd, 2009 , 2636 Views (Rate 1.78)



  

I've been getting this error way too often recently, so I've decided to point out some of the causes.

1) using my older desktop pc I cannot use adb to connect to the Android device, but I can see the files on the micro SDCard. Seems to be related to hardware, and not much I could do to fix it. On the other hand, I can use my notebook to connect with adb wihtout any issues.

2) under ubuntu, using latest SDK from google, I remember everything worked smooth: adb shell, adb push, and the others. Suddently, I got this error:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

Same for adb devices, adb-getstate and so on.

The problem is that we need to run everything with root privileges.
So the correct way to do it is:

sudo ./adb kill-server
sudo ./adb shell

Hope this saves you some precious time.

Radu Motisan


  

More on PocketMagic:

Atmega8 and enc28J60 for ethernet support | 8868 Views | Rate 27.37
Atmega8 and enc28J60 for ethernet support
How to make metallic sodium | 1442 Views | Rate 26.7
How to make metallic sodium
Tube: USN-5J29 | 1094 Views | Rate 25.44
Tube: USN-5J29
How to set the AVR Fusebits | 2555 Views | Rate 25.3
How to set the AVR Fusebits
Dual H-Bridge for controlling two motors | 2110 Views | Rate 24.82
Dual H-Bridge for controlling two motors
Tube: GP-5 (ГП-5) | 640 Views | Rate 24.62
Tube: GP-5 (ГП-5)

39 Responses to “Android adb error: “device not found” on Ubuntu”

  1. 1
    Daniel Holm:

    Thank you so much! It made my day! Or perhaps week!

  2. 2
    Radu Motisan:

    I’m glad somebody found this useful :) .

  3. 3
    tim:

    THX this is verry usefull i had looking on a lot of site’s but couldn’t find an answer thxs !!

  4. 4
    Radu Motisan:

    Yeah. Small tips but annoying bugs.

  5. 5
    zelrik:

    What is adb? Why it says command not found when I use it?
    Why I cant connect to my phone with ubuntu???

  6. 6
    Radu Motisan:

    @zelrik, adb is part of Android’s SDK used for various remote operations (Android Debug Bridge). First you need to download the google android sdk for linux, (also read http://www.pocketmagic.net/?p=665).

    Then simply un-archieve the SDK, and inside the TOOLS subfolder you’ll find adb.

  7. 7
    tim:

    Just go to your Android tools map there you find adb you can use it by typping the folowing at the tools map adb devices this shows you the list of attached devices if it doesnt restart the deamon
    Greetings

  8. 8
    Aparna:

    Hey Radu,
    Thanks for the info..
    when i give the following command i’m getting this error…
    sudo ./adb shell
    error: device not found
    how can i fix it??
    Regards
    Aparna..

  9. 9
    Radu Motisan:

    Hi Aparna,

    If my post above doesn’t help you, you might want to know that the “device not found” error also appears when:
    1) connectivity issues (bad cable, no device connected, etc)
    2) your USB port is not 2.0
    You might want to try connecting your android on a different PC. Hope this helps.

  10. 10
    pimpim:

    You need to also enable usb debugging on th phone itself. It is an option under settings-applications-development (exact names can differ, I only know the german names)

  11. 11
    cz:

    Is the command suit for all android platform?
    I tried but I got this:
    “‘sudo’ is not recognized as an internal or external command,operable program or batch file.”

  12. 12
    Radu Motisan:

    cz, you need to type those commands on your PC, not on the Android.
    You might want to read the article again.

  13. 13
    cz:

    Dear Radu,

    First of all very grateful to your comment.

    Yes, certainly I have typed those commands on my PC, and the status I mentioned “’sudo’ is not recognized as an internal or external command,operable program or batch file.”happened when I typed the commands.
    The adb error troubled me for a long time. If you have any other method to resolve this problem, please tell me.
    Thanks very very much.

  14. 14
    Radu Motisan:

    hi cz, Sorry for the confusion.

    The idea is that you need root for those commands.

    So either you use ‘sudo’ (to execute the following command as root), either you login as root and type the commands (adb kill-server and adb shell) directly in a root console (make sure you have the # prompt), or last option, login as a non-privileged user and type su in the console, to gain root, and type the commands at the command prompt.

  15. 15
    cz:

    hi Radu,
    I am glad to tell you that the problem was resolved.
    I only changed the SDK from 1.5_r1 to 1.5_r3, and the device can be found by PC.

    Thanks again for all your help:)

  16. 16
    Radu Motisan:

    cz, thanks for the follow up and I’m glad you’ve made it

  17. 17
    Asif:

    Hello Radu,

    I am facing the same problem and I am already logged in with root privilages but still I am stuck. I had checked in the minicom, there board is detecting USB host and telling “android usb gadget : high speed config #1:android”

    but at my desktop side it gives “no device found error”.
    I am using Redhat Linux 2.6.9. Is any driver is needed for this?

  18. 18
    Ganesh:

    Wow I googled for my error and found it in couple of minutes on this blog. Thanks for relieving me of my headache!

  19. 19
    Radu Motisan:

    I’m happy to hear that, good luck with your project!

  20. 20
    lgespee:

    Thanks mate,

    Was trying to figure out why Ubuntu 0.10 was unable to find my ADP1.
    Indeed I ran the processes with user privileges instead of root/sudo.
    Thanks a lot for saving me some time and a headache.

  21. 21
    Yarik:

    Thanks, man!! I was looking for the solution to make the adb see devices from the eclipse. After trying out several workarounds I found your post and it just perfectly worked!
    Cheers,
    Yarik

  22. 22
    Radu Motisan:

    Thanks, I’m glad it proved useful.

  23. 23
    Manivel:

    I have the same issue but how to get it resolved in windows xp?

  24. 24
    Radu Motisan:

    Well, I think it’s a different issue in your case: a hardware problem with your USB port. Try using a shorter USB cable, or try plugging in a different port. I can’t connect the Android on my desktop but I have no issues on the laptop.

  25. 25
    Manivel:

    I tried to use other USB ports but didn’t work. The connection seems fine as I can transfer files but its only the commands like fastboot/adb that cannot identify the device. Should any setting be changed?

  26. 26
    sundar:

    Hi Radu Motisan,
    i successfully compiled my hello.c file using GNU/ARM tool chain. After when i try to push that file using adb push command i got the error as “device not found’”.i dont know what is the problem and why this problem occurs.pls help me

  27. 27
    sundar:

    Hi Radu Motisan,
    I am also having another one doubt pls clarify. Eclipse is essential to run the android emulator in linux without using eclipse shall we run the emulator because why i am asking means i cant able to set the ADT plugin in eclipse 3.2. Now i trying to run the emulator using GNU/ARM toolchain but i yet got succeed.

    Thanks in advance
    Sundar

  28. 28
    sundar:

    Hi Radu Motisan,
    I am also having another one doubt pls clarify. Eclipse is essential to run the android emulator in linux without using eclipse shall we run the emulator because why i am asking means i cant able to set the ADT plugin in eclipse 3.2

    Thanks in advance
    Sundar

  29. 29
    Yuriy:

    Hello everyone!

    sundar,
    Try to install eclipse 3.5 Classic (avaiable from http://www.eclipse.org/downloads/packages/release/galileo/sr2) and follow all the instrusctions from here http://developer.android.com/sdk/index.html

    Then you will be able to create virtual devices and run programs on them.

    Radu Motisan,
    I have the same problem with adb (no device found). I am running Ubuntu on virtual machine under Windows 7. My phone is recognized as RNDIS/Ethernet Gadjet and is connected to virtual machine. The phone is tuned (USB debug turned on), and I am logged as root on Ubuntu. I have tried everything listed in this topic, but it doesn’t help. Do you have any suggestions?

    Thanks,
    Yuriy

  30. 30
    Ruairi:

    I had the same problem device not found for any adb commands despite everything being set up fine. Tried everything mentioned here to no avail. Anyway after running the device through eclipse and using the adb devices command in the terminal to list connected devices I have full use of adb command again. This works every time I have that problem. Weird bug or something but hopefully this will work for others.

  31. 31
    Arunabh Das:

    Still getting a device not found on my MacBook Pro. – Arunabh Das

  32. 32
    PocketMagic » Android NDK Cygwin make error 127:

    [...] This machine also fails to connect to the Android properly, via USB, I get lots of timeouts and disconnects on large data volume. I've presented that issue here. [...]

  33. 33
    Wickid_D:

    @Ruairi:
    What exactly do you mean you “after running the device through eclipse?” I know what eclipse is, just never used it, so how about a few more steps for those who are having the same problem you had, where the same solution may come into play?

  34. 34
    Thanagmaniarun:

    Good, I really happy..that i am able to connect my HTC Desire Z via ADB :) :)

  35. 35
    Daruko:

    Thank you so much! That really saved a great deal of time :D

  36. 36
    dr.joe:

    Can’t get this to work with my Bionic. LSUSB shows the device is there but even with the proper rules file, debugging on, and running with sudo I still get nothing in my adb device list.

  37. 37
    ayush:

    THANKS ALOT YOUR JUST AWESOME

  38. 38
    SSN:

    Even with the root privilege, I’m getting “no device found” error. I also tried modifying the rules find in /etc/udev/rules.d. The device is being shown with “lsusb”.

  39. 39
    Radu Motisan:

    what device are you using?

Thank you for commenting. Your comment won't show until approved, which can take some time.

Please copy the string bzpATv to the field below: