[SOLVED] Lost Root Access?? [LOCK REQUEST] - G1 Q&A, Help & Troubleshooting

Mod lock this thread! I decided to downgrade my SPL back to stock HBOOT-0.95.0000 and flash DREAM.nbh, so now I'm at a stock G1 running Android V1.0 the speed is amazing now lol. Going to root it again tomorrow k?, cya.
I don't know how, but I lost my root access. When I open Terminal on my phone, and type "su", it does not give the "#", which means I don't have root anymore. I don't know what to do, I'm running Cyanogenmod 6.1.0 RC1, DangerSPL is installed (HBOOT-1.33.2005), and my radio is 2.22.23.02 (T-Mobile USA).
What can I do to get my root access back?? Please help me. I'm running a Custom ROM w/o root access anymore!
EDIT: Okay, when I type "su", I now get the "#", so does that mean I have root again?
EDIT2: Whenever I type "cd /system", it does not let me go through... do I not have root??
EDIT3: Yeah, I don't think my phone isn't rooted anymore.. whenever I try to do the commands to gain root access, it gives errors saying (are you root?)
EDIT4: Damn it I'm getting pissed. When I type su, it gets the #, but when I type "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system," it does not work and gives me a "mount: permission denied (are you root?)"
Somebody give me advice please.

What do you expect from a plain old 1.0 Android ROM? You do not have root, but ... you can gain it back easily. Follow the "standard" rooting tutorials.
One suggestion to all: read first, then flash.
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

Related

adp1 seems unrooted after update to crb43

Hello All and thank you for the amazing work going on.
This question might have been answered, but I didn't found it.
I bought the dev phone at google and updated it to cupcake following this which is solely intended for adp1 :
http://www.htc.com/www/support/android/adp.html
Here are the versions installed :
Baseband : 62.50S.20.17H_2.22.19.26I
Kernel : 2.6.27-00393-g6607056 [email protected] #1
Build : dream_devphone-userdebug 1.5 CRB43 148830 test-keys
from my computer, when getting the prompt after the command "adb shell", I can type su and I don't get any error message ; it seems I can root to it.
But on the other hand, from the app Terminal Emulator on the phone, when typing su I get the error message "su: uid 10046 not allowed to su"
Do you know what's wrong if any, and if I am really root ?
And if not, how to get to it?
Thank you
guyiom
did u use the tmobile cupcake us release? if you did, that rom is not rooted and you should use a rooted cupcake rom like CyanogenMod or JF. I suggest CyanogenMod
Use adb and input the following
adb remount
adb shell
mount -o remount,rw /dev/block/mtdblock3 /system
cat /system/bin/sh > /system/bin/su
chmod 4755 /system/bin/su
You're welcome
in fact as I posted, I said it seems to be rooted from adb but not from device itself. the update I used was provided by HTC only for the dev phone (it is explicitely said not for tmo g1)
anyway what dif between JF and Cyanogen ?
I already donloaded JF 1.51 one. How to apply it (or cyanogen) then ?
Thank you for the quick reply
guyiom
DOHCtor you ROCKS !!!
you just forgot to mention after the adb shell to go to root by su
then all commands went fine
as I like to understand, do you know the reason I had these symptoms ( root in adb but not on device) ?
again thank you very much.
as of ever, nux communities are reliable
guyiom
guyiom said:
DOHCtor you ROCKS !!!
you just forgot to mention after the adb shell to go to root by su
then all commands went fine
as I like to understand, do you know the reason I had these symptoms ( root in adb but not on device) ?
again thank you very much.
as of ever, nux communities are reliable
guyiom
Click to expand...
Click to collapse
They were trying to patch a hole without covering it up completely for the dev phones. Just a security thing I'm guessing.
but the update was for rooted pĥones, so that's weird from htc.
anyway thank you again, from now I will document myself to get JF or Cyanogen.
From your signature you seems to have both, one for recovery, one for running. Can you tell me the differences between them ?
thank you
guyiom
Cyanogen's Recovery Image is amazing and will make your life a lot easier. I suggest using that instead of the JF recovery image. As for the ROM it self. i also suggest cyanogenMOD since its the fastest and probably the most stable in my eyes.
Hi and thank you for the reply,
So are you suggesting me to download this file : http://code.google.com/p/android-roms/downloads/list/cyanogen_JFv1.51_CM3-ADP.zip and rename it to update.zip to go to the process with Power + Home buttons ?
Thank you
guyiom

[Q] stuck rooted HELP! Nexus One

