Develop Bugs

[TUT] Re-flash stock ROM (RUU) after bricking a rooted device (for noobs)

Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU (ROM Update Utility) for your device from androidfiles.org. Make sure you download a Primo_C RUU for a CDMA device (no sim card) or a Primo_U RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!

Hi
Thanks for that perfect decsription exactly when I needed it
I just had a weired effect with my new windows 7 laptop that I want to share.
I installed the USB drivers and "fastboot devices" showed my HTC fine
but even flashing the stock recovery image was not working.
So it was stucking in the "Sending" part and never continued.
I then moved to my old laptop with Vista did exactly the same things
and there it worked without problems.
I disabled virus scanner, checked for htsync and used the original USB cable
without success.
But now I know why I normally never touch Windows and only
work on linux
Regards
max
---------- Post added at 11:19 PM ---------- Previous post was at 10:33 PM ----------
Hi
CafeKampuchia said:
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
I have done that now - compared to my first "try"
Regards
max

hi. thanks for the tips.
however when i do this, i get an error "FAILED <remote: signature verify fail>
Any suggestions?

ur RUU and CID is diff...

ryanlow134 said:
ur RUU and CID is diff...
Click to expand...
Click to collapse
and... how do i make them the same?

lcavada said:
and... how do i make them the same?
Click to expand...
Click to collapse
Use the correct RUU package for your device
regards
max

Another way of saying it is that you downloaded the wrong RUU for your device.

not working
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out

I use fastboot flasher for this.. this tool is good .

sush93 said:
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
Click to expand...
Click to collapse
"Waiting for Device" at fastboot usually related to bootloader driver. You need Android USB Driver
See : http://developer.android.com/sdk/win-usb.html

Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!

run the ruu in hboot..
Sent from my HTC One V

thevilish said:
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
Click to expand...
Click to collapse
Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
NOTE: There is no boot/reboot and enter pin in between.

paarthdesai said:
run the ruu in hboot..
Sent from my HTC One V
Click to expand...
Click to collapse
I've done this before and didn't succeeded, but now it works! Magic
Thanks a lot!

help
CafeKampuchia said:
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
PLEASE HELP!
The 5th point does not work for me. I can not run the code.
What can i do?

what do you mean by navigate to the folder where you installed sdk?

brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
It means that if you installed SDK in c:/android, then u must type.in the command prompt: cd c:/android and hit enter
Cheers
Sent from my HTC One V using xda app-developers app

brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
where the fastboot.exe is located and stock recovery must be in the same folder for the command to work

[ask] Error 155
hey guys, ive been reading all tutorial for reverting to stock RUU.
the first time i tried, it works prefectly.
then after a few weeks, i tried to revert to stock RUU, it failed .
it show error 155.
i already flash the boot , recovery that i found inside the stock RUU, also I've relock the phone.
but when i relock the phone, it show "info Lock successfully , status read failed no such file / directory"
when i enter bootloader, it show that my device already "relocked"
does the relocked proses is successfully ?
iam running PrimoU 2.09.707.1 with stock bootloader, CWM recovery, and rooted ..

I did exactly as it is mentioned but at the end where there is vertical progress bar it gives me an error of customer Id... Failed to update. What shud i do. How do I check what my customer Id is I can't Download it from play store coz can't boot into normal screen... How do I make ruu and cid same.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Cannot update, root or flash recovery

After trawling the internet for about 4 hours, downloading various things and reading many guides, I decided to give up and create this thread.
I have a HTC Wildfire S with the following in bootloader
MARVEL PVT SHIP S-OFF RL
HBOOT-0.90.0000
MICROP-0451
RADIO-7.54.39.08M
Apr 8 2011,17:45:10
Android version: 2.3.5
HTC Sense version: 2.1
Software number: 2.14.771.4
1. OTA always seemed to fail with an icon of a phone with a red triangle (I assume that means missing recovery).
2. RUU always seemed to turn up with Error 191.
3. Created a goldcard, and tried RUU again, still Error 191.
4. Placed rom_01.zip in root of SD card and renamed to PG76IMG, booted into HBOOT where nothing happened.
5. Repeated with rom_02, and same result.
6. Attempted flashing recovery, and then a full RUU zip through fastboot, which neither worked. The errors I received were "FAILED (remote: not allowed)" & "FAILED (remote: 42 custom id check fail)" respectively.
7. Extracted the boot.img & system.img, and attempted to flash via fastboot, and received the "FAILED (remote: not allowed)" error.
8. Downloaded an AIO toolkit, and attempted flashing recovery, and the zip file and received the same errors. Also attempted perm root from there, which still had no results.
9. Somehow factory reset it, and repeated all of the above, still with no results.
I would appreciate any help,
Thank you.

