I've already flashed the pre-rooted LP and have the device rooted but without RW. Can I change [NUT]'s script with the above and flash it, will I get RW?
[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE
- Thread starter [NUT]
- Start date
please can anyone tell me how to mount internal storage !! whenever I mount through recovery it just mount to external storage(SD card)
I've tried all the three recoveries [TWRP][PhilZ Touch][CWM]
am I missing something ? I'm using eXistenZ Ultimate | 3.5.5 Rom on my Xperia Z
USB debugging activated and the drivers are installed
I've tried all the three recoveries [TWRP][PhilZ Touch][CWM]
am I missing something ? I'm using eXistenZ Ultimate | 3.5.5 Rom on my Xperia Z
USB debugging activated and the drivers are installed
D6503_23.1.A.0.690_XZDRKernel2.8.3-RELEASE.flashable not work for me !!! thank's for your good job !!!
this did the trick for me
now xposed....fingers crossed
edit
xposed installed fine, but as soon I've activated the first module it went in bootloop
Last edited:
this did the trick for me
now xposed....fingers crossed
edit
xposed installed fine, but as soon I've activated the first module it went in bootloop
even if you dont install any module, it will bootloop after the second restart. tried so many times!
---------- Post added at 11:57 PM ---------- Previous post was at 11:55 PM ----------
lol, find myself refreshing this thread and nut's page every 10 mins. everyone else like me? hahaha
upload ur own kernel just to make sure! that's what i did, so that i know the kernel matches the firmware.
why would i ?! the idea is to flash NUT modified kernel which contain the stuff we need
Lol, you can upload your own kernel to nut's website and it will auto generate the modified version for you to download.
来自我的 D6603 上的 Tapatalk
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
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
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.
The issues with XZDR are mainly caused by Sony actually properly setting up SELinux support for the very first time on the LP ROM's, something they neglected in all of the KK releases. This makes the LP version a lot more secure, which is a good thing. The problem is that I now know what to fix, but am still looking in to how to fix it. :angel:
For the techies among us:
During INIT the hijack still works, but the script is not able to change anything on the rootfs, it allows you to create a folder and if you mount a tmpfs on it you can write stuff to it, but if you try to write anything to the folder as it is (without tmpfs) it will not allow you to do so. This is because the SELinux context of my scripts is not set correctly, so the kernel blocks just about everything I try to do. I'm busy configuring and compiling a new busybox to include in XZDR with better SELinux support, as the one I am currently using is lacking the extended SELinux support I will need to fix this.
The other problem is that init is less easy to override with the init from the recoveries, it simply continues the LP boot, I am in the progress of including 2nd-init support ( created by SkrilaxCZ ) and will be integrating parts and ideas of the safestrap project by Hashcode to fix these issues.
The last but not least problem is that I can still mount the SDCard, but I am unable to write to it, most likely also due to the SELinux restrictions. If you remove the SDCard from the device it will use /cache which seems to be set up with less strict permissions and it will be able to do just about everything, except boot the actual recoveries.
Last night I worked from 23:00PM all the night up to 6:30AM, pulling an almost an all-nighter. I'm not giving up just yet
My thanks go to @Hashcode for a late night chat (for me that is, he was at work as he is located on the other side of the globe!) which helped me find the most likely cause.
Last edited:
ok, i installed NUT AdvKernel, i noticed it didn't make XZDR.prop on the sdcard! is this why it couldn't find the recoveries to boot them? the file /sbin/xzdr.sh in ramdisk needs the property file.
Edit: ops, nevermind, it suppose to be in /cache
Edit: ops, nevermind, it suppose to be in /cache
Last edited:
@Nut thank you so much for your hard work and contribute to xda and to our Xperia's ☺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
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.
Thanks Guys
@[NUT] & @Hashcode, thanks very much for the incredible contribution of time, brainstorming (& anything else I have not considered), in making our Xperia's even more awesome than what they already are, can't wait for the new version of XZDR, I am even more excited about it now than what I was after updating to 5.0.2.
I am really enjoying your short updates about this latest issue and can't wait for the next working release of XZDR :good:
Thank You!
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
My thanks go to @Hashcode for a late night chat (for me that is, he was at work as he is located on the other side of the globe!) which helped me find the most likely cause.
@[NUT] & @Hashcode, thanks very much for the incredible contribution of time, brainstorming (& anything else I have not considered), in making our Xperia's even more awesome than what they already are, can't wait for the new version of XZDR, I am even more excited about it now than what I was after updating to 5.0.2.
I am really enjoying your short updates about this latest issue and can't wait for the next working release of XZDR :good:
Thank You!
Last edited:
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
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.
keep going dude.. i belive you can!
we all need d6630 prerooted can into recovery.
i pray for you luck
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
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.
Thank you very much NUT
While we are all waiting patiently for the next release of XZDR, let's show our thanks by making a donation to @[NUT] for the long hours and dedication. I believe he's saving for a Z4, or Z4 tablet.
My $50 USD Donation Sent (Unique Transaction ID #...890940W)
My $50 USD Donation Sent (Unique Transaction ID #...890940W)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
691-=[XZDualRecovery]=-
TWRP 2.8.7.0 & PhilZ Touch 6.59.0
*** For Locked and Unlocked BOOTLOADERS! ***
I proudly present you the first and only DUAL RECOVERY for locked boot loaders on our lovely Xperia phones!
If you have an unlocked bootloader and chose to keep the STOCK Sony kernel, you can also use this MOD.
Currently supported XPERIA models:
These are also links to the device specific Q&A threads.
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543, D6563
Xperia Tablet Z2: SGP511, SGP512, SGP521, SGP551, SGP561
Xperia ZR: C5502, C5503, C5506
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322
Xperia Z3: D6603, D6633, D6643, D6653, D6616
Xperia Z3 Compact: D5803, D5833
Xperia Tablet Z3 Compact: SGP621, SGP641, SGP651
I will be adding more and more devices to the list in the near future, keep your eyes on this thread for them to be released
I will also start a Q&A thread for each of the models officially supported, once released from the experimental stage.
XZDualRecovery User Manual
Special Thanks:
- DooMLoRD for all his excellent work on our much loved Sony phones!
- The Team Win developers for TWRP
- The ClockWorkMod developers for CWM
- @alexocean for his awesome job testing almost all FW releases and the discovery of SuperSU causing problems for the installation of this recovery!
- @RoberM for testing
- @surdu_petru for testing and handy pointers
- @Androxyde for allowing to use his linux and mac adb binaries.
- @lancebukkake for finding the TWRP 'fix' to use exFAT formatted sdcards!
- @delewer for the final fix for TWRP and its use of exFAT formatted sdcards
- @DevShaft for some code help on the windows installer (the menu!)
- @Androxyde again, but now for his bash code/script suggestions... oh boy this guy is a genius! :highfive:
- @Tamirwig and @shoey63 for their excellent job at testing early BETA's (Xperia Z)
- @gregbradley for his extensive testing on the Xperia Z1
- @russel5 for his tinkering and general debugging help
GitHub Repository:
https://github.com/xNUTx/XZDualRecovery
Downloads:
All past, current and future releases will appear on http://nut.xperia-files.com/ for download, also providing a QR code for easy downloading on your mobile The flashable file will bring any previous version to the latest release.
Well, enjoy! :fingers-crossed:
The origins of this XZDualRecovery package are in the packages done by:
Krabappel2548, Cpasjuste and DooMLoRD
Thank you for your excellent work guys! :victory:
Your thanks (and donations) should (also) go out to them, they deserve it! :highfive:
XDA:DevDB Information
XZDualRecovery, Tool/Utility for the Sony Xperia Z
Contributors
[NUT], AngelBob , shoey63 , Olivier, Krabappel2548, DooMLoRD, Cpasjuste, Tungstwenty, sijav, zxz0O0, MohammadAG, McBane87, oshmoun
Source Code: https://github.com/xNUTx/XZDualRecovery
Version Information
Status: Stable
Current Stable Version: 2.8.26
Stable Release Date: 2016-02-22
Created 2013-07-18
Last Updated 2016-02-22250Hello guys,
I noticed there are some problems getting dualrecovery to work on Lollipop. I created a small hack to bypass the SELinux enforcement (wonder why no one else created it already). Anyway I attached a little bat file to fix dualrecovery again (tested on Z3C).
Source will be released in the next days and probably also integrated in the official dualrecovery.
Happy eastern.
Edit: Source available here https://github.com/dosomder/byeselinux136Known Issues and Frequently Asked Questions
Known Issues:
All known issues in PhilZ, TWRP and CWM on locked boot loaders apply, see their respective threads for more information.
Busybox updaters can kill XZDualRecovery, see the FAQ below for more information.
Frequently Asked Questions:
How to set the correct time & date in PhilZ 6.59.0
About TWRP 2.6 and the use of INTERNAL STORAGE
Installation of XZDualRecovery on UNROOTED devices
XZDualRecovery's (2.8.21 and older) Busybox dependency and compatible Busybox updaters
I installed XPOSED on Lollipop and now I am experiencing a boot loop!
While using the installer I get the message "This device is unauthorized" and I can't install XZDualRecovery!
123122A small update on progress:
The issues with XZDR are mainly caused by Sony actually properly setting up SELinux support for the very first time on the LP ROM's, something they neglected in all of the KK releases. This makes the LP version a lot more secure, which is a good thing. The problem is that I now know what to fix, but am still looking in to how to fix it. :angel:
For the techies among us:
During INIT the hijack still works, but the script is not able to change anything on the rootfs, it allows you to create a folder and if you mount a tmpfs on it you can write stuff to it, but if you try to write anything to the folder as it is (without tmpfs) it will not allow you to do so. This is because the SELinux context of my scripts is not set correctly, so the kernel blocks just about everything I try to do. I'm busy configuring and compiling a new busybox to include in XZDR with better SELinux support, as the one I am currently using is lacking the extended SELinux support I will need to fix this.
The other problem is that init is less easy to override with the init from the recoveries, it simply continues the LP boot, I am in the progress of including 2nd-init support ( created by SkrilaxCZ ) and will be integrating parts and ideas of the safestrap project by Hashcode to fix these issues.
The last but not least problem is that I can still mount the SDCard, but I am unable to write to it, most likely also due to the SELinux restrictions. If you remove the SDCard from the device it will use /cache which seems to be set up with less strict permissions and it will be able to do just about everything, except boot the actual recoveries.
Last night I worked from 23:00PM all the night up to 6:30AM, pulling an almost an all-nighter. I'm not giving up just yet
My thanks go to @Hashcode for a late night chat (for me that is, he was at work as he is located on the other side of the globe!) which helped me find the most likely cause.
