Database Info

F2FS FOR EVITA ANY AOSP ROM

F2FS FOR EVITA ANY AOSP ROM
F2FS for EVITA
AOSP only!
Current CM or most any of our AOSP ROMs around here that use a current CM based kernel.
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 2.7.1.0 KK version
F2FS capable TWRP Recovery 2.8.5.0 KK versionThis is the same as the current official TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Kernel+fstab conversion zip Flash this after converting partitions to F2FS to install a CM kernel with F2FS support built in. This zip uses an anykernel installer so it should be comparable with most current ROMS. The zip will extract your current boot.img, unpack and replace your current fstab with a new fstab to indicate you current partition types, replace kernel with F2FS capable kernel , then repack and replace the boot.img
Fstab conversion zip 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, 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/Evita-f2fs
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 recovery img.
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 change partition type. Convert to F2FS. Repeat for cache.
6. Flash the Kernel+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
2. Flash kernel+fstab conversion zip.
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.
Code:
CHANGELOG
V1.0 - Initial release
V1.1 - added inline_data flag to F2FS mounts
V1.2 - updated to latest kernel/fstab as of 8/9
V2.0 - updated for cm-12.0
Source:
Kernel: https://github.com/jrior001/android_kernel_htc_msm8960/tree/cm-11.0-f2fs
Recovery tree: https://github.com/jrior001/twrp-htc-evita/tree/cm-12.0
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.
XDA:DevDB Information
F2FS EVITA, Kernel for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/jrior001/f2fs_fstab_convert_script
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-07-08
Created 2014-07-09
Last Updated 2015-02-26

Links and Instructions are now up. As promised, F2FS support is now possible for /data and /cache on Evita. For now there is no support for converting /system to F2FS as most have said it does not show significant gains because there is far less writing to /system partition. Also, as of now the only way to support converting /system would require specific ROMs built specifically for F2FS on system. As I have done it here we remain flexible to flash any regular nightly and still enjoy the gains of F2FS on /data and /cache. Follow instructions carefully and enjoy.

If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps

pandasa123 said:
If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps
Click to expand...
Click to collapse
I've been following some other devices trials and tribulations with f2fs. Most other places I'm seeing dev convert the partitions in the device trees fstab. This results in a fixed f2fs or fixed ext4 ROM. As a dev that means building 2 ROMs which is a time waster.
With these fstab scripts I modded from the grouper forums I was able to make basically any aosp ROM adaptable to f2fs or ext4 for data and cache. I have included this same script work and the needed f2fs tools into the torched installer as well as the f2fs conversion zips.
Pandasa123 I have posted all the source in the f2fs thread. You really only need the kernel commits and the f2fs capable recovery along with my scripts. You could also build a fixed f2fs ROM if you chose and I have commits on my github and on CM gerrit to use as examples for that as well. I have also pushed kernel commits to CM gerreit in hopes that intervigil will merge them to make this a lot simpler but I highly doubt that will happen.

@pandasa123, little more info...
If you look through my fstab zip scripts you'll find that they check the partitions for filesystem type, unpack the boot.img and the edit the fstab accordingly for f2fs or ext4 with all the proper mount flags and then repack the boot.img.
This seemed to me to be an easy way for any user to get their feet wet on f2fs and it takes the extra work away from the devs having to cook duplicate roms. Flash any current ROM, then flash the conversion zip to get your fstab proper based on whatever partition format you are currently on.
There is also a movement on liquid smooth to incorporate this type of conversion script into the ROM zip but its still a huge wip.

Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita

timmaaa said:
Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita
Click to expand...
Click to collapse
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).

I haven't yet, I'm a stay at home dad to a seven week old little girl so I struggle to find the time to even flash a ROM recently. If I get some free time (that's a fairly big if) I'll definitely test it out. It's a real shame about his Ville, I think he got really unlucky and his PC thermalled and rebooted on him during the hboot change. Pretty sure he's getting it jtagged though.
Sent from my Evita

jrior001 said:
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).
Click to expand...
Click to collapse
I will test and report back with benchmarks shortly.

EXT4 vs F2FS benchmarks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These were done on the same ROM (PA 4.42 stock kernel, then PA 4.42 F2FS evita kernel), followed instructions exactly, rebooted and re-ran the benchmark several times with approximately the same results. Benchmarks were performed on the /data partition. Not sure why SQLite performance took such a hit...

sephiroth2k said:
Click to expand...
Click to collapse
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.

jrior001 said:
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.
Click to expand...
Click to collapse
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there

sephiroth2k said:
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there
Click to expand...
Click to collapse
Its off in Evita source as well. Appreciate the effort and I will look more at that commit as well.

