Database Develop

adb insufficient permissions

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?

What response (if any) do you get to the "adb devices" command?
What exact command are you trying to execute when you get that error?

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.

Can you access the device via fastboot?

When I first got the device I used fastboot to unlock the bootloader.
now the command
Code:
fastboot reboot
hangs at
Code:
< waiting for device >
I can still reboot the device into recovery and fastboot.

another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.

last thoughts, as it's been a while since I've used adb on Ubuntu...
Code:
./adb kill-server
./adb start-server
./adb devices
???
./PROFIT
It seems to be somehow an issue with your local adb set up, not anything phone-related. Could even perhaps be a driver issue.

raim1312 said:
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
Click to expand...
Click to collapse
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL

i get the same results after killing and starting adb either as user or root. i'll pull out the drivers and android sdk and reinstall. i'll let you know how it goes once its done

codesplice said:
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
Click to expand...
Click to collapse
Yeah sorry about that one. i'm still a newb but willing to learn

i just reinstalled the android sdk and removed the udev rules. gave my pc a reboot and killed then started the adb server.
same issue.
to verify adb was working i plugged my gf's mt3g in and adb found it.
i've never need to reinstall usb drivers in anything but windows so honestly I don't know how to do it in ubuntu. can you point me in the right place?

I'm afraid I'm out of ideas then. I've only had very limited experience using adb on my Ubuntu install

well thanks for all the help codesplice.
i'll keep looking and post anything i do here.

raim1312 said:
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
Click to expand...
Click to collapse
Please do. Everything that I was able to find on google relates to a screwy adb server... but being able to adb on another device complicates things. Very interested to see what you figure out on this.

I installed the rom froyou frf50 with radio from here:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
didn't work.
while looking into returning the phone to stock i received an ota update. so i ran it.
the update failed during a signature check.
i tried to follow the instructions here to return to stock: http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
only issue is fastboot will not find my device.
performed a nandroid restore to go back to cm6 frf91.
fastboot still will not find my device.
i'm at a loss here. the device is usable for everything but adb. and adb is the main thing i need. i dont' want to keep whacking at this and cause more issues.
any ideas are welcome. all my data is backed up and the bootloader is already unlocked.

its... working??? i finally got adb to recognize my device.
first i restored the phone back to stock using this: http://forum.xda-developers.com/showthread.php?t=717870
then i replaced the cable i was using for one from a Motorola droid. (since the mt3g has a different usb port i had to use a different cable).
then i ran the adb kill and start server commands as root. and voila. it works.
i remove the cable and go back to the one that came with the phone and it still works. not sure what happened but adt is working as well. so im back up and running. i wish i knew the cause of this frustration but i fear i will never know. anyway thanks for all your help!

Yikes.... take your boat back!!!
Perhaps you ran chmod u+s on adb?
Edit: Yep, that was the problem for me..
I don't know the commands to well, so i just right clicked adb and went to permissions and removed set uid.
seems adb needs started from root, but making the file always run as root doesn't work so well.. I thought it would fix my annoyances with eclipse starting adb with not enough permissions. Perhaps ill chmod u+s eclipse instead.
Oh and btw... nexus one can kiss my a$#. HTC Hero!!

Solution for permission problems:
http://wiki.cyanogenmod.com/index.php?title=Udev

[Q] Need help with my semi-broken NC - what did I do wrong?

I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...

Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.

z4root will work and install superuser for you.

mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.

Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted

This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.

axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...

gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.

axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.

gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?

norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.

gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.

johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!

