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

(how to) adb for noobs, by a noob

This instructional piece is brought to you by a complete noob. Please be aware that this is simply telling how I got ADB to work on LinuxMint 10 Julia. Some of the steps may be unnecessary but since I am a noob, I took bits and pieces of info and advice to finally accomplish my mission. The main reason I am writing this is because a lot of the tutorials I found are not written for people new to Linux like myself and I found myself confused by simple instructions because I was unfamiliar with some basic terminal commands.
The first thing I did is watch this video on youtube.com. The instructions I am about to give for installing the SDK comes from here.
http://www.youtube.com/watch?v=t8UREMU-wSU
This video walked me through step by step how to install the Android SDK in Ubuntu. Since LinuxMint is a derivative of Ubuntu, it worked perfectly.
The first thing to do is go to this link and download the SDK for Linux.
http://developer.android.com/sdk/index.html
Then move the file to your home folder. Open a terminal and first “cd” to your download folder. Then move the file as follows: ( please be aware that anywhere you see “tombepa”, replace it with your username)
[email protected] ~ $ cd Downloads
[email protected] ~/Downloads $ mv android-sdk-linux_x86.tgz /home/tombepa
After you have moved it, you must unzip it. This is done with the “tar” command. First you must be in your home folder within the terminal because that is where the file is. After you moved the file, your terminal will still be in the Downloads folder and look something like this:
[email protected] ~/Downloads $
Simply type “cd” without the quotes and press enter to return to the home folder:
[email protected] ~/Downloads $ cd
[email protected] ~ $
Then type in the “tar” command and press enter to unzip the file:
[email protected] ~ $ tar xvf android-sdk-linux_x86.tgz
You will then see a lot of lines of text as it unzips. This will create a folder within your Home folder named “android-sdk-linux_x86” and it will contain all the contents it needs for now. It is then safe to remove the android-sdk-linux_x86.tgz file itself from the Home folder. If it is the only .tgz file in the folder then you can type this and press enter. It will remove all .tgz files from the Home folder.
[email protected] ~ $ rm *.tgz
Now it is time to start the SDK and download the packages for Android Development. Now I am not sure if this is needed just to get ADB to work, but once again, I am a noob and was just going by the instructions. In the terminal, you must enter the newly created folder by typing:
[email protected] ~ $ cd android-sdk-linux_x86/
Now that you are in the folder, type this to start the SDK:
[email protected] ~/android-sdk-linux_x86 $ tools/android
A fews lines of text will come up and then after about 5 seconds the SDK graphical interface will open.
This can be seen in the video. On he left side, click the option that says “Available Packages.” Then click “Android Repository” in the middle of the screen. Once you have clicked that, it will automatically select all packages. I left it that way and clicked “Install Selected.” This took about 15 minutes to complete. Once again, probably overkill to install everything, but whatever.
From there I was graced with a link from CondemnedSoul to set up ADB. The link was:
http://wiki.cyanogenmod.com/index.ph...he_Android_SDK
This wasn't exactly the right page I was looking for, but in bold print, it said for ADB go here:
http://wiki.cyanogenmod.com/index.php?title=ADB
(I left the first link in because it gave good info as well on installing the SDK. So thanks CondemnedSoul on pointing me in the right direction!)
It instructed me to download a file linux_adb_fastboot.zip and extract it to ~/bin. After learning how to do that, I typed:
[email protected] ~/Downloads $ unzip linux_adb_fastboot.zip -d ~/bin
What does it do? I don't know, just following orders.
Then it said I needed to set up udev. This apparently gives me and you the permission to use adb on the android device. There has to be rules written and permission given that the computer and the phone recognizes. The first thing to do is create a file called “51-android.rules” in this directory: /etc/udev/rules.d/
Since I can't remember which step actually worked to create the file. Here is the link I was using. I used them all because I did not really know what I was doing but it worked. If anyone can be more specific on how to create it, please enlighten me and I will amend this and give you credit of course.
http://forum.androidcentral.com/linux/57132-how-set-up-udev-rules-ubuntu-10-10-a.html
After it was created, I had to put all the rules in place. After using the instructions on setting up udev from Cyanogen, I came up with these rules. I put them in the file I created by using Nautilus to go to the file, right click on it, then select “Open as Administrator.” I do not know how to do it from the terminal, sorry.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0c98"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0ff9"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", OWNER="tombepa" GROUP="tombepa"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0c98"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0ff9"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", OWNER="tombepa" GROUP="tombepa"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", USER="tombepa"
(Once again, wherever you see “tombepa”, replace it with your username.)
Click save, then exit all programs and reboot your computer.
Plug the phone in and open a terminal. Navigate to the tools folder inside the android-sdk-linux_x86 folder by typing:
[email protected] ~ $ cd android-sdk-linux_x86/
[email protected] ~/android-sdk-linux_x86 $ cd tools
[email protected] ~/android-sdk-linux_x86/tools $
Then to test to see if it is working, type:
[email protected] ~/android-sdk-linux_x86/tools $ adb devices
If it says;
List of devices attached
HTXXXXXXXXXX device
And the X's are actually numbers, then there you have it! ADB is working.
From there I was able to push my very first apk straight to my phone. With some help from Busphan, I was directed to save the apk I wanted to the “tools” folder, then type:
[email protected] ~/android-sdk-linux_x86/tools $ adb push WHATEVER.apk /system/app
The first several tries it did not work. I then read some more and one website suggested to type:
adb kill-server
adb start-server
adb devices
adb remount
adb push WHATEVER.apk /system/app
I knew it had worked this time because after the last line, a line of text came up telling me how large the file was that was moved. Then I rebooted the phone by typing:
adb reboot
And there it was. Thank you one again to Tazzpatriot, CondemnedSoul, all the devs out there that put this stuff on the internet and youtube for us to learn, and especially Busphan for seeing me through the last steps.
Once again, if you guys see somewhere for me to be more clear about something, tell me what to fix and I will amend this post and give you credit.

