yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Bejda:
@stratosk,i'm only saying that seeing the last_version in /system provided by latest Devil kernel that comes with:

Linux version 3.1.10 (Devil2_0.94_i9000_CFS_BLN_CMC) (gcc version 4.4.3 (GCC) ) #635 PREEMPT Thu May 24 19:27:57 CEST 2012

Makes me remind (mainly cause of the PREEMPT word) of the last_kmsg file i had when using previous devil kernel version and when my phone did that:boot/devices logo>kernel logo>device logo >and surprise(surprise cause i'm used to cwmless bootloops)! Finally device booted for real,bootanimation etc... and then i was able to catch a last_kmsg of what's happened.

Cause that last_kmsg was saying:

[Long serial numbers lines...]

Internal error: oops: 17 [something with PREEMPT]

Unable to handle Kernel... virtual adress...

Kernel panic - not syncing fatal exception.rebooting..

The fact i didn't had any Bod today despite i tested lots of configurations and did lots of reboots with latest Devil kernel can't be considered as a proof indeed... just an idea/feeling i had...

But still, from my user without knowledge point of view i still consider that up-quoted last_kmsg error is one of the main thing to check, that's why i reported my little and fast done research on that "Internal error : oops : 17".
[Galaxy S I9000 Android Development] ZioGTS:
I must be extremely lucky, but I'm not having bootloops since I stopped wiping cache and dalvik before flashing a new ROM or kernel (or even both in a row)...
[Galaxy S I9000 Android Development] tiwag:
That's true for me too. Made the same experience. After a while it booted normally again. :-)

Elite Ics ROM RC1.2

Semaphore kernel 1.2.0S

tapatalked using recycled bits and bytes
[Galaxy S I9000 Android Development] pbecks1963:
I vote for: that dev's "remove" boot animations from there kernel/rom so that we can see what the phone is doing at boottime. Maybe enhance the output at boottime? (about "Enhance", "verbose" is the word that comes to mind, show more output when running commands)

I know: thats why we have logs... :-)

Verstuurd van mijn GT-I9000 met Tapatalk
[Galaxy S I9000 Android Development] AsfaltSame:
Maybe this can help?

I am on CM9 nightly and i flashed Devil2_0.94_i9000_CFS_BLN_VC_20120524.zip with CWM and got bootloop. flashed Semaphore_ICS_1.2.0s.tar with odin and got bootloop. flashed	Semaphore_ICS_1.2.0.tar with odin and everything is ok. ticked off processor performance "set on boot" and rebooted. flased Devil2_0.94_i9000_CFS_BLN_VC_20120524.zip with CWM again and everything is ok now.

P.S. I never cleared cache or dalvik
[Galaxy S I9000 Android Development] test123456789012:
Maybe a new lead- for me at least.

Current stable setup:

ROM: update-cm-9-20120524-NIGHTLY-galaxysmtd-signed

(previous) Kernel: Semaphore 1.2s

Everything else: F4k's 720p playback fix for bigmem kernels.

What I did to get a bootloop:

Went into Semaphore CWM, installed latest cm nightly (update-cm-9-20120528-NIGHTLY-galaxysmtd-signed), installed latest gapps and applied F4k's fix.

rebooted the phone from recovery menu.

Phone boots up normally. 2nd boot okay, too.

Went back into CWM, installed semaphore 1.2s.

rebooted the phone from recovery menu.

Phone boots till 2nd semaphore logo then loops, no CWM.

What didn't solve the bootloop:

Went into download mode and flashed Semaphore 1.1.1s via Heimdall:

Phone booted till the second appearing of semaphore logo, then loops. No CWM.

Went into download mode and flashed Semaphore 1.2s via Heimdall:

Phone booted till the second appearing of semaphore logo, then loops. No CWM.

Went back into download mode and flashed Icy Glitch v14 B6 via Heimdall:

Phone boots till logo then loops. CWM accessible this time.

Back to download mode and flashed Semaphore 1.2s via Heimdall.

Phone booted till the second appearing of semaphore logo, then loops. No CWM.

What solved the bootloop:

Went back into download mode and flashed Icy Glitch v14 B6 via Heimdall:

Phone boots till logo then loops. CWM accessible this time.

installed latest cm nightly (update-cm-9-20120528-NIGHTLY-galaxysmtd-signed), installed latest gapps and didn't apply F4k's fix.

rebooted the phone from recovery menu.

Phone boots up normally. 2nd boot okay, too.

Went back into download mode and flashed semaphore 1.2 via heimdall:

Phone boots up normally. 2nd boot okay, too.

Went back into CWM mode and flashed F4k's fix:

rebooted the phone from recovery menu normally into ROM two times.

Went back into download mode:

installed semaphore 1.2s via heimdall.

rebooted the phone.

Phone boots up normally into ROM every time now.

I don't know what's causing this odd behaviour but I think it has something to do with the large ram versions/patched ROMs. Could this be?
[Galaxy S I9000 Android Development] BlueFlame4:
Worked for me as well o0 Thank you!
[Galaxy S I9000 Android Development] cdmackay:
Just as a data point, I've never used such versions, and have never had a bootloop, despite flashing many, many, times.

Do we have any bootloop sufferers who get problems with "regular" versions?
[Galaxy S I9000 Android Development] test123456789012:
After my experience with the -s versions, I think I will definitely try to resolve any future bootloop issues with the non-s-version, like I did in my previous post, again.
[Galaxy S I9000 Android Development] Bejda:
Maybe but bootloops/no recovery issues appeared before large ram kernel versions and the two .tar that usually helps me to recover from this are initial cm7 and... Mnics LR.tar

At the moment i wish i had bootloops with Devil kernel and solve it with Devil 0.94 .tar version cause of the last_kmsg (and last_kmsg.bak) he produce at every boot.
[Galaxy S I9000 Android Development] stratosk:
Thanks for your detailed report.

This is weird because you said you flashed twice 1.2.0s. The first time didn't resolve bootloop and the second time didn't cause a bootloop.

I wonder if:

1) this is random

2) we are prettry sure that we can't access recovery.

With my second point I mean that when the phone is in bootloop might be a little tricky to boot into recovery. Sometimes it needs a second or third try to do it. Also it may be useful to remove battery, put it back in and the use the 3 button combo to be able to boot in recovery.

My major concern is why recovery is lost. Bootloop may occur by bad configuring OC, voltages etc.
[Galaxy S I9000 Android Development] test123456789012:
I see your point! I didn't have any settings enabled that aren't accessible via semaphore app. So no OC, no UV or the like was applied. Low memory Killer settings to default. No deep idle, too.

I don't care if CWM is lost or if it is extremely hard to get into. ;) I didn't try hard to get into CWM /this/ time, but in the past, whenever I had a bootloop, I was so afraid to flash something else that I tried /every/ possible way to get into CWM. Pulling battery was one of them. Maybe you read my first post –*that time I tried hard but did not succeed.

It seems pretty random for sure, though. I will report back, if my next nightly-update will cause that problem again.

Edit: Do you have an explanation why Icy Glitch recovers CWM virtually every time I flash it?
[Galaxy S I9000 Android Development] stratosk:
No offence at all but I mean that the point of this thread is to resolve the issue of bootloops with the concurrent loss of recovery.

You can have bootloops easily if for example OC/UV your phone too much (of course it's not your case) or if using some bad configuration.

If you can boot to recovery (even if this requires a bit of effort) and clear your init.d and recover your phone then there is no issue.

I don't know why Glitch helps you every time. There are also many reports from people that flashed a different kernel from that they used before and the problem solved.
[Galaxy S I9000 Android Development] LinkinParkmetre:
I am on CM9 nightly and i flashed Devil2_0.94_i9000_CFS_BLN_VC_20120524.zip with CWM and got bootloop. flashed Semaphore_ICS_1.2.0s.tar with odin and got bootloop. flashed Semaphore_ICS_1.2.0.tar with odin and everything is ok. ticked off processor performance "set on boot" and rebooted. flased Devil2_0.94_i9000_CFS_BLN_VC_20120524.zip with CWM again and everything is ok now.

P.S. I never cleared cache or dalvik

This solution IS MAGIC

It should be in the front page.

Even if this is not a serious fix, it's just a workaround, but a working one !

It would greatly help to much people like me who are in trouble

PS: I got bootloop by simply choosing reboot in recovery from Anarkia Rom 0.3.0, kernel devil 0.89
[Galaxy S I9000 Android Development] test123456789012:
None taken! :)

My point was that if you cannot get into recovery then there is no difference if CWM is actually there or not. Will try harder to get into CWM next time (which will happen, I fear).

I mentioned Glitch because maybe he does something different than others, more similar to GB or so.
[Galaxy S I9000 Android Development] stratosk:
I could place this solution on the OP, but I'm afraid it does not work for everyone.

A simple example is LinkinParkmetre case. He flashed a different kernel and it worked.

I agree with you, if you can't get into recovery, you have problem and this is what we try to resolve here.
[Galaxy S I9000 Android Development] LinkinParkmetre:
Even if I doesn't work for many people, it could work for some.

Maybe list possible workarounds in a list in the OP

