yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] 2k4ever:
I'm not a dev, so I can't answer your question (and hopefully I don't spam you thread with useless stuff)

but I have experienced the bootloop once and couldn't get out of it even by restoring a nandroid backup

so my question is: is there any partition that is not backed up through the CWM backup? and could that be the reason for the bootloop?
[Galaxy S I9000 Android Development] mialwe:
The bootloops occur without doing a Nandroid backup, too.

I'll throw in my own observations, please correct me if I'm wrong in any point:

- bootloop occurs if using "adb reboot recovery"

- bootloop cannot be cured via flashing an ICS boot.img (Heimdall tested)

- bootloop can be cured via flashing a Gingerbread zImage (Heimdall tested)

- flashing the ICS kernel CWM-zip causing the loop again works without bootloop

I'll try to get some logs if it happens again, not sure they are available during the loop but maybe...
[Galaxy S I9000 Android Development] krarvind:
yo stratosk, most if not all extended power menu is based of this commit from CM

https://github.com/CyanogenMod/andr...3ba99507d54808293739d127ac0a22786c810b#diff-7
[Galaxy S I9000 Android Development] bhu1:
@stratosk, i respect ur initiative. But i think this is related to manufacturing of particular sgs(s). My phone till now has never gone into such bootloops on ics, no matter which kernel i try. My phone was manufactured in feb 2011. Maybe in later batches of sgs they changed some HARDWARE stuff.
[Galaxy S I9000 Android Development] krarvind:
Never experienced this and i have done this many many times via pc

When bootlooped and i lose recovery, i am always able to get it back via heimdalling my kernel boot.img

Haven't had to do this

Good to know but i never had to do this

[/QUOTE]
[Galaxy S I9000 Android Development] mialwe:
Sorry, just wanted to help with some observations.

Happened to me via "adb reboot recovery" (using this every 10 minutes while testing kernel stuff) just a few minutes before seeing this thread. Flashing ICS boot.img did not help, flashing GB zImage did. Flashing same ICS kernel via CWM again: successful boot. Same for 4 or 5 similar incidence I had during the last few weeks.
[Galaxy S I9000 Android Development] krarvind:
Same here, was just responding, not refuting your obs. cheers
[Galaxy S I9000 Android Development] Bejda:
Most common step i've heard about or experienced myself could be a dalvik-cache wipe then boot with Pawitp's kernel.
[Galaxy S I9000 Android Development] ak:
bootloop

Bootloop in my opinion is present, and in some cases frustating.

In my case it occurs when i have the phone connected to pc and i make this steps for flash a new rom:

- wipe cache and dalvik

- format system

- install flash from zip

- reboot

It doesn't occur when i flashing without connected usb cable.

NB:

3 buttons combo for recovery doesn't work anymore after this problem.

I have tested with Devil Kernel and Semaphore only. :cool:
[Galaxy S I9000 Android Development] mialwe:
But if recovery is lost there's no way to wipe dalvik cache?

Krarvind, you wrote about "adb reboot recovery" that "Never experienced this and i have done this many many times via pc" - so how did you reboot to recovery before you got a loop?
[Galaxy S I9000 Android Development] Bejda:
It's difficult to log cause when usb plugged phone get stucked at power off screen between kernel image and device boot.Have to go fast!

I only remember something about "can't write to data" but didn't saved the log...was a simple reboot and don't remember kernel or rom I've been using at this moment.

@mialwe: yes,i meant a possible step that can trigger/produce the los recovery btlp.
[Galaxy S I9000 Android Development] krarvind:
So far only time i got bootloops is if my zip files didn't flash correct, for eg, my base flashes and my essentials wouldn't or if i were to flash only base and not essentials.
[Galaxy S I9000 Android Development] super_extreme:
One time, long ago, so I don't know what was before, I wanted to start the phone, then it showed bootloader screen, then kernel, died and started again, bootloader screen, kernel screen, ...

I removed battery, inserted it and it started normally?!? :confused:

Sorry if this was spam! :rolleyes:
[Galaxy S I9000 Android Development] ak:
but in this scenario at least 3 buttons combo have to work ... but for me never work ...
[Galaxy S I9000 Android Development] chris59264:
Idem with kernel devil.wipe cache and wipe dalvik = loss of recovery
[Galaxy S I9000 Android Development] malcho:
Once when i lost recovery on semaphore i managed to get it back by long press three buttons for recovery.

I hold that buttons for a minute and suddenly recovery appears.

It's always different situation no pattern to discover what is wrong.

These things happens to me since upgrade to IMM76D.Maybe there is the problem.
[Galaxy S I9000 Android Development] ghul21:
Hello

I change kernels, always in the same way with cernel cleaning script.

I had an unpleasant incident recently when changing the Devil 0.7.2 kernel on an older version 0.6.7. I do not know what are the differences at the binary level.

I tried to fix via recovery cwm and I managed to fire recovery. Unfortunately, it was probably an old version which in no way able to handle packages with our roms.
[Galaxy S I9000 Android Development] Mangus_U*RA:
In my case...I had bootloops with no recovery (blwnr lol), just after flashed an updated cm9 nightly and cleared cache+dalvik (happened 2 times in one month).

Then..."reboot system now"....and I get blwnr :D

edit

ps: when I read blwnr...I read "blown her"....i'm sick...
[Galaxy S I9000 Android Development] Zatta:
I would suggest you to remember that the purpose of this thread is to figure out why the problem occurs and find a solution to the problem. Heimdalling out of it is what I call a workaround, not a solution.

Taptalked u see
[Galaxy S I9000 Android Development] duffymm:
in my experience, i've encountered the bug of the thread 1 time, and a friend of mine twice.

if i remember right, in all the 3 cases the bug happened when we upgraded from one nightly to the next one with USB cable connecte to the computer.

i mean, copying file with USB to the phone (the cm9 nightly .zip)

going to recovery

installing the cm9 .zip

reboot

with usb cable still connected, after that, i never installed any kind of .zip with USB cable plugged and connected to the computer
[Galaxy S I9000 Android Development] Bejda:
Yeah many have thought about the usb plugged factor (including me when the story began) but no,others reports and mine doesn't confirm this.
[Galaxy S I9000 Android Development] mialwe:
Well, I think I add one report about USB now. Just flashed another ROM to test,

- booted fine with default kernel

- reboot to recovery with 3-button-combo -> stuck at kernel logo

- downloadmode-flash of mnics-20120509 -> bootloop

- pulled USB + reboot

=> boots up fine. Strange.
[Galaxy S I9000 Android Development] GreenSGS:
As you mention that,I remembered when I had sudden and only bootloop without reason and yeah, phone battery was low and I had USB plugged in and I must say I only succeeded to recover, when I unplugged USB. May be coincidence but true.

I +1 usb connected factor.
[Galaxy S I9000 Android Development] stratosk:
Can you reproduce boot loops rebooting in recovery with USB plugged in?

Could you please PM me ROM's name?
[Galaxy S I9000 Android Development] Bejda:
Could be another "probability factor" (or something like this) indeed.

The fact that so many peoples are seeing/feeling a correlation is to take into account... even if you as me did have unexpected cwmless kernelloops while unplugged too.
[Galaxy S I9000 Android Development] mialwe:
- no, boot to recovery now is fine with mnics-20120509 (downloadmode flash)

- ICS333 RC4

- last_kmsg attached
[Galaxy S I9000 Android Development] Mangus_U*RA:
My two bootloops cases was both with usb cable UNplugged.
[Galaxy S I9000 Android Development] spoonymoon:
Works

This is a way i found out myself, i know its ´funny´way but it gets me backup and running in under 5 m.

I get a bootloop situation somehow...??

Go into download mode flash this tar in Odin

(Voodoo-test-6.0-Gingerbread-JVH-GT-I9000-odin-pda.tar)

giving me a start up screen that dont boot up, but then pull battery , use 3 button combo getting me into recovery again (which i could not before) i dont have access to external drive, but have this rom permanent on my internal sd

(ics_4.0.3_mr1-rc4.1_i9000.zip) flashing it, makes no errors and boots system up fine, with most settings intact, then i go into CWM and external is there again, then restore what backup i want..and voila :D

works every time on every setup i´ve tried.

http://speedy.sh/BvUHz/Voodoo-test-6.0-Gingerbread-JVH-GT-I9000-odin-pda.tar

Link is both files

Peace bRoS :)
[Galaxy S I9000 Android Development] Bejda:
I see some common lines with mine from previous page,

