Database Develop

z4mod for the Tab

Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/

Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.

Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?

knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.

jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477

doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know

evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?

Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it

[Q] VooDoo what?

What is the deal with voodoo?
Why would you want to disable a "fix"?
It sounds like "lagfix" would be something you'd not want to disable, but it seems to be something that most people disable.
Can anyone explain that one to me?

How much searching have you done? I'm pretty sure lagfix has been discussed a bunch of times.

... the lagfix is due to Samsung's proprietary RFS file system.
The "Voodoo Lagfix" changes the existing file structure and essentially makes the OS and I/O run smoother/faster.
People only disable it to be able to flash another ROM... although it is arguably easier to just flash back to stock and install the new ROM.

You may also want to disable the lagfix if you are looking to change the kernel or a theme. In normal use of the rom, no you would not want to disable
Sent from my SAMSUNG-SGH-I897 using XDA App

[Question]:zImage and modem binary swaps

I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?

Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?

This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?

Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.

d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.

Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above

I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk

birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???

Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?

I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood

Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!

Ext4 (on sdcard) for OpenZio

As I seem to be repeatedly losing files (including my entire music library, recently), and I am tired of it taking so long to recognize new files that I put on the sdcard via USB; I am starting this thread in hopes of starting efforts to get ext4 support included (or patched to) the OpenZio rom.
I apologize, Spz0, if I am stepping on any toes. Just thought this should be a separate thread from the main build thread.
--Reasons for using Ext4:
1. Native Linux filesystem. Mounts instantaneously, reducing boot time.
2. Journaled filesystem. Corrupt / lost files virtually eliminated.
3. Major performance improvements over Fat32.
4. Large file support (not my thing, but some people want it)
--Problem(s) with Ext4 on sdcard:
1. Unable to natively read card with Windows.
(still able to mount via USB to phone)
2. Permissions may be difficult to work out.
Any thoughts?

From what I gather in my searches, the following will need to be done to accomplish this:
1. Kernel module (ext4.ko) needs to be installed.
2. Appropriate libraries also need to be installed.
3. init.rc needs to have mount options changed.
4. Permissions issues need to be addressed.

Id love to see ext4 support but that lies within the kernel
Sent from my Kyocera Zio M6000 using XDA Premium App

It isn't a monolithic kernel is it? If not, modules can be inserted on the fly
Sent from my Zio using XDA App

A what now?
Sent from my Kyocera Zio M6000 using XDA Premium App

before i switched over to openzio rom i ran ext3 on my sdcard, but did not try ext4. now my linux machine is dead and gone i have not tried either with openzio. with ext3 i did notice a small increase of speed, but never benchmarked to see how much.

Ext4 performs substanially better than ext3. The biggest improvement with ext3 was adding journaling support.
As for inserting kernel module on the fly, I am speaking as a Linux admin. I can't really speak about the Android kernel in particular. Typically linux kernels are dynamic, and allow for inserting of kernel modules as needed. Alternatively, kernels can be compiled as monolithic (or static), meaning that all required modules are compiled into the kernel.
I believe the required module is ext4.ko. I also read that there are some required libraries as well.

Well with android our kernel lies within our boot image. I'm sure ext4 can be added it's just a matter of taking the boot.img apart and adding ext4.ko then rebuilding the image and flashing it to the boot partition of the phone.
Sent from my Kyocera Zio M6000 using XDA Premium App

As my car is in the shop, and I can't work (contractor that travels to jobs with a ton of tools), I may get more motivated to look into this more.
BTW, loosing my entire music library wasn't due to the filesystem, it was an ID10T error. I accidentally put one of my other SD cards in my phone, then proceeded to run over my 16GB card with my chair. Oh well, I think it was a class 4. Getting a class 10 card tomorrow.

You'd have to hit up Adrynalyne for a kernel update.
Havent seen him around for months.
I won't be using ext4 for my ROM. Perhaps someone else who develops a ROM for the Zio may, but I just dont have the time right now, and the Zio is pretty maxed out as it is with all the work we've done on it thusfar.
A better more viable option would be to get someone to build CM6 for you all, so the zio can somewhat stay on the learning curve. This phone is getting a touch old with all the newer cricket phones that are coming on the market now. Unfortunately I dont (and havent) seen any new devs capable of producing CM6 hit the forums with a zio lately... But, you never know..
Good Luck!

I'll be getting my laptop back soon... And I need something to do on the free time to keep up on Linux, so I might just try building CM6 for the Zio.
Sent from my Kyocera Zio M6000 using XDA Premium App

Cool cool.
I have been pretty busy with my car and work
Mostly tho it's procrastination
Sent from my Zio using XDA App

[Q] ext4 to rfs file formate

I was just wanted to make sure i did this the right way to change from ext4 to rfs file formate is just disable voodo lagfix and then flash cwm and thats it.Anybody please correct me if I'm wrong .

Yep, by disabling voodoo u'll go back to rfs but imo the cwm flash after that was unnecessary.

Thanks alot i thought that was right i wanted to make sure before I flashed a new rom I need to be on rfs for the rom I'm gonna flash.
Sent from my SAMSUNG-SGH-I897 using xda premium

I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.

OwenW71 said:
I'm in the same boat, running Cog5v2 w/ CWM 4.0.4. How do I verify that the file system is now RFS?
edit:
Pulled up terminal and ran 'mount'. Filesystem is still EXT4. The 'disable-lagfix' trick did no good.
Click to expand...
Click to collapse
Did you reboot?
Sent from my SAMSUNG-SGH-I897 using XDA App

Yep, then checked mount in terminal. The Cognition kernel did not use Voodoo, so the 'disable-lagfix' is not going to get the job done, I think.

That is a beta kernel, from what I remember it had trouble converting back to rfs from ext4. You'll have to flash back to a "stock" firmware with either a 1 click or using a .pit along with the firmware .tar with Odin/heimdall to repartition your file system.

Yikes. Since I'm stuck on EXT4, will my TiBu data backups be any good once I'm up and running on RFS?

Doesn't matter, your backup is fine.

1. Another easy way is to download the "voodoo control app" from the market. It will let you toggle rfs / ext4 from there and reports on current file system.
If I am not mistaken, this portion of the app is free..........but it is worth buying if you do a lot of ext4 stuff.
If you are on a GB ROM from KH3 on, ext4 is kind of unecessary, since rfs makes no difference in "laggy-ness"

Cognition 5 isn't voodoo. I don't remember if you can change it on CWM. Check in CWM if there is an option to switch to rfs or disable lag fix, if not you need to use ODIN back to "stock". Doesn't matter wich leaked firmware you use.

+1
FOR COGNITION:
prbassplayer is correct
See here http://forum.xda-developers.com/showpost.php?p=16664289&postcount=2818
You have to go back to stock.

Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.

prbassplayer said:
Voodoo app won't work on Cognition 5's kernel. The paid app is for Voodoo sound implementation.
Click to expand...
Click to collapse
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.

chappatti said:
Absolutely agreed. see my post above.
But on GB ROMs voodoo app works great for ext4 etc. I have the paid app and it works all the time.
Click to expand...
Click to collapse
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...

studacris said:
Why do you need an app for voodoo rfs/ext4 conversion?
All it does, therefor all you have to do, is make a file (or folder doesn't matter) in the voodoo folder of your sdcard named disable-lagfix then reboot.
To re-enable simply delete that file and reboot...
Click to expand...
Click to collapse
Well, I am lazy..... And first timers can be comfortable !

Also its in CWM anyways. I have paid for sound, so I have control over conversions on it. But as Studa said it isn't needed.