i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
billycar11 said:
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
Click to expand...
Click to collapse
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
StefanGA said:
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
Click to expand...
Click to collapse
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
billycar11 said:
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
Click to expand...
Click to collapse
interesting.. how did you do it? I did it in TWRP 2.8.1.0 via advanced wipe and after that got stuck on the motorola bootlogo..
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
billycar11 said:
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
Click to expand...
Click to collapse
I tried it again.. this time it worked.. I rebooted after format directly back into recovery and was then able to restore my data from ext4 to f2fs.. not sure, why it didn't work the first time around, but thanks for checking back!
Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption
Newrooter22 said:
Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption
Click to expand...
Click to collapse
It only wipes /data.
Though, if you use TWRP by Pretoriano80 there's no point as that has decryption.
If you still want to continue you need to Format Data, 'reboot recovery', then remove fileencryption flag in /vendor/etc/fstab.hi3660. (you can pull this file using adb, edit on computer then push it back using adb.).
If you don't edit fstab your phone will re-encrypt on next boot to system.
You will also have to flash Public and HW zip for your firmware as these will be gone (system update ability and themes are stuff that will be gone if you don't flash these.)
Hi guys,
I am in confusion.
Ultimate questions is: why can't my proper TWRP decrypt data? Being under LOS16. Asking me for password I can't provide. I updated Magisk and Viper and got bootloop.
Entering recovery mode, no internal storage, followed the repair file system method with changing file structure to ext2 than to ext4, still no internal storage.
All I want is to recover media files before reflashing LOS.
1. How to decrypt data?
2. Why by default TWRP doesn't do it.
Thanks
DATA partition is by default ext4 or f2fs or something else?
i need help because i did change file system in Twrp option
Hello, i have a Redmi note 9S which shipped with Android 10 out of box.. i'm using Dynamic System Updates (DSU) with unlocked bootloader to try custom roms and decided to modify some custom GSI to manually root it and customize some apps (modifications directly to system partition) but noticed that system partition can't be mounted as rw and gives error "wrong fs type, bad option,.." i can only mount it as ro.
I knew that this happens because ext4 partition formatted with EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (so called ext4 dedup) and this prevent it from being mounted as rw, trying to extend system.img with fallocate and resize ext4 file system with resize2fs and then use "e2fsck -E unshare_blocks" seems to work but the phone can't boot and trying to create a new rw system.img also fail as device doesn't boot, also i noticed that GSI versions with "vndklite" can be mounted as rw but same thing, it fail to boot when flashed with DSU and the device reboot again to the main OS..
So i have two questions here:
1) is that happens because the device refuse to boot system partition without EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS as it's already shipped with Android 10 and support this out of box or this happens because of DSU and will boot if flashed with fastboot?
2) and most importantly how can i modify system.img and then apply EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (apply shared blocks feature on the file system) like what custom roms developers do so i can boot a modded system partition?
Any help would be appreciated.. Thanks!
same question, did you find answer?