[solved] Unable to set udev rules for my android samsung galaxy

duquesnc · 2009-10-16 10:09:48

Hi,

I'm trying to access my samsung galaxy through adb (the android debug bridge), but I always end up with a "error: device not found". I believe this is because of a bad udev rule, because I do not see any device in /dev for my phone, when I plug it.

I require your help for being able to access this phone through adb.

I followed several tutos.Interesting posts can be found in the following list :
for english users
http://developer.android.com/guide/deve … evice.html (obviously)
http://forum.hdblog.it/showthread.php?t=3926
http://ghantoos.org/2009/08/08/running- … r-android/
http://android-dls.com/wiki/index.php?title=Fastboot
http://forum.hdblog.it/showthread.php?t=3995&page=14
for french users
http://www.korben.info/samsung-galaxy-d … ering.html
http://www.frandroid.com/forum/viewtopic.php?id=1692
At some moment, I thought the solution would be found here:
http://bbs.archlinux.org/viewtopic.php?id=59509
but nope, it did not work for me.

The error happens when I try to do a 'adb shell', which is supposed to run the remote shell interactively.
When I try to list the connected devices with 'adb devices', the returned list is empty.

I tried with the phone normally booted, with usb debugging enabled, and I tried in recovery mode.

Other useful infos:
I succeeded to flash the phone in fastboot mode. The config I was using with udev was at the moment:

$cat /etc/udev/rules.d/50-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

$cat /etc/udev/rules.d/51-android.rules 
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

$cat /etc/udev/rules.d/90-android.rules 
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"

I am also able to mount the sdcard of the phone normally (I use the notification "usb connected" on the phone, then "mount") and using ivman I can see the phone files on my file manager.

When my phone is plugged, with usb debugging enabled

$lsusb | grep Phone
Bus 002 Device 006: ID 04e8:6601 Samsung Electronics Co., Ltd Z100 Mobile Phone

less usefull:
I am running a x86_64 with the android sdk (and the ndk) installed through yaourt.

$cat .zshrc|grep android
export PATH=$PATH:/opt/android-sdk/tools/

I tried to access the phone with two different adb : the one provided by the sdk, and the one I found on korben.info (http://pictures.korben.info/2009/08/Sam … eak.tar.gz) which is supposingly a little different, because the samsung galaxy has a different hardware from the other gphones.

[EDIT] also, to restart udev, I issue

#udevadm control --reload-rules

and I don't know if that is enough

PS : Not related, but if you want to compile your own android kernel, I just found another interesting link : http://www.receptorblog.com/wordpress/h … ng-galaxy/

Last edited by duquesnc (2009-10-16 23:35:12)

duquesnc · 2009-10-16 12:53:42

I do not find any relevant information to feed this topic, but if you bother asking me what would be interesting...

Please help. I'm stuck.

Bump.

duquesnc · 2009-10-16 21:29:19

up

duquesnc · 2009-10-16 23:33:50

Okay. I don't really know *why*, but it seems like I managed to get it working.

Actually the guys in this post http://bbs.archlinux.org/viewtopic.php?id=59509 are right. For getting adb to work, you don't need any udev rule. Just spawn adb as root. Actually I think the rules I had were preventing the config to work properly.

The tricky part is having fastboot working while adb works too. For this one, refering to the wiki of android-dls, I remembered that the device id was different when in fastboot mode. Unfortunately, the mentioned entry for the samsung galaxy did not work for me, because afaik, the samsung galaxy has a hardware different from the other gphones (so it would be 18d1 instead of 0bb4). So what works with me is only one file in /etc/udev/rules.d:

$ cat /etc/udev/rules.d/90-android.rules 
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"

Also, you *can* reload udev easily, issuing as root:

udevadm control --reload-rules

I'll put the flag [solved] on my post, I hope it can help someone else.

I also say I could flash all this stuff using a regular x86_64 archllinux, without any problem (I just had to yaourt -Sy android-sdk).

Last edited by duquesnc (2009-10-16 23:36:41)

InfernalH · 2010-01-02 12:34:12

Hey, thanks, works for me too! But only for fastboot adb works only when replaced with this one: http://floe.butterbrot.org/external/adb.gz

Last edited by InfernalH (2010-01-02 14:33:01)

Znupi · 2010-05-12 22:16:36

Sorry for bumping a relatively old thread.. But WHERE DID YOU GET THAT ADB? It fixed my Samsung Galaxy Spica, too (and I spent hours trying to get it to work before finding this thread)!

Edit: Nevermind, found it. http://code.google.com/p/android/issues/detail?id=5027 .. thanks for compiling it for us

Last edited by Znupi (2010-05-12 23:23:24)

Arch Linux

#1 2009-10-16 10:09:48

[solved] Unable to set udev rules for my android samsung galaxy

#2 2009-10-16 12:53:42

Re: [solved] Unable to set udev rules for my android samsung galaxy

#3 2009-10-16 21:29:19

Re: [solved] Unable to set udev rules for my android samsung galaxy

#4 2009-10-16 23:33:50

Re: [solved] Unable to set udev rules for my android samsung galaxy

#5 2010-01-02 12:34:12

Re: [solved] Unable to set udev rules for my android samsung galaxy

#6 2010-05-12 22:16:36

Re: [solved] Unable to set udev rules for my android samsung galaxy

Board footer