[honami][CWM Advanced Edition] PhilZ Touch

Search This thread

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Uploaded on goo.im:
philz_touch_6.12.8-honami-FIXED-fw-C6902_14.2.A.1.136.img
 

Black_halo

Senior Member
Jan 26, 2013
146
13
Chicago
Hey guys. New to honami with the c6906 on AT&T but I just want to clarify some things because I've been familiar with Motorola with philz touch so long and switching to Sony seems so new but any way we're suppose to:

1. Download & flash CWM

2. Flash philz touch over CWM recovery

3. Unlock bootloader

4. Then install custom rom of choosing?

I've read through the forums and I saw things about .img and .dt files so are there any extra steps? I don't want to be on stock and I don't want to brick either. Sorry if I sound like a noob but these are the only steps I took with flashing on Motorola and just seeking clarity.
 

juicio90

Senior Member
Dec 8, 2013
146
11
Can't take a backup, with the lasted version. I have CM 11, and everything work fine, just can't make a backup to SD ext...

Sent from my Xperia Z1 using XDA Premium 4 mobile app
 

[NUT]

Senior Member
@Phil3759

I'm afraid something broke in PhilZ Touch 6.26.1 at least:

recovery.log snippet:
Code:
I:show_background_icon set to default (false)
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
I:show_battery set to default (true)
[SNIP]
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
[SNIP]
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
display_frame failed, no overlay
: Out of memory
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented

This is true for the Z1, Z1 Compact and Z Ultra...

Have any idea what might be wrong?

Touch events seem to get registered and using the buttons actually performs actions. It's just not putting anything on screen.

@shoey63 for reference
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
@Phil3759

I'm afraid something broke in PhilZ Touch 6.26.1 at least:

recovery.log snippet:
Code:
I:show_background_icon set to default (false)
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
I:show_battery set to default (true)
[SNIP]
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
overlay_display_frame failed, overlay commit Failed
!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
[SNIP]
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
Overlay Set Failed: Out of memory
display_frame failed, no overlay
: Out of memory
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented
ERROR: Clear MSMFB_DISPLAY_COMMIT failed!: Function not implemented

This is true for the Z1, Z1 Compact and Z Ultra...

Have any idea what might be wrong?

Touch events seem to get registered and using the buttons actually performs actions. It's just not putting anything on screen.

@shoey63 for reference

Disabe the qcom msm flag or such
No pc to verify exact name
Probably not implemented in stock kernel or custom graphics.c you use
 
  • Like
Reactions: [NUT]

[NUT]

Senior Member
Disabe the qcom msm flag or such
No pc to verify exact name
Probably not implemented in stock kernel or custom graphics.c you use

Okay, will try to find it.

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

@Phil3759

Code:
# inherit from Sony common
include device/sony/common/BoardConfigCommon.mk

BOARD_EGL_CFG := device/sony/rhine-common/rootdir/system/lib/egl/egl.cfg

# inherit from qcom-common
include device/sony/qcom-common/BoardConfigCommon.mk

TARGET_SPECIFIC_HEADER_PATH := device/sony/rhine-common/include

# Kernel properties
TARGET_KERNEL_SOURCE := kernel/sony/msm8974

# Platform
TARGET_BOOTLOADER_BOARD_NAME := MSM8974
TARGET_BOARD_PLATFORM := msm8974
BOARD_VENDOR_PLATFORM := rhine

[SNIP]

# Qualcomm
BOARD_USES_QCOM_HARDWARE := true
BOARD_USES_QC_TIME_SERVICES := true
TARGET_USES_QCOM_BSP := true
TARGET_ENABLE_QC_AV_ENHANCEMENTS := true
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_QCOM_DISPLAY_VARIANT := caf-new
TARGET_QCOM_MEDIA_VARIANT := caf-new

Which one are you refering to?
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Okay, will try to find it.

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

@Phil3759

Code:
# inherit from Sony common
include device/sony/common/BoardConfigCommon.mk

BOARD_EGL_CFG := device/sony/rhine-common/rootdir/system/lib/egl/egl.cfg

# inherit from qcom-common
include device/sony/qcom-common/BoardConfigCommon.mk

TARGET_SPECIFIC_HEADER_PATH := device/sony/rhine-common/include

# Kernel properties
TARGET_KERNEL_SOURCE := kernel/sony/msm8974

