yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Bejda:
I was thinking about the fact some users stated they never ever experienced cwmless bootloops and so was wondering myself something:

Could that difference be achieved by maybe the only thing that could really differs from users to users,i mean its contents,the sdcard?

It's strange that we all know peoples for whom it never happened as they're flashing stuffs here and there the same way frequents victims do.
[Galaxy S I9000 Android Development] aladin6:
Feedback: Flashed a stock ROM(JVT) then Semaphore ICS then CM9.

No bootloops :). First time discovering CM9 (never succeed to install it because of the lost of recovery). Thank you stratosk for your perfect kernel.

To conclude, i think that the new version of Semaphore resolves the problem of the lost recovery when installing CM9 :)
[Galaxy S I9000 Android Development] frankind:
Found bootloop on Semaphore kernel

I found bootloop when use semaphore kernel (not mean another kernel not found).

Step:

1.Try to reboot with normal

2.When reboot i try to go to recovery mode when Samsung version show "I9000"

3.after that I stuck with Semaphore logo

4.after i try to remove and add battery.

5.I start my phone and it not show Samsung version but it show Semaphore Logo and bootloop.

6.I try to go to recovery mode but it does not work.

7.I try to flash Semaphore kernel by ODIN.

8.I can go to recovery mode but after i full wipe or install other rom from here I still stuck on recovery mode.

My workaround is : New install GB then install ICS from recovery mode again.
[Galaxy S I9000 Android Development] aladin6:
So let's talk of my experiece perhaps that it will fix the problem of bootloop on some devices.

I wanted to update my build to the latest one of the 10th June. I installed it but i had a bootloop. I flashed with Odin Semaphore 1.2.2 and it passed without bootloops.

Conclusion: THE MAIN PROBLEM OF BOOTLOOPS IN SOME DEVICES IS THE DEFAULT KERNEL.
[Galaxy S I9000 Android Development] FadeFx:
You must be wrong as this happens to users of custom kernels as well.

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

tapatalked from Galaxy S
[Galaxy S I9000 Android Development] aladin6:
If that happens with custom kernels ROMs so i have nothing to say.

Weird, weird, weird.... :confused: :confused: :confused: :confused:
[Galaxy S I9000 Android Development] Zatta:
You found it! Was just about to give you the link to this thread after your thorough scientific analysis on the other thread :-)

Taptalked u see
[Galaxy S I9000 Android Development] Chappac:
These are my experiences with Ics boot loops on Cm9 and Slim Ics with standard kernel and and devil kernel.

This has happened to mine and my girlfriends I9000 around 5 times each, both the same day once. Each time while doing different things.

The only way I have been able to fix is flashing a Gb ROM via Odin then cm9/slim again.

The last time I flashed just devil kernel and got into recovery so I could make a backup of my data. Did the normal GB flash and back to Slim Ics everything booted fine. So I did an advanced restore of just my data and BOOTLOOP AGAIN on the slim boot animation pulled battery then looping on devil screen and LOST recovery AGAIN

So maybe /Datadb has something to do with the problem as restoring just /data did not cause bootloop

Hope it helps
[Galaxy S I9000 Android Development] shaarky:
So, again new experiences...

I was so far using Semaphore 1.2.2s on CM9 without a bootloop for more then one week, maybe two weeks. I was rebooting phone to recovery maybe for 50 times during this period ? (GPS problems, testing modems).

Then I started testing again with latest Devil3 - and today I got again first bootloop. Standard way of fixing - flashing 1.2.2s.tar via Odin did not help, CWM not accessible even with Semaphore 1.2.2s, just flashing Devil3 back and keeping it booting - fixed.

But I had new observation - I tried this time during bootloop to pull out battery a start phone again - AND - it worked. Till today I thought the only way is to flash FixRecovery.tar....
[Galaxy S I9000 Android Development] profalbert:
I was able to avoid this issue for quite a while now. I never had it during normal operation in the last 2 months. I was always on some CM9-nightly and always with stock-kernel.

Just in case I avoided:

* going to recovery only by: Power off --> 3-button-combo

* keep USB unplugged during the whole flash procedure (from Power-off to Power-on with the new ROM).

However I got it again today:

* went to recovery by Powering off and 3-button-combo

* flashed CM9 (20120529)

* wiped /data

* reboot system

* --> Bootloop without recovery

Using these steps I can reproduce the bootloop quite often. It's wiping /data immediately after flashing either a ROM or gapps and then reboot.

