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

Search This thread

Bartekreaper

Senior Member
Nov 21, 2014
488
283
next to Wroclaw
@[NUT] I have looks like the same problem like @theduke7 but After flashing dualrecovery BETA i have NDR Utils and cant enter recovery, from app or buttons. There is no led, no green, no purple, just only vibration and booting to system... and cant mount system r/w

Edit. After install BETA installer, i have access to recovery and can mount system r/w ._.
 
Last edited:
  • Like
Reactions: [NUT]

harley1rocker

Senior Member
Jan 29, 2012
510
34
45
jemison
My build number is 270. BL is unlocked. Rooted using kingroot. HOW CAN I GET RECOVERY FROM HERE?

FLASHIFY? Zip file

Sent from my C6802 using XDA Free mobile app
 

o-l-a-v

Senior Member
Jan 6, 2012
685
544
Oslo
My build number is 270. BL is unlocked. Rooted using kingroot. HOW CAN I GET RECOVERY FROM HERE?

FLASHIFY? Zip file

Sent from my C6802 using XDA Free mobile app

Use "ZU-lockeddualrecovery2.8.21-RELEASE.installer.zip". Use option one first. If it fails, try option two. Should work :)
 

Attachments

  • Capture.PNG
    Capture.PNG
    5.8 KB · Views: 383

harley1rocker

Senior Member
Jan 29, 2012
510
34
45
jemison
Use "ZU-lockeddualrecovery2.8.21-RELEASE.installer.zip". Use option one first. If it fails, try option two. Should work :)

So flash this through flashify??? Wipe??? Dalvic,cache,data???

To be clear I have no recovery so far. I AM ROOTED WITH KINGROOT.

Sent from my C6802 using XDA Free mobile app

---------- Post added at 06:36 PM ---------- Previous post was at 06:04 PM ----------

Use "ZU-lockeddualrecovery2.8.21-RELEASE.installer.zip". Use option one first. If it fails, try option two. Should work :)

Hey Olav. Do I flash this using flashify

Sent from my C6802 using XDA Free mobile app
 

harley1rocker

Senior Member
Jan 29, 2012
510
34
45
jemison
Did it on a comp.... It does NOT WORK

Sent from my C6802 using XDA Free mobile app

---------- Post added at 09:56 PM ---------- Previous post was at 09:32 PM ----------

Thanks, that would be great :)

Sent from my C6603 using xda app-developers app

This whole shabang is horsesh!t. A person would spend days figuring all this out. AND MY PHONE CAME WITH THE BL UNLOCKED. Root was easy. But all the other garbage to get recovery is as stated above. I've ran all of it and it still fails. Fails and.........some more fails

Sent from my C6802 using XDA Free mobile app
 

thelegendy

Senior Member
May 6, 2013
254
39
Ankara
www.hamdicatal.com
Hi guys, i have a problem with installing recovery. I'm on the stock 23.4.A.0.546 non-rooted D6503. I downloaded "Z2-lockeddualrecovery2.8.21-RELEASE.installer" and extract to C: and ran "install.bat" file. After some processes, it said "Installation finished. Enjoy...". But my device doesn't reboot and I can't enter recovery. How can I enter recovery? Please, help me...
 

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Hi guys, i have a problem with installing recovery. I'm on the stock 23.4.A.0.546 non-rooted D6503. I downloaded "Z2-lockeddualrecovery2.8.21-RELEASE.installer" and extract to C: and ran "install.bat" file. After some processes, it said "Installation finished. Enjoy...". But my device doesn't reboot and I can't enter recovery. How can I enter recovery? Please, help me...
Can you copy paste the output of command window?

Sent from my D6603 using Tapatalk
 

thelegendy

Senior Member
May 6, 2013
254
39
Ankara
www.hamdicatal.com
Can you copy paste the output of command window?

Sent from my D6603 using Tapatalk

Yes, I can...

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]?3
* 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 D6503
Firmware is 23.4.A.0.546

=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (31 bytes in 0.031s)
1145 KB/s (18340 bytes in 0.015s)
0 KB/s (501 bytes in 1.000s)
762 KB/s (12198 bytes in 0.015s)
1745 KB/s (65965 bytes in 0.036s)
192 KB/s (3082 bytes in 0.015s)
3492 KB/s (29204 bytes in 0.008s)
84 KB/s (1357 bytes in 0.015s)
1075 KB/s (34473 bytes in 0.031s)
145 KB/s (1202 bytes in 0.008s)
2019 KB/s (96956 bytes in 0.046s)
2536 KB/s (1410852 bytes in 0.543s)
2249 KB/s (3415979 bytes in 1.483s)
2463 KB/s (2420805 bytes in 0.959s)
2311 KB/s (1936455 bytes in 0.818s)
734 KB/s (11760 bytes in 0.015s)

=============================================
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
=============================================
111 KB/s (1776 bytes in 0.015s)
828 KB/s (13592 bytes in 0.016s)
2188 KB/s (197320 bytes in 0.088s)
712 KB/s (9496 bytes in 0.013s)
854 KB/s (13672 bytes in 0.015s)
Copying kernel module...
1462 KB/s (34473 bytes in 0.023s)
0 KB/s (765 bytes in 1.000s)
2782 KB/s (96956 bytes in 0.034s)
Kernel version is 3.4.0-perf-gc42d8a9-01971-gef29327
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 0xCE969278
__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 . . .
 

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Yes, I can...

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]?3
* 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 D6503
Firmware is 23.4.A.0.546

=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (31 bytes in 0.031s)
1145 KB/s (18340 bytes in 0.015s)
0 KB/s (501 bytes in 1.000s)
762 KB/s (12198 bytes in 0.015s)
1745 KB/s (65965 bytes in 0.036s)
192 KB/s (3082 bytes in 0.015s)
3492 KB/s (29204 bytes in 0.008s)
84 KB/s (1357 bytes in 0.015s)
1075 KB/s (34473 bytes in 0.031s)
145 KB/s (1202 bytes in 0.008s)
2019 KB/s (96956 bytes in 0.046s)
2536 KB/s (1410852 bytes in 0.543s)
2249 KB/s (3415979 bytes in 1.483s)
2463 KB/s (2420805 bytes in 0.959s)
2311 KB/s (1936455 bytes in 0.818s)
734 KB/s (11760 bytes in 0.015s)

=============================================
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
=============================================
111 KB/s (1776 bytes in 0.015s)
828 KB/s (13592 bytes in 0.016s)
2188 KB/s (197320 bytes in 0.088s)
712 KB/s (9496 bytes in 0.013s)
854 KB/s (13672 bytes in 0.015s)
Copying kernel module...
1462 KB/s (34473 bytes in 0.023s)
0 KB/s (765 bytes in 1.000s)
2782 KB/s (96956 bytes in 0.034s)
Kernel version is 3.4.0-perf-gc42d8a9-01971-gef29327
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 0xCE969278
__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 . . .
You can not use towelroot on 546 (actually not on any Lollipop firmware). To install recovery you need to have already rooted firmware...

Sent from my D6603 using Tapatalk
 

ondrejvaroscak

Senior Member
Jan 21, 2015
1,517
1,159
Aachen
Did it on a comp.... It does NOT WORK

Sent from my C6802 using XDA Free mobile app

---------- Post added at 09:56 PM ---------- Previous post was at 09:32 PM ----------



This whole shabang is horsesh!t. A person would spend days figuring all this out. AND MY PHONE CAME WITH THE BL UNLOCKED. Root was easy. But all the other garbage to get recovery is as stated above. I've ran all of it and it still fails. Fails and.........some more fails

Sent from my C6802 using XDA Free mobile app
Watch mouth. You evidently have no clue what are you doing. In flashify you can only flash "flashable" zips and not "installer" zips. The installer you unzip on your pc and run the bat/shell.

However, you are rooted using Kingroot, so must first get rid of kingroot and install SuperSU or Superuser. Installer doesn't work with kingroot.

