This is a simple .zip file you can flash on any amami, which uses a ramdisk like the combinedrootfs from Cyanogenmod 11. Your device needs to have a f2fs-compatible kernel, for example this one.
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your system, data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
Ok but... what is f2fs?
It is a new file system, which is especially designed for flash-based storages, like our phones. It will give you much better reading and writing speed.
Installation:
1. Be sure, that you have a f2fs-compatible kernel and your ramdisk's structure is similar to Cyanogenmod's one. If you are on any aosp-based rom, the ramdisk will be compatible anyway.
2. Flash the .zip file from a custom recovery
3. Reboot recovery
4. Now go to advanced wipe and you can change the file systems of system, data and cache to f2fs.
Some more information:
If you convert cache to f2fs:
->No data will be lost
If you convert data to f2fs:
->Your whole internal storage will be wiped. backup your data before you decide to do that!
If you convert system to f2fs
->You need to flash your rom again. You need to modify the updater script of your rom before that like this
OK. I formatted data with f2fs, but want to flash a new rom. What to do?
You need to flash a kernel with f2fs and this zip, no need for any wipes
Download:
http://www.androidfilehost.com/?fid=23578570567713678
For Developers:
You can include this in your rom like this: https://gist.github.com/CoolDevelopment/54ede52a1e075da48151
XDA:DevDB Information
F2FS for amami, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, NovaFusion
Version Information
Status: Testing
Current Beta Version: 2.0
Beta Release Date: 2014-07-16
Created 2014-07-16
Last Updated 2014-07-16
@CoolDevelopment
So, if I corectly understand this zip will erase all data including internal storage? Am I right? But about if I use nightlies? Will I neen to flash it every time after update?
da900 said:
this zip will erase all data including internal storage?
Click to expand...
Click to collapse
It won´t erase your internal storage , I flashed and everthing is there !
pvillasuso said:
It won´t erase your internal storage , I flashed and everthing is there !
Click to expand...
Click to collapse
OK. Thanx. But will erase all data, so I need to install all apps again?
da900 said:
OK. Thanx. But will erase all data, so I need to install all apps again?
Click to expand...
Click to collapse
Nope , it won´t erase any data, files, apps, etc from your internal o external storage
from the OP :
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
CoolDevelopment said:
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
Click to expand...
Click to collapse
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
da900 said:
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
Click to expand...
Click to collapse
You need to flash a f2fs compatiblr kernel and this zip, no wipes
But if you don't do that your rom will bootloop
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
New version!
I uploaded a new version with /system support and a few fixes.
I also updated the op.
Have fun!
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
idimitro said:
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
Click to expand...
Click to collapse
Every rom flashes a boot.img. This boot.img contains a zImage and a ramdisk(on sony devices it is a bit more complicated but that's enough for now).
Using f2fs needs:
1. A zImage(kernel) with f2fs support
2. A ramdisk with f2fs support
This zip modifies the ramdisk for compatibility with f2fs.
You need to flash a f2fs kernel manually.(for example my moshkernel)
And everytime you flash a new rom, you have to modify the contents of the boot.img again
And why don't I just let you flash a modified boot.img? It is only one file.
It would only be compatible with one rom. This is compatible with any rom and boot.img, which uses the ramdisk architecture like cyanogenmod(combinedrootfs).
I hope I could explain it well
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
najar360 said:
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
Click to expand...
Click to collapse
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
CoolDevelopment said:
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
Click to expand...
Click to collapse
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
najar360 said:
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
Click to expand...
Click to collapse
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
CoolDevelopment said:
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
Click to expand...
Click to collapse
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
najar360 said:
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
Click to expand...
Click to collapse
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
CoolDevelopment said:
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
Click to expand...
Click to collapse
yeaps. i'm using 0.1.2 version.
najar360 said:
yeaps. i'm using 0.1.2 version.
Click to expand...
Click to collapse
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
CoolDevelopment said:
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
Click to expand...
Click to collapse
is my step correct?
edit : try slimkat and it work.
Hi,
I use a Stock 5.1.1 Android Rom on my S6 Edge LDU with some selfmade modifications (Debloat, Kernel Upgrades etc.).
Flashed a new Kernel (F2FS compatible) but my Rom seem's to be not compatible with F2FS because it get's always stuck on Boot Loop.
I tryed the following way:
Create a Flashable Zip -> http://forum.xda-developers.com/showthread.php?t=2746044
And converted it to F2FS -> http://forum.xda-developers.com/galaxy-s2-plus/development/linux-ext-to-f2fs-rom-converter-t2840303/page2
...but i always get the Device not Compatible error...
Is there anyway to Convert my TWRP Backup to a F2FS compatible format ?
Thanks
http://forum.xda-developers.com/showthread.php?p=55476692
Sent from my SM-G920W8 using Tapatalk
As far as I know, probably not. F2fs is a type of flash file system, you can format partitions with this type of file system which would be specific to that partition. Because when you back up from twrp, the backup isn't in a particular flash file system format, it's not a partition to be able to convert it plus going from one flash file system to another completely wipes the that partition.
Sent from my SM-G920F using XDA-Developers mobile app
Yeah, I wasn't really sure what the point was. The backup's an archive of files, and making it a flashable zip doesn't make it a ROM. Files will restore to whichever FS is on the device.
Sent from my SM-G920W8 using Tapatalk
Hello, any gus can help me ? I'm using sutlan's cm 13 on my one plus one ,and I want to change the filesystem to f2fs, but I don't know because each time I tried it turned to be ext4 again and again. What a sad story it is . And this is my operation steps following:
Recovery : the official twrp recovery 3.0.2
ROM : sultan's cm 13 from XDA
1. Boot into recovery - advanced wipe -choose system - transfer filesystem type -choose f2fs ,and then data partition as well .
2.flash ROM.
3.reboot and the filesystem turns to be ext4 back.
So ,I just wandering how should I do ? Any body knows please give me some help . I'll be appreciated .
Sultan's ROM only supports F2FS on /data and /cache.
Sent from my A0001 using Tapatalk
I'm currently on AOSPExtended ROM(7.1.1) with it's stock kernel. I recently heard about f2fs system which is more faster and has increased life span of flash storage than current ext4 system.
Now I want to know whether this ROM and kernel are f2fs compatible, and how can I change my partitions to f2fs in detail without loosing my current data.
Thank you.
in previous iterations of android, only data partition was allowed to be in F2FS format (by default data partition is in F2FS format unless you have a GPE device). all the rest should be in ext4. some kernels allow cache to be in F2FS thats all. you can format some partitions to F2FS via TWRP recovery. however if any F2FS partition is unsupported you will endup in a bootloop.
Hi
How to format data and cache partitions in ext4, it's seem to be solution for installing PixelExperience for who are stuck on bootlogo ?
system is ext4
data is f2fs
cache is ext4
Do not change or you will have boot problems.
KrisM22 said:
system is ext4
data is f2fs
cache is ext4
Do not change or you will have boot problems.
Click to expand...
Click to collapse
Why i'm stuck only on pixel experience, i don't understand
fix the format of those to what I said above and all will be well. if not, nope!
KrisM22 said:
fix the format of those to what I said above and all will be well. if not, nope!
Click to expand...
Click to collapse
Fix?... How to?
Sent from my Moto Z2 Play using XDA Labs
Format &/or fix you can into twrp - wipe, adv.wipe, select partition...
All Android phones I met had ext4 support inbuilt, sometimes you need format data(unencrypt) when it ask about password.