[Galaxy S II General] v1p.:
I was able to recover from this dreaded condition

Hey guys. I got my S2 recovered from this dreaded state of ****. I have ran through all of this thread, & have seen that only suggested solution is to data/factory reset your fone.

Well, I have done that 7 times in last 2 months & this was 8th time yesterday, that it went into Bootloop after hanging-up upon trying to visit this site "exploretouch.ie" in stock browser.

Following are my ROM's details :

ROM: Stock - XXLS8

Build# : JZO54K.I9100XWLSD

Kernel : Philz-Touch 4 (CWM Base Version: 6.0.2.8) [I beg pardon, I don't know if this is correct info, but this is what I see when I start recovery.]

I was really frustrated with this random but frequent affair of bootloop. So I booted into recovery. I was trying to analyse the cause of dumpstate log, by actually going through it, well, I am a 'nobody' on android dev, so could found anything that seems a logical reason for this. but ye I saw mascare of apps, almost every , with "- has died" suffix :laugh: near this line :

05-10 22:36:26.483 2192 2763 I ActivityManager: Process com.google.android.gms (pid 9363) (adj 10) has died.

.

.

05-10 22:36:26.693 2192 2516 E android.os.Debug: !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_watchdog

.

..

05-10 22:36:26.758 2192 5508 I ActivityManager: Process com.android.MtpApplication (pid 8416) (adj 11) has died.

Solution : This is what I did, though it seems obvious but I couldn't find it anywhere.

I manually triggered e2fsck, while booted into recovery mode. :fingers-crossed:

I used this command : /sbin/e2fsck -fy /dev/block/mmcblk0p10

/dev/block/mmcblk0p10 is the /data

Although if I gave it -p switch, e2fsck returned Segmentation fault ( ! ) :confused:

So it ran through for a while, around 5-8 min. With this as the end :

/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p10: 13806/131072 files (8.7% non-contiguous), 349525/524288 blocks

After that I started my phone & booted up pretty well, with no loss whatsoever ( i.e no need to install apps again, as they are there, useable a well )

So I have couple of questions here to ask, if someone can help me out :

1. Why does the e2fsck isn't triggered at every such kind of phone reset (either hung-up or with battery yanked out) ?

2. There's still no clue what caused the dumpstate to trigger, and as soon as it finishes, phone simply dies. This is the list of "died" apps in chronological order in dumpstate log.

05-10 22:03:34.734 2192 2552 I ActivityManager: Process com.sec.android.widgetapp.SPlannerAppWidget (pid 8087) (adj 0) has died.

05-10 22:03:34.819 2192 5508 I ActivityManager: Process com.sec.android.widgetapp.SPlannerAppWidget (pid 8122) (adj 0) has died.

05-10 22:21:48.743 2192 5508 I ActivityManager: Process com.sec.android.daemonapp.ap.accuweather (pid 6143) (adj 12) has died.

05-10 22:27:44.018 2192 2811 I ActivityManager: Process com.samsung.helphub (pid 7756) (adj 11) has died.

05-10 22:27:44.023 2192 2957 I ActivityManager: Process android.process.media (pid 4758) (adj 11) has died.

05-10 22:27:44.173 2192 5508 I ActivityManager: Process com.google.android.apps.plus (pid 3449) (adj 11) has died.

05-10 22:35:43.318 2192 5508 I ActivityManager: Process com.sec.pcw:CameraAutoUpload (pid 8401) (adj 11) has died.

05-10 22:36:26.483 2192 2763 I ActivityManager: Process com.google.android.gms (pid 9363) (adj 10) has died.

05-10 22:36:26.693 2192 2516 E android.os.Debug: !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_watchdog

05-10 22:36:26.758 2192 5508 I ActivityManager: Process com.android.MtpApplication (pid 8416) (adj 11) has died.

05-10 22:36:26.953 2192 2204 I ActivityManager: Process com.google.android.partnersetup (pid 9058) (adj 11) has died.

05-10 22:36:26.963 2192 2202 I ActivityManager: Process com.sec.android.widgetapp.favoriteswidget (pid 6595) (adj 10) has died.

05-10 22:36:26.963 2192 17639 I ActivityManager: Process com.google.android.googlequicksearchbox (pid 9000) (adj 10) has died.

05-10 22:36:26.963 2192 5509 I ActivityManager: Process com.sec.android.app.clockpackage (pid 30171) (adj 10) has died.

05-10 22:36:38.168 2192 2811 I ActivityManager: Process com.sec.android.widgetapp.programmonitorwidget (pid 8561) (adj 11) has died.

05-10 22:36:38.188 2192 9337 I ActivityManager: Process com.google.android.gm (pid 9318) (adj 11) has died.

05-10 22:36:38.203 2192 2551 I ActivityManager: Process com.google.android.gsf.login (pid 5146) (adj 10) has died.

05-10 22:37:03.703 2192 2763 I ActivityManager: Process com.sec.android.widgetapp.ap.hero.accuweather (pid 8347) (adj 11) has died.

05-10 22:37:15.808 2192 9337 I ActivityManager: Process com.sec.android.sCloudRelayData (pid 8663) (adj 10) has died.

05-10 22:37:15.818 2192 5509 I ActivityManager: Process com.android.MtpApplication (pid 9707) (adj 10) has died.

05-10 22:37:16.138 2192 17640 I ActivityManager: Process com.samsung.helphub (pid 9562) (adj 10) has died.

05-10 22:37:17.178 2192 17640 I ActivityManager: Process com.sec.android.sCloudBackupApp (pid 9764) (adj 10) has died.

05-10 22:37:17.213 2192 3082 I ActivityManager: Process com.sec.android.app.controlpanel (pid 8590) (adj 10) has died.

05-10 22:37:17.623 2192 2957 I ActivityManager: Process com.google.android.youtube (pid 9782) (adj 9) has died.

05-10 22:37:30.028 2192 2549 I ActivityManager: Process com.sec.android.provider.badge (pid 7704) (adj 10) has died.

05-10 22:37:30.243 2192 2202 I ActivityManager: Process com.google.android.apps.uploader (pid 9678) (adj 10) has died.

.... weew .. They are tooooo many :silly:. So any of these apps is the one on which the blame goes ?

3. Can we edit any startup script to enable e2fsck on /data & /system partitions ?

Many Thanks