This is a simple .zip file you can flash on any amami, which uses a ramdisk like the combinedrootfs from Cyanogenmod 11. Your device needs to have a f2fs-compatible kernel, for example this one.
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your system, data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
Ok but... what is f2fs?
It is a new file system, which is especially designed for flash-based storages, like our phones. It will give you much better reading and writing speed.
Installation:
1. Be sure, that you have a f2fs-compatible kernel and your ramdisk's structure is similar to Cyanogenmod's one. If you are on any aosp-based rom, the ramdisk will be compatible anyway.
2. Flash the .zip file from a custom recovery
3. Reboot recovery
4. Now go to advanced wipe and you can change the file systems of system, data and cache to f2fs.
Some more information:
If you convert cache to f2fs:
->No data will be lost
If you convert data to f2fs:
->Your whole internal storage will be wiped. backup your data before you decide to do that!
If you convert system to f2fs
->You need to flash your rom again. You need to modify the updater script of your rom before that like this
OK. I formatted data with f2fs, but want to flash a new rom. What to do?
You need to flash a kernel with f2fs and this zip, no need for any wipes
Download:
http://www.androidfilehost.com/?fid=23578570567713678
For Developers:
You can include this in your rom like this: https://gist.github.com/CoolDevelopment/54ede52a1e075da48151
XDA:DevDB Information
F2FS for amami, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, NovaFusion
Version Information
Status: Testing
Current Beta Version: 2.0
Beta Release Date: 2014-07-16
Created 2014-07-16
Last Updated 2014-07-16
@CoolDevelopment
So, if I corectly understand this zip will erase all data including internal storage? Am I right? But about if I use nightlies? Will I neen to flash it every time after update?
da900 said:
this zip will erase all data including internal storage?
Click to expand...
Click to collapse
It won´t erase your internal storage , I flashed and everthing is there !
pvillasuso said:
It won´t erase your internal storage , I flashed and everthing is there !
Click to expand...
Click to collapse
OK. Thanx. But will erase all data, so I need to install all apps again?
da900 said:
OK. Thanx. But will erase all data, so I need to install all apps again?
Click to expand...
Click to collapse
Nope , it won´t erase any data, files, apps, etc from your internal o external storage
from the OP :
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
CoolDevelopment said:
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
Click to expand...
Click to collapse
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
da900 said:
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
Click to expand...
Click to collapse
You need to flash a f2fs compatiblr kernel and this zip, no wipes
But if you don't do that your rom will bootloop
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
New version!
I uploaded a new version with /system support and a few fixes.
I also updated the op.
Have fun!
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
idimitro said:
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
Click to expand...
Click to collapse
Every rom flashes a boot.img. This boot.img contains a zImage and a ramdisk(on sony devices it is a bit more complicated but that's enough for now).
Using f2fs needs:
1. A zImage(kernel) with f2fs support
2. A ramdisk with f2fs support
This zip modifies the ramdisk for compatibility with f2fs.
You need to flash a f2fs kernel manually.(for example my moshkernel)
And everytime you flash a new rom, you have to modify the contents of the boot.img again
And why don't I just let you flash a modified boot.img? It is only one file.
It would only be compatible with one rom. This is compatible with any rom and boot.img, which uses the ramdisk architecture like cyanogenmod(combinedrootfs).
I hope I could explain it well
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
najar360 said:
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
Click to expand...
Click to collapse
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
CoolDevelopment said:
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
Click to expand...
Click to collapse
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
najar360 said:
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
Click to expand...
Click to collapse
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
CoolDevelopment said:
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
Click to expand...
Click to collapse
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
najar360 said:
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
Click to expand...
Click to collapse
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
CoolDevelopment said:
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
Click to expand...
Click to collapse
yeaps. i'm using 0.1.2 version.
najar360 said:
yeaps. i'm using 0.1.2 version.
Click to expand...
Click to collapse
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
CoolDevelopment said:
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
Click to expand...
Click to collapse
is my step correct?
edit : try slimkat and it work.
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Must have recovery
Got wipe then to advanced and click the box for cache do the wipe
Then go to install find your rom install it then find your kernel and install that then reboot
Kjssplass said:
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Click to expand...
Click to collapse
1. You need a custom recovery.
2. You need a custom recovery.
3. If you need the data from them just copy and paste them. Not only is it not possible without compiling Android, but it is not useful.
4. Since wiping is usualy done with mkfs (or even rm -rf) allocated space will be made.
I have a J710DM/DS. I flashed the latest version of TWRP (TWRP for j7xelte - 3.0.2.1) with no problems.
But when I try to do a backup (to the external SD card), I get the expected "failed to mount /data" errors that result from dm-verity.
TWRP's website talks about this and mentions that some versions have a "System Image" option, but I don't see it on my phone.
So how do I properly do a backup?
This is nothing to do with dm-verity, it's encryption.
Format DATA to remove encryption and then install the boot patch.
My builds of TWRP have image backup, but not sure if I've compiled a j710 version.
ashyx said:
This is nothing to do with dm-verity, it's encryption.
Format DATA to remove encryption and then install the boot patch.
My builds of TWRP have image backup, but not sure if I've compiled a j710 version.
Click to expand...
Click to collapse
Thanks for the information.
What boot patch?
Edit:
Also, what's the recommended way to format DATA? If TWRP can't even mount it, can it even format it?
Haphim said:
Thanks for the information.
What boot patch?
Edit:
Also, what's the recommended way to format DATA? If TWRP can't even mount it, can it even format it?
Click to expand...
Click to collapse
FORMAT *not* WIPE. You don't need to mount to FORMAT.
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
ashyx said:
FORMAT *not* WIPE. You don't need to mount to FORMAT.
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Click to expand...
Click to collapse
Thank you so much for elaborating!
Quick follow-up: I have already flashed SuperSU previously. Will I need to flash it again after formatting DATA?
Haphim said:
Thank you so much for elaborating!
Quick follow-up: I have already flashed SuperSU previously. Will I need to flash it again after formatting DATA?
Click to expand...
Click to collapse
You will need to reflash supersu.
Quick, but vital question:
Does flashing "no-verity-no-encrypt_ashyx" mean that I can now safely restore a full system backup?
Haphim said:
Quick, but vital question:
Does flashing "no-verity-no-encrypt_ashyx" mean that I can now safely restore a full system backup?
Click to expand...
Click to collapse
If you made a backup of an unencrypted data partition then you can restore if /data is mountable.
If you are not restoring /data then it doesn't matter.
Thank you so much for helping me understand all of this. You're the best!
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.)
Help me with this situation
Why can not flash?
Do you Reverted partition to stock partitioning?
Is your recovery an up to date recovery like TWRP 3.2.x,3.5.1, OrangeFox ,SHRP?
sys1admin said:
Help me with this situation
Click to expand...
Click to collapse
That happened to me once when using the reparticioner I had to install the rom 8.1 to my factory phone with odin after the first start I installed the twrp and from there my cell phone started working fine again
sys1admin said:
Help me with this situation
Click to expand...
Click to collapse
First thing is few lineage OS not work on Vendor partition. To over come this use below steps:
Note: Use orange fox recovery for smooth flow
1. Run revert vendor practitioner for exynos 7870.
2. Then reboot to recovery.
3. Goto format option perform format ( This will erase your internal storage data before action this step take a backup)
4. Then navigate to wipe option then wipe Dalivk cache, cache, system, data, internal storage
5. Then install lineage os zip. reboot and enjoy
If you want to install any treble rom in feature better use Universal script. This script make 4096MB system partition, 512MB vendor partition & 57 cache partition