adb doesn't detect Android devices

Question

When I plug in a device via USB, adb devices comes up empty. I followed the instructions on the Android site[1] by adding the code below and restarting the adb server (I also restarted my machine since I couldn't get it to work). Both my Nexus One and Samsung Nexus are still undetected.

~ cat /etc/udev/rules.d/51-android.rules

# nexus one
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_adb", MODE="0666",    GROUP="wheel"
# samsung nexus
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", SYMLINK+="android_adb", MODE="0666", GROUP="wheel"

Any ideas?

http://developer.android.com/guide/developing/device.html

Do you see the USB device (say using 'lsusb')? If so, what vendor ID does it report? — David Schwartz
– David Schwartz, Commented Jan 23, 2012 at 6:09
Ya that is where I got the numbers from. 04e8:6860 (Samsung Nexus) 18d1:4e12 (Nexus One) — chris
– chris, Commented Jan 23, 2012 at 6:15
This may be stupid, but did you turn on usb debugging on the devices? — Anasthase
– Anasthase, Commented Jan 23, 2012 at 8:30
@david - I am not totally sure where the symlink should appear. I saw that added on some other posted solution — chris
– chris, Commented Jan 23, 2012 at 13:16

chris · Accepted Answer · 2012-01-24 04:45:49Z

3

It turns out the problem was that when I initially installed the android sdk's there was an issue when doing it through eclipse and the solution was to run eclipse via sudo. This did allow everything to be installed, but I think it may have been responsible for my issues since all the files belonged to the sudo group. I re-downloaded the sdk and instead of installing the versions through eclipse I installed them by running the android terminal command. After installing, running the ddms detected my devices. ** I also notices that I pluralized the ATTR in my rules file. In the end below is what worked for me (after creating the adbusers group and adding myself).

# nexus one
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="adbusers"
# samsung nexus
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="adbusers"

answered Jan 24, 2012 at 4:45

chris

4,3515 gold badges45 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Rajdeep Dua · Accepted Answer · 2012-01-23 06:19:22Z

0

Why is your GROUP 'wheel'? Try changing it to plugdev

answered Jan 23, 2012 at 6:19

Rajdeep Dua

11.2k2 gold badges34 silver badges22 bronze badges

1 Comment

chris Over a year ago

I don't think the group name is important, but only that I belong to the set group, which is why I used wheel. I admit it was laziness on my part to why I set it to an existing group I belonged to rather than create a new one :)

DevByStarlight · Accepted Answer · 2013-02-11 20:20:02Z

0

General answer is to verify / update the USB drivers.

I often find the USB driver that installs automatically from the device itself is either 1) out of date or 2) not intended for "true" application developer debugging support. (ie, more for "consumer" access to the device as a storage media rather than adb debugging support)

Android Developer page has a list of vendor links to get the USB drivers for the device

http://developer.android.com/tools/extras/oem-usb.html

answered Feb 11, 2013 at 20:20

DevByStarlight

1,08013 silver badges17 bronze badges

Comments

Vitaliy A · Accepted Answer · 2013-06-01 15:07:33Z

0

Try to:

Uninstall old Kies
Install: SAMSUNG Kies,PC Sync (Software) (ver.2.3.3.12085_7_5) from http://www.samsung.com/us/support/downloads/global#global_download_list

it worked for me :)

answered Jun 1, 2013 at 15:07

Vitaliy A

3,8381 gold badge34 silver badges34 bronze badges

Collectives™ on Stack Overflow

adb doesn't detect Android devices

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related