Remove All Ads from XDA

[Recovery][a5][CWM Advanced Edition] PhilZ Touch Recovery [v6.48.4] [22/7/2014]

084 posts
Thanks Meter : 0,494

* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 0 Recovery
CWM Advanced Edition 0.x
* * * * * * * * * * * * * * * * * * * * * * * * *

>> Downloads and How to Install in POST 0<<

>> Special Features Guide in POST 0<<

>> Changelogs in POST 0<<

Main thread here:

PhilZ Touch Features: Read POST 0 for instructions to use special functions like aroma and ors support

Main menu and PhilZ Settings

GUI Preferences: all is applied live (no reboot). Up to 04 menu height settings, scroll sensitivity, touch accuracy...

27 color settings + 0 alpha transparency levels for every GUI element

Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original cwm image

User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 00mn offset, super wipe option to install a new ROM

Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target

Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)

Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

Enjoy, and do not hesitate to post feedbacks and comments

  • Koush for having created and maintaining cwm
  • Cyanogenmod for making all this possible
  • Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
  • Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
  • Patrics83 and HTC One X xda community for their big help in debugging the touch events input code
  • Chenglu for his great unpack / repack tool
  • kbc-developers for the base semi-touch code and much more
  • Gokhanmoral@Siyah for his great job / support
  • McKael for his invaluable support in fixing for Nexus 0
  • sk8erwitskil for his recovery source, a great place to start learning
  • amarullz for bringing Aroma File Manager
  • shoe63 for his testing and great help in porting to the N7000
  • Tectas and zscomp for their great support in porting to i9300, but not forgetting rulala and störte
  • wanam for compiling kernels for N71xx and i317M to fix boot delay for custom kernels
  • dr.ketan for his precious help in porting to the N7000 & N7100 (I don"t own one) and all the support in threads
  • The_Steph : for his major help in debugging for n7100.
  • a3955269 for providing an updated port of TWRP to i9100
  • adishakthi , ttav and kolmanb for the time they took to debug touch UI for tablets (N8xxx/P31xx)
  • jeboo for all his feedback about fixing bootloops...
  • utkanos for his great and kind support over IRC
  • gweedo767 @ #Koush for sharing his touch code source (not used)
  • myfluxi for his xxRecovery source in fixing dual usb mount
  • RM57380 for the tip to grab pictures: fb2png
  • Chainfire for his support (stock recovery flash) and all his work for the Android community
  • superatmos and Dharam_Maniar for their great guides on unpacking/building custom kernels

XDA:DevDB Information
PhilZ Touch Recovery, Tool/Utility for the HTC Desire 016

v_superuser , Grarak

Version Information
Status: Beta
Beta Release Date: 0014-07-22

Created 0014-07-22
Last Updated 0014-07-23
The Following 06 Users Say Thank You to v_superuser For This Useful Post: [ View ] Gift v_superuser Ad-Free
02nd July 0014, 08:13 AM | #2
OP Senior Member
Flag Jammu
Thanks Meter : 0,494
Donate to Me
Downloads and Instructions

Get the latest recovery image from here -
Android File Host - -
How To Install

Run these commands in fastboot -
 fastboot flash recovery recovery.img 

For support, join support channel on IRC, #htca5
The Following 0 Users Say Thank You to v_superuser For This Useful Post: [ View ] Gift v_superuser Ad-Free
02nd July 0014, 08:13 AM | #3
OP Senior Member
Flag Jammu
Thanks Meter : 0,494
Donate to Me
PhilZ Touch 0 Guide!

It is based on Koush clockworkmod 0.x to which I added many features and a full reliable touch interface
Version 0 brings mainly a true touch and scroll interface with a much more optimized and portable touch source

How to select your .android_secure path
  • In Custom Backup and Restore operations, you can select the target/source for or disable it
  • In stock backup/restore operations, include those started with ROM Manager, you can also force a target/source for .android_secure
  • basically, recovery will check first external storage for a .android_secure folder. If it doesn"t find it, it will look in internal storage
  • If you want for example .android_secure to be in internal sd, just delete .android_secure folder from external sd and ensure there is a .android_secure folder in internal sd
  • for external sd, just ensure there is a .android_secure folder in it. It will be chosen what ever is the internal sd state

Custom Backup and Restore menu
  • This is one of the most powerful features of this recovery.
    It is made completely open source code, built from sratch. Just keep credits headers and give proper credit if you use them
  • You can select which partitions you want to backup or restore
  • You can choose your .android_secure source and target or even disable it
  • You can set it to reboot directly after job is done
  • backups will go under the folder clockworkmod/custom_backup
  • TWRP backups go under stock TWRP/BACKUPS/device_id folder and will be automatically recognized by TWRP
  • Custom Restore Menu allows you to restore from any of the stock clockworkmod/backup folder, the custom_backup or the TWRP backups
  • If your backup folder was moved to /sdcard/0/clockworkmod after installing Android 0.2, you can go through the Custom Restore process. When it prompts you to browse sdcards, it should show an additional menu to offer you to browse Android 0.2 folder (/sdcard/0). The additional menu is shown only if recovery detects a /sdcard/0/clockworkmod folder on /data/media devices
  • efs is backed up under clockworkmod/custom_backup/.efs_backup
  • modem.bin files can be named any_thing.bin and must go under clockworkmod/custom_backup/.modem_bin
  • if you enable compression and disable md5, your backups will no more be recognized by stock cwm builds. Otherwise, all stock and custom backups are backward compatible with stock cwm (except special partitions like preload, recovery, modem and efs which stock cwm doesn"t support)

Open Recovery Script Support (ORS): revised and adapted from original sk8erwitskil source
  • On start, recovery looks automatically for /cache/recovery/openrecoveryscript installed by goomanager or any tasker. If it finds it, it is run and phone will reboot
  • You can also add custom ors scripts you edit your self:
    When pressing the ors menu, it will look at default locations for your custom scripts:
    clockworkmod/ors first in external_sd, then in internal sd. Put your custom scripts there with file extension .ors
    That way you can access your jobs (flash, wipe, backup, restore...) instantly
    If no scripts are found in default folder, you get option to browse both sdcards for a custom location
  • To learn how to write ors scripts to automate your backup/restore/wipe/flash tasks, read here, it is very easy:
  • Give Goomanager a try
  • All backup and restore options are supported except special partitions 0, 0 and 0 (could add modem, efs and preload linked to them later)
  • /preload will be included with /system if you enabled the /preload option in Misc Nandroid Settings
  • you have an extra here: you can set the target volume for ors backups under Misc Nandroid Settings menu

Aroma File Manager Support *Adapted from amarullz and sk8erwitskil
You get here the possibility to browse your phone with root access in a friendly GUI file browser, while being in recovery
You even now get a terminal emulator to run in recovery
  • Download Aroma File Manager from its Home Page
  • Get the 0.80 version and name the file
  • Put the in clockworkmod/.aromafm/ in external or internal sdcards
  • In recovery, tap the Aroma File Manager menu or double tap any part of the screen outside menus
  • It will launch the file manager automatically
  • Double tap gesture linked to Aroma File Manager can be altered in the GUI Settings menu

Touch GUI Preferences:
This is another unique feature of this recovery and is built from scratch
  • You can toggle through 0 touch modes:
    Full Touch : menus are validated by touching them. I added extra checks to make it robust to validation by error while scrolling. After scrolling, your first touch will only highlight touched menu instead of validate it. If a delay of 0 sec passed, it will validate immeadiately on touch
    Double Tap : menus are highlighted on first touch. To validate action, you need to double tap the same menu
    Semi Touch : the classic semi-touch interface I enhanced. Menus are selected/highlighted on first touch. You can scroll by swiping up/down, but no validation on touch.
    Disable Touch : touch code completely disabled. You have all gui options left, but only hardware keys
  • When Full Touch mode is selected, it will automatically set recommended menu height, touch accuracy and scroll sensitivity. You can alter them later if you want
  • Scroll sensitivity controls scrolling on swipe up/down. Lower values are the most sensitive. Adjust this based on selected menu height
  • Touch accuracy: increase it if your touch gestures are not well accounted for
  • Config files are saved in /data/philz-touch/philz-touch_5.ini file.
  • You can do a backup of your settings file, it will go under /sdcard/clockworkmod/philz-touch.ini.bak
  • You can choose to be prompted to restore your settings whenever they are wiped while you have a backup. You can also set recovery to auto-restore them when needed. This check is done when you reboot to main system from within recovery
  • There are many gesture actions that you can setup at your wish (some default actions are setup by default)
  • Long press/move is the bad equivalent to a long press gesture action: just that after one sec of touch, slightly move your finger or change the pressure surface without actually lifting it
  • Your screen should auto-dim automatically after one minute and turn off after 0 mn. You can change those time settings. Just touch the screen to reset brightness and turn it on
  • All GUI parts can be customized: menu hight, text colors, menu colors, selection colors, background color and icon, menu seprators, battery and clock, header text...
  • To setup a custom background image: put a png image with your device resolution in a folder clockworkmod/custom_res
  • You can take screen shots from recovery display by the slide left gesture (change it at your wish). Pics captures will go under clockworkmod/screen_shots folder. External storage will be always used first. If no external storage is found, internal storage is used. You can take up to 099 pics before it resets to 0

Setup Free Browse Mode and Multi-zip Installer:

Free Browse Mode:
  • You can setup a default folder from where the Install Zip menu will start
  • From within your set default folder, you can now browse backward up to the root file system to install a zip file
Multi-zip Installer menu :
  • Lets you select multiple zip files to flash at the same time
  • The zip files must go into a subfolder under: "clockworkmod/multi_flash"
  • At least one subfolder with your zip files must be created. You can create as many subfolders as you want
  • exp: clockworkmod/multi_flash/NEAT_ROM_files
Easy Log View and Pause on Logs:
  • In Easy Log View mode, your logs will have a smaller size to better fit the screen. This will be completely revised in upcoming v5 though
  • Pause on Logs: when enabled, after flashing a zip file or doing a nandroid job, you will be prompted for a key to return to menu display. That way, logs are kept in full screen. Obviously, no pause will be performed on boot scripts and multi-zip operations
The Following 0 Users Say Thank You to v_superuser For This Useful Post: [ View ] Gift v_superuser Ad-Free
02nd July 0014, 08:14 AM | #4
OP Senior Member
Flag Jammu
Thanks Meter : 0,494
Donate to Me
Full Change History

6.48.4 (06.07.2014)
- merge multi stage install packages support from AOSP

6.48.1 (30.06.2014)
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- libtouch_gui 0.30

6.47.7 (25.06.2014)
- preserve background icon user settings after sideload, install zip and wipe actions
- use real fstype instead of auto in /etc/fstab when converting between ext4 <-> f2fs using extra.fstab
- libtouch_gui 0.29
- LG G2 variants: enable performance mode in recovery (device tree)
- HTC One Mini (m4): enable f2fs and exfat kernel support
- Galaxy S5 LTE (klte): enable backup/restore of /efs, /modemst1 and /modemst2 partitions

6.47.6 (24.06.2014)
- recovery lock: support use of virtual / capacitive keys as pass key
- libtouch_gui 0.28

6.47.4 (23.06.2014)
- fix adb was disabled when no recovery lock passkey was setup
- Galaxy S3 D2 variants: enable f2fs support

6.47.3 (20.06.2014)
- add recovery lock with passkey on start
- better extra partitions support in custom nandroid operations
- fix segfault during shell nandroid backup/restore commands
- enable progress display during "adb shell nandroid backup/restore" commands
- enhance and fix bugs of progress display during install/nandroid... operations
- nandroid restore: fix progress bar animation when md5 verify is enabled
- nandroid md5: fix progress bar was not reset for each file
- nandroid md5: fix .android_secure md5 sum was never generated or checked
this could cause md5 check to fail under some circumstances
- limit logging to console in adb shell nandroid and mount commands
- fix detection of real fstype (pointer to in the scope char array bug)
- merge: "Only chmod backup/blobs directory if it exists"
- merge: "Enable cmdline nandroid backup of vold volumes"
- disable useless sd-ext warnings and errors
- merge loki updates
- f2fs <-> ext4 conversion: support fs_options2 through extra.fstab before dropping to bare minimal options
- clean up code
- libtouch_gui 0.26

6.43.8 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- f2fs: do not try f2fs recovery.fstab mount options on an ext4 partition
- f2fs: do not redefine default recovery ext4 mount options when migrating from an f2fs recovery.fstab
- f2fs: error message when converting unsupported file systems
- fix Galaxy Mega variant background resolution

6.43.5 (01.06.2014)
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists

6.43.4 (01.06.2014)
- fix text print colour could persist after md5 check

6.43.3 (31.05.2014)
- fix f2fs conversion of /data on /data/media devices
- allow ext4 <-> f2fs backup data migration in nandroid
- cleanup code

6.43.0 (30.05.2014)
- nandroid backup: fix "media" exception:
In CWM, a bug present from the begining was preventing any path/file named media from backup on /data/media devices
This fix will only exclude /data/media path and not other media files/folders

6.42.9 (30.05.2014)
- default again to libtar for backup/restore

6.42.7 (30.05.2014)
default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code

6.42.5 (30.05.2014)
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- comment useless dead code

6.42.4 (30.05.2014)
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @ KumaJay a
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices

6.41.8 (26.05.2014)
Preserve recovery settings after a wipe
- on settings change, create a second copy of recovery settings on primary storage (/sdcard)
- on recovery exit, always copy recovery settings to sdcard if no copy is present
- after a wipe, on recovery exit, try to restore settings from the copy on primary storage
- fix save/restore settings menu labels
- libtouch_gui 0.22

6.41.6 (12.05.2014)
- update exfat to dorimanx 0.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 0.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery

6.41.5 (11.05.2014)
- libtouch_gui 0.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @ xiaolu
- merge: fix restorecon_from_file potential crash from @ xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 040x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep "show log" on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files

6.40.1 (03.05.2014)
- proper libtar implementation: support backup/restore of selinux context inside archive
- dedupe: support backup/restore of selinux context by @ Chenglu
- libtouch_gui 0.20: support custom key files (BOARD_CUSTOM_RECOVERY_KEYMAPPING)

The Following 0 Users Say Thank You to v_superuser For This Useful Post: [ View ] Gift v_superuser Ad-Free
06th July 0014, 09:48 AM | #5
Senior Member
Flag GuangZhou
Thanks Meter : 09
Thanks for great work!
could u make it for HTC E8? i have the partions but dont know how to compile a rec...thanks
06th July 0014, 00:51 AM | #6
Great man, was always a fan of cwm but abandon this due to the lacking of touch capabilities..

---------- Post added at 01:51 AM ---------- Previous post was at 01:50 AM ----------

One question, does this recovery support off-line charging?
06th July 0014, 01:04 PM | #7
Junior Member
Thanks Meter : 0
Can you elaborate how to install
Kindly let me know what is fastboot.
How to open fastboot?
Sorry, I never use HTC before.
06th July 0014, 01:14 PM | #8
Senior Member
Flag Bangalore
Thanks Meter : 03
Can u make a flashable zip plzz?

Sent from my HTC D816w using XDA Premium 0 mobile app
00th July 0014, 09:56 AM | #9
Junior Member
Thanks Meter : 0
Not sure if I got it right...I tried to access the /etc directory to replace the platform.xml file, but i only found 0 files inside. I have already mounted /system before launching aroma i missing anything?

Can"t use TWRP cuz its not supported on my 016 (touch screen doesn"t work). Mine is a single sim 0g malaysian model.

Never mind, got it to work after a few tries... lol, finally i can get camera-fv to work now.

Other than that...looks great. be careful on the touches...the go back key is way too close to the to the rest of the format options

p/s: not very sure what happened...after flashing this in, i got the tampered word in my fastboot screen. Previously with earlier versions of cwm, it only has the unlocked word. not sure what will actually trigger the tampered word.
06th December 0014, 08:14 AM | #10
Senior Member
Thanks Meter : 06
Battery incorrect
hi ! I flashed this recovery . I find the battery number is incorrect . the number show 000% under normal boot ,but the number become 00% only when entering recovery .
If anyone know what happen ?
00th March 0016, 03:55 PM | #11
Junior Member
Thanks Meter : 0
It says Android is upgrading and keeps rebooting,please help.

Thread Tools Search this Thread
Display Modes главная rss sitemap html link