To try to use F2FS on /system I did these steps
1. Installed F2FS compatible kernel
2. Took TWRP backup of /system
3. Formatted /system as F2FS
4. Enabled use rm -rf instead of formatting in recovery
5. Restored /system backup to the newly formatted F2FS /system
6. Edited /cust/etc/fstab.qcom to mount /system as F2FS
7. Rebooted but phone shuts down during mounting/kernel boot probably due to ramfs trying to mount as ext4 instead of F2FS
ROM is Pixel Experience and kernel is KudKernel.
I don't know how to obtain boot logs on this device since it doesn't have a UART and it crashes too early for ADB to be usable. Being able to obtain logs would be really helpful for this
I'm on AOSP extended Pie (latest) with Englezos kernel.
My cache is f2fs.
I had data as f2fs as well but kept encountering problems, most significantly, Magisk would not function normally.
On my next clean flash I'll just go stock file systems since from what I've read and experienced, the difference in performance is negligible to minimal.
not recommended use f2fs on mido. which is unstable
Related
I've been playing around with which filesystems I can format the android systems partitions and then install a custom ROM on.
I tried formatting them to F2FS and then installing a CM and Squids kernel found it wouldn't boot, then wiped them back and formatted
them to ext4 (which I think is the default android filesystem) and installed CM and Squid's kernel
and now on boot its asking me to enter a password to boot my android system.
partitions were the filesystems were changed are /system /data /cache.
I really don't want to be admitting this right now that I bjorked my system while tinker gnoming,
and don't know enough to put it back.
But yeah formatting ext4 /data /cache /system and then flashing everything back should have done it right?
Damn think I may have run into a bug in the Recovery where no matter what happens it still thinks /data is f2fs even when its been formatted back to ext4
Never mind unbricked it, I think this is the end of late night beer fueled tinkering for me, but I've restored the system.
Should TWRP have been able to format /data to another filesystem besides ext4 or f2fs and which filesystem was the
default on /data from the beginning?
The recovery system seemed to assume that /data was F2FS and even after trying to format it with something different
the repair tool ran was always the F2FS one and always dropped some error messages even after a format to Ext4.
This whole project started when I got the 'good idea' into my head to see if I could format all the partitions that mattered with
F2FS and flash CM 12.1 R53 with Squid's R8 with the partitions formatted F2FS.
Eh I'm done shooting myself in the foot for awhile (or the ass).
Ended with /system (ext4), /data (f2fs), /cache (ext4) and then flashed everything and the system is running great.
The whole experience was worth getting more familiar with TWRP and learning that it is built noob 'tough'.
And can perform awesome awesome surgery for you, when your done shooting your self in the ass.
By the way bro... I think the data partition on this phone comes in f2fs by default
Sent from my MotoE2(4G-LTE) using Tapatalk
I have the same issue!
Fishy.. why in the hell would you do that unless you *found* a phone
and were then trying like a noob to reformat it ?
Hi I tried using F2FS /system on my Redmi Note 4 (mido)
First I flashed a F2FS capable kernel and took a TWRP backup of /system
Next I formatted /system as F2FS
Then I restored the TWRP backup of system after telling it to use rm -rf instead of formatting so it keeps it F2FS
I modified /cust/etc/fstab.qcom to mount /system as F2FS instead of ext4
But when I rebooted to system my phone shutdown during boot which means something went wrong with the mounting
It seems like the kernel or initrd is set to use EXT4. Can someone help me on how to get it to use F2FS ? I don't know how to get UART logs on this phone so that would be helpful too. ADB logcat won't work because it crashes too early
So a few months back, I decided to format my data partition to F2FS and see how it works, so I used orangefox rec. and it successfully changed the data partition from ext4 to F2FS.
But today, I wanted to get back to ext4, and so i went to orangefox and formatted my data partition to ext4. And then i rebooted, But after rebooting, it was still showing F2FS for data partiton, so i again changed file system to ext4 and this time, i formatted data as well. But even after doing that, when i rebooted, it was still showing me F2FS.
So pretty much , Im stuck on F2FS.
Can anyone help me how to fix this? I have used fastboot to try and force change the data partiton to ext4 , but it just gives errors.
Hello,
I own a Xiaomi Redmi Note 10 Pro (sweet). Its bootloader is unlocked and I use TWRP 3.6.1 as recovery. The problem is that when I install a rom (EvolutionX), everything works until I reboot to TWRP. At that point, my recovery is unable to mount the phone's internal storage and it shows as 0 bytes. I have followed a few help topics already, which stated that the solution was to change the data partition format to Ext2, then back to Ext4. However, this makes my phone unable to restart to system. The problem is that when I format my data, the data partition is by default formated as f2fs. I'm guessing that any other data format makes it unable to boot.
So the problem is:
When data is formatted to Ext4, TWRP is able to mount my phone's internal storage and install roms. However, in that case, my phone won't boot to system.
In the other case, my data is formatted to f2fs, which makes my phone totally functional, but my recovery useless. Which means I can't root my phone or update it.
What could I do?
Thanks in advance.
are you mixing up file system type with encryption? if your android is 12, TWRP is not able to decrypt (yet). then just disable encryption and format userdata f2fs (unencrypted).
otherwise claim it to TWRP maintainer he forgot f2fs support.
After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Edit: New thread here. <<<
Try format . Wipe dalvik cache / cache / data
resty1 said:
After installing TWRP and changing file system of /data to EXT2 & EXT4, I can't boot the system (Boot loop?). I can still open up TWRP though. Not sure what to do to fix it.
Device: Nextbook Ares 11a (NXA116QC164)
Click to expand...
Click to collapse
What method do you use for flashing twrp recovery?
Not all devices use ext4. Are you sure this one does?