Hello XDA-Forum,
i am new here, so you dont know me. Therefore i have to mention at least one thing about me: I never ask for help. Especially not regarding electronic Devices and Computer Systems. I always found my answers without asking.
Now i do ask for help. Do the math, its a serious problem . As i am used to solve my problems before asking for help, i have much to tell before anyone could add to what i already know about this problem (although i have to admit that i am pretty new to the Smartphone World). And as sure as i know that no one here wants to read another "Phone broken, HELP!" Thread, so sure i know that not everyone has the time or patience to read my ramblings (i actually wrote a rant too, but decided not to include it here ). So i prepared a summary, and you can see at a glance (almost) if you could help me at all.
Short Story:
My HTC One is Hard Bricked, and beyond my ability to repair - stuck in QHSUSB_DLOAD mode, no access to partitions, no booting under dead screen. It seems i have to send it in for repairs, but i dont like that(well who does?). I researched the problem, tried every solution i could find - no result! if you happen to know a solution, please read the long story to learn what i have tried so far, and if your solution is something completely new (something i didnt try) - PLEASE tell me ASAP before i send it in for repairs.
So, i tried everything i know of and came to the conclusion: it is beyond repair, at least for me. But as this is against everything i believe in (well not everything but i hope you get the point ) i want to find some other Solution if not for me ( as i need my Phone to be working again soon) then at least for the next one facing the same problem. Again: read the long story, or at least the last part, to know what i am asking for... Basically i want to collect all information regarding this problem and find a solution if possible.
Oh and i would prefer technical answers (even if i might have to learn more to understand them) over answers that suggest "Dont bother, you are a noob, you wouldnt understand, just send it in". If you are about to give such an answer, rethink and do something else .
Long Story (Part 1 - What happened):
31/12/2013: My HTC One suddenly stopped working. Until then it worked just fine since i bought it in July 2013. It happened without any apparent cause or any hint of what went wrong, during everyday use, no water involved, no falling, nothing that i could identify as cause. I pressed the power button to wake the phone as always - but the screen stayed black. At first i thought the battery could be empty, but i checked it only 5 minutes before, and it said 32%... still i thought the power indicator could be buggy. Since then it never showed any lifesign again though. It wont start, it wont charge.
I researched about this, and it seems that others had the same problem, and on several different devices. I think i found almost every Qualcomm based device, but mostly the problem was caused by flashing, so this can not be the same problem. If i remember correct, i found HTC One, HTC One S, HTC Desire C, HTC Sensation, Nexus 4/7, Samsung Galaxy S3/S4 and maybe some more, with the same issue i have - Device suddenly went black and got stuck in QHSUSB_DLOAD mode without apparent cause. Many people get at least a lifesign from the LED tough ( be it blinking occasionally, or staying on all the time, or blinking after pressing certain buttons) - i dont.
Long Story (Part 2 - What i tried):
I found several tips on how to revive a device in this state, most recommending something like "press power and one(or both) volume button(s) for XX seconds/minutes" sometimes with the addition to do this under a bright light bulb.
I tried holding the power button, power + vol. down, power + vol. up, power + vol. up + vol. down, for {10,20,30 seconds, or 1,1.5,2,3,5,10 minutes} (countless times), and the same under a light bulb (i doubt this makes any difference as i already did some resets previously, outside in pitch black darkness long before the phone died).
Some recommended to plug it in to charge and dont touch it for 3,8,12 hours - i did that. i tried charging with wall plug and via USB at laptop (for short periods and for 1,3,4,6,8,12,18 hours without touching it).
At the moment i try to leave it off the charger for some days (the weekend and probably some days after) hoping that it will eventually loose all charge and does some sort of reset after that. I doubt it will work, or even be enough time for discharging (as i doubt that it actually USES power in this state) but dont know what else to try before sending it in.
The charging-led stays off when plugged in and there is no response at all from the device. Except when i plug it in at the laptop, Windows recognizes it as QHSUSB_DLOAD. And under Linux i get the Qualcomm device too - no partitions though. If i press power for 10 seconds while connected, it reconnects - so the power button is working. QPST recognizes it as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode? I tried to get some information through QPST but it tells me the phone needs to be in DIAG mode - which i obviously cant activate on the phone itself. Other than that no life sign at all( also no recognition by adb and fastboot - so its not booting under a dead screen as someone suggested somewhere - dont remember where).
Everyone who had gone as far as i did in trying to revive the phone just gets this last answer "JTAG, or send it in for repair".
Long Story (Part 3 - What i learned):
As i understand it, the Qualcomm Processor switches to this state (QHSUSB_DLOAD) in case there is a severe problem. But i want to know exactly WHAT problem can cause this? And if there is ANY way of convincing the processor to switch to some other state without opening the device?
I dont know JTAG, i never heard of it before this research, so please correct me if i am wrong, i did just a brief research on JTAG and found it too complex to grasp in one or two days i will delve into it at a later time. Here is my first few-minutes-glance at JTAG: it is some sort of standardized hardware-debugging protocol built into many chips, and also the Mainboard or Processor or both in modern Smartphones and Tablets. One would need to open the device and solder the connection cables of a "JTAG-Box" to specific contacts on the Phones Mainboard, is that right? or is there a plug? (I think i found some people using a plug and some using solder iron... i dont remember properly.) When a JTAG-Box is connected to a JTAG-enabled chip, it can issue debugging-commands and/or queries to check (and/or modify?) the functionality of the chip. I found some mentions of JTAG via USB without explanation, is this a way to issue JTAG commands without JTAG-Box over USB Cable? (would be very convenient) Or is it just a way to connect the JTAG-Box via USB to the Computer?
You might ask, if i researched it, i should have every answer, so why am i posting this? Right, i got SOME answers. Now, i know...:
1) ... that am not the first one, nor the only one with this particular Problem. And not even my phone model is the only device with this problem. It might be, all Qualcomm powered devices are possible candidates for a sudden-brick-syndrome.
2) ... some ways to revive a Phone in this state (none working for mine).
3) ... if all reviving tricks fail - JTAG or Repair-service.
4) ... that JTAG needs an opened device (or does it? JTAG via USB maybe?)
5) ... that my phone is not entirely dead: at least the processor can still (sort of) communicate with the PC in Qualcomm High Speed USB - DownLOAD mode.
6) ... no one knows (or tells) what the cause is (or could be) for this problem. The only answers i got are: "There are many possible causes." and "It could be a Software problem" (HTC Support) and finaly "No one can tell without analyzing the device" (HTC and Carrier Support) - Sure no one can definitely tell what EXACTLY is wrong with THIS device... but someone could know what COULD be wrong (What the KNOWN causes are), and just tell me.
Long Story (Part 4 - What i want to know):
Well... I could(/should?) just give in and send my phone in for repairs and hope for warranty. But i did unlock the bootloader through HTCDev (had no other option for unlocking due to HBOOT 1.44) and suspect, they might use this fact to refuse warranty and charge me for repairs, which i might not be able to afford right now. Further, i am feeling absolutely helpless in doing so, and i am NOT used to feel helpless facing ANY sort of problem with ANY electronic device! It is NOT a nice feeling! And i want to change that! Even if it will be too late for me, as i have to get my phone back soon and will probably send it in this week for that reason, i want to find a Solution, that anyone could use to solve this Problem without even contacting the Service, if it is possible to find such a Solution. That is the reason i am posting this, and here is what i want to know:
1) EVERY Story about devices stuck in QHSUSB_DLOAD mode.
1a) IF they where revived and HOW.
1b) What was the cause?
1c) If they could not be revived...
- ... and had to be replaced by a new device: what did the repair team tell what exactly was broken? if they told you anything at all.
- ... and needed replacing parts: WHAT parts where replaced?
- ... ANY hint of what caused the defect?
1d) WHEN did it happen? (while flashing seems to be the most common scenario, but i and some others had it happen during everyday use)
2) What exactly is possible to do in QHSUSB_DLOAD mode (probably using QPST)? and what isnt? f.e.:
2a) Pulling any data from the phone without switching to DIAG mode?
2b) Getting ANY information about the phone? (IMEI,CID, etc... Hardware components - i guess it would need a switch to DIAG mode?)
2c) Switching to DIAG(or any other) mode ONLY using the PC and USB connection? (if possible, how?)
2d) Pushing any Data to the device
As i understand it, that is the purpose of this mode(is that correct?), but:
2e) What data can be pushed? Bootloader? System Image? .... i think some CPU firmware is delivered with QPST, correct?
2f) Is it possible to convert an existing System Backup so that it can be flashed with QPST? (i understand QPST needs files in IntelHEX format to push them? Or is that just the CPU Firmware?)
2g) QPST recognizes my phone as "Q/QCP-XXX (Download)". Is this normal or should it recognize the phone model even in download mode?
3a) If i get no Partitions in Linux while the QHSUSB_DLOAD device is recognized, could this be an indicator for an Hardware failure?
3b) Does it mean, at least the flash memory is fried? (my guess)
3c) Could i tell if the Mainboard was fried by NOT even getting a QHSUSB_DLOAD device? Or can it still be the Mainboard?
3d) Can i tell anything from these facts (Getting QHSUSB_DLOAD device recognized but no partitions)? other than "its a hard burned brick" obviously...
4a) Which kind of HARDWARE failure could create this state?
4b) and how could that happen during normal use in a device that is only 6 months old, and in good condition? 5a) What kind of SOFTWARE failure could cause it?
5b) while it is running? (every day use / not flashing) 6) IF i send it in:
6a) Will they be able to access my data?
6b) Can they tell (by JTAG maybe) if it was rooted,flashed, had an unlocked bootloader?
6c) And the hardware is dead, will they just replace the fried parts? or replace the Phone with a new one? (not really important but nice to know )
7a) Is it possible to use ANY type of JTAG commands/queries/(whateveritiscalled) WITHOUT opening the device? (via USB)
7b) Without a JTAG-Box? (already existing software simulating a JTAG-Box) 8) What kind of Information can be gathered by JTAG? f.e.:
8a) Working state of hardware components?
8b) Access to files on flash memory? 9) What kind of modifications/commands can be made/issued by JTAG? (depends on the device/chip attached i assume?)
I know i could just buy a JTAG-Box and learn everything about JTAG to answer some of these questions myself. But i did not find time for learning about something completely new (new for me) yet, and i dont have the money at the moment to just buy a JTAG-Box without knowing how to, and if i will use it (dont even know how much it is...). I will certainly NOT open my 660€ phone, probably breaking the screen and whatever in the process, because of its DONT-OPEN-ME-Design(nice looking, but in some cases inconvenient), and make it a test-dummy for my first JTAGing steps. So it would be nice if someone with some experience in that matter, could give me a brief overview of the possibilities and uses of a JTAG-Box - AND if there is some way to simulate one.
And finally i would like to get into contact with people who might have a clue of the possible causes for this problem, and the ability and willingness to work on a solution. I did find some WIP Unbricking Projects also working on a solution for QHSUSB_DLOAD related issues, but all of them where Model-specific (and mostly for cases where a specific flashed software was the cause) and none for the HTC One (M7)... Although i would like to have a general solution for every device and cause, i doubt there would be any Model-specific Project if it was POSSIBLE at the moment to provide a general one. It would be nice though, if we could at least TRY to make one(some people probably are already trying). But i assume (from what i read) that the existing unbricking projects still need access to the internal storage. So, no access to storage = hardwarefailure & not unbrickable by software?? Even if thats the case and my phone is realy beyond (sofware)repair, i would still like to get answers to my other questions!
If you did read all of this - Congratulations! Have a coffee and a break
I am sorry for:
- noob questions (if there are any left besides the JTAG related - i cant tell anymore)
- annotations and supplements in braces (it can be annoying, i always squeeze in some thoughts somewhere)
- forcing you to read this wall of text, probably full of spelling and grammar errors (i am tired and somewhat tense)
- bad English (not my native language, and... i am tired)
OMG this post is incredibly long. I'll give you a short answer.
Yout phone is hard bricked and MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things.
If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty. You SHOULD sebd your device for repair definitely, I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Sent from my HTCONE using Tapatalk
Very interested in the actual answer, and the reason, subscribed.
Sent from my iPod touch using Tapatalk
elvisypi said:
... MAYBE a JTAG may fix it, BUT the phone needs to be opened, which with this phone is pratically impossible to be done, furthermore you need smb with experience on those things...
Click to expand...
Click to collapse
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
elvisypi said:
...If you weren't soing anything to your phone(s-off, hboot flash, ruu, etc) than probably the motherboard is dead...
Click to expand...
Click to collapse
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
elvisypi said:
...probably the motherboard is dead. I have seen this happen a lot of times with this phone, probably because of not genuine charger/faulty...
Click to expand...
Click to collapse
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
elvisypi said:
...I'm 99.9% sure no one will notice it's HTC dev unlocked, cause it doesn't turn on. A lot of users have sent their and had no problems. Good luck!
Click to expand...
Click to collapse
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
MarvThor said:
Thats why i wont just try it... not on this phone, and not before i know more about JTAG.
Well, the phone is (was) s-off, rooted, and running ARHD 40.3 + TWRP 2.6.3.3 - but i did this long before it died and never had problems during the process, or while using the device.
I mostly used the HTC plug which came with the phone for charging. Although i didnt use the original cable, because it broke shortly after i got it. Sometimes i used a USB-Battery-Pack to charge the phone on-the-go. Could any of this be the Cause?
So, they cant just JTAG it (or do something similar) and it will turn on again? Obviously not if the motherboard is fried... but is it possible that it isnt, and they can? I will send it in nontheless, but i would like to understand what is possible, and find the cause aswell as a solution.
oh and thank you!
Click to expand...
Click to collapse
Hi, just wondering if you had any updates to your story?
I have a HTC One in basically the same situation - it totally died on my wife in the middle of her using it. The battery was at over 50% and we have never even dev unlocked it or flashed ROMs or recovery etc. No lights come on when charging, tried all manner of the power, power+vol key combos etc, tried the bright light as well, nothing gets it to come alive. Plugging into the computer does recognise the HSUSB_DLOAD low level qualcomm device but as yet I havent been able to get drivers to allow it to be recognised. I am taking it to a place on the weekend that says they have JTAG box and may be able to help. I would send it away for warranty replacement but it's my wife's phone and she hadnt backed up the photos on it for a few months and we have a 20 month old son, so we are trying everything possible to retrieve the data off it. Lesson learned, will be putting in place backup regime on our phones from now on!
Will let you know if any joy comes from the JTAG process
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Sorry, i totally forgot about this Thread over all the other things in the last weeks (Starting a Business, moving to a new Place.. etc).
scarecrow420 said:
Hi, just wondering if you had any updates to your story?
Click to expand...
Click to collapse
Yes, i sent it in for repairs, and got it back two weeks later. They had to replace the Mainboard and some other Parts(plus some they broke during Repairs), i could not get any information about the possible causes other than "there are many"... It was covered by the warranty though.
I dont think they could get any data from the Phone.
scarecrow420 said:
Will let you know if any joy comes from the JTAG process
Click to expand...
Click to collapse
I would appreciate that
scarecrow420 said:
Reading your recent comments it is interesting to note that we do have an external power brick (IO Gear 11,000 mAH unit) that we sometimes have charged the phone on. Potentially we even used the 2.1A output from this power brick rather than the 1.0A output on occasion.
Click to expand...
Click to collapse
If the cause is indeed the power brick, i will have to check mine again (measure its output). It is supposed to have 5.0V 1.0A output only, which is the same that the HTC Charger is labeled with.
Well, good luck with your Phone! But if your Phone is as dead as mine, i am afraid you probably wont get those Photos back...
-
Ok, i got my phone back without trouble - but i am still researching (when i have got the time ) the causes and a possible solution for this problem. So, if anyone has any information that could be helpful: please post it here!
Hi guys! Sorry for my bad english but i'm italian. My HTC One gone in QHSUSB_DLOAD mode 3 times (it's not a joke) and i've still it in my hands
This is my configuration now: (today my phone entered in QHSUSB_DLOAD mode)
Firmware = 4.19.401.8 (Darkbootoader)
ROM = SkyDragon v12.0
Kernel = ElementalX 13.0
PVS = 5
Today when tried to turn on the screen with doble tap it do nothing, screen was completly black and same thing when i hold the power button with vol down. After i plug in USB (it was a normal nokia cable) cable and hold power + vol. down for about 20 seconds (there wasn't LED or blinking button, anything) it's boot into bootloader:highfive:
I suppose (because every time my phone bricks when i do too Undervolting) it has "hangry" of energy and it boots up anymore if i don't give him an "help". The same thing when i had the MIUI with the same undervolting
Maybe is too much Undervolting the reason of hard brick, did you undervolt your CPU like me?
Did you find out any answer?
Where you able to bring it back to life?
Did you send it back to HTC for repairs? How did it go?
Would this work?
http://unlimited.io/qhsusbdload.htm
Dredead said:
Would this work?
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
third time.
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Hi, I Have Same Problem Since A Month With My HTC One M7 32GB
I Got this phone as a Gift From USA HTC one M7. My Phone Just got hanged on lockscreen when i try to restart it, it turns off but did not turn on,no single light is turning on, no screen light or notification, no recovery or download mode. its like a brick piece. i tried all charging tricks such as USB PC ,Wall Charger for Hours, Orignal Charger and rest things, i cannot send phone to USA , i am in qatar, what should i do, any guys who experienced such problem and how did they solved it and, what will be the cost if no warranty. any help ? thanks in advance. :crying:
till22 said:
To make a long story short (like you did in the OP), I have to same problem
The cause: flashing newer firmware version. All the symptoms are exactly the same. When I get home from work today I will try these 2 things, they are a little variation of what I already tried:
http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
http://www.androidlegend.com/how-to-use-adb-fastboot-commands-with-your-android-device/
I don't have much hope that I can fix it myself and am already in contact with HTC though. The main problem is that I'm in Argentina and I bought the phone in Germany..
You didn't find any other possible fixes, right?
Click to expand...
Click to collapse
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
mkclarke said:
Hi, how did this go? I just bricked mine doing the same thing... upgrading firmware. I can't get it to respond to any of the suggested methods. What sucks is that the firmware update dialog in fastboot looked good to me. Sucks...
Click to expand...
Click to collapse
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
clsA said:
The link to the fix is on page one
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Cool, thanks! I wonder if a vm running linux would work. All my machines are windows. Not sure how the vm would handle the usb connection. I'll have to see what I can figure out.
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
clsA said:
I just used an ubuntu boot CD when I did it
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Yes! I just thought of that after I posted. I think I still have an ubuntu live CD around here somewhere...
Thanks!
I'll be damned! This worked! I just popped in the latest Ubuntu liveCD and went to town. My phone is now up and charging. Once it's at 100%, I'll try pushing TWRP recovery to it and restoring my last backup.
Thanks again for sending me to that link!
---------- Post added at 10:42 AM ---------- Previous post was at 09:59 AM ----------
Done and done... pushed TWRP and restored my last backup. It's as if it were never bricked! And it also updated my kernel, which is what I was trying to do in the first place.
Just for future reference for anyone coming across this thread, there are two distinct types of bricks being discussed here.
The first results from a borked firmware update. In this case, everything works on the hardware side, it's just that the phone can't boot because the firmware is messed up. This is usually fixable using Dexter's method.
The second, and the problem experienced by the OP, is more serious and is hardware related. I have seen this occur with multiple HTC models. Something related to power management on the motherboard dies so that the phone no longer can no longer get power to start up. When this happens, the phone will typically have shut down without warning despite having a good battery charge. I have never seen or heard of a fix for it beyond returning it for warranty repair.
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Related
No Boot loader
Not charging
No lights
Nothing by pressing vol down and power buttons
Nothing by pressing both vol buttons and reset button
Turned off for hours without battery and pressed power button for long time to drain the battery and turned back on.
Nothing works any more ideas.
But when I connect it to my laptop it does make a notification sound that a new device is connected and is called the qualcomm cdma technologies msm.
If I have bricked it and no solutions and I have warranty should I call HTC or my insurance company?
See..
http://forum.xda-developers.com/showthread.php?p=7444943#post7444943
OK,try this! Remove the Battery-Cover. Look at the Space between the Battery and the Phones Frame on the lower side,on the right of our SIMcard. If you can see two small Pins,remove the battery, and reinsert it carefuly,so that the two Pins are touching the contacts on the Battery...
what happened?
flashing fail? any details please.
DN41
When experiencing any kind of problems its always usefull to post what you was doing before the problem occured. With no other information, there is no way to do any kind of propper trouble shooting.
Its like droping your car at a garage, say it has problems and walk away. Was it that you ran out of gas, did you battery failed or the engine, is it only a lightbulb that doesnt work. A car mechanic wont be able to help you with the car problem cuz he dont know what kind of problem you were experiencing
Try to recharge your phone by default loader (not by pc-USB) for a few hours and try to boot again. Or try entering boot loader while pressing volume down and power on after a few hours of loading.
I agree.
The issue has been posted like a telegram being sent to a grandchild for her nanny's funeral...!!
No one will probe you for your issues. You need to provide as many details as to how you r***ed your HD2..!!
Hi
i have pretty much the same problem. I got this phone on ebay because someone tried to put another rom on it and failed due to an power failure (thunderstorm).
When i connect the phone to the computer via USB, it recognizes a Qualcomm CDMA MSM Driver but cannot install it.
About the phone:
No lights, no bootloader, nothing. It becomes warm while charging so i assume the hardware is not faulty. I guess the bootloader is broken.
Do you have any idea how to save this phone?
i had once a similar issue...
i flashed and failed (not really, cause it works again )..
everything was the same only that i could get access to bootloader (and so my leo booted up).
but when it was powered off and i connected it to my pc, it also recognized a qualcomm device...
badly, that doesnt help you...
i have no plan how to get this work again...if the phone doesnt turn on...
maybe its time for a prayer.
DN41
I just found this thread, and hoping someone has come up with an answer, though I havn't actually searched the threads yet as i just got the phone today, cause someone bricked it trying to unlock it (I assume because his only clue was I might need to flash a different rom). But its the same symptoms, no lights, dosn't show charging, attempts to install a qualcomm CDMA MSM driver when connected to windows pc.
Is there a solution?
Thank you in advance for your replys.
DemonLoader said:
I just found this thread, and hoping someone has come up with an answer, though I havn't actually searched the threads yet as i just got the phone today, cause someone bricked it trying to unlock it (I assume because his only clue was I might need to flash a different rom). But its the same symptoms, no lights, dosn't show charging, attempts to install a qualcomm CDMA MSM driver when connected to windows pc.
Is there a solution?
Thank you in advance for your replys.
Click to expand...
Click to collapse
Nope. You're screwed.
Two nights ago I was watching a video through the YouTube app when suddenly the screen froze up. When it stayed unresponsive for 5 minutes or so, I shut it off by holding the power button down, which seemed to have worked as intended. After that it's become absolutely unresponsive. It will not boot up or turn on whatsoever, nor will the LED light up when plugged into a wall to charge.
The phone was running CM7 and had CWM as recovery, but I'm absolutely stumped as to why it fails to boot up. Has my phone decided to spontaneously brick itself? Is it potentially a hardware fault? Any suggestions would be appreciated. I'll be taking it to a repair center tomorrow, since I've really no choice as of right now.
Yea not really much else you can do besides taking it in for repairs. Maybe remove battery for an hour, although from the sounds of it, it won't do anything.
Nonverbose said:
Yea not really much else you can do besides taking it in for repairs. Maybe remove battery for an hour, although from the sounds of it, it won't do anything.
Click to expand...
Click to collapse
Doesn't seem to work. However an interesting observation, when plugged into the PC, it's detected as QHSUSB_DLOAD. Is it possible my phone's entered some sort of low-level mode? And if that's the case, is there any way to reverse this? I say I held the power button down and it shut off but I may have hit the volume keys in my panic.
So yes, I remain hopeful there's some miracle that will let me get out of this mess.
vr90 said:
Doesn't seem to work. However an interesting observation, when plugged into the PC, it's detected as QHSUSB_DLOAD. Is it possible my phone's entered some sort of low-level mode? And if that's the case, is there any way to reverse this? I say I held the power button down and it shut off but I may have hit the volume keys in my panic.
So yes, I remain hopeful there's some miracle that will let me get out of this mess.
Click to expand...
Click to collapse
This interests me too, I'll be researching all the info I can find, although the first search on qhsusb_dload has come up with a lot of questions and no answers as yet.
Many threads have blamed partitioning the sdcard in cwm recovery as the cause of this.
Did you manage to get any drivers for this qhsusb_dload mode?
Edit: these might be useful. http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19
Progress.
Nonverbose said:
Did you manage to get any drivers for this qhsusb_dload mode?
Click to expand...
Click to collapse
Yeah, I've tried out the QPST software and drivers and believe it or not, an answer to my fears. My phone has entered Download Mode with seemingly no way to exit it. I can't find any posts about this in regards to the Incredible S. I guess nobody's been careless or unlucky enough to get it to this state. See the attached picture. Also I can't help but note all the question about ENTERING download mode as opposed to EXITING download mode. Is it so simple that my brain simply can't comprehend the answer?
unfortunately, its not a simple answer. Probably the best thread concerning this issue is in the sensation forum http://forum.xda-developers.com/showthread.php?t=1468791
Nonverbose said:
unfortunately, its not a simple answer. Probably the best thread concerning this issue is in the sensation forum http://forum.xda-developers.com/showthread.php?t=1468791
Click to expand...
Click to collapse
A dead-end unfortunately. It seems more like a preventative measure than anything. I can't enter diag mode on account of phone being stuck in download mode. I'd like to believe it's hardware related. Anyway, I believe it's time I called the repair centre. I appreciate the help you've given me.
EDIT: Seems like Fonebiz refuses to repair my phone, warranty or no, as it's an overseas model, (even though it's physically the exact same phone, down to the model S710e) short of sending it overseas. Unbelievable. I think I'll go cry in a corner now.
EDIT2: Gave it to a local shop to send for repair. I'll let them figure it out. If anybody has any information on proper use of the Qualcomm Software Download tool, by all means link to me.
Hey all,
I've had an HTC One M7 from ATT for a year and two days. I know it it is that time, because I according to ATT and HTC, it's my problem now because my warranty and insurance expired.
It has been a wonderful phone. I have not rooted it or ran any non-Play Store apps. I have not dropped it or exposed it to water. It was working normally, and sitting at 70%, when it powered down.
Power button and holding it down didn't do anything. No response from being plugged in. I ran through power+up vol, then power+down vol, then power+up vol+down vol (for five minutes). I will let it charge all tonight, but I don't know if that will do anything.
When plugged into my computer, it registers as "Qualcomm HS-USB QDLoader 9008 (COM5)," which from what I read, is the sign of a hardbrick.
I am currently abroad and don't know if I will be able to find a JTAB (from what I gather, that can help). Are there ANY other ideas of how to get this phone running again? It happened so randomly, I can't imagine that the HW would suddenly die; it must be SW.
My only thought is that it doesn't like the HTC European charger, and it Borked the charge data. But HTC Tech Support said as it was OEM, there shouldn't be any problem.
A few important work SMS and the phone number of a date I was in the process of confirming with are on this phone. Please help.
Heartfelt thanks,
vorwarnung
vorwarnung said:
Hey all,
I've had an HTC One M7 from ATT for a year and two days. I know it it is that time, because I according to ATT and HTC, it's my problem now because my warranty and insurance expired.
It has been a wonderful phone. I have not rooted it or ran any non-Play Store apps. I have not dropped it or exposed it to water. It was working normally, and sitting at 70%, when it powered down.
Power button and holding it down didn't do anything. No response from being plugged in. I ran through power+up vol, then power+down vol, then power+up vol+down vol (for five minutes). I will let it charge all tonight, but I don't know if that will do anything.
When plugged into my computer, it registers as "Qualcomm HS-USB QDLoader 9008 (COM5)," which from what I read, is the sign of a hardbrick.
I am currently abroad and don't know if I will be able to find a JTAB (from what I gather, that can help). Are there ANY other ideas of how to get this phone running again? It happened so randomly, I can't imagine that the HW would suddenly die; it must be SW.
My only thought is that it doesn't like the HTC European charger, and it Borked the charge data. But HTC Tech Support said as it was OEM, there shouldn't be any problem.
A few important work SMS and the phone number of a date I was in the process of confirming with are on this phone. Please help.
Heartfelt thanks,
vorwarnung
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2770684
alray said:
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Thank you for the suggestion!
I'm not experienced with tools like this. My device is not-rooted, and I cannot tell if it is powered on or off. Will this tool still work?
vorwarnung said:
Thank you for the suggestion!
I'm not experienced with tools like this. My device is not-rooted, and I cannot tell if it is powered on or off. Will this tool still work?
Click to expand...
Click to collapse
your phone is bricked, this tool is the only known way to recover from qhusb_dload mode, read the guide carefully and follow instructions.
the only other way out of this is to send your phone to htc so the can replace the motherboard.
alray said:
your phone is bricked, this tool is the only known way to recover from qhusb_dload mode, read the guide carefully and follow instructions.
the only other way out of this is to send your phone to htc so the can replace the motherboard.
Click to expand...
Click to collapse
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.
vorwarnung said:
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.
Click to expand...
Click to collapse
It happened to me also after a firmware update ...the link he posted saved my One !!!
vorwarnung said:
This just happens without any signs or warning? I feel like a critical software problem like this would be taken care of in debug. The only change to my phone was an OTA to Sense 6 two weeks ago, but it hasn't had any problems software or otherwise. Sure looks like HTC screwed me over with this one.
Click to expand...
Click to collapse
QHSUSB_DLOAD = Dead phone, either because of hardware defect or because a firmware incompatibility
option 1: follow the guide to revive your phone, if it doesn't work
option 2: send the phone to htc for repair.
option 3: there is no other options!
---------- Post added at 07:36 PM ---------- Previous post was at 07:34 PM ----------
clsA said:
It happened to me also after a firmware update ...the link he posted saved my One !!!
Click to expand...
Click to collapse
this guy (dexter) did an awesome work
clsA said:
It happened to me also after a firmware update ...the link he posted saved my One !!!
Click to expand...
Click to collapse
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!
vorwarnung said:
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!
Click to expand...
Click to collapse
unfortunately, there is no way to transfer data from your phone in qhsusb_dload mode
sorry
vorwarnung said:
I suppose it's wishful thinking to assume that I'll keep any data on the phone, eh? I had to turn off my backup while I'm studying abroad, so I have about two months worth of contacts and photos to lose. Aw, well. Thanks for telling me about your experience!
Click to expand...
Click to collapse
The fix was all in firmware I don't remember loosing anything in the process ...it was like a Miracle happened
clsA said:
The fix was all in firmware I don't remember loosing anything in the process ...it was like a Miracle happened
Click to expand...
Click to collapse
In your experience with this, can you run it in a virtualbox? I can see my device, and it's recognized as it should within Ubuntu and Fedora (both virtual), but the .sh can't seem to locate my phone. Since it is pulling the correct code, I can assume it is not a hardware issue.
I'm sorry if you're not qualified to answer this question, but being new, it won't let me post in Dexter's thread.
Thanks!
vorwarnung said:
In your experience with this, can you run it in a virtualbox? I can see my device, and it's recognized as it should within Ubuntu and Fedora (both virtual), but the .sh can't seem to locate my phone. Since it is pulling the correct code, I can assume it is not a hardware issue.
I'm sorry if you're not qualified to answer this question, but being new, it won't let me post in Dexter's thread.
Thanks!
Click to expand...
Click to collapse
I just used an Ubuntu live CD
Sent from my LG-E970 using Tapatalk
Hello, before proceding to explain the problem I have to say a few things:
- the phone I'm gonna talk about is not mine YET, it's a faulty Xperia T I want to purchase if I find a 80% clear and cheap solution. This means I cannot try any idea you give me on it, 'cause I don't have it.
- I'm not a total noob in firmware and hardware fixes, but not yet an expert, so I'd appreciate a few explanations in the procedures you comment.
- I'm Spanish, so don't expect perfect texts from my posts
- sorry if a thread exactly like this is already solved, but I couldn't find any clear information about this problem on a Xperia device, so that's why I asked.
Now, the problem:
This Xperia T, as the owner explains, suddenly turned off and never woke up again. When he tries to turn it on it just vibrates, but no image displays. And when he plugs it on a red LED shows up (as if the phone was charging normally), but no more life signs.
Now, these are the fixes I would try:
- reset battery, because the owner is a normal user, and, as the battery is a "non-removable" piece, I don't think he tried to pull it off and on again.
- buy a new battery because this one could be damaged and non-functional.
- jtag is discarded because this happened in a stock rom, with no root, custom recovery, flashing or anything like that.
- get a new (or, at least, functional) motherboard, because this could be sudden death.
So now you could say "if you already know which could be the problem and the solution, then why you ask?". Well, what I'm searching for is opinions, what of those problems I mentioned has the highest likelihood to be the winner, because if you all guys think the most likely problem it could be it's the motherboard, then I won't purchase the phone, because motherboards are terrifically expensive.
So thanks in advance for reading all this
laumapu said:
Hello, before proceding to explain the problem I have to say a few things:
- the phone I'm gonna talk about is not mine YET, it's a faulty Xperia T I want to purchase if I find a 80% clear and cheap solution. This means I cannot try any idea you give me on it, 'cause I don't have it.
- I'm not a total noob in firmware and hardware fixes, but not yet an expert, so I'd appreciate a few explanations in the procedures you comment.
- I'm Spanish, so don't expect perfect texts from my posts
- sorry if a thread exactly like this is already solved, but I couldn't find any clear information about this problem on a Xperia device, so that's why I asked.
Now, the problem:
This Xperia T, as the owner explains, suddenly turned off and never woke up again. When he tries to turn it on it just vibrates, but no image displays. And when he plugs it on a red LED shows up (as if the phone was charging normally), but no more life signs.
Now, these are the fixes I would try:
- reset battery, because the owner is a normal user, and, as the battery is a "non-removable" piece, I don't think he tried to pull it off and on again.
- buy a new battery because this one could be damaged and non-functional.
- jtag is discarded because this happened in a stock rom, with no root, custom recovery, flashing or anything like that.
- get a new (or, at least, functional) motherboard, because this could be sudden death.
So now you could say "if you already know which could be the problem and the solution, then why you ask?". Well, what I'm searching for is opinions, what of those problems I mentioned has the highest likelihood to be the winner, because if you all guys think the most likely problem it could be it's the motherboard, then I won't purchase the phone, because motherboards are terrifically expensive.
So thanks in advance for reading all this
Click to expand...
Click to collapse
Does the red LED light stay lit up while charging? Maybe you'd want to google the "rubberband method"; it's for charging the phone when it can't charge on it's own while off.
Antiga Prime said:
Does the red LED light stay lit up while charging? Maybe you'd want to google the "rubberband method"; it's for charging the phone when it can't charge on it's own while off.
Click to expand...
Click to collapse
Yes, the red LED keeps lit up. I've searched for that method and I'll try it if I purchase the phone, thank you so much
But what's your opinion about what the problem could be? Or which is the most likely?
EDIT: this is the thread I found about the rubberband trick http://forum.xda-developers.com/showthread.php?t=1849170, but is it called soft-bricked even when no firmware/modding stuff is involved?
RE-EDIT: ok, yes, even when no firmware/modding stuff is involved (lol)
RE-RE-EDIT: but still, if it's a hardware issue then all those tricks won't work, because there's physical damage, so that's why I asked for opinion x)
In my opinion, that behaviour is 90% due to a battery that is fried.
A broken battery is not able to supply the power needed for loading the kernel (that's why you don't see Sony logo and you can't recharge).
If you're lucky you can repair that phone with 15 euros for a new original battery.
ok guys, new information:
Apparently, the owner has way more knowledge about hardware repairing than I have, so we started talking about our ideas about all this thing and he said he already tried to reset battery, and he even replace it with a new one, so the fried-battery theory is discarded. Now I (we) think the problem could reside in the power IC, but that leads to a weld repairing, and I don't have the tools to deal with that.
So the thread is almost closed with this new info, but I still accept suggestions/opinions/ideas/whatever you wanna say, even if you enjoy typing the Macarena, at least we'll laugh with that xp
laumapu said:
ok guys, new information:
Apparently, the owner has way more knowledge about hardware repairing than I have, so we started talking about our ideas about all this thing and he said he already tried to reset battery, and he even replace it with a new one, so the fried-battery theory is discarded. Now I (we) think the problem could reside in the power IC, but that leads to a weld repairing, and I don't have the tools to deal with that.
So the thread is almost closed with this new info, but I still accept suggestions/opinions/ideas/whatever you wanna say, even if you enjoy typing the Macarena, at least we'll laugh with that xp
Click to expand...
Click to collapse
If I were you, I wouldn't buy that phone.
istux said:
If I were you, I wouldn't buy that phone.
Click to expand...
Click to collapse
Now that I know this, buying that phone has lost positions in my what-to-do list, just after the "comb my turtle's hair" thing lol
Thanks for caring
laumapu said:
Yes, the red LED keeps lit up. I've searched for that method and I'll try it if I purchase the phone, thank you so much
But what's your opinion about what the problem could be? Or which is the most likely?
EDIT: this is the thread I found about the rubberband trick http://forum.xda-developers.com/showthread.php?t=1849170, but is it called soft-bricked even when no firmware/modding stuff is involved?
RE-EDIT: ok, yes, even when no firmware/modding stuff is involved (lol)
RE-RE-EDIT: but still, if it's a hardware issue then all those tricks won't work, because there's physical damage, so that's why I asked for opinion x)
Click to expand...
Click to collapse
What I thought it might be was that the battery wasn't charged. It happened to me once, so I kept the power button pressed while connecting it and after a few hours I was able to use flashtool, and keep in mind that sometimes new batteries don't come charged.
But if that's not the case, then that method won't help you.
Hello!
I met a guy who was willing to sell his M7 for 100€. He doesn't look like someone who is into technology so I believe the problems he said the phone had were due to software issues but I don't want to risk buying it and discovering that the problems are really from the hardware.
I'm not really informed about the phone and it's common problems so I'm counting on you (pls pls) to help me point the problem and help me make myself sure that I'm not going to dive in a bad deal.
The guy couldn't give me detailed info about the status of the phone, the told me "I don't know, sometimes it works, sometimes it does not, I can't check what's wrong". So I asked him if all the ports (usb and jack) were working well, if the speakers were fine, if the camera was taking photos... But I want to be able to ask more specific questions. What should I check before buying?
Also... if it is from software, am I always able to install a recovery and flash a custom rom or flash stock again to fix that?
I'm coming from a Nexus device so I don't really know the hurdles of this one (Nexus has none), I had for some time an LG G2 and it was a pain in the *** to bypass the bootloader lock and a sure risk of bricking the device... How are things with dear M7?
I bricked my phone 5 times, and restore the the ROM using RUU.
If its soft-bricked, you can un-bricked it easily if its M7
What you need to check is hardware, make sure everything is working using soft code *#*#3424#*#*
& check if it have heating issue ? which mostly cause the problems.
Well, I know it has a problem with the camera (pink photos) and something that doesn't let the phone charge when it is on. It detects a cable when there's no cable and shows "unsuported charge" message in the notifications. It charges when the phone is off and usb is detected in a PC without a problem.
I believe a factory reset works for the usb thing but the camera one I believe it's faulty and needs repair. Am I wrong?
diogofd8 said:
Well, I know it has a problem with the camera (pink photos) and something that doesn't let the phone charge when it is on. It detects a cable when there's no cable and shows "unsuported charge" message in the notifications. It charges when the phone is off and usb is detected in a PC without a problem.
I believe a factory reset works for the usb thing but the camera one I believe it's faulty and needs repair. Am I wrong?
Click to expand...
Click to collapse
The Pink/Purple Camera issue is also software problem. I think, if you use other Camera Application, you won't notice any Pink/Purple issue. but Make sure by testing yourself
Its a bit of a rip off I Brought my Faulty HTC One M7 For 53.00 AUD And can repair it for 50 AUD Aswell, Which i have started