yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] katinatez:
Main thread + features + install instructions + dev support

http://xdaforums.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
[ONE Android Development] katinatez:
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img

adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot

Changelog​

[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 [MENTION=2661222]xiaolu[/MENTION]

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

​
[ONE Android Development] katinatez:
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​
[ONE Android Development] DJMartini:
Thanks [MENTION=3814731]katinatez[/MENTION]
[ONE Android Development] gulp79:
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?
[ONE Android Development] katinatez:
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.
[ONE Android Development] gulp79:
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 [MENTION=3685904]ak[/MENTION] to add aroma fix to his kernel? Or maybe [MENTION=912474]Dees_Troy[/MENTION] can add f2fs support. :)
[ONE Android Development] katinatez:
[MENTION=2941594]johnnyslt[/MENTION] said he would help patch the f2fs, just give us time.
[ONE Android Development] radz_:
Del
[ONE Android Development] katinatez:
Don't understand. What is the question?
[ONE Android Development] radz_:
Me too[emoji12]

By the way, whats the difference? This works on s4 i9505 right?
[ONE Android Development] Phil3759:
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
[ONE Android Development] katinatez:
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
[ONE Android Development] katinatez:
Will not work on s4, your in one plus one forum.
[ONE Android Development] Mr Woolf:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
[ONE Android Development] gulp79:
Set up your time in options...
[ONE Android Development] Mr Woolf:
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.
[ONE Android Development] gulp79:
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
[ONE Android Development] katinatez:
Correct settings is time settings/Qualcomm time daemon. That should fix your time.
[ONE Android Development] Phil3759:
: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
[ONE Android Development] Roulianooo:
The same for me :'(

Really want to test Lollipop but really don't like TWRP :silly:
[ONE Android Development] fiz:ik:
What are you referring to? I'm on 5.0 with latest Philz and no problems here? :cool:
[ONE Android Development] DJMartini:
Wanna be able to use 2 different ROM's though ... My CM11 4.4.4 is stable ... 5.0 isn't stable enough for me to use as a daily driver yet. I'd like to be able to swap back and forth between them with different /data partitions etc.
[ONE Android Development] katinatez:
I have no idea what the last couple of post are about. I also am going to flash lollipop today and run Philz recovery.
[ONE Android Development] Roulianooo:
We talked about multirom for witsh twrp is mandatory and we dont wanna loose philz :P
[ONE Android Development] katinatez:
Trust me you could flash any rom with Philz
[ONE Android Development] Roulianooo:
But not in multirom
[ONE Android Development] katinatez:
http://xdaforums.com/showpost.php?p=56714605&postcount=137
[ONE Android Development] martinoff:
nobody here said that have any problem with philz :p

i have flash already L5.0 without a single issue from recovery, just for me L5.0 is far away to be my daily driver

so i will not sacrifice either my awesome rom or my very stable(thanks to you) recovery for it

IMHO
[ONE Android Development] katinatez:
Sorry, I thought people could not use recovery to flash Android V5.
[ONE Android Development] Pipodi93:
Guys, I can't find the OTG option... Sorry but I've just bought an OTG cable, never used it!
[ONE Android Development] katinatez:
In recovery, just plug in cable; it auto mounts
[ONE Android Development] anandbibek:
Katinatez, is this the best option I have for OPO? Or is there anything better available?

Cause I read about TWRP corrupting EFS partitions and I want to get rid of TWRP asap
[ONE Android Development] katinatez:
I roll with Philz, but try both, use which ever suits your needs
[ONE Android Development] anandbibek:
The artifacts while using aroma file manager are the screen of recovery visible in the background. If you can put a white cover on the screen before loading aroma, I think it'll be solved.

I've no idea about coding recoveries. So I don't know it's even possible or not
[ONE Android Development] an0therus3r:
I'm already on PhilZ recovery for my opo (6.44.9) and willing to update to latest version. It's only not clear for me if this recovery supports SELinux? Euphoria OS requires it when you want to flash, at least that's the warning in instructions for it.
[ONE Android Development] katinatez:
Its supported
[ONE Android Development] an0therus3r:
Great. Thanks for your quick response and work of course.

Also noticed a few roms on your download page, maybe I should try them out as well ;)
[ONE Android Development] katinatez:
Come and get your final version v6.59.0
[ONE Android Development] Schrotty35:
Thank you for the update.
[ONE Android Development] katinatez:
Always in op

Edit: I thought you were asking for changelog, your welcome, time to go to sleep
[ONE Android Development] fiz:ik:
Why is it final? :) Good work though! :good!
[ONE Android Development] katinatez:
QUOTE: Phil3759

End Of Support

Quote:

Project Status: No Longer Updated

As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.

CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.

Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP or the CM Simple Recovery

If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives.
[ONE Android Development] fiz:ik:
Where am I *****ing around about CWM? I defended it in every thread where TWRP-users were complainimg about TWRP. I never had any problem with CWM or Philz
[ONE Android Development] Astrovilos:
He is not reffering to you my friend. He is just quoting Phil in order to explain you why it's the final version. ;)
[ONE Android Development] fiz:ik:
Ohhhhhhhh.. oops my fault, I did not see the QUOTE at the beginning :)
[ONE Android Development] llevin:
I have a new OnePlus One and I seem to be unable to install any recovery :(

Apparently I'm doing something wrong, but I don't know what...

(BTW, I am not a noob, just new to OPO - I have done this many times on the Nexus One and Nexus 4).

I have unlocked bootloader. And when I reboot to recovery I see a simple one with the title "Cyanogen Recovery" at the top of the screen.

I've downloaded PhilZ. When I try to install it from recovery, I get an error about wrong signature.

So I I've extracted the recovery.img and flashed it with fastboot. Fastboot says "OKAY" and "finished" - all looks fine.

But when I reboot to recovery, I still get the same "Cyanogen Recovery" - not PhilZ!

Same happens when I flash TWRP or CWM - All I get is the Cgen recovery.

What am I missing here?
[ONE Android Development] katinatez:
Go to settings/developers options/unchecked update cm recovery

Then use fastboot commands
[ONE Android Development] SaschaKH:
'fastboot oem unlock' that you have done alredy

'fastboot reboot' that it might make automatic after unlocking, but if not you need to reboot it

'fastboot flash recovery recovery.img' maybe with the path to the recovery image, i.e. something like 'fastboot flash recovery path\recovery.img'

'fastboot reboot' again

All of this commands needed to be given from a PC to the via USB connected O+O that is in fastboot mode, but as you say you already did the first two lines, it should be np for you.

BTW I did forget to uncheck the 'update recovery' in system settings the first time I did it, but it worked. Only thing is with next update I had to do 'fastboot flash recovery recovery.img' again.
[ONE Android Development] llevin:
Thanks! So simple...

All working fine now :)
[ONE Android Development] dizM0nkey:
Goes to Cyanogen Recovery when holding volume down

I've installed the recovery, and I'm able to boot into it using fastboot, but when I try to boot in using the volume down rocker, I get into Cyanogen Recovery.

Did I miss something? How do I get into PhilZ Touch without using fastboot?

Thanks,

diznanl
[ONE Android Development] elrey311:
Did you look at the post just above yours?
[ONE Android Development] an0therus3r:
Any plans to support Cyandelta ?

I hate it to switch to other recovery just to have Cyandelta working.

/edit:

Seems you need to change path for it to work properly.
[ONE Android Development] chrcol:
I been searching but how does one go from CM11S recovery to philz recovery? is no option to install zip files.

never mind done it but was a chore.

install JDK win64 files

Install android studio

set JAVA_HOME env variable in windows to jdk path, probably C:\Program Files\Java\jdk1.8.0_25 (substitute version number) - this is needed to start android tools gui, not sure if needed for the command line tools.

navigate to path where fastboot binary resides, on my rig is C:\Users\Chris\AppData\Local\Android\sdk\platform-tools and open a command prompt there.

reboot device to bootloader mode (fastboot mode)

run "fastboot devices" to check its connected

run "fastboot oem unlock" this wipes all settings and apps be warned, it even wiped files I uploaded to the internal flash memory.

after reboot reboot again into bootloader mode

run "fastboot devices" to verify connected

run "fastboot flash /path/to/recovery.img" this takes barely one second

run "fastboot reboot"

Now next time you reboot into recovery it should be philz.

I hope I dont need to use fastboot again. :)
[ONE Android Development] playya:
just as an fyi - this is rather simple and exactly how it has to be done the first time. There is no zip to flash for the first time at least. Fastboot is a nice tool and at least you know how to use it now which could come in handy again. At this stage you should not have to use it again unless you want to fastboot the original images again
[ONE Android Development] katinatez:
Wow that was to many steps, for future adb you need to set up enviremental variables. Look at step 6 here

http://jaxov.com/2010/10/set-up-adb-on-windows-7-vista-xp-for-android-phones/

After you do this you don't have to navigate to fastboot folder.Also after placing file at root of C partition.And your command will be like this

Fastboot flash recovery C:\recovery.img

Or if you run Linux it's even more easier and less steps.

Enjoy the recovery.
[ONE Android Development] mchauhan:
End Of Support!!!!!!!!!!

End of Support:(:(:(

I am using Philz Touch from last couple of years for all my devices. Can not imagine using any other recovery now. So sad to know the emd of the support thing..

However I am sure he has other real life matters to take care of.

Thank you [MENTION=4666971]Phil3759[/MENTION] [MENTION=3814731]katinatez[/MENTION] for all your work.

I hope I can use this for Lollipop for sometime before moving to TWRP.
[ONE Android Development] katinatez:
Update coming compiling now but will test for a day or two before releasing! Update bring faster boot with cm-12.0 using a cm-12.0 kernel, updated recovery fstab to flash bacon_firmware_update_2015_01_16.zip, updated f2fs commits.
[ONE Android Development] katinatez:
Ok all done running cm-12 and previous version took to long to boot maybe because I updated to cm-12 firmware. But compiled with cm-12 kernel and boots so much faster and aroma file manager still works!!! As opposed to twrp v2.8.4.1 does not load aroma at all. More testing then I will release in a couple of days.
[ONE Android Development] xlollomanx:
Awesome job! Can I assume that new recovery is compatible with older CM like CM11/s? Thanks for your work.

Sent from my Oneplus One
[ONE Android Development] playya:
Must admit I was a die hard TWRP user until the issue with TWRP and its instability started back with 2.8.1 or so. I came over to this recovery and without fail has flashed and restored every thing I needed. No complaints or worries at all. Your update is appreciated but must say things work fine as is... Thx :good:
[ONE Android Development] jasraja:
Thanks so much, really feel safe to have devs like you for this device. Keep up the good work!
[ONE Android Development] abhibnl:
Hi! Can we also flash it if on cm11s? I know recovery has it's own kernel and as you mentioned that it's running over cm12 kernel, so due to my limited knowledge, i just want to confirm if it can cause any conflicts with cm11s rom which i highly doubt it can.

Sent from OnePlus One Powered by Boeffla
[ONE Android Development] katinatez:
Just stick to v6.59.0 the update is for users running cm-12.0
[ONE Android Development] abhibnl:
Thanks for the clarification.

Sent from OnePlus One Powered by Boeffla
[ONE Android Development] Clark789:
Only for information: i just flashed v6.59.0 on my OPO CM11s via Flashify and had absolutely no issues. Now i came back to PhilzTouch after i read many issues with TWRP...

Feels good! :)

Cheers

Clark
[ONE Android Development] Roulianooo:
Thanks [MENTION=3814731]katinatez[/MENTION] you rock :D

Flashed 5 minutes ago , everythings fine
[ONE Android Development] donalgodon:
I can't get nightly builds to flash properly with this latest version. The CM updater doesn't work anymore with CM 12.

Any idea why?
[ONE Android Development] katinatez:
Are you saying you can't flash cm nightly with v6.59.1? Let me try
[ONE Android Development] donalgodon:
No, it flashes manually, but not with the CM Updater app.
[ONE Android Development] katinatez:
Try it with v6.59.0 and let me now if it works.
[ONE Android Development] katinatez:
Are you trying to update opos new ota? Go back to v6.59.0 because v6.59.1 has a cm-12 kernel and the ota is still 4.4.4 with bug fixes.
[ONE Android Development] donalgodon:
No, I'm running the CM 12 nightlies, and the CM updater app downloads the latest nightly builds fine, but when it reboots into recovery, the flash fails and I have to manually find the file and flash it.

Manual flashes work. I'll try the older version and report back to the thread.
[ONE Android Development] gogib:
you can try to go advanced functions and click on sdcard target
[ONE Android Development] donalgodon:
Older version does not work.

Philz Touch 6.59.0

ClockwordMod v.6.0.5.1

Finding update Package...

E: Unknown volume for path[@/cache/recovery/block.map]

E: Can't mount @/cache/recovery/block.map

Installation aborted.

---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------

Changing target does not work. It' s one of the first things I tried, actually.
[ONE Android Development] :
same on twrp saddly
[ONE Android Development] katinatez:
[MENTION=402300]amarullz[/MENTION] has been busy updating his aroma file manager this one can load into recovery with great display but has one bug left; that is it's exit of file manager causes a reboot of device. Now is the time to show the dev some love with donations for all the current updates. Here is my report after testing.

http://xdaforums.com/showpost.php?p=59203826&postcount=1015

Here is the current one that works

https://github.com/amarullz/AROMA-Filemanager/releases/tag/2.00
[ONE Android Development] LeroViten:
[MENTION=3814731]katinatez[/MENTION] nothing there... :(

~• Posted via Bacon Flavoured Tapatalk •~
[ONE Android Development] nicesoni_ash:
Both links return 404.

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Android Development] katinatez:
Edited my post fixed links, but here they are again

http://xdaforums.com/showpost.php?p=59203826&postcount=1015

Here is the current one that works

https://github.com/amarullz/AROMA-Filemanager/releases/tag/2.00
[ONE Android Development] fiz:ik:
Anyone having the issue that rebooting from latest version into a 5.x ROM causes a bootloop? I have to power off the device and then boot it to start properly :confused:
[ONE Android Development] algus:
I am getting the same error both in CWM recovery and TWRP as well.

How can we fix this?

I know how to flash updates manually, but we have 'updates' menu for a reason, why not fix it?

EDIT: looks like a problem with cyanogenmod, hope it'll get fixed someday... https://jira.cyanogenmod.org/browse/NIGHTLIES-581
[ONE Android Development] NuLLV01D:
Could We Get an Updated Recovery [MENTION=3814731]katinatez[/MENTION]? THough I Know no more Development is being done on this, But I Really Love Philz!
[ONE Android Development] katinatez:
Philz recovery project will not end, I love this recovery & and it's my recovery of choice!

Soon, I was working on it last night. Trying to make philz backup all of Firmware partitions: which are 8 partitions. But at the moment could only make custom backup of 4 partitions. What I am trying to accomplish is to have philz & unofficial twrp compatible in restore or backup with philz twrp mode. Also being built with cm-12.1 device tree as well as updated f2fs commits with Jaegeuk Kim repo, & exfat kernel support.

https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4

So that's the proposed update/changelog coming. So already running update just trying to make the custom partitions to work correctly.

https://github.com/katinatez/philz_touch_cwm6/commit/17ef1677a5e952a9bac4f93567224ea366c27647
[ONE Android Development] anandbibek:
I had found a recovery script on xda that when flashed via philz, backed up all of my partitions that I didn't even know I had. It was from some guy named vonnegauht or something..
[ONE Android Development] katinatez:
Thanks, but are you going to share link? Or recoveryscript for users here?
[ONE Android Development] katinatez:
Come and get it, please do not mirror links to recovery. I keep count of my downloads Thank You

Enjoy :D

Changelog

2015-05-18

Updated 6.59.2

updated f2fs with Jaegeuk Kim repo

https://git.kernel.org/cgit/linux/ke...g/?h=linux-3.4

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.0 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
[ONE Android Development] fmc000:
Hello,

I'm interested in trying this recovery for the first time. Coming from your unofficial twrp, with a pretty standard CM12.1 installation (AKA no f2fs - no encryption), is there something I should worry about?

Is this "Philz twrp mode" an option I will find in this recovery? (I guess so as there's no such wording in twrp :p )
[ONE Android Development] NuLLV01D:
Nothing to worry about, Philz is pretty foolproof so I don't think you'll have much trouble getting adapted.

No, there isn't any sort of mode. It's just that the backups you now take in this Philz are compatible (can be restored by) with TWRP and vice versa