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

stuck on BOOT LOOP & cant get into recovery!

Hello guys.... so I flashed a rom about 6 months ago, and yesterday my phone died and when I put it on the charger it was stuck on boot loop. I tried to go into recovery but when I do it also goes into boot loop. I've also tried the ADB command, but it says "Adb is not recoznices as an internal or external commad operable program of bactch file" so i'm out of ideas right now..i can't really flash another rom if I can't get into recovery can anybody help me? thanks in advance...

jy_ventura said:
Hello guys.... so I flashed a rom about 6 months ago, and yesterday my phone died and when I put it on the charger it was stuck on boot loop. I tried to go into recovery but when I do it also goes into boot loop. I've also tried the ADB command, but it says "Adb is not recoznices as an internal or external commad operable program of bactch file" so i'm out of ideas right now..i can't really flash another rom if I can't get into recovery can anybody help me? thanks in advance...
Click to expand...
Click to collapse
In fastboot, you can only use fastboot commands. Choose fastboot from the HBOOT menu, and when connected to your computer, it should say "FASTBOOT USB." Then, you should be able to do a "fastboot devices," and your device should show up. Please provide the output of "fastboot getvar all" and we can better judge how to proceed.

Captain_Throwback said:
In fastboot, you can only use fastboot commands. Choose fastboot from the HBOOT menu, and when connected to your computer, it should say "FASTBOOT USB." Then, you should be able to do a "fastboot devices," and your device should show up. Please provide the output of "fastboot getvar all" and we can better judge how to proceed.
Click to expand...
Click to collapse
It says
***unlocked***
Supersonic evt3 ship s on
Hboot- 2.18.0001
Microp-041f
Touch panel-atmel224_16ab
Radio-2.15.00.12.19

jy_ventura said:
It says
***unlocked***
Supersonic evt3 ship s on
Hboot- 2.18.0001
Microp-041f
Touch panel-atmel224_16ab
Radio-2.15.00.12.19
Click to expand...
Click to collapse
That's not what I asked for, but it might be enough. You'll need to relock the device (fastboot oem lock) and then flash the 5.07.651.1 firmware.zip via RUU mode.
Here's the file you need to download, and place the file in the same folder on your computer from which you're running fastboot.
So, after relocking, at the command prompt reboot to RUU mode.
Code:
fastboot oem rebootRUU
Then flash the firmware zip.
Code:
fastboot flash zip firmware.zip
Once complete, the command prompt will come back, and you can reboot back to the bootloader.
Code:
fastboot reboot-bootloader
At this point, you will have the stock recovery, and hopefully it'll boot into it. So, when you get back to HBOOT, choose the "RECOVERY" option. If all is well, you'll get the red triangle with exclamation point, which is the stock recovery. Press both volume buttons and the power button at the same time to bring up the menu, and choose the option to reboot the device now. Hold the volume down button immediately after choosing to reboot so you can get back into HBOOT.
From there, you just have to unlock again, and then you should be able to flash a custom recovery.
Make sure you are running these commands from the folder with fastboot.exe in it. Otherwise they will give you the error you mentioned in your OP.

This may sound dumb but im having a problem relocking the device. My computer is not registing my phone.
Captain_Throwback said:
That's not what I asked for, but it might be enough. You'll need to relock the device (fastboot oem lock) and then flash the 5.07.651.1 firmware.zip via RUU mode.
Here's the file you need to download, and place the file in the same folder on your computer from which you're running fastboot.
So, after relocking, at the command prompt reboot to RUU mode.
Code:
fastboot oem rebootRUU
Then flash the firmware zip.
Code:
fastboot flash zip firmware.zip
Once complete, the command prompt will come back, and you can reboot back to the bootloader.
Code:
fastboot reboot-bootloader
At this point, you will have the stock recovery, and hopefully it'll boot into it. So, when you get back to HBOOT, choose the "RECOVERY" option. If all is well, you'll get the red triangle with exclamation point, which is the stock recovery. Press both volume buttons and the power button at the same time to bring up the menu, and choose the option to reboot the device now. Hold the volume down button immediately after choosing to reboot so you can get back into HBOOT.
From there, you just have to unlock again, and then you should be able to flash a custom recovery.
Make sure you are running these commands from the folder with fastboot.exe in it. Otherwise they will give you the error you mentioned in your OP.
Click to expand...
Click to collapse

jy_ventura said:
This may sound dumb but im having a problem relocking the device. My computer is not registing my phone.
Click to expand...
Click to collapse
Do you have the correct drivers installed (or any drivers)?
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
These drivers should work: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

i have all drivers and i reinstalled just in case but i only get as far as it saying hboot usb plug on my phone but it doesnt pop up and open in my computer
Captain_Throwback said:
Do you have the correct drivers installed (or any drivers)?
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
These drivers should work: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse

jy_ventura said:
i have all drivers and i reinstalled just in case but i only get as far as it saying hboot usb plug on my phone but it doesnt pop up and open in my computer
Click to expand...
Click to collapse
For the purposes of this exercise, you need to select "FASTBOOT". Once you select that, it should change from FASTBOOT to FASTBOOT USB if the drivers are installed correctly.
Nothing is supposed to open on your computer - I'm not sure what you mean by that. You have to open a command prompt, and navigate to the location of fastboot.exe on your computer, which you're presumably downloaded previously.

Im not sure what I meant either sorry its been a long day. So, okay I have the correct drivers because it does say FASTBOOT USB but when I try in that command i get an error message stating it's not recognize internal or external.
Captain_Throwback said:
For the purposes of this exercise, you need to select "FASTBOOT". Once you select that, it should change from FASTBOOT to FASTBOOT USB if the drivers are installed correctly.
Nothing is supposed to open on your computer - I'm not sure what you mean by that. You have to open a command prompt, and navigate to the location of fastboot.exe on your computer, which you're presumably downloaded previously.
Click to expand...
Click to collapse

jy_ventura said:
Im not sure what I meant either sorry its been a long day. So, okay I have the correct drivers because it does say FASTBOOT USB but when I try in that command i get an error message stating it's not recognize internal or external.
Click to expand...
Click to collapse
Again, you have to run the command from the folder with fastboot.exe in it. Are you doing that? Please provide a screenshot of the folder contents and the command prompt.

I dont think I am because this is literally what i have the phone plugged into my pc and then I have command prompt running.... so when you say i have to run the command from the folder...i guess i'm lost as in what folder since my phone is on the screen that says fastboot usb... sorry! noob completely!
Captain_Throwback said:
Again, you have to run the command from the folder with fastboot.exe in it. Are you doing that? Please provide a screenshot of the folder contents and the command prompt.
Click to expand...
Click to collapse

jy_ventura said:
I dont think I am because this is literally what i have the phone plugged into my pc and then I have command prompt running.... so when you say i have to run the command from the folder...i guess i'm lost as in what folder since my phone is on the screen that says fastboot usb... sorry! noob completely!
Click to expand...
Click to collapse
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.

no i havent....but i have it now... its done downloading now
Captain_Throwback said:
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.
Click to expand...
Click to collapse

So I downloaded it but I keep getting an error message that it cannot start due to adbwinapi.dll is missing. Ive reinstalled it a few times....im lost completely
Captain_Throwback said:
Have you downloaded fastboot to your computer?
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
You can download fastboot from here: https://www.htcdev.com/process/legal_fastboot_win
Wherever you save that is the folder you need to open the command prompt from, and where you need to put the firmware zip file.
Click to expand...
Click to collapse

jy_ventura said:
So I downloaded it but I keep getting an error message that it cannot start due to adbwinapi.dll is missing. Ive reinstalled it a few times....im lost completely
Click to expand...
Click to collapse
You shouldn't be running anything related to adb. Just follow my instructions. Everything I said is for fastboot, not adb.