Try solution 1 (semaphore kernel trick..)

then

Try solution 2 (fixrecovery.tar..)

then...

etc

then a poll/vote to know which solution worked for who, or if none worked

Attach semaphore kernel file & devil kernel file (if their author agrees), odin 1.85 file, galaxy s drivers (in case of...).

You will be able to know if one solution is more efficient than an other, all users could at least try to recover their phone, without searching unefficiently in (too) many threads & posts...
[Galaxy S I9000 Android Development] karol1981:
Bootloop welcome :/ dalvik and cache cleared and... :mad: every time when i cleared dalvik and cache ,catch bootloop.

Nothing help, try midnight.tar, sem.tar , heimdall dont work with my phone :/

Rom LBR1.1.1

Kernel semaphore 1.2.0s
[Galaxy S I9000 Android Development] Bejda:
Devil .tar? fixrecovery.tar? cm7 initial .tar?

You should try cm7 initial,good chances to work:

http://db.tt/Dd1sgMFg

When released 3 buttons Cwm could take some time to appear wait a little even if you see again your device boot logo.

As it's an old Cwm you'll have to flash another ics kernel zip with it and reboot system.
[Galaxy S I9000 Android Development] karol1981:
Fixrecovery.tar only back my recovery, flashing witch sem.zip,midnight.zip only get boot to recovery .
[Galaxy S I9000 Android Development] FadeFx:
Try flashing ezboot-gingerbread and then your usual kernel.zip from recovery, that helped me today. If it helps you please confirm...

------------------------------

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] danieleb89:
hi, the fastest way I found to fix bootloop issue is:

flash cm7-initial-kernel.tar and then flash MNICS-20120523-2-LR.tar both with Odin, so fast and painless...

I have a question, is there a way to obtain the same result using Heimdall?! (I'd like to use linux! :P )
[Galaxy S I9000 Android Development] UltrasFrankfurt:
extract the zImage of both and enjoy

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] danieleb89:
cm7-initial-kernel didn't help me to get the recovery with Heimdall, I hope not to have to try it again...
[Galaxy S I9000 Android Development] m4rcus:
<3 u dude. so.much.thanks.
[Galaxy S I9000 Android Development] ryanmat:
Didn't see this mentioned on the thread yet, and if it has feel free to disregard...

On both Glitch and Devil kernel after flashing a new ROM (CM9 nightly specifically) using TWRP, as soon as I reboot I end up in the bootloop/lost recovery. I then can recover using the ODIN .tar kernel, good thing for nand backups! :)
[Galaxy S I9000 Android Development] chris59264:
The topic created by stratosk is to solve, why the recovery goes!,,,, WHY? ? No solutions to the problem, just why! Thanks all
[Galaxy S I9000 Android Development] stratosk:
The topics was created to for both reasons. To know why and to resolve it (if possible).

BTW, I added a bootloop detection mechanism in latest Semaphore version.

A script tries to identify bootloops and then forces the phone to recovery in next boot.

I don't know if this will help for our issue, but I think we can try it.
[Galaxy S I9000 Android Development] FadeFx:
I do not think it will help, because when we are looping i guess there is no way to go to recovery as well. I think it would be better to have the commandline output on screen (instead of kernel splash) at second or third loop and then if possible stop the bootprocess where it fails instead of looping.

------------------------------

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] stratosk:
Yes, maybe this is true.

But, this is what I think: ICS kernels use a special register (named SP_INFORM6) to store a value for the next boot (SP_INFORM6 keeps its value after reboot). When the kernel boots it reads this register and if it finds a value of 2, passes a parameter in command line bootmode=2.

The first binary/script that the kernel runs is 'init'. This is a script in our case. Init script scans the command line and if it finds bootmode=2 it prepares the recovery initramfs and the recovery is loaded.

I made two changes:

1) An init.d script tries to detect bootloop and if it will detect one it put the value 2 in SP_INFORM6. This means that the next boot will be in recovery (if something else evil does not happen)

2) In the init (the first script the kernel runs), I put the value 2 in SP_INFORM6 at the beginning of the script. And restores the value at the end of the script. This means that if anything goes wrong in the init script (mounting partition, coping etc) the next boot will be in recovery.

Of course all these in theory, I don't really know if it will work.

Your idea about showing information is not bad. Unfortunately, simply removing boot splash will not work. Other changes also needed for information to be displayed on the screen.
[Galaxy S I9000 Android Development] FadeFx:
I just said instead of kernel splash, how it would work i actually had no idea... unfortunately.

