[Z Ultra][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A - Sony Xperia Z Ultra

-=[XZDualRecovery]=-
PhilZ Touch & CWM & TWRP
*** For Locked and Unlocked BOOTLOADERS! ***
Welcome to the Xperia Z Ultra Questions & Answers thread!
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
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!​

---

INSTALLER: How to install using the installer:
Make sure you have USB debugging turned ON.
download ZU-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
unpack at C: or somewhere you will remember!
navigate to the resulting directory and look for install.bat, double click it to run;
Linux:
unpack in your home folder with 'unzip ZU-lockeddualrecovery[VERSION]-BETA.installer.zip'
navigate to the resulting directory and 'chmod +x install.sh', then execute it, follow instructions.
Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
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 ZU-lockeddualrecovery[VERSION]-BETA.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 ZU-lockeddualrecovery[VERSION]-BETA.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.initd.active 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:
[Locked Bootloader]CWM recovery 6.0.2.8 for locked bootloaders v4[25-03] by Krabappel2548
[APP/RECOVERY] TWRP 2.4.3.0 for lockled bootloaders installer by Cpasjuste
[KERNEL][Z] DooMKernel {JB}(v06)[20130414] by DooMLoRD
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:

---

Awesome, and thank you! I can't see a reason why i should flash this if i already have recovery/TWRP installed? Or? Would you recommend me to install this one, or isn't it that big of a deal?

---

LordManhattan said:
Awesome, and thank you! I can't see a reason why i should flash this if i already have recovery/TWRP installed? Or? Would you recommend me to install this one, or isn't it that big of a deal?
Click to expand...
Click to collapse
No, it's a personal preference really
XZDualRecovery has been created with choice in mind. It's feature rich and more are coming but if you can do without the features...

---

Hi guys, can someone tell me what i am doin wrong??
1. Hes not asking about choice from menu.
and also
2. hes going forward saying theres no choice64 and cannot push any files...
http://feb.imghost.us/FUDj.png
//okay, i am stupid i suppose to navigate there through cmd, not explorer. Sorry for bothering.

---

downloaded ZU-lockeddualrecovery2.7.92-BETA.installer
(model 6802; Clean non-root .136)
what is this:
ro.build.product=C6802
ro.build.id=14.2.A.1.136
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
Any help ?

---

avetny said:
downloaded ZU-lockeddualrecovery2.7.92-BETA.installer
(model 6802; Clean non-root .136)
what is this:
ro.build.product=C6802
ro.build.id=14.2.A.1.136
setsockopt() failed: Bad address.
this device is not supported.
kallsyms_addresses search failed.
Any help ?
Click to expand...
Click to collapse
Check the 3rd post on the development topic... It clearly states not all rom versions can be rooted like this.
You need the 534 JB4.2 release for this to work.

---

I didn't check cuz I thought it for developers
Thanks for help

---

Dual recovery was working fine, now it stopped and I'm getting the red LED burn.
I was reading the OP again and it mentioned Busybox. If I installed a busy box pro apk I had, could that have broken the dual recovery? Should I just reinstall?
I didn't flash anything or reinstall ROMs prior to it breaking.

---

Poi25 said:
Dual recovery was working fine, now it stopped and I'm getting the red LED burn.
I was reading the OP again and it mentioned Busybox. If I installed a busy box pro apk I had, could that have broken the dual recovery? Should I just reinstall?
I didn't flash anything or reinstall ROMs prior to it breaking.
Click to expand...
Click to collapse
That depends on the version of XZDR you installed really... If you had the latest it should fix busybox by itself.
Check the logs inside the XZDualRecovery folder, it will probably tell you what's wrong.

---

[NUT] said:
That depends on the version of XZDR you installed really... If you had the latest it should fix busybox by itself.
Check the logs inside the XZDualRecovery folder, it will probably tell you what's wrong.
Click to expand...
Click to collapse
I had .95 beta. Busybox messed it up, uninstalling busybox did nothing. I just restored the phone and fixed it real quick, no big deal.

---

Hi all,
If I am already on TWRP, can I simply flash the zip file then reboot recovery? Just curious
thanks!

---

kipue said:
Hi all,
If I am already on TWRP, can I simply flash the zip file then reboot recovery? Just curious
thanks!
Click to expand...
Click to collapse
As long as you are using a stock based rom, yes.

---

[NUT] said:
As long as you are using a stock based rom, yes.
Click to expand...
Click to collapse
Can I use it for a KitKat ZU?
Sent from my C6802 using Tapatalk

---

quachhanthanh said:
Can I use it for a KitKat ZU?
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
As long as it is already rooted, yes. Otherwise you will have to downgrade to the last rootable version (.532) to root and upgrade to KK.

---

[NUT] said:
As long as it is already rooted, yes. Otherwise you will have to downgrade to the last rootable version (.532) to root and upgrade to KK.
Click to expand...
Click to collapse
I am on rooted (.136) with ur dual recovery. So I can download a KitKat zip flashable and install it through recovery?
Sent from my C6802 using Tapatalk

---

Never Mind..

---

I'm running Monx and I've been using TWRP for a while, but I want to try PhilZ, and I can't get this thing to work. Is being on Monx messing me up? When I install this and tell it to boot PhilZ, the phone just turns off. Then if I hold Vol-Up and Power, the phone stays off. I can still boot TWRP just fine, but it seems like everything else is getting blocked off. Any advice?

---

installation says device is not supported for me
i have c6833 running 4.4.2