I really dont know what im doing wrong I downloaded the fastboot and then the filmware i put them both in one same folder and then when command prompt came up i got an error...idk what im doing wrong!
Captain_Throwback said:
You shouldn't be running anything related to adb. Just follow my instructions. Everything I said is for fastboot, not adb.
Click to expand...
Click to collapse

jy_ventura said:
I really dont know what im doing wrong I downloaded the fastboot and then the filmware i put them both in one same folder and then when command prompt came up i got an error...idk what im doing wrong!
Click to expand...
Click to collapse
What do you mean when the command prompt came up? I asked for screenshots for this reason. Difficult to be able to determine the issue if you don't provide enough information.

Okay back to the start, I have both files in one folder....do I extract?
Captain_Throwback said:
What do you mean when the command prompt came up? I asked for screenshots for this reason. Difficult to be able to determine the issue if you don't provide enough information.
Click to expand...
Click to collapse

jy_ventura said:
Okay back to the start, I have both files in one folder....do I extract?
Click to expand...
Click to collapse
Extract the fastboot zip.

Okay I extracted files now im here...
Do I run fastboot?
Captain_Throwback said:
Extract the fastboot zip.
Click to expand...
Click to collapse

[Q] help stuck in boot loop after flashing Android Revolution HD 53

my bootloader show the following
***UNLOCKED***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OpenDSP-v31.120.274.0617
OS-1.10.605.8
eMMC-boot 2048MB
Aug 7 2013,16:38:58.0
after flashing the custom rom android revolution hd it said "flashed successfully please perform a full system reboot". when performed a reboot its stuck into a loop
into a panic situation right now cant use my phone please help guys
i am having recovery TWRP 2.7.0.0

Cant you just restore a backup or flash another rom? What is android revolution hd based on, jb, kk? Make sure your firmware matches the base of your rom. So if you flash a rom based on jb also flash jb firmware, if your on a kk rom, flash the kk firmware.
Also you say you have twrp 2.7.0.0? That is not a valid version for the verizon htc one.

cmlusco said:
Cant you just restore a backup or flash another rom? What is android revolution hd based on, jb, kk? Make sure your firmware matches the base of your rom. So if you flash a rom based on jb also flash jb firmware, if your on a kk rom, flash the kk firmware.
Also you say you have twrp 2.7.0.0? That is not a valid version for the verizon htc one.
Click to expand...
Click to collapse
sorry i just heard a lot about this ROM and made up my mind to use it permanently, but after flashing when i got the problem, I searched for it everywhere and found that it does not provide support for Verizon HTC one....feeling like a buge dumbbo right now as i didn't do a backup.
Can you please suggest me a good custom rom for verizon HTC One and/or also any way to return to the stock firmware?

what is the valid version of TWRP for Verizon HTC One?

Well there are tons of good roms in the develompent and original development threads. I my self prefer to just use rooted stock.
The latest twrp is 2.6.3.4 http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
If you wanted to you could do an ruu to get back to the stock firmware. http://vzw1files.dyndns.org/RUUs/

There is a 2.7.0.1. Also try ViperOne ROM.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

Thats cool, i didnt realize a new twrp had been released.

I don't remember if it's an official build, but it's faster and smoother.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

ruu gives error during flash
cmlusco said:
Well there are tons of good roms in the develompent and original development threads. I my self prefer to just use rooted stock.
The latest twrp is 2.6.3.4 http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
If you wanted to you could do an ruu to get back to the stock firmware. http://vzw1files.dyndns.org/RUUs/
Click to expand...
Click to collapse
i downloaded the 1.10.605.8/ version from the link you provided but this gives an error during flash

What was the error exactly?

cmlusco said:
What was the error exactly?
Click to expand...
Click to collapse
i used usb otg and copied the zip file to the sd card and then clicked on install and then selected the zip file and the swiped...the following comes written on the screen
Updatind partition details...
Full SELinux support is present.
E:Storage partition '//TWRP/BACKUPS/FA37KS92245
Installing '/sdcard/rom.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/rom.zip'
Updating partition details...
Failed