MyCanSeeYou said:
After trawling the internet for about 4 hours, downloading various things and reading many guides, I decided to give up and create this thread.
I have a HTC Wildfire S with the following in bootloader
MARVEL PVT SHIP S-OFF RL
HBOOT-0.90.0000
MICROP-0451
RADIO-7.54.39.08M
Apr 8 2011,17:45:10
Android version: 2.3.5
HTC Sense version: 2.1
Software number: 2.14.771.4
1. OTA always seemed to fail with an icon of a phone with a red triangle (I assume that means missing recovery).
2. RUU always seemed to turn up with Error 191.
3. Created a goldcard, and tried RUU again, still Error 191.
4. Placed rom_01.zip in root of SD card and renamed to PG76IMG, booted into HBOOT where nothing happened.
5. Repeated with rom_02, and same result.
6. Attempted flashing recovery, and then a full RUU zip through fastboot, which neither worked. The errors I received were "FAILED (remote: not allowed)" & "FAILED (remote: 42 custom id check fail)" respectively.
7. Extracted the boot.img & system.img, and attempted to flash via fastboot, and received the "FAILED (remote: not allowed)" error.
8. Downloaded an AIO toolkit, and attempted flashing recovery, and the zip file and received the same errors. Also attempted perm root from there, which still had no results.
9. Somehow factory reset it, and repeated all of the above, still with no results.
I would appreciate any help,
Thank you.
Click to expand...
Click to collapse
Have you unlocked the bootloader?

aWFSuser said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
Using HTCDev? As updating the HBOOT seems to fail. I have to skip the first couple of steps. When trying to get the oem token, it still doesn't work.
Sent from my XT1032 using XDA Premium 4 mobile app

MyCanSeeYou said:
Using HTCDev? As updating the HBOOT seems to fail. I have to skip the first couple of steps. When trying to get the oem token, it still doesn't work.
Click to expand...
Click to collapse
First of all you need to unlock your bootloader. If htc official site is not working for you, then you try below methods.
Try THIS or This one
Good luck!

testmasterbd said:
First of all you need to unlock your bootloader. If htc official site is not working for you, then you try below methods.
Try THIS or This one
Good luck!
Click to expand...
Click to collapse
Hey thanks, for your suggestions, neither were successful.
They both receive an error when collecting the token.

MyCanSeeYou said:
neither were successful.
They both receive an error when collecting the token.
Click to expand...
Click to collapse
Then, I think you need to check your USB "cable/pc-port" and htc driver on your PC. If possible then try with fresh PC/install.

testmasterbd said:
Then, I think you need to check your USB "cable/pc-port" and htc driver on your PC. If possible then try with fresh PC/install.
Click to expand...
Click to collapse
Sorry for the late reply, only managed to try it yesterday.
No luck again :/. Used a few different laptops and cables.

MyCanSeeYou said:
Sorry for the late reply, only managed to try it yesterday.
No luck again :/. Used a few different laptops and cables.
Click to expand...
Click to collapse
Try the following commands, with your device in fastboot mode and your rom1.zip and rom2.zip in you adb folder. Also ensure that your command prompt is ran from that folder by using shift+ right click then open command window here.
[Code/] fastboot oem rebootRUU
Fastboot flash zip rom1.zip
Code:
The command window might now ask to flush or reflush the command. So
[Code/] fastboot flash zip rom1.zip
[Code]
Wait for this to complete then run
[Code/] fastboot flash zip rom2.zip
(Same reflush stuff may come again, if so reissue command again)
Fastboot flash zip rom2.zip
Fastboot reboot
[Code]
All should now be well.
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
All should now be well.
Click to expand...
Click to collapse
Thanks you SO much! It updated my hboot, but when I tried the HTCDev method, it failed upon flashing the unlock_code.bin. Instead I used the HTC unlocker tool thing, it worked like a charm! Installed a custom recovery via fastboot and now trying out all the ROMs!
Sent from my XT1032 using XDA Premium 4 mobile app

