I own a Motorola DROID TURBO (XT1254) with unlocked bootloader and the Stock ROM /data and /cache partitions are in f2fs filesystem and /system is in ext4 filesystem and I have some doubts and questions:
1. Some Custom ROM's like LineageOS on this device can be installed with /data and /cache partitions formatted in ext4 and f2fs, In your daily Stock or Custom ROM in which filesystem are formated the /data, /cache and /system partitions?
2. I read that the f2fs filesystem are used by Motorola on Stock ROM's due to notable higher write speeds (this helped to the Nexus 7 2012 owners, because has eMMC bug) but has more chances of data corruption (in some devices exists the garbage collection problem), and ext4 is more reliable for data and has higher read speeds. What are you experience with ex4 and f2fs filesystems on Android? and in Moto Maxx/DROID TURBO, which is better for you?
3. Apart for Motorola, Samsung create the f2fs filesystem but not use it in their devices, Huawei uses f2fs filesystem since Android 7.0 Nougat/EMUI 5.0, OnePlus tried it on OnePlus 3/3T, but in OnePlus 5/5T switched back to ext4. Google says "F2FS isn’t supported for the internal storage as it doesn’t support inline hardware encryption", and Android 7.0 Nougat and higher supports Direct Boot and file-based encryption but only in ext4 filesystem. A website says that the Motorola Moto Z (an other Motorola device) are faster than Google Pixel (XL?), because the Moto Z uses f2fs filesystem.
4. It would be good to share the used filesystem in your phone and in which ROM uses this filesystem.
Note: Can you check partitions filesystem with Diskinfo app or TWRP in Wipe> Choose partition> Repair or change filesystem
This information and questions apply for all Moto Maxx/DROID TURBO owners (XT1225, XT1250, XT1254)
I like to know your opinions about the ext4 and f2fs filesystems for Moto Maxx/DROID TURBO
In case of necessity, I post it also in DROID TURBO sub-forum
No one replied here?
lat94084 said:
No one replied here?
Click to expand...
Click to collapse
This was very hotly debated three years ago, in late 2014 and early 2015 -- mostly dealing with the XT1225. You can probably dig up old threads over in the Droid Turbo forum where it was discussed. (We were all in one forum back then. It was the "All Quark" forum.) The forums were split in September 2015, but some of the threads never got moved. Droid Turbo finally got bootloader unlock in November 2015, thanks to Sunshine, but by then the topic was no longer being discussed.
There was some reason why the topic was dropped and everyone just went with the default system. Maybe didn't work well with TWRP backups or something about encrypting? Also, there was false low storage warnings. I don't remember. I just remember it was too much hassle so everyone didn't bother.
ChazzMatt said:
This was very hotly debated three years ago, in late 2014 and early 2015 -- mostly dealing with the XT1225. You can probably dig up old threads over in the Droid Turbo forum where it was discussed. (We were all in one forum back then. It was the "All Quark" forum.) The forums were split in September 2015, but some of the threads never got moved. Droid Turbo finally got bootloader unlock in November 2015, thanks to Sunshine, but by then the topic was no longer being discussed.
There was some reason why the topic was dropped and everyone just went with the default system. Maybe didn't work well with TWRP backups or something about encrypting? Also, there was false low storage warnings. I don't remember. I just remember it was too much hassle so everyone didn't bother.
Click to expand...
Click to collapse
The DROID TURBO I own have unlocked bootloader thanks to Sunshine (is a little expensive, but is worth it), I asking about ext4 or f2fs as filesystem for /data partition, the DROID TURBO Stock ROM is the /data partition formatted as f2fs, but the majority of Android devices the /data partition is formatted as ext4 and some questions and comparation between both filesystems for /data partition
Three questions: ¿The /data partition of your phone is formatted now as ext4 or f2fs?, ¿The encryption is working on both filesystems or only one (ext4 or f2fs)? and ¿Your phone is in the Stock ROM formatted the /data partition as ext4 or f2fs?
I published this in DROID TURBO forum, but no one replied here.
lat94084 said:
The DROID TURBO I own have unlocked bootloader thanks to Sunshine (is a little expensive, but is worth it), I asking about ext4 or f2fs as filesystem for /data partition, the DROID TURBO Stock ROM is the /data partition formatted as f2fs, but the majority of Android devices the /data partition is formatted as ext4 and some questions and comparation between both filesystems for /data partition
Three questions: ¿The /data partition of your phone is formatted now as ext4 or f2fs?, ¿The encryption is working on both filesystems or only one (ext4 or f2fs)? and ¿Your phone is in the Stock ROM formatted the /data partition as ext4 or f2fs?
I published this in DROID TURBO forum, but no one replied here.
Click to expand...
Click to collapse
I don't use encryption on mine or my wife's phone. My phone is formatted however TWRP formatted it. @bhb27 our official TWRP dev and who maintains two popular ROMs recommends f2fs.
[RECOVERY][OFFICIAL TWRP 3.1.1][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=62363432&postcount=2
[QUOTE @bhb27]The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.
I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.
TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.
That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.
To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>
For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS
____________
This will not affect custom ROM, but i recommend to use f2fs.[/QUOTE]
In conclusion /data formatted as f2fs is better for Moto Maxx/DROID TURBO than ext4. I asking because only some Android devices use /data partition as f2fs because the majority is formatted as ext4. In Nougat custom ROM'S is f2fs better? And ChazzMatt your phone is formatted the /data partition as f2fs or ext4?
Hi all,
What is the file system (Data partition) used on Zenfone 6 ZS630KL ?
Is it EXT4, F2FS or whatever ?
Please enlighten
Hello,
i Have recently upgraded to android 10. When flashing twrp i get a message failed to mount system partition. If i reformat system to ext 2 then back to ext4 i can mount system in twrp. When i re flash latest factory pixel 2 image and go back into twrp i can no longer mount system again. Is this some new thing with Android 10? Without it mounted i can not access my system partition with root explorer or other root apps. is there a way to force system to mount after flashing a new image?
After reflashing with magisk system was mounted somehow. Not sure how this happened.
Hello, i have a Redmi note 9S which shipped with Android 10 out of box.. i'm using Dynamic System Updates (DSU) with unlocked bootloader to try custom roms and decided to modify some custom GSI to manually root it and customize some apps (modifications directly to system partition) but noticed that system partition can't be mounted as rw and gives error "wrong fs type, bad option,.." i can only mount it as ro.
I knew that this happens because ext4 partition formatted with EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (so called ext4 dedup) and this prevent it from being mounted as rw, trying to extend system.img with fallocate and resize ext4 file system with resize2fs and then use "e2fsck -E unshare_blocks" seems to work but the phone can't boot and trying to create a new rw system.img also fail as device doesn't boot, also i noticed that GSI versions with "vndklite" can be mounted as rw but same thing, it fail to boot when flashed with DSU and the device reboot again to the main OS..
So i have two questions here:
1) is that happens because the device refuse to boot system partition without EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS as it's already shipped with Android 10 and support this out of box or this happens because of DSU and will boot if flashed with fastboot?
2) and most importantly how can i modify system.img and then apply EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (apply shared blocks feature on the file system) like what custom roms developers do so i can boot a modded system partition?
Any help would be appreciated.. Thanks!
same question, did you find answer?
Hey,
i was wondering which file system the google pixel 2 is using for the userdata and system partition. My pixel 1 is using ext4 while my pixel 5 is already using f2fs. I am looking for a phone that still uses ext4 for the two partitions but is also running on android 11.