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
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
Ok, so I finally found and settled on a kernel with f2fs support. The Simplicity 1.1 kernel for my stock, but modified 5.1.1 TW system. I've tried to follow the guides out there on how to convert the /data and /cache partitions to f2fs. I've followed them to the T and every time I reboot, it comes up saying the data partition is damaged and gives me the option to reset the phone, so I always end up rebooting to recovery and converting back and restoring from my nandroid backup and all is well. I hate being defeated and want to give this a shot, so if anyone has successfully done it or has any advice, it would be truly be appreciated! Thank you all for your time
Chuck
Which recovery you use to format to f2fs
Hi earlier in the month I installed the soak test and for some reason my data partition changed to ext4 now I understand that this may not be visible but if there's any dev out there working on our moto g4s could possibly compile a twrp recovery with F2Fs support thanks.