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

Search This thread

kimdonghwan

Member
Jul 25, 2008
49
5
Hello.. i have Z3+ E6553 Single SIM

Unlock Bootloader Allowed = NO
1. Is it possible to make it YES?
2. Is it possible to install TWRP without Unlocking Bootloader?

Here is the status:
USB Debugging = ON
Unknown Sources = ON
OEM Unlock = YES (version 7.1 has this menu)
MyXperia = Deactivated
FindMyDevice = Deactivated

i flashed countless time various ROMS from 6.0 to 7.1
Googled everywhere for solution but failed

Please help me..Thanks in advance..
 
Last edited:



Hello.. i have Z3+ E6553 Single SIM

Unlock Bootloader Allowed = NO
1. Is it possible to make it YES?
2. Is it possible to install TWRP without Unlocking Bootloader?

Here is the status:
USB Debugging = ON
Unknown Sources = ON
OEM Unlock = YES (version 7.1 has this menu)
MyXperia = Deactivated
FindMyDevice = Deactivated

i flashed countless time various ROMS from 6.0 to 7.1
Googled everywhere for solution but failed

Please help me..Thanks in advance..
First of all, never quote the OP. Now the answer to your question: Unfortunately, not! The Z3 / Z3C phone series were the last flagship phones for which it was possible to have TWRP recovery installed still keeping their bootloaders locked. From the Z3+ onwards, with the implementation of dm-verity, root access can only be achieved after unlocking it. Nevertheless, as your phone' services menu states that you are not allowed to unlock it, I'm afraid you won't be allowed to root your phone.
 
Last edited:
  • Like
Reactions: kimdonghwan

kimdonghwan

Member
Jul 25, 2008
49
5
First of all, never quote the OP. Now the answer to your question: Unfortunately, not! The Z3 / Z3C phone series were the last flagship phones for which it was possible to have TWRP recovery installed still keeping their bootloaders locked. From the Z3+ onwards, with the implementation of dm-verity, root access can only be achieved after unlocking it. Nevertheless, as your phone' services menu states that you are not allowed to unlock it, I'm afraid you won't be allowed to root your phone.

i bought this phone via online shop and it is actually SOV31 from Japan, KDDI AU..shown on the label inside the SIM slot.
but i can use my country's SIM Card and has no problem with 2G-3G-4G..

Flashed with Original Japanese ROM, shown SOV31
Flashed with many Global ROMs, shown E6553

The status of the Network is 0, everything is 0 except Network Subset = 5

is there anything i can do to install TWRP or Phil ?
Thank you very much

Note:
i have seen several posts on this forum which have the same phone as mine, E6553 and also E6533..
Some people have Unlock Allowed = YES, while others NO.
It means Z3 / Z3C are not the last ones which can be unlocked.
We don't know the method and why some Yes some No.. :(
 
Last edited:
i bought this phone via online shop and it is actually SOV31 from Japan, KDDI AU..shown on the label inside the SIM slot.
but i can use my country's SIM Card and has no problem with 2G-3G-4G..

Flashed with Original Japanese ROM, shown SOV31
Flashed with many Global ROMs, shown E6553

The status of the Network is 0, everything is 0 except Network Subset = 5

is there anything i can do to install TWRP or Phil ?
Thank you very much

Note:
i have seen several posts on this forum which have the same phone as mine, E6553 and also E6533..
Some people have Unlock Allowed = YES, while others NO.
It means Z3 / Z3C are not the last ones which can be unlocked.
We don't know the method and why some Yes some No.. :(
All the phones by Sony can be unlocked, provided that 'Unlock allowed' says 'Yes'. Z3 and Z3C can have root access either locked or unlocked. From Z3+ onwards, only unlocked.
 

Francois76l

Senior Member
May 13, 2008
53
10
ROUEN
Dear all,
I'm desesperately looking for a recovery on my sgp512 running stock android 6.0.1 (23.5.A.1.291) to be able to install custom rom (AICP 13.1) on my Z2 tablet wifi version.
I'm trying to import my kernel.sin or boot.img here: http://nut.xperia-files.com/path/XZDualRecovery but no way something is not working.
Maybe someone can help me?...
Thanks for your help

My bootloader is unlocked
 
Last edited:

Rootk1t

Senior Member
Jun 2, 2013
2,112
868
Dear all,
I'm desesperately looking for a recovery on my sgp512 running stock android 6.0.1 (23.5.A.1.291) to be able to install custom rom (AICP 13.1) on my Z2 tablet wifi version.
I'm trying to import my kernel.sin or boot.img here: http://nut.xperia-files.com/path/XZDualRecovery but no way something is not working.
Maybe someone can help me?...
Thanks for your help

My bootloader is unlocked
Hello!

Look here. Also check your device subforum.
 

thewizardoz

Senior Member
Sep 22, 2009
83
2
Perth
I still got no response to my question re the empty XZDualRecovery 2.8.27 folder!

There are no files in Nut's XZDualRecovery 2.8.27 folder. :(

