Database Users

evo wont turn on unless i take out battery

anybody else run into this? i know if i installed a programmed that messed up the startup but if i have to power down the phone and turn it on, the only way i can complete this is by taking the batter out and putting it back in and then the phone powers on.

I just started to have the same trouble. I am going to be doing a wipe and starting over this weekend ... hopefully that will clear up the trouble.

Let me know how that works for you. Mine is doing the same thing.

Having the same problem here, can't figure out why.
Sent from my PC36100 using Tapatalk

this all sounds ominous

i have problems getting mine to turn on as well. i find i have to press and hold the power button for 5 or more seconds to get it to turn on. this may be intentional...

Mine seems to have the same issue, I have to take my battery out also.
Not a big deal since I dont reset often, and its not Windows mobile.
-------------------------------------
Sent via the XDA Tapatalk App

The only time I've had this happen was when the device was connected to the charger, either too the pc or plug. Removing the cord and letting the notification light go off allowed me to boot again normally.

thorpe24 said:
this all sounds ominous
Click to expand...
Click to collapse
Yep. Sounds like you messed with settings that you don't know what you're changing. Start with a clean slate and don't edit what you don't know.

guys when you hit power off the Orange led lights... the phone is not fully shut down until that light turns off (30sec to a min). after that the phone can turn back on without a battery pull.

rutter9 said:
Yep. Sounds like you messed with settings that you don't know what you're changing. Start with a clean slate and don't edit what you don't know.
Click to expand...
Click to collapse
I can assure you I didn't change any settings I didn't know I was changing. And BTW there's no setting that's "Don't let phone turn on without taking the battery out first" and no other settings anywhere, not in EPST, not in Testing, nowhere that would create this problem.
I have found that once you turn it off if you wait 45 seconds all the way up to 2:00 minutes the phone will turn back on without a battery pull.

Ohwut, go to Settings...About Phone...Battery and Boot...and uncheck the box for "Don't let phone turn on without taking the battery out first". You were probably screwing around in here and checked this one by mistake.

davidboyd said:
Ohwut, go to Settings...About Phone...Battery and Boot...and uncheck the box for "Don't let phone turn on without taking the battery out first". You were probably screwing around in here and checked this one by mistake.
Click to expand...
Click to collapse
i needed a laugh this morning.

I was having this same problem. I decided to take it into sprint to see what they had to say. I haven't rooted or done anything with my MSL. After about 15 minutes the techs told me that it was a bad battery. They put a black hero battery in the phone and I have not had a single problem since. they did not wipe my phone back to factory, just replaced the battery.
Maybe you would have luck with the same thing... My suggestion is if you upgraded from a hero like I did, try your hero battery. if you don't have any problems after that, put the evo battery back in and take it to the sprint store and get yourself a replacement battery for it... I can't guarantee that that they won't wipe your phone so backup first. Always backup before taking your phone in to be serviced.

skunkd said:
guys when you hit power off the Orange led lights... the phone is not fully shut down until that light turns off (30sec to a min). after that the phone can turn back on without a battery pull.
Click to expand...
Click to collapse
Mine was off for 5-10 minutes and no light and no response to holding the power down. No options to power off or turn on. NO response at all till I pulled the battery out and replaced it. It hasnt happened since. Of course I had to be with a bunch of iphone users so they were having their fun.

wfhowell said:
Mine was off for 5-10 minutes and no light and no response to holding the power down. No options to power off or turn on. NO response at all till I pulled the battery out and replaced it. It hasnt happened since. Of course I had to be with a bunch of iphone users so they were having their fun.
Click to expand...
Click to collapse
Mine has the same problem. I bought mine from radio shack so trying to get them to do anything is like pulling teeth. And they don't reserve Evos in case something goes wrong like a sprint store does.

I hate to bump such an old thread, but...
Mine will NOT turn back on once I turn it "off" without a battery pull. I'm talking like, waiting more than 5 minutes.
Anybody know what's happening here?

drbadass said:
I hate to bump such an old thread, but...
Mine will NOT turn back on once I turn it "off" without a battery pull. I'm talking like, waiting more than 5 minutes.
Anybody know what's happening here?
Click to expand...
Click to collapse
I had this issue for awhile but it seemed to go away on its own. I have a feeling it might have been a buggy app that either got uninstalled or fixed in an update.
But it was a very annoying problem!!

drbadass said:
I hate to bump such an old thread, but...
Mine will NOT turn back on once I turn it "off" without a battery pull. I'm talking like, waiting more than 5 minutes.
Anybody know what's happening here?
Click to expand...
Click to collapse
try short presses of power button, usually 3rd to fifth press turns it on for me, w/o batt pull