[Q] Nexus one bricked :( and lost recovery mode

can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (

I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.

justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me

http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide

but my phone cant connect with PC, atlthough i installed google usb driver.

i might be wrong but cant you just flash a original ruu, than root and reinstall recovery

#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.

hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217

#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone

hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?

baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip

You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk

And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.

[Q] Can't get past Recovery Mode - Need Help!

After rebooting for a cyanogenmod update which failed to install, my phone will not boot into Cyanogenmod - only clockwork.
I have precious data on the phone that I need to extract, mainly pictures.
ADB only recognizes the phone as "offline" and I cannot pull any files from it.
Any suggestions? Thanks a lot guys.

icer22x said:
After rebooting for a cyanogenmod update which failed to install, my phone will not boot into Cyanogenmod - only clockwork.
I have precious data on the phone that I need to extract, mainly pictures.
ADB only recognizes the phone as "offline" and I cannot pull any files from it.
Any suggestions? Thanks a lot guys.
Click to expand...
Click to collapse
did you cleared cache?
When you are trying to use adb your phone is in cwm recovery?

alray said:
did you cleared cache?
When you are trying to use adb your phone is in cwm recovery?
Click to expand...
Click to collapse
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.

icer22x said:
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.
Click to expand...
Click to collapse
Do you have a nandroid backup on your phone?
Also is all your drivers properly set and updated on your cumputer? Can you post a screenshot of Windows devices manager with the phone info?
Are you using the original usb cable? Some usb cables only have GND and 5V pins (no data). Also be sure to use usb 2.0 and a usb port directly from your motherboard (not in front of your computer) and don't use any usb hub.

Well I got it recognized by ADB now.
What is the file structure like in order to pull files from the phone?
What commands can I use in ADB to pull the main sd directory?

icer22x said:
Yes I've cleared the cache and rebooted with the same results - just boots back into Recovery Mode.
And yes, when I am using ADB I am in Recovery Mode. I can't get past that.
Click to expand...
Click to collapse
oh and when you are in bootloader, is fastboot working?
Code:
fastboot devices
does it says fastboot usb or only fastboot (in red)
I nerver used adb to pull files so idk. Maybe somthing like ''adb pull /sdcard/ C:\something'' ?
maybe you can find here
or use twrp to make a backup of your data, then pull the backup to your computer

alray said:
oh and when you are in bootloader, is fastboot working?
Code:
fastboot devices
does it says fastboot usb or only fastboot (in red)
I nerver used adb to pull files so idk. Maybe somthing like ''adb pull /sdcard/ C:\something'' ?
Click to expand...
Click to collapse
Thanks man. That helped.
If anyone ever finds themselves in this situation, make sure your SDK packages are updated to the latest Android OS version. This is why ADB was recognizing my device as offline.
Also, running the command adb pull /sdcard/ C:<somewhereonyourPC> will pull all the data from your HTC one.

icer22x said:
Thanks man. That helped.
If anyone ever finds themselves in this situation, make sure your SDK packages are updated to the latest Android OS version. This is why ADB was recognizing my device as offline.
Also, running the command adb pull /sdcard/ C:<somewhereonyourPC> will pull all the data from your HTC one.
Click to expand...
Click to collapse
oh nice to see adb pull /sdcard/ C:<somewhereonyourPC> was the right syntax :laugh:
For the sdk packages you should always make sure it is updated before doing anything to the phone. Same for drivers. An ''adb devices'' and ''fastboot devices'' won't hurt before messing with the phone to make sure everything set correctly.
Now I presume you'll be ok to flash your rom again?1

[Q] Need Help With Recovering After Modifying build.prop

I've a rooted Nexus 6 running Lollipop 5.1. I edited /system/build.prop in an attempt to get Miracast working. I added the following line:
persist.debug.wfd.enable=1
However, now my phone won't boot. It's stuck at the "Google" screen. I think the permissions on build.prop are wrong but when I try to connect with adb via USB, my computers don't recognize the device. I press volume down + power and then plug the phone in. Nothing comes up when I issue ./adb devices. I've tried on both a Windows 7 desktop and a Macbook.
Am I missing something with adb and my connection procedure? Am I just hosed? Is there any way to get this device running again, even if it means a factory reset?

EvaUnit02 said:
I've a rooted Nexus 6 running Lollipop 5.1. I edited /system/build.prop in an attempt to get Miracast working. I added the following line:
persist.debug.wfd.enable=1
However, now my phone won't boot. It's stuck at the "Google" screen. I think the permissions on build.prop are wrong but when I try to connect with adb via USB, my computers don't recognize the device. I press volume down + power and then plug the phone in. Nothing comes up when I issue ./adb devices. I've tried on both a Windows 7 desktop and a Macbook.
Am I missing something with adb and my connection procedure? Am I just hosed? Is there any way to get this device running again, even if it means a factory reset?
Click to expand...
Click to collapse
Do you have a custom recovery? If so, you can adb push a stock build.prop to /system after mounting /system in recovery (think it's adb shell mount /system). Your other option is to use fastboot and flash system.img. It would be best to use whatever 5.1 build you are on. I would think you'd be able to boot fine after just flashing system.img, but you could also erase cache and userdata if it doesn't. Whatever you do, don't lock your bootloader, at least until you know you can boot up normally.

mwalt2 said:
Do you have a custom recovery? If so, you can adb push a stock build.prop to /system after mounting /system in recovery (think it's adb shell mount /system). Your other option is to use fastboot and flash system.img. It would be best to use whatever 5.1 build you are on. I would think you'd be able to boot fine after just flashing system.img, but you could also erase cache and userdata if it doesn't. Whatever you do, don't lock your bootloader, at least until you know you can boot up normally.
Click to expand...
Click to collapse
It's stock recovery. I'll give fastboot a try.

Worked like a charm. I don't know why I didn't think of it last night. I was so fixated on that file, heh. Thanks a bunch, man!