MyCanSeeYou said:
Thanks you SO much! It updated my hboot, but when I tried the HTCDev method, it failed upon flashing the unlock_code.bin. Instead I used the HTC unlocker tool thing, it worked like a charm! Installed a custom recovery via fastboot and now trying out all the ROMs!
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No problem pal
Sent from my HTC Desire S using Tapatalk

[Q] Wildfire stuck on HTC logo after restoring stock rom

Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53

petnas said:
Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53
Click to expand...
Click to collapse
Can you link to the ROM your trying to install?
Sent from my HTC Desire S using Tapatalk

petnas said:
Hi guys,
I'm going crazy with this Wildfire. I had Cyanogenmod on this unlocked device. I tried to restore a stock Marvel ROM. After that I could not start the phone anymore, it's just stuck at white screen with HTC logo. I booted in boot mode and could not get to recovery. I managed to install via fastboot USB a clockwork recovery, from there I could install some ROMs I found (including Marvel and Cyano) but after rebooting my phone just reached the HTC logo and stays stuck there. I can't RUU because for some reason the process fails during upgrade.
Any idea?
BUZZ PVT SHIP S-OFF
HBOOT-6.01.0002
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.15.31
Nov 17 2010, 12:08:53
Click to expand...
Click to collapse
DON'T RESTORE A STOCK MARVEL ROM!!! Our device is "buzz", "marvel" is Wildfire S.

Same for me
KoolKid98189 said:
DON'T RESTORE A STOCK MARVEL ROM!!! Our device is "buzz", "marvel" is Wildfire S.
Click to expand...
Click to collapse
I'm stuck on it aswell but I can go into Recovery.
However when I try and install the stock rom:
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.zip
I get the error message:
Amend scripting (update script) is no longer supported. Amend scripting was deprecated by Google in android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 gingerbread based recovery . Please switch to edify scripting ( update - script and update binary) to create working update zip packages. Installation aborted.
and when I try the safe flash zip:
Buzz_Froyo_hTC_WWE_2.22.405.1_SAFE_FLASH_ZIP
it always says its bad.
Also when I download the .exe instead of zip and it runs through the program it finds the phone but says it has less than 30% battery even though I have been charging my phone from the socket for 2 days.
Any ideas on what to do?
Thanks, Aadil

Answer
aadil10 said:
I'm stuck on it aswell but I can go into Recovery.
However when I try and install the stock rom:
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.zip
I get the error message:
Amend scripting (update script) is no longer supported. Amend scripting was deprecated by Google in android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 gingerbread based recovery . Please switch to edify scripting ( update - script and update binary) to create working update zip packages. Installation aborted.
and when I try the safe flash zip:
Buzz_Froyo_hTC_WWE_2.22.405.1_SAFE_FLASH_ZIP
it always says its bad.
Also when I download the .exe instead of zip and it runs through the program it finds the phone but says it has less than 30% battery even though I have been charging my phone from the socket for 2 days.
Any ideas on what to do?
Thanks, Aadil
Click to expand...
Click to collapse
try this file
shipped-roms(dot)com/download.php? category=android&model=Buzz&file=RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
use . instead of (dot)
follow these instructions if it doesn't work
forum(dot)xda-developers(dot)com/showthread.php?t=1132028
use . instead of (dot)
hope that helps

digijedi007 said:
try this file
shipped-roms(dot)com/download.php? category=android&model=Buzz&file=RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
use . instead of (dot)
follow these instructions if it doesn't work
forum(dot)xda-developers(dot)com/showthread.php?t=1132028
use . instead of (dot)
hope that helps
Click to expand...
Click to collapse
No, didn't work.
And the guide is for downgrading hboot which I've done.
I have clockwork Recovery mod v4.0.1.4 and I think I need 5
but whenever I try to flash a zip I get the error:
Finding update package...
Opening update package...
Installing update...
Instalation aborted.

