Database Info

[MOD][S-OFF] AOSP Based ROM Custom MTD Partitions Nexus One - Easy Flash/Patch

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.

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:

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

[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:

Enable F2FS for USERDATA & CACHE

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.