[UNBRICK] HTC Unbricking Project

[Captain_Throwback]

I bricked mine by flashing "PJ75IMG_Jewel_3.16.651.3_Firmware". It completed successfully but when it finished it turned off, never to turn on again. Now it is stuck in QHUSB_DLOAD (I think -- absolutely ZERO signs of life on the phone itself, and the ONLY indication anything is there is the presence of the Qualcomm, Inc Gobi Modem entry in lsusb). Will this tool do anything to help it pop back to life after the failed firmware flash?

No, it most likely won't. I'm curious to know where you got that file from. That's an older file which is how several devices were bricked before. My thread no longer has that file, and I updated the link in the Wiki too. If there's somewhere else I need to update to prevent people from bricking, I need to know.

 

[NoSkills1]

Support

Stuck in QHSUSB_DLOAD?

Get the RacunHunter!

Support for DirtyRacun is on IRC channel #unlimited on freenode. If you do not have an IRC client you can use the link below.

 

[curiousGeorge]

It was linked and mentioned a number of times from the MeanBean thread as well as themikmik. It was presented as the latest firmware without the touch-panel drivers. I am looking again and I see this firmware in a number of threads, but the zip files in some of them contain the word "extended" which mine did not contain.

I actually downloaded this file a few weeks ago and used it successfully on another LTE device without issue when it was the recommended download without problems.

Is there a known way to recover from this situation?

[edit]
It seems that if the partitions aren't enumerated in Linux, there's no known method of recovering from a failed firmware flash/downgrade. This is the case for me. The only solution is JTAG repair. Some people like MTV do it for $60. Does HTC offer warranty replacement?

 

[ak074]

It was linked and mentioned a number of times from the MeanBean thread as well as themikmik. It was presented as the latest firmware without the touch-panel drivers. I am looking again and I see this firmware in a number of threads, but the zip files in some of them contain the word "extended" which mine did not contain.

I actually downloaded this file a few weeks ago and used it successfully on another LTE device without issue when it was the recommended download without problems.

Is there a known way to recover from this situation?

[edit]
It seems that if the partitions aren't enumerated in Linux, there's no known method of recovering from a failed firmware flash/downgrade. This is the case for me. The only solution is JTAG repair. Some people like MTV do it for $60. Does HTC offer warranty replacement?

sorry but no. htc's warranty is for repair only.

 

[SouL Shadow]

Support

Stuck in QHSUSB_DLOAD?

Get the RacunHunter!

Support for DirtyRacun is on IRC channel #unlimited on freenode. If you do not have an IRC client you can use the link below.

RacunHunter is ONLY for fixing a brick during the use of DirtyRacun. It won't fix anything else.

QHSUSB_DLOAD is not unique to dirtyracun. It stands for Qualcomm High Speed Universal Serial Bus Download. It's a feature built in to all Qualcomm chipsets. However it's usage can be, and usually is, restricted by the OEM (for "security" reasons). It's because of this security that we are so limited in our ability to unbrick this phone.

-SLS-

 

[jclendineng]

any news? I bricked flashing a bad boot.img, was s-off, now no light, power or anything, usually I have been able to unbrick, but linux isnt seeing sdX partitions, only qdl (ttyUSB0)...any updates or should I jtag it and be done with it? Thanks. Scoured google and looks like I am screwed, but just wondering.

Edit, I have an evo 3d, but been following devs here.

 

[dexter93]

any news? I bricked flashing a bad boot.img, was s-off, now no light, power or anything, usually I have been able to unbrick, but linux isnt seeing sdX partitions, only qdl (ttyUSB0)...any updates or should I jtag it and be done with it? Thanks. Scoured google and looks like I am screwed, but just wondering.

Edit, I have an evo 3d, but been following devs here.

Nope. JTAG it

Στάλθηκε από το Sensation μου χρησιμοποιώντας Tapatalk 2

 

[alejobog]

this is the latest version! could try to revive my htc droid dna changing the hboot

 

[smartmazila]

I've bricked wildfire cdma. looking for all wildfire unbrick sites but no luck. Is there any chance to unbrick it with this method? there isn't listed wildfire that's why I ask.

 

