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
When I hold Power and Vol Down I get the text prompts, I hit Vol Up promptly and get the Android with gears turning animation for about 10 seconds, then get the Android with the warning triangle and can't go any further.
Any Suggestion? Tablet is a B80, rooted via Nachoroot. I have an SD card in the microSD slot.
I have Clockwork Mod (reboot into recover does a normal reboot) and Gnufabio's Reboot2Recovery (which ends with the Android and the warning symbol). It is my understanding that Rom Manager can't update the bootloader, so I haven't even tried.
Col.Kernel said:
I have Clockwork Mod (reboot into recover does a normal reboot) and Gnufabio's Reboot2Recovery (which ends with the Android and the warning symbol).
Click to expand...
Click to collapse
Are you sure you have CWM? Have you installed it?
When reboot to recovery doesn't load CWM is usually because CWM is not installed.
AzureusPT said:
Are you sure you have CWM? Have you installed it?
When reboot to recovery doesn't load CWM is usually because CWM is not installed.
Click to expand...
Click to collapse
Let me clarify. I have ROM Manager, and yes it's installed. I can't install a 3rd party Recovery because the bootloader is encrypted. It's a new Transformer (B80 s/n), not one of the older ones.
I am unable to boot into the stock recovery by any of the methods listed in the OP.
Col.Kernel said:
Let me clarify. I have ROM Manager, and yes it's installed. I can't install a 3rd party Recovery because the bootloader is encrypted. It's a new Transformer (B80 s/n), not one of the older ones.
I am unable to boot into the stock recovery by any of the methods listed in the OP.
Click to expand...
Click to collapse
ROM manager doesn't do anything for the TF. Just because you have ROM Manager install doesn't mean you have cwm recovery install.
You need to install CWM recovery as suggested by AzureusPT.
Go on the theme and app section and look for RecoveryInstaller. That will help you flash cwm.
Edit: here's the link
http://forum.xda-developers.com/showthread.php?p=19319421
baseballfanz said:
ROM manager doesn't do anything for the TF. Just because you have ROM Manager install doesn't mean you have cwm recovery install.
You need to install CWM recovery as suggested by AzureusPT.
Go on the theme and app section and look for RecoveryInstaller. That will help you flash cwm.
Edit: here's the link
http://forum.xda-developers.com/showthread.php?p=19319421
Click to expand...
Click to collapse
Thank you!!!!
Hi All,
I've looked all around for the answer to this and am thoroughly lost. I have the Verizon Galaxy S3 with VRALHE. I rooted it, then used EZ-Unlock 1.2 to unlock the phone, then installed Rom manager and flashed CWR. It says it installed 6.0.1.2 but when I try and go into recovery it only goes into Android Recovery. If I flash CWR and right away click the boot into CWR button it seems to go but after that it will only go into Android Recover both via Rom manager and holding Volume Up, Power and Home. Anyone know whats going on?
Thanks for your help!
If it does go into cwm the first time then after that stock there are two files you need to erase that basically reinstall the stock recovery on reboot. I can't recall them, but you could probably search here and find them. Or the easier way is busy flash a custom ROM n that first boot into cwm. By the way ez recovery is better for installing our recoveries, give it a shot.... It may sick without the extra stuff I just told you.
Sent from my SCH-I535 using xda app-developers app
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Boss428man said:
Anyone know where to look into about the files that need to be deleted? I'm not finding much. EZ recovery worked the first reboot but returned to Android recovery after a reboot.
Click to expand...
Click to collapse
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
I like to help, but Google stuff. This is what you would have found as the second result
/system/recovery-from-boot.p*
/system/etc/install-recovery.sh
Sent from my SCH-I535 using xda app-developers app
So to confirm to everyone, Deleting the 2 files above does work! So delete the files then re-flash CWR and restart that's it!
I wanted to thank everyone for the help!
Same problem but a little different
shimp208 said:
I would recommend re-flashing Clockworkmod Recovery from EZ recovery, then using EZ recovery to boot into Clockworkmod Recovery, after your are in Clockworkmod Recovery select the "Reboot system" option, you should then be asked if you want to erase two files to make Clockworkmod Recovery stick permanently (At least until you flash a different recovery) select the "Yes" option, then after it has completed that task the phone should reboot, while it is rebooting boot into recovery and you should find that Clockworkmod Recovery is still installed.
Click to expand...
Click to collapse
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
What rooting guide did you follow? Did you flash Clockworkmod Recovery yet? If you can provide me with this information I can try help you further. If you haven't flashed Clockworkmod Recovery yet then you will be presented with the normal stock Android recovery system that you described.
Wizardtech-101 said:
I have the same problem sorta, my phone instead of going into CWR it goes into Android system Recovery, and it asks me for an update, I was trying to root my phone but it won't even let me go into recovery so I can root it. Do you know why it's asking me this? Also idk if this helps but the android dude is in the background with an open stomach and a triangle and an exclamation mark in it. Hope my details were helpful, thanks.
Click to expand...
Click to collapse
Ummm... You do not necessarily go into recovery to root it. Have you installed and used Odin through your PC? You say you are trying to root your phone, so before you get ahead of yourself trying to flash recoveries I recommend reading up a little bit, it is very important you follow directions specifically or you will brick your device....
http://forum.xda-developers.com/showthread.php?t=2046439
There is even a video watch it while you root your phone, and pause along with it.
If you have already done some of this, and done any of it wrong there are steps to recover through Odin.
SL101 with CWM 1 click root v.1 which i understand is basically the same as the TF101
Tried rooting and seemed to be a success but bricked when trying to install cy mod.
Tried factory reset in recovery mode and still bricked.
Won't mount to SD card.
Can't seem to find any guides to reset firmware back to stock...
Any ideas? links to a guide i haven't found? (I have looked) or am I bushwacked?
Thanks.
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Did you use ROM Manager to install CWM?
That does not play nice with the Asus tablets.
You can try using PERI to push a new recovery via ADB when in recovery.
I would use ADB to push the TWRP 2.3.2.3 blob myself.
*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
chchas said:
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
Click to expand...
Click to collapse
Follow freds instructions above
*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
ALSO. Might note that I do not have access to my tablets home screen AT ALL. Not through cold boot or anything (unless it takes more than 30 minutes to cold boot)
chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
*Detection* said:
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
Click to expand...
Click to collapse
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
chchas said:
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
Click to expand...
Click to collapse
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
*Detection* said:
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
Click to expand...
Click to collapse
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
chchas said:
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
Click to expand...
Click to collapse
Been there done that. I had to use adb commands to push a new recovery blob. What version of cwm are you using again?
I have always had to use this one. After having this exact same issue.
D
DatDude123 said:
I have always had to use this one. After having this exact same issue.
D
Click to expand...
Click to collapse
v6.0.1.3
Do you have instruction on how you fixed yours? or a link ?
http://forum.xda-developers.com/showthread.php?p=16557195
This is what saved me. Alk I flash now is arhd and revolver. I do not attempt jellybean any longer......it was me, a laptop, and the tablet connected via usb and using adb commands. You are about to learn a lot.
D
So are there any handy links to a step by step of this? i found one for a Prime but i don't think it's the same thing....
So I followed this guide for adb http://forum.xda-developers.com/showthread.php?t=1071584 and got all the way to the end'. Now i'm stuck, where do I go from here? I don't want to screw anything up so any pointers will help!
Also, i can do this adb stuff while in recovery mode right?
Thanks!
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?