[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE
- Thread starter [NUT]
- Start date
Im still on lollipop. is there a way to update just the TWRP recovery to latest v3.0.3?
Last edited:
Hm, I updated TWRP via XYDualrecovery but then I only have TWRP 3.
If it is ok, you can flash twrp inside old twrp. I think you have to set the file filter from zip to img.
If it is ok, you can flash twrp inside old twrp. I think you have to set the file filter from zip to img.
Do I need to select the partition to flash .img to kernel image during the installation.?
Hello,
I downgraded my lolipop to kitkat then rooted and I want to instal dualrecovery. I don't know exactly what to do with it. I want to install xposed + lolipop thats why I'm needing recovery. It looks like a problem with install.bat but im not sure. BTW. Sorry for my english.
EDIT:
I'm sure that I downloaded the whole zip right. I also tried it on different PC and the same error. Yes I unpacked it.
EDIT2:
I solved this problem
Nevermind
I downgraded my lolipop to kitkat then rooted and I want to instal dualrecovery. I don't know exactly what to do with it. I want to install xposed + lolipop thats why I'm needing recovery. It looks like a problem with install.bat but im not sure. BTW. Sorry for my english.
EDIT:
I'm sure that I downloaded the whole zip right. I also tried it on different PC and the same error. Yes I unpacked it.
EDIT2:
I solved this problem
Nevermind
Last edited:
yes. You can. Though, latest version may have issues with such an old android as 4.2.2
I need some help please. I wanted to root my Xperia T2 Ultra D5303 on Android 5.0.1 with this (on Windows 10), but I get lots of permission denied and no such file or directory errors.
Is there any fix for this?
Code:
find: `/i': No such file or directory
find: `5.1': No such file or directory
find: `/c/$Recycle.Bin/S-1-5-18': Permission deniedIs there any fix for this?
I have a problem.
I was running at Official 6.0.1 Android, locked bootloader, without a root. Then I decided to get custom rom. So I've unlocked my bootloader on official Sony way, then I wanted to root my device but I needed to downgrade to 5.0.2. And I did it. Then, using the KingRoot I rooted my device successfully, Install SuperSU. Then I needed the TWRP. So I download it (lastest version from official website) and install it using install.bat file. Then I install this ROM, also bootloop fix through the TWRP. Wipe system, Cache, and Prepare to install new ROM. My device successfully booted into system but there is no NDR Utils app. I've tried to download it from Google Play Store but then I got this message "Unable to read XZDR.prop [NUT]'s XZDualRecovery is required for this future".
I tried to install it again on usual way using install.bat file, but my device stock at boot, freezes at boot up animation.
What to do? How to install TWRP again, but not to install new custom rom...and not to get stuck at boot animation..?
ANY HELP WOULD BE APPRECIATED :good::fingers-crossed::victory::victory:
I was running at Official 6.0.1 Android, locked bootloader, without a root. Then I decided to get custom rom. So I've unlocked my bootloader on official Sony way, then I wanted to root my device but I needed to downgrade to 5.0.2. And I did it. Then, using the KingRoot I rooted my device successfully, Install SuperSU. Then I needed the TWRP. So I download it (lastest version from official website) and install it using install.bat file. Then I install this ROM, also bootloop fix through the TWRP. Wipe system, Cache, and Prepare to install new ROM. My device successfully booted into system but there is no NDR Utils app. I've tried to download it from Google Play Store but then I got this message "Unable to read XZDR.prop [NUT]'s XZDualRecovery is required for this future".
I tried to install it again on usual way using install.bat file, but my device stock at boot, freezes at boot up animation.
What to do? How to install TWRP again, but not to install new custom rom...and not to get stuck at boot animation..?
ANY HELP WOULD BE APPRECIATED :good::fingers-crossed::victory::victory:
I read somewhere that EliteKernel have it's own recovery. That should be enough?
Elitekernel need unlocked bootloader.. If you unlock it you will loose drm keys. Be sure you have backup of your TA partition before unlocking.
My bootloader is definitely unlocked. And EliteKernel is installed. I guess that if I couldn't install it if my Bootloader is locked...?
Never tried flash custom kernel on locked bootlader but if isn't unlocked you will stuck on boot logo..
Hi all,
1) I have installed this recovery on z3c 4.4.4. I have successfully obtained both recoveries, but my installer couldnt clean the phone in this step:
"Reboot to system from recovery to allow the installer to clean up after installation"
It just stopped and wrote "Enjoy recoveries" or stg like that. I Wonder if there may be residual files in my phone's root directory due to this skip?
2) Moreover, I have installed slim 3.8 successfully, but x-plore file manager cant delete or edit root files anymore. I can do with ES file explorer, but that was not the case with my previous installations(different recovery also) and I think it maybe due to my incorrect installation of xzdualrecovery?
Thanks in advance
1) I have installed this recovery on z3c 4.4.4. I have successfully obtained both recoveries, but my installer couldnt clean the phone in this step:
"Reboot to system from recovery to allow the installer to clean up after installation"
It just stopped and wrote "Enjoy recoveries" or stg like that. I Wonder if there may be residual files in my phone's root directory due to this skip?
2) Moreover, I have installed slim 3.8 successfully, but x-plore file manager cant delete or edit root files anymore. I can do with ES file explorer, but that was not the case with my previous installations(different recovery also) and I think it maybe due to my incorrect installation of xzdualrecovery?
Thanks in advance
What's the latest rootable firmware version for z2 D6503, I can install this recovery on? Thanks.
Sent from my SM-G955F using Tapatalk
Sent from my SM-G955F using Tapatalk
Similar threads
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!
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
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-22250Hello 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/byeselinux136Known 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
About TWRP 2.6 and the use of INTERNAL STORAGE
Installation of XZDualRecovery on UNROOTED devices
XZDualRecovery's (2.8.21 and older) Busybox dependency and compatible Busybox updaters
I installed XPOSED on Lollipop and now I am experiencing a boot loop!
While using the installer I get the message "This device is unauthorized" and I can't install XZDualRecovery!
123122A 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
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.
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
