yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Ashex1:
ext3 is still considered experimental so fastkatt may have just gone with the ext2 conversion. I use the auto convert and it kicked over to ext3 for me. ext4 is not available by default but if you grab the source of z4mod you should be able to patch it to do ext4, but once again that's experimental. Regarding the wake lag I may just be blowing air as I'm extra sensitive to the phone lag since my other phone is a N1 running froyo.

I grabbed the JI6 odin tar and pulled zImage out of it then patched it. Once I did that I stuck it inside a tar and used odin to flash it to my phone. I'm not posting my kernels just yet, I'm going to wait until a stable release of z4mod is out then I'll start patching and posting them.

If you're on windows with your phone connected open command prompt and run the command 'adb shell mount' (assuming debugging is enabled) it will list the mounted partitions. Here's my layout for an example:

rootfs / rootfs rw 0 0

none /proc proc rw 0 0

none /sys sysfs rw 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

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

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

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/stl9 /system rfs ro,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0

[b]/dev/block/mmcblk0p2 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0[/b]

/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

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

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

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

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

/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Vibrant Android Development] FastKatt:
I pulled my kernel from the ODIN tar. I used clockwork recovery to flash it. If you want to use clockwork instead of ODIN, an easy way to "build" your zip is to grab one of the other clockwork kernel zips around here (like a Jac kernel) and replace the zImage contained in the zip with yours.

I chose ext2 because that was the most tested under z4 at the time and I knew the JI6 kernel supported it. JI6 also supports ext3 but I wanted to start simple. Fortunately, it has worked so well I haven't felt the need to try any others though I do want to get ext4 working. I wouldn't read too much into the wake lag. I'm very diligent (obsessive maybe? :)) about closing anything I'm not using and closing everything before I lock the phone. This may be why I don't see wake lag.

Currently I am trying to get a Jac ext4 compatible kernel to work. I chose the Jac kernel because I would like to have the OC/UV features in addition the ext4 support. Unfortunately, the kernel repacker script used in z4 does not work with compressed initramfs which is what the Jac kernels use. I'm hacking away at this problem but progress is slower than I'd like. The stock JI6 kernel contains an uncompressed initramfs so the scripts work fine with this.
[Vibrant Android Development] rogerchew:
awesome thanks man! just did the ext2 conversion and things are going smooth so far.

so im going to assume the zimage is the main part of the zip that contains all the specific kernel changes, while everything else in the zip file is standard? i have a JI6 tar that i've been using odin with, so with this method i'll be able to build my own stock kernel?
[Vibrant Android Development] FastKatt:
zImage is the kernel. It contains the kernel and initramfs to startup the phone.

The clockwork flashable zips like Jac1.1 that flash just the kernel contain other files but zImage is the only file that you need to change. The other files tell clockwork to use the redbend app to flash the zImage to the phone. You can find instructions on XDA that tells you how to build your own clockwork flashable zip. For this exercise, following those instructions, you will end up with the same contents as the Jac cw flashable zip but with your zImage instead of his. If you want to do something more than flash the zImage you should search for and read the instructions to learn the details. You probably should anyway so you are comfortable with what you are doing. However, in this case, drag and drop is your friend if you want a quick "fix". ;)

If you do use drag and drop, make sure you drop the zImage into the same folder in the archive where the existing zImage is. This overwrites the zImage that is there and puts your zImage in the place the scripts expect it should be.
[Vibrant Android Development] ubernewb:
now if only someone could take the gps fix, combine it with ext3 mod, then overclock it, we'd be in business! haha.. seems like people only pick one, then put out their mod. so hard to choose which one to go for
[Vibrant Android Development] rogerchew:
personally, with the lag fix, i see no reason to overclock the phone. but to each our own! ;)
[Vibrant Android Development] ubernewb:
why do the lag-fix? the phone worked great before it.. the answer is simple.. we all want TEH POWA!! haha

