Double No-touch Binary Options

End Of Back up

Projection 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 carelessness this project for real life alternatives.
CWM is a dead project for now, until some dev resurrects it. I was near to do, until these new projects came.

Current version will probably work a while for many devices. Some devices with new ROM installers could accept bug. Just use TWRP

and avert

the new CM Elementary Recovery

If the electric current version works for you, there is no reason you don’t use it though. No demand to ***** in all threads considering information technology doesn’t piece of work for you. Just move on to other alternatives.

Download Home



https://mega.co.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw

Older versions:
http://d-h.st/users/philz_touch

Specific Devices Threads


All full general requests for these devices must go into their threads
Continue this thread for dev support and porting to new devices

Amazon

– Kindle Burn down HD eight.9 (jem)
– Kindle Fire HD seven (tate)

Android

– Ane (sprout) past @varun.chitre15

Asus

– Asus Transformer Pad TF300T (tf300t)
– Asus Transformer Prime TF700T (tf700t)

HTC

– HTC Evo 3D (shooteru) past @johnnyslt
– HTC Desire X (protou)
– HTC DROID Incredible 4G LTE (fireball)
– HTC Explorer (pico)
– HTC One GSM (m7ul –> m7)
– HTC One T-Mobile (m7tmo –> m7)
– HTC I AT&T (m7att –> m7)
– HTC One Sprint (m7spr)
– HTC Ane Verizon (m7vzw)
– HTC I M8 (m8): unified for International, Verizon and Sprint
– HTC Ane Mini (m4)
– HTC Droid DNA (dlx)
– HTC Desire 601 (zara)
– HTC Want 601 dual sim (zaradug) by @andreya108
– HTC Desire S (saga) past @Ruling
– HTC Desire HD (ace) by @Ruling
– HTC One Southward (ville)
– HTC 1 V (primou)
– HTC Ane X (endeavoru)
– HTC One Ten+ (enrc2b)
– HTC One XL (evita)
– HTC Evo 4G LTE (jewel)
– HTC Rezound (vigor)
– HTC Desire 816 (a5) by @v_superuser

Google

– LGE Nexus four (mako)
– LGE Nexus 5 (hammerhead)
– ASUS Nexus vii (tilapia + grouper)
– ASUS Nexus 7 2013 (flo)
– ASUS Nexus seven 2013 LTE (deb)
– Samsung Nexus 10 (manta)
– Samsung Galaxy Nexus – GSM (maguro)
– Samsung Galaxy Nexus – Verizon (toro)
– Samsung Galaxy Nexus – Dart (toroplus)
– Samsung Galaxy Nexus S (crespo)
– Samsung Galaxy Nexus S 4G (crespo4g)

LGE

– LG Optimus One P500 (p500)
– LG Optimus L5 (e610)
– LG Optimus G International (e975)
– LG Optimus Chiliad ATT (e970)
– LG Optimus G Sprint (ls970)
– LG Optimus M Canada (e973)
– LG Optimus G Pro GSM (e980)
– LG Spectrum 4G (vs920)
– LG G2 AT&T (d800), TMO (d801), Int (d802), d803, d805, d806, Verizon (vs980), Sprint (ls980)
– LG Nitro Hard disk AT&T (p930)
– LG G Pad eight.3 (v500)
– LG Optimus 4X Hd P880 (p880)
– LG Optimus L7 P700 (p700) by @ali.filth

Motorola

– Motorola Droid RAZR M (xt907)
– Motorola Droid RAZR Hd International (xt925) and U.s.a. (xt926)
– Motorola Unified msm_8960 (xt925/xt926)
– Motorola Atrix Hard disk (mb886)
– Motorola Moto Ten variants: TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060)
– Motorola Moto M unified (falcon) for: Verizon (xt1028), BoostMobile (xt1031), GSM (xt1032), Dual Sim (xt1033), Retail United states of america (xt1034)

Oppo

– Find 5 (find5)
– Find 7, Find7a (find7)
– N1 (n1)

Samsung

– Milky way S2 i9100/P

