Database Info

[RECOVERY] Permanently replacing your recovery with ClockworkMod Recovery Image

Since the Evo just got NAND protection removed, I figured I'd share the persistent version of ClockworkMod recovery
Currently ROM Manager is using a recovery hot replace to give you a custom recovery. But I'll eventually be packaging this into ROM Manager's flashing process like the other phones it supports. I'll wait a week or so to switch, while everyone switches over to the new root.
For those that want to make ClockworkMod their default recovery on recovery boot, use this image:
These step assume you have already unlocked your NAND using the "Part 2" thread in the forums.
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-supersonic.img
http://www.droidaftermarket.com/koush//recoveries/flash_image
Place these files on the root of your SD card.
Then run this from a root Android shell.
cd /data/local
cat /sdcard/flash_image > flash_image
chmod 755 flash_image
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Done!

For insurance stuff, will we need to flash stock recovery img to get rid of everything?

<3
Will we be able to update this with ROM Manager?

Re: Permanently replacing your recovery with ClockworkMod Recovery Image
You are a God!
-------------------------------------
Sent via the XDA Tapatalk App

TheBiles said:
<3
Will we be able to update this with ROM Manager?
Click to expand...
Click to collapse
Yes, in a week, when everyone has done their NAND unlock, ROM Manager will start flashing and replacing your recovery for you, so you don't need to do this manually. I do not want to switch right now, because that will leave people who haven't unlocked out in the cold.

Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?

HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.

HTC6800 said:
Does this mean that for right now if we make this the real recovery that when we choose "Reboot to Recovery" in ROM Manager that it will not work until ROM Manager is updated?
Click to expand...
Click to collapse
no, it means when you choose reboot to recovery in any application, ROM manager, quickboot or thru adb it will reboot to the phone's recovery partition but instead of loading the stock recovery, it will load this custom recovery!
this is basically a permanent or "sticky" recovery where as before we had to load the custom recovery every time as a temporary or "non-sticky" recovery. the days of temporary or non sticky recoveries are OVER ... at least until the next update from HTC/Sprint!

Koush, I m still a completely rookie on root part, EVO4G is my first androind phone, and 0 experience on root. Besides, i haven't done anything about rooting evo4g yet (still kinda struggle here, worrying to brick such a$$kicking phone, anyway). So please forgive if my question sounds ridiculous and stupid.
lets say if i decide do root like next months, so i should follow the 1st part root my phone by "PC36IMG.zip", then what's next step? should I use adb shell complete flash recovery, and 2nd part to remove NAND protection, at last run ROM Manager flash recovery permanently? or I can just directly use ROM Manager after root'd phone, like the instruction "[TUTORIAL] IDIOT-PROOF Root Guide! No ADB, no fuss!" by theBiles, to flash recovery permanently?

Koush said:
No, that will still work.
This is just an option for people that want to boot into recovery via the power key combination. Or those that don't want to apply the update.zip on the root of their SD card to switch to ClockworkMod. It's just a convenience/safety net people wanting to replace their recovery now.
Click to expand...
Click to collapse
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0

phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
Hrm, let me double check on mine

phinnaeus said:
This doesn't seem to be the case on my phone. After going through Toast's NAND unlock process (replacing his recovery image with yours in the last step, only change) I boot back up and try to "reboot into recovery" from ROM Manager. It takes me to a screen with an android and a white triangle with a ! in the middle.
From that point I have to take out the battery to turn off the phone, afaik. For the record, at that point I turned on the phone while holding down vol down and got into the stock hboot screen where it checks for PC36IMG.zip. It didn't find anything because I have moved the files, so I selected recovery, and it booted right into ClockworkMOd Recovery v1.8.2.0
Click to expand...
Click to collapse
I get the android with the white triangle as well when using reboot into recovery from rom manager. However the normal recovery is now clockwork great job and thx K!

Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.

jeremydk said:
Confirming this as well.
Booting to recovery via adb or hboot works as expected, reboot from Rom Manager doesn't.
Click to expand...
Click to collapse
Found the problem Fix is being uploaded!

Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img

Koush said:
Flash this:
http://www.droidaftermarket.com/koush/recoveries/recovery-clockwork-1.8.2.2-supersonic.img
Click to expand...
Click to collapse
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?

So what exactly does this do or look like? I'm a bit confused on that one.

