[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE

Search This thread

gegu2

Member
Dec 25, 2014
27
13
It seems that installation script couldn't find files which should be transfered to your mobile. Make sure that you have unpacked whole xzdr installation package and you are trying to run installation script from unpacked installation package folder (which contains installation script and the rest of xzdr files).

Sent from my D5803 using XDA Free mobile app
 
  • Like
Reactions: [NUT]

WhySoSeriousJoKer

Senior Member
Oct 22, 2013
923
287
Leeuwarden
ZTE Axon 30
It seems that installation script couldn't find files which should be transfered to your mobile. Make sure that you have unpacked whole xzdr installation package and you are trying to run installation script from unpacked installation package folder (which contains installation script and the rest of xzdr files).

Sent from my D5803 using XDA Free mobile app

Launch the install.bat file without administrator was the trick and it works great now :)
 
  • Like
Reactions: zoky79 and [NUT]
Jun 28, 2015
49
9
Nice :)

It's too bad my installer patch fixed that failed message for linux, but it clearly didn't for MacOS ... but thank you for confirming it still works :)
I tried this on another Xperia phone. It just showed nothing but it was just searching for my phone when I got the phone connected to the laptop. Any fix?

Sent from my C5502 using Tapatalk
 

[NUT]

Senior Member
I tried this on another Xperia phone. It just showed nothing but it was just searching for my phone when I got the phone connected to the laptop. Any fix?

Sent from my C5502 using Tapatalk

Well, you leave out some crucial info on that request for help:

What type of Xperia? Is it rooted? are the developer options enabled and did you set USB Debugging ON?
 

chris.82

Senior Member
May 20, 2013
131
25
I've a Xperia Z1 rooted with Kingroot... Can I have the Dual recovery with this root system? Which option (1,2,3 or 4) should i choose into the "installer" with Windows?
Thank you very very much

Inviato dal mio C6903 utilizzando Tapatalk
 

gitzz

Senior Member
Nov 10, 2013
529
155
Hathras
OnePlus 9 Pro
Amazfit
I've a Xperia Z1 rooted with Kingroot... Can I have the Dual recovery with this root system? Which option (1,2,3 or 4) should i choose into the "installer" with Windows?
Thank you very very much

Inviato dal mio C6903 utilizzando Tapatalk

I rooted with Kingroot 4.1 on ZR!! And tried installing recovery and Kingroot did gave the option to install it and it got installed. Although after that I flashed a pre-rooted zip with supersu and xposed!!

Sent from XDA not so Premium App
Gitzz's Xperia™ ZR [Stock 5.0.2, SuperSu, Xposed, XZDR, LB]
 

chris.82

Senior Member
May 20, 2013
131
25
I rooted with Kingroot 4.1 on ZR!! And tried installing recovery and Kingroot did gave the option to install it and it got installed. Although after that I flashed a pre-rooted zip with supersu and xposed!!

Sent from XDA not so Premium App
Gitzz's Xperia™ ZR [Stock 5.0.2, SuperSu, Xposed, XZDR, LB]
Ok. But when the installer ask you the number of the operation (1,2,3 or 4) what you had selected?

Inviato dal mio C6903 utilizzando Tapatalk
 

[NUT]

Senior Member
why cant i install this.. no changes at all after installing or flash.. still only twrp

You are leaving out quite a lot of information I need to help you...

Use your brain and you will know what I want to know... if not, put yourself in MY position and imagine me asking you the same question...
 

jing000l

Senior Member
Mar 26, 2011
153
11
www.aq.co.ir
i have a problem with 21 version on ZR,after flash i cant access to internal memory (internal SD)
can some body do a favor and upload 20 version flashable for ZR asap,cause i cant find it on nut webpage,tnx
 

chris.82

Senior Member
May 20, 2013
131
25
I made the change from Kingroot to SuperSU and seems all right.

Now I tried to install the DualRecovery, but I have a problem: when I select “1” for the rooted ROM with SuperSU the program asks me to connect the phone. Basically it is as if he detects USB debugging. Why? *The problem there is before the charging from KR to SU too.


I tried to do the procedure suggested by @[NUT] : **“If you have USB debugging turned on, and your mobile disconnected from your PC, just make sure you 'revoke all authorizations for USB debugging' in the developer options menu. Then reboot your phone and before doing anything else, make sure you're looking at the home screen on your device, then hook up your USB cable. Your mobile should then ask if the connected PC is authorized or not. Once answered you can start the installer.” *...but it don’t work….

What can i do?! *Thank You!

Inviato dal mio C6903 utilizzando Tapatalk
 
Jun 28, 2015
49
9
Well, you leave out some crucial info on that request for help:

What type of Xperia? Is it rooted? are the developer options enabled and did you set USB Debugging ON?


==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================

1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit

Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================
error: protocol fault (no status)
Device found!

=============================================
Getting ro.build.product
=============================================
error: device offline
Device model is * daemon started successfully *
Firmware is 10.6.A.0.454

