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

Search This thread
By:
Advanced…
iBuzman

iBuzman

Senior Member
Mar 7, 2011
1,437
654
Melbourne
Sony Xperia XA2
^^ without the benefit of having 6 or 7 test devices either.. I built one zu rom and soft bricked a few dozen devices so I can only imagine the head scratching and stress this "hobby" (lol) must cause you. Thx again

(and I just double checked, yes I'm on latest beta 71 so not testing old versions :))

Sent from my C6833 using Tapatalk
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
iBuzman said:
^^ without the benefit of having 6 or 7 test devices either.. I built one zu rom and soft bricked a few dozen devices so I can only imagine the head scratching and stress this "hobby" (lol) must cause you. Thx again

(and I just double checked, yes I'm on latest beta 71 so not testing old versions :))

Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse

Yah... Headache's keep away luckily, just a bald spot from all the head scratching over these kinds of issues :silly:

I'll send you a PM. I will need some people on both JB 4.2 and JB 4.3 roms or the willingness to switch between them to be able to properly debug this, I'm assuming it might be kernel related...

To anyone else:

PLEASE DO REPORT EVERYTHING YOU FIND OUT OF THE ORDINARY, EVEN IF IT'S ONLY A MINOR INCONVENIENCE!!

And people, remember the golden rule: until I announce a release here, consider any newer package as 'alpha' build with possible unexpected results when installing or using.
 
Last edited:
  • Like
Reactions: iBuzman
AngelBob

AngelBob

Senior Member
Jun 23, 2013
275
628
The reason your only getting twrp when pressing up or down now is that DOWN will always boot twrp
UP boot's what is configured in the XZDR.prop, which i suspect is configured to twrp too.
 
Last edited:
iBuzman

iBuzman

Senior Member
Mar 7, 2011
1,437
654
Melbourne
Sony Xperia XA2
[NUT] said:
Dissapeared?? https://play.google.com/store/apps/details?id=com.camber.ndrutils

It should still show? :eek:
Click to expand...
Click to collapse

Weird.. It's disappeared from any search and this appears when following link:
u3u6a3eh.jpg

(don’t tell me I'm the only one who always tries vol-up-power first.. :silly: )

Strange because I was compatible when I installed it - and that's my 5 star review (in screenshot) suggesting you add z ultra to compatibility :)

I haven't done anything since (that I know of) that should cause this (no build prop, dpi changes etc)

Weird... A post just before mine couldn't find it either.


Edit: found and compatible when identified as 6802 instead of 6833 :)
Sent from my C6833 using Tapatalk
 
Last edited:
zOOOOmer

zOOOOmer

Senior Member
May 4, 2010
80
19
Moscow
kamalmawa said:
I have flashed stock .569 TFT -> unlocked bootloader using flashtool -> flash doomLords advanced stock kernel using fastboot -> Install latest UPDATE-SuperSU-v1.86.zip through CWM-> flash stock kernel -> relocked bootloader by restoring TA backup
this did not wipe my data or sdcard.
Click to expand...
Click to collapse
That part about flashing stock kernel - do I just get ftf, exclude everything in Flashtool and flash it?

PS I'm extremely sorry for going offtopic here.
 
CiscoX

CiscoX

Senior Member
Sep 24, 2012
273
74
frantic912 said:
any idea how to get stock recovery, not XZDualRecovery after flash this...?
Click to expand...
Click to collapse

Hi.
Read the first post :)

How to revert back to original single recovery:

This recovery MOD leaves your original recovery.tar in place.
You can overwrite the chargemon executable in /system/bin/ from this MOD with your backup made earlier and change its permissions to 755 (-rwxr-x-r-x).
You can then remove /system/bin/dualrecovery.sh (if it is there), /system/bin/recovery.twrp.cpio.lzma (or .tar), /system/bin/recovery.philz.cpio.lzma and /system/bin/recovery.cwm.cpio.lzma (or .tar) and reboot.
 
  • Like
Reactions: frantic912
CiscoX

CiscoX

Senior Member
Sep 24, 2012
273
74
@[NUT]

I can't upgrade from v.2.7.63 Beta to v.2.7.71 Beta. I used the XZ-lockeddualrecovery2.7.71-BETA.flashable.zip and install it from CWM after that i couldn't access any recovery. My device boot up normaly, vibrates and green led light, but i can't access any recovery, then led turn red and the device continue boot up.

I also tried to remove dualrecovery to make a new clean install of XZ-lockeddualrecovery2.7.71-BETA.installer.zip but that didn't help, no access to recovery. So i removed XZ-lockeddualrecovery2.7.71-BETA on device and installed XZ-lockeddualrecovery2.7.63-BETA.installer.zip and no problem, now i can access the recoveries :)

Any idea how to fix this?

I follow this:

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/ric
/system/bin/chargemon
/system/bin/dualrecovery.sh

Then inside */system/bin/ rename chargemon.stock to chargemon check its permissions (should be 755 or otherwise visible as -rwxr-x-r-x). Done!
 
frantic912

frantic912

Senior Member
Jan 22, 2011
141
13
Putrajaya
CiscoX said:
Hi.
Read the first post :)

How to revert back to original single recovery:

This recovery MOD leaves your original recovery.tar in place.
You can overwrite the chargemon executable in /system/bin/ from this MOD with your backup made earlier and change its permissions to 755 (-rwxr-x-r-x).
You can then remove /system/bin/dualrecovery.sh (if it is there), /system/bin/recovery.twrp.cpio.lzma (or .tar), /system/bin/recovery.philz.cpio.lzma and /system/bin/recovery.cwm.cpio.lzma (or .tar) and reboot.
Click to expand...
Click to collapse

tq....i try flash this update 1st
 
You must log in or register to reply here.

Similar threads

IgorEisberg
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.7.0]
Replies
3K
Views
3M
IgorEisberg
IgorEisberg
X
(PORT) (4.0+) (All Devices) (PS4 Remote Play Port)
Replies
2K
Views
1M
U
Unlinked
A
[TOOL] [UPDATE 04/09/2015] Flashtool version 0.9.19.10 - Windows / Linux / Mac
Replies
4K
Views
5M
Z
zdob
zxz0O0
Easy Root Tool for various Xperia devices
Replies
2K
Views
1M
L
lawrenceh
olokos
Unlock all bands of your Qualcomm device! Use your phone globally! No bs!
Replies
2K
Views
1M
Shahnewaz
Shahnewaz

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 691
    [NUT]
    [NUT]
    -=[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
    View
    250
    zxz0O0
    zxz0O0
    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
    View
    136
    [NUT]
    [NUT]
    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
    jdjta said:
    [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]
    Click to expand...
    Click to collapse

    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.
    View
    123
    [NUT]
    [NUT]
    Change log

    RELEASE Change log:

    http://nut.xperia-files.com/html/xzdualrecovery-change-log.html
    View
    122
    [NUT]
    [NUT]
    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.
    View

New posts