NOTE:As i have already moved on to the S6 edge, the amount of support that i can provide would be minimal
THIS IS COMPATIBLE WITH ALL VARIANTS OF THE NOTE 3.
Firstly f2fs can only be used with f2fs compatible KERNEL'S and if you brick your device,Its just because you didnt read and follow the instructions listed from this part of the OP.
Before we start,I would like to thank @psycho4us4 who had allowed me to start a guide thread on the Note3 Forums on f2fs based on his thread from the Note2 http://forum.xda-developers.com/note-2-tmobile/development/how-to-conversion-t2853975
Kernel's with full f2fs support>System,Cache,Data
-Lean Kernel http://forum.xda-developers.com/showthread.php?t=2488082
(Tested)
-Shinto kernel.
http://forum.xda-developers.com/showthread.php?t=2895089
(Tested)
Feel free to inform me on kernels which have full support with all 3 partitions mentioned
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTRUCTIONS FOR CONVERSION OF EXT4 TO F2FS
1.Make sure you have the latest TWRP Recovery on your device(V2.8.1.0 Should be good to go) Get it here> http://teamw.in/project/twrp2
2.In the { Settings } menu of TWRP make sure the [ Use rm -rf instead of formatting ] is unchecked MAKE A FULL, COMPLETE BACKUP with TWRP 2.8.1.0 ( I can't stress this enough if you don't want to use Odin). Keeping in mind that whatever format your partitions are is what format they will be backed up as, such as EXT2, EXT3, EXT4, FAT, F2FS, etc. This will wipe INTERNAL SD so please make a backup of it to your EXT SD CARD/EXTERNAL MEMORY DRIVE.
3. Next from TWRP home, select { WIPE }
4. Then select { ADVANCED WIPE }
5. Then select { CACHE } and click { REPAIR OR CHANGE FILE SYSTEM }
6. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
7. Now select { SYSTEM } and click { REPAIR OR CHANGE FILE SYSTEM }
8. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
9. Then select { DATA } and click { REPAIR OR CHANGE FILE SYSTEM }
10. Then select { Change File System } and select { F2FS }, then SWIPE TO CHANGE. After it formats successfully click { Back }. Then hit the back button for 2 pages until your back at the [ Select Partitions To Wipe page ].
11. Next from TWRP home, click { Settings } then { X } the box that says [ Use rm -rf instead of formatting ].
12. Hit the back button, then select { Restore }. Click on the package you want to restore ( this is the backup you made in step #2 )'
13. Next { X } the boxes { CACHE, SYSTEM, and DATA ONLY }. Then SWIPE TO RESTORE.
14. ALL DONE now just click { Reboot System }
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Just in case you have a problem and you needed to convert back to EXT4,Here is how you do it
INSTRUCTIONS FOR CONVERSION FROM F2FS TO EXT4
1. If you don't already have a backup that you want to use ( backed up with the [ Use rm -rf instead of formatting ] UNCHECKED ) then make one using Step 2 from above instructions.
2. Follow steps 2 through 14 from above, the only thing you have to do different is, instead of choosing { F2FS } for the file format you can choose ANY of the options available as long as the KERNEL you are running supports the format you are switching to.
3. That"s it
3a. If you already have a backup done with the format you desire all you have to do is make sure the [ Use rm -rf instead of formatting ] option is UNCHECKED then restore the { CACHE } AND { SYSTEM } partitions from the package you desire that was made in the format you desire.
3b. The { DATA } has to be done manually by following steps 3, 4, 9, 10 but then hit the back button till your at the TWRP home screen. Next do step 11. Then restore the { DATA } partition from the same backup as mentioned in step 3a.
3c. Reboot and done!
--------------------------------------------------------------------------------------------------------------------------------
sorry to ask that but what's the interest of that manipulation??????
rayman95 said:
sorry to ask that but what's the interest of that manipulation??????
Click to expand...
Click to collapse
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
In my opinion, f2fs would definitely boost the speed of your device or rather smooth it out and help with reliability.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Great. Thanks for the guide. I'm sure you note 3 users will love this.
Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...
adario73 said:
Thank you for this !
Testing right now.
i'll backup everything and save in external microsd, never know ...
---------- Post added at 07:59 PM ---------- Previous post was at 07:35 PM ----------
I receive the message 'FAILED' when attemting to restore the system partition, but only at the and, after restoring all of the 2 GB
going on, maybe it'll work ...
Click to expand...
Click to collapse
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.
psycho4us4 said:
Try slimming down your system partition before you make the backup. It's got to be twrp blocking the restoration of such a large system partition. We have the same issue with the note 2. Only for some users though.
Click to expand...
Click to collapse
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua
psycho4us4 said:
I hear ya. I also think it's time for someone to talk to bigbiff about this issue. Whatcha think @lanchua
Click to expand...
Click to collapse
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
adario73 said:
i think you are right, but my ROM is samsung based, and it is soooo large
i don't know how much i'll be able to trim it.
Thank you anyway !
Click to expand...
Click to collapse
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
Hit me on hangouts.
[email protected]
Ianchua said:
Yeap. We should talk about this, it seems that various devices have various problems restoring system when the file is too big.
What ROM are you on? I will try to emulate this on my Note3.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3
adario73 said:
i'm on XNote ( not the S5 port ), the last version published here ...
thank you for this.
I'm really curious to see the performances of f2fs on note3
Click to expand...
Click to collapse
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Alright. By the way which Variant of the Note3 are you using?
And trust me, the effects is very visible ask the Note 2 guys who used it! They will tell you that its real good! And touchwiz lag? It tamed it
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
you are making me VEEEERY curious !
the variant i have is HLTE N9005
adario73 said:
you are making me VEEEERY curious !
the variant i have is HLTE N9005
Click to expand...
Click to collapse
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Than you should be good to go.
Try this steps,
After formatting one partition and converting it, reboot to recovery before moving on to format and convert other partitions from there.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4
adario73 said:
The only partition that fails ( to restore ) is system.
So, if i well understood, i should try the following :
- format the system partition;
- restart recovery;
- restore the partition from the backup.
ok, i'll try !
thank you again !
EDIT : tried and does not work, reverting again to ext4
Click to expand...
Click to collapse
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Does the back up of your ROM consist of a F2FS compatible kernel? If it does not, than it could be why your system refused to get restored.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )
adario73 said:
At the moment i'm using Ultimate Kernel, which is F2FS compatible.
What if i format using F2Fs and then do a clean install ?
Will i be able to restore a Titanium backup ? ( why not ... )
Click to expand...
Click to collapse
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Ianchua said:
Yes definitely. Just remember to put your TB backup folder in External SD card.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Click to expand...
Click to collapse
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3
adario73 said:
OK, flashing right now on F2FS partition, will report later ( after succesful apps restore )
...
...
not booting ...
clean install failed !!!
...
...
flashed LeanKernel, doesn't boot .
it really seems i can't use F2FS goodness on my Note3
Click to expand...
Click to collapse
Okay. Try this once more,
Try Conerting the System to f2fs first than convert the rest there after.
Reboot to recovery after doing all this
For the restore part. Restore System,cache and data separately with reboot to recovery in between.
Sent from a ELITE S5 Powered Note3 rigged with f2fs awesomeness with Compulsion Kernel. Peace✌
Related
******************* INFO&CREDITS *******************
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) 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.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button
Downloads
********************************************************* Downloads *********************************************************
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch
Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.
Do you run into any issue with this f2fs so far?
LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5
Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go
CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.
delete please
sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is for use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab according to your current partitions and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new TWRP recovery img if you are not already on it.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
Code:
#include
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy ACE 3 LTE. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card (non tested)
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation, Note: Only manual installation is supported, because this mod is not officially supported.
MultiROM has 3 parts you need to install:
MultiROM
Modified recovery
Patched kernel
Now let's head to the installation. Note: Your primary ROM is recommended to be lollipop, because it doesn't act well as a secondary, due to enforcing selinux. Although you can use it as secondary, but change it's selinux status. My setup is Lollipop as primary, and KitKat as secondary. Stock ROM was not tested, because I hate it
I spent about 5 days working on this. My head will explode There is a tiny issue. MultiROM boot menu does not show up as it should. That's why we should use the MultiROM manager apk. and switch ROMs from the app.
Attention: The steps are if you use CM-12.1 as primary ROM
Kernel for Stock ROM with kexec-hardboot patch here
Step 1: Install this patched kernel over CM12.1. Or this, if you want OC.
Step 2: Install the modified Multirom Manager apk, I added support for our device
Step 3: Install Multirom
Step 4: Install MultiROM TWRP, via previous TWRP recovery, it can flash images
Step 5: Reboot into new recovery
Step 6: Install CM11, as secondary ROM!!
Step 7: Go to recovery-->Advanced-->MultiRom-->List ROM-->Choose CM11-->Flash Zip. Flash either stock kernel, or oc_kernel. Both include the necessary kexec-hardboot patch. Usually Multirom requires only primary ROM to have the kexec-hardboot patch, but in our case it does not work this way.
Now you are ready to switch ROMs. Ooh, almost forgot. MultiROM boot manager will show up if you connect the phone for offline charging, you will find out what happens on each case. This is the only bug that I can't resolve yet. Although multirom can be used, with this bug.
Code:
Update 20150829: Download everything from this [URL="https://androidfilehost.com/?w=files&flid=37974"]folder[/URL]
Kernel will be updated when ROM is built
Changelog: Re-implemented kexec hardboot and fixe last_kmsg creation
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
NOTE: If secondary ROM does not boot, select Restorecon under multirom
Click to expand...
Click to collapse
Switch ROMs from the MultiRom manager app
NOTICE: I can't guarantee it will work on other variants rather than "R"
To uninstall Multirom simply flash this
You current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
CM12.1 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-12.1
CM11 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0
Stock kernel for stock rom w/ kexec-hardboot patch - https://github.com/kostoulhs/android_kernel_samsung_loganrelte/tree/master
MultiROM device tree - https://github.com/kostoulhs/android_device_samsung_loganreltexx/tree/multirom
Big thanks to Tasssadar for this awesome utility.
Also thanks @Grarak for the melius patch, i was based on it
Reserved
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Levivig said:
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Click to expand...
Click to collapse
Exactly
Sent from my GT-S7275R
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
F. Dutch said:
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
Click to expand...
Click to collapse
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
kotzir said:
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
Click to expand...
Click to collapse
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
kotzir said:
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
Click to expand...
Click to collapse
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Or just we will never can install ROMs on the SD card ?
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
kotzir said:
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
Click to expand...
Click to collapse
So we will stay do this , just if we install a ROM in the SD card .
Or what ?! :|
OK , after flashing the stock kernel with kexec-hardboot patch, I can't flash any other kernel like arasma kernel in my stock ROM(4.2.2) ?
If I can't .. Can you make a kexec-hardboot patch for arasma kernel ?
Here : http://d-h.st/aYr
Or .. Can you make the lollipop kernel (1.7GHz) work on the stock ROM ?
Sent from my GT-S7275R using XDA Free mobile app
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
zh_eco said:
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
Click to expand...
Click to collapse
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
kotzir said:
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
Click to expand...
Click to collapse
:good::good: Nice Work Man
zh_eco said:
Can I Make My Setup Like This ? :
...my sd card use ext4 partition , is this partition supported ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
May I ask why you do this?
MTP practically destroys any real world benefit that EXT could possibly offer you, and if you use UMS et al you'll hit permissions issues with the media that completely ruin its ability to function as removable storage unless every single one of the systems it touches only has a single user or you carefully craft the system environment so that the user always has the same UID.
It's just weird to use a journalled filesystem with access permissions as removable storage. Either MTP destroys any gains you might possibly get, or UMS makes it impossible to access the contents of the volume on ~99% of all the systems you'll ever encounter in the wild. Ever wondered why you never see external storage volumes with permission based filesystems? This is why. It's largely silly.
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
F. Dutch said:
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
Click to expand...
Click to collapse
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
kotzir said:
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
Click to expand...
Click to collapse
Thanks but the only backups i have of stock are made with CWM. When i try to restore it says .Android_secure.vfat.Tar and .Android_secure.vfat.Tar.a are missing so i can't restore and make a backup with TWRP. Found some info about it and trying tot make it work right now.
kotzir said:
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
Click to expand...
Click to collapse
Thank U Very Much @kotzir For Adding My Videos To "OP"
Small update, check OP
/include/disclaimer or warning.h
/*
* Your warranty is not void as I Think!!
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you, Hard, a Lot $ Lot:laugh::laugh::laugh:
* But I will always be here to HELP! You...
*/
Features
> Made by [email protected]
> Support for all GPT Partitions...:highfive:
> Special EFIDroid Support..
> Secret Tweaks...:victory:
> Specially for Hard Working Dev's like @yoAeroA00...
> Advanced Backup...
> Advanced Restore...:angel:
> Advanced Mounting Points..:highfive:
> Advance Itself...:laugh:
> You tell???
XDA:DevDB Information
yoAeroA00 TWRP 3.0.2.1 Developers Edition Recovery for Nokia X2, Tool/Utility for the Nokia X2
Contributors
yoAeroA00, Lovely Nokia X2 Users & Fans...
Source Code: http://PM me if you need that...
Version Information
Status: Stable
Created 2017-01-22
Last Updated 2019-02-06
DOWNLOADS
Yes! Baby.. Made In INDIA
If you need any kind of live help than come on Slack
> Build's of TWRP 3.0.2.1 :- [20170122]
NOTE: If you need Support for any Awesome Feature than Comment in this Post or PM me... :good::good:
Enjoy!!:laugh:& In response to Continue this Project Push the Thump'sUP!! Bro...:good:
Development Catalogue
>Build 20170122 :- First Initial TWRP 3.0.2.1 Release with a Lot of Custamizations and Features...
is these supporting sdext partition ?
after trying not supported :crying:
frnsl3 said:
is these supporting sdext partition ?
after trying not supported :crying:
Click to expand...
Click to collapse
Use EFIDroid instead of SDExt...:fingers-crossed:
Because if you use SDExt than you need to partition your SD Card from PC but in EFIDroid Partitioning of SDCard is not Required...
yoAeroA00 said:
Use EFIDroid instead of SDExt...:fingers-crossed:
Because if you use SDExt than you need to partition your SD Card from PC but in EFIDroid Partitioning of SDCard is not Required...
Click to expand...
Click to collapse
i need sdext because need more internal storage in ROM , if efidroid can do this can you write some tutorial for this.
thx
frnsl3 said:
i need sdext because need more internal storage in ROM , if efidroid can do this can you write some tutorial for this.
thx
Click to expand...
Click to collapse
It can do more than that...[emoji41]
Like you can customize the size of each partition as per your need...
I had written a guide about it on it's thread..[emoji6]
Sent from my ara using XDA-Developers Legacy app
Good luck bro and thanks
You are new level ... ????
Thx pro .... You are the best of all
yoAeroA00 said:
DOWNLOADS
> Build's of TWRP 3.0.2.1 :- [20170122]
Click to expand...
Click to collapse
How your project is better than this?
SimonVN said:
Recovery Project v3.0.2-0.1
for Nokia X2
Downloads
Flashable ZIP: twrp-3.0.2-0.1-flashable-ara.zip
Recovery image file only: twrp-3.0.2-0.1-20160531-ara.img
Click to expand...
Click to collapse
mirfatif said:
How your project is better than this?
Click to expand...
Click to collapse
I just add sd-ext support for user who want to use Link2SD. I have tried yoAreoA00 TWRP and see there's too many unnecessary partitions. The flashable zip has a bug also (The dd script call the wrong image name, I have to extract it and flash the IMG file myself).
SimonVN said:
I just add sd-ext support for user who want to use Link2SD. I have tried yoAreoA00 TWRP and see there's too many unnecessary partitions. The flashable zip has a bug also (The dd script call the wrong image name, I have to extract it and flash the IMG file myself).
Click to expand...
Click to collapse
Same here. I also flashed the image through RASHR
But backing up Modem partition is a good thing. Also sd-ext support should be added
mirfatif said:
How your project is better than this?
Click to expand...
Click to collapse
Hmm... Again... It is for advanced users specially Dev's and as you guys were reporting errors in networks, sims, .... It supports backing up every partition of Nokia x2 ,ya every.. For future safety.. And even your imei.. And see features list...
Sent from my Nokia ara using XDA Labs
yoAeroA00 said:
Hmm... Again... It is for advanced users specially Dev's and as you guys were reporting errors in networks, sims, .... It supports backing up every partition of Nokia x2 ,ya every.. For future safety.. And even your imei.. And see features list...
Click to expand...
Click to collapse
Personally I liked it and have plan to use it unless a better version is released. So the credit goes to you.
But support for sd-ext might also have been a good addition in case someone has a natural inclination towards 2nd partition.
mirfatif said:
Personally I liked it and have plan to use it unless a better version is released. So the credit goes to you.
But support for sd-ext might also have been a good addition in case someone has a natural inclination towards 2nd partition.
Click to expand...
Click to collapse
I.........Agree:good:
Sent from my Nokia ara using XDA Labs
extractTarFork() process ended with ERROR=255
I'm in trouble
I:
Backed up my (CM11) system, boot, data and cache to SD card using your recovery
Successfully flashed Factory Firmware 2.1.0.13 using NCS
Unlocked bootloader through fastboot
Flashed yoAeroA00-R.img (extracted from yoAeroA00-TWRP-3.0.2.1_20170122.zip) through fastboot
Booted into recovery
Tried to restore my backup
But now I'm continuously getting this error:
extractTarFork() process ended with ERROR=255
Googled a bit and tried following one by one:
Wiped /data by manually selecting FS ext4 from advanced options
Fixed SELinux Contexts
Unmounted /data before restoring backup
Nothing works.
HELP!!!
EDIT:
Issue resolved. I booted to ROM and flashed recovery through RASHR. Everything is normal now
mirfatif said:
I'm in trouble
I:Backed up my (CM11) system, boot, data and cache to SD card using your recovery
Successfully flashed Factory Firmware 2.1.0.13 using NCS
Unlocked bootloader through fastboot
Flashed yoAeroA00-R.img (extracted from yoAeroA00-TWRP-3.0.2.1_20170122.zip) through fastboot
Booted into recovery
Tried to restore my backup
But now I'm continuously getting this error:
extractTarFork() process ended with ERROR=255
Googled a bit and tried following one by one:
Wiped /data by manually selecting FS ext4 from advanced options
Fixed SELinux Contexts
Unmounted /data before restoring backup
Nothing works.
HELP!!!
Click to expand...
Click to collapse
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
yoAeroA00 said:
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
Click to expand...
Click to collapse
Thanks. I flashed recovery through RASHR and everything worked well
Backup / Restore Encrypted /data Partition
yoAeroA00 said:
Data is encrypted so let your phone boot to stock ROM than try restoring data partition...
Click to expand...
Click to collapse
Is there a way to backup / restore encrypted /data partition?
mirfatif said:
Thanks. I flashed recovery through RASHR and everything worked well
Click to expand...
Click to collapse
What do you mean by RASHR??
My brother has got a POCO F1 and, he wanted to format his userdata and cache partitions like me (Mi 6 user here, AEX Pie + Vantom Kernel) to F2FS on his POCO.
What I've tried (and succeeded) is, adding the lines from my fstab file to his fstab.
Here's the steps we've followed:
- We've installed 9.1.24 Global Developer fastboot firmware by using the MiFlashTool (because AEX 6.3's flashable zip gave an error and told us to update to that version in the output).
- Then we've installed OrangeFox 9.0.1 as it also supports F2FS.
- Then I've got that fstab file, added the 2 lines for userdata and cache into it for F2FS, from my fstab (same android versions and kind of identical partition tables like my Mi 6 so, we tried - and succeeded, please follow).
- Then we've formatted the userdata and cache partitions to F2FS in the recovery.
- Then we've flashed AEX 6.3, Sphinx Kernel (looks nice, I may get some ideas from that) and the flashable* (see the attachments, alongside the original fstab from that version) "FSTAB-EXT4&F2FS-encryptable=footer-BERYLLIUM.zip" that I've made for the fstab.
- Then the GApps (particularly, OpenGapps Nano variant) and the other stuff like fonts etc (not important to specify but meh).
Then the system booted just fine, we've tried everything we could imagine to test and it seems working totally fine.
* Because of I was just lazy (lol) and used that old ass ZipMe app to create the flashables below, before flashing them you have to mount Vendor partition from the Mount screen of the OrangeFox/TWRP to get the the new fstab file written successfully.
> Also note that because of the POCO lacks a proper encryption method on F2FS (just like my Mi 6) your userdata partition will remain unencrypted by using this fstab file.
> For any reasons if you'd want to have your original fstab file back (even though this new one would work just fine for default EXT4 too), you can use the other flashable that I've attached below.
I hope this would be helpful for anybody so sharing the steps and ideas.
I think the same idea could be applicable to the combinations of other kernels that support F2FS and (I don't know, if anybody tries it please tell in the comments) even for MIUI (with a kernel that supports both F2FS and MIUI of course).
If you have any questions or suggestions, (preferably) tell in the comments or if you really want, you can also send pm for various reasons.
I hope that support for F2FS gets improved over time so everybody gets to use it on their devices lol, it's the healthy decision for the flash based storages (check the up to date documentations before starting a flame war or I'll ignore your ignorance - I'm just trying to help here and I feel bad for having to state this here explicitly, on my own behalf).
Note that, I'm not responsible for any possible damages/data losses to your phone (you know the drill here at XDA)/thermonuclear war or whatever; so please use your own brain and make your preliminary research and take precautions before trying anything that you aren't familiar with. Thanks.
Did you tried MIUI + Sphinx + F2FS?
Does official twrp support f2fs for poco
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
can i install this on stock miui 10.2.2.0 with custom extreme kernel???
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
Adriano-A3 said:
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Click to expand...
Click to collapse
How did you establish FSTAB EXT4 that works for you?
IronRUS said:
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
How did you establish FSTAB EXT4 that works for you?
Click to expand...
Click to collapse
mount | grep f2fs
Is it possible to modify system to boot f2fs also?? Thanks in advance
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well as i know ,you simply can't, every ROM installation will re-format /system to ext4 automatically
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
You can check the filesystem in Android by some apps like DiskInfo
The system cannot be f2fs since most roms target an ext4 /system partition when installing, so it would always format the system partition to ext4. Eventhough you can backup and restore all of its data once you convert, it would be formated back to ext4 the next time you flash anyway
Jole7 said:
Is it possible to modify system to boot f2fs also?? Thanks in advance
Click to expand...
Click to collapse
It's useless. F2FS is good to random write. /system is entirely read-only.
I will try to make it for system partition as an experiment
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
pipyakas said:
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
Click to expand...
Click to collapse
Performance "degradation" because of formatting data to F2FS? Nope.
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well, your filesystem is itself is the one that's "under the hood". You may notice faster system bootups, app launches and also some in app responsiveness improvements if a particular app is constantly trying to access the storage to record "random" stuff into it's databases.
For system, nope as the others explained before me. I think that it's enough for cache and userdata partitions.
Rommco05 said:
Will attached files works also for Mi8?
Click to expand...
Click to collapse
I don't know, compare the mount points in your current fstab file. If they're similar to F1's then you may try what I've done here.
Dan_Jacques said:
Did you tried MIUI + Sphinx + F2FS?
Click to expand...
Click to collapse
Nope, we stay away from that crap xd but you can try if you wish.
thanhnvt194 said:
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
Click to expand...
Click to collapse
Yes. As long as the mount points stay the same, you can continue to use it.