Tuesday, 27 October 2015

QDL Mode Brick



Hi Guys,
Long story short, I had an HTC Desire C, but somehow it got stuck in a hard brick (QDL/QHSUSB_DLOAD)... so I decided to look on ebay and find a phone with a broken screen to swap out the boards (since I still had a functional screen). I won an auction for two HTC Desire C's with broken screens/cases, but one of them was also stuck in this QDL Brick. So now I have two HTC Desire C's stuck in QDL Download Mode and one that works. So while I've solved the problem (I have one phone that works), before I consign the other two phones to silicon heaven, I was wondering if anyone has had any success getting out of this kind of brick? I did a lot of google-type research and the furthest I had gone was to connect the phone to QPST... which is moot because I have no files to upload to it.

In case I am not clear and for those of you unfamiliar with what I mean by QDL brick, essentially the phone does not power on (no matter what kind of button combination, fully charged, plugged in, 30 seconds, etc) and when connected by USB is recognised as a Qualcomm device in QDL Download mode. Here is an lsusb printout from Linux of the phone when connected.

Quote:









Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)




And here is a picture of what I get in QPST when I connect one of them to my computer.
QPST Screenshot

If anyone has any suggestions, even if to say that the phones are dead bricks, please let me know. I imagine to fix this using QPST I need files (google qpst QHSUSB_DLOAD, I can't post links since I am a new account), but I have been unable to figure anything out... The other solution I thought was to use backup/restore functions in QPST to transfer good configurations from the working phone to those bricked... but I don't know if this would work and I have not been able to connect the good phone to QPST.
Thanks.



No comments:

Post a Comment