# Platform
TARGET_BOOTLOADER_BOARD_NAME := MSM8974
TARGET_BOARD_PLATFORM := msm8974
BOARD_VENDOR_PLATFORM := rhine

[SNIP]

# Qualcomm
BOARD_USES_QCOM_HARDWARE := true
BOARD_USES_QC_TIME_SERVICES := true
TARGET_USES_QCOM_BSP := true
TARGET_ENABLE_QC_AV_ENHANCEMENTS := true
TARGET_QCOM_AUDIO_VARIANT := caf
TARGET_QCOM_DISPLAY_VARIANT := caf-new
TARGET_QCOM_MEDIA_VARIANT := caf-new

Which one are you refering to?

TARGET_USES_QCOM_BSP

remove / comment that line
 
  • Like
Reactions: [NUT]

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Will try to build it later tonight, thanks, will update you on the subject after some testing.

do not forget to make clobber after that or at least remove all minui intermediates
Not sure if more cleaning is needed before building again. Start with minui, then maybe a clobber if it fails
 
  • Like
Reactions: [NUT]

juicio90

Senior Member
Dec 8, 2013
146
11
it is related to cm updater and /data/media path they use
There is a toggle for cm users

Sorry, but I'm nooby ... Where is it?

Edit: I found it... Man.. I really appreciated your work :thumbup:. Thanks for you help. Now it is working !!! :D Sorry for my bad English. Thank you very much!
Sent from my Xperia Z1 using XDA Premium 4 mobile app
 
Last edited:
  • Like
Reactions: Phil3759

acabreram

Senior Member
Mar 28, 2013
275
44
Samsung Galaxy S9
it is related to cm updater and /data/media path they use
There is a toggle for cm users

Hi could you dev this for Xperia Z1 Compact please!! I know that there is a locked dual recovery and is a excelente work but i never use TWRP
and cwm has some bugs for example when you make a back up don´t show progress and you don´t know if is stuck or what.

Please Dev this for stock Kerner and custom.

Thanks!!
 

Top Liked Posts

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

    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:


    Big credits to @DooMLoRD for his help to rebase on stock kernel

    XDA:DevDB Information
    [honami][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia Z1

    Contributors
    Phil3759, DooMLoRD, [NUT]

    Version Information
    Status: Testing

    Created 2014-03-29
    Last Updated 2014-03-29
    7
    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

    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:

    hi @Phil3759,

    firstly welcome to the Z1 forums!

    the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:
    http://xdaforums.com/showthread.php?t=2447310


    I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..

    download link for fixed image is:
    http://d-h.st/Iz2


    BTW me and my colleague @Napstar have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):

    our sources have also been released quite some time back:
    http://xdaforums.com/showthread.php?t=1485829

    but i discontinued work on it as i got busy with personal work


    I would recommend getting in touch with @Napstar, may be we can collaborate for some bigger things :)


    also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel? (I have made my DooMKernel for close to 21 devices from various vendors Sony, HTC, Samsung, Huawei, Kindle, etc; currently I actively support only 4 devices though: Xperia Z1, Z, SP & T)



    note to users:

    if you want to test out this recovery then you need to HOTBOOT this kernel:
    Code:
    fastboot boot kernel.img



    regards,

    DooMLoRD
    4
    @Phil3759 and @shoey63

    I've cracked it, I found the way to set the stock kernel to SELinux=permissive on the Sony kernel by controlling the sysfs entry.

    Sony has no SELinux configuration AT ALL, file contexts are unset. But from the moment the kernel boots, SELinux is set to enforcing while sony themselves set it to permissive at some point.

    The entry point for the locked bootloader recovery is too early so I need to write a 0 in to /sys/fs/selinux/enforce during the on init in the init.rc and Philz will be able to use minivold to mount the sdcard1 regardless of the used filesystem :victory:

    Good catch :good:
    Sony sucks and you rock LoL
    4
    I really appreciate sony community with many devs/advanced users working on the support
    :good:
    4
    @Phil3759 and @shoey63

    I've cracked it, I found the way to set the stock kernel to SELinux=permissive on the Sony kernel by controlling the sysfs entry.

    Sony has no SELinux configuration AT ALL, file contexts are unset. But from the moment the kernel boots, SELinux is set to enforcing while sony themselves set it to permissive at some point.

    The entry point for the locked bootloader recovery is too early so I need to write a 0 in to /sys/fs/selinux/enforce during the on init in the init.rc and Philz will be able to use minivold to mount the sdcard1 regardless of the used filesystem :victory: