Related
OK. I've been asked to create a new thread so I can update the OP with the latest info, so here we are.
First off, if you currently run voodoo, or any other lagfix, YOU MUST DISABLE IT.
DON'T FORGET TO BACKUP YOUR DATA. We make an effort to backup for you and restore, but it's entirely possible that the process will lose your data or otherwise break things. I recommend Titanium Backup for apps/data, please only backup/restore user apps/data with Titanium. System level stuff sometimes doesn't restore properly, causing FCs and other errors.
Now, install the kernel.
http://www.tabbal.net/files/Kernel-ttabbal-v1.7.zip
REBOOT. The z4mod will not install properly if you are not booted into one of my kernels.
Now you can install the z4mod. Reboot into STOCK recovery, then select "Reinstall Packages" to get to clockwork. Now you can install the ZIP below. DO NOT INSTALL FROM ROM MANAGER. It will work, but /cache can't be dismounted if you do it that way, so you can't convert it.
http://www.tabbal.net/files/z4mod-ttabbal-ext4-v1.5.zip
If you want to get back, which you need to do to convert between ROMS and such, here's the revert script.
http://www.tabbal.net/files/z4mod-ttabbal-rfs-v1.5.zip
Tested on Bionix Final and Fusion. Reports of it working on Eugene's ROMS and JI6. Note that if you want to run JI6, you need to install the kernel backport package from Eugene here.
http://forum.xda-developers.com/showthread.php?t=796425
FAQ:
Q) Can I run z4mod with JAC/KK/JI6/Stock Kernels?
A) NO. The kernel has to be modified to work properly with z4mod. So far, I have been unable to build JAC/KK kernels from source. Someone did manage to modify a stock JI6 kernel, but I am unsure of the results. If it has been confirmed, I will add a link here.
Q) What do I need to do to flash a new ROM?
A) Convert back to RFS with the RFS zip above.
Q) I get errors in Clockwork when trying to flash ZIPs.
A) I'm working on that. The workaround for now is to use "adb shell" to mount the partitions manually. Then it will work. The exception is a full ROM flash. You must revert back to RFS for those.
Q) Why bother? VooDoo, OCLF, etc. already exist.
A) z4mod has more potential. We can convert just about any partition to use whatever filesystem we want to. Voodoo and OCLF are limited to /data. The same tricks could be used to convert others, but z4mod is a cleaner design which makes doing that easier.
Thank You
Thanks for taking the time to build a Kernel for the Vibrant that will work with the Z4mods. It was starting to look like no devs were going to work on this Lag Fix mod for the Vibrant!
By the way, have had installed for a week now and everthing is working great, and I'm really digging the Backlight notification built in!
Running Bionix 1.1 with
Ext 2 for Data, DBdata, Cache, and System! No more RFS!
When you say "The exception is a full ROM flash" do you mean that a full ROM flash will not have any problems flashing from CWM after reverting back, or is it still necessary to do an adb mount?
Thanks a lot for the new thread. Much more organized.
Thanks for creating the new post...I was going to post this today as well
The 1.7 kernel version is working perfectly on my Bionic Fusion rom.
Appreciate all your work.Hopefully more people will try it out now...
Sent from my Galaxy using Tapatalk
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
jdkackley said:
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
Click to expand...
Click to collapse
I think he is working on that.
bstromberg said:
When you say "The exception is a full ROM flash" do you mean that a full ROM flash will not have any problems flashing from CWM after reverting back, or is it still necessary to do an adb mount?
Click to expand...
Click to collapse
For a full ROM flash, you must flash the RFS ZIP file, reboot to recovery, then flash the new ROM. The reboot is important, don't skip it.
Wow, thanks for starting this up anew.
Is there a way to convert /cache or others? Any caveats to converting other partitions?
Wow, this is like night & day compared to stock & feels a bit faster than Voodoo.
I did a fresh install of Bionix (older version with voodoo) and played with it & then did a fresh install of Bionix (same version, stock kernel) and then flashed z4 on top of it & it still feels a bit snappier.
I did that so I could get a feel for the differences between it & voodoo (non-scientific).
I'll probably finally upgrade to Bionix Fusion 1.1 with this kernel since it doesn't offer voodoo anymore & this actually seems faster than voodoo for me.
THANK YOU FOR THIS!
Kubernetes said:
Wow, thanks for starting this up anew.
Is there a way to convert /cache or others? Any caveats to converting other partitions?
Click to expand...
Click to collapse
For me, it converted
/data
/dbdata
/cache
tjhart85 said:
Wow, this is like night & day compared to stock & feels a bit faster than Voodoo.
I did a fresh install of Bionix (older version with voodoo) and played with it & then did a fresh install of Bionix (same version, stock kernel) and then flashed z4 on top of it & it still feels a bit snappier.
I did that so I could get a feel for the differences between it & voodoo (non-scientific).
I'll probably finally upgrade to Bionix Fusion 1.1 with this kernel since it doesn't offer voodoo anymore & this actually seems faster than voodoo for me.
THANK YOU FOR THIS!
For me, it converted
/data
/dbdata
/cache
Click to expand...
Click to collapse
Awesome. Silly question, but what do Quadrant scores look on this? I'm curious because database writes should be super fast with this, right?
jdkackley said:
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
Click to expand...
Click to collapse
No OC/UV. Personally, I don't miss the OC, it's that smooth with z4mod. I am looking into adding it, but hope to just work more closely with Team Whiskey to add it to their kernels as they are way ahead of me on OC/UV stuff. There's no point in everyone working on the same stuff. And if they handle the main kernel I can concentrate on other stuff.
I will try this when I can use other kernels.
ttabbal said:
No OC/UV. Personally, I don't miss the OC, it's that smooth with z4mod. I am looking into adding it, but hope to just work more closely with Team Whiskey to add it to their kernels as they are way ahead of me on OC/UV stuff. There's no point in everyone working on the same stuff. And if they handle the main kernel I can concentrate on other stuff.
Click to expand...
Click to collapse
Thanks for the quick reply! And I totally understand what you mean about everyone doing double work. There is no need for that. You guys all have enough that your working on.
I do have another question if you dont mind. Does this kernal affect either negatively, positively or nochange over stock, the battery life of the phone? The only reason why I ask is that I have noticed an increase in battery life for my phone while running VooDoo with JAC's OC/UV kernal. If no one has tested this at this point I am willing to flash it and give it a go and report back. But I just thought that if someone already has, then there is no point in me doing double work as well. As the battery life is what I really like about JAC's kernel. Thank you in advance! And just for the record this looks to be very promising in the future. Maybe if JAC is out there looking over any of this thread, hopefully he can chime in and provide us all with some insight or help. Thanks again Ttabbal! Great work!
Kubernetes said:
Awesome. Silly question, but what do Quadrant scores look on this? I'm curious because database writes should be super fast with this, right?
Click to expand...
Click to collapse
I have Data, Dbdata, cache, and System all converted to EXT 2 with the Z4Mod and my quadrants are around 1800. This lagfix is much faster than any lagfix to date whether you use EXT 4 or EXT 2.
The UV/OC really doesnt matter with this mod, but of course it could only get better when that is implemented.
Works Great! Thanks!
Followed the instructions and everything worked like a charm. Converted /data and /dbdata to ext4 and /cache to ext2. Ran Quadrant and got a score of 1621. Everything seems very snappy and smooth. Overclocking would be nice, but isn't really necessary. Great work ttabbal! Thanks!
dsellers2 said:
I have Data, Dbdata, cache, and System all converted to EXT 2 with the Z4Mod and my quadrants are around 1800. This lagfix is much faster than any lagfix to date whether you use EXT 4 or EXT 2.
The UV/OC really doesnt matter with this mod, but of course it could only get better when that is implemented.
Click to expand...
Click to collapse
I was getting 2100 with lagfix from TW's website. Then I OC'd.
jdkackley said:
Thanks for the quick reply! And I totally understand what you mean about everyone doing double work. There is no need for that. You guys all have enough that your working on.
I do have another question if you dont mind. Does this kernal affect either negatively, positively or nochange over stock, the battery life of the phone? The only reason why I ask is that I have noticed an increase in battery life for my phone while running VooDoo with JAC's OC/UV kernal. If no one has tested this at this point I am willing to flash it and give it a go and report back. But I just thought that if someone already has, then there is no point in me doing double work as well. As the battery life is what I really like about JAC's kernel. Thank you in advance! And just for the record this looks to be very promising in the future. Maybe if JAC is out there looking over any of this thread, hopefully he can chime in and provide us all with some insight or help. Thanks again Ttabbal! Great work!
Click to expand...
Click to collapse
I'm also wondering about battery life. That's the only reservation I have about the kernel required for this lagfix. I have been getting horrible battery life recently even though I've conditioned and all that jaz. So I'm a little worried about it.
I hope everyone understands that I'm not really concerned about the actual overclocking as much as I am with the undervolting of the CPU at midrange speeds. Strictly for battery life. I am completely aware of the benefits of converting the filesystem to extension 2/3/4 and do realize that this will greatly enhance the speed of the phone. I just wanted to be clear. And I am in no way trying to give anyone any type of attitude or imply any type of flaming what so ever. Thank you all for sharing your experiences.
When I went to install the z4mod it completed in like 3 seconds but in the text it says "This WILL take awhile". I'm wondering if I did it right, I followed directions in OP completely. I'm running JI6.
Edit: Also for some reason It wont allow me to install anything from the market, so, I probably screwed something up. Not sure how tho.....
If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Vibrant? I only have an I9000, but the app (and lagfix) should work fine on the Vibrant as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
Awesome, Thanks Ryan! Downloading now, will report.
Update: Stock JK2 kernel patched fine but the conversion to ext2 did not work.
testing...........
Whitehawkx said:
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.
Click to expand...
Click to collapse
Quote above from i9000 forum, but thought I should reply here since this is for Vibrant.
Same for me. I am on a Vibrant Running TW Obsidian V3.1, stock kernel. Uploading my kernel, patching & redownloading all seemed to work. Selected convert filesystem, the app said it was copying files, etc., and rebooted. App still says FS is RFS after reboot, and Quadrant score is the same. Maybe doesn't work with this ROM?
Also, I was surprised there was only an option for ext2. I thought the point of z4mod was to use ext4 or some other format. I apologize if I am mistaken. Thanks for all your hard work! OCLF app is great.
justingriff said:
Quote above from i9000 forum, but thought I should reply here since this is for Vibrant.
Same for me. I am on a Vibrant Running TW Obsidian V3.1, stock kernel. Uploading my kernel, patching & redownloading all seemed to work. Selected convert filesystem, the app said it was copying files, etc., and rebooted. App still says FS is RFS after reboot, and Quadrant score is the same. Maybe doesn't work with this ROM?
Also, I was surprised there was only an option for ext2. I thought the point of z4mod was to use ext4 or some other format. I apologize if I am mistaken. Thanks for all your hard work! OCLF app is great.
Click to expand...
Click to collapse
I was running it on stock rom so I'm betting it's strictly a coding issue. As for ext2 being the only option I believe it's b/c that is all the stock kernel supports. Someone correct me if I'm wrong...
Whitehawkx said:
I was running it on stock rom so I'm betting it's strictly a coding issue. As for ext2 being the only option I believe it's b/c that is all the stock kernel supports. Someone correct me if I'm wrong...
Click to expand...
Click to collapse
Correct. I think stock also supports ext3 also
Tested on stock 2.1 ji6, Error: Cannot patch kernel.
Worked perfectly on stock 2.1
Tested on TW 4.2 ULF with Eugene's A12 kernel... couldn't convert...
Tested on Eugene stock Froyo build and it works...
Worked like a charm Ryan! I had to root phone again due to a soft brick last and your Z4root got me rooted quick and easier than the previous method I used. Thanks!
Didn't work for me, on stock 2.1 (ji6). It would only reboot into recovery after patched kernel was applied.
Does it work with Froyo?
Also how different is it from the Universal Lagfix that team whiskey has?
hanbaoquan15 said:
Does it work with Froyo?
Also how different is it from the Universal Lagfix that team whiskey has?
Click to expand...
Click to collapse
Yes it works with Froyo. This is an app that patches the kernel, not an entire kernel replacement like the ULF. This is a bit less invasive because any future kernel changes from Samsung won't require a reflash. On the other hand, ULF has far more options (including formatting more than just /data and your choice of file systems -- although z4 has stated RyanZA will add these options in future releases)
I want to convert all of /System.
Thanks
Gave it a shot. Uploaded kernel, patched it, downloaded it, rebooted to flash kernel, but doesn't seem to flash it. Every time I reopen the app it wants to try flashing it again. Is it just a CWM .zip that I can flash manually, and if so where can I find it?
I'm running Macnut R12 with stock JK2 kernel.
budney said:
Didn't work for me, on stock 2.1 (ji6). It would only reboot into recovery after patched kernel was applied.
Click to expand...
Click to collapse
Nope -- doesn't work. What's the simplest way to fix this?
It seemed to patch the stock JK2 froyo kernel, but the filesystem would not convert to ext2...
legit mod!
scrizz said:
I want to convert all of /System.
Thanks
Click to expand...
Click to collapse
That won't do anything as /system is read-only. The lag comes from writebacks.
If we unroot with z4 with the phone flashed with a rom will it brick?
Sent from my SGH-T959 using XDA App
Every single one of them are failing @ System.
I have flashed many roms and have yet to see this issue.
I have even tried to install a nandroid and they say system.img not found, skipping restore of System
my quadrant before doing anything was ~950 so im assuming no lagfix was present.
did you flash back to stock with odin1click??
ed116 said:
did you flash back to stock with odin1click??
Click to expand...
Click to collapse
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
iamamp3pimp said:
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
Click to expand...
Click to collapse
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
ccdoggy said:
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
Click to expand...
Click to collapse
+100000000
iamamp3pimp said:
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
Click to expand...
Click to collapse
Because it is the phone...not the rom or kernel...unless you had a bad flash to begin with.
This is why it is recommended when switching to different roms...and even sometimes flashing updates to certain roms ...that it is the most prudent thing to do, to head off these types of issues that come up sometimes. It is also recommended to do a master clear as well...and I usually go one step further and wipe and format the drives and do a factory reset. Sometimes doing it more than just once too. It may be a royal PITA...but...the alternative is what you are experiencing it seems...
Mac
is there a way to tell which filesystem is being used?
i have CWM 2.5.1.2
my Axura restore did work.......so i at least have a phone for the moment
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
I don't see why not. You can try and if it don't work you can flash an older version in ROM Manager
vinnyjr said:
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
Click to expand...
Click to collapse
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
I guess I won't find out until I try. Newly rooted and going to give CyanogenMod a try. Know I am going to be happy as hell with it.
Thanks
The new recovery should be fine with flashing any roms. As for any standing problems with it, im am uncertain. You may want to wait 2 weeks or so to see if their are any problems from people using it. Personally I like Amon ra so i cant say.
ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
Click to expand...
Click to collapse
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
mikeacela said:
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
Click to expand...
Click to collapse
Yes. I did full wipe on everything. I even fix permission. No luck at all.
ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
Click to expand...
Click to collapse
I used it to flash and install tonight's build successfully...
I have a "side question".
To flash any GingerBread flavor, do we need 3.x.x.x ou 2.5.x.x is working?
I haven't give CM7 a try yet, but I'm not sure if I need/want to upgrade to 3.x.x.x, 2.5.1.4 work well for me.
DumbUglyDragon said:
I used it to flash and install tonight's build successfully...
Click to expand...
Click to collapse
I got it too. No more crazy rebooting. I solve it by reformatting my SD card and recreating ext3. I guess 3.0.0.5 recovery messed up my ext3 partition. Now, MM CM14 is working pretty well. FYI, I am using 2.5.1.4 recovery.
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
doesn't work with MIUI for me!
don't understand that, but luckily its not a big deal flashing older versions!
baseballfanz said:
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
Click to expand...
Click to collapse
I hear you there! That was me last night! DON'T USE 3.0.0.5! The only fix I found to actually work was to completely format my SD card and then re-partition it, then use RA and a fresh install. What a pain in the arse!
Same thing here. Switched to 3.0.0.5, and the next thing, my ext was fried and I had to reformat the entire card. Could be coincidence, but...
Sent from my Nexus One using XDA App
Hey I have a question I am on Darkyy 9.3 and have flashed to stock before numerous times and have a Download Mode Jig always handy but I have been hearing and reading recently that with good ROMs with the new install script that you can just flash ROMs over each other if you wipe data and cache and dalvik cache and if you get in trouble just flash to stock.
The reason this interests me is because im a build 1011 and its super annoying because I have to flash to JH3, then Root, then apply 3 button fix.zip sometimes if the 3 buttons dont work, ROM Manager, Quick Boot, JH7ota.zip, then flash the next ROM.
I am willing to do this but I am feeling lazy today and wanna try out Serendipity so Im asing YOU do you think i'll be alright if I flash Serendipity JS3 over a JS5 Darkyy 9.3?
Also one more questions related to that is Serendipity users does it overwrite your Kernel and modem when flashing? I have Suckerpunch and JL3 and am wondering if I should disable lag fix-->Install latest Speedmod. Or would the ROM script just overwrite that.
Finally a question that was posed to me today from a user that doesnt flash to stock and hasnt had a problem that really made me think that what really is the difference when using Odin which installs an unneccesary bootloader and ect going from a JS5 base to a JH3, then using CWM to go JS5 to JS3? Wouldnt it seem logically easier and safer?
Any input and comments about your experience will be GREATLY appreciated.
you can use odin1click, or odin3...
since you have a jig, flashing to stock is not a big deal to you.
Owais1437 said:
you can use odin1click, or odin3...
Click to expand...
Click to collapse
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
I Odin3 back to stock, but I'm also on the safe side. I have heard more and more people flash over the old ROM with using Odin though.... I figure that it only adds a few more minutes to the overall task, so why not?
always flash stock imo
just best to go to stock , flashing over has created small bugs for me ..., i do this even for common builds or updates, even though the Dev's work hard to make them upgradeable...i still do .....and if your courageous,,, its good you have the jig or a 1007 build
My personal choice is flash to stock if the roms use different kernels. If the kernel is the same, even different revs of same, I don't bother with stock.
Sent from my Captivate using XDA App
mengbo said:
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
Click to expand...
Click to collapse
I use print one click all the time and my phone is build 1012
Sent from my SAMSUNG-SGH-I897
I always flash to stock and go through the whole process. I find it less buggy and the mental idea of a clean slate allows me to address issues solely on that rom and not past components.
It's sure as heck faster to flash to stock than to read through 1000's of posts to figure out if it's a good idea or not when I don't know as much about it...
I'm still new to the flashing ROMs world, but I'd rather be safe than sorry at this point so I go back to stock whenever I switch.
Ive now just wiped data cache and dalvik cache, and flashed over 4 ROMs in the past week with ZERO problems.
That being said im always safe I do it at home with my jig and odin ready on my PC.
But i actually havent had a single problem.
Darkyy-->Andromeda-->Paragon-->Serendipity