Internal error: oops: 17

Long serial numbers lines

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

Kernel panic - not syncing fatal exception.rebooting..
[Galaxy S I9000 Android Development] greasyguy:
+1

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] Bejda:
I did have AND did not have bootloops while flashing/rebooting with plugged usb AND unplugged,i deserve two thanks and four +1 :)

I've just recovered from bootloops using Mnics-20120509-7-LR.tar but...

Was on cm9 based rom with latest cm9 kernel and flashed Devil2-0.79 (the kernel create a backup folder in init.d,he puts all scripts found there)

The thing is i wasn't at home (no adb) and flashed the Mnics.tar with auto-reboot ticked. Was happy when i saw bootanimation starting waiting to chek and send here the last_kmsg.bak in /data but there wasn't any,only user.log with apparently nothing special.

Surely i'm missing something but i don't get it cause now after reboot i still can't see any kmsg files,only users logs.

It's the first time i flash Mnics since 202,something changed?

Edit:must say i did see reworked/data user.log in the changelog of Mialwe's topic and still have the concerned user.log:

http://dl.dropbox.com/u/25071013/last_user.log.txt
[Galaxy S I9000 Android Development] mialwe:
So thats +1 thanks from me now :)

- nice to hear MNICS helped to recover

- nice to hear user.log did show "apparently nothing special" - that's the reason I developed this for - to check if the MNICS initramfs/settings/tweaks works as it should.

