Database Users

How to get to stock recovery menu if I have CLOCKWORK Recovery installed

how can I put my phone in stock recovery mode? I tried holding both volume keys down and power, it just powercycles. Even if let go on the second screen off. if I continue on holding - it just powercycles. If i hold vol down and power - it goes into download mode...
I have Clockwork installed. If I start recovery from ROM Manager it bypasses stock recovery straight to Cloclwork menu. I am trying to install battery percentage indicator, which I can only do thru stock recovery menu. How can I start stock rec mode?...
Also it says DO NOT INSTALL this lag fix http://forum.xda-developers.com/showthread.php?t=765820 using ROM MANAGER. So how can I install it then??

in clockwork recovery theres an option to boot into regular recovery. i believe its in advanced settings?

adb is your friend. seriously, how have people on this forum not figured this out yet? (I don't actually even know how to reboot into recovery with just the buttons off the top of my head)
either "adb reboot recovery" or download "Terminal Emulator" from the marketplace type "su" and then "reboot recovery"

bmvik said:
how can I put my phone in stock recovery mode? I tried holding both volume keys down and power, it just powercycles. Even if let go on the second screen off. if I continue on holding - it just powercycles. If i hold vol down and power - it goes into download mode...
I have Clockwork installed. If I start recovery from ROM Manager it bypasses stock recovery straight to Cloclwork menu. I am trying to install battery percentage indicator, which I can only do thru stock recovery menu. How can I start stock rec mode?...
Also it says DO NOT INSTALL this lag fix http://forum.xda-developers.com/showthread.php?t=765820 using ROM MANAGER. So how can I install it then??
Click to expand...
Click to collapse
delete "update.zip" on internal sdcard. make sure to reinstall clockwork recovery again using rom manager after u r done.
make sure whatever ur installing is rename to update.zip for stock recovery to work.
for lagfix use this http://forum.xda-developers.com/showthread.php?t=751864
unzip it. connect ur phone with usb debugging. click lagfixme wait for it to prompt for superuser then it will do the rest for you

Kaik541 said:
adb is your friend. seriously, how have people on this forum not figured this out yet? (I don't actually even know how to reboot into recovery with just the buttons off the top of my head)
Sorry, I'd like to learne to use adb, I am a noob.
either "adb reboot recovery" or download "Terminal Emulator" from the marketplace type "su" and then "reboot recovery"
Click to expand...
Click to collapse
I knew I could do it using terminal emulator but I need to learn commands
akachay said:
delete "update.zip" on internal sdcard. make sure to reinstall clockwork recovery again using rom manager after u r done.
make sure whatever ur installing is rename to update.zip for stock recovery to work.
for lagfix use this http://forum.xda-developers.com/showthread.php?t=751864
unzip it. connect ur phone with usb debugging. click lagfixme wait for it to prompt for superuser then it will do the rest for you
Click to expand...
Click to collapse
Should I delete it from my internal after I have the battery indicator installed, should I get rid of that update.zip? I did a backup using ROM Manager before adding the battery indicator. So I have my former ROM and Current ROM backed up.
OMG, I've been going crazy trying to get my phone into boot screen all night. Thanks for this!

Rhiannon224 said:
I knew I could do it using terminal emulator but I need to learn commands
Should I delete it from my internal after I have the battery indicator installed, should I get rid of that update.zip? I did a backup using ROM Manager before adding the battery indicator. So I have my former ROM and Current ROM backed up.
OMG, I've been going crazy trying to get my phone into boot screen all night. Thanks for this!
Click to expand...
Click to collapse
yea delete update.zip(battery indicator). open rom manager to install your clockwork recovery which will automatically put an update.zip(clockwork recovery) back on ur sd card. thus "update.zip" is just a rename for whatever program/file.

Also there is an app called quick boot in the market. Its free and will take you to stock reboot and recovery without going through the whole hold power
And vol up and down at same time. Is super easy to use. It have icon on my phone next to rom manager so one will be clockwork recov, and the othe stock.
Sent from my SAMSUNG-SGH-I897 using XDA App

Is there a way to make clockwork the default? I'm so used to using adb I do reboot recovery then go ARRRGH I wanted clockwork!

thanks guys!! I ended up using that app from the market. And renaming the battery zip file to update.zip

gunnyman said:
Is there a way to make clockwork the default? I'm so used to using adb I do reboot recovery then go ARRRGH I wanted clockwork!
Click to expand...
Click to collapse
reboot thru ROM manager, it will take you to Clockwork right away, right?

bmvik said:
reboot thru ROM manager, it will take you to Clockwork right away, right?
Click to expand...
Click to collapse
well yeah but I seem to be able to type ./adb reboot recovery faster

I have a kernel that replaces stock recovery with clockworkmod. I'm trying to work out whether I can actually distribute such a thing, and also how to incorporate downloading it into my kernel build script so that I don't need to include it with the sources.
Sent from my SAMSUNG-SGH-I897 using XDA App

Unhelpful said:
I have a kernel that replaces stock recovery with clockworkmod. I'm trying to work out whether I can actually distribute such a thing, and also how to incorporate downloading it into my kernel build script so that I don't need to include it with the sources.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm pretty sure Koush said he wanted this from the start. The reason he changed the way clockwork recovery works for our phones was because recovery and the system are handled by the same part of system code, unlike with other phones.
He wanted to make it available to be incorporated into other kernels/ROMs instead of relying specifically on his kernel (which is why the roundabout happened from earlier where he offered the stock kernel to revert to)

It doesn't use a custom kernel, it's started from an update.zip normally.
Sent from my SAMSUNG-SGH-I897 using XDA App

Does our recovery system work the way it does because of lack of fastboot?

Another idea. is there something we can add to build.prop or perhaps init.rc so a command such as adb reboot clockwork would work? Just spitballing here.

Unhelpful said:
It doesn't use a custom kernel, it's started from an update.zip normally.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Unless I'm mistaken, his original method did require a custom kernel or modified the stock kernel which is why he offered the stock kernel for people to reflash when he provided the final release.
Sent from my Samsung SGH-i897

GRH78 borked clockwork and root

So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?

zeiroe said:
So as many of you are now finding out is that clockwork is borked and so is root with the new update. The root method on cyanogenmod wont work. The rootboot.img breaks wifi and you still cannot get into clockwork recovery ... well at least I can't. Anyone else seeing this and possibly have a solution?
Click to expand...
Click to collapse
ya the OTA breaks root and CWM,,,thats why in roms the ability to OTA is removed

Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.

Just a minor issue that comes from running custom recoveries and roms. Koush already is working on a flashable update that will work with CWR. Just gotta be patient. Chances are that if you have been keeping up with the tweaks and new apk's in the dev forum, this update won't really mean that much anyway. I am a sucker for wanting the latest version number in my "about phone" though

distortedloop said:
Reflash koush's clockwork recovery via fastboot.
After the successful flash, you can get into CWM recovery by selecting Recovery while still in fastboot.
Once in CWM, go to mount options menu and mount /system.
Then use adb shell to navigate to /system/bin.
Once in /system/bin type chmod 6775 su
Root functionality should now be restored when you're in normal boot mode.
Getting permanent CWM recovery back is proving more problematic for me. Once you reboot the phone after that first install, selecting Recovery gives you the Android and "!" screen. Battery pull required.
You can however, get back into CWM recovery by either fastboot flashing the image again as above, or from the ROM Manager app where you flash the recovery and then select boot into recovery.
Pain in the butt, but not totally lost.
Click to expand...
Click to collapse
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks

zeiroe said:
Bah im a douche up arrow and didnt read the line and I was flashing the stock boot.img over and over lol ... Thanks
Click to expand...
Click to collapse
LOL, don't you hate when that happens.
Glad it worked out for ya in the end!

[RECOVERY] 3e Recovery Modded w/ No Verification

NOTE
This is took from untermensch's thread in the Vibrant forum so I take no credit for this (http://forum.xda-developers.com/showthread.php?t=833423)
I have noticed some of you are having issues after installing a new kernel or rom, when you boot into recovery you now have 3e, which does not allow unsigned zips to be flashed. With this version of 3e it has no-verification check, now allowing you to flash whatever you want.
This zip has
1) 3e recovery modified to disable signature checking
2) disables the forced wipe after installing any update.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
You can either leave the modded 3e recovery or you can now flash CWM via Rom Manager
**Just like anything else, I am not responsible if this bricks your phone, this is fairly simple, follow the guide...Do at your own risk**

Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.

