Develop Bugs

[FIXED] Help!Cant flash any recovery images

Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....

It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!

I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...

coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.

Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good

timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now

so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...

If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4

I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA

topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App

Nevermind I got the Su command to work
Sent from my PC36100 using XDA App

you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.

Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!

hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?

Build number 1.47.651.1 CL195459 release-keys

yea same here......and what is it that your trying to do...go back to stock ROM?

I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.

OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!

Oh Boy...Huge Error...Help Requested

Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.

fisheric1 said:
Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.
Click to expand...
Click to collapse
Need any and all information about your phone. I also notice that you are new. The dev section isnt for Q/A there is an entire section dedicated to solving these issues. Please remember that next time. Keeps things cleaner. So please gather anything you can about your phone. Method, Hboot, Version, Radio, Anything that can help anyone here identify something.

Do you have the rom in the root of the usb card? If so try full data wipe and installing the room see if it boots up.

Thanks for the quick reply. Will remember. Desperation has gotten the better of me. I will move over to Q/A if you prefer.
HBOOT-2.10 0001
RADIO - 2.15
Initially rooted via Unrevoked 3 beta RC2 yesterday.

if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)

T3hPWN said:
if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)
Click to expand...
Click to collapse
I agree with this method... the best way to determine the recovery to use would be to go into the terminal and type
Code:
cat /proc/mtd
if you see "400000" then you need to get the clockwork v3.0.0.2 that supports this phone partion layout. If you see "20000" then you should get amon_ra 1,8 from here:
http://forum.xda-developers.com/showthread.php?t=705026
The information I gathered was from this post:
http://forum.xda-developers.com/showthread.php?t=894331
Making sure you have the correct recovery is the first step. Once that is done create a nandroid and save it somewhere to ensure that the wimax partition is saved.

You have to flash the modified version of Amon_ra found in Zikronix thread. You can find my thread that points to it or just search for hboot 2.10 and follow the instructions in that rooting thread. It seems you're already rooted so just flashing the recovery is probably all you will need.

