Post Reply

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

OP Vauix

26th December 2012, 09:56 AM   |  #21  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Dec 2012
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 by so88os; 26th December 2012 at 10:01 AM.
26th December 2012, 10:10 AM   |  #22  
Senior Member
Thanks Meter: 43
 
296 posts
Join Date:Joined: Jan 2012
Quote:
Originally Posted by so88os

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.

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.
26th December 2012, 10:26 AM   |  #23  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Dec 2012
Quote:
Originally Posted by muayyadf1

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.

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.
26th December 2012, 11:35 AM   |  #24  
Junior Member
Thanks Meter: 0
 
14 posts
Join Date:Joined: Dec 2012
I've already decided to send it for service from HTC.
26th December 2012, 12:16 PM   |  #25  
OP Senior Member
Thanks Meter: 75
 
161 posts
Join Date:Joined: Mar 2011
Quote:
Originally Posted by KeroG

I've already decided to send it for service from HTC.

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.
26th December 2012, 02:01 PM   |  #26  
andryyyy's Avatar
Senior Member
Thanks Meter: 104
 
217 posts
Join Date:Joined: Feb 2011
More
Just send it in. Lucky me I got it well-insured.
26th December 2012, 02:20 PM   |  #27  
Junior Member
Thanks Meter: 0
 
14 posts
Join Date:Joined: Dec 2012
Tomorrow it takes the carrier, and will comment if finally falls under the warranty
26th December 2012, 02:43 PM   |  #28  
usaff22's Avatar
Senior Member
Flag Unfortunately, Maps has stopped.
Thanks Meter: 1,476
 
3,472 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by KeroG

Tomorrow it takes the carrier, and will comment if finally falls under the warranty

You should act dumb when taking it to the carrier.

Sent from my HTC One S using Tapatalk 2
26th December 2012, 02:46 PM   |  #29  
OP Senior Member
Thanks Meter: 75
 
161 posts
Join Date:Joined: Mar 2011
Quote:
Originally Posted by usaff22

You should act dumb when taking it to the carrier.

Sent from my HTC One S using Tapatalk 2

Not sure its dumb or smart... Just say it died suddenly (dunno about my carriers ota's...)
26th December 2012, 02:54 PM   |  #30  
usaff22's Avatar
Senior Member
Flag Unfortunately, Maps has stopped.
Thanks Meter: 1,476
 
3,472 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by Vauix

Not sure its dumb or smart... Just say it died suddenly (dunno about my carriers ota's...)

Just say it was updating to the "new version" and suddenly turned off and won't go back on again.

Sent from my HTC One S using Tapatalk 2

The Following User Says Thank You to usaff22 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in One S General by ThreadRank