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

Search This thread

[NUT]

Senior Member
I also couldn't boot into both CWM and TWRP, flashed, it shown installation finished, and then the phone reboot, see the Sony logo, and then green led, press the volumn up, nothing happen, same situation when press volumn down to try to boot into TWRP...the green led disappeared so quickly, but fortunately my phone can boot in normal, just couldn't enter both kind of recovery...I tried so many times, so...pls help..


Sent from my C6603 using xda premium

Yeah, better install v1.0 or 1.1 for now. Link to the downloads in the OP.

Sent from my C6603 using xda app-developers app
 
  • Like
Reactions: domingo1702

kaefert

Senior Member
Nov 14, 2007
513
190
Vienna
I've followed the guide for loocked bootloaders and ended up in an extremly short bootloop (only the sony logo, and phone vibrates once about every 0.8 seconds)
Am I the first one this is happeneing to? I didn't find anything when searching this thread for "bootloop"

Now I've managed after playing around to get into fastboot with connected pc, but I'm not sure what to do next. is there somewhere the orignal sony kernel that I could try flashing? I don't think it will allow me to flash a custom kernel, they all say you need unlocked bootloader for a reason... please help, I want to unbrick my phone
 

[NUT]

Senior Member
@kaefert

Just rebooting seems to help you get it kinda working... I honestly do not know why that bootloop occurs on install...

I'm redoing almost everything for the next version, its taking longer then expected though, better install v1.0 until I release the next version.

Look at my signature too for guides on disaster recovery options you have. Press vol-up+power for some seconds to reboot your phone.

Sent from my C6603 using xda app-developers app
 
  • Like
Reactions: kaefert

kaefert

Senior Member
Nov 14, 2007
513
190
Vienna
@kaefert

Just rebooting seems to help you get it kinda working... I honestly do not know why that bootloop occurs on install...

I'm redoing almost everything for the next version, its taking longer then expected though, better install v1.0 until I release the next version.

Look at my signature too for guides on disaster recovery options you have. Press vol-up+power for some seconds to reboot your phone.

Sent from my C6603 using xda app-developers app

hehe, you'd figure that this disaster recovery link is big enough that people would get the idea to follow it themselfs if needed ;) sorry mate, gonna follow that guide now. Thanks for the quick response, and thanks for developing for the Z :)
 

FSN

Senior Member
Mar 14, 2012
166
41
Zurich, Switzerland
I've followed the guide for loocked bootloaders and ended up in an extremly short bootloop (only the sony logo, and phone vibrates once about every 0.8 seconds)
Am I the first one this is happeneing to? I didn't find anything when searching this thread for "bootloop"

Now I've managed after playing around to get into fastboot with connected pc, but I'm not sure what to do next. is there somewhere the orignal sony kernel that I could try flashing? I don't think it will allow me to flash a custom kernel, they all say you need unlocked bootloader for a reason... please help, I want to unbrick my phone
exactely the same happened for me, rebooted phone multiple times, everytime the same error with the continuous vibrating.
 

DickyOhYK

Senior Member
Jan 28, 2012
72
4
singapore
Hi do anymore have chargemon stock rom for Sony xperia Z?? Can send me a link to download??

Sent from my C6603 using xda premium
 

bazz007

Senior Member
Jun 20, 2010
105
21
stuck on boot

Hi, i installed you script everything finished fine but on reboot its stuck on the sony logo with purple led and vibrating? whats happened
 
Last edited:

[NUT]

Senior Member
Hi do anymore have chargemon stock rom for Sony xperia Z?? Can send me a link to download??

Sent from my C6603 using xda premium

Download the installer zip, chargemon.stock is inside the files folder, rename to chargemon, correct permissions to 755 and it should work again. chargemon.stock gets installed by this package as well
inside /system/bin




Hi, i installed you script everything finished fine but on reboot its stuck on the sony logo with purple led and vibrating? whats happened

See link in signature, restore /system only and you won't lose any data.


exactely the same happened for me, rebooted phone multiple times, everytime the same error with the continuous vibrating.

See my previous comment.

Sent from my C6603 using xda app-developers app
 

bazz007

Senior Member
Jun 20, 2010
105
21
sorted

I fixed it using SUS didn't see your post till after so lost everything but at least phone is not dead :) don't think ill be trying again
 

[NUT]

Senior Member
I've figured out why the installer version most likely causes the bootloop!

