[jewel][CWM Advanced Edition] PhilZ Touch

Phil3759 · Feb 9, 2014

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://forum.xda-developers.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:

HTC Evo 4G LTE (jewel)
For new Sense 5 bootloader: use 6.13.6 and above

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

Magnum_Enforcer · Jan 4, 2014 at 10:33 PM

So does this recovery have the same issue as the original CWM for the HTC EVO 4G LTE, which caused problems with the /misc partition?

Sent from my HTC EVO 4G LTE

Phil3759 · Jan 4, 2014 at 10:34 PM

FinZ28 said:
So does this recovery have the same issue as the original CWM for the HTC EVO 4G LTE, which caused problems with the /misc partition?

Sent from my HTC EVO 4G LTE

It is based on original CWM, however handling partitions is a bit different
What was your issue exactly as stock CWM doesn't use /misc?

Magnum_Enforcer · Jan 4, 2014 at 10:37 PM

http://forum.xda-developers.com/showthread.php?t=1675430

I never used it myself. I'm sure more experienced users who actually dealt with the issue will chime in.

Sent from my HTC EVO 4G LTE

Phil3759 · Jan 4, 2014 at 10:40 PM

FinZ28 said:
http://forum.xda-developers.com/showthread.php?t=1675430

I never used it myself. I'm sure more experienced users who actually dealt with the issue will chime in.

Sent from my HTC EVO 4G LTE

I hope that after near 2 years CM device tree was fixed for that!
This is based on the KitKat branch

Magnum_Enforcer · Jan 4, 2014 at 10:46 PM

Phil3759 said:
I hope that after near 2 years CM device tree was fixed for that!
This is based on the KitKat branch

Maybe so, but TWRP has been the only recovery for the EVO LTE otherwise.

Sent from my HTC EVO 4G LTE

Phil3759 · Jan 4, 2014 at 11:04 PM

Well
Guess some one has to back up his /misc and flash the bad ass

chemjb · Jan 5, 2014

Im about to flash it via image flash gui. How would I know if my misc if messed up?

Sent from my EVO using Tapatalk

Edit: flashed it and a few things.

while installing viper rom the asert fails and can't flash it.

I like the option to clone current rom to update.zip but it freezes when creating the zip.

other than that it seem pretty good.

thank you

xHausx · Jan 5, 2014 at 12:58 AM

If I remember correctly it was just overwriting the first few bytes of the misc partition with boot flags when it should contain the firmware version instead. Commenting it out in the fstab should be enough to prevent it.

scottspa74 · Jan 5, 2014 at 2:05 AM

I saw this recovery available for my daughters Samsung tab 3 the other day. I know some users in that forum really like it.

Thanks for sharing to jewel.

Sent from my EVO 4G LTE using XDA Premium 4 mobile app

Phil3759 · Jan 5, 2014 at 1:29 PM

chemjb said:
Im about to flash it via image flash gui. How would I know if my misc if messed up?

Sent from my EVO using Tapatalk

Edit: flashed it and a few things.

while installing viper rom the asert fails and can't flash it.

I like the option to clone current rom to update.zip but it freezes when creating the zip.

other than that it seem pretty good.

thank you

Creating the zip takes a lot of time without showing any progress
Just be patient

xHausx said:
If I remember correctly it was just overwriting the first few bytes of the misc partition with boot flags when it should contain the firmware version instead. Commenting it out in the fstab should be enough to prevent it.

Nothing in the fstab would overwrite firmware actually
Here's the fstab used in recovery, so that you can check if something is wrongly mapped

Code:

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

#<src>						<mnt_point>	<type>	<mnt_flags and options>					<fs_mgr_flags>
/dev/block/mmcblk0p21	/boot		emmc	defaults						defaults
/dev/block/mmcblk0p22	/recovery	emmc	defaults						defaults
/dev/block/mmcblk0p26	/devlog		ext4	noatime,nosuid,nodev,barrier=0				wait
/dev/block/mmcblk0p35	/system		ext4	rw,noatime,barrier=0					wait
/dev/block/mmcblk0p36	/cache		ext4	noatime,nosuid,nodev,barrier=0				wait
/dev/block/mmcblk0p37	/data		ext4	noatime,nosuid,nodev,noauto_da_alloc,barrier=0		wait,encryptable=footer,length=-16384

# SD card
/devices/platform/msm_sdcc.1/mmc_host/mmc0	auto	auto	defaults		voldmanaged=sdcard0:38,noemulatedsd
/devices/platform/msm_sdcc.3/mmc_host/mmc1	auto	auto	defaults		voldmanaged=sdcard1:auto

# USB storage
/devices/platform/msm_hsusb_host/usb	auto	auto	defaults			voldmanaged=usbdisk:auto

