Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,785,935 Members 52,750 Now Online
XDA Developers Android and Mobile Development Forum

Completely dead, unresponsive phone

Tip us?
 
badbwoydes
Old
#1  
Senior Member - OP
Thanks Meter 8
Posts: 109
Join Date: Sep 2010
Location: Kingston

 
DONATE TO ME
Unhappy Completely dead, unresponsive phone

Hey guys,
I can't believe what happened to my phone. It was working perfectly up until a few hours ago.
I tried flashing ElementalX v8 which I have been running for months with no issues, as I wanted to change some of the settings. After the flash, it showed it was successful, but there was also another line similar to "E: cannot mount partition". Can't remember exactly. I went to wipe cache and dalvic manually as I always do, then saw a few more lines that looked similar to that, then after tapping Reboot the System, my phone powered off and hasn't worked since. The battery was at 21% and plugged in at the time, which I suppose is risky, but i've never had a prob before. I flash ROMs. radios and kernels a lot.

My phone will literally not do anything at all right now. The LED isn't even on while it's plugged in to it's wall charger, it won't vibrate, flash anything on the screen. Absolutely nothing
I have tried holding power button for up to a minute while plugged in and unplugged, and also, held volume down and power for up to a minute while plugged in and unplugged.

When I connect it to my PC, it shows a device with a driver error "qhsusb_dload". From my research, it seems that I will need to send it for JTAG service or try the steps in the "unbrick evita" thread, which I will, after leaving it plugged in overnight.

I would like to know:
Can I resolve this by purchasing a used Logic board, either from the AT&T or International version?
Can a replacement battery resolve this? A friend has the same phone with a broken LCD that he's scrapping
Is there any possibility it will start working again if it was just left plugged in for hours?

I am in Jamaica and this is a really sticky situation for me. I can't even get a phone out here to use a MicroSIM :-/

I'd appreciate any help at all. Thanks
Device: AT&T HTC One X (4G > 4 Cores) [SIM Unlocked, Rooted, Boot Loader Unlocked, S-OFF]
ROM: ViperXL 3.2.8, JB 4.1.1, Sense 4+ / Heavily customized with Venom Tweaks
Kernel: ElementalX v7.0.2 (OV +5mv, (1000mv base - hard to get stable), 1.4GHz, ROW, Lionheart, No zRAM, Fast Charge)
Recovery: TWRP 2.3.0.0
Radio: Telstra 2.40

RIP HTC TouchPro (aka: AT&T Fuze)
Lover of all things HTC and representing Jamaica!
 
timmaaa
Old
#2  
timmaaa's Avatar
Recognized Contributor
Thanks Meter 5,873
Posts: 12,632
Join Date: Jun 2011
Location: Melbourne

 
DONATE TO ME
Firstly, it is the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? Where did you download the kernel?

I think you are one of the very rare and unlucky people whose phone has bricked for no apparent reason. A battery will not fix it because your partitions are screwed. The only options you have see these:

1. Leave the phone connected to a charger overnight (or at least eight hours) and try to power it on again. This option only has a very slim chance of working.

2. Replace the motherboard.

3. Jtag repair.

Sent from my Evita
OnePlus One | crDroid/AK.033 | TWRP 2.7.1.1

Do not PM me asking for assistance, that's what my Q&A thread is for!
The Following User Says Thank You to timmaaa For This Useful Post: [ Click to Expand ]
 
badbwoydes
Old
#3  
Senior Member - OP
Thanks Meter 8
Posts: 109
Join Date: Sep 2010
Location: Kingston

 
DONATE TO ME
Quote:
Originally Posted by timmaaa View Post
Firstly, it is the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? Where did you download the kernel?

I think you are one of the very rare and unlucky people whose phone has bricked for no apparent reason. A battery will not fix it because your partitions are screwed. The only options you have see these:

1. Leave the phone connected to a charger overnight (or at least eight hours) and try to power it on again. This option only has a very slim chance of working.

2. Replace the motherboard.

3. Jtag repair.

Sent from my Evita
Thank you for the reply.
I have the AT&T One X 16GB Model. The Kernel I has was from these forums as well, which I used numerous times before. I just wanted to flas it again to change the settings so the kernel file itself has been on my phone for quite a while now.

Is this the only part i'll need to get?: http://www.ebay.com/itm/ATT-HTC-One-...item4d1859d891

I will still attempt the guides here: http://forum.xda-developers.com/show....php?t=1966850 and here http://forum.xda-developers.com/show....php?t=2226445
Device: AT&T HTC One X (4G > 4 Cores) [SIM Unlocked, Rooted, Boot Loader Unlocked, S-OFF]
ROM: ViperXL 3.2.8, JB 4.1.1, Sense 4+ / Heavily customized with Venom Tweaks
Kernel: ElementalX v7.0.2 (OV +5mv, (1000mv base - hard to get stable), 1.4GHz, ROW, Lionheart, No zRAM, Fast Charge)
Recovery: TWRP 2.3.0.0
Radio: Telstra 2.40

