[Thunderbolt General] cyberkeeper1:
Solution to RUU failures to any of you out there.

first off, many thanks to you guys for providing me with the shipped-roms.com link, because i would have never figured out where the roms were, nor would have i discovered what i am about to tell you. Most of the time my finds happen by accident... lol.

This function will work for ANY HTC phone that uses RUU as an update source. works for any version so far as i know. i updated and restored using xx.605.5 and it worked fine. :)

anyhow, without further delay...

Guys i have something VERY interesting when i was reviewing a debugging output. i managed to get a hold of a fastboot code to enter RUU mode. thats right... manually enter RUU mode and flash a STOCK zip file from shipped-roms.com, or any other place that has stock roms. i went into my temp folder and grabbed the extracted "rom.zip" from the RUU application once it loaded and asked me to start the process, and copied it to my desktop. Once that was done, i simply closed the program because it failed so many times with Error 155. OH I AM SO EXCITED. it flashed everything. forget that dumb program. i did it myself and hboot flashed to the old 1.04.0000 and everything else. IT WORKED!!!!!! no splash loop, no stuck HTC screen... nothing!!!!

I have found this out as a computer technician over the years... if you want something done right, find a way to do it yourself instead of letting some program automate it for you. i will share with you my ingenious HARD work to find this info. it took me weeks to get this phone working. My hboot WAS corrupted so of course it would not load anything.

Here is my lovely command set to get it to RUU manually:

First, put your phone into fastboot. you know the drill, Power + Vol Down. you will need to write down your serial number. Second, in order for this to work, you MUST have your bootloader locked. do not worry about the ***security warning*** because it will overrule it. the worst it wll say is ***Relocked*** as mine does once its finished. but who cares? now i can use the REV tool properly to to properly root the thing.

fastboot devices (this is to acquire your serial number)

fastboot oem lock (locks the bootloader and reboots.)

fastboot -s <INSERT_SERIAL_NUMBER_HERE> oem rebootRUU

fastboot -s <INSERT_SERIAL_NUMBER_HERE> getvar boot-mode (fastboot checks what boot mode you are in. It will say boot-mode:RUU.)

fastboot -s <INSERT_SERIAL_NUMBER_HERE> erase cache (very much needed, others need not be formatted as RUU will automatically.)

fastboot -s <INSERT_SERIAL_NUMBER_HERE> flash zip "<PATH_TO_ZIP_FILE>" (must have quotes, and must be a signed, stock zip file.)

afterwards, fastboot will output with the following messages: (along with every file it loads, but i have ommited those to save eye strain... haha)

[QUOTE]Here is the output i got from fastboot while updating:

INFO start image[hboot] unzipping for pre-update check...
INFO start image[hboot] unzipping & flushing...
INFO start image[boot] unzipping & flushing...
INFO start image[recovery] unzipping & flushing...
INFO start image[system] unzipping & flushing...
INFO start image[sp1] unzipping & flushing...
INFO start image[dzdata] unzipping & flushing...
INFO start image[mdm9k] unzipping & flushing...
[/QUOTE]
if everything goes well you will see:

OKAY [278.641s] (this is how long it took in my computer. your total time value WILL be different.)

There was more INFO output, but i got tired of copying it.

Anyhow, as you can see it was successful and i was able to completely restore my phone, google account and everything. if you have any questions, let me know please. also, i think because this does not exist on any forum i have read so far, it should be made as a sticky in the thunderbolt general forums. It is my request that it be done for users who have the same or similar problems.