[manta][CWM Advanced Edition] PhilZ Touch

Search This thread

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Thank you
I am collecting info to try to fix it for unsupported phones

Sent from my GT-I9100 using Tapatalk 2
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Oh, if you can attach a log after a failed capture it would be great
Advanced / report error
Then attach philz_recovery.log here

Sent from my GT-I9100 using Tapatalk 2

Just tried:
- swiped left
- say error message
- went into Advanced and selected "report error" -- saw message at bottom of screen indicating file location / name
- rebooted into Android, and cannot find the file in /sdcard/clockworkmod.

I also made sure I have "show hidden files " turned on in my file explorer... I can see a number of hidden files now, but not Philz log...

EDIT: tried another path to be certain: storage\sdcard0\clockworkmod -- same view, nothing there...

EDIT: searched entire N10 for the log -- not found (using FileExplorer / FX)

EDIT: search entire device for "*.log" created within the hour -- no results.
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
For the log, look into /data/media/clockworkmod folder instead of /data/media/0/clockworkmod

Or, set sdcard path to /data/media/0 in Advanced menu and default folder will show on sdcard while in main ROM
That's Android 4.2

Sent from my GT-I9100 using Tapatalk 2
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
For the log, look into /data/media/clockworkmod folder instead of /data/media/0/clockworkmod

Or, set sdcard path to /data/media/0 in Advanced menu and default folder will show on sdcard while in main ROM
That's Android 4.2

Got it...attached...

EDIT...that's weird... I'll try uploading again... OK...XDA doesn't like "log" as extension. Zipping it...
 
Last edited:
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Great. Seems nexus 10 doesn't use default frame buffer path

Sent from my GT-I9100 using Tapatalk 2
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Let me know if you need me to explore / trace down paths...

Would be great, yes
By default, it tries to read from /dev/graphics/fb0
But seems not the good path or unable to read whole data from it
I can dig into sources, but if you can make sure frame buffer is the one i wrote above...

Sent from my GT-I9100 using Tapatalk 2
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Would be great, yes
By default, it tries to read from /dev/graphics/fb0
But seems not the good path or unable to read whole data from it
I can dig into sources, but if you can make sure frame buffer is the one i wrote above...

OK... I see /dev/graphics/fb0

It's readable, writeable and not hidden...Last modified at 10:06 this morning. Root owns it. What else can I tell you about it?
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
OK... I see /dev/graphics/fb0

It's readable, writeable and not hidden...Last modified at 10:06 this morning. Root owns it. What else can I tell you about it?

Ok, maybe just a read issue in code
Will look at it, but without a device it will be a real pain

Sent from my GT-I9100 using Tapatalk 2
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
Ok, maybe just a read issue in code
Will look at it, but without a device it will be a real pain

Does this apply?

http://stackoverflow.com/questions/7356503/why-cannot-i-read-data-from-dev-graphics-fb0

Since the fb0 is a buffer file, it is an always-changing file, you should copy it to a certain ACCESSIBLE destination then read it with FileInputStream, easily having the correct data.

Like:

("cat /dev/graphics/fb0 > /dev/myRawFrame.raw");

File CurrentRawFile = new File("/dev/myRawFrame.raw");
and you're done :)
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Issue is not there
You can look at the fb2png.c file in my github. It is small (only 2 functions) and the error is there in one of the 2 functions, probably get_device_fb(...)

Sent from my GT-I9100 using Tapatalk 2
 

vizzy

Senior Member
Jan 5, 2012
2,173
398
I made a backup. But when I tried searching for it using es explorer I couldn't find it ?..... The largest file I had was 10mb pdf file .....

Sent from my HTC One using Tapatalk 2
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Read about /data/media/0

Sent from my GT-I9100 using Tapatalk 2
 

vizzy

Senior Member
Jan 5, 2012
2,173
398
Read about /data/media/0

Sent from my GT-I9100 using Tapatalk 2

Yeah nothings there. I'll try another back up and see how it goes.

When i go into CWM and click restore, it says I have a backup in the following folder:

/sdcard/clockworkmod/backup/

except, when go into my sd card using a file explorer I go into the clockworkmod folder and it says empty? The furthest i can go is:

/sdcard/clockworkmod/
 
Last edited:

hanspampel

Senior Member
Dec 7, 2011
2,140
3,128
Hmm same by me. I had made 3 backups with PhilZ, but cant restore one of them. They all in /data/media/clockworkmod/backup. But nothing will show up in CWM.
 

jonstrong

Senior Member
Jan 20, 2012
1,790
719
www.jonathanrstrong.com
You have to use a root explorer, and make sure you can see hidden files. I just set up ES File Explorer to do that, and lo and behold, I can now navigate to /data/media/clockworkmod/backup -- and see two folders labeled with the timestamps of the two backups I made with CWM recovery.
 
  • Like
Reactions: vizzy

vizzy

Senior Member
Jan 5, 2012
2,173
398
You have to use a root explorer, and make sure you can see hidden files. I just set up ES File Explorer to do that, and lo and behold, I can now navigate to /data/media/clockworkmod/backup -- and see two folders labeled with the timestamps of the two backups I made with CWM recovery.

How do you do that ?

I hate this updated es explorer

Sent from my HTC One using Tapatalk 2

Ahh so it does, well played my friend !
 
Last edited:

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.