RIP HTC TouchPro (aka: AT&T Fuze)
Lover of all things HTC and representing Jamaica!
 
timmaaa
Old
#4  
timmaaa's Avatar
Recognized Contributor
Thanks Meter 5,873
Posts: 12,632
Join Date: Jun 2011
Location: Melbourne

 
DONATE TO ME
That looks like the right part to be, except that it's a 32gb model, which I don't think would be a problem. It's definitely worth trying this unbricking methods, but successful attempts are pretty rare. I think you're about the third person I've seen brick after flashing the Elemental kernel.

Sent from my Evita
OnePlus One | crDroid/AK.033 | TWRP 2.7.1.1

Do not PM me asking for assistance, that's what my Q&A thread is for!
 
redpoint73
Old
#5  
redpoint73's Avatar
Recognized Contributor
Thanks Meter 2,961
Posts: 6,707
Join Date: Oct 2007
Quote:
Originally Posted by badbwoydes View Post
Can a replacement battery resolve this? A friend has the same phone with a broken LCD that he's scrapping
Its not a battery issue. As timmaaa mentioned, something went wrong with the flash (as it has happened to a couple others). JTAG is probably your best bet, or replacing the board.
Please click the "Thanks" button if you found a post helpful!

Phone: AT&T HTC One (M8)

Tablet: Samsung Galaxy Tab Pro 8.4 (WiFi only)
 
falcon66
Old
#6  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Mar 2013
This probably wont help but I had a bad flash of twrp not long ago. Flashed the recovery and the phone died on reboot. I hooked it up to the computer and i got "qhsusb_dload" in device manager. I thought it was bricked for sure. Anyway while i was trying different things, I held the power button on for a long time and it started up again. It didn't have a recovery but i flashed 2.6.3 again and it has been fine ever since. Thinking that i was one of the lucky ones though. I guess you have already tried that though.
 
badbwoydes
Old
#7  
Senior Member - OP
Thanks Meter 8
Posts: 109
Join Date: Sep 2010
Location: Kingston

 
DONATE TO ME
Quote:
Originally Posted by falcon66 View Post
This probably wont help but I had a bad flash of twrp not long ago. Flashed the recovery and the phone died on reboot. I hooked it up to the computer and i got "qhsusb_dload" in device manager. I thought it was bricked for sure. Anyway while i was trying different things, I held the power button on for a long time and it started up again. It didn't have a recovery but i flashed 2.6.3 again and it has been fine ever since. Thinking that i was one of the lucky ones though. I guess you have already tried that though.
Hi. When you said died on reboot, do you mean you chose the option for it to reboot then it never turned back on? Mine is literally and totally dead. It does absolutely nothing and when it's plugged in to my PC it shows "qhsusb_dload"
How long did you hold the power button? I've held mine for about 3 minutes now.
Device: AT&T HTC One X (4G > 4 Cores) [SIM Unlocked, Rooted, Boot Loader Unlocked, S-OFF]
ROM: ViperXL 3.2.8, JB 4.1.1, Sense 4+ / Heavily customized with Venom Tweaks
Kernel: ElementalX v7.0.2 (OV +5mv, (1000mv base - hard to get stable), 1.4GHz, ROW, Lionheart, No zRAM, Fast Charge)
Recovery: TWRP 2.3.0.0
Radio: Telstra 2.40

RIP HTC TouchPro (aka: AT&T Fuze)
Lover of all things HTC and representing Jamaica!
 
falcon66
Old
#8  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Mar 2013
Quote:
Originally Posted by badbwoydes View Post
Hi. When you said died on reboot, do you mean you chose the option for it to reboot then it never turned back on? Mine is literally and totally dead. It does absolutely nothing and when it's plugged in to my PC it shows "qhsusb_dload"
How long did you hold the power button? I've held mine for about 3 minutes now.
It was less that 3 minutes. I flashed the recovery in fastboot, rebooted and it didn't start. No led when plugged into the charger. Showed "qhsusb_dload" in the my computer's device manager. It was just dead. It was the right recovery for the phone, just the modified 2.6.3 version for 4.4.2 roms. After I got it going again, I flashed the normal version. I have since flashed the modified one again and it was fine. I don't really know why it happened.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA Xposed Tuesday: How to Control Google Play Wake Locks – XDA Developer TV

Xposed Modules are usually pretty simple. There are a few … more

Make Text Entry More Efficient with Macro Text Expansion

One of the best things about the modern day smartphone is its ability to save us … more

Fix KitKat WiFi Drops on Your Own

Despite introducing many useful features and overall great performance and enhancements,Android 4.4 KitKat … more

Bring Back Tablet UI on KitKat

Google presented their brand new UI for tablets alongsidethe release of Android 3.0 Honeycomb back in early … more