[Q] Bootloops after battery empties - Nexus S Q&A, Help & Troubleshooting

Hi everyone, I've got a Nexus S 4g, SPH-D720.
This is the second time this happened to me: my phone's battery reached 0% and turned off, I turned it back on after plugging it in, and it turned off again for some reason. Tried to turn it back on, got stuck in a bootloop.
(I was running Apex 1.1.2 at the time that this happened, but it has happened before when I was on CM 9 v4.0 as well. The first time, I was using a calibrator app that told me I had more battery left than my phoen was displaying, so after it powered off I took the battery out and put it back in multiple times to see if the phone would turn on. It didn't. However, I did not do that this time, but the same thing happened.)
I tried clearing cache and flashing the same rom over the current one, but the loop persisted, and the only way to get my phone back was to do a data wipe/factory restore and reinstall everything from scratch.
The first time this happened, I had last backed my app up via Titanium 2 days prior. After the first time, I set Titanium to make backups every night, so the only thing I lost were a few text messages.
Now, I'm afraid to turn my phone if the battery dies in case this happens again and I have to erase everything. Is there any way I can figure out what the problem is? I suspect it is the ClockworkMod Touch Recovery (v 5.8.0.2), but has anyone else had this issue?
I appreciate you taking your time to read all the way through this.

What setting do you have cpu at? If its set too high your system cant handle the boot process correctly. If theres no power to handle the load itll reset itself. Wait until you get at least a solid bar or completely full and start your phone. Dont trust apps to properly tell you your battery percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium

I forgot to add. The recovery is not causing the problem it has to do with battery and/ or rom/ kernel. And its not good for battery to constantly be run to zero. Thats why theres a warning to plug your phone in at a certain percentage.
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium

Processor is set to 100 min 1200 max. Yeah, I did have the same kernel so that's probably it. I'll try not to turn my phone on until it's charged while off. Thanks!
(btw, the "app" I was using was a battery calibrator script)

Your welcome and i was having issues the same way and turned off set on boot and it didnt happen again. Some of these phones are touchy! im sure you know about scripting if you did it! Lol
sent from nexus s running kangyu 2.2.1 rom/ 3.0.31 CM9 Ink kernel on xda premium

Related

[Q] Overheating problems

Well i'm currently running CM7 RC2 with the Netarchy 1.3.0.0 kernel. I'm constantly having my phone overheat and reboot on me in the middle of the night. Overheating typically only happens while charging, but when it does i have seen my phone get up to 102 to 107 F. I had my alarm set for this morning, when i woke up my phone had a completely black screen with the buttons lit up, and the phone was very hot. So i had to do a battery pull, after i pull the battery it boots up normally and starts to cool down. Does anyone have any idea what the problem could be? Thanks in advance. Plus i have found that my phone still reboots, sometimes it will randomly reboot when i'm not doing anything and it will show my boot animation but it's not full color, and slightly dimmed. And the only way to boot normally is to do a battery pull. This same problem has happened on my wife's Nexus S. I have her set up with the same kernel and rom i'm running.
Just a question. Do you have the main settings set on boot?
I had exactly the same happen last night with CM7 RC2 and Netarchy 1.3.0.1. The phone was really hot and I was worried it had been damaged being stuck like that for so long. It seems fine now though.
What do you mean? im not using setcpu, and my phone is not OC'd. @phillevy mine has been doing this everyday it seems like, when it gets that hot it really worries me too.
Are you using the phone to tether?
Nope i don't use tethering at all, i'm constantly connected to wifi at home.
This is the first time I've had this happen where the phone as overheated like this, although I've had a few reboots to the dimmed cyanogen bootscreen. I'm using setcpu and have a screen off profile of 100-800mhz.
Looks like I am going to try rc3 and see if these issues still persist.
Sent from my Nexus S using XDA App

BAMF Sense 3.0 GB RC2 (I Busted Something)

I must have screwed something up as my phone is stuck in some sort of power cycle. Everything seemed to be working fine including several restarts after doing configurations and learning how the LCD density works. I do a shutdown of the phone I see the shutdown animation, but the screen still has the backlight on. It never seemed to actually shutdown so I hit the power button and the screen goes out. I go to boot into recovery to create a backup of my settings and like a moron i didn't delete the MR2 upgrade. I answered no to the install up the upgrade and reboot the phone. This is when the power cycles actually started I see no signal, 1x the phone locks up then restarts. I reflashed the radio in case it become corrupted and no change. I cleared the cache and the Dalvik to see if that would work NOPE now it's stuck on the DAS BAMF the baddest! boot screen. I did install the latest dreamkernal for the bluetooth options. Other than starting to install apps I can't think of what I may have done to do this. I don't have a problem reflashing, but I hate to cause this problem again. I did wipe 4x the factory, cache, Dalvik before flashing the rom and verified the md5. I know it's probably not possible without knowing exactly what I did, but any ideas or suggestions?
You've got wiping data/cache/dalvik/bat stats covered. I think 4 times is overkill, but certainly not hurting anything.
When you flash a ROM, are you flashing anything else....other mods, etc., before letting the phone restart?
Do you have a good radio? Try MR2 if you're not already, some have reported bugs or issues with MR2.5.
Check the md5 of both the ROM and Radio.
I would try to shut down the phone then pull the battery then boot bootloader and reinstall radio. If that don't work I would try a full wipe and reinstall
Sent from my BAMFBOLT using XDA Premium App
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Can you restore from a backup?
dms76 said:
I flashed the latest dream kernel after flashing bamf and using MR2 verified MD5 before flashing. I did try a battery pull as I had to remove the sd card to delete the radio in order to go in recovery. I did do a reflash since i would have to anyway. I was just trying to figure out what I did wrong in my configuration and I think I did. When I turned the phone off I thought something was wrong since it looked like the backlight was still on. I think I corrupted something during shutdown that caused the problem. I noticed the phone seems to take a little longer to shutdown then with the rooted stock. I'm paying better attention so we will see. Probably all just human error
I also changed my min speed to 368 since i read some phones don't like 245. However I am not sure what the best Governor is to use so I left it with the interactiveX defaults.
Click to expand...
Click to collapse
AFAIK all phone run fine at 245, its the 184 that doesn't play nice with some phones. Also turn off fast boot in the Settings>Applications menu, some people seem to have random problems when that is turned on.
I was in the process of trying to make a backup when something broke. It was actually easier to start over because then I could go setting by setting to see what I did wrong. I think it was just how I shut it down that fubar the whole darn thing. It seems to be working correctly now and I created a backup as well.
184 not 245 gotcha and thanks! That could save some battery life I would assume. No matter how well built there is still a better idiot!

Hot reboot app killed my phone

Well I used a hot reboot app for about the 50th time tonight, and it decided to kill my phone. It gets stuck at the AT&T screen and won't go past it. I've left it there for half an hour (don't wanna go too long because I don't like burn-in) and it just stays there. Tried battery pull, nothing. Running infusion kernel 2.0 core B (or whichever is the 200mhz stepping one) it was overclocked and set to performance mode at the time, which I have a feeling is what broke it. I'd do anything to fix it that doesn't involve completely re-installing the whole ROM and kernel and everything, I had to do that one night and it took about 12 hours. And I just can't be doing that with classes now.
So yes, an app has actually broken a phone for the first time in the history of ever.
If it helps at the very least in the recovery menu I can mount USB storage. I would try deleting the voltage controller boot settings but I don't think you can do that without actually having the phone running.
SNIPPY SNIPPY, WIPE ON (Mod Edit) clockwork MOD FIXED IT, i think.. probably jinxed myself there.
TheNetwork said:
Well I used a hot reboot app for about the 50th time tonight, and it decided to kill my phone. It gets stuck at the AT&T screen and won't go past it. I've left it there for half an hour (don't wanna go too long because I don't like burn-in) and it just stays there. Tried battery pull, nothing. Running infusion kernel 2.0 core B (or whichever is the 200mhz stepping one) it was overclocked and set to performance mode at the time, which I have a feeling is what broke it. I'd do anything to fix it that doesn't involve completely re-installing the whole ROM and kernel and everything, I had to do that one night and it took about 12 hours. And I just can't be doing that with classes now.
So yes, an app has actually broken a phone for the first time in the history of ever.
If it helps at the very least in the recovery menu I can mount USB storage. I would try deleting the voltage controller boot settings but I don't think you can do that without actually having the phone running.
SNIPPY SNIPPY, WIPE ON (Mod Edit) clockwork MOD FIXED IT, i think.. probably jinxed myself there.
Click to expand...
Click to collapse
It is not unheard of for apps that don't shut a device down properly to cause data corruption. Glad you got it fixed.
Thread closed

[Q] My phone keeps turning off.

My phone will randomly turn off out of nowhere. Earlier today I had 17% battery and it just turned off instantly. I turned it back on and had 87% battery. About 10 minutes later it instintly turned off again and when I turned it on I had 25% battery. It's getting really annoying. I never had this problem before, nor have I ever dropped it.
Is there something wrong with the pins on the back of the case or something?
Thanks in advanced for the replys.
Hypercore said:
My phone will randomly turn off out of nowhere. Earlier today I had 17% battery and it just turned off instantly. I turned it back on and had 87% battery. About 10 minutes later it instintly turned off again and when I turned it on I had 25% battery. It's getting really annoying. I never had this problem before, nor have I ever dropped it.
Is there something wrong with the pins on the back of the case or something?
Thanks in advanced for the replys.
Click to expand...
Click to collapse
Hi,
A little information is always useful when seeking help.
ROM,
Radio,
Kernel,
Mods,
Themes,
I have the same issue, my phone turn power off randomly, sometimes on high percentage of battery and sometime on low level, some days it works fine and some days it happen 5 or 6 per day , the weather so clod now so i'm sure it's heating
my phone info:
Android Version: 2.3.4
Kernal Version: 2.6.35.14
Rom: Android Revolution HD™ 3.6.8 XE | 4.1.8 Sense 3.5
Any Help will be appreciated
Thanks
tantan911 said:
I have the same issue, my phone turn power off randomly, sometimes on high percentage of battery and sometime on low level, some days it works fine and some days it happen 5 or 6 per day , the weather so clod now so i'm sure it's heating
my phone info:
Android Version: 2.3.4
Kernal Version: 2.6.35.14
Rom: Android Revolution HD™ 3.6.8 XE | 4.1.8 Sense 3.5
Any Help will be appreciated
Thanks
Click to expand...
Click to collapse
nvm................
i had this same issue, for me it helped to move all my apps back to my SD card and reformat my sd card. Since then it happend once again and that was after i dropped my phone and my sd card unmouted. but besides that occasion havent had it for about a three week now.
might be related to moving apps to sd card, not sure do if this actually started the problems for me.
I m on stock ROM and i live in europe
I've got the same problem since about a week, phone randomly turning off. Though never when i'm using it, alsways when the phone is in standby mode, including the strange battery level jumps. I thought it was an app so i did a hard reset, but the turning off remained. I switched from Sense to Launcherpro, still no change.
My phone runs on stock rom, 2.3.4, Sense 3.0, Kernel 2.6.35.13
This weekend i'll backup my SD-card and reformat it, if this helps i'll let you know.
Try a new battery
My battery's only 6 months old!?
Noppe said:
My battery's only 6 months old!?
Click to expand...
Click to collapse
Mine had 2 months
Mains said:
Mine had 2 months
Click to expand...
Click to collapse
Been there, done that; problem still exists... I have tried a new battery new software (factory reset and hard reset in the repair centre), boardsap, other simcard, other sd card... The problem still is there, I am trying to get a new phone. The problem is the phone ... My question is is this only a normal sensation problem or is this also a problem on the Sensation XE?
My phone is starting to show the same symtons again. Overnight it also has shut down. So i guess the sd format did not get rid of the problem. But on my phone it definitively made it less frequent. As before the format i had it 5 times a day and now i have it once a 2 days. Probably will get worse overtime as the last time i had it.
snah65 said:
Been there, done that; problem still exists... I have tried a new battery new software (factory reset and hard reset in the repair centre), boardsap, other simcard, other sd card... The problem still is there, I am trying to get a new phone. The problem is the phone ... My question is is this only a normal sensation problem or is this also a problem on the Sensation XE?
Click to expand...
Click to collapse
Let me know if u succeed, i contacted HTC today and they told me to factory reset my phone. Not looking forward to that, do. Might do it next week.
forgot to ask, did HTC give u those out of warranty our did u buy them yourself?
Let me ask you a question. Have any of you polished your covers to chrome? I have had the same issue of my phone turning off in my holster, but only when I have my polished case on it. When I put my spare one that has not been touched, the phone works flawlessly. Not sure if there is some weird static buildup that is shorting the phone. Also, to get it to turn back on, I have to pull the battery first.
I had the same problem on my Sensation, turning off randomly (not reboot). And the battery would display wrong reading once it is back on. Initially I thought this was due to bad rooting or a custom ROM issue, I restored back to stock and right there on the language selection screen on first start and without the SD card, it went off. That made me sure it was a problem something else. I thought then it would be due to bad charges in the battery, used different charger to charge, didn't work, then I replaced the battery, somehow the problem stopped and when I insert back my old battery the problem still didn't come back. I don't have an explanation to this behavior. It works fine now.
That sounds weird, I didn't polish my back to chrome... And I also do not need to pull my battery to turn it back on. A few times I had that it turned of and it would directly turn of again after it was restarted (home screen loaded). The only way to get out of that was to hook it up to the charger.
Sent from my HTC Sensation Z710e using XDA App
It's really odd. I can't even use the phone any more.
When I turn it on, as long as the screen stays on it will not turn off.
Once I lock it and put it in my pocket, about 40 seconds later it shuts off. This isn't just powering down, it just instantaneously shuts down. I also can't turn the device back on no matter how many times I press power, I have to physically pull the battery and put it back in to turn it on.
One more thing to add: My girlfriend smacked my phone out of my hand once accidentally and the case doesn't click in. It stays in place but if you hold the case and attempt to take it off it falls off. I'm thinking it could possibly be a problem regarding the pins, but from what I know the pins only control the screen.
Edit: One last thing, when it's connected to my computer and being charged it never shuts down.
Read
I had this same problem two days ago. Left work and my phone just shut off while in my pocket. I was running sense-o-maniac Desense 3.5. It continued this behavior for the next day. Also my battery was showing random charge percentages. There were two issues"
1. I was had used the battery calibrator app from the market to erase my bat stats - problem - it kept erasing my battery stats.
2. I was using set CPU and after reading many dev forums about such issues, I realized that setting the idle below 384 mhz, it causes the phone to random reboot.
Once I conducted a complete wipe and flashed MIUI I was good. no issues.
My Suggestion: Try a complete wipe, then Android Rev HD wipe, then reflash, Wipe cache, Davlick Cache, Fix permissions, then reboot. Drain the battery, then recharge to 100% and wipe bat stats
TMO US Sensation 4g
Baseband:10.56.9035.00P_10.14.9035.01_m
Kernal: 2.6.35.14-Bricked-v1.5-ondmnd-1536-192.show-p1984
ROM: Sexy MIUI 1.12.9.01
2nd factory reset and reformatting the microSD did not solve my problem...
@anari101: I'm a big fan of custom roms, but currently my sensation's still running a stock rom. I'd rather not void the guarantee at the moment by flashing it as the phone isn't functioning properly. If i can't fix this problem without flashing a custom rom, i can return it to HTC and hope for a repair or a new device/battery...
Anybody got any other ideas?
i also dont want to root a phone that might have problems.
I did not do any factory reset yet, but the problem is comming back now i have once a day it just shuts down. The last time when i picked it up and pressed the power butten the screen was white for a split second. However if i look at my history of battery monitor widget it stopped recording an houre earlier. clueless to why this happens.
If your phone is rooted, I agree with anari - use current widget and battery calibration to re-calibrate your battery. Let phone charge all the way and then some like another 2 hours. Use battery calibration to get rid of batterystats.bin. Let battery completely drain (Hopefully it doesnt shut off in the process). Definitely seems like something is wrong with your ROM's battery settings.
If you dont have your phone rooted. Have you received any updates lately? If a factory reset didnt help - go to your local Tmobile and just have them ship you a new phone. Not worth dealing with the issue and they can get you a new phone within a couple days.
EDIT: If you have NOT factory reset your phone. You can try to copy all data off your SD card, reformat it. Insert it, let the phone recognize and set it up then add everything back on. If that doesn't work, factory reset (after using Astro to backup all apps). If THAT doesnt work, go get a new phone.
I am having this same problem. Mine always happens when I take my phone out of my pocket after it's been sitting for a while. It also seems that my battery is always around 30-40 percent. It will unlock then just turn off. I turn it back on and after about 30 seconds it turns back off. The only way I can get it to stay on is plugging it in to the charger for a couple of minutes after turning it on and it won't do it again for a while. I don't know what it is but I'm thinking battery or SD card.

I think my sidekick is dying!

In the last few weeks my sideckick "reboots" itself, as it don't ask for the pin code.. It just reboots..
But now, he reboots and the first screen that appears that says T-mobile Sidekick 4g Samsung, appears, for about 5 seconds, turns off, and reapers, that on continuous loop!
The first time it happened, I took the battery off, and when I put it back, without me turning the phone on, e started doing the loop by itself..
After a few tries taking the battery off, he came to life..
But yesterday, that happened again, and stayed that way the whole evening.. Until it run out of battery, I went home, tried to recharge and it came to life again.. I was about to going to sleep and he rebooted again, and started the loop again.. It stayed all night that way, and in the morning, it was turned off.. I thought it was the battery again, so I plug it in, and it now is in continuous loop trying to charge the battery but before it starts, it turns off and does the loop again..
I have glourious overdose rom, but never had the problem except in the last few weeks!
Heeelp!
EDIT: It was in continuous loop trying to recharge, but I unplug it, and it turned on! It had 2% battery, and is now charging on.. I rebooted in recovery, and wiped cache and dalvik cache.. Probably it will happen the same all over again during the day..
I am considering changing rom..
It could be a battery issue, but the first thing i would do is dirty flash the same ROM on top of this one (no wipes) and see if it helps. If not do a full wipe then flash a new ROM. If this still dosent fix this then i would go back to stock with hiemdall and choose to repartition at the same time, then reroot and flash a ROM.
Also make sure the contacts to the battery are clean and touching fully, if it is a battery, at least they are cheap!
hope it all works out!
This may be something that happen during root that messed it up
So if demkantor suggestions didn't help odin to kg2 then root an flash a new rom should help if not its a really bad issues with either the battery or other hard ware (like the power button broke an is constantly pushing it)
If you do fix it you want to make sure you make a backup via red/yellow cwm
Sent from my SGH-T839 using xda app-developers app

Categories

Resources