yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] riso123:
Really. I and others must be doing it wrong then, since many of us had the no boot or recovery issue and recovery kernel didn't help, yet midnight did work.

Of course, since your so sure it works on all ICS roms, I and everyone else must be wrong.

The increasing arrogance of the users on XDA is becoming beyond a joke.
[Galaxy S I9000 Android Development] riso123:
Interesting. In all scenarios had you set the low memory killer values at all?
[Galaxy S I9000 Android Development] zodiaxe66:
PLEASE READ OP BEFORE POSTING,provide a log or steps of reproduction of bootloop...

But am sad to hear that so people have these problems.really hope that devs come up with a solution.

But this will happen faster if we "noobs" stay clear of this thread and open our own "noob" bootloop thread

Sorry about posting this thought it was necessary
[Galaxy S I9000 Android Development] burakgon:
All ICS kernels have 100mhz internal voltage as 1000mv. That's too low for some of devices and so much people have reboot problems including my gf because of this.

Another fact, when I fail overclock a few times I'm losing the recovery. I think file corruption on kernel parts causing this.

So If kernel developers fix 100mhz undervolt to 1100 mv this problem will be mostly decreased.
[Galaxy S I9000 Android Development] stratosk:
This could cause some instability issues but definitely this can't be THE reason of bootloop issue.

Remember that many people overclock the phone and in many cases there are kernel crashes because of this. So, if the problem was cause because of a kernel crash, I guess we would have many more reports about bootloops.

(OT: Anyway I will revert the INT voltage to 1100 - as it was in GB for stability reasons)
[Galaxy S I9000 Android Development] Chris_84:
If this post useless delete it stratosk. But never had problem flashing devil over glitch or from glitch to devil.
[Galaxy S I9000 Android Development] burakgon:
Another thing, when I delete NSTOOLS settings from devil kernel recovery with low battery, I'm losing recovery. Did million times. About %10 battery.

But when I delete nstools settings from adb with rm command in recovery it works nice.

Can the reason battery level?

Maybe kernel allows booting with %3 battery, but rom just allow booting with %5 battery for an example. So when battery is %4 we stucking there.

So this can cause bootloops? I can't imagine this if linux kernel has a battery line like that.
[Galaxy S I9000 Android Development] dannybuoy:
I've only had this happen to me once and I'm pretty sure I know what triggered it. I had been running MIUI ICS builds stably for a while, before I started messing around with the overclocking settings. After setting LiveOC to 120% my phone rebooted and ended up in the boot loop.

So if anyone here is getting the issue, let us know if you've been overclocking or not!
[Galaxy S I9000 Android Development] lpalvaro:
I had it lots of times without any overclock. I think that it's related to rebooting to recovery from the power menu and then flashing connected to an USB cable. And it's also related to cleaning dalvik cache
[Galaxy S I9000 Android Development] GoRRaN:
Had severals bootloops till now..only solution for me, was : battery out, go to recovery, wipe again, flash the rom again...worked every time
[Galaxy S I9000 Android Development] DerTeufel1980:
well, i could not reproduce this issue till now.

what i can say for sure:

reboot recovery, and then flashing a rom/kernl never put me into bootloops. i never cleared any cache or wiped anything, and i flash kernels for testing sometimes 20 a day.

i have also flashed from cm9 to cm7 and back several times, without factory reset, or wiping anything. the worst thing what happend, were some apps force closing after first boot.

for me it has something to do with wipe (dalvik) cache and/or lippol's cleaning script (which i never ever have used, since i own my sgs)
[Galaxy S I9000 Android Development] cdmackay:
I hesitate to spam the thread, especially as I've never had a bootloop, despite many dozens of ROM/kernel flashes, but...

It might be interesting to know if the problem might be related to which method is used to enter recovery:

- reboot recovery from power menu

- reboot recovery from recovery

- 3-button press from power off

For me, I always use the first method & never wipe anything. Only use CM9, with stock, and then Semaphore kernel.
[Galaxy S I9000 Android Development] .:Crack:.:
Actually just had a bootloop after my phone suddenly shut down... Oc'ng to 1230 MHz... Didn't lose rec. though :)
[Galaxy S I9000 Android Development] Bejda:
Another thing to mention is that it doesn't happen when we want it to :p ,been flashing and rebooting all the way but nope,still that sad moment when my bootanimation appears (:confused:what am i saying here),i knew it was there waiting in the shadow to attack me treacherously tomorrow morning at my job with no pc until the evening but no,it finally occurs now!Yeah!

