[2015.10.09]CWM 6.0.5.1 - PhilZ Touch 6.59.0 (libtouch_gui 1.42)

[licensedtoquill]

The backups are tar.gz archives, if you have CWM mode and compression enabled. They are split into many files you can concatenate using cat

Basically, in a linux box, you can run this:

cat backup_file_image* | pigz -d -c | tar -xpv

or

cat backup_file_image* | tar -xzpv

backup_file_image can be system.ext4.tar.gz for example

Note that windows tools cannot open the tar.gz archives because they containe the selinux context extensions, not supported by most windows archive tools as long as I tested

If the image is a tar not compressed (no .gz extension), use this:

cat backup_file_image* | tar -xpv

Real example if your archive set consists of the following files:


command:

cat data.ext4.tar.gz* | pigz -d -c | tar -xpv

or

cat data.ext4.tar.gz* | tar -xzpv

Basically, cat command will concatenate the .a, .b, .c and so on files into one file and extract the resulting archive

To get the whole tar.gz file, just run the cat part of the command

Thanks for that succinct description Phil, I do use Mint on all boxes which which huff'n'puff under windows but was relatively uncomfortable using command lines: I will have to GET comfortable now!!

I was kinda surprised that Philz recovery was so easy to implement and load and seems to be so versatile and now discover that I can retrieve data off a (not bricked but) DEAD machine which won't even load Android using it! However many times I implement TWRP successfully with Odin, it constantly recovery-boots to a black screen.

Thanks for responding on page 635 of a thread: Are you SURE this amazing app is end-of-life?

 

[Phil3759]

Are you SURE this amazing app is end-of-life?

Sadly yes

If I'd ever get in run again, it will be on rebasing with TWRP. However, for now, real life took all my time + the extra on-sleep time I was using to code

 

[BadUsername]

Sadly yes

If I'd ever get in run again, it will be on rebasing with TWRP. However, for now, real life took all my time + the extra on-sleep time I was using to code

I'd assume that would be a massive project, is that starting from scratch? I assume nothing could be ported.

Real life needs to take priority, I don't mind twrp, just miss everything else this had to offer. It was fun to use and always reliable, never had an issue. Probably because every problem seemed to be instantly addressed.

A philz recovery based on twrp would be amazing through, I could only imagine the crazy customizations and features that are unique to your recovery.

Regardless of your future plans with this, thank you for all you've done for this community. You've certainly impacted my experience and made Android an exciting platform for me to explore.

 

[fix-this!]

I used to use philz recovery all the time. Sad the project is dead but I wish you luck phil, thanks for the memories. Twrp isnt soo bad to use I guess.

 

[licensedtoquill]

Sadly yes

If I'd ever get in run again, it will be on rebasing with TWRP. However, for now, real life took all my time + the extra on-sleep time I was using to code

I have been struggling with the Linux commands and meanwhile on your suggestion as to it being end-of-life, installed TWRP. Then I managed to use Odin to flash a stock ROM onto my s3, successfully!! But it seems to have wiped out all my data so i am wondering if there is any app I can use to restore the Philz-backed up data from my SD card back onto the same phone?
Or do I have to re-install Philz over twrp and use the Philz restore function from SD card there?

 

[Pjerisimo]

I have been struggling with the Linux commands and meanwhile on your suggestion as to it being end-of-life, installed TWRP. Then I managed to use Odin to flash a stock ROM onto my s3, successfully!! But it seems to have wiped out all my data so i am wondering if there is any app I can use to restore the Philz-backed up data from my SD card back onto the same phone?
Or do I have to re-install Philz over twrp and use the Philz restore function from SD card there?

Reflash philz and then restore backup.

 

[Jawor245]

Hi i know its discontinued project but is it possible to build with cm12.1 source on arm64 device?

 

[lystab]

setting date/time using "Try Force Persist after Reboot"-Option left phone unusable

just in case anybody else runs into the same difficulty:

Environment: Galaxy S4 I9505 (root) | Android 5.0.1 | Recovery: PhilZ Touch 6.59.0 with ClockworkMod v6.0.5.1

Objective: using "Try Force Persist after Reboot"-Option in manual date/time setup of PhilZ recovery rendered the phone unusable with many app crashes ("unfortunately app has stopped") and the error "UIDs inconsistent - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable".

