Database Info

Annoying boot loop issue

This one has got me baffled and annoyed. So ive updated to fp1 as ive noted in past posts. Ive tried pjb (fp1 version) and the stock ota update, both with tweaked 2.0. I have multiple batteries so wen 1 dies i swap it out for a fresh one. Everything will be working fine til i need to swap out batts, wen i do and try to reboot i get stuck in a damn bootloop and have to wipe data to get the phone to wrk. As u can imagine its pretty annoyin, even wit TB, to have set up my stupid shortcuts n widgets every othwr day.
Before anyone asks i went back to stock first, then the ota update, the fashed rom and kernel. Never had this problem on ep4. U might think tht i should just go back to ep4 then. Well, the problem there is that my email wont sync rite becuz of ozmail notifocation (yes i typed STOP, yes i contacted vzw, they said it should be fixed but it wasnt. Only thing that fixed it was goin to fp1)
So that is my problem. This is my 4th time starting from scratch, so hopefully this time will stick. We shall see.
If anyone has any advice i am all ears.
Sent from my SCH-I510 using XDA

Check out post #585 in the [FP1H][Rom][Cwm][Odin]Tweaked v2.0 thread under the Dev forum. Sounds like the same issue reported there.
EDIT: oops, that was you!

I can't for the life of me think of why that would happen. I also have an extra battery and have NEVER had that happen when swapping them. Has it been the same battery inserted when this happens or does it happen with both? Are they the exact same battery? After turning the phone off to switch do you wait about 30 seconds or so before pulling the battery? Happened with stock kernel and custom FP1 kernel? Stock rom and custom rom? Those are the first things that come to mind that MAY be a factor.

I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!

cnoevl21 said:
I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!
Click to expand...
Click to collapse
Did you test between flashing the kernel and rom on fp1? Might be interesting to see if you can isolate the issue further. I'm at a loss for what I could've done to cause the issue, but I can try to look into it if all signs point to tweaked.

How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?

imnuts said:
How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?
Click to expand...
Click to collapse
I doubt the 3600 is oem because samsung hasn't heard of batteries that big yet :S

I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA

cnoevl21 said:
I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
OK so if you swap batteries and get bootlooped, does the phone work again if you put in the original battery?

Nope. Once in the bootloop the only way Ive found to get out of it is to reflash.
Sent from my SCH-I510 using XDA

I just tried to reproduce you issue by shutting down and swapping in my spare 1600mAh battery. The phone booted up fine.
Not sure if it would have any impact, as I'm not sure exactly what it does, but have you tried wiping battery stats in CWM before booting with the new battery?

I am going to do the wipe battery stats this time around. I always do anyway on a fresh flash just to try n calibrate the battery.
DW I dont think it is Tweaked, its prob my phone or possibly i am screwin up the flash somehow (though i dont know what I could be doing wrong) If no one else has had this issue it cant be the rom.
Heres a few questions that answers could possibly explain the problem. Does it matter what is flashed first? ROM or kernel? And after you power down the phone there is that Team whatever animation, when that goes away is the phone powered down or does it take more time afterwards to be completely powered down? I always wait til the animation turns off, then pull the batt, but maybe the phone is fully off?

I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.

sbradley07 said:
I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.
Click to expand...
Click to collapse
Unless the ROM you are flashing includes a kernel (AFAIK only the ones based on leaks did), there should be no difference in order (just saying).

Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol

cnoevl21 said:
Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol
Click to expand...
Click to collapse
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck

THEbigSWEEN said:
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck
Click to expand...
Click to collapse
never happened until i updated to fp1. i havent tried just using stock fp1 cuz stock is just horrible on this phone. im all reloaded (once again) so we'll see, but if it happens again i will contact verizon about it and see if they will send a replacement.

[Q] Bootloops after battery empties

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

[Q] Phone won't turn on despite everything

So today I woke up and tried to turn on my phone after a good night's charging. I held onto the power button for at least 5 minutes and nothing. I did it again and the phone displayed the boot image for like five seconds and then turned off again. As I am typing this my phone's power button has been taped for about an hour (couldn't find an answer that worked online).
My phone is the G2x. I didn't think that I needed to post it in the G2x forums because I thought the phone model was kind of irrelevant. My phone is rooted and I was running the HellFire Phoenix rom, a CM7 based rom. I had the ICE9 theme on before it was broken, though I don't think thats the problem because its just a theme. I have also flashed a custom kernel called Trinity Kernel. I also used the SetCPU app to UV/OC my phone. At the time, my phone was clocked at like 800 mHz and 216 when the screen was off. 216 seems a little low but on all the other roms I've had (more demanding roms that CM7) I never had any problems.
Can somebody PLEASE help me. Hopefully I didn't brick my phone, though I don't know how I could have. I was always safe when flashing and never did anything "wrong" like flashing something for another phone.
Oh and this is my first post.

Try to re flash a fresh firmware..
Sent from my fingers to your face using xda premium.!

I can't even get my phone into recovery. It doesn't turn on.
EDIT: nvm my phone is working. turns out there is NO electricity going into my room, so my battery completely depleted. now i have an even bigger problem.

Your said:
I can't even get my phone into recovery. It doesn't turn on.
EDIT: nvm my phone is working. turns out there is NO electricity going into my room, so my battery completely depleted. now i have an even bigger problem.
Click to expand...
Click to collapse
what is the problem now..?
Sent from my fingers to your face using xda premium.!

Battery mode

Just grabbed Ann O1 after my vibrant OD'd on me. Updated to gb, used ROM manager to flash cwm 5.0.2.7, but when i flash any aokp roms, eventually the phone doesn't boot. Goes to the "LG" splashscreen, and then a black screen with a white battery shows up. Only way to boot back up is a factory/data reset. Am i supposed to only plug the phone in when it's on? Is this the known "offline charging" issue? Thanks in advance?
Sent from my LG-P500 using XDA

Yes, thats a bug. I think it goes like this.
Earlier there was no offline charging support(when a switched off phone was charged, it booted right up, there was no support for charging in switch off mode).
To correct this they tried to implement this offline charging but it did not work like it should.
hephappy said:
In charger mode, only kernel and charger app is working...
The problem is in charger mode, cable pull out couldn't be detected, so you see charger logo again.
To fix: Pull out charger cable, wait 10 seconds, LONG PRESS (3-5 seconds) power button. If you see charger logo again, LONG press again. It will boot normally.
Click to expand...
Click to collapse
You could also try cm9 tinystream. This bug( weird offline charging support) is removed from it.

I've tried holding power from the battery screen again to boot, but it still doesn't boot. At this point, I'll just chill with the stock gb rom rather than have to deal with my tp2 when the O1 is borked lol. Makes me wish i didn't sell all 10 of the phones i had last year :-/... Yes,.I'm a recovering crackflasher!
Sent from my LG-P500 using XDA

I had this problem too, just reflashed my ROM, wiped everything. Didn't really matter to me.

I've been testing various roms and recently i'm using an ICS AOKP rom that is very fluid and stable. Due to the big rom size, I applied the data2SD tweak that came very handy to me.
The overall experience of ICS is addicting and I think than can no longer go back for the CM7 based roms anymore.
For the custom recovery I'm currently using the amonra 3.06 from this thread: http://forum.xda-developers.com/showthread.php?t=844483 and no more problems have been shown since the CWM used before.

[Q] Hard-brick? :(

Hi All,
I think I might have hard bricked my phone but I'm not sure. I had Synergy r56 and IMOSEYON's kernel for several months and stayed on that even after the JB releases came out. This past weekend I decided to upgrade to the latest release, r147. I wiped data/cache, flashed r147, and it booted up fine. The only problem was that it would appear to reboot about twice an hour (or more). I read that it could be the kernel that was included (Ziggy). So I decided to try KT747 but before that I flashed the newest radio (VRKL3), then flashed KT747 but that didn't help with the reboots. This was late last night and I had to wake up early for work so I decided to work on this in the morning. Woke up to a dead phone -- it wont charge!
With the power plugged in, I pull out the battery and put it back in and the phone vibrates and a red LED comes on. I see the display turn on and I see the battery image (with zero charge) that you usually see when you charge the phone while it's switched off. This image last less than a second and then it's gone. I tried going into download mode but that doesn't work either. I'm wondering if I get a fully charged battery, would that help me boot up. Any ideas??

Yes get a new battery from someone that's charged. If your seeing life with the screen coming on then you are not hard bricked. I would recommend having everything ready to Odin back to stock when you get the battery and go ahead and put it to stock.
Sent from my VS920 4G using xda app-developers app

Guess that's good news. Now to find someone who has an S3...if I can't, can it take it in to a Verizon store? Or is that a bad idea? Thanks for your response!

Not on this phone but I know people would take the droid x into verizon and they would let them use one of their batteries to see if it would boot. Wouldn't hurt trying. And you can get batteries pretty cheap on amazon, external chargers too. Good luck.

Just placed an order on Amazon for a battery/charger set. Will update this thread tomorrow! Thanks again guys!

This has been happening to me since I got my s3. If I let my battery die it's a pita to charge it back up as I have to keep pulling thwarted battery and or get lucky. The battery charging icon would show up and disappear and the red led light would show up, That doesn't mean its charging. The battery charging icon has to stay put to know it's charging. This hasn't really bothered me enough to get a replacement. So my 2 cents
Sent from my SGH-i535 using xda premium

I'm curious have you just left out plugged in for a couple hours? Also what about recovery mode?
Sent from my VS920 4G using xda app-developers app

The no charge after battery dead is a bug in CWM.

Both CWM and TWRP? I just installed TWRP and haven't had this issue before with CWM.
prdog1 said:
The no charge after battery dead is a bug in CWM.
Click to expand...
Click to collapse

Update:
Got my extra batteries less than 10 minutes back. Stuck one of the batteries in the phone and it booted!!!! I'm stoked! lol...anyway, if someone could guide me through what I'd need to do to get back to the latest Synergy JB rom (r147 I believe it is) after I go back to stock because I'm pretty sure I screwed something up with everything I did to get to where I am.
What I've done so far:
Unlocked bootlader
Flashed the latest radio (RLK3 I think it is)
Flashed the KT747 kernel over the one that came in Synergy r147
What do I need to do to get back to Synergy r157? Do you think it's best to go back to stock and re-do everything or is there an easier way? I'm a little paranoid cos I've been out of this game for a while and am not sure what effects my flashing kernels/radios will have on anything I try to undo. Also, if I do flash the Synergy ICS nandroid (r56) that I took prior to flashing r147, will that revert the kernel to Ziggy's?
Thanks in advance guys!

Nevermind. On Synergy r155 now and am having several unrelated issues. Thanks for the assistance.