Awesome job man, I will definitely check this out, as I'm in the process of replacing ubuntu with mint 10 to try it out. This will come in handy to set up sdk and adb. Thanks for posting this.

Thank you, I'll add the thanks and check it out when I get home
Sent from my phone, duh

Just finished installing Mint 10. I will post again after I run through the sdk advanced process.
Sent from my Ginger Tazz using XDA App

Busphan said:
Just finished installing Mint 10. I will post again after I run through the sdk advanced process.
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
When you get to the part about creating the File in udev for rules, if you can help me polish it up a bit, I am sure others would appreciate it.
Sent from my Droid using XDA Premium App

tombepa said:
When you get to the part about creating the File in udev for rules, if you can help me polish it up a bit, I am sure others would appreciate it.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
Well, all went well, except we I got to the tools/android command. I kept type cd tools/android, lol. As for the udev portion that is beyond me, but I just followed the commands in the link and it worked. Although, I didn't do the extra stuff you said with nautilus. I wish I had some more input to "polish up" the udev portion but if folks follow the link it will be fine. So my thoughts are you wrote very good instructions to get adb working on Mint or Ubuntu. Again great job. Now all I have to do is go back in and set up eclipse.

Just a quick tip, most of the time when you are typing on a command line, such as the cd command, you can let the shell auto-complete the line by pressing tab. For example, when the active directory is your home, you can start typing cd andr and then press the tab key and it may/should automatically fill in the rest for you (cd android-sdk-linux_x86/.)

doogald said:
Just a quick tip, most of the time when you are typing on a command line, such as the cd command, you can let the shell auto-complete the line by pressing tab. For example, when the active directory is your home, you can start typing cd andr and then press the tab key and it may/should automatically fill in the rest for you (cd android-sdk-linux_x86/.)
Click to expand...
Click to collapse
Thanx for the tip. Tgat does make it go faster and have less mistakes
Sent from my Droid using XDA Premium App

