Develop Bugs

[Q] Desire S-ON bootloop, RUU img help if u please :)

Hi.
I have a problem with my DHD, and have been browsing these forums for a solution. Im new to this so i need some confirmation, a url, and some explanation.
This happend:
I tried to root my desire HD with visionary+ r14. I did temproot, got back into the app just fine, checked for "set system r/w after root", and clicked attemt permroot. The phone booted, and got stuck in a bootloop. My Hboot menu sais S-ON on top. Tried reseting factory settings nothing helps. Since i didnt get the phone rooted, no clockword recovery installed...
Phone details:
The phone had the factory 1.32 build on it.
other info that might be valid:
Hboot: 0.85.0007
microp-0438
radio-26.03.02.26_M
eMMC-boot
oct 11. 2010
1. From searching and reading, it seems i need a RUU stock image build 1.32, can anyone provide me with an URL for the correct image?
2. Can i use the bootloader on the phone to do this? ..and how?
Hope u have some time to spare, and help this niblet :=)
Thnx for reading
PS:
Before i did this, the phone was rooted, with the same visionary pluss file. I tried to install clockword recovery mod, but it wouldnt "take". I then factory reset the phone in the android recovery menu, and the rest is listed above.

Download your RUU from here: http://xdafil.es/index.php?path=DesireHD/RUU/

How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?

sirreal1988 said:
How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?
Click to expand...
Click to collapse
If you install HTC sync (download it from their website or it is also in your sdcard unless you have not removed it ), you get all the necessary drivers...

Hm, i have installed HTC sync, but as my phone is stuck on the blackscreen and red triangle, HTC sync does not detect my phone.
When i try to run the exe file "RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed", it gives me an error [170], USB connection error.
Is there a way to run this file from the bootloader?

Try to push a PD98IMG.zip (this is stock HTC 1.32 rom from this thread unrooted, hboot s-on) to the sd card, boot into bootloader and flash "new" rom
with adb:
Code:
adb push directory/to/your/PD98IMG.zip /sdcard/
adb reboot bootloader
or if adb doesn't work, put the stock rom into the top of your sdcard, reboot the phone while holding the vol-down button.
follow the instructions on the device(normally it search for the PD98IMG.zip and ask you to install it)

How importanat is the last part of the filename of the RUU file "_2 6.03.02.26_M_release_155891_signed". As the phone is not bootable i cant check find that info on the phone anymore.

"Radio_12.28b.60.140e_2 6.03.02.26_M" it's the radio version.
At the bottom of this site is the USB Driver try it.

Thnx to both of u. Everything now working like a charm.

Good that you got it sorted. Can you edit the tag and put [solved]?

sirreal1988 said:
Thnx to both of u. Everything now working like a charm.
Click to expand...
Click to collapse
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).

soni.setia said:
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).
Click to expand...
Click to collapse
with an unbranded device it should be easy, download the driver and the image in the posts above, install the driver and run the exe.
On linux/unix you can download the sdk (intructions to install on the site) and then you are able to use the adb commands with the PD98IMG.img also in the posts above.
with a branded device it can be more complicated take a look at this but i don't know how far your system is online and if you are able to use adb.

As the guy above me mentioned, it's quite easy to recover your phone if it's unbranded.
Download a WWE RUU from the link someone postet before. Then boot into the bootloader and connect your DHD to your pc. If you have htc sync installed, it should recognise your phone. Then run the RUU on you pc and everything should be fine now.

