Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
dadrumajor said:
Thanks in advance for any help...
Recently my phone bricked, out of the blue. I rooted it and flashed the most recent release of TWRP (I don't remember the utility I used) and tried (and failed) to gain S-OFF with lazypanda and moonshine. After flashing the stable CM10 release and realizing the touch screen did not work, I found a ParanoidAndroid release that I wanted to try (http://forum.xda-developers.com/showthread.php?t=2373565). I flashed it from recovery and it worked great for around a week, then one morning it just bricked. Before that, I had rebooted it many times each into recovery and bootloader and did a couple full reboots. I had also fully powered down and back up a couple of times as well. However, that morning I powered down the phone and it has not powered up since. I began the power down on the AC charger, and removed the charger a few seconds after the screen went black; the buttons were still lit up. It does not respond to any button combination other than having a PC recognize it as a QHSUSB_DLOAD device. I have tried the LazyPanda unbrick method, PblClear, and (against all hope) an RUU, none successful. At this point, I am forced to concede that I must take my phone to Sprint and have it replaced under TEP...unless someone has a solution?
Again, quick details - brick occurred after a week of full and non-buggy operation. Not the result of a botched S-OFF attempt as far as I know, though I did try to gain S-OFF with 2 different utilities, failing both times. Removed power cord (AC Charger) while powering down; LED does not light up, will not respond to any button combination. Mounts as QHSUSB_DLOAD device.
Thanks again for taking your precious time to help me! :laugh:
Click to expand...
Click to collapse
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
FinZ28 said:
PM XDA member Zarboz regarding JTAG, which may be just what you need to resurrect your phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks! What exactly would a JTAG do? I did some research but couldn't find a good answer. Is there an advantage to that over just bringing it to Sprint to replace it, or do you think they might not take it?
EDIT: I went through my research again; I guess I just didn't understand it the first time. So, a JTAG can access and write to any memory on the phone, especially the memory that is now unavailable due to messing up the low-level boot software?
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
iconoclastnet said:
I've run into a similar situation on a completely different phone. I have a nexus 4 on AT&T that's been running ParanoidAndroid without problems for many months (most recent update flashed about 3 day earlier) that just wouldn't turn on one morning. The only indication it's alive at all is that it shows up as QHSUB_DLOAD / QDL mode when connected to the computer, and if I hold down the power button long enough to force it to restart the indicator light will briefly turn red for about a second. Your post caught my attention because almost no one else runs into this situation other than when they're flashing something wrong to the phone. Perhaps there's a bug in ParanoidAndroid that's responsible? (It's the only common element I see so far.)
Anyway, most every unbrick tool I can find expects you at least can access the storage to rewrite bootloaders, etc. The only thing I've found so far that will talk to the Qualcom chip in this mode is a perl script that still doesn't manage to get me out of this mode and to a state where the other tools can take over. JTAG may be my last resort. If you're considering a JTAG service, you should be aware that it involves taking apart the phone and in some cases soldering temporary leads to the circuit board. If you have any warranty style replacement options, you'll likely have to choose between those or the JTAG route.
Click to expand...
Click to collapse
Just an update - I went to Sprint, and they agreed to replace the phone...waiting on it at the time of writing, but I will be starting from scratch. I plan to unlock the bootloader and root but not try for S-OFF as TWRP does have a way around it...and I WILL be staying away from ParanoidAndroid, although I love their ROM. Too bad...I just don't want another paperweight on my hands!
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
dadrumajor said:
-EDIT- iconoclastnet: do you remember what circumstance the phone was in when it bricked? Like, on the charger, off the charger, turning on or off as it was plugged in/unplugged? Because I was unplugging mine just as it was powering down (not a reboot) and that's when it would not turn back on.
Click to expand...
Click to collapse
Sorry for the delayed response, I was out of town for a couple of weeks and didn't notice your reply until now. Anyway, just for the record...
The notification led was indicating that the battery was about to run out (yes, I set a custom notification color for very low battery). It appeared to finally give up and shut off just moments before I reached the charger. So, I plugged it in and let it charge over night like usual, except the next morning it wouldn't turn on or respond to anything. At first I thought that the battery might not have charged for some reason, so I switched to a wireless charger because it has a charging/full indicator led on the charger itself, and confirmed a fully charged battery. Plugging it into the computer revealed the QHSUB_DLOAD / QDL mode status. I still haven't been able to get it out of that mode. At this point I'm really more interested in recovering the data from it than whether or not the hardware works normally anymore.
As for Paranoid Android, I've been using it successfully on a couple of other devices (both before and since the brick incident) and haven't had any problems with it, so it may be a complete coincidence. I'm at a loss for a good explanation though.
The issue was with TRIM not being removed from some early 4.3 ROM builds, which caused the bricks. It was discussed in some of the ROM threads. Had nothing to do with whether a phone was S-on or S-off.
Sent from my HTC EVO 4G LTE
Related
So, I'm running Ognimnella's 3D Anorexia using Mac kernel, no tweaks, no overclock other than what the kernel is set as for stock, 1.56Ghz I believe. I checked; No water damage either. Last night I remapped my search key to recent apps, and this morning was looking for a way to re-implement the search key function somewhere else. So, I was looking for a way to remap the long press to no avail. Eventually i started looking around in the sys/usr files for something referencing the long press home button to bring up APP_SWITCH so i could remap that to SEARCH and didn't really find anything. However I found a file, I can't remember the name, I don't even know if it's relevant, where the camera button functions were located. I attempted to remap the "FOCUS" key to SEARCH and saved the text, and rebooted to apply changes, (possibly, I didn't even know if it was going to work).
However after leaving it sit for around 2-3 minutes while otherwise occupied, I came back expecting to find it booted up however it was still off. I attempted to turn the phone on, no cigar. Plugged it into my charger. No red light. Nothing. Tried to boot into bootloader. No beans. Tried to use ADB to "adb reboot-bootloader" and it says "no device found." And when I plug it into my computer a strange 3-beep comes through, kinda like when you normally connect a usb, but 3 fast beeps instead of two. I also downloaded the [UNBRICK] file from the sticky and Unknownforces all in one tool and tried em both out in Ubuntu. Neither one of their tools detects my phone after plugging it in. I've tried battery pulls, leaving the battery out for 20 minutes, leaving it on the charger for a half hour, trying to boot without the SD in, and even trying to press camera and volume.
Basically, am i SOL? Did I hard brick my phone, even though I wasn't even flashing anything? And finally, is there anything I could do?
did u use a cdma on gsm as far as the unbricking and do u have cdma or gsm? also were u using the room for a while or just flashed? what radios and hboot ?
Well, I'm CDMA and was hboot 1.5 juopunut S-OFF, had been for going on 3 months, and had flashed it about a day ago and everything was going fine. As to Radios, I couldn't tell you, I've never messed with that.
FennrarrXDA said:
Well, I'm CDMA and was hboot 1.5 juopunut S-OFF, had been for going on 3 months, and had flashed it about a day ago and everything was going fine. As to Radios, I couldn't tell you, I've never messed with that.
Click to expand...
Click to collapse
another possibility, are you using cwm 4.0.1.4 revolutionary or 4ext recovery? Those are the only 2 recoveries that support charging the phone while it is off.
If you can jump start your battery a little with a 9v and paperclip, might help you boot up to recovery. That or borrow a sensation owners battery to test.
How would i go about doing that?
By the way, I am using TWRP 2.2 and was at 97% when I restarted my phone, and it was early morning and I had just pulled it off the charger ~10 minutes before. Could it have been a bad charge?
FennrarrXDA said:
How would i go about doing that?
By the way, I am using TWRP 2.2 and was at 97% when I restarted my phone, and it was early morning and I had just pulled it off the charger ~10 minutes before. Could it have been a bad charge?
Click to expand...
Click to collapse
oh, twrp should support off mode charge as well, soo hmmm.
The reset combo when phone freezes to just restart, not erase is volume up+down and power held together for 10 or so seconds.
Someone also said to hold camera button when plugging in, then try powering on.
No dice on either method. I'm pretty sure I'm sol, and am going to have to buy a cheapo phone off of eBay if I can't convince a Sprint rep to replace it. But I don't know. Thanks though! I aappreciate it.
Hey,
I have the same issue.
I have another HTC Evo 3d and can verify the battery is fully charged.
However when I put in my other Evo 3d it wont turn on.
Plugging in the cable to a charger does nothing and no LED ever comes on.
However my charger turns different colors when charging and the led turns from green to yellow when i plug the broken evo 3d in so something (current being drawn) is happening but the EVO and the LED just won't turn on. I unlocked the bootloader but the phone is still on Sprint Stock Rom.
a
getting to 10 posts
Fried motherbooard. Happened to me
My phone wouldn't power on so I got it repaired at a phone repairs shop. The guy there thought there was a software error because he saw the error triangle on bootup. He was mucking around with it in download mode when I got there, I said not to worry about it, paid for the repairs and left.
The phone will not boot, and will not go into recovery or download modes with the respective key combinations
UNLESS
I have it plugged into a power source, in which case I can enter download/recovery mode, but when I try to boot the phone I just get the empty battery picture with the loading circle appearing periodically.
--- Possible solution: bad battery
I have flashed CWM onto the phone using odin in download mode and have flashed .zip roms that were previously working before this debacle, but again the phone won't boot onto the newly installed rom.
I have tried flashing the correct stock rom using odin but the phone won't boot this way either.
When I take the battery out and connect the phone to a power source it is non-responsive.
Apart from a batter problem (which I will be able to test tomorrow), what could be the cause of this problem, and how might I be able to fix it?
Sounds like a JTAG (but don't get your hopes up) or a motherboard replacement job (more likely) to me. If the phone won't boot at all/shows no signs of life, something is majorly wrong. As to what that is, nobody here could tell you that with certainty because we don't have the phone in front of us, but if it's not booting at all either the NAND is buggered or something else on the MB has crapped itself.
Cross your fingers it's just a simple battery issue, but it doesn't sound like it.
MistahBungle said:
If the phone won't boot at all/shows no signs of life
Click to expand...
Click to collapse
What does being able to access recovery mode/download mode contribute to this? The phone works to a degree, it seems, it just won't boot to an OS.
How might I go about troubleshooting the hardware?
(Might as well use this as a learning experience)
Right. Sorry. Just re-read your OP. Still sounds like the NAND is stuffed, which explains why you've tried flashing flashing stock/CWM & phone still won't boot normally. One thing you could try is search for Hopper8's 'Odin troubleshooting' thread, and flash the 3 part firmware linked in that thread. If the phone still won't boot normally after that, it's pretty much a certainty that you'll need to replace the MB at least, which leads to the next paragraph...
Also, if you find the 'booting when plugged into charger but not with battery' thing is still happening even with a new battery, that suggests whatever circuitry is responsible for taking zzz's from the battery & powering the device is (also) faulty/damaged. You could also try the obvious & clean the battery contacts with some isopropyl alcohol. The most common charging/power type problems we see here is the USB board/port dying. But if the phone is slightly functional whilst on charger, it probably isn't that, still might be worth replacing though given how quick/cheap/easy it is to do. There could be a short/whatever causing at least some of the problems, and it wouldn't be the first time a faulty USB board has caused that/manifested itself in less obvious ways than what we normally see (I.E causing the problems you're seeing rather than causing intermittent charging problems or phone rebooting randomly on its own or whatever).
In that case, try the service manuals for the device; these have been posted here before & can also be found with a Google search. They have detailed schematics/parts lists/walk throughs of the most common repairs w/pics, and might help if you want to have a go at fixing it yourself.
Thanks for the response.
I'm in the process of downloading the three part firmware to test later in the night.
Providing that fails, I'll look into part supplies and start researching how I can, if at all, repair this myself.
On the topic of faulty USB boards- I had my phone serviced a few months ago for just that, and it worked fine, but in the weeks leading up to this event my phone HAD been rebooting itself semi-regularly, although I put this down to a software issue rather than a hardware issue. I'll get my hands on the service manual for the I9100 and start reading up.
In the meantime I can just get a cheap burner Nokia that won't play up on me for the next 20 years.
Interesting. In that case, given the other alternatives are more expensive (assuming the 3 part firmware & new battery doesn't fix things), it may just be a case of another dodgy USB board & you might want to start there.
If you can't find the manuals anywhere, let me know & I'll see if I can dig them up from an external drive I have stashed away somewhere (don't have it handy now, but will dig it up tomorrow for you if necessary).
Yep, unlike current technology, old phones like that just seem to work no matter what you throw at them
The three part firmware flashing has moved things along slightly- after it finished the stock SGS2 boot screen appeared for a second or so and while leaving it on the charger it will cycle between showing the grey loading battery and an android with a loading bar underneath, which is progress from before. It is still unresponsive when disconnected from the power- I have procured the service manual and will look into disassembly/diagnostics when I have some small enough tools. I'll still try using a different battery when I can, but it probably isn't the issue.
Clean the battery contacts hard with a pin
Sent from my GT-I9100 using xda premium
hello guyz
Sorry for my bad english .
I''m here cuz my htc one max was out of charge ,
and when i plugged it to charge it won't charge ,
i tried to open it and same
#i tried to open it with recovery mode and smae
#led light not working too
#i tried different chargers with different outlits .
what to do plz ?
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Jiggity Janx said:
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Click to expand...
Click to collapse
i didn't work , same
Same here, vzw Htc One max no charge, no power....
One foggy hungover little extra bad on me. Was firewater s-off with temporary root, twrp 2
6.3 recovery flashed fine but never had SU commands only SH. In a hungover haze I noticed twrp had 2.7 open recovery out and without due thought I downloaded it to update the recovery. I blatantly force flashed the zip from my phone using CWMR. foolish of me straight out, no excuses. Phone rebooted twrp recovery flashed 2.7 zip and then power dropped immediately. Will not power up/charge.
I got the USB/DLOAD message. Been reading every since to self fix . Would appreciate advice on proper path to take. I've been reading on one hand since it was S-Off it possibly blew the LCD and no bueno brick city. Yet I've also seen success with flashing the RUU as a possible. Other option I found so far was run the JTAG method with Ubuntu and/or try shorting the 2/5 pins with 300k resister.
I'm not concerned about warranty, I would really appreciate anyone who has the time to respond and experience with this indescretion. I would prefer not to damage it further with incorrect fixes if possible. I believe i just jacked my boot image and need to use the RUU method unless the LCD was blown from over clocked over voting .
Direction on the correct method if any is appreciated. I'm completely open to answer questions i may not have addressed. Totally thoughtless and my fault yet I'm very clear on what I did to cause it. Many years electronics repair, still medicore Linnux skills so please go easy on me there. I just need the correct path if known. Im a big boy and fully capable of learning it on my own so no need for you to feel you have to list script and hold my hand.... but a good ass chewing is never out of line ") Thanks for any experience you wish to share.
someone help please ?
Phones dead, no led, no charging, no button combo brings it back. Everything worked great, plugged it in Friday night like always, wake up Saturday to find it was off while on the charger. The cable and charger that it came with, and girlfriends DNA charges on it no problem. Took it to Verizon and they tried a few things, nothing they did helped, like I was surprised. So they are sending me one, but I want to know what happened and how to fix it. This seems to be a common problem, but it seems most people at least get it to power back on at one point.
Exactly what was happen to me some time ago.The only solution i found is to open case and charge the battery about 10 seconds.I advise you to use usb port of your computer to charge it. Btw if you let it drain to zero you will have to do this procedure again
This morning I got in my car and plugged my phone in, turned on Waze and drove to work which everything was fine. I started to do some testing on my phone at work which was killing the battery so I plugged it in, but the light did not appear for charging. I tried plugging it into two different computers, wall outlet, and different cords. I tried a co-workers phone on my cord and his started charging with no problems both connected to the PC and wall outlet. I cleaned the USB port on the phone thinking their maybe some dirt and build up in there, but still no love. Tried simulating a battery pull, flashing a ROM, and doing a restore...again no love. So I am guessing either the battery or the port is bad, even though the cable clips into place and is not loose.
My question I guess is: I have insurance on the phone, but do I need to RUU the phone in order to get the work done or will Sprint not care? I don't want to RUU and not be able to unlock and root again, but at the same time....I need a working phone. Also, if I missed something in my troubleshooting that someone has had success with for the same issue, please let me know.
Here is an early Thank You for those that may have suggestions or advice.
bdiddled said:
This morning I got in my car and plugged my phone in, turned on Waze and drove to work which everything was fine. I started to do some testing on my phone at work which was killing the battery so I plugged it in, but the light did not appear for charging. I tried plugging it into two different computers, wall outlet, and different cords. I tried a co-workers phone on my cord and his started charging with no problems both connected to the PC and wall outlet. I cleaned the USB port on the phone thinking their maybe some dirt and build up in there, but still no love. Tried simulating a battery pull, flashing a ROM, and doing a restore...again no love. So I am guessing either the battery or the port is bad, even though the cable clips into place and is not loose.
My question I guess is: I have insurance on the phone, but do I need to RUU the phone in order to get the work done or will Sprint not care? I don't want to RUU and not be able to unlock and root again, but at the same time....I need a working phone. Also, if I missed something in my troubleshooting that someone has had success with for the same issue, please let me know.
Here is an early Thank You for those that may have suggestions or advice.
Click to expand...
Click to collapse
Hey bud. First thing I would do is flash the latest stable TWRP for the phone. Then boot to recovery and see if it will charge.
If not, try flashing a stock kernel and see if that fixes the issue.
If it still has problems, I would be willing to bet it is hardware related be it the board, port, or battery.
If you are S=OFF, you will be able to root and unlock just fine. I don't know the carriers policies, but it's always safe to be RUU if you intend to do a Insurance claim. Make sure all your internal memory is backed up prior to flashing a RUU.
I found out the usb port on the phone is bad, but if I plug it in halfway the phone will charge. Thanks for the response and suggestion neo.
bdiddled said:
I found out the usb port on the phone is bad, but if I plug it in halfway the phone will charge. Thanks for the response and suggestion neo.
Click to expand...
Click to collapse
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
tlarm said:
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
Click to expand...
Click to collapse
I have not heard of this one before. I will give this a try, see what happens and report back. Thanks.
tlarm said:
I've had that problem a few times too. Followed these instructions (found somewhere else) and it's corrected it every time:
1. Power phone off
2. Put on charger for at least ten minutes (does not appear to be charging, but that was the instruction)
3. Hold both the volume up and power buttons at the same time for at least two minutes (phone goes into kind of a boot loop)
4. Release both and phone reboots and charging works again
For me it fixed the "messing with the USB plug"
At least worth a try.
Click to expand...
Click to collapse
Unfortunately this did not work for me, but thanks for the suggestion.
bdiddled said:
Unfortunately this did not work for me, but thanks for the suggestion.
Click to expand...
Click to collapse
Sorry that didn't work. I always hate giving up, especially when it's usually a mess I've caused. Hahaha but anyway, if things are straightening out when I have issues, I go back and flash the stock android rom, I'm on Verizon and use the deodexed one in another post on here. Seems as though using the rom designed for the phone cures a lot of ills (imagine that). Again, unless your set on sending it back (personally I hate the hassle of that) I'd give that a try too along with doing the button holding thing too if just flashing the rom doesn't correct it. Good luck whichever you decide!
tlarm said:
Sorry that didn't work. I always hate giving up, especially when it's usually a mess I've caused. Hahaha but anyway, if things are straightening out when I have issues, I go back and flash the stock android rom, I'm on Verizon and use the deodexed one in another post on here. Seems as though using the rom designed for the phone cures a lot of ills (imagine that). Again, unless your set on sending it back (personally I hate the hassle of that) I'd give that a try too along with doing the button holding thing too if just flashing the rom doesn't correct it. Good luck whichever you decide!
Click to expand...
Click to collapse
Well I ran an RUU yesterday and had no luck, until I found plugging it in halfway got it to charge. I have tried everything that I can think of along with neo and your suggestions, but the port is just bad. So I am hoping it will hold off until the end of the month when the m9 comes out and I am able to upgrade. So I will ride it out till it completely stops charging or I get a new phone. I do appreciate your suggestions and help though.
bdiddled said:
Well I ran an RUU yesterday and had no luck, until I found plugging it in halfway got it to charge. I have tried everything that I can think of along with neo and your suggestions, but the port is just bad. So I am hoping it will hold off until the end of the month when the m9 comes out and I am able to upgrade. So I will ride it out till it completely stops charging or I get a new phone. I do appreciate your suggestions and help though.
Click to expand...
Click to collapse
If you have insurance they should cover that... Also if your have Verizon the extended warranty may cover it.
TapPed fRom mY HTC OnE mAx
Before anyone says "this has been answered a million times" and posts a link, I want to assure you that I have read every single thing I can here on xda before posting.
The current status of my DNA is unknown to me. The device is rooted and has been for quite a while. It is S-OFF and has been for 3 years. The bootloader is UNLOCKED and has been for 3 years. The recovery is TWRP (most recent version for the DNA). The ROM it was running was santod040's GPE ROM for the DNA. It was running that rom for 6 months.
The device had no Sim card in it. It was used primarily as a backup device if I needed it and to play a few gaming apps that I have multiple accounts with (clash of clans). The device was used only on wifi for gaming. No apps were downloaded to the device prior to the device failure. No websites were visited prior to failure. 360 security was on the device as the primary antiviral app.
Symptoms that created current affliction:
None that I know of
Current affliction(s):
Will not power on
PC USB will not recognize (running Windows 10 - HTC Sync is NOT installed on my computer)
Will not hard reset
Will not boot to bootloader
Will not charge on AC power with original HTC charger (led flashes but never goes solid)
Will not charge on AC power with alternative triple shielded cables (led flashes but never goes solid)
Will not charge with any cable via PC USB (led flashes but never goes solid)
Possible remedies to affliction that have been attempted:
Volume down and power button simultaneously - FAILURE
Volume up and power button simultaneously - FAILURE
Both volume up and down with the power button simultaneously - FAILURE
Holding power button to reset manually - FAILURE
ADB - FAILURE
Boot to bootloader - Not possible for the moment
Boot to recovery - Not possible for the moment
Power up - FAILURE
The only thing it does is flash the amber led light when attached to AC or the PC via the charge cables (I have tried many)
Any and all help or solutions to at least get it back to recovery or the bootloader would be appreciated. I have the RUU 1.15 and a stock original backup saved to the PC. If I can get to at least recovery I should be able to sideload or oem lock the device and run the RUU. But for now I can't even get a screen.
Please help in any way you can and I thank you all in advance for any assistance rendered.
I don't know,but i can only assume that the battery is dead. You can buy new battery and try to replace it yourself. I bough battery replacement for my Droid DNA in case something happens from aliexpress : http://www.aliexpress.com/item/orig...rfly-droid-dna-htl21-bl83100/32260653385.html
HTC Droid DNA Battery Replacement Guide: https://www.youtube.com/watch?v=aFCvGcG0dVs
I give just a guess.
it seems, like cirios83 said, battery is "dead", i.e. battery is alive, but it self-locked by controller on very low voltage level.
why?
something makes battery drain. in my case it was unexpectedly died sound chip tf9887. time of replacing take over 1-2 hour in service (if they have an donor).
beffore going to service you can take off a back lid, disconnect the battery and measure resistance of supply chain. it must be close to infinity.
if it is not. you will know at least, that mainboard is in trouble.
this is example of one of many reasons why phone is "dead"
cirios83 said:
I don't know,but i can only assume that the battery is dead. You can buy new battery and try to replace it yourself. I bough battery replacement for my Droid DNA in case something happens from aliexpress : http://www.aliexpress.com/item/orig...rfly-droid-dna-htl21-bl83100/32260653385.html
HTC Droid DNA Battery Replacement Guide: https://www.youtube.com/watch?v=aFCvGcG0dVs
I give just a guess.
Click to expand...
Click to collapse
Since the phone is a uni body design, I have never looked into actually taking it apart. We do have a few places where I live that specialize in repairs and such, but I am not completely sure that the battery is the issue, it had one other problem that developed about a year and a half ago. That problem was the loudspeaker on the back no longer produced sound.
Perhaps there is a loose connection in the hardware itself causing it to no longer function. It's not a pressing matter as I do have another backup device or two. I'm just a little disheartened that it's no longer functioning.