Hey guys,
i thinking about using f2fs on Nokia X
I format /data and /cache as f2fs and changed values in fstab.qcom and its work and it 2x faster than ext4 !
But i have one question, can anyone port recovery like twrp, cwm and philz with f2fs support
because in philz recovery /data and /cache not accessible
Related
hi all,
i know how to format IN YOUR ROM to ext4 but i am building a ROM and i used the Stock Rom that is in Rfs FS , how do i format to ext4 ? i use PX-Kernel 3
thank you
EDIT: btw is it normal that when i exract the boot.img i dont get a Ramdisk ?
And again , no answer...
I suggest you tar the contents of the RFS /system partition, reboot into recovery, format /system to ext4 and extract the contents of your tarball.
For those who don't know what is f2fs, please search in the google.
After long time of testing, researching, etc, I managed to get my stock KK to use f2fs in /system and /cache partition.
But /data partition no matter what flags i tried to edit fstab.qcom to get it to use f2fs, device will get into bootloop.
So now the f2fs is not in its full potential.
I give up to make f2fs work in /data partition in stock KK.....very tired.
LG stock maybe have hardcoded some parameters about /data partition, so f2fs don't work.
This usage of f2fs in /system and /cache in stock KK, required to use my new F2FS kernel(which build-in a modified fstab.qcom and fstab.geefhd) and my new twrp(with the ability to format partition to f2fs).
But i am not sure if i will share them, as the benefits of using f2fs in /system and /cache is so little.
Who will want it actually?
Prerequisite is a device with stock KK with 4.1.2 bootloader.
Wing
mukwing said:
For those who don't know what is f2fs, please search in the google.
After long time of testing, researching, etc, I managed to get my stock KK to use f2fs in /system and /cache partition.
But /data partition no matter what flags i tried to edit fstab.qcom to get it to use f2fs, device will get into bootloop.
So now the f2fs is not in its full potential.
I give up to make f2fs work in /data partition in stock KK.....very tired.
LG stock maybe have hardcoded some parameters about /data partition, so f2fs don't work.
This usage of f2fs in /system and /cache in stock KK, required to use my new F2FS kernel(which build-in a modified fstab.qcom and fstab.geefhd) and my new twrp(with the ability to format partition to f2fs).
But i am not sure if i will share them, as the benefits of using f2fs in /system and /cache is so little.
Who will want it actually?
Prerequisite is a device with stock KK with 4.1.2 bootloader.
Wing
Click to expand...
Click to collapse
Hi,
I was looking around and saw someone mention that TWRP would format /data and skip /data/media could you check on that.
If it works please do tell.
How did you put the 4.1.2 bootloader on a KitKat F240L?
I had that until i got an update from LG OTA and it replaced my CWM with stock bootloader.
Forget about this old post.
I have successfully used f2fs on /system /cache and /data on cm rom with modified kernel and rom.
(I decided not to share it. Because i shift back to stock rom as the benefit of using f2fs is not much on our phone) )
Just not sucessfully use f2fs on stock rom.
For keeping 4.1.2 bootloader on KK, first, flash back to kdz version of 4.1.2(then your bootloader will be 4.1.2), then use flashable zip method to upgrade to KK, thus your 4.1.2 bootloader will not be touched. If using kdz method to upgrade to KK, you will be using KK bootloader, which is troublesome.
Btw, it is no way using f2fs on /data without format the /data/media also, they are on one partition!
Wing
Hey guys,
i modify recovery and kernel to work with f2fs
- Recovery is Philz recovery with NULL kernel
- Kernel have modified fstab to mount f2fs partitions
I don't own the kernel, Kernel has been compiled by mdfzhi.
I only changed mountpoints and some bugs to get it work.
But it have modified fstab:
- cache is mounted in /dev/block/mmcblk0p25 as F2FS
- preload is mounted in /dev/block/mmcblk0p19 as EXT4
- data is mounted in /dev/block/mmcblk0p22 as F2FS
I switched it because f2fs require at least 200MB partition and cache have only about 100MB and preload about 300MB. - It will boost performance
Requirements:
- Nokia X
- installed system (like CM11, PAC etc.)
Installation:
0, THIS WILL CLEAR YOUR USERDATA AND CACHE, not SDCARD
1, download zip and unpack it
2, flash kernel and recovery with fastboot dont use flashify it will brick your phone
3, boot into recovery, it will get some errors like /data and /cache wont mount - just ignore this, it will work later
4, connect your phone to pc
5, run formater.bat or formater.sh - we must format this from pc because is ext4, after this is complete you can format data and cache from recovery (f2fs)
6, reboot and enjoy
If you found any bugs, tell me
This mod work in custom rom based on android 4.1.2?
Burnmode said:
This mod work in custom rom based on android 4.1.2?
Click to expand...
Click to collapse
I havent tested it on 4.1.2, it may work, just try it
I flashed data/system/cache to f2fs and the rom boots but gets stuck at the beginning, with all kinds of com.android.phone and system ui crashes.
Anyone know how to make f2fs work on cm13?
Skwerl23 said:
I flashed data/system/cache to f2fs and the rom boots but gets stuck at the beginning, with all kinds of com.android.phone and system ui crashes.
Anyone know how to make f2fs work on cm13?
Click to expand...
Click to collapse
You have to flash agni kernel it supports f2fs but i advise you stay away from f2fs as it corrupts data. Use f2fs only if you are sure.
Sent from my GT-N7100 using Tapatalk
Stick with original Format. Ext2
Sent from my Xiaomi Mi 5 using XDA Labs
harishdayanand said:
Stick with original Format. Ext2
Sent from my Xiaomi Mi 5 using XDA Labs
Click to expand...
Click to collapse
Ext2, No..... ext4 is better
Skwerl23 said:
I flashed data/system/cache to f2fs and the rom boots but gets stuck at the beginning, with all kinds of com.android.phone and system ui crashes.
Anyone know how to make f2fs work on cm13?
Click to expand...
Click to collapse
Else if you want to use f2fs, you must have a ROM who can boot with a good fstab to mount partition in f2fs format!!!!
I have made my rom with F2FS on cache partition (cannot format data ATM with my old recovery, it failed, i must update it).
Code:
#test f2fs
[B][I][COLOR="Red"]/dev/block/platform/dw_mmc/by-name/CACHE /cache f2fs noatime,nosuid,nodev wait[/COLOR][/I][/B]
#/dev/block/platform/dw_mmc/by-name/CACHE /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
#test f2fs
/dev/block/platform/dw_mmc/by-name/USERDATA /data f2fs noatime,nosuid,nodev wait
/dev/block/platform/dw_mmc/by-name/USERDATA /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check
/dev/block/platform/dw_mmc/by-name/HIDDEN /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
If you want i can share my rom for you to try.....?
Bizcuite
Which filesystem is used for /data and /cache by latest OxygenOS (Nougat based)?
If I have formatted these 2 partitions as f2fs do I need to change them to ext4 before flashing latest Oxygen_4.1.3.zip in TWRP?
Just f2fs on data for OOS
rg_gapa said:
Which filesystem is used for /data and /cache by latest OxygenOS (Nougat based)?
If I have formatted these 2 partitions as f2fs do I need to change them to ext4 before flashing latest Oxygen_4.1.3.zip in TWRP?
Click to expand...
Click to collapse
I would stay on ext4 there is no real difference only in really big application. Also don't encrypt your device since it can take up to 10 minutes to boot in TWRP when encrypted on F2fs! Also it is not stable yet.
FYI: Currently I'm using data as f2fs and cache as ext4 - that's how OOS 4 works by default.