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
Related
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 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
I see my favourite glitch kernel have f2fs support.
How can i convert stock 5.1.1 rom to f2fs?
Recovery?
Using F2FS for the system partition isn't really interesting imo, and as you encountered can be annoying if your rom installation script forces EXT4. I suggest you to try formatting DATA and CACHE partitions as F2FS (make sure to backup your whole internal storage if needed) using the latest TWRP recovery. Remember to reflash Glitch kernel after that (using MTP in recovery to get back your whole internal SD data) so your device can boot (as the kernel package will detect partitions at flash time). Good luck !
Tnx, will try.
On N7 2012 and 4.4 android this tool was good for me.
How did this work out? Is it worth doing?
Hi all, I tried to search every posts in the thread of wilson3q's unofficial build cm12.1, to see if the rom supports f2fs since I really love this rom. But I only found 1 post asking without answer. So may I ask is this rom supports f2fs for system, cache, and data?
Below were what I have done before but failed.
1. Flash AGNi pureCM kernel and reboot back to TWRP 2.8.7.0
2. Flash zips provided in the thread of AGNi pureCM kernel to turn my N7105's system, data and cache from ext4 into f2fs
3. Flash latest build of wilson3q's unofficial build cm12.1, then wipe cache/davik cache
4. Flash AGNi pureCM kernel again, then wipe cache/davik cache
5. Flash Open Gapps, then wipe cache/davik cache
After all these, I noticed the System partition is back to ext4 again, is this means wilson3q's unofficial build cm12.1 doesn't support f2fs? In addition, the rom loops in CM boot logo if the Data and Cache continue to be f2fs. Everything gets fine again if I change all the partition back to ext4.
Can anyone help?
erictrixis said:
Hi all, I tried to search every posts in the thread of wilson3q's unofficial build cm12.1, to see if the rom supports f2fs since I really love this rom. But I only found 1 post asking without answer. So may I ask is this rom supports f2fs for system, cache, and data?
Below were what I have done before but failed.
1. Flash AGNi pureCM kernel and reboot back to TWRP 2.8.7.0
2. Flash zips provided in the thread of AGNi pureCM kernel to turn my N7105's system, data and cache from ext4 into f2fs
3. Flash latest build of wilson3q's unofficial build cm12.1, then wipe cache/davik cache
4. Flash AGNi pureCM kernel again, then wipe cache/davik cache
5. Flash Open Gapps, then wipe cache/davik cache
After all these, I noticed the System partition is back to ext4 again, is this means wilson3q's unofficial build cm12.1 doesn't support f2fs? In addition, the rom loops in CM boot logo if the Data and Cache continue to be f2fs. Everything gets fine again if I change all the partition back to ext4.
Can anyone help?
Click to expand...
Click to collapse
In TWRP there is a setting to use "rm -f" instead of formatting. If you make sure this is on before flashing the ROM it might work. I remember doing this some years ago.
Installing the ROM usually formats /system as ext4 but that setting just wipes all files (shouldn't be any as you formatted to f2fs) and so keeps the old file system (f2fs) rather than formats the new (ext4).
This worked for me on my N7100 using Agni kernel (had f2fs support). In the end I stopped using f2fs since my phone would have the "sleep of death" so I had to pull the battery. Eventually this lead to massive corruptions of the file system on /data and I lost everything.
I read somewhere that f2fs speed advantage is not that great on read only partitions such as /system.
Anyway, that's my experience, it's up to you what you do now. Hopefully my advice works in your N7105.
Sent from my GT-N7100 using Tapatalk
DarrenNewsgroup said:
In TWRP there is a setting to use "rm -f" instead of formatting. If you make sure this is on before flashing the ROM it might work. I remember doing this some years ago.
Installing the ROM usually formats /system as ext4 but that setting just wipes all files (shouldn't be any as you formatted to f2fs) and so keeps the old file system (f2fs) rather than formats the new (ext4).
This worked for me on my N7100 using Agni kernel (had f2fs support). In the end I stopped using f2fs since my phone would have the "sleep of death" so I had to pull the battery. Eventually this lead to massive corruptions of the file system on /data and I lost everything.
I read somewhere that f2fs speed advantage is not that great on read only partitions such as /system.
Anyway, that's my experience, it's up to you what you do now. Hopefully my advice works in your N7105.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thank you so much! I will try that when I get back to home!
Hello, I would like to know which are the correct partitions to change the file system to F2FS. Can I flash to cache, cache and dalvik, system, data, internal storage? Or could you please indicate me which the correct partitions to change the file system to F2FS. The rom stock are compatible with that F2FS file system? I think that from recovery (twrp latest version) it is possible to change the F2FS file system of the partition, thank for you help.
Note:my phone model is LG g3 d851
F2FS on stock requires a compatible kernel and modded ramdisk (fstab), btw you can format data and cache (correct partitions) to F2FS but your phone won't boot.
Loller79 said:
F2FS on stock requires a compatible kernel and modded ramdisk (fstab), btw you can format data and cache (correct partitions) to F2FS but your phone won't boot.
Click to expand...
Click to collapse
Hello,
Could you please tell me that I must modify of the ramdisk (fstab) to avoid problems of bootloop. I have read in several sites that brings advantages in writing data to modify the System and data partition. Thank for you answer.