phinnaeus said:
Just did this, works perfectly. Thanks for the fast response, Koush. Sending some beer your way.
Edit: When I boot into recovery manually (hold down voldown, select recovery) I get into version 1.8.2.2.
When I boot into recovery from ROM Manager I get into version 1.8.1.9. Does this mean there are two different recoveries on my phone and it is booting into them distinctly based on which method I use? Or is it just a error in reporting version numbers?
Click to expand...
Click to collapse
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries

Koush said:
Booting via ROM Manager still uses the recovery hot replace, which is using a recovery with a different version number. They're exactly the same, no worries
Click to expand...
Click to collapse
Oh gotcha. So thats what that progress bar is before it loads up? And this won't happen with the updated ROM Manager coming in a week. I guess thats not really a question, but if I'm wrong feel free to correct me

Koush said:
./flash_image recovery /sdcard/recovery-clockwork-supersonic.img
Click to expand...
Click to collapse
Worked great but it might help to change that to
./flash_image recovery /sdcard/recovery-clockwork-1.8.2.2-supersonic.img
Took me a second to figure out why it said directory or file doesn't exist
Thank You for all your work

Cant RCK tf300t

Hi, Im trying to install cm 11.0 on my tf 300t, im trying to install TWRP. The boot loader is unlocked and the device is rooted. I tried get into the fast boot menu but cant. I hit Power and vol down and get into a new screen with a row of 3 icons. I see the RCK and hover over the button for 5 sec... nothing happens. I waited for 5 min an nothing happened. I then tried to hit the volume up button but that fails and re boots me into the OS. Im running 4.2.1. Is there a Fix for this problem? Can I install TWRP another way? (maybe through ADB?) Thanks

macieksoft said:
Hi, Im trying to install cm 11.0 on my tf 300t, im trying to install TWRP. The boot loader is unlocked and the device is rooted. I tried get into the fast boot menu but cant. I hit Power and vol down and get into a new screen with a row of 3 icons. I see the RCK and hover over the button for 5 sec... nothing happens. I waited for 5 min an nothing happened. I then tried to hit the volume up button but that fails and re boots me into the OS. Im running 4.2.1. Is there a Fix for this problem? Can I install TWRP another way? (maybe through ADB?) Thanks
Click to expand...
Click to collapse
The first time you install TWRP, it should be through ADB (fastboot). Flash it from your computer. After that, you will be able to flash ROMs from the recovery menu on the tablet.

cmendonc2 said:
The first time you install TWRP, it should be through ADB (fastboot). Flash it from your computer. After that, you will be able to flash ROMs from the recovery menu on the tablet.
Click to expand...
Click to collapse
I cant Flash though... the instructions say to go to Hover over the RCK fir 5 seconds, I can do that but nothing happens. " I can boot into the JB, but thats it.

macieksoft said:
I cant Flash though... the instructions say to go to Hover over the RCK fir 5 seconds, I can do that but nothing happens. " I can boot into the JB, but thats it.
Click to expand...
Click to collapse
AHAHHAHAHA IM SO STUPID xD. On android 4.2.1 you dont get a message, you can just send the file over through adb. Nothing happens if you hover over the screen. Thanks for the help.

Now I have another problem, both TWRP and CWM don't have access to any files. They still boot up, but they don't have the ability to install or find any files or create logs. Im getting the errors saying nothing can mount.

macieksoft said:
Now I have another problem, both TWRP and CWM don't have access to any files. They still boot up, but they don't have the ability to install or find any files or create logs. Im getting the errors saying nothing can mount.
Click to expand...
Click to collapse
Did you flash the 4.2 TWRP file? CWM has no version that woks with the 4.2 bootloader, except for the one in the flatline.img for NVFlash. If you flashed the regular TWRP recovery by mistake, follow the instructions here to recover, and start all over again. Remember to choose the correct recovery.

graphdarnell said:
Did you flash the 4.2 TWRP file? CWM has no version that woks with the 4.2 bootloader, except for the one in the flatline.img for NVFlash. If you flashed the regular TWRP recovery by mistake, follow the instructions here to recover, and start all over again. Remember to choose the correct recovery.
Click to expand...
Click to collapse
What would be the correct file be then? I tried flashing the " openrecovery-twrp-2.6.3.0-tf300tg-JB.blob " off of here http://techerrata.com/browse/twrp2/tf300t (thats what I first flashed) Could you link/tell me which file I would need? thanks.

