This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights
It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.
Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.
Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk
The light doesnt change
clean off the battery contacts
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL
There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.
Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.
This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.
I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.
I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....
Hey there,
I've been learning from XDA for a while.
On the last few months I rooted, flashed and put on some stamina on my htc hero gsm.
Finally I had it in good shape, and stopped fiddling about. I was pretty happy with my "new" hero.
Unfortunately, about two days ago, it went off by itself, while sitting on my desk.
I tried to get it back on, but no signs of life.
Holding the power button, I got nothing.. no lights, vibration, not at all.
Tried holding the menu to get to recovery, but the thing still don't move.
Checked the battery.. over 4v, almost full. Tried an old battery.. nothing.
Connected the charger.. not even the yellow light came on.
So, I guess this is it.. or there is anything else I can try?
Was anyone there? did anyone came back?
Repair shop is not an option to me.. here in Brazil, competence is rare and expensive.
I'll miss my htc, it's time to clean the dust from my N95 8Gb.
Well if you dont get the yellow light, and the fact it went off while it was used not flashed, i would say that is a hardware failture
kemoba said:
Well if you dont get the yellow light, and the fact it went off while it was used not flashed, i would say that is a hardware failture
Click to expand...
Click to collapse
So, nothing can be done? Is there any guide for troubleshooting mobile hardware for dummies?
Thanks anyway..
I very recently had my Nexus give me the blinking red light of death. It started when I couldn't flash the latest Franco Kernel due to an "Unmatching MD5" error. So, I thought why not update Cyanogenmod 10 to the latest nightly? Lo and behold, it skips the prompt asking if I want to install it and the phone shuts off. The furthest I've gotten right now is getting it to the standard recovery, and that was only for a minute (this was after I hooked the phone up and used the Nexus toolkit to reflash the stock recovory). Now, when I try to flash the stock ROM, I either get "device not found" or that some random error has happened. I'm stuck between either using software methods to fix this, or sending it in for an RMA sooner than I thought I would (it has tons of scratches and dents).
Just as a note, I know about the battery trick, and I'm not up for doing that. I'd sooner RMA it, as I believe after relocking the bootloader it would still be under warranty since it seems to technically have no ROM installed right now.
Will it boot into fastboot?
It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.
CodemasterRob said:
It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.
Click to expand...
Click to collapse
If you can get into Fastboot mode, have you tried flashing the stock images from Google?
Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.
CodemasterRob said:
Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.
Click to expand...
Click to collapse
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app
Mephisto Zap said:
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Heh, I was about to direct you to the OP
That *might* fix it, but I believe a full battery replacement is in order. The phone was reaching an excess of 150 degrees before it shut down, it literally burnt my leg and gave me a red spot. All is well though; I managed to pry the SIM card out, wipe all of the partitions, and get it back to factory state before it completely turned over in it's grave. Learned my lesson the first time around; got myself a case to prevent all of those nasty scratches and I'll be ordering XO skins soon.
Ok, so my friend has a problem with his Nexus 7. The device doesn't turn or and the screen flicker's if it's plug to the wall. This started happening after he dropped it on the floor, so it has to be some kind of hardware issue. My first thought's are that the panel has broken, is there a way to confirm this when I open the device? Or do you guys have some other thoughts, thanks in advance!
I have the same problem as you, and I am yet to find a solution. Mine just got stuck booting one day and then a day later wouldn't switch on at all and only get screen flickers when you plug it into a charger.
If we knew what had gone wrong, we might be able to fix it?
Sent from my LG-P768 using xda app-developers app
Check battery cable
You must open device and check if battery cable got loose...
I have the same problem, i just posted about it in my own thread. My N7 was never dropped. I tried reseating the battery cable. No luck.
We've got a sticky just for this issue.
http://forum.xda-developers.com/showthread.php?t=2090826
Hope it helps!
-bk
billykxda said:
We've got a sticky just for this issue.
http://forum.xda-developers.com/showthread.php?t=2090826
Hope it helps!
-bk
Click to expand...
Click to collapse
The difference between what is in this thread and the sticky is the flickering. I haven't seen any mention of people have flickering screens. In my case, the stick is the first place i went and i tried every recommendation offered.
My screen flickered and was snowy. Just didn't mention it.
If you tried all of the fixes in the OP, then I agree you are in a different problem space.
Good luck with it.
So I've had my phone (d803 canada telus) for 2 years and it's been fine for most of it but a few months ago it started to reboot over and over, sometimes when im using an app or sometimes just sitting there.. sometimes it reboots right away and others it takes a whole night of wait to start again. Is there a way to fix this, i have performed a factoty reset and it didng didn't fix the problem.
Weirdly for about phases of a week once in a while the problem would stop amd and id be like whoa cool but it would start again and this time it looks like its gonna stay. Please help? Called and the only thing they said i could do was "repair" it for $149 but nuh uh. I don't even know what could have changed to the phone physically because i take good care of it.
not sure if goign back to stock again a tot or kdz installation might help.?
or maybe you have hardware problem
raptorddd said:
not sure if goign back to stock again a tot or kdz installation might help.?
or maybe you have hardware problem
Click to expand...
Click to collapse
What kind of hardware malfunction could cause a phone to turn on and off 40 times a day?
Minchan_5 said:
What kind of hardware malfunction could cause a phone to turn on and off 40 times a day?
Click to expand...
Click to collapse
It could be anything. A single bad capacitor could ruin a phone. It's rare but it does happen from time to time. Like raptorddd suggested, try to tot back to stock following THIS GUIDE. Then update to th latest ota and factory reset. If that doesn't fix it then it looks like you need a new phone. Good luck.
Had this issue when my battery started dying.
Got a replacement and the problem went away
If you take the phone apart you may notice the battery could have started to swell
Minchan_5 said:
So I've had my phone (d803 canada telus) for 2 years and it's been fine for most of it but a few months ago it started to reboot over and over, sometimes when im using an app or sometimes just sitting there.. sometimes it reboots right away and others it takes a whole night of wait to start again. Is there a way to fix this, i have performed a factoty reset and it didng didn't fix the problem.
Weirdly for about phases of a week once in a while the problem would stop amd and id be like whoa cool but it would start again and this time it looks like its gonna stay. Please help? Called and the only thing they said i could do was "repair" it for $149 but nuh uh. I don't even know what could have changed to the phone physically because i take good care of it.
Click to expand...
Click to collapse
tiguy99 said:
Had this issue when my battery started dying.
Got a replacement and the problem went away
If you take the phone apart you may notice the battery could have started to swell
Click to expand...
Click to collapse
Ok so I took my phone apart and didn't notice anything that weird except that it was reeeaallyy dirty inside, dust all over the place, mainly at the bottom where the speakers are. I cleaned it mostly but I don't think that's the problem. But I looked a little closer at the battery and it doesn't seem swelled like you suggested but it had tiny dents. Would I need to get it replaced? Don't even know how this could have happened. Would pictures help or is the desc enough
Yes. It's not holding proper voltage
Minchan_5 said:
Ok so I took my phone apart and didn't notice anything that weird except that it was reeeaallyy dirty inside, dust all over the place, mainly at the bottom where the speakers are. I cleaned it mostly but I don't think that's the problem. But I looked a little closer at the battery and it doesn't seem swelled like you suggested but it had tiny dents. Would I need to get it replaced? Don't even know how this could have happened. Would pictures help or is the desc enough
Click to expand...
Click to collapse
tiguy99 said:
Yes. It's not holding proper voltage
Click to expand...
Click to collapse
I'll try a new battery then, thanks!
No prob!
Keep us posted