Develop Bugs

Help me fix my Recovery

So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?

and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort

zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images

AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.

back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.

AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.

Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA

Stuck trying to install custom rom

Okay so I am trying to install the jdroid rom, btw first time ever doing this so bare with me, anyways I can't boot my phone stays at HTC quietly brilliant screen with some writing underneath it red. I can get into the bootloader menu, where I am rooted and says my bootloader is unlocked. I can also get into clockwork mod however I messed up when transferring the rom onto my phone. I unzipped it and put it there instead of leaving it in the zip file. I can't mount to my laptop through clockwork mod, is there any other way? Again I can't boot my phone. Thanks
EDIT: Now whenever my phone boots, it boots into the clockworkmod and keeps rebooting I can't do anything, cant mount my phone at all

Bizarre48 said:
Okay so I am trying to install the jdroid rom, btw first time ever doing this so bare with me, anyways I can't boot my phone stays at HTC quietly brilliant screen with some writing underneath it red. I can get into the bootloader menu, where I am rooted and says my bootloader is unlocked. I can also get into clockwork mod however I messed up when transferring the rom onto my phone. I unzipped it and put it there instead of leaving it in the zip file. I can't mount to my laptop through clockwork mod, is there any other way? Again I can't boot my phone. Thanks
Click to expand...
Click to collapse
Yes ... instal this recowery (Link to the latest unofficial test recovery with USB issues fixed and automount by RichardTrip) and you can push your zip on SD

Thanks for the reply
I used this command: fastboot flash recovery <Name Of the downloaded file>.img
But I'm still stuck at the boot screen

Bizarre48 said:
Thanks for the reply
I used this command: fastboot flash recovery <Name Of the downloaded file>.img
But I'm still stuck at the boot screen
Click to expand...
Click to collapse
You need to enter the fastboot mode ... hold "volume-down + powerbutton" for 10 secs and then again push the powerbutton to enter the fastboot mode.
Edit: and after that use the comand fastboot flash recovery nameofrecovery.img

Just saw the edit now will try thanks alot man appreciate it!

Bizarre48 said:
I did that, then when I went to recovery when it boots its at the htc quietly brilliant screen.
Click to expand...
Click to collapse
OK, did you instal the ROM + boot.img?
Edit: im going to sleep ... read THIS, if that doesnt help, then THIS

Okay I still can't do it nothing works! I flash the recoveries and I still get stuck at the htc boot screen. so frustrating

Bizarre48 said:
Okay I still can't do it nothing works! I flash the recoveries and I still get stuck at the htc boot screen. so frustrating
Click to expand...
Click to collapse
What you need to do when flashing:
a) CWM recovery
fastboot flash recovery xxxrecovery.img
fastboot reboot-bootloader
fastboot erase cache
b) Flashing a ROM
extract the boot.img from the ROM.zip
fastboot flash boot boot.img
fastboot erase cache
enter recovery
install the ROM.zip
reboot

READ THIS THREAD
http://forum.xda-developers.com/showthread.php?t=1609190
basically summarises what above posters are saying in step by step detail

Yea I'm just going to use the at&t ruu and restart to process all over again. hopefully this works

Bizarre48 said:
Yea I'm just going to use the at&t ruu and restart to process all over again. hopefully this works
Click to expand...
Click to collapse
Next time also read the instructions.
M.

as long as you can get the correct RUU and flash the correct stock recovery, RUU will defo work, then you can start again from scratch. I've done this myself
edit: AT&T????? Are you even in the correct forum using the correct files/methods??? HTC One XL is different forum, different files!!!!!!!!!!!!!!

Alright I got out of it using the st&t ruu, though I live in Canada and on Rogers. Data doesnt work but that is not surprise. Gotta wait for a root access and/or bootloader unlock for 1.85. will be patient.

Bootloop after Revolution HD 8

Hi guys,
i've got a big problem with my HTC One X after installing Android Evolution 8 from here
http://forum.xda-developers.com/showthread.php?t=1562603
I cant post in the thread there so I hope this is a good place.
I unlocked and rooted the HTC succesful with clockword mod.
After that I used this instruction:
http://www.youtube.com/watch?v=gxJf8xIVVC0
So i made a backup with clockwork mod, after that i wiped all the caches as said in the video and then I installed Android Evolution 8.
After reboot i got a reboot loop, after showing the startup screen the One X reboots, again and again.
I figured out that the problem could be, that i didnt use the superwipe tool, i justed wiped as in the tutorial.
Is there a way to reset the HTC or to restore the backup and to reinstall again or can I throw the HTC away?