aadil10 said:
No, didn't work.
And the guide is for downgrading hboot which I've done.
I have clockwork Recovery mod v4.0.1.4 and I think I need 5
but whenever I try to flash a zip I get the error:
Finding update package...
Opening update package...
Installing update...
Instalation aborted.
Click to expand...
Click to collapse
So do you want to go back to official (albeit old sense software?)
---------- Post added at 09:43 PM ---------- Previous post was at 09:34 PM ----------
If you don't i'd recommend this rom it does run quite a bit faster than sense http://download.cyanogenmod.org/get/jenkins/2808/cm-7.2.0-buzz.zip
it's what i use on my buzz

digijedi007 said:
So do you want to go back to official (albeit old sense software?)
---------- Post added at 09:43 PM ---------- Previous post was at 09:34 PM ----------
If you don't i'd recommend this rom it does run quite a bit faster than sense http://download.cyanogenmod.org/get/jenkins/2808/cm-7.2.0-buzz.zip
it's what i use on my buzz
Click to expand...
Click to collapse
thats the problem, I get that error message whenever I try to flash a zip

before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader

digijedi007 said:
before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
yeah I formatted it all
And how can I find adb/fastboot on the recovery zip? when I click it it just shows:
android-info.txt
recovery.img
and where is my adb dir?

aadil10 said:
yeah I formatted it all
And how can I find adb/fastboot on the recovery zip? when I click it it just shows:
android-info.txt
recovery.img
and where is my adb dir?
Click to expand...
Click to collapse
you will need these http://adbdriver.com/upload/AdbDriverInstaller.exe (adb drivers) also make sure to uninstall any htc desktop software you have installed, you will need to install this http://forum.xda-developers.com/showthread.php?t=2317790 (adb+fastboot tools) and afterwards put that downloaded recovery zip into that folder it would be C:\Program Files (x86)\Minimal ADB and Fastboot if you have a x64bit operating system otherwise it would be at C:\Program Files\Minimal ADB and Fastboot\
then you would need to use your fastboot mode > when you hold your vol buttons+pwr button during startup select fastboot there and then from your pc using the commands i speciefied you would overwrite the recovery with a newer one so to do that the easiest would be to use the shortcut on your desktop that the minimal adb installer creates ,
so open minimal adb shortcut on your desktop
then excecute these commands
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader

digijedi007 said:
before you try flashing anything did you format everything but ext_sd card?
recovery 5 http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-buzz.zip
also try seeing if there is a adb/fastboot option somewhere in your recovery when you find it open it
then from your pc / run from your adb/fastboot dir
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
Clockworkmod 5 worked when I flash it but when I restart my phone it goes back to version 4

You have to flash recoveries with pc's , just flashing it with your existing recovery won't help at all, so you need to use the software i provided links for and use that adb commands to overwrite your existing recovery so do>take out the battery from the phone and unplug it>then>put battery back >
then run the adb shortcut on your desktop>
then just hold pwr+vol btns simultaneously>then
at the very top - select "Fastboot",and connect your phone with the USB Cable to your PC.Then it should say "Fastboot USB" on your phone's screen.>
Type:
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
afterwards reboot your phone and then try flashing another zip and see if it works

digijedi007 said:
You have to flash recoveries with pc's , just flashing it with your existing recovery won't help at all, so you need to use the software i provided links for and use that adb commands to overwrite your existing recovery so do>take out the battery from the phone and unplug it>then>put battery back >
then run the adb shortcut on your desktop>
then just hold pwr+vol btns simultaneously>then
at the very top - select "Fastboot",and connect your phone with the USB Cable to your PC.Then it should say "Fastboot USB" on your phone's screen.>
Type:
fastboot flash zip recovery-clockwork-5.0.2.0-buzz.zip
afterwards reboot your phone and then try flashing another zip and see if it works
Click to expand...
Click to collapse
Nevermind, somehow when I booted my phone it went onto cyanogenmod 7 so its working!