taking out the battery for 5 minutes did not help either. I was able to resurrect it by flashing Midnight kernel. After flashing midnight, it booted completely (well /data was wiped).

Also, I did all of these steps above at about 70% battery.
[Galaxy S I9000 Android Development] Zatta:
This quote comes from the devil3 thread but I thought it was worth mentioning it here.
[Galaxy S I9000 Android Development] BLADESMAN1889:
I don't think there is any pattern to the bootlooploop as I've had it on 3 separate occasions now, on 2 different ROMS [CM9 & AOKP] and 2 different kernels [Pawitp & Semaphore] between Jan 2012 & most recent June 2012.

1st time after wiping Cache/Dalvik

2nd time while attempting to boot into Recovery from Extended power menu

and 3rd time whilst the phone was just sat in standby mode [screen off] which I noticed when the screen lit up and was rebooting itself and went into bll.

On all 3 occasions I lost Recovery and left the phone for 20-40 mins rebooting, turned off tried all the usual - remove battery, sim, sd card.

In the end I got the phone/Recovery back by flashing the CM7 initial kernel via Odin.
[Galaxy S I9000 Android Development] jimcantfixit:
Today I experienced the lost recovery issue. Flash in semaphore 1.2.2s.tar via Odin did not work. Only thing that worked was fixrecovery.tar.md5

Using slimICS 4. I was battered by this issue. Just don't understand it. I hope that this is solved as semaphore is my favourite kernel. Good luck on your efforts.

Trolled from my GT-I9000 using XDA
[Galaxy S I9000 Android Development] yaatzek:
Maybe it's more rom related. I'm on cm9 only, flashing day by day nightlys, sometimes flashing different kernels and never had bootloops.
[Galaxy S I9000 Android Development] FadeFx:
Nope, i was on cm9 only as well, also i was on devil kernel only. Bootloops are known to happen on all 4.0.4 roms and all respective kernels afaik, but they all are based on teamhacksungs work for cm9, so its hard to say where the bug hides.

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S I9000 Android Development] tomatenjungee:
i experienced exactly the same thing. Even flashing darkys ressurection didnt solved it. fixrecovery.tar.md5 is a good hint
[Galaxy S I9000 Android Development] FadeFx:
Any news on the bootloop issue? Haven't run my sgs1 for a week now since the sgs3 arrived my home, but would like to give it to someone as soon as we can be sure it will boot after a shutdown.

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S I9000 Android Development] aladin6:
Better flash a CM7 on it if the receiver "doesn't know what a smartphone means"(can't fix a ROM problem or even update nightlies), plus CM7 is the most stable one ;).
[Galaxy S I9000 Android Development] dastinger:
Midnight GB kernel saved me from another bootloop (maybe Semaphore GB would as well but never tried it). Flashed the .tar, got Recovery, flashed Sema 1.2.5s again and booted. This has been my favourite process. If Semaphore doesn't work (which it did since the new intra mfs), Glitch usually does.
[Galaxy S I9000 Android Development] FadeFx:
I am pretty aware of the problems cm9 comes with and the only one that is showstopping ATM is the bootloop problem.

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S I9000 Android Development] Zatta:
I remembered this post and it made me think again: can it be that the common factor in the bootlooploops is the use of certain datafix scripts?
[Galaxy S I9000 Android Development] Bejda:
I thought about this too Zatta but "unfortunately" no, i had this on both configuration. Really both configuration cause it happened for me sometimes after coming back from a Sammy ginger rom without beginning to tweak my datadata partition.

But the fact that it could happened when phone is "stopped" while something (about data's maybe) is running in the background has been raised before and i'm still wondering about this... I mean, about this too :confused:
[Galaxy S I9000 Android Development] sidh10:
Please help me

I installed cm9 from Darky 10.2 resurrection. I diabled lagfix, cleared cache,dalvik cache and installed. The phone booted into cm9. I then rebooted into recovery to install gapps and then did the wipe again and now my phone is stuck in boot loop and I cant even access recovery. What to do? Pleasee help me.
[Galaxy S I9000 Android Development] Bejda:
Many things to say/ways to help and this thread is not really about about helping peoples to recover from this issue but well it's the only one that specifically talk about this so...

My first option will be:

If you're an Odin user let's try semaphore 1.2.5 .tar leaving odin as it is and see if phone boots fine.

Find it here:

http://xdaforums.com/showthread.php?t=1468795
[Galaxy S I9000 Android Development] sidh10:
Thank you soo much! You just rescued me and my phone! Sorry for my foolish question and if I posted in the wrong place.
[Galaxy S I9000 Android Development] Bejda:
That's the question but assuming it will work both options should do it.

My idea behind flashing semaphore with auto- reboot ticked is to recover from it with shorter time, without much boot and reboot between,and maybe grab useful infos from log files after (boot.txt or else?Stratosk could say about this).

Anyway if it doesn't work try both and if still doesn't work there's many other ways to get out of it as it never happened without wiping stuffs/flashing back Sammy ginger rom.

Well see ;)