[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

Received error in installing while getting update via OTA

hi guys,
a very noob person here when it comes to andriod. just want to ask how can i update my device to JB since when i downloaded the updated via OTA there was an error in installing message.
Here is my phone current spec
Endeavor PVT SHIP S-on RL
Hboot - 0.43.000
thanks in advance

R: Received error in installing while getting update via OTA
The phone is Locked or relocked??
And you hboot is very old, which version of android e sense do you have??
Sent from HOX

Guich said:
The phone is Locked or relocked??
And you hboot is very old, which version of android e sense do you have??
Sent from HOX
Click to expand...
Click to collapse
im not quite sure if this is locked or relocked as i got this as a second hand unit
Here are the versions i can see in the software information:
Andriod version - 4.0.3
HTC Sense version - 4.0
Software number - 1.25.707.3
HTC SDK API level - 4.11
HTC extension version - HTCExtension_403_1_GA_3
Kernel Version - 2.6.39.4-g6b459dc
[email protected] #1
SMP PREEMPT Thu Mar 22 20:40:13CST 2012
Baseband Version - 1.1204.90.13
Build Number - 1.26.707.3 CL48562 release-keus
Browser Version - WebKit/534.30
Appreciate for any advice on how can i update my HTC One X device
Thanks

You can use this !
http://androidfiles.org/ruu/securek...Radio_1.1204.103.14_release_257076_signed.exe
It will bring you back to full stock, after that you can update up to JB.

do i need to use a tool to run the setup in my HTC One X?
sorry for the dumb question but this is my very first time in handling Andriod OS
thanks

You can set your phone with pc or your hands...

The RUU is your tool. You hold down the power + volume down button together as long as it takes for you to see the bootloader
On top of the bootloader will say
Unlocked
Locked
Relocked
One of these 3 !
To run the ruu the bootloader must either be LOCKED or RELOCKED !
To lock the bootloader you need this fastboot command
Fastboot oem lock
After that you execute the ruu.exe from the pc and follow instructions. Charge the battery to full power before you start !!!

i tried running the ruu.exe on my laptop but i received an error saying that complete first the current setup before proceeding or contact your administrator

Oke try this
Right click mousebutton on the ruu.exe and select
Run as administrator
And/or reboot the pc once

there was an error on opening in the usb master when the phone opened on the Hboot.
any idea on how can i fix this?

That's normal....we all have that. Its because of the usb cable being plugged in !
But don't press on HBOOT or anything else. Just put it on the first page of the bootloader and run the ruu as above

no luck...im still having the same error while executing the ruu.exe
anything elso i can do?

Hmm well afaik its a computer problem (no administrator rights of some kind) maybe transfer the ruu to another pc and try it again ?

ok will look for another laptop but this is the second laptop that i used but the same error occuers on both
user id used is already the administrator..
how i wish there is still other ways i can update my htc one x

Yes it could be done with a stock nandroid backup but if you don't have that. The problem is your low hboot. I don't think there is one that low available for you.
Can you give these commands another go for me
Fastboot oem readcid
Fastboot getvar version-main
Or a direct hboot flash but i need your exact CID for that ! But then you are still dependant on a custom rom.....

equal dianapa
sir, where should i run the command you just requested?

In steps
1 Download android sdk and unpack the bundle
2 uninstall HTC syncmanager if you have it installed but leave the drivers
3 put the phone in the bootloader
4 navigate in the android sdk folder to the platform tools folder. Hold down shift and click the right mouse button and select "open command window here"
5 type in that window
Fastboot getvar version main
and
Fastboot oem readcid

version is 0.5a
CID = HTC_044

That's not the main version number....try again, it looks like this
1.28.401.** or 2.17.415.**. These are examples !

i cannot run the fastboot getvar version main in the command window
only fastboot getvar version is the being executed which gives me the value of 0.5a

[Q] RUU not detecting device

I was following this guide
http://forum.xda-developers.com/showthread.php?t=1859714
I have appropriate RUU and images
When i run the ruu however it gives an error saying i hsould check the device is connected
i'm running the RUU while in fastboot. Should there be anything i have to do?

mangusbrother said:
I was following this guide
http://forum.xda-developers.com/showthread.php?t=1859714
I have appropriate RUU and images
When i run the ruu however it gives an error saying i hsould check the device is connected
i'm running the RUU while in fastboot. Should there be anything i have to do?
Click to expand...
Click to collapse
Does you pc recognizes the phone?

matt95 said:
Does you pc recognizes the phone?
Click to expand...
Click to collapse
the usual installing driver for usb device popped up.
and i ran some fastboot commabds previously
Edit: Fastboot devices isn't detecting anythign now
I tried re-unlocking but when i go to use fastboot flash unlocktoken unlock_code.bin it gets stuck on waiting for devices.
I tried instaling htc sync and copying the drivers in the win 8 64x section.

Get it on at a win 7 machine.....might be the fastest solution

Mr Hofs said:
Get it on at a win 7 machine.....might be the fastest solution
Click to expand...
Click to collapse
i'm gonan try installing the RUU from a pc i never used for root-related stuff.
Just confirming i need to only install the following for the RUU to install:
Minimal ADB & Fastboot
Htc Sync
and just in case, can anyone tell me where i can find the recovery.img and boot.img i need to flash before installing the ruu
CID HTC_044
getVersion-main number ends with 707.24 (Asia)

The ruu will do that for you

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