[APP][ABANDONED] z4mod

RyanZA

Senior Member
Jan 21, 2006
2,023
778
0
JHB
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
 

Attachments

Last edited:

DAGr8

Inactive Recognized Developer
Feb 27, 2010
3,713
6,309
263
Montreal
quick question I need to disable vodoo before using this right ?

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

testing now
 

RyanZA

Senior Member
Jan 21, 2006
2,023
778
0
JHB
quick question I need to disable vodoo before using this right ?

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

testing now
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.
 
  • Like
Reactions: KeesKaas

epakrat75

Senior Member
Aug 11, 2010
1,054
107
0
Chicago
- 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.
I have a Vibrant and this is why I have avoided using the OCLF in the past. Many ROMs don't even need a lag fix. However, with that issue gone, I'll at least try it and report back on it. :D
 
Last edited:

DAGr8

Inactive Recognized Developer
Feb 27, 2010
3,713
6,309
263
Montreal
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.
hey I forgot to mention I had flashed setiron's reoriented kernel on it , so yea result is could not patch kernel ..
 

DamianGto

Senior Member
Sep 17, 2010
2,022
420
0
I guess i have more test to do. But right now Im stuck with 0.12 problem.

I did test it:p
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.:p
Instead of restarting the phone.

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

RyanZA

Senior Member
Jan 21, 2006
2,023
778
0
JHB
I guess i have more test to do. But right now Im stuck with 0.12 problem.

I did test it:p
I knew it would not work.;-)
The thing i was testing was if you could do this on a kernel that has note been patched. Well you can press the button and the phone restart. I guess it try but failed and restart again.
Can you do a check on the kernel so you know its patched?
I thinking of ways happens if people try every kernel without the patch. It should point them to the website.:p
Instead of restarting the phone.

Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
It checks for a /z4mod/z4version file to determine if it's been patched already. If you are using an earlier patched z4mod kernel that doesn't have that file, then it won't work right. If you start with a stock samsung kernel then it should work fine.

can i use this with speedmod kernel?
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels. At present, any custom kernel that does not change the initramfs (in particular, the /init binary and init.rc mount options) too heavily should work fine.
 
Last edited:

Whitehawkx

Retired Recognized Developer
Oct 13, 2010
2,447
9,270
0
Emerald City
Hey Ryan,

I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
 

DamianGto

Senior Member
Sep 17, 2010
2,022
420
0
Okay. Then its just because the bug in the latest z4build then.
That's why it tried to apply the change.
Z4ziggy is working on that problem:p
Hope he will solve that soon. Right know Im on stock filsystem with my new kernel. Lol.
Kind of fun to compare them.


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

Whitehawkx

Retired Recognized Developer
Oct 13, 2010
2,447
9,270
0
Emerald City
Hah... Okay that's pretty strange. What method did you use to root btw? Perhaps it's a busybox conflict of some type.
Hmmm the rom/kernel I flashed came pre-rooted. Now that I think about it, I was using the stock JK2 kernel but it has a custom init script to allow the use custom boot animations. Could this be effecting the conversion process by chance? Anytime I manually root though I use OCLF from the market.
 

yiannisthegreek

Senior Member
Jul 2, 2009
1,996
256
0
Edmonton
Hey RyanZA,

I see that there is a list of devices in the first post but I dont see a listing for the GT-i9000M specifically. I see the i9000, i9000B and i9000T but no "M". Is there a reason for this? Is the i9000M considered in the generic i9000 family? Also...

A bit off topic here but I am curious to know if I root using z4root and need to unroot for warranty purposes, will it remove ALL traces that it had been rooted including Busybox and Superuser app?

I know that Samsung has issued a memo stating that if a phone shows up rooted to a service center that the warranty will be voided and Id really like to try this rooting method.

Also, as you are probably aware, the i9000M here in Canada has issues with internal sd card failures and I am curious to know if just rooting with z4root will possibly kill my internal sd?

Thanks...
 

DAGr8

Inactive Recognized Developer
Feb 27, 2010
3,713
6,309
263
Montreal
Feel free to give it a shot, but the current emphasis in this 0.9 app release is on patching and lagfixing the stock samsung kernels. Once that is all working and bugfree across devices, then I will look more at supporting custom kernels.
should probably put this on OP , less hassle probably .

if nobody else test it on the cappy ill flash to stock just to test ..
 

z4ziggy

Senior Member
Sep 10, 2010
87
15
0
@DamianGto:

The problem is with CWM recovery - it's busybox-tar is not working properly.
I think I found a way to overcome this and I updated the git, so now CWM option should be working again.
 

z4ziggy

Senior Member
Sep 10, 2010
87
15
0
Hey Ryan,

I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
If you could paste the contents of the following 2 files we might learn more:
/z4mod/log/init
/sdcard/z4mod.log
 

likeberty

Member
Sep 18, 2010
10
0
0
Just installed on my device (GT-I9000 with official JPA just released today in Thailand)

It worked fine. I got 1730 from quadrant.

Thanks for your excellent job. ^__^