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
Related
[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]
Hello everybody!
I got inspired by mero01, who made similar tools for my previous mobile phone, the HTC Desire HD.
Imho a new version of an Android ROM should NEVER ever do a full wipe. Personally I prefer to wipe on my own AND to _personally_ have the option which file system is going to be used.
That's why I've created my own zip files, which do either a FULL_wipe or an easy_upgrade_wipe.
These zip files could work on multiple phones, but they are only tested and confirmed to be working on the LG Optimus 2x (P990). Just for the sake I've also implemented a check inside of them if that's the phone, which the wipe(s) are performed on.
**** !NONE WILL FORMAT YOUR SDCARD! ****
I DON'T TAKE ANY RESPONSIBILTY FOR DATA LOSS OR ANY DAMAGE CAUSED TO YOUR DEVICES. USE AT YOUR OWN RISK!!! UNDO IS NOT POSSIBLE!
PREREQUISITES:
* Clockworkmod Recovery (recommended version: v6.0.2.5)
INSTRUCTIONS FOR EVERY FILE:
Code:
1. Download the zip file you want.
2. Place it anywhere in your /sdcard/
3. Reboot into CWM recovery
4. Install zip from sdcard
5. CONFRIM --- CAUTION! THIS IS UNDO-ABLE!!!
6. done :)
7. Don't reboot, flash any rom you want
8. Flash it
9. Reboot and have fun! ;)
FULL_WIPES
This patch comes in two versions (EXT3 and EXT4) and needs to be applied prior to the flash of any ROM. It will WIPE your device and format all partitions either in EXT3 or EXT4.
Wipes performed:
* SYSTEM
* DATA
* CACHE (always EXT3)
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
EASY_UPGRADE_WIPES
These patches also come in the previous two versions (EXT3 and EXT4) and there is an additonal lite variation, which won't wipe your dalvik cache. Use the easy upgrade wipes if you DON'T want to remove your data (especially useful for ROM upgrades)!
Wipes performed:
* SYSTEM
* CACHE (always EXT3)
* non lite versions: Wipes the dalvik cache on DATA
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
NO_JOURNAL
This won't do any wipes, but will remove the JOURNAL(S) on your file systems. If it gets applied to EXT3 partitions it clearly results in EXT2 partitions.
You will get the fastest possible EXT* file systems if it is applied to the EXT4 partitions.
It can also be applied on already existing file systems, although I'd suggest to use a clean file system. Make a backup if you still want to perform it, because it can be dangerous!
Wipes performed:
* NONE
CHANGELOG:
Code:
[U]2014-06-23[/U]
- New LITE easy upgrade wipes available, which won't clean your dalvik cache.
[U]2012-12-10[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.5 (ICS versions only)
- Fixed system partition wipe.
[U]2012-11-27[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.4
- Fixed progress bars.
- Now available in two versions: one for the old (GB), one for the new (ICS) partition layout
- Easy upgrade wipes will now also clean the dalvik cache
- All full and easy wipes re-made from scratch, please use with care and eventually perform a backup before using them.
[U]2011-12-28[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.3
- First public release
************************************************************
[U]2012-12-10[/U]
NO_JOURNAL v0.3 (ICS version only)
- Fixed system partition converting.
[U]2012-11-27[/U]
NO_JOURNAL v0.2
- Fixed progress bars
[U]2011-12-28[/U]
NO_JOURNAL v0.1
- First public release
Have fun!
Greetings,
dr4go
Frequently asked questions (FAQ):
What is the difference between the o and n versions?
The o stands for OLD-, whereas n is an abbreviation for NEW-partitioning layout. Unfortunately LG changed the location of the data partition (from mmcblk0p8 to mmcblk0p9).
so what's the difference between the erase/reset data factory on CWM???
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
koboltzz said:
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
Click to expand...
Click to collapse
Exactly. Thanks for the answer koboltzz.
For the HTC Desire HD there was also an EXT4 version of CWM available, which changed the default algorithms of the "Wipe data/Factory reset" and the "Format" options to EXT4.
But with the latter possibility you loose the ability to format EXT3 partitions. That's also why I always used mero01's zip files to accomplish wipes.
Imho it's the best option, because if you REMOVE the formatting lines from the ROMs you want to flash it's absolutely no problem to also use an EXT3 designed ROM (like Hypnos2X for example) on EXT4 file systems (that's the operating system I'm currently on).
And I tell you also because I dislike the FULL wipes on nearly every ROM available for the LG Optimus 2X. If you have a problem and just want to reinstall the ROM without loosing any data there is no way to do that.
Yes, an easy wipe should always be done by the standard ROM zip itself - of course... but I've always also removed those lines, because that way you also get the freedom of the file system.
It's up to you...
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
Using it and after that flashing Fr19 with ext4 Kernel (from modaco) -> no boot at all ->freezing
This will not happen, if you first do a fullwipe by cwm (ext3), then flash Fr19 and after that use the universal converter to ext4 from benee.
But this only changes data and system partition to ext4 by default.
There is definitely something wrong with the script, an other example:
First flashing 0-full_wipe_0.3_ext4.zip
after that Fr19 ROM (up to this point it would have been a bootfreeze, look above)
and after that flashing universal converter to ext4, phone will boot now, but will not be able to install any app 'there is insufficient space' (which is totally not true), most likely because cache partition is fu.cked up by 0-full_wipe_0.3_ext4.zip
Time for version 0.4
koboltzz said:
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
[...]
Time for version 0.4
Click to expand...
Click to collapse
I will look into it. Thank you for the additional information.
Delete this comment i guess i need to learn how to read im sorry!
dr4go said:
I will look into it. Thank you for the additional information.
Click to expand...
Click to collapse
Anything new to this?
koboltzz said:
Anything new to this?
Click to expand...
Click to collapse
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
dr4go said:
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
Click to expand...
Click to collapse
hey dr4go got something weird here...
when i flash your ext3 zip everything is fine atleast the mount command say so
but then when i want to convert them to ext2 something really weirds occur the system partition becomes ext2 but the data and cache partition become ext4 according to the mount command using recovery 5.0.2.7R2
Here is the convert tool made by Topogigi, and slightly modified by me to include /system conversion.
/cache has not the same parameters it seems.
First (and second) post(s) updated.
And I'll promise you also to release something bigger next time. Guesses won't be commented.
ONly comment I can do is: Nice to see you my friend! How are you?
carburano said:
ONly comment I can do is: Nice to see you my friend! How are you?
Click to expand...
Click to collapse
Everything fine here! Nice to see you too. I finally found some free time and also motivation, because of the marvellously working CyanogenMod 10 on our phones. It's unbelievable... I was nearly freaking out when reading the notice.
And you? How are you? Hopefully everything is also great on your side?
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
spica1234 said:
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thank you. As you may have realized... a little busy as usual... otherwise totally fine. How is it on your side? Everything ok?
cojo11 said:
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
Click to expand...
Click to collapse
What exactly did you do? And which ROM did you try to flash afterwards? Imho the zips should be fixed now - I didn't encounter a single problem since using them.
i try it with ICS 28E and 28G for my Ghostrider Aroma Rom with new Partition Layout,but when i use ext3 or ext4 i got a Bootloop,i put the stuff in the Updater-Script,all runs with Aroma and lokks fine but when i reboot,i got the Bootloop
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
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
F2fs for zuk z1 is here.
This mod works only on cm 14.1 based roms.
The below file contains patched fstab.qcom so you can convert /data and /cache partition to f2fs.
Warning!!!!!!!
Converting /data to f2fs will wipe out entire data partition.
Make sure to backup your entire internal storage partition.
Me or xda will not be held responsible for any of your loss after proceeding with the below instructions.
Requirements:-
1) A rom based on cm 14.1 running Radioactive-kernel 3.20
2) Zuk z1
3)make sure you are on the stock boot image of your rom. If you flashed supersu, restore back to original boot image or dirty flash your rom
4) Proceeding with below instructions will reset your device. Make sure to keep rom zips on pc and backup internal storage.
I can't make it more clear that I'll not be held responsible for the losses due to hou not reading the entire instructions properly.
Instructions :-
1) Download the kernel attached below.
2) Download TWRP (Official 3.1.0-0) and flash it
3) Install the kernel zip i provided.
4) If you want to change only Cache partition to f2fs, boot into twrp, go to wipe, select advanced wipe, select Cache, change fs, select f2fs, swipe to confirm.The rom will be compatible with both ext4 (existing) and f2fs. So you can choose if you want only cache partition or both cache and data
5) If you want to convert data partition, boot to twrp, go to wipe, select advanced, wipe select data, change fs, select f2fs.
6) if you want supersu, make sure to flash it after flashing this kernel. Else your device might bootloop.
Enjoy faster read and write speeds.
Credits :-
All the devs on xda,
Especially @acuicultor and @OrdenKrieger who brought nougat to this device Nd team nuclear
i forgot from where I edited the fstab.
Plz pm me if i forgot anyone's name
Edit :-
Source code
https://github.com/Yrahate7/Radioactive-kernel-HAM
ADDICTEDYASH said:
F2fs for zuk z1 is here.
This mod works only on cm 14.1 based roms.
The below file contains patched fstab.qcom so you can convert /data and /cache partition to f2fs.
Warning!!!!!!!
Converting /data to f2fs will wipe out entire data partition.
Make sure to backup your entire internal storage partition.
Me or xda will not be held responsible for any of your loss after proceeding with the below instructions.
Requirements:-
1) A rom based om cm 14.1 running Radioactive-kernel 3.20
2) Zuk z1 [emoji14]
3)make sure you are on the stock boot image of your rom. If you flashed supersu, restore back to original boot image or dirty flash your rom
4) Proceeding with below instructions will reset your device. Make sure to keep rom zips on pc and backup internal storage.
I can't make it more clear that I'll not be held responsible for the losses due to hou not reading the entire instructions properly.
Instructions :-
1) Download the kernel attached below.
2) Download TWRP (Official 3.1.0-0) and flash it
3) Install the kernel zip i provided.
4) If you want to change only Cache partition to f2fs, boot into twrp, go to wipe, select advanced wipe, select Cache, change fs, select f2fs, swipe to confirm.The rom will be compatible with both ext4 (existing) and f2fs. So you can choose if you want only cache partition or both cache and data
5) If you want to convert data partition, boot to twrp, go to wipe, select advanced, wipe select data, change fs, select f2fs.
6) if you want supersu, make sure to flash it after flashing this kernel. Else your device might bootloop.
Enjoy faster read and write speeds.
Credits :-
All the devs on xda
Click to expand...
Click to collapse
Mate why you open a thread with Radioactive kernel on tittle? Also why you used my kernel without asking permission first? You should make a flashable zip with the modded fstab without my kernel inside. Please do it that way or i will report.
Sent from my Nuclear OnePlus3T
acuicultor said:
Mate why you open a thread with Radioactive kernel on tittle? Also why you used my kernel without asking permission first? You should make a flashable zip with the modded fstab without my kernel inside. Please do it that way or i will report.
Click to expand...
Click to collapse
Sorry man.
I wanted to make sure that you read it.
I'll change it right away.
And regarding the kernel, I've compiled my own kernel based on your source. It has a few mods which u didn't include.
Currently i didn't have a name. So much sorry about it. I i havent uploaded the source as i didn't have any new name.
ADDICTEDYASH said:
Sorry man.
I wanted to make sure that you read it.
I'll change it right away.
And regarding the kernel, I've compiled my own kernel based on your source. It has a few mods which u didn't include.
Currently i didn't have a name. So much sorry about it. I i havent uploaded the source as i didn't have any new name.
Click to expand...
Click to collapse
You know that you are breaking gpl? And why your zip looks exactly same like mine? I can help you if you need just pm me.
Sent from my Nuclear OnePlus3T
acuicultor said:
You know that you are breaking gpl? And why your zip looks exactly same like mine? I can help you if you need just pm me.
Click to expand...
Click to collapse
Yes i know that. But currently i don't have enough internet plan to upload it. I'll upload it asap as my exams are over. I. E. After 12th may
ADDICTEDYASH said:
Yes i know that. But currently i don't have enough internet plan to upload it. I'll upload it asap as my exams are over. I. E. After 12th may
Click to expand...
Click to collapse
You made a fork of Radioactive kernel, right? Then push to github your commits, that's not a lot of data consuming,then share the link here.
Sent from my Nuclear OnePlus3T
This thread is a clear violation of the GPL.
Please upload the source and contact me. I will re-open it then.
As for now thread closed.
Edit: Thread re-opened.
- T W R P 3.2.3-0L [Labs Mod] -
The Swiss Army Knife TWRP Mod for the Axon 7
INTRODUCTION
This was a long term project that I have been using for a long time. I created some scripts to make it easier and faster to flash new roms and quickly restore the daily driver configuration after a testing session. For easier access I modified the TWRP interface to add direct access to the scripts. They had many problems but they were good to me since I created them and I knew how to used them well, but they were not ready for other users.
But the time has come and I have cleaned up most of the annoyances in the tools and in the UI. I have named it "Labs Mod" since it allows me to have my flashing lab on the go, making it extremely easy to switch to different configurations, or recover the daily driver configuration in a few minutes. I believe it is free of major bugs and now I can concentrate on adding new scripts, and more options to the current scripts.
FEATURES
On top of the latest improvements introduced in the official TWRP 3.2.3-0, this mod offers the following added features:
Full vendor partition support (mount, format, wipe, partition image flash, TWRP backup and restore).
Integrated Bootstack backup and restore.
Modem firmware image flash
Reboot to EDL
Button to enable device mapper verity (DM-Verity) enforcing
Button to disable the eMMC write protection (disemmcwp)
Backup/Restore internal storage to the TWRP Backup folder in the external SD. Ensure you have enough free space, free space check is not yet implemented.
EDL backup zip creation. Dual zip use since the resulting zip can be installed using TWRP from the phone or using MiFlash from the computer. It offers the following package creation options:
OS: Operating system (boot, vendor and system).
GPT: Partition table only.
CONFIG: Device config data (IMEI, SN, MAC, etc).
BOOTSTACK: Boot firmware without modem.
MINIMAL: Includes GPT+bootstack+modem+recovery.
EMERGENCY: Minimal + device config.
FULL: Minimal + OS.
FACTORY: Includes Full + config.
Integrated Treble PARTY tool for creating and removing the vendor partition. Vendor partition is required for Treble ROMs. Removal is required for flashing old non-treble roms.
Lockscreen security removal. Removes password, pattern, fingerprint, etc... (in case you forget your password or the security descriptor gets corrupted).
Google account binding removal (in case you want to wipe from within recovery and test with different google accounts).
Bootloader unlock message removal.
New! Expand OS partitions (Vendor and System) to fit the whole partition. Useful for expanding the GSI filesystem for having space for adding GApps or moving apps to system.
New! Deep Wipe function performs a low level wipe of the partition data, erasing the remaining the portions of the eMMC that stored the partition information.
REQUIREMENTS
You need an unlocked Axon 7
INSTALLATION
WARNING, THIS SOFTWARE COULD WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES TWRP CUSTOM RECOVERY IN AN UNLOCKED DEVICE, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
Follow these steps:
1. Download the TWRP Labs Mod image to your External SD card.
2. Boot to TWRP and select the Install option in the main manu.
3. Tap on the install image button and select your external SD. select the image file you downloaded, select the recovery partition and confirm.
4. Reboot to recovery again to ensure the changes are applied properly.
DOWNLOAD
TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod.img Flavor of the mod using the official TWRP 3.2.3-0 Kernel binary (Quick boot even when using F2FS, full ADB support, NO B12 Oreo encryption). Use this if you do not plan on using device encryption. Please note that you won't be able to use any tool of this version if your device is encrypted.
TWRP_3.2.3-0L_v1.3.B12-Axon7-Labs_Mod.img Device encryption enabled flavor of the Labs mod. It use the 3.2.1-8 TWRP Kernel binary (Long boot when using F2FS, NO ADB support, B12 Oreo encryption). Use this one if you use device encryption. Please note that this flavor doesn't support adb interface.
NOTES
1. I do not have the time and expertise to dig into kernel hack so this is why I do not provide a unified kernel with fast F2FS boot, ADB and B12 encryption. Probably people developing kernels could help on this issue. It would be nice having a kernel with proper F2FS boot support, B12 encryption and ADB interface. Until then, there is no other way than having 2 flavors depending on the features we require.
SOURCES
C'mon, all of them are scripts!!! the sources are at glance. Use them in your projects but don't forget to give credit to the source !!!
CREDITS
@NFound for the recovery kernel binary supporting Oreo B12 encryption.
@someone755 for the keycheck binary I use in my scripts.
@Chainfire for the TWRP install script hacks.
I hope you enjoy it as much as I did creating and learning throughout the enlightenment journey.
Nice.
Any info on the scripts that are included?
voetbalremco said:
Nice.
Any info on the scripts that are included?
Click to expand...
Click to collapse
Well, all of them are Bourne shell scripts. Some of them are stupidly simple such as those in the Reboot menu, and others in the Advanced > Oki Labs menu are very elaborated, specially:
- PARTY tool: for creating and removing the vendor partition. I released it a few days ago as a separated tool that could well work in other devices.
- EDL backup: for creating EDL flashable backups of a configuration. This tool will probably require a full thread due to the concepts involved. The big feature is that the generated zip can be also flashed using any TWRP.
- Internal Storage Backup/Restore: TWRP doesn't offer a straightforward solution for backing up the internal storage, since it is excluded from the data backup, now it is possible to create a backup and restore the contents of the internal SD in case you want to mess up with the userdata partition. Now this script creates a set of files under the TWRP/backup folder. I am planning to add the possibility of having different backup folders, the same way the GUI treats the data partition.
That is looking very sweet!!!
I'm excited, nice work man!
This is just fantastic!
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
nfsmw_gr said:
Well, the non b12 version can't decrypt my device, running los 15.1
also, the lab options did nothing, and when I pressed on PARTY the recovery froze on me.
Hmm.
Click to expand...
Click to collapse
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Oki said:
Well, that's why in the OP I provide 2 flavors of the mod. If you require decrypt then you have to use the B12. PARTY will not work either if your device is encrypted and you are using the 3.2.3-0L. In your case, using device encryption, you have to use the 3.2.3-0L(B12). You will have all the functions except for ADB. PARTY will work fine too.
Click to expand...
Click to collapse
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
nfsmw_gr said:
Got it.
I thought the B12 version was for stock-based ROMs.
Okay I'll flash the other one once I get home, thanks.
Click to expand...
Click to collapse
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Oki said:
I'll clarify it a bit more to avoid any misunderstanding. Sorry about that.
Click to expand...
Click to collapse
Thnx for this tool ! I'll test that this weekend.
It would be great if you'd make a small guide on this with a couple of situations / a possible indepth review with screens / what's possible and what's definitely not possible with this twrp tool.
Anyway seems very promising :good:
Sheesh...i have no external sd card
I have garde flashed your TWRP_3.2.3-0L (B12) -Axon7-Labs_Mod.img but this version says when starting in twrp that my password is wrong. the version 3.2.1.8 of nfound unlocks my password quite normal
Excellent Job! I can't wait to get back my Axon 7 from RMA Services. I'm just going to need sometime to get this running coming from stock MIflavor.
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
docentore said:
Found bug. Installed the ADB version (thanks Cthulu!), wanted to check the functionality.
Went into the Storage Backup and my phone froze. Rebooting from ADB worked.
EDIT: tried to reproduce the issue - same thing happened 2nd time.
EDIT2: It freezes at any option in Oki Labs
Click to expand...
Click to collapse
I can't duplicate the issue. Are you sure you downloaded it properly? Do you have an SD card? The backup requires an SD card with enough space. Checking for free space is in the todo list for this weekend.
raystef66 said:
Thnx for this tool ! I'll test that this weekend.
Anyway seems very promising :good:
Click to expand...
Click to collapse
Not good enough!
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
docentore said:
It is downloaded properly. SD card has more than 100gb free space.
As mentioned in edit it is any option that I used in Oki Labs menu that froze my phone
Click to expand...
Click to collapse
What option are you testing? the Storage Backup? What format are you using in your SDCard? Does it happen at the beginning or after a while? Is there any file under TWRP/BACKUPS/STORAGE in your Micro SD after the failure?
@Oki this is amazing. Thank you.
Is it possible to use the recently released kernel sources from los15 to solve the issue of needing two revisions?