Yes but exited... Closed even in the tray and background process too...
Sent from my C6603 using XDA Free mobile app
[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE
- Thread starter [NUT]
- Start date
Yes but exited... Closed even in the tray and background process too...
Sent from my C6603 using XDA Free mobile app
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
I'm assuming you are rooted already?
Open a CMD window, cd to the files directory inside the xzdr extraction folder. Connect your z and then type adb devices
It should give you a list of connected and adb recognised devices. It should also give a hint what to do next I guess
I hope thats right.
Kernel.sin from the new Xperia Z1c6903 Firmware 14.4.A.0.157_RC4_Customized Nordic
https://mega.co.nz/#!pt0gwIzS!l3ztyMFsSxQCzQfVHtC9okeNuBz3_fjywd8_QMNd130
Last edited:
Get me the kernel.sin then
Thank you very much
kernel from: Z3 Compact D5803_23.0.1.A.5.77_Stock kernel Sony
Impatiently waiting
Last edited:
I am a bit lost on the NDR Utils app. It says that it can’t XZDR.prop. I have checked the permission and it was both readable and writable.
Though I don’t have any problem accessing the recoveries using the volume buttons, I am just a bit worried with the app.
Let me know if this is irrelevant and I would be glad to remove this from your thread.
Cheers!
Though I don’t have any problem accessing the recoveries using the volume buttons, I am just a bit worried with the app.
Let me know if this is irrelevant and I would be glad to remove this from your thread.
Cheers!
As long as /system/bin/chargemon exists, the current XZDR project files will make it work as long as you have correct working recoveries built.
The thing is, from the top of my mind, the M2 and E3 do not have a Sony built ROM (but one built by third party development firm FOR Sony) and these lack this specific entry point.
This itself is the reason why things will be radically changed with the next version, making it able to hijack anything which is viable as a hijack...
Recovery Losing after Flash D1strikerz1's Rom
I lost recovery after flashed D1srtikersz1's Rom. In dual recovery topic, they say that I should install flash recovery again in order not to lose. I tried 10 times yesterday, but it failed. First I flash Rom. Second I untick reboot, come back to recovery. Third I flash dual recovery. Then reboot and Sony Loogo bootloop. What am I doing wrong? Can you fix this pls?
MOD EDIT Never quote the whole OP @gregbradley
I lost recovery after flashed D1srtikersz1's Rom. In dual recovery topic, they say that I should install flash recovery again in order not to lose. I tried 10 times yesterday, but it failed. First I flash Rom. Second I untick reboot, come back to recovery. Third I flash dual recovery. Then reboot and Sony Loogo bootloop. What am I doing wrong? Can you fix this pls?
I lost recovery after flashed D1srtikersz1's Rom. In dual recovery topic, they say that I should install flash recovery again in order not to lose. I tried 10 times yesterday, but it failed. First I flash Rom. Second I untick reboot, come back to recovery. Third I flash dual recovery. Then reboot and Sony Loogo bootloop. What am I doing wrong? Can you fix this pls?
MOD EDIT Never quote the whole OP @gregbradley
I lost recovery after flashed D1srtikersz1's Rom. In dual recovery topic, they say that I should install flash recovery again in order not to lose. I tried 10 times yesterday, but it failed. First I flash Rom. Second I untick reboot, come back to recovery. Third I flash dual recovery. Then reboot and Sony Loogo bootloop. What am I doing wrong? Can you fix this pls?
Last edited by a moderator:
Nope. I've decided to move fixing that to the next major version update, sorry mate.
Sorry...Not working on Xperia T2 Ultra Dual D5322 - 4.4.3
Philz and CWM woring but TWRP has no text display.
Thanks for the report! Are you able to take a photo of how TWRP looks on your phone? It might help me find the cause.
Please remove the OP quote, that's unnecessary...
Okay, try using the installer instead of the flashable package. So, prepare your phone, install XZDR, flash the ROM and boot it up. Then use the installer to install XZDR. I think the ROM you are flashing has replaced the chargemon binary with it's own recovery script and XZDR moves that to chargemon.stock. This is what creates the bootloop...
Ok, I'm sorry. I'm newly learning to use forum. First of all, with flashtool I flashed stock recovery, then root with this topic http://xdaforums.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298, then I installed your recovery, then I I flashed dstrikerz1's Rom, then I boot it up, then I installed recovery with your installer, while it is booting it created bootloop again. I did everyting according to rules, but something is wrong. maybe your recovery script has a bug maybe dstrikersz1's rom has a flashing bug. But I'm sure that something is wrong
Ok, I'm sorry. I'm newly learning to use forum. First of all, with flashtool I flashed stock recovery, then root with this topic http://xdaforums.com/xperia-z1/general/root-14-4-0-157-lb-ubl-t2933298, then I installed your recovery, then I I flashed dstrikerz1's Rom, then I boot it up, then I installed recovery with your installer, while it is booting it created bootloop again. I did everyting according to rules, but something is wrong. maybe your recovery script has a bug maybe dstrikersz1's rom has a flashing bug. But I'm sure that something is wrong
Flash only his ROM and forget XZDR for now. Then send me the /system/bin/chargemon binary you have in the (correctly working and running) dstrikersz1's rom. As soon as you can confirm beyond a shadow of a doubt the ROM is working correctly and I have had time to examine the chargemon binary/script we will find a solution to this issue.
ok, I will try to collect files which you want and I will make a zip and give a link to you. But it will take a time
Thanks for your help.
Get me the kernel.sin then
Thank you very much
kernel from: Z3 Compact D5803_23.0.1.A.5.77_Stock kernel Sony
Impatiently waiting
kernel post3131
http://xdaforums.com/attachment.php?attachmentid=3098577&d=1420415599
hi How to publish?
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.