if i can make it faster without destroying the reliability of the phone, why not?
[Vibrant Android Development] betasp:
Ok, I flashed ext3. Fast... fast. Good with large Nand chips, too.
[Vibrant Android Development] ubernewb:
any chance you could post your zimage file with ext3? i've been throwing different ones at the online tool for the past hour, but keep getting errors =[
[Vibrant Android Development] Ashex1:
Currently it looks like only stock kernels work. Did you try the stock JI6 kernel?
[Vibrant Android Development] ubernewb:
searching for that one to try next.. all the ones i have on my pc are modded.
[Vibrant Android Development] Segnaro:
I posted a prepatched one a few pages back. Here's the original unpatched JI6 kernel.
[Vibrant Android Development] ubernewb:
thank you! =]
[Vibrant Android Development] metalfan78:
I tried this last night, flashed the patch, then the auto mod.zip. In recovery it said it was converting file system, it finished and rebooted then hung on the vibrant screen forever. I eventually had to use odin to get up and running again. Did I miss something, did this happen to any one else. I'm running bionix 1.9.1 w/ kk kernel

The cake is a lie!
[Vibrant Android Development] wildklymr:
First ive seen this. Reminds me of the soft bricking voodoo sometimes does.
[Vibrant Android Development] metalfan78:
I might try it again with the ext 3 mod. Can I ask which one most are flashing?

Bionix 1.9.1 w/ kk kernel
[Vibrant Android Development] stephenj37826:
Me too same exact thing.never used odin before I almost cropped my pants lol
[Vibrant Android Development] metalfan78:
Lol, yea the first time I used odin it was a little freaky, but it's pretty easy to use

Bionix 1.9.1 w/ kk kernel
[Vibrant Android Development] dsellers2:
How were you able to get rid of Voodoo Completely before flashing another Kernel? I'm aware of using the "disable lagfix" file and reboot and let it change back to RFS. But after that the Voodo folder still exist. Because the Folder is still there it would seem that Voodoo is not completely gone...Just disabled.

Do you just flash the Z4 mod stock kernel and after that can you successfully delete the Voodo folder or do you leave the Voodoo folder? That is my only concern up to this point is completely ridding myself of Voodoo before implementing a Native conversion or Z4Mod.

I'd be interested in seeing the process of someone that was once on Voodoo and switched to the Z4Mod. In my searching I have not seen a clear way to completely rid my self of Voodoo.

Thanks,

Dave
[Vibrant Android Development] Bernardos70:
You guys up to some noob questions?

1. Does it wipe all data?

2. Does ROM Manager work within it, and how easy is it to revert back to stock file system?

3. If/when reverting, how would I get it back to the regular File system work? Would I then lose data since I don't see any ext2 > Samsung's FS? (not that consequential).

4. Anything else I should know besides what has already been said about the process when dealing with large NAND chips, which I have?

I think that's it for now. I'm extremely excited about doing this tonight once I get home.
[Vibrant Android Development] javacody:
How do we get back to stock for future OTA releases?
[Vibrant Android Development] Segnaro:
disable-lagfix file in Voodoo folder is all you have to do.

Flash z4mod.rfs.update.zip to revert to the original file system.

1. No

2. Yes. Flash z4mod.rfs.update.zip to revert to Samsung's FS

3. z4mod.rfs.update.zip. I did not experience data loss
[Vibrant Android Development] imthekuni:
I had the same problem with bionix 1.9 w/ stock kernel, hung at Vibrant screen.
[Vibrant Android Development] Bernardos70:
Thank you for the reply! I'm considering using your JI6 patched (following your instructions, obviously). Comfortable enough with Odin to go back to unpatched stock, even wiping whole phone, it's not a big deal. I'll do it tonight at home!
[Vibrant Android Development] Whitehawkx:
I'm curious if KingKlick's kernel will work with EXT4 mod. In his changelog it says "Added support for EXT4 filesystems." Soooo if the Z4 patch tool just enables support for different ext's, shouldn't King's kernel be good to go then? At least with the EXT4 mod? I suppose I could just give it a go myself and report back, but I'm at work so will be another 7 hours... :P
[Vibrant Android Development] rogerchew:
the update.rfs.zip file that goes back to rfs has crapped out on me twice now, everytime it goes into recovery, the up/down buttons work, but the power button to select doesn't. annoying....had to odin twice last night.

getting to convert to ext2 and ext3 on the other hand works just fine, its' booting into recovery that effs up. you end up in a continuous bootloop in recovery and you can't get out.

btw, for ****s and giggles i was running quadrant on the different file systems:

one click lag fix = ~2100

4z ext2 = ~1800

4z ext3 = ~1200
[Vibrant Android Development] Ashex1:
Are you talking about the voodoo folder in /sdcard? That is for storing logs and can be deleted. Voodoo doesn't work for me due to my phone having a larger NAND.

