Database Develop

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[TUTORIAL] Full Steps to Acheive Root + ClockwordMod Recovery with new KA6 2.2

I have put together some steps to take your fresh KA6 2.2 Official update and add Root and ClockworkMod Recovery. It may look hard, but should only take a couple minutes.
This is without ODIN or ROMS.
Steps:
0. Have yourself a T-Mobile Vibrant and PC Running Windows.
1. Use SuperOneClick (latest) to root phone. When you run the application, click the first button on the left and wait for the process to complete. Details will be scrolling in the middle window.(http://forum.xda-developers.com/showthread.php?t=803682)
2. Use a file manager (ROOT EXPLORER) or adb with root access to mount /system/ and remove bloatware (SLACKERRADIO and AMAZONMP3 and such) from /system/app/
2a. TOTAL NOOBS: Get SUPER MANAGER from the market (FREE). Then grant it root by going into SUPER MANAGER and selecting File Manager > [Menu BUTTON] > Setup > Enable ROOT function. Then go up levels, the top button on the file manager which will take you up a directory, until you get to / and scroll to the bottom and select [system]. Then select [app]. Then click [Menu BUTTON] > Switch System to R/W and press R/W. Scroll down and long press the slackerradio.apk to delete. You can do this too amazon market to delete and other useless apps.​
3. YOU NEED STEP 2 TO DO THIS STEP! Install Busybox from Market and run Busybox Installer to ensure its properly working and the latest is installed.
4. Run SuperOneClick again to place phone into shell root ADB (Second button from the left). Allow the process to run and then a pop up will say something about rebooting the phone. DO NOT DO THIS, continue on to the next step.
5. While in shell root from the previous step, run (3e) to (2e) modified recovery script. The instructions are simple. Download, unzip, and run the batch file found inside. This is ran from the COMPUTER NOT YOUR PHONE. Use the menu system to complete and then reboot as recommended. (http://forum.xda-developers.com/showthread.php?t=833423).
5a. NOT NOOBS: you can copy over the recovery yourself to /system/bin as mentioned by some commenters. If you do not know what this is, then ignore it.​
6. Remove any update.zip files from /sdcard/ and also remove any ClockworkMod directories using your favorite file manager or by mounting to a computer with a wire and activating the drive for My Computer. This is the internal one, not external.
7. Use ROM MANAGER from market to install ClockworkMod Recovery and reboot. This is free to download. When you launch, select the top item to install the recovery and then a menu will pop up to choose the phone you have. Happily select Vibrant. Once that's done, select reboot into recover right below that.
8. Re-install packages and it should reboot. You can navigate the menu using VOL UP AND DOWN and power to select.
9. Re-install packages again and it should boot into Clockwork Recovery. It should change form BLUE TO GREEN
ALL DONE.
That should do it for ya! Let me know if it worked out. Please follow all steps and don't cut corners.
Should you need to get back to ClockworkMod Recovery, you can use "adb reboot recovery" and re-install packages, or reboot into recovery with ROM MANAGER.
Edit Rev.a: added a step (6) Made the instructions more precise and added additional steps to clear up some confusion.(1-22-11)
Edit Rev.b: Added step 2a from request. root explorer is not free so use super, that works too. (1-24-11)
Edit Rev.c: Added more detail to the steps and added supplemental info for replacing the recovery with the modified one. (1-27-11)
Edit Rev.d: Super1Click has updated, so latest? works.
Side note: I do step 4 because from my experience, I had trouble getting the modified 3e script to get root. Figured might as well just give it root to begin with.
Side note: Yes I am aware that there are other methods and different ways. This was the noob way for me to convey it to the masses. I still do appreciate all feedback regardless of what it is. Thanks!
jmcghee1973:
***For kicks you can do your 2.2 KA6 update the download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.

***For kicks you can do your 2.2 KA6 update then download Supercurio's KA6 voodoo kernel and ODIN it and have Root & CWM all in one shot.
Not to hijack your thread...

Yea I know, but I wanted to find a way without ODIN.
added ur blurp

Reinstalling packages does not seem to work for me. Every time I click it and it reboots it keeps going into the samsung recovery menu... Help?

Does it give an error for signing or just looks like its working then reboots?

Looks like it works and then reboots
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/

Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card changed directories with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager

Nothingness00 said:
Double check if there is a update.zip and clockworkmod folder with a zip in it on your internal memory. I think the external card stopped working with the 2.2 update.
EDIT: infact, remove any update.zip and clockwork folder from the internal memory and run ROM MANAGER again and fresh download the clockwork 2.5.1.2. then check and confirm its on the internal. should be /sdcard/
once its confirmed there, then try again to reboot into recovery with rom manager
Click to expand...
Click to collapse
Tried that, still can't get into clockwork recovery...
I didn't do this step though, would it affect anything?
2.Use a file manager or adb with root access to mount /system/ and remove bloatware (SLACKER and AMAZONMP3) from /system/app/

I would highly suggest doing that step. The system is full to begin with. Use Root Explorer and grant access, then mount system into r/w and remove the stupid stuff. You should do this to get Busybox on (AS IN BEFORE YOU INSTALL BUSYBOX)

What does busybox do?

jmoreau10 said:
What does busybox do?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/BusyBox
ITS ESSENTIAL

Got it working man, thanks.

Awesome! Good to hear. This is my first tutorial and I'm stoked that its working well for others.

I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.

dsilver981 said:
I've been an XDA visitor since my AT&T Titan WM6 days. I've done alot of flashing and modding since then and have always been able to find solutions without asking until now. This clockwork recovery issue is kicking my butt.
I am having trouble with steps 4 & 5.
what are the specific buttons to press on superoneclick in step 4?
How exactly do I use the file 3(e)_recovery_installer?
Thanks for any help.
Click to expand...
Click to collapse
4. Run SuperOneClick again to place phone into root shell ADB
For this step, run SuperOneClick from before, the same you used to root. The second button says "Shell Root". Click that Wait for it to say you have shell root until you reset.
5. Run (3e) to (2e) modified recovery script (http://forum.xda-developers.com/showthread.php?t=833423)
Just download the attachment in the first post and follow instructions. Its fairly simple process. Keep in mind, this may not work unless your phone is shell root from step 4

Thank you Nothingness. Cleared it right up. Worked perfectly.

dsilver981 said:
Thank you Nothingness. Cleared it right up. Worked perfectly.
Click to expand...
Click to collapse
Awesome! Great to hear it! Love them thanks

im a total noob, but im about to try this, wish me luck haha

thoetherguy said:
im a total noob, but im about to try this, wish me luck haha
Click to expand...
Click to collapse
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.

Nothingness00 said:
Luck? ****'s easy as pi. Well... Er... Just follow the steps to a tee.
Click to expand...
Click to collapse
haha, yeah it was easy , thanks...

[Q] Rom Manager on Nexus s claims device is not rooted

Hi
When I start the Rom Manager I get the message "You must root your phone for ROM Manager to function. Superuser was not found as "/system/bin/su" or/system/xbin/su".
I have followed the instructions here on how to root my Nexus s and I am able to enter recovery mode and am able to go into bootloader. I also see that is says "Unlock" there.
So the way I understand it, the phone is rooted. Unless I miss something here.
I also see the Superuser icon in my launcher.
What am I doing wrong?

Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?

I dont think it was mentioned in the guide.
how do I do that?
Can I reapply the su zip file again?

jerrycycle said:
Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?
Click to expand...
Click to collapse
OK. That is what I was missing.
Now its done.
Thanks

dbenyakar said:
OK. That is what I was missing.
Now its done.
Thanks
Click to expand...
Click to collapse
What method did you use to root?

[Solved] Can't flash Clockwork Recovery.

I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
failed to copy recovery.img permission denied
Click to expand...
Click to collapse
Thanks for any help, I'm hoping it's just a small little step I missed.

mikeeey said:
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
Thanks for any help, I'm hoping it's just a small little step I missed.
Click to expand...
Click to collapse
This is covered in the cwm thread in development section you need to use a file explorer that has root access and change permissions to the /data folder. You can use es file explorer, its free. Open it go into settings then browse as root... not really sure exact steps but they are in the came thread.

O my such a small step I missed! Thank you! Ill try this later today.

Permissions of /data are set to R/W but I still get the same error..
I'm starting to wonder if the cause of this is because I tried using Rom Manager to flash clockwork, THEN tried the adb method. Maybe it already being there is causing the permission denied?
edit: so it looks like it was as simple as me looking over the permissions and thinking I saw everything was checked, but really the two checks from the left under "other" were grayed out lol, checking those fixed it.

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.