I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
Yes. Searching the forums for the various ways how to root 2.2.1
The problem is that it already says that I am rooted. But any app that requires root says that I'm not. I think it might have to do with being rooted with androot while the update happened. I want to try to avoid factory resetting the phone if possible.
doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
I have the same problem. I tryed to restore to my 2.2 backup i made on rom manager before updating to 2.2.1 but it do not work.
nexusdue said:
Yes. Searching the forums for the various ways how to root 2.2.1
Click to expand...
Click to collapse
No research ... no gain.
it may say it but you dont.. why it says it cause it still sees the su in xbin and superuser in app.. but if you read the 2.2.1 update it did remove everything with root.. which sucks.. i have instructions on how to root 2.2.1 with rage..
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
$chmod 700 /data/tmp rageagainstthecage
exit
go to sdk/tools
/tools>freenexus.bat
adb shell
$cd data/local/tmp
ls
check if all files are in
rage
su
Superuser.apk
busybox
$./rageagainstthecage
743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
DONT TYPE ANYTHING TILL YOU HERE THE ADB ON PHONE RESTARTS.
C:/adb kill-server
C:/adb start-server
adb shell
#
should get pound sign if not run ragecage again and dont do anything to you here the last ding on computer
#cd /data/local/tmp
#./busybox cp busybox /system/bin/
(if get read-only error do this
mount -o remount,rw /dev/block/mtdblock3 /system)
#chmod 4755 /system/bin/busybox
#./busybox cp Superuser.apk /system/app
#./busybox cp su /system/bin/
#chmod 4755 /system/bin/su
#exit
if $ type exit again
then go into terminal on phone, and type su
if you get the # you have root once again! yay!
now to install busybox command
hope this will help you to get root back..
i found this so this may work for you and easier to do
http://forum.xda-developers.com/showthread.php?t=803682
I have done both the rageagainstthecage to see how hard it would be but if you follow step by step, you'd be fine. I have also upgraded to 2.2.1 and tried SOC and that works as well. After I used SOC, I reverted back to 2.2 and loaded Rod's Rom again. I was curious
What is SOC and how did you get back to 2.2?
Sent from my Nexus One using XDA App
Super One Click root, I believe.

Need help from botched root attempt.

GRRRRR SuperOneClick breaks it also
I hate posting a question, but I've exhausted searching for an answer.
I have a G1 that i am trying to root in order to flash, I made the mistake of using ANDROOT because it said it worked for G1. Well it said it rooted my phone, but I think it botched something internally because I can't actually get root access.
I then attempted to use the SUPERONECLICK and it ran through the whole proccess and failed when it did a test command at the end to send a SU request.
I then tried some other things to flash clockworkmod recovery with no success.
Now when I attempt to access root in terminal I get...
"371 could not load needed library 'libbinder.so' for 'su' (lLibrary 'libbinder.so' not found)CANNOT LINK EXECUTABLE"
I'm not an idiot, I've rooted and flashed both the NEXUS ONE and CAPTIVATE many times problem free, but this has now got me stumpped and I've searched to no avail. Any help is appreciated.
I'm having the same problem.
Path I took was a bit different, just got here from WM some Linux exp not much.
I tried universal androot
It said it worked. But it didn't.
Then SuperOneClick
Failed at SU test.
So i tried the Shell Root that said it worked.
Only proof I have that it works is that android screen cast works.
Then I was installing Titanium and it said I didn't have root or my busy box was not installed. So I pushed I'm having trouble ... I downloads it.. to where i dont know
I tried pushing it from command prompt with
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
at this point I get that error
when I exit and come back into shell I get the same error just by typing SU.
Any help would be appreciated it. I have a Zio
What's a zio?
To both...start over with the DREAIMG.nbh and just start from scratch. These one clicks may work but they're boring. I actually unrooted one of my dreams and used visionary and it worked too funny (but boring)
htc vision

Z4root no sup user app??

Hello everyone, I have been tring to root my phone for two day. I tried the z4root and it gets to rebooting and just stops, it finally reboots when I press the home button but it never installs super user app. I went to unlocker and tried androot, nothing. At the end of superone-click short fuse it failed the test for su permissions but installed superuser but it wouldnt do anything. Please help me root this phone. I have an Alltel phone. Kernel ver. 2.6.29-bc0d2cff firmware ver. 2.1-update 1 baseband ver. 2.42.01.04.23 if you need more info just pm me.
Thanks
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
I used z4 and it got stuck like you said, i clicked home and for me superuser was there.
but since not try rebooting and if its not there then, download android terminal emulator.. type su then press enter. if you see a # then youre rooted, so go just download superuser from the market and you should be solid
Try super one click. It installs superuser when it installs root files.
Sent from my HERO200 using XDA Premium App
stayclean said:
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
Click to expand...
Click to collapse
I tried it your way and this is what happens... So any Ideas
5. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2/system/bin/sh
6. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
operation not permitted
I tried this one.. It didnt work..
but thanks..

[Q] What are the terminal commands and/or adb commands for unrooting

I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
okachowwa said:
I really just want to unroot my Captivate and I was wondering if there was a way to do so through adb or terminal. I am on stock 2.2.
Click to expand...
Click to collapse
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
jmtheiss said:
Take a look at this. It's the one-click root/unroot.
I know you said you wanted terminal, and if you look at the batch files for this program, you should be able to see the commands being used to do the rooting/unrooting.
....Or you could use the program. Either way.
(One other thing - are you wanting to place your phone in a rooted state, or remove it from a rooted state? Rooting is putting it in the rooted state, unrooting is removing it from the rooted state. Not trying to be definition crazy, but knowing what you're wanting to accomplish sometimes requires different steps.)
Click to expand...
Click to collapse
I'm definitely trying to unroot lol and thanks...and I didn't root with that however so should it still work the same?
EDIT: I got E:verification error thing when i used that method. As stated, I'm on 2.2.
Please you guys, I just need to know the commands, I have found some online, but I don't know if they are the same for the Captivate. Please help me. I have root to use the Terminal Emulator, so I need to confirm they are the same.
This is the one I found, is it the same for the Captivate?
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /sdcard/Superuser.apk
rm system/xbin/busybox
rm /system/xbin/su
rm /sdcard/su
rm /sdcard/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit (first "exit" takes you out of su)
exit (second "exit" takes you out of the terminal)
reboot

Categories

Resources