To disable Voodoo, check this thread it's in the first post. Essentially you have to disable it, reboot then verify it is. After that you can change out the kernel.

And just to reiterate it for everyone PRESENTLY ONLY THE STOCK KERNEL CAN BE SUCCESSFULLY PATCHED VIA THE ONLINE PATCHER.

If you get into a reboot loop you'll need to patch a stock kernel then flash it using ODIN.

ADDITIONALLY, THE Z4MOD BREAKS STOCK RECOVERY DUE TO A KEY MAPPING ISSUE, MAKE SURE THAT DEBUGGING IS ENABLED SO YOU CAN USE ADB TO REBOOT OUT OF IT. USE CLOCKWORK FOR FLASHING ZIPS.
[Vibrant Android Development] aloxotls:
Does this only work on stock ROMs? I have tried both Bionix and Hybrid R4 and I get stuck in a boot loop. It happens every time I flash the patched Kernel, I do not even get a chance to run the update.zip to convert the file system. I know my patched kernel is good because it works fine when I load the JI6 stock ROM.
[Vibrant Android Development] Whitehawkx:
I believe Eugene states in the OP for the Hybrid4 that the stock JI6 kernel does not work with his rom. That said, you will need to patch the stock JFD kernel and use it instead.

EDIT: See my previous post regarding King Klick's kernel. I'm curious if it will support EXT4 Z4mod since it says it has EXT4 support built into it.
[Vibrant Android Development] rogerchew:
ugh so that's what it was... btw, how do you use adb to reboot out of it (for future reference)?

adb reboot?
[Vibrant Android Development] krylon360:
how did you get the ext2 script to load. JI6 patched kernel boots me into stock recovery with a non working power button, so I can't flash the script, cant even boot into CW
[Vibrant Android Development] Ashex1:
Scroll up, you need to enable usb debugging so you can use adb to reboot out of it. You have to boot into Clockwork to flash the update zip.
[Vibrant Android Development] rogerchew:
using the patched JI6 kernel posted in this thread worked, it allowed me to boot into recovery just fine. the problem i had was when i tried to undo the conversion. Then i would get stuck in recovery with a non working power button.
[Vibrant Android Development] aloxotls:
You are going to have to use the Clockwork Mod app and select install rom from sd and choose the zip you want to flash.
[Vibrant Android Development] Whitehawkx:
So just for clarification - the Z4mod only breaks the power button in stock recovery, but in clockwork everything works fine... is this correct?
[Vibrant Android Development] wildklymr:
No, theyre talking about the actual rom manager application with the phone booted up
[Vibrant Android Development] aloxotls:
I tried to use the Z4mod on King Klick's kernel and at first I could not get it to convert because it checks the kernel to see if it is patched. So I deleted the checks out of the script and got it to convert but King Klick's kernel would not recognize the /data folder.
[Vibrant Android Development] Whitehawkx:
Well... damn. Good to know. Thanks for heads up, was gonna try when I got home. I'm really hoping to get this working with one of the OC kernels. Even though I've read it's not really needed, it's always nice to have options. I'm sure someone will figure it out in due time.
[Vibrant Android Development] es7241:
This happens to me too, because I guess since this Z4mod is for the I9000 it changes to its recovery so the key mapping is off and it is impossible to select with the power button. But all I did was reflash the Stock Kernel with ODIN, and i am currently in clockwork right now trying to get back to RFS to flash Bionix Fusion to try this mod with that.
[Vibrant Android Development] Ashex1:
Gah, I really want to get /dbdata converted as everything that reads/writes from there lags and I've had the phone lock up once because of that :(
[Vibrant Android Development] FastKatt:
When running the kernel patching script use the "-norec" option to keep it from changing the recovery.

Example: z4build -norec zImage
[Vibrant Android Development] wildklymr:
could someone who has downloaded the original z4build please post it? The link in the i9000 op seems to be broken. And I'm getting errors trying to mod the stock jfd zimage with the website ryanZA set up. Thanks in advance.
[Vibrant Android Development] es7241:
Does the Online Kernel Patcher support that, because isn't the script only for linux, but I am running windows... I just used the kernel posted in the previous pages here because when trying to patch the kernel online I keep getting errors.

UPDATE

