yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Adevem:
lmao alright. i just thought no one is having the issue anymore ;p

1. download the kernel file and the rom file, put it on your internal sdcard.

2. boot into CWM recovery.

3. flash whatever kernel you like(i'm sure most are fixed now.) -

do not reboot after flashing!

4. now go to mounts and storage - mount /system and format /system

5. flash the rom and flash the kernel again -

all without a reboot

6. you can select reboot now. if previously you had a lagfix applied, you'll get a prompt about configuration changes. just select "No, remove the new config" or something like that.

7. do not flash any kernels with /system corruption from now on, or you're gonna have to go through everything again.

hope i made sense ;)

oh yea since you're using a non-wipe version. it will keep your settings. some settings might not retain as JPU changed some things. so refer to my guide here and you should be good.
[Galaxy S I9000 Android Development] Skin1980:
Thanks for this usefull thread!
[Galaxy S I9000 Android Development] aleksa55:
Thanks

fixed
[Galaxy S I9000 Android Development] pwhooftman:
Found this in user.log when using Voodoo Lagfix in YA/OK:

Hi Supercurio,

I always have suffered from a Force Close during boot when using Voodoo (one buzz, followed by 3 short buzzes a few seconds afterwards), even with the Stock Kernel JPA. Currently i'm using YA-OK with Voodoo Lagfix enabled, and still have 1 Force Close during boot. First i thought it was YA-OK related, but when i realized i used to suffer from a boot-FC with JPA also, i beg to differ.

However, i have a user.log in /system (no CAPS there fortunately) which reads:

/sbin/post-init.sh: cd: line 214: can't cd to sbin/init.d
Tue Nov 23 07:31:10 CET 2010 USER EARLY INIT START
Tue Nov 23 07:31:10 CET 2010 USER EARLY INIT DONE
Tue Nov 23 07:31:10 CET 2010 USER INIT START
Tue Nov 23 07:31:10 CET 2010 USER INIT DONE
mount: mounting /dev/block/stl9 on /system failed: Device or resource busy

Is this 'corruption' related?. I have always felt that enabling ext4 speeds the phone up during boot so much, that the boot order is messed up and media scanning tries to kick in before everything is mounted or something like that. Or maybe i'm just talking nonsense.
[Galaxy S I9000 Android Development] Gohst_oc:
My user.log says the same as the one from pwhooftman.

I used RyanZA LagFix a few months a go (a very early version).

I did unlagfix and flash JPM with Odin (Re-Partition on).

And still a corrupted RFS?
[Galaxy S I9000 Android Development] Cy4n1d3:
user.log existant does not mean your system is corrupted. It could just be a hint...
[Galaxy S I9000 Android Development] Sloogy 82:
user.log

device or resource busy

and that on each position

is that n corrupdet system?
[Galaxy S I9000 Android Development] coldhandz:
Hi Supercurio.

After flashing the fix kernel would I have to flash the snapshot Voodoo5 or is the fix kernel stable to run as it is?

Thanks

Great work by the way!!!

Seems a lot of SGS's are in this way:(
[Galaxy S I9000 Android Development] benoitb85:
How can i check if /system is in RFS or EXT4 ?

I tried

df -h

and

cat /etc/fstab

but I don't see this information.
[Galaxy S I9000 Android Development] kalpik:
mount | grep /system

Then look for check=no
[Galaxy S I9000 Android Development] supercurio:
If you used ULF-based kernel, /system is in RFS. "NO RFS" mode is just a name, /system is still in RFS.
[Galaxy S I9000 Android Development] supercurio:
I'm preparing a 2x faster version

log:

2010-11-23 09:39:10 model detected: 8GB
2010-11-23 09:39:10 filesystem detection on system:
2010-11-23 09:39:10 RFS on /dev/block/stl9
2010-11-23 09:39:10 filesystem detection on dbdata:
2010-11-23 09:39:11 Ext4 on /dev/block/stl10
2010-11-23 09:39:11 filesystem detection on cache:
2010-11-23 09:39:11 Ext4 on /dev/block/stl11
2010-11-23 09:39:11 filesystem detection on data:
2010-11-23 09:39:11 Ext4 on /dev/block/mmcblk0p2
2010-11-23 09:39:12 debug mode enabled
2010-11-23 09:39:12 convert system (/dev/block/stl9) from rfs to rfs
2010-11-23 09:39:12 check space for system:
2010-11-23 09:39:12 free space: 1269 MB
2010-11-23 09:39:12 space needed: 262 MB
2010-11-23 09:39:15 make a limited copy of /system in ram
2010-11-23 09:39:18 backup system
2010-11-23 09:40:20 time spent: 60.10s
2010-11-23 09:40:20 format /dev/block/stl9
2010-11-23 09:40:20 format system as RFS using Android init + a fake init.rc to run fat.format
2010-11-23 09:40:28 restore system
2010-11-23 09:41:35 time spent: 65.49s
2010-11-23 09:41:38 manage fat.format in /system/bin
2010-11-23 09:41:38 fat.format wrapper already installed in /system/bin
2010-11-23 09:41:38 running extension: empty.sh
2010-11-23 09:41:38 running init !
[Galaxy S I9000 Android Development] igniztion:
Tried flashing the K9 kernel, stuck on boot logo. Tried ADB and it says /system/bin/sh: not found.

Back to older speedmod kernel and it boots again. I will try the CWM backup method mentioned above and check back with the results. Might be a long shot though, as it seems my filesystem is already corrupted properly.
[Galaxy S I9000 Android Development] GemPatsu:
Hey I´m confused!

I´m using Doc´s Rom ADJP5 v8.0.1 with no lagfix aplied at the moment, but I used "NO-RFS advanced (a=e4)" lagfix before. So should I use this Kernel and can I with Doc´s Rom?

- So at the moment I would have to flash the .tar file via Odin as PDA with no

repartition, right?

- Will there be a flashable Update .zip?

Thanks
[Galaxy S I9000 Android Development] supercurio:
NO-RFS advanced use use /system as RFS and corrupts it.

Yes, and if someones else makes it there will be an update.zip, help is welcome!
[Galaxy S I9000 Android Development] benoitb85:
Thanks, it confirmed that I'm on rfs and I don't have this check=no mount option.

So I think I might be affected by the corruption.

The fix provided is a kernel (if I look inside the tar file). I think I have the kernel Universal-341-RAM-FROYO.tar as I flashed my galaxy S following this procedure:

http://galaxys-team.fr/viewtopic.php?f=18&t=3601&start=0

Will applying the fix make any other changes (than fixing /system) to my OS ?

By the way, I've frequently had an annoying issue on my phone where the pictures (mainly), the videos (sometimes) and the music (rarely) get listed 2/3/4 times in gallery, movie player, and music player. The actual files on the SD cards are not duplicated.

The fix is to delete the Media Storage data from application management and reboot.

Could this be related to a /system fs corruption ?
[Galaxy S I9000 Android Development] supercurio:
Okay, the 2x faster version is online.
[Galaxy S I9000 Android Development] GemPatsu:
Thanks a lot.
[Galaxy S I9000 Android Development] toansta:
supercurio, flashed the kernel as pda (no partition) but it doesn't work for me?

was there a baseline pre-requisite kernel that i needed to be on?
[Galaxy S I9000 Android Development] supercurio:
Yes, PDA, no-repartition. no pre-requisite.
[Galaxy S I9000 Android Development] toansta:
THANK YOU supercurio!

works :)

so everything is fixed now? i can apply hardcore's kernel (K9) after this?
[Galaxy S I9000 Android Development] supercurio:
Yes, or Voodoo 5 snapshot;) Or any proper kernel.
[Galaxy S I9000 Android Development] MrBusiness:
Hi, I just want to check if I am right, I want to provide a German tutorial for all our forum members which aren't able to follow the English instructions ;)

I am on hardcore Kernel K8 (which means old ULK) or another older ULK build.

step1) disable all lag fix options

step2) disable all startup tweaks

step3) flash voodoo rfs fix kernel

