Database Develop

[HOWTO] Changing Filesystem to F2FS on the Sprint S4

This guide is for the Sprint Galaxy S4 only and as of now it is only compatible with two kernels: KToonsez S4 Kernel 4.4 AOSP (4/17 or later) and PoKernel 1.7 F2FS ONLY Build. This guide CANNOT be used on Touchwiz or Android 4.3 yet. I will update it when and if that becomes possible
*Disclaimer: You are doing this to your phone under your own consent. This is an experimental procedure and may not work on some hardware revisions or on devices where certain conditions are not met. You assume all the risk by flashing any of the software below or changing your filesystems. I am not responsible if your phone does not work based on the method I am describing below. Modify at your own risk.
This guide had to be updated in order to correct misinformation. The guide will follow KT's instructions explicitly until it gets to the formatting of the system partition
***If you want to format your /system partition to F2FS please read that section first as it requires steps to be taken from your currently working AOSP rom!***
First, go this link download the file:TWRP-KT.ALL-IN-1.zip
http://goo.gl/HLz4al
Formatting Data and Cache to F2FS
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and check the box to force F2FS for data and cache (you can also check the box to include /system partition if you want to convert your ROM's zip to use that too)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
Formatting System Partition with F2FS (Required: KT SGS4 Kernel 4/28 or later!)
Steps:
1.) Before doing any F2FS conversion with the above instructions, use your currently working AOSP ROM to grab the AOSP 4.4 Kernel from HERE (4/28 or later only!) and save it to your external memory card
2.) Once it is saved reboot to recovery and install it (Flashing a kernel in TWRP is Install -> Folder where kernel is -> Click KT 4/28 kernel -> Swipe to install -> Clear cache/dalvik -> Main menu -> click advanced -> Fix Permissions -> Reboot to system)
3.) After you are back in your working AOSP ROM with KT 4/28 kernel installed, download the AOSP rom you want to use and save it to your external sd card (You can leave the filename as it is, the program will rename it for you)
4.) Open KTweaker and click "Tools" and at the very bottom choose "F2FS: Convert ROM ZIP"
5.) It will ask you to locate the file, ask if you're sure, and then it will do the conversion; upon completion the zip file that was created will have "-F2FS.zip" at the end of it
6.) Now you can follow the steps above, but when you get to step 9A you will use the "-F2FS.zip" file instead of the standard ROM file
This procedure is necessary because KTweaker changes your favorite ROM to pass the command mkfs.f2fs so that your system partition is formatted to F2FS before the files are installed. I did this myself to verify and it works a treat. One crucial step to remember though is that after you install your F2FS converted ROM you absolutely must install KT's kernel so your phone will boot.
Returning to EXT4
NOTE: Follow these steps EXACTLY, do NOT add or remove any steps, period!!!!
1. Backup everything from your internal SD to your PC or external SD, since the entire internal SD is going to get wiped out with format!!!!!!!!!!
2. Download the files from the folder that you got these instructions from (Ignore the OLD WAY folder) and SAVE TO THE EXTERNAL SD!!!
3. ONLY DO THIS STEP IF YOU ARE ON AN OLD VERSION OF MY TWRP. Flash TWRP-KT.ALL-IN-1.zip (this is what gives us the ability to format using F2FS)
4. Reboot recovery
5. Go to "Settings" and uncheck the box to force F2FS for data and cache (If you checked the box to include /system partition uncheck it first)
6. Go to "Wipe->Advanced" option and wipe the "Cache" partiton
7. Go to "Wipe->Format Data" option (THIS WIPES YOUR ENTIRE INTERNAL SD CARD, all files and folders, all gone so make a backup to your external SD or PC!!!!!!!!!!!!!)
8. This step you have 2 choices:
A. Flash your ROM/gapps to start completely fresh
B. Go to restore option and ONLY restore your "Data" (you can also restore /system if you are doing the f2fs conversion on /system partition too)
9. ONLY DO THIS STEP IF YOU INSTALLED A NEW ROM. Flash my newest kernel (needs to be a kernel dated 05.05.2014 or newer)
10. DONE!!!!!!!!!!!!!
11. KTweaker has a new option under "Tools" screen to "Get Partition info" to double check your work.
FAQ
Q: Why can't I use this on Touchwiz?
A: It has been developed for the most recent Linux kernel 3.8 and has been implemented in kernels built for 4.4.x OSP builds. This isn't to say it cannot be used on Touchwiz, it is a filesystem and as long as there is a kernel that offers support for reading it installed on your device it should theoretically work on your hardware. However, this can be proven/disproven by the devs here and I will update this answer if it cannot be implemented in a backwards fashion.
Q: Are there advantages to using F2FS?
A: It is built and intended for use on flash filesystems which our devices run exclusively. So since it was developed for flash memory there will be a benefit to using it as it matures. However, this does not imply that benchmarks will increase or your whole phone will become more responsive, its intent is to have files be accessed and written more efficiently. It is supposedly also built for the long-term user who does not constantly reformat their devices because it is supposed to handle large amounts of old files and cleaning more effectively that EXT4. Source: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
Q: Will this trip Knox?
A: No more than installing a custom recovery would. So if you already had a custom recovery (Read: TWRP, PhilZ, CWM) in place you are safe following this guide. For now of course; I do not know if there will be another iteration of Samsung software that locks down the device futher.
Q: Can I clear Cache and Dalvik to troubleshoot after changing my filesystem?
A: I tried this myself and the answer is yes. As long as you are using the F2FS custom recovery made by KToonsez you can wipe Cache and Dalvik from recovery and it will rebuild your system. Something I did notice is that first boot will stay on the splash screen longer with F2FS than with EXT4. I saw it hang on the splash screen of my Liquid rom for an extra minute before actually booting and showing cache rebuild. **Your Mileage May Vary**
Q: Why isn't the System Partition formatted into F2FS?
A: This can be done now with KTweaker. See section above.
Q: What ROMs can I use with this filesystem?
A: Any 4.4.x rom (most are 4.4.2 now) that is compatible with either KToonsez S4 AOSP kernel or Pokernel 1.7 F2FS Only.
Q: In Advanced Wipe, Preload has been added to the options of things to wipe. Should I?
A: Ktoonsez answer found HERE was that he has never wiped preload. So I suggest against it unless you know what you are doing.
Thanks
Linux, Google, and Samsung (all this neat stuff comes from those communities)
TWRP Team for their custom recovery and its updates
Ktoonsez for his awesome kernel and the modified recoveries
CPA Poke for his awesome kernel that has F2FS support baked in
LuigiBull23 for edits and reminding me to add content
XDA for giving us a place to host experimental phone procedures
The XDA Devs for all the work they do for us with their time
The XDA community for providing feedback and making this a great place to hang out
If I forgot anyone specifically please let me know and I will update this section or any section
Enjoy and let us know how it works on your device!

