yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pele78:
good question...

i smell a massive flame coming...

atm nothing makes sense, coming on devs, quite frankly pigs will fly soon..

its really dont make sense, first a scare, then no really evidence or proper explanation...:mad:

i meam if this RFS SYTEM WAS SOOOOOOOOOOOO BAD why aint samsung being dealt with ? or is this some kind of white house republican food LOL

and the sgs 2 is rfs...so there must be a reason why samsung still uses it... especially with all the choices of file systems out there zzzzzzzzzzzz
[Galaxy S I9000 Android Development] kalpik:
Actually, there IS a problem.. Just that its not "explosive".. It *will* be fixed in the coming versions.. So no need to speculate..
[Galaxy S I9000 Android Development] pele78:
i know kalpik, not speculating but wow, all im asking is for a explanation as to whats going on, i mean ok lets jump the gun and paint a bigger picture :

OK wooooooot Bug found which f's up the system, fix on the way....

And thats it ?

no reason no explanation no nothing...LOL, well it seems like everyone who has flashed or sumink i dunno cause its just a guessing game now, has this bug right ?

regardless if used a lagfix or not ?

ok so its safe to say every SGS user in the world has this bug right? because of RFS System ? LOL ?

Kalpik.... its no speculation but it would be nice if some kernal mod or someone just explain what is going on for the wider community at least so we can learn or understand..... SGS Politics just dont cut it lol

Its like a Ubuntu Forum all over again lmao...
[Galaxy S I9000 Android Development] DamianGto:
I think its funny this bug surfaced when someone start to promoted voodoo.;-)

People then started to get corrupted system when they did try different things to check it.

I think this bug has been handle so bad. It also funny that someone claims that only k9 and voodoo 5 is safe. Even stock kernels is unsafe.

Smells bad advertising.

Don't get me wrong. It good that bugs will surface, but it could been handle different and many people have been suffering with crashes unnecessary.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
[Galaxy S I9000 Android Development] pele78:
You hit the Nail on the HEAD TOTALLY !!!!!!

Im a grown man with a wife who is my world and rock, have 3 wonderful kids who are the pillars....

I dont buy into **** LOL...

Its like all of a sudden people start waling on water wtf LOL
[Galaxy S I9000 Android Development] hardcore:
This fix is for people who are using ULK and want to migrate to stock kernel, Voodoo, SpeedMod K9, or any other kernel that doesn't corrupt /system. SpeedMod K9 is a ULK kernel that fixes this problem - it's just a bug in the older version of ULK. I've put out the initramfs from K9 out (the initramfs is basically the ULF part) so that other ULK kernel builders can implement it for a quick fix (or fix it themselves).

In other words, it is advisable to apply this fix and move to a kernel that mounts /system correctly. But the fix is not guaranteed to work, depending on how badly the rfs /system has been corrupted.

OR... a better way is to just reflash the ROM with a kernel that mounts /system correctly.
[Galaxy S I9000 Android Development] supercurio:
Hi,

This is a reference post, to inform and help people.

Trolls or flamewars don't have their place here, thank you.
[Galaxy S I9000 Android Development] pele78:
well then care to explain properly so that users do not have to end up posting and posting and posting and posting and posting ?

And when i mean explain explain in detail - who, what, where how and why ?

It does not hurt to explain and people Hundreds of users minds at ease before things get out of control.

Thank you very much.
[Galaxy S I9000 Android Development] pele78:
oh and when i mean explain, i dont wanna see loads of linux type jargon that you expect even the novice of users to undertand.

I want to see clear detailed information in a user friendly manner.

Thank you.
[Galaxy S I9000 Android Development] kalpik:
Read the first post!!!!

http://xdaforums.com/showthread.php?t=848471
[Galaxy S I9000 Android Development] kalpik:
Why said stock kernel is unsafe? The problem is *only* with kernels based on ULK.. Like I said before, please READ the first post!
[Galaxy S I9000 Android Development] DamianGto:
Hardcore: i know you do anything to fix the issues. I don't blame you at all. I just don't like the statement that all other kernels that's not k9 or voodoo is bad.

Even stock kernel has been flagged bad. That will meen that all sgs that is using stock kernel is corrupted. I don't buy that.

