[Q] 'adb root' not working - answer inside - Desire Q&A, Help & Troubleshooting

Hy,
i try to get the 'adb root' working but i get this msg 'adbd cannot run as root in production builds'
My desire is rooted by Unrecovered 3 and i installed the new Superuser app. I am S-OFF, lates busybox is running and su in adb shell works. but i don't know why adb root didn't and what to do...
asked google, tried some of the 'answeres' -> nop
Its my first post but i am not a totaly newby
If someone knows what i have missed or have an idea, you are wellcome
Edit:
Ok, my fault - dont understut what "adb cannot run as root in production builds" means...
Have to be in the recovery, not booted up to Android (production build),
in recovery adb starts automaticly as root...
could be closed, thx

Have you got USB debugging enabled?
Mike
Sent from my HTC Desire using XDA App

Yepp is on

I'm not sure what the command 'adb root' does, but have you mounted system, data etc....
Sent from my HTC Desire using XDA App

Is mounted, and everythink i whant to do works exept root for adb.
I like to try out the Android Commander, but it wont get root.
Superuser App asked me and I gave it the root permission but i have checkt out that i have no root for adb. I dont undersant why. Dont noticed it till yet cause did everything with Terminal Emu on my desire, su - remound ops ... everything works. As i understand 'adb root' should restard adb with root permision so you can use the privileged adb commands and that seams to be necesary for android commander to do his job.
Any Ideas why it dont work?

Related

[Q] Help on rooting

Sorry for making you read this if I made a nooby mistake.
So I rooted my Slide, and flashed the Eng-release to it. When I use ROM Manager to install the CM6 onto it, I can't get past touching reboot into Clockwork Recovery. I already flashed the Clowckwork into it (I think; you just need to push the Flash ClockworkMod Recovery button right?), but when I push the reboot into it button, nothing happens.
I tried the Fix Permissions button, and it says "An error occurred while attempting to run privileged commands!" That means that the app doesn't have root access, right? How do I give the app root access? I tried two superuser apps, one from the Market and one from this website, the one with a Ninja. When I choose preferences on the superuser app, it just hangs until I get the Force Close error.
How do I grant my app root access? I know I rooted my Slide because when I connect it to my phone and use adb shell, the pound sing comes up.
What method did you use? Did the phone have the 1.35 OTA Update?
Try this: download terminal emulator from the market, its free.
Turn on: you will see a "$" symbol type "su" (w/o qoutes)
if you see this "#" you are rooted..
Im sure there are easier other ways to check, thats just what I do. I know you didn't install the rom, so don't worry about that yet.
Chances are you arent rooted, I dont what adb shell would say, since I didnt have to use it directly, I just used my windows cmd prompt.
After looking at the other post a few below this one about the exact same problem that I had, I did what he did and copied the update.zip to my phone and booted into recovery. Thanks for the help, though I'm ok now.
Btw, I did have the terminal, and it did have the # sing
Sent from my T-Mobile myTouch 3G Slide using XDA App

[Q] ADB Shell Won't Allow me to run as SU

So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?
adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!
Try clearing data for the SuperUser app?
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?

[Q] Question about Flashing

