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
Think I rooted it , tried to go into recovery, now I'm stuck. anyone here? right now? maybe can give me live assistance, over IM of some sort? pleaseeeeeeeeee
Looks like you're in the stock recovery, and the clockwork recovery mod was overwritten (it does that every time you reboot).
you can refer to this post for instructions on flashing the cw recovery again and rooting: http://forum.xda-developers.com/showthread.php?t=931865
it's basically just a fastboot command.
What do you mean you think you rooted it
Sent from my trinity nexus s
Also someone posted Odin with stock image...perfect for situations like this
http://forum.xda-developers.com/showthread.php?t=947950
i don't think we need to go the Odin way just yet
it sounds like he's in the stock recovery, he just need to do the fastboot, and all that stuff to get things going
The box pouring an arrow onto an android and/or the exclamation mark android is stock recovery. From there, just hit power first, hold it, then hit up arrow, you should get into stock recovery.
If that didn't work, pull the battery and let the phone boot normally. IF you're on 2.3.2 or higher, the install-recovery.sh script will replace the stock recovery in case you some how munged it up.
Reboot into fastboot with the volume key and power key, then when the box with the arrow appears do the power key hold and press the volume up, you should be in stock.
As others said, you can also just fastboot boot or fastboot flash the clockwork recovery image.
You're phone's not bricked, so no panic necessary.
edit: oh, and finally, if you actually succeeded in rooting, you could also just use ROM Mgr app to flash/boot to clockwork recovery, which is what you really should be using.
Hello, everyone. I'm brand spankin' new here and have what could be either a complete brain scrambler or a newb screwup. I searched everywhere and could not find a person in a similar situation, so please don't tell me to utfse, unless you have a special magic search engine from the future where the HTC Doubleshot has already been fully hacked and pimped out.
Anyway...
I successfully performed the permanent root and s-off procedure with Revolutionary.
Now, when I went to flash the clockworkmod custom recovery image for it, I got a successful installation message, but when I booted with volume down+power select recovery, it goes to the mt4gs splash screen and stays there. I have to pull the battery out and boot normally, because I can't flash a new image through recovery. I tried flashing from the clockwork mod rom manager under several similar devices, update.zip method and flashing it from fastboot in ADB and flashing it from the Terminal app, but to no avail. Is there another way to flash either a new recovery image or revert back to the stock recovery?
Re-flash recovery until it works from hboot. No chance of brick if you aren't flashing the hboot.
Also, give it a few minutes at the mytouch splash.
I tried it again. Waited 30 min, no luck. Is there another way to flash the image? When I tried it through adb it said the image couldn't be found or didn't exist, even though I had it in both the root folder and the sd card. When I tried it in terminal, it didn't recognize my command to flash_img.
Get cwm fro here http://android.modaco.com/topic/343...e-mytouch-4g-slide-unofficial-modaco-edition/
then use fastboot:
Code:
fastboot flash recovery doubleshot.clockworkmod.4.0.0.9.modaco.img
When I enter the command in adb it gets stuck on "waiting for device". I installed the htc device driver already and when I hit adb devices it comes up.
in adb ????
You should be in bootloader to run fastboot commands
How do I enter the command in the bootloader? When I select fastboot it gives me the option to reboot, go back to bootloader or reload bootloader. I can't get into the recovery menu, it freezes at the splash scree. Is there any way to flash clockwork onto it without having to go through the currently installed recovery?
Oops, nvm. Got it now. Thank you so much, all of you!
Ok, I have another question. Now, this one IS a stupid newb question. When I first rooted it, I got a little uninstall-trigger-happy, and deleted the htcsense3.0 launcher from my device. I know, I know, I'm retarded. But the good thing is I backed it up in Titanium backup before deleting it (also deleted it from TB). When I realized what a fool I was (after my home screen wouldn't come up0 I worked around it by holding the camera button and accessing the quick settings menu from the notification bar. I then Hold the Genius button and open the market, go to my apps, and open Titanium backup from there. I never thought I would say this, but thank god for the Genius button??
So, I've tried installing the .apk file from the sdcard in several different file manager apps, but with no luck. Is there a way I can force it back into it's original directory instead of reinstalling it?
I just installed launcher pro, but I'd like to eventually get back to the HTC sense launcher, however bulky and annoying it may be.
Thank you all for your help, you've been very helpful and not in the least bit condescending. I look forward to contributing to this forum.
IBtokin said:
I just installed launcher pro, but I'd like to eventually get back to the HTC sense launcher, however bulky and annoying it may be.
Thank you all for your help, you've been very helpful and not in the least bit condescending. I look forward to contributing to this forum.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214783
here's a link to download the stock ROM. It will reinstall everything for you including HTC Sense and whatever, and the good part is you don't have to erase data before installing, just download and install via recovery and you'll have everything back! Assuming, of course, that you can access titanium backup and unfreeze what you need.
That rom worked perfectly. Thank you.
[Q] Superuser wants to update, selected "Recovery Install", now screen is stuck
I am currently borrowing a friend's phone. I am currently not near any computers, and I won't be able to go home until next Monday.
Before all of this, I only know that Superuser wanted to upgrade. It suddenly shut off my phone, reboot, and then notified me of this. The notification popup recommended me to use Recovery Install foe HTC devices, which I did. And now, here I am.
My phone is stuck on the 4ext recovery v2.2.7 RC5 logo screen, the one with the red and blue sides of a circle, with a black zigzag line through the middle.
I am still able to tell the phone isn't completely stalled, as the battery charge percentage number can increase/decrease while charging it/draining it.
I don't know what to do right now. I can't turn off my phone via Power button, and can't control anything with the volume buttons.
Anyone knows what to do at this point? Thanks.
tom_mai78101 said:
stuck on the 4ext recovery v2.2.7 RC5 logo screen
Click to expand...
Click to collapse
This version number means that you're on the classic style recovery, not the touch recovery. You need to navigate it similarly to in fastboot. If it has become corrupt, you may need to re-flash a recovery. I would suggest 4EXT Recovery Touch v1.0.0.5, which is both a touch recovery and much more recent (mid-2013 vs late 2011).
Assuming S-OFF or unlocked bootloader;
To flash
Code:
fastboot flash recovery recovery.img
To run without flashing
Code:
fastboot boot recovery.img
tom_mai78101 said:
I am currently not near any computers, and I won't be able to go home until next Monday.
Click to expand...
Click to collapse
If you can't get into recovery and can't get into normal Android, even if you're S-OFF, you will need another device to send the commands to your phone. If you can get into normal Android and are S-OFF, you can attempt to dd as root the recovery image over partition mmcblk0p21, but be extra careful because any mistakes can cause even more serious problems.
All fixed, sorry for the delayed reply.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
download: https://www.mediafire.com/folder/w9nh7oyabwvww/tate
fastboot -i 0x1949 flash recovery tate_recovery_xxxxxxxx.img
restore old recovery:fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img
Flashed the img fine from twrp install menu, seems to work great. Marshmallow logo might not make complete sense, but there's no more graphical error when loading, so overall big improvement. :good:
r3t3ch said:
Flashed the img fine from twrp install menu, seems to work great. Marshmallow logo might not make complete sense, but there's no more graphical error when loading, so overall big improvement. :good:
Click to expand...
Click to collapse
Are you talking about the giant Marshmallow logo before going into TWRP? Too big imho
xWolf13 said:
Are you talking about the giant Marshmallow logo before going into TWRP? Too big imho
Click to expand...
Click to collapse
Yeah I admit it's a little too large but I do like it in general for MM roms. But for twrp, despite AOSP 6 base, a user could be using a non-MM rom and the logo could seem out of place. I also liked the blue kindle logo with twrp so I could differentiate between booting into recovery or system.
Either way, I suppose you should direct aesthetic complaints to @monster1612 as he pushed the new logo.
r3t3ch said:
Yeah I admit it's a little too large but I do like it in general for MM roms. But for twrp, despite AOSP 6 base, a user could be using a non-MM rom and the logo could seem out of place. I also liked the blue kindle logo with twrp so I could differentiate between booting into recovery or system.
Either way, I suppose you should direct aesthetic complaints to @monster1612 as he pushed the new logo.
Click to expand...
Click to collapse
Suggestions noted. I'll work on reducing the size of the logo (it was one of my first bootloader logo mods, so I wouldn't know for sure how it looked on a physical screen ). Also, I'll work on making a TWRP logo so one can easily identify what mode the kindle's booting into.
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
transi1 said:
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
rework f2fs
for test f2fs make backup, in "Wipe" twrp menu need try convert data and test boot rom, after convert cache and test new f2fs
Click to expand...
Click to collapse
This is over my head. I'll sit back and learn on this one.
transi1 said:
build 160312: http://www.mediafire.com/download/lbcna9arzznpmkk/tate_recovery_160312.img
Click to expand...
Click to collapse
I just noticed I can't boot into recovery by holding either of the volume buttons. Previous builds of twrp allowed booting directly into recovery by holding the volume up button. Is it possible to add this?
r3t3ch said:
I just noticed I can't boot into recovery by holding either of the volume buttons. Previous builds of twrp allowed booting directly into recovery by holding the volume up button. Is it possible to add this?
Click to expand...
Click to collapse
use old build or fastboot .... reboot oem recovery.
seems trouble with new CM-environment
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Maromi said:
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Click to expand...
Click to collapse
You could also just flash the img from twrp 2.8.7.0 the same way you flash a zip.
Maromi said:
repackaged 3.0.0 into .zip for flashing.
easy upgrade from 2.8.7.0. no fastboot required
Click to expand...
Click to collapse
Thanks! I'll give it a try. :good:
build (3.0.1) 160403: http://www.mediafire.com/download/b286zg2cs0go0i8/tate_recovery_160403.img
transi1 said:
build (3.0.1) 160403: http://www.mediafire.com/download/b286zg2cs0go0i8/tate_recovery_160403.img
Click to expand...
Click to collapse
Seems like something is wrong with this build. After flashing the img directly from last twrp 3.0.0 build 160312, rebooting to recovery causes the screen to go black. TWRP is technically running since MTP mount seems to still work, but nothing is being displayed on the tablet screen. Had to flash back old recovery from fastboot.
r3t3ch said:
Seems like something is wrong with this build. After flashing the img directly from last twrp 3.0.0 build 160312, rebooting to recovery causes the screen to go black. TWRP is technically running since MTP mount seems to still work, but nothing is being displayed on the tablet screen. Had to flash back old recovery from fastboot.
Click to expand...
Click to collapse
I installed the img by using fastboot flash and didnt see any issue.
Can you even flash an .img file?
Hey, I take it back. You are right If you do a reboot to recovery from within Android it goes black....
Ive been doing reboots and holding the volume key to get into recovery.
mikeataol said:
I installed the img by using fastboot flash and didnt see any issue.
Can you even flash an .img file?
Hey, I take it back. You are right If you do a reboot to recovery from within Android it goes black....
Ive been doing reboots and holding the volume key to get into recovery.
Click to expand...
Click to collapse
Yes, for awhile now in twrp you can flash an img file to either the boot or recovery partitions by pressing the img button in bottom right corner of the same file browser you use to flash a zip file.
Holding the volume key during boot isn't supported in these builds. If you need it you'll have to go back to 2.8.7.0.
r3t3ch said:
Yes, for awhile now in twrp you can flash an img file to either the boot or recovery partitions by pressing the img button in bottom right corner of the same file browser you use to flash a zip file.
Holding the volume key during boot isn't supported in these builds. If you need it you'll have to go back to 2.8.7.0.
Click to expand...
Click to collapse
from power off holding the (left)volume key with volume at top works... just did it....I just start holding at the orange splash screen
mikeataol said:
from power off holding the (left)volume key with volume at top works... just did it....I just start holding at the orange splash screen
Click to expand...
Click to collapse
Ah you're right. Not sure what I was doing wrong before then; maybe I was just holding them both or something.
@transi1
I appreciate all that you do, just a head's up.
Thank you for the great roms & twrp. (Save the last twrp build. ?)
tate_recovery_160403 only gives me a black screen. At one point I had the twrp background as a shadow border to my fastboot screen.
(That looked kinda neat!)
Back running tate_recovery_160312.
Sent from my Amazon Tate using Tapatalk
Both newer build of rr & twrp seem to be running fine on my jem.
Is Twrp 3.0.1. Stable? If not I will flash 3.0.0 and hope for the best, as I am well know for bricking kindles. I have like, 2 that are bricked that I can't fix, and another one with no recovery or os.