i also wiped the cache and dalvik and tried again but same error
my mid is PN0731000
and currently cid is SuperCID but tried to flash the zip file with both VZW__001 and SuperCID and got same error

You do not flash ruus in recovery. You flash them using fastboot and a cmd prompt on your pc.
fasboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot

I'm having this same problem, but the issue I'm having is the fact that I'm running on Windows 8.1 x64 and it's not recognizing my fastboot. I'm getting the error 10 code for the device and I've tried updating the drivers and yes I do have driver verification off. Please help

cmlusco said:
You do not flash ruus in recovery. You flash them using fastboot and a cmd prompt on your pc.
fasboot oem rebootRUU
fastboot reboot
fastboot flash zip nameoffile.zip
Click to expand...
Click to collapse
after issuing the first command the reboots and a htc logo with black background is shown now after waiting for around 10 seconds i issue the second command aand here the problem arises as device enters into boot loop and restarts again and again, should i skip the second command or there's a way around?

My bad, i put those in the wrong order. It should be
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Sorry about that.
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
thaunknownartist said:
I'm having this same problem, but the issue I'm having is the fact that I'm running on Windows 8.1 x64 and it's not recognizing my fastboot. I'm getting the error 10 code for the device and I've tried updating the drivers and yes I do have driver verification off. Please help
Click to expand...
Click to collapse
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip

cmlusco said:
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip
Click to expand...
Click to collapse
This is the code I just got. "This device cannot start. (Code 10)
A request for the USB BOS descriptor failed." and I updated both adb and the drivers.

cmlusco said:
My bad, i put those in the wrong order. It should be
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Sorry about that.
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
Try these drivers. They work for me on win 8.1 x86, but should also work for x64. http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
Also when was the last time you update the adb.exe and fastboot.exe files on your pc? http://vzw1files.dyndns.org/ADB/miniadb.zip
Click to expand...
Click to collapse
thanx by the way skipping the second code worked....

thaunknownartist said:
This is the code I just got. "This device cannot start. (Code 10)
A request for the USB BOS descriptor failed." and I updated both adb and the drivers.
Click to expand...
Click to collapse
Im not sure. If you google "adb fastboot win 8.1 x64" there are tons of threads and youtube vidoes on how to get it working. Also make sure your using usb2.0 ports not usb3.0 ports on your pc.

cmlusco said:
Im not sure. If you google "adb fastboot win 8.1 x64" there are tons of threads and youtube vidoes on how to get it working. Also make sure your using usb2.0 ports not usb3.0 ports on your pc.
Click to expand...
Click to collapse
I've been doing this since 8am EST lol this is why I came to my forum. And my USB 3.0 is broke so I couldn't use it if I wanted too, I'm also running AMD not Intel so most of the fixes I see are for Intel or require USB 3.0 :/

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

Stock HTC One M8 with Bootloop

Hi All,
Really struggling to find info for the bootloop issue on stock HTC one M8 loads for rooted etc
so my phone randomly restarted and then got stuck in a boot loop. i couldn't do anything i managed to get into Fastboot after waiting for the battery to die completely. got into Fastboot and factory reset. but no change.
The fix seems to be to flash RUU onto it but i cannot find any info on how to do it on a un-rooted HTC One M8.
Any suggestions/guidance?

also forgot to add if i choose Recovery from fastboot screen i just get a image of a HTC phone on the screen with a red triangle and ! inside.

borinous said:
also forgot to add if i choose Recovery from fastboot screen i just get a image of a HTC phone on the screen with a red triangle and ! inside.
Click to expand...
Click to collapse
My HTC One M8 is experiencing the identical problem. PLEASE HELP!

ive continued to do some digging and found a method for flashing RUU using just the micro SD card. dont have a card reader to hand at the mo so ill be trying this later. ill let you know how i get on.

