Related
Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Hi guys,
i have exactly the same problem, already have tried all of these solutions, nothing have worked for me... Please help.
PS:sometimes my screen lights up <black totally, but lights up>... when plugged into usb cable or charger... but not now anymore...
I have bought this phone in china, there is S/N but i guess that here in UK i cannot do anything about it since HTC's warranty is not global...
listenger said:
Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Click to expand...
Click to collapse
Have you tried a different battery?
I just ordered a new battery... Takes a couple of days before I recieve it
listenger said:
I just ordered a new battery... Takes a couple of days before I recieve it
Click to expand...
Click to collapse
Also keep note of which recovery you are working off of. There have been charging issues with certain recoveries.
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
listenger said:
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
Click to expand...
Click to collapse
I would suggest to go to a store that sell's the Sensation and ask if you can test one of their batteries out to see if your phone has either a battery issue or something else. If you are stateside, of course try a tmobile store, but without knowing where you are located, this is a hypothetical at this point.
I know I had an issue with my Nexus1 not booting up from a kernel I had flashed. But I noticed my charging led was flashing three times and then stop. I researched this here on xda and found that it just needed to be put into recovery again somehow. I ended up just plugging the phone into the wall and remove the battery. Try to power it on there and then reinsert the battery and try the power + volume down button. That time it booted for me. But again, this was for my Nexus1 not with this phone.
same happened to me, sent to HTC and had main board replaced, lcd, flex cable etc. the driver the phone looks for is the equip HTC use to jtag... I am not sure if this is a hardware failure or boot corruption...but even though it was s-off via alpha rev it was that damaged they didnt complain... i say hardware failure. the thing is even when i have s-off i didnt change the rom. I have a riff box on order so if this happens again we can surely see if this failure is software or hardware..
Yeah, do what kpjimmy said; go to a store where Sensation's are sold and ask if you could use a battery to test it out to see if it's bricked. It it's not, you'll need a new battery (try getting one for free from HTC, citing warranty. I did it with my battery cover). If it doesn't work, you're mostly likely bricked, unfortunately. Refer to anarchy's post for more info on that side of things
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
arifafzan said:
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
Click to expand...
Click to collapse
Havn't had the time to really do any custom ROM or the like, so the phone was all original from the factory...
So I'm stumped... I've flashed my Charge many times, no problems until now.
I wanted to flash back to stock ROM and had my Samsung drivers installed and Odin recognizing the phone and everything was good, but then Odin was taking WAAAAAAY too long. In the past this usually took about 20 mins. This time, after 45 mins and the progress bar hanging in the same place for 30+ mins on factory.rfs I disconnected the phone (I know this is where I screwed up). Now Odin won't recognize the phone at all. It does get into download mode, but Odin won't pick it up.
Same computer, same cable, and same USB ports as I've had when flashing this phone many times before. I don't know what my options are now. I don't think I can flash either the ROM or PIT without Odin at least recognizing the phone. What can I do now?
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
dragonlady726 said:
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
Click to expand...
Click to collapse
FWIW, I've also noticed a simple computer reboot fixes it....
jco23 said:
FWIW, I've also noticed a simple computer reboot fixes it....
Click to expand...
Click to collapse
I neglected to mention in my OP that I was going through the right protocol with driver uninstall/reinstall and rebooting each time. I rebooted again for good measure after seeing your post but I still get the same.
It's the same result from two different computers, one with Win7 and the other XP (I read in another thread that XP had worked better for some). If the phone is powered on, even though it doesn't successfully boot, Odin and Windows recognize it properly. If it's in download mode neither one recognize it, windows says the device failed to start and shows either unrecognized device or "Gadget Serial" (which would be a great name for a band, but google searches for it aren't much help).
I don't think it's a driver problem because it's recognized when the phone is powered on. But could there be a specific driver out there for the phone when in download mode only? I've flashed this phone dozens of times and never had a problem until now. I'm on the verge of forking over the $50 and sending it to JTAG if no one can suggest something else to try. Please help
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
lukegman said:
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
jco23 said:
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
Click to expand...
Click to collapse
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
dragonlady726 said:
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
Click to expand...
Click to collapse
Also, are you sure you have enough battery juice? To make sure, leave it plugged in to a wall outlet for about 30 min to an hour.
tappin' that....
Finally fixed - Bad USB port
Just to close out the thread, I did finally get my phone fixed. The issue was a bad USB port that decided to fail during flash. This is according to Josh from MobileTechVideos, who is a great guy with amazing customer service.
Longer version: I sent it off to MobileTechVideos/JTAG and after a week I got a call back saying the JTAG process didn't work and as a last resort they could try replacing the USB port itself. Josh told me that it was either the port or the controller, that the port was a known failure point on the Charge, and if replacing the port didn't work it meant the USB controller had failed and I'd be out of luck. He also said that if the port replacement didn't fix the issue he wouldn't charge me and refund my original payment (which impressed the hell out of me given the time he had already put into it and there was no guarantee that the extra work would fix it). This was late afternoon on Valentine's Day... he said that he'd get to swapping out the port the next day but an hour later called back to tell me that he replaced the port and flash was successful. I wish everyone was as straightforward in communication and dedicated to their job.
So yeah, MobileTechVideos is legit, Josh is a rock star, and send those guys your phone if something really screwy happens. They will take the time and go above and beyond if necessary to fix it, and you will absolutely get your money's worth.
Hoping that no one else is "lucky" enough to have their USB port fail mid-flash, but if your symptoms look like mine a bad port might be your problem.
I've heard nothing but good things about them. I've never used them myself, but I have directed a couple of people to them and heard nothing but glowing reviews.
Cool I managed to finally back up my sd card after a few attempts with a bad port (went out after a month of having the phone). I've been on a rotating batteries off a wall charger system, but need to odin because everytime I get down to 110-120 ish mb of internal memory my charge says low memory blah blah, I clear cache, play store , etc.
Needless to say people have said resorting back to stock ep4 etc with Odin should work, but I'm afraid mid flash something will happen. I have to jam the cord in, wrap extremenly tight while holding the phone at a perfect angle and sometimes it still will beep like being disconnected.
I have no idea if this would be possible for you, but I wonder if Mobile Odin could help you?
Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?
amateurhack said:
Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?
Click to expand...
Click to collapse
Have you tried to force reboot (Vol down + Power button for about 7-10 secs)?
Yes. Thanks for the reply. That's what I meant by soft reset. What the issue, I figured out, was that my battery had decided to self-destruct. It didn't have enough charge to even boot the phone successfully, so it was not possible to put it into recovery mode or anything else. I took it to Sprint and they replaced it under warranty.
Sent from my XT897 using XDA Premium 4 mobile app
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
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
timmaaa said:
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
Click to expand...
Click to collapse
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...e_Replacement_Parts_Tools&hash=item4d1859d891
I will still attempt the guides here: http://forum.xda-developers.com/showthread.php?t=1966850 and here http://forum.xda-developers.com/showthread.php?t=2226445
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
badbwoydes said:
Can a replacement battery resolve this? A friend has the same phone with a broken LCD that he's scrapping
Click to expand...
Click to collapse
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.
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.
falcon66 said:
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.
Click to expand...
Click to collapse
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.
badbwoydes said:
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.
Click to expand...
Click to collapse
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.
So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.
One option you can try is getting an EDL cable.
Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.