1. Plug-in your device then exec command ‘lsusb’ then you will see the list of current usb devices
Bus 003 Device 023: ID 18d1:d00d
We will see a device is appeared when it plug-in and disappeared when it plug-out. That device is we wanted and take my environment as an example it is located at line 1, “Bus 003 Device 023: ID 18d1:d00d”, without device provider.
2. Login as root and create this file: /etc/udev/rules.d/50-android.rules
For Gusty/Hardy, edit the file to read:
SUBSYSTEM==”usb”, SYSFS(idVendor)==”18d1“, MODE=”0666″
For Dapper, edit the file to read:
SUBSYSTEM==”usb_device”, SYSFS(idVendor)==”18d1“, MODE=”0666″
Fix for ADB in Ubuntu 9.10 (32bit)
I figured I would post this fix just in case anyone was having problems w/ adb in Ubuntu like I was having. I am no Linux Guru, if there is a better way of fixing this problem let me know
After Rooting the phone and installing Android SDK, when trying to run adb I would get this:
$ adb devices
List of devices attached
???????????? no permissions
I fixed this by:
In the blank area copy and paste this, inserting your user name in place of :
Save and Exit.
Restart the udev by:
Restart adb:
You should see the message:
* daemon not running. starting it now *
* daemon started successfully *
Now when you adb devices your phone should show.
After Rooting the phone and installing Android SDK, when trying to run adb I would get this:
$ adb devices
List of devices attached
???????????? no permissions
I fixed this by:
Code:
sudo gedit /etc/udev/rules.d/10-motorola-droid.rules
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct} =="41db", MODE="0600", OWNER=""
Restart the udev by:
Code:
sudo service udev restart
Code:
adb kill-server
adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now when you adb devices your phone should show.
0 comments:
Post a Comment