[DEVDB][TWRP][PhilZ Touch] XZDualRecovery 2.8.26 RELEASE
- Thread starter [NUT]
- Start date
sorry wrong wrote b4. imean supercharger.
extract file to your root sdcard1 than use smanager that you can download from play store.
this link for supercharger download include busybox. 1.19.4.
https://app.box.com/s/gwy7g161ojlt7uu8ddeo
download smanager from play store. that use
it to run startme... in directory of supercharger. only thick SU on smanager than run it. c.on picture attached. follow all instruction when run it. choose all Yes.
Sent from my C6602 using xda premium
Attachments
Read on 1st page post on this thread
or
try this recovery to flash dual recovery.
you only need root access
https://app.box.com/s/yd0oni809rdfsjmb76x8
Sent from my C6602 using xda premium
Last edited:
I' ve exp experienced a possible bug with the XZD. It took me over a day of sleuthing, but once found it was easy to reproduce.
It seems running the XZD script prevents apps from being able to correctly use the built-in light meter.
It took me over a 40 point checklist of steps after flashing the ROM, but when it came to running the XZD script, all light meter apps stopped running correctly, reporting that the light meter was unavailable. Removing the recovery was the only way to bring it back. Tested on two apps, GPS status and "Light meter v.4".
Install XZDR, no light meter.
Remove XZDR, working light meter.
On XperiaZL, 10.3.a.0.423 C6502
Can anyone confirm this?
Any ideas how to get recovery and keep the light meter?
Sent from my C6502 using xda app-developers app
It seems running the XZD script prevents apps from being able to correctly use the built-in light meter.
It took me over a 40 point checklist of steps after flashing the ROM, but when it came to running the XZD script, all light meter apps stopped running correctly, reporting that the light meter was unavailable. Removing the recovery was the only way to bring it back. Tested on two apps, GPS status and "Light meter v.4".
Install XZDR, no light meter.
Remove XZDR, working light meter.
On XperiaZL, 10.3.a.0.423 C6502
Can anyone confirm this?
Any ideas how to get recovery and keep the light meter?
Sent from my C6502 using xda app-developers app
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
Please help me help you by doing 2 things:
1) let me know what apps you tried and
2) test it with another recovery to make sure it's XZDualRecovery causing it as sole package...
-Edit-
Tried andoid sensor box from Play... It's free and works for me...
Sent from my C6603 using xda app-developers app
Last edited:
I've tried GPS Status and Toolbox (has integrated light meter), beeCam light Meter (FM Bee), Light Meter (Borce Trajkovski), Rex Light Meter, Light Meter (TomCode), Light Meter (Diax), and Light-o-meter (Spaceware). None of these worked with the XZDR installed, and the first two I tried (Diax and GPS Status) without XZDR worked.
Can you recommend a recovery that will work on 10.3.A.0.423, preferably CWM? That's what brought me to XZDR, it's the only one I could find at the time that would work. I'd like to assume that recoveries that would work for the Z would also work for the ZL, but I'm sure you'll warn me not to do that.
BTW I'm using version 2.5.1.
Last edited:
Just tried with 2.6, got the same thing.
In Light Meter v.4:
"Light sensor data are not available."
After following XZDR removal instructions, they're back again, right as rain.
Any logs I could help you with? Just tell me where to find them.
I'm having a bit of a tough time finding a different recovery for this firmware. I tried an old doomkernel for 253 but it bricked my phone. I really don't see that many options for this firmware.
Hmm... As you can see, they both work just fine for me... All of the sensors do... What you have is really awkward...
Sent from my C6603 using xda app-developers app
I can add that the light sensor doesn't appear to work for me either.
I haven't tried removing the recovery to see if that fixes it.
Edit : The ambient light sensor test via the service menu returns an empty value.
Something is not right.
Just for info, I have a C6603 on sw version 10.3.A.0.423 generic ES, customisation number 1270-6697. Rooted and dual recovery installed. No other mods or other alterations to /system.
Sent from my C6603 using Tapatalk 2
I haven't tried removing the recovery to see if that fixes it.
Edit : The ambient light sensor test via the service menu returns an empty value.
Something is not right.
Just for info, I have a C6603 on sw version 10.3.A.0.423 generic ES, customisation number 1270-6697. Rooted and dual recovery installed. No other mods or other alterations to /system.
Sent from my C6603 using Tapatalk 2
Last edited:
Well, sure...insofar as any unexpected, apparently completely inconsistent bug might be considered "awkward". Attributing Dalvik scanning on every boot seemed more consistent than this problem does, and that wasn't even it, as it turns out.
But I've eliminated every other posibility. Not having the flight meter really irked me , so I flashed to a stock kernel that I knew worked with the light meter, first thing after flashing and general set-up was to install GPS Status &Tollbox so I could check the light meter, which worked. Then I went through *40* individual steps, robooting the phone between each step, checking the light meter, then logging the update and light meter check.
The penultimate update, before the final update of restoring Titanium backup and cleaning up after that, was the XZDR.
After 40 reboots and checks after each update, it was the XZDR that took out my light meter. Removing XZDR per instructions brought back the light meter in every case, multiple apps tested, under 2 different versions of XZDR.
Now it appears we have it on both Z and ZL.
Here's a random idea:
Write this as an app, that when switched "on" writes all the files (the ones deleted/renamed during the XZDR removal) into their correct place, then when instructed boot into either CWM or TWRP from system shutdown. After finishing in recovery, phone reboots into recovery switched "off" mode, with all the files mentioned before renamed to stock or deleted*.
*Or better yet just renamed.
Last edited:
Picked up my Xperia Z last night woop woop :victory:
I'm having the same issue as godjak i.e. I can't boot into CWM.. but TWRP is fine. I followed the instructions in the OP and then tried a couple of times and searched before posting here. Any ideas?
My setup: rooted, locked, superuser and running unbranded .434
Same here: with DualRecovery light sensor doesn't work; without DualRecovery light sensor work.
C6603 with 10.3.1.A.0.244 firmware.
With the update to .244 my phone started doing the same, so now I have something to really test on...
Sent from my C6603 using xda app-developers app
Sent from my C6603 using xda app-developers app
I had the problem on 423, so it doesn't seem dependant on firmware version.
Sent from my C6603 using Tapatalk 2
No, not really:
I never had it before the latest... but i have a hunch what it might be ... The ROM has no issues accessing the light sensor, just the apps... which points me in a certain direction on where to look for the cause.
I HOPE I'll get some time tonight to experiment with the hunch.
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.
