[SOLVED] adb doesn't detect Android devices

iso · 2012-01-23 05:44:20

When I plug in a device via USB, `adb devices` comes up empty. I followed the instructions on the Android site[1] , but 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?

1. http://developer.android.com/guide/deve … evice.html

Last edited by iso (2012-01-24 04:43:01)

mrmylanman · 2012-01-23 12:58:44

When I use ADB and Fastboot, I need to run the commands as sudo. I think it has something to do with permissions, and I never felt like changing them with the actual devices, so I'd give running the commands as root a shot, if you haven't already (solved my problem anyhow).

Hope this helps!

Stemp · 2012-01-23 13:16:19

I use the AUR package android-udev.
The google part is :

#      Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="adbusers"
#      NEXUS S
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e21", 
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", SYMLINK+="android_fastboot" 
#      Nexus One
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e11", 
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="0fff", SYMLINK+="android_fastboot"
#      Generic and unspecified debug interface
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", SYMLINK+="android_fastboot"

And I'm part of the adbusers Group.

iso · 2012-01-23 13:33:06

@mrmylanman - running with sudo still shows no devices

@Stemp - I created the adbusers group, added myself to it, installed android-udev and added the configurations, restarted my machine, but still can't detect any devices. Since the Samsung Nexus isn't included with your settings when I plugged it shows "???????????? no permissions" when running `adb devices` which is expected.

mrmylanman · 2012-01-23 23:04:33

I'm assuming you have debugging enabled in the settings app of your phone. Super basic, but that's strange I have never encountered an issue like this before. Good luck with it. I was hoping I could be of help but it seems like maybe not.

iso · 2012-01-24 04:42:19

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"

Thanks for the help.

Arch Linux

#1 2012-01-23 05:44:20

[SOLVED] adb doesn't detect Android devices

#2 2012-01-23 12:58:44

Re: [SOLVED] adb doesn't detect Android devices

#3 2012-01-23 13:16:19

Re: [SOLVED] adb doesn't detect Android devices

#4 2012-01-23 13:33:06

Re: [SOLVED] adb doesn't detect Android devices

#5 2012-01-23 23:04:33

Re: [SOLVED] adb doesn't detect Android devices

#6 2012-01-24 04:42:19

Re: [SOLVED] adb doesn't detect Android devices

Board footer