Related
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
No it converted to rfs
Sent from my GT-I9003 using XDA App
Ok... What about I wipe date from cwm? Does that revert the partitions back to rfs as well?
I don't think by wiping your data cache u can revert back to rfs. you have to reflash for rfs.
e398rokr said:
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
Click to expand...
Click to collapse
Wiping doesnot changes the partition format. When you flash a new firmware the partitions will be converted to rfs.
send from gt-i9003 using android keyboard
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Lucasred said:
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Click to expand...
Click to collapse
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
sirilpta said:
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
Click to expand...
Click to collapse
Could be the reason, but many guys at another forum did it and it worked perfect for them, i think the error could be in the flash of kph, so the whole process went bad
Lucasred, i had the same problem twice. But i had tried it with XXKPQ.
can i converted file system too ext4 on KPU
google translate
user_i9003 said:
can i converted file system too ext4 on KPU
google translate
Click to expand...
Click to collapse
Yes, I'm using it.
For the others: the restore of the nandroid backup after the conversion failed whenever I tried to convert the phone before deodexing it. Try to deodex first, and then convert.
What I found weird was that the error was "not enough space", but when I tried to restore the backup on rfs it worked, doing the same after the ext4 conversion gave the error. I don't know how you could convert the partitions in ext4 with an odexed rom, I didn't look for any solution, maybe if you don't want to deodex your rom you could try to remove some system apps or something like that before the nandroid backup, in order to get more space.
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.
Is there any guide on how to convert my s7 to f2fs ?
Sent from my SM-G930F using Tapatalk
Go to recovery and simply format your partitions to F2FS. Don't forget about backup. Anyway, I really don't recommend using F2FS on other partitions than system and cache.
F2FS
Hi. DON'T EVER NEVER TOUCH TO SYSTEM !!
Only Data and cache.
Use compatible TWRP and Kernel.
//////////// USE IT AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY FAILURE OR BRICKED DEVICES /////////////////
THIS IS NOT a PUBLICITY for Any ROM or KERNEL
They are Simply just what i use
I have successfully changed my data partition to F2FS and using arter kernel as well
Also I have managed to get the Data back in place so after the whole operation all my ROM data are intact
NOTE THAT YOUR ROM & KERNEL MUST SUPPORT F2FS TO BE ABLE TO BOOT
Note that changing any partition filesystem from a type to another will require formatting that partition
From what i understood converting /system and /cache to f2fs is useless hence I converted /data only as it the main partition that you write on
First of all your internal storage is in /data/media/0 path and hence it will be wiped
I used the official TWRP to be sure of no issues
Take care of the 12th step as if it was missed you will start from scratch >> CRITICAL
Note that Fstab file already contains DFE so if you are unecrypted like my case flashing Fstab keeps me unencrypted without flashing DFE
Now let's start the operation of converstion of/data from ext4 to f2fs in a step by step guide
1- BOOT TO RECOVERY
2- TAKE A FULL NANDROID BACKUP ( MOST IMPORTANT IS THE DATA PARTITION )
3- TAKE A FULL CLONE OF YOUR INTERNAL STORAGE while you are in TWRP( To PC either via MTP or adb command and i prefer the adb method as it ensure that all your files are copied including hidden files )
4- WIPE > Format Data > Yes ( it is a factory reset and all your internal storage will be wiped )
5- Reboot to recovery again
6- Wipe > Advanced Wipe > Check Dalvik , cache , system and Data > Wipe and DONOT reboot to recovery
7- Connect cable again and copy the FSTAB Tools ZIP file only
9- Flash the FSTAB TOOLS File
9- Wipe > Advanced Wipe > Check Data ONLY > Repair or Change file system > F2FS > Change File system
10-Copy via cable whatever you need from your internal storage or the whole of it as your wish
11-Ensure that the TWRP Backup you took in step 2 is copied to internal storage again
12-GO TO TWRP SETTINGS and Tick the 3rd option in the first TAB ( it is called use rm -rf instead of formatting )
13-The above step ensured that when you restore Data partition TWRP won't format it again to ext4 and leave it as f2fs
14-Restore > Choose your fresh Backup > RESTORE DATA PARTITION ONLY ( you will see a message that you are restoring a backup taken of ext4 filesystem , donot worry it worked in my case )
15-Flash the following in order : Vendor > ROM > Fstab File ( NOT the tools one ) > Gapps > Arter97 kernel > Reboot
16-You should boot to the OS with all your data ( settings ) like they were intacted and now the /data partition is f2fs
17-Restore your internal storage if you still didnot do it in step # 10
18-Reboot to recovery and Flash Magisk ( optional )
Notes :
- I though that 4th step was useless however it is mandatory as it erases Vendor or something similar
- I though that 6th step is duplicate to 4th step and was useless however without it TWRP didnot change filesystem to F2FS
- The FSTAB must be flashed after every vendor update ( it can be before or after ROM in the sequence , the most important that it is after every Vendor BEFORE YOU BOOT )
- I didnot flash magisk in step # 15 as crCroid recommends that you boot to system one time before you flash magisk
- crDroid default kernel doesnot support f2fs and if i didnot flash arter97 i wouldnot be able to boot
- By this setup i cannot go back to crDroid default kernel anymore unless f2fs is supported by it
- If ROM doesnot support f2fs the system wouldnot Boot as it would not be able to understand the /data partition filesystem
- Ofcourse any Kernel and ROM combo that supports F2FS should be valid to apply this guide
Finally thanks for all the Devs for thier hard work and dedication , You all made our POCO a lovely BEAST
I think this thread is belong to guides&news and discussion forum
thanhnvt194 said:
I think this thread is belong to guides&news and discussion forum
Click to expand...
Click to collapse
Yes i you are right but do not know how to move thread from a forum to the other
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Is this arter kernel specific? I used shadow kernel and the fstab changes are flashed with the kernel
dgrasley said:
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Click to expand...
Click to collapse
They are in arter kernel thread in the OP
Thread moved to the correct section.
LTT
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
piet8stevens said:
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
Click to expand...
Click to collapse
crDroid Kernel doesnot for now
While the ROM does
What about my apps and its data, can I restore it back?
Edikuun said:
What about my apps and its data, can I restore it back?
Click to expand...
Click to collapse
Read the guide carefully
You will br able to restore everything but the most part that needs patience is restoring internal storage
works on miui ?
RubenPCA said:
works on miui ?
Click to expand...
Click to collapse
Didnot try but saw other users says it works
Which kernels/ROMs are supported?
Shished said:
Which kernels/ROMs are supported?
Click to expand...
Click to collapse
Read in the OP of the ROM / Kernel you want
A lot aupport f2fs now
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Debraj903 said:
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Click to expand...
Click to collapse
Didnot try but I believe it is the same concept
My internal storage went from 30GB free to 15GB free
Edikuun said:
My internal storage went from 30GB free to 15GB free
Click to expand...
Click to collapse
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
shouk_1987 said:
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
Click to expand...
Click to collapse
It's okay now, I forgot to delete my twrp backup and titanium backup. Anyways, nice guide! Successfully converted to f2fs