This information has done more harm than good.

I don't think its nice to scare people that they start to test things and breaks the phone so they have to flash it with a fresh firmware and loose all the data.

Like i did say its good bugs will surface and been fixed. But not this way this bug has been handle.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
[Galaxy S I9000 Android Development] benoitb85:
The situation is clear enough now. hardcore did a very good recap on this page.
[Galaxy S I9000 Android Development] kalpik:
WHO SAID STOCK KERNEL IS BAD? Please STOP spreading misinformation!
[Galaxy S I9000 Android Development] Driekes:
I know I have only been here a couple of days doing a massive amount of reading into the subject. This is work done by people, people make mistakes and sometimes a bug pops up. In this case it can *possibly* corrupt the /system because of they way ULK kernels use it. There is no (proper) error check as far as I can tell.

So it does not necessarily happen to everyone, but on the long term it does. There is a fix and because it is not always possible to see the implications directly it could happen that there is more fuzz than needs to be.

I might be out of place here, because I am only a few posts here, but I think the devs would appreciate asking, instead of requesting like you do.. It makes it not very appreciated, the hard work they try each day.

I still have a question which I would like to repeat? Anyone knows?
[Galaxy S I9000 Android Development] HazzBazz:
Hrrrrmmmmm I honestly don't think Supercurio has any interest of his own in this...he hosts an add free, open source project and contributes to that, if you're gonna flame him for pointing out (and fixing - for free - in his own time) then xda is not the place for you.

Supercurio is wise not to rise to the bait but I sure as hell can (as a troll myself). You're right, this currently relies on some understanding of the internal workings of the computers we call phones, if you don't have that knowledge (I only have very limited knowledge, nothing like supercurio, but it makes sense to me even if I haven't looked at it in full)...wait for the confirmation by the kernel writers if you're a sceptic, don't expect to be spoonfed technical hackery ! I don't. Xda doesn't. Let's chill.
[Galaxy S I9000 Android Development] pele78:
Kalpik mate you fully well know me back at yours and Docs thread.

What i am stating is for more clearer details, or basically when someone back at that thread wants answers im just gonna say :

See Curio. The End.

Nothing is properly clear, and its gonna get a whole lot worse as users start to log in demanding answers as to whats going on especially those who have no clue about ODIN !!! its bad enough most dont know how to clear simple market data etc to fix market again as an option...
[Galaxy S I9000 Android Development] kalpik:
What is it that's not clear? Ask, and I can try to explain :)
[Galaxy S I9000 Android Development] pele78:
before you go flapping your gums mate, im speaking as to get an understanding as to whats going on..

its funny that when someone asks a simple question, others tend to read between the lines and draw a line based on hostility.

well lets just get one thing straight i am one individual amongst hundreds. im just trying to find answers to help those who dont have a slightest clue.

So hard...
[Galaxy S I9000 Android Development] DamianGto:
Supercurio: lets make this clear once for all.

What kernel is unsafe and what kernel i safe?

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
[Galaxy S I9000 Android Development] ussittette:
Hello,

I flashed 2nd rfs fixer about one hour ago with odin as PDA without re-partition and let it reboot.

I had removed any lagfix and startup tweaks before and was on doc's rom 8 (JP5).

Problem is, it never rebooted correctly (i pulled the battery after 30 min).

Now, I can't access to recovery or download mode anymore and the phone is stuck at the "Galaxy S" screen.

And when i plug the usb port, the loading screen doesn't load correctly (ironic, isn't it ?), there's just an empty battery with the circle showing up.

Is there a way to fix this ? How about the homemade usb connector ?
[Galaxy S I9000 Android Development] kalpik:
Ill say this once more.. *Only* kernels based on sztupy's ULK are unsafe (except K9).
[Galaxy S I9000 Android Development] hardcore:
Chill out guys. Let me try to simply the situation:

1. Supercurio found a bug with ULFK 0.3. It was probably a typo or oversight, but it results in /system not getting mounted correctly, which corrupts /system in some slow way.

2. The corruption is there, but also not that bad because it will work fine for most people. The chance of it crashing or causing immediate harm is slim. And its fixable by a new firmware flash.