designgears said:
Old news, we have CWM now in pretty much everything.
Also you cannot just replace the recovery file... you have to replace the images in sbin or in the zImage its self, otherwise you get errors and cannot do anything.
Click to expand...
Click to collapse
I done the exact method above and works fine for me...
Place extracted recovery file in /system/bin/ , reboot and flash cwm via rom manager, works perfectly fine...the reason I posted was, if you read Hardcores thread, and seen this in other threads, that after flashing his kernel, when they goto recovery they now have 3e (depending on which method when entering recovery)..alot of people have done it the way I posted with no issues...im not trying to argue with you, you by far know more then me, just posting what worked for me and some others

sounds like a good idea for the people that updated to Rogers froyo that has the 3e recovery. You could just flash a new kernel, but this is definately a good alternative.
Thanks
Sent from my SGH-I897 using XDA App

If you look at Darkyy's rom he has a script that does this.

Thanks, this works flawlessly on a Rogers Froyo Stock. Now I have CWM working and good to go. The only thing left would be to apply some kind of lagfix.

Tested and works with Rogers 2.2 Rom. Thanks

skorchir said:
Tested and works with Rogers 2.2 Rom. Thanks
Click to expand...
Click to collapse
I also have.
Thanks

Works great on Rogers 2.2. Thanks