------------------------------

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] ryanmat:
In my case I can repeat this bootloop regularly. So, if you can suggest any logs I should be pulling when I go into bootloop I will gladly do so if that will help the kernel devs to pinpoint the issue. Try it yourself and see if you wind up in a bootloop:

CM9 stock -> Flash Glitch/Devil kernel -> Boot -> Reboot Recovery -> Flash new CM9 nightly using TWRP -> Reboot system -> Bootloop/lost recovery
[Galaxy S I9000 Android Development] stratosk:
Taking logs when in bootloops is difficult (impossible?). You could take the /proc/last_kmsg after the first successful boot. But it will only help if your last boot was the unsuccessful one.

If you could try my latest version when in bootloops, it would be fine for me.

Thanks for your help anyway.
[Galaxy S I9000 Android Development] tazzydemon:
5.0 Boot Loop Recovery but to 4.2

I too got the infamous bootloop after upgrading from 4.2. Once this happens you can't get into recovery mode. I was hoping to flash a semphore kernel to see if this would stop it. No luck However if you press up/home/power then eventually it will go into download mode.

I found that odin would not connect and used an early heimdall to flash an ezbase to the phone from which I reflashed 4.2. Because of no odin I could not flash a kernel on its own. I then repeated the entire process to the same effect.

I also noted that if one plugged the usb in when in the bootloop it would stop and revert to charger indicator - although this indicator did not work as such. Plugging the charger in to an off phone would also start it bootlooping - although this may be by design in ICS.

So again no logs available, sorry.

---------- Post added at 11:07 PM ---------- Previous post was at 10:43 PM ----------

Sorry wrong thread!!
[Galaxy S I9000 Android Development] stratosk:
Don't worry, not so wrong... :D
[Galaxy S I9000 Android Development] ryanmat:
Stratosk! You may have found the answer! I replicated my bootloop as previously mentioned, then went into download mode, and flashed your 1.2.2.tar kernel. Pulled the battery and did the 3 button combo into recovery! Was able to reboot, and even restore my nand backup. Thank you for your amazingness! :D
[Galaxy S I9000 Android Development] stratosk:
I'm glad it helped you buy we need more tests on this. :)

I also would like to know if the automatic boot to recovery will work.
[Galaxy S I9000 Android Development] Bejda:
I have a good "almost based on nothing" feeling about the shorter time spent on kernel boot image with latest semaphore.

Edit:Not sure that it's only due to new intramfs from my side, it really seems much faster now, more something about "detection"...
[Galaxy S I9000 Android Development] pbecks1963:
Hello stratosk,

Just want to tell you that i am on slim ics v3.9 (stock kernel) and flashed your latest kernel (1.2.2s). I got into a boot loop (galaxy s logo, semaphore kernel, and so on). (no recovery, 3bc) After a couple of these cycles the phone stoped doing this and the battery logo became visable.

I saved my ass with: Odin and cm7-galaxys-initial-kernel.tar. Reflashed 1.2.2s and everything is ok now.

Tell me if you need any log.. (which onces, where located)
[Galaxy S I9000 Android Development] stratosk:
Hi,

Unfortunately I don't think there are any logs remained...

I had also bootloops. I flashed Slim 3.9 and configured everything. I said to myself let's try a dalvik and cache clearing. And as many users reported: bootloops.

Flashed latest Semaphore through ODIN, nothing.

Flashed fixrecovery.tar and the phone didn't rebooted as expected. But It did with a second try. Flashed semaphore from CWM and again nothing.

I though that I have to flash anything from scratch.

And then suddenly I rebooted the phone and after a while... ROM's boot animation.

I think someone reported this, that after some cycles of bootloops the phone recovered itself.
[Galaxy S I9000 Android Development] ipuljic:
I have flashed AOKP B37. Clean Dalvik and Cache than flashed Semaphore 1.2.2s. Reboot. Bootloop. But on second boot it goes right to recovery. And after that I was able to reboot system.
[Galaxy S I9000 Android Development] stratosk:
This exactly how the new boot loop detection should work! :)

Thanks for your feedback!
[Galaxy S I9000 Android Development] FadeFx:
Hmm, strange... i can not imagine how this could work... but still, there are different types of bootloops...

------------------------------

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] stratosk:
Maybe reading my answer again could help you to imagine:

http://xdaforums.com/showpost.php?p=26858142&postcount=249

Please feel free to contribute and help us to resolve the different types of bootloops (I believe that there are 2 types).

BTW, I tried your idea about removing the boot splash and display kernel messages. Although I didn't manage to successfully boot it the kernel messages scrolling too fast to read anything.
[Galaxy S I9000 Android Development] Bejda:
Could we try last_version file to /system as latest Devil 0.94 with,on kernel side,just the "check if file is there" part (not the "skip copying some files if she's there"),only the detect process.