It happens after flashing a rom without wipe except dalvik-cache and cache partition but i did make the exact same flash procedure (same rom to same rom) about 1 hour ago and it did boot that time.

Well,logcat didn't worked while bootlooping,can't found any adb devices so as always i flashed initial cm7 kernel,reboot to recovery and now i'm here adb connected to device in cm7 recovery menu...

Can anyone tell me what info can i grab now trough adb?I was using Devil kernel so i thought about pulling the user.log at first but:

adb pull /data/user.log

remote object '/data/user.log' does not exist

Think it's the location of midnight that i typed no?

Anyway could someone help me get the more informations possible in the situation i am right now?

...ho well so much things i'm not used to for now and time to go sleeping,next time with your help i'll be better prepared :)
[Galaxy S I9000 Android Development] aladin6:
For me, JVU+chainfire kernel+ CM9 => bootloops + no recovery (when installing CM9)! And believe me, i tested all scenarios! The only ROM that passed is INFINITUM in version 1 i guess! Probably, i think that's a kernel problem :confused:
[Galaxy S I9000 Android Development] dastinger:
Well, I don't think I'll help much trying to find a solution but I'll try to report what happened to me.

First scenario:

I was running AOKP M4 and flashed Semaphore 0.9.8s (I guess it was that version). I wiped cache, Dalvik, init.d and NS Tools settings.

Result -> Bootloop without Recovery.

Solution -> Flashed Semaphore's boot.img using Heimdall and flashed Semaphore 0.9.8s again without any wipes.

Second scenario:

Started to get random reboots on AOKP B32 + Semaphore 1.0.1s. Tried to solve it in many ways but ended up going back to GB. Flashed the Rom again, let it boot and then Semaphore.

Result -> Bootloop without Recovery.

Solution(s) -> Tried to flash boot.img with no success.

Tried to flash fixrecovery.tar.md5. All I got was a CWM 2.x that wouldn't let me flash the rom again and kernel flashing didn't work.

Tried to flash older Semaphore ICS versions boot.img and it didn't work either.

Went back to GB, repeated the same process with AOKP again and, same result.

Long story short, I ended up trying Slim and had the same problem everytime I flashed Semaphore. Found out that the problem was with dalvik wiping and not Semaphore itself. Flashed Semaphore without wiping Dalvik and all ran smoothly. Now, I may wipe dalvik and it works with no problems whatsoever.

Like I said, I don't think I'll help much with these reports but, even if dalvik wiping has something to do with it, other users' reports say that they don't have any problem with this. I think I just added even more randomness to what may cause this.
[Galaxy S I9000 Android Development] HM.Carbide:
It is just a guess from reading.

Could it be the following problem?

1. Flash kernel or a rom including kernel.

2. Being still in the old (inconsistent) recovery, and wiping something, or flashing other kernel.

Maybe a step between is missing. Reboot into recovery again, to start the new recovery.

Could it be, that the old inconsistent recovery damages the new one?
[Galaxy S I9000 Android Development] burakgon:
Looks like problem is wiping dalvik cache %80.

Let me wiping dalvik cache from adb with rm -r command on recovery.

If that works I will wipe dalvik from recovery menu to test again to be sure.
[Galaxy S I9000 Android Development] Bejda:
@Burakgon: Does your tests (thanks for that :) ) "works" or not i'm not sure we'll get sure of anything unfortunately...

I said myself that the only little common point i can see from various users reports is dalvik-cache wiping related and most oftenly with Pawitp's kernel but let's take as exemple a rom i know and mostly use with Pawitp's one bundled which wipe dalvik cache at install:

Few weeks ago and two times i had los'recovery bootlps at first boot after flashing it.Ok,i got the habits now of flashing directly any other kernel just after installation before reboot system.Had no problem since i'm doing that but it's not a rule huh ;)

