Phone: T-mobile Galaxy S4 (SGH-M919)
Android: Touch Wiz 4.4.4 FOH3 (Stock rooted)
Updated some apps in the app store, while they were installing I got dressed. When I picked up my phone it just shut off.
Thinking it was a dead battery, I plugged it in while in the car. It still doesn't come on. After awhile it would power on, I'd see galaxy s4 logo then the phone would shut off again.
Sometimes it would make it all the way to the T-mobile splash screen, and in some cases it would completely boot up into the phone, but then shut off again.
If I boot into recovery, the phone shuts off as well. Sometimes I can see recovery for 2 seconds then the phone will shut off...other times the entire screen turns bright pink
Now, before you tell me I have a stuck/bad power button. I can boot into download mode and the screen stays on the entire time. So how can that happen if the power button is stuck?
I've reflashed the stock 4.4.4 t-mobile rom and the problem still happens.
So maybe it is a faulty/bad/stuck power button. OR what I think is the case, one of those apps that updated had some bad code or malicious things happening that overload the ram.
How can I wipe my dalvik and other cache partitions to test that theory, if I cannot boot into recovery?
Update:
Had the power button replaced and even tested a different battery. The issue still happens......So I dunno wtf the deal is. I've also managed to get twrp back on and wipe dalvik and cache, still stuck in reboot.
Maybe my processor is over heating and I need a new phone or logic board?
Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?
Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
if you can get into cwm then try fastboot and flash the factory images from the boot screen
_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.
id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it
I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.
Hello everyone,
My phone is NOT rooted. Earlier today it was stuck on the Samsung Screeen when I turned my phone on. I then used the power, camera, volume down button combo to bring me into recovery mode. Now everytime my phone turns on it stays in recovery mode. I can scroll up and down on my choices but there is not a key that I can press that will select a choice. Any ideas for how I can get my phone to work?
Screen I am stuckl on reads: "android system recovery <3e>
enter: OK key, Select : Vol UP/ Vol Down
reboot system now
apply update from SD cared
Wipe Data/factory reset
wipe cache partition
then theres an exclimation mark in a triangle with the android dude below that
#manual Mode#
If you don't care about existing app data, Odin would be a great choice. Either Odin-ing in a custom recovery or a fresh stock system would get you out of the situation.
Sent from Samsung Captivate Glide @ CM10.1.2
Sounds like you tried to do something and the phone didn't like it, hence you boot back into recovery on it's own.
Use Odin and reflash stock.
Much Thanks
Thank you very much for the responses, for some reason I was under the impression that your phone had to be rooted in order to use odin, much thanks!
I do not care about my personal files getting lost, but just out of pure curiosity, roughly, how would one accomplish that?
I'm try out odin now!
Back to my old problem! Any ideas?
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
apugslovesxda said:
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
Click to expand...
Click to collapse
Well, first boot of flashing any custom or stock rom takes a bit to fully boot. If you're stuck at the Samsung or Galaxy S screens, then you should reflash. If you have tried that and still having the same issue, then try a few more times. I've read posts of people having constant boot loops on flashes and they finally got one flash to properly stick after many tries.
So odined again and again, this time my phone eventually did turn on but it literally took 30 mins. When it did turn on I had no network connection nor could I use my touchscreen, it eventually shut off. I'ma go get robbed at the sprint store in a bit lol.
End Thread
End Thread- I got a Samsung Galaxy Note 3. My god- this phone is amazing. Kinda bull**** that I got nothing for my old phone with full insurance when it seems like it was a hardware failure!
Can't wait to play with this beast of a phone tomorrow!
Yes, you may ask, just search on google, but people are having problems with the POWER button only.
When I power on my phone, as normal it goes on the Galaxy S4 logo, but after around 2 seconds of it, the phone just powers off.
The phone is detected by odin, and when it resets after flashing a rom, it restarts normally, but powers off quickly, and thats it.
Please help, I was flashing a custom rom by ALBE95 (s6 4.7 port), but it did the same problem, so I wanted to reflash the normal rom, and the problem just happened again.
EDIT: I can also go into download mode, but I can't go to recovery
Maybe a battery problem?
I already fixed it ;p
A few weeks ago, my Tab Pro 8.4 started bootlooping. I did a few cache/dalvik wipes and got it going again. I think I reflashed the ROM and GApps also.
Now It is doing something odd. If I leave it plugged in overnight, it powers off. It takes a very long (20 second) power button hold to get it to wake. That woke it in the past, but today is something new. Now it is going into a bootloop. During the boot animation, it stutters, freezes, then goes back to the bootloader splash page (the one with the "seandroid enforcing" and "warranty bit" message on top).
It has no issue going into TWRP and I have just done a full backup. I am going to go back into TWRP and make a copy of internal. I have a few files in there that I don't want to lose.
Could this be a ROM issue? (I will update ROM info after next time I am in the device/TWRP) Hardware? I just installed a new battery, but this issue started with the old battery. Any ideas on how to get this revived?