– Galaxy S2 Epic 4G Touch on – SPH-D710 (d710)
– Galaxy S2 i9100G
– Galaxy R/Z (i9103)
– Galaxy S i9000 (galaxysmtd)
– i9001 – Galaxy Southward Plus (ariesve)
– Galaxy S Captivate (captivatemtd) by @brandonabandon
– Galaxy Yard Duos (i9082)
– Milky way Showroom – SGH-T599N (codinamtr)
– Galaxy Westward i8150 (ancora)
– Galaxy Grand Quatro I8552 (delos3geur) by @ali.filth
– Galaxy S ii Skyrocket SGH-I727 (skyrocket)
– Galaxy Southward Blaze 4G – SGH T769 (t769)
– Galaxy S2 HD LTE – SGH-I757M (celoxhd)
– Exhilarate – SGH-I577 (exhilarate)
– N7000
– Galaxy S3 i9300 – i9305
– Milky way S3 Unified d2 variants (d2lte): d2att d2cri d2mtr d2spr d2tmo d2usc d2vzw
– Milky way S3 T-Mobile / SGH-T999 (d2tmo)
– Galaxy S3 AT&T (d2att)
– Milky way S3 Sprint (d2spr)
– Milky way S3 Verizon (d2vzw)
– Galaxy S3 Mini GT-I8190 (gilded) by @Android-Andi
– Milky way Due south Relay 4G – SGH-T699 (apexqtmo)
– Galaxy Express AT&T (expressatt)
– Galaxy S4 Exynos – i9500
– Milky way S4 Unified Qualcomm variants (jflte): jfltecan jflteatt jfltecri jfltecsp jfltespr jfltetmo jflteusc jfltevzw jgedlte jfltexx jfltezm
– Galaxy S4 – i9505 (jfltexx –> jfltejflte)
– Milky way S4 – T-Mobile (jfltetmo –> jflte)
– Galaxy S4 – Verizon (jfltevzw –> jflte)
– Galaxy S4 – AT&T (jflteatt –> jflte)
– Milky way S4 – Sprint (jfltespr –> jflte)
– Galaxy S4 Mini i9190 (serrano3gxx), i9192 (serranodsub) and i9195 (serranoltexx)
– Galaxy S5 International (kltexx –> klte)
– Milky way S5 Exynos SM-G900H (k3gxx)
– Galaxy Mega i9205 (meliusltexx)
– Galaxy Mega i9200 (melius3gxx)
– Milky way Premier i9260 (superior)
– Galaxy Note ii (N7100 – N7102 – N7105 (t0lte)
– Galaxy Notation 2 LTE Sprint SPH-L900 (l900)
– Galaxy Note two LTE Verizon SCH-I605 (i605)
– Galaxy Note 2 AT&T (t0lteatt)
– Galaxy Note 2 – TMO (t0ltetmo)
– Galaxy Note 3 LTE International – N9005 (hltexx)
– Galaxy Annotation 3 T-Mobile (hltetmo)
– Galaxy Annotation 3 Dart (hltespr)
– Galaxy Annotation 3 Verizon (hltevzw)
– Galaxy Note 3 Canada (hltecan)
– Galaxy Note four International (trltexx), credits @Chenglu
– Galaxy Note 10.1 – N80xx
– Milky way Note ten.1 – 2014 Wifi (lt03wifi), 3G (lt03wifiue)
– Galaxy Note eight.0 (N51xxx)
– Galaxy Tab 2 7.0 (p31xx)
– Milky way Tab two 10.1 (p51xx)
– Milky way Tab 3 vii.0: SM-T210 WiFi (lt02wifi) – SM-T111 3G (lt023g)
– Galaxy Tab iii viii.0 (lt01wifi, lt013g, lt01lte)
– Galaxy Core – GT-I8262 (arubaslim) – past @ali.filth
– Galaxy Mini (tass)
– Galaxy Gio (gio)
– Milky way Fit (beni)
– Galaxy Ace (cooper)
– Galaxy 5 (galaxy5)
– Milky way 551 (callisto)
– Galaxy Tab Pro 8.iv WiFi SM-T320 (mondrianwifi)

Sony

– Xperia Z (yuga)
– Xperia Z1 (honami)
– Xperia Z2 (sirius) – by @DooMLoRD
– Xperia Z Ultra (togari)
– Xperia SP (huashan)
– Xperia T (mint)
– Xperia ZL (odin) – past @shoey63
– Xperia L (taoshan) by @varun.chitre15
– Xperia M (nicki) by @icoolguy1995

ZTE
– maintained past @cooldudezach
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
– Warp Sequent – N861 (warp2)
– Warp 4G (warplte)
– Awe (nex)
– Overture (becky)
– Royal (apollo)
– Source (hera)
– Iconic Phablet (stormer)
– Radiant (metis)

Huawei

– Acsend P1 U9200 (viva)

MicroMax

– A56/A57
– A110Q (unofficial repack past @sukarang9)
– A110 @bindassdost
– A177 Canvas Juice
– A310 Canvas Nitro past @thedevilashish

Cubot

– Cubot One (unofficial repack by @Maximus1a)

OnePlus

– One (bacon) by @acer73 and @katinatez

Xiaomi

– RedMi 1s (armani) by @juliusssss
– RedMi Note 4G (dior) by @juliusssss
– Redmi Notation 3G past @Countless
– Redmi ii/2A/Prime number by @Rohan Taneja

Xolo

– Opus 3 by @thedevilashish
– A500S by @EndLess

PhilZ Touch Features:


Read
POST 2
for instructions to use special functions like aroma and ors back up

• touch interface:
  – toggle between 4 touch modes:
  
  FULL TOUCH
  ,
  
  DOUBLE TAP
  
  to validate,
  
  SEMI TOUCH
  
  (coil only no affect validation) and
  NO Touch
  to only use hardware keys
  – written from scratch total touch code
  – bones
  roll kinetics
  for faster scrolling on demand
  – rubber full touch : no wrongly validations while scrolling
  – when you ready total bear upon manner, it defaults to optimized settings for menu height, gyre sensitivity and touch accuracy (you still can alter them manually later)
  – adjust scroll sensitivity in a huge palette
  – adjust menu height in a huge palette
  – adapt touch accuracy
  –
  
  30 color settings for each of the eight GUI parts + 5 blastoff transparency settings
  
  
  –
  
  user custom background png
  
  tin can be selected in add-on to 30 solid colors choice
  –
  
  show / hide background icon
  
  
  –
  
  show / hibernate bottom virtual buttons
  
  
  –
  
  show/hide + set colour and transparency for bill of fare line separators
  
  to match solid color themes, like Black…
  –
  
  set number of bottom log rows to show
  
  
  –
  
  intermission on logs way
  : no more miss logs during zip installs
  –
  
  auto dim screen
  
  subsequently user configurable delay
  –
  
  auto plow off screen
  
  afterwards user configurable delay
  –
  
  adapt brightness
  
  and turn off screen with a gesture action
  – testify/hibernate clock and remaining battery %, even during nandroid operations
  –
  
  clock and battery stats now effectively refresh
  
  every 5 seconds and during nandroid operations
  – toggle vibrator on/off on touch
  – toggle key repeat for volume upwardly/down scrolling when maintained pressed
  – key repeat also enabled for virtual buttons
  – set time zone + 30mn offset + DST: right time tin can at present be set up for nandroid backup path and clock
  – capture recovery screen shots with a gesture activeness (only some devices)
  –
  
  basic theme back up
  
  
  – one file to relieve all settings
  – backup and restore settings file
  – backup and restore only GUI settings
  – reset to default settings selection
  – prompt to restore your settings from a fill-in when they are wiped past a new ROM install
  – option to automobile restore your settings from a backup without a prompt
  – all toggles are applied live, without restart of recovery (except reset of stock CWM groundwork image)
  – toggle carte options are automatically correct aligned and carte du jour text left aligned based on device display size
  –
  
  configurable gesture deportment
  : double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change effulgence, blank screen, capture screen shot, launch Odour File Manager
  ​

  
  Note: after ringlet, there is a minimal small-scale delay (0.five sec) to validate on next touch. This is by blueprint and not a bug. It is there to limit erroneous validation while scrolling
  

• 
  true JB 4.2 migration: toggle betwixt /data/media and /information/media/0
  
• 
  Secure recovery lock with passkey
  
• scan phone with root admission using full GUI in
  Aroma File Managing director
• terminal access from recovery
  with root access through Odour File Manager
• 
  Multi Zip Install menu
  : check multiple zip files to install in a row
• 
  Custom Install Nix Manner
  : set a default folder to start with + browse backward upwards to the root
• 
  exFAT, NTFS and Ext4
  
  support in recovery for external storage through kernel modules for many devices for faster write speed
• 
  TWRP fill-in and restore support
  , include full md5 sum support (single and multivolume, compressed and non compressed formats)
• 
  Advanced statistics during fill-in operations
  
  shown in colour: full backup size, backup size progress, backup time, compression ratio…
• 
  support .android_secure fill-in/restore
  
  from external storage
• optional reboot later custom backups/restores
• 
  sd-ext back up
  
  (ext4)
• nandroid backups back up /preload
  in backup and restore jobs (custom and stock modes)
• nandroid backups support /misc
  in backup and restore jobs (custom fashion)
• devs: 5 extra optional partitions supported in nandroid operations past editing recovery.fstab
• set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore,
  
  enable nandroid compression using pigz (multi-cpu gzip pinch) and choose ors backup target volume
  
• 
  recreate md5 sum check
  
  for your cwm backups for compatibility with stock CWM if y’all need to revert
• cancel nandroid operation with back push
• 
  create custom_rom.zip
  
  from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
• nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, and so ro.romversion, then ro.build.display.id)
• 
  custom fill-in and restore job list:
  
  backup and restore freely any partition combo (include modem and efs)
• backup/restore EFS
  in both tar + img formats, now with time tags for both tar and .img
• support flash modem.bin
  image files in addition to custom modem.img files, now support for multiple *.bin versions under defended binder
• during custom restore, you can see the contents of the folder y’all desire to restore from
• delete custom or TWRP backups from recovery menu
• total wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
• full support for
  openrecovery script specifications
  include all fill-in and restore options
• run openrecovery scripts in 2 modes: on outset goomanager boot scripts + ane touch carte du jour to either straight open a default path or freely scan for scripts
• define ors backup target volume from within Nandroid Settings menu
• ors backup/restore in stock clockworkmod or TWRP modes
• advanced power options carte du jour
• detailed build info in About carte du jour

Video Teaser:
new update soon…

Primary menu and PhilZ Settings

GUI Preferences: all is applied live (no reboot). Upward to fourteen menu meridian settings, roll sensitivity, impact accuracy…

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

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

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

Backup and Restore any partitioning in a complete liberty, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can as well be restored past original CWM Avant-garde Restore Card
TWRP Fill-in 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 activity (double tap is default)

Full Wipe to Install a new ROM (sdcard is preserved)
Costless Scan Manner to install null files: select a default folder to first with and browse upwards to the root

Enjoy, and do not hesitate to postal service feedbacks and comments

Credits

To ALL people who help in porting device sources and give feedback for debugging
A special give thanks also to the below, and ALL who I do not mention only did contribute a lot with their efforts

• Koush for having created and maintaining cwm
• Cyanogenmod for making all this possible
• Tallustus from Team Skyfire for his slap-up support over IRC:
  
  MAJOR CREDITS
  
• Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
• Chenglu for his unpacking tools and porting i9505:
  
  Huge credit
  
• kbc-developers for the base semi-touch code and much more than
• [e-mail protected]
  for his great job / support
• sk8erwitskil for his recovery source, a peachy place to start learning
• shoe63 for his aid from the get-go across many devices
• DooMLoRD for his piece of work and help with Sony
• [NUT] for his ports to Sony
• wanam for compiling sensors-costless kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat back up and much more
• dougiebee for his work on fixing time on many Qualcom devices
• ausdim for all the support in developing kernels for i9505
• medicoketan for his precious help in porting to the N7000 & N7100 (I don’t own 1) and all the support in threads
• Chainfire for his support (stock recovery flash) and all his piece of work for the Android community

XDA:DevDB Information




PhilZ Touch – Advanced Clockworkmod, Tool/Utility for the Android Full general

Contributors


Phil3759

Source Code:
https://github.com/PhilZ-cwm6/philz_touch_cwm6

Version Data


Status:
No Longer Updated

Created
2014-03-29
Terminal Updated
2016-01-05

You can fetch source from this link (
cm-11.0 branch
):
https://github.com/PhilZ-cwm6/philz_touch_cwm6

I no longer maintain the older branches
Before you offset, make sure yous can build stock cwm from cm-11.0 source
Once y’all can build stock CWM, just replace your bootable/recovery folder with this one and luncheon for your device

Device tree changes examples:


They are minimal and detailed beneath
You tin meet a few examples from here:

device tree: https://github.com/PhilZ-cwm6/philz_touch_cwm6_device_vendor/tree/cm-eleven.0
vold exfat/ntfs/f2fs kernel support: https://github.com/PhilZ-cwm6/android_system_vold/tree/cm-xi.0
selinux extensions for extra partitions: https://github.com/PhilZ-cwm6/android_external_sepolicy/tree/cm-11.0

To avoid modifying BoardConfig.mk and device.mk for all devices I support, I modified the build makefile:
https://github.com/PhilZ-cwm6/android_build/tree/cm-xi.0

Those are the just optional changes to get all features of this recovery mod.
To utilize f2fs/exfat/ntfs kernel back up, y’all should learn how to alter the kernel too. Else, skip the vold changes and flags (see below details)

Optional PhilZ Affect extra flags:


The beneath info are optional. Y’all should still be able to build without editing annihilation in device tree

1. bootable/recovery/boardconfig/BoardConfig.mk
   
   It is a quick style to add device specific tags without altering device tree. That style I can spot needed changes easier.

                                       # Info on some tags:  - KERNEL_EXFAT_MODULE_NAME: This will force minivold to apply much faster kernel modules instead of slow fuse information technology will merely work if you have modified vold sources (contact me for info) you'll likewise have to copy modules to ramdisk and load them in init.rc or a loader script y'all demand either an exfat enabled prebuilt kernel or to compile exfat modules along kernel y'all also need to patch minivold: [url]https://github.com/PhilZ-cwm6/android_system_vold[/url]  - KERNEL_NTFS_MODULE_NAME:    Aforementioned as in a higher place, but for ntfs.  - TARGET_USERIMAGES_USE_F2FS := truthful         will enable f2fs back up and ext4 <-> f2fs conversion and fill-in migration         plainly you demand to add f2fs support into the kernel         read near the extra.fstab use to employ specific and distinct f2fs and ext4 mountain options         else, it will drop to bare minimal ext4 or f2fs mount options if not defined in recovery.fstab  - BOARD_USE_MTK_LAYOUT :=   true         will enable backup/restore of boot, recovery and uboot partitions on MTK devices  - BOARD_MTK_BOOT_LABEL :=   "/bootimg"         This flag is optional, it is used only if BOARD_USE_MTK_LAYOUT is divers         If not defined while previous flag is enabled, default boot characterization is assumed "/bootimg"         Else, it is assigned the defined value         In fstab.device used past recovery (recovery.fstab), boot mount point must exist the aforementioned equally what we         define in label         It is likewise mandatory that it is defined to real device label (true cat /proc/dumchar_info)         Division size is grabbed during backup/restore from /proc/dumchar_info         uboot label is defined as "/uboot". It is automatically backed-upwardly/restored with boot and recovery         recovery label is e'er assumed to exist "/recovery"  - BOARD_HAS_LOW_RESOLUTION:   (optional) for all devices beneath 1024x768 resolution.   it forces default impact sensitivity to a lower value. It can be altered in GUI Settings  - BOOTLOADER_CMD_ARG:   This will override ro.bootloader.mode. Mostly used for Samsung devices to access download mode  - TARGET_COMMON_NAME   The device name that volition be displayed on recovery start and in Near dialogue  - BRIGHTNESS_SYS_FILE:   Needed to be able to alter screen effulgence  - ro.cwm.backup_partitions:   this can be ready on boot or during compile into default.prop. exp in device.mk:   PRODUCT_PROPERTY_OVERRIDES += \       ro.cwm.backup_partitions=/modemst1,/modemst2,/devlog    it will add together back up to fill-in/restore those partitions in nandroid custom jobs provided they are besides defined in recovery.fstab
                                     

2. device/brand/phone_name/device.mk
   

                                       PRODUCT_COPY_FILES += \     $(LOCAL_PATH)/rootdir/etc/extra.fstab:recovery/root/etc/extra.fstab
                                     

3. extra.fstab documentation:
   
   * Needed until fs_mgr_read_fstab() starts to parse blk_device2 entries
   * extra.fstab sample:

                                       # add here entries already existing in master device fstab, but for which you lot want a blk_device2, fs_type2 or fs_options2 # mount point must be the same, mmcblk device must be your device true path # you can set up the f2fs mountain options for partitions you desire to be able to toggle between f2fs/ext4 # information technology will enable faster transfer speed for devices supporting usb mountain storage # makes information technology possible to sectionalization vold managed storage (sdcard/usb disks) and format it to ext2/ext3 # used besides to stat for size of mtd/yaffs2 partitions  # blk_device2           # mount_point           fs_type2    fs_options2     flags (not used in actress.fstab lawmaking) /dev/cake/mmcblk0p28   /storage/sdcard0 	auto	    defaults		defaults /dev/block/mmcblk1p1	/storage/sdcard1 	auto	    defaults		defaults /dev/block/sda1		/storage/usbdisk0 	car	    defaults		defaults /dev/block/mmcblk0p30		/data		f2fs      [options] 	[flags]
                                     

If it doesn’t build or errors, post log/error hither and I will assistance if I can

Adding
Full
PhilZ Bear on version support for your device

• Compile for your device by replacing bootable/recovery contents with files from my git
• Set the needed options in bootable/recovery/boardconfig/BoardConfig.mk
• It is very of import to set the right options so that libtouch_gui can exist initialized properly
• Optional: you can add together your signature here, just do not remove other About ui_prints delight, go on credits
  https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/advanced_functions.c#L3328
• postal service a link to your thread or attach your recovery.img here and I will upload them to goo.im and main OP for official support
• If you lot accept errors, bugs or demand a specific characteristic for your custom kernel, only let me know by PM
• If errors are related to libtouch_gui, endeavour to disable the PHILZ_TOUCH_RECOVERY flag here by adding a #
  https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/Android.mk#L6
  Then, mail hither your error log when compiling

Missing sources in my github:


none, it is all open up source now

– all gui options, include touch on code
– Create Update.naught from current ROM or from pre-existing backups

– All the same, they are all enabled through the new libtouch_gui library. Just set your flags and compile it

Will libtouch_gui sources published?


They are open source now

Non for now. Why?

Respond: in this post

Can I include and use your libtouch_gui in my recovery modernistic ?


You lot are welcome, but:
– do not reverse code
– practice not binary edit it
– add credits in your code
– do not remove credits headers from sources and requite proper credit in your thread site
– post a link to this thread on your site/thread
– push fixes to my github if you find bugs that y’all fix or if you add new features

How to select your .android_secure path

Custom Backup and Restore menu

Open Recovery Script Support (ORS):
revised and adapted from original sk8erwitskil source

Odor File Manager Support
*Adapted from amarullz and sk8erwitskil
You get here the possibility to scan 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

Touch GUI Preferences:

This is another unique feature of this recovery and is built from scratch

Setup Free Scan Manner and Multi-goose egg Installer:

Pause on Logs:

i- what happens if I wipe/format/manufactory reset my data/media device?

format /data:
but data is wiped, exclude /data/media:

                                cd /information ; for f in $(ls -a | grep -v ^media$); do rm -rf $f; done
                              

format /sdcard
: simply /data/media or /information/media/0 (depending on setting you lot choose in Advanced menu) is wiped

                                rm -rf /sdcard/* rm -rf /sdcard/.*
                              

format /data and /data/media:
will result a true format on /information volume, obviously killing /data/mediaFactory reset:
will also preserve /data/media (rm -rf)Clean to Install a New ROM:
will do a factory reset (format /information, /cache, /datadata and sd-ext) + format /system +/- /preload. Your system will not kick until y’all install a new ROM

two- I backed up my data and I cannot observe it when I kicking into phone

Stock CWM and CM Updater app are using a non conventional linking for internal storage: internal storage is linked every bit /sdcard/0
PhilZ touch supports truthful /sdcard paths past linking information technology to either /data/media or /information/media/0
/sdcard/0 has no significant in PhilZ Touch unless you fix it to /data/media

Past default, if a folder /data/media/0 exists, PhilZ Touch volition default /sdcard to it, else it volition use /data/media.
The reward is for all stock +4.ii users: they can directly access their backups from /sdcard, while in main system and run across them on PC in MTP style.

You lot tin override that setting in Advanced Menu and force it to /data/media or revert to /data/media/0
I recommend moving all your old cwm path to /data/media/0/clockworkmod and set sdcard to /data/media/0 unless you are switching between stock CWM and this modernistic or you need CM Updater app

To sum information technology upward: for stock +4.2 rom users, go along default (/data/media/0). For CM users, if yous frequently use CM Updater to flash in recovery, forcefulness /data/media

3- I come up from stock CWM/TWRP and PhilZ Touch on cannot run into my backups

Read Answer 2

iv- Aroma file managing director doesn’t kickoff when I double tap screen

Read the guide to install aroma file managing director.
Path inverse in v5!
Read the /data/media/0 faq 2

5- CMUpdater cannot flash downlaoded files

If you lot become a /sdcard/0 error, information technology means you accept /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn’t support /information/media/0 and is faking recovery with a /sdcard/0 implementation

You lot still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater

6- How to wink a kicking.img or recovery.img file?

– Put your boot.img or/and recovery.img files under a subfolder in

clockworkmod/backup

on sdcards
exp: /sdcard/clockworkmod/backup/cm-ten.1-nightly_20130713/kick.img
– Navigate to Backup and Restore / Custom Backup and Restore / Custom Restore Job
– Unselect all partitions except boot and/or recovery
– Select >> Start Custom Backup Chore <<
– Scan to your fill-in location until your cm-10.1-nightly_20130713, and select any file within information technology
– You are done

7- My backups take a long fourth dimension to consummate

Get-go, brand sure you set compression to fast or depression. Depression pinch setting gives around 30% pinch with serenity no impact on speed. Rise compression value makes backups extremely slow with very little proceeds on space.

Stock CWM uses exfat fuse but without whatsoever buffering of writes. The end of information technology is a non usable matter for any backup considering of an incredibly slow write speed.
TWRP uses exfat fuse binary to do the backups + caches tar writes to ameliorate speed. This could cause data corruption on some devices.
PhilZ Bear upon uses patched kernel with native exfat support (static style) for Samsung devices and soon other brands. This is supposed to be the faster and safest way.
However, information technology seems to struggle on some devices because of the logging mode used past CWM

Solutions:
– hide progress bar in Nandroid Settings card: this will dramatically improve speed for many devices
– practice not use exfat
– modify exfat carte du jour to another brand. Ask in forum what people are using with good speed
– some users reported a real wearisome downwardly when carte du jour/device is hot. Allow your phone residue from intensive read/writes before starting a backup
– switch to another recovery like twrp if you cannot live with it. PhilZ Touch is compatible with TWRP and tin can backup/restore twrp format

8- You think you found a issues?

– Make sure your issue is recovery related
– All external sdcard bug: first format in PC with principal segmentation, tons of people are formatting as logical and come weep
– Reproduce your effect and while in recovery:
– Go to Advanced / Report Error
– Copy the /sdcard/clockworkmod/philz_recovery.log file and attach it hither
– Give detailed info about your issues
– Without these, at that place is little chance I can help y’all, so, do not get mad if I do not answer

9- Loki things

Locked bootloader? How to lokify before flashing:

• In Advanced Menu / Toggle Loki Support : enable automobile loki
• Wink the zip file and you are washed

PhilZ Touch recoveries that come in a zip file format AND released afterwards v6.01.two take a script in the cypher to lokify the recovery image during flash even if you are coming from older recoveries or TWRP (cheers @Wootever)

The included recovery.img in the zippo is non lokified, it will exist lokified during wink

If you are using a new CWM or PhilZ Bear upon with car-loki enabled, please disable it earlier flashing my zip files to avoid any event with double lokifying, if ever possible!

Unlocked bootloader users tin still extract the recovery.img file and restore information technology from inside recovery:

• put recovery.img in /sdcard/clockworkmod/backup/philz_update/recovery.img
• In Custom Fill-in and Restore card, unselect all except recovery
• validate to scan to the update recovery.img
• done

10- Assert error vii on device name when installing roms and updates

Start of v6.02.two, recoveries are based on cm-11.0 (KitKat) device tree.
In all nil installers, you accept a file called update-binary. It is the executable that volition procedure and interpret all commands in updater-script, which will practice all actions.

Older update-binary files cannot access arrangement assert props on kitkat based kernels.
Fixes:
– edit your updater-script in cypher file and remove all assert lines checking for device name. Use notepad++ or a linux editor
– manually alter your update-binary in the zero with a new i you take from a cm-xi.0 release
– revert to an older recovery earlier half-dozen.02.2
– ask your rom releaser to update his update-binary

Note: starting time of 6.09.6, this error is fixed. However, you tin can terminate up with error in FAQ 11

11- various status 7 errors: format() expects 5 args, got iv – set_permissions errors…

Showtime read FAQ x
Commencement of 6.09.6, recovery will analyze the update-binary that comes with your zip package. If it detects an outdated version, it volition be automatically replaced during flash.

This volition fix all assert getprop errors discussed in FAQ x (often used to cheque if the nil is meant to exist flashed on your device)

However, doing and then, can expose y’all to a agglomeration of new errors if the update-binary is +2 years sometime. In that case, the updater-script code used could non match the new update-binary:

The error “format() expects 5 args, got iv”
is caused by not using the beneath new format command in updater-script:

format(fs_type, partition_type, location, fs_size, mount_point)

exp:

                                format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-proper name/system", "0", "/system");
                              

The mistake due to failure on set_perm
is caused by using 2 years old update-binary
New ones volition arrest installation when setting permission fails on whatever file, while it was previously immune to proceed

Fixes:

– beginning of half dozen.15.4, PhilZ Bear upon added an option to force using the update-binary that comes in your aught. It volition make information technology work except for the assert for device name error. Even so, that mistake is very easy to fix by any one (see FAQ 10). The choice doesn’t stick on reboot, you accept to manually set it when yous flash such files. It is done on purpose to go along you warned about potential risks using such bad scripts often coming from a copy paste procedure
– hammer your ROM maker to keep up to his time, and look closer at his scripting and update-binary engine used

12- Fourth dimension fix for Qualcom Chips and other devices

On many Qualcom devices, setting the fourth dimension is disabled on dissimilar levels, depending on the device
New PhilZ Impact versions added a workaround to this limitation. The fixes do not modify in anyway the RTC flags in kernel, as information technology is not recommended by Qualcom

–

Qualcom Time Daemon:
This is the recommended selection. It will load the fourth dimension daemon from /system and will go on your recovery time in sync with ROM.
All the same, many CM/AOKP/Custom Roms do not have a proper implementation of the daemon. Enquire your ROM dev to properly implement Qualcom proprietary binaries and RTC permissions.

–

Use RTC Time Kickoff:
This is the second workaround, recommended for ROMs without proper time daemon. You accept to enable the choice.
Subsequently that, information technology will ask you to setup the actual time/appointment manually. Do it AND Validate your choice to apply the actual time.
Enabling the offset style without manually setting correct time AND validating your option has no issue!

–

Attempt Force Persist on Reboot:
This is your concluding option, if all other options failed. Disable previous 2 options and enable this i.
You will need to setup time/engagement manually AND validate your choice. Else, it won’t have any issue.

–

Normal/manual way: Non Qualcom based devices, tin can simply utilize the default mode to fix time/date manually

xiii- My ROM maker advises another recovery

If an installer script cannot run on PhilZ Bear upon, it won’t run on CWM. PhilZ Touch on is but a CWM mod in that regard. Installer is not modified

Rule of thumb: If a ROM cooker says “YOU MUST USE A GIVEN RECOVERY”, be sure at that place are bugs in his work
A properly formatted updater-script, beat kid scripts or odor scripts should be able to run on any recovery as it should telephone call real blk device paths and not “pre-defined” mountain points

Mountain points WILL vary from recovery to another and mayhap from a version to another. Relying on them is a bad idea

Also, many practice miss proper edify scripting rules:
– /sdcard is a symlink, not a folder since years now (/data/media)
– you cannot extract without mounting showtime
– you must create your paths. Installer won’t be verifying you lot did so
– you cannot mountain vold paths (sdcard, usb storage…) past calling the mountain point in a beat out script. Expect at your fstab nether recovery to sympathise why

If a rom maker has issues to understand this, he can ask for help here or in an edify scripting thread

14- F2FS <-> EXT4 format migration

• Under “mounts and storage” menu, if “toggle f2fs <-> ext4 migration” is enabled, whenever we endeavor to format an ext4 or f2fs segmentation, we get a prompt to convert betwixt f2fs/ext4
• To convert /data on /information/media devices, we must as always select the “/data and /data/media” carte
• Nandroid implementation to migrate your information/ROM from ext4 to f2fs:
  – backup your existing data
  – in “mounts and storage”, format the partitions you want to convert to f2fs
  – restore your data
  – on restore, if both backup paradigm and target sectionalisation has different fstype and fstype is either ext4 or f2fs, we favour target devise fsytpe (data migration)​