Post Reply

adb on linux insufficient permissions

9th June 2010, 11:14 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Feb 2009
I am using linux and I have adb running, but any time I try to send a command to my evo I get

error: insufficient permissions for device

Anyone know what I'm doing wrong?
9th June 2010, 11:36 PM   |  #2  
Senior Member
Flag Detroit, MI
Thanks Meter: 73
 
452 posts
Join Date:Joined: Jun 2007
More
Start the adb server as root. So if you were on Ubuntu, you'd want to run the following command.

adb kill-server (you must do this to kill the user started server)

sudo adb start-server

Or you can basically do any adb command with sudo to start it. I typically use:

sudo adb devices

This starts the ADB server and tells me my phone is definitely hooked up.
The Following 14 Users Say Thank You to sph33r For This Useful Post: [ View ]
9th June 2010, 11:46 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Feb 2009
Thank you. I can't believe I didn't think of that.
10th June 2010, 12:23 AM   |  #4  
timothydonohue's Avatar
Senior Member
Flag Portland, Maine
Thanks Meter: 104
 
1,517 posts
Join Date:Joined: Oct 2007
More
if that's not the deal, it could be that you don't have a rules file set up for it in etc/udev/rules

search the forums for 'adb ubuntu' in the post titles, you find at least a few threads about the rules file you need to make. or, just take the file i made, remove .zip from the end of it, and put it into etc/udev/rules
it has a rule for this device and the nexus i used to have. you'll need to restart udev to get it to recognize. i think the command is just restart udev, lol, but i'm not sure. don't remember exactly. google it. or,
restart your pc
Attached Files
File Type: zip 51-android.rules.zip - [Click for QR Code] (166 Bytes, 1866 views)
The Following User Says Thank You to timothydonohue For This Useful Post: [ View ]
17th September 2010, 01:01 AM   |  #5  
Junior Member
Austin
Thanks Meter: 0
 
3 posts
Join Date:Joined: Jun 2010
so what does it return if your rsa key are hosed?

this is what i got

# grep RSA /dev/mtd/mtd0
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
13th November 2012, 11:22 AM   |  #6  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Oct 2010
Thanks
Quote:
Originally Posted by sph33r

Start the adb server as root. So if you were on Ubuntu, you'd want to run the following command.

adb kill-server (you must do this to kill the user started server)

sudo adb start-server

Or you can basically do any adb command with sudo to start it. I typically use:

sudo adb devices

This starts the ADB server and tells me my phone is definitely hooked up.

Thank you - stupid me didn't think of that
9th August 2014, 12:13 PM   |  #7  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Jun 2007
Thumbs up YEY
Quote:
Originally Posted by timothydonohue

if that's not the deal, it could be that you don't have a rules file set up for it in etc/udev/rules

search the forums for 'adb ubuntu' in the post titles, you find at least a few threads about the rules file you need to make. or, just take the file i made, remove .zip from the end of it, and put it into etc/udev/rules
it has a rule for this device and the nexus i used to have. you'll need to restart udev to get it to recognize. i think the command is just restart udev, lol, but i'm not sure. don't remember exactly. google it. or,
restart your pc

- Dude your a lifesaver. I have no idea wtf udev rules is but that worked perfectly. Stop and started the adb server once rules in place and the device popped up a dialog saying "Allow Debugging" - Success!

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes