Be careful :changes like lagfix...

---

Well I am happy for the work That is being done by the XDA 15800 forum members esp rex,sahil,sazby,gsm101 , brave buddy , addicted and others...

However I just wish to draw people's attention to actually understanding how things like lagfix works so that they dont face the problems that I faced...

http://forum.xda-developers.com/show...5&postcount=40

Just chck out the final piece of code of UN-lagfix that u run to undo i5800 lagfix:

echo "Cleaning /data"
cd /data
busybox rm -r *
echo "Removing auto boot support"
busybox mv /system/bin/playlogosnow /system/bin/playlogos

echo "All done! Rebooting device so that the EXT2 Loopback device is freed."
reboot


chck out the bold part. so what the lagfix does is create a ext2 partion in your internal memory, and whenever your device boots , it is automatically directed to that ext2 chunk.
Now if your phone is working correctly, then no problem.
However IF your phone crashes while u still have lagfix enabled... well I guess after that people will be stuck onto their boot screen staring at i5800 logo for days to come....

morever whatever firmware u flash, since the command makes changes in the mbr, it cant be resolved by usual flashing via odin.
You actually need to restore the proper boot partition which can be done via adb . But then ADB can be used only when the phone is on and in debugging mode..

more reasons why you should be careful with these fixes is

1) i5800 is a relatively new phone. We still don't have the stock kernel, stock recovery with us. For other phones like galaxy s that is available for download.

2) The odin for i5800 is meant mainly for flashing(its not yet advanced). However it lacks the repartition option that is present in galaxy s odin.

3)No clockwork mod recovery for i5800 . Nandroid backup not there.


This post is not meant to be disrespectful to others. I have immense respect for people who work hard and take risks to bring new features to our phones But still it is better to understand something before we do it.. I have learned it the hard way.

anyway for those who have an indian i5801, might want to know that only 2 firmwares out there to solve the issues. so any issues you face do keep a copy of both in your pc, esp datafs and zimage..

ddj5/ddj6

first you flash only the boot kernel, ie zimage, and then again u flash ddj6 . If you are lucky it will boot correctly.

you can backup like this
http://forum.xda-developers.com/show...92&postcount=8
what is indian i5801 stock firmware ?
be the way if you flash or stay in the boot screen
is the MULTI CSC fimrware make this bug
efs is not flash by odin,and the product code and imei is in nv_data.bin
if the stock efs only have one csc ,flash to MULTI CSC firmware
like I5801DKATGY(HONGKONG),only have one csc
flash I5800XWJH2 is ok,if flash XXJP8 JP9 JPA MULTI CSC firmware
that stay in the boot screen
==========================================
Previously Samsung used code *#272*HHMM# (HH being hour and MM minute, = current time) to access the Preconfiguration menu.

Originally Posted by Saka911

Well I am happy for the work That is being done by the XDA 15800 forum members esp rex,sahil,sazby,gsm101 , brave buddy , addicted and others...

However I just wish to draw people's attention to actually understanding how things like lagfix works so that they dont face the problems that I faced...

http://forum.xda-developers.com/show...5&postcount=40

Just chck out the final piece of code of UN-lagfix that u run to undo i5800 lagfix:

echo "Cleaning /data"
cd /data
busybox rm -r *
echo "Removing auto boot support"
busybox mv /system/bin/playlogosnow /system/bin/playlogos

echo "All done! Rebooting device so that the EXT2 Loopback device is freed."
reboot


chck out the bold part. so what the lagfix does is create a ext2 partion in your internal memory, and whenever your device boots , it is automatically directed to that ext2 chunk.
Now if your phone is working correctly, then no problem.
However IF your phone crashes while u still have lagfix enabled... well I guess after that people will be stuck onto their boot screen staring at i5800 logo for days to come....

morever whatever firmware u flash, since the command makes changes in the mbr, it cant be resolved by usual flashing via odin.
You actually need to restore the proper boot partition which can be done via adb . But then ADB can be used only when the phone is on and in debugging mode..

more reasons why you should be careful with these fixes is

1) i5800 is a relatively new phone. We still don't have the stock kernel, stock recovery with us. For other phones like galaxy s that is available for download.

2) The odin for i5800 is meant mainly for flashing(its not yet advanced). However it lacks the repartition option that is present in galaxy s odin.

3)No clockwork mod recovery for i5800 . Nandroid backup not there.


This post is not meant to be disrespectful to others. I have immense respect for people who work hard and take risks to bring new features to our phones But still it is better to understand something before we do it.. I have learned it the hard way.

anyway for those who have an indian i5801, might want to know that only 2 firmwares out there to solve the issues. so any issues you face do keep a copy of both in your pc, esp datafs and zimage..

ddj5/ddj6

first you flash only the boot kernel, ie zimage, and then again u flash ddj6 . If you are lucky it will boot correctly.

Quite an interesting post these things are surely of importance and we people will have to start from scratch and either make other work tweaked for our purpose or have to build new one.
I will be looking into the details and first thing of importance is to have a backup plan when things go wrong because ppl who buy this phone buy it mostly because they cant afford more expansive ones or 2 phone so safety should be the first and foremost concern here.....

Happy coding...

Originally Posted by god_md5

you can backup like this
http://forum.xda-developers.com/show...92&postcount=8
what is indian i5801 stock firmware ?
be the way if you flash or stay in the boot screen
is the MULTI CSC fimrware make this bug
efs is not flash by odin,and the product code and imei is in nv_data.bin
if the stock efs only have one csc ,flash to MULTI CSC firmware
like I5801DKATGY(HONGKONG),only have one csc
flash I5800XWJH2 is ok,if flash XXJP8 JP9 JPA MULTI CSC firmware
that stay in the boot screen
==========================================
Previously Samsung used code *#272*HHMM# (HH being hour and MM minute, = current time) to access the Preconfiguration menu.

well the default firmware for Indian i5801 is

july ddj5
august ddj6

and yeah it is a multi-csc firmware( csc corresponds to area and apns)

but the problem is that the version of ddj5 and ddj6 hosted on sam firmware are leaked builds...

the original build should be ddj2/3 (4 is unlucky in korean)

p.s. If any indianforum member who is reading this has an untouched(never rooted,never flashed) new i5801, then we can try and extract stock kernel , bootloader , ziimage and boot.bin from there so that we have a safety net in future.
regards,
aka.

addicted2088 here.. The two threads that I've started don't mess with the system files at all. Nothing can go wrong because of them..

Just letting people know that any bricked phones are not because of my instructions, but can be because of the work done by the other members named above. But since the work they're doing is good, we all gotta take some risks. I know I do..

No disrespect to those whose names have been mentioned in this thread. Appreciate the great work that you guys are doing..

I have the indian ddjg6 version of galaxy 3...but i rooted the device by z4root but nothing else is done like flashing...and all...
-Devilgod (United Devils)

Hello ..

So, in theory, the lagfix i had ported doesn't change at all the partition scheme of the i5800, since it's a LOOPBACK device in the /data partition: If you prefer, a partition in the partition. So, it can't, at all, brick your phone, since you ALWAYS can flash again with Odin (As i said before, you should remove the battery while not in USB/AC).


And you HAVE TO flash a datafs.rfs if something went wrong. I say it again.

Originally Posted by Gsam101

Hello ..

So, in theory, the lagfix i had ported doesn't change at all the partition scheme of the i5800, since it's a LOOPBACK device in the /data partition: If you prefer, a partition in the partition. So, it can't, at all, brick your phone, since you ALWAYS can flash again with Odin (As i said before, you should remove the battery while not in USB/AC).


And you HAVE TO flash a datafs.rfs if something went wrong. I say it again.

hello, Thanks for the feedback...
I just created the thread so that we can make a repository of the stock kernel, boot etc. so that in future it will be useful when we go for nandroid backup or kies update

so does this lagfix work??? after all????
or not?
i have seen someone brick his phone....

Originally Posted by Saka911

hello, Thanks for the feedback...
I just created the thread so that we can make a repository of the stock kernel, boot etc. so that in future it will be useful when we go for nandroid backup or kies update

this makes absolutely no sense to me... in that case you´d need to change the thread title and also content of first post, which makes all other posts obsolete what again makes the whole thread obsolete.

however, this lagfix is confirmed working multiple times but it surely needs some work to be done, and in my opinion is not really needed. my girlfriends G3 opens contacts even faster than my SGS (this however could have to do with her having 120 contacts versus me having 800+) despite my SGS runs on custom kernel with ext4 for data partition. Also Lagfixes though a loop device are always a little risky to loose data when doing an unpropper shutdown.
But what the op stated is just untrue, the lagfix does not resist a firmware flash if that firmware contains a datafs.rfs file.