[i919x][CWM Advanced Edition] PhilZ Touch

Search This thread

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
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

Main thread + features + install instructions + dev support
http://xdaforums.com/showthread.php?t=2201860


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


Download links
Last version can be found here:
Galaxy S4 Mini

i9190 (serrano3gxx)
i9192 (serranodsub)
i9195 (serranoltexx)

http://goo.im/devs/philz_touch/CWM_Advanced_Edition
 
Last edited:

arco68

Recognized Developer
Oct 11, 2010
2,913
24,822
Here ya go:

Code:
lrwxrwxrwx root     root              2013-09-29 20:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-09-29 20:14 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2013-09-29 20:14 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2013-09-29 20:14 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2013-09-29 20:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-09-29 20:14 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2013-09-29 20:14 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2013-09-29 20:14 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2013-09-29 20:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-09-29 20:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-09-29 20:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2013-09-29 20:14 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-09-29 20:14 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2013-09-29 20:14 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2013-09-29 20:14 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2013-09-29 20:14 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2013-09-29 20:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-09-29 20:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-09-29 20:14 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-09-29 20:14 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-09-29 20:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2013-09-29 20:14 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2013-09-29 20:14 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-09-29 20:14 userdata -> /dev/block/mmcblk0p24
Also output of /proc/partitions if needed:

Code:
major minor  #blocks  name
 179        0    7634944 mmcblk0
 179        1      61440 mmcblk0p1
 179        2        128 mmcblk0p2
 179        3        256 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5       2048 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7        512 mmcblk0p7
 179        8      12800 mmcblk0p8
 179        9       8192 mmcblk0p9
 179       10      13952 mmcblk0p10
 179       11       3072 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13      10240 mmcblk0p13
 179       14      10240 mmcblk0p14
 179       15      10240 mmcblk0p15
 179       16       7160 mmcblk0p16
 179       17       3072 mmcblk0p17
 179       18          8 mmcblk0p18
 179       19       8192 mmcblk0p19
 179       20      12288 mmcblk0p20
 179       21    1536000 mmcblk0p21
 179       22     204800 mmcblk0p22
 179       23      36864 mmcblk0p23
 179       24    5685231 mmcblk0p24
 179       32    1955840 mmcblk1
 179       33    1955809 mmcblk1p1
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Here ya go:

Code:
lrwxrwxrwx root     root              2013-09-29 20:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2013-09-29 20:14 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2013-09-29 20:14 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2013-09-29 20:14 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2013-09-29 20:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2013-09-29 20:14 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2013-09-29 20:14 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2013-09-29 20:14 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2013-09-29 20:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2013-09-29 20:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2013-09-29 20:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2013-09-29 20:14 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2013-09-29 20:14 param -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2013-09-29 20:14 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2013-09-29 20:14 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2013-09-29 20:14 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2013-09-29 20:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2013-09-29 20:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2013-09-29 20:14 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2013-09-29 20:14 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2013-09-29 20:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2013-09-29 20:14 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2013-09-29 20:14 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2013-09-29 20:14 userdata -> /dev/block/mmcblk0p24
Also output of /proc/partitions if needed:

Code:
major minor  #blocks  name
 179        0    7634944 mmcblk0
 179        1      61440 mmcblk0p1
 179        2        128 mmcblk0p2
 179        3        256 mmcblk0p3
 179        4        512 mmcblk0p4
 179        5       2048 mmcblk0p5
 179        6        512 mmcblk0p6
 179        7        512 mmcblk0p7
 179        8      12800 mmcblk0p8
 179        9       8192 mmcblk0p9
 179       10      13952 mmcblk0p10
 179       11       3072 mmcblk0p11
 179       12       3072 mmcblk0p12
 179       13      10240 mmcblk0p13
 179       14      10240 mmcblk0p14
 179       15      10240 mmcblk0p15
 179       16       7160 mmcblk0p16
 179       17       3072 mmcblk0p17
 179       18          8 mmcblk0p18
 179       19       8192 mmcblk0p19
 179       20      12288 mmcblk0p20
 179       21    1536000 mmcblk0p21
 179       22     204800 mmcblk0p22
 179       23      36864 mmcblk0p23
 179       24    5685231 mmcblk0p24
 179       32    1955840 mmcblk1
 179       33    1955809 mmcblk1p1