Cause: the phone clock was set to the year 1923 when using manual date/time setting option in PhilZ recovery (sometimes different years like 1942). Qualcomm boards read the last clock settings from "/data/time/ats_1" and "/data/time/ats_2" on boot. These are binary closed source files. They differ between versions of Qualcomm boards. The method used by PhilZ recovery to persist the clock settings is not suitable for Galaxy S4 I9505 phones and let to date/time settings way out of range.

Solution: used AROMA filemanager within PhilZ recovery to restore a former backup version of ats_1 and ats_2 files.

ea4hs3e6

 

[Phil3759]

just in case anybody else runs into the same difficulty:

Environment: Galaxy S4 I9505 (root) | Android 5.0.1 | Recovery: PhilZ Touch 6.59.0 with ClockworkMod v6.0.5.1

Objective: using "Try Force Persist after Reboot"-Option in manual date/time setup of PhilZ recovery rendered the phone unusable with many app crashes ("unfortunately app has stopped") and the error "UIDs inconsistent - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable".

Cause: the phone clock was set to the year 1923 when using manual date/time setting option in PhilZ recovery (sometimes different years like 1942). Qualcomm boards read the last clock settings from "/data/time/ats_1" and "/data/time/ats_2" on boot. These are binary closed source files. They differ between versions of Qualcomm boards. The method used by PhilZ recovery to persist the clock settings is not suitable for Galaxy S4 I9505 phones and let to date/time settings way out of range.

Solution: used AROMA filemanager within PhilZ recovery to restore a former backup version of ats_1 and ats_2 files.

ea4hs3e6

That option was needed on some early 4.x android versions. Later, the Qualcom fix was implemented.
You should use Qualcom option for Qualcom devices

The force option never did any harm in my tests, but I did not test under Android 5.x. It shouldn't unless Samsung did implement time in an uncommon way

 

[lystab]

thanks for your quick reply. Using the "Qualcomm Time Daemon" resulted in the date set to some year between 1970 and 1997. The implementation of the Qualcomm clock on the Samsung Galaxy S4 with Android 5.x seems to be quite odd.

 

[hazmatkid]

Is it ready for xt 1625

 

[zputnyq]

Help me please.
I'm having this probkem.

When I try to backup .android_secure in custom backup of philz touch it always says "keep only one folder bla bla bla"
I read in an article about .android_secure folder it said that there are two folder considered the same, one in internal storage & the other in external storage (micro sdcard). Based on that, then I tried to rename one so philz touch won't detect it but the notification "keep only one folder" still appears.
Can u show me how to solve it?

 

[o.ahmed]

can i use this CWM 6.0.5.1 - PhilZ Touch 6.59.0
for new android 5.x.x and 6.x.x for Samsung devices
to take back up from one and restore it to another
by useing odin to flash CWM
like models
i545
l720
l720t
...
is it necessary to have root before flashing cmw

 

[It_ler]

can i use this CWM 6.0.5.1 - PhilZ Touch 6.59.0
for new android 5.x.x and 6.x.x for Samsung devices
to take back up from one and restore it to another
by useing odin to flash CWM
like models
i545
l720
l720t
...
is it necessary to have root before flashing cmw

As I am using TWRP, IDK if this recovery will work on your device(s).
You don't need root if you flash the recovery tar file with PC Odin.

Sent from my Samsung Galaxy S5 using XDA Labs

 

[o.ahmed]

can i use this CWM 6.0.5.1 - PhilZ Touch 6.59.0
for new android 5.x.x and 6.x.x for Samsung devices
to take back up from one and restore it to another
by useing odin to flash CWM
like models
i545
l720
l720t

does cwm will give me ability to restore and backup rooms fro like models?
and did it brick my deceives if flashing cwm stooped?

 

[S3Pleb.]

[*]start odin3 and configure it as in picture below
..

This... can you re-upload the image or tell me what configuration I should use?

 

[KoSett]

Please add oppo a37 (neo9) .We need custom recovery.

 

[DSA]

Please add oppo a37 (neo9) .We need custom recovery.

who?

 

[KoSett]

hi

who?

I am oppo a37 user, We need Custom recovery. Help our device.

 

[stormeye25]

Hello, I have an MT6580 and when I flash the recovery, it goes in bootloop even after deleting dalvik cache... do you have any advice please?