Related
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.....
So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
to not confuse anyone it poped again which then made the device inoperable, forgot to mention that *hits head*
flynney said:
So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
Click to expand...
Click to collapse
suicide !! domestic violence !!
its the HTC auto destruct sequence. It has detected that you have enough money saved up for a new phone, has reported this fact to HTC and they have sent the kill signal. You should start recieving phone ad emails from them any time soon.
lol I would never hurt my beloved HD2 i love it too much.
and im broke i dont have enough money for a cup of tea now days lol
bbbbbbbbbbbbbbbbbibibibi
bobobobobobobobobo
get a job
Whilst at it, get a new or 2nd hand hd2
flynney said:
So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
Click to expand...
Click to collapse
Maybe you were pushing the GPU aspect of the Snapdragon SOC too much.
i haven't a clue didnt think bubble jump was a demanding game, and i have a job, but ive used all my money on car insurance lol
If you can get to the bootloader (even if you can not see the screen) task 29 and reflash original Win 6.5 ROM. By doing that you can eliminate software and, if you have warranty or insurance, exercise that.
I could not possibly suggest that now is a time to get insurance and, having waited a significant time period, drop the HD2 from a great height.
Sent from my HTC HD2 using XDA Premium App
hey, couldn't boot in to spl due to the pop, i think that ultimately killed the whole system as non of my spare batteries work nor does the charger, the insurance i have on it accepted it fine and have told me i should expect a replacement in about a week.
I am very pleased that you have insurance then and will not be without your beloved HD2.
If no charge is a secondary problem then an interesting test was whether or not you could access the bootloader whilst external power is applied - in this Maglr world I believe that you can trickle charge through that method. You probably did that which I think confirmed a major hardware problem (check battery terminal pins though).
I hope it arrives quickly for you.
Sent from my HTC HD2 using XDA Premium App
well from what i could tell the pins were all still in tact and before the pop, the charger worked on it. seemed very odd why it would just do that, but I'm no electrician. thanks for the replys guys =)
Just a story here, I RMAed my TF about a week and a half ago for like 8 dead pixels (just bought it at the end of August) and just got it back today. Went to go nvflash it so I could have root back, etc etc., and when it booted up (came back at 91%) I noticed it wasn't charging. I tried flashing a custom kernel, still not charging. Thought that was weird, so tried nvflashing again, except nvflashing wouldn't work. Thing was, the nvflash had had some trouble the first time, because I was doing it on my husband's computer (mine like, exploded yesterday, some ArchLinux update did NOT like me) and it kept saying "could not connect to any USB devices." I didn't think much of it when it finally worked because he said his had done that before, but in retrospect, must have been related to the charging problem.
Anyway, at this point I was pretty crabby, because I don't really understand how I RMAed my perfectly functioning TF (with slightly defective screen) and I now have a completely non-functioning TF with a perfect screen. (I guess they fixed the problem?) WTF were they even messing with the USB port for anyway? Anyway, I never was able to nvflash it back to stock, except I did manage to get it to work finally by holding the USB cable at its base next to the TF carefully (and before anyone says it's the cable, tried several, it is not) but then it interrupted halfway through and would not restart, and I'm pretty sure the tablet is a brick. Could someone correct me if I'm wrong - is there a way to restart the nvflash process if it has been interrupted partway through?
Either way, just thought I'd share this nightmare. I'm still pretty irritated with Asus, which is saying something, because I've always been kind of an Asus fangirl.
you did not mention if is still not charging . If so could be the small switch inside. Search for not charging as there are several threads on opening TF and finding switch. If bat gets too low can effect flashing.
The battery was at about 88% when I flashed - now the TF won't do anything at all, including start the nvflash process over again. Terminal just throws an error and says something about not being able to restart because end point was not reached. (Not by the computer) I'm pretty sure it had nothing to do with having enough charge, it just won't connect properly.
Like I said though, doesn't matter much now, because the TF won't do anything. Won't go into APX mode or boot. I assume this is because the nvflash process interrupted halfway through. It won't let me restart it - get the error I mentioned. I assume I'm screwed, but was wondering if anyone knew a way to get it going again. I thought it was pretty impossible to brick a TF (like a Droid X) but I've never seen an nvflash (or an SBF) interrupted halfway through.
Edit: and yeah I have no idea if it'd charge like this or not, but somehow I doubt it Firmware = poof.
Sent from my DROIDX using Tapatalk
do you know which RMA facility it was shipped too? ive heard horror stories about the texas facility. just curious oh and i hope you get it fixed
I have a ASUS G73 notebook that I had to RMA like a year ago for screen problems. It went to some place in Indiana. When I got it back it had an LCD with a deep gouge in it as if someone had taken a knife to it. So yeah who knows what the deal is with the companies ASUS outsources repair to.
Was indeed Texas. Gave them a call and the guy was like "Derp we think something might be wrong with the battery" and had me try turning it on, blah blah. Am shipping it back tomorrow. I don't feel particularly bad, since it wasn't my screwup, and it's not like I was a dumbass and was like I WILL FLASH AT 3% BATTERY LOLZ. There's clearly something messed up somehow with the connectors.
Anyway, I hope that it gets resolved soon. Being without it really sucks for school. I'm sure its just going to get there and they're not going to be able to turn it on either, no matter what they try. Makes me wish I would have just stuck with the dead pixels though, because I suppose if they do replace it, I'll end up with a B9O. :/
Edit: Thanks for commiserating with me anyway, guys - helps me feel a little better!
Sent from my DROIDX using Tapatalk
My coworker and I both had to RMA the dock to the TX facility and both docks came back with problems. I sent it back there yet another time but his was sent to CA. The turnaround time was amazing but the quality... not so much. It's on its way back to me though and tomorrow I'll know what they did this time.
uploder said:
do you know which RMA facility it was shipped too? ive heard horror stories about the texas facility. just curious oh and i hope you get it fixed
Click to expand...
Click to collapse
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.
Had my Nexus 4 for some time now and the issues started once Android 5.x.x was released but has increased more recently.
I ended up trying around eight different ROMs posted on here hoping it might be OS level but it still does it.
Currently using this MIUI build whilst sacrificing the ability to use certain apps like banking.
It's getting to the point where it decides to power down and might not even turn back on till the next day. Which is exactly what happened yesterday.
When I attempt to power it on it gets as far going through all the boot animations; then I'll hear some sort of notification sound and it just powers down. This is the case for all ROMs.
As far as the battery being messed it was replaced with a new one a few months ago with me thinking it may be a solution for it. It's never been dropped or damaged so I don't suspect any internal damage. There's also no overheating ever if it helps. Just wanted to gather some opinions/advice on it before I pull the plug on the device and buy something else.
I am not sure if my situation is similar to yours but I'll share it anyway.
My battery was also a newly replaced recently but with an OEM battery, not the original from LG.
So it turns out that so-called 'new' battery depleted rather quickly and the power off randomly happens to me as well.
Until one morning, I realize the back cover was having this huge hump like its about to break apart.
Then I took apart the back cover and to my surprise, the battery was bulking inside (sign of a faulty battery)
Although it still can hold the charge, but it was making my phone looked like it was about to explode.
So my mistake at the time was thinking that the battery is fine when its actually not.
Because it was from OEM, so there is a chance or possibility that battery might go bad beyond our expectation.
Thanks for the reply!
Yeah I did replace it with a non LG battery but that was out of non being in stock at the time.
What I have now is a Kamal Star replacement from Amazon
The bulking you mention I don't seem to have with this current battery but when I was replacing the previous one I did notice it was bubbling if that's the best way for describing it; just a few small bump/bubbles over it randomly spaced. I really hope it wasn't somehow the cause the of the current fault.