Hi all, so I was trying to test some under volting and my phone randomly shut off. When i turn it back on, the phone goes into a boot loop. Besides the boot loop I can still access recovery and Odin. What is the safest way to revert back to original settings? Thanks!
Looks like I fixed it. Please close this thread.
What did you do to fix it?
Also, remember, when playing with CPU parameters it is important to not have anything set at boot until you have tested it for a good while in order to make sure it is stable.
With under volting .... breast way to find good values is to keep dropping it down.... in 25mv intervals, until you have issues (such as reboots) then add 50mv to that setting.
Related
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Well the phone will take slightly longer to boot up once you wipe the caches, because they have to rebuild. Do you wipe your cache and dalvik when flashing a boot animation?
WhiteiceDMSTech said:
Over the last few months, I have noticed that my phone tends to get stuck on the splashscreen ALOT. I notice it when I reboot the phone. I can't remember it really ever being like this.
Someone did make a custom boot screen (The Michael Jordan symbol by Rydah in the Theme's and App forum.) I am in no way saying it's this or his fault or anything, I just have noticed it happening a lot sometime after I added that file.
I have flashed a lot of rom's here and there (always wiping ALL and using the format.all 2x before flashing a new ROM.)
I was wondering if anyone else has encountered anything like this and if they were able to correct it somehow? Or, if anyone has any suggestions on what I can do to try and correct this so anytime I reboot, it reboots normally instead of locking up?
BTW, when it locks up, I do the battery pull and let the battery sit for 30 seconds before I put the battery back in and reboot.
Thank you,
Whiteice
Click to expand...
Click to collapse
That's never really happened to me on a consistent basis. I've got stuck at the splash screen a couple of times, but it was my own doing one way or another. How long do you let it hang on the Splash screen before you pull the battery? Sometimes mine will sit on the splash for a good minute or so during a normal reboot. After wiping cache's it can sit there for a good 3 or 4 minutes sometimes. I've caught myself pulling hte back cover off the phone to yank the battery, then I notice that the boot animation was starting, and it booted up. I just wasn't patient enough. Have you tried changing away from that boot animation, temporarily, to see if the problem goes away? I doubt that's the cause, but you never know. And if it started happening right when you changed boot animations, I'd say the first thing to try would be changing out to a different one, and see if the problem persists. Has this been happening on any ROM/Kernel combo you've tried? Perhaps it's the kernel you're on, have you tried another? Do you use SetCPU?
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
I use different kernels to try them out depending on if I am using a sense based or AOSP rom, and it seems to happen no matter what kernel. I do not use SetCPU.
Whiteice
WhiteiceDMSTech said:
Thank you for the responses.
Just to make sure, it is not the boot animation but the splash screen (Originally the white screen that had EVO on it) that I have changed.
The boot animation screens are usually the ones that comes with whatever ROM I am using. I have done the particle motion boot animation from time to time.
And, anytime I flash I flash in recovery, I always ALWAYS wipe cache and dalvik cache (Unless I am flashing a new ROM, then I wipe everything 2x prior to flashing it.)
I usually let the splashscreen sit for about a minute, maybe 2 if that. I was under the impression that if the splashscreen sits there for more then a minute, then I should battery pull to fix it?
Whiteice
Click to expand...
Click to collapse
Oh I gotchya, so it was the splash screen you changed to the jordan symbol. Yea, I mean, most of the time it will pass by the splash screen in less than 30 seconds, but for whatever reason, from time to time it will sit in the splash for a little longer than normal. If it goes past 5 minutes then yea, that's too long. It shouldn't take that long. Have you tried a different kernel?
Yes, I try different kernel's all the time and it happens on most of them.
It seems that anytime it freezes up on the splashscreen and I reboot, and it still freezes up on the splashscreen that I have to reboot into recovery (AMON 2.3) and wipe cache and delvik cache each and every time for it to clear whatever is going on. Then usually it reboots fine the next boot after doing that until I reboot again and it locks up. Then repeat above.
Thank you,
Whiteice
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/
Hey, I tried to search for this, I looked in every sub forum for the Hercules, but I was unable to find anything...
More often than not, if my phone ever dies, or I turn it off (i.e. flashing something, or just trying to clear out the memory), it gets stuck rebooting... It will go through the boot animation and get to the main screen, and as its going through, on the notification bar it will say "Preparing USB Storage" and there is where it gets frozen and will shut itself off, and in order for me to do anything with it after that, I have to do a battery pull. It was happening when I was on any custom rom and so I tried going back to stock rom, and it is still happening... Is it by chance a setting I am messing with that is causing it? Because when I switch roms, it will seem to fix it for about 1 week... And then it happens again, I have since tried to never turn my phone off, but if I forget to charge it and it dies naturally, that is when I have the BIGGEST problem and it takes FOREVER to try to get it to boot up... Any ideas? Or should I just take it to T-Mobile when it is doing it and have it swapped?
Hey guys,
So my G3 with Cyanogenmod was misbehaving today - the notification led was flashing but the screen wouldn't turn on. I pulled the battery and turned the phone on, and it seems that the problem was low battery. During the boot, the phone turned off.
When I got home, I plugged it into charge and left it for a while. Now I'm trying to boot it up, but it doesn't get past the initial "LG" screen before turning off again.
Now, I suppose the fix to this will be to flash something. I have a backup from the 4th which will be fine, but is it worth just downloading the most recent nightly and flash that over instead of reverting? Will flashing again fix the problem do you think?
OR: is there an easier fix that anyone can recommend that doesn't involve the inconvenience of flashing a backup?
Thanks for taking the time to read guys, have a great day!
EDIT: Fix found - wiped cache/dalvik cache and this seemed to fix it without flashing feel free to delete this thread
My phone does not overheat while in Android because it has the kernel modifing stuff. It's maximum is almost 50 degrees(never reached that hot).
But when in recovery and I'm restoring a backup, the CPU temperature raises drastically, and if the process takes long, it even raises up to 90 degrees and the phone shuts down(to prevent damage to the chip, like on PCs).
I was thinking to limit my 4 CPUs to only 1 when using the recovery so it might not overheat. Is there any way to do that?
I'm using Multirom TWRP recovery.
Don't use charger when you use Twrp. It will make your CPU temp raise. If your phone is still in high temperature, try to shut down for short time.
judy4302 said:
Don't use charger when you use Twrp. It will make your CPU temp raise. If your phone is still in high temperature, try to shut down for short time.
Click to expand...
Click to collapse
My problem is that for some reason, when I enter recovery, the temp raises up drastically. It's automatically at 40+ celsius which is absurd.
And when I start a backup or a restore, it goes up and up, until it reaches 90 and it restarts, without finishing the process and it won't get past the Sony logo. I turn it off, let it cool, and everything works again. I was thinking of installing the Dualrecovery as this happens only in Multirom TWRP. I can backup with the app "Online Nandroid Backup" without any problems. Temp does not go beyond 45 celsius. Only in recovery.
Also I can't seem to install the Dual recovery while being on Lollipop. The phone just simply does not boot. It stucks at the Sony logo, and it keeps my Multirom...
I'll try entering recovery without a charger, and I'll report back, but I still accept any ideas as to why this only happens inside recovery...