Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Credits
Phil3759 for his awesome recovery
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Android-Andi for helping with aroma issue
XDA:DevDB Information
[bacon][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the ONEPLUS ONE
Contributors
katinatez
Version Information
Status: Stable
Current Stable Version: 6.59.4
Stable Release Date: 2015-09-22
Last Updated 2015-09-22
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Changelog
Code:
[SIZE="4"]
2015-09-22
Updated 6.59.4
Fixed backup of LOGO partition
2015-09-21
Updated 6.59.3
Added f2fs to system partition
to support 3 partition f2fs backup
2015-05-18
Updated 6.59.2
updated f2fs with Jaegeuk Kim repo
[URL="https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4"]https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4[/URL]
Backup Firmware all 8 partitions, and modem partition named firmware
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware
Compatible backup & restore with unofficial twrp v2.8.6.1 in Philz twrp mode
cm-12.1 kernel
exfat kernel support
f2fs data & cache in fstab
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check
2015-01-31
Updated 6.59.1
switched to cm-12.0 kernel for faster loading
updated recovery.fstab
updated f2fs commits
2014-12-14
6.59.0
add larger font, thanks [user=2661222]@xiaolu[/user]
2014-10-26
6.58.8
Added CM fix for persist partition
Added backup/restore of persist partition
2014-10-13
6.58.7: Source Update and Fixes
merge NTFS sources into recovery
add NTFS check binary (ntfsfix)
compile NTFS binaries as libraries and link them to recovery binary
spares 500Kb space
fix compile error when NTFS is disabled
2014-10-11
Update to developers: v6.58.4
Fixes building errors and issues related to new CyanogenMod changes
2014-10-05
Update 6.58.0
libtouch_gui 1.42
CWM 6.0.5.1
update sources
Fix display turned off on auto dim timer:
Some devices, like Motorola and Nexus, have their screen turned off is brightness is set to 0
add option to define min brightness value at compile time
by default, min brightness value is now 10 instead of 0
2014-09-18
6.57.9
fix install in "Free Browse Mode" from non vold managed volumes
2014-09-14
Update v6.57.8
CWM 6.0.5.1
fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
merge CWM updates to selinux permissions for init services
fix adb for 3.10 kernel
2014-09-13
Faster boot
Fixed usb-otg
Updated F2FS version 3.4.y
2014-09-03
6.57.5
Full F2FS Support
format,mount,read f2fs
Initial Release
2014-08-28
6.57.5
CWM 6.0.5.0
libtouch_gui 1.41
Aroma File Manager fixed
Screenshots fixed
EFS backup
[/SIZE]
DOWNLOADS
Android File Host
I added a couple of more recoveries I built here, but there will be seldom updates if any.
CWM Full Touch recovery now supports aroma file manager loading.
And stock bacon recovery has been updated, it's here for those who want to take it back to stock recovery
Thanks @katinatez
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
gulp79 said:
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
Click to expand...
Click to collapse
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
katinatez said:
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
Click to expand...
Click to collapse
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
gulp79 said:
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
Click to expand...
Click to collapse
@johnnyslt said he would help patch the f2fs, just give us time.
Del
radzmin said:
Del
Click to expand...
Click to collapse
Don't understand. What is the question?
katinatez said:
Don't understand. What is the question?
Click to expand...
Click to collapse
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
katinatez said:
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Click to expand...
Click to collapse
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Phil3759 said:
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Click to expand...
Click to collapse
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
radzmin said:
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
Click to expand...
Click to collapse
Will not work on s4, your in one plus one forum.
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Set up your time in options...
gulp79 said:
Set up your time in options...
Click to expand...
Click to collapse
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Mr Woolf said:
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Click to expand...
Click to collapse
Try with options, have you enabled battery clock? In the options there are some flag to set. For me works, I've to set up time only after option reset
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Correct settings is time settings/Qualcomm time daemon. That should fix your time.
katinatez said:
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
Click to expand...
Click to collapse
:good:
As I thought, the issue is Aroma is no more compatible with many CM kernels
I am not sure about the exact missing part though as I never had an affected device
Related
Team Win Recovery Project 2.4, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Special thanks to toastcfh, the sexy, neckbearded, nice thighed, elite guy that he is, for helping to get TWRP working properly on the S3 Mini.
Reserved!
yayyyyyyyyyyyyyyyyyyyyy
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Aaawwwwweeeeesssoommeeeeee!
Sent from my GT-I8190 using xda app-developers app
Oh yeah! Great work.
So will this work with other versions too? (Specifically the I8190L version )
And my flashable zip again.
Sv: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
tys0n said:
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Benzonat0r said:
And my flashable zip again.
Click to expand...
Click to collapse
I tried this zip.
You are the master!
ExtSd is found here.
All features works pretty cool.
Only the version inside must be upgraded.
Very good work.
Only one thing were so much fun,
Partition sd card..
Good evening
Sent from my GT-I8190 using xda app-developers app
mermigas said:
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
Click to expand...
Click to collapse
Yes, but with rom manager you won't find a recovery for our device because CWM in this forum isn't official build.
Not saying it's no good. xd.bx did a great job, it's just not official
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Trykall8 said:
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Oh, I didn't know it was official CMW! Thats great!
Can you really install TWRP with rom manager?
Isn't it CWM touch?
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Benzonat0r said:
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Click to expand...
Click to collapse
Well the goomanager didn't find anything for my device, I mean didn't find no recoveries.
Sent from my GT-I8190 using Tapatalk 2
It's probably a bug, use my flashable zip.
Also does flashing this recovery increase the binary count?
Sent from my GT-I8190 using Tapatalk 2
If you flash it via CWM or via Terminal with dd if command then no, but if you flash it via Odin yes
And yes there's an official CWM recovery and also CWM touch recovery for our device.
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Dees_Troy said:
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Click to expand...
Click to collapse
ro.product.name=goldenxx
Another port of my custom recovery.
For the aroma file manager option to work you have to flash the zip at least once as the zip file will put aroma in the correct place on your sdcard.
Download ------> cwm6032touch_v15.0.2_m7.zip
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
htc-msm8960 for their device tree
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
Code:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Code:
v15.0.0
- updated to latest cwm source
- added HTC One into the group
Code:
v15.0.1
- fix zip file
[/CODE]
Current Version:
v15.0.2
- update to latest cwm official changes
Click to expand...
Click to collapse
How touch works:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Sounds great - keeping the backup size low is very useful especially when all of the roms are 900+ MBs. I wish there was an easy way to move / still use my TWRP backups.
Thanks... Testing it out now...
Sent from my HTC One using xda app-developers app
Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated
johnblundon said:
Any Idea if this works for the Canadian HTC One on Bell?? I'm not really sure what the differences between the versions are... I tried to install CMW Touch last night and it all seemed to work but when I select recovery it just reboots (twice) and then boots up normally... Sorry Kinda new to the One and installing a recovery
Any help or advice would be greatly appreciated
Click to expand...
Click to collapse
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?
sk8erwitskil said:
hmmm i havent checked out what the differences are between att and bell ones. it might have a different partition layout. how did you install recovery?
Click to expand...
Click to collapse
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.
johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
can you do a:
Code:
fastboot boot recovery.img
scotty2hotty1125 said:
Wanted to let you know flashing the zip via recovery didn't work, but flashing via fastboot worked fine for me.
Click to expand...
Click to collapse
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.
sk8erwitskil said:
can you do a:
Code:
fastboot boot recovery.img
yah i think thats due to the s-on or something. just make sure to flash the zip once so you get the aroma fm feature.
Click to expand...
Click to collapse
The script is to flash boot.img aswell. A bit of a typo!
backfromthestorm said:
The script is to flash boot.img aswell. A bit of a typo!
Click to expand...
Click to collapse
so youre saying you were flashing boot and recovery?
sk8erwitskil said:
so youre saying you were flashing boot and recovery?
Click to expand...
Click to collapse
No, just look at the script in the zip. It's all wrong.
backfromthestorm said:
No, just look at the script in the zip. It's all wrong.
Click to expand...
Click to collapse
ah youre right. thanks for catching that! i just typed the wrong name so it wasnt flashing anything haha. fixed it now
thanks a lot
great recovery with no aroma installer issue
Still don't think it will flash anyway, unless s-off, though you could try dd'ing it like how we flash the boot partition now if the straight flash won't do it.
@sk8erwitskil
Hey which kernel you using for this?
johnblundon said:
Used fastboot method with windows found here: http://forum.xda-developers.com/showthread.php?t=2173863 and used the touch one... not sure about the partition stuff, it gave me all successful messages in CMD prompt but like I said when I go into the bootloader and select recovery it just shows the HTC screen then reboots HTC screen again reboots and boots normally into the system...
Thanks for any help and info you can provide
Click to expand...
Click to collapse
Boot into phone and go into settings and disable fast boot and you should boot into recovery fine.
Thanks I'll try right now
WORKED PERFECTLY!!! THANKS SOOOO MUCH!!!
Flyhalf205 said:
@sk8erwitskil
Hey which kernel you using for this?
Click to expand...
Click to collapse
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.
sk8erwitskil said:
im using a prebuilt one i found on github somewhere. actually, i think it was from htc-msm8960. if you were going to say i need to credit the person i got it from then you are absolutely correct. when i made my thread i just grabbed my other thread as a template and just updated a few things but forgot to update the credits section. ill do that right now. sorry about that.
Click to expand...
Click to collapse
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?
Flyhalf205 said:
I was just curious. Thought someone said they didn't have Aroma issues which was odd because the htc-msm8960 was originally forked from me and my CWM has Aroma issues and I use the stock kernel which so technically you do too.... lol follow me?
Click to expand...
Click to collapse
yah im using the same kernel then. are the aroma issues proven to be kernel related? and i think the person that mentioned aroma was referring to the fact that the installer wasnt build with aroma so they didnt have to deal with that when installing this recovery.
EDIT 05 September 2014: Added fstab.hammerhead formatted for f2fs-all and f2fs-data for those who wish to manually replace the ramdisk's fstab.hammerhead in a kernel to mount the partitions as f2fs.
NOTE: This will only work on kernels that have f2fs tools commited to their kernel image. Make sure the kernel you wish to modify has F2FS support otherwise it WILL NOT WORK!
22 July 2014: Made changes to the Android Kitchen to retain the USB stick mount.
16 July 2014 If you have used any previous version of F2FS ROM CONVERTER prior to the date, please update to the latest version in the links below to correct major errors, to put more fault checks in place and provide better instructions for non Nexus 5 devices to use. Version number is in the Window Title from v0.3.
First off I have to say that I did not create any of these tools but rather I brought them together and I modified them to make it straight forward and easier to format the partitions as F2FS, make a ROM F2FS-ALL and modify a kernel for F2FS-ALL or just F2FS-DATA.
I would suggest you click on each link and click Thanks for each of them.
Thanks and links to the original authors and software.
Hammerhead FSTAB files formatted for F2FS-ALL and F2FS-DATA
Note1: Rename the desired file to fstab.hammerhead to replace the exisiting one in the ramdisk.
Note2: Use Android Image Kitchen to unpack and repack a kernel file (boot.img) during which you can replace the fstab.hammerhead
Note3: Some kernels' updater-script mounts /system or /data as EXT4. Therefore it needs to be modified from the original and added back to the zip.
e.g. Change mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system"); to run_program("/sbin/busybox", "mount", "/system");
and change mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data"); to run_program("/sbin/busybox", "mount", "/data");
Link: http://d-h.st/l87
Download: follow above link
Thanks: kdh2834
Tool: F2FS and F2FS-ALL kernels modified by kdh2834 with help on how to do it. (Actually it was because of him I can now get my N5 running with a full F2FS-ALL ROM and kernel)
Link: http://forum.xda-developers.com/showpost.php?p=52550395&postcount=1
Thanks: osm0sis
Tool: Android Image Kitchen (for unpacking and repacking a kernel)
Link: http://forum.xda-developers.com/showpost.php?p=36067074&postcount=1
Download my version: http://d-h.st/E74
Thanks: TeamWin
Tool: TWRP recovery for formatting the partitions as F2FS (use the latest version)
Note: It can also show the format of a partition in Wipe -> Advanced Wipe
Link: http://techerrata.com/browse/twrp2/hammerhead
Download follow above link
Thanks: Phil3759 and to rootSU for the Nexus builds
Tool: Philz touch recovery for formatting the partitions as F2FS (use the latest version)
Link: http://forum.xda-developers.com/showpost.php?p=48377548&postcount=1
Download: follow above link
Thanks: legolas93's FormatPartitions.zip
Note: These flashable zips need one of the above recoveries to work
Tool: Flashable zips to format the partitions automatically
Link: http://forum.xda-developers.com/showthread.php?t=2678140
Download my version to format all partitions to F2FS: http://d-h.st/RCz
Download my version to format the data partition to F2FS: http://d-h.st/2AI
Thanks: NABENDU1 for F2FS ROM CONVERTER
Note: Mine has been heavily modified for Nexus 5 phones but can be used by any device
Link: http://forum.xda-developers.com/showpost.php?p=52201672&postcount=1
Tool: F2FS ROM Converter v0.5 to make a flashable ROM with F2FS support.
Download my version: http://d-h.st/Uiq
EDIT: Latest version (v0.5) replaced the AOSP F2FS-ALL kernel (boot-f2fs-all.img) as it was not fully F2FS-ALL compatible. Previous version still had /cache partition as EXT4
EDIT: Latest version (v0.4) has support for Slimkat and similar ROMs that need to mount the /data partition.
Instructions
Note: The following steps can be done in any order EXCEPT that step 1. must be done before step 2.
1. Install one of the recoveries.
Note1: If you are on a stock recovery and your phone is locked you will need to backup everything first!
Note2: There is a flashable zip to lock and unlock the boot loader without formatting (only after initial unlock) and Philz Touch Recovery has a password lock as well if you are concerned about security.
WARNING: Before doing the below step, backup your ROM AND your DATA on your sdcard as it will be formatted!
Suggestion: Do an adb pull.
2. Format the partitions using the flashable zips.
3. Use the Android Image Kitchen I provided to modify a kernel with F2FS support. Drag and drop the boot.img on 1_mod_f2fs_kernel.bat file and just follow the instructions.
The kernel can then be installed by sideloading the zip file (see step 4.) or using fastboot from the bootloader (e.g. fastboot flash boot boot.img)
4. Use the F2FS Converter I provided to convert a ROM to mount the /system with a F2FS partition
The ROMs flashable zip will have to be sideloaded (In Philz Touch go to Install Zip -> Install zip from sideload, / In TWRP click Advanced -> ADB Sideload)
Note1: Only needs to be used with a F2FS-ALL kernel.
Note2: There is an option to use your preferred F2FS-ALL kernel as opposed to the default ones.
EDIT: Added which batch script to drop the image file onto in step 3.
Thanks, makes it easy for lazy people like me. Will use it later and let you know how it went.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Волк said:
Thanks, makes it easy for lazy people like me. Will use it later and let you know how it went.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If I missed anything let me know although I tested it to make sure it worked for myself.
Please remember to do a sdcard backup on to your computer. The backups from the the custom recoveries does not back up the sdcard.
Any devs working on a similar method for sgh-I747?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
aircooledbusses said:
Any devs working on a similar method for sgh-I747?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found a TWRP recovery that should support f2fs for your i747 here:
http://techerrata.com/browse/twrp2/d2att
Download the latest version.
Or you can use Philz Touch Recovery but it seems like you will need to build it yourself (if you know how)
Backup everything and move the backups to a computer.
And run one of the format tools according to which partitions will have F2FS (only /data f2fs-data OR /system /data & /cache f2fs-all)
I found one kernel that supports F2FS, there are probably others.
http://forum.xda-developers.com/showthread.php?t=2390147
To answer your question: I am not sure. I am just sharing what I did to make my life easier with others.
These tools will not work for your i747 as they are but I will look into what I can modify to make it work for yours and you can tell me if it works.
If you are getting problems I will see what I can do to help if I have the time.
I will post something when I can.
F2FS-ALL Kernels
You can check http://forum.xda-developers.com/google-nexus-5/development/kernel-f2fs-modified-kernels-t2746951 for some kernels.
The CM kernel was modified by me for F2FS-ALL
You can get it here:
http://d-h.st/1rS
I have modified the ElementalX kernel (ElementalX-N5-1.02-cm.zip) to F2FS-ALL.
Original kernel is here:
http://forum.xda-developers.com/showpost.php?p=47286518&postcount=1
Note1: You need to install the CM kernel above first as the Elemental X uses the ramdisk of the current working kernel, which in this case has the fstab.hammerhead with the f2fs information.
Note2: I had to modify the mount command as well in the updater-script from this:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
to this:
run_program("/sbin/busybox", "mount", "/system");
You can get the working ElementalX 1.02cm F2FS-ALL version here:
http://d-h.st/oEt
Chaos Kernel v13.0 July 08 (nightly) F2FS-ALL - http://d-h.st/h3H
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
GizmoTheGreen said:
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
Click to expand...
Click to collapse
I will look at that kernel later.
If you backup it up using an adb pull, that's what I did not sure about the custom recovery backups as they usually name the backups according to the format, at least for Philz Touch Recovery.
In regards to the stock 4.4.4 with f2fs-all, I just had up a post about that.
Here it is: http://forum.xda-developers.com/showthread.php?t=2791580
GizmoTheGreen said:
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
Click to expand...
Click to collapse
Sorry about the kernel but I only change the ramdisk to set which partitions are to boot with F2FS. So if it doesn't already support F2FS I don't know how to add it. I am relatively new to linux and android. I will like to setup a build environment and learn how to build the kernels and ROMs myself but I have been procrastinating as I need to free up some space on a drive.
Some kernels have the support but are not set up to boot the partitions. I am skimming the forums looking for different kernels to try.
At the moment I am using a CM (CAF based) kernel although there are a lot more ASOP kernels. I will try going to stock to try out some of them.
Huge time reduction!
Thank you for your mod.
Thanks for the great tools!
Could you please provide the modified f2fs-all Elemental X kernel you mentioned earlier? You seemed to have forgotten to post it.
mzheng086 said:
Thanks for the great tools!
Could you please provide the modified f2fs-all Elemental X kernel you mentioned earlier? You seemed to have forgotten to post it.
Click to expand...
Click to collapse
It is in post #7 but it is the caf version. Or did you want the AOSP version?
dechronic said:
It is in post #7 but it is the caf version. Or did you want the AOSP version?
Click to expand...
Click to collapse
I might have missed something obvious. In that case, please point it out to me. In post #7, I only see a link to the original thread of Elemental X kernel, and two links to the modified CM11 kernel. But there is no link to modified Elemental X kernel.
mzheng086 said:
I might have missed something obvious. In that case, please point it out to me. In post #7, I only see a link to the original thread of Elemental X kernel, and two links to the modified CM11 kernel. But there is no link to modified Elemental X kernel.
Click to expand...
Click to collapse
Oh shoot you are right. I don't how come I posted the same kernel twice. Uploading it now. I will edit that post and copy the link into the next post once I am done and I also have a link for Chaos-Kernel_v13.0-[07-08]-[11-16]-f2fs-all.zip (nightly) which I will post shortly too.
---Copied from Post #7--
You can get the working ElementalX 1.02cm F2FS-ALL version here:
http://d-h.st/oEt
Chaos Kernel v13.0 July 08 (nightly) - http://d-h.st/h3H
I tried your version of the tools on CharizardX (AOSP) kernel and this 4.4.4 stock rom. http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
it failed to mount my data partition and I got a 128mb temp ramdrive at each boot... not sure what went wrong.
temp booted cwm recovery to reformat back to 4ext and then philz to restore my backup from usb drive, so I'm back at a working system...
edit:working now with your kernelupload in the other thread, but I can't seem to get superuser working, flashing koush's superuser via .zip. also I et a bootloop running antutu... probably kernel. what AOSP kernel do you recommend? I'd love to use faux's but last I heard there was trouble with wifi for some reason...
GizmoTheGreen said:
I tried your version of the tools on CharizardX (AOSP) kernel and this 4.4.4 stock rom. http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
it failed to mount my data partition and I got a 128mb temp ramdrive at each boot... not sure what went wrong.
temp booted cwm recovery to reformat back to 4ext and then philz to restore my backup from usb drive, so I'm back at a working system...
edit:working now with your kernelupload in the other thread, but I can't seem to get superuser working, flashing koush's superuser via .zip. also I et a bootloop running antutu... probably kernel. what AOSP kernel do you recommend? I'd love to use faux's but last I heard there was trouble with wifi for some reason...
Click to expand...
Click to collapse
Honestly, I only just started using F2FS in the last week or so. I haven't tried an AOSP Roms yet to try out the AOSP kernels.
I just downloaded Slimkat as the script mounts the /data partition as well, so I have modify my script to account for that. I will try out some AOSP kernels that I will mod for F2FS-ALL and let you know what I got to work.
dechronic said:
I just downloaded Slimkat as the script mounts the /data partition as well, so I have modify my script to account for that. I will try out some AOSP kernels that I will mod for F2FS-ALL and let you know what I got to work.
Click to expand...
Click to collapse
You should be able to remove that mount if the user already has /data on f2fs, since data isn't normally formatted, and hence fully wiped and unmounted. If the user is migrating to f2fs, then, yes that would need to be changed. Also, ROM scripts format /system to ext4, which has to be removed or changed to the f2fs command.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Волк said:
You should be able to remove that mount if the user already has /data on f2fs, since data isn't normally formatted, and hence fully wiped and unmounted. If the user is migrating to f2fs, then, yes that would need to be changed. Also, ROM scripts format /system to ext4, which has to be removed or changed to the f2fs command.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The script searches for the mount /data command because as was pointed out to me, some ROM scripts mount it. Particularly Slimkat. It only changes it if it finds it. Otherwise it is ignored. If the the ROM is selected to be reconfigured as F2FS-ALL then it looks for any format /system, mount /system and mount /data commands. If is set to reconfigured as F2FS-DATA then only the /data is mounted as F2FS if required by the ROM's updater script
Sent from my Nexus 5 using XDA Free mobile app
Hi there!
Today I finally found how to make our codinas' kernels universal, i.e. allow to install kernel on whatever ROM and finally separate recovery from kernel. It's well known, bootloader decides what will be loaded - kernel or recovery. That probably may explain why AnyKernel installer(or other similar) doesn't work on codina, because we can't move recovery partition anywhere.
But there is also a little trick that allow us load recovery and boot.cpio from different partition - https://github.com/ChronoMonochrome/Chrono_Kernel/commit/df9094f1f12618ad9599da266792d6b2f8106170 - just an another approach
Don't worry, we won't touch bootloader at all.
As can be seen, /dev/block/mmcblk0p17 (kernel2 partition) will be used for storing recovery.cpio and boot.cpio. On stock that may not work (I don't know for what exactly uses Kernel2 partition, besides of manually restoring of kernel1 partition. I only know that is almost useless on custom ROMs, and we can use it as we want )
First do some preparations:
Download this kernel and needed recovery/boot scripts(4.4.x.cpio.zip, 4.4.x_f2fs.cpio.zip, etc... 4.4.x.cpio means that it support only ext4) from my google drive (folder ramdisks), unzip recovery (twrp or cwm) and rename to recovery.cpio, then move it to external SD card. Then do it with boot scripts that you've downloaded (e.g. 4.4.x_f2fs.cpio.zip - unzip and rename to boot.cpio)
Well, that all that needs for installation. Read following instruction very carefully, otherwise that may cause brick Keep in mind, all that you do at your own risk! I'm not responsible if you brick your phone!
Installation method:
1) reboot into recovery, plug your phone to your PC, enable adb:
Code:
adb shell
2) Format kernel2 partition to ext4 file system:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p17
Think twice before you hit 'enter' button - wrong command may cause hardbrick!
3) create /ramdisk folder and mount kernel2 partition
Code:
mkdir /ramdisk
mount -t ext4 /dev/block/mmcblk0p17 /ramdisk
move your recovery.cpio and boot.cpio to this folder, give 777 permissions:
Code:
chmod 777 /ramdisk/recovery.cpio
chmod 777 /ramdisk/boot.cpio
4) install downloaded kernel
Now you can change recovery via changing /ramdisk/recovery.cpio - just make a backup of this file, and then replace with one of another recoveries. If you want to install another ROM or change filesystem of partition then replace /ramdisk/boot.cpio with one of needed boot scripts. Don't forget to give 777 permission (probably 644 is enough, but I didn't test it) to both of these files.
This method tested and working on 4.4.x TC ROM + twrp recovery + kernel with full F2FS support.
Well, now it's time to create uncompressed kernel, that may slightly decrease the boot time
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
sorset said:
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Click to expand...
Click to collapse
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
Click to expand...
Click to collapse
Yes, you can roll back to usual kernels. it doesn't matter what written on kernel2 partition - real kernel or anything else...
ChronoMonochrome said:
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Click to expand...
Click to collapse
Ok, thanks , But why do you mount kernel2 partition inside of OS? As I understand boot.cpio is necessary before booting OS . And inside of OS is just an extra storage! (is that true?)
sorset said:
And inside of OS is just an extra storage! (is that true?)
Click to expand...
Click to collapse
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Ace 2 has 15 - 20 Partitions my Friend
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
And what ? We actually talking about kernel2 partition.
ChronoMonochrome said:
And what ? We actually talking about kernel2 partition.
Click to expand...
Click to collapse
sorry, i meant @sorset
ChronoMonochrome said:
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Click to expand...
Click to collapse
You are right , but I remember days that 1.44MB floppy disk was a large STORAGE and 16MB was HUGE
sry , I have another question , So can I remove its line from fstab to prevent mounting?
I'm confused
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
Yes,With counting internal storage , 17 exactly , but thats not the point , I'm afraid.
sorset said:
sry , I have another question , So can I remove its line from fstab to prevent mounting?
Click to expand...
Click to collapse
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
Click to expand...
Click to collapse
I don't get it rephrase please
ChronoMonochrome said:
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
I don't get it rephrase please
Click to expand...
Click to collapse
I didn't too
There is an Image named boot.img in kernel flashable zip archive that extracts into partition 15 (named kernel) as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image , and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
sorset said:
as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image
Click to expand...
Click to collapse
originally kernel + recovery
, and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
Click to expand...
Click to collapse
In my mod kernel(mmcblk0p15) and recovery (mmcblk0p17) are splitted.
Thank you. I see.
This is probably the best (and only?) way to rebuild the ramdisk without having to compile anything, which is an excellent base for my NoUMS patches
:good:
<remove>
I'm thinking of changing to f2fs on userdata and cache partition and use it with LOS (or crDroid) with DFE. However, I would have to format my internal storage for that. So just wondering if its worth the effort. For people already using it @ccelik97 others, please comment
Just do it, it will boost your performance a bit.
Just remember flashing the fstab file (mount vendor before).
And only format /data and /cache NOT /system
ext4 has faster reading speeds which is better for /system
I would also recommend to use Orange Fox Recovery which disables FE itself when you install a vendor package
using it just because - since it hasnt cause me any issues yet. There's almost no improvement as far as daily usage goes, but maybe it's just because I didnt spend much time with ext4 since I got the phone
VC-34 said:
Just do it, it will boost your performance a bit.
Just remember flashing the fstab file (mount vendor before).
And only format /data and /cache NOT /system
ext4 has faster reading speeds which is better for /system
I would also recommend to use Orange Fox Recovery which disables FE itself when you install a vendor package
Click to expand...
Click to collapse
Which ROM are you using with F2FS ?
Tried it with lineage OS (unofficial build) but it did not boot. Flashed Sphinx Kernel also, but again same result.
Mafioso said:
Which ROM are you using with F2FS ?
Tried it with lineage OS (unofficial build) but it did not boot. Flashed Sphinx Kernel also, but again same result.
Click to expand...
Click to collapse
Im on 9.4.12 Xiaomi.eu ROM but it works on every ROM just follow this steps when you make a clean flash:
1. flash ROM
2. mount vendor, flash fstab.zip
3. flash the other files (kernel, magisk, gapps)
and now reboot
let me know if it doesnt works:fingers-crossed:
VC-34 said:
Im on 9.4.12 Xiaomi.eu ROM but it works on every ROM just follow this steps when you make a clean flash:
1. flash ROM
2. mount vendor, flash fstab.zip
3. flash the other files (kernel, magisk, gapps)
and now reboot
let me know if it doesnt works:fingers-crossed:
Click to expand...
Click to collapse
Yeah, pretty much did the same thing. However latest version of orangefox recovery from blitzfire3 doesn't format it to f2fs by reading from fstab file. You have to change to f2fs i mean data and cache through partition options in ofox recovery wipe menu, after which it gets changed. Will try some other rom.
VC-34 said:
Just remember flashing the fstab file (mount vendor before).
Click to expand...
Click to collapse
Hey, I Can't Find An fstab File For Enabling f2fs On My Poco X3 Pro. Help
Hashman9820 said:
Hey, I Can't Find An fstab File For Enabling f2fs On My Poco X3 Pro. Help
Click to expand...
Click to collapse
Look into your boot image!