adb shell 'device not found' (linux)

[Guest MrVanes]

Hi,

It seems that I'm currently not able anymore to "adb shell" to my Liquid anymore. I'm running ThePasto's CM7.1RC1 and noticed that the USB device id has somewhere in time changed from 0502:3202 long ago to 0502:3222. I adjusted my udev rules to make the device 0666 and run "adb shell" as root (so rights shouldn't matter anyway) but adb keeps returning "error: device not found". Even after an "adb kill-server". Adb is perfectly able to find and shell to my Iconia A500 (0502:3341), so I assume my linux/adb install to be flawless. Anyone seeing this particular problem and found a solution?

[Guest black_dez]

Install the latest drivers

[Guest MrVanes]

Install the latest drivers

What drivers? I'm using Linux like the topic says... Is there any particular kernel module I should enable/load?

[Guest black_dez]

Strange. I have a perfectly see. Have you created the file / etc/udev/rules.d/51-android.rules with line:

SUBSYSTEM == "usb", SYSFS {idVendor} == "0502", MODE ="0666"

Edited May 31, 2011 by black_dez

[Guest MrVanes]

Strange. I have a perfectly see. Have you created the file / etc/udev/rules.d/51-android.rules with line:

SUBSYSTEM == "usb", SYSFS {idVendor} == "0502", MODE ="0666"

Exactly like that and yes I enabled debugging as well... :D

[Guest black_dez]

And you are using the latest SDK?

[Guest MrVanes]

And you are using the latest SDK?

android-sdk_r11-linux_x86.tgz

[Guest black_dez]

Then I really do not know how we can help :D

[Guest Master_T]

Try to use "adb wireless", lets you use adb over wifi, without the need for drivers. To use it, acti9vate it on the phone, then type on the shell:

adb connect <phone's_ip_on_the_LAN>

now the phone is connected, and you can use the usual adb commands.

[Guest MrVanes]

Try to use "adb wireless", lets you use adb over wifi, without the need for drivers. To use it, acti9vate it on the phone, then type on the shell:

adb connect <phone's_ip_on_the_LAN>

now the phone is connected, and you can use the usual adb commands.

It doesn't seem to work:

# ./adb connect 192.168.1.109

unable to connect to 192.168.1.109:5555

# telnet 192.168.1.109 5555

Trying 192.168.1.109...

telnet: Unable to connect to remote host: Connection refused

Do I need to enable wireless adb on the device and if yes, where exactly?

Never mind, I found "adbWireless" in Market.

Edited May 31, 2011 by MrVanes

[Guest parvata]

Note that to connect over tcp ip you first need access to the android shell. May be you install a shell app on the phone and then execute the below three commands on the phone's android shell.

setprop service.adb.tcp.port 5555

stop adbd

start adbd

After this you should be able to connect using the adb connect command.

Try to use "adb wireless", lets you use adb over wifi, without the need for drivers. To use it, acti9vate it on the phone, then type on the shell:

adb connect <phone's_ip_on_the_LAN>

now the phone is connected, and you can use the usual adb commands.

[Guest MrVanes]

Using adbWireless and the adb connect <ip> method I can now access my phone using adb again.

Thx! Still weird I can't connect over USB though...

[Guest ma4000]

just run adb as root and it will work out of the box, without the need to add any files etc.

google should say that on the android sdk site...

[Guest MrVanes]

just run adb as root and it will work out of the box, without the need to add any files etc.

google should say that on the android sdk site...

Please re-read the original topic post. I start adb as root... it doesn't help!

Maybe kernel 2.6.39 (the last of the Mohicans) does me wrong? But then again, the Iconia A500 plays along nicely so it definately is something to do with the Liquid or CM7.1?