Edit:if it works auto-reboot ticked please try to not to reboot after until further infos,there could be a last_kmsg file (produced at every boot) somewhere in (dont remember clearly the path) /sys/... wich could help to identify what happened.
[Galaxy S I9000 Android Development] Bejda:
I didn't noticed your edit while i was answering,

I'd say as Stratosk:

If indeed it worked like this,you didn't reboot since that and you're still around...the location of last_kmsg is /proc.
[Galaxy S I9000 Android Development] jgcaap:
I dunno why but everytime i flash a file from a folder everything goes great. But most times i flash a file located at root of /sdcard/ i loose my recovery. Anyone can test and see if this is the issue?
[Galaxy S I9000 Android Development] Silentbob999:
I always flashing from /sdcard/ and didn't lost recovery recently ;-)

Envoyé depuis mon GT-I9000 avec Tapatalk
[Galaxy S I9000 Android Development] kasper_h:
I had a bootloop this morning. Had it before and I have a working boot.img I always flash with Heimdall. But now this didn't help, could not even enter recovery. Stock CM9 kernel (as boot.img) extracted from yesterdays nightly also resulted in a continuing bootloop.

RecoveryFix.tar.md5 (extracted zImage) did give me recovery, but it doesn't allow flashing an ICS kernel from CWM (build.prop error), neither could I restore a nandroid backup.

I then finally flashed Semaphore's zImage (extracted from the tar). Now my phone finally booted into CM9. Flashing a new kernel after that was also without problems.

Is there a difference between flashing a zImage and a boot.img? Because only when flashing a zImage I could get a working recovery again...

I don't know what's causing this, but I am glad I could get away without reflashing a stock-ROM :)
[Galaxy S I9000 Android Development] Bejda:
Hi Kasper_h,not sure of a difference between boot.img and zImage cause we can grab the boot.img of a cwm zip and just rename it to zImage to get a working Odin .tar if tar'd,for windows users, with iZarc or PowerArchiever (didn't test PowerArchiever personally but that's what I've heard).

Difference should lie in semaphore.

Edit:i already had this get prop assets ( something like this?) error when flashing something after recovering recovery with usually sure ways, seems to be another strange and parallel issue that gives complications when by instance you got recovery back using cm7 initial kernel .tar ( sure shot for me like it seems all ginger based kernel,Devil.cm7 too) and have to flash something else to reboot on ics.
[Galaxy S I9000 Android Development] DerTeufel1980:
Boot.img from cm9 is different from stratosk s and mine. You can't rename cm9 boot.img to flash it with odin. At least it would miss all modules...

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] Bejda:
Thanks for precision DerTeufel,i would have done this if needed thinking it will be the same for all boot.img
[Galaxy S I9000 Android Development] kasper_h:
Yes, I already noticed the increased file size, so I guessed modules were included.

Can the better bootloop-factor be related to the init-combo the two of your are using?

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] DerTeufel1980:
Atleast stratosk started this, to prevent bootloops, but I think they did not get less. Anyway, his idea is great :-)

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
It for sure is a great idea. I'm looking into it in detail ATM, I think it is a smart way to do things :)
[Galaxy S I9000 Android Development] stratosk:
I feel that bootloops reduced a little bit (of course is just a feeling :) ).I think less people complain about bootloops.

@kasper_h

Please let me know if you need further info.
[Galaxy S I9000 Android Development] yaatzek:
Maybe because everyone is aware that possible reason for bootloops is cleaning cache/dalvik and people wipe it less or never, like me. Maybe that's why we get less notifications for bootloops last days.
[Galaxy S I9000 Android Development] malcho:
I completly lost bootloops.Even after clear cache and dalvik.

For me problem is solved.
[Galaxy S I9000 Android Development] AsfaltSame:
me too

Sent from my GT-I9000
[Galaxy S I9000 Android Development] aladin6:
malcho, you are on Semaphore or stock kernel? And CM9 ?I think that i'll return to ICS(but not now, i need my phone :p)
[Galaxy S I9000 Android Development] aladin6:
I think that merged change solves the bootloop problem, no?
[Galaxy S I9000 Android Development] FadeFx:
That could well be, but wouldn't that effect all devices? Btw had no bootloop for weeks now..(ok i don't use the i9000 that much anymore...)

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S I9000 Android Development] stratosk:
I really don't know, my friend. I use totally different procedure to build kernel/initramfs.
[Galaxy S I9000 Android Development] Helloworld294:
I don't know if its helpful or no, and I'm not a dev (unfortunately;) ) but I only been getting bootloops when nandroid restoring. I found a fix to that. Wipe cache and dalvik cache before nandroid backup and wipe those again before a restore. I think the faulty caches cause errors during a boot process, which causes a loop. But I don't think this info is important, just wanted to let ya know :)

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pxrave:
lost recovery with devil 1.0.2 ics

oc to 107% => played angry birds => hang => restart no access to recovery
[Galaxy S I9000 Android Development] jugster:
battery logo boot loop

This is the bootloop I am experiencing on android versions flashed from recovery. If I flash from Odin I don't seem to get it at all.

http://youtu.be/TvjUUL852Us

From that boot loop I am always able to get into download, and recovery works about half of the times, seems like there is a timing thing you have to hit.

From recovery, if I choose reboot to system, the phone properly boots up.

From within the phone if I reboot, it properly reboots.

If I do a shutdown, then what is shown in the video happens.

If I flash a new kernel (tried devil and semaphore) from download, the phone boots normally again, until it is shutdown.

Shutdown always creates this issue.

Is this a known boot loop problem that can be solved as well?

Cheers,

J
[Galaxy S I9000 Android Development] vincentru:
My bootloop and losing CMW recovery

For me, it happened many times:

1. On AOKP Milestone 6: After shutting down my sgs, I entered Download mode, did nothing, turned it off (with on/off button) and then... paw, bootloop and recovery lost (AOKP M6 Splashscreen .. Splashscreen... Splashscreen).

2. From rooted JVU stock ROM, under CMW recovery, I wiped cache and data, installed CM10 Unofficial from SDCard (root), then bootloop within new CMW recovery from CM10 itself (CMW... reboot.... CMW.... reboot.... CMW....). When trying to get out of the bootloop (removing battery) => Phone-to-PC logo with exclamation mark and no possibility to reboot under CMW.

Hope it helps
[Galaxy S I9000 Android Development] Abyv:
Cm10 from xxjvu gave me boot loops..but. cm9..wen flashed after xxjvu..got me to cm10
[Galaxy S I9000 Android Development] romdroid.:
If u get into a bootloop and want to acess the phone in order to take a backup, how should you do it?

please look into my thread and help me out http://xdaforums.com/showthread.php?t=1827927
[Galaxy S I9000 Android Development] FcoEnrique:
How can I make a init.d clear in CWM? :confused:
[Galaxy S I9000 Android Development] Christophe86:
Problem also exists on earlier version then IMM76D.

Because my phone is now in bootloop modus, i'm going to try to hold the three button combo for a while like you say.

edit: I held the three buttons combo for 2 minutes, no recovery showing up.

edit2: It might be interesting to notice that the bootloop and loss of recovery was caused on my phone

just by wiping cache and dalvik cache

(I did this because I couldn't turn mobile data on, thought it might fix it, you never know). Besides that I did nothing.

The funny thing is, I flashed Semaphore ICS a few days ago and didn't wipe dalvik cache to make sure it doesn't get stuck into bootloop. Phone was working great. Today I went into recovery just to clear cache and dalvik for reason mentioned above, chose 'reboot system' and it got stuck. now i'm asking myself if it would have happened would I first powered off the phone and then put it back on.

One more thing. Going into recovery here by using the power menu when phone is on and then flashing a kernel is a guarantee for bootloops and lost recovery.

I personally think this might be a cwm problem...
[Galaxy S I9000 Android Development] saszseb:
Bootloop is e.g. when you flash Glitch over Devil directly.

Sent from IMM76I.
[Galaxy S I9000 Android Development] riso123:
Just want to point out that your right about the going from GB to ICS kernel thing, but I found that flashing Midnight kernel through Odin THEN flashing any ICS kernel of my choice worked were flashing recoveryfix failed.

In the case of semaphore kernel not booting past kernel splash or going to recovery, the fault was found to be setting low memory to supercharge, at least with cm9.
[Galaxy S I9000 Android Development] saszseb:
1. you are on a Sammy ROM with a CWM compatible kernel like Midnight or Semaphore and want to get an ICS ROM. The steps are:

- factory reset

- flash a nightly (CM9)

- factory reset

- flash your ICS ROM.

2. you want to change a kernel on an ICS ROM:

-recovery

-flash Semaphore

-choose "reboot recovery", you are on recovery of Semaphore

- clear "initd" and "nstools settings" in advanced menu.

-flash the kernel

-reboot.

It always works on every ICS ROM.

Sent from IMM76I.
[Galaxy S I9000 Android Development] burakgon:
Solution

Flash this from odin.

Than flash ICS kernel again and fixed.

http://ics.samsung-updates.com/trouble/FixRecovery.tar.md5
[Galaxy S I9000 Android Development] Christophe86:
I'm using Slim ICS here :p It's not a kernel or rom specific issue. I already encountered bootloops and losing recovery with Devil, Semaphore and Glitch as kernels and CM9, CNA, AOKP, SGSICS, Dark Knight and Slim ICS as roms. For now it almost happens completely at random.

For the ones who posted a solution or a guide how to flash a rom/kernel above. That's very kind of you, but that's not why Stratosk started this thread.

The question here is not how we can fix this issue, because that's already known, but how it comes that we sometimes run into a bootloop or even lose recovery when doing al the correct steps.

Can we reproduce this issue, if yes, we can look if it's rom, kernel, cwm or user related.
[Galaxy S I9000 Android Development] adytum:
Seems to be a lot of unrelated posts in this thread..

Anyway, what can safely be deduced here, seems to be that bootloops never happen without cleaning dalvik cache. But that can't possibly directly trigger bootloops, can it?

Sent from the fridge.
[Galaxy S I9000 Android Development] Netmatrix:
Strange on GB never had this kind of boot loops, I think it has to be a corruption of recovery partition...
[Galaxy S I9000 Android Development] mialwe:
http://xdaforums.com/showpost.php?p=25497862&postcount=5

Maybe there are more than one reason for bootloops but wiping dalvik *never* caused any bootloop over here, simply flashing a kernel CWM zip did 4 or 5 times.
[Galaxy S I9000 Android Development] sUsH667:
same here, happened few times while flashing various kernels AND after executing "reboot recovery" from cwm.

after that, i don't use "reboot recovery" no more and always flash kernel-zips multiple times directly after another, with the result that i never experienced this bootloop anymore since then.

maybe this helps someone to prevent.

greetz,

sUsH667
[Galaxy S I9000 Android Development] adytum:
I didn't mean that dalvik wipe causes bootloops, but that it seems to be a common denominator for it to happen, however that might not be correct at all.

Personally I've never had bootloops at all, so I'm just really curious as to what's going on.

Sent from the fridge.
[Galaxy S I9000 Android Development] slaphead20:
I have had the loop on my 2010 sgs
[Galaxy S I9000 Android Development] scubadude:
My experience. Only had bootloops and lost recovery when using lippols kernel cleaning script. Happened several times. If i clear cache & dalvik cache i don't have problem.

In past i used to run kernel cleaning then flash kernel and reboot.

Now i clear cache, clear dalvik cache, clear init, clear ns tools, flash kernel and reboot into phone. So far no issues with this method.
[Galaxy S I9000 Android Development] clay21:
I don't think its hardware because my phone was manufactured in Oct 2011 and i had one experience with this issue.So its just a naughty ics bug lol.
[Galaxy S I9000 Android Development] fane1:
Glad u brought this to discussion :)

I also have that problem when changing from a gb rom to an ics rom,especially slim ics.

What i usually do and for me its the only way that works is to flash a stock JVU firmware,then apply Chainfires updated JVU kernel,reboot into recovery and flash ics.But its not the end... usually first atempt fails because i think it really needs a ics kernel.So the solution is to remove the battery,3 combo buton to recovery and flash an ics rom that is not slim.Then after successful instalation u can choose slim and thats all good.

I hope that my experience helped to this thread. :)
[Galaxy S I9000 Android Development] dafabsl:
i've these bootloops too, and the happen to me at a time when i need my phone the most, and no pc is near -.- i tried to put out battery to avoid it, worked at the beginning, but now, no matter what i do..

and my experience is that i can't flash a ics kernel from the recovery fix.. that really sucks..

i knoe try too work out a pattern and'll report if i get some news

sent from my Galaxy S running INFINITUM 1.1.0 + MNICS-143LR