[d2lte/d2spr][CWM ADV.] OFFICIAL PhilZ-Touch Recovery 6.48.4[7.06.14]

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

Click to expand...

Click to collapse

SPH-L710
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

Click to expand...

Click to collapse

11- various status 7 errors: format() expects 5 args, got 4 - set_permissions errors...

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

This will fix all assert getprop errors discussed in FAQ 10 (often used to check if the zip is meant to be flashed on your device)

However, doing so, can expose you to a bunch of new errors if the update-binary is +2 years old. In that case, the updater-script code used could not match the new update-binary:

The error "format() expects 5 args, got 4" is caused by not using the below new format command in updater-script:

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

Click to expand...

Click to collapse

exp:

Code:

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

The error due to failure on set_perm is caused by using 2 years old update-binary
New ones will abort installation when setting permission fails on any file, while it was previously allowed to continue

Fixes:
- start of 6.15.4, PhilZ Touch added an option to force using the update-binary that comes in your zip. It will make it work except for the assert for device name error. However, that error is very easy to fix by any one (see FAQ 10). The option doesn't stick on reboot, you have to manually set it when you flash such files. It is done on purpose to keep 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

Click to expand...

Click to collapse