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

Everything about F2FS for our device (Recoveries, patches, info,...)

Alright guys, as most of you most likely already noticed, we are preparing our device to run completely on F2FS. This task, however, needs some information and tools, which I will try to provide in this thread. It is WIP, so don't expect too much yet
First of all, we need a F2FS capable recovery. I have compiled both, CWM and TWRP, but CWM seems to have some issues, so please use TWRP for now
The only ROM running on F2FS for now is our unofficial CM11, but I will update the following list as soon as I get to know about another ROM
Unofficial CM11
To install a F2FS ROM coming from an ext4 filesystem (default), you have to do the following steps:
0) make backups (including titanium backup)
1) flash the F2FS TWRP recovery image
2) manually format /system /data and /cache to F2FS (WARNING: internal sdcard will be wiped as well)
3) flash the F2FS ROM
4) flash GAPPS
5) boot
Regarding custom kernels, if you don't use the default kernel, please don't make bug reports. If we know that the ROM and kernel are working properly, then we can go on. But for now, if you run into problems using a custom kernel, please keep it to yourself.
I assume you will want to restore your data after formatting to F2FS, but keep in mind that if you restore your /data partition via recovery, the old filesystem will be restored as well (ext4). This means, you cannot restore your old backup via recovery. However, if you have a Titanium Backup backup, you sure can restore this.
ROM devs
In order to compile a flashable zip, the updater-script has to be altered. But don't worry, you don't have to do this manually I edited the script creating the updater-script and made a patch, which can be found in the 2nd post
XDA:DevDB Information
F2FS related tools/info/..., Tool/Utility for the LG Optimus 4X HD
Contributors
laufersteppenwolf
Version Information
Status: Stable
Created 2014-06-29
Last Updated 2014-06-30

Reserved
Updater-script patch:
The patch in the attachment patches the updater-script (generator) to be compatible with F2FS partitions (proper mounting and formatting).
Save it inside the build dir, then open a shell and cd to the correct path. Now run "git apply <patchname>.patch" and you're good to go
Example:
Code:
cd /path/to/ROM_sources/CM11/build
git apply F2FS_updater-script.patch
cd ..

@laufersteppenwolf Ok, I'm a bit confused: according to what I'm reading here, and on your unofficial CM11 thread, I assume that /system should be formatted with F2FS using the new twrp recovery you uploaded..but reading what @Demetris and @iodak are saying on iodak kernel's thread, it seems like only /data and /cache partitions will be turned to F2FS, while /system will stay on ext4..the same has been said by @Demetris in the official CM11 thread..so, my question is: are you thinking to try developing in different ways? Just to understand where you are pointing to, and to acquire a clear knowledge about the status of your work Thank you guys!
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

peppethustra said:
@laufersteppenwolf Ok, I'm a bit confused: according to what I'm reading here, and on your unofficial CM11 thread, I assume that /system should be formatted with F2FS using the new twrp recovery you uploaded..but reading what @Demetris and @iodak are saying on iodak kernel's thread, it seems like only /data and /cache partitions will be turned to F2FS, while /system will stay on ext4..the same has been said by @Demetris in the official CM11 thread..so, my question is: are you thinking to try developing in different ways? Just to understand where you are pointing to, and to acquire a clear knowledge about the status of your work Thank you guys!
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't follow iodak's kernel thread, and lately neither the official CM thread, which is why I can't say anything about those discussions. However, all the above info is still correct, as the /system partition still has to be F2FS (you can take a look into our fstab), at least up til now.
And no, I will not go a different was, as my main goal is to keep our device as unified as possible (hence also all various ROM sources on our p880-dev github for slim, gummy,...). All this F2FS stuff is still in a pretty early stage, which is why there can always be changes.

laufersteppenwolf said:
I didn't follow iodak's kernel thread, and lately neither the official CM thread, which is why I can't say anything about those discussions. However, all the above info is still correct, as the /system partition still has to be F2FS (you can take a look into our fstab), at least up til now.
And no, I will not go a different was, as my main goal is to keep our device as unified as possible (hence also all various ROM sources on our p880-dev github for slim, gummy,...). All this F2FS stuff is still in a pretty early stage, which is why there can always be changes.
Click to expand...
Click to collapse
Mmm, yes, it's clear, reading fstab..thank you. The strange thing which took me asking for that question was the discussion between Demetris and iodak in iodak kernel's thread (about using f2fs only for /cache and /data) Anyway, you are the devs, so let's wait
Sent from my LG-P880 - Beanstalk 4.4.4 - Iodak 9.95 kernel - using XDA Premium 4 mobile app

Alright ROM devs, just uploaded the patch to the 2nd post with some quick instructions, but I assume you know how to apply it

laufersteppenwolf said:
Alright ROM devs, just uploaded the patch to the 2nd post with some quick instructions, but I assume you know how to apply it
Click to expand...
Click to collapse
What is a patch? Can i use a brush to apply it? :silly:
Can you make a cwm flashable zip for us? :silly:
Btw because i have a screen protector this can be applied over it or i need to remove it?

Demetris said:
What is a patch? Can i use a brush to apply it? :silly:
You sure can try to use a brush
Can you make a cwm flashable zip for us? :silly:
Yeah, sure, no problem, but first you need to provide me a CWM for my and your PC
Btw because i have a screen protector this can be applied over it or i need to remove it?
Click to expand...
Click to collapse
I'm sorry, but you need to remove your screen protector, your back and your battery in order to apply it...

Yeah make twrp or cwn flashable zip [emoji4]

laufersteppenwolf said:
Updater-script patch:
The patch in the attachment patches the updater-script (generator) to be compatible with F2FS partitions (proper mounting and formatting).
Save it inside the build dir, then open a shell and cd to the correct path. Now run "git apply <patchname>.patch" and you're good to go
Example:
Code:
cd /path/to/ROM_sources/CM11/build
git apply F2FS_updater-script.patch
cd ..
Click to expand...
Click to collapse
Got any guide on doing this, can't seem to find any.

baxtex said:
Got any guide on doing this, can't seem to find any.
Click to expand...
Click to collapse
Well, TBH, I don't know how else to describe
as anothe example, let's say we want to compile CM11, and all sources are in ~/CM11 (you ran the repo init command in ~/CM11)
DL the patch and save it under ~/CM11/build, named F2FS_updater-script.patch
then run the following commands in your terminal:
Code:
cd ~/CM11/build
git apply F2FS_updater-script.patch
then you can compile the ROM as usual, but make sure to run repo sync before applying the patch

Demetris said:
What is a patch? Can i use a brush to apply it? :silly:
Can you make a cwm flashable zip for us? :silly:
Btw because i have a screen protector this can be applied over it or i need to remove it?
Click to expand...
Click to collapse
Hi Revered Developer:
Two questions into one: Is it really worth formating F2Fs, which seems to be yes with a lot of buts, and should we choose Art selected runtime. The ART problem is theoretically ok, better than Dalvik, pratically every time I turn Art on, benchmarks ans subjective feeling od the device got worst: Nexus7Flo and t0lte Note II. We need Xposed installer and surround environment...
http://www.xda-developers.com/search/Art+compilers

using twrp where can i find the option to format /data and /cache to f2fs?
edit: found it, under andvanced wipe

Roms with data and cache f2fs while system ext4
If I have non all-f2fs rom. Can I install it with only data and cache f2fs
Because CM11 is all-f2fs and other roms are not, but @iodak released kernel that is compatible with different f2fs and ext4 combinations.
So what roms I can install with data and cache f2f2 while system is ext4
I'm really confused with this :silly: :silly:

Every normal rom (ext4) can be installed with data or/and cache on f2fs. And you able to update or change rom without problems.

iodak said:
Every normal rom (ext4) can be installed with data or/and cache on f2fs. And you able to update or change rom without problems.
Click to expand...
Click to collapse
Thank you for making this clear to me :victory:

Hey want to ask... I don't have external SD, so if I format to F2FS my internal memory will be wiped right? So, must I push ROM zip to internal memory through ADB to install ROM? or there is any other method?
Thanks.

masmoe said:
Hey want to ask... I don't have external SD, so if I format to F2FS my internal memory will be wiped right? So, must I push ROM zip to internal memory through ADB to install ROM? or there is any other method?
Thanks.
Click to expand...
Click to collapse
1.Right
2.Yes
3.No without SD card

Just for Information: Carbon Rom from animus7 also uses F2FS. And sadly the TWRP is very Buggy for me. I wipe dalvik and it wipe WHOLE /DATA (including /data/media)

Optimissimus99 said:
Just for Information: Carbon Rom from animus7 also uses F2FS. And sadly the TWRP is very Buggy for me. I wipe dalvik and it wipe WHOLE /DATA (including /data/media)
Click to expand...
Click to collapse
Also AOSB ROM is on F2FS ,weird issue tho,did ot happen when you already was on F2FS?
Sent from my LG-V500 using XDA Premium 4 mobile app

