Database Users

Ubuntu No devices permission

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

ubuntu abd

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

adb not recognizing a500

I'm running Linux and im trying to develop and test apps on my a500, and when I try to adb shell im getting permission errors.

not really helping but... you can allways go the vmware/virtualbox way.....

did u edit the udev rules?

I have a script I use that basically just does:
adb kill-server
sudo adb start-server
(assuming permission errors are on your desktop and not the device.)

You can have a look here http://mlien.net/w0QiUXHLyBR you'll find the udev rules to get adb working

EASY fix. this happened to me too.
goto acer.com filter your way to the iconia page,
click the download tab,
download usb drivers,
disconect iconia/pc,
install drivers,
reboot attach iconia,
cmd adb devices it will now be listed.
__________________________________________________ ______________________
ZTE Blade - Rooted OC 729mh CM7 RC2 V nice
Advent Vega - Rooted OC 1.4gh - Corvous5 rom gorgeous smooth and qqquick
Iconia A500 - Rooted - HComb Sweet
Don't forget to hit the Thanks'o'meter

MJ-12 said:
EASY fix. this happened to me too.
goto acer.com filter your way to the iconia page,
click the download tab,
download usb drivers,
disconect iconia/pc,
install drivers,
reboot attach iconia,
cmd adb devices it will now be listed.
__________________________________________________ ______________________
ZTE Blade - Rooted OC 729mh CM7 RC2 V nice
Advent Vega - Rooted OC 1.4gh - Corvous5 rom gorgeous smooth and qqquick
Iconia A500 - Rooted - HComb Sweet
Don't forget to hit the Thanks'o'meter
Click to expand...
Click to collapse
you should read his post - it's linux.
what you need is this in your udev file (/etc/udev/rules.d/51-android.rules)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="tim" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="tim" #ACER
change tim to your nick
you can get those values via lsusb in your commandline.
restart udev afterwards with: sudo service udev reload
regards,
tim

Opps,
Soz ur right, tbh i just read the title and wanted to help.
__________________________________________________ ______________________
ZTE Blade - Rooted OC 729mh CM7 RC2 V nice
Advent Vega - Rooted OC 1.4gh - Corvous5 rom gorgeous smooth and qqquick
Iconia A500 - Rooted - HComb Sweet

Thanks all!
It worked.

MJ-12 said:
Opps,
Soz ur right, tbh i just read the title and wanted to help.
Click to expand...
Click to collapse
it may have not been useful to OPs problem, but it certainly helped mine thanks

seraphimserapis said:
you should read his post - it's linux.
what you need is this in your udev file (/etc/udev/rules.d/51-android.rules)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3325", MODE="0666", OWNER="tim" #ACER
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0502", ATTRS{idProduct}=="3341", MODE="0666", OWNER="tim" #ACER
change tim to your nick
you can get those values via lsusb in your commandline.
restart udev afterwards with: sudo service udev reload
regards,
tim
Click to expand...
Click to collapse
Thanks I been looking for this.. I Just got a tablet yesterday. Any Idea how to get it to show up as a mountable device under linux?

That's tricky because it identifies itself as an MTP (Plays-for-sure) device, not a USB storage device . MTP devices can be mounted using the mtpfs fuse driver. Search for mtp mtpfs and mount and you'll eventually find what you're looking for.

mrvanes said:
That's tricky because it identifies itself as an MTP (Plays-for-sure) device, not a USB storage device . MTP devices can be mounted using the mtpfs fuse driver. Search for mtp mtpfs and mount and you'll eventually find what you're looking for.
Click to expand...
Click to collapse
Thanks.. That did it.

ubuntu 11.04 with galaxy 9000

any idea how to conect the galaxy 9000 with adb and my pc runing ubuntu 11.04
i have put SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" but i don't have any conection.

I'm on natty, no need to edit fstab at all, it's mounted automatically.
But I cant do usb tethering

try "sudo adb devices"
works fine in Debian

[Q] ADB troubles on Kubuntu Natty

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?