And don't blame others for your own incapacity.

Sent from my D6603 using Tapatalk

---------- Post added at 00:39 ---------- Previous post was at 00:37 ----------

So, should I downgrade to Kitkat and root it? If it is, how can I do this?
Or use kingroot and then replace kingroot with SuperSu. There is plenty guides how to root Z2/Z3 on XDA just take a while and search.

Sent from my D6603 using Tapatalk
 

T_money_third

Senior Member
Feb 6, 2014
55
3
Trinidad
Okey so I had duel recovery and I installed the play store busy box thinking I'd need it to get Viper android fx working. Only when the Rom I'm using got an update I realised I can't boot into recovery. Will flashing this again work?, or is the bootloader broken? I'm asking because I'll get to use a computer tomorrow I don't own 1
 

thangnh

Senior Member
Mar 17, 2010
130
3
Please help me. I installed Dual Recovery from my computer, then flash a custom ROM (Resurrection Remix), flash the recovery again before reboot (When installing custom ROMs: Be sure to flash XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!). Still I lost recovery ("Reboot into recovery" will go to stock recovery). Anything I've done wrong? Thanks.
 

sigprof

Senior Member
Jan 5, 2012
180
234
Please help me. I installed Dual Recovery from my computer, then flash a custom ROM (Resurrection Remix), flash the recovery again before reboot (When installing custom ROMs: Be sure to flash XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.flashable.zip from http://nut.xperia-files.com after installing the ROM and before you reboot, this way you will not lose recovery!). Still I lost recovery ("Reboot into recovery" will go to stock recovery). Anything I've done wrong? Thanks.
The XZDualRecovery installer and flashable versions are not compatible with custom ROMs which are not based on the stock kernel. If you are installing a ROM such as CyanogenMod, Resurrection Remix, or any other ROM which requires an unlocked bootloader, there are two options for using a custom recovery instead of the one built into the ROM:
  1. Go to the XZDualRecovery > Kernel Builder section on http://nut.xperia-files.com/, upload the boot.img file from your ROM, get back a kernel image with builtin XZDualRecovery, then flash that image in the fastboot mode. When you upgrade your custom ROM, repeat this process again using boot.img from the new ROM version (do not try to flash the kernel image made for an older ROM version — it may be incompatible with the updated ROM).
  2. Many custom ROMs for unlocked bootloader devices support loading the recovery image from the FOTAKernel partition; you can look for a "FOTA recovery" image in the forum for your device. If this works, it may be more convenient, because you will not need to reflash the recovery after upgrading the custom ROM, but you won't be using XZDualRecovery in this case.
 

Rootk1t

Senior Member
Jun 2, 2013
2,118
870
Okey so I had duel recovery and I installed the play store busy box thinking I'd need it to get Viper android fx working. Only when the Rom I'm using got an update I realised I can't boot into recovery. Will flashing this again work?, or is the bootloader broken? I'm asking because I'll get to use a computer tomorrow I don't own 1
You updated busybox and broke recovery)
See first post of this thread.
 
  • Like
Reactions: [NUT]

shoey63

Recognized Contributor
@[NUT] Hi
dear i want add your recovery in my boot.img ( sony xperia z ) and make custom boot.img
i know how to add one recovery ( like twpr or ... ) but dony know how can add dualrecovery at same time.
can you help me here?
thanks a lot man

Which rom or firmware do you want to add it to? Try the kernel builder, it does everything for you.
 

[NUT]

Senior Member
@russel5 I think I found a cause for the flashable package to fail...

It's caused by the fact that system is getting wiped on installation using a PRF created package... Now I need to really think long and hard how to fix this...

I also reintroduced an old bug, which I corrected already (something you helped me fix a while back), on my own kernel ric solution, the fix will be restored in the next beta version. This by itself might be the cause of the issue in the flashable version used in a PRF package... but I should fix this either way.

Expect a new BETA release today.
 
  • Like
Reactions: Bartekreaper

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.