Great guide my friend!

delete

Thanx great guide
Sent from my SPH-L720 using XDA Premium 4 mobile app

Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk

Mistertac said:
Great guide OP! Always nice to have a thread to link to.
I'm sure it's been talked about but your posts doesn't mention the ramdisk files. They're listed but not talked about. Now I'm somewhat limited myself in understanding everything there is to know about these things but are those files to do with eventually formatting the system partition to f2fs?
May be worth putting a little note in there regarding those files... You know how some folks go flash crazy once in recovery lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Hello again.. Lol
The ramdisk mod is now obsolete as it's already included in the kernel zip, which will automatically determine whether you're still on EXT4 or F2FS and make the required changes to the ramdisk accordingly. So no need to flash anything but the kernel as usual after following the steps.

OK yea I figured it was either to do with what I said or to do with the kernel obviously. Just figured I'd ask anyways
Sent from my SCH-I545 using Tapatalk

I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!

I'll be the first to admit that I wasn't entirely sure what the ramdisk files were for. I knew they might have been for advanced users considering they were offered, but not listed in the instructions. I didn't know for sure and I didn't want to use the word "obsolete" because, well, I was so wrong before
I am glad LuigiBull23 jumped in and answered that for us. I'll get it added into the the guide so future users know what they are or are not used for. Keep the questions coming, I love learning about this stuff!
Click to expand...
Click to collapse
I understand. A lot of people were and still are confused about these files..
In short, during the testing phases of F2FS, KT compiled a separate zip for changes to the ramdisk that in turn would reflect the EXT4/F2FS mount points as a means to avoid possible bootloops and such. It was indeed a success and as a result was included in his kernel.
Now, upon flashing the kernel it is able to determine which partitions are formatted as EXT4 or F2FS and mod the ramdisk accordingly. He only left the files on his server in case he ever needed them again. So they are most definitely OBSOLETE. You certainly wouldn't have gone wrong using the term in this case.

Updated the guide for KT's new all-in-one TWRP recovery that will allow you to switch back and forth between F2FS and EXT4. I used his exact instructions from his guide in all areas except for the system formatting section which I wrote. If you are using his custom TWRP recovery go ahead and grab the new one so you can use it in the future!