Ok, was it the 7.2 one

digijedi007 said:
Ok, was it the 7.2 one
Click to expand...
Click to collapse
yeah, back to how it was after I flashed cyanogen mod

In Over My Head

Hey Devs,
I am running a HTC One M8 H/K from Sprint. I rooted it the week I got it and could not have been happier. A few days ago my 4G stopped working and I tried to install an OTA update but it wouldn't take. I tried to unroot and relock the bootloader but I think I have done some steps out of order. I do not have a recovery anymore although I still think I am rooted. I tried doing some RUU's but none of the .exe's will even start. I tried flashing firmware with a zip as well with the Hansoon's toolkit but I keep getting an error 12.
My fastboot info reads
*** Software status ***
*** Relocked ***
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.08.20.0916
OpenDSP-v54.2.2-00564-M8974_HM.0811f
OS-3.31.654.2
eMMC-boot 2048
I had CWM PhilzTouch installed as a recovery but I when I select recovery on HBOOT I just get returned to the HBOOT screen. Any help would be greatly appreciated. I'm at wit's end here and know when it's time to ask for help. Thanks in advance.

dommiboy said:
I tried doing some RUU's but none of the .exe's will even start.
Click to expand...
Click to collapse
Do you have HTC Sync, or at least HTC drivers installed? This is required for the RUU to work.
What version of Windows?
dommiboy said:
I tried flashing firmware with a zip as well with the Hansoon's toolkit but I keep getting an error 12.
Click to expand...
Click to collapse
If its not a signed firmware package, it won't flash with s-on.

Do you NEED HTC Sync installed to run an RUU? I've never had it installed on my Windows 7 PC here at work and RUUs work fine but at home on my Windows 8.1 laptop they won't run past the T&Cs

EddyOS said:
Do you NEED HTC Sync installed to run an RUU? I've never had it installed on my Windows 7 PC here at work and RUUs work fine but at home on my Windows 8.1 laptop they won't run past the T&Cs
Click to expand...
Click to collapse
Definitely don't need HTC Sync to RUU (although not sure if you need HTC drivers, or if "generic" fastboot drivers will do). HTC Sync sometimes causes more problems than it solves. But I just mention HTC Sync, as its what most people have installed on their PC after connecting the phone and letting it do its thing automatically. And easy for folks to just Google for HTC Sync rather then finding a link for HTC drivers alone.

I have the HTC drivers on the computer. I'm able to adb commands and I originally rooted using this computer. The computer is running 8.1. When I try running RUU it never gets past the install wizard.

The firmware packages read signed in the filename. I have tried so many I can't even give you the links but I would say 90% came off this forum. I tried all of the base stock non-rooted complete firmware packs I could find.

dommiboy said:
I have the HTC drivers on the computer. I'm able to adb commands and I originally rooted using this computer. The computer is running 8.1. When I try running RUU it never gets past the install wizard.
Click to expand...
Click to collapse
If I knew that I'd tell you! When you get to the T&Cs, open a Run box and type in %temp% and in there, in one of the new folders, will be a zip file called rom. Copy this to your Desktop and flash this in RUU mode (fastboot oem rebootRUU) using htc_fastboot.exe (which I have here - htc_fastboot flash zip rom.zip) and it should work

dommiboy said:
The computer is running 8.1. When I try running RUU it never gets past the install wizard.
Click to expand...
Click to collapse
That may be your problem. RUUs don't play well with Win8.1. Try a Win7 or even an XP machine.
---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------
dommiboy said:
A few days ago my 4G stopped working and I tried to install an OTA update but it wouldn't take. I tried to unroot and relock the bootloader but I think I have done some steps out of order. I do not have a recovery anymore although I still think I am rooted.
Click to expand...
Click to collapse
What happened when you tried to OTA?
You don't need to relock the bootloader to OTA, nor do you need to unroot. But all system files must be stock (nothing modified by root).
For a vast majority of instances (pretty much everything except trying to run RUU), I don't recommend to relock the bootloader. Its not required for OTA as mentioned, and it puts you in a worse position than UNLOCKED.
Did you try to fastboot flash the stock recovery and install the OTA again (believe you need to unlock bootloader again to do so)? You don't need a firmware zip to do that. Just find the stock recovery for your CID here: http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
dommiboy said:
The firmware packages read signed in the filename. I have tried so many I can't even give you the links but I would say 90% came off this forum. I tried all of the base stock non-rooted complete firmware packs I could find.
Click to expand...
Click to collapse
Are you running firmware for your CID (its required with s-on)? If not, that is why you have error 12 signature fail with a signed file.

