Related
How do I fix this issue?
I am a linux n00bie
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
You need to create a file named
/etc/udev/rules.d/51-android.rules
containing the line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
you need to be root to create the file, use
sudo -s
to become root, then
gedit /etc/udev/rules.d/51-android.rules
will open the new file for editing.
You'll have to reboot when done.
Thank you for your help and please excuse my ignorance in linux.
I just installed ubuntu today
The above didn't seem to work after a reboot.
I did successfully create the file however.
Any ideas?
Thanks.
There is another Vendor id for NexusOne. "0bb4" is not for Nexus but G1:
Working record for Nexus is:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
As stated by DEEsx1 the following is correct:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
However, it has been a mystery as to why the following location/file does not work for everyone:
Code:
/etc/udev/rules.d/51-android.rules
I am running Ubuntu 9.10 on my laptop with nothing special, just a straight load. the 51-android.rules code did not work for me.
I searched around on a few linux/android forums and found that some people had luck with creating the following file:
Code:
/etc/udev/rules.d/90-android.rules
However, that did not work for me. I had to create the following file:
Code:
/etc/udev/rules.d/99-android.rules
Now, if you are still getting the error, you don't need to reboot, you just need to restart udev:
Code:
sudo /etc/init.d/udev restart
You may also need to restart the adb daemon:
Code:
adb kill-server
adb start-server
adb devices
Now, worse case that I have seen, make sure the phone is not plugged into the computer, reboot the system AND the phone then try again (I have only seen this once).
Hope these tips help!
DEEsx1 said:
There is another Vendor id for NexusOne. "0bb4" is not for Nexus but G1:
Click to expand...
Click to collapse
You are correct, I didn't realize I had two udev files and I opened the wrong one.
thanks for your help! I'll try this out when I get home.
Yay! it worked. Thanks for your help.
Just out of curiosity how in the hell would I have otherwise known to create a file with a seemingly random name in a random folder?
and why 51-android.rules? why not 1-android or 5000000-android?
What's the logic there?
thanks again
charkosh said:
Just out of curiosity how in the hell would I have otherwise known to create a file with a seemingly random name in a random folder?
Click to expand...
Click to collapse
Welcome to Linux!
Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this.
charkosh said:
and why 51-android.rules? why not 1-android or 5000000-android?
Click to expand...
Click to collapse
The files are processed in order of their name so 51-xxx is mid-way through, 99-xx is at the tail end of the processing order. Sometimes, the order is important.
Also, after posting the wrong info to you earlier, I deleted the entry I posted. But, it turns out, the Nexus one poses as both id numbers. While in Android its VendorId=18d1, but in the bootloader (waiting in fastboot usb), the VendorId=0bb4.
So, I put both lines in one file today and all is well again.
I.e:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and I changed my filename to 99-android.rules
then ran:
sudo restart udev
and now I can access the phone as a non root user again, either from adb or fastboot-linux.
rotohammer said:
Welcome to Linux!
Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this.
The files are processed in order of their name so 51-xxx is mid-way through, 99-xx is at the tail end of the processing order. Sometimes, the order is important.
Also, after posting the wrong info to you earlier, I deleted the entry I posted. But, it turns out, the Nexus one poses as both id numbers. While in Android its VendorId=18d1, but in the bootloader (waiting in fastboot usb), the VendorId=0bb4.
So, I put both lines in one file today and all is well again.
I.e:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and I changed my filename to 99-android.rules
then ran:
sudo restart udev
and now I can access the phone as a non root user again, either from adb or fastboot-linux.
Click to expand...
Click to collapse
Thanks for this! You're a life saver. Actually a hair saver, I get to quit pulling mine out now!
I am definitely glad you posted about the differing device id when using the bootloader. That little detail kicked my butt for about an hour before I figured out what was going on. In Ubuntu (and probably other distros) there is a command line utility called lsusb, that gives you the nitty-gritty details about all the connected usb devices, including the device id. Just in case anyone stumbles across this thread for some yet unreleased android phone.
rotohammer said:
Welcome to Linux!
Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this.
The files are processed in order of their name so 51-xxx is mid-way through, 99-xx is at the tail end of the processing order. Sometimes, the order is important.
Also, after posting the wrong info to you earlier, I deleted the entry I posted. But, it turns out, the Nexus one poses as both id numbers. While in Android its VendorId=18d1, but in the bootloader (waiting in fastboot usb), the VendorId=0bb4.
So, I put both lines in one file today and all is well again.
I.e:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and I changed my filename to 99-android.rules
then ran:
sudo restart udev
and now I can access the phone as a non root user again, either from adb or fastboot-linux.
Click to expand...
Click to collapse
Thanks! It worked for me!
Samsung Vibrant
Thanks adding the file allowed me to remote debug my samsung vibrant on Ubuntu 10.4 - Many thanks!
Unable to see the Galaxy S on Ubuntu after above steps
mattb3 said:
I am definitely glad you posted about the differing device id when using the bootloader. That little detail kicked my butt for about an hour before I figured out what was going on. In Ubuntu (and probably other distros) there is a command line utility called lsusb, that gives you the nitty-gritty details about all the connected usb devices, including the device id. Just in case anyone stumbles across this thread for some yet unreleased android phone.
Click to expand...
Click to collapse
I have followed each of the steps mentioned above. adb devices gives the below response
List of devices attached
????????????? no permissions
adb host restart
Try to restart the host and then try again to connect the phone. The adb host seems to not start correctly after start or reboot of the linux system:
Talderon said:
You may also need to restart the adb daemon:
Code:
adb kill-server
adb start-server
adb devices
Click to expand...
Click to collapse
rotohammer said:
You need to create a file named
/etc/udev/rules.d/51-android.rules
containing the line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
you need to be root to create the file, use
sudo -s
to become root, then
gedit /etc/udev/rules.d/51-android.rules
will open the new file for editing.
You'll have to reboot when done.
Click to expand...
Click to collapse
It's not closely necessary reboot. You can try following this steps:
1. Unplug your smarthone from USB
2. Run this command: sudo restart udev
3. Plug your smartphone to USB
These permission issues were driving me nuts. I finally just decided to run adb as root user:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
These steps works fine with a motorola dext (with the right Id). Thank you so much
Fixed
rotohammer said:
You need to create a file named
/etc/udev/rules.d/51-android.rules
containing the line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
you need to be root to create the file, use
sudo -s
to become root, then
gedit /etc/udev/rules.d/51-android.rules
will open the new file for editing.
You'll have to reboot when done.
Click to expand...
Click to collapse
Thanks ! Had the same problem ..
Worked Fine on Ubuntu (Virtual Machine) using HTC Desire.
With the same idVendor -as it's the right one for Bravo-
^^
+1 on having to:
sudo ./adb kill-server
sudo ./adb start-server
The most complete set of directions in this thread boil down to (read thread for details):
Put both of the vendor ID lines in 99-android.rules
unplug
restart udev
kill and restart adb server as root
plug in
./adb devices
What exactly do I need to use adb in ubuntu 10.4
I cannot get anything to work and I'm not too familiar with linux.
I have the sdk downloaded and my terminal opened up to my tools directory, but I literally cannot figure out what I'm doing, no commands work and I can't even find my device (adb devices)
I have exclusively used windows for adb on my previous two phones, but I'm using ubuntu more and more so I would like to be able to use adb in it.
Easy.
cd /path/to/sdk/tools
./adb
ADB doesn't recognize my incredible in 10.4 when I do ./adb devices it is blank.
I've tried with the phone set to charge only and to disk drive.
I've tried following this:
a couple of topics concerning a rules file in /etc/udev/rules.d
I greated a 51-android.rules file and it looks like this now:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0ff9", MODE="0600", OWNER="mbambic"
I've restarted udev a few times and killed the adb server and done ./adb devices to restart it, no luck.
Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.
x.v_ said:
Do you guys have USB Debugging enabled?
Applications -> Development -> USB Debugging. MUST be checked.
Click to expand...
Click to collapse
yes, I've used adb numerous times on windows
http://developer.android.com/guide/developing/device.html
I'm no expert, but this is what I followed and my phone shows up in adb devices.
OK, that was my bad with debugging not on.
Now I'm getting the following:
#./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
I've tried with and without the rules file I created in /etc/udev/rules.d called 51-android.ruleswith the following entries that has been chmod a+rx
version 1
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
or version 2
UBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct} =="0c9e", MODE="0600", OWNER="myusername"
or version 3
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
based on this info:
$ lsusb
Bus 001 Device 022: ID 0bb4:0c9e High Tech Computer Corp.
Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again
I keep getting no command 'adb' found when I try to type any command
I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
Assuming you downloaded the sdk pack, your problem is that adb isn't in your path. Take a look at h t t p://developer.android.com/sdk/installing.html. To just temporarily add it, at the shell prompt enter:
Code:
export PATH=${PATH}:<your_sdk_dir>/tools
Also, you may have permission problems when running adb. The easiest way around this is to run adb as root, i.e.: sudo adb (but you'll also have to add adb to root's path then).
mtxpert said:
Got it:
edited the rules file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_adb", ATTRS{idProduct} =="0c9e", MODE="0666"
Rebooted phone
Turned on disk drive
restarted udev
killed adb and started again
Click to expand...
Click to collapse
Ok, so you used both lines in your 51-android.rules file? Interesting, so you're making the driver specific to the DI? I've been operating with just the first line, which allows to use the DI and the G1, but then again, I've also been unsuccessful at rooting
br125 said:
I keep getting no command 'adb' found when I try to type any command
Click to expand...
Click to collapse
In Linux Mint 9 x64 Isadora (much the same as Ubuntu 10.04 Lucid Lynx), I added the path command to my bashrc file in ~/user. Not sure how to make it global (prob would go somewhere in the mysterious&powerful /etc), but I'm the only user on my system, so for my purposes that doesn't matter
If this is the wrong forum, please feel free to move my post. I figured the devs here might be the best source of information to start with.
My laptop is running Kubuntu 11.04 and fully updated. I've followed all the various (and somewhat inconsistent) posts on the web about getting ADB to run on USB connections under Linux. I am successful getting ADB to see my G2 phone, but not my Nook Color.
Here's my /etc/udev/rules.d/51-android.rules:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
The permissions are set correctly, at 644. I've tried both ATTR and ATTRS; it doesn't seem to matter which.
Some, but not all, posts about getting ADB to work also indicated the requirement of another file, .android/adb_usb.ini. The presence or absence of this file seems to have no effect. Regardles, here's mine:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0bb4
2080
No matter what I attempt (even including reboots, thinking that restarting udev wasn't sufficient), ADB sees only my G2 and never my Nook:
Code:
List of devices attached
SH0C7R200734 device
Despite the fact that my Nook otherwise works fine on my Kubuntu box; lsusb sees it:
Code:
Bus 001 Device 008: ID 2080:0002
And I can mount its drives and Calibre is also very happy with it.
I'm running ManualNooter 4.6.16 with Dalingrin's 063011 Froyo EMMC kernel. In Nook Color Tools, USB debugging is enabled and auto mount is disabled.
I'm stuck at what to try next. Any thoughts?
i'm having a problem on my mint install, i cant see my Nexus S and i know its rooted, i can allow permissions on Superuser, however, i get this error when i'm trying to see devices
oICS 1.3 is what i'm using
USB Debugging is enabled
Code:
List of devices attached
???????????? no permissions
lsusb sees it fine
Bus 001 Device 078: ID 04e8:6860 Samsung Electronics Co., Ltd
i added the line into 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and restarted udev and i still get ???????????? i have a rooted galaxy that works fine on this pc with ADB.
i even tried re installing SU under recovery. can anyone give me a hand? what am i missing?
Try the following:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb devices
I had the same issue. I tried the kill and restart server and it did not work.
Sent from my Nexus S using xda premium
gangaskan said:
i'm having a problem on my mint install, i cant see my Nexus S and i know its rooted, i can allow permissions on Superuser, however, i get this error when i'm trying to see devices
oICS 1.3 is what i'm using
USB Debugging is enabled
Code:
List of devices attached
???????????? no permissions
lsusb sees it fine
Bus 001 Device 078: ID 04e8:6860 Samsung Electronics Co., Ltd
i added the line into 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and restarted udev and i still get ???????????? i have a rooted galaxy that works fine on this pc with ADB.
i even tried re installing SU under recovery. can anyone give me a hand? what am i missing?
Click to expand...
Click to collapse
Make sure USB debugging is checked in settings and check the stay awake option too.
adb Kill-server
adb start-server
adb devices
give it a shot.
I am using Ubuntu Lucid to connect to my ZTE Blade. Everything was OK. Now I can see the phone using lsusb but the phone's sdcard does not show in /media. I have
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"
in 51-android-rules (in /etc/udev/rules.d)
This has not changed.
However, I now have
# Mass_storage (pci-0000:00:13.5-usb-0:7:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="ZTE_Mass_storage_CM7-Blade-0:1", SYMLINK+="cdrom1", ENV{GENERATED}="1"
in 70-persistent,cd.rules (in /etc/udev/rules.d): this file was modified very recently (but by Ubuntu rather than by me).
Help please!
Do this. Type sudo gedit/etc/udev/rules.d/51-android.rules
Remove this entry.
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"
Edit your user name and add this.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1353", MODE="0660", OWNER="<your user name>" #Normal
SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1351", MODE="0660", OWNER="<your user name>" #Debug
SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1354", MODE="0660", OWNER="<your user name>" #Recovery
Sent from my Blade using XDA app
Done as requested: it did not work.
Have you tried using a different SD card? Which rom are you running?
Sent from my Blade using XDA app
I don't have another sdcard: I'll buy one. I'm using Cyanogen for ZTE Blade. I previously converted Gen1 to Gen2 before installing Cyanogen. I had to reinstall Cyanogen recently as phone refused to boot: I think that there's a fault in the phone/Cyanogen causing this when the battery runs down. However, before Cyanogen reinstall I did not do convert Gen1 to Gen2 as I thought this only had to be done once. Could this be the reason?
PS the phone was recognised by Ubuntu Lucid till yesterday using the android rules file that I previously had. Only change on Ubuntu was that change to the persistent rules files I previously mentioned.
Latest: phone now showing as 1.0 GB disk (i.e. sdcard's contents) under Ubuntu. All I did was to drag down notifications area a& it then gave option to turn USB storage on, which I did. However I would still like to know about the meaning of:
# Mass_storage (pci-0000:00:13.5-usb-0:7:1.0-scsi-0:0:0:1)
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="ZTE_Mass_storage_CM7-Blade-0:1", SYMLINK+="cdrom1", ENV{GENERATED}="1"
in 70-persistent,cd.rules (in /etc/udev/rules.d): this file was modified very recently (but by Ubuntu rather than by me).