My friend has a completely unrooted, stock Evo. I'm not sure about the hardware version, and I hope it doesn't matter.
They were texting and using navigation with the phone plugged into a car charger, when it turned itself off and now won't turn back on. After a battery pull, it'll boot to the splash screen, but then shuts off again. After that, it doesn't boot at all.
I've tried getting it into fastboot, but I'm not incredibly familiar with the Evo. So far, no luck.
I have a rooted Incredible, so I've tried all the little tricks I've used to fix my phone.
So, any ideas? Bad hardware, bad software? Get it replaced?
My last Evo (I'm on my third one) was unrooted & would do something similar. At first it would just reboot itself, but then the screen would freeze & flicker and I would have to pull the battery then try to boot it up. Sometimes it would take 10 or so tries, but after it would boot up it would eventually do the same thing. At first doing a factory reset would fix it but then that stopped working.
If it's similar to my issue then it will have to be replaced. If your friend has insurance then they'll replace it for free since it isn't user damage. Until they get a replacement, try booting into fastboot & selecting reboot from there instead of just powering it on. That worked for me a few times.
I had tried the fastboot reboot, but it wouldn't even get that far.
Turns out, the navigation and texting had drained the battery faster than the car charger could charge it. After a full charge overnight, it's booting up fine. So it was fortunately a very simple problem.
Thanks for the reply, though.
Sent from my ADR6300 using XDA App
I was going to update to latest AOKP, I selected reboot to recovery, phone turned off and never turned back on. I can't get into recovery mode either this is very odd any ideas?
This is very strange because this should not cause a hard brick... when I selected reboot to recovery it seemed like it froze for a second, but though it was just in the middle of restarting, then it just shut off. Why would that cause this, only thing I can think is maybe my battery drained... I have it hooked up to a charger right now. But like I said I can't get the phone to do anything.
Same thing happened to me with Galaxy Note from AT&T, I've been looking in several forums about this, but since the phone is not even charging the battery or booting, I'm loosing hope.
This suck ass
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
nexus24 said:
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
Click to expand...
Click to collapse
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
had tisesr
mentisimperium said:
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
Click to expand...
Click to collapse
I've heard of that too, I took apart my s3 and removed the power button as well as blew some compressed air through it. Still didnt work but yes keep me updated!
I ripped my power switch from the motherboard. To turn it on you plug it in and hold home and volume down to go to the odin screen. click volume down to reboot the phone. I am waiting for a new switch to come in the mail which I will attempt to solder onto the board.
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.