[madman34]

Greetings,
I have posted this elsewhere during my ordeal a few days ago and it might help you. I did the same thing and I am an engineer, but did miss a logical step which messed me up just the same way as yours. Basically I have found that what happens is that the company has a check in the bootloader that challenges any software to prove that it belongs there. The purpose of the 2.04 unlocker is basically to prevent this and allow us to load anything into the thing we want. This is what happens: In the first step you sync with active sync and load a temporary image of the new bootloader, and then (now this is where I messed up, maybe you too?) I failed to notice the screen on the phone prompting me to 'press the power button', so I did not do it. This would have coppied the new bootloader into the area of flash that holds the stock 1.6 bootloader from Verizon/HTC. All still looked good so I flashed the DCD 2.0.0 ROM and when the phone reset it came to the splash screen and halted, which is what it should do and then you can enter bootloader mode and flash the radio 3.2.7 ROM, well unless you do what I did and not allow the phone to store the new flash because I missed the step and ended up in the stock 1.6 bootloader. So there I was with a splash screen that stuck but said I have the 3.16 ROM and the 1.30.60 radio. The problem here is that the new ROM, the old bootloader, and the old radio are not compatible. The new bootloader will not flash again because it must first be coppied into a specific area of RAM first, then a command sent to it by pressing the power button can then copy it into the flash, but we can not get active sync to recognize it and therefore copy it in. I tried the trick to flash the bootloader from the micro-sd card, but since the new bootloader is not properly signed the stock one holds the screen at 'loading' and refuses to do it. OK then I reasoned that the way to bring it back would be to get the stock updater from HTC but found that it was not there, so I asked around and finally got linked to the FTP here where I retrieved the stated to be ROM file. The updater did for me exactly as it did for you, 0% then timeout, so I figured it was a bust and I had bricked the thing because if the signed version would not go then nothing would. Having nothing to loose, I tried the Sprint 2.09 which is on the HTC page and a very interesting thing happened, it got to 2% before stopping and giving me an 'Invalid Vendor ID' error. This tells me that the Verizon version floating around is NOT totally stock and signed because somthing else for another vendor could at least get a start out of it and failed at a reasonable expected place. Failing to find (at least so far) a valid download of the Verizon software, and because the unit was only 12 days old, I played stupid and told the guy at the Verizon proper store a little fib and said that I was loading stuff and it just locked up and when I reset it that it stuck at the splash screen. He took it to the back to the PST (Product support tool) PC which has the load on it and put it into bootloader mode (power + camera + reset button) and flashed it right back working, proving that I still have not found the stock flash on the net. So if anyone has it, please give, and if not I might in a few days as I have a few friends at VZW that might be able to get it for me. I am now waiting patiently for a stock version. Not because I think it will crash again, but because as some people seem to be doing perfect with the new ROM and some are not, I want a roll back path if it does not work well. Hope this helps.