Hey Guys. I've been trying a few more things today. I first tried running opening the temp folder with the RUU install shield running but that's all the farther it gets. I never see a rom zip because it never makes it to the T&C's. Next I tried flashing these firmwares with Hansoon's toolkit.
4.20.6.51.10/URL]
[URL="http://forum.xda-developers.com/showthread.php?t=2729173"]3.30.654.2 Full Firmware From OTA/URL]
Both of those failed with a signature failure.
I will try flashing a recovery but I have no idea which one I should try to flash nor how to flash it.
In a final act of desperation for the night I tried to S-off with firewater which I pulled from web archive. I was able to push the file to the device, I had root permissions, I THINK I was able to chmod the file, however when I tried to run the file it just said not found. When I cd into the directory it's nowhere to be found?? I have no idea what happened there. I need to take a break for the evening to keep from physically bricking it into a wall. BTW, my reasoning for trying to S-Off was to use writecid and completely circumvent the signature errors. Maybe it was an okay idea, maybe it wasn't, but it didn't work so that's all that counts
I will try the official HTC RUU exe tomorrow when I have access to a win7 box but after that I really am out of ideas. I do seriously appreciate the help thus far and will greatly appreciate any more! Thank you!

1. Get rid of that Hansoon's toolkit, don't use it
2. Get the correct files from : http://forum.xda-developers.com/showthread.php?t=2729173
a- Sprint_HTC_One_M8_HK_4.20.654.10_RUU (exe)
or
b- 0P6BIMG_Sprint_HTC_One_M8_Harman_4.20.654.10_RUU.zip (zip)
3. Get the htc_fastboot.exe from @EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have three options here (all of this need a relocked bootloader, which you already have)
(Note : not sure whether this still valid on newer RUU, use USB 2.0 on your PC regardless Win 7, Win 8.1 or Win 10)
Option 1: Run the RUU.exe
a- relock bootloader
b- boot to bootloader/fastboot usb mode
c- Right click the RUU.exe and select run as Administrator
Option 2: Use the RUU.zip
a- rename the long RUU.zip name to RUU.zip (easier for you to follow commands)
b- relock bootloader
c- use the htc-fastboot.exe instead of the regular fastboot.exe
b- boot to bootloader/fastboot usb mode
c- run below commands
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
Option 3 : Try the above 2 options first, keep this option 3 later

dommiboy said:
In a final act of desperation for the night I tried to S-off with firewater which I pulled from web archive. I was able to push the file to the device, I had root permissions, I THINK I was able to chmod the file, however when I tried to run the file it just said not found. When I cd into the directory it's nowhere to be found?? I have no idea what happened there.
Click to expand...
Click to collapse
firewater was discontinued in December. Its an online service, and won't work now that the dev has stopped supporting it.
---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------
ckpv5 said:
(Note : not sure whether this still valid on newer RUU, use USB 2.0 on your PC regardless Win 7, Win 8.1 or Win 10)
Click to expand...
Click to collapse
AFAIK, USB 3.0 still indeed plays havoc with RUUs and fastboot. But I don't think it would cause the RUU program to stop at terms and conditions, it would probably get stuck at trying to communicate with the device.
Suspect its a Win8 issue.

redpoint73 said:
Suspect its a Win8 issue.
Click to expand...
Click to collapse
I have no problem running RUU with my Win 8.1 64-bit, the only thing is my USB ports are all 2.0
and some Win 8.1 can't detect device when in fastboot mode but that easily can be fixed with a reg file (no need all those 3rd party drivers)

