Related
@HardLight
to put in my p500 f2fs style I have to change it before the partition tools or TWRP does it
wi fi not connecting in kernel 3.0.101
the rom cm11-2014 / 08/30 and cm11-2014 / 08/29 f2fs so2sd the keyboard does not work
I will use the rom cm11-2014 / 08/18 os2sd get put right until the f2fs
I'm a beginner, but I like these rom's that you put here
Thank you for helping us make our phone better
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
This is a personal build of TWRP with F2FS support(proper way) based off 2.8.1.0 branch from Omnirom(recovery) which I butchered and added F2FS..
This was tested with CM11 way back last year..I just posted it for the heck of sharing it since I have not seen the same idea/achievement here on M7 forums..and seems this phone needs a "refresh"(in a good way)..
Now whats F2FS?? Googling can give you trivial INFO yet you can start your way here
This file system developed by Samsung lean towards a less noisier, less workloads, and a faster throughput File System that can substitute EXT4 in the near future(they already use it)..extensively if you rely heavy on Benchmarks it has been put to the test by some Devs here on XDA like this one
Now enough with the chit-chat..on this TWRP build I only converted /DATA as F2FS..now you might be wondering why?? Answer is because its the most actively used partition on your phone..System apps use it to store settings/info/etc...Framework uses it too for caching and storage...Extensively your Apps(the ones you install) use it as well..so theres completely no point converting the whole phone to F2FS which in the latter can just cause you more issues when you want to return to stock..
This only works on AOSP based ROMs(i tried it on CM11) though you'll need a kernel with F2FS support baked in for things to work properly.. (Who wants me to build one? I know for sure you don't..)
DO NOT TRY ON SENSE(You have been warned) Tried it once well it boots up(Proper F2FS kernel is required) but you'll end up on a security windows and you might not get out if it..OR you may be able to boot it up but you cannot install apps(happened to me twice and no Dice on installing anything)..well you're free to play with it so who knows who might get a lucky pick on getting this working on HTC Sense ROM's, but for now I'll safely say/advise to use on AOSP ROMS only..
Download here
**I won't be liable for any damage on your phone..you are on your own here..
**This project does not come with a warranty..
XDA:DevDB Information
Recovery with F2FS, Tool/Utility for the HTC One
Contributors
kairi_zeroblade
Version Information
Status: Stable
Stable Release Date: 2015-02-05
Created 2015-02-05
Last Updated 2015-02-05
Reserved
Why not? It's time to update your aosp kernel production mate!
Sounds great
For your Sense-Problem: it does boot, right? So it shouls work but HTC implemented some nasty **** to block your phone when using F2FS. So there has to be some code for checking the filesystem and then launching the "block-app". Removing the abvoe mentioned code would give the Sense users the opportunity to use it to.
Maybe you this can help you
@kairi_zeroblade when you say AOSP roms only, does that rule out GPE because CM12 is very buggy
Does this recovery tested on CM12 and derivative ROM's?
:good:
Hi,
I'm trying to use f2fs on my m7. The fstab from the kernel looks like that:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,noatime,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
/dev/block/platform/msm_sdcc.1/by-name/radio /firmware/mdm vfat ro,fmask=0000,dmask=0000,shortname=lower,context=u:object_r:firmware_file:s0 wait
/dev/block/platform/msm_sdcc.1/by-name/adsp /firmware/q6 vfat ro,fmask=0000,dmask=0000,shortname=lower,context=u:object_r:firmware_file:s0 wait
# USB storage
/devices/platform/msm_hsusb_host/usb* auto auto defaults voldmanaged=usbdisk:auto
The rom I try to boot on with cache on f2fs, system and data still ext4 is the one linked here
Any hint what's the problem/what part doesn't support it properly?
L
Info
Is encrypted sdcard compatible with F2FS file system?
I'm using your recovery now with AICP 8, the f2fs parts are working fine, but everytime I tried to format back to ext4, I needed another twrp version from either the official site or MDMower.
And the second thing I found was, the recovery always tells me it didn't found a few files (theme related things).
Would it be possible to update the f2fs twrp to version 2.8.5.6 from here?
L
Edit: I mixed together the 2.8.5.6 unofficial with the kernel and ramdisk from @kairi_zeroblade 's f2fs version. Up to now it seems to work fine. The f2fs paritons get mounted and backup is working also. Flash an upadate or restore isn't tested yet. And what I also can't test, if it works for ext4 (or also f2fs) people who use encryption. Could that be tested by someone please?
Link: openrecovery-twrp-2.8.5.6-m7-materialised-F2FS.img
Hi there,
here's an update to version 2.8.6.1
openrecovery-twrp-2.8.6.1-m7-materialised-F2FS.img
L
Info
I want to test last version.
Which partition can i convert in F2FS?
Is needed kernel support?
ultrasound1991 said:
I want to test last version.
Which partition can i convert in F2FS?
Is needed kernel support?
Click to expand...
Click to collapse
most roms only support data & cache for f2fs and you will need a compatible kernel for f2fs. I won't say i tried every rom out there but AICP & Vanir support f2fs very well. You could theoretically install any rom for f2fs is you had a third party kernel out there that was compatible... and I'm not sure if there are any right now (i think AGK is going to get it soon though)
qkall said:
most roms only support data & cache for f2fs and you will need a compatible kernel for f2fs. I won't say i tried every rom out there but AICP & Vanir support f2fs very well. You could theoretically install any rom for f2fs is you had a third party kernel out there that was compatible... and I'm not sure if there are any right now (i think AGK is going to get it soon though)
Click to expand...
Click to collapse
Ok, i want to try.
I will convert system,data and cache to f2fs.
Does my rom is full compatible if it start normally?
ultrasound1991 said:
Ok, i want to try.
I will convert system,data and cache to f2fs.
Does my rom is full compatible if it start normally?
Click to expand...
Click to collapse
no system will not work but data and cache will!
qkall said:
no system will not work but data and cache will!
Click to expand...
Click to collapse
Ok, but does system will work in next version? Or in future?
ultrasound1991 said:
Ok, but does system will work in next version? Or in future?
Click to expand...
Click to collapse
Honestly, I don't know... but I would assume it would eventually be a feature but I'm not knowledgeable to know.
here's a tutorial for properly settings up f2fs though
I sort of recommend using Vanir though - a faster experience.
qkall said:
Honestly, I don't know... but I would assume it would eventually be a feature but I'm not knowledgeable to know.
here's a tutorial for properly settings up f2fs though
I sort of recommend using Vanir though - a faster experience.
Click to expand...
Click to collapse
I want XenonHD or AICP, or a ROM that will be updated over Lollipop in future.
ultrasound1991 said:
I want XenonHD or AICP, or a ROM that will be updated over Lollipop in future.
Click to expand...
Click to collapse
I can't speak for XenonHD but AICP and Vanir are incredibly active (vanir not so much on m7 xda forums but the google plus page is good)
edit- i just checked... it doesn't look like XenonHD has f2fs support yet... but if you had a third party kernel that would work (which again i don't think there are any atm).
qkall said:
I can't speak for XenonHD but AICP and Vanir are incredibly active (vanir not so much on m7 xda forums but the google plus page is good)
edit- i just checked... it doesn't look like XenonHD has f2fs support yet... but if you had a third party kernel that would work (which again i don't think there are any atm).
Click to expand...
Click to collapse
Now i'm downloading AICP 8 ROM, AGK AOSP 1.7 Kernel and twrp 2.8.6.1 f2fs materialised (Isn't there normal themed?).
---------- Post added at 09:05 PM ---------- Previous post was at 08:58 PM ----------
9Lukas5 said:
Hi there,
here's an update to version 2.8.6.1
openrecovery-twrp-2.8.6.1-m7-materialised-F2FS.img
L
Click to expand...
Click to collapse
Is this update your or of kairi_zeroblade?
Hi all,
I'm currently using Novafusion CarbonROM 4.4.4, TWRP v2.8.0.0 with the f2fs filesystem. I want to goto OmniROM 5.1.1 (found here) which I understand doesn't use f2fs but ext4.
How do I have to go about doing this?
Can I use the current TWRP to convert from f2fs to ext4 and after that use it to write the new ROM, or?
Thanks in advance for your insights
Androidioid said:
Hi all,
I'm currently using Novafusion CarbonROM 4.4.4, TWRP v2.8.0.0 with the f2fs filesystem. I want to goto OmniROM 5.1.1 (found here) which I understand doesn't use f2fs but ext4.
How do I have to go about doing this?
Can I use the current TWRP to convert from f2fs to ext4 and after that use it to write the new ROM, or?
Thanks in advance for your insights
Click to expand...
Click to collapse
Nevermind, I managed;
- formated all partitions to ext4 with TWRP through the Wipe function;
- updated to the latest TWRP with the latest Odion;
- updated to OmniROM
This kernel have tested for g3311,and g3312/13 need to test
And it just for offical rom currently
Kernel Features:
[*]Based 43.0.A.7.55 official sources
[*]bootimg based 43.0.A.7.99_hk
[*]bootimg with magisk
[*]disbaled verity
[*]update to 3.18.36
[*]Added Ultra KSM
[*]KSM config have adjusted in bootimg
[*]OTG(just test)
[*]enable mtk dymamic
[*]F2FS supported
[*]Compiled with linaro 6.3 and enabled optimized flag
[*]CPU Governous(bioshock,thunderx,smartass,smartmax and more and more)(thunderx is default)(some gov is just test)
[*]I/O Scheduler(vr,sioplus and more,bfq is default)
[*]Added ThunderQuake Engine
[*]Added thunderchage and fastcharge(just test)
[*]Added frandom
[*]TCP:westwood is default
[*]Some Changes to improve performace
[*]Gpu midgard drivers update to r20p0
[*]Added Wireguard
[*]Added zswap
[*]Cpu overclock to 1556 and minimum 221
[*]Gpu overclock to 650 and added lower volt
[*]and more need you to explore
------------------------------------
Change Log
2020/3/6
[*]Fix fstab only f2fs error
------------------------------------
Contributor: rote66
Download link: kernel link
Kernel Source:: https://github.com/rote66/android_kernel_sony_pine
------------------------------------
To flash it:
1.backup your boot.img in your external_sd
2.flash twrp to boot
3.flash this kernel and reboot
About Change to f2fs
you need this TWRP
fixed MTP and support f2fs
TWRP link: TWRP link
Credits:
All developers for mediatek and in my commit
Version Information
Status: Stable(perhaps)
Current Stable Version: v1.5
Kernel Version: 3.18.x
Stable Release Date: 03-02-2020
I'm onstall that on my G3312 with last ROM and he stuck in bootloop
maximon8613777 said:
I'm onstall that on my G3312 with last ROM and he stuck in bootloop
Click to expand...
Click to collapse
Have fixed a fstab error,you can try it again
rote66 said:
Have fixed a fstab error,you can try it again
Click to expand...
Click to collapse
Yep, all is work. I be test that before stable LOS 14
maximon8613777 said:
Yep, all is work. I be test that before stable LOS 14
Click to expand...
Click to collapse
Los14.1 can be suited,just replace kernel manually.
rote66 said:
Los14.1 can be suited,just replace kernel manually.
Click to expand...
Click to collapse
Yes, but RIL on LOS has not working -> it makes no sense for me because i using L1 on the main
maximon8613777 said:
Yes, but RIL on LOS has not working -> it makes no sense for me because i using L1 on the main
Click to expand...
Click to collapse
ril and camera are hard working
decryptions and passwords?
Hi!!!
This will be the very first post of an utter noob
Namely, why upon installing the TWRP3.3.1-0_G3311_fix_rote66.img the phone cnstantly reboots into recovery and does not allow to make any changes without first providing a PASSWORD to decrypt DATA?
Am I doing something wrong? I can't flash the kernel, I can't in fact do anything...
noizzette said:
Hi!!!
This will be the very first post of an utter noob
Namely, why upon installing the TWRP3.3.1-0_G3311_fix_rote66.img the phone cnstantly reboots into recovery and does not allow to make any changes without first providing a PASSWORD to decrypt DATA?
Am I doing something wrong? I can't flash the kernel, I can't in fact do anything...
Click to expand...
Click to collapse
Your data is encrypted?Sorry i have not test the data with encryption.It seems the TWRP's decryption not Working. MayBe you can decrypt your data with formatting data.Or test the other twrp in fourms.
rote66 said:
Your data is encrypted?Sorry i have not test the data with encryption.It seems the TWRP's decryption not Working. MayBe you can decrypt your data with formatting data.Or test the other twrp in fourms.
Click to expand...
Click to collapse
Hi, no other TWRP in forums works and I have put all of them to test, really. No other boot.img works. Not even the one obtained through Magisk. Nothing. It never boots. I tried formatting data too. To no avail, though. It never completes the process.
The bootloader IS unlocked, the very model CAN have custom ROMs flashed to it. The problem must be elsewhere.
noizzette said:
Hi, no other TWRP in forums works and I have put all of them to test, really. No other boot.img works. Not even the one obtained through Magisk. Nothing. It never boots. I tried formatting data too. To no avail, though. It never completes the process.
The bootloader IS unlocked, the very model CAN have custom ROMs flashed to it. The problem must be elsewhere.
Click to expand...
Click to collapse
I think you need formatting data (format not wipe) then flash a non force-encrypt boot (like flash this kernel,it include boot.img)