F2FS with CM11 Nightly
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?

mwilder817 said:
When I used KTweaker to convert my latest CM 11 nightly, it came back and said that it was done but could not find all the lines to modify. Is this ok?
Click to expand...
Click to collapse
I know it has been forever since you posted this and I apologize for the late answer, but I imagine that if you received that error you got a bad download of CM11. I've personally converted the snapshot and several nightlies of CM11 and they all passed nicely.
So for anyone getting this, if you get a similar error message: Re-download the ROM you are converting

to bad its still not possible with touchwiz, love to use f2fs on a stock rom for my sgs4-lte.
is it possible in the near future that we can use f2fs on those devices with a Samsung stock rom, using another kernel is no problem.
or is this hard to tell ?

Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.

RealMikeyTaylor said:
Hello, I've been trying to use this to change my filesystem because I'm coming from CM12 and I'm trying to flash a GPE rom on my S4. But after flashing I am rebooting straight to recovery. Also I'm using the latest TWRP.
Click to expand...
Click to collapse
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!

mwilder817 said:
Make sure you are using a version of TWRP that support F2FS. I don't think the standard issue TWRP does. @AntaresOne has one that does support F2FS and is based on the latest version (2.8.3.0). That's the one I use. Of course, I'm hooked on his CM12 ROM as well. He does really good work!!
Click to expand...
Click to collapse
But doesn't it have to be in EXT4 for it to work for a GPE ROM?

RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
You are probably right. I haven't tried the GPE ROM yet.
Sent from my SPH-L720 using XDA Free mobile app

RealMikeyTaylor said:
But doesn't it have to be in EXT4 for it to work for a GPE ROM?
Click to expand...
Click to collapse
Yup gpe uses ext4 on all partitions because it uses tw framework

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github

reserved
reserved against whatever need

reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.

On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).

bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...

Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.

bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:

bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...

bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.

bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal

xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)

reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.

bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e

andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.

Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.

cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...

Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

How please to format to f2fs

Installed TWRP 2710 and Lollipop 5.1.1 ROM from Jolinnard's thread at http://forum.xda-developers.com/gal.../roms-kernels-nameless-kasper-kernel-t2937458 and very pleased with result.
Jolinnard mentions using f2fs, so I would like to know how to format /cache and /data to f2fs given lack of ability in TWRP 7210 to do this. I think others would find this useful also. Thanks in advance.

Should be under advanced Wipe
Paulantj said:
Installed TWRP 2710 and Lollipop 5.1.1 ROM from Jolinnard's thread at http://forum.xda-developers.com/gal.../roms-kernels-nameless-kasper-kernel-t2937458 and very pleased with result.
Jolinnard mentions using f2fs, so I would like to know how to format /cache and /data to f2fs given lack of ability in TWRP 7210 to do this. I think others would find this useful also. Thanks in advance.
Click to expand...
Click to collapse
You should be able to find it under Wipe -> Advanced Wipe -> select what you want to change and use the button change filesystem.
I don'y know what the Support is for F2FS for different ROMS and Kernels, make sure you read carefully and F2FS is supported.

djcasl said:
You should be able to find it under Wipe -> Advanced Wipe -> select what you want to change and use the button change filesystem.
I don'y know what the Support is for F2FS for different ROMS and Kernels, make sure you read carefully and F2FS is supported.
Click to expand...
Click to collapse
Thanks, but while TWRP 2.7.1.0 does support f2fs (as does the ROM I mentioned in OP), it does not support the functionality you mention, but is the latest TWRP supporting Galaxy Tab 8.9.
I guess that some Gparted Live CD or USB may be the way to go and mounting the Galaxy Tab 8.9 /cache and /data in turn and formatting. I am not knowledgeable enough to work out the full sequence, nor adventurous enough to risk messing up the PC from which I would need to do this.

Guess we have to wait on someone converting twrp 2.8+ for the Tab 8.9

TWRP backup question: system vs system image

Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Edit (1/15/2016):
Thanks to RMarkwald and scryan for the quick responses and info. So it seems that the system image isn't going to be needed, and backing up System, Data, and Boot will be good enough for normal backup of the phone/rom before trying something that might break the current setup.

giantninja said:
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Click to expand...
Click to collapse
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.

I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.

rocco24 said:
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
Click to expand...
Click to collapse
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju

simms22 said:
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
Click to expand...
Click to collapse
Thanks for the explanation. I meant the system.img not the full factory image my bad.