I was able to patch the Stock Kernel with the online patcher but it replaces the recovery :-/
[Vibrant Android Development] rogerchew:
Absolutely right, thats why the undo messes up. Havent been able to successfully undo the conversion without going through odin.
[Vibrant Android Development] Segnaro:
Use ROM Manager to reboot into Clockwork Recovery, but it would be better getting flashing a patched kernel without the broken recovery mode.
[Vibrant Android Development] rogerchew:
Question how do you boot into clockwork through rom manager if after flash youre stuck in recovery with broken power button? How do you get out of recovery?
[Vibrant Android Development] Segnaro:
If you reboot into recovery through Rom Manager, it takes you to Clockwork Recovery where the power button still works.
[Vibrant Android Development] wildklymr:
RyanZA says he will add an option to the online patcher for no recovery.
[Vibrant Android Development] rogerchew:
Oh sweet this is going into oclf?

Nm... You talking about the patcher for the kernel
[Vibrant Android Development] wildklymr:
Yeah the patcher. RyanZA took over this, so ziggy can go on to bigger and better things.
[Vibrant Android Development] down8:
Anyone have issues with Swype after this mod?

Stock, rooted, applied modded kernel, applied ext2.

I didn't lose root, but now Swype is messed up. First it wouldn't run at all. I switched to Samsung kb, rebooted, switched back to Swype. Now, it comes up, but is missing all the special keys (letters are there, but the emoticon key, the Swype key, etc., are just blank keys).

Any issues like this for anyone else running the stock JI6 with this mod?

EDIT: I also applied the Rescan Media mod after the ext2 update - not sure if that may be pertinent.

-bZj
[Vibrant Android Development] rogerchew:
hmm...might be the mod, cause my swype was fine when i first converted to ext2.
[Vibrant Android Development] imthekuni:
is anyone else getting stuck at the vibrant boot screen after flashing a z4mod JI6 kernel using Bionix 1.9 (w/ stock kernel)?

I have used both the earlier posted modded JI6 file as well as one I patched online

used ODIN to revert to stock JI6 and still stuck at vibrant boot screen
[Vibrant Android Development] rogerchew:
i got stuck at the vibrant screen as well but it had nothing to do with bionix.

fortunately, the fix to this is you gotta use "eugene's froyo no brick tar" and odin with that then odin back to stock in order to boot up again.
[Vibrant Android Development] down8:
I also can't complete a run of Quadrant - it stops benching at the 3D tests. WTF?

EDIT: Finally finished a Quadrant run - 1884 using ext2! Not bad at all. But I really want Swype back....

-bZj
[Vibrant Android Development] Segnaro:
Did you convert back to RFS?
[Vibrant Android Development] javacody:
I thought ODIN would reformat all the partitions that should be RFS? You need to include the PIT and PDA files, right?
[Vibrant Android Development] aloxotls:
I was having the same problem and it is because Bionix still uses a JFD kernel and not the JI6 kernel. If you use odin and flash JAC's or KK's kernel it will boot up just fine.
[Vibrant Android Development] krylon360:
same issue here with bionix fusion. I'm looking into the issue. The modded JI6 flashes in CW, you can then flash the z4mod script, then just hangs at the vibrant screen, but you hear the startup sound.

I can get out of it by flashing a non-patched kernel in odin, but then it unroots me. so I just reroot.
[Vibrant Android Development] wildklymr:
Does anybody have the original Z4build script? The online patcher that RyanZA made hates me, and I didn't save the original Z4build. Or since we have a patched stock JI6 Kernel thanks to Segnaro, could someone who has had success with the online patcher please patch and post the stock JFD Kernel please?
[Vibrant Android Development] Segnaro:
http://www.sgscompilebox.dreamhosters.com/files/z4mod-source-0.3.tar.bz2

Extra downloads and instructions for setting it up:

http://xdaforums.com/showpost.php?p=8643564&postcount=155
[Vibrant Android Development] wildklymr:
Awesome Thanks!

Edit: I'm getting an error when trying to patch.

I set up the editor.sh and the z4build like in that thread.

I have the jfd zImage in the same directory as z4build.

when I run it either with or without -norec I get...

./z4build: line 89: realpath: command not found

when I check z4build the lines it is referring to are

# Making sure we have everything