3. But nevertheless, its still a bug. And its fixable, and has been fixed in ULFK scripts. I have posted the fixed ULFK scripts already, so all the ULFK kernel makers can update it.

4. Since it is a ULFK bug, it is likely that all the active ULFK kernels devs will update their kernels to fix it.

5. When that happens, users of the older ULFK kernels will run into the same problem (unable to boot) that they run into when flashing back to stock/Voodoo/other fixed kernels. They will have to either (i) use this tool or other methods to fix it, or (ii) reflash their firmware.

The point is: It's a real problem with ULFK 0.3. But it won't cause much *immediate* harm. But its been fixed anyway in newer ULFK. And eventually all ULFK users will have to update and go through the 'conversion' hassle.

----------

Now for something non-technical. I really want to thank Supercurio for finding and sharing this problem. He didn't have to and we could just have continued to be un-informed. But he did, and even tries to make an 'easy' fix (which may not even be possible!).

I can't say the same for everyone, but if I know that there is a bug with the software, and there *is* a fix, then I'd rather implement the fix. Even though not doing so may not cause me any immediate damage. But it's really the individual person's choice.
[Galaxy S I9000 Android Development] pele78:
OK ill rack a few up what other users would ask (mainly novice users) :

How do i know if this affects me ?

Do i have this Bug ?

How do i check ?

What Roms does this affect ?

What do i need to do in Odin, i have never used it before ?

Does this only affect user going from k8 to k9 ?

What if i didnt use a lagfix ?

Who else is affected by this ?

If im on XXXXXXX Rom do i need to apply this fix regardless even if i have not used a K* Kernal ?

Does this affect all kernals ?

Which kernel ?

Kalpik, its question like these that will come flooding in there masses, it may not come now but they sure will soon.
[Galaxy S I9000 Android Development] pele78:
You see this was not hard to post, simple stuff like this should be put in the first post - like a simple but updating FAQ etc.

Then we can reduce the amount of posts and question being asked, would save alot of hassle.

Thank you

P.S. dont let this post get lost in this thread...
[Galaxy S I9000 Android Development] gtg465x:
ALL of these questions have been answered in this thread and most of them are answered in the first couple posts.
[Galaxy S I9000 Android Development] kalpik:
If you're running any kernel based on ULK (except K9, for now), you are affected.

See above.

Open terminal, type "mount" and look for the line containing /system. If it does not have "check=no", you are affected (you can potentially have a corrupt /system)

See 1st answer.

No, you don't (ill post a solution tomorrow)

It can potentially corrupt your /system even if you're on k8.

You are still affected.

See 1st answer.

See 1st answer.

See 1st answer.
[Galaxy S I9000 Android Development] kalpik:
You have to understand that english is not supercurio's native language.. So sometimes its hard for him to explain everything :)
[Galaxy S I9000 Android Development] HazzBazz:
No no, you're flaming and trolling. User guides will come if theyre needed, but to say something's for someone's self interest because you dont understand is wrong. End. Not saying that was your intention...but it came across as rude. Perhaps I came across as rude in my response, if so I apologise. Let's focus on making our phones good and not ridicule the informed.
[Galaxy S I9000 Android Development] bigriot:
English is not my first language but I understood just fine what Supercurio was saying. Like so many people point out in the DOC Rom thread the answers are in the thread. This thread only has about 14 pages ATM so going through all the posts shouldn't be too hard. How about asking nicely instead of calling outright people's hard work B.S?
[Galaxy S I9000 Android Development] DamianGto:
Thanks hardcore to make this clear for all. I hope this information gets into the first post.

I still think this should have been done of Supercurio.

