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?
Related
Hi, just reporting my findings on F2FS,
To use system partition in F2FS you need to convert rom, adjust scripts, etc.. so i was trying to find if it worth the hassle
Let's take in consideration two things:
1. F2FS have consistently better write speeds than EXT4 , but the same cant be said for read speeds.
2. EXT4 can become laggy when not trimmed, F2FS is always trimmed,
F2FS makes sense for /data and /cache partition but not for /system... /system partition have almost no changes so its 99% trimmed and usually read only
i used this app https://play.google.com/store/apps/details?id=vog.com.aiv to benchmark bootup time in seconds
CM11 2305 nightly, /data and /cache in F2FS , only change is /system partition format (less is better)
ext4
32,06
28,55
28,01
28,13
27,08
27,77
f2fs
27,44
28,65
40,91
36,95
28,29
27,46
28,41
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
DZeros said:
Even if it is not so good, it is still a step in the right direction.
I will probably try it at some point.
Click to expand...
Click to collapse
F2fs is good, I'm using it, but Just for partitions with lots of writing operations only, simple as that.
And the big plus is that i don't need to worry with compatible roms and updates, just flash any rom updates, without any conversion, and flash kernel after..
Enviado de meu Nexus 4 usando Tapatalk
opssemnik said:
thanks for showing, but i still prefer using f2fs on system because some files in /system get called all time(i.e framework-res.apk),but its not that difference, our nand is already fast.
Click to expand...
Click to collapse
Read times for /system are not faster in f2fs, but it's up to you
Enviado de meu Nexus 4 usando Tapatalk
Thank you for pin pointing this out. A lot of people still believe F2FS will make their phones fly for some reason. I've tested a phone with F2FS next to another running EXT4 and there was no real world performance boost or anything of that sort. F2FS got higher benchmark scores. That's it. Its no a placebo effect but in real world performance it makes no difference.
Sent from my Nexus 4 using XDA Premium 4 mobile app
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
This would explain why there is now a longer than normal delay every single time when I hit the home button that is not noticeable when system is ext4. When on ext4 system this delay was hardly noticeable and with f2fs it seems like there is lag but as soon as it does go home I can then open the app drawer immediately with no lag whatsoever. If it was normally slow or laggy to go home then it took an equal amount of time to open app drawer as the lag existed everywhere, here it is only on the home button.
okanb3 said:
So, i'm on full F2FS. And i agree with your post. Is there anything i must do to use system as EXT4 or just flash not-f2fs-rom ?
Click to expand...
Click to collapse
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
diogo.sena said:
flash any rom, and then flash one of those jolinard f2fs kernels with filename ending in auto.. they work with any partition layout!
Click to expand...
Click to collapse
There must be another way, with this method,the rom doesnt boot.
ashishv said:
There must be another way, with this method,the rom doesnt boot.
Click to expand...
Click to collapse
What rom and what kernel exactly did you use?
diogo.sena said:
What rom and what kernel exactly did you use?
Click to expand...
Click to collapse
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
ashishv said:
I flashed velocity rom, rebooted into recovery again and flashed franko kernel 208 f2fs. The phone didnt get past boot logo.
Then i formatted system, flashed velocity ext4 again, this time without installing kernel. Surprisingly, the rom booted, but the phone was asking password to decrypt storage, ehich left it unusable. So i tried to go back to f2fs rom by formatting system and lashing f2fs velocity, but here again the phone didnt boot past the boot screeen. Finally i had to flash formatpartitions.zip , followed by flashing f2fs velocity, and finally the rom booted. BTW my phone was off for 2 days because of this lol.:laugh:
Click to expand...
Click to collapse
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
diogo.sena said:
Well, at least you solve it, but next time, try to use twrp from multirom thread instead of flashing fromatpartitions.zip, there's a feature to change back and forth between ext4 and f2fs for any desired partition, and use franco from this link
http://mirror.lnx.im/android/mako/franco/
( i used semaphore auto version, but it should work the same way for franco )
Click to expand...
Click to collapse
Twrp with ext4/f2fs format option for mako
http://d-h.st/g59
Multirom app, which will install the recovery without fastboot.
https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
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
I installed the N beta and have to say it was not working for me as I had a few bugs with it. There is a way to easily revert back to MM.
Boot into TWRP.
Go to advanced wipe and select everything including system. (This will delete everything including os from your phone)
Reboot and go into twrp again.
Flash 3.2.8 and SuperSu (optional)
Thats it. No need for any special build as OP said.
Thx for that Info. Have you been on F2fs or on ext4?
In my case I guess i can´t got beta 8 installed and twrp ask for pin did you think if i wipe data and flash 3.2.6 i manage to revert?
Blubber120 said:
Thx for that Info. Have you been on F2fs or on ext4?
Click to expand...
Click to collapse
i was on ext4. to get on f2fs you have to hard reset your device after flashing beta.
Crash said:
In my case I guess i can´t got beta 8 installed and twrp ask for pin did you think if i wipe data and flash 3.2.6 i manage to revert?
Click to expand...
Click to collapse
I think you have enabled pin on bootup. You can try disabling it and then you should be able to get to recovery.
Thx. I am afraid, if on f2fs, it wouldnt be that easy, but good to know that it works if we stayed on ext4
Blubber120 said:
Thx. I am afraid, if on f2fs, it wouldnt be that easy, but good to know that it works if we stayed on ext4
Click to expand...
Click to collapse
you can clean reflash the open beta 8 instead of 3.2.8 which would take you back to ext4 then you can flash 3.2.8.
what is the file system by default in op3 and will installing open beta 8 change file system to f2fs or to ext4?? thanks
Ext4 is default. Whether ob8 changes it or not, i got no aim.
bonham1988 said:
I installed the N beta and have to say it was not working for me as I had a few bugs with it. There is a way to easily revert back to MM.
Boot into TWRP.
Go to advanced wipe and select everything including system. (This will delete everything including os from your phone)
Reboot and go into twrp again.
Flash 3.2.8 and SuperSu (optional)
Thats it. No need for any special build as OP said.
Click to expand...
Click to collapse
Thanks for sharing :good:
Very useful info.
Correct me if I am wrong, but this method to revert back to 3.2.8 will only work only if you have flashed open beta 8 with official twrp as the partition will remain to EXT4.
If you have flashed the update through stock or modded twrp recovery then your system partition will become F2FS so this method to revert back to 3.2.8 will not work as it need EXT4 system partition.
daninantro said:
Correct me if I am wrong, but this method to revert back to 3.2.8 will only work only if you have flashed open beta 8 with official twrp as the partition will remain to EXT4.
If you have flashed the update through stock or modded twrp recovery then your system partition will become F2FS so this method to revert back to 3.2.8 will not work as it need EXT4 system partition.
Click to expand...
Click to collapse
I'm on the latest twrp by eng.stk, twrp-3.0.2-1.28
bonham1988 said:
I'm on the latest twrp by eng.stk, twrp-3.0.2-1.28
Click to expand...
Click to collapse
So I am guessing your system partition is ext4 and f2fs , right? Coz, after a clean flash the system will become f2fs partition (thats what I read)
EDIT: Oh, You need to do hard reset for f2fs..
Also, did you read another thread? the users who did a remote session with OP said that u need some certificate file to downgrade to official OTA. something related to encryption
daninantro said:
So I am guessing your system partition is ext4 and f2fs , right? Coz, after a clean flash the system will become f2fs partition (thats what I read)
Click to expand...
Click to collapse
No it remains on ext4 even after a clean flash. You have do a hard reset to change it to f2fs.
I wonder what happens if file system is changed to f2fs. Should we change the partition to ext4 in twrp before installing OOS 3.2.8?
bonham1988 said:
I installed the N beta and have to say it was not working for me as I had a few bugs with it. There is a way to easily revert back to MM.
Boot into TWRP.
Go to advanced wipe and select everything including system. (This will delete everything including os from your phone)
Reboot and go into twrp again.
Flash 3.2.8 and SuperSu (optional)
Thats it. No need for any special build as OP said.
Click to expand...
Click to collapse
Buddy,
"wipe everything", that includes internal storage.. I read that it's not a good ideea to wipe internal storage.
But, thanks for info.
When you say wipe everything do you also mean internal storage? I really don't want to wipe that if it isn't absolutely necessary.
I am on Arter's CM13 Rom with modified kernel and with cache, system and data, all on f2fs.
What all do i have to keep on f2fs and what on ext4 to install Beta8.
After that i can follow all the steps with modified recovery, right? Or do i have to flash 3.5.5 or Beta7 first?
GaugeX said:
I am on Arter's CM13 Rom with modified kernel and with cache, system and data, all on f2fs.
What all do i have to keep on f2fs and what on ext4 to install Beta8.
After that i can follow all the steps with modified recovery, right? Or do i have to flash 3.5.5 or Beta7 first?
Click to expand...
Click to collapse
I know that the OP3T only uses F2FS for the DATA partition.
All other partitions are EXT4.
So I guess they will probably keep it that way on Nougat.
The beta 8 kernel might actually support F2FS for the other partitions, but without the source code I think you can only try.
Personally I am running Nougat Beta 8 as mentioned with DATA only on F2FS.
it might be a silly question, but now reading a lot about ext4 and F2FS everything I am totally messed up. Below are the confusions/queries-
1. How can I come to know I am on which files system, ext4 or f2fs ? (if I have twrp installed)
2. can it be changed from on to other, if yes, how?
3. Two latest builds - stock 3.2.8 and beta 8 are on ext4 and f2fs respectively, is it correct?
4. If I am on beta8 (flashed via modded twrp), how can I downgrade to stock 3.2.8 ?
I just did a full flash and erase with sweet_global_images_V13.0.12.0.SKFMIXM_20220801.0000.00_12.0_global ROM.
after a quick rom setup with no sim and no wifi, I went back to TWRP and the data partition can't be mounted.
I tried then the usual advanced wipe, setting the partition to ext2 then to ext4 and the rom does not boot and goes back to recovery.
If from recovery I do a wipe, then the rom starts, but after setup, going back to TWRP gives agaion the same problem and the data partition can't be mounted.
Any Idea?
which TWRP version you use?
Zibri said:
....Any Idea?
Click to expand...
Click to collapse
Have you format data partition before starting the new rom?
Format is neccesary to remove the encryption of the formal rom.
Wipe data isn't enough for that.
yes I did... but I think MIUI reformats it.
which twrp are you using?
Maybe the twrp you're using doesn't support encryption yet
it worked with MIUI 12.5.9.. but MIUI 13.0.12 reformats the userdata partition if it is formatted with twrp.
maybe because of dm-verity but I am not sure.
I just did this:
FULL FLASH from EDL or FASTBOOT without relock and including userdata.
Then fastboot boot twrp-3.6.2_11-0-sweet.img
Form TWRP I reformatted userdata as EXT4.
Then booted the system... after booting for the first time the system, userdasta is again encrypted.
Yes, seems u are using twrp which not support decryption yet, change ur twrp/ofox then (there is 1 that already support android 13)
hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
n0te8user said:
hello.my phone is n950F i have problem. my problem is
when i flash stock rom w/odin
then set up twrp this app cant see my internal storage without apply format data or tap change file system ex4 exfat etc.
but i choose format data or repair file system button, mine system is formatting. so i must have flash stock rom odin again.
if i flash stock rom again, twrp cant see my interal storage, 0mb error. again again again. how i flash kernel in twrp on stock rom?
Click to expand...
Click to collapse
If you are using twrp from this thread, it's mentioned on the 3rd post
corsicanu said:
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Click to expand...
Click to collapse
or maybe try to disable data encryption which is mentioned on the 1st post
corsicanu said:
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Click to expand...
Click to collapse
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
ace2nutzer said:
You need to format /data with the "yes" confirmation.
The stock ROM will survive, because it's on /system and /preload.
After that you need to flash a fully patched kernel with removed forced encryption (like a2n kernel) before you reboot to the system. Otherwise the stock kernel will encrypt the /data partition once again.
Click to expand...
Click to collapse
i know i tried this but mine stock rom installed after flashing with odin (turkey) and after apply twrp format data stock rom are very different. the second i said seems like global rom. it contains weird settings and apps I will do what you say and take a screenshot,1 2 hours later you will understand me better.