[Thunderbolt Android Development] cyberkeeper1:
Actually, use this link to download the RUU EXE file. This is totally stock, unrooted software. This will put you back on hboot 1.15 with XD SHIP Hboot flag. For this, you need ADB.

EDIT: download the RUU ExE Here.

Do this in the following in the command prompt (you MUST be in FASTBOOT mode at this time) :

EDIT 4: There was a code box here, but i moved it down with better instructions and format.

EDIT 3:

ok now what you want to do is override the default way to flash the phone. By default, RUU will use windows, ADB, and fastboot all archived into the EXE file you download. What you want to do is make sure you grab the ROM.ZIP located in the TEMP folder. start the program, follow the instructions, but do not continue once its is at the part where its ready to flash the phone. remember, we want to manually do this because the RUU program WILL fail because of your hboot version. Once you have found the ROM.ZIP file, grab the file and place it in the "platform-tools" folder of the android SDK Tools folder. you may copy or move it, but cutting or moving it will be faster and it doesnt physically move any data, but makes a symbolic link to it. just remember to remove it when finished. This ROM is NOT hboot flashable! you cannot place it into the root of the sd card and flash via HBOOT. it wont break your phone, but you would be wasting your time. this is an RUU and must be done using the fastboot command line. I hope that being this far into trying to return to stock that you have the SDK Tools installed. the paths below are to refer to when searching for the file you need.

For Windows XP and earlier its

"C:\Documents and Settings\_USERNAME_HERE_\Local Settings\Application Data\TEMP"

Vista and above use this path

"C:\Users\_USERNAME_HERE_\Local\Application Data\TEMP"

Once you have finished all of that and put the file where it needs to be, begin to do these commands.

fastboot devices (this is to acquire your serial number)

fastboot oem lock (locks the bootloader and reboots. if you are not already locked)

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 omitted those to save eye strain... ha-ha)

[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.)

if you see this:

FAILED (remote: 90 hboot pre-update! please flush image again immediately)

dont panic. hboot has been updated and the phone must be restarted to continue updating. just re-run the

fastboot OEM RebootRUU

command to reboot the phone. In some cases, the phone doesn't have to be restarted, so just try pushing the zip file again using

fastboot -s <INSERT_SERIAL_NUMBER_HERE> flash zip "<PATH_TO_ZIP_FILE>"

you may refer to my RUU post here if you find anything confusing or or not to your liking. its mostly the same thing but better typed.