Yesterday ,i flashed it and let it boot with bundled kernel (Pawitp's then):boot succesfully.

Still on it i tried (but was on devil at this moment) to reboot into recovery,clear dalvik-cache,reboot system now and it did boot fine too.

After that i flashed another rom (same base,no need to wipe data or something but dalvik cache is scripted too):boot ok.

About 1 hour later,was back on first rom and reflash the other (exact same process,no visibles changes in my configuration and was from devil to same devil kernel) and here they comes:bootloops with lost access to recovery.....

Really i can't see any logic behind but i agree that something with playing with dalvik-cache could serves to get more chances to reproduce the phenomena the closest way.

I recall that the phenomena we're trying to identify here can happen for the most unexpected case when:

Flash something that have no reason to make a mess on our phone.

Just reboot or power off/on.

(hmm,and let's put aside those when coming from sammy gingerbread rom to ics or aosp 2.3.7 rom,this is not what we're talking about here).

One points is sure:

Some never ever had this.(so they're wondering wtf are we talkin'bout).

So,yesterday i ended up in the very thing we're talking about here I think but couldn't connect to adb while bootlooping.I'd like to know what can i do to grab useful info after initial cm7 kernel flash by odin that give me back recovery menu and possibility to connect to adb before doing any further steps.

Many chances it will happen to me again i'd like to know what can i do to help us on the concern.

I only get a dmesg...from what i understood a dmesg when on a plain calm cwm3 recovery menu shouldn't give many infos :p .

adb shell cat proc last_kmsg said file not found (was too late maybe?)

And now that i managed to get back on my rom without need to wipe data the user.logs(and .bak) i see of Devil kernel seems previous to the incident,as if bootloops doesn't allow enough boot time to produce one (should be logical,don't know).
[Galaxy S I9000 Android Development] Korshar:
No. I have a very early model (June/July 2010) and it has happened to me after following procedure:

1) installing slim 3.5

2) kernel cleaning script v2

3) installing semaphore 1.1.1s

--> bootloop, got fixed after FixRecovery was flashed over odin
[Galaxy S I9000 Android Development] corgar:
don't have a logcat o kmsg.

what i did and step to reproduce:

wipe cache and dalvik cache.

Flash new cm9 nightly.

If i install nightly from rom manager it will delete dalvik cache AFTER rom flashing and all went fine. I i wipe Before the flashing recovery is lost and bootloop begin.

Another thing that i spotted is, if i try to Fix recovery with the package Fix:recovery.tar and i try to flash over again the cm9 rom i get a Problem with assert failed, and the rom update script can't recognize my device as an i9000 and installation got aborted.