Thanks for the guide, i got it working, once i remembered it was abd instead of adb lol... i'm a noob still

[Q] Setting up ADB on nook with Ubuntu

Hey everyone, I'm a big newb when it comes to Ubuntu. I got into it because I wanted an OS that was as open as CM7, and so far it's great! I was trying to install ADB on my computer and I was using the link http://forum.xda-developers.com/showthread.php?t=921169. I got JDK installed, and sdk, its about step 4 that I get lost. In terminal when I put in $ ./adb devices it doesn't list any devices. I might be wrong, but I think it needs to recognize my nook as a adb device before I can do anything else. Am I missing a step? Any help would be great!

actorman46 said:
Hey everyone, I'm a big newb when it comes to Ubuntu. I got into it because I wanted an OS that was as open as CM7, and so far it's great! I was trying to install ADB on my computer and I was using the link http://forum.xda-developers.com/showthread.php?t=921169. I got JDK installed, and sdk, its about step 4 that I get lost. In terminal when I put in $ ./adb devices it doesn't list any devices. I might be wrong, but I think it needs to recognize my nook as a adb device before I can do anything else. Am I missing a step? Any help would be great!
Click to expand...
Click to collapse
Follow the steps from Nookdevs.com here http://nookdevs.com/NookColor_USB_ADB
In your case, since you have everything setup. Make note specifically to run this command from the link posted above:
Ensure that your rooted NOOKcolor is plugged in.
Run the following command in terminal:
Code:
mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices
If you get output that looks like the following you have succeeded:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[YOUR NOOKCOLOR SN] device
-Racks

racks11479 said:
Follow the steps from Nookdevs.com here http://nookdevs.com/NookColor_USB_ADB
Click to expand...
Click to collapse
okay on step 4 it says to edit your .bash_profile, by putting the command in terminal
nano ~/.bashrc
then append these lines at the end and save the file.
export PATH=${PATH}:<your_sdk_dir>/platform-tools
I'm not sure what it's asking me to do. After putting in nano ~/.bashrc do I just scroll to the bottom and add that line? And if that's it, how do I save it?
Told you I new! But thanks for showing me the right link.
Oh, that command you told me to pay attention to doesn't work for me but when I type in
$ cd ~/android-sdk-linux_x86/platform-tools
[email protected]:~/android-sdk-linux_x86/platform-tools$ ./adb devices
it now lists my device with permission, the same way that command was supposed to.
I just need help setting my path in bashrc!

actorman46 said:
okay on step 4 it says to edit your .bash_profile, by putting the command in terminal
nano ~/.bashrc
then append these lines at the end and save the file.
export PATH=${PATH}:<your_sdk_dir>/platform-tools
I'm not sure what it's asking me to do. After putting in nano ~/.bashrc do I just scroll to the bottom and add that line? And if that's it, how do I save it?
Told you I new! But thanks for showing me the right link.
Oh, that command you told me to pay attention to doesn't work for me but when I type in
$ cd ~/android-sdk-linux_x86/platform-tools
[email protected]:~/android-sdk-linux_x86/platform-tools$ ./adb devices
it now lists my device with permission, the same way that command was supposed to.
I just need help setting my path in bashrc!
Click to expand...
Click to collapse
1. Yes, just scroll to the bottom and add 'export PATH=${PATH}:~/android-sdk-linux_x86/platform-tools/platform-tools' to the file.
2. Once you add the path, to save and exit. Press 'Control' and 'X'. It will give you an option to save changes. Type in "Y" and then press "Enter"
3. After you save the file you have to run:
Code:
$ source ~/.bashrc
That should now set the correct path to your SDK tools. You might have to restart terminal for it to take effect.
-Racks

[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?

ICS and mint 11 64 problem seeing with ADB

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.