[dexter93]

I've bricked wildfire cdma. looking for all wildfire unbrick sites but no luck. Is there any chance to unbrick it with this method? there isn't listed wildfire that's why I ask.

The wildlife isn't supported and will never be. Different soc

Sent from the bricktator

 

[smartmazila]

The wildlife isn't supported and will never be. Different soc

Sent from the bricktator

Sad info anyway thank you

 

[ifsrob88]

My bricked evo 4g lte

First and foremost I would like to thank the devs for their relentless hard work and experimentation to try to figure out a panacea for our bricked htc evo 4g lte. Thank you!!!!

My phone is S-off hboot 1.19 using 3.15 firm TWRP 2.3.1 Mean Bean ROM.

I was on a phone call and the it dropped the call then turned itself off. I tried the extended hold of the power button, the power and vol down and even the three finger salute (power, vol down and camera button}. Since this did not alleviate the problem I went so far as to change the battery thinking maybe it simply lived out its useful life. BTW I only use OEM wires and chargers. I was on the charger when the phone died during the call.

Since I did not get resolution to my problem I read and tried RacunHunter, QHSUSB_DLOAD fix, Jet, Emmc_Recover as you might have guessed it could not find the device...check connections. I read your entire Thread and again was impressed with the knowledge of the devs here and learned so much from all of your comments and insights. I have included the lsusb and dmesg in an attached file so as to not clog up the thread.

Any help, if possible, would be greatly appreciated. If however, sending it off to get it JTag is the only solution the so be it. You are my last resort.

Thanks again and sorry for the long post.

Rob

 

[Vysse]

I am new to linux so I may be missing something but I keep getting
Device can't be detected. Check connections
when I run
sudo ./brickdetect.sh
any help?

 

[ifsrob88]

I have the same problem as you Vysse.

 

[Cyc323]

What is the appropriate package means.?

I looked at the original post and it said to use appropriate package to unbrick. I already have Linux installed and downloaded RUU file. I just need to know where I can download the appropriate package.
Thanks
Eddy

 

[nickcaper]

I looked at the original post and it said to use appropriate package to unbrick. I already have Linux installed and downloaded RUU file. I just need to know where I can download the appropriate package.
Thanks
Eddy

default folder. just hit download and it will download it to the correct folder

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Yea.. Um.....Phone is NOT detected..
Ive tried every USB port there is..

I have this like new white evo right here...
dead..

what now?

 

[Captain_Throwback]

default folder. just hit download and it will download it to the correct folder

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Yea.. Um.....Phone is NOT detected..
Ive tried every USB port there is..

I have this like new white evo right here...
dead..

what now?

Some details might be helpful. How did you get to this point?

 

[nickcaper]

Some details might be helpful. How did you get to this point?

Thanks but I just returned the Nexus and got a G4

Peace!

 

[G0DKING]

Hey captain, just out of curiosity, when the phone connects, can you post the output of: ls -l /dev/ttyUSB0

Still trying to figure out what type of connection is being made. When it's showing a usb dev id of 05c6:f006 it's not a gobi or qdl device, but it is something. Myself and another person are digging around to try and figure it out. He also said he knows EhostDL also shows up with the same id as qdl (05c6:9008), so this is something else altogether...

-SLS-

---------- Post added at 05:14 PM ---------- Previous post was at 04:54 PM ----------

Btw, you are the 3rd person I've seen this week to experience these same symptoms. The phone first goes in to qdl mode, then after some time starts connecting/disconnecting repeatedly, showing up as 05c6:f006. All 3 ppl reached the same result in completely different ways. You most likely because of mismatched firmware, the 2nd because he dd'd partition 5 in to partition 4 (I don't know why he thought that would be a good idea), and the 3rd simply by plugging his phone in to a "cheap" car charger.

-SLS-

I have this problem, too. An lsusb of "ID 05c6:f006 Qualcomm, Inc." with a dmesg of "ttyUSB0: Qualcomm USB modem converter". Have there been any developments in this unsolved mystery?
@SouL Shadow, @dexter93, @Tripp-phpBB, @Captain_Throwback