I haven't used unrevoked, and I know there are several versions. But I have seen others who have used unrevoked and couldn't flash anything bc evidently the method they used to root didn't install the flash_image file on their phone.
I know that installing flash_image fixed being able to flash for some people who rooted with unrevoked.
This issue came up and I was able to help some people, if you check near the end of fastRX8 thread. But I was only able help point the right direction, they figured out the rest of the way. The OP there has the flash_image file and tells you what terminal commands to install it.
I don't know how for you to check if you gave it or not, as I can see mine on sd card cuz I put it there when I rooted.
Beyond this suggestion, lithid can probably help much better than I.
But def post your hardware version, root method, and hboot version (you see that when you go into bootloader and read the top line.
Sent from my PC36100 using XDA App

Wow, sorry, theres been several posts since I started tying. Looks like these guys got it for ya
Sent from my PC36100 using XDA App

Was there a resolution for your problem? If so please post so anyone searching in the future can resolve there problem quickly.

you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.

dkdude36 said:
you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.
Click to expand...
Click to collapse
You mean the modified amon ra recovery image?

exactly...

dkdude36 said:
exactly...
Click to expand...
Click to collapse
Ya it worked for someone else in the Amon_Ra Clockwork thread here is the link.
zikronix said:
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to.
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
Click to expand...
Click to collapse
OP flash the PC36IMG in the bootloader to load this new recovery, then you can go into your new recovery and flash a new rom.

i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?

defjef123 said:
i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?
Click to expand...
Click to collapse
Were you restoring a backup or did you stuck on loop on a new rom flash?

i wasnt even trying to flash a rom yet. i was doing the very first nand backup so i could check some roms out. after the backup was complete it gave the option to power off so i did and when i turned my phone back on it was in the bootloader loop. so i went back to recovery, wiped everything, restored nand and i said it restored but when i rebooted it was back in the bootloader loop.so i just search around trying to get help but couldnt find much so i put sprintlovers since it boots up right when you turn your phone on. now it wouldnt even nand backup it said some error and was in the bootloader loop again so i just reinstalled sprintlovers, again

Try downloading an actual rom in zip format (not sprintlovers pc36img) and see if you can flash a new rom fresh. Make sure to wipe everything.
Try using Caulkings format all zip in recovery to wipe your caches.
http://www.mediafire.com/file/ikylelx99c49133/Calkulin's_FORMAT_ALL.zip

put in on my sd card turned my phone off to go into recovery and now my phone wont even turn on

it came on now. gonna try to wipe and flash that rom

Stuck on boot screen! Help!

Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible

Hi, I'm basically in the same boat (I take it you tried one of the stable CM6 builds?).
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<

enectrixx said:
Hi!
I bought a Desire HD a week ago and today I decided to try one of the custom roms. I rooted it with Visionary+, turned s-off with the one-click tool found in another thread, installed Rom Manager and Clockwork mod and then flashed it with a custom rom from the recovery/boot screen without wiping anything.
The problem is, when I later tried to install another rom, it wouldn't boot, it's stuck on the HTC boot screen. I've tried reflashing it, wiping everything there is to wipe and I even tried RUU but it won't recognize the phone. Can anyone help me how to restore to the normal stock rom?! I can bring up the Clockworkmod recovery menu if I take out the battery and put it back in.
I would be very grateful if someone could help me with this! Consider that I'm a noob though so try to write the instructions as simply as possible
Click to expand...
Click to collapse
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.

Headwoünd said:
Hi, I'm basically in the same boat.
Digged through an awful lot of stuff, found something about downgrading clockwork.
Maybe this'll help you, I'm still having trouble.
I've found an older clockwork recovery image, gathered all the SDK bits and pieces, got my USB drivers set up after even more digging - now this:
D:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY
booting--- FAILED (remote: not allowed)
It's rooted, S-OFF, all that good jazz. Halp. :<
Click to expand...
Click to collapse
seems like your pc is not recognizing your phone. And should not you flash the recovery first and then boot?

I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.

Headwoünd said:
I did flash the recovery via Rom Manager, which gave me Clockwork Recovery version 3.0.0.5.
Then I had Rom Manager download CM6, it rebooted the phone, phone gets stuck in HTC splash screen.
According to the thread I linked above, I needed to downgrade Clockwork Recovery, hence flashing 2.5.x.x via command prompt.
The drivers are installed correctly, I'm at least sure of that.
Recovering my previously backed up stock ROM won't get me further than the splash screen either, same with wiping everything that can be wiped before that.
Click to expand...
Click to collapse
Then use ROM manager to downgrade the CWM to 2.x. You can do it under the option "All recoveries" in ROM manager. People are reporting problems with the latest version of CWM. Check if you get the same if you wipe everything and install another custom ROM.

Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.

Same here. When I boot I just see the initial "HTC" logo, nothing else.
I had Mike's Revolution HD ROM installed and working just fine, and then I tried to install another mod, which got me to this situation.
I have CWM 3.0.0.5 and I have a nandroid backup of the working system from before installing the last mod.
I tried recovering the nandroid, which goes smoothly (including the MD5 validation of the backup) but it still doesn't boot afterwards. I wiped the boot, system and data partitions and tried restoring again - same result.
I assume my next step is to flash a new ROM but unfortunately I don't have any ROMs on my SDCARD, so I need a way to push it there. I tried with fastboot but it doesn't recognize a partition called "sdcard". I believe adb should work while I'm in CWM but it just says "error: device not found".
Any suggestions?

sphuyal said:
Which version clockwork mod are you using? And what is the ROM you tried to flash?
Sometimes custom ROMs can take 5 minutes to boot...so give it some more time and see if that helps.
Click to expand...
Click to collapse
Sorry, no idea which version, but it's the default that comes with Rom Manager. I downloaded Rom Manager yesterday so I guess it's the most recent Clockwork mod.
Left it for 15 minutes, still nothing. I used Android Revolution HD 2.0.11 for the first flash which worked and then when I tried to install Pays-ROM HD Sparta 1.0 I got stuck on the boot screen. I've tried recovering from the previous backup I made on the recovery screen with no result.

Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5

Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.

as a rule i have found out cwm3 is for flashing gingerbread and cwm2 is for froyo

Headwoünd said:
Went a different approach - finally figured out that you could mount the sdcard via Clockwork Recovery, threw newest CM7 nightly on there and installed it with Clockwork as well.
CHRIST that was a pain in the ass... and I thought downgrading the stock ROM was annoying.
Click to expand...
Click to collapse
Thanks for the advice! It worked for my DHD too Except that I, after flashing ut with CM7, restored it to stock with RUU! Thanks to everyone here who tried to help

erank said:
Just got mine back alive
Flashed CWM 2.5.1.3 and restored the nandroid with it.
Spending the last few hours searching the forums my best advice is to avoid 3.0.0.5
Click to expand...
Click to collapse
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?

encrypshun said:
how do I get 2.5.1.3 onto the device when I can't even get the darn thing to load?
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.

sphuyal said:
Read here: http://forum.xda-developers.com/showthread.php?t=855490&page=132 (jump to page 132 #1312)...
Take your battery off, then put it back in. Hold power button and volume down button at the same time. You come to recovery...or alternately you can use adb.
Click to expand...
Click to collapse
mate you're a STAR. I actually downloaded a recovery image (from post 1315) in the same thread but it kept saying "connecting to device". When I downloaded the recovery image from 1312 and ran "fastboot flash recovery recovery.img" it say's
sending recovery ... OK
writing recover ... OKAY
What do I do next? Just reboot the device?

oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1.3 and boom I'm in. Man I though the device was a goner....I'm almost feeling brave enough to install Cyanogen 7.X

encrypshun said:
oh mother looks like I got somewhere. I did a format device and it went into the CWM 2.3.XX screen as below, reloaded Cyanogen 6.1 and boom I'm in. Man I though the device was a goner....
Click to expand...
Click to collapse
So you are happy with your device now?

Well not really, I went back to HTC Sense because Internet Pass Through wasn't available on Cyanogen and now I cannot get the phone to login and create my google account no matter what

Headwoünd said:
Can't find a way to even get past the first splash screen - only thing I can properly access is the Bootloader.
Click to expand...
Click to collapse
the REMOTE NOT ALLOWED error means you only have radio s-off, so you cannot issue fastboot commands to your device.

twrp getting stuck on team win boot img when i try to get to recovery

hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?

mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
Cwm 5.0.2.7 all day.
Sent from my SGH-T989 using xda app-developers app

I have exactly the same issue. I had problems trying to wipe cache on CWM 5 so I installed through Goo, now when I boot into recovery, it gets stuck on TEAMWIN screen.

files- images
make sure you have the file in the right place wwhen you know you do get the switcher and then down ld. the file again i had to trial and error it a few times :victory:

The newest twrp gets stuck for me too. I just flashed back to a cwm

noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Same issue here on the Telus T989D. Any solutions without using cwm?

You can always try the manual method if your brave and familiar with the terminal. Go to Team Win's for our phone here: http://teamw.in/project/twrp2/101. Download the .IMG file and follow the instructions under Download - Recovery Image Method (using dd): Not hard but doublecheck your typing before hitting enter or you'll brick your phone.
I'm not responsible for any actions taken because of this post. Good Luck, its worth it in the long run.
Sent from my SAMSUNG-SGH-T989 using xda premium

One small problem with that.....
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:

This worked for me:
reflash CWM, flash superwipe, install TWRP through goomanager.

i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753

dailo23 said:
i had the same problem on my t989 and this odin flashed version posted here worked fine
http://forum.xda-developers.com/showthread.php?t=1852753
Click to expand...
Click to collapse
I flashed that version through Odin and it seems to be running just fine. I wiped caches and now TWRP appears to be working normally :fingers-crossed:

mightymike889 said:
hey i just tried to change my recovery bc cwm got messed up with the whole cache not being able to wipe. so i went through goo manager and tried to install twrp it looked like it install right and when i go into recovery it get stuck on teamwin boot img and doesnt do anything. what should i do?
Click to expand...
Click to collapse
EDIT: Wow I guess I didnt read the critical part where your stuck on the recovery boot screen so the attachment below wont help.... JUMP DOWN TO POST #21 AND FOLLOW IT TO RECTIFY THE GETTING STUCK ISSUE
Here, try this file guys. Someone over in the Jedi threads made a CWM flashable TWRP zip. You can thank me for bringing it to your attention if you want, but I did not create this ( I just clicked on the attachment paperclip for the thread and browsed through all the attachments because I knew I saw it somewhere in the development section...)
I also checked TWRP's own website and for the Hercules, v.2.3.1.1 is the latest version supported for our device so far but I only found 2.3.0.0 packed in a recovery flashable form.
Just flash it via CWM like any other zip and once its done it'll reboot your device automatically to system, so just reboot it back to recovery to make sure it worked. It did for me when I did awhile back with v.2.2.2.0 and I just used the below file to flash and update it in TWRP to v.2.3.0.0
Hope it helps

incgnito said:
Hi guys. I'm having a somewhat similar issue, but it's a little more problematic than that. I was in mid-flash when I unfortunately learned that any attempt to work with the cache resulted in an immediate freeze-up. From what little of the log I've seen, it's trying to tell me that the cache partition is read-only. Any attempt to unmount, wipe, or work with the cache in any way will result in an immediate lock up. This is *after* wiping the system and data partitions. I have been able to get TWRP to start correctly twice in the last 40 times I've tried to boot up the phone.
Question: I noticed that TWRP has a button where you can enter a terminal command. I don't have adb set up yet on this machine, since reloading it. I would imagine the answer would be 'no', but is it possible to put a different recovery image on the sd card, then use TWRP's terminal button to issue the command to flash it, or would that make matters worse? Or am I going to have to set up adb and odin again on another machine and use that? Any feedback would be greatly appreciated.
Side note: I should've stayed with CWM non-touch. :crying:
Click to expand...
Click to collapse
i just started having this exact problem with the cache partition. it will freeze on me whenever i try to reformat it, i can't unmount it, etc. i also get stuck on the twrp "teamwin" blue start up screen. have you figured out a solution?
edit- got it working again.. ended up odin flashing twrp 2.2 and i was able to wipe everything and install the new rom stuff.

noodles2224 said:
The newest twrp gets stuck for me too. I just flashed back to a cwm
Click to expand...
Click to collapse
Will you kindly explain how you did this?

y0urm0msname said:
Will you kindly explain how you did this?
Click to expand...
Click to collapse
What exactly is your issue?

Eks Dee Aye said:
What exactly is your issue?
Click to expand...
Click to collapse
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!

y0urm0msname said:
Same as OP. I have never re-flashed CWM. This was my first time trying TWRP. I am looking for instructions to either...
Re-flash CWM
Re-install a version to TWRP that works
Thanks!
Click to expand...
Click to collapse
Do you currently have CWM or TWRP as your recovery?

Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
Currently the non-functioning TWRP. I tried flashing CWM from the Rom Manager app, but that froze too. Looking for a reliable fix. I do not have a preference for recovery.

Eks Dee Aye said:
Do you currently have CWM or TWRP as your recovery?
Click to expand...
Click to collapse
If you have either I guess it doesn't really matter. Just install/flash the attached file below just like you would any other rom via your recovery.
After it installs reboot back into recovery and you will see the old recovery replaced with the latest TWRP for the T989.
Lemme know if this works for ya.

Eks Dee Aye said:
Just install/flash the attached file below just like you would any other rom via your recovery.
Click to expand...
Click to collapse
This is the part I don't understand. If my TWRP is stuck, how do I install/flash via my recovery?

[Q] HTC One M8 (bricked?)

Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything

thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.

I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.

thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.

Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?

thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.

Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error

Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw

thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.

Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.

@thetinyjesus You could also try this app. No PC necessary.

Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe

thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.

Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks

If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.

Okay once im back home ill show the output

Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.

Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted

Anyone?