I tested it on Galaxy S i9000m bell and it work A+
i do not have to flash cf-boot to make unsigned zip to be installed
thanks a lot for your hard work.
only thing is botton function become different then original 3e
but its working A+

I'm a little confused on how the Recovery works..... I have a I897 that I flashed Cognition 2.3b8 to with ROM Manager/CWM and when I chose "reboot into recovery" from ROM Manager from inside Cognition, it worked fine after reloading packages once. A few days ago, I flashed Perception 10.1 with the firebird kernel. After noticing the battery didn't last as long as it used to with Cognition, I did some research and found the SpeedMod kernel K12L. Before I flashed it, I did a backup from ROM Manager which rebooted into CWM with no problems and did the backup with no problem. I have since flashed K12M and K12N. Now I thought I would give Cog 3.0 a shot and wanted to back up my current config with Perception 10.1/SpeedMod K12N. From ROM Manager, I chose to backup, named my backup and the phone rebooted into 3e Recovery and gave the errors you listed above but I don't understand why? Is it because of the I9000 kernel which doesn't make sense since Firebird is a I9000 kernel. Was it from flashing SpeedMod? Also noticed, that only the volume up/down buttons worked, not the power button which is also the select key. Only way out was to 3 button reboot (or pull the battery) which rebooted into CWM and then initiated the ROM Manager backup.
Any ideas why? Also, if I was to ODIN flash JH6 back to the phone, would that restore the Stock 2e Recovery? Sorry for the long post, but I'm still trying to learn this stuff and think you guys are awesome. The captivate would be a crappy phone if it wasn't for you all.

I guess if I had read your second post a little closer I would have seen that flashing SpeedMod causes it. I used your fix in the OP and when I tell it to "Reboot into Recovery" from ROM Manager, it boots into what I assume is 3e (Goes by real quick) and shows something about MOVI and verification and then boots into CWM Recovery v2.5.1.2. If I 3 button boot into recovery, it boots into CWM v2.5.1.0 SpeedMod ULFK. Seems to work now but I'm still confused. Thanks again.

Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.

davidis57 said:
Using sgstools to change mount RW completes its task fine. When I try to copy the new file to /system/bin it does not allow it. The permissions do not change. I tried terminal emulator it doesnt work either. The files stay -r only. I have tried so many times to delete/rename/ or copy over. I just gave up. My system is 2.2 and rooted before you ask.
Click to expand...
Click to collapse
Use a terminal emulator or adb shell and type...
Code:
chmod 777 /system/bin/recovery
That should give r/w permission to the file, ...i just tested to verify it and it worked for me. also if you have Root Explorer you can just long press the file and select Permissions and check all the boxes.

Exact the same thing is happening to me! Beforehand I had flashed CF Root to get Superuser also at the same time when rooting. I Still can boot into recovery with 3BR and come into the speedmod ULFK settings. Speedmod introduces 3e and you need signed packages. You must have 2e for this I assume!? Can anyone tell me what goes wrong?

Im using the Speedmod kernel and it always pissed me off that everytime I wanted to flash somethng via CWM that I had to pull the battery and restart my phone for it to finish because of the 3e 'no signed packages'
I did the steps in the OP and I noticed that I didnt even have a recovery file in system/bin but I put it in there anyway. I rebooted and flashed a different modem just to check and sure enough, it worked. Now I dont have to worry about pulling my battery and having to reboot my phone everytime I want to flash something.
Thanks for this!

Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?

davidis57 said:
Well the file is moved now. I get reinstall packages in recovery and thats all does. I installed rom manager and have cwm on my sdcard. The phone does not go into cwm recovery. It doesnot give me options to apply install.zip. I have dxjpa and z4root running. This modded recovery does not work. Any ideas?
Click to expand...
Click to collapse
Once you install cwm and reboot back into 3e, select reinstall packages, it will install cwm and then load into it , if it doesn't then the file didn't copy over, make sure it replaces it ok, I've used this quite a few times and it works everytime, and everyone that has posted has not had an issue, so it does work
Sent from my SGH-I897 using XDA App