[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

[RECOVERY][EXPERIMENT/TEST] TWRP 3.2.1.x for TF701T

Hi, I don't post much on here but I wanted to share something with everyone since this is one of my fav tablets (before one of my drives crash and the data is lost, lol).
Disclaimer: I'm providing this AS-IS, I've been using this for about a few weeks now and while there may be bugs, it's been working for me and figure I'd share a newer version of TWRP for the TF701T. This will need some testing, I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base).
Hopefully this helps someone who loves this lil tegra transformer as much as I do!
I'll post links to source later on but to build this but if anyone wants to try;
-I used a slightly modded version of the zombi-x device tree
-tweaked the rm-wrapper (from the timduru katkiss device tree) so it references the correct includes (I was building under zombi-x 5.1 using omni twrp 8.x)
-Since the device tree was already using a prebuilt kerenel, I plugged the one from the TWRP 2.8.x kang/area51 by sdbags release
-The "rom base" folder I was building under was "zombi-x" 5.1/LP
-and the TWRP sources were from omnirom's oreo/8.x source
Here's a link to my dropbox tf701t folder, I keep a backup in the recovery folder.
I also built a 3.0.0.0 "area51" version, think I found that in the zombi-x repositories also. Both booted, roms I had installed, backups were made and restored under both however I've used the 3.2.1.x version more exetensively.
DROPBOX TF701T LINK!
Anyways, happy holidays everybody! I'll try and keep up with this post and update things when I get a chance, but for now rock on!
PS. Should be able to
Code:
fastboot boot <recoveryimagefile.img>
to test it before flashing permanently with
Code:
fastboot flash recovery <recoveryimagename.img>
PS2. Added images to post for 3.2.1.0 and the "Area51" 3.0.0.0 builds, Enjoy!
PS3. UPLOADED SOURCES! (finally, lol)
DEVICE TREE
-The device tree is still setup to use the prebuilt kernel (I compiled from source posted below this, with gcc 8.x toolchain). If using the kernel source below, use recovery_tf701t_defconfig - otherwise just make sure whatever config you run is setup to use LZMA for ramdisks here.
-Also this device tree is setup to use F2FS, I left the original ext4 fstab files included with a ext4_* prefix if anyone's curious. I'll fix that eventually and split them into 2 branches (ext4-only and f2fs).
KERNEL SOURCE
-This experimental kernel has some tweaks, F2FS support (no encryption), O/C @ ~2.5Ghz, bunch of extra governors (lionheart works nicely), but in it's base form works great for booting recovery.
Hopefully this stuff helps others bulding for this awesome lil tablet! Back to some more compilations while I got time.
UPDATE: F2FS Test (12/30/17)
-Added a recovery build that I have been running for a bit with F2FS support
-Use this with a ROM that supports F2FS, or repack a boot.img with a F2FS kernel and mod the ramdisk (edit fstab to mount /data /system and /cache with F2FS.).
-It supports the usual ext4 and other filesystems, but defaults to f2fs when using the format data and wipe commands (modded fstab on /system /cache /data).
-Also haven't had any issues formatting /cache, or touch not working with this kernel. I'll get around to a normal ext4 version and upload that as it seems to fix the /cache issues.

Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.

hitmancho said:
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
Click to expand...
Click to collapse
Glad it works for you too, I noticed the /cache issue also on the other TWRP 2.8.x version posted for this tablet too. One thing that I do (even on the other TWRP) is wipe the partition I want (or change its fs type) first, and if I need to touch another partition then I reboot the recovery and it works.
It's annoying, I'm currently testing building the kernel inline instead of using the 2.8.x kernel (from that other posted recovery) in the device tree. I'm using sources that I know boot, just playing with the configs to see how it plays with TWRP. I ported over the f2fs stuff from the katkiss kernel to mess around with, boots in the rom fine - so if I can get it to boot recovery then the f2fs formatting stuff should work and mount correctly.
Sidenote - one thing I notice with the 3.2.1-0 version is the screen seems to work better, I haven't had the touchscreen not responsive issue I had with the previous TWRP 2.8.x version.
Going for a coffee, I'll play around with it tonight (and remember to upload stuff to my github eventually to share). Long day of work, time to unwind

Small Update (Progress is good!)
So, took some time to dig around why it wasn't booting the recovery when I built from the same (working) kernel source I'm booting the normal android os with. Turns out, most likely due to space savings, the recovery is set to boot LZMA - turned that on in the config and that kernel now booted up recovery perfectly!
I'm rebuilding the kernel, since in my infinite wisdom, I compiled with my selinux disabled kernel - which also worked, but bombed out on any rom zips that ran anything to do with contexts/perms. Good news was F2FS worked mounting, formatting, etc.. Hopefully tomorrow I'll have a selinux friendly f2fs supporting kernel for recovery that'll work.
Random sidenote: I was eyeing the newer kernel drivers (from 4.x), If everything works as it's currently configured, I'll give try backporting the newer stuff and see how she runs. Just wanted to post a small update with some notes just in case anyone in wants to try building it themselves.

Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.

silverchairbg said:
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
Click to expand...
Click to collapse
I need to reformat /system and /cache only - most times. No need to reinstall apps.

You're lucky then, I always end up with errors on dirty flash and format /data also fails, so I resort to changing FS. Sometimes even this gives errors and I need to do it several times until errors are gone.

I just restart recovery and try formatting again.

AmauryRR great work! Please use the memory card of the docking station

Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).

I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base)
Click to expand...
Click to collapse
Can you, please, describe how it is working?
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Sasisco said:
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
Click to expand...
Click to collapse
Yes, please, more info on that!

Tf701t update
Hi AmauryRR,
Any chance you could break the process down step by step for none-IT people like me? i have tried everything but think i have to accept that this is above my pay grade .
i am especially having a difficult time with the boot loader. Indicates the following: "An unknown error occurs, which may be a network......try again later"
i can email you the screenshots as i can't seem to upload them here.
regards
rob

Can someone get me recovery work in android 4.2.2 ,
10.14.1.47 bootloader please?
"" I searched in google all recovery file can't be downloaded''

Any chance of a flashable version of this?

[ROM][UNOFFICIAL][7.1.2] LineageOS 14.1 - 20200511

DISCLAIMER
By using this ROM, you agree that the developer is not responsible for any physical damage caused to you or your device, or non-physical damage which includes but not limited to:
- broke up with gf due to missed phone calls
- got fired by bossku due to missed alarm
- drove your car into the sea due to faulty GPS
- got caught while traveling in Japan because your camera has no shutter sound
- got last place in kahoot quiz due to device lagging
- accidentally fried the egg due to device overheating
Continue to read this thread only if you agree.
Click to expand...
Click to collapse
LineageOS 14.1 for Samsung Galaxy Note N7000
Beware, you are about to enter a danger zone!
​
ABOUT
This is more of like a learning attempt, as I never build cm-14.1 for n7000 before. Besides that, I think that it might be useful if I can rework the device sources to make it more proper and organized. I hope this build with new security patch will benefit people who wants to stay on cm-14.1.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration: - Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.
The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card.
This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.​2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired.
8. Prepare a coffee or tea and sit back on your couch. Reboot system.
DOWNLOAD
Icedrive
XDA:DevDB Information
LineageOS 14.1, ROM for the Samsung Galaxy Note GT-N7000
Contributors
lee.wp14
Source Code: https://github.com/hikuii
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.3.1-1 (Emulated Storage Compatible)
Based On: LineageOS
Version Information
Status: Testing
Created 2020-05-11
Last Updated 2020-05-26

LineageOS 14.1
LATEST BUILD
lineage-14.1-20200511-UNOFFICIAL-n7000
kernel-4c4d93693090e956abb234bca54368d46be42981
NOT WORKING/UNTESTED
- GPS/AGPS: untested
- DRM: untested
BUILD-SPECIFIC NOTES
- CPU Hotplug is disabled, please monitor battery usage.
- Thermal throttle for CPU is set to 1.2GHz at 69C, stop at 64C. Memory is 90C and stop at 85C.
INSTALLATION NOTES
- Nougat builds have DEXPREOPT disabled as it breaks the system on Exynos platform. Thus, first boot will take longer than usual.
CHANGELOG20200511
- Initial build.
​

Reserved

Thats great

plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????

Adham_android said:
plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????
Click to expand...
Click to collapse
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?

lee.wp14 said:
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?
Click to expand...
Click to collapse
https://b.top4top.io/p_1607stgxn1.jpg

Adham_android said:
https://b.top4top.io/p_1607stgxn1.jpg
Click to expand...
Click to collapse
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.

lee.wp14 said:
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.
Click to expand...
Click to collapse
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?

Adham_android said:
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?
Click to expand...
Click to collapse
Attach a picture of the error after you flash from /tmp.
Or maybe, manually unmount /sdcard1 and flash again from /tmp.
/tmp is not a storage, /tmp is a linux tmpfs, it is not a persistent storage. Think of it as a RAM.

You couldn't just update the assembly from bauner. Security patch. Or can your assembly be put on top of a bauner assembly?

Thanks for this ROM this is the most stable rom i have ever used and it gives me excellent performance much better than samsung own touchlagwiz on jellybean 4.1.1 the only issue i have encountered i the horrendrously bad battery life and overheating the phone gets so hot that you can boil a drop of water on it.
Sorry if I wasted your precious time.
Regards.

Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.

tuxayo said:
Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.
Click to expand...
Click to collapse
I used that Android 9 ROM but lot of times system ask to close or wait apps not responding, so I think it is too slow for daily usage (even with Lspeed and FDE.ai installed).
EDIT: Unfortunately it seems that it cannot install magisk in this ROM
and actually the Lineage 16 build with the LSpeed performance preset and trimming the partitions seems reasonably performant.