[TabZ][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A

Search This thread

[NUT]

Senior Member
-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***


Welcome to the Xperia Tablet Z Questions & Answers thread!

I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones! :cool:

If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.

Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651

To follow development, be sure to check the DevDB thread!
 
Last edited:

[NUT]

Senior Member
INSTALLER: How to install using the installer:
  1. Make sure you have USB debugging turned ON.
  2. download TabZ-lockeddualrecovery[VERSION]-RELEASE.installer.zip from http://nut.xperia-files.com
  3. Windows:
    1. unpack at C: or somewhere you will remember!
    2. navigate to the resulting directory and look for install.bat, double click it to run;
  4. Linux:
    1. unpack in your home folder with 'unzip TabZ-lockeddualrecovery[VERSION]-RELEASE.installer.zip'
    2. navigate to the resulting directory and 'chmod +x install.sh', then execute it, follow instructions.
  5. Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
  6. Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
  7. Enjoy DUAL RECOVERY!

How to install or update using a previously installed (XZDualRecovery) recovery:
Create a backup of /system/bin/chargemon and keep it somewhere safe, then just flash TabZ-lockeddualrecovery[VERSION]-RELEASE.flashable.zip from http://nut.xperia-files.com using CWM or TWRP.

How to remove:

Delete the following files:
/system/bin/recovery.twrp.cpio.lzma (or .tar)
/system/bin/recovery.cwm.cpio.lzma (or .tar)
/system/bin/recovery.philz.cpio.lzma
/system/bin/charger
/system/bin/dualrecovery.sh
/system/bin/mr

Rename /system/bin/mr.stock to /system/bin/mr to restore stock functionality, then inside /system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). Done!


When installing custom ROMs:
Be sure to flash TabZ-lockeddualrecovery[VERSION]-RELEASE.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!

How to use:
At boot, once you feel the phone vibrate and while you see the green led burn:
- press VOL-UP for PhilZ Touch;
- press VOL-DOWN for TWRP.

To enter Vanilla CWM, you will need to use the (free) NDRUtils app from the Play store

2.x Features:
  • When you have a SDCard1 and the XZDualRecovery is able to use it, you can put a file called 'donotrun' inside the XZDualRecovery log folder to make XZDualRecovery escape following boot attempts.
    If you find yourself in a bootloop situation, take out your SDCard1 and put that file in the directory if it exists using a PC. Reboot your phone with Power+Vol-UP and you will be able to boot your phone as if there was no recovery there!
  • XZDualRecovery will signal the escape or any reason why it would not be able to continue normal operation with a 2 second burn of your LED in the color RED. A reason would be a broken /cache and no SDCard1 or a busybox in /system/xbin which does not support the lzcat command. If you see that, check /tmp/XZDualRecovery for a logfile there, it will tell you why.
  • XZDualRecovery will try to use your SDCard1 for logging and functionality, if it has been formatted with ext2/4, FAT16/32 or exFAT. NTFS is currently unsupported.
  • XZDualRecovery now prevents the RIC service from starting up, this means when running XZDualRecovery the Remount-Reboot fix is no longer needed.

Defaults:
  • The default on first boot with the boot-to-recovery flag set by any recovery is PhilZ Touch Recovery.
  • Init.d support is disabled by default, set dr.enable.initd to true to enable it.
  • Insecure ramdisk support is disabled by default, set dr.insecure.ramdisk to true to enable it, set to 'power' to boot it by pressing the power button at boot.

