Related
Hi all,
I desperate need help. After an unsuccessful radio flash, my Desire won't even turn on. No response from any buttons or lights. Here's how it happened:
I'm relatively new to Android. I recently bought a Desire, to replace my Touch HD, which has seen about 25 different WM ROMs, over it's life.
I successfully rooted my Desire and had tried a few ROMs. I was sitting on the MoDaCo Custom ROM r17, which was all customised and running perfectly. I'd even used ADB to successfully update my wifi config to connect to my company LEAP-authenticated network.
I decided to flash the latest radio (32.37.00.32U_4.06.00.16_2), from this thread:
http://forum.xda-developers.com/showthread.php?t=687464
I entered Recovery using 'Fake-Flash';
I started flashing the radio image;
All the good messages were scrolling down the screen;
I kept one eye on the phone while I worked on my laptop;
I saw a message saying something to the effect of "Finished installing radio..." (sorry, I don't remember the exact wording);
The blue recovery menu had returned, with 'reboot device' as the default selection;
As I clicked the trackball, I saw another message appear under the 'finished' messages, which said "Writing rad " I guess it didn't have time to print the whole message, when I selected reboot.
The screen went blank then a graphic appeared in the middle (where the recovery exclamation mark and triangle usually appear), of a software box with a curved yellow arrow over it and the android icon peeking out from behind it. I left it for a while (already had that sinking feeling) then pressed the power button. It switched off and stayed there.
Since then, nothing that I've tried has received any response. Various combination's of button pushes, USB connection, removed SIM, SD and battery...nothing, not even an LED.
I've searched and haven't been able to find any solutions to this particular situation. Can anyone help, or am I totally bricked?
Regards, PF.
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
socktug said:
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
Click to expand...
Click to collapse
No question is silly under this circumstance!
Yes. I'd just taken it off overnight charge. 100%. If I plug the USB cable in now, there is no response from the LED.
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
socktug said:
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
Click to expand...
Click to collapse
ok. The charger has been plugged in for 35 minutes and still no response.
Also don't want to sound patronizing, but have you taken the battery out and turned on with the back button helld?
Ignore me, just reread your original post.
the procedure u said sounds rite, thats whats ment to happen, when you flash a radio, only other thing that comes to mind is, sure the radio u flashed was for the gsm desire?
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
cgrec92 said:
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
Click to expand...
Click to collapse
Right first time. It won't turn on at all. It doesn't react in any way to any of the button combinations I'm aware of from rooting and flashing it. Nothing happens at all.
I live in an HTC household, so I've tried a number of chargers and cables, including the PC's USB port. I haven't tried another battery...but the incumbent battery was holdng a good charge and was 100% at the time. What's more, I remember that the phone can run on the charger without the battery.
Not surprisingly, adb devices shows no connected devices.
I think everyone is right, it's back to HTC. I *hope* you're right that they cover it under warranty. I'm going on the weekend, so I'll let you all know the result.
Thanks to all for your help.
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
peewster said:
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
Click to expand...
Click to collapse
In the usb brick situation you can still charge. This isn't it!
socktug said:
In the usb brick situation you can still charge. This isn't it!
Click to expand...
Click to collapse
Ok i didn't know that.
If the phone doesn't turn on at all, you can maybe try sending it back to the shop for replacement. Chances are, they won't be able to know what happened, so you can pretend it just stopped working.
If it gets back to HTC, they probably won't bother to figure out what's wrong with the phone and just give you a replacement. Otherwise, they'll just send you the phone back and you won't have lost much (maybe postage costs?).
ash1684 said:
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Click to expand...
Click to collapse
Thanks for the suggestion. I left the battery out overnight. Then tried to activate it (all the usual button combos) with:
Battery out, USB cable plugged in;
Battery in, USB unplugged;
Battery in, USB in.
I scoured the 'net for anything on protection mode for the Desire...no luck. If there is one, it hasn't been posted yet.
I would just act stupid and try to return it under warranty!
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Umbrella Corp. said:
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Click to expand...
Click to collapse
Yes, if it's totally bricked then just send it back to HTC and they will change it with no problems just same as acer done with my Liquid
All's well that ends well
Good news...
The HTC service centre were kind enough to replace my 'faulty' handset.
Re-flashed with r19 and radio updated (patiently) successfully.
Thanks all for your support.
Nice one. Glad it worked out for you
GReetings,
So I have searched for a lot of forums to see if there is an answer to this.
So the story goes. I got myself a new phone and put the TP2 in a drawer. After moving, I have a reason to pull it out and get it ready to be used again. However, it wont turn on.
So I figure the battery went dead. I plug it into the charger, the LED lights up, and got to wait a few minutes. After a minute or so, the white HTC screen suddenly comes on the screen, it vibrates one quick, and shuts off again.
I cant power it up, I can get it to boot loader. Really not sure what the problem is here.
Any ideas suggestions would be welcome as I want to put this one back to stock so I can send it to my step-kid for use.
Try charging it for a few hours, while it is closed. If the phone regularly reboots and then switches off, leave it that way.
The idea is to charge the battery enough, so as the phone boots.
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
kilmarac said:
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
Click to expand...
Click to collapse
Did you get it to work? I'm having the same problem. I posted in another thread that had the same problem as you.
Maybe HTC really is pushing an auto kill program.
Sent from my PG86100 using Tapatalk
Unfortunately, it didnt work. I think the phone was probably dropped one too many times and is broken. I cant get it to boot, cant even get into the bootloader. So I have no idea.
Steefje said:
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Click to expand...
Click to collapse
I also had the same problem I took out the battery and blew on it to get it to cool down and had it sit out of the phone for 10-15mins then put it in the phone and plugged into charger and left it for 30mins then hit the power button.
This reboot cycle happens when my phone dies in android and it works every time for me.
Hope that helps
for future reference, the phone died with a Sim card in it, revived when a Sim card was replaced.
Sent from my cm_tenderloin using Tapatalk
yesterday I had the same problem, boot loader doesn't work. But.... I charged my battery, replaced it, pushed Vol. down + EndCall btn. + Power btn and inserted battery. As a result my boot loader is working now. But after running task 29 and flashing custom firmware my phone doesn't came back alive. I'm looking for solution now. Did anybody have the same problem?
When I'm flashing original firmware the process stops on checking my phone.
Please, give me advice how to solve my problem. Thx.
RHOD*** 32M SS-BC
SPL-0.88.000
MircoP(LED) Wrong Plat(0x0)
MicroP(KEY) Wrong Plat(0x0)
Turbo HW/Turbo SW
TP MFG DATA
501,526 793,854
810,209 211,200
211,855 Calibrated
First off it looks like you are not Hard SPLed so custom ROMs will be a problem for you. Second you have a major error with your keyboard and touch screen. I have a TP2 that took a dip into some water that has the same error - MircoP(LED) Wrong Plat(0x0) and MicroP(KEY) Wrong Plat(0x0). When I first got the phone it would not turn on but would make a noise that sounded like it was crying. I got another TP2 that works fine and swapped the top halfs of the phones because the new one looked like a dog chewed on it. It still worked but in real bad shape. The touch screen that got wet works fine so it is on the TP2 that I use all the time. The wet TP2 will now start up but the keyboard, all of the front buttons but the end key, and touch screen don't work. The touch screen will only register getting touch in one spot. So if you have a software keyboard up only the t will be hit. I Hard SPLed it, ran task 29, and installed a custom rom on it. I have to use My Mobiler to do anything with it. It also will take a battery that has a full charge and drain it to about 50% in about 20 minutes and then claim the battery is dead even on a charger. Something to play with.
With the error you have unless you got it wet you might have a bad flex cable. I would try to fix the error first before trying to change roms.
Thank you for answer.
My phone was HardSPLed and flashed by custom firmware and works fine for half a year. The reason for my situation was broken charger... I think that problem in hardware when I put it on charge, my phone lightly flashed by orange lamp and became can't turn on
You are told that it is looks like it doesn't hacked because I tried to roll it back to original.
Are you sure the phone did not get wet? Everything you describe makes it sound like the phone took a dip. If not, try plugging it into a computer and see if it will charge and turn on.
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
You can only HSPL once. If they (or you) relocked the device, you won't be able to unlock it again unless you can get Olipro/cmonex to take pity on you.
Glad I could help. Here is a small warning. Once a phone gets wet it's days are numbered. You might have a week, a month, or a year but the phone will die. I would plan ahead for the phone to die and keep an real close eye on it.
Sent from my HTC Touch Pro 2 running FRX07.1 using the XDA mobile application powered by Tapatalk
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
If you need to HardSPL a second time, PM me.
Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?
Hi
elmonen said:
Hello! let's just cut to the chase. I need help..
Couple of days ago I got tired of waiting for the new ota for my phone so I decided to root.. unlocking bootloader went well, installed newest cwm, made a backup of my rom and chose renovate 3.0 as my first rom to try... everything works normal and I update the faux kernel on the rom to version 5b01.. all works normally at this point.. I play games, listen to music, surf the web.. yesterday I then updated the kernel to 5b03.. I went playing dark knigt rises (btw a very good game) and the phone heats up pretty much (which I think is normal as the game is quite heavy and I use wilkyys game booster app). I play about 15minutes and I get the message that the battery is running low, I plug the charger in and continue.. five minutes go and the phone freezes and the screen goes black.. the phone is connected to the charger and the charging light blinks red.. the phone won't start, even when pressing the power key for 10seconds. I can get to the bootloader and recovery _when_ the phone is connected to the charger thou.. if I unplug the charger the phone won't do anything. I search the problem on xda and find some threads about similar problems.. eventually after changing from the wallcharger to the usb charger on my pc (did this many times..) the red light goes solid and I press power and the phone boots normally.. weehee I made it!! or so I thought..
Next day: I woke up and the phone was in charger all night. Battery reads 100%. I load "system tuner" and experiment with undervolting my phone (only -50mv) and run some benchmarks and everything seems working.. I start to download an app from the play store.. the phone freezes and again the same flashing red light is to be seen, I thought it could be because of the undervolt but I'm not sure anymore.. and now I haven't got the phone in working condition.. I have now got the phone in recovery for about three hours and there should be enough juice for it to start but it wont..
I also restored my backup but that didin't help.. with the getvar battery-voltage command it reads about 2500mv which should be enough to atleast power it on?
Click to expand...
Click to collapse
2500mv is far too low for lithium ion batteries. There are protection mechanisms in most lithium ion batteries that will trigger at 2.7volts or lower putting the battery and its protection circuitry into deep sleep.
From the battery university: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries/
Li-ion should never be discharged too low, and there are several safeguards to prevent this from happening. The equipment cuts off when the battery discharges to about 3.0V/cell, stopping the current flow. If the discharge continues to about 2.70V/cell or lower, the battery’s protection circuit puts the battery into a sleep mode. This renders the pack unserviceable and a recharge with most chargers is not possible. To prevent a battery from falling asleep, apply a partial charge before a long storage period.
If this is the case you may not be able to recover easily. We can only assume something went wrong with the phones firmware that caused it to deeply discharge and now protection measures have kicked in.
Regards
Phil
hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..
Hi
elmonen said:
hmm.. thanks for the answer.. last night I got the charging light to stay solid when I plugged the phone in and I was so happy.. but I was so stupid and tried immediatly to turn it on.. it even started and got to the quietly brilliant screen, but died pretty soon and the red light started blinking again.. then I realised I should have kept it charging for a while before trying to turn it on... god damn it..
Click to expand...
Click to collapse
When lithium batteries are deep discharge (below 2.7volt) changes take place which can cause short circuits in the battery, recharging then becomes dangerous, hence the battery goes into a form of safety mode, it's like a fuse blowing. It may never take a charge again, or if it does, the battery life will be less than before.
Hope it recovers okay however if it really did hit 2.5volt it could be permanently damaged now.
Regards
Phil
mine was doing that for a while. Keep it plugged in, if the wall charger doesnt work hook it up to a computer. it will turn on again...
simple keep the phone on charge for few hours and dont touch it.
Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?
elmonen said:
Ok back to the problem.. the phone was in charger yesterday for about 12hours.. and still won't show any signs of recovery.. blinking red light continues... I might just have to accept that I have to send it in to repair... sigh.. and I think I have to pay for it..
As I said in my first post I have restored a nandroid backup of which I made as soon as I installed cwm.. so I should be at stock firmware? allthou I can't confirm it as I can't get the phone to boot but cwm said restore was succesful.. next step is to install original recovery and relock the phone, am I correct? so next question is.. is there anyway to do this as everytime I try to flash something with flasboot I end up with "failed: low battery"...?
Click to expand...
Click to collapse
I've experienced this kind of problem when I drain the battery flat; naturally, I crapped myself like everyone else since there's no easy way to remove the battery like you would for any other phone.
All I did (and still do) when this happens is hold the power button until the main buttons flash white a few times, let go and it should reboot the phone..
two minutes pressing power button, nothing happens
elmonen said:
two minutes pressing power button, nothing happens
Click to expand...
Click to collapse
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
no response! only response is that when it's in charger I can get to to blootlader and recovery with the vol- power combination..
If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Amicushia said:
If it won't charge read this thread. http://forum.xda-developers.com/showthread.php?t=1658084
Helped me out with similar problem.
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Tried that :/ won't work.. as my phone doesnt restart with the script.. only way to get a response from it is to press power and vol down when in charger...
Thanks for the suggestion thou.
all right.. quick update.. I have sent the phone in for repair.. so just waiting for the repair bill
Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.
elmonen said:
Ok... update (don't know if anyones interested..) Today I got at txt message from my carrier that the phone is now ready.. and what do you know.. it was covered by warranty. They changed the motherboard and the screen module (I had one dead pixel) needless to say Im pretty happy now.
Click to expand...
Click to collapse
Don't you just love it when that happens.
I had a rooted phone and my warranty was probably void. A week ago I dropped the phone screen first onto a concrete floor and I expected the worst. Picked it up and turned it on and to my surprise, the screen hadn't cracked. Used it for 5 minutes and it worked as it normally would. When I got back home and wanted to make a call, the screen wouldn't turn on. The lights for the buttons would light up but the screen would remain blank. Calls and texts would come through so the phone worked, just without the screen. After about 10 minutes of tinkering, the screen turned on and I heaved a sigh of relief thinking all was normal again. But when I locked it and tried unlocking it, the screen refused to turn on again. At this point I assumed there would be a loose connection between the MB and screen.
I took the phone to a few repair shops around here to find out how much they would charge and I got quotes around $200. So I decided to try taking it to the vodafone store to see how much it would cost to get HTC to repair the phone. The guy over the counter inspects the phone and finds no physical damage to the screen and says that they'd be glad to replace the phone right then and there at the price of me losing all my data as that would be unrecoverable. I told him I'd be glad to have a replacement on the spot. So in the end, I guess I got a good deal.
Lucky you !
Sent from my HTC One X using XDA Premium HD app
I had the same problem last night:
phone charging with the HTC wallcharger, alarm set.
the device did not ring: it died during the night.
At first, impossible to boot (rom or hboot) or to charge it. I plugged it on my PC and the red light started to flash. One hour later, it was still flashing, so I tried to turn it ON
It turned ON but repported 2% battery only. (ok, that's why it was refusing to boot)
4 hours later, ON and plugged to the HTC wallcharger (that I verified of course), it was still 2%
After three reboots, plug/unplug several times, suddenly battery displayed 44% instead of 2%
Battery monitor repports that indeed, the device charged for the 1st part of the night, then suddenly and very quickly discharged to 0 while plugged, with no particular app to drain the battery.
During the 4 hours it was plugged and ON, it remained 2%, then a sudden 44% after a reboot.....
What the hell is that???? I've now cleaned cache and battery stats in recovery and I'm letting it charging to see if it goes above these 44%
Weird, I really thought my battery had just died....
EDIT: 2 minutes later, it now repports 46%, so seems to charge correctly. But I need to know what happened, I usually relay on my phone alarm to wake up, and if it happens again, it could be a real problem. Maybe I should flash an other recovery, even if I never had a single problem with it?
kennylovesyou said:
did the buttons even flash??
Try holding vol down + power until you get a response, then try holding the power button again ..
for me the key was to get the buttons to flash white, thats when i knew things were gonna be ok! :highfive:
Click to expand...
Click to collapse
I have drained battery, been charging all night with a flashing red LED. No response. Now when I plug it in it still flashes red. When I hold the power button (also power+volume down) the main buttons start flashing white, but no response from the phone whatsoever.
When I let go the power button during the flashing, the lights either go out or stay on..
Any ideas? Thank you!
Hey guys.
Some days ago problems started with overheating. I mean not the usual 40 °C overheating, i mean realy fingerburning crazy hot overheating.
Then friday night my HOX freezed while charging and playing pvz2. And when i say freezed i mean display and sound and everything. I couldnt even turn it of by holding power button for 10 secs. Neither could i turn it on for half an hour after battery drained and i pluged in the cable.
Since my ROM i had was a bit buggy, i thought it might be a solution, flashing another one and so i did.
Happily starting new ROM after flashing, frustrated by first expressions. When the phone charges i cant do anything, otherwise it crashes.
Today it startet crashing while incomming calls. Then finaly it crashed so hard, i cant even start the bootloader. I think the battery is empty, but also i can't charge the phone (or it seems like i cant, cause the led won't light up).
Any Ideas or solutions? Would be great, need an alarm clock for tomorrow
Hmm probably not going to have an alarm clock tomorrow. Leave it on the charger over night. When it's not reacting/powering up in the morning it's over.
So, i tried to start it today again but no reaction. I'm gonna try to send it to t-mobile. Hope i will get a replacement even without warranty because my bootloader is unlocked. Otherwise it would hurt my purse :'(
I doubt they will be able to resurrect it
This sounds like a hardware failure to me.
So, not likely that they will be able to detect the unlocked bootloader.
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!