Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

adb insufficient permissions


  • Please log in to reply
10 replies to this topic

#1 Raim1312

Raim1312
  • Members
  • 4 posts
  • Twitter:raim1312
  • Country:
    us - United States
  • Location:
    RI
  • Device Model:
    |1|
  • CM Version:
    CM 6.0.0 RC1
  • Recovery Image:
    ClockworkMod

Posted 22 July 2010 - 12:58 AM

I've had a MT3G for awhile and just upgraded to a Nexus One. I still have my old phone and can use adb with the MT3G without any issues. When I try using adb with the Nexus one i receive an error insufficient permissions on the device. Here's some more info about my setup:
Nexus One:
Clockwork Mod Recovery
CM6.0.0RC1
USB debugging is enabled

Computer:
Ubuntu 10.04
I have the rules set up for adb

I have tried remounting and restarted adb with root permissions and have still receiving the same error. I've tried connecting to another Ubuntu box and a windows xp box with the same error.
Any help?

#2 mzsigler

mzsigler
  • Donators
  • 65 posts
  • Country:
    us - United States
  • Location:
    38103/91360
  • Device Model:
    Galaxy Note
  • CM Version:
    Waiting for one
  • Recovery Image:
    ClockworkMod

Posted 22 July 2010 - 05:58 AM

Do you mean adb shell? Or just normal adb? When you type "adb devices" in terminal, does your device show up?

#3 CiDhed

CiDhed
  • Donators
  • 347 posts
  • Twitter:cidhed
  • Country:
    us - United States
  • Location:
    Missouri
  • Device Model:
    Evo3d,N1,G1
  • CM Version:
    Nightlies or Alphas.
  • Recovery Image:
    Amon_RA

Posted 22 July 2010 - 10:57 AM

On my g1 I could just use adb as a normal user but on my n1 I have to sudo ./adb kill-server and sudo ./adb start-server

#4 Raim1312

Raim1312
  • Members
  • 4 posts
  • Twitter:raim1312
  • Country:
    us - United States
  • Location:
    RI
  • Device Model:
    |1|
  • CM Version:
    CM 6.0.0 RC1
  • Recovery Image:
    ClockworkMod

Posted 23 July 2010 - 01:54 AM

When i run adb devices i receive this:

List of devices attached 
????????????	no permissions

adb shell gives this:

error: insufficient permissions for device

I receive the same output running the commands as user or superuser. I've also killed and started the server as user and root. Remember I'm running the udev rules so I can run these commands as user.

Today I went ahead and reflashed my phone. I downloaded cm6 from xda and frf91 from the same post. Checked the md5sum for the update and then wiped and flashed.
Even after the wipe I'm in the same spot.

#5 Raim1312

Raim1312
  • Members
  • 4 posts
  • Twitter:raim1312
  • Country:
    us - United States
  • Location:
    RI
  • Device Model:
    |1|
  • CM Version:
    CM 6.0.0 RC1
  • Recovery Image:
    ClockworkMod

Posted 23 July 2010 - 02:32 AM

another update. when fully loaded into the rom fastboot doesnt work. but when i boot into recovery fastboot finds the device.

#6 Raim1312

Raim1312
  • Members
  • 4 posts
  • Twitter:raim1312
  • Country:
    us - United States
  • Location:
    RI
  • Device Model:
    |1|
  • CM Version:
    CM 6.0.0 RC1
  • Recovery Image:
    ClockworkMod

Posted 23 July 2010 - 03:02 AM

i was working with codesplice over on xda. still not resolved but heres the most recent update:
http://forum.xda-dev...ad.php?t=732698

#7 mzsigler

mzsigler
  • Donators
  • 65 posts
  • Country:
    us - United States
  • Location:
    38103/91360
  • Device Model:
    Galaxy Note
  • CM Version:
    Waiting for one
  • Recovery Image:
    ClockworkMod

Posted 23 July 2010 - 05:48 AM

View PostRaim1312, on 23 July 2010 - 02:32 AM, said:

another update. when fully loaded into the rom fastboot doesnt work. but when i boot into recovery fastboot finds the device.

That's normal. Fastboot only works in bootloader.

#8 galv0nix

galv0nix
  • Members
  • 12 posts
  • Twitter:techguytim
  • Country:
    us - United States
  • Location:
    San Diego, CA, USA
  • Device Model:
    HTC Magic 32B
  • CM Version:
    CM 6 nightlys
  • Recovery Image:
    ClockworkMod

Posted 03 November 2010 - 04:47 AM

Having same issue.

Linux Mint 10 (a prettier version of Ubuntu 10.10)
current adb, clockwork, CM 6.1RC1
not a linux newbie

#9 CiDhed

CiDhed
  • Donators
  • 347 posts
  • Twitter:cidhed
  • Country:
    us - United States
  • Location:
    Missouri
  • Device Model:
    Evo3d,N1,G1
  • CM Version:
    Nightlies or Alphas.
  • Recovery Image:
    Amon_RA

Posted 03 November 2010 - 02:14 PM

Have you tried running the start server as a super user?

#10 1n73rn37_j3d1

1n73rn37_j3d1
  • Members
  • 4 posts
  • Twitter:@zdziura
  • Country:
    us - United States
  • Location:
    Plymouth, NH
  • Device Model:
    Samsung Fascinate
  • CM Version:
    Stock
  • Recovery Image:
    ClockworkMod

Posted 18 November 2010 - 04:23 PM

I realize that this thread is semi-old, but I stumbled upon it while doing a Google search, trying to find a solution for the same problem. I had previously rooted my Samsung Fascinate on a Windows machine, then switched over to using Ubuntu Linux. I set up my Android development environment properly, following Google's instructions, but I couldn't use adb for some reason. I was getting the "insufficient permissions for device" error. When doing "./adb devices", my display would look like:

List of devices attached 
????????????	no permissions

How do you fix this?

1) Go into super user:
sudo su
2) Navigate to the tools directory in the Android sdk:
(in my case) cd ~/android-sdk/tools
3) Restart the device server:
./adb kill-server ./adb start-server (thank you CiDhed for posting this!)
4) Profit

Again, I'm sure that there are a lot of people who know how to do this already, but for those like me who have limited Linux/Android experience, it's always nice to have a step-by-step guide to doing anything... At least at first ;)

#11 temasek

temasek
  • Donators
  • 3345 posts
  • Twitter:temasek71
  • Country:
    sg - Singapore
  • Device Model:
    Nexus One / O2X
  • CM Version:
    CM7.2.0 RC0 SelfKANG
  • Recovery Image:
    Amon_RA

Posted 18 November 2010 - 04:32 PM

Deleted