Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,220 Members 37,554 Now Online
XDA Developers Android and Mobile Development Forum

Ubuntu No devices permission

Tip us?
 
charkosh
Old
#1  
Member - OP
Thanks Meter 0
Posts: 77
Join Date: Sep 2009
Default Ubuntu No devices permission

How do I fix this issue?
I am a linux n00bie

giovanni@giovanni-laptop:~$ adb devices
List of devices attached
???????????? no permissions
Google Nexus One
T-mobile
Cyanogen 5.X

Retired:
Mytouch 3G
T-mobile
Cyanogen 4.X.X
 
rotohammer
Old
#2  
rotohammer's Avatar
Senior Member
Thanks Meter 1,067
Posts: 1,380
Join Date: Jan 2007
Location: New Jersey
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.
-Rotohammer
T879 Note on T-Mobile
Do not quote my entire first post in a reply!
The Following 2 Users Say Thank You to rotohammer For This Useful Post: [ Click to Expand ]
 
charkosh
Old
(Last edited by charkosh; 1st March 2010 at 05:14 AM.)
#3  
Member - OP
Thanks Meter 0
Posts: 77
Join Date: Sep 2009
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.
Google Nexus One
T-mobile
Cyanogen 5.X

Retired:
Mytouch 3G
T-mobile
Cyanogen 4.X.X
 
DEEsx1
Old
(Last edited by DEEsx1; 1st March 2010 at 11:21 AM.)
#4  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Aug 2009
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"
 
Talderon
Old
#5  
Talderon's Avatar
Senior Member
Thanks Meter 120
Posts: 1,144
Join Date: Sep 2008
Location: Seattle

 
DONATE TO ME
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!
Talderon

_____________________________________________
DEVICE: Nokia Lumia 920 (Yellow)
STATUS: STOCK
ROM: STOCK
NETWORK: AT&T LTE US (Puget Sound Area, Washington)

Professional Web Design
_____________________________________________
DropBox! 2GB Free and can get more space FREE!
Read here: http://db.tt/rJoFjP7
The Following User Says Thank You to Talderon For This Useful Post: [ Click to Expand ]
 
rotohammer
Old
#6  
rotohammer's Avatar
Senior Member
Thanks Meter 1,067
Posts: 1,380
Join Date: Jan 2007
Location: New Jersey
Quote:
Originally Posted by DEEsx1 View Post
There is another Vendor id for NexusOne. "0bb4" is not for Nexus but G1:
You are correct, I didn't realize I had two udev files and I opened the wrong one.
-Rotohammer
T879 Note on T-Mobile
Do not quote my entire first post in a reply!
 
charkosh
Old
#7  
Member - OP
Thanks Meter 0
Posts: 77
Join Date: Sep 2009
thanks for your help! I'll try this out when I get home.
Google Nexus One
T-mobile
Cyanogen 5.X

Retired:
Mytouch 3G
T-mobile
Cyanogen 4.X.X
 
charkosh
Old
#8  
Member - OP
Thanks Meter 0
Posts: 77
Join Date: Sep 2009
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
Google Nexus One
T-mobile
Cyanogen 5.X

Retired:
Mytouch 3G
T-mobile
Cyanogen 4.X.X
 
rotohammer
Old
#9  
rotohammer's Avatar
Senior Member
Thanks Meter 1,067
Posts: 1,380
Join Date: Jan 2007
Location: New Jersey
Quote:
Originally Posted by charkosh View Post
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?
Welcome to Linux!

Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this.

Quote:
Originally Posted by charkosh View Post
and why 51-android.rules? why not 1-android or 5000000-android?
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
T879 Note on T-Mobile
Do not quote my entire first post in a reply!
 
djn541
Old
#10  
djn541's Avatar
Senior Member
Thanks Meter 1,735
Posts: 1,276
Join Date: Oct 2009
Location: Aurora, Co

 
DONATE TO ME
Quote:
Originally Posted by rotohammer View Post
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.
Thanks for this! You're a life saver. Actually a hair saver, I get to quit pulling mine out now!
Phone: Google Nexus 5
ROM: I build my own from CM source
Theme: Stock ATM
Recovery: TWRP
#EUROSKANK!


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Windows Developers Rejoice! Dev Program’s $99 Yearly Fee is No More!

Microsoft rule in the mobile market, much like the giant dinosaurs … more

Add the Xperia Z2 Lock Screen to Your Favorite KitKat ROM

Almost every OEM adds its own unique flair to their stock firmwares. While some of … more

Android App Review: Control Your Phone with Quick Control Panel – XDA Developer TV

Your Android smart device has many features that you … more

Play Music on Android Wear with Stellio Music Player

Android Wear smartwatchesare growing inpopularity every day. Some devices have already … more