what rom or version are you using? when I was on the 1st OTA update rom I had that problem. But when I OTA to 1.47 it went away. now I am on froyo and of course it's good.

Possible bricked phone?

Installed CM7 on the EVO 4G three days ago and everything has been working fine. Until today when I went to turn my phone on, nothing happened. It vibrated like normal when its booting up, but nothing came up on the screen. Since then, nothing is happening at all. No charging light when plugged in, no sounds, no vibrations, nothing on the screen, not showing up on computer.
What do I try to get this thing to respond?
Did I cause this or is this a hardware problem that just happened to be about the same time I rooted this thing?

slackerlack said:
Installed CM7 on the EVO 4G three days ago and everything has been working fine. Until today when I went to turn my phone on, nothing happened. It vibrated like normal when its booting up, but nothing came up on the screen. Since then, nothing is happening at all. No charging light when plugged in, no sounds, no vibrations, nothing on the screen, not showing up on computer.
What do I try to get this thing to respond?
Did I cause this or is this a hardware problem that just happened to be about the same time I rooted this thing?
Click to expand...
Click to collapse
What method of rooting did you do? You try a battery pull and hold the power button down for 15 secs with the battery out and try to boot it.

reaper24 said:
What method of rooting did you do? You try a battery pull and hold the power button down for 15 secs with the battery out and try to boot it.
Click to expand...
Click to collapse
A bricked phone will have a red triangle looking thing that won't go away lol. One that doesn't respond is usally spanked silly lol. Tho there may still be hope your's isn't try the pull method on batt.

I pulled the battery, held power button and volume down while plugged into wall, no response. Should I leave it unplugged and not try the volume button with it?

slackerlack said:
I pulled the battery, held power button and volume down while plugged into wall, no response. Should I leave it unplugged and not try the volume button with it?
Click to expand...
Click to collapse
Try it without being plugged in and with battery out just hold power button down. Usally clears some big issues. If it doesn't work then it could be spanked. Bad unit.

slackerlack said:
I pulled the battery, held power button and volume down while plugged into wall, no response. Should I leave it unplugged and not try the volume button with it?
Click to expand...
Click to collapse
Do you have an extra battery to try out, or temporarily borrow from a friend? Are you sure your battery was charged up, and it didn't die? It sounds odd that it just did that out of the blue. I'd be suspicious of.a dead battery. They can die to the point that they will not take a charge, and they're totally dead.
Sent from my PC36100 using XDA App

k2buckley said:
Do you have an extra battery to try out, or temporarily borrow from a friend? Are you sure your battery was charged up, and it didn't die? It sounds odd that it just did that out of the blue. I'd be suspicious of.a dead battery. They can die to the point that they will not take a charge, and they're totally dead.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's true lol SBC kernels can spank battery quicker. Id try new battery if it's not it then Id swap it out at sprint.

I do not have another battery to test with, I will have to go to a sprint store to do that. I dont have the unit with me to test tonight, but I will take these suggestions home with me. Thanks guys. Lets hope I didn't brick my girlfriends two week old EVO. She loved the Cyanogenmod that I put on there.

slackerlack said:
I do not have another battery to test with, I will have to go to a sprint store to do that. I dont have the unit with me to test tonight, but I will take these suggestions home with me. Thanks guys. Lets hope I didn't brick my girlfriends two week old EVO. She loved the Cyanogenmod that I put on there.
Click to expand...
Click to collapse
So what kernel were u running?
Sent from my PC36100 using XDA App

[Q] MT4G won't turn on

I was charging my phone on my computer when it just froze and turned off.
After that, I was trying to turn in back on, so I pressed the power button = nothing happened.
I then proceeded to charge it back on the usb charger, hoping that it will turn on or the led light will. Nothing happened.
I don't really know what happened with my phone.
Can someone help me please?

Might sound of obvious but your battery is in correctly right?
Sent from my HTC Glacier using XDA App

kimbernator said:
Might sound of obvious but your battery is in correctly right?
Click to expand...
Click to collapse
Yes it is. I don't know what just happened. I'm like really panicking right now.

Take everything out..battery, sim...leave it out for like 5-10 minutes then try it again.

lowandbehold said:
Take everything out..battery, sim...leave it out for like 5-10 minutes then try it again.
Click to expand...
Click to collapse
I did that as well. I actually left it for 3 hours. Still, nothing happened.

Does the indication light come on when plugged to the charger?