Error reporting:
Please, when reporting errors or problems:
  • Put up a notice in this thread providing the package name you used to install or update;
  • Include ROM name and/or FW version numbers;
  • Include what SU apk you are using (SuperUser or SuperSU)
  • Send me the contents of all the log files from right after a failed boot attempt or a link to an archive containing these logs by PM (that's including the .old rotation logs!). If you have no website or online location to store the logs, PM me for an email address to send them to.
  • Logs can be found inside:
    • /cache/recovery
    • /tmp/XZDualRecovery
    • /storage/sdcard1/XZDualRecovery
    • /cache/XZDualRecovery (if the previous exists, this one will not!)
    NOTE: I need them ALL!
I really need them to troubleshoot what failed and what worked OK. Thank you!

-------

Special Thanks:
  • @DooMLoRD for all his excellent work on our much loved Sony phones!
  • The Team Win developers for TWRP
  • The ClockWorkMod developers for CWM
  • @alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
  • @RoberM for testing
  • @surdu_petru for testing and handy pointers
  • @Androxyde for allowing to use his linux and mac adb binaries.
  • @lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
  • @delewer for the final fix for TWRP and its use of exFAT formatted sdcards
  • @DevShaft for some code help on the windows installer (the menu!)
  • @Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
  • @Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
  • @gregbradley for his extensive testing on the Xperia Z1

Well, enjoy! :fingers-crossed:

The origins of this XZDualRecovery package are in the packages done by:
Krabappel2548, Cpasjuste and DooMLoRD
Thank you for your excellent work guys! :victory:
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
 
Last edited:

spoonymoon

Senior Member
Aug 31, 2011
1,414
579
Det mørke Jylland
As long as the ROM chef says it needs to be flashed using CWM or TWRP, yes :)

That would be any STOCK based ROM for your model.

Sent from my C6603 using xda app-developers app

Hei and thanx alot :p

So with this cwm installed on my 311 rooted z, i'll be able to flash aokp or cm10.1 roms from cwm? And Even be able to have dualboot?

Woow this is excatly what i miss!!

But but I Will be First to flash on 311 and not sure on what happens IF it ends in bootloop or not booting at all?

And how do i(we) revert things Again?

Plz advise ;)
 

[NUT]

Senior Member
Hei and thanx alot :p

So with this cwm installed on my 311 rooted z, i'll be able to flash aokp or cm10.1 roms from cwm? And Even be able to have dualboot?

Woow this is excatly what i miss!!

But but I Will be First to flash on 311 and not sure on what happens IF it ends in bootloop or not booting at all?

And how do i(we) revert things Again?

Plz advise ;)

You can only flash ROM's that do NOT require a custom kernel on a locked bootloader.

The XZDualRecovery does NOT offer dualboot, only dual recovery, it means you can use either TWRP or CWM to flash, backup and restore your tablet.

If you ever try to flash a new ROM, you create a backup using either recovery first. In case of a bootloop you can then restore your tablet using either a FTF combined with FLASHTOOL or use SUS to restore it to working order. Then you can root it again and install XZDualRecovery to be able to restore your backup.

Just as a friendly pointer: it's wise to have an external sdcard when flashing ROM's as in case of emergency, the SUS (for sure) or FLASHTOOL (if your not carefull) restores both wipe your internal storage, and if you stored your backups there, they will be gone.

Be sure to keep a backup of your internal storage contents on your pc/Mac... Just as a precaution.

All the above is to be read with the following in mind: BETTER SAFE THEN SORRY!

Sent from my C6603 using xda app-developers app
 
  • Like
Reactions: spoonymoon

nyknight77

Senior Member
Sep 20, 2011
146
21
If I get a bootloop, how come I can't just go into cwm recovery and restore a nandroid backup? Why having to do ftf and flashtool, reroot, reinstall recovery, then restore backup?


Sent from my SGP312 using Tapatalk 2
 

[NUT]

Senior Member
If I get a bootloop, how come I can't just go into cwm recovery and restore a nandroid backup? Why having to do ftf and flashtool, reroot, reinstall recovery, then restore backup?


Sent from my SGP312 using Tapatalk 2

You might be able to boot to recovery in case of a bootloop, but if that's not possible that might be your only solution. It all depends on where during boot the loop occurs.

Sent from my C6603 using xda app-developers app
 

takumibox

Senior Member
Sep 14, 2010
53
1
As long as the ROM chef says it needs to be flashed using CWM or TWRP, yes :)

That would be any STOCK based ROM for your model.

Sent from my C6603 using xda app-developers app


the resolution of TWRP is not correct, can be used at Xperia tablet z
 