Im gratefully he did find this bug so people can fix it before its to late, but i don't like how it has been handle. I have been asked alot of this and I've seen alot of broken phones just because of this. Have this issue been handle in a better way this phones has still working( they do work after a flash, but it has taking time for me. That's why Im not happy with this).

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
[Galaxy S I9000 Android Development] supercurio:
Yes, this kernel is only a fix. It will re-convert /system at each boot.

It's really not designed to be used for anything else than fixing a problem :)
[Galaxy S I9000 Android Development] zenkinz:
uploading YA-OK kernel v1.31 as we speak now :D
[Galaxy S I9000 Android Development] pele78:
no need apologies mate, its just a bit frustrating thats all, and even more frustrating trying to help others who have no clear clue, an i for one dont wanna try play a guessing game to cure someones fear.

no hard feelings.
[Galaxy S I9000 Android Development] pele78:
I know that and fully appreciate it, but without any digs, if he explained about the very technicality of the issue then surely he could put alot and i mean alot of users minds at rest by stating those little things, like for example those random questions i gave you that could come from hundreds of users which would cut down alot of unneeded confusion and posts and spam, and even the so called frustrated so-called hostile post here and there, or even some users having to go off and create a fresh thread to be heard in amongst this mess.
[Galaxy S I9000 Android Development] zurchpet:
I just want to report my experiences with this problem.

I was in K8-256HZ. I tryed to install K9. No Boot. Despite having completely fresh flashed last friday. Seems the corruption is bad. So I tried your fix kernel. And Same as others I never reached "Step 2". So it must already be corrupted badly. After only 5 days! I could enter recovery and reapplied Docs V8.0.1 and without rebooting K9-256HZ. Now it rebooted and is removing the "Vodoo-Like" (/data on ext4 only) lagfix. restorong dbdata now. Wish me luck. Don't want to reflash the whole thing. Luckily I have nandroid and Titanium backups to save me some time if I have to walk this path.

@Supercurio: Thank you for pointing this bug out and trying to build a fix for us. Many thanks. Even if it actually didn't work for me.

@hardcore: Thank you for fixing the bug in K9. Now I can sleep well again :-)

PS: It is asking me for my PIN. No FCs or anything suspicious. Thank you all.
[Galaxy S I9000 Android Development] karl999999:
try this?

http://xdaforums.com/showpost.php?p=9380727&postcount=2846
[Galaxy S I9000 Android Development] specialex:
can i use voodoo 5 pre6 with DXJPA?
[Galaxy S I9000 Android Development] kraksen:
Hello m8s,

Skimmed through all the pages, but couldn't find an answer to my question:

I am running 2.2 JPA with vodoo.snapshot (before that, i was runnning 2.2 JPA with vodoo.pre6).

Do i need to apply the fix by supercurio ? And if so, should i then re-apply vodoo.snapshot once again?

Or is everything just fine, and i don't need to do anything, since i have only been using the Vodoo lagfixes ?

Thanks :)
[Galaxy S I9000 Android Development] sharky34:
Kraksen, You don't have to use then rfs fix.
[Galaxy S I9000 Android Development] AlexandreT:
How long is this fix supposed to take to complete? Mine has been here for the past 5 mins after saying step one. When should I just quit and end up reflashing everything?

Thanks.
[Galaxy S I9000 Android Development] kraksen:
@sharky34: Thanks for the quick reply m8 ;)

@AlexandreT: I would advice you to be patient m8. Depending on whats on your phone, the flashing/conversion times appearently vary.
[Galaxy S I9000 Android Development] dckiwi:
I think 90% of flashers get it already. I haven't seen too many questions - it's all very straight forward.

Here's a piece of advise. If you can't understand the explanations to date, or the explanation in post one you should NOT BE flashing roms, kernels, etc.

Do us all a favor and stick to Kies. Curio/Kaplik/Hardcore are doing an awesome job - let's let them focus on it.
[Galaxy S I9000 Android Development] tanoxxx:
Hi, sorry but english for me sometimes is a big problem..

I have only one question:

If i make this fix after can i use every kernel i want (I would like to continue using the raspdeep kernel) and the problem is resolved and not reappears.. or this problem back again when i flash the raspdeep kernel...?

Thanks

Ps. Sorry for the question but I'd like to understand this thing..

Thanks.
[Galaxy S I9000 Android Development] tarzanug:
Is it possible to flash this fix through cwm... Update.zip?
[Galaxy S I9000 Android Development] dckiwi:
The curio fix? that's a tar, needs odin.
[Galaxy S I9000 Android Development] dckiwi:
It will only come back if you flash an old ULF kernel, or flashing a kernel where the author was using the same condition to create the corrupt /system (Mounting any RFS filesystem without check=no).