borinous said:
The fix seems to be to flash RUU onto it but i cannot find any info on how to do it on a un-rooted HTC One M8.
Click to expand...
Click to collapse
RUU works fine on unrooted phones. Its an official HTC tool designed to be used on stock devices. You just connect the phone to a PC, boot into fastboot mode, and run the RUU executable on the PC, and the executable will do the rest.
This is provided you use the correct RUU for your specific device version (and not all versions have RUUs).
If you want more help on identifying the right RUU (if there is one) we'll need more info about your phone. In fastboot mode, open command prompt on computer, and do command fastboot getvar all, and post the results (delete IMEI and serial number).
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
borinous said:
also forgot to add if i choose Recovery from fastboot screen i just get a image of a HTC phone on the screen with a red triangle and ! inside.
Click to expand...
Click to collapse
That is the stock recovery. If you press vol up and power, it will show you the recovery menu. But there is not much you can do with it, that will help your current condition, aside from trying a factory reset.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
diezmerc8 said:
My HTC One M8 is experiencing the identical problem. PLEASE HELP!
Click to expand...
Click to collapse
Just saying you have the same problem, isn't going to do much for you; or allow anyone to help you much. Please provide specific information about your device version, as I requested from the OP.

redpoint73 said:
RUU works fine on unrooted phones. Its an official HTC tool designed to be used on stock devices. You just connect the phone to a PC, boot into fastboot mode, and run the RUU executable on the PC, and the executable will do the rest.
This is provided you use the correct RUU for your specific device version (and not all versions have RUUs).
If you want more help on identifying the right RUU (if there is one) we'll need more info about your phone. In fastboot mode, open command prompt on computer, and do command fastboot getvar all, and post the results (delete IMEI and serial number).
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
That is the stock recovery. If you press vol up and power, it will show you the recovery menu. But there is not much you can do with it, that will help your current condition, aside from trying a factory reset.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
Just saying you have the same problem, isn't going to do much for you; or allow anyone to help you much. Please provide specific information about your device version, as I requested from the OP.
Click to expand...
Click to collapse
Thanks ill give that a go when i get home. if no good ill proceed with a claim through my phone insurance and get a new one.
In the mean time i'm quite enjoying my Galaxy S3 running CM13. maybe if i get my HTC working i should do the same

redpoint73 said:
RUU works fine on unrooted phones. Its an official HTC tool designed to be used on stock devices. You just connect the phone to a PC, boot into fastboot mode, and run the RUU executable on the PC, and the executable will do the rest.
This is provided you use the correct RUU for your specific device version (and not all versions have RUUs).
If you want more help on identifying the right RUU (if there is one) we'll need more info about your phone. In fastboot mode, open command prompt on computer, and do command fastboot getvar all, and post the results (delete IMEI and serial number).
---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------
That is the stock recovery. If you press vol up and power, it will show you the recovery menu. But there is not much you can do with it, that will help your current condition, aside from trying a factory reset.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
Just saying you have the same problem, isn't going to do much for you; or allow anyone to help you much. Please provide specific information about your device version, as I requested from the OP.
Click to expand...
Click to collapse
Fair enough. To further elaborate on my experience.
I have the HTC One M8 Google Play Edition (Unlocked).
-Downloaded the RUU (version 6.12.1540.4) and HTC Sync Manager from HTC.
-Put device into FASTBOOT mode
-Connected device via USB with HTC Sync Manager open (Showed device was loaded with OS-5.07.1700.11)
-Ran the RUU. Phone displayed HTC logo
-RUU attempted to execute
-ERROR [155]: UNKNOWN ERROR -- The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
-Felt confident I had the correct RUU. Proceeded with the Recover button. No success there.
-For confirmation, I know my phone is GSM so I also tried the RUU for AT&T and T-mobile. Again, same error result.
-Device maintains HTC logo on screen.
-After unplug of USB connection, device displays
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.23.213311491.A13G
OpenDSP-v50.2.2-00591-M8974_F0.0810
OS-5.07.1700.11
eMMC-boot 2048MB
I am not familiar with the the command prompt procedure (command fastboot getvar all), but I can provide what the phone displays under BARCODE:
*** LOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS-5.07.1700.11
eMMC-boot 2048MB