Hard to say, there are lots of firmware brick problems lately. Could be removal of the hboot, could be you jumped to far ahead in firmware and had some loaders still (like hboot perhaps) that were incompatible with some of the loaders in new firmware. Seeing a lot of this lately....
Sent from my HTC6525LVW using Tapatalk
SO this is what i did.
1. I was running stock VZW with my selection of bloat removed.
2. I am also running custom edited HBOOT, one of the ones with the red text hexed to white (1.55 firmware all around)
3. i flashed evolution mods "fixed for now" kernel
4. This put me in a boot loop (load the OS, run for a sec, then reboot)
5. SO i flashed a few different kernels, scrosler, faux, etc... everything in the book to keep me from bootlooping. No dice and no wifi.
6. SO i was going to reflash the 1.55 firmware update (with kernel) thinking it would flash the stock kernel, and i be back to normal
7. BUT........... (and this maybe where i F'D it up) I removed the HBOOT from firmware zip (my reasoning being i had a 1.55 HBOOT already, and didnt feel like reflashing the modded HBOOT)
8. Threw it in RUU mode, flashed the zip, fastboot reboot, deader than a hammer. And that where i stand.
All MD5's prechecked (i can appreciate the necessity of this from where i work), i use ADB and fastboot commands quite well, we actually feed scripts into singleboard computers through a terminal emulator to prevent typos. Im just surprised i could actually do that.