I also see that @mdmower is implied in maintaining your repo, so I doubt he makes crap as he's one of the most rigorous maintainers

xHausx · Jan 5, 2014 at 10:31 PM

Phil3759 said:

Nothing in the fstab would overwrite firmware actually
Here's the fstab used in recovery, so that you can check if something is wrongly mapped

Code:

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

#<src>						<mnt_point>	<type>	<mnt_flags and options>					<fs_mgr_flags>
/dev/block/mmcblk0p21	/boot		emmc	defaults						defaults
/dev/block/mmcblk0p22	/recovery	emmc	defaults						defaults
/dev/block/mmcblk0p26	/devlog		ext4	noatime,nosuid,nodev,barrier=0				wait
/dev/block/mmcblk0p35	/system		ext4	rw,noatime,barrier=0					wait
/dev/block/mmcblk0p36	/cache		ext4	noatime,nosuid,nodev,barrier=0				wait
/dev/block/mmcblk0p37	/data		ext4	noatime,nosuid,nodev,noauto_da_alloc,barrier=0		wait,encryptable=footer,length=-16384

# SD card
/devices/platform/msm_sdcc.1/mmc_host/mmc0	auto	auto	defaults		voldmanaged=sdcard0:38,noemulatedsd
/devices/platform/msm_sdcc.3/mmc_host/mmc1	auto	auto	defaults		voldmanaged=sdcard1:auto

# USB storage
/devices/platform/msm_hsusb_host/usb	auto	auto	defaults			voldmanaged=usbdisk:auto

I also see that @mdmower is implied in maintaining your repo, so I doubt he makes crap as he's one of the most rigorous maintainers

Ohh yeah, you should be good if it's not even in the fstab.

I don't think anyone meant to imply that it was someones fault, more of just a heads up about it. As far as I know leaving it undefined doesn't hurt anything so it's unlikely anyone ever took the time to troubleshoot it.

It's incredibly easy to fix but there was no way to get s-off when a lot of people had it happen to them. So it could turn into a pain if you needed to run a RUU.

Captain_Throwback · Jan 14, 2014 at 2:44 PM

Has anyone actually confirmed their misc partition is intact after flashing this? I realize there's no reason it shouldn't be, but wanted to see if there was confirmation yet. Otherwise I can be the guinea pig, I suppose.

Captain_Throwback · Jan 15, 2014 at 12:29 AM

Also, does this version support SELinux, so that kitkat ROMs can be flashed?

scottspa74 · Jan 18, 2014 at 7:28 AM

Captain_Throwback said:
Also, does this version support SELinux, so that kitkat ROMs can be flashed?

Hey capn, 3rd post mentions this is based off 4.4 CWM branch, so it would reason it has SElinux, but that obviously isnt confirmation. Do you still have the misc file to fix the broken partition if this breaks it?

Sent from my EVO 4G LTE using XDA Premium 4 mobile app

Magnum_Enforcer · Jan 18, 2014

scottspa74 said:
Hey capn, 3rd post mentions this is based off 4.4 CWM branch, so it would reason it has SElinux, but that obviously isnt confirmation. Do you still have the misc file to fix the broken partition if this breaks it?

Sent from my EVO 4G LTE using XDA Premium 4 mobile app

The file used to be in the other CWM thread. Hopefully it's not needed now.

Sent from my HTC EVO 4G LTE

gunfromsako · Jan 18, 2014 at 8:24 PM

Thanks for bringing this over phill! I was going to ask since I use it on my n7 but I know u you have a lot on your plate. Imho this is a more "reliable" recovery than others.

Sent from my EVO using Tapatalk

Magnum_Enforcer · Feb 3, 2014 at 3:06 AM

Finally got this recovery installed earlier. Misc partition is fine. So far, so good. Looks great and lots of options:good:

Magnum_Enforcer · Feb 3, 2014 at 8:04 AM

Should have posted the output showing that there weren't any issues with the misc partition. Here it is:

Sent from my HTC EVO 4G LTE

hondafreak513 · Feb 3, 2014 at 4:25 PM

FinZ28 said:
Finally got this recovery installed earlier. Misc partition is fine. So far, so good. Looks great and lots of options:good:

How did you install this..

Sent from my EVO using Tapatalk

[jewel][CWM Advanced Edition] PhilZ Touch

Inactive Recognized Developer

Retired Forum Moderator

Inactive Recognized Developer

Retired Forum Moderator

Inactive Recognized Developer

Retired Forum Moderator

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Recognized Developer

Recognized Developer

Senior Member

Retired Forum Moderator

Senior Member

Retired Forum Moderator

Retired Forum Moderator

Attachments

Senior Member