[REF] Dead/Bricked phone after JB OTA, QHSUSB_DLOAD

Search This thread
By:
Advanced…
S

so88os

New member
Dec 26, 2012
2
0
Brick HTC ONE S

Hello friends.
I have a problem after upgrading to JB.
HTC One (s4) Europe2.31.401.5 radio 1.06es].
TWRP v2.3.1.0 hboot 1.14.0002 REELOCKED
So in your example >>> the body of a RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Loader was opened to the right of the root and rekoveri TWRP, SuperCID (units).
Received notification of the new firmware. Battery is 70% +.
What to do:
1. Closed the loader through mcOneSToolsXE 3.5.1
2. Reflash RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe.
3. Received notification of the new firmware.
4. Start the installation.
5. The body has become a brick.
6. Set Ubunti - updated it.
7. Download the necessary files to the root folder.
8. In the terminal window, went through the root to the "Home" for breaching operations "instructions."
9. Brick sees Qualcomm, Inc. Gobi Wireless Modem (QDL mode).
10. In the second terminal window, I see / Dev / sda / dev/sda1 / dev/sda2 / dev/sda5 / dev/sda6 / dev/sda7 ... manipulation of the fishing ... 12 ... did not work ...

One terminal window
Bus 001 Device 005: ID 05c6: 9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 004 Device 002: ID 046d: c050 Logitech, Inc. RX 250 Optical Mouse
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 003 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root forelock

2 terminal window
uaman @ Mars: ~ $ ls / dev / sd *
/ Dev / sda / dev/sda1 / dev/sda2 / dev/sda5 / dev/sda6 / dev/sda7

May already have some solutions for this problem?
That you can recommend?
Thank you.
 
Last edited:
M

muayyadf1

Senior Member
Jan 13, 2012
559
127
so88os said:
Hello friends.
I have a problem after upgrading to JB.
HTC One (s4) Europe2.31.401.5 radio 1.06es].
TWRP v2.3.1.0 hboot 1.14.0002 REELOCKED
So in your example >>> the body of a RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Loader was opened to the right of the root and rekoveri TWRP, SuperCID (units).
Received notification of the new firmware. Battery is 70% +.
What to do:
1. Closed the loader through mcOneSToolsXE 3.5.1
2. Reflash RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe.
3. Received notification of the new firmware.
4. Start the installation.
5. The body has become a brick.
6. Set Ubunti - updated it.
7. Download the necessary files to the root folder.
8. In the terminal window, went through the root to the "Home" for breaching operations "instructions."
9. Brick sees Qualcomm, Inc. Gobi Wireless Modem (QDL mode).
10. In the second terminal window, I see / Dev / sda / dev/sda1 / dev/sda2 / dev/sda5 / dev/sda6 / dev/sda7 ... manipulation of the fishing ... 12 ... did not work ...

One terminal window
Bus 001 Device 005: ID 05c6: 9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 004 Device 002: ID 046d: c050 Logitech, Inc. RX 250 Optical Mouse
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 003 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root forelock

2 terminal window
uaman @ Mars: ~ $ ls / dev / sd *
/ Dev / sda / dev/sda1 / dev/sda2 / dev/sda5 / dev/sda6 / dev/sda7

May already have some solutions for this problem?
That you can recommend?
Thank you.
Click to expand...
Click to collapse
Same here, after the firmware update the phone became a brick and I cannot even see the partitions.
I think somebody is screwing our phones. Not funny at all in christmas time.
I just hope we could fix the issue and not buy another phone.
 
S

so88os

New member
Dec 26, 2012
2
0
muayyadf1 said:
Same here, after the firmware update the phone became a brick and I cannot even see the partitions.
I think somebody is screwing our phones. Not funny at all in christmas time.
I just hope we could fix the issue and not buy another phone.
Click to expand...
Click to collapse

it means that we are not alone, let's hope for the best.
I am confident that the experts will be able to XDA to solve this problem and help us too.:rolleyes:
 
V

Vauix

Senior Member
Mar 30, 2011
162
73
KeroG said:
I've already decided to send it for service from HTC.
Click to expand...
Click to collapse

Yea me aswell. I can't see the partitions either and can't simply pull it out of dload. I suspect the update corrupted our bootloader, but there is no way to know for sure at this point. There have been some cases on other phones devs managed to create a work around. But I don't that's even possible with s-on and locked bootloader.

From what i read on the internet most phones who cant be pulled out of dload (if it ends up there accidentally) they will replace the mainboard. Because it's either a corrupted boatloader or a hardware issue (wide variety from short circuit, charging/battery issues, or fried parts). I don't know if that's because of the man-hours or staff education on the local tech centers. But either way our warranty should cover it although the unlocking I guess. Though I'm not sure if our imei will pop up in a database from unlocking our bootloader via htc-dev.
 
andryyyy

andryyyy

Senior Member
Feb 2, 2011
235
107
I wouldn't even tell them you were upgrading. Just write them it doesn't turn on anymore.

Anyone else noticed the device flapping in its states before it reaches QDL mode?

Reset it from QDL, watch modules getting loaded, unloaded, loaded, unloaded .. until it (sometimes :p) comes back to QDL.

// If there is a developer out there with a very risky idea: Just let us know .. I don't care if it gets even more bricked ;P
 
Last edited:
v3n3

v3n3

Senior Member
May 31, 2012
316
130
Add me to that list :p

Just sent HTC a VERY nice E-Mail, explaining why they suck and that I want a ****ING new Device.
Cant wait for their response tomorrow, might call my lawyer too, just in case they go the "OH, your device is unlocked" road.
 
arsenalfreak

arsenalfreak

Senior Member
Sep 3, 2010
232
40
some people say it happens because it shouldnt be charging when updating ... its written in the update instructions to disconnect from usb during the process O.O

---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------
andryyyy said:
I wouldn't even tell them you were upgrading. Just write them it doesn't turn on anymore.

Anyone else noticed the device flapping in its states before it reaches QDL mode?

Reset it from QDL, watch modules getting loaded, unloaded, loaded, unloaded .. until it (sometimes :p) comes back to QDL.

// If there is a developer out there with a very risky idea: Just let us know .. I don't care if it gets even more bricked ;P
Click to expand...
Click to collapse

yeaa same here ...
 
Last edited:
G

gauron

Member
Jan 22, 2009
13
0
maybe its a help ... i disassemled my bricked phone, disconnected the battery, connected usb and reconnected battery

now a

ID 05c6:f006 Qualcomm, Inc.

device appears ... maybe anyone can handle something with this ...
 
andryyyy

andryyyy

Senior Member
Feb 2, 2011
235
107
gauron said:
maybe its a help ... i disassemled my bricked phone, disconnected the battery, connected usb and reconnected battery

now a

ID 05c6:f006 Qualcomm, Inc.

device appears ... maybe anyone can handle something with this ...
Click to expand...
Click to collapse

Does not help, same here on flapping mode.

---------- Post added at 09:54 PM ---------- Previous post was at 09:50 PM ----------
arsenalfreak said:
some people say it happens because it shouldnt be charged when updating ... its written in the update instructions to disconnect from usb during the process O.O

---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------



yeaa same here ...
Click to expand...
Click to collapse

shouldnt be charged, too?

well, i would give my one s to a dev who is willing to unbrick it .. just text me. he/she could keep it.
 
M

muayyadf1

Senior Member
Jan 13, 2012
559
127
Is there any hope or are we done and need new devices?
please don't say no.
Any developer is trying to do anything?
 
You must log in or register to reply here.

Similar threads

LlabTooFeR
[ROM] MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 | Fast&Stable | OTA | 4.06.401.1
Replies
3K
Views
755K
K
kdd998
show-p1984
[Kernel] Bricked-Kernel Ville - Sense JB
Replies
3K
Views
309K
javelinanddart
javelinanddart
brwetz
[HOW-TO] ADB Push a ROM to your phone
Replies
71
Views
438K
Bertonumber1
Bertonumber1
itsmikeramsay
  • Locked
[ROM][S4][TMOUS]~|Axiom S & S-Less|~[Aug 17]~|AXSuite & OTA Updates|
Replies
5K
Views
406K
O_G
O_G
bilal_liberty
[ROM][JB][11.07] Team Venom presents: ViperOne S 3.2.1 - Welcome to the future
Replies
1K
Views
273K
Flippy498
Flippy498

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    V
    Vauix
    Hi All,

    There are more and more reports coming in from people who ended up with a dead/bricked phone after the JellyBean Update 4.1.1 , 3.16.401.8 OTA. As you connect it to your PC you will soon find out it's in QHSUSB_DLOAD mode.

    The purpose of this threat is to see how many people are affected, what people have done to attempt to recover their phone, and to find a possible solution (this chance seems rather small though).

    There are alot of post about this in the JellyBean Speculation/News/Discussion threat, starting from page 157.

    There are 2 threats about it in Q&A:
    One S in QHSUSB_DLOAD mode
    My HTC to really died

    Reported attempts to recover:
    QHSUSB_DLOAD Fix by team Unlimited
    Unbricking HTC devices with the QHSUSB_DLOAD issue tutorial by kgs1992
    Step 3 (and some others) from [TUT] Downgrade/Unbrick Ville S4
    Another HTC one V recover guide where i can't find the link for.

    Please report here if you have this issue. Please mention your CID, in what country you downloaded the OTA, the software version you upgrade from and the hboot version.

    Also any new ideas to recover our phones our self are welcome!

    My phone:
    2.31 Unbranded Europe
    1.14 Hboot
    Downloaded in The Netherlands
    1111111 Supercid
    View
    2
    Tecardo
    Tecardo
    Hello, can some one of you plaese send me his bricked One S? I live in Germany,so a german person would be good:
    Contact me on tecardo@gmail.com or here on this forum.
    If the device doesn't work anymore, i will send it back as it is, and also will send back if it works again: I WILL NOT START PHONE, NOR WILL I READ ANYTHING OR DO ANYTHING WITH YOUR PRIVATE DATA. You can get this with a letter if you want.
    I only need a device with this error. I will wipe Phone if wanted.


    Thanks.
    View
    2
    andryyyy
    andryyyy
    Noch ein Düsseldorfer ;P
    View
    1
    H
    hellgod
    My phone is bricked too

    Orginal CID was HTC_203 (maybe), not branded by telecom company - France
    but changed to 11111111

    I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
    View
    1
    ryanshew
    ryanshew
    Jnanadarshan said:
    So does that mean if I run JB on HTC__001 CID it'll work ? Though I've T-Mob version of Jelly Bean I want WWE RUU to run.
    Click to expand...
    Click to collapse

    No, t mobile has different MID. You need to s-off for that.

    HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
    View

New posts