step4) let it boot and convert everything

step5) change kernel to latest voodoo or latest hardcore (k9)

Please confirm, thank you!
[Galaxy S I9000 Android Development] coldhandz:
Supercurio, I was just wondering if the disable lagfix option currently works on the Voodoo snapshot?

Thanks

Ps does the Voodoo snapshot maintain 2e recovery?
[Galaxy S I9000 Android Development] igniztion:
This doesn't work because system is already corrupted. It just restores the corrupted system over the newly formatted /system.

Seems like the way to go is to flash a stock PDA as supercurio mentioned.
[Galaxy S I9000 Android Development] jurguh87:
By the way, I've frequently had an annoying issue on my phone where the pictures (mainly), the videos (sometimes) and the music (rarely) get listed 2/3/4 times in gallery, movie player, and music player. The actual files on the SD cards are not duplicated.

The fix is to delete the Media Storage data from application management and reboot.

Could this be related to a /system fs corruption ?[/QUOTE]

have had the same problem here all pictures where duplicated or even trippled but only on the gallery

anyone have a clue??

i also have a file on my internal sdcard with lost.dir and also on my ext.sdcard and inside the file i got several files with big numbers as names

does anyone know what it is and how it gets there
[Galaxy S I9000 Android Development] toansta:
sorry supercurio, i thought it had worked because i heard the voice say step 1 so i went to get a drink.

i never heard it say step 2, and so the phone never booted.

something wrong in the script maybe?
[Galaxy S I9000 Android Development] Jonathan_m84:
you can easily fix this by deleting using rootexplorer:

dbdata/databases/com.cooliris.media/

and

sdcad/android/data/com.cooliris.media/

and then reboot
[Galaxy S I9000 Android Development] coldhandz:
have had the same problem here all pictures where duplicated or even trippled but only on the gallery

anyone have a clue??

i also have a file on my internal sdcard with lost.dir and also on my ext.sdcard and inside the file i got several files with big numbers as names

does anyone know what it is and how it gets there[/QUOTE]

Not sure if it's connected but that happened to me when I installed a Facebook app. All of a sudden my pictures doubled/tripled! Not sure if it was a sync issue. Deleted the app and had to remove the duplicate photo's manually.

Possibly check if >show hidden files> is checked. in >My Files/menu/more/settings
[Galaxy S I9000 Android Development] coldhandz:
Or flash the fix.tar then Voodoo snapshot?
[Galaxy S I9000 Android Development] supercurio:
Yes

And 2e recovery is not useful as it contains CWM.
[Galaxy S I9000 Android Development] miragebg:
So which lagfix is recommended after flashing K9 kernel on repaired RFS system?

P.S

I am really sorry for my noob question, but could someone tell me what to do exactly to know if my FS is corrupted?

I am using YA-OK kernel with NO-RFS Advanced (a=ext4) lagfix...
[Galaxy S I9000 Android Development] titooo7:
Hi supercurio,

It would be really nice if you can upload the fix to be used also through cwm.

I won't have access to odin till the evenign and I want to fix that issue asap

thanks in advance!
[Galaxy S I9000 Android Development] MrBusiness:
Could anyone comment on my previos posting, is this the way to go?

http://xdaforums.com/showpost.php?p=9373544&postcount=40

EDIT: Download down for debbuging, interesting ...
[Galaxy S I9000 Android Development] supercurio:
Hi MrBusiness!

step1) disable lagfix options only if it's JFS

step2) flash Voodoo /system RFS fixer

step3) wait 3 minutes

step4) install a non-buggy kernel :)
[Galaxy S I9000 Android Development] supercurio:
Yes that's the main reason why I did this, to provide an easy solution for people who want to switch to Voodoo kernel from broken ULF.
[Galaxy S I9000 Android Development] pwhooftman:
Corruption: How & what clear, but 'why'?

I understand how corruption starts, and what the signs of corruption are, but i'm still puzzled why it occurs (as you can tell, i still think there are rational answers in the RFS world:-))