Ok, sorry for the thread, I had no time to wait for an answer because battery was almost empty and didnt charge, so i risked it an tried to restore the Backup in Clockwork recovery.
That worked an now the HTC works fine again.
So i ll charge it and after that I user Super wipe before I reinstall Evolution 8 again.
Maybe the thread will help somebody else one day, cheers.

Steps to get out of boot loop
Hi,
You are probably got into a boot loop because the boot.img you have on your phone is not compatible with the custom ARHD ROM or is not correctly flashed. First charge the phone upto at least 50% battery (to be safe). Then try following the steps below:
1. Download this pack>> Fastboot Pack http://forum.xda-developers.com/show....php?t=1616741
2. Extract the boot.img from the Custom Rom you are trying to install in a folder on your computer.
3. Extract Fastboot Pack into a folder on your computer and replace the boot.img by the boot.img extracted from the Custom Rom in Step.2
4. Turn your phone OFF
5. Turn your phone ON in bootloader mode by holding the power and vol down buttons at the same time, your phone will start in HBOOT mode. It will be displayed somewhere in the middle of the text.
6. Use the volume keys to move up and down the list, and select Fastboot, then press the power key. Now your phone will come in FASTBOOT mode.
7. Connect your phone to the computer via USB cable. Your phone will now display USB FASTOOT instead of just FASTBOOT.
8. Run 05-erase-cache.bat
9. Run 06-flash-custom-boot.bat
10. Run 08-install-clockwork-recovery.bat
11. Disconnect the USB cable. Your phone will now again say FASTBOOT.
12. Use the up or down volume key to select HBOOT and press the power button. This will take you back to HBOOT mode.
13. Use the volume keys to scroll to RECOVERY and press the power button.
14. This will take you to Recovery mode, now you can flash the Custom Rom you want using Recovery mode.
Let me know if I helped by clicking Thanks

Hi,
thanks for your answer.
Unfortunately also after using the Super wipe i've got a Bootloop after installing HD 8.1.0.
The link with the fastboot Pack doesn't work, where can I find it?
After downloading Fastboot Pack, I have to replace the boot.img in the file Android_Revolution_HD-One_X_8.1.0.zip with that one from Fastboot Pack, is that right?

Just install boot image for ARHD 8.1 that is included in thread of ARHD. This definitely boot image problem. I think you didn't flashed it. Just follow the instruction on first page.
Sent from my HTC One X using xda premium
---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------
You can only flash boot image in fastboot mode, not in CWM.
Sent from my HTC One X using xda premium

I'm having the same problem (I think). After successfully installing the boot.img for ARHD 8.1.x, I get a bootloop trying to enter recovery mode (or trying to boot normally).
Edit: I installed ClockworkMod Recovery Touch prior to this but never tested it... Maybe that has something to do with it.

Fast boot tool
Dosum said:
Hi,
thanks for your answer.
Unfortunately also after using the Super wipe i've got a Bootloop after installing HD 8.1.0.
The link with the fastboot Pack doesn't work, where can I find it?
After downloading Fastboot Pack, I have to replace the boot.img in the file Android_Revolution_HD-One_X_8.1.0.zip with that one from Fastboot Pack, is that right?
Click to expand...
Click to collapse
You can use this tool instead of Fastboot ...
http://forum.xda-developers.com/showthread.php?t=1634786
And NO it is the other way round, You need to replace the boot.img in the tool by the one you get in ARHD and then run the tool. In this tool you will find a folder for boot.img which will contain one boot.img file already. Just replace that and run the tool. for HTC One X whenever you want to install a custom Rom, you need to do this.
A boot.img is normally a part of the custom Rom zip file which automatically gets flashed when you flash the rom. BUT this doesn't happen with One X due to some reason. So we need to flash the boot.img separately BEFORE flashing the ROM.
Let me know if the above helps by clickng Thanks
---------- Post added at 11:10 PM ---------- Previous post was at 11:04 PM ----------
joebrooks said:
I'm having the same problem (I think). After successfully installing the boot.img for ARHD 8.1.x, I get a bootloop trying to enter recovery mode (or trying to boot normally).
Edit: I installed ClockworkMod Recovery Touch prior to this but never tested it... Maybe that has something to do with it.
Click to expand...
Click to collapse
Hi.. What do you mean by getting a bootloop trying to enter recovery?
Which boot.img did you flash ? It should be the one which is inside the ARHD ROM zip file. So extract that and try following the steps in my reply above. If you still fail let me know the exact steps you took and issue and I will try to help.
Let me know if the above helped by clicking Thanks

