[Q] Stuck On White HTC Boot Screen PLEASE HELP!!!

When I first turn on it'll stay stuck in HTC white screen logo till battery dies.

If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.

I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.

When I first turn on it'll stay stuck in HTC white screen logo till battery dies.

If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.

I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.

I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.

Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?

The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):

You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".

If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.

I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.

If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.

sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).

Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?

The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):

You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".

If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.

I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.

If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.

sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).

I have the vivid , and yes it says *** locked ***

I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?