MNICS does not copy last_kmsg for you as other kernel (devil?) does. The default Android/Linux way to get the logs is using either ADB or a terminal emulator app as root:

cat /proc/last_kmsg > /data/local/last_kmsg.log

The file /data/local/... can be named as you like as well as you can choose the directory to use, e.g. /sdcard/bootloop.log would work fine, too.
[Galaxy S I9000 Android Development] Bejda:
Ah my bad, seeing /data user.log concept with kudos to you i thought you we're behind the /data last-kmsg too and didn't noticed my confusion until now :)

Thanks for the adb log how-to, i see now the errors i made last time i tried.
[Galaxy S I9000 Android Development] dastinger:
Hi guys.

A friend's SGS is bootlooping atm. He's coming over tomorrow for me to solve the issue. My question is, are there any logs that may be useful? He didn't have logger enabled so I don't know if any will be available but, if there is, could you tell me where they are stored? He was with Semaphore 1.1.1s.

Anyway, I'll report back tomorrow to let you know what saved the phone.
[Galaxy S I9000 Android Development] thaidroid:
Since CWM5 I have had problems with Full restore from CWM backup, always ending up with boot loop. Restoring data only has been problem free.

Then I tried to go to mounts and storage and mount everything before running the CWM backup. Also Mounting everything before doing restore. Somehow this seems to work, I can do a full CWM restore including system and not end up with boot loop:)

I'm on ICS333 and the problem I'm describing is when I've flashed an other rom and then wanted to go back to 333 via restore.

Works for me...so you never know:D:D

I dont think it's kernel related it's a CWM thing in my opinion since in CWM3 there never was such a problem

Most of the time I will do restores etc with a USB charger attached but not a USB data cable(I use airdroid)
[Galaxy S I9000 Android Development] dastinger:
So, just solved the issue. Wasn't as easy as I thought it would be.

1 - Flashed Semaphore 1.1.2.tar using Odin and still, no Recovery;

2 - Flashed Midnight 0.9.0 and got Recovery;

3 - Flashed Semaphore 1.1.1s and only got Recovery. Couldn't even boot unless to Recovery. Strange thing is, everytime I connected the USB cable to the phone, it would immediately enter Recovery :confused: ;

4 - Flashed Slim 3.6 + Essentials and, same. Only Recovery (with the USB thingy);

5 - Tried with Devil 0.79 this time -> Bootloop;

6 - Flashed Midnight 0.9.0 again and got Recovery;

7 - Finally tried Glitch V14 B6 and it booted :)

Now flashed Semaphore 1.1.1s after a successful boot into the Rom and everything is fine.
[Galaxy S I9000 Android Development] test123456789012:
Current stable setup for weeks:

ROM: SlimICS 3.5

(previous) Kernel: Semaphore 1.1.1s

Everything else: Stock SlimICS

What I did to get a bootloop:

Went into Semaphore CWM, wiped dalvik-cache and cache, cleared init.d.

rebooted the phone from recovery menu.

Phone boots to the second semaphore logo then loops.

What didn't solve the bootloop:

Went into recovery and flashed Semaphore 1.1.1s via Heimdall:

mbj:~ XXX$ heimdall flash --kernel /Users/XXX/Downloads/Android\ restore\ Heimdall/zImage

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

What solved the problem:

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

mbj:~ XXX$ heimdall flash --kernel /Users/XXX/Downloads/Android\ restore\ Heimdall/boot.img

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

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

Phone reboots normally into ROM.

Icy Glitch recovered my phone several times successfully in the past. So did latest Speedmod for GB, flashed via Heimdall. But I don't use Speedmod for that purpose anymore, because of the older CWM.