This was fast, thank you :good:
Just finished downloading stock recovery.img to repack with better exfat support than fuse
Meanwhile, you can get a cm build in above links, I just populated
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Have one question:
i9190 and i9195 can use same kernel? Do they have same /proc/partitions links?

If no, anyone can upload recovery.img from a recent Samsung stock firmware for i9190?
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
New files

- i9195: repack with stock Samsung ramdisk for faster exfat support + enable mount usb storage for external sd
- serranoltexx: cm-10.1 repack
http://d-h.st/users/philz_touch/?fld_id=25693#files

Please, test these in both versions:
- adb shell is root?
- adb sideload works?
- mount usb storage for external sd is ok?

Why this: Samsung kernel has support for exfat using kernel modules, which is way faster than fuse, used by cyanogenmod builds
However, on the S4 (i9505), Samsung introduced wired policies that could cause adb shell to fail to have root rights
I also disabled wired Samsung policies to enable flashing cm-10.2 ROMs and maybe get adb shell as root
I am not sure if both above versions have usb storage mount working + adb sideload

A detailed report about each of these will make it possible to improve support
 

proxuser

Senior Member
Jul 2, 2010
1,836
5,712
www.emexci.com
New files

- i9195: repack with stock Samsung ramdisk for faster exfat support + enable mount usb storage for external sd
- serranoltexx: cm-10.1 repack
http://d-h.st/users/philz_touch/?fld_id=25693#files

Please, test these in both versions:
- adb shell is root?
- adb sideload works?
- mount usb storage for external sd is ok?

Why this: Samsung kernel has support for exfat using kernel modules, which is way faster than fuse, used by cyanogenmod builds
However, on the S4 (i9505), Samsung introduced wired policies that could cause adb shell to fail to have root rights
I also disabled wired Samsung policies to enable flashing cm-10.2 ROMs and maybe get adb shell as root
I am not sure if both above versions have usb storage mount working + adb sideload

A detailed report about each of these will make it possible to improve support

hi thx for the good job.

install with your script doesnt worked on i9195 but with cm10.1 head it worked.

i have not tested things you want because i am not at home. but recovery working. first boot need 3-5min. install rom worked but it doesnt mount my 64gb samsung microsd. only internal.

this one is working install to i9195

Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || 
       getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || 
       getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" || 
       getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");

Sent from my GT-I9195 using xda premium
 
Last edited:
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
hi thx for the good job.

install with your script doesnt worked on i9195 but with cm10.1 head it worked.

i have not tested things you want because i am not at home. but recovery working. first boot need 3-5min. install rom worked but it doesnt mount my 64gb samsung microsd. only internal.

this one is working install to i9195

Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || 
       getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || 
       getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" || 
       getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");

Sent from my GT-I9195 using xda premium

I am re-uploading zip files with correct serranolte and serrano3g most often used tags
Should be online soon
Let me know about questions I asked above so that we can look to fix things
 
  • Like
Reactions: Trunghuy90

proxuser

Senior Member
Jul 2, 2010
1,836
5,712
www.emexci.com
tested: philz_touch_5.15.9-i9195.zip

- boot to recovery need 2-3 minutes.
- E:can't mount /external_sd/

mount sdcard and internal (cant test it now but in ubuntu it doesnt show)

- adb shell is root?

look attachaed picture 1

- sideload works ?
yes it works
look attached picture 2

install cm10.2 works, it boots :)

if boot time be fixed its very usable and fast recovery. thx
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
tested: philz_touch_5.15.9-i9195.zip

- boot to recovery need 2-3 minutes.
- E:can't mount /external_sd/

mount sdcard and internal (cant test it now but in ubuntu it doesnt show)

- adb shell is root?

look attachaed picture 1

- sideload works ?
yes it works
look attached picture 2

install cm10.2 works, it boots :)

if boot time be fixed its very usable and fast recovery. thx