Corruption starts when check=no is not used. I presume this means that when /system is mounted without check=no, a check is performed. How can a check lead to corruption?. Or is it that the check might find inconsistencies, and a work around is stored in the RFS system (like reallocating blocks) which only can be read if subsequent mounts also include a check? So, mounting with check=no is just a crude way to ignore inconsistencies so the system will at least boot?

And was this present in original Samsung Kernels also, or did this creep in when ULF kernels where invented?

PS. Many many thanks for all your efforts
[Galaxy S I9000 Android Development] supercurio:
I believe there are 2 different working mode for the RFS filesystem. One without "check=no", and one with "check=no".

Both are incompatible.

And that's once again a terrible design. In my tests, it's not related to filesystem checking or not because if you mount with check=no a corrupted fs it's detected and a user.log is written.

The name "check" is probably a very unfortunate choice.
[Galaxy S I9000 Android Development] CyberT3:
So how should i proceed? I have doc's XWJPA v7.6.2, enabled all tweaks, lagfix disabled. Should i just:

1. flash Voodoo /system RFS fixer

2. wait 3 minutes

3. install a non-buggy kernel

or do i need to do something else before. And one more question do i have to do this with odin because i never used it before (only cwm)? Thanks!
[Galaxy S I9000 Android Development] pwhooftman:
They should have named that option "voodoo", just as mysterious :D

Thanks for your swift reply.
[Galaxy S I9000 Android Development] hacksome:
ufff!... supercurio just tweeted that ULF can cause corruption in /efs.

That's dangerous guys.
[Galaxy S I9000 Android Development] miragebg:
Is there any chance that my phone is not affected, eventhough I am using YA-OK kernel+ Advanced NO-RFS ext4 and first three tweaks enabled?

Is it for sure that my FS will became corrupted in future?
[Galaxy S I9000 Android Development] supercurio:
Yes a few people on IRC told me their phone didn't worked anymore if they used a non-ULF kernel.

Good news is that it's recoverable if you're not too unlucky (using a standard kernel can corrupt the corrupted /efs nvram forever, which means no more IMEI or baseband unable to start)

UPDATE: false alarm (even if 1 user has a non-working phone system)
[Galaxy S I9000 Android Development] mayday2:
I used Speedmod K8 with No-RFS ext4 before and then flash K9. I got no problem to boot up and use the phone. Is there any way to check if the fs has been corrupted or not before I reformat it? Btw, I find user.log and user.log.old under /system. Does it mean that I got corrupted fs already?
[Galaxy S I9000 Android Development] GemPatsu:
Hey trying to flash the fixkernel .tar via Odin but now I´m stuck on Galaxy S Bootscreen. The voice anounced step 1 but nothing further is happening.

I`m on Doc´s Rom ADJP5 v8.0.1.

Flashed via Odin 1.52 as PDA and no repartition.

Stuck there for about 20 min
[Galaxy S I9000 Android Development] miragebg:
Supercurio, please tell me how to check if my phone is affected and if it's not- is it enough just to flash K9 over my current config?

I have user.log and user.log.old , but nothing of other mentioned symptoms..
[Galaxy S I9000 Android Development] calvinbui:
better than me, just the bootscreen. on jp8
[Galaxy S I9000 Android Development] GemPatsu:
So after 30 min i pulled the Battery and installed the Rom which I still had on my SD Card. So at least my Phone boots again, but does this mean my System is that bad corrupted, that not even supercurio can work his voodoo on it anymore?
[Galaxy S I9000 Android Development] toansta:
+1 i seem to have the same problem still.

although i was on doc rom JPOv7.6.2 and using hardcore's kernel K9 i wanted to flash your kernel so i can fix everything and start from fresh again.

doesn't boot after step 1.

thanks for the help and hard work, supercurio

edit: previous post sounded sarcastic
[Galaxy S I9000 Android Development] yani2000:
In Terminal Emulator after "mount | grep efs" I get:

/dev/block/stl3 /efs rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

I use NO-RFS Advanced EXT4. (/system still in RFS :( )

For further details see my sig.
[Galaxy S I9000 Android Development] dehem333:
I also want to know this.
[Galaxy S I9000 Android Development] GemPatsu:
Sorry, didn´t want to sound sarcastic, I just need your Help. Serious, don´t want to offend anybody and I´m thankfull for all your work supercurio!
[Galaxy S I9000 Android Development] toansta:
LOL GemPatsu,

i meant my previous post sounded sarcastic, hence the edit.

not yours mate :)
[Galaxy S I9000 Android Development] Driekes:
I don't have a windows pc at my disposal at this moment, is it easy to create a .zip which I can flash using CWM? I am currently reading into Heimdall.. I have to find a .pit file in order to flash only the kernel fix? Anyone here who can help me on this?
[Galaxy S I9000 Android Development] bolmedias:
I kinda regret the No-RFS lagfix now >.
[Galaxy S I9000 Android Development] GemPatsu:
Ok, glad to hear, but sarcasm is a concept I hardly get in german so I´m totaly lost with it in english ;) .

End of topic

@toansta
[Galaxy S I9000 Android Development] supercurio:
My mistake, this was a false alarm.

There is no known kernel / ramdisk that corrupt /efs.
[Galaxy S I9000 Android Development] hacksome:
duh!..

That's better. :D
[Galaxy S I9000 Android Development] GemPatsu:
Second try same result,

tried to flash the fixkernel .tar via Odin and again beeing stuck on Galaxy S Bootscreen. The voice anounced step 1 but after that nothing happend. I was stuck on bootscreen for about 30 min before I pulled the Battery and flashed the Rom again.

I`m on Doc´s Rom ADJP5 v8.0.1.

Flashed via Odin 1.52 as PDA and no repartition.

Should I be more patient wait longer? Any suggestions or can I provide any more information?

Cheers
[Galaxy S I9000 Android Development] miragebg:
So after updating to K9 we cannot use any of NON-RFS lagfixes anymore, can we?
[Galaxy S I9000 Android Development] dannyyung:
hi curio, after the voodoo fix, I got a new voodoo folder and a file called "voodoo_system_conversion.tar". What do I do with them? Can I simply delete it or better to keep them as a backup or something?

ps: Thank you all to your hard work:)
[Galaxy S I9000 Android Development] miragebg:
After upgrading to K9, my SGS is stucked at first boot screen...tried to flash Voodoo repair kernel via ODIN- same result...stucked on boot screen... What to do now?

supercurio, help me please...

edit: it seems kinda looping there, boot screen- black screen for 1 sec and again boot screen...
[Galaxy S I9000 Android Development] supercurio:
Yes, you can delete it safely :)
[Galaxy S I9000 Android Development] supercurio:
Hi!

Please tell which version you used.

I would recommend to you flashing a stock firmware, or at least the system part of it.

If you can send the voodoo/logs directory, it will be helpful, you can grab it after restoring another firmware.
[Galaxy S I9000 Android Development] fuze_freak:
Curio if I flash a stock ROM and then upgrade to Doc's ROM, can I install k9 or voodoo without any problem ?

it is save ?
[Galaxy S I9000 Android Development] titooo7:
+1 please, I also need to install the fix with cwm

try flashin an stock pda file. Did you try that already?
[Galaxy S I9000 Android Development] miragebg:
Just flashing JM8 and upgrade to doc's rom all over again...

booted properly now, but is it safe to flash Doc's rom as long as it contains older version of Hardcore's kernel???
[Galaxy S I9000 Android Development] hacksome:
This may not be the right forum.. still.. Curio, do you have any plans to release the brightness fix (as we had on eclair - with very low minimums) with Voodoo?. My eyes hurt reading books on SGS!
[Galaxy S I9000 Android Development] fuze_freak:
what lagfix should we apply after k9 ?

I had on DOc's ROM the no rfs all ext4
[Galaxy S I9000 Android Development] mali100:
Hi supercurio,

here is a log from my sgs stuck on bootscreen:

http://dl.dropbox.com/u/7888343/logs.zip

I used voodoo-system-rfs-fixer-kernel-2
[Galaxy S I9000 Android Development] miragebg:
does full reflash to Eclair JM8 with repartition with ODIN remove completely this corrupted FS problem?

My Voodoo log of the fixer contains:

ERROR: unable to call fat.format: cancel conversion.
[Galaxy S I9000 Android Development] supercurio:
Yes, absolutely.
[Galaxy S I9000 Android Development] supercurio:
Thanks, i take a look at this
[Galaxy S I9000 Android Development] supercurio:
Okay.

OR :

- The filesystem corruption is too severe

- A script/lagfix deleted fat.format

my tool won't be able able to recover it
[Galaxy S I9000 Android Development] miragebg:
Master, is it safe to flash doc's modded rom and after first boot immediately to flash K9 kernel?

Is it dangerous for the FS with one single boot with older Hardcore kernel?
[Galaxy S I9000 Android Development] mali100:
Ok, I will reflash tonight, thanks anyway

edit: fat.format is in sbin, so it seems the corruption is to high
[Galaxy S I9000 Android Development] tomatenjungee:
hey supercurio,

thx for the nice explanation. I came from a ULF Kernel, flashed a stock firmware and then used your voodoo_snapshot (which is working awesome even with CWM). Well nearly like your explanation above.

My question: I didnt use your RFS-Fixer in this procedure ... am i alright that my system now cant be corrupted anymore (if it even was) ?

thx for an answer ... best regards :> keep up the g00d work
[Galaxy S I9000 Android Development] fuze_freak:
Hey curio I install jm9 after that Install Doc's ROM and without doing a restart I install k9 would that work ?

and with lagfix you recommend ?
[Galaxy S I9000 Android Development] hardcore:
You can, this /system problem has nothing to do with Non-RFS lagfixes, as all the lagfixes in ULFK don't touch /system. But the problem affects all ULFK users, even those that don't use lagfixes.
[Galaxy S I9000 Android Development] calvinbui:
jm8 did not work me.

i had to stock jm8, then update to jpo, then the fix worked
[Galaxy S I9000 Android Development] supercurio:
Hi hardcore!

Did you wrote a HOWTO fix the corruption issue using tools inside your kerneL ?

I'll make a link, or maybe you prefer writing directly to the second post, let me know, we're on the same boat here.
[Galaxy S I9000 Android Development] hardcore:
Hi curio. Its not a proven working procedure but it might work.

http://xdaforums.com/showpost.php?p=9371094&postcount=2709
[Galaxy S I9000 Android Development] coldhandz:
Supercurio:D

What optimizations are you working on for Voodoo5?:D

hehe
[Galaxy S I9000 Android Development] Driekes:
Unfortunately I am still working my way out of the noob area, but I am trying. I've succesfully installed Doc Rom 7.62, 3 button fix, CWM etc. Now I want to upgrade to K9, but I prefer a zip method instead of Odin, because I have a windows pc and I can only use Heimdall at this moment.

Could I use a flash zip for the K-9 and replace the zimage file with yours? Would that work or is that dangerous?
[Galaxy S I9000 Android Development] miketwn:
YUP...never used lagfix and had to reflash PDA...........
[Galaxy S I9000 Android Development] psychedelic'd:
Thanks for this fix supercurio. Worked without a hitch for me.

Just 1 question: Every time I boot into recovery now the fix starts by itself. Is there a way to stop this? Do I have to flash a different kernel?
[Galaxy S I9000 Android Development] gslayer1988:
AFAIK this is just a fix, after your done you can flash a different kernel.
[Galaxy S I9000 Android Development] zenkinz:
the main thing is mounting /system with "-o check=no" right?

and doing so is only to avoid any potential corruption, but not fix any corruption if it already occurs (in which case the device will not boot in the first place). Just want to make sure I got the context right as I have not been following the android development closely in the past few days
[Galaxy S I9000 Android Development] ragin:
Am I correct if I say that THIS FIX is for people who want to migrate from ULK to VOODOO? On the face it appears so. If I am sticking with ULK for some time to come, do I really need this FIX? If I want to go to a STOCK ROM, I would definately re-partition, format etc etc. :D