It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App

davidis57 said:
It did copy over in fact i deleted the old one and put the new one in its place. It never installs anything and seems to error but its so fast i cant read it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Try starting over, delete the recovery file and also delete the update.zip on the root of the sdcard, then copy the modded recovery over to /system/bin/ , then open rom manager and install cwm again, something could have happened with the update.zip, cause if you are able to get into 3e and select reinstall packages and it actually starts but errors out with the update.zip, then something could possibly be wrong with the update.zip .. it might restart after you select reinstall packages, but it should then load in to cwm, if it doesnt and boots back into android, then go into rom manager and select restart recovery and see if that works

can't change TWRP 2.1.1 settings to stop official recovery from reinstalling

Hi all,
I have a Nexus 7, rooted, running stock 4.1.1 rom, and just installed TWRP 2.1.1
I have been reading this thread, http://forum.xda-developers.com/showthread.php?t=1779092 , however I cannot post on the thread due to being a new/low post count member.
I read that, and it does happen, that each time I reboot, the stock recovery reinstalls itself.
I attempted to follow this....
NOTE: The stock ROM may automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced -> File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Click to expand...
Click to collapse
but it doesn't seem to work.
Firstly, when I go to the "Mount" menu, there is only 3 entries.....1 large button which says "Mount USB Storage", and 2 boxes which are selected with a cross in the box, "Unmount Data", and "Unmount Cache". If I do press Mount USB Storage I can only Unmount it to return to menu.
So regardless of that part, if I then go to the file manager, and browse to the system folder, the folder shows up empty, and the only thing showing is a Bin subfolder (also empty)
any ideas whats wrong?

Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7

TheBiles said:
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
Click to expand...
Click to collapse
hi,
yeah I did use the tool, all is rooted fine. If you install TWRP from GooManager, and then press to reset to recovery, TWRP loads fine. Once you reboot again however, the stock roms overwriting the TWRP so it no longer works each time. The steps there were supposedly to stop this from happening, from within TWRP, however the options aren't even there. Sadly, I can't post in the TWRP thread due to having less than 10 posts

How r u booting into recovery? Do u power off then use button combo? I use quickboot from market. Its free and boots u into recovery without having to manually turn off the device. I had the same exact issue u drescribe when attempting to follow op instructions. I couldn't do it so I said what the hell, let me see if I boot into recovery using quickboot it overwrites. I was happy to discover that it didn't.
Sent from my EVO using Tapatalk 2

Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom

Midnight Tboy said:
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Click to expand...
Click to collapse
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2

pathtologos said:
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yup....just installed Quick Boot (Reboot),
chose Recovery, and again its rebooting back to the original recovery instead of the TWRP.
Guess I'll have to flash to a custom rom to get around it if want it sorting now....or wait till I have the minimum post count to post on the main TWRP thread
Not end of the world to reinstall apps and games I guess when the custom roms are more mature, so long as I remember to use Titanium Backup to save my games progress

you need to rename the recovery-restore.sh file in /system/etc/ (I forget the name offhand - if you look at the filenames there you'll figure it out). It restores the stock recovery at every reboot unless deleted or renamed. Then flash your 3rd party recovery.

Hi,
thats the trouble.....I use the file manager in TWRP, and I can't see that file anywhere.
The TWRP page says to go to /system......but when I go there its empty, only one subfolder, /system/bin, which also shows up empty

Install Clockwork

Hello, I tring to get root on my Nexus 7.
I install the clockwork recovery and then install the JB-SuperSU, but every time I reboot, I lose the recovery.
How could I keep the recovery?
Thanks and best regards.

Which version of CWM are you using? I believe 6.0.1.0 comes with a script that tweaks certain files to make it easier to get back in to recovery. It should prompt you the first time you select "reboot system now".
Also, are you trying to get into recovery from the boot screen (i.e. power + volume buttons) or through an app's rebooter? I've never had luck doing it the first way, but getting in through the reboot function on Titanium Backup or ROM Toolbox should work.
Sent from my DROID BIONIC using xda app-developers app

Can you boot into stock N7 recovery?
If so, find a superuser.zip (or something similar to this name) compatible with the N7, then put into the root of the N7, Install zip from SD. <------------------------- YOU DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE.
Have you unlocked your boot loader?

Thanks,
I am using recovery-clockwork-6.0.1.0-grouper.img, I think that it is a problem of Hosts Editor app. It says that I have no read/write permission.
I access from "adb shell" and I can execute "su" command. How can I check if I have full root access on the device?
Thanks and best regards.