I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Hope these questions are ok and thank you for all that you've done for our devices. This F2FS change is one of the most noticeable performance increases I've seen on my Evita and it's been my daily driver since AT&T released it back in 2012. Are there any benchmarks that you'd like me to run or any questions I might be able to answer for you on my usage/experience? If so, I may have to ask for detailed instructions if there's something I haven't needed to do before with android (still learning).

budroid said:
I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
Click to expand...
Click to collapse
That's bid difference I saw as well, apps install and load a bit quicker.
budroid said:
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Click to expand...
Click to collapse
If you ran a backup of your old ext4 /data partition and attempt to restore it, TWRP will restore it exactly as it was, in ext4. Lable your backups yo make it easier on yourself!! Twrp will restore in the same format as it was when backed up. Make sure you run the fstab script afterwards or you will bootloop while it fails to load /data.
budroid said:
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Click to expand...
Click to collapse
Yes but it will replace your kernel with a basic CM kernel w/f2fs support. If you want to run torched you made the right choice using the fstab only.
EDIT: Torched Installer includes the conversion script as well now.
budroid said:
Hope these questions are ok and thank you for all that you've done for our devices.
Click to expand...
Click to collapse
Great questions!! And your welcome, I've learned tons messing with this over the last 2 years

Flashed torched instead of Evita f2fs and speeds are much better.

sephiroth2k said:
Flashed torched instead of Evita f2fs and speeds are much better.
Click to expand...
Click to collapse
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita

timmaaa said:
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita
Click to expand...
Click to collapse
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.

sephiroth2k said:
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.
Click to expand...
Click to collapse
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita

timmaaa said:
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita
Click to expand...
Click to collapse
No problem - difference is incredible - apps install and open much faster, everything seems smoother (this is subjective of course). Thanks @jrior001 for breathing new life into my aging evita :highfive:

[HOW TO] CONVERT any ROM to F2FS format

NOTE:As i have already moved on to the S6 edge, the amount of support that i can provide would be minimal
THIS IS COMPATIBLE WITH ALL VARIANTS OF THE NOTE 3.
Firstly f2fs can only be used with f2fs compatible KERNEL'S and if you brick your device,Its just because you didnt read and follow the instructions listed from this part of the OP.
Before we start,I would like to thank @psycho4us4 who had allowed me to start a guide thread on the Note3 Forums on f2fs based on his thread from the Note2 http://forum.xda-developers.com/note-2-tmobile/development/how-to-conversion-t2853975
Kernel's with full f2fs support>System,Cache,Data
-Lean Kernel http://forum.xda-developers.com/showthread.php?t=2488082
(Tested)​
-Shinto kernel.
http://forum.xda-developers.com/showthread.php?t=2895089
(Tested)
Feel free to inform me on kernels which have full support with all 3 partitions mentioned
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTRUCTIONS FOR CONVERSION OF EXT4 TO F2FS
1.Make sure you have the latest TWRP Recovery on your device(V2.8.1.0 Should be good to go) Get it here> http://teamw.in/project/twrp2
2.In the { Settings } menu of TWRP make sure the [ Use rm -rf instead of formatting ] is unchecked MAKE A FULL, COMPLETE BACKUP with TWRP 2.8.1.0 ( I can't stress this enough if you don't want to use Odin). Keeping in mind that whatever format your partitions are is what format they will be backed up as, such as EXT2, EXT3, EXT4, FAT, F2FS, etc. This will wipe INTERNAL SD so please make a backup of it to your EXT SD CARD/EXTERNAL MEMORY DRIVE.
3. Next from TWRP home, select { WIPE }
4. Then select { ADVANCED WIPE }
5. Then select { CACHE } and click { REPAIR OR CHANGE FILE SYSTEM }
6. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
7. Now select { SYSTEM } and click { REPAIR OR CHANGE FILE SYSTEM }
8. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
9. Then select { DATA } and click { REPAIR OR CHANGE FILE SYSTEM }
10. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
11. Next from TWRP home, click { Settings } then { X } the box that says [ Use rm -rf instead of formatting ].
12. Hit the back button, then select { Restore }. Click on the package you want to restore ( this is the backup you made in step #2 )'
13. Next { X } the boxes { CACHE, SYSTEM, and DATA ONLY }. Then SWIPE TO RESTORE.
14. ALL DONE now just click { Reboot System }
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Just in case you have a problem and you needed to convert back to EXT4,Here is how you do it
INSTRUCTIONS FOR CONVERSION FROM F2FS TO EXT4
1. If you don't already have a backup that you want to use ( backed up with the [ Use rm -rf instead of formatting ] UNCHECKED ) then make one using Step 2 from above instructions.
2. Follow steps 2 through 14 from above, the only thing you have to do different is, instead of choosing { F2FS } for the file format you can choose ANY of the options available as long as the KERNEL you are running supports the format you are switching to.
3. That"s it
3a. If you already have a backup done with the format you desire all you have to do is make sure the [ Use rm -rf instead of formatting ] option is UNCHECKED then restore the { CACHE } AND { SYSTEM } partitions from the package you desire that was made in the format you desire.
3b. The { DATA } has to be done manually by following steps 3, 4, 9, 10 but then hit the back button till your at the TWRP home screen. Next do step 11. Then restore the { DATA } partition from the same backup as mentioned in step 3a.
3c. Reboot and done!​
--------------------------------------------------------------------------------------------------------------------------------​

sorry to ask that but what's the interest of that manipulation??????

rayman95 said:
sorry to ask that but what's the interest of that manipulation??????
Click to expand...
Click to collapse
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Great. Thanks for the guide. I'm sure you note 3 users will love this.

Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...

adario73 said:
Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...
Click to expand...
Click to collapse
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.

psycho4us4 said:
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.
Click to expand...
Click to collapse
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !

adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua

psycho4us4 said:
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua
Click to expand...
Click to collapse
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Hit me on hangouts.
[email protected]

Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3

adario73 said:
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3
Click to expand...
Click to collapse
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
you are making me VEEEERY curious !
the variant i have is HLTE N9005

adario73 said:
you are making me VEEEERY curious !
the variant i have is HLTE N9005
Click to expand...
Click to collapse
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4

adario73 said:
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4
Click to expand...
Click to collapse
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )

adario73 said:
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )
Click to expand...
Click to collapse
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

Ianchua said:
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3

adario73 said:
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3
Click to expand...
Click to collapse
Okay. Try this once more,
Try Conerting the System to f2fs first than convert the rest there after.
Reboot to recovery after doing all this
For the restore part. Restore System,cache and data separately with reboot to recovery in between.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌

F2FS for ACE(CM12/LP AOSP ONLY)

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

[TOOL]TWRP-F2FS[M7UL]

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?

[all variant]F2FS[2017/07/08]

Some infos about F2FS
History of F2FS
F2FS ( flash-friendly file system ) means «flash adapted system file », was created by Kim Jaegeuk (Hangul: 김재극), intended and oriented to NAND flash memories. It is a file system structured in log.
It was integrated into the version 3.8 of Linux kernel. (February 19, 2013).
Is F2FS better than Ext4 ?
F2FS reading speed is relatively equivalent to the original ext4 Android format, but you might notice an improvement in overall fluidity thanks to the huge writing speed improvement.
Trim is automatic with F2FS, which is not the case on ext4.
F2FS features
Multi-head logging
Multi-level hash table for directory entries
Static/Dynamic hot and cold data separation
Adaptive logging scheme
Configurable operational units
Dual checkpoint
Roll-back and roll-forward recovery
Heap-style block allocation
TRIM/FITRIM support
Online fs defragmentation/file defragmentation
Inline xattrs/data/dir
Offline filesystem check (Check and fix inconsistency)
Atomic operations
Filesystem-level encryption
Offline resizing
Inner periodically data flush
Extent cache
Installation
-Note you need to use our unofficial lineage (https://forum.xda-developers.com/xperia-e3/orig-development/lineage-os-2017-06-11-t3627728) and our boot-twrp or boot-twrp-root.img.
You have to install Lineage before starting, and you must boot it at least once.
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then "Change or Repair File System"
Change File System
Choose F2FS and slide to confirm
Now go back to advanced wipe and repeat the previous three steps for cache
Reboot your phone
How to come back to ext4 ?
You want to come back to ext4, or just install a new rom ?
You just need to follow the installation that we have detailed earlier, but choose ext4 instead of F2FS

reserved

Thanks @infus38 @rmnhg and all the other Dev who has contributed in Bringing This Awesome Thing (F2FS) To Our Phone

Ali Haide 001 said:
Thanks @infus38
For Bringing This Awesome Thing (F2FS) To Our Phone
Click to expand...
Click to collapse
Thank all the lineage realization not just me

infus38 said:
Thank all the lineage realization not just me
Click to expand...
Click to collapse
Sorry i forgot
And Don't worry I will Thank Everyone

In future it will be present in more ROMs

rmnhg said:
In future it will be present in more ROMs
Click to expand...
Click to collapse
Thank you and congratulations for becoming senior member

rmnhg said:
In future it will be present in more ROMs
Click to expand...
Click to collapse
Yep

Ｄｈｒｕｖ said:
Thank you and congratulations for becoming senior member
Click to expand...
Click to collapse
Thanks @dhruv

Congrats @rmnhg (ramon) on becoming Senior Member
Thank you @rmnhg (Ramon) and @infus38 (Thomas) for The Lineage And Of Course F2FS:victory: