Originally Posted by NxNW
You can keep the $100, just see if you can run fastboot getvar all and post the results here and I'm sure plenty of folks will be happy to chime in for free.
If you got adb working on windows 7, presumably you have a working install of the latest android SDK. Also you say you can get into HBOOT.
If so, you're not completely "bricked".
You should still be able to run some fastboot commands. That will be your way out.
Just to spell this out, connect the phone to your PC, boot into the bootloader, select fastboot (on the phone) and try running some of the fastboot commands (from a terminal window in the PC). Start with 'fastboot devices' to see if you are even talking. If your phone's serial number appears, proceed to 'fastboot getvar all' and post the results (edit out your imei and serial number) here.
You can do a lot from fastboot, such as flashing a fresh recovery or even an RUU.
"Brick" is a pretty extreme state. You're not bricked.
Sent from my HTC One using xda app-developers app
Thanks for the help, really appreciate it. My Windows is unable to recognize the phone via ADB, so I cannot run any fastboot commands. I will go home tonight and try again for the exact readout, but I couldn't perform any commands whatsoever.
However, when using CENTOS (through vmware), the OS recognizes the phone:
[root@localhost Desktop]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 003: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Screenshot of HBOOT:
My "main" problem, is I do not know how to get ADB/fastboot installed to my CENTOS mounted on Vmplayer. I think if I can use ADB and fastboot commands, I can push a custom recovery to my phone and install a working ROM.