Hi, I've got a Motorola Defy in Argentina (Carrier: Personal, means telecom). Well, I want to Root it, I've tryied z4mod, the ADB Method, 1 click, etc, and I still got the message "The application xxxx needs root user permissions", btw I have the Root (#) console in "adb shell", but I can't move files to /system/media (whit "AndExplorer" from mobile). Do I have to mount the FS there??
I've got the "Superuser" app working, and some applications whit "Root permissions" (because I've checked Remember my answer on the Popup when the app needs root privilegies)
Im a little bit confused because the version is not similar that you use here.
Version Number: JORLA_U3_6.14.7
Firmware version: 2.1-update1
So, I want to root it, and maybe upgrade to Froyo, but that questions make me scared (specially if i brick it).
What should I do?
PS: I've made a "Backup" with SystemRecovery app. This backup will work if I want to back my firmware to the stock one? (forgive the apps, I don't care).
Nobody can guarantee your backup will work, but it's a risk you'll have to take if you want to hack.
According to my search, your carrier uses UMTS 850 / 1900. This means you could have a different baseband firmware than the T-Mobile users here, and definitely different from the European users. The problem is, the only SBF files available are for European 900/2100.
So first things first, take a nandroid backup from the custom bootstrap recovery if you can get that working. Back up those files somewhere safe.
Read about the "3g fix". There is a folder containing the baseband firmware files, and you'll want to back those up in case you lose 3g on a custom ROM.
If your phone becomes unbootable, you'll have to flash an SBF to boot it, *then* root it again, install custom recovery again, and finally restore the nandroid backup.
Sent from my Nexus One using XDA App
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
cocus said:
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
Click to expand...
Click to collapse
How are you attempting to do this backup?
You need to download the bootstrap custom recovery, and use that to boot into the recovery menu. From there you go into backup/restore.
If you have successfully rooted your phone, then all apps have the opportunity to run as root. They should be able to make the request via Superuser Permissions, which would then prompt you.
Ok, but the bootstrap custom recovery is for 2.51 or similar firmware numbers, I've got 6.14. So, I really didn't test because I don't have experience with this things and I don't want to screw up all.
I tell you, for example, the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
BTW, I've got a root shell on adb (when I reboot the phone, I loose the root ). That means that is rooted??? (Got it using RATC)
Well, either it's compatible or it's not. If the bootstrap makes your phone unbootable... I guess you'll have to try for a warranty claim
Sent from my Nexus One using XDA App
Hahaha, I like to flash things and understand how it works, but in this case, I would prefer not screw nothing. Btw, I've buyed it on 15/jan.
So, for my other question the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
But when I restart the phone, I loose the # on "adb shell".
BTW, I've found the open source code of an earlier version of my defy on
opensource.motorola.com/sf/go/projects.moto_defy/frs.defy_latam
Anyone knowns how to compile this? I've got Debian lenny, Ubuntu 10.04, Ubuntu 10.10.
Thanks
Compiling a ROM yourself won't help if you can't sign it with Motorola's key. Yay locked bootloader...
Sent from my Nexus One using XDA App
Cocus,
I got the same phone as yours. Also from Personal.
And I am on the same situation, want to flash it, but not to brick it.
Let me know if you find out something ...
Hi, yes you can contact me via PM & I will send all the stuff that I've got. But I only get the rootshell via RageAgainstTheCage. When you reboot it you loose it, but you can use "su" or "rootshell" to get it again.
Now Im playing with C and C++ native code, with the ndk and sdk (no java ). Contact me
z4root worked in argentine (Latin American) defy.
Hi
I have a Motorola Defy like yours , (in Argentina - Carrier: Personal ).
I have rooted successfully using z4root 1.3.0 , that you can get from this post (look attached file at end ):
http://forum.xda-developers.com/showthread.php?t=833953
With z4root 1.3 you have the option of get root temporarily or permanent. The first one doesn't works for me ( no errors but no root ). The permanent root yes, works like a charm .
Hi, It seems that is not working for me... I've touched the permanent option, it restarted and the z4root says that is rooted, but I haven't the root console in adb shell, neither the apps run as root.
Edit: If I try to run "su" on the non-root console($) it says "Permission denied". But, running "rootshell" from RATC, it gives me a root shell.

Tried to Root G2 (S-ON)

If on Recovery, it says S-ON, is that a Problem?
triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?
and where would the HTC G2 Drivers have to be installed?
triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip
Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.
yeah I have Superuser Permissions but it FC's when you try to open it
triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?

Help with unrooting

I cannot get a response from the original thread that is stickied so I figured I would ask here. I am currently s-off and on Froyo. Everytime I try to install a ROM it just bootloops. The only one that actually works in Kangdamnation (sp). I would love to do UKB but it bootloops as soon as the lockscreen pops up on first boot. I have the HTC extended battery, althought I doubt that has anything do to with these issues. I have tried to go back to s-on so I can get a new phone sent to me under warranty but am stuck.
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
Once I get to this point the adb will find and show my phone but once i type in the adb root it says "adbd cannot run as root in production builds and if i try to continue to remount it says "remount failed: Operation not permitted"
I have checked to insure that busybox and root was installed with the superoneclick program
Please someone help me. Also, when i type in su to the cmd (i run it as admin) it says not allowed.

Categories

Resources