I've got a strange issues and, unfortunately, I'm not exactly sure when it started. When I do a reboot or a shutdown of my phone it will not power back on after it shuts down. I can't push the power button to make it power back on. I have pull the battery first, then it will power back on without any issues.
I honestly don't reboot or shutdown my phone very often, so I don't really know when this may have started. I'm running Uncommon Sense v1.1 with the stock kernel. I also have a custom Boot Animation and Splash screen. I know I've done successful boot/restarts with the custom splash screen and with Uncommon Sense v1.0. Booting into Bootloader or Clockwork seems to work fine.
Any suggestions on what I should check?
I figured this out. I upgraded to Clockwork 2.5.0.5 a few days ago just prior to me noticing this issue. I downgraded back to 2.5.0.1 and everything seems to be working again. Weird.
Related
Hi!
I flashed CM7 (Stable) last night and it was working great. I was using it today when phone froze on me...I don't remember what I was doing...I think I was listening to Pandora. Even though the system was frozen, I was able to hold down the Power button to select Reboot. Phone rebooted but it was stuck on the splash screen for at least 10 minutes. I pulled the battery but it won't get past the splash screen. I tried to get into hboot but the phone vibrated several times and then displayed a blank screen. Now all my phone is doing is flashing the green LED.
Any ideas?
Thanks,
Marc
This could be bad, but don't panic yet.
It has happened to me before and a simple waiting 5-10 min and a battery pull has done the trick.
Do you have a nandroid backup? If so and the battery pull works reboot into hboot and then recovery and restore it. If not boot into hboot and do a full factory reset.
If after waiting a while and you a battery pull still doesn't do the trick try holding down the power button and volume UP. This could possibly reboot it.
If you finally give up I suggest trying this thread.
http://forum.xda-developers.com/archive/index.php/t-958411.html
Thanks! I stopped panicking enough to be able to get into HBoot I still couldnt get past the splash screen so I ended up reflashing CM7. Everything is fine and dandy now. I'm keeping an eye out on it today because it froze when it was running low on battery...I want to see if it does the same thing today. Thanks again for the help!
Good luck...
I've had great luck with the CM7 ROM. Last night I ran my battery down to 1% before charging and didn't experience any issues. Hopefully your issue is resolved for good!!!
Glad I could help! I really like CM7 the battery is great on it. If it freezes again try to reflash it. If it works, Great! haha
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/
Had a friend bring over an Evo 4g with the infamous bootloop of death.
Specs:
Revolutionary
S-Off
HW: 003
Radio: 2.15.0808
HBoot 6.16
*Aftermarket Extended Battery*
First attempt at booting the phone, it would hit the lockscreen and reset. Then it stopped on the boot animation, and then it hit the splash screen after that reboot and it gave up. Trying to get to recovery at that stage resulted in freezing on the splash screen as well. Flashed the Amon-Ra recovery successfully and it would SOMETIMES go to it and then sometimes it would just freeze on the splash screen. Hmm... Tried CWM recovery with similar results. When I was in recovery, I did factory data and cache wipes as well, just to be on the safe side. No luck. Alright, so I figured let's reset everything and start over, maybe there was a bad flash of a rom or kernel. Flashed the hex-edited HBoot 6.17 and then the stock P36IMG.zip for the 4.54 version. Everything went smooth, no error messages, all OK. Now the phone is listed as S-On with the appropriate HBoot and Radio versions. Good deal...and bootloop issue continues. Argh! Figured, I should try running the RUU from the PC just for heck of it. I tried both the 4.54 and 4.67 versions and both provided Error 120 saying the battery was not 30% or more. Odd, since the battery was charged fully according to the charging light, and from the brief times it did hit the lockscreen the battery looked fine. So I took a break from it. I came back to it the next day and thought I would try and, it booted to the lockscreen, and bootloop. Hmm. Seems it only likes to boot when cool or not having messed with it for awhile. Interesting. Let it set for a bit then put it on a fan and tried to boot to recovery...and it was the first time it had went to recovery in awhile. Hmmm. Took the phone and put it in a tupperware and put it in the freezer for like 10-15 minutes and tried to boot again. Booted all the way just like normal! Weird. Running like a champ. Played around with it for a few minutes, then just let it sit for awhile. No reboots at all. Rebooted the phone manually, but there comes the bootloop. So, threw it back in the freezer and tried it again after a bit and now the phone has been on for over 5 hours. Haven't played with it much, but before it just wouldn't even load, but now, obviously the temp has risen to normal levels and no restarts. I'm completely baffled. Would this be an issue with the battery since it is an aftermarket one (don't have a stock one to test unfortunately) since I know it can cause random issues and RUU didn't like it or...some strange hardware malfunction? Previously thought it might be an issue with the NV partition from the MetroPCS flash but since it is up and running OK now, I would think that would not be the case. Any thoughts?
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.
msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.
So enjoy the fix if you ever run into the above issue.
Im fine with stock, but I miss the fun of trying new roms.
I was running a custom KitKat ROM on my Note II, but lately it has been acting up. For example, it would randomly restart on me. And when I would go to shut it down, it wouldn't shut down. Only reboot. And if I take the battery out, as soon as I put the battery back in it would start booting up (I wouldn't even press any buttons).
So I decided to flash Cyanide Android's custom ROM 6.0.1 (Cyanide-v5.0-t0lte-Detoxified-20160828.zip). It is running wonderfully. So far, no random reboots. However, the problem still remains with when I go to shut it down, it reboots. And if I put the battery back in (after taking it out), it starts booting up.
Any ideas on where to start to pinpoint the problem?
Does the same thing happen on a stock ROM? If it does, at least you know if probably isn't a software problem.
I don't know. It started happening loooong after I started putting custom ROM's on. I didn't bother going back to stock. I doubt it's a custom ROM problem.
You'll never really know until you try a stock ROM.
audit13 said:
You'll never really know until you try a stock ROM.
Click to expand...
Click to collapse
Ok. Yes. It does it with stock ROM as well. Now what?
Strange that the problem still exists. Maybe one of custom ROMs changed something in the phone's behaviour? I'm really not sure. Sorry.
It happened randomly after having a custom ROM for at least a year. And it also does weird things like, it's on, and I go to turn the screen on, and it just won't turn on (even though the phone is on). So I have to hold in the power button to hard boot it.