Well if your device is actually bricked, try downgrading your hboot to 1.4 using closeone's live cd. It's super easy...

Originally Posted by ssojyeti2

Well if your device is actually bricked, try downgrading your hboot to 1.4 using closeone's live cd. It's super easy...

Will try that. Thanks

Originally Posted by El Queson

Will try that. Thanks

Theres no need to do that. For failed s-off and brick after the wire trick (juopunutbear):

1. get sd and battery out
2. insert battery
3. plug into wall adapter and leave it to charge overnight( not pc usb, wall socket)
4. insert battery and try to boot

Also: while attempting the wire trick, use a wire, not a paperclip

Originally Posted by dexter93

Theres no need to do that. For failed s-off and brick after the wire trick (juopunutbear):

1. get sd and battery out
2. insert battery
3. plug into wall adapter and leave it to charge overnight( not pc usb, wall socket)
4. insert battery and try to boot

Also: while attempting the wire trick, use a wire, not a paperclic

Will try this first.

Originally Posted by El Queson

Will try this first.

Also : the modes jb uses have nothing to do with this unbrick method and the downgrade method . Nor all brick types are the same . In fact if you really managed to brick with jb you can't recover with either of the two . The downgrade will just not work

Sent from my HTC Sensation Z710e

I seem to be stuck

---

Originally Posted by dexter93

Theres no need to do that. For failed s-off and brick after the wire trick (juopunutbear):

1. get sd and battery out
2. insert battery
3. plug into wall adapter and leave it to charge overnight( not pc usb, wall socket)
4. insert battery and try to boot

Also: while attempting the wire trick, use a wire, not a paperclic

I had failed s-off and brick after the wire trick (juopunutbear) and tried the above steps last night, but no change.

Then I tried the downgrade method, but closeone's live cd couldn't see my device.

Finally I tried this, but brickdetect.sh doesn't give me the sdX. It just says
The bricked device is on
Use the above node to perform operations using the emmc_recover tool

My Windows Device Manager consistently shows my bricked phone as QHSUSB_DLOAD (unlike the previous poster who reports inconsistent QHSUSB_DLOAD).

I am hopeful, but nothing has worked. BTW, I have used lsusb to make sure my USB is 2.0; I am using the suggested live cd which doesn't have Unity; I have disabled automount; and tried it on a 32-bit and 64-bit using the proper downloads.

All suggestions are appreciated. Thanks!

Originally Posted by rayrodriguez

All suggestions are appreciated.

Thanks!

I'm no expert on this stuff, but it sounds to me like you somehow got stuck in download mode. It might be worth running controlbear one more time to see if it can detect your phone in that mode. If that doesn't work, I found this thread for the HTC One V via Google, and it seems HTC can fix the problem (see post #10) if your phone is still under warranty.

I'd wait until the OP of this thread responds, because he is an expert on this stuff and still might be able to help you.

ramjet73

Here's a post from another forum that might help. That person had the same USB status and was able to recover it using the controlbear program.

ramjet73

I need help.

---

Hi all, I have a huge problem with my evo 3d.
Could not do anything.
I've tried everything already, and not achieving anything.
My evo 3d will be brick or not?
Please look at the photo and tell me what you think.



Anything that can help me appreciate it.

Originally Posted by Troyman

Hi all, I have a huge problem with my evo 3d.
Could not do anything.
I've tried everything already, and not achieving anything.
My evo 3d will be brick or not?
Please look at the photo and tell me what you think.

Attachment 1087061

Anything that can help me appreciate it.

Download the 1.13.651.7 RUU which can be found on closeone's downgrade livecd thread.
Put your phone on fastboot USB and run the RUU. You then should be good.