I have issues running RUUs, but both mine are USB 3.0 - but the issue I have is it not even running past the T&Cs. It extracts the files and then does nothing. Windows 7 Pro 64-bit at work works fine
Fastboot works fine (never had an issue with Windows 8.1 Pro), though, and I can flash RUU ZIPs without issue

ckpv5 said:
I have no problem running RUU with my Win 8.1 64-bit, the only thing is my USB ports are all 2.0
and some Win 8.1 can't detect device when in fastboot mode but that easily can be fixed with a reg file (no need all those 3rd party drivers)
Click to expand...
Click to collapse
The issue I've seen with Win8.1 is some C++ files not updated, so it might be build specific. A few users manually updated the appropriate files to get RUUs working.
Agree that checking the USB type (2.0 versus 3.0) is a good call. But I think that would not cause the RUU exe to crash at Terms & Conditions; but rather just get stuck trying to connect to the phone.
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
EddyOS said:
I have issues running RUUs, but both mine are USB 3.0 - but the issue I have is it not even running past the T&Cs. It extracts the files and then does nothing. Windows 7 Pro 64-bit at work works fine
Click to expand...
Click to collapse
Right, that is the issue I've seen with USB 3.0.
Of course, it makes sense for the OP to look at (troubleshoot) every possibility (including USB type). Just trying another computer is probably the easiest fix, as long as they have access.

I'll say I was using USB 3.0 at work on the Win 7 machine, so I think it's just some PCs don't like the RUUs - proper annoying!

Randomly, thought I'd try again but run the RUU in Compatibility Mode as Windows 7 (as Administrator) and it worked fine

HTC One M8 Verizon has no OS & no Recovery...

All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks

AndroidJason said:
All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks
Click to expand...
Click to collapse
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.

crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
Thanks, I will give this a try. Since it will take me back to stock, will I have to root again before installing TWRP & custom ROM?

crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?

AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?

AndroidJason said:
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?
Click to expand...
Click to collapse
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
Click to expand...
Click to collapse
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!

crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!
Click to expand...
Click to collapse
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?

AndroidJason said:
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?
Click to expand...
Click to collapse
Yes, my bad, got option 1 & 2 mixed from memory

crackerjack1957 said:
Yes, my bad, got option 1 & 2 mixed from memory
Click to expand...
Click to collapse
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.

AndroidJason said:
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.
Click to expand...
Click to collapse
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.

crackerjack1957 said:
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.
Click to expand...
Click to collapse
Still up, wanted to give you time to respond.
I can't get the RUU update to run from pc, so it looks like this could be a dead end for me. Thank you again for trying.
I hate to get a new phone, none of the new Verizon phones can be rooted or an unlocked bootloader.
Can't get the new Nexus phones as we purchase directly through Verizon & not Google. (this is my company phone & HAS to be purchased through Verizon)
I'll retrace some steps in the morning.

AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner

crackerjack1957 said:
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner
Click to expand...
Click to collapse
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.

AndroidJason said:
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.
Click to expand...
Click to collapse
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.

AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.

AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Still not working.
Followed all the instructions, re-downloaded the RUU. I've uninstalled the HTC sync & drivers; ran cc cleaner, rebooted, reinstalled HTC snyc & drivers.
I've even tried this on two different Windows 7 pc's. One I left the HTC Sync on, the other I uninstalled & just left the HTC drivers behind. (as one person suggested)
Should the RUU installer app say updated to version & then it instead of a version it list odd characters that I dont even know how to type on a keyboard?
I think I've got my first true brick.

crackerjack1957 said:
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.
Click to expand...
Click to collapse
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.

AndroidJason said:
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.
Click to expand...
Click to collapse
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.

AndroidJason said:
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.
Click to expand...
Click to collapse
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader

crackerjack1957 said:
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
I get the following when I attempt to flash using this method...
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826414592 bytes
sending 'zip' (1683272 KB)...
OKAY [ 63.976s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 63.991s
My phone also doesnt do what is described by staying at an HTC splash screen; it just boots right to the bootloader like it always does.
I've seen that remote: not allowed trying some of my own method during this whole process; not sure what that means.