Attachments

  • IMG_20130624_140523.jpg
    IMG_20130624_140523.jpg
    247.7 KB · Views: 346
Last edited:

Itcouldbeyou

Member
May 14, 2010
23
3
This doesn't and will never work for installing CM, AOSP and similar ROMS right? Maybe you should include a big disclaimer in your first post about this.
Still nice work!
 

[NUT]

Senior Member
This doesn't and will never work for installing CM, AOSP and similar ROMS right? Maybe you should include a big disclaimer in your first post about this.
Still nice work!

Never is a big word :p

If you unlock your bootloader using FLASHTOOL after creating a backup of the TA partition it might just be helpful enough to flash whatever you want :) TWRP and CWM are able to flash a kernel, just not a custom one on a locked bootloader.

Doing so will result in a soft-bricked device with the risk of having to wipe everything on your device.

But no, a CM, AOSP or AOKP ROM implies a custom kernel, that will never work on a locked bootloader, but that should already be communicated by the respective ROM builders, but from my perspective at least: that is something outside the scope of this thread...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    -=[XZDualRecovery]=-
    PhilZ Touch & CWM & TWRP
    *** For Locked and Unlocked BOOTLOADERS! ***


    Welcome to the Xperia Tablet Z Questions & Answers thread!

    I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones! :cool:

    If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.

    Currently supported XPERIA models:
    These are also links to the device specific Q&A threads.
    Xperia Z: SO-02E, C6602, C6603, C6606, C6616
    Xperia ZL: C6502, C6503, C6506
    Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
    Xperia Z Ultra: C6802, C6806, C6833, C6843
    Xperia Z1: C6902, C6903, C6906, C6943, C6916
    Xperia Z1 Compact: D5502, D5503, D5506
    Xperia Z2: D6502, D6503, D6506, D6543, D6563
    Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
    Xperia ZR: C5602, C5603, C5606
    Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
    Xperia S: LT26i
    Xperia SP: C5302, C5303
    Xperia T2 Ultra: D5303, D5322
    Xperia Z3: D6603, D6633, D6643, D6653, D6616
    Xperia Z3 Compact: D5803, D5833
    Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651

    To follow development, be sure to check the DevDB thread!
    12
    INSTALLER: How to install using the installer:
    1. Make sure you have USB debugging turned ON.
    2. download TabZ-lockeddualrecovery[VERSION]-RELEASE.installer.zip from http://nut.xperia-files.com
    3. Windows:
      1. unpack at C: or somewhere you will remember!
      2. navigate to the resulting directory and look for install.bat, double click it to run;
    4. Linux:
      1. unpack in your home folder with 'unzip TabZ-lockeddualrecovery[VERSION]-RELEASE.installer.zip'
      2. navigate to the resulting directory and 'chmod +x install.sh', then execute it, follow instructions.
    5. Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
    6. Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
    7. Enjoy DUAL RECOVERY!

    How to install or update using a previously installed (XZDualRecovery) recovery:
    Create a backup of /system/bin/chargemon and keep it somewhere safe, then just flash TabZ-lockeddualrecovery[VERSION]-RELEASE.flashable.zip from http://nut.xperia-files.com using CWM or TWRP.

    How to remove:

    Delete the following files:
    /system/bin/recovery.twrp.cpio.lzma (or .tar)
    /system/bin/recovery.cwm.cpio.lzma (or .tar)
    /system/bin/recovery.philz.cpio.lzma
    /system/bin/charger
    /system/bin/dualrecovery.sh
    /system/bin/mr

    Rename /system/bin/mr.stock to /system/bin/mr to restore stock functionality, then inside /system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). Done!


    When installing custom ROMs:
    Be sure to flash TabZ-lockeddualrecovery[VERSION]-RELEASE.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!

    How to use:
    At boot, once you feel the phone vibrate and while you see the green led burn:
    - press VOL-UP for PhilZ Touch;
    - press VOL-DOWN for TWRP.

    To enter Vanilla CWM, you will need to use the (free) NDRUtils app from the Play store

    2.x Features:
    • When you have a SDCard1 and the XZDualRecovery is able to use it, you can put a file called 'donotrun' inside the XZDualRecovery log folder to make XZDualRecovery escape following boot attempts.
      If you find yourself in a bootloop situation, take out your SDCard1 and put that file in the directory if it exists using a PC. Reboot your phone with Power+Vol-UP and you will be able to boot your phone as if there was no recovery there!
    • XZDualRecovery will signal the escape or any reason why it would not be able to continue normal operation with a 2 second burn of your LED in the color RED. A reason would be a broken /cache and no SDCard1 or a busybox in /system/xbin which does not support the lzcat command. If you see that, check /tmp/XZDualRecovery for a logfile there, it will tell you why.
    • XZDualRecovery will try to use your SDCard1 for logging and functionality, if it has been formatted with ext2/4, FAT16/32 or exFAT. NTFS is currently unsupported.
    • XZDualRecovery now prevents the RIC service from starting up, this means when running XZDualRecovery the Remount-Reboot fix is no longer needed.

    Defaults:
    • The default on first boot with the boot-to-recovery flag set by any recovery is PhilZ Touch Recovery.
    • Init.d support is disabled by default, set dr.enable.initd to true to enable it.
    • Insecure ramdisk support is disabled by default, set dr.insecure.ramdisk to true to enable it, set to 'power' to boot it by pressing the power button at boot.

    Error reporting:
    Please, when reporting errors or problems:
    • Put up a notice in this thread providing the package name you used to install or update;
    • Include ROM name and/or FW version numbers;
    • Include what SU apk you are using (SuperUser or SuperSU)
    • Send me the contents of all the log files from right after a failed boot attempt or a link to an archive containing these logs by PM (that's including the .old rotation logs!). If you have no website or online location to store the logs, PM me for an email address to send them to.
    • Logs can be found inside:
      • /cache/recovery
      • /tmp/XZDualRecovery
      • /storage/sdcard1/XZDualRecovery
      • /cache/XZDualRecovery (if the previous exists, this one will not!)
      NOTE: I need them ALL!
    I really need them to troubleshoot what failed and what worked OK. Thank you!

    -------

    Special Thanks:
    • @DooMLoRD for all his excellent work on our much loved Sony phones!
    • The Team Win developers for TWRP
    • The ClockWorkMod developers for CWM
    • @alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
    • @RoberM for testing
    • @surdu_petru for testing and handy pointers
    • @Androxyde for allowing to use his linux and mac adb binaries.
    • @lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
    • @delewer for the final fix for TWRP and its use of exFAT formatted sdcards
    • @DevShaft for some code help on the windows installer (the menu!)
    • @Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
    • @Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
    • @gregbradley for his extensive testing on the Xperia Z1

    Well, enjoy! :fingers-crossed:

    The origins of this XZDualRecovery package are in the packages done by:
    Krabappel2548, Cpasjuste and DooMLoRD
    Thank you for your excellent work guys! :victory:
    Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
    4
    Yes ,. It aligns correctly now ,. :good: :D

    Will you include it in the next beta or we have to do it manually ?

    I'll include a correctly working version in the next beta package line, as soon as 2.7 is released as 'RELEASE' package.

    I will start a seperate package line for all supported models as 2.8 beta, which should eventually have a true tablet Z version of PhilZ Touch Recovery as well.

    As soon as they (all supported models) have been released and reach the 'RELEASE' status, BETA 2.9 will become a single installation package again but it will contain all variations and assemble the correct recovery ramdisks during installation.

    Big plans, but having a single unified installer and the ramdisk assembly are needed to keep the overall package size low and keeps overall maintenance and the future release plans simple ;)
    3
    Is there also support for the SGP311 and SGP312?

    Probably yes, but i can not say yes for 100%. Just install 2.5 BETA and see, it will most probably work.
    3
    Confirmed. It worked on my SGP311. I did a CWM backup without a glitch. Still have to try to restore.

    Enviado desde mi SGP311 usando Tapatalk 2