Totally experimental.. ATM this is basically a "proof of concept" for proper F2FS support.
Please, don't take risks if you are not sure you're doing... This can totally erase your system, data, etc... (make a full backup before, etc...)
I've sucessfully tested formatting /cache and /data to F2FS. This should work on any Shield Tablet model (properly updated, at least MM).
Downloads:
Latest TWRP with F2FS support available here.
Kernel with proper F2FS support like BitO-K8 and BitO-K10 / KX10 for N
F2FS fstab injection tool (to replace fstab.tn8 in current ramdisk) for M (updated version for N here)
Instructions:
Flash TWRP (via fastboot, rashr, o r similar if rooted ) and boot into recovery
Advanced Wipe, select partition (data, cache), and select change FS to F2FS
Flash compatible Kernel zip from TWRP
Flash F2FS injection tool (this replaces fstab.tn8 in ramdisk with an updated version with F2FS support)
Reboot
WARNING NOTES:
If you format /system with F2FS, you'll need to reflash your ROM (ROM bust support install in F2FS /system WITHOUT re-format to EXT4...) (TESTED, not working ATM with standard restore from TWRP)
If you format /data you need to restore a backup (previous in TWRp...), or reconfigure your whole system (TESTED)
You can safely format /cache to F2FS following instructions (TESTED)
Ok data and cache is f2fs for stock 1.3 system won't boot on f2fs
skooter32 said:
Ok data and cache is f2fs for stock 1.3 system won't boot on f2fs
Click to expand...
Click to collapse
Do you mean you've tested successfully /cache and /data in F2FS but you got error with /system ? Thx
BitOBSessiOn said:
Do you mean you've tested successfully /cache and /data in F2FS but you got error with /system ? Thx
Click to expand...
Click to collapse
Yes cache and data is at f2fs but when system is f2fs it don't go by Nvidia sign and switches off
skooter32 said:
Yes cache and data is at f2fs but when system is f2fs it don't go by Nvidia sign and switches off
Click to expand...
Click to collapse
Ok, that's right, tested... thx ! Only /cache and /data with F2FS atm...
BitOBSessiOn said:
Ok, that's right, tested... thx ! Only /cache and /data with F2FS atm...
Click to expand...
Click to collapse
Great work tho Bit0 was gonna say tho about this Linux kernel flaw cow or whatever are u gonna be patching ur kernel with the coding?
Twrp screenshots
skooter32 said:
Yes cache and data is at f2fs but when system is f2fs it don't go by Nvidia sign and switches off
Click to expand...
Click to collapse
Nice work Bit & co!
From what I've seen, there's no benefit to f2fs on /system because in normal operation it is read-only and f2fs improves more the write performance.
Awesome work Bit! I found a couple fix it's to make your TWRP work flawlessly. First your fstab file has an incomplete line, I've been testing with this attached fstab for the recovery successfully if you want to take a look. you can also copy it into the ect folder as recovery.fstab, your twrp.fstab is perfect. I also had to modify my boot.img with the same fstab.tn8. The only way I was able to get /system /data /cache to all format and boot was to re-install a rom with this edited into the updater script.
#--INFORMATION
ui_print(" "); ui_print("INSTALLING f2fs ROM STARTED");
#--PREPARE DEVICE PARTITIONS
ui_print("-- Preparing device partitions");
package_extract_dir("META-INF/SCRIPTS", "/tmp");
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/CAC", "/cache");
run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");
run_program("/sbin/fsck.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/CAC", "/cache");
run_program("/sbin/mount", "-t", "f2fs", "/system");
run_program("/sbin/mount", "-t", "f2fs", "/data");
run_program("/sbin/mount", "-t", "f2fs", "/cache");
delete_recursive("/system");
ui_print("-- Wiping all user data files");
set_metadata("/tmp/wipe.sh", "uid", 0, "gid", 0, "mode", 0777);
run_program("/tmp/wipe.sh");
#--INSTALLATION
ui_print("-- Extracting system & data");
your kernel and fsf2 utils are perfect, with out your tremendous effort f2fs would still only be an far off idea, congrats and we did it!
@BitOBSessiOn since you're the man, I was wondering if you could replicate some of the features of http://forum.xda-developers.com/oneplus-one/development/lightning-kernel-omni-rom-v01-t3245895
into your kernel for us. with minimal changes from https://github.com/nikhil18/lightning-kernel-bacon do you think you could add some of the features? with minimal changes I think you could add the governors to your kernel and the optimizations
Does this work on stock? I'm gonna try it out anyway, but yeah...
Yup, it works on stock.
Latest kernel with full F2FS support (BitO-K8) and tool for fstab.tn8 updating:
http://forum.xda-developers.com/showthread.php?p=69718234
TWRP MultiROM+F2FS v3.0.2 (008)
Available here.
BitOBSessiOn : I take it with a version of the K8 (kx8) can use on / cache / data and / system as well?
this work on shield tablet k1?
k3wlar said:
BitOBSessiOn : I take it with a version of the K8 (kx8) can use on / cache / data and / system as well?
Click to expand...
Click to collapse
/system depends on specific ROM (it doesn't work on stock), but usually you only get a performance boost with /data and maybe /cache.
sarmentoedu said:
this work on shield tablet k1?
Click to expand...
Click to collapse
Yes, it should.
Twrp 3.0.3 (20121220)
TWRP 3.0.3 (MROM modded) available here.
For those who are using F2FS, do you still experience the occasional and annoying lagging with your shield tablet? Thanks in advance
TWRP 3.0.3-1 (20170118) (F2FS support updated)
Latest TWRP 3.0.3-1 with F2FS (updated) support available here.
It's recommended to use one kernel with also updated F2FS support, like BitO-KE8-003.
EDIT: F2FS format option fixed. Link updated
Related
This recovery & patch allow installation of AOSP based ROM (CyanogenMod/OpenDesire/DeFrost) with partition sizes set to match that of Nexus One.
No more need for Apps2SD hacks!
It is very easy to install, however requires security to be disabled on your device (S-OFF in FASTBOOT).
Steps to install:
1. Download AOSP Based ROM to your SD card.
2. Download nexified-boot-patch-v1.0.0-bravo.zip to your SD card.
3. Reboot in Fastboot
4. Fastboot flash recovery nexified-recovery-clockwork-2.5.0.7-bravo.img
5. Reboot into recovery
6. Wipe data/factory reset
7. Flash ROM
8. Flash nexified-boot-patch-v1.0.0-bravo.zip
9. Reboot & Enjoy
Both the recovery, and the boot patch, have kernel cmdline:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
The patch also removes "dalvik.vm.dexopt-data-only=1" from build.prop which places dalvik-cache on the cache partition as per AOSP.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Warnings:
Do not flash radio via recovery, only via fastboot. You should not be flashing radio via recovery anyway, it is strongly discouraged.
Credits:
AlphaRev - for bringing S-OFF to HTC Desire
Firerat - for the original mtd patch which I learned a lot from.
Lbcoder - for the initial information on how to modify partitions via kernel commands, i learned a lot from him as well.
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Kali- for porting CM6 to Desire thanks a bunch
I am doing this to try and spark further interest in this, in the hopes that other developers may improve on it, as the default partition sizes on the desire are crap.
How to uninstall / set partitions back to normal:
Boot into Fastboot
Fastboot flash standard/unmodified clockwork recovery or amon_ra
Reboot into recovery
Wipe data/factory reset
Flash ROM & Reboot
Downloads:
nexified-recovery-clockwork-2.5.0.7-bravo.img
nexified-boot-patch-v1.0.0-bravo.zip
Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
nice work.....
back in a flash
xtcislove said:
Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
Click to expand...
Click to collapse
No, the partition sizes are passed as kernel parameters, so recovery & ROM must be patched to use the same parameters.
so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works
Well done!
Very brave of you to almost brick your device (twice?) and continue development nonetheless.
I don't need it, but many others will love this. Thanks a lot.
If I follow your procedure am I stuck on nightly-132, or once i've got the resized partitions can I continue to flash CM6 nighlites?
These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?
great works on my Desire..Thanks daedelus82 and other persons...I see 197 Mb on available space..
Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?
Great Work! I hope this becomes the norm, we need that /system space for apps.
Excellent! At last! Thank you very much!
aleksei87 said:
Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?
Click to expand...
Click to collapse
Hello, yes I will patch CM6.0.2 stable as well. I have to go to work now but within a few hours. I will also try to answer other questions but have to run right now.
Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
marinierb said:
These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?
Click to expand...
Click to collapse
Yes, boot.img for ROM, and recovery.img for recovery
djind said:
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?
Click to expand...
Click to collapse
Sorry I have patched CM and Clockwork Recovery only.
ieftm said:
Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Only breaks fastboot flashing of system and/or userdata, as fastboot will flash it to different blocks than the kernel is using. All other partition locations/blocks are unmodified meaning flashing of recovery, boot, and radio will be fine.. Also if you flash userdata, system, and boot all at same time it will also work, as overwriting boot will remove the kernel cmdline.
Would love to see a HBOOT implementation of this that does not require kernel modifications.
cgrec92 said:
so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works
Click to expand...
Click to collapse
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Thanks very much for this, I'll be flashing it shortly. I have two questions if you don't mind!
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data? (just for the love of god make it a multiple of 16 or my OCD will break the universe)
Updated OP. Added CM6 stable v6.0.2
nawoa said:
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data?
Click to expand...
Click to collapse
You can patch system and cache to whatever sizes you want, it really depends on your ROM. If you have less than 96MB in your system partition then partitioning it to 96MB should be fine. I normally like to leave a few MB spare for good measure. See below for description on flashing radio from a re-partitioned recovery.
ezterry said:
Same steps as the rom, just ensure you *never* flash *any* spl or radio for any reason from a re-partitioned recovery with a cache partition that does not match the spl's actual cache start location. Or you will be in the market for a jtag adapter to fix your brick.
Click to expand...
Click to collapse
ieftm said:
There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Thx !! we are waiting for that ;-)
Hmm... Because of the radio flashing issue and because I use DT-A2SD anyway, I think I'm going to hold off on using this until there's the HBOOT solution you guys are talking about.
Crossing my fingers that all I need to do is install standard clockwork recovery then go to a standard CM build.
******************* INFO&CREDITS *******************
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button
Downloads
********************************************************* Downloads *********************************************************
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch
Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.
Do you run into any issue with this f2fs so far?
LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5
Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go
CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.
delete please
sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is for use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab according to your current partitions and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new TWRP recovery img if you are not already on it.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
This is a personal build of TWRP with F2FS support(proper way) based off 2.8.1.0 branch from Omnirom(recovery) which I butchered and added F2FS..
This was tested with CM11 way back last year..I just posted it for the heck of sharing it since I have not seen the same idea/achievement here on M7 forums..and seems this phone needs a "refresh"(in a good way)..
Now whats F2FS?? Googling can give you trivial INFO yet you can start your way here
This file system developed by Samsung lean towards a less noisier, less workloads, and a faster throughput File System that can substitute EXT4 in the near future(they already use it)..extensively if you rely heavy on Benchmarks it has been put to the test by some Devs here on XDA like this one
Now enough with the chit-chat..on this TWRP build I only converted /DATA as F2FS..now you might be wondering why?? Answer is because its the most actively used partition on your phone..System apps use it to store settings/info/etc...Framework uses it too for caching and storage...Extensively your Apps(the ones you install) use it as well..so theres completely no point converting the whole phone to F2FS which in the latter can just cause you more issues when you want to return to stock..
This only works on AOSP based ROMs(i tried it on CM11) though you'll need a kernel with F2FS support baked in for things to work properly.. (Who wants me to build one? I know for sure you don't..)
DO NOT TRY ON SENSE(You have been warned) Tried it once well it boots up(Proper F2FS kernel is required) but you'll end up on a security windows and you might not get out if it..OR you may be able to boot it up but you cannot install apps(happened to me twice and no Dice on installing anything)..well you're free to play with it so who knows who might get a lucky pick on getting this working on HTC Sense ROM's, but for now I'll safely say/advise to use on AOSP ROMS only..
Download here
**I won't be liable for any damage on your phone..you are on your own here..
**This project does not come with a warranty..
XDA:DevDB Information
Recovery with F2FS, Tool/Utility for the HTC One
Contributors
kairi_zeroblade
Version Information
Status: Stable
Stable Release Date: 2015-02-05
Created 2015-02-05
Last Updated 2015-02-05
Reserved
Why not? It's time to update your aosp kernel production mate!
Sounds great
For your Sense-Problem: it does boot, right? So it shouls work but HTC implemented some nasty **** to block your phone when using F2FS. So there has to be some code for checking the filesystem and then launching the "block-app". Removing the abvoe mentioned code would give the Sense users the opportunity to use it to.
Maybe you this can help you
@kairi_zeroblade when you say AOSP roms only, does that rule out GPE because CM12 is very buggy
Does this recovery tested on CM12 and derivative ROM's?
:good:
Hi,
I'm trying to use f2fs on my m7. The fstab from the kernel looks like that:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,noatime,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
/dev/block/platform/msm_sdcc.1/by-name/radio /firmware/mdm vfat ro,fmask=0000,dmask=0000,shortname=lower,context=u:object_r:firmware_file:s0 wait
/dev/block/platform/msm_sdcc.1/by-name/adsp /firmware/q6 vfat ro,fmask=0000,dmask=0000,shortname=lower,context=u:object_r:firmware_file:s0 wait
# USB storage
/devices/platform/msm_hsusb_host/usb* auto auto defaults voldmanaged=usbdisk:auto
The rom I try to boot on with cache on f2fs, system and data still ext4 is the one linked here
Any hint what's the problem/what part doesn't support it properly?
L
Info
Is encrypted sdcard compatible with F2FS file system?
I'm using your recovery now with AICP 8, the f2fs parts are working fine, but everytime I tried to format back to ext4, I needed another twrp version from either the official site or MDMower.
And the second thing I found was, the recovery always tells me it didn't found a few files (theme related things).
Would it be possible to update the f2fs twrp to version 2.8.5.6 from here?
L
Edit: I mixed together the 2.8.5.6 unofficial with the kernel and ramdisk from @kairi_zeroblade 's f2fs version. Up to now it seems to work fine. The f2fs paritons get mounted and backup is working also. Flash an upadate or restore isn't tested yet. And what I also can't test, if it works for ext4 (or also f2fs) people who use encryption. Could that be tested by someone please?
Link: openrecovery-twrp-2.8.5.6-m7-materialised-F2FS.img
Hi there,
here's an update to version 2.8.6.1
openrecovery-twrp-2.8.6.1-m7-materialised-F2FS.img
L
Info
I want to test last version.
Which partition can i convert in F2FS?
Is needed kernel support?
ultrasound1991 said:
I want to test last version.
Which partition can i convert in F2FS?
Is needed kernel support?
Click to expand...
Click to collapse
most roms only support data & cache for f2fs and you will need a compatible kernel for f2fs. I won't say i tried every rom out there but AICP & Vanir support f2fs very well. You could theoretically install any rom for f2fs is you had a third party kernel out there that was compatible... and I'm not sure if there are any right now (i think AGK is going to get it soon though)
qkall said:
most roms only support data & cache for f2fs and you will need a compatible kernel for f2fs. I won't say i tried every rom out there but AICP & Vanir support f2fs very well. You could theoretically install any rom for f2fs is you had a third party kernel out there that was compatible... and I'm not sure if there are any right now (i think AGK is going to get it soon though)
Click to expand...
Click to collapse
Ok, i want to try.
I will convert system,data and cache to f2fs.
Does my rom is full compatible if it start normally?
ultrasound1991 said:
Ok, i want to try.
I will convert system,data and cache to f2fs.
Does my rom is full compatible if it start normally?
Click to expand...
Click to collapse
no system will not work but data and cache will!
qkall said:
no system will not work but data and cache will!
Click to expand...
Click to collapse
Ok, but does system will work in next version? Or in future?
ultrasound1991 said:
Ok, but does system will work in next version? Or in future?
Click to expand...
Click to collapse
Honestly, I don't know... but I would assume it would eventually be a feature but I'm not knowledgeable to know.
here's a tutorial for properly settings up f2fs though
I sort of recommend using Vanir though - a faster experience.
qkall said:
Honestly, I don't know... but I would assume it would eventually be a feature but I'm not knowledgeable to know.
here's a tutorial for properly settings up f2fs though
I sort of recommend using Vanir though - a faster experience.
Click to expand...
Click to collapse
I want XenonHD or AICP, or a ROM that will be updated over Lollipop in future.
ultrasound1991 said:
I want XenonHD or AICP, or a ROM that will be updated over Lollipop in future.
Click to expand...
Click to collapse
I can't speak for XenonHD but AICP and Vanir are incredibly active (vanir not so much on m7 xda forums but the google plus page is good)
edit- i just checked... it doesn't look like XenonHD has f2fs support yet... but if you had a third party kernel that would work (which again i don't think there are any atm).
qkall said:
I can't speak for XenonHD but AICP and Vanir are incredibly active (vanir not so much on m7 xda forums but the google plus page is good)
edit- i just checked... it doesn't look like XenonHD has f2fs support yet... but if you had a third party kernel that would work (which again i don't think there are any atm).
Click to expand...
Click to collapse
Now i'm downloading AICP 8 ROM, AGK AOSP 1.7 Kernel and twrp 2.8.6.1 f2fs materialised (Isn't there normal themed?).
---------- Post added at 09:05 PM ---------- Previous post was at 08:58 PM ----------
9Lukas5 said:
Hi there,
here's an update to version 2.8.6.1
openrecovery-twrp-2.8.6.1-m7-materialised-F2FS.img
L
Click to expand...
Click to collapse
Is this update your or of kairi_zeroblade?
My brother has got a POCO F1 and, he wanted to format his userdata and cache partitions like me (Mi 6 user here, AEX Pie + Vantom Kernel) to F2FS on his POCO.
What I've tried (and succeeded) is, adding the lines from my fstab file to his fstab.
Here's the steps we've followed:
- We've installed 9.1.24 Global Developer fastboot firmware by using the MiFlashTool (because AEX 6.3's flashable zip gave an error and told us to update to that version in the output).
- Then we've installed OrangeFox 9.0.1 as it also supports F2FS.
- Then I've got that fstab file, added the 2 lines for userdata and cache into it for F2FS, from my fstab (same android versions and kind of identical partition tables like my Mi 6 so, we tried - and succeeded, please follow).
- Then we've formatted the userdata and cache partitions to F2FS in the recovery.
- Then we've flashed AEX 6.3, Sphinx Kernel (looks nice, I may get some ideas from that) and the flashable* (see the attachments, alongside the original fstab from that version) "FSTAB-EXT4&F2FS-encryptable=footer-BERYLLIUM.zip" that I've made for the fstab.
- Then the GApps (particularly, OpenGapps Nano variant) and the other stuff like fonts etc (not important to specify but meh).
Then the system booted just fine, we've tried everything we could imagine to test and it seems working totally fine.
* Because of I was just lazy (lol) and used that old ass ZipMe app to create the flashables below, before flashing them you have to mount Vendor partition from the Mount screen of the OrangeFox/TWRP to get the the new fstab file written successfully.
> Also note that because of the POCO lacks a proper encryption method on F2FS (just like my Mi 6) your userdata partition will remain unencrypted by using this fstab file.
> For any reasons if you'd want to have your original fstab file back (even though this new one would work just fine for default EXT4 too), you can use the other flashable that I've attached below.
I hope this would be helpful for anybody so sharing the steps and ideas.
I think the same idea could be applicable to the combinations of other kernels that support F2FS and (I don't know, if anybody tries it please tell in the comments) even for MIUI (with a kernel that supports both F2FS and MIUI of course).
If you have any questions or suggestions, (preferably) tell in the comments or if you really want, you can also send pm for various reasons.
I hope that support for F2FS gets improved over time so everybody gets to use it on their devices lol, it's the healthy decision for the flash based storages (check the up to date documentations before starting a flame war or I'll ignore your ignorance - I'm just trying to help here and I feel bad for having to state this here explicitly, on my own behalf).
Note that, I'm not responsible for any possible damages/data losses to your phone (you know the drill here at XDA)/thermonuclear war or whatever; so please use your own brain and make your preliminary research and take precautions before trying anything that you aren't familiar with. Thanks.
Did you tried MIUI + Sphinx + F2FS?
Does official twrp support f2fs for poco
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
can i install this on stock miui 10.2.2.0 with custom extreme kernel???
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
Adriano-A3 said:
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Click to expand...
Click to collapse
How did you establish FSTAB EXT4 that works for you?
IronRUS said:
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
How did you establish FSTAB EXT4 that works for you?
Click to expand...
Click to collapse
mount | grep f2fs
Is it possible to modify system to boot f2fs also?? Thanks in advance
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well as i know ,you simply can't, every ROM installation will re-format /system to ext4 automatically
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
You can check the filesystem in Android by some apps like DiskInfo
The system cannot be f2fs since most roms target an ext4 /system partition when installing, so it would always format the system partition to ext4. Eventhough you can backup and restore all of its data once you convert, it would be formated back to ext4 the next time you flash anyway
Jole7 said:
Is it possible to modify system to boot f2fs also?? Thanks in advance
Click to expand...
Click to collapse
It's useless. F2FS is good to random write. /system is entirely read-only.
I will try to make it for system partition as an experiment
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
pipyakas said:
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
Click to expand...
Click to collapse
Performance "degradation" because of formatting data to F2FS? Nope.
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well, your filesystem is itself is the one that's "under the hood". You may notice faster system bootups, app launches and also some in app responsiveness improvements if a particular app is constantly trying to access the storage to record "random" stuff into it's databases.
For system, nope as the others explained before me. I think that it's enough for cache and userdata partitions.
Rommco05 said:
Will attached files works also for Mi8?
Click to expand...
Click to collapse
I don't know, compare the mount points in your current fstab file. If they're similar to F1's then you may try what I've done here.
Dan_Jacques said:
Did you tried MIUI + Sphinx + F2FS?
Click to expand...
Click to collapse
Nope, we stay away from that crap xd but you can try if you wish.
thanhnvt194 said:
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
Click to expand...
Click to collapse
Yes. As long as the mount points stay the same, you can continue to use it.