For ANYONE still in possession of the 1.7 installer, you can still use it but you need to open the installer.bat with notepad and remove the line with

adb shell "su -c /system/bin/reboot"

It is executing this command before run.sh finishes it's work, effectively causing incomplete scripts to be placed in /system/bin. Because of this the bootproces goes into a bootloop as the chargemon process ends without a positive exit code, and init fires it again to make sure it gets the time to start properly... That's causing the vibration every some seconds to refire.

Safest option is not to use it at all if you feel uncomfortable editting scripts.

Sent from my C6603 using xda app-developers app
 
Last edited:
  • Like
Reactions: eagle1977

[NUT]

Senior Member
Version 2.0 BETA - trial version

Running stock kernel during construction, for as far as i can see: all issues have been resolved.

CWM and TWRP work ok for me, the installer reboot issues have been resolved with an adb wait-for-device and then cleaning up :)

You can download 2.0 on http://www.fun-industries.nl/xda/ and test it out :)

A detailed changelog will come when it gets released for real.

Tell me what your experience is when you download and install it now.
 
  • Like
Reactions: eagle1977
Running stock kernel during construction, for as far as i can see: all issues have been resolved.

CWM and TWRP work ok for me, the installer reboot issues have been resolved with an adb wait-for-device and then cleaning up :)

You can download 2.0 on http://www.fun-industries.nl/xda/ and test it out :)

A detailed changelog will come when it gets released for real.

Tell me what your experience is when you download and install it now.

Will this work on unlocked bootloader and running cm10.1 ?
I really miss TWRP. :(
 

alexocean

Member
Jul 25, 2011
19
9
Hi, have tried the new 2.0 version of the lockeddualrecovery and it does the same thing as the 1.7.
Im running into bootloop (purple led with vibrations every 4-5 seconds).Have tried to reflash stock kernel NL with only root (no recovery) to try a fresh install of the dual recovery and the same thing (purple led with vibrations).

Im doing it with the installer.bat
 
  • Like
Reactions: [NUT]

[NUT]

Senior Member
Hi, have tried the new 2.0 version of the lockeddualrecovery and it does the same thing as the 1.7.
Im running into bootloop (purple led with vibrations every 4-5 seconds).Have tried to reflash stock kernel NL with only root (no recovery) to try a fresh install of the dual recovery and the same thing (purple led with vibrations).

Im doing it with the installer.bat

:eek:

I'm actually flabbergasted by this ... that's driving me bonkers, it works just fine for me :crying:

Follow the disaster guide in my signature, restore system _only_ using flashtool and an FTF. You'll get your phone back to working order without losing data or apps.

Once you get it back in working order, please try to send me the logs from either cache or the directory on your external sdcard if you can...
 

alexocean

Member
Jul 25, 2011
19
9
:eek:

I'm actually flabbergasted by this ... that's driving me bonkers, it works just fine for me :crying:

Follow the disaster guide in my signature, restore system _only_ using flashtool and an FTF. You'll get your phone back to working order without losing data or apps.

Once you get it back in working order, please try to send me the logs from either cache or the directory on your external sdcard if you can...

Ummm, have installed ftf complete, then i have installed 2.0 installer for dual recovery (purple led stucks on sony logo with vibrations).Then i have flashed only system and rerooted the phone to access the cache folder.The cache folder contains one folder named "recovery" but it has no files and on the external sd card there is only the clockworkmod folder with an 0 bytes file.

Can you tell me if the logs that you need are on another folder or do i make something wrong?

Have tried to install the 2.0 version with the zip file too (on cwm 6.0.2.8. for locked bootloaders).It gives no errors but when i reboot my phone there is no recovery installed and my cwm 6.0.2.8 does not work until i install it again (there is no green led when on sony logo, only a half second green/red led).
 
  • Like
Reactions: [NUT]

[NUT]

Senior Member
I'll take a look today :)

Sent from my C6603 using xda app-developers app

Thanks :)

I've asked @krabappel2548 to do a code review, I am missing whatever is causing this behavior. I'm hoping a fresh look at things can help solve this mystery...

Need device specific information!

Can people running in to problems please report what firmware version you are running?

Mine is .434 NL Generic. Maybe the problems are caused by a difference there...

To be honest, I'm clutching at straws there, I really have no idea why my dual recovery scripts fail on some phones and works just fine on others (like mine)...
 
Last edited:

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.