=============================================
Step2 : Sending the recovery files.
=============================================
8 KB/s (31 bytes in 0.003s)
2238 KB/s (18340 bytes in 0.008s)
97 KB/s (501 bytes in 0.005s)
1701 KB/s (12198 bytes in 0.007s)
2270 KB/s (65965 bytes in 0.028s)
601 KB/s (3082 bytes in 0.005s)
1900 KB/s (29204 bytes in 0.015s)
220 KB/s (1357 bytes in 0.006s)
1869 KB/s (34473 bytes in 0.018s)
234 KB/s (1202 bytes in 0.005s)
2139 KB/s (96956 bytes in 0.044s)
3516 KB/s (1410852 bytes in 0.391s)
3238 KB/s (3412607 bytes in 1.029s)
3167 KB/s (2313633 bytes in 0.713s)
3170 KB/s (1995185 bytes in 0.614s)
1914 KB/s (11760 bytes in 0.006s)

=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.

NOTE: this only works on certain ROM/Kernel versions!

If it fails, please check the development thread (Post #2) on XDA for more details.

REMEMBER THIS:

XZDualRecovery does NOT install any superuser app!!

You can use one of the recoveries to root your device.
=============================================

=============================================
Sending files
=============================================
865 KB/s (1776 bytes in 0.002s)
2654 KB/s (13592 bytes in 0.005s)
2947 KB/s (197320 bytes in 0.065s)
1848 KB/s (9496 bytes in 0.005s)
1335 KB/s (13672 bytes in 0.009s)
Copying kernel module...
2404 KB/s (34473 bytes in 0.014s)
249 KB/s (765 bytes in 0.002s)
3381 KB/s (96956 bytes in 0.028s)
Kernel version is 3.4.0-perf-g8fa3dae
Version does not match 3.4.0-perf-ge4322cd, needs patching...
dd: conv option disabled
Kernel module patched.

modulecrcpatch (by zxz0O0)

module_layout: patched to 0x42B348D2
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match

=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
error: only position independent executables (PIE) are supported.

=============================================
Installation finished. Enjoy the recoveries!
=============================================

Press any key to continue . . .

well, this is new. it worked, but it never rebooted or showed a green light when I restarted it. :confused:

Apparently I needed to root. I have dual recovery on my backup ZR now.
 
Last edited:

Top Liked Posts

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

    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: C5502, C5503, C5506
    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

    I will be adding more and more devices to the list in the near future, keep your eyes on this thread for them to be released :)
    I will also start a Q&A thread for each of the models officially supported, once released from the experimental stage.

    XZDualRecovery User Manual

    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
    • @russel5 for his tinkering and general debugging help :cool:

    GitHub Repository:
    https://github.com/xNUTx/XZDualRecovery

    Downloads:
    All past, current and future releases will appear on http://nut.xperia-files.com/ for download, also providing a QR code for easy downloading on your mobile :) The flashable file will bring any previous version to the latest release.

    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:

    XDA:DevDB Information
    XZDualRecovery, Tool/Utility for the Sony Xperia Z

    Contributors
    [NUT], AngelBob , shoey63 , Olivier, Krabappel2548, DooMLoRD, Cpasjuste, Tungstwenty, sijav, zxz0O0, MohammadAG, McBane87, oshmoun
    Source Code: https://github.com/xNUTx/XZDualRecovery


    Version Information
    Status: Stable
    Current Stable Version: 2.8.26
    Stable Release Date: 2016-02-22

    Created 2013-07-18
    Last Updated 2016-02-22
    250
    Hello guys,

    I noticed there are some problems getting dualrecovery to work on Lollipop. I created a small hack to bypass the SELinux enforcement (wonder why no one else created it already). Anyway I attached a little bat file to fix dualrecovery again (tested on Z3C).

    Source will be released in the next days and probably also integrated in the official dualrecovery.

    Happy eastern.

    Edit: Source available here https://github.com/dosomder/byeselinux
    136
    Known Issues and Frequently Asked Questions

    Known Issues:
    All known issues in PhilZ, TWRP and CWM on locked boot loaders apply, see their respective threads for more information.

    Busybox updaters can kill XZDualRecovery, see the FAQ below for more information.

    Frequently Asked Questions:

    How to set the correct time & date in PhilZ 6.59.0
    • Boot to PhilZ Touch;
    • Tap 'Recovery Settings';
    • Tap 'Gui Preferences';
    • Tap 'Time Settings';
    • Tap 'Change date and time';
    • Tic one of the last 3 options in this menu to try it;
    • Reboot to PhilZ Touch to see if it sticks, if not, try another and reboot to see if it helped, do this for all options to try them;
    • If one of them does help but does not stick at reboot, tic 'Try Force Persist on Reboot' once (it will un-tic itself after a reboot).
    • Done! :)

    NOTE: if it's close to being correct (max 15h difference before or after your time) you need to correct the timezone.


    About TWRP 2.6 and the use of INTERNAL STORAGE
    [snip]...but permissions are set like: Srw-Srw-r (644) (It seems like the 'S' is the problem, I'm sure GID and UID are ticked)...[snip]

    A workaround for this issue is to use TWRP's advanced options, after creating a backup you wish to move to the PC:

    1. go back to the main menu
    2. go to advanced
    3. go to filemanager
    4. navigate to /data/media/0/TWRP/BACKUPS/*SERIAL*/*BACKUPNAME*
    5. select one of the backup files
    6. press chmod button (the one without 755)
    7. type 0664 and press go
    8. repeat 5->7 for each of the files in the backup, you can skip boot and the md5 files.
    9. reboot to system and you should be able to copy the files without problems.

    Alternatively you can install adbd Insecure by @Chainfire (non-free app from Play, or for free from it's XDA thread) and run ADBd itself as root, which elevates the rights and omits the issue all together.

    I think it's a feature and not a bug (as it secures your backups), but I'll try to convince Team Win to make the setuid/setguid a choice rather then a default.


    Installation of XZDualRecovery on UNROOTED devices
    The 2.8.21 and older installer package uses Easy Root Tool for various Xperia phones, it is able to gain root on all of the currently supported devices, allowing to install XZDR.

    Confirmed working:
    • Z - C6603
    • Z1 Compact - D5503 (doesn't seem to work on JellyBean), SO-01F (docomo)
    • Z1 - C6903,
    • Z Ultra - C6802, C6833
    • ZR, C5502
    • Z2 - D6503
    • Z2 Tablet - SGP511, SGP512
    • ZL2 - SOL25

    If you want to help me perfect this list, use the tool done by @zxz0O0 in his topic and try to root your device. When testing also try older ROM versions, the latest FW versions may have been patched.

    Thanks @zxz0O0 for the initial list.

    The rootless installation has been made possible by:
    • @geohot: Root exploit
    • @MohammadAG: Disable RIC kernel module (Link)
    • @cubeundcube: Disable RIC on Z2 phone (findricaddr/writekmem)
    • @zxz0O0: for creating the initial tool where I have based this unrooted install option on.

    Thanks for your hard work guys! :highfive:

    The 2.8.22 and later installer package uses rootkitXperia for various Xperia phones, it is able to gain root on all of the currently supported devices -if they are running the correct Lollipop version- allowing to install XZDR.

    Thanks go to @cubeundcube and @zxz0O0 respectively for developing and making some changes to allow me to utilize it for XZDualRecovery installation. Thanks guys!


    XZDualRecovery's (2.8.21 and older) Busybox dependency and compatible Busybox updaters

    Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.

    @vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.

    Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox.

    XZDualRecovery 2.8.22 and newer do not suffer from this dependency, you can use whatever busybox updater app you like when you have 2.8.22 or newer installed.


    I installed XPOSED on Lollipop and now I am experiencing a boot loop!

    @ondrejvaroscak found a workaround to fix your bootloop issues: [WORKAROUND] Bootloops with Xposed in Lollipop

    While using the installer I get the message "This device is unauthorized" and I can't install XZDualRecovery!

    Authorizations... The latest versions of adb and android need this, it's nothing XZDR related. If you have USB debugging turned on, and your mobile disconnected from your PC, just make sure you 'revoke all authorizations for USB debugging' in the developer options menu. Then reboot your phone and before doing anything else, make sure you're looking at the home screen on your device, then hook up your USB cable. Your mobile should then ask if the connected PC is authorized or not. Once answered you can start the installer.
    122
    A small update on progress:

    The issues with XZDR are mainly caused by Sony actually properly setting up SELinux support for the very first time on the LP ROM's, something they neglected in all of the KK releases. This makes the LP version a lot more secure, which is a good thing. The problem is that I now know what to fix, but am still looking in to how to fix it. :angel:

    For the techies among us:

    During INIT the hijack still works, but the script is not able to change anything on the rootfs, it allows you to create a folder and if you mount a tmpfs on it you can write stuff to it, but if you try to write anything to the folder as it is (without tmpfs) it will not allow you to do so. This is because the SELinux context of my scripts is not set correctly, so the kernel blocks just about everything I try to do. I'm busy configuring and compiling a new busybox to include in XZDR with better SELinux support, as the one I am currently using is lacking the extended SELinux support I will need to fix this.
    The other problem is that init is less easy to override with the init from the recoveries, it simply continues the LP boot, I am in the progress of including 2nd-init support ( created by SkrilaxCZ ) and will be integrating parts and ideas of the safestrap project by Hashcode to fix these issues.
    The last but not least problem is that I can still mount the SDCard, but I am unable to write to it, most likely also due to the SELinux restrictions. If you remove the SDCard from the device it will use /cache which seems to be set up with less strict permissions and it will be able to do just about everything, except boot the actual recoveries.

    Last night I worked from 23:00PM all the night up to 6:30AM, pulling an almost an all-nighter. I'm not giving up just yet :cowboy:

    My thanks go to @Hashcode for a late night chat (for me that is, he was at work as he is located on the other side of the globe!) which helped me find the most likely cause.