graphdarnell said:
Did you flash the 4.2 TWRP file? CWM has no version that woks with the 4.2 bootloader, except for the one in the flatline.img for NVFlash. If you flashed the regular TWRP recovery by mistake, follow the instructions here to recover, and start all over again. Remember to choose the correct recovery.
Click to expand...
Click to collapse
Ok, so i'm assuming I need the openrecovery-twrp-2.6.3.0-tf300t-4.2.blob file. I DO have access to fastboot, can I just flash over the other Twrp recovery installed? Or do I have to follow the steps at http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 ? Thanks.

So I ended up flashing the blob file, and it did work. But when I tried installing CM11 I got an error and it shut down. Now I had a boot screen of the ASUS logo, flashing on/off every 20 sec. BUT I did make a backup, and was able to restore the system from that. Can anyone tell me what I have to wipe/do to install CM 11 on the tf300t? Or even cm 10.2 if its easier.
some (maybe) useful info
- I can boot into fastboot
- I can boot into the OS
- I do have a backup in case anything goes wrong
- I have twrp 2.6.3

macieksoft said:
So I ended up flashing the blob file, and it did work. But when I tried installing CM11 I got an error and it shut down. Now I had a boot screen of the ASUS logo, flashing on/off every 20 sec. BUT I did make a backup, and was able to restore the system from that. Can anyone tell me what I have to wipe/do to install CM 11 on the tf300t? Or even cm 10.2 if its easier.
some (maybe) useful info
- I can boot into fastboot
- I can boot into the OS
- I do have a backup in case anything goes wrong
- I have twrp 2.6.3
Click to expand...
Click to collapse
I successfully installed CM 10.2 But I cant get CM11 working, anyone want to share how they got CM 11? Thanks

[Q] [SOLVED] Flashing recovery.img without fastboot?

Hi all!
My power button is stuck as pressed constantly, and cannot be unstuck.
So there is no way to flash recovery image under fastboot;
nor can I flash CWM recovery TOUCH using ROM Manager, due to network reason that cannot be solved from my aspect;
Flashify said "cannot find recovery block", thus unable to flash by it;
GooManager seems only able to flash TWRP that I decide not to use at present.
So what I want to ask is, is there a way, for our Nexus S, to flash recovery by an Android terminal command? Thanks in advance!

cdljl2005 said:
Hi all!
My power button is stuck as pressed constantly, and cannot be unstuck.
So there is no way to flash recovery image under fastboot;
nor can I flash CWM recovery TOUCH using ROM Manager, due to network reason that cannot be solved from my aspect;
Flashify said "cannot find recovery block", thus unable to flash by it;
GooManager seems only able to flash TWRP that I decide not to use at present.
So what I want to ask is, is there a way, for our Nexus S, to flash recovery by an Android terminal command? Thanks in advance!
Click to expand...
Click to collapse
Have you tried the 'recovery tools flasher' app? .... just put the recovery image on sd and flash through the app ... it should work

Here you Go:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/

rameezwajid said:
Have you tried the 'recovery tools flasher' app? .... just put the recovery image on sd and flash through the app ... it should work
Click to expand...
Click to collapse
A great lot of thanks! This should be it!
[EDIT]
Tried it, seem to have no use... it said it successfully flashed image, but the recovery is still the old one (TWRP) instead of the one I chose to flash (CWM Touch)

smit.sanghavi said:
Here you Go:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
Click to expand...
Click to collapse
I see the command! Thanks a lot!

cant help you

Cyanogen Recovery problem

Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks

benzso63 said:
I already make sure the phone "update Cyanogen Recovery" is unchecked.
Click to expand...
Click to collapse
Well, you should have checked that BEFORE the update, not after.
benzso63 said:
IS there a way I can use TWRP instead?
Click to expand...
Click to collapse
Yes, there are many ways. Check custom recovery installation.

benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.

benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon

Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Heisenberg said:
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse

I did but it saids device not found.
gsmyth said:
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
Click to expand...
Click to collapse

benzso63 said:
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Click to expand...
Click to collapse
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.

Hi Heisenberg, I got the problem solved by using the toolkit. Now I got my TWRP back and rooted. Thanks for the info.
Heisenberg said:
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Click to expand...
Click to collapse

No Volume Buttons. Is flashing custom recovery from 12s impossible?

Hey Guys,
I want to flash twrp to my OnePlus One, but CyanogenOS12S won't let me without a hardware boot into recovery mode. My OnePlus' volume buttons do not work, thus i cannot do a hardware boot to recovery mode. When i boot into cyanogenOS and try a software reboot into recovery mode it defaults to Cyanogen's stock recovery. (And yes I have unchecked "update Cyanogen recovery" in developer options)
Is there any way for me to flash and access a custom recovery? I very much hope there is as I would like to have this phone rooted to perform nandroid backups and to attemot to fix the low mic volume issue when im not on speakerphone.
Appreciate any help!
Thanks,
Mrcalebw

easiest way is going to be fastboot flash a new recovery like twrp using fastboot. Just google. As of now you have stock cm recovery installed

Cannot leave the fastboot screen
aeppacher said:
easiest way is going to be fastboot flash a new recovery like twrp using fastboot. Just google. As of now you have stock cm recovery installed
Click to expand...
Click to collapse
Hey!
Thanks for the reply and help. I tried to do this, but once I
fastboot falsh recovery recovery.img' which is successful
then 'flashboot boot recovery.img' The fastboot screen lights up brighter and my oneplus disconnects from adb and my computer and i have to do a hard power off by holding the powerbutton.
And I'm back where i started without a custom recovery to boot into.

mrcalebw said:
Hey Guys,
I want to flash twrp to my OnePlus One, but CyanogenOS12S won't let me without a hardware boot into recovery mode. My OnePlus' volume buttons do not work, thus i cannot do a hardware boot to recovery mode. When i boot into cyanogenOS and try a software reboot into recovery mode it defaults to Cyanogen's stock recovery. (And yes I have unchecked "update Cyanogen recovery" in developer options)
Is there any way for me to flash and access a custom recovery? I very much hope there is as I would like to have this phone rooted to perform nandroid backups and to attemot to fix the low mic volume issue when im not on speakerphone.
Appreciate any help!
Thanks,
Mrcalebw
Click to expand...
Click to collapse
If your phone is rooted. I guess it would be. Then try this steps to reboot it to recovery
No need of pc.
1. Download TWRP manager from the play store
2. Open the app
3. Open menu in the app by touching the left top corner of the app.
4. Touch on the reboot option and then
5. Touch on the reboot to recovery and touch yes.
Sent from OPO using Tapatalk
Press on thanks if I helped you

Currently not root
ashuthosh.heda said:
If your phone is rooted. I guess it would be. Then try this steps to reboot it to recovery
Click to expand...
Click to collapse
Hi,
Thanks for your help. The trouble is that i do not currently have root on my phone.
If its possible to get root, without having to boot into custom recovery that would be fantastic.
I'm beginning to feel like this might be a lost cause.
I'd love any suggestions though!

Is the bootloader of your OPO unlocked??
Sent from OPO using Tapatalk
Currently on Resurrection Remix.
Press on thanks if I helped You

ashuthosh.heda said:
Is the bootloader of your OPO unlocked??
)
Click to expand...
Click to collapse
Yes, the bootllader has been unlocked through use of adb

Then try flashing the supersu zip from the fast boot and try the steps as mentioned above
Sent from OPO using Tapatalk
Currently on Resurrection Remix.
Press on thanks if I helped You

Flash supersu without custom recovery?
ashuthosh.heda said:
Then try flashing the supersu zip from the fast boot
Click to expand...
Click to collapse
And how do i flash supersu zip from fastboot? Without having to temporarily boot into a custom recovery?
As far as I was aware you cant flash supersu unless you have a custom recovery installed, which i cannot install (original post issue)
If theres a command I'd be very grateful!

mrcalebw said:
And how do i flash supersu zip from fastboot? Without having to temporarily boot into a custom recovery?
As far as I was aware you cant flash supersu unless you have a custom recovery installed, which i cannot install (original post issue)
If theres a command I'd be very grateful!
Click to expand...
Click to collapse
Did you tried any oneplus one tools?
You can cannect your phone as adb right? Then try this tool.
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
It may help. It has the option boot to fastboot and boot to recovery.
Sent from OPO using Tapatalk
Currently on Resurrection Remix.
Press on thanks if I helped You

Only boots to custom from full boot
ashuthosh.heda said:
Did you tried any oneplus one tools?
You can cannect your phone as adb right? Then try this tool.
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
It may help. It has the option boot to fastboot and boot to recovery.
Sent from OPO using Tapatalk
Currently on Resurrection Remix.
Press on thanks if I helped You
Click to expand...
Click to collapse
I have tried a couple of toolboxes. The trick there is that adb commands only send once the phone has booted and is on debugging mode. When full boot happens, the cyanogen stock recovery overwrites the custom recovery.