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
As we dont yet have a custom recovery image for the Desire HD like AmonRA or Clockwork Mod, i have added ADB support to the recovery image that is currently used with perma rooting the DHD, it includes support for ADB Shell, Busybox, and mount commands, has SU shell by default and has RW permissions on all mountable partitions.
Requirements;
perma rooted desire with S-OFF HBoot
correct fastboot binary from HERE and adb drivers
Changelog;
V1: Initial Release
-DOWNLOAD
Clockwork MOD Test
Here is a test version of clockwork mod for the Desire HD, it is flashable and includes ADB Shell support, to activate the power button to choose options, you need to scroll through the menu 3 times until you see the message "menu back button enabled", this is due to the clockwork version being designed for devices with a trackball button.
DOWNLOAD
FLASH THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
How to flash;
Boot phone into bootloader mode (Hold volume down when powering on, or adb shell reboot bootloader)
run from cmd/terminal "fastboot flash recovery adb_recovery.img"
raider your a star will flash when wake up!
mikecoffee said:
raider your a star will flash when wake up!
Click to expand...
Click to collapse
so...your asleep?
Fantastic! Will flash this tomorrow after some sleep. Can't wait for the custom roms to come flooding in, especially some AOSP.
Sent from my Desire HD using XDA App
nice. flashed and working as should be!
here is a test recovery image for clockwork mod, it is based on the clockwork mod for desire Z/G2, as the Desire HD has no trackball button, if you scroll through the list 3 times until you see the message "menu back button enabled" the power button will become the select button.
THIS VERSION IS ONLY FOR TESTING UNTIL AN OFFICIAL CLOCKWORK MOD IS RELEASED, FLASHING IS NOT RECOMMENDED
http://db.tt/nt4dHN6
RaiderX303 said:
here is a test recovery image for clockwork mod, it is based on the clockwork mod for desire Z/G2, as the Desire HD has no trackball button, if you scroll through the list 3 times until you see the message "menu back button enabled" the power button will become the select button.
THIS VERSION IS ONLY FOR TESTING UNTIL AN OFFICIAL CLOCKWORK MOD IS RELEASED, FLASHING IS NOT RECOMMENDED
http://db.tt/nt4dHN6
Click to expand...
Click to collapse
Sweet dude, backing up via clockwork now! so at least it runs. I will probably flash back to your ADB recovery though, it got me out of a little schoolboy error I made earlier.
sweet, now time for making roms
good stuff! Backup and restore worked fine
then we just need a flash test of a rom
I'm working on a ROM based on the G2 Rom for a clean android, flashing update zips works. Just not managed to get it booting yet
Sent from my Desire HD using XDA App
So there's some positive feedback. Is the Clockword Mod version still not recommended?
AndyCr15 said:
So there's some positive feedback. Is the Clockword Mod version still not recommended?
Click to expand...
Click to collapse
I just bootet it, and it seems to run well. Just try it without flashing it.
AndyCr15 said:
So there's some positive feedback. Is the Clockword Mod version still not recommended?
Click to expand...
Click to collapse
Works fine here
LecterMe said:
I just bootet it, and it seems to run well. Just try it without flashing it.
Click to expand...
Click to collapse
Oh yeah, what's the command for that booting without flashing
Fastboot reboot xxxx.img?
fastboot boot xxx.img :-D
also can this sucsefully flash zImages via the update.script ?
Thanks, I went ahead and flashed it, works great. Scroll through the menu's 3 times to get the power button to work, as was mentioned above.
flashed this recovery today as I was getting twitchy Works fine thanks
mmmm
When I hit backup I get this
E:Can't mount /dev/block/mmcblkp1 (or /dev/block/mmcblk1)
(No file or directory)
Can't mount /sdcard
any ideas?
afrcom15 said:
mmmm
When I hit backup I get this
E:Can't mount /dev/block/mmcblkp1 (or /dev/block/mmcblk1)
(No file or directory)
Can't mount /sdcard
any ideas?
Click to expand...
Click to collapse
this may sound stupid but you do have full root and s-off with the bootloader?
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
When it boots to that, try pressing the home button
Sent from my Onyx CM7 Google Nexus S!
You mean on the exclamation screen? I vl try that but I don't I will help cost I had remove battery to make that screen go away
Sent from my Nexus S using XDA App
Just give it a go. Battery pulls don't hurt the phone.
Sent from my Onyx CM7 Google Nexus S!
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
What rom are you on?
everything stock ... clockwork mod installed from rom manager .. latest and current are same...but rooted.
kenvan19 said:
Just give it a go. Battery pulls don't hurt the phone.
Sent from my Onyx CM7 Google Nexus S!
Click to expand...
Click to collapse
Tried it. Nothing happens. Have to take battery out. But I can still access recovery by rebooting in recovery from rom manager
Try installing it from the bootloader.
Name the image file recovery.img
Put it in the android sdk tools folder(or wherever your fastboot.exe is) and run the command -
"Fastboot flash recovery recovery.img"
Then reboot, it should work.
The android with a "!" is the stock recovery. You don't have to pull the battery at that screen, just press hold power button, then press volume up, you should end up in stock recovery.
In ROM Mgr, FLASH clockwork recovery (twice for good luck, seriously) before trying to boot/backup from ROM Mgr. That should get you going.
The fastboot flash method mentioned above also works.
Part of your issue is that there's a file called /etc/install-recovery.sh that overwrites clockwork recovery with the stock one every time you boot up normally. Rename/delete that file and clockwork will stick after that.
suhas_sm said:
When I select backup Rom in ROM manager, it reboots and i get a screen with an exclamation mark with an android bot. Same thing happens when I try to get into recovery with power on + volume up button.
But when I select reboot in recovery from rom manager it works and i was then able to take a back up from there.
What do i do ? Current and latest clockwork version are same according to rom manager. I updated it twice using ROM manager to make sure its the correct one
Click to expand...
Click to collapse
I have found if you to flash Clockworkmod recovery from Rom Manager and you already have the same version, it will remove it all together.
just reboot your phone and run the recovery installer once. Right now, it should be version 3.0.0.5. After you run it. Reboot your phone -> hold power + up (or down don't remember) -> select recovery.
If it is there, you should be able to get to it from the Rom Manager link also.
Serious_Beans said:
Try installing it from the bootloader.
Name the image file recovery.img
Put it in the android sdk tools folder(or wherever your fastboot.exe is) and run the command -
"Fastboot flash recovery recovery.img"
Then reboot, it should work.
Click to expand...
Click to collapse
yeah will keep that as option if Rom Manager doesn't work for me.
distortedloop said:
The android with a "!" is the stock recovery. You don't have to pull the battery at that screen, just press hold power button, then press volume up, you should end up in stock recovery.
In ROM Mgr, FLASH clockwork recovery (twice for good luck, seriously) before trying to boot/backup from ROM Mgr. That should get you going.
The fastboot flash method mentioned above also works.
Part of your issue is that there's a file called /etc/install-recovery.sh that overwrites clockwork recovery with the stock one every time you boot up normally. Rename/delete that file and clockwork will stick after that.
Click to expand...
Click to collapse
Thanks for the information That should explain why Clockwork doesnt show up everytime. And yeah didnt have to pull the battery, simply went into default recovery from that screen Thanks. will try renaming install-recovery.sh
GchildT said:
I have found if you to flash Clockworkmod recovery from Rom Manager and you already have the same version, it will remove it all together.
just reboot your phone and run the recovery installer once. Right now, it should be version 3.0.0.5. After you run it. Reboot your phone -> hold power + up (or down don't remember) -> select recovery.
If it is there, you should be able to get to it from the Rom Manager link also.
Click to expand...
Click to collapse
I installed once again. It said no recovery or image found. Installed again, could go into clockwork recovery but after rebooting again the same
renaming install-recovery.sh in etc folder worked Now can I go into clockwork recover on every boot
Hi,
I use the tool root toolkit 0.8.3
I did "Backup & Root"
then Install "SU only"
then Install "touch recovery only"
I can't reboot in CWM -no app in ICS and no prompt when I close my tab and no cwm prompt appear when I push power + vol up or down....
how I can get this clock mod recovery ?
Best regard
Bankaiii
Volume down, then press power, then wait 3 seconds and press volume up.
If that doesn't work, try the PERI tool to get CWM.
Thing O Doom said:
Volume down, then press power, then wait 3 seconds and press volume up.
If that doesn't work, try the PERI tool to get CWM.
Click to expand...
Click to collapse
thanks to answer me, but now I installed "everything" I'm afraid to use 1 click tool.
Or I have to uninstall all to use 1 click safely.
I dont want have 2 tools installed for the same job.
Why there is no prompt to ask to reboot in cwm , its weird !
which difference between touch clockworkmod recovery v5.8.1.8 and cwm from 1 click aka PERI ?
Root Toolkit Problem
Yesterday I used the Toolkit to Root my Asus Transformer B70 i believe (sorry its not here with me). I followed all the steps and everything went fine. I then upgraded the CWM with Rom Manager, Rom Manager was granted SU Permission so i know the root is fine, however when i try to flash a new Rom (Cyanogenmod 9) it just reboots (not into recovery) and does nothing. i also find Superuser keeps crashing and i think it is when i go to flash the new Rom.
Any advice?
Rouge XM supports external storage. That's about it.
You can safely use PERI even after using the other tool.
adrian- ROM manager causes issues. Bad issues. See my warning in general...
PERI can also fix that, use the fix bootloop option.
and about "1-Click Transformer Root" - which difference ?
how I can know if Im rooted ?
Just use what you want to use. Everything works. 1ctr does root first then cwm. Mine does cwm then root.
oh my god ! it works
But I must confess one thing :
Windows try to install driver when I plug the Tab - so When I remove driver (from device manager) and reboot windows I have to click quicly on icon (green color in task bar) to ask to stop automatic install. Cause I already install your driver adb.
So I think automatic install driver from Windows is the main problem for many people try to root and put cwm.
Now Im under with PERI >> Rogue XM Recovery 1.5.0 (based v 5.0.2.8) !!!
Thanks !
which rom you advise me (this is next step
Whatever rom you like, I'm currently switching between AOKP and gummy :]
Stock based=
ARHD
Revolver
AOSP Based
Megatron/cm9
AOKP
Gummy
etc
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
DuhCiphered said:
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
Click to expand...
Click to collapse
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
DuhCiphered said:
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
Click to expand...
Click to collapse
No Odin has nothing to do with the bootloader.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2