[manta][CWM Advanced Edition] PhilZ Touch

Search This thread

Phil3759

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

To take a screen shot, just slide left

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:
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though :p

This sounds pretty cool though.

I warn people when I release an untested recovery on a given device
Most noobs tend to forget that flashing is not a safe operation. It can always turn into a nightmare
You can check the list of currently supported devices from main thread here: http://xdaforums.com/showthread.php?t=2201860
And browse into the different device support forums

Till now, the warning never became true except when some people flashed the wrong file in their phone :eek:

This warning should keep noobs away from testing it
 

espionage724

Senior Member
Feb 8, 2010
2,937
733
wiki.realmofespionage.xyz
OnePlus 6
Well, will you be the first to give a feedback ? :D
Sure :)

I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.

Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
 
  • Like
Reactions: zourn

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Sure :)

I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.

Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).

Thank you for the feedback (reached my daily limit for :good:)

Brightness:
Do you by case know the path for your device brightness file?
Not a big deal though as I can search / look for it in rc files. I used Samsung usual path, but it seems they used a different one for google devices

Battery:
Will check for the battery path used

Touch
It is supposed to be one finger to use :eek:
Interesting though...
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Can any one run this in adb shell while in recovery
Or you can use the console terminal in aroma file manager while in recovery
Code:
 find /sys/. -name '*bright*' >/sdcard/brightness.txt

Then
Code:
 find /sys/. -name '*battery*' >/sdcard/battery.txt

And attach the resulting brightness.txt and battery.txt files on sdcard

About multi touch: i will look to allow only slot 0 to ignore second finger



Sent from my GT-I9100 using Tapatalk 2
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/ -name '*'  >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here

Please do this in recovery, not main system

Sent from my GT-I9100 using Tapatalk 2
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Ok,

Can you do this now:
Code:
 ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
 
Last edited:

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Ok,

Can you do this now:
Code:
 ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks

Sorry I'm a bit out of sync with you -- but I've attached the one you asked for just before revising your post.

find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt

Result is attached. I'll run the other command in a moment.
 
Last edited:
  • Like
Reactions: Phil3759

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Ok,

Can you do this now:
Code:
 ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks

OK -- re-learning linux command line as I go (it's been many years!). Good to wake up that part of the brain again...

Had to modify command above: needed a space between ls and -l, and I'm assuming you want "/sys" up front in the fully qualified file name... Assuming that's all good, the new result is attached as battery2.txt

Let me know if this is what you need, or if anything else is needed. I've got some time to squeeze in a few of these today as needed. Also REALLY looking forward to trying this out on my N10 (and would love to see this on the Galaxy Nexus if ever possible!).
 
Last edited:
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess

I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links

Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt

Thank you for your patience :good::good:
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess

I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links

Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt

Thank you for your patience :good::good:

Try the attached...
 
Last edited:
  • Like
Reactions: Phil3759
I must be in stupid mode today !!

Have been running Galaxy S3 with PhilZ Touch for some time now .... superb :good:

Got a new Nexus 10 last week and want it on there as well ..... stupid bit coming now :confused:

Downloaded latest version from this thread - but it shows as "philz_touch_5.00.7-manta.img"

Not a zip or a tar file for Odin ..... what am I missing from under my nose?

Homer
 

Top Liked Posts

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

    To take a screen shot, just slide left

    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:
    5
    New update v6.12.8 available.:good:

    6.12.8 (30.01.2014)
    - time and date menu text formatting and order
    - version display edit
    - add ntfs write support to devices using kernel modules instead of fuse
    - loki: merge "Support LG Optimus F7 ZV5_02"
    - zip installer: update loki binaries for LOKI devices
    - zip installer: use new update-binary sources
    - add NTFS kernel module support for more Samsung devices

    6.12.2 (28.01.2014)
    - manually set time and date in recovery
    - support Qualcom time daemon to sync time with main system (credits to dougiebee)
    - support RTC offset hack for Qualcom devices without a proper time daemon in system ROM (credits to dougiebee)
    - option to drop to system set time and date commands (credits to dougiebee)
    - set default nandroid compression level back to low
    - roll out exfat-nofuse sources from dorimanx into various kernels from Samsung and other brands
    - code fix and cleanup
    - New: Oppo N1

    6.10.6 (23.01.2014)
    - update SuperSU to 1.91
    - merge android_system_core changes to adb to fix push to extra storage paths
    - do not use performance mode during install zip: fixes hang on unmount /system in updater-script when usb cable is connected
    - i9505 ans US variants: update kernel to fix random hang on boot
    - update to CWM 6.0.4.7
    - merge "Fix up bu restore"
    - ROM Manager: workaround to backup/restore to/from external storage

    6.10.2 (20.01.2014)
    - enhance touch init (fix touch on some Sony devices)
    - really fix reading device max brightness value
    - loki: merge "Support Open EU LG Optimus F6 and US Cellular Optimus F7"
    - New: HTC One X+ (enrc2b)

    6.10.0 (18.01.2014)
    - read the device max brightness setting to fix brightness toggle on some Sony devices
    - merge: "Populate mount menu with new mount/format matrix" - final version
    - merge: "Use cat for adb backup."

    6.09.8 (16.01.2014)
    - merge: "Populate mount menu with new mount/format matrix"
    - New: Moto X variants: US Cellular (xt1055), Sprint (xt1056)
    - New: Galaxy Tab 2 P3110 (p3110)

    6.09.6 (15.01.2014)
    - do not error on missing sd-ext when wiping dalvik cache
    - merge: "su: Update for latest su daemon compatibility"
    - merge "Clean up c formatting - 1"
    - merge "Remove "Go Back" option from verify root and recovery options"
    - merge "Fix potential chmod failures"
    - merge: "Add a copy of the updater binary to the recovery resources"
    - merge: "install: Support downgrade scenarios"
    - merge: "install: Fix possible overflow condition in the updater "scanner""
    - merge: "minui: do not use flexible array initialization"
    - merge: "correctly mount tmpfs as /tmp in recovery"
    - New: Sony Xperia SP (huashan)
    - New: Sony Xperia T (mint)
    - New: Samsung i9192 (serranodsub)
    - New: Motorola Moto X variants: VZW (xt1060), GSM (xt1058), TMO (xt1053)
    - New: Samsung Galaxy Note 10.1 LTE (n8020)

    6.09.2 (12.01.2013)
    - TWRP: merge "support use TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID"
    - toggle prompt on low free space during backup
    - SuperSU update to v1.89
    - loki: merge "Support LG Vu 3."
    - code cleanup
    - New: US Cellular CH-R530U (d2usc) support


    Download
    5
    And here the flashable Zip.
    5
    New version 5.03.0

    Below is full change log
    In short:
    - potential serious bug for /data/media devices
    - Advanced Backup statistics during nandroid tar operations
    - Update to cwm 6.0.3.2
    - 3 new colors as requested
    - Add toggles to change color of header text and battery/clock display color
    - Small GUI changes (fix color highlight of virtual buttons and the bottom menu line color


    5.03.0
    - fix backup size progress in twrp mode
    - improve code for backup stats during nandroid jobs
    - display full backup stats (total size, compression ratio, elapsed time) at end of backups
    - merge last cm-10.1 updates:
    * fix nandroid cmd command did not load volume table
    * support nandroid dump/undump commands
    * nandroid backup command line still segfaults
    * silent log when mounting /data/media
    Touch:
    - add 3 new color palettes (30 colors total): dimmer gray, yellow and gold
    - add toggle for header custom color
    - add toggle for battery and clock custom color
    - line at bottom of menus will now have same color as menus separator lines
    - set new defaults to header and menu text colors
    - show backup/restore stats in color during nandroid jobs
    - fix touch issue when exiting friendly log or blanked screen, and pressing on virtual buttons

    5.02.3
    - fix root break for devices with shared recovery partition caused by Whil Wheaton update
    - advanced backup size monitoring during nandroid operations
    - prompt to cancel backup on low free space (% and absolute)
    - live display size stats during backup: total data written, free space left
    - support backup and restore of /misc partition for both CWM and TWRP operations
    - prevent potential segfault when calling is_data_media_volume_path()
    - merge cm-10.1 changes:
    * remove adb sideload /tmp/update.zip after flashing to avoid second flash under some circumstances
    - fix android_secure could not be backed up under some circumstances (ensure mount of sdcard)
    - completely rewritten android_secure support: much simpler code
    Touch:
    - optimize cancel nandroid job action
    - allow cancel yaffs2 nandroid operations
    - allow dim screen timeout during yaffs2 nandroid operations
    - fix set brightness and auto-dim screen timer for Nexus 7 and Nexus 10
    - fix battery stats display for Nexus 10
    - restore default actions of real device keys we fake for touch events
    - correctly map device virtual keys to default recovery actions
    - fix virtual buttons highlight color to match their line separator color (blue)

    5.00.8
    - support Nexus 7 and Nexus 10
    - clean code for non PhilZ Touch buils
    - Merge cm-10.1 changes to cwm 6.0.3.2:
    * recovery: fix sideload cancel" into cm-10.1
    * make_ext4fs support
    * auto prompt to root device when booting to main system

    5.00.5
    - use device specific background images during compile process


    Download links
    Last version can be found here:
    5
    This variant of CWM really fcked up my NEXUS 10. I downloaded the latest 5.15.0 "philz touch" according to the OP now my device won't boot into recovery or bootloader. AND I HAVE NO OS INSTALLED. The ORIGINAL CWM should be more easy to find, rather than these sketchy "better editions". Wtf do I do now ORIGINAL POSTER.?

    I understand the frustration -- but you get a lot more help in a forum like this if you can avoid trashing other people's work, and blaming them for something you chose to do of your own free will. If you took a close look at all the threads where Phil3759 participates, the people that make use of his recovery are generally thrilled with it, and recognize it as a solid, feature rich tool with a lot of attention paid to performance, compatibility and user interface. Take a look at his profile -- you won't see many posters here with over 19,000 "thanks". That's a pretty solid testimony to the value he brings to the forum.

    Every single piece of custom code on this forum comes along with warnings, and a reasonable expectation that people will read them. If you're not prepared to undo whatever a utility like this does, you should think twice about flashing it. If you need help, instead of denigrating a fine piece of code that's been made available, free of charge, to us, and blaming the developer, you might try explaining what you did, clearly and in detail, and asking for help -- nicely, and with the respect that the developer deserves.

    BTW: Philz Touch has worked splendidly on my GNex (toro) and Nexus 10. Never an issue. It is, in short, the best recovery I've used over the past few years. The only reason I've temporarily replaced it with CWM Touch is to be able to flash 4.4 ROMs. If and when Phil has time to incorporate the latest core CWM code (from 6.0.4.3 or later), then I'll switch back to Philz Touch in a heartbeat.

    In the meantime -- you should read up on Fastboot, and tools like the Wugfresh Nexus Root Toolkit. If you can learn Fastboot and ADB directly, that's best, as you'll know exactly what's going on and have total control of the commands being issued to your device. Wug's toolkit is excellent, and if you search a bit, you'll find one or two others with similar functionality. In short - using Fastboot, you'll be able to replace the recovery on your N10, and start fresh.