Related
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
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Red Fox said:
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Click to expand...
Click to collapse
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
simms22 said:
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
Click to expand...
Click to collapse
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Red Fox said:
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Click to expand...
Click to collapse
ahhh, i misunderstood you first. try flashing the recovery again.
simms22 said:
ahhh, i misunderstood you first. try flashing the recovery again.
Click to expand...
Click to collapse
I just tried the recovery OS ROM, no progress, still freezing the same. Could you please explain this recovery, that you suggest?
If the system doesn't make it to the next stage/screen, w/the android. I feel like something is missing to pass go, and collect $100 big one's, LOL!
Sent from my Nexus S
Note: I also attempting this through, ROM Manager. As Bootloader triggers same results. ROM's are all DL'ed from http://mirror.teamdouche.net/?device=crespo (Blank Stare)
Sent from my Nexus S
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Red Fox said:
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Click to expand...
Click to collapse
I do have exactly the same problem.
Which recovery.img did you flash?
stiefa00 said:
I do have exactly the same problem.
Which recovery.img did you flash?
Click to expand...
Click to collapse
Here is the recovery.img that I flashed:
http://www.megaupload.com/?d=C933QJOO
Same recovery.img used when rooting, here is the source:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
Sent from my Nexus S
Another alternative, Terminal Emulator:
- install recovery to sd-card(no folders)
- Terminal:
su
flash_image recovery /sdcard/name-of-recovery.img
-=Edit=-
Phone should pause for a second and then show you a new blank line. Turn it off and back on. Holding down VolumeUp and Power to ensure it flashed correctly. Done.
Sent from my Nexus S
thx, got it!
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
ykphuah said:
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
Click to expand...
Click to collapse
Dude, this is discussed in multiple threads already.
The OTA 2.3.1 and 2.3.2 updates place a new script in the /etc folder that checks the crc on your recovery image at every bootup. If it fails, a backup copy of stock replaces it.
If you want to stay on Clockwork, you need to rename the file /etc/install-recovery.sh to something like /etc/install-recovery.sh.bak
Ah ok thanks! I din know where or what term to search for this.
I was just about to try updating from NScollab 1.0.39 to 1.0.40 and for some reason my nexus s refuses to boot into recovery. It doesn't seem to exist anymore. Im not sure if it is related or not but my phone became very laggy after my first failed attempt to boot into recovery. I tried fixing user permissions and rebooting many many times but it doesn't seem to help.
What does it do when u try to boot into recovery?
Sent from my HTC Sensation 4G using XDA App
It doesnt do anything. It just reboots into the bootloader.
Thank you for the quick reply
edit:
i tried flashing recovery again through rom manager and now whenever i try to boot into recovery it just hangs at the google logo with the unlocked padlock.
Hmmm
Do me a quick favor.
go here:
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
and download the 4.0.0.2 recovery image and save it to some directory on ur computer
then follow these steps:
1. Open up command prompt/terminal and plug in phone to computer
2. Type "adb reboot bootloader"
3. It will take you to fastboot mode. Now type "fastboot erase recovery"
4. Then type fastboot "flash recovery ____.img"
( ____ is the name of the recovery img file)
5. Now it will flash and once it says "OKAY" then scroll down using volume down into recovery and see what happens
plz get back to me bout this!
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
i so hate rom manager! i cant believe that people still use it
shahravi94 said:
IT WORKS! It went into recovery! Thank you so so much! Is there anything else I should do or am i set to go?
Click to expand...
Click to collapse
Since it works, you can wipe and flash ns collab lol
Sent from my HTC Sensation 4G using XDA App
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Yeah prolly a ROM manager issue
Sent from my HTC Sensation 4G using XDA App
shahravi94 said:
Thank you so much for the quick help! btw i updated recovery from rom manager and i ran into the same problem with it not booting into recovery so i am guessing there is a problem with the latest version of recovery? I'll just reflash through the instructions you gave me.
Click to expand...
Click to collapse
the recovery generally doesnt stick if flashing it through rom manager. flash it through fastboot and itll stick.
Hmm thanks for the advice! ill keep that in mind
Hi,
I rooted my Samsung Infuse and flashed CM7 as explained in http://forum.xda-developers.com/showthread.php?t=1311960
It looks awesome, many thanks to the people who put it together. ( I couldn't reply there since I am a "noob")
My phone boots fine in to CM7 and I can make calls and use other hardware, no problem so far.
I was trying to get Gapps by going to Rom Manger -> Download ROM -> Scroll down to Google Apps. It reboots and ends up at the screen with the white triangle around an exclamation and the android icon. I do not get the ClockworkMod menu. I have to press and hold the power button to reboot normally and get back to CM7.
Am I missing the recovery executable file? I looked in /system/bin and /sbin and it is not there. Should I copy the one I used earlier in to /system.bin ?
Thank you.
I believe cwm can show that when it is working, on some builds you can toggle between it showing the files being copied and that screen with the power button if I remember right.
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
suryathesun said:
Thanks for the reply, Dani897.
I am trying to get the Google apps installed which I couldn't since the recovery mode isn't showing up.
Any hint how I can get them on?
Click to expand...
Click to collapse
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Dani897 said:
Not really sure, I don't run CM7. But if you are using ROM manager it might just start flashing and never enter the menu.
If it is hanging maybe you can find gapps.zip on xda somewhere and put it on the sd card. Then use the reboot into recovery option instead of the flash ROM option in ROM manager.
Click to expand...
Click to collapse
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
suryathesun said:
Thanks Dani897, didn't realize the reboot has recovery option. Now I have the Gapps installed.
In fact, CWM showed up when I rebooted into recovery mode. Wonder why ROM Manager couldn't do that.
Click to expand...
Click to collapse
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Sarius24 said:
Why not install the. Apk's instead of flashing the Google aps
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Thanks for the reply Sarius24, I will try that the next time.
Do you happen to know of a reliable source for such apk's?
Dani897 said:
If I remember correct ROM manager has several options, 1 is to download and flash roms, 1 is to flash from sd card 1 is to reboot into recovery. if you use the first two options it goes into recovery but not the menu, it skips strait to flashing so you don't needed to do any more work, it only shows the menu if you reboot into recovery.
Click to expand...
Click to collapse
Good to know that. In fact, I tried the "Download ROM" option which downloaded the Gapps zip and rebooted in to the white triangle screen.
Now moving onto fixing other issues
Thank you.
It is impossible to use the bottom command for rebooting into recovery mode in stock ROM.
Code:
$ reboot recovery
Then, I made a patch for solving this problem.
After installing this patch, you can reboot into recovery mode to type the bottom command into ADB or Terminal Emulator application.
Code:
$ reboot-recovery
This .zip file is installed through ClockworkMod Recovery.
iBluemind said:
It is impossible to use the bottom command for rebooting Optimus 3D in stock ROM.
Code:
$ reboot recovery
Then, I made a patch for solving this problem.
After installing this patch, you can reboot into recovery mode to type the bottom command into ADB or Terminal Emulator application.
Code:
$ reboot-recovery
This .zip file is installed through ClockworkMod Recovery.
Click to expand...
Click to collapse
Or if your on custom rom you can just go to settings, Privacy and click factory data reset.. it wont delete anything click reset phone and it will take you into your CWM recovery..
It won't delete anything because you do not have the original recovery it will just go to cwm recovery you do what you need to and reboot. You don't lose anything unless you format while your in recovery. Simple solution. But thank you very much for this ...
Meemo23 said:
Or if your on custom rom you can just go to settings, Privacy and click factory data reset.. it wont delete anything click reset phone and it will take you into your CWM recovery..
It won't delete anything because you do not have the original recovery it will just go to cwm recovery you do what you need to and reboot. You don't lose anything unless you format while your in recovery. Simple solution. But thank you very much for this ...
Click to expand...
Click to collapse
Oops.. oh my mistake... I edited this thread..
This patch just enable rebooting into recovery mode(like CWM Recovery) easily.
This patch may enable that adding "restart" button into shutting down menu is easy.
Sent from my LG-SU760 using XDA
If you're using CyanogenMod, you can reboot into recovery straight from the power menu
pandaball said:
If you're using CyanogenMod, you can reboot into recovery straight from the power menu
Click to expand...
Click to collapse
Yes, I know that.
Sent from my LG-SU760 using XDA
iBluemind said:
Yes, I know that.
Sent from my LG-SU760 using XDA
Click to expand...
Click to collapse
You might want to consider re uploading as it is broken lol..
Meemo23 said:
You might want to consider re uploading as it is broken lol..
Click to expand...
Click to collapse
OK. I uploaded again.
the file is damaged
Forum likes to kill zip files. Upload it else where
Hello iBluemind and thanks for your work. This is a real "patch" or a replacement binary? I see it is somehow old, now.
Can we use it, for example, on my Samsung GT-S7562 (Duos S) that's rooted and re-flashed with stock 4.0.4 ROM (DDBMJ1) that was deoxed, rooted, optimized, bloatware-removed etc.? The only thing that I am trying to achieve and that's not there is the "Reboot into Recovery" option when selecting power menu… (or even reboot to recovery via SSH command, of course, as it doesn't happen now).
Many thanks to everyone!
Bro just type su before reboot recovery on stock to reboot to recovery!