Hope this post is of any help.
[Galaxy S I9000 Android Development] ivanchin99:
I can vouch for that. Met with the dreaded bootloop after wiping cache & dalvik and then reboot.
[Galaxy S I9000 Android Development] aladin6:
I think that this change from the nightly of 13th is related with bootloop problem, no?
[Galaxy S I9000 Android Development] cdmackay:
That's a makefile change, i.e. a compile-time change, so it's hard to see how it could cause the inconsistent behaviours seen.

but then again, what do I know? :)
[Galaxy S I9000 Android Development] aladin6:
That bootloop is really a "headache" :D! For me, it never passed, i have never seen my SGS with CM9 :\! Weird weird problem, i hope that devs detect the source of the problem.
[Galaxy S I9000 Android Development] FadeFx:
ok, so this is my first look into this thread and i dont have the passion to read the whole thread first...

Rom: CM9

Kernel: Devil2.0.84

however, first i think there are two different types of those bootloops, one where you flash the kernel with odin and you are golden, the other one that after flashing the kernel only brings you to recovery when you try to boot. What i can say for sure is that both of them have nothing to do with those:

shutdown/reboot from power menu

shutdown/reboot with power button

flashing updates with usb/power cable connected

since i last time odin´d a stock samsung rom and checked repartition i have never expirienced the first type of bootloops again, but i had two of the second type. the last one i had today, my device was in my pocket and when i grabed it i was greeted by kernel splash...

this time i backed up my last_kmsg.txt and last_kmsg.txt.bak from my data partition (those files are Devil kernel specific) in the hope that they are of any help.

http://dl.dropbox.com/u/33802958/last_kmsg.txt

http://dl.dropbox.com/u/33802958/last_kmsg.txt.bak
[Galaxy S I9000 Android Development] mgroover:
I had this strange issue going from Slim 3.4 to 3.5 with a simple zip upgrade.

Did a nandroid backup prior to running the upgrade just in case, just a "safety habit" of mine.

Phone goes bootlooping and I try running the upgrade script again (BASE + Essentials) but still bootlooping so I run the nandroid. Phone does not go much more than a few seconds of trying to boot from the system partition (bootloader + kernel are ok) , looking at the syslog with adb during boot makes me pretty sure the backup has not been restored correctly as it's not finding files etc.

Did a full wipe of the phone, tried restoring the nand backup again as I could still access the recovery console and tried booting. Now it just bootloops on the kernel loader. Can't access CWM, it just reboots. Oh well, looks like the recovery part is dead also. So.. after ALOT of testing different things and still no success in getting in to recovery with 3-button combo I set it to download mode and reflash with a GB rom and work my way up again. 3.5 installed and good to go.

Same thing happened on the upgrade to 3.6 (bootloop and troubles) but this time I unplugged the ext sdcard for some reason. It wen't right past the bootloop no problems. Tried restoring the nand (habits never wear ;)) and inserting the ext sd again. Same thing.

I was able to fully replicate the issues I had going from 3.4-3.5 just by having the external sdcard plugged in.

From now on, I remove the external card as soon as I do an upgrade.

Worth mentioning is that I am only running the "stock" kernels for the Slim ROM and that I have had similar issues with both Dark Knight and different MIUIv4 flavours previously. Also tried with another sdcard but same thing.

This NEVER happened when messing around with GB ROMs and still doesn't seem like it does as I tried messing with some Darky and GB MIUI installs but with no issues.

Hope my novel helps someone in some way ;)
[Galaxy S I9000 Android Development] lerkin:
Just guessing. Guys, can those bootloops be because you backup-restore your nand backups to-from external memory (SD card)? I never had those bootloops (I know not all devices affected) and I always make my nand backup to internal memory. Used aokp till m5, since then I'm on CM9 + latest stable devil kernel, usually flashing every other day.
[Galaxy S I9000 Android Development] pbecks1963:
no, i always (nandroid) backup to internal sd. Had lots of boot/cwm-loops (because i used to flash a lot of different rom's and kernel's) Now that i am "faithfull" to 1 rom and 1 kernel i haven't had any cmw-less kernel-loops.

[last statement isn't true anymore, upgraded my devil kernel and got a BOD]
[Galaxy S I9000 Android Development] AsfaltSame:
I could finnaly install devil kernel to my nightly without bootloop. I did not do any clearing of dalvik or cache, and I did a backup to my internal memory.
[Galaxy S I9000 Android Development] Bejda:
On the " recover from cwmless bootloops " side i always had, as @Saszseb, 100 % success with initial cm7.tar with odin.

Good thing now is i'm getting about the same stats (5/5) with MnIcs 20150509 LR.tar.

Cwmless bootloops occurs > flash MnIcs 20150509 LR.tar auto-reboot ticked > boots fine :)

Sad thing is i'm unable to grab last_kmsg log with adb. Obviously i could get more used to it that i am now but it says errors (file or location doesn't exist) and finally gives me empty last_kmsg file :(

So,question goes right to the point to Mialwe...: sorry but could it be possible to include, even punctually for testing purposes, the automatic last_kmsg (+.bak) to /data process from Devil in your kernel? :o

I think i could produce many maybe useful logs that way.
[Galaxy S I9000 Android Development] ratl0lz:
Nope it can't.
[Galaxy S I9000 Android Development] pbecks1963:
any progress?

Hello guys,

Is there any progress in finding the cause of bod (bootloops off death)?

Just flashed a newer devil kernel over the previous version and choose to "reboot to recovery". Gave me a bod. (everythings fine now, bye the way)
[Galaxy S I9000 Android Development] Bejda:
By bod you mean phone boot image >kernel boot image >back to device boot image > etc..etc... and no access anymore to recovery?

Just to be sure ;)

By the way newest Devil version comes with an odin flashable .tar

When i tried it coming from another kernel just for testing my own made .tar it didn't produced last_kmsg,only user.log

I think it's because i didn't had /data/local/devil folder at this moment and it hasn't been created cause if i remember well after many reboots there still wasn't any last_kmsg in /data and they appeared once i created /data/local/devil folder

Then if one using another kernel and counting on devil's tar to recover from cwmless bootloops and grab a last_kmsg log maybe it's better to create the folder before? But still i'm not so sure of it and it was own made .tar so maybe it's different with the one provided by DerTeufel.
[Galaxy S I9000 Android Development] Vertron:
I got a bootloop within 2 days of using the devil kernel overclocked to 1.2. I then changed to the midnight kernel overclocked again and got 2 bootloops in 2 days.

I then decided to leave it at stock clocks and it hasn't bootlooped for over a month.
[Galaxy S I9000 Android Development] chavez13:
Restoring recovery: really easy job!

I was on CM9 Nightly and I wanted to update the kernel to MNICS 202. I flashed the kernel zip file using CWM but my phone was stuck on a bootloop :(. It happened to me before, but the solution was a bit long and boring: flashed an official rom using Odin, then flashed a CWM kernel etc. This time I tried a new way: I simply went into download mode using the 3 button combo and flashed a new kernel via Odin. The result: my phone came back to life without losing anything.
[Galaxy S I9000 Android Development] stratosk:
Actually, not much progress.

But from this thread came up a new initramfs approach that Mialwe and myself developed.

At this time MNICS, Devil, Semaphore and Slim's kernel use this new initramfs. The first 3 kernels also available as ODIN/Heimdall flashables.

Maybe, this works as a workaround and will reduce bootloops.
[Galaxy S I9000 Android Development] Bejda:
Hello Stratosk, maybe reduced but not eradicated unfortunately. And i went through complications another day for recover from Bod (let's call it like that) using any of the three new initramfs based kernel with odin but it could be another reason so let's put it aside.

I'm still wondering about the last_kmsg me and Mialwe had the " chance " to grab, those that came with :

Internal error : oops : 17 PREEMPT

Long serial numbers lines

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

Kernel panic - not syncing fatal exception.rebooting

By searching for "internal error : oops : 17 PREEMPT" I found many Linux related subject but didn't see any real reason/explanation for it.

When it comes to android (typed my search on xda) it is often on tablet devices and mostly comes with (sorry i don't remember well) " internal error : oops : 17 PREEMPT" something about /sys and the "unable to handle Kernel..." (still if i remember well) shows something different. Edit:Not so sure about the Android tablets giving something different about unable to handle etc...but sure it mostly comes with /sys/..something error.

Anyway, that's when i saw that the latest Devil put a last_version binary file in /system that i thought about this all.

Here's the file:

http://db.tt/QzfD3Ott

I did lots of reboots, flash and Devil's kernel tests today without any Bod but you know well it's not giving any proof it could helps to prevent.
[Galaxy S I9000 Android Development] stratosk:
I'm sorry but I'm not sure I understand your point.

Do you mean that the last_version file resolves boot loop issue?
[Galaxy S I9000 Android Development] paintball23456:
im not a dev :(but i have always left my phone in the bootloop and it resloves it self in the end in like 10min:D:D:D just thought this might be helpful