Database Users

[Q] Installing Thunderkat 4.4.3 on F2FS partitions

Reading more on F2FS trying to formulate a plan of attackx. Latest TWRP 2.7.1.0 is able to repair/format F2FS partitions, so I'm covered there before installing a ROM.
Some ROMs have the boot.img fstab files mount just /data as F2FS (like a Moto X). Others mount all partitions as F2FS (haven't found any threads comparing benefits of doing all vs. just /data)
/META-INF/Com/Google/android/updater-script needs to be modified to format and mount the appopriate partitions as F2FS.
So for a phased approach, say getting toes wet with just setting up /data for F2FS, is it just
1) editing the ThunderKat_manta-KTU84M-20140607.zip boot.img fstab and changing
Code:
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,
data=ordered 0 0
to
Code:
/dev/block/platform/dw_mmc.0/by-name/userdata /data f2fs rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,
data=ordered 0 0
2) editing the ThunderKat_manta-KTU84M-20140607.zip /META-INF/Com/Google/android/updater-script so that it will now do a destructive format of /data to F2FS
Code:
format("f2fs", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/userdata", "0", "/data");
3) doing the install from TWRP?
Am I on the right track? Miles off?
If I'm on the right track, what's required to do all partitions as F2FS? Would I have to put the ROM to be installed on a USB stick via USB OTG so that the recovery could find it after all the formatting?

I've been messing with this today and so far, I'm getting permissions issues quite possibly related to SELinux. Issues with SELinux relabeling issues are not allowing writing on F2FS partitions...
EDIT: Confirmed my suspicion that it was SELinux related. Attached screenshot shows CM11 4.4.3 with ThunderKat kernel and data partition mounted as F2FS

Just an idea cause it's so convenient: On my N7 there's an app called "Convert to F2FS" - Play Store. It converts ANY rom to f2fs. It also works for N4 & N5's. Dev states that he'll add other devices if contacted. It works brilliantly & is about a buck & 1/2. It doesn't work on 4.4.3 yet tho
Sent from my Nexus 7 using Tapatalk 2

Hi Craig,
will the latest ThunderKat still fail due to SELinux relabeling if installed on F2FS? Would a tool like this one make a difference?
http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
craigacgomez said:
I've been messing with this today and so far, I'm getting permissions issues quite possibly related to SELinux. Issues with SELinux relabeling issues are not allowing writing on F2FS partitions...
EDIT: Confirmed my suspicion that it was SELinux related. Attached screenshot shows CM11 4.4.3 with ThunderKat kernel and data partition mounted as F2FS
Click to expand...
Click to collapse

vprasad1 said:
Hi Craig,
will the latest ThunderKat still fail due to SELinux relabeling if installed on F2FS? Would a tool like this one make a difference?
http://forum.xda-developers.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702
Click to expand...
Click to collapse
I haven't tested this yet with the new release. Will do so this weekend.
Sent from my Nexus 5

craigacgomez said:
I haven't tested this yet with the new release. Will do so this weekend.
Sent from my Nexus 5
Click to expand...
Click to collapse
FYI latest TWRP 2.8.0.1 does not have F2FS format in wipe, whilst it is in the 2.7.1.0.

[Q] make /data to f2fs problem, help !!

Hello,
I'm a new developer and try to reference other people's steps to change /data to f2fs. However, I have some problems and it have bothered me a few days. When I chose format /data and type yes, it showed error message " E: Unable to mount '/data' ". As a result, I decided to format then mount /data by myself. Unfortunately, when I used modified TWRP to mount /data which have already formatted by mkfs.f2fs , it showed error message "mounting /data, operation not supported on transport endpoint". However when I mount /data which formatted by make_ext4, it was success. I have already read my threads but I couldn't find a solution. Did any thing I forget to modified? Can anyone help me or give me some hints? Plz
Here is my modify step: (reference ss2man44 's thread in Nexus 7 Developer Discussion ,＃Use of F2FS for /data)
1. use f2fs patch to modified kernel, turn on f2fs then flash to my device. It works.
2. modified twrp.fstab and fstab.grouper
3. give statically link to TWRP
Here is my environment:
Device: Nexus 7 (2012)
Kernel version: 3.1.10 (nightly)
Android version: 4.4.3
ROM: CyanogenMod(cm-11)
TWRP: 2.7.1.0 (support F2FS)

CONFIG_F2FS_FS=y
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
That last one defaults to N.
Switching to y fixes f2fs in twrp. However, it looks like I'm running into additional selinux issues with android: ubject_r:unlabeled:s0 data

[i9505][Q] F2fs partition

How can I convert a rom in f2fs without applying kt-tweaker? And how to format /sysem partition correctly because I0ve tryed to install CM12 after convert system but the instllation got errors and gapps fail to install
thanks in advance.

[Q] [OPINIONS PLS] My Nexus 4 running KK PA 4.6, Full F2FS. Please suggest better rom

Hi all, not so sure if this is repeated question.
I am looking for a faster rom for my phone, wants it to be fast and saves battery. Could you guys provide suggestions?
My Nexus 4 is currently on:-
Rom: Paranoid Android 4.6-Beta6 (Unofficial release, found under development threads)
Kernel: 3.4.104-franco-Kernel-SaberMod-r213.2
File system: Full-F2FS (System, cache, data are in F2FS file system)
Thanks in advanced. ^^

Chroma+Quanta kernel, you can convert /data and /cache to f2fs if you want

voron00 said:
Chroma+Quanta kernel, you can convert /data and /cache to f2fs if you want
Click to expand...
Click to collapse
Will there be performance sacrifice as system partition not F2FS?
I would PM you later on how should I carry out the process. The last time I flashed, I got message prompting me to type a message to access locked storage, but it's actually due to it couldn't access as kernel doesn't support F2FS. Probably I didn't flash F2FS kernel after flashing rom.

ordinarystar said:
Will there be performance sacrifice as system partition not F2FS?
I would PM you later on how should I carry out the process. The last time I flashed, I got message prompting me to type a message to access locked storage, but it's actually due to it couldn't access as kernel doesn't support F2FS. Probably I didn't flash F2FS kernel after flashing rom.
Click to expand...
Click to collapse
There is no big improvement of using F2FS at all. And since /system is read only this is totally not need
And yes, you got storage locked because of kernel without F2FS support.

Unable to Mount System

i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.

Ragavendran 007 said:
i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.
Click to expand...
Click to collapse
You have to format data and then change system partition to ext4 and now you can flash the rom again.

Aarju said:
You have to format data and then change system partition to ext4 and now you can flash the rom again.
Click to expand...
Click to collapse
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs

Ragavendran 007 said:
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs
Click to expand...
Click to collapse
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.

Aarju said:
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.
Click to expand...
Click to collapse
F2fs has better writing speed. Then I may help to install the apps faster.. right?

https://medium.com/thecyberfibre/f2fs-versus-ext4-our-take-on-the-ongoing-battle-c0324f46d040

Ragavendran 007 said:
F2fs has better writing speed. Then I may help to install the apps faster.. right?
Click to expand...
Click to collapse
While faster, you may find yourself with compatibility issues in regard to your preferred ROM, etc.
Sticking with ext4 (for now) is simply the better option at the moment because it ensures that your reliability and compatibility. Also, there are apparently some issues with f2fs when it comes to device encryption.
Therefore: just wait. Maybe in the future f2fs will be the better option. As for now: I don't think that with an OP5 you need to worry about the installation time of apps taking too long.