At morning i take my phone assumed stand by and when i pushed the power button he doesn't wake up. I try several time to reboot it normally( doesn't work), in recovery (doesn't work again) then i tried in download and it works !
I flashed the last kernel Semaphore 1.2.6 and it reboot kindly. But in the yesterday evening i left it with 67% of battery and when i rebooted it after flashing the battery was empty.
The question is :
Why the phone wouldn't reboot without kernel reflash ???
And why it emptied the battery like that ???
What software / Rom are you using?
I also had a lot of problems with semaphore but version 1.2.5. I was on CM9 then and used midnight, it was faster and less battery consuming.
I suggest to flash another kernel, seems kernel related. Maybe smart to use a kernel cleaning script before flashing another kernel.
I was on CM9 build 2012/05/07 with the semaphore kernel.
Related
Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone
I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?
fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)
jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....
BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks
farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.
Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.
Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689
My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks
Read Bejda's post, one post above yours.
Taptalked u see
wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes
I'm using Doc's master Rom Ics V8 and the semaphore kernel with Huge Memoroy (Sbm I Think ) and the phone has been having FC lately and when I tried to reboot it just got stuck on booting... any Idea why??
Normally, take the battery out and wait a few minutes - reboot...
If that does not work try to re-flash the rom in recovery etc.
This always works for me.
Apologies for opening a new thread for this. I am unable to reply on the dev thread as I have less than 10 posts. So in reference to the following post, I'd like to contribute some experience I had in the last two weeks.
http://forum.xda-developers.com/showthread.php?t=1627689
Across the space of two weeks, I have had a chance to note this symptom on three devices.
Device 1 SGS i9000
Rooted phone and have been on CM9 for as long as I can remember. Wake up one morning to find phone with BLN on, but no ability to wake the phone (power button, home button, volume buttons, nothing works). Popped the battery out, and the bootloop / no recovery went on forever. Had to Odin flash back to Stock 2.3.6 to start again. Since then, any CM9 (nightlies or RC2) attempted always end up in the bootloop, i.e. stock > flash rom, first boot = bootloop. I figured then if I had to go back to 2.3.6, I'd rather go to JB. First JB tried was HellyBean, and the same thing happened. It was only trying pawitp's current alpha CM10 that it worked. Days later reverted back to ICS (Paranoid Android v1.6) due to lags and bugginess.
Important to note, the CWM kernel I have gone through are 6.0.0.3, 6.0.0.8, 6.0.1.0. And Paranoid Android put me back to 5.5.0.4.
Device 2 SGSi9000
Rooted phone and have been on CM9 for as long as I can remember. Phone cut off and rebooted in the middle of a phone call and ended up in bootloop with no recovery. Exactly the same symptom attempting to get the phone back into any of the CM9 roms (nightlies or RC2). Ended putting the phone on Paranoid Android as well.
Device 3 HTC Sensation
Had a lot of trouble trying to flash CM9 on this using CWM. Random bootloop with no recoveries. CWM at that time was 6.0.0.8, which I had lots of trouble flashing Gapps on. More on this device posted here: http://forum.xda-developers.com/showthread.php?t=1786703
And finally, one other observations across all these devices. Somehow with CWM v6.x.x.x I had rather poor battery life. For instance, on CM9 Nightly 07/23, say I started with 100% charge in the morning at 8am, by 12pm, I would be looking at 80% left. Once a week, I will let the phone shut itself down on low power, and charge without switching the phone on. On any other evenings, I would plug the phone and leave it charging overnight, e.g. at 10pm with only 30% left. I have constantly noticed that within a few minutes, it jumps back to 40%, which is rather odd. A 10% charging achieved within minutes is rather unusual.
I have also noted that, when the SGS i9000s ended in the bootloop / no recovery situation, the phone can never be charged. Plugging the phone for charging will the a blank battery icon lit up, with the swirly thing on top of the icon appeared frozen and it stays that way.
Being on lower version of CWM, in this instance, v5.5.0.4., I can observe the units (observed being the keyword here) charges "normally", i.e. no funny 10% charge achieve within minutes. Also, battery life are much better as well, i.e. only 10% drain between 8am (100%) to 12pm (90%).
So, not being a developer but someone that likes to tinker and observed:
- Is it possible that newer version of CWM potentially have some impact to battery life?
- Is it possible that how CM9 is being flashed onto a phone has potential issue? I find it a bit disturbing on an initial flash from stock to CM9, I had to pop the battery out after the flash initially loads a new CWM onto the phone. Then start the flash again with the newly loaded CWM.
I am hoping all these I have experienced in a short amount of time can be helpful to potentially looking into where issue might be. Most people have one phone and tested across different kernels and ROMs. I had the luxury of testing across three devices on a narrower choices of kernels and ROMs.
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yup, on every occasion I mentioned above, wipe (system/data/cache) are part of the ritual. Just didn't mention them.
I just think the battery-pulling feels rather odd. Can understand why it's needed, but just feel odd. Wondered if it'd be better to keep kernel and ROM separate, e.g. flash new kernel via Odin, then simply do ROM. This might be a 'cleaner' method perhaps? It feels almost like flashing kernel as part of the process is like modifying Windows files whilst still in Windows, then do a reboot.
For now I have fear against v6.x.x.x kernels. But will likely go back to it once CM10 is stable. We'll see.
I installed Eryigit's Android 2.3.6 ROM onto my SGP 5 and have this battery charging boot loop. Are there any solutions for this yet?
I've flashed CM 9.1 rom 2 weeks ago. Everything was perfect (well, ok camera app was a bit laggy). I installed it through CWM, like wiki says.
2 days ago, I was using phone as Navigation, and battery depleted to 0 (phone switched off). When I plugged it into a charger, battery charging animation was displayed, then phone switched off and so on (loop). Same situation is when I power on. CM logo endless loop.
Recovery doesn't start, download mode is working tho.
I checked different battery, same thing.
Is it software related problem ? Should I just flash phone again via ODIN or Heimdall?
I had something similar like this a few months ago because my nephew was pressing random buttons. I did indeed just reflash the phone again. Lucky for me I had a backup of my data so that fixed most of my problems.
Hope you figure it out,
Currently, I've flashed hardcore Kernel (CM wiki page) to flash CM9.1 rom.... it gives me Status 7 error (get.prop("ro.product.device")). Same with CM 10 Nightly.
Flashing Slim ICS gives me Status 0 error.
What should I do?
Hey just flash stock GB firmware via Odin then u r good to go...
Do post results
If my post helped, don't mind hitting THANKS
Yes it helped. Thanks.
Strange tho, stock 2.3.6 feels faster than CM9.1
Hello,
FYI; I'm running a Galaxy S i9000 with Slim Bean 3.1 (4.1.2) and semaphore kernel 2.6.5 (was 2.6.0)
So today I woke up my battery was a low at 5%. But everything was normal and had been for a long time. I fell back asleep as I have the day off.
Woke up an hour or two later and my phone was dead. So I put my phone into charge.
Came back about 40 minutes later, enough charge to boot the phone, check my messages, but as I pressed the power button it just went into bootloop. And it hasn't done anything but that since. Every time I try to turn the phone on, the Galaxy S logo appears, then semaphore kernel logo appears, then disappears and reappears and then the whole process repeats.
And I tried plugging in the phone again to charge, but every time I do, the empty battery icon appears, it disappears and reappears, then turns off and turns back on again to do the exact same thing.
So on and off charge, it won't do anything but repeat a few steps over and over.
I cannot enter recovery, cannot boot the phone, the phone does not respond to being plugged into the charger, but I can enter download mode.
So I started googling and trying to fix my problem.
So far I have tried:
- Several three button combos to enter recovery.
- Using ADB to enter recovery (but as the phone isn't on, this doesn't do anything)
- Pulling out the battery, putting it in holding three button combos
- Trying different batteries
- Charging the phone
- Flashing semaphore JB 2.6.5 using ODIN
So basically the phone is bootlooping; when in charge, charge looping (is that even a thing?); and won't respond to any attempts to boot into recovery or boot at all.
I'm trying to avoid just wiping the phone using ODIN and reinstalling from GB to JB (which I have done before, and know how to do).
I'm currently leaving it to bootloop until the battery is actually dead and then I'll see if I can try all over again. Doubt it though.
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Bejda said:
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Click to expand...
Click to collapse
What would that do?
It can be or battery this happens with me if the battery is dead it will only go into download mode.....
Sent from my GT-I9000 using xda premium
Zorigo said:
What would that do?
Click to expand...
Click to collapse
Flash it like you did with semaphore .tar,there's good chances your device will just boot fine as if nothing happened.
Such boot loops are a long unexplained story but if you want to use semaphore try 2.6.6 version if it matches your rom,I was having many cwmless bootloops like you had and it didn't happened anymore since this version.
Ahh thanks for the info
I just got impatient and reinstalled everything from the ground up so everything's okay now and I have semaphore 2.9.x on slim (4.2.2)