Hello folks,
Well, we all know that the stock Moto G filesystem is F2FS. But surprisingly, the Moto G GPe has a native Ext4 support. Since F2FS is supposed to have about a 30% better performance, I decided to try out the convert to F2FS feature in Philz recovery. So I formatted my system and cache to F2FS (since it didn't give me an option to wipe data and data/media to convert) and flashed a ROM. Currently, I seem to be facing a bootloop.
Anyway, has anyone else tried something like this? If yes, then please share your experience here.
Cheers.
It would be great if that would be possible,then you could jump from retail stock to GPe more easly. I have an XT1032 stock rom and i'd really like GPe,but my concerns are that would i be able to stock XT1032 again from GPe? You know,for F2FS and if i wanted to flash custom roms again to have better support. Any thoughts on my question? And look the first post,this is really interesting since if you'd want custom roms and you are on GPe,you wouldnt need to flash stock ROM to avoid bugs with custom roms and GPe
TWRP also include a format to f2fs <-> ext4 option:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
http://teamw.in/project/twrp2
Wipe > Advanced Wipe > <Select Partition> > Repair or Change File System > Change File System
I will test this out tomorrow when I have some time.
U need a kernel support somewhat like this in nexus 5 for f2fs
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Stock kernel supports f2fs, GPE kernel does not. Development of a GPE kernel that supported f2fs would be ideal, assuming the GPE stock ROM also functions correctly with a f2fs formated USERDATA partition.
Has anyone even tried to flash boot.img from stock,and then converting in philz?
DeHuMaNiZeD said:
Has anyone even tried to flash boot.img from stock,and then converting in philz?
Click to expand...
Click to collapse
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
lost101 said:
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
Click to expand...
Click to collapse
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Sent from my Moto G using XDA Premium 4 mobile app
Using TWRP to reformat 'data' from f2fs to ext4 wipes SDCARD and didn't even change the format. Right now it appears if you plan on moving between GPE and non-GPE and possibly back again, keep a full firmware image for both.
EDIT: Actually it appears TWRP did format correctly. But the GPE kernel can't get past the Bootloader. Perhaps there are other partition table differences.
After another try..the following works fine.
Migrate to GPE:
1) In TWRP, wipe, and format 'Data' from f2fs to ext4 (this will wipe internal storage.)
2) Sideload / adb push GPE ROM or flash ROM and Kernel via fastboot.
3) Reboot
Return to Motorola Stock:
1) In TWRP, wipe, and format 'Data' from ext4 to f2fs (this will wipe internal storage.)
2) Sideload / adb push Stock ROM or flash ROM and Kernel via fastboot.
3) Reboot
rudi_j7 said:
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Click to expand...
Click to collapse
I re-read your OP. The GPE Kernel expects the 'userdata' partition to be ext4. Unless someone develops a custom kernel to support it; you will never be able to run the GPE ROM with an f2fs 'userdata.'
Because you set all partitions to F2FS. Only need to change /data to F2FS. Leave system and cache ext4. You would need a ROM with a patched fstab and then a kernel supporting f2fs for system and cache to be in F2FS as well. Plus major benefit is in /data, not system and cache. I tested full F2FS on my N4 and it was more a pain with less gain. /data is all that should be F2FS.
Sent from my Moto G using Tapatalk
You can get it by deleting the partition / data and change it later by f2fs with TWRP fastboot erase boot partition and flash the boot.img from the stock 4.4.4 rom motorola everything from GPE and I have it so it shows more fluid
OP updated with the twrp odin repack from yuga.
- based on TWRP 2850 for yuga
- changed TWRP splash curtain
- adddd F2FS binary from olivier
http://www.mediafire.com/download/38gxejrk6v3yrxe/TWRP285v4.img
WARNING! THIS WILL WIPE YOUR DATA PARTITION (INTERNAL SCDARD). MAKE SURE YOU HAVE A BACKUP BEFORE PROCEEDING!
Click to expand...
Click to collapse
Hope this helps, guide on how to convert /CACHE and /DATA to F2FS partitions. I've tried this before on my Nexus7 2012, and F2FS improves benchmark scores. Same behavior happened on my ZL, it improved benchmark from 21k to 26k!
Requirements:
1. ROM / Kernel that supports F2FS. I've tried this on CM12 build 03/12 and CM12 build 03/15, F2FS works ok. I believe this has been merged to CM since Mar builds.
2. mkfs.f2fs binary. Credits to Olivier for this. I grabbed his MultiROM TWRP for ODIN, unpack and grabbed the mkfs.f2fs binary. Unpack regular TWRP for ODIN and copied over the mkfs.f2fs binary, repack and flashed it on the FOTA partition.
3. Unlocked bootloader. Since we will be using custom ROM / kernel that supports F2FS, we need to have unlocked bootloader, or else it will result to softbrick. Hopefully when Sony releases Android5, hoping that their stock kernel supports F2FS so that no need to unlock bootloader.
Steps: (pics included for reference)
1. Make sure you are on modified TWRP with the mkfs.f2fs binary. If you dont want to unpack / repack, use the MultiROM TWRP.
2. Select Advanced > Terminal Command.
3. Start on /system/bin (optional).
4. Enter the command to format /cache to F2FS
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/cache
Click to expand...
Click to collapse
5. Enter the command to format /data to F2FS
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
6. Reboot recovery to refresh / reread the partitions. This step is very IMPORTANT!
7. If you have custom TWRP themes, it will revert back to plain TWRP, due to /data partition being formatted to F2FS.
8. Go to Wipe > Advanced Wipe.
9. Select Cache >Repair or Change Filesystem
10. It will show that /cache partition is now on f2fs filesystem.
11. Repeat step 9, select Data > repair or Change Filesystem. It will show /data partition is now on f2fs filesystem.
ADDED NOTE : I've also tried to format /system partition to F2FS, it formats it successful, but upon flashing the CM12 ROM, it reverts back to EXT4. I beleive this behavior happens because the system.img is in EXT4 format. This will be next project soon to complete ALL F2FS - /system /data / cache on F2FS partitions.
WARNING! THIS WILL WIPE YOUR DATA PARTITION (INTERNAL SCDARD). MAKE SURE YOU HAVE A BACKUP BEFORE PROCEEDING!
Click to expand...
Click to collapse
BIG THANKS to OLIVIER for the MultiROM TWRP and of course to CM12 for implementing F2FS.
How could I know that currently running kernel indeed runs F2FS?
ryanrudolf said:
Hope this helps, guide on how to convert /CACHE and /DATA to F2FS partitions. I've tried this before on my Nexus7 2012, and F2FS improves benchmark scores. Same behavior happened on my ZL, it improved benchmark from 21k to 26k!
Requirements:
1. ROM / Kernel that supports F2FS. I've tried this on CM12 build 03/12 and CM12 build 03/15, F2FS works ok. I believe this has been merged to CM since Mar builds.
2. mkfs.f2fs binary. Credits to Olivier for this. I grabbed his MultiROM TWRP for ODIN, unpack and grabbed the mkfs.f2fs binary. Unpack regular TWRP for ODIN and copied over the mkfs.f2fs binary, repack and flashed it on the FOTA partition.
3. Unlocked bootloader. Since we will be using custom ROM / kernel that supports F2FS, we need to have unlocked bootloader, or else it will result to softbrick. Hopefully when Sony releases Android5, hoping that their stock kernel supports F2FS so that no need to unlock bootloader.
Steps: (pics included for reference)
1. Make sure you are on modified TWRP with the mkfs.f2fs binary. If you dont want to unpack / repack, use the MultiROM TWRP.
2. Select Advanced > Terminal Command.
3. Start on /system/bin (optional).
4. Enter the command to format /cache to F2FS
5. Enter the command to format /data to F2FS
6. Reboot recovery to refresh / reread the partitions. This step is very IMPORTANT!
7. If you have custom TWRP themes, it will revert back to plain TWRP, due to /data partition being formatted to F2FS.
8. Go to Wipe > Advanced Wipe.
9. Select Cache >Repair or Change Filesystem
10. It will show that /cache partition is now on f2fs filesystem.
11. Repeat step 9, select Data > repair or Change Filesystem. It will show /data partition is now on f2fs filesystem.
ADDED NOTE : I've also tried to format /system partition to F2FS, it formats it successful, but upon flashing the CM12 ROM, it reverts back to EXT4. I beleive this behavior happens because the system.img is in EXT4 format. This will be next project soon to complete ALL F2FS - /system /data / cache on F2FS partitions.
BIG THANKS to OLIVIER for the MultiROM TWRP and of course to CM12 for implementing F2FS.
Click to expand...
Click to collapse
Sweet! I would love to see this on my Z2. It does wonders for my Nexus 10!
Would be nice if you attached mkfs.f2fs here in this thread.
phhuang said:
How could I know that currently running kernel indeed runs F2FS?
Click to expand...
Click to collapse
if you are running a fusion3 based device (z, zr, zl, tablet z, tablet z wifi) with a nightly or a recent build direct from source, it supports f2fs. i merged support for it directly into cm12 on the first of march.
thanks QSNC youre the man! still figuring out how to set /system to F2FS.
mkfs.f2fs binary
I attached mkfs.f2fs binary which is compiled from https://github.com/CyanogenMod/android_external_f2fs-tools
Thanks! Then I guess my Z1 could just pass it by now...
It says
Code:
/system/bin/mkfs.f2fs: line 1: syntax error: unexpected "("
-------------EDIT
I got it working using this, although I had to set the permissions to 755 after pushing via adb.
ADDED NOTE : I've also tried to format /system partition to F2FS, it formats it successful, but upon flashing the CM12 ROM, it reverts back to EXT4. I beleive this behavior happens because the system.img is in EXT4 format. This will be next project soon to complete ALL F2FS - /system /data / cache on F2FS partitions.
I think it is becuase of the block-based zip-filesfrom lollipop. The zip file flashes a filesystem directly instead of mounting /system and copying the system files to this patition.
i forgot to add, im using official TWRP 2.8.5.0 for Yuga (Xperia Z), i just repack it to use build.prop of ZL and included the mkfs.f2fs binary from MultiROM TWRP.
qsnc said:
if you are running a fusion3 based device (z, zr, zl, tablet z, tablet z wifi) with a nightly or a recent build direct from source, it supports f2fs. i merged support for it directly into cm12 on the first of march.
Click to expand...
Click to collapse
the merges u made, its only for fusion3 or its already also on CM12 z1, z2, z3 devices?
Good looks on this! Gonna be following this thread.
Can't you format using TWRP GUI?
After I tried it TWRP won't mount the new partitions. Not after reboot either. Z1 compact, TWRP 2.8.4.0 with mkfs.f2fs repack.
Edit: Seems like stock CM12 @ Z1c don't support f2fs yet. I've successfully formatted cache through terminal in TWRP, but when booting I get bootloop. And TWRP still won't mount it.
arunsai123 said:
I attached mkfs.f2fs binary which is compiled from https://github.com/CyanogenMod/android_external_f2fs-tools
Click to expand...
Click to collapse
Your compile is much bigger than any other mkfs.f2fs out there. (Most is 166kb uncompressed). Why is that?
Quick update -
I flashed my ZL with latest unofficial nightly build of Shufuking. It is based on CM12.1 / Android 5.1. F2FS still works, im running /cache and /data as F2FS.
Your guide is a bit complicated - actually, you can just flash a TWRP build of mine (http://olivier.hubdroid.com/yuga/twrp/) and switch to F2FS, without having to download a separate binary etc:
Go to Wipe > Advanced Wipe > select the desired partition > Repair or change filesystem > Change filesystem > f2fs
@Olivier
i tried your build fof odin, in this link http://olivier.hubdroid.com/odin/twrp/
but it won't boot. once i flash to fota and reboot, cyanogen recovery boots up. i tried every nightly build but it wont boot. i also tried the yuga builds for my odin same behavior. hope you csn create for odin, i'llbe happy to be tester for it.
OP updated with the twrp odin repack from yuga.
- based on TWRP 2850 for yuga
- changed TWRP splash curtain
- adddd F2FS binary from olivier
http://www.mediafire.com/download/38gxejrk6v3yrxe/TWRP285v4.img
ryanrudolf said:
@Olivier
i tried your build fof odin, in this link http://olivier.hubdroid.com/odin/twrp/
but it won't boot. once i flash to fota and reboot, cyanogen recovery boots up. i tried every nightly build but it wont boot. i also tried the yuga builds for my odin same behavior. hope you csn create for odin, i'llbe happy to be tester for it.
OP updated with the twrp odin repack from yuga.
- based on TWRP 2850 for yuga
- changed TWRP splash curtain
- adddd F2FS binary from olivier
http://www.mediafire.com/download/38gxejrk6v3yrxe/TWRP285v4.img
Click to expand...
Click to collapse
Logs. I need logs. If everything else fails, flash this hack too.
@Olivier
hack works! it now boots to TWRP 2860! i suppose if we flash new CM 12.1 nightly, we have to flash the hack again? thanks very much!
EDIT:
i reflashed original CM12.1 boot.img and same behavior happened, TWRP wont boot, it goes to cyanogen recovery. unpack / repack CM12.1 boot.img and replace the elf ram disk from your hack, it now works ok! am i correct the hack only replaces the elf ram disk?
I have converted my Nexus 7(grouper) to all f2fs and flashed slimlp. How do I convert it Ext4 file system and flash CM 12 Nightlies.?
I believe it's the same way you converted to F2FS, but this time select "EXT4" and not "F2FS".
I thought of doing that, but better get to know from someone who has done that before.
Flashing factory image restored to ext4.. That is safest method to do this.
After you convert everything back ext4, you can convert the data and cache back to f2fs because the nightlies in cm12 support this. You just need to leave the system partition as ext4 since this isn't supported yet.
Yup, I have seen those options, but didn't convert it to F2FS.I am giving my tab to my brother and he is not interested in flashing and all, but before giving I wanted to try baton(I have a one plus one), that's why I have flashed CM12.1. I was unable to get baton work.
I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!
Up
Most probably as the official one from twrp supports f2fs natively.
I would recommend to go back to official twrp convert to f2fs properly from there and then flash the modified one, do this if you are brave enough, i havent tried this method but it should work. If all fails stay on ext4 till garak or twrp updates their twrp versions.
Thanks for you answer... I thought the same... I'll try as the new phone will come and let you know...
IlD4nX said:
I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!
Click to expand...
Click to collapse
I got the same error for my Redmi Note 3 ... tried 3.0.0.0, 3.0.2.2, but nothing. then a guy suggested this:
https://www.androidfilehost.com/?fid=24591000424943818
and it worked. Now I can't boot on f2fs, just trying to make it work on 6.0.1 Mokee rom