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

Bricked my Nexus?

Hi guys,
A little help would be appreciated here as I think i've bricked my SNS just now..
I was following this guide here: http://forum.xda-developers.com/showthread.php?t=878446 in an attempt to flash clockworkmod to then flash something else however:
I get to step 14 after booting into recovery and a whole bunch of e:/ errors are shown, mainly around the Cache when in the cwm recovery screen.
I attempted to flash the stock ROM as per this thread: http://forum.xda-developers.com/showthread.php?t=1063664 (Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader)
However this error'd and went back to the cwm screen with the e:/ errors.
The phone will now not boot past the Google logo with the unlocked padlock on the screen.
Any ideas atall? I've tried factory wipe/cache/devlik wipe ect but the errors are still showing?
Thanks in advanced!

i had experienced same problem " E:/ errors"
try use newer or older version of recovery , that's how i solved it ...
can you still be able to enter fastboot ? if so , you can flash new recovery img via adb
if you can't ,that's gonna be kinda problem , i suggest you try Odin ...although it could be little more complicated then recovery

qtwrk said:
i had experienced same problem " E:/ errors"
try use newer or older version of recovery , that's how i solved it ...
can you still be able to enter fastboot ? if so , you can flash new recovery img via adb
if you can't ,that's gonna be kinda problem , i suggest you try Odin ...although it could be little more complicated then recovery
Click to expand...
Click to collapse
Thanks for replying.. How do I get into Fastboot if it doesn't boot though? + what command do I use to get there from a Mac?
I've used odin before so am aware of how it works, but wouldn't know which files to flash if you know what I mean?
Edit: Im using cwm 3.0.0 by the way, not sure if that helps?

adaimespechip said:
Thanks for replying.. How do I get into Fastboot if it doesn't boot though? + what command do I use to get there from a Mac?
I've used odin before so am aware of how it works, but wouldn't know which files to flash if you know what I mean?
Edit: Im using cwm 3.0.0 by the way, not sure if that helps?
Click to expand...
Click to collapse
To enter fastboot when phone is off just hold the volume up button and the power button at the same time
Sent from my Google Nexus S using xda premium

smok3thekid said:
To enter fastboot when phone is off just hold the volume up button and the power button at the same time
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Oh! Yes sorry, I can do that indeed..

[Q] [i9023] Blank/Black screen in recovery

Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!

I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.

Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?

Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App

Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English

Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686

Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES

bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh

Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App

Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..

Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...

Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.

I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!

Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.

Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?

I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next

Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.

khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!

Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App

Can't boot into recovery

So I installed TWRM and now every time I boot into recover system it shows "No command" with an android layed on his back, pressing and holding power but. + plus volume doesn't get me in the recovery (saw this in a thread as a solution). I've also tried to reinstall it, the only way for me to get in it is to connect it to my computer and flash the recovery again. Any suggestions?

rylark said:
So I installed TWRM and now every time I boot into recover system it shows "No command" with an android layed on his back, pressing and holding power but. + plus volume doesn't get me in the recovery (saw this in a thread as a solution). I've also tried to reinstall it, the only way for me to get in it is to connect it to my computer and flash the recovery again. Any suggestions?
Click to expand...
Click to collapse
If you mean TWRP by squid2, OP describes two methods. Which of them did you use?
- "fastboot boot twrp-osprey-2.8.7-test1.img" will flash TWRP as a temporary (one time) recovery
- "fastboot flash recovery twrp-osprey-2.8.7-test1.img" will make it permanent

RGold55 said:
If you mean TWRP by squid2, OP describes two methods. Which of them did you use?
- "fastboot boot twrp-osprey-2.8.7-test1.img" will flash TWRP as a temporary (one time) recovery
- "fastboot flash recovery twrp-osprey-2.8.7-test1.img" will make it permanent
Click to expand...
Click to collapse
Thank you for the reply, I used the first method you mentioned. I never heard the second one, could you like me a tutorial for it please?

rylark said:
Thank you for the reply, I used the first method you mentioned. I never heard the second one, could you like me a tutorial for it please?
Click to expand...
Click to collapse
Wait, is it the same process? I just have to type "flash recovery "file location" instead of "boot"?

rylark said:
Wait, is it the same process? I just have to type "flash recovery "file location" instead of "boot"?
Click to expand...
Click to collapse
One you're just booting temporarily into TWRP and not overwriting the stock recovery, the other, you're flashing TWRP as the default recovery. So yes, leave off the boot part and you'll flash TWRP as the default recovery.
Sent from my SM-T530NU using Tapatalk

Tel864 said:
One you're just booting temporarily into TWRP and not overwriting the stock recovery, the other, you're flashing TWRP as the default recovery. So yes, leave off the boot part and you'll flash TWRP as the default recovery.
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
Worked perfectly, thank you once again kind sir.

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.