if [ $# -eq 1 ]; then

zImage=`realpath $1`

elif [ $# -eq 2 -a "$1" == "-norec" ]; then

zImage=`realpath $2`

RECOVERY="false"

I googled realpath and the first few links said it's php so I installed php5...same result.

Am I missing something? I have the Kernel repacker and the arm compiler.

Using ubuntu 10.04 x64
[Vibrant Android Development] Bernardos70:
OMFG. Is this real? Is it even legal for this to exist? Market opens instantly. Media scan takes 10 seconds. Wow. Thanks everyone (Segnaro for the patched JI6, Ziggy for the mod, RyanZA for the online patcher, and the OP here for bringing it to our attention). I can't even believe this. I don't even care about Froyo right now. Holy smackarel.

(BTW, I was on stock JI6, Rooted, did all of the flashing through clockworkmod recovery aka ROM Manager, not a single hiccup in the process. I knew this thing was blazing when the media scanner took 10 seconds instead of 2 minutes it regularly took!)

Signed

One completely stoked Vibrant owner
[Vibrant Android Development] rogerchew:
can you check to see if you mounted just /data or also /dbdata, /cache and /system ?? cause ryanza posted up a new script that converts those to ext2 as well and i wasn't able to get that one to work.
[Vibrant Android Development] imthekuni:
ya flashing modded JI6 hangs at vibrant screen, not sure why.

dont know why I should revert to RFS when the whole point of z4 is to use ext2/3/4 (using 2)
[Vibrant Android Development] Bernardos70:
Just now? I downloaded whatever was in the original post at around about 2 hours before you posted. I don't know how to check those, and I'm going to bed right now, but if you reply in the next 5 mins or so I'll check it for you. :D
[Vibrant Android Development] rogerchew:
in adb shell type "mount" and see which folders are ext2 and which are rfs.
[Vibrant Android Development] ttabbal:
http://xdaforums.com/showpost.php?p=8746153&postcount=63

JFD based kernel, built from source, with a working z4mod zip package. I'm running it on Bionix Fusion right now. :D

ext4 only for now. It would be pretty easy to make other versions though. It's also only /data right now. I will try to look into getting /dbdata and /cache converted as well. It should work, but I haven't tried it.
[Vibrant Android Development] Bernardos70:
Here is the snapshot:
[Vibrant Android Development] es7241:
Kernel doesnt flash it says E:Can't chown/mod ...... and so on but it would be nice if it worked
[Vibrant Android Development] rogerchew:
awesome man! think you could build a JI6 based kernel and get /dbdata and /cache converted as well? i checked the latest ryanza update from the original thread in I9000 and he was able to get /dbdata and /cache and /system? or something converted to ext2, but it didn't work with the vibrant for me.

below is ryanza's conversion for ext2 of /dbdata /cache etc. Didnt' work for me on vibrant patched JI6 stock kernel.

http://xdaforums.com/showpost.php?p=8731921&postcount=674
[Vibrant Android Development] rogerchew:
yea you only got /data as ext2, everything else is still rfs. that means it's the old update.zip file you're using, not the latest one that ryanza posted inside the thread.
[Vibrant Android Development] ttabbal:
Odd. I'm pushing the current test version up now. Just change 1.2 to 1.3 in the filename. If it still gives errors, please "adb pull /tmp/recovery.log" and get that to me. It's up, I have flashed it on my phone, so I know it works at least in some cases. :)
[Vibrant Android Development] ttabbal:
Curious, why so much excitement to get /dbdata and /cache converted? Is there a particular problem I'm not aware of with running RFS on those, other than that it's RFS? :D Those are pretty fast even with RFS on them.
[Vibrant Android Development] xavyi:
I would love to see this as well (:

*crosses fingers*
[Vibrant Android Development] es7241:
Seems to be working, only if we had an overclock and the Datadb and Cache But all is well , It is now converting the Data. Cant wait for ext2 and ext3 support.

Edit - I got a Soft Brick when after I flashed thee zh4mod, but the kernel itself worked fine...

Edit - After flashing z4mod again it worked!
[Vibrant Android Development] frank707:
i keep loosing root. any solutions? how can i reroot if rommanager won't reboot into clockworkmod recovery without su permissions, and i can't flash root update.zip through stock recovery because power button is not functioning in stock recovery with z4 kernel. Does someone have a working z4kernel mod JI6 kernel without the modded recovery, or have a odin flashable kernel mod z4?