Related
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
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.
Hey there.
I have an Xperia ZR that is unable to get into flashmode to reflash and it cant turn on.
Sometimes when plugging it into a charger or computer theres a red led lighting on but it just stays like that no matter how long you leave it. Unable to turn on and cant get it into flashmode. Tried with a rubber band to keep holding volume down while have it plugged in with flashtool ready for an entire day with no result.
Have also had the battery out for an entire night but nothing has worked. Is it just broken completely or is there some way to get it to do something again?
ChrisRoxor said:
Hey there.
I have an Xperia ZR that is unable to get into flashmode to reflash and it cant turn on.
Sometimes when plugging it into a charger or computer theres a red led lighting on but it just stays like that no matter how long you leave it. Unable to turn on and cant get it into flashmode. Tried with a rubber band to keep holding volume down while have it plugged in with flashtool ready for an entire day with no result.
Have also had the battery out for an entire night but nothing has worked. Is it just broken completely or is there some way to get it to do something again?
Click to expand...
Click to collapse
Hmm... Sounds like you tried pretty much everything. How about some background info? How did it get this way? Is the bootloader unlocked? Probably not relevant, but you never know.
My best guess would be that there's a loose contact with the USB connector or something, but that doesn't explain why the display doesn't come on when the red light comes on (are you running a custom ROM?). In any case, by this point, the service center is probably your best bet, if you're under warranty that is; if not, you can try taking it to a 3rd party repair shop (that's how I got my screen replaced after my warranty ran out), or maybe disassemble it yourself to see if there's anything you can jam back into place. Don't know what else you can do.
Good luck.
P.S. What about fastboot?
SirVer said:
Hmm... Sounds like you tried pretty much everything. How about some background info? How did it get this way? Is the bootloader unlocked? Probably not relevant, but you never know.
My best guess would be that there's a loose contact with the USB connector or something, but that doesn't explain why the display doesn't come on when the red light comes on (are you running a custom ROM?). In any case, by this point, the service center is probably your best bet, if you're under warranty that is; if not, you can try taking it to a 3rd party repair shop (that's how I got my screen replaced after my warranty ran out), or maybe disassemble it yourself to see if there's anything you can jam back into place. Don't know what else you can do.
Good luck.
P.S. What about fastboot?
Click to expand...
Click to collapse
I dont really know anything about it, its a friends phone that bought it used. Theres 100% no warrenty on it and if anything needs to be replaced i can do that but its just determining where the issue is.
Fastboot doesnt seem to do anything either. Also the battery does get hot after leaving it in the charger for ages so i dont think there is a lose connection there? But im not sure.
If theres an issue with the screen it should still boot and such.
I thought it might be an issue with the power and volume buttons but then it should still turn on when charging id assume, or partially turn on, until the battery charging screen at least.
Wait i just tried to plug it in again.
Now flashtool gives me this
07/022/2015 13:22:00 - INFO - Device connected with USB debugging off
07/022/2015 13:22:00 - INFO - For 2011 devices line, be sure you are not in MTP mode
however if i unplug it and replug it it doesnt detect it before i pull out the battery and put it in again. Holding either volume up or down doesnt do anything still, gives same message and doesnt go into fastboot or flashmode
ChrisRoxor said:
Wait i just tried to plug it in again.
Now flashtool gives me this
07/022/2015 13:22:00 - INFO - Device connected with USB debugging off
07/022/2015 13:22:00 - INFO - For 2011 devices line, be sure you are not in MTP mode
however if i unplug it and replug it it doesnt detect it before i pull out the battery and put it in again. Holding either volume up or down doesnt do anything still, gives same message and doesnt go into fastboot or flashmode
Click to expand...
Click to collapse
That's... Interesting. And Flashtool just stays like that until you unplug it? It doesn't lose the connection (device disconnected) or anything like that? If it does lose it, it could be a battery issue...
SirVer said:
That's... Interesting. And Flashtool just stays like that until you unplug it? It doesn't lose the connection (device disconnected) or anything like that? If it does lose it, it could be a battery issue...
Click to expand...
Click to collapse
Yea still staying like that, doesnt say it disconnects before i unplug it, and then it wont connect again before the battery has been out
ChrisRoxor said:
Yea still staying like that, doesnt say it disconnects before i unplug it, and then it wont connect again before the battery has been out
Click to expand...
Click to collapse
... OK, I don't know what kind of black magic was used on that phone to screw it up like this, but it sounds like something's off in the battery circuit (just guessing). I'm not sure that's even fixable, but it couldn't hurt to try a mobile repair shop. Who sold you something this broken, anyway? eBay?
SirVer said:
... OK, I don't know what kind of black magic was used on that phone to screw it up like this, but it sounds like something's off in the battery circuit (just guessing). I'm not sure that's even fixable, but it couldn't hurt to try a mobile repair shop. Who sold you something this broken, anyway? eBay?
Click to expand...
Click to collapse
i dont know who they bought it from but yea seems like something with either the usb connector circuit and maybe buttons. The battery voltage is okay. Reading 3.5V and specified 3.7V on the battery so that should be eliminated as a problem
ChrisRoxor said:
i dont know who they bought it from but yea seems like something with either the usb connector circuit and maybe buttons. The battery voltage is okay. Reading 3.5V and specified 3.7V on the battery so that should be eliminated as a problem
Click to expand...
Click to collapse
Nah, I didn't mean the battery itself, I meant (as you said) the connector circuit between the port, the battery, and the motherboard. You can try opening it up, see if there's anything you can do, but apart from a repair shop, I don't see what else can be done to save it. Maybe someone else will have some ideas.
Good luck. ?
SirVer said:
Nah, I didn't mean the battery itself, I meant (as you said) the connector circuit between the port, the battery, and the motherboard. You can try opening it up, see if there's anything you can do, but apart from a repair shop, I don't see what else can be done to save it. Maybe someone else will have some ideas.
Good luck.
Click to expand...
Click to collapse
Yea okay, thanks! I'll try disassemble it when i get the time to see if there are any loose connections and test the cables and such.
Take out the battery and try putting it on Flashmode.
(Heard this somewhere for some other phone or might be for Xperia)
Sent from my Xperia ZR using XDA Free mobile app
Daedroza said:
Take out the battery and try putting it on Flashmode.
(Heard this somewhere for some other phone or might be for Xperia)
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
flashmode without battery in? Ill give it a shot
ChrisRoxor said:
flashmode without battery in? Ill give it a shot
Click to expand...
Click to collapse
Nothing happened
Any other suggestions maybe? Hopefully?
Upon further investigation, it appears that some of the back screws and the plasic in the edges behind the rear cover, is damaged. It appears as though someone has opened the phone previously and been unable to make it function again afterwards and then sold it online to get rid of it.
So ill open it up and check the insides of it, then give an update if there are more issues!
ChrisRoxor said:
Upon further investigation, it appears that some of the back screws and the plasic in the edges behind the rear cover, is damaged. It appears as though someone has opened the phone previously and been unable to make it function again afterwards and then sold it online to get rid of it.
So ill open it up and check the insides of it, then give an update if there are more issues!
Click to expand...
Click to collapse
This is exactly why it took me so long to trust online shopping. ?
Download sony pc companion.
start support zone.
chose first option update software.
A dialog will open.
chose repair the phone at the bottom and follow the guide. it should repair your phone to stock settings.
everything will be deleted on your phone
i was about to open a thread when i came across this one, i have similar issue with my ZR, i had bought it brand new, but after few weeks of lollipop update, one day the phone just started rebooting randomly, and after few hours it didnt boot back up, it just went dead. and same issues, when i plug in red light comes on, but only for few secs, and no help using PC companion or flashtool. i took it to repair shop they said theyll charge me for just checking what the problem is, i said no thanks. ill take it to repair shop n see what they say.
My phone decided to not switch on any longer. The only sign of life is the notification led blinking red when is in charge, no way to access it with any program if I attach it to the PC with a USB cable.
I should send it to the Sony repairing center (still under warranty) but the phone is rooted; given its situation do they discover it ?
I had that exact problem. Turned out that the battery suddenly died after about a year.
In my experience they never care what stuff is currently on the phone. Instead they'll just flash it with the latest stock rom after fixing the hardware.
Thanks a lot for sharing your experience. I really hope will be the same in my case as well. I'll post here what will happen.
PS I'm wondering about the batteries' quality: my daughter with a z1c had your same problem (a little more than one year life), you, may be myself... I know the sample is not significant but...
Same thing happened with mine & i was on a custom rom with unlocked bootloader...they probably had no way to get into the phone just like i couldn't so they probably couldn't tell it was modified...it was just a brick at that point...i noticed certain batches were affected by this sudden death and after pulling my tag out i noticed my phone was part of that batch that was poorly assembled in china...so brand new phone for me!
Fictional Reality said:
Same thing happened with mine & i was on a custom rom with unlocked bootloader...they probably had no way to get into the phone just like i couldn't so they probably couldn't tell it was modified...it was just a brick at that point...i noticed certain batches were affected by this sudden death and after pulling my tag out i noticed my phone was part of that batch that was poorly assembled in china...so brand new phone for me!
Click to expand...
Click to collapse
OK, another positive experience. I cross my fingers and I'll post what will happen to me
I have the impression they dont even check the software, they just flash a new fw and thats it. Or they dont care.
My phone locked up on me like this, but I solved it by pushing a pin into the reset button hole.
Geoff2 said:
My phone locked up on me like this, but I solved it by pushing a pin into the reset button hole.
Click to expand...
Click to collapse
Thanks for the suggestion but I tried any possible way to resurrect my phone, including what you're saying, without any result. I hope to confirm soon what all the contributors to this thread are saying...
Just received the device from assistance; everything went well: the motherboard was replaced.
The only drawback is that the lost the tiny grill that cover the mic at the bottom of the phone !!!!!
After I took this Samsung Galaxy Ace Duos(SCH-i589) and refreshed the GT-S5830 ROM with Odin, it became a hard brick (I did this because I installed AIDA64 Android Edition and it said gt-s5830 under "Hardware", which turned out to be purely misleading, I thought it would refresh successfully) now the phone has no reaction, no Recovery, no download mode, nothing, complete hard brick, no reaction, what should I do? : (
DavidLiang1129 said:
After I took this Samsung Galaxy Ace Duos(SCH-i589) and refreshed the GT-S5830 ROM with Odin, it became a hard brick (I did this because I installed AIDA64 Android Edition and it said gt-s5830 under "Hardware", which turned out to be purely misleading, I thought it would refresh successfully) now the phone has no reaction, no Recovery, no download mode, nothing, complete hard brick, no reaction, what should I do? : (
Click to expand...
Click to collapse
If the device is completely unresponsive, there is nothing you can do as an end user to fix it.
You're going to have to have it repaired or replaced.
V0latyle said:
If the device is completely unresponsive, there is nothing you can do as an end user to fix it.
You're going to have to have it repaired or replaced.
Click to expand...
Click to collapse
Thank you for your reply! It's not completely unresponsive, after I press the download mode shortcut for a few seconds, the screen flickers a little and then goes out, nothing happens, as if it wanted to enter download mode but failed
V0latyle said:
If the device is completely unresponsive, there is nothing you can do as an end user to fix it.
You're going to have to have it repaired or replaced.
Click to expand...
Click to collapse
In addition I had to remove the battery and then connect the computer without the battery before this could be triggered
In addition, I tried this method, but I don't know how long to press these buttons, I keep pressing them, but the screen just keeps flashing and nothing happens
V0latyle said:
If the device is completely unresponsive, there is nothing you can do as an end user to fix it.
You're going to have to have it repaired or replaced.
Click to expand...
Click to collapse
my friend who has a Samsung Galaxy Ace 3(GT-S7278U) also went through a hard brick like this, he told me to charge the phone, after about 24 hours, the phone will automatically go into download mode, I haven't tried it yet, I've never heard of this method (picture is my friend's phone)
V0latyle said:
If the device is completely unresponsive, there is nothing you can do as an end user to fix it.
You're going to have to have it repaired or replaced.
Click to expand...
Click to collapse
I bought a USB JIG from an online shopping platform because I checked the forums and the vast majority of people said that USB JIG would help, but the merchant said "this product will not help hard bricks" which confused me a little, I wanted to know the exact answer? If you or someone else can answer it, I would appreciate it! (Also, luckily, I didn't refresh the partition table. A friend of mine said that if I did, the phone would be dead.)
DavidLiang1129 said:
I bought a USB JIG from an online shopping platform because I checked the forums and the vast majority of people said that USB JIG would help, but the merchant said "this product will not help hard bricks" which confused me a little, I wanted to know the exact answer? If you or someone else can answer it, I would appreciate it! (Also, luckily, I didn't refresh the partition table. A friend of mine said that if I did, the phone would be dead.)
Click to expand...
Click to collapse
The only jig I could think of would be JTAG, and while I imagine the board does have a JTAG header, Qualcomm (and Samsung) provides a means to perform low level flashes using specialized tools such as QPST. However the tools and the files necessary are not publicly available and there is zero end user support. Most repair centers won't reflash your phone; they'll just replace the main board and program it with your IMEI.
V0latyle said:
The only jig I could think of would be JTAG, and while I imagine the board does have a JTAG header, Qualcomm (and Samsung) provides a means to perform low level flashes using specialized tools such as QPST. However the tools and the files necessary are not publicly available and there is zero end user support. Most repair centers won't reflash your phone; they'll just replace the main board and program it with your IMEI.
Click to expand...
Click to collapse
Thank you for your reply. As far as I know, USB JIG comes in two varieties, one is forced to boot the device into download mode via a MicroUSB plug with 4 resistors, and the other is what you call JTAG, and I bought the former
V0latyle said:
The only jig I could think of would be JTAG, and while I imagine the board does have a JTAG header, Qualcomm (and Samsung) provides a means to perform low level flashes using specialized tools such as QPST. However the tools and the files necessary are not publicly available and there is zero end user support. Most repair centers won't reflash your phone; they'll just replace the main board and program it with your IMEI.
Click to expand...
Click to collapse
USB JIG arrived today, but it didn't work... I removed the battery two seconds later, put it back on the phone, and plugged in the USB JIG, but nothing happened, I even waited five minutes, was I using it wrong? I even paid about 10 CNY(about $1.50) for it, including a 2 CNY USB JIG and 8 CNY shipping... If it's just a dust plug, it's not a good deal...) I need help. Thank you so much!
Good news, guys! Instead of using the USB JIG, I switched to a USB cable that was just on the charger of one of my old phones. I connected my battery-free Galaxy to my computer, pressed volume up + Volume Down + Power, and something magical happened: my computer made the sound of new hardware discovery! The screen lights up and displays the Samsung Logo, but it goes black after a few seconds. (I think the USB cable doesn't connect reliably, but only it works.)
DavidLiang1129 said:
Good news, guys! Instead of using the USB JIG, I switched to a USB cable that was just on the charger of one of my old phones. I connected my battery-free Galaxy to my computer, pressed volume up + Volume Down + Power, and something magical happened: my computer made the sound of new hardware discovery! The screen lights up and displays the Samsung Logo, but it goes black after a few seconds. (I think the USB cable doesn't connect reliably, but only it works.)
Click to expand...
Click to collapse
Check Device Manager and see if it displays an unknown device
V0latyle said:
Check Device Manager and see if it displays an unknown device
Click to expand...
Click to collapse
Thanks for your reply, on my first attempt, I didn't look for an unknown device, Windows just said "failed to install device driver" and I never succeeded again... The screen was just black, but when I plugged the phone into the computer using the USB cable, Windows said there was an unrecognized USB device. I tried several USB cables, but only that made the computer respond
V0latyle said:
The only jig I could think of would be JTAG, and while I imagine the board does have a JTAG header, Qualcomm (and Samsung) provides a means to perform low level flashes using specialized tools such as QPST. However the tools and the files necessary are not publicly available and there is zero end user support. Most repair centers won't reflash your phone; they'll just replace the main board and program it with your IMEI.
Click to expand...
Click to collapse
By the way, this phone uses Qualcomm SOC. Can I remove it and short some contacts to enter 9008 mode?
DavidLiang1129 said:
By the way, this phone uses Qualcomm SOC. Can I remove it and short some contacts to enter 9008 mode?
Click to expand...
Click to collapse
Not that I know of
V0latyle said:
Not that I know of
Click to expand...
Click to collapse
Ok, so it doesn't seem like there's any other software-based way to recover it, thanks for all your help, but I'm still looking forward to what software-based way to recover it
DavidLiang1129 said:
Ok, so it doesn't seem like there's any other software-based way to recover it, thanks for all your help, but I'm still looking forward to what software-based way to recover it
Click to expand...
Click to collapse
You can try these if you haven't already. Sometimes 3's a charm... This article indicates there are hard points present, I can't verify that as you're deeper than I ever care to go. If that option is viable you better make sure you get it right as it bypasses all built in safeguards and as I understand it could completely brick the phone for good. Might want pay a expert with lots of experience try to recover it... or learn as you go.
blackhawk said:
You can try these if you haven't already. Sometimes 3's a charm... This article indicates there are hard points present, I can't verify that as you're deeper than I ever care to go. If that option is viable you better make sure you get it right as it bypasses all built in safeguards and as I understand it could completely brick the phone for good. Might want pay a expert with lots of experience try to recover it... or learn as you go.
Click to expand...
Click to collapse
Thank you!! When I followed Method 3, the phone screen flashed and Windows told me it had found an unrecognized USB device! I feel like I'm getting there!!
blackhawk said:
You can try these if you haven't already. Sometimes 3's a charm... This article indicates there are hard points present, I can't verify that as you're deeper than I ever care to go. If that option is viable you better make sure you get it right as it bypasses all built in safeguards and as I understand it could completely brick the phone for good. Might want pay a expert with lots of experience try to recover it... or learn as you go.
Click to expand...
Click to collapse
What do I do next? Do I need any hardware drivers?
DavidLiang1129 said:
What do I do next? Do I need any hardware drivers?
Click to expand...
Click to collapse
I haven't a clue but for Windows you need the right USB drivers. You can try the find the right driver option as well as checking Event Viewer for error messages, etc. Or more Google searches...
I purposely avoided playing with the firmware on Androids including upgrades/updates. That works well for me.