It could be cwm zip to be flashed just before flashing the kernel corresponding version (we could stay in recovery to flash the both following i think?).

I think it's something to be tested on reproducibles cwmless bootloops situations like those reported before (dalvik-cache cleaning then different kernel flash or else...).
[Galaxy S I9000 Android Development] stratosk:
I'm sorry but I didn't understand you. Could you please clarify?
[Galaxy S I9000 Android Development] Bejda:
I thought I've talked about this here but can't find it now,so here's the page where i asked DerTeufel about his new 0.94 feature and told my...hem..observations.

http://xdaforums.com/showthread.php?p=26696960&highlight=last+version+idea#post26696960

I'm still saying too that for me the boot time (time spent on kernel logo) is shorter on Devil 0.94 and latest semaphore than on others or previous kernels that already had new initramfs...really i know nothing but keep feeling there's something about "detection" and feel safe flashing,rebooting,etc...with latest semaphore if I'm already using it just like with Devil 0.94 if i put his last_version file in my /system before flashing it coming from another one (and after too if i stay with latest DerTeufel's kernel of course).
[Galaxy S I9000 Android Development] stratosk:
This is not related to bootloop detection. It's just a file that marks the version number. If the version of the kernel is different with the version marked in the file kernel stuff is installed.

This was used on CFroot kernel and Semaphore GB. It has a small disadvantage. If a user installs a kernel A then a kernel B and the again kernel A, the script will not realize the kernel change and will do the installation. In the init script we developed (Mialwe and myself) we check kernel version with the version of a module (in /system/lib/modules).
[Galaxy S I9000 Android Development] karol1981:
I had a bootloop, and semaphore 1.2.2s.tar restore my revovery and phone boot normal.
[Galaxy S I9000 Android Development] stratosk:
Good news! :)

Thanks for your feedback.
[Galaxy S I9000 Android Development] Federico0:
In my last case, i just wipe cache and dalvik cache and i got a bootloop with semaphore 1.22 kernel and ics 333. (Very good combo, anyway)

Actually, with the same configuration, i got a bootloop just performing a factory reset
[Galaxy S I9000 Android Development] stratosk:
And... bad news!

Did you recover from bootloops?

If not please for a small test: remove the battery and wait a couple of minutes. Put back the battery and boot your phone.
[Galaxy S I9000 Android Development] jgcaap:
i had same issue . Didnt recover from bootloop , had to reflash everything again :(
[Galaxy S I9000 Android Development] Netmatrix:
Hi Stratosk, i just want to report, that i rebooted to recovery and choose wipe both caches (Dalvik and Cache), and reboot phone and i don't have a bootloop the phone booted normaly (using 1.2.2s).

Thank you for this!

now i'm feeling a secure phone in my hands again...:D
[Galaxy S I9000 Android Development] eidikos:
i had the same problem

did it and bootloop

but when i flash 1.2.2 it works

tried 3 times
[Galaxy S I9000 Android Development] stratosk:
What was your previous kernel before flash 1.2.2? Do you mean it just worked reflashing the kernel?
[Galaxy S I9000 Android Development] pbecks1963:
just want to report that i upgraded from slim (ics) rom 3.9 to 4.0. (semaphore 1.2.2s kernel)

No problems.

did a dalvik cache wipe

flashed the rom (3 parts)

flashed semaphore 1.2.2s

fix permissions

rebooted..

done.

(also rebooted to cwm twice to install kf1/kb3 modem)
[Galaxy S I9000 Android Development] eidikos:
my previous rom was 2.0 ics333 and kernel semaphore 1.2.2s

i just upgraded to ics333 2.0.1 which includes semaphore 1.2.2s
[Galaxy S I9000 Android Development] Half Man Half Biscuit:
Using TiramiSlim RC2 ROM with Devil2_0.94 kernel.

Flashed a file and got stock on bootscreen.

Took out battery and tried to get into CWM recovery,s#$ t has to happen it didn´t go.

I was already beyond pissed,then remembered sometimes if i take battery out a few seconds longer it helps.

Nope nothing,had to reflash everything again.

The point is,sometimes if you take your battery out longer (5-10min) it helps,sometimes not.

Could be a problem of losing data,or if you flash some wrong poop.

Just my opinion
[Galaxy S I9000 Android Development] AsfaltSame:
I use nightly ROM and now I switched to midnight kernel and my bootloops are completly gone!

I think it has something to do with the sdcard preferences, because midnight kernel flips these around.

Sent from my GT-I9000