rocco24 said:
Thanks for the explanation. I meant the system.img not the full factory image my bad.
Click to expand...
Click to collapse
the system.img is in the factory.img, just like the boot.img, cache.img, etc..

Nailed it thanks

RMarkwald said:
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
Click to expand...
Click to collapse
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again

giantninja said:
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
Click to expand...
Click to collapse
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...

scryan said:
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
Click to expand...
Click to collapse
Awesome. That's what I was thinking, but I've been wrong before, so it never hurts to verify.
Thanks!

Opps wrong thread... Lol

Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.

cstokes86 said:
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
Click to expand...
Click to collapse
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.

JimSmith94 said:
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
Click to expand...
Click to collapse
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.

I'm in npd90g preview flashed via twrp.if I want official ota
Just flash system image of mm latest and this downgrade doesn't brick my phone ? Can I get ota? And what other should I flash with system image ? Boot ,data and recovery also ?

I dont no much english like othetr peopel
Promblem is i root my honor5x then device get so heat up . After that i deciede to reset it factory setting i have done it but now my device is stuk in twrp loop its not going back normal condition like factory setting plz help me ........ plz

@Shakil jamali: Wrong forum. Go to Honor 5X forum and ask again.

cstokes86 said:
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
Click to expand...
Click to collapse
Good question. Is this system image actually a partition? Or something TWRP does combining the system image part with a few others into one file? If it is a partition would it be possible to delete it and resize system partition to make use of the extra space? I'm on a nextbit robin stock 7.1.1. Sys image shows as 3,072mb.

For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA

soyti2x said:
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
Click to expand...
Click to collapse
First, for your 255 error, look at this post. Get rid of the corrupted file and a normal nandroid will work.
To answer your main question, you can use the system.img as a backup. It is intended for people who want an complete, untouched system backup to restore prior to attempting a OTA update.
An alternative approach to backup/restore that works very well in N6, is Chainfire's FlashFire.

CM13 Encryption and TWRP

In years past on the Nexus 5, I've been able to encrypt my phone and still flash nightlies with TWRP, it would just prompt me for my lockscreen password. When I first got my Victara, there were issues with it, so I just no longer bothered encrypting my phone.
I'd like to start encrypting my phone again with my new job, before I blow my phone up has anyone been successful encrypting with CM13 and TWRP 2.8.7.1 (latest)?

With CM13, TWRP v2.8.7.1 and my Moto X 2014 (XT1096), when my phone was encrypted, upon entering recovery, it would ask me for a password. Unfortunately, no matter what I entered, it wouldn't accept it. I went back to no encryption until TWRP works with it.
If you need encryption, there is a work-around. I copied the build to /cache (vice /sdcard) and was able to upgrade fine with each nightly.

newtoncd said:
If you need encryption, there is a work-around. I copied the build to /cache (vice /sdcard) and was able to upgrade fine with each nightly.
Click to expand...
Click to collapse
Once the update is downloaded to the /cache dir, how exactly do you accomplish the update? Do you follow the typical update method (https://goo.gl/mC6kaN), just doing so with the cache dir?

cableghost said:
Once the update is downloaded to the /cache dir, how exactly do you accomplish the update? Do you follow the typical update method (https://goo.gl/mC6kaN), just doing so with the cache dir?
Click to expand...
Click to collapse
From that URL (section 5 under updating manually), whenever you see /sdcard, just point TWRP recovery to /cache.
Even with encryption turned on, TWRP can see the /cache directory just fine.

newtoncd said:
From that URL (section 5 under updating manually), whenever you see /sdcard, just point TWRP recovery to /cache.
Even with encryption turned on, TWRP can see the /cache directory just fine.
Click to expand...
Click to collapse
Thanks; I'll give it a try.

I was able to encrypt/decrypt CM13 with TWRP 2.8.7.5, but couldn't get it to decrypt after updating to 3.0. Having trouble tracking down a link for 2.8.7.5, but I must have gotten it from somewhere around here.

fsad said:
I was able to encrypt/decrypt CM13 with TWRP 2.8.7.5, but couldn't get it to decrypt after updating to 3.0. Having trouble tracking down a link for 2.8.7.5, but I must have gotten it from somewhere around here.
Click to expand...
Click to collapse
Interesting. I heard from the TWRP Dev directly saying that decrypting was not possible because they did not have a moto x 2014 to work on and create specific code for it.
As long as I can update, that should be okay. I haven't tried the loading update into cache yet, though.
MotoX2014, via TapaTalk