I still haven't got a response to my question about the XZDualRecovery 2.8.27 folder being empty!!

Is there a XZDualRecovery 2.8.27 version out there anywhere?

If not, what is the best recovery to install on a stock phone please?

Thanks.
 

serqeftin

Senior Member
Nov 4, 2011
189
31
Hi,
How can uninstall dualrecovery, because I cant install any newer version TWRP. help p.ease.
Thanks.

---------- Post added at 03:45 PM ---------- Previous post was at 03:45 PM ----------

Hi,
How can uninstall dualrecovery, because I cant install any newer version TWRP. help p.ease.
Thanks.
 
  • Like
Reactions: kleptes

maverick6664

Senior Member
Aug 18, 2017
86
17
Rooting D6616 failed

Hi,

I failed to root my D6116. I tried with supersu in vain. And I tried firmware D6616_23.1.C.0.385_R15C_US T-Mobile_1286-4514.ftf also, in vain.
Code:
Adjusting for SuperSU!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Step1 : Waiting for Device.
=============================================

Succes

=============================================
Device and firmware information:
=============================================
Device model is D6616
Firmware is 23.1.C.0.399
Android version is 5.0.2

=============================================
Step2 : Sending the recovery files.
=============================================

1 KB/s (31 bytes in 0.029s)
1925 KB/s (18170 bytes in 0.009s)
277 KB/s (501 bytes in 0.001s)
3755 KB/s (12812 bytes in 0.003s)
6105 KB/s (65965 bytes in 0.010s)
2004 KB/s (3159 bytes in 0.001s)
5412 KB/s (29204 bytes in 0.005s)
434 KB/s (699 bytes in 0.001s)
4687 KB/s (34473 bytes in 0.007s)
716 KB/s (1202 bytes in 0.001s)
6823 KB/s (96956 bytes in 0.013s)
7612 KB/s (870760 bytes in 0.111s)
7733 KB/s (3415700 bytes in 0.431s)
7542 KB/s (2420099 bytes in 0.313s)
3642 KB/s (14346 bytes in 0.003s)

=============================================
Step3 : Setup of dual recovery.
=============================================

Look at your device and grant supersu access!
/system/bin/sh: su: not found
Press enter to continue AFTER granting root access.

/system/bin/sh: /system/xbin/su: not found

=============================================
             Installation FAILED!

Please copy and paste the contents of
this window/screen to the DevDB thread.
=============================================
As you see, I'm running XZdualrecovery on Linux. What's wrong??
:confused:

EDIT: Finally rooted with KingRoot (windows version.) Now I'm replace this with supersu.
 
Last edited:

maverick6664

Senior Member
Aug 18, 2017
86
17
Self reply!!

Hi,

I failed to root my D6116. I tried with supersu in vain. And I tried firmware D6616_23.1.C.0.385_R15C_US T-Mobile_1286-4514.ftf also, in vain.

EDIT: Finally rooted with KingRoot (windows version.) Now I'm replace this with supersu.

My bad!!

It has turned out that I forgot to turn "Allow mock locations" on before I ran XZdualrecovery. Now twrp is in my D6616. Indeed it works with D6616 as advertised!! Sorry for misinformation!!!

Cheers and thanks NUT!! You are a jewel!!
 
Last edited:
  • Like
Reactions: saf4xdadev
Already use "search" but no one say about X Compact (Kugo) at 2019 :crying:
Someone know how to root with Locked Bootloader for X Compact?
AFAIK, since the Xperia Z3+ was released, with the implementation of dm-verity, it's not possible to have root privileges if one keeps its bootloader locked. The old Z3 and Z3 Compact models were the last ones to allow it. Nevertheless, the modifications were, then, done on the system partition.

Sent from my Xperia Z5 Compact using XDA Labs
 
  • Like
Reactions: shoey63

Radnanum

Senior Member
Dec 14, 2016
179
17
munandarif.blogspot.com
AFAIK, since the Xperia Z3+ was released, with the implementation of dm-verity, it's not possible to have root privileges if one keeps its bootloader locked. The old Z3 and Z3 Compact models were the last ones to allow it. Nevertheless, the modifications were, then, done on the system partition.

Sent from my Xperia Z5 Compact using XDA Labs

If i unlock bootloader, it has any side effect?
I remember it when still use Z3 a few year ago, if phone UB it affect to camera perfomance.
 
Last edited:
If i unlock bootloader, it has any side effect?
I remember it when still use Z3 a few year ago, if phone UB it affect to camera perfomance.
If your device happens to have a marshmallow ROM, you'd have the chance to make a backup of its TA partition (which contains the DRM keys), because the process of unlocking its bootloader wipes that partition for good. With that backup, it would be possible to prepare the stock kernel including your phone's DRM keys, and by ooting it through Magisk, it' would be highly probable to trick its system as if the bootloader was locked.

Sent from my Xperia Z5 Compact using XDA Labs
 
Last edited:
  • Like
Reactions: Radnanum

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.