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

Search This thread

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
If I'm not misunderstanding, it's some of the bloatware that cause the boot loop?So weird. Do we have a way to know which specific one(s) then? :confused:

It may be one app, more apps or some combination... I think unless developers of Xposed can help to determine, it would be too complicated and lengthy to find out...

Sent from my D6603 using XDA Free mobile app
 

FcukBloat

Senior Member
Jun 18, 2012
6,284
3,012
If I'm not misunderstanding, it's some of the bloatware that cause the boot loop?So weird. Do we have a way to know which specific one(s) then? :confused:


yes weird but that has been confirmed already ;)


ondrejvaroscak said:
It may be one app, more apps or some combination... I think unless developers of Xposed can help to determine, it would be too complicated and lengthy to find out...

exactly very time consuming ;(
 

munkustrap

Senior Member
Apr 18, 2011
113
56
Shanghai
It may be one app, more apps or some combination... I think unless developers of Xposed can help to determine, it would be too complicated and lengthy to find out...

Sent from my D6603 using XDA Free mobile app



---------- Post added at 03:45 AM ---------- Previous post was at 03:42 AM ----------

yes weird but that has been confirmed already ;)


exactly very time consuming ;(
Sad. But according to this thread, installing Gmail and sync after debloating caused new boot loop. So my wild guess is the real reason might be more complicated than it looks, and hope the solution will be simpler than we have now.
 
Last edited:

FcukBloat

Senior Member
Jun 18, 2012
6,284
3,012
please stop OT now in respect to OP ;)

ps. as promised sent my donation @[NUT], that's not so much but hope it'll be enough for a couple of beers in the weekend you really deserve them thanks again for all your efforts! cheers :good: :p
 
  • Like
Reactions: [NUT]

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Possible workaround for mount problems in A8 2.8.6

IMHO is the problem in TWRP itself. In XZDualRecovery 2.8.6 is TWRP v2.8.6.0, whereas in XZDualRecovery 2.8.5 is TWRP v2.8.5.0.

I tried to replace recovery.twrp.cpio.lzma file in installer of 2.8.6 with version from 2.8.3, installed it over.

TWRP is back to version 2.8.5.0 and so far works well...
 
  • Like
Reactions: PVL_93_RU and [NUT]

MaSsAcRe1992

Member
Mar 17, 2015
39
3
Dortmund
Hm, so far its the only recovery for locked bootloader on XPERIA Z.

---------- Post added at 10:50 ---------- Previous post was at 10:47 ----------



You are a real massacre, really. Did you bother to read instructions?

Byeselinux is a script that disables enforcing Selinux, hence makes XZDualRecovery 2.8.3 working. You run it from Windows/Linux while connected to mobile over USB. You need to be already rooted.

SGP621-RICDefeat.zip is NOT flashable. You unzip it in PC, and like byeselinux, you run it while connected to your mobile. It disables RIC, hence enabling remounting filesystem in writable mode.

You need to uninstall and reinstall your file manager (Root explorer, ES File Explorer) after installing SGP621-RICDefeat.zip

Guys, I really wonder how many times I and others have to write it down.

havent had much time to google it and wanted a shoprt answer, much thanks my friend. :)
 

[NUT]

Senior Member
XZDualRecovery 2.8.7 Released!

RELEASE Change log:
Version 2.8.7:
  • Fully debugged for use with Sony's Lollipop and restored functionality on KitKat on all supported models. Both for locked bootloader installations and the XZDualRecovery Advanced Stock Kernel builder.
  • Included the byeselinux patch by @zxz0O0, heavily modified. It will unload the module when booting to the ROM to restore SELinux functionality.
  • Converted XZDR from using my own solution to the more elegant 'wp_mod' method by @MohammadAG. It now uses my own solution as a backup.
  • Made sure the modules will only be installed when required either by device or ROM version.
  • Updated the flashable package to do the same.
  • Updated the included NDR Utils to the latest version.
  • Updated the (installer) included adb binaries to the current latest version (Required when using TWRP 2.8.6.0 and newer).
  • The installer and the chargemon hijack script will now make a copy of the init 'rc' files to /system/.XZDualRecovery to be used during updates using the flashable zip, this way the (long!) list of firmwares in the installdisableric.sh script can be discarded in the future, which was only used in the flashable package because these init rc files are unavailable while in recovery.

My immense gratitude goes to all the people involved in debugging this release, your input, tinkering, patience and test results where invaluable.