Maybe a bad power button?
If the light comes when charging, I've read you can power on by holding down the home button.
Glacier (duh)
CM7.0.3 (winning!)
Faux 2.5.2 LV (blazing)

esincho said:
Does the indication light come on when plugged to the charger?
Click to expand...
Click to collapse
No, it didn't. Its just dead.
I just returned it to Costco. Thankfully, they were lenient with the return policy because I missed it by 4 days and they still accepted.
Still, I don't have an idea on what happened.

rooted mt4g, powerbutton doesnt work.. under warranty?

My rooted mt4g's power button just stopped working. So i couldn't shut it off for some time. i would reboot by going to terminal emulator, su and reboot.
Today i rebooted my phone and it didnt reboot properly...was stuck on the black screen so i had no choice but to pull the battery out, so now i cant turn it back on.
I called tmobile and explain the problem and said its still under warranty so they will send me a replacement, i only have to pay for shipping.
my question is that since i cant turn on the phone to bring it back to original rom/unroot. Do u guys think there is going to be an issue when i return the phone to them rooted with cm7? i dont want to get charged however much they charge for returning phones that voilated the warranty thingy.

r0mmel said:
My rooted mt4g's power button just stopped working. So i couldn't shut it off for some time. i would reboot by going to terminal emulator, su and reboot.
Today i rebooted my phone and it didnt reboot properly...was stuck on the black screen so i had no choice but to pull the battery out, so now i cant turn it back on.
I called tmobile and explain the problem and said its still under warranty so they will send me a replacement, i only have to pay for shipping.
my question is that since i cant turn on the phone to bring it back to original rom/unroot. Do u guys think there is going to be an issue when i return the phone to them rooted with cm7? i dont want to get charged however much they charge for returning phones that voilated the warranty thingy.
Click to expand...
Click to collapse
Hmmm I see... Do phone's detect ADB while it's off? If so then that's you're only hope I'm assuming.
If all else fails then maybe you can just pop the phone in the microwave for a quick 3 seconds so that the phone wont boot at all. Now that's raking it to extreme of course.
Chances are that T-Mobile wont even check. But I guess its a risk. Because then it'd suck if T-Mobile did turn it on then find a custom ROM.
Sent from my HTC Glacier using xda premium

yea... adb doesnt detect a device thats turned off. hehe
microwave eh? ... maybe.. good idea though..

r0mmel said:
yea... adb doesnt detect a device thats turned off. hehe
microwave eh? ... maybe.. good idea though..
Click to expand...
Click to collapse
Lol yeah, that's an extreme answer but it would be very unfortunate if they decide to try and turn it on then find out it's been modded. I think they end up charging your account like 350 or whatever.
But IMO I honestly don't think they'll even go that far to check. But that's just my opinion lol. Either way, good luck man.

Pull out the battery.
Connect the USB charging cable.
Insert the battery.
Repeat several times until your phone turns on.
Might work.

tried it maybe like 4 times.. its what the tmobile tech support asked me to do.
Jack_R1 said:
Pull out the battery.
Connect the USB charging cable.
Insert the battery.
Repeat several times until your phone turns on.
Might work.
Click to expand...
Click to collapse

Seems to work for me - insert battery while it's plugged in, if it doesn't turn on, battery out, battery in.
As for a software reboot - download the app Easy Reboot.
For HBOOT, try holding down the volume down key while the charger is plugged in, and insert the battery as above.
Sent from my Nook Color!

weird i just tried the battery on and off... still didnt work, the charge light just goes on and off as well... i do have an aftermarket charger, and im using the wall charger not the usb to computer... if that makes any difference..

Yeah I was using the wall charger too, but the one that came with the phone. The very first battery insert (followed by a 5 second pause) started the phone up. Strange. I have ENG HBOOT and ClockworkMod 5.x installed if that makes a difference.

i dont have eng hboot because my phone is already unlocked by tmobile, i didnt see a need for it. i have the latest cwm and latest cm7...
cmstlist said:
Yeah I was using the wall charger too, but the one that came with the phone. The very first battery insert (followed by a 5 second pause) started the phone up. Strange. I have ENG HBOOT and ClockworkMod 5.x installed if that makes a difference.
Click to expand...
Click to collapse

Just on a whim - I don't suppose that running a RUU.exe will provide a way to force the phone to turn on? Doubtful but worth a try.

I think I'm bricked?

I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.

You fool.

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium

Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312

overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.

I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2

ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7

Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up

KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.

So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium

abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7

abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.

Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before

First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.

So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?

Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it

Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.

abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way

dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?