[APP][ABANDONED] z4mod

Search This thread
By:
Advanced…
DamianGto

DamianGto

Senior Member
Sep 17, 2010
2,022
420
androidfreak2010 said:
Is this faster than the ULF-based kernel lagfixes?
Click to expand...
Click to collapse

Hard to tell. Many say its same, some say its smoother.
Its hard to measure for there is not any benchmarks program to show this. Quadrant is just a score and have little to do with how the phone feels.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
 
Peacemanibk

Peacemanibk

Senior Member
Oct 18, 2010
124
7
What about writing an own benchmark app? Just startet a thread about this in the app section. I agree quadrant gives you just a number, but with a refined benchmark (testing different read-write situations on different partitions) one maybe see clearer differences between the different lagfixes...

Sent from my GT-I9000 using XDA App
 
DamianGto

DamianGto

Senior Member
Sep 17, 2010
2,022
420
Peacemanibk said:
What about writing an own benchmark app? Just startet a thread about this in the app section. I agree quadrant gives you just a number, but with a refined benchmark (testing different read-write situations on different partitions) one maybe see clearer differences between the different lagfixes...

Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse

Yes we need a benchmarks program that's made for sgs.
That would show more true numbers.
But its only numbers and can't show how the phone feels to work with. But it will give you a hint.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
 
I

iqbalbaskara

Senior Member
Aug 10, 2010
120
4
Bandung
REPORTING! :)
Phone: international (SEA) GT I9000
About 3 days ago I updated to froyo, restored the apps from eclair using titanium backup. Installed Z4root and Z4mod, converting to EXT2 filesystem. no problem, the installation went painlessly.

Yesterday i did a factory reset since the phone was having some problems which i suspect came from the restored apps. I did the factory reset without reverting back to RFS.

Today I reinstalled the Z4root and Z4mod apps. no problem with Z4root, it detects that my phone is rooted just fine.

The problem lies with Z4mod, it detects that my phone's kernel has been patched, and the filesystem conversion button is available on the screen (but not unpatch kernel button). I selected ext2, tapped convert filesystem, the phone processed it, reset itself, the blue Z4 screen which says i should not turn of the phone showed up for about half a second, and the phone rebooted. It went on with no problem, but when i opened up Z4mod again, it still says the filesystem is still RFS, Q benchmark hovers around the 950s. Tried the convert filesystem button again with same result.

any way i can acquire ext2 filesystem back? Thanks!

here's the z4mod log:
Code: 
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Mon Nov 22 12:59:32 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
grep: /etc/fstab: No such file or directory
+ currentfs=
+ [  == ext2 ]
+ [  ==  ]
+ currentfs=rfs
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [ rfs == rfs ]
+ busybox mount -t rfs /dev/block/mmcblk0p2 /data -o nosuid,nodev,check=no
+ busybox rm -f /sdcard/data.z4mod.tar
+ busybox awk {print $3}
+ busybox sed s|/[^ ]*||g
+ busybox tail -n1
+ busybox df /dev/block/mmcblk0p1
+ free_space=6982816
+ busybox awk {print $2}
+ busybox sed s|/[^ ]*||g
+ busybox tail -n1
+ busybox df /dev/block/mmcblk0p2
+ backup_size=586704
+ [ 586704 -ge 6982816 ]
+ busybox rm /sdcard/data.z4mod.tar
rm: can't remove '/sdcard/data.z4mod.tar': No such file or directory
+ busybox rm /data/rfs.log
rm: can't remove '/data/rfs.log': No such file or directory
+ busybox tar cf /sdcard/data.z4mod.tar /data
tar: removing leading '/' from member names
tar: /data/gps/lcs.socket: socket ignored
tar: /data/misc/wifi/sockets/wpa_ctrl_3095-2: socket ignored
tar: /data/misc/wifi/sockets/wpa_ctrl_3095-3: socket ignored
tar: /data/misc/wifi/eth0: socket ignored
tar: /data/.pcsync_stream: socket ignored
tar: /data/.usb_stream: socket ignored
+ busybox echo 0
0
+ busybox umount /data
+ [ data == data ]
+ [ ext2 == rfs ]
+ echo -en \x83
+ busybox dd of=/dev/block/mmcblk0 seek=466
0+1 records in
0+1 records out
1 bytes (1B) copied, 0.001653 seconds, 604B/s
+ [ ext2 == rfs ]
+ [ ext2 == jfs ]
+ [ ext2 == ext2 ]
+ mountopt=nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ mkfs.ext2 -q -L data -b 4096 -m 0 -F /dev/block/mmcblk0p2
+ tune2fs -c 100 -i 30d -m 0 /dev/block/mmcblk0p2
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to 100
Setting interval between checks to 2592000 seconds
Setting reserved blocks percentage to 0% (0 blocks)
+ busybox mount -t ext2 /dev/block/mmcblk0p2 /data -o nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ busybox mount
+ busybox grep /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 on /data type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,nobh)
+ busybox tar xf /sdcard/data.z4mod.tar -C /
+ ret=0
+ [ 0 == 0 ]
+ busybox rm /sdcard/data.z4mod.tar
+ busybox touch /system/etc/fstab
+ busybox sed -i \,/dev/block/mmcblk0p2,d /system/etc/fstab
+ echo /dev/block/mmcblk0p2 /data ext2 nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ busybox mount -o remount,ro /system
+ busybox umount /dev/block/mmcblk0p2
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 0
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Mon Nov 22 13:22:50 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Thu Nov 25 00:44:12 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Thu Nov 25 00:49:51 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
 
Last edited:
M

mew1838

Member
Nov 25, 2010
27
1
Hello all,

This is my first post here so take it easy on me. Thank you RyanZa for the work you have put into these apps and others who have contributed as well. I was running the JPA official FroYo build and I ran Z4Root + Z4Mod to convert to EXT2 file system. I will test out how it goes. My question is:

1) to revert to stock, I see a restore kernel option in Z4Mod. Do I just hit that and I will get back to completely stock?
 
Last edited:
L

lenrek

Senior Member
Jun 29, 2010
394
32
iqbalbaskara said:
REPORTING! :)
Phone: international (SEA) GT I9000
About 3 days ago I updated to froyo, restored the apps from eclair using titanium backup. Installed Z4root and Z4mod, converting to EXT2 filesystem. no problem, the installation went painlessly.

Yesterday i did a factory reset since the phone was having some problems which i suspect came from the restored apps. I did the factory reset without reverting back to RFS.

Today I reinstalled the Z4root and Z4mod apps. no problem with Z4root, it detects that my phone is rooted just fine.

The problem lies with Z4mod, it detects that my phone's kernel has been patched, and the filesystem conversion button is available on the screen (but not unpatch kernel button). I selected ext2, tapped convert filesystem, the phone processed it, reset itself, the blue Z4 screen which says i should not turn of the phone showed up for about half a second, and the phone rebooted. It went on with no problem, but when i opened up Z4mod again, it still says the filesystem is still RFS, Q benchmark hovers around the 950s. Tried the convert filesystem button again with same result.

any way i can acquire ext2 filesystem back? Thanks!

here's the z4mod log:
Code: 
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Mon Nov 22 12:59:32 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
grep: /etc/fstab: No such file or directory
+ currentfs=
+ [  == ext2 ]
+ [  ==  ]
+ currentfs=rfs
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [ rfs == rfs ]
+ busybox mount -t rfs /dev/block/mmcblk0p2 /data -o nosuid,nodev,check=no
+ busybox rm -f /sdcard/data.z4mod.tar
+ busybox awk {print $3}
+ busybox sed s|/[^ ]*||g
+ busybox tail -n1
+ busybox df /dev/block/mmcblk0p1
+ free_space=6982816
+ busybox awk {print $2}
+ busybox sed s|/[^ ]*||g
+ busybox tail -n1
+ busybox df /dev/block/mmcblk0p2
+ backup_size=586704
+ [ 586704 -ge 6982816 ]
+ busybox rm /sdcard/data.z4mod.tar
rm: can't remove '/sdcard/data.z4mod.tar': No such file or directory
+ busybox rm /data/rfs.log
rm: can't remove '/data/rfs.log': No such file or directory
+ busybox tar cf /sdcard/data.z4mod.tar /data
tar: removing leading '/' from member names
tar: /data/gps/lcs.socket: socket ignored
tar: /data/misc/wifi/sockets/wpa_ctrl_3095-2: socket ignored
tar: /data/misc/wifi/sockets/wpa_ctrl_3095-3: socket ignored
tar: /data/misc/wifi/eth0: socket ignored
tar: /data/.pcsync_stream: socket ignored
tar: /data/.usb_stream: socket ignored
+ busybox echo 0
0
+ busybox umount /data
+ [ data == data ]
+ [ ext2 == rfs ]
+ echo -en \x83
+ busybox dd of=/dev/block/mmcblk0 seek=466
0+1 records in
0+1 records out
1 bytes (1B) copied, 0.001653 seconds, 604B/s
+ [ ext2 == rfs ]
+ [ ext2 == jfs ]
+ [ ext2 == ext2 ]
+ mountopt=nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ mkfs.ext2 -q -L data -b 4096 -m 0 -F /dev/block/mmcblk0p2
+ tune2fs -c 100 -i 30d -m 0 /dev/block/mmcblk0p2
tune2fs 1.41.12 (17-May-2010)
Setting maximal mount count to 100
Setting interval between checks to 2592000 seconds
Setting reserved blocks percentage to 0% (0 blocks)
+ busybox mount -t ext2 /dev/block/mmcblk0p2 /data -o nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ busybox mount
+ busybox grep /dev/block/mmcblk0p2
/dev/block/mmcblk0p2 on /data type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,nobh)
+ busybox tar xf /sdcard/data.z4mod.tar -C /
+ ret=0
+ [ 0 == 0 ]
+ busybox rm /sdcard/data.z4mod.tar
+ busybox touch /system/etc/fstab
+ busybox sed -i \,/dev/block/mmcblk0p2,d /system/etc/fstab
+ echo /dev/block/mmcblk0p2 /data ext2 nosuid,nodev,noatime,nodiratime,errors=continue,nobh
+ busybox mount -o remount,ro /system
+ busybox umount /dev/block/mmcblk0p2
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 0
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Mon Nov 22 13:22:50 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Thu Nov 25 00:44:12 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Thu Nov 25 00:49:51 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
Click to expand...
Click to collapse

You have the same problem as me. I fix the problem by manually download the original kernel and restore it using Odin. After that, I rerun z4mod until it works.
 
J

jacklmx

New member
Nov 22, 2010
1
0
Phone got wiped..or i believe so.

My galaxy S I9000 got wiped i think, after i convert ext2 file system to RFS, then restored my previous kernel, all done through z4mod. after the reboot all my apps including android market are gone. all the customization i did eg. theme, wallpaper, settings are gone too, everything returned to what a phone would be like freshly out of the factory. Hope anyone can help me as i am really new to all the modding flashing etc. I followed all the steps mentioned by Ryan and in z4mod, didn't do anything else.
 
R

RyanZA

Senior Member
Jan 21, 2006
2,023
784
JHB
iqbalbaskara said:
REPORTING! :)
Phone: international (SEA) GT I9000
About 3 days ago I updated to froyo, restored the apps from eclair using titanium backup. Installed Z4root and Z4mod, converting to EXT2 filesystem. no problem, the installation went painlessly.

Yesterday i did a factory reset since the phone was having some problems which i suspect came from the restored apps. I did the factory reset without reverting back to RFS.

Today I reinstalled the Z4root and Z4mod apps. no problem with Z4root, it detects that my phone is rooted just fine.

The problem lies with Z4mod, it detects that my phone's kernel has been patched, and the filesystem conversion button is available on the screen (but not unpatch kernel button). I selected ext2, tapped convert filesystem, the phone processed it, reset itself, the blue Z4 screen which says i should not turn of the phone showed up for about half a second, and the phone rebooted. It went on with no problem, but when i opened up Z4mod again, it still says the filesystem is still RFS, Q benchmark hovers around the 950s. Tried the convert filesystem button again with same result.

any way i can acquire ext2 filesystem back? Thanks!

here's the z4mod log:
Code: 
###############################################################################
#
# Starting z4mod-0.12 'ext2' convert on /data (/dev/block/mmcblk0p2)
# Thu Nov 25 00:49:51 UTC 2010
#
###############################################################################
+ [ ! -f /z4mod/z4version ]
+ partition=data
+ devblock=/dev/block/mmcblk0p2
+ filesystem=ext2
+ [ ext == ext ]
+ busybox grep ext2 /proc/filesystems
+ [ ext2 ]
+ format_cmd=mkfs.ext2
+ echo /z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/z4mod/bin:/:/sbin:/system/xbin:/system/bin:/sbin:/usr/sbin:/bin:/usr/bin
+ [ mkfs.ext2 ==  ]
+ busybox which mkfs.ext2
+ [ /z4mod/bin/mkfs.ext2 ]
+ busybox mount -o remount,rw /
+ busybox mount -o remount,rw /system
+ busybox ln -s /proc/mounts /etc/mtab
ln: /etc/mtab: File exists
+ [ data == system ]
+ busybox awk {print $3}
+ busybox grep /data /etc/fstab
+ currentfs=ext2
+ [ ext2 == ext2 ]
+ halt
+ busybox umount /data
umount: can't umount /data: Invalid argument
+ [  ==  ]
+ busybox umount /sdcard
umount: can't umount /sdcard: Device or resource busy
+ exit 1
Click to expand...
Click to collapse

The problem here is that the conversion script is picking up your /data partition as already being EXT2! Confusing, since you say it isn't.

I think I understand the problem though - your /etc/fstab file must still show /data as being ext2, even though it isn't.

Correct way to fix this is to actually check that the filesystem really is ext2, and not rely on /etc/fstab. Or, (better actually!) the app should check out the /etc/fstab and make sure it's all in order first. Thanks for the bug report!! :)

duongla said:
Hi RyanZA,

Pls include 2e or CWM recovery into the patched kernel.

Thanks
Click to expand...
Click to collapse

The CWM recovery in the z4mod git has a few issues still (well they might be sorted now actually). At any rate, that option will be included in the next version, or the version after that if the CWM in git still isn't working 100%.

mew1838 said:
Hello all,

This is my first post here so take it easy on me. Thank you RyanZa for the work you have put into these apps and others who have contributed as well. I was running the JPA official FroYo build and I ran Z4Root + Z4Mod to convert to EXT2 file system. I will test out how it goes. My question is:

1) to revert to stock, I see a restore kernel option in Z4Mod. Do I just hit that and I will get back to completely stock?
Click to expand...
Click to collapse

No! Make 100% sure you are back on RFS before using the restore kernel option, or your data will be lost. It won't actually cause any problems if you want to do a reset though. Next version of the app will check to make sure you are on RFS before flashing back.

jacklmx said:
My galaxy S I9000 got wiped i think, after i convert ext2 file system to RFS, then restored my previous kernel, all done through z4mod. after the reboot all my apps including android market are gone. all the customization i did eg. theme, wallpaper, settings are gone too, everything returned to what a phone would be like freshly out of the factory. Hope anyone can help me as i am really new to all the modding flashing etc. I followed all the steps mentioned by Ryan and in z4mod, didn't do anything else.
Click to expand...
Click to collapse

Sounds like the ext2->rfs conversion before your reflash did not work, or alternatively you changed back with /data being on ext2. Post logs if possible. :)
 
G

G.HendriX

Member
Feb 8, 2008
24
1
Installed z4mod without problem, kermel patched but aftet clicking on the conversion button: a quick reboot but the filesystem remains rfs.

On stock froyo JP5 ITV

Fingers crossed for the next version


Thank you!



Sent from my GT-I9000 using XDA App
 
I

iqbalbaskara

Senior Member
Aug 10, 2010
120
4
Bandung
RyanZA said:
The problem here is that the conversion script is picking up your /data partition as already being EXT2! Confusing, since you say it isn't.
I think I understand the problem though - your /etc/fstab file must still show /data as being ext2, even though it isn't.
Correct way to fix this is to actually check that the filesystem really is ext2, and not rely on /etc/fstab. Or, (better actually!) the app should check out the /etc/fstab and make sure it's all in order first. Thanks for the bug report!! :)
Click to expand...
Click to collapse

no problem, glad that helped! I finally flashed back to DXJG4, update to froyo via kies, installed z4root and z4mod, and everything goes all smooth and dandy now :D
 
G

GeoH2102

Member
Aug 8, 2010
20
0
Cheers Ryan, this lagfix is absolutely brilliant! My phone feels incredibly smooth, way smoother than with any of the other available lagfixes. Real easy install too ^_^
 
A

ahhentz

Member
Nov 21, 2010
8
0
Hi there. I'm new to this Android modding stuff, and so I would like some clarifications before I try using one of these lagfixes so I don't do anything stupid :p

I understand that z4mod uses native ext2 instead of loopback mounting. So this means that the app backs up the partition's contents, formats it and then reverts the backup, right? Also, if I understand correctly, the kernel must be patched before the actual lagfix process is done. Why does it need to be done? Is it because stock kernels don't have built in ext2 support?

In a related note: how easy/safe it is to revert the lagfixing process? My question is because of warranty. My handset is relatively new, and if I ever need to use my warranty, it would be better if I have it as close as possible to a factory configuration.

Now on an unrelated (possibly a little off-topic) question: is there a good resource for technical explanations about the update.zip file? Under the hood stuff. I searched the forums and found nothing.

Thanks in advance.

Sent from my GT-I9000B using XDA App
 
D

davidis57

Senior Member
Nov 11, 2010
106
5
albuera
Stupid me. After using Z4root and Z4mod my Galaxy S was still laggy with the official Froyo. I forgot to change the file system to Ext2 it still was set to Rfs.

Sent from my GT-I9000 using XDA App
 
A

AnnihilatorSC

Senior Member
Apr 17, 2008
126
3
Is it possible to add a (customizable?) initscript via z4mod? In order to add kernel tweak options such as ones found in the SpeedMod kernel, possibly?
I'd also like to have a RFS-free phone - including /dbdata, /cache and /system. Can those be converted as well?
 
P

PhoenixFx

Senior Member
Dec 1, 2006
659
128
When I try to patch the kernal i get "zImage test failed". I tried restarting the phone and reinstalling z4mod twice. Keep getting the same error.

unbranded/unlocked SGS running 2.2 (JPO flashed with Kies), rooted with SuperOneClick. No kernel patches or lag fixes installed.
 
D

ducutu

Member
Jul 27, 2008
46
5
Constanta
Originally Posted by jacklmx
My galaxy S I9000 got wiped i think, after i convert ext2 file system to RFS, then restored my previous kernel, all done through z4mod. after the reboot all my apps including android market are gone. all the customization i did eg. theme, wallpaper, settings are gone too, everything returned to what a phone would be like freshly out of the factory. Hope anyone can help me as i am really new to all the modding flashing etc. I followed all the steps mentioned by Ryan and in z4mod, didn't do anything else.
Click to expand...
Click to collapse

Same here, once on JPA and now on JP7 (stock both fw).
After trying z4mod - patching > EXT2 > RFS > restore kernel, my phone got wiped only after restoring kernel. It was ok after the RFS conversion.
Market is missing too.
So this hapened twice for me and for other people/phones.
This sound like a bug.


Maybe I'll try the next version ;)
 
Last edited:
DamianGto

DamianGto

Senior Member
Sep 17, 2010
2,022
420
davidis57 said:
Stupid me. After using Z4root and Z4mod my Galaxy S was still laggy with the official Froyo. I forgot to change the file system to Ext2 it still was set to Rfs.

Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse

Lol. Well glad you find that out.
Just convert to ext2 and you will be fine.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
 
You must log in or register to reply here.

Similar threads

N
[APP] BLN control - the official BLN settings app by neldar
Replies
1K
Views
848K
T
Tom Mix
R
[APP] One Click Lag Fix APK - 2.0 (UNSUPPORTED development halted)
Replies
2K
Views
830K
Yousef Algadri
Yousef Algadri
R
  • Locked
[APP][OUTDATED]One Click Lag Fix APK
Replies
1K
Views
584K
T
tubbytubby
Nodial
[WINDOWS APP] Kies 2.0 Registry Patcher 1.8.0.0, patch registry on latest Kies
Replies
629
Views
691K
moalesipufos
moalesipufos
xan
[APP][24Nov] - 4.9 - SGS1+2] Voltage Control - control OC/UV for OC kernels
Replies
694
Views
606K
M
mehdiexe

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 8
    R
    RyanZA
    Alright, here is the z4mod app at long last! This release needs a lot of testing for different devices still, so make sure you check the compatibility table below unless you know how to use Odin to flash back your original kernel. Thanks for helping to test this!

    [size=+1]This is still in beta! If you know how to flash with Odin, please help test so all bugs can be found and fixed to allow for wider release![/size]

    What is this?

    Another lagfix. This one is a bit different from existing lagfixes though:

    - Differences from OCLF: Uses native EXT/JFS instead of loopback mounts. Loopback mounts in linux can be a bit flakey at times, especially when they're on RFS. So this is generally better.

    - Differences from lagfix kernels such as voodoo or sztupy's: These types of lagfixes are kernels compiled from GPL sources for specific devices. This can cause a number of issues, such as losing out on bug fixes in later Samsung kernels released after the GPL code, or differences in devices such as the I9000B, etc. z4mod also has (imo) a nicer design, in that it uses /etc/fstab for filesystem mounting, as well as keeping the convert scripts outside the kernel. It should also work across ALL (or many?) Samsung devices without changes!


    How do I use this?

    Install the app. Click the buttons. It should all just work. Let me know of any issues or complications! This is still in testing!

    Device/firmware compatibility table

    Samsung Galaxy S Devices
    Stock Samsung
    I9000 Stock Samsung 2.2 : WORKING
    I9000 Stock Samsung 2.1 : NOT TESTED
    I9000B Stock Samsung 2.2 : NOT TESTED
    I9000B Stock Samsung 2.1 : NOT TESTED
    I9000T Stock Samsung 2.2 : NOT TESTED
    I9000T Stock Samsung 2.1 : NOT TESTED
    I9000M Stock Samsung 2.2 : NOT TESTED
    I9000M Stock Samsung 2.1 : NOT TESTED
    Captivate Stock Samsung 2.2 : NOT TESTED
    Captivate Stock Samsung 2.1 : NOT TESTED
    Vibrant Stock Samsung 2.2 : NOT TESTED
    Vibrant Stock Samsung 2.1 : NOT TESTED
    Epic Stock Samsung 2.2 : NOT TESTED
    Epic Stock Samsung 2.1 : NOT TESTED
    Fascinate Stock Samsung 2.2 : NOT TESTED
    Fascinate Stock Samsung 2.1 : NOT TESTED
    Stock Japanese Docomo Galaxy S (SC-02B) : WORKING
    Stock SHW-M110S (Korean SGS) : WORKING

    Custom Firmwares
    Any custom firmware that uses a stock kernel works as the stock kernel in the table above
    Custom kernels that make use of changed filesystems or boot up scripts are unlikely to work at this time. Emphasis is on stock kernels currently.

    Custom Kernels

    BLN (backlight notification) custom kernel for GT-I9000 works
    Voodoo kernels do not work
    Kernels with heavily modified boot procedures such as rooted Vibrant kernels do not work
    CFRoot kernel does not work.
    DamianGto's kernels work

    Other Samsung Devices
    NOT TESTED

    More info on z4mod
    http://www.sgscompilebox.dreamhosters.com/about.html

    Source Code
    http://github.com/z4/z4mod

    V0.9.2 Changelog

    Fix for EXT2->RFS Conversion. Please update to this app version before using this conversion.
    Other small bug fixes.
    Conversion page now has scrolling text informing you of progress and any errors.

    V0.9.3 Changelog

    Critical: Upload kernel now passes binary MIME type to prevent corrupt kernels
    Fixes for text in conversion screen.
    Fix for 'mmcblk0p2' always being chosen for /data, even on devices that use 'mmcblk0p1'
    Bug fixes for UI

    Donations

    Donate link is available at https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
    View
    1
    R
    RyanZA
    DAGr8 said:
    quick question I need to disable vodoo before using this right ?

    anyways im running vibrant rom ( axura ) on my rogers captivate ( i896 )

    testing now
    Click to expand...
    Click to collapse

    This probably won't work if you have a Voodoo kernel installed. The Voodoo kernel is unlikely to be patchable, since it's not native RFS, and does not use /etc/fstab.
    View
    1
    DamianGto
    DamianGto
    jerkysans said:
    Hi RyanZA and everyone. I've applied this lag fix to my device and I'm quite satisfied, but I think I somehow screwed my device and now need to factory reset. My question is, do I need to revert to rfs, restore the kernel, and unroot the device before I do the master reset under Settings > Privacy?

    Thanks.
    Click to expand...
    Click to collapse

    Yes you need to convert back or you will loose all your data.
    You dont need to do more.


    **Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
    View
    1
    DamianGto
    DamianGto
    munnergep said:
    Hi!

    I'am on 2.2.1, now.

    In 2.2, i used z4root+z4mod+ one of DamianGto's (excellent) kernel.
    I tried to use it the same way like in 2.2, but no success on 2.2.1 :(
    1. z4root does not worked
    2. with rooted kernel, z4mod said: can't patch kernel

    Is it possible to use all of these on 2.2.1 (and what order), or am i doing something wrong?

    (sorry for my very basic english)
    Click to expand...
    Click to collapse

    You need to root with oneclickroot.
    Z4root don't work with this new firmware.
    Then you install busybox from market. You may need to remove some ringtunes to make some room on the system.
    Then you can use one of my kernel and use z4mod to convert to ext2.
    Then you get a fast system again:)


    **Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
    View
    1
    DamianGto
    DamianGto
    lifeisjustgreat said:
    Hi DamianGto and all, have you got any idea if I do factory reset after apply z4mod, am I still able to unpatch the kernel and back to my original kernel? Thanks a lot.

    Sent from my GT-I9000 using XDA App
    Click to expand...
    Click to collapse


    I would change first before i did the factory reset.
    It does remove all user data.

    **Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
    View

New posts