Hi.. What do you mean by getting a bootloop trying to enter recovery?
Which boot.img did you flash ? It should be the one which is inside the ARHD ROM zip file. So extract that and try following the steps in my reply above. If you still fail let me know the exact steps you took and issue and I will try to help.
Let me know if the above helped by clicking Thanks
Click to expand...
Click to collapse
When I try to boot into ClockworkMod Recovery (by selecting RECOVERY on the HBOOT screen), I get a boot loop. Same thing happens if I select REBOOT from the FASTBOOT screen.
Yes, I'm using the right boot.img. It's my understanding I have to install this before I can install the ROM.
To install it, I put my phone into fastboot USB mode, and ran:
Code:
fastboot flash boot boot.img
fastboot erase cache
My One X is an S-ON device, btw.

Hi, it worked for me to flash the boot.img manually first
(boot.img for 8.1.x
S-ON devices can't flash boot.img in recovery, so you need to flash it manually before flashing ROM
--- MD5 Checksum: 6D2E1B1A7F0FA35BCB559A20089F3160 --- taken from http://forum.xda-developers.com/showthread.php?t=1562603), after that I could install HD 8.1.0 succesfully.
My One X is S-Off.

Dosum said:
Hi, it worked for me to flash the boot.img manually first
(boot.img for 8.1.x
S-ON devices can't flash boot.img in recovery, so you need to flash it manually before flashing ROM
--- MD5 Checksum: 6D2E1B1A7F0FA35BCB559A20089F3160 --- taken from http://forum.xda-developers.com/showthread.php?t=1562603), after that I could install HD 8.1.0 succesfully.
My One X is S-Off.
Click to expand...
Click to collapse
That's what I did, but I got a boot loop.
Where can I find a copy of the default boot.img? Or is there another way to restore my system to normal so I can try again?
Edit: Also, are there different boot.img's for different firmware versions?

Hi,
because the original thread with the boot.img has been moved/edited, I upped it for You:
https://dl.dropbox.com/u/8381571/fastboot.zip
Theres a description inside, after flashing the boot.img it should work for you, let me know if it helped.

joebrooks said:
When I try to boot into ClockworkMod Recovery (by selecting RECOVERY on the HBOOT screen), I get a boot loop. Same thing happens if I select REBOOT from the FASTBOOT screen.
Yes, I'm using the right boot.img. It's my understanding I have to install this before I can install the ROM.
To install it, I put my phone into fastboot USB mode, and ran:
Code:
fastboot flash boot boot.img
fastboot erase cache
My One X is an S-ON device, btw.
Click to expand...
Click to collapse
Ohh sorry I assumed your One X is S-OFF, you definitely need to do that FIRST, before going ahead with this flashing business. There is an awesome tool by hasoon2000 for doing this, which you can find here : http://forum.xda-developers.com/showthread.php?t=1604439
Just use the above tool to S-OFF your device, flash the recovery and then follow the steps I have given before. If you need more help with S-OFF let me know and I will provide detailed instructions for doing that.
Let me know if I helped by clicking thanks

ARHD 9
I just installed ARHD 9 and followed the instructions but now when it boots up it flashes onto the homescreen for a few seconds and then reboots, does anyone have a fix? i dont have a back up either

I think fastboot erase cache might be useful.
Every ROM requires (and is packaged with) a boot.img, you need to flash the ROM and you need to flash the associated boot.img.
If you get bootloops, make sure you have flashed the correct boot.img.
If the ROM reboots after it's started, make sure you superwiped when changing bases.
Basically, do all of the steps in the instructions, without missing out any of the steps.

JustJayBro said:
I just installed ARHD 9 and followed the instructions but now when it boots up it flashes onto the homescreen for a few seconds and then reboots, does anyone have a fix? i dont have a back up either
Click to expand...
Click to collapse
I have faced that issue in the past. Just flash again, follow the steps I have given before. Remember to clear the cache at the beginning, and flash the boot img that you get inside the ROM you are flashing i.e. the one inside ARHD 9. Also, before you flash the ROM, wipe data (NOT SDCARD) and dalvik cache as well.
Let me know if I helped by clicking thanks

Cannot access flashboot / recovery - RESOLVED

Hi,
I've looked through a lot of threads but can't match the symptoms to mine (this could be a lack of knowledge on my part) so any help is appreciated.
I've previously flashed ARHD a number of times successfully including a new boot image. I flashed 9.2 today with CD Tools Suite and this was fine. I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
The update ran successfully (per CWM) but I can't boot into it. All I get to is the HTC One white screen with a beats audio logo beneath it. I also can't get the phone to reboot into flashboot / recovery so that I can do anything with it (I've tried holding the power button and either vol up or down but this just reboots the phone and it goes back to the white screen again).
I'm sure there is a way out of this. Could anyone please help me?
Many thanks.

Hi, you wrote,
I later decided that I wanted to re-flash without the CD Suite Tools and did this by going into recovery and re-flashing the ARHD zip.
Click to expand...
Click to collapse
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.

Didn't someone say holding volume up & power can brick your phone?
Fastboot is volume down & power.
Press them at the exact same time, keep them held till fastboot loads up (even if it does another reboot)
Sent from my HTC One X using Tapatalk 2

phase sdeyou
Bit Banger said:
Hi, you wrote,
Did you use fastboot to flash the correct boot.img file first? It's my understanding that anytime you flash a rom you must flash via fastboot the correct boot.img file for that rom followed by erasing cache before entering recovery and flashing the rom.
Click to expand...
Click to collapse
They both use the same boot image so no need to re-flash that.

chrisjcks said:
keep them held till fastboot loads up (even if it does another reboot)
Click to expand...
Click to collapse
This was the key for me. It rebooted a couple of times then went into fastboot.
Thank you very much!

[Q] HTC One M8 GPE won't boot to custom recovery

Hi all-
I just received my HTC One M8 Google Play Edition today. I successfully unlocked the bootloader (I see the open padlock every time it boots), but I'm running into trouble with TWRP. I downloaded TWRP 2.7.0.3 from this thread. Since I'd like to get OTA updates in the future, I am attempting to boot (not flash!) TWRP using
Code:
$ ./adb reboot bootloader
$ ./fastboot boot ~/Downloads/openrecovery-twrp-2.7.0.3-m8_ul_ca.img
downloading 'boot.img'...
OKAY [ 1.251s]
booting...
OKAY [ 0.001s]
finished. total time: 1.252s
$
but after the second command, the phone just reboots to the normal system. I have attempted renaming TWRP to recovery.img, but that didn't change the behavior. I have tried a factory reset, and that didn't change the behavior. If I attempt to manually enter recovery from HBoot, I get the dead android logo.
I really just want to flash SuperSU.
Any and all help is greatly appreciated. Thanks!
Stephen

TWRP doesn't work on GPe for some reason. Use Philz CWM.
Sent from my HTC One_M8 using Tapatalk

Tikerz said:
TWRP doesn't work on GPe for some reason. Use Philz CWM.
Click to expand...
Click to collapse
I wondered about that, but for some reason I didn't find the Philz m8 thread until you mentioned it. So I downloaded CWM from this thread and had the exact same experience...
Other thoughts?
Thanks!
Stephen

A little concerned that I wasn't able to boot either TWRP or CWM, and (while I don't think I'd flashed anything) just going into HBoot and selecting recovery also didn't work (dead Android icon), I grabbed the 4.4.2 firmware from here and flashed the stock recovery.
After flashing the stock recovery I had the *TAMPERED* label in HBoot (which surprised me a little because I assumed stock would 100% match what was already there). Now if I selected Recovery from HBoot I would get a temporary flash of "This image is for development use only (etc.)..." and then end up back in HBoot. I tried once or twice more to just boot CWM and still no luck. So finally I flashed CWM, installed SuperSU, and then flashed back to stock. I guess I'll find out when the first OTA rolls around if the system is still "stock" enough.
Thanks,
Stephen

scbash said:
Hi all-
I just received my HTC One M8 Google Play Edition today. I successfully unlocked the bootloader (I see the open padlock every time it boots), but I'm running into trouble with TWRP. I downloaded TWRP 2.7.0.3 from this thread. Since I'd like to get OTA updates in the future, I am attempting to boot (not flash!) TWRP using
Code:
$ ./adb reboot bootloader
$ ./fastboot boot ~/Downloads/openrecovery-twrp-2.7.0.3-m8_ul_ca.img
downloading 'boot.img'...
OKAY [ 1.251s]
booting...
OKAY [ 0.001s]
finished. total time: 1.252s
$
but after the second command, the phone just reboots to the normal system. I have attempted renaming TWRP to recovery.img, but that didn't change the behavior. I have tried a factory reset, and that didn't change the behavior. If I attempt to manually enter recovery from HBoot, I get the dead android logo.
I really just want to flash SuperSU.
Any and all help is greatly appreciated. Thanks!
Stephen
Click to expand...
Click to collapse
I might be wrong, but isn't the command "fastboot boot recovery recovery.img" whereas "recovery.img" would be the path to the recovery you want to boot to without flashing? If I'm not mistaken, "fastboot boot" would boot the phone up to the system.

suprtrukr425 said:
I might be wrong, but isn't the command "fastboot boot recovery recovery.img" whereas "recovery.img" would be the path to the recovery you want to boot to without flashing? If I'm not mistaken, "fastboot boot" would boot the phone up to the system.
Click to expand...
Click to collapse
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen

scbash said:
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen
Click to expand...
Click to collapse
download the stock revovery listed here (in development).install cwm, root, and redo your stock recovery via fastboot

rbouza1 said:
download the stock revovery listed here (in development).install cwm, root, and redo your stock recovery via fastboot
Click to expand...
Click to collapse
Yup, that's what I ended up doing earlier this afternoon. Thanks though.
Stephen

Thus may be a dumb question but how do we root the gpe edition. I tried with weak sauce but it failed. Thanks
Sent from my HTC One_M8 using Tapatalk

aaronc_98 said:
Thus may be a dumb question but how do we root the gpe edition. I tried with weak sauce but it failed. Thanks
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I figured it out- http://howtorootmobile.com/root-htc-one-google-play-edition-unlock-bootloader-install-twrp/
thanks,

Fastboot boot stopped working on One m7 since 3.x. I'm assuming they continued the trend..
sent from my mobile device

Unfortunately non of the recoveries available will "boot" into recovery. Philz works if you flash the recovery. I would say flash philz recovery and then flash back the stock GPE recovery I posted in Dev

scbash said:
When I did it with my wife's Nexus 5, it was "fastboot boot <image>" (and there it worked without a hitch). In the middle of other things last night I did try that and got "no such file: recovery". So I'm still open to user error, but at least that particular change didn't fix my problem...
Thanks,
Stephen
Click to expand...
Click to collapse
Yep, found out I was wrong when I went to do it myself. After some research, it seems the code used to include the extra "recovery", but no longer does.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

SaHiLzZ said:
Fastboot boot stopped working on One m7 since 3.x.
Click to expand...
Click to collapse
graffixnyc said:
Unfortunately non of the recoveries available will "boot" into recovery.
Click to expand...
Click to collapse
Thanks for the confirmation SaHiLzZ and graffixnyc. I was worried I might have a bum phone there for a bit.
Stephen

SaHiLzZ said:
Fastboot boot stopped working on One m7 since 3.x. I'm assuming they continued the trend..
sent from my mobile device
Click to expand...
Click to collapse
fastboot boot didn't work on the m7. It works on the m8 I have tested it and I used an unreleased recovery to boot the recovery to pull the stock recovery from the GPE. You can boot the recoveries on sense based roms but for the GPE edition one the ones for Sense aren't booting. the dt.img's are different between the two devices.

graffixnyc said:
fastboot boot didn't work on the m7. It works on the m8 I have tested it and I used an unreleased recovery to boot the recovery to pull the stock recovery from the GPE. You can boot the recoveries on sense based roms but for the GPE edition one the ones for Sense aren't booting. the dt.img's are different between the two devices.
Click to expand...
Click to collapse
Since booting rather than flashing is my preferred workflow, do you know if the "unreleased recovery" you used is planned to be released? I've already flashed Philz and flashed back, but for future use it would be convenient.
Thanks,
Stephen

Just had the same problem like yours but the latest CWM 6.0.4.8 works for me.
I got touch CWM from here
The superuser.zip file from here
Both are made by clockworkmod
Commands
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-touch-6.0.4.8-m8.img
Once I got in the temporary CWM recovery, I backed up the entire system to sdcard. I pulled out the stock recovery image file (24MB in size) in case I need it for OTA in the future.
Then flash the superuser.zip and reboot back to the vanilla android. Stock recovery and everything else was untouched and we got rooted.

erythrophilia said:
Just had the same problem like yours but the latest CWM 6.0.4.8 works for me.
Click to expand...
Click to collapse
After the 4.4.4 OTA update, I was also able to boot (not flash) Philz recovery to reroot my phone.
Long version in case it's helpful to someone else in the future: I think either my phone shipped with corrupt firmware or I somehow corrupted it while unlocking the bootloader originally, and then I made matters worse by flashing back to a "stock" firmware that didn't exactly match the shipped M8 GPE recovery. Turned out that with that bad "stock" firmware the 4.4.3 OTA failed to apply, so to make the 4.4.3 OTA work I had to flash the 1.16.1700.16 firmware from this thread. After the 4.4.3 update ./fastboot boot <custom-recovery> still didn't work, so I did the flash custom/root/flash stock cycle. Then a week later the 4.4.4 update rolled through without incident, and suddenly ./fastboot boot <custom-recovery> worked fine.
Thanks,
Stephen