Thank-You-message2_edited-1.png
 

akkufix

Senior Member
Mar 12, 2011
1,244
1,111
Ok, 2.8.7 (think it is A8 now?) works for me on D6503 XZ2, LB and LP.
I "updated" working 2.8.3 recovery with installer 2.8.7 and can access Philz, TWRP and CWM.
Sure, also R/W works fine. Could create a directory in /
:good: A big thanks to you @[NUT]
 
Last edited:

[NUT]

Senior Member
Ok, 2.8.7 (think it is A8 now?) works for me on D6503 XZ2, LB and LP.
I "updated" working 2.8.3 recovery with installer 2.8.7 and can access Philz, TWRP and CWM.
Sure, also R/W works fine. Could create a directory in /
:good: A big thanks to you @[NUT]

Not for 100%, the flashable zip contained a small bug, which has now been fixed. The NDR Utils and adb binary updates are new to 2.8.7 too.
 

adolfovm

Senior Member
Nov 25, 2011
89
61
Mexico City
yes weird but that has been confirmed already ;)




exactly very time consuming ;(

I'm not so sure the issue comes from bloatware, I think it's more some odex files, from a similar thread I downloaded the specific file only for deodexing the Z2 rom without any debloating and I have no bootloop issues afterwards, didn't faced any FCs either. After applying the deodex zip all was working smoothly with Xposed!

This is the thread that talks about the issue:

http://xdaforums.com/xperia-z2/development/fix-xposed-bootloop-23-1-0-690-d6503-t3073129

And if it helps anyone here's the Z2's zip for deodexing only and making xposed work after reboots:

http://xdaforums.com/showpost.php?p=59909535&postcount=39
 

pepzin

Member
May 25, 2011
15
10
Updated to 2.8.7 from TWRP :victory: :highfive:

Seriously [NUT], thank you for being so awesome! I can't remember the last time I saw a developer being so helpful and a complete opposite of elitist. It really shows that you are very passionate for this project, and because I did som investigation on my own, I now know much more about the boot process of an Android device.

And thats why I will donate what I can afford to you now :)
 

fabfor

Senior Member
Jul 1, 2010
145
47
RELEASE Change log:
Version 2.8.7:

It seems that I am the only one experiencing problems with last build..
I was on 2.8.3 with zxz0O0 script installed, Lollipop on D6603.
After running 2.8.7 installer the phone rebooted to system and not to recovery , it seems that I lost root (tried adaway and it cannot copy host file) and cannot mount / as rw in root explorer while I could before.
Neither NDR utils nor keypress lead me to recovery...
What did I do wrong???
Find attached cmd window and XZDualRecovery folder.
Please help me to debug, I am the one who lost bluetooth funcionality after applying zxz0O0 script. If this is related, I can provide logs about bluetooth failure.

Code:
==============================================
=                                            =
=  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]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!

=============================================
Getting ro.build.product
=============================================
Device model is D6603
Firmware is 23.1.A.0.690

=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (30 bytes in 0.031s)
1091 KB/s (17459 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
371 KB/s (11893 bytes in 0.031s)
2061 KB/s (65965 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
1884 KB/s (30148 bytes in 0.015s)
1 KB/s (1357 bytes in 1.000s)
1077 KB/s (34473 bytes in 0.031s)
68 KB/s (1089 bytes in 0.015s)
849 KB/s (13592 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
4497 KB/s (719520 bytes in 0.156s)
4344 KB/s (3419223 bytes in 0.768s)
3781 KB/s (2420408 bytes in 0.625s)
3903 KB/s (1936104 bytes in 0.484s)
11 KB/s (11305 bytes in 1.000s)

=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x    1 shell    shell       719520 Apr 10 23:14 /data/local/tmp/recovery/busybox
Premere un tasto per continuare . . .

##########################################################
#
# Installing XZDR version 2.8.7 RELEASE
#
#####

Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
The byeselinux module exists, testing if the kernel accepts it.
insmod: can't insert '/system/lib/modules/byeselinux.ko': File exists
Removing zxz0O0's byeselinux patch module, restoring the original.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy disableric to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
mkdir: can't create directory '/sdcard/clockworkmod/': Permission denied
touch: /sdcard/clockworkmod/.hidenandroidprogress: Permission denied
Make sure firstboot goes to recovery.

=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================


=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================


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

Attachments

  • XZDualRecovery.zip
    3.5 KB · Views: 48
Last edited:

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Not for 100%, the flashable zip contained a small bug, which has now been fixed. The NDR Utils and adb binary updates are new to 2.8.7 too.

Installed 2.8.7, TWRP still shows error on postrecoveryboot.sh ended with ERROR=1
Wiping data also error E:mount -o bind ´/data/media/0 .....etc.

Modifying your recovery 2.8.7 with TWRP 2.8.5.0 because 2.8.6.0 causes errors in wiping...

Philz works normally..

---------- Post added at 01:16 ---------- Previous post was at 01:06 ----------

It seems that I am the only one experiencing problems with last build..
I was on 2.8.3 with zxz0O0 script installed, Lollipop on D6603.
After running 2.8.7 installer the phone rebooted to system and not to recovery , it seems that I lost root (tried adaway and it cannot copy host file) and cannot mount / as rw in root explorer while I could before.
Neither NDR utils nor keypress lead me to recovery...
What did I do wrong???
Find attached cmd window and XZDualRecovery folder.
Please help me to debug, I am the one who lost bluetooth funcionality after applying zxz0O0 script. If this is related, I can provide logs about bluetooth failure.

Code:
==============================================
=                                            =
=  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]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!

=============================================
Getting ro.build.product
=============================================
Device model is D6603
Firmware is 23.1.A.0.690

=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (30 bytes in 0.031s)
1091 KB/s (17459 bytes in 0.015s)
31 KB/s (501 bytes in 0.015s)
371 KB/s (11893 bytes in 0.031s)
2061 KB/s (65965 bytes in 0.031s)
192 KB/s (3082 bytes in 0.015s)
1884 KB/s (30148 bytes in 0.015s)
1 KB/s (1357 bytes in 1.000s)
1077 KB/s (34473 bytes in 0.031s)
68 KB/s (1089 bytes in 0.015s)
849 KB/s (13592 bytes in 0.015s)
24 KB/s (385 bytes in 0.015s)
4497 KB/s (719520 bytes in 0.156s)
4344 KB/s (3419223 bytes in 0.768s)
3781 KB/s (2420408 bytes in 0.625s)
3903 KB/s (1936104 bytes in 0.484s)
11 KB/s (11305 bytes in 1.000s)

=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x    1 shell    shell       719520 Apr 10 23:14 /data/local/tmp/recovery/busybox
Premere un tasto per continuare . . .

##########################################################
#
# Installing XZDR version 2.8.7 RELEASE
#
#####

Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
The byeselinux module exists, testing if the kernel accepts it.
insmod: can't insert '/system/lib/modules/byeselinux.ko': File exists
Removing zxz0O0's byeselinux patch module, restoring the original.
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy disableric to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
mkdir: can't create directory '/sdcard/clockworkmod/': Permission denied
touch: /sdcard/clockworkmod/.hidenandroidprogress: Permission denied
Make sure firstboot goes to recovery.

=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================


=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================


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

I know it will sound horrible, but try install fresh Lollipop, prerooted. Or even better clean stock KK, so you can prove your Bluetooth thing is not HW related. As for recovery, try SGP621-RICDefeat.zip (no flash, install from PC) to regain system r/w and see if you can get 2.8.7 work, if not, just start from scratch with clean KK/LP.
 
Last edited:

Meannekes

Senior Member
Dec 23, 2009
220
88
FW: 23.2.A.0.278
Created prerootet firmware with your dualrecovery in it (2.8.7)(added version to disableric)
Works fine here, thanks
 

fabfor

Senior Member
Jul 1, 2010
145
47
I know it will sound horrible, but try install fresh Lollipop, prerooted. Or even better clean stock KK, so you can prove your Bluetooth thing is not HW related.
horrible indeed!!! :eek::eek::eek:
... I thought the same at the beginning, but not after reading lines like this in logcat
Code:
E/bt_upio (27738): set_bluetooth_power : write(/sys/class/rfkill/rfkill0/state) failed: Operation not permitted (1)
well, I don't really know how to debug it, but it doesn't make me think of something HW related

As for recovery, try SGP621-RICDefeat.zip (no flash, install from PC) to regain system r/w and see if you can get 2.8.7 work, if not, just start from scratch with clean KK/LP.
Regained root, system r/w and recovery reinstalling xzx0O0 and 2.8.3.
I stop here atm, goodnight everybody
 

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.