I would check now before flashing any new kernels that they consider this.
[Galaxy S I9000 Android Development] tanoxxx:
Really really thanks for answer me..

So if I understand it .. even if I do the supercurio fix my galaxy can get another time the problem if i flash the the raspdeep kernel..

Its correct?

Sorry if im hard to understand but english is not my best language but i try to do my best...

Really thanks.
[Galaxy S I9000 Android Development] avss:
Yes...if the raspdeep-kernel dev doesnt implement the correct fix you will be in the same position you are now when flashing that kernel back.
[Galaxy S I9000 Android Development] tanoxxx:
Really really thanks for all answer..

hardcore say in one post:

I have posted the fixed ULFK scripts already, so all the ULFK kernel makers can update it.

This script is only for the Developers?

I must wait for example raspdeep integrating this script in yours kernel or i can run in some way buy me this script to fix the problem?

Sorry for this other question.

Thanks thanks again.
[Galaxy S I9000 Android Development] supercurio:
If it still does nothing after 5min, it means it fails.
[Galaxy S I9000 Android Development] dckiwi:
Wait for the all clear from the original rom/kernel author. (Wait for them to fix it, that is if it needs fixing of course)
[Galaxy S I9000 Android Development] spline1:
Fix dosn't work on 2 SGS with K8 Kernel.

No Boot any more
[Galaxy S I9000 Android Development] BronzedDroid:
If I flash a clean new official ROM like JPA or newer, with repartition ticked, will this fix the corruption errors? My guess would be yes, but my guess is that you know better. Atleast that's what I'm guessing.
[Galaxy S I9000 Android Development] omnicronx:
They are doing a great job, but I feel you are being foolish here..

Just because users will blindly flash these fixes on their phones, does not mean they understand the work behind them..

I think you are kidding yourself if you think 90% of the flashers understand whats happening here. (heck I'd be surprised if that many even knew what RFS is..)

I'm a developer and new to the platform, and personally I feel the entire i9000 forum is all over the place. Sure after a day or two I was able to wrap my head around most of it, but if I knew where to start it would have made things a lot easier. Its hard for a community like this to grow if you expect everyone to be a 'hardcore power user'..

A little documentation never hurt anyone. Not saying it should be the responsibility of the dev's either, as this is a community :)

edit: that being said, this thread in particular is very well explained by the dev if you understand terminology.
[Galaxy S I9000 Android Development] coldhandz:
Hi Supercurio. I have a question, I managed to flash your fix kernel but I am now having trouble getting back into download mode in order to flash the snapshot:confused:

Is this a known problem?

Thanks

Edit: got it:)
[Galaxy S I9000 Android Development] nobloat:
I've flashed the fixer kerner, and booted it. It said 'step 1', 'step 2', rebooted, all ok. Then flashed zenkinz31 kernel.

It booted perfectly, but I still have capital /BIN and /ETC, and user.log is created again even if I delete it.

Means the fix didn't work?
[Galaxy S I9000 Android Development] dckiwi:
Fair call, maybe my words were poorly chosen. I do stand by the general premise though - we should not blindly flash stuff unless we have a basic knowledge of what's going on and how to fix our screw-ups....
[Galaxy S I9000 Android Development] dckiwi:
Yes, that will flash the kernel thus reversing the bug (as long as it's official, not modified).
[Galaxy S I9000 Android Development] extralife:
$ export PATH=/data/local/bin:$PATH

$su

# mount

rootfs / rootfs rw,relatime 0 0

proc /proc proc rw,noatime 0 0

sys /sys sysfs rw,noatime 0 0

tmpfs /tmp tmpfs rw,noatime 0 0

/dev/block/stl9 /system rfs rw,noatime,vfat,llw,gid/uid/rwx,iocharset=utf8 0 0

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

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

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

tmpfs /dev tmpfs rw,noatime,mode=755 0 0

devpts /dev/pts devpts rw,noatime,mode=600 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw,noatime 0 0

tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

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

/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

#

-------

so in this case i`m affected :-\

-------

on doc 8.0.1 - k8 & hoping for a save solution