[MOD][RECOVERY] All-F2FS for GT-I9190|GT-I9192|GT-I9195 [TWRP 2.8.6.0 & Philz Touch]
Hi!
Here I'll try to explain how to use F2FS partitions on your Galaxy S4 Mini.
This is for "All-F2FS" that mean that /system, /cache, /data and /external SD are formatted with F2FS, keep in mind that this can work only with a compatible kernel and ROM.
About F2FS
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Warning
* You agree to use this MOD/Guide on you own risk and I don't take any responsability if you encounter any issue or if your personal data is lost
Requirements
Your S4 Mini, GT-I9190 or GT-I9195 or GT-I9192 (serrano3g, serranolte, serranods)
An external MicroSD card or a PC (for backup/restore)
Preinstalling Steps
Backup of your personal data to an external SD card or PC (photo, music, ringtones, etc).
Make a full nandroid (just in case that you want to rollback to EXT4) and copy to your PC.
Download and copy to your External SD Card TWRP or Philz Touch with full F2FS support. (Downloads on Second Post)
Download and copy to your External SD Card latest version of f4ktion kernel or use one with All-F2FS support.
Download and copy to your External SD Card CarbonROM with F2FS support, or you can test on your favorite ROM, take in mind that using F2FS on External SD Cards will require F2FS support on your ROM of minivold for vold managed volumes. (Downloads on Second Post)
How can you test your favorite ROM?
I'll include this time CarbonROM with support for F2FS, on upcoming builds you'll need to edit manually the updater-script.
You need to edit updater-script on the zip file, you need to change the following:
Look for:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
And change it for:
Code:
run_program("/sbin/busybox", "mount", "/system");
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Installation Steps (Clean Install)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.2) Now go to Wipe menu and select Format Data and type "yes" (Warning this will format Data partition and your Internal Storage, so please don't forget to make a backup of your personal data)
1.3) Optional, select Advanced Wipe menu and check System and Cache partitions to convert to F2FS respectively.
For Philz Touch
1.1) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.2) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.3) Optional, you can select format /system and format /cache to convert to F2FS respectively.
2) Install your ROM as usual, then flash your GApps and f4ktion kernel in this order.
3) Restore your personal data to your internal SD Card.
If you don't want to make a clean install, you can convert /data partition to F2FS using and restoring a /data nandroid backup.
Installation Steps (Restoring /Data partition)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Make a nandroid of /data partition.
1.2) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.3) Now go to Wipe menu and select Advanced Wipe menu and check Data, swipe to confirm wipe.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
For Philz Touch
1.1) Make a custom nandroid of /data partition.
1.2) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.3) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
How to check if you have correctly formatted partitions to F2FS?
Through terminal do:
Code:
su
mount | grep f2fs
Through adb do:
Code:
adb shell
su
mount | grep f2fs
Also you can check F2FS's status by doing:
Code:
cat /sys/kernel/debug/f2fs/status
Or just install DiskInfo app
Credits
@Dees_Troy for TWRP
@ktoonsez for F2FS mod
@Phil3759 for Philz Touch
TWRP 2.8.1.0 F2FS MOD
GT-I9190
GT-I9192
GT-I9195
Philz Touch F2FS
GT-I9190
GT-I9192
GT-I9195
F4k said:
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Darktitor said:
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Click to expand...
Click to collapse
This step is if you want /system partition as f2fs, you can use f2fs on whatever you want.
If you don't edit updater-script, your /system partition will be formatted as ext4
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Phenom2122 said:
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Click to expand...
Click to collapse
It's the same but with modified updater-script, this version will format /system partition as f2fs, the one on Carbon's thread as ext4.
All formatted f2fs and everything flashed and running smoothly thanks f4k
Sent from my GT-I9195 using XDA Premium 4 mobile app
From now on we should unzip the rom file and change tha script to have f2fs?
Hope random reboots to stop..
Everything fine with clean install.. One bug tha colors in recent calls with tha black theme
Στάλθηκε από το GT-I9195 μου χρησιμοποιώντας Tapatalk
@F4k nice splash screen you have in your twrp recovery, also glad you added the "force wipe to use f2fs option " this way I can use the twrp themes without the need for additional changes to it.
Sent from my GT-I9195 using Tapatalk
Since doing a format of /data and /data/media Philz works correctly the first time with settings in mnt/shell/emulated/0/clockworkmod. After doing a reboot into recovery later, suddenly it has created a mnt/shell/emulated/0/0/clockworkmod and it seems to be randomly reading settings from either location ie. sometimes it will correctly launch Aroma, sometimes it wont. This is a very strange error because I went back to one of the older Philz versions and the same problem persists.
Will try out TWRP now.
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
chacox said:
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
Click to expand...
Click to collapse
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
F4k said:
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
Click to expand...
Click to collapse
ok, I will try right now! and Ill let you know if it works in that way, thanks for your great job!
update: yeah it worked in that way! I have f2fs in every partition! thanks
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
aguaz said:
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
Click to expand...
Click to collapse
To use F2FS on external sd cards, ROM needs to have F2FS support on minivold for vold managed volumes, my CarbonROM builds support it.
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
F4k said:
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
Click to expand...
Click to collapse
My understanding is that the mount point on /mnt/media_rw/sdcard1 is for internal use only. Apps however use the additional mount point on /storage/scdard1 . This mount point has a fuse layer on top, which prevents the use of symlinks on eg ext4 formatted cards. (see here: http://forum.xda-developers.com/showthread.php?t=1442729)
So I'm wondering if F2FS can be accessed by apps natively w/o fuse layer in order to use symlinks. That is of course assuming F2FS supports symlinks itself.
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
After using TWRP for a while I decided to go back to Philz, this time without reformatting or restoring any old settings. Everything is working perfectly now, something crazy must have happened with my old settings, I suspect with 'Sd Card Target'.
Thank you very much for this F4k. Besides the addition of F2fs support, previously the latest version available to us was 6.41.6, very nice to have such an up to date version now I seriously would donate if I had the means to, and as soon as I actually have some money in my bank account for a change I definitely will be doing so
dulemars said:
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
Click to expand...
Click to collapse
I don't added crypto support yet to TWRP
i've a problem with system partition.
i use twrp recovery. i've do a clean install format data, i've cheked in Advanced Wipe System and Cache partitions to convert to F2FS, wiped system and cache, i've install last cyanogen nightly and... in diskinfo data is f2fs, cache is f2fs but system is ext4.... why? what's wrong?
thanks
Related
Everything Should Be Functioning Properly & Some Extra Features Have Been Added.
I love Amon_RA's recovery images and decided to make one using his source code for the Incredible to give us another option other than clockwork. This is my 2nd recovery I've made since switching to android from windows mobile about two weeks ago. Lg ally was the other Link here . This one I built with an ext-4 kernel I compiled so you can partition apps2sd with ext4 in recovery but remember your rom's kernel must support ext-4 too.
Link to Amon_RA's nexus one recovery thread as it has a good description of what all the features are Link here
To use if you have s-off download the PB31IMG_RA-inc-v1.7.0.6_GNM.zip and unzip it to get the PB31IMG.zip and copy that to the root of your sdcard. Boot phone holding down vol down and select yes to update.
To use with unrevoked recovery reflasher download the recovery-RA-v1.7.0.5.img and in recovery reflasher select file and custom recovery and navigate to where you downloaded the file.
Special Thanks:
Amon_RA for his source code Buy him a redbull
Team Unrevoked for the Recovery Reflasher and the S-off Link
Koush source code
worstenbrood source code for modded desire recovery
changelog v1.7.0.2 :
fixed data wiping and cache wiping as they are ext3 partitions not yaffs2
currently wiping cache can only be done with wipe cache not wipe data/factory reset
Thanks koush for the help
fixed flashing update.zips
changelog V1.7.0.3:
fixed small error in sd partitioning script
changelog V1.7.0.4 see attached pics
Added usb mount of phone's internal storage
Added toggle of signature verification on update.zips
Added gui mount umount menu
changelog V1.7.0.5
Changed nandroid-mobile.sh script to correctly backup and restore /data/data and backup and restore .android_secure on /emmc if selected.
Changelog V1.7.0.6
Fixed typo that caused nandroid to always restore most current backup.
Changes v1.8.1
Supports both Amoled and SLCD
Now supports Flashing from Emmc or Sdcard!!!
Has zip directory browsing from clockwork so zips are no longer needed in root of sdcard (thanks Koush & Amon-Ra)
Wipe Menu no longer uses scripts
Fix error in script for sd-ext upgrading
Fixed The sd-ext issues??
Updated the PB31IMG to be compatible with 3.26.605.1 and prior
Also in rom manager too!!!
Changes 2.2.1
Updated UI
Fixed zip progress menu in flashing
Fixed .android_secure backup back to sdcard from /emmc (was changed in the 11/10 htc update)
Expanded the UI for fuller listing of sdcard zips & dirs. (Thanks Amon_RA)
Still recommend making a folder called Custom_Roms on sd and placing update.zip's there
Selectable nandroid partitons gui for backup (Thanks Amon_Ra)
Now backs up sd-ext partiton as a whole if that option is selected in nandroid.
Downloadable from rom manager!!!
Fully working with gingerbread/cm7 and wipes all partitons correctly.
Added menu option to format /data partiton to ext4 and is able to reformat back to ext3 too. (See notes below)
Above option for ext4 requires a kernel with ext4 support and changing the mount line in init.inc.rc in boot.img/ramdisk from ext3 to ext4. This will enable mounting of the ext4 /data as ext4 instead of having the ext4 partition mounted as ext3. This formatting will persist through rom flashing and /data wiping but can be reverted via ext3 reformat option. Warning a non ext4 enabled kernel will not be able to mount an ext4 /data partition. If a ext3 data nandroid is restored to an ext4 formatted data partiton all the old files will work as ext3 and anything newly added will be in ext4 (best to start /data fresh to get full benefit of ext4 fs).
Example for changing init.inc.rc line in boot.img for cm7 (similar for stock rom on froyo too)
Code:
mount ext3 /dev/block/mmcblk0p1 /data wait nosuid noatime nodiratime
change to
Code:
mount ext4 /dev/block/mmcblk0p1 /data wait nosuid noatime nodiratime
Then repack boot.img and reflash.
Change log 3.02:
Nandroid now has the option to backup & restore .android_secure on /sdcard or /emmc (stock GB has .android_secure on /emmc)
Added busybox symlinks for mount & umount (now sense 3.0 roms that use busybox to mount in updater script work)
Added script to (re)format /emmc as ext3, ext4 or fat32 (run "partemmc help" from adb shell for use)
Added options in wipe menu to wipe /sdcard & /emmc
Wiping all or wipe .android_secure wipes it on both /sdcard and /emmc
Changed ui back to cyan colors.
Updated /data as ext4 to wipe /datadata also.
Nandroid now suppressed backup of /datadata also when selecting to not backup /data partition
File system type for /cache, /data, /sd-ext and /emmc are auto detected so you can use alternate filesystems (rom kernel & boot.img permitting)
As always properly wipes and you can use update-script or updater-script (amend or edify)
Added flash_eraseall binary this can be used to fix a corrupted nand mtd(not emmc) by erasing it then you can reflash it. Use is "adb shell flash_eraseall /dev/mtd/mtdX" where X is the number of the mtd you wish to erase.
Changelog: 3.06
Added ability to restore CWM backups.
Compiled for armv7a-neon so its faster.
Rewrote the ext3|4 menu to use C not scripts
Added a developer menu:
Developer menu:
Make and flash boot from zimage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Toggle full ext wipe : This toggles between doing a quick wipe (default) of ext partitions or a full wipe which reformats them.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Downloads:
Source
recovery-ra-dinc-3.06-gnm.img
MD5 : c280fc5cfacf1018211f9ed4ffd42d87 recovery-ra-dinc-3.06-gnm.img
Old PB31IMG_RA-inc-v1.7.0.3_GNM.zip
MD5= d8aae2598c6f7b3f441bbea2ba35beb1
Old PB31IMG_RA-inc-v1.7.0.4_GNM.zip
MD5= 92d187e7b4bc6553e6daa369af8e55ce
Old PB31IMG_RA-inc-v1.7.0.5_GNM.zip
MD5= 832a1980c30a7dd7dd7751020bf2fb45
Old recovery-RA-v1.7.0.5_GNM.img for recovery reflasher
MD5=30a78ffca87de656a6a77246af6ff6e8
Old PB31IMG_RA_inc_1.7.0.6.zip
MD5= 2f0210ee1ede2bfd0f80af5f07c6da5c
Old PB31IMG_RA_inc_1.8.1_GNM.zip
MD5 9d6da2a06219651eb9be82872570b510
Old PB31IMG_RA_inc_v2.2.1_GNM.zip
MD5 84b5bae5c5adc4936e3a48c742cc03e4
PB31IMG-RA-3.02-GNM.zip
MD5 3efae04dc59bdaf4ea7bb18aea5b208d PB31IMG-RA-3.02-GNM.zip
Buy me a energy drink Follow me on twitter @getitnowmarket
Has anyone tested??
• Sent from my Droid Incredible running Sky Raider 2.5.2 •
thatdudebutch said:
Has anyone tested??
• Sent from my Droid Incredible running Sky Raider 2.5.2 •
Click to expand...
Click to collapse
I just tired it and it works perfectly, i just flashed the img via 3.1
Amazing work! Finally! I hate clockwork but love amon ra. Nice work!
what's the difference between this and clockwork? i'm not trying to instigate anything. clockwork is the only recovery that i've used but from reading that linked thread it looks like maybe it has a few more features? i'm not sure. the UI between the two seem somewhat similar too.
Awesome. If Clockwork ever fails me, I have another option. Thank you.
Dude, this is awesome. Finally! Source?
Haven't tried it, but it's always nice to have options. Thanks for taking the time to put this together!
update keeps failing for me and a couple other in the IRC.
borgey420 said:
update keeps failing for me and a couple other in the IRC.
Click to expand...
Click to collapse
same here. tried to flash using reflash, pb31img, and flash_image. all fail.
scuccia said:
same here. tried to flash using reflash, pb31img, and flash_image. all fail.
Click to expand...
Click to collapse
I was able to download, but md5sum didn't match
Looking into it think I uploaded the wrong binary version. Fixed and am going to re-upload
Is there a way to go back to clockwork if we don't like this.
Sent from my Incredible using XDA App
Ruben1123 said:
Is there a way to go back to clockwork if we don't like this.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
http://unrevoked.com/rootwiki/doku.php/public/forever
under the reinstall factory recovery there is a link to the clockwork pb31img... almost at the bottom of the page... its there so you can do it after you load an official update with s-off
Thanks for this. You helped me with my Ally already (which works great now), and now the Incredible. Thanks again!
Very well done, sir! I was missing my Amon_RA from my G1 days and this has hit the spot. I checked the md5 sums, applied your image file with flash_image... then powered off and manually booted into recovery from bootloader/hboot, to avoid boot mode 3, a little lesson also learned from my G1 days
Now all that's left is to put in a nice blue care bear for a background and remove the plug for your company and we'll be all set!
Sent from my Incredible using XDA App
am I stupid, or is the link not up?
Im having trouble with the wipe data command as "userdata" mtd on this phone is called "datadata" and is not wiping. Will re-release once fixed. Other than that its fully functional.
is the zip up??? If not can someone provide a mirror
As far a features go, what's the difference between this and clockwork?
-Sent from your mom's phone.
Hi guys Do I need a special version of int2ext in order to use it with Jelly Bean rom (in particular CM 10.1)? An ext4 partition will be fine for this use? Last but not least: to install this script is needed a special procedure (like mount /system and /data in recovery)? Thank you for your help and time Have a great life, peace!
MeltingSnowman said:
Hi guys Do I need a special version of int2ext in order to use it with Jelly Bean rom (in particular CM 10.1)? An ext4 partition will be fine for this use? Last but not least: to install this script is needed a special procedure (like mount /system and /data in recovery)? Thank you for your help and time Have a great life, peace!
Click to expand...
Click to collapse
1. Int2ext scripts work in JB
2. .ext4 is the best option
3. The procedure is always the same:
First of all create you sd-ext partition using MiniTool Partition
Code:
1. Backup your current data (optional)
2. Boot into CWM/Go back to CWM menu
3. Flashing the script:
>>> mount data
>>> mount system
>>> mount sd-ext
>>> format SD-EXT (YOUR EXTERNAL PARTITION, NOT YOUR SD!)
4. Flash the script!
5. Reboot system
Viper The Ripper said:
1. Int2ext scripts work in JB
2. .ext4 is the best option
3. The procedure is always the same:
First of all create you sd-ext partition using MiniTool Partition
Code:
1. Backup your current data (optional)
2. Boot into CWM/Go back to CWM menu
3. Flashing the script:
>>> mount data
>>> mount system
>>>(mount sd-ext)
>>> format SD-EXT (YOUR EXTERNAL PARTITION, NOT YOUR SD!)
4. Flash the script!
5. Reboot system
Click to expand...
Click to collapse
Thank you so much for the fast and super-detailed answer. One thing I don't understand the reason why: the ext partition I crate in sd card with my pc is empty so why do I need to format it again with CWM?
MeltingSnowman said:
Thank you so much for the fast and super-detailed answer. One thing I don't understand the reason why: the ext partition I crate in sd card with my pc is empty so why do I need to format it again with CWM?
Click to expand...
Click to collapse
You can create your sd-ext using your pc or CWM, I advise you to use your PC (MiniTools Partition). It's safe, easy and you can choose .ext4 format
Using CWM >> Format sd-ext command will wipe your sd-ext data, so don't worry about "re-format" your sd.ext, it won't change your sd-ext's system format
The best, the safest & the easiest way to create a partition on your SD card is always via your custom recovery. You can format it to the EXT4 file system using the EXT4 conversion tool by PSDNA. Mini partition tool killed my brand new 4GB class 4 SD card.
Also nothing special for Jelly Bean as @Viper The Ripper said. It is just the same drill & yeah, cronmod scripts support all android versions & the flashing procedure always remains the same. I recommend you to use INT2EXT+.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
The best, the safest & the easiest way to create a partition on your SD card is always via your custom recovery. You can format it to the EXT4 file system using the EXT4 conversion tool by PSDNA. Mini partition tool killed my brand new 4GB class 4 SD card.
Also nothing special for Jelly Bean as @Viper The Ripper said. It is just the same drill & yeah, cronmod scripts support all android versions & the flashing procedure always remains the same. I recommend you to use INT2EXT+.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
I created succesfully a 768mb EXT4 partition with Minitool Partition flawlessly. First I formatted the SD card with Windows. Than into Minitool Parition I deleted the whole FAT32 partition, created a new FAT32 partition set as active with 768mb unallocated. Last thing I did was allocate that 768mb as EXT4. All partition are created as primary, not logical. Also used diskinfo on android and got that 768mb working without problems. Hope my steps are good hints for you to avoid other dead SD cards
FIRST OF ALL, we should say thanks to @alvinhochun 's work on porting kexec hardboot patch to Xperia M. His original thread is here: http://forum.xda-developers.com/showthread.php?t=2568151
And @Tasssadar who has ported kexec hardboot patch on MSM chips. Original thread is here: http://forum.xda-developers.com/nexus-4/orig-development/kexec-hardboot-patch-t2472316/post46223952
As for the kernel patch and kexec binary for TX, they are here: http://forum.xda-developers.com/showthread.php?t=2747215
OK let's begin our tour on TX...
0. Disclaimer
This is a rather dangerous hack. I'm not responsible for data loss, broken SD cards, dead internal storage or bricked phones. Try this at your own risk. Proceed only when you know what you are doing.
1. Requirements
a. ROM with “kexec hardboot” patched kernel. My OmniROM build will do the job. Since Alx31Tse is also using my kernel source for TX, the Carbon builds for TX may be capable of handling this as well. This ROM should be installed into internal storage : just flash it in recovery as usual.b. External MicroSD card which is big enough for your ROMs. One ROM takes up ~4GB space.c. Some basic knowledge of partitions, device nodes, ramdisk modding(check this thread by letama: http://forum.xda-developers.com/showthread.php?t=2418893).
2. Partitioning the external sdcard
a. Plan the partitions
Each ROM need three partitions : system, data and cache. You need at least 1.4GB system + 2GB data + 400MB cache for stock ROMs. The system partition for third-party ROMs can be shrinked to ~900MB. Of course you can set your own data partition size if 2GB does not suit your needs. The space left can be used for storing data just like a normal sdcard.
For example, I'm using a 16GB card and going to install two stock ROMs (9.1.B.1.67 + 9.2.A.0.295). So I have to create at least 6 partitions for them:
1.4GB system for 295
2GB data for 295
400MB cache for 295
1.4GB system for 67
2GB data for 67
400MB cache for 67
There is ~8GB left after all these partitions. This can be used as a normal sdcard. Just create another partition for it.
b. Go partitioning it!
Everyone has his own way of doing this. I prefer using a USB card reader and Disk Utility that comes with Ubuntu.
Erase the card and initialize it with GUID Partition Table (GPT). Of course you can use MBR, but I didn't test it. Be careful in the following steps if you choose MBR.
Create the “normal sdcard” partition. In my example, create a 8GB partition here and format it with FAT32. THIS PARTITION SHOULD BE THE FIRST ONE ON THE CARD! Otherwise Android system may not be able to recognize it.
Create the partitions for guest systems. There are no particular order for the partitions. Just make sure you remember their order. DO NOT FORMAT them for now.
In my example:
PART 1: 8GB, FAT32
PART 2: 1.4GB unformatted
PART 3: 2GB unformatted
PART 4: 400MB unformatted
PART 5: 1.4GB unformatted
PART 6: 2GB unformatted
PART 7: 400MB unformatted
3. Kernel mods for guest systems
For each guest system:
a. Unpack its kernel.
If you are going to install a full stock ROM, please choose a corresponding kernel with recovery built-in in Android Development section.
If you are going to install a third-party ROM (OmniROM, CM etc) or customized stock ROM (Rockers etc), chances are that their kernels have recovery built-in already and you can proceed.
Now unpack the kernel.
We have zImage(sec0.bin), ramdisk(sec1.bin) now. The rest can be ignored.
b. Modify the mount entries in fstab (and other files)
fstab is the file that suggests the real device for the /system, /data and /cache mount points. Modding it will make it possible to mount the partitions other than the ones in internal storage on /system /data and /cache, so that we can separate different systems into different partitions.
Now you have to be clear about “how the partitions on external card will be presented in your phone” (their device nodes). In my example (GPT with 7 partitions):
PART 1: 8GB → /dev/block/mmcblk1p1
PART 2: 1.4GB → /dev/block/mmcblk1p2
PART 3: 2GB → /dev/block/mmcblk1p3
PART 4: 400MB → /dev/block/mmcblk1p4
PART 5: 1.4GB → /dev/block/mmcblk1p5
PART 6: 2GB → /dev/block/mmcblk1p6
PART 7: 400MB → /dev/block/mmcblk1p7
As has been mentioned above, mmcblk1p1 is for normal file storage, p2~p4 is for 295, p5~p7 is for 67.
Files that need modding:
(sec1.bin/sbin/ramdisk.cpio) /fstab, /fstab.qcom, /init.target.rc
Click to expand...
Click to collapse
(sec1.bin/sbin/ramdisk-recovery.cpio) /fstab, /fstab.qcom, /etc/recovery.fstab, /etc/twrp.fstab
Click to expand...
Click to collapse
The fstabs are easy to deal with. Just change the block device name for /system /cache and /data to /dev/block/mmcblk1p* accordingly. The init.target.rc has only one line that should be modded. For example,
FOR 9.1.B.1.67 in my example:
ramdisk.cpio/fstab:
/data ext4 /dev/block/mmcblk1p6
/cache ext4 /dev/block/mmcblk1p7
/boot/modem_fs1 raw /dev/block/platform/msm_sdcc.1/by-name/modemst1
/boot/modem_fs2 raw /dev/block/platform/msm_sdcc.1/by-name/modemst2
Click to expand...
Click to collapse
ramdisk.cpio/fstab.qcom:
/dev/block/mmcblk1p5 /system ext4 ro,barrier=1,discard wait,check
/dev/block/mmcblk1p6 /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer
/dev/block/mmcblk1p7 /cache ext4 nosuid,nodev,noatime,barrier=1,discard wait,check
/dev/block/platform/msm_sdcc.1/by-name/SDCard /mnt/int_storage ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check
Click to expand...
Click to collapse
ramdisk.cpio/init.target.rc:
(SEARCH FOR /system)
on post-fs
mount ext4 /dev/block/mmcblk1p5 /system ro remount barrier=1
Click to expand...
Click to collapse
Just do the same for ramdisk-recovery.cpio. For example:
ramdisk-recovery.cpio/etc/recovery.fstab
/boot emmc /dev/block/mmcblk0p4
/system ext4 /dev/block/mmcblk1p5
/cache ext4 /dev/block/mmcblk1p7
/data ext4 /dev/block/mmcblk1p6 length=-16384
/sdcard ext4 /dev/block/mmcblk0p15
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
And replace mmcblk1p5~p7 with p2~p4 then do it all again for 9.2.A.0.295's ramdisk.cpio & ramdisk-recovery.cpio
NOTE: All these fstab and rc files should be rw-r—r-- and owned by root:root. Otherwise the system may fail to boot.
Now repack the ramdisk.cpio, ramdisk-recovery.cpio and then the whole ramdisk.
4. Installing the guest systems
Take notice of the texts in red. Change them to fit your needs.
a. Preparing the guest systemsIf you are installing full stock ROM (FTF format), you can use Flashtool to dump the system image (Flashtool > Tools > Sin Editor, load system.sin from FTF archive and dump data). Then write the image to the sdcard by “dd if=system.ext4 of=/dev/sdb2“ on the computer.
If you are installing ROMs in ZIP format, you need to modify updater-script and replace all (for 9.1.B.1.67 in my example)
/dev/block/mmcblk0p12 or /dev/block/platform/msm_sdcc.1/by-name/System to /dev/block/mmcblk1p5
Click to expand...
Click to collapse
/dev/block/mmcblk0p13 or /dev/block/platform/msm_sdcc.1/by-name/Cache to /dev/block/mmcblk1p7
Click to expand...
Click to collapse
/dev/block/mmcblk0p14 or /dev/block/platform/msm_sdcc.1/by-name/Userdata to /dev/block/mmcblk1p6
Click to expand...
Click to collapse
And
remove /dev/block/mmcblk0p4 or /dev/block/platform/msm_sdcc.1/by-name/Kernel formatting/writing lines
Click to expand...
Click to collapse
Then repack the ROM and push it into phone's internal sdcard.
b. Boot the guest kernel/systemRemember we have zImage and modded ramdisk for each guest system? adb push them to /data partition. The kexec binary is needed as well. Now you can use the kexec binary(check the beginning of this thread) to boot your guest kernel and then recovery.
For example:
I pushed 295 kernel zImage to /data/boot4.3/zImage-stock, modded ramdisk to /data/boot4.3/initrd-stock, and kexec binary to /data/kexec. Now execute as root:
Code:
cd /data
chmod 755 kexec
busybox sync
busybox mount -o remount,ro /system
busybox mount -o remount,ro /cache
busybox mount -o remount,ro /data
busybox sync
./kexec --load-hardboot [COLOR="Red"]./boot4.3/zImage-stock[/COLOR] –initrd=[COLOR="Red"]./boot4.3/initrd-stock[/COLOR] --mem-min=0x85000000 --command-line="`cat /proc/cmdline`"
busybox sync
./kexec -e # phone reboots and guest kernel (295) starts
NOTE: the guest kernel's cmdline may not be exactly the same as the host one. However, it doesn't matter much. 67 and 295 both boot fine using the same cmdline as OmniROM. Since bootloader will append some parameters to the command line, using guest's sec3 without appending these parameters manually is not a good idea.
c. Preparing filesystems and installing ROMs in ZIPAfter the phone reboots, press Vol buttons at purple LED to go into recovery. Now you are in the recovery for your guest system (295).
FORMAT (not wipe) /data and /cache there. For ZIP ROMs you need to format /system as well.
Then install the modded ZIP file if needed. You can also flash SuperSU or anything else to this guest system in the recovery (remember to check if there are wrong block device paths in updater-script).
After finishing the installation of one guest system, reboot and you will go into the host ROM. Execute the commands again and specific the next guest system's zImage and ramdisk to boot into the next guest system. Then do the formatting and flashing things as described above.
5. Boot into guest systems
Once you finish installing all the guest systems, reboot. Then in the host ROM you can execute the commands in Step 4 again to boot into the corresponding guest system. Don't press any key after the reboot. If there's nothing wrong, you will see the bootanimation and then the Android system. Since external sdcards may not be as fast as internal storage, the first boot may take very long time. If you see the bootanimation, just be patient and it will boot up finally.
===========================================================
I know I can't speak English well and it's hard to make myself clear. So if you feel confused, please post your questions here so that everyone who knows the answer will be able to help.
And if you are skilled in Android things, you can choose your own way to achieve the goal:
Partition the sdcard → Mod fstsb and rcs to mount partitions on sdcard to /system etc → Mod the ROM installation script → Boot into guest recovery to format(initialize) data & cache &system and flash ROM → Boot into the guest Android OS
Click to expand...
Click to collapse
This is a little bit complicated. But I do hope this will add more fun to our device
Thanks for your sharing
got it
Although this is labeled for the Xperia TX, after reading through everything, it looks like this works on all devices, you just have to change a few things. Good job putting this together! (Even though I don't have an Xperia TX)
r3pwn said:
Although this is labeled for the Xperia TX, after reading through everything, it looks like this works on all devices, you just have to change a few things. Good job putting this together! (Even though I don't have an Xperia TX)
Click to expand...
Click to collapse
Yeah, it seems that the guide applies to all devices with patched kernels
updateing said:
Yeah, it seems that the guide applies to all devices with patched kernels
Click to expand...
Click to collapse
This guide is nice, full of content, and detailed, but wouldn't it have been easier, though, to just make a MultiROM port?
r3pwn said:
This guide is nice, full of content, and detailed, but wouldn't it have been easier, though, to just make a MultiROM port?
Click to expand...
Click to collapse
I have thought of porting MultiROM, but I'm running a tight schedule...sorry
Whether this Xperia V can also be made from ??
Mircinko96 said:
Whether this Xperia V can also be made from ??
Click to expand...
Click to collapse
It's applicable to Xperia V in theory. But you need a kernel with kexec hardboot patch, which hasn't appeared yet (as far as I have seen). If you know how to compile a kernel, you can try patching the kernel yourself.
.........
do I need linux to unpack kernel?
TWRP 3.0.1-0 with "All-F2FS" support
I have modified the standard TWRP recovery to work with F2FS partitions.
This is different from the previous recoveries that i published.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
Zeus-Kernel.zip (CM12.1) - Here
Zeus-Kernel-MM.zip ( MM ) - Here
recovery-sprout-F2FS-All.img - Here
TWRP 3.0.1-0 Latest - Here
Changelogs:
-29/10/15: Initial Release
-02/04/15 : TWRP 3.0.1-0 Release
To switch your /system, /cache and /data partitions to F2FS follow instructions:
You need:
-Two files you can download above.
-A Android One (Sprout4) device obviously.
-Patience and Time.
Steps:
Flash this recovery with Fastboot (Maybe Flashify, Your wish)
Reboot in new recovery
Backup your /system , /data
(a) Go to Wipe, then Advanced Wipe, Select /System.
(b) Click on "Repair or Change File System"
(c) Click on "Change File System" option
(d) Select F2FS then Swipe to Change.
Repeat steps (a) to (d) with /data and /cache as you did with /system.
Now come back to main screen and go to "Settings"
Select "Use rm -rf instead of formatting."
Go to Restore menu and restore your previously backed up data.
Now Flash the Kernel zip provided above.
Reboot.
Done.
It's easier than it seems.
To restore partitions to stock:
Backup /system and /data
Change File System to EXT4.
Go to Restore menu and restore /system and /data again.
XDA:DevDB Information
[RECOVERY][All-F2FS] TWRP 3.0.1-0 with All-F2FS support, Tool/Utility for the OEM Cross Device Development
Contributors
Swapnil Solanki
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Stable Release Date: 2016-04-02
Created 2015-10-30
Last Updated 2016-04-02
Reserved
Reserved
Yay......
It's here..
Thanks sir...
Thanks I got it resolved..
In the Meantime I'll keep mashing Thanks button...
Could you make a flashable zip for the recovery? Thanks!
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Sure I'll make it soon.
Keep mashing thanks button
Regards.
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
This doesn't change it. It just gives support for it.
No. (Misunderstood your question.)
He said it's for sprout4, but I think it don't wipe that.
vjtigas said:
This doesn't change it. It just gives support for it.
I don't think so.
He said it's or sprout4, but I think don't it wipes that.
Click to expand...
Click to collapse
wait for Op explain this
:cheers
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
austinpinto said:
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
Click to expand...
Click to collapse
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
Yeah, it'll allow you to change the filesystems to F2FS.
It should still be F2FS after flashing KK ROMs. But LP and MM ROMs include an EXT4 image in their zips, so flashing MM or LP ROMs will convert the system partition to EXT4. Data and cache will stay as EXT4.
Formatting data always wipe /data/media. Wiping data with sprout8 recovery keeps /data/media, but as OP says that this is for sprout 4, it'll either not work with sprout8 (not sure) or wipe /data/media if you wipe /data.
hp5942 said:
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Click to expand...
Click to collapse
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
austinpinto said:
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
Click to expand...
Click to collapse
Try reinstalling driver while device is in recovery. I had to install it twice on Win10
Hope that helps
I'm not sure where I'm going wrong. After I converted to f2fs, TWRP straight up refused to mount /system, /data and /cache.
I had to convert it back to ext4 before TWRP would mount them. Can anybody help me out?
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
harsh. said:
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
Click to expand...
Click to collapse
I think Zeus is the only kernel for sprout that supports f2fs. Your safest bet would be to install the latest Zeus(4.5) kernel.
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
krittin98 said:
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
Click to expand...
Click to collapse
No you'll have to do that yourself manually. Recovery is flashed to support mounting of F2FS. Follow instructions given at the beginning of thread and don't forget to flash Zeus kernel given at beginning of thread (mm of lollipop specific depending on your rom). Happy Flashing
I'm unable to take backup as not enough space can I flash system ROM n gapps from SD card after F2FS?
Sent from my Micromax AQ4501 using Tapatalk
Hi,
I made this guideline for those who want to convert filesystem from EXT3 / EXT4 to F2FS on lavendar, for amazing speed & performance.
I already had MIUI EU beta working on my phone.
Note: Internal data storage will be wiped. Make sure to have a backup.
Steps:
1. Install Orange Fox Recovery (latest one)
2. Reboot to recovery
3. Go to Manage Partition
4. Select "Cache" and click orange tick button, then choose F2FS as the file
system and proceed.
5. Again, select "Data" and click orange tick button, then choose F2FS as the file
system and proceed.
6. Reboot to Recovery again.
7. Install a custom kernel which support F2FS (i.e Evira)
8. Install Universal F2FS support patch file. (otherwise causing boot loop)
9. Reboot
Enjoy the speed.>>>>>>>>>>>
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
If you are not so sure (neither am I, I will go research mount command options) then I recommend 3 separate zips
One that's F2FS only for cache and data
One that's all EXT4 for cache and data in case someone needed to revert without reflashing rom
And one that's F2FS cache and EXT4 data because migrating data partition can be a lengthy process for some people. But formatting cache is always easy.
Click to expand...
Click to collapse
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
jalzate94 said:
I had the same problem, to solve it do the partitions process, flash first evira, reboot to recovery again and flash the patch. It worked for me and booted succesfully into the rom. I use xiaomi eu 9.8.9 too.
Click to expand...
Click to collapse
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
Is there actually any benefit at all in using F2FS on Lavender since the flash type is not one of ones supported by F2FS?
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Plast0000 said:
What do you mean when you say that its flash type is not supported by F2FS?
also see these posts:
https://forums.oneplus.com/threads/...o-perfomance-after-formatting-to-f2fs.441177/
https://forum.xda-developers.com/showthread.php?t=2697069
Click to expand...
Click to collapse
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
gardiol said:
See, F2FS works on NAND flash memories.... Lavender ilis NOT a NAND flash, so there is no advantage in using it. At least this is the rationale if I am not wrong.
As speed goes, F2FS is no benefit as your link said, but also for the wear and tear there is not much benefit
Sent from my Note 5 / 5 Plus using XDA Labs
Click to expand...
Click to collapse
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Plast0000 said:
Hmm? according to mi website and wikipedia it uses eMMC 5.1 which is a NAND storage. why wouldn't it work?
As for my link they all agree that F2FS is a bit slower for read but hellalot faster for write. overall gain is considerable.
Click to expand...
Click to collapse
... Well, my info is wrong then... In this case it would be useful
Sent from my Note 5 / 5 Plus using XDA Labs
White_Lion said:
Hi! Filesystem F2FS keeps always even if you make full wipes + format data? For example, if i do the process but later i want to change my device's ROM, system will still have F2FS after wipes and format data? Sorry i've never changed my device's Kernel so i don't know if the system keep the new kernel (and the F2FS support patch file mentioned in this post) after a wipe + format data or they have to be re-flashed. Thank you in advance.
Click to expand...
Click to collapse
No, the data partition will be converted back to ext4 everytime you do "format data".
Not formatting your data could keep the f2fs status, but it's risky to not formatting data when changing ROM in lavender due to it's strict encryption issue.
Plast0000 said:
Did as instructed. got a boot loop : (
Are you sure that fstab flags are properly set? I don't see 'nofail' option or maybe there's some other option that substitutes?
I use miui eu 9.8.9
I reformatted back to EXT4 and it boots again.
Click to expand...
Click to collapse
Miui.eu ROMs doesn't fully support F2FS. The rom does, but the kernel doesn't.
You need to make sure both the ROM and kernel has F2FS support.
if one of them don't, you'll get bootloop.
Plast0000 said:
So I do it like this?
1- change partition fs
2- reboot into recovery
3- flash evira
4- reboot into recovery
5- flash fstab.zip
6- reboot into rom
Click to expand...
Click to collapse
I've been on F2FS since.. April I think, and I've installed and tried so many roms without any problem.
here's what I normally do and it works all the time:
- Make sure data & cache are ext4
- format data
- reboot recovery,
- wipe cache, dalvik, system, data, internal,
- flash firmware
- flash ROM
- flash gapps (optional)
- flash magisk
- flash kernel that has f2fs support (optional, if the rom's kernel doesn't support F2FS)
- reboot system
————————————————————————
it's necessary to install the rom in EXT4 because automatic encryption doesn't work in f2fs partition (I think... based on my experience). granted, you can do the encryption manually from settings, but it's require to have 80%++ battery and the more stuff you have in your internal, the longer it'd take to manually encrypt the device. automatic encryption is just easier to do. You can leave your internal decrypted as well, but you won't be able to use your fingerprint or any screen lock methods. That's just how redmi 7 family works.
————————————————————————
- once you get into system, reboot to recovery once again
- convert cache & data to f2fs
- flash magisk
- flash universal f2fs patch
- reboot
now your /data and /cache are in f2fs.
If you're already on a rom and kernel that support f2fs, you can just do the later half of this tutorial without the need to reinstall rom and everything, but you'd lose all your data. good luck!
What's the benefit of changing cache into F2FS?
begging
Seeking flash tutorial videos
Thanks
thx for guide.
Which custom rom that support f2fs?