Sadly, it is probably a kernel issue. Only fix is custom kernel to fix these, compiled from Samsung sources, with a few fixes to enable exfat loading, root and probably disable flashing sensors which causes the delay

Meanwhile, I will drop to a pure cyanogenmod based ramdisk instead of Samsung
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
So, any more feedback to confirm mounting external storage works or not?
 

stiffmeister75

Senior Member
Nov 4, 2010
88
25
Hi Phil3759,

For my S4 Mini I9195 only the philz_touch_5.15.9-serranoltexx.zip worked.
With this recovery i could make a backup to the ext. SD, but it took about 25 minutes.
When i flash philz_touch_5.15.9-i9195.zip, then the phone stuck always on booting to recovery
and i have to remove the battery an reflash with odin.

stiff
 

citymen34

Senior Member
Feb 9, 2013
633
3,908
istanbul

Top Liked Posts

  • There are no posts matching your filters.
  • 53
    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

    Main thread + features + install instructions + dev support
    http://xdaforums.com/showthread.php?t=2201860


    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


    Download links
    Last version can be found here:
    Galaxy S4 Mini

    i9190 (serrano3gxx)
    i9192 (serranodsub)
    i9195 (serranoltexx)

    http://goo.im/devs/philz_touch/CWM_Advanced_Edition
    6
    New version based on cwm 6.0.5.0 is up.

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

    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 1.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 1.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 1.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 1.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 @KumaJaya
    - 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 1.22


    Download

    6
    Here ya go:

    Code:
    lrwxrwxrwx root     root              2013-09-29 20:14 aboot -> /dev/block/mmcblk0p5
    lrwxrwxrwx root     root              2013-09-29 20:14 backup -> /dev/block/mmcblk0p16
    lrwxrwxrwx root     root              2013-09-29 20:14 boot -> /dev/block/mmcblk0p13
    lrwxrwxrwx root     root              2013-09-29 20:14 cache -> /dev/block/mmcblk0p22
    lrwxrwxrwx root     root              2013-09-29 20:14 efs -> /dev/block/mmcblk0p10
    lrwxrwxrwx root     root              2013-09-29 20:14 fota -> /dev/block/mmcblk0p15
    lrwxrwxrwx root     root              2013-09-29 20:14 fsg -> /dev/block/mmcblk0p17
    lrwxrwxrwx root     root              2013-09-29 20:14 hidden -> /dev/block/mmcblk0p23
    lrwxrwxrwx root     root              2013-09-29 20:14 modem -> /dev/block/mmcblk0p1
    lrwxrwxrwx root     root              2013-09-29 20:14 modemst1 -> /dev/block/mmcblk0p11
    lrwxrwxrwx root     root              2013-09-29 20:14 modemst2 -> /dev/block/mmcblk0p12
    lrwxrwxrwx root     root              2013-09-29 20:14 pad -> /dev/block/mmcblk0p8
    lrwxrwxrwx root     root              2013-09-29 20:14 param -> /dev/block/mmcblk0p9
    lrwxrwxrwx root     root              2013-09-29 20:14 persdata -> /dev/block/mmcblk0p20
    lrwxrwxrwx root     root              2013-09-29 20:14 persist -> /dev/block/mmcblk0p19
    lrwxrwxrwx root     root              2013-09-29 20:14 recovery -> /dev/block/mmcblk0p14
    lrwxrwxrwx root     root              2013-09-29 20:14 rpm -> /dev/block/mmcblk0p6
    lrwxrwxrwx root     root              2013-09-29 20:14 sbl1 -> /dev/block/mmcblk0p2
    lrwxrwxrwx root     root              2013-09-29 20:14 sbl2 -> /dev/block/mmcblk0p3
    lrwxrwxrwx root     root              2013-09-29 20:14 sbl3 -> /dev/block/mmcblk0p4
    lrwxrwxrwx root     root              2013-09-29 20:14 ssd -> /dev/block/mmcblk0p18
    lrwxrwxrwx root     root              2013-09-29 20:14 system -> /dev/block/mmcblk0p21
    lrwxrwxrwx root     root              2013-09-29 20:14 tz -> /dev/block/mmcblk0p7
    lrwxrwxrwx root     root              2013-09-29 20:14 userdata -> /dev/block/mmcblk0p24
    Also output of /proc/partitions if needed:

    Code:
    major minor  #blocks  name
     179        0    7634944 mmcblk0
     179        1      61440 mmcblk0p1
     179        2        128 mmcblk0p2
     179        3        256 mmcblk0p3
     179        4        512 mmcblk0p4
     179        5       2048 mmcblk0p5
     179        6        512 mmcblk0p6
     179        7        512 mmcblk0p7
     179        8      12800 mmcblk0p8
     179        9       8192 mmcblk0p9
     179       10      13952 mmcblk0p10
     179       11       3072 mmcblk0p11
     179       12       3072 mmcblk0p12
     179       13      10240 mmcblk0p13
     179       14      10240 mmcblk0p14
     179       15      10240 mmcblk0p15
     179       16       7160 mmcblk0p16
     179       17       3072 mmcblk0p17
     179       18          8 mmcblk0p18
     179       19       8192 mmcblk0p19
     179       20      12288 mmcblk0p20
     179       21    1536000 mmcblk0p21
     179       22     204800 mmcblk0p22
     179       23      36864 mmcblk0p23
     179       24    5685231 mmcblk0p24
     179       32    1955840 mmcblk1
     179       33    1955809 mmcblk1p1
    6
    updated to new 6.08.8 to mainly add new perf mode
    6
    Guys new version is up.

    Changelog

    6.41.6 (12.05.2014)
    - update exfat to dorimanx 1.2.9 latest sources
    - fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
    - repo sync latest sources
    - Galaxy Tab Pro 8.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 1.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 240x320 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 1.20: support custom key files (BOARD_CUSTOM_RECOVERY_KEYMAPPING)

    6.29.9 (27.04.2014)
    - merge "Recovery: swap XY on swipe controls"
    - shell pipe: set exit code to error if any pipe element fails
    * this was causing backup state to be reported good while tar command failed

    6.29.7 (27.04.2014)
    - minitar: add options help and change log
    - minitar: build as a static library to spare 150 kb (only 16kb size increase)

    6.29.2 (26.04.2014)
    - fix potential bug when verifying root and recovery state on exit
    - merge "Fix verify_root_and_recovery menu selections":
    - hide the Go Back button from confirm menu
    - merge "Prohibit mounting/formatting swap partitions in recovery"
    - add minitar binary to /sbin instead of busybox tar
    - minitar: enable more options, enable long options, fix selinux backup/restore, enhance GNU tar compatibility
    - revert RECOVERY_NEED_SELINUX_FIX patch
    - enable seamless backup/restore selinux context using minitar binary
    - TWRP mode: support backup/restore of selinux context
    - libtouch_gui 1.19

    6.27.6 (21.04.2014)
    - add libtouch_gui for armv6 devices, thanks @yuweng and androidarmv6 team
    - loki: sync to upstream
    - Galaxy S5 SM-G900H (k3gxx): update kernel to XXU1ANCI
    - Amazon Kindle Fire HD 7 (tate): fix background and virtual keys
    - Amazon Kindle Fire HD (jem & tate): fix display battery level
    - LG G2: repack on older cm 6.25.4 kernel to fix graphic issues
    - New: HTC One M8 Verizon (m8vzw)
    - New: LG Optimus One P500 (p500) - arm v6 based

    6.27.2 (18.04.2014)
    - libtouch_gui 1.18
    - confirm cancel nandroid jobs (prompt to press 'Back' twice or resume after 5 secs)
    - vibrate after backup/restore operations

    6.27.0 (17.04.2014)
    - MTK support: fix backup & restore of boot/recovery/uboot partitions
    - MTK devices: improve error handling of partitions size
    - do not consider su symlink in /system/bin as a broken root
    - New: Amazon Kindle Fire HD 7 (tate)
    - New: Amazon Kindle Fire HD 8.9 (jem)
    - New: Galaxy S5 SM-G900H Exynos variant (k3gxx)
    [/hide]

    Download