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

Search This thread

kamalmawa

Senior Member
Sep 24, 2010
1,496
1,145
Melbourne
This is where it gets interesting... it detects the correct node for the XZ...

Does your volume control still work using the volume buttons? :eek:

It should work just fine... :confused:

A little tutorial, to compare your effords to try and get in to a recovery:
Turn on Phone, you see the kernel logo;
You feel the phone vibrate 2 times with a green led;
NOTE: WHILE the green led is burning you have 3 seconds to press either volume-up or volume-down;
You press one of the 2 volume buttons ONCE while the LED is still green to enter a recovery.

What do you different from this guide?

Omg this is now even now more crazy. Now I can go to TWRP using both volume up and down keys but no phliztouch cwm. Before it wasn't working at all. Like the other guy said it turned red after purple. I did have a habit of abusing the volume key instead of pressing once though but it never caused any problems before.
Windows installer usually rebooted to phliztouch for the first time. But now it won't happen. I'm gonna do a clean install again. Which files should I delete?

Sent from my C6603 using Tapatalk
 

[NUT]

Senior Member
Omg this is now even now more crazy. Now I can go to TWRP using both volume up and down keys but no phliztouch cwm. Before it wasn't working at all. Like the other guy said it turned red after purple. I did have a habit of abusing the volume key instead of pressing once though but it never caused any problems before.
Windows installer usually rebooted to phliztouch for the first time. But now it won't happen. I'm gonna do a clean install again. Which files should I delete?

Sent from my C6603 using Tapatalk

Don't delete anything. What you are experiencing is a feature and not a bug... I'll do a little patch up to make it boot to philz with the vol-up again. Anyone who wants to go to vanilla CWM will need to use NDR Util.

I'll also try to make the command feature work with @Tungstwenty's number 2 solution while I'm at it :) I always meant to fix that somehow, some day :D
 

[NUT]

Senior Member
BETA Change log:
BETA releases will only appear on http://nut.xperia-files.com and the DevDB thread and as soon as enough people report it to be working fine will it move in to the Q&A thread as a RELEASE version.
Version 2.7.74:
  • Restored the use of apps which allow you to boot to recovery to perform a specific task, based on an idea from @Tungstwenty. :good:
    NOTE: This feature is largely untested but it should work OK :fingers-crossed:
  • Restored the Volume-UP key in it's former glory. If you wish to boot to Vanilla CWM, you MUST use NDRUtils.
  • Eventhough it impacts speed on exFAT formatted SD cards, I've reverted PhilZ to use the minivold to mount the SDcard1 and USB disks, to fix the compatibility with the Z1 and Z Ultra.

Enjoy! :good:

Please DO report everything not working as intended!
 

jagdesh

Senior Member
Sep 30, 2009
1,108
275
Pune
Hi Nut. I would like to report that the now pressing the volume up button I am entering into Philz recovery but for some reason the backlight of the phone is kit working on Philz recovery. I mean the phone's backlight does not work and it does on TWRP

Sent from my C6903 using XDA Premium 4 mobile app
 
  • Like
Reactions: [NUT]

Dsteppa

Senior Member
May 7, 2012
1,912
452
@[NUT]
did you read my reply ??
ja we hebben dat wat je laatst vroeg man.
reageer ff :)

Let the guy R.I.P Geez!:p
Ik heb ook wat problemen:
http://imgur.com/5YJFZAu

I read this page where the guy seemed to have almost similar problems, but my device doesn't restart or anything.
http://xdaforums.com/showthread.php?t=2261606&page=4

I've manually installed SuperSu (From CF), but that just said that the binaries can't be found.

I tried the latest FW and .244 both completely stock and fresh installs with full wipe, but both of them gave me the same message.
Also tried an older version of the recovery (Because I know that it worked for me last year), but same problem...
 
Last edited:

[NUT]

Senior Member
@[NUT]
did you read my reply ??
ja we hebben dat wat je laatst vroeg man.
reageer ff :)

Ik heb het gelezen ;)

Can you do a feature request on DevDB? Just to make sure I don't forget... I'm kinda busy with my update-to thread for a fully rooted JB4.3 Z1 without loss of data...

Everyone can do the same from now on, report the following info for me please:
  • CM device name
  • CM device repo link (and what CM version it exists on)
  • Device resolution (not as '720p' but as '1280x800')
  • If /system/bin/chargemon exists
  • If /system/bin/sa77_recovery exists

Incomplete requests will get put on the last position of the to-do list, so make sure you post all the required info.

Let the guy R.I.P Geez!:p
Ik heb ook wat problemen:
http://imgur.com/5YJFZAu

I read this page where the guy seemed to have almost similar problems, but my device doesn't restart or anything.
http://xdaforums.com/showthread.php?t=2261606&page=4

I've manually installed SuperSu (From CF), but that just said that the binaries can't be found.

I tried the latest FW and .244 both completely stock and fresh installs with full wipe, but both of them gave me the same message.
Also tried an older version of the recovery (Because I know that it worked for me last year), but same problem...

You are missing a symlink to the su binary... I'll change the installer to use the (SuperSU default) /system/xbin/su binary for the next release.

For now, open android terminal and type:
Code:
su
ln -s /system/xbin/su /system/bin/sh

After which the installer should start to work just fine.
 
  • Like
Reactions: Dsteppa

[NUT]

Senior Member
Doesn't seem to work either:confused:
http://imgur.com/ZRb6ArJ

Tenzij ik iets verkeerd doe

Are you sure you are rooted? :confused:

Type the following if you think you are:

(stop at the first one that does not work)

Code:
/system/xbin/su
export PATH="/system/xbin:/system/bin:$PATH"
su

If you had to stop at some point and you still have recovery (but you wanted to update to the latest) flash the latest SuperSU or re-root your phone...
 
  • Like
Reactions: Dsteppa

[NUT]

Senior Member
Hi Nut. I would like to report that the now pressing the volume up button I am entering into Philz recovery but for some reason the backlight of the phone is kit working on Philz recovery. I mean the phone's backlight does not work and it does on TWRP

Sent from my C6903 using XDA Premium 4 mobile app

Hmm funny, I know it's kinda dark, it was for me on my Z1, but usable... in a dark room, are you able to see anything? If so, navigate to PhilZ Touch settings and change the backlight value to max. It will still be a bit dark though.

Please report this issue to Phil3759 in his device support thread. Make sure you let him know you are using XZDualRecovery for locked bootloaders.

The new Z1 and Z Ultra XZDR builds have this device specific build now, previously I had modified the Xperia Z recovery patched up to work on the Z1 and Z Ultra.
 

Dsteppa

Senior Member
May 7, 2012
1,912
452
Are you sure you are rooted? :confused:

Type the following if you think you are:

(stop at the first one that does not work)

Code:
/system/xbin/su
export PATH="/system/xbin:/system/bin:$PATH"
su

If you had to stop at some point and you still have recovery (but you wanted to update to the latest) flash the latest SuperSU or re-root your phone...

I'm a blonde f*cking noob....
Forgot that I needed root... since it was like 6 months ago that I did this...
Could you please add that in the notes please:p That you need to have root to make this work.

Thanks for the effort.
 
Last edited:
  • Like
Reactions: CiscoX and [NUT]
Let the guy R.I.P Geez!:p
Ik heb ook wat problemen:
http://imgur.com/5YJFZAu

I read this page where the guy seemed to have almost similar problems, but my device doesn't restart or anything.
http://xdaforums.com/showthread.php?t=2261606&page=4

I've manually installed SuperSu (From CF), but that just said that the binaries can't be found.

I tried the latest FW and .244 both completely stock and fresh installs with full wipe, but both of them gave me the same message.
Also tried an older version of the recovery (Because I know that it worked for me last year), but same problem...
@Dsteppa
hahaha hoor deze :p
oohwee that s*cks you have that kind of sh*tty problems
and also to bad to hear also a DUtCh friend !

Ik heb het gelezen ;)

Can you do a feature request on DevDB? Just to make sure I don't forget... I'm kinda busy with my update-to thread for a fully rooted JB4.3 Z1 without loss of data...

Everyone can do the same from now on, report the following info for me please:
  • CM device name
  • CM device repo link (and what CM version it exists on)
  • Device resolution (not as '720p' but as '1280x800')
  • If /system/bin/chargemon exists
  • If /system/bin/sa77_recovery exists

Incomplete requests will get put on the last position of the to-do list, so make sure you post all the required info.



You are missing a symlink to the su binary... I'll change the installer to use the (SuperSU default) /system/xbin/su binary for the next release.

For now, open android terminal and type:
Code:
su
ln -s /system/xbin/su /system/bin/sh

After which the installer should start to work just fine.

@[NUT]
ok is cool homez :D
hmm ok and that should work for our XP JB 4.1.2 users or we just need to test?
Btw i bought almost an Xperia SP :)
But i still had not my money on tha bank... Lame :( :crying:
Next time better :D
* sorry that was kinda OT
 

[NUT]

Senior Member
[XZDualRecovery] 2.7.75 BETA released!

BETA Change log:
BETA releases will only appear on http://nut.xperia-files.com and the DevDB thread and as soon as enough people report it to be working fine will it move in to the Q&A thread as a RELEASE version.
Version 2.7.75:
  • Now including NDRUtils in the installation packages. Whenever the app is updated, Play should do that for you.
  • Updated the mr script, debugged by @Tungstwenty, it is now confirmed working.

Enjoy :)
 
  • Like
Reactions: nimo9 and Bird40

scoobydu

Senior Member
May 16, 2005
480
44
Is there anything special to run the linux script on mac os mavericks?

I'm getting;

mac-mini-2012: local$ /Users/local/install.sh
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?

Its being executed from my local folder on my ssd.

Trying to install on 4.2.2 on both the Tab and Ultra, both rooted.
 

[NUT]

Senior Member
Is there anything special to run the linux script on mac os mavericks?

I'm getting;



Its being executed from my local folder on my ssd.

Trying to install on 4.2.2 on both the Tab and Ultra, both rooted.

It needs to be unpacked on to a folder which has the Unix file permissions and user ownership file attributes set. Otherwise sudo won't know if you may run it AFAIK.
 

bogdan wst

Senior Member
Nov 22, 2009
292
47
BETA Change log:

Version 2.7.75:
  • Now including NDRUtils in the installation packages. Whenever the app is updated, Play should do that for you.
  • Updated the mr script, debugged by @Tungstwenty, it is now confirmed working.

Enjoy :)

Just in case someone needs to restore a backup made in TWRP/Philz - 2.7.74 version ... will this backup be able to be restored with the new 2.7.75 version of recovery ?



Sent from my C6903 using XDA Premium 4 mobile app
 

scoobydu

Senior Member
May 16, 2005
480
44
Ok thanks.

Its strange as they seem fine and as the other files in the directory; read/write by me and read only by staff.

Does the script need root on the mac or linux, or can it just be ran as a user, as I am assuming.
 

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.