system mount problem? build.prop corrupted? ( i don't think build prop got corrupted with a bad flash but god know )

another thing is, if i wipe cache and dalvik cache WITHOUT flashing a rom afterward i got no bootloop.

if i got some other infos i will post here.
[Galaxy S I9000 Android Development] xavierf:
I used CM9 with original kernel.

At the begining, when I flashed the new nightly. I had every time a bootloop whithout recovery.

Now, I use rommanager to check and flash updates.

I use wipe dalvik cache option and No more Problem.
[Galaxy S I9000 Android Development] jacobuscuracao:
I've seen bootloop in cases where cache and dalvik were wiped AFTER install of the Rom + kernel, instead of before, suggesting that at the time the kernel had a problem with that? I know it sounds silly while I'm saying it, but that was the sequence of events

on CM9 1x builds with stock kernel

---------- Post added at 04:20 AM ---------- Previous post was at 04:14 AM ----------

sorry for asking the obvious, but did that upgrade from GB to CM9 include removing the battery at the first bootloop? and even after that you got no recovery?
[Galaxy S I9000 Android Development] stratosk:
Thank you for your help everybody.

But please try to keep this thread clean. I didn't start this thread to share experience about the bootloop. I know that this is not necessarily bad, but it's out of scope of this thread.

I think if we will continue in that way the thread will be moved from 'Android Development' forum.
[Galaxy S I9000 Android Development] stratosk:
Anybody know something about when the recovery partition is flashed with recovery image?

I found this in CM9's updater.sh script:

/tmp/bml_over_mtd.sh boot 72 reservoir 2004 /tmp/boot.img

if ! $IS_GSM ; then
/tmp/bml_over_mtd.sh recovery 102 reservoir 2004 /tmp/boot.img
fi

In Semaphore's installer script I never flash recovery partition.

What other dev's do?

I google for some info. And I found that the recovery.img is always in /system and it's flashed on every reboot. I guess this is not happening in our case.

Anyone can share more info?
[Galaxy S I9000 Android Development] danieleb89:
I also found this problem three or four times, and i've tried both fixrecovery and cm7initialkernel, so I came to these conclusions:

Heimdall -> i can't solve the situation, with cm7initialkernel nothing changes, with fixrecovery i can use the recovery but when I flash a rom my phone reboots on recovery always...

Odin -> I can solve only with cm7initialkernel, with fixrecovery I have the same issue that I have with heimdall...

I can also say that odin saved my ass everytime and I never needed to make a clean flash...

finally I found that at least three times on four I had devil kernel, when my phone is on this kernel is perfect, smooth and stable, but in recovery I'm always afraid that it couldn't restart (the "touch" recovery doesn't give me much security)!
[Galaxy S I9000 Android Development] DerTeufel1980:
i also don't flash the partition
[Galaxy S I9000 Android Development] ZioGTS:
The pot calls the kettle black! :rolleyes:

EDIT: Sorry, I couldn't resist feeding the troll... I apologize.
[Galaxy S I9000 Android Development] mialwe:
For MNICS: Same, no separate flashing to recovery partition. But having

assert(run_program("/tmp/erase_image", "boot"));
assert(package_extract_file("boot.img", "/tmp/boot.img"),
run_program("/tmp/bml_over_mtd.sh", "boot", "72", "reservoir", "2004", "/tmp/boot.img"),
delete("/tmp/boot.img"));

the recovery partition is not touched, not cleaned, nothing. The other way around flashing e.g. a kernel with updated CWM (new options or similar) the new recovery shows up fine - even if installer does not touch the recovery partition and never did!?
[Galaxy S I9000 Android Development] Bejda:
If it happens to me again,unable to log while bootlooping then flash initial cm7 kernel,reboot to recovery and finally able to connect trough adb,is there at this point any commands that could help to grab info?
[Galaxy S I9000 Android Development] corgar:
can reproduce similar lost of recovery if i try to flash any zip from cwm only if my usb cable is plugged in.

with recovery fix can't even mount anymore system partition. Always need to start from scratch with odin. can't grab last kmsg since telephone isn't recognized by my pc. I can only get it recognized via download mode.
[Galaxy S I9000 Android Development] burakgon:
Now I lost recovery again by removing NSTOOLS settings from DEVIL menu. But if I delete it by adb @ recovery no problem.
[Galaxy S I9000 Android Development] lerkin:
xdaforums.com/showthread.php?t=1504808&page=30

Check it out please, can it be similar?

My friend has just tottaly bricked his n7000
[Galaxy S I9000 Android Development] fatjoez:
I'm on MIUI v4 ICS rom.

Wipe Dalvik cache = bootloop

Happens on any kernel (mialwes midnight, devil, glitch, semaphore)
[Galaxy S I9000 Android Development] Jarmezrocks:
I respect the OP with regards to keeping this clean. But I can totally relate to your experience both the same and complete opposite. Hard not to name name names and my device is different but I found the only good touch recovery for me was glitch, but I was always scared I would toast my phone if I used it (so god damned hot you could fry an egg on that ***** not even over clocked:eek: stock as a rock) and then platypus was smooth as sailing when the phone was working but come recovery time its like eek is this going to work? I was thinking asking these devs if we can make the best of both worlds but i think that is going to be difficult?

Question? Has anyone ever lost the middle multi-tasking button with any of their ICS kernels? I have noticed that I had a nandroid backup that killed my middle button....but only when restoring data partition, but that made me think WTF is controlling the button combination that is NOT in system? Someone answer that for me please!! I ended up grabbing databases and placing them in data/data via rootbrowser and then pulling appart the data.tar and grapping all the apks I wanted and putting them in a flashable zip and flashing to /data/app.

Also had nandroid restore of data cause bootloops? How does that work? :confused:

Trust me I have conjured up every concievable way of restoring my phone (out of necessity - i.e retrieving a gorgeous girls contact out of the depths of helll bootloop, no recovery no flashing back MD5 error, corrupted data recovery and all sorts of crap you guys have probably known or done your selves).
[Galaxy S I9000 Android Development] saszseb:
1. I've never had any random bootloops.

2. I've tried it on 10 ICS ROMs.

3. I sometimes make bootloops to find a solution for me.

Sent from IMM76I.
[Galaxy S I9000 Android Development] saszseb:
I was talking about my experience. If I want to get a bootloop I'll flash Glitch over Devil.

Sent from IMM76I.
[Galaxy S I9000 Android Development] stratosk:
I believe we have recovery because both normal initramfs AND recovery initramfs is packed into boot.img.

Maybe, we should flash also recovery partition with kernel+recovery initramfs?

That's why I asked what the rom does when you boot into recovery.

Many articles, searching in google about recovery, mention that a recovery.img exists in /system and it's flashed on every reboot (?!?).

I'm not very familiar with this boot process.

What triggers the boot of recovery. I checked the commit krarvind send. And when you choose reboot only the recovery string is passed to the reboot function.

Then what? Is this passed to the bootloader? And the bootloader decides to boot from 'boot' partition or 'recovery' partition?

In our case (I believe - maybe it's not true) the boot.img handles both normal and recovery booting.

EDIT: I know this will not fix the corruption of boot or recovery partition (in case of bootlops). I'm searching this because I have the suspicion that we don't use the recovery partition. Maybe if we use it, this could save bootloops.
[Galaxy S I9000 Android Development] stratosk:
I just checked my recovery partition. As I thought: it's empty.

It tried:

cat /dev/mtd/mtd1 > recovery.img

both from normal and recovery mode.

This means that recovery partition is not used. I wonder why. Or maybe we don't flash it in our kernel flashing scritps... I will check it.

EDIT: I flashed CM9 and again checked the recovery partition. It's empty
[Galaxy S I9000 Android Development] riso123:
You have or haven't had boot loops???
[Galaxy S I9000 Android Development] Bejda:
Helper wannabe instant :)

I was looking at what you said and found this page:

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Tried this command:

# cat /dev/mtd/mtd1 > /sdcard/mtd1.img

That gave me a mtd1.img image file:

http://db.tt/cmiOTHFy

Knowing that i did had los'reco btlps yesterday,flashed cm7 initial kernel then Devil and i think I did not reboot until now (pfff,no.Remember now having even flash rom this morning) (" This file is automatically flashed onto mtd1 every time you shut down.").

Probably bull...t useles saying but don't know how to show my gratitude for you to take responsibility to open this here topic.
[Galaxy S I9000 Android Development] stratosk:
As you may see it's empty (it's full of 'FF' in hex).

sixstringsg confirmed this (that the recovery is unused) in a question on his thread.

This explains the fact that if anything goes wrong in boot partition and the kernel does not boot (bootloops) then in most cases there is also no recovery.
[Galaxy S I9000 Android Development] mialwe:
Found some thread posts about recovery partition not beeing used at least on (some?) Samsung devices, too, however this information never was "official".

Found something interesting in the kernel source: https://github.com/CyanogenMod/andr...92f39/usr/galaxysmtd_initramfs_files/init#L21

The file contains loading stuff for different boot options and supports the theory of both images in one boot.img (we are actually packing ramdisk.img and ramdisk-recovery.img into one boot.img when preparing the kernel, do we?) - according to the reboot option the load offsets are changed.
[Galaxy S I9000 Android Development] Bejda:
Yeah a big 7,50 mb of "FF" file...thanks for further explanations again,don't waste too much time on it when it's so far far away from the point ;)

Hope you got something with that recovery partition thing.
[Galaxy S I9000 Android Development] krarvind:
AFAIk, its the board used in sgs variants. NExus devices have recovery images separate from kernel, you don't need them embedded which i prefer than the sgs
[Galaxy S I9000 Android Development] stratosk:
Thanks mialwe!

I never noticed this file. Do you know when this script runs and where is located in our phone? (the init in root directory / is a binary one).

Yes, we do pack both initramfs in boot.img. But, I have the wrong impression that a copy of boot image somehow is also flashed (from ROM) in the recovery partition.

I also asked sixstringsg for this because he mentioned this in his thread.

So, we have the recovery mtd partition unused.

Actually we had the same logic in GB. We had one boot partition and no recovery. In the same initramfs we have also the recovery binary and files needed for recovery.
[Galaxy S I9000 Android Development] stratosk:
Yes, I think it's better. Because you have a second option if the boot partition is corrupted.

Maybe this is our issue.

I also don't understand the relationship between the old bml7 partition and the mtd boot partition.

I mean in GB the bootloader obviously loads the kernel from bml7 partition. How the same bootloader boot the mtd boot in ICS?
[Galaxy S I9000 Android Development] asder00:
today a very strange thing (just for you to know)

went in recovery

then

wiped cache and dalvik

= bootloop -_-

Elite V11

I always fix with the fixrecovery via odin, then install ICSSGS4.2, then the rom i want. ICSSGS is the only rom that I can install after fixrecovery that don't go in bootloop again!