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

Search This thread
By:
Advanced…
Traxx67

Traxx67

Senior Member
Dec 4, 2007
169
8
In The Air
OnePlus 8 Pro
Hello,

i have flash the new recovery, but now i have 2 recovery, the 2.5 and the 2.6.
The 2.5 is coming when i press volume button and the led is purple, and the 2.6 is coming when the led is green...

Why????
Thank you
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
Hen Ry

Hen Ry

Senior Member
Oct 21, 2012
679
368
Saxony
Samsung Galaxy S23 Ultra
Teo032 said:
Ahh so that's how things are with this phone. Thanks for explaining, so much clearer now... totally did not noticed the difference in led... I was reading the instructions where it says to press it with the green led. But I thought "oh my led color is different... probably because I have the 6602.." Never noticed the green lol so i clicked it at the first led color.. fail

Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse

I have edited the DoomKernel v9, may I offer it here upload
 
D

donottouch

Guest
Anyone have a problem entering CWM?

I have green light than vol-up makes it purple then a few sec it has no led notification at all,and my phone stuck on black screen.... have to reboot power + vol up for 10 sec....

TWRP works fine. I have locked BL and have no intention to unlock it....

Thanks
 
G

guhvanoh

Senior Member
Dec 5, 2010
1,527
566
Slightly South of London
sites.google.com
donottouch said:
Anyone have a problem entering CWM?

I have green light than vol-up makes it purple then a few sec it has no led notification at all,and my phone stuck on black screen.... have to reboot power + vol up for 10 sec....

TWRP works fine. I have locked BL and have no intention to unlock it....

Thanks
Click to expand...
Click to collapse

Yes, but only on my tablet. My fone is fine.
FYI, TWRP is still in landscape mode for tablets and not fixed yet.

Sent from my SGP311 using xda app-developers app
 
D

donottouch

Guest
It did not make any logs at all so no way to find why.


Sent from my C6603 using Tapatalk 2
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
guhvanoh said:
Yes, but only on my tablet. My fone is fine.
FYI, TWRP is still in landscape mode for tablets and not fixed yet.

Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse

Thats correct, i never updated the TabZ thread because of that. There really is no worthy change there. I'm working on a solution to that by having a multi device package to keep the installation equal and simple and have XZDualRecovery make the choices what to use.

It's a feature destined to get introduced in version 3 of XZDualRecovery.
 
  • Like
Reactions: sweets55 and guhvanoh
M

mervluk

Senior Member
Jan 30, 2013
272
79
Stupid newbie here.

All dandy on original (rooted but locked bootloader) stock 350. Foolishly after needing to reflash to stock 423 (rooted again but still with locked bootloader) after a defective install, I decided to have a go again at reinstall. All OK until mkdir fails for sd card1 (external card). Phone starts rebooting as indicated by the install log but is now dead - for over 1 hour. Can't access the logs. There does seem to be something wrong with the SD card as the PC too says "read only" despite the phone being able to write to it, well sometimes at least. SuperSU installed, and right .bat used, permission granted, and USB debugging on.

Is my only recourse now another SUS reflash, and start over?

Update: disconnect, hard switch off holding start/volume keys, starts reboot then tried entering CWM by holding volume up key, purple light then again . . . nothing. So I guess its a defective install . . .

Update 2: managed a normal reboot. Only logs are - nothing in cache -
/tmp/XZDualRecovery: stops at starting stage 2
/storage/sdcard1/XZDualRecovery load of gibberish with load of white question marks inside black triangles.That has a date of 31.12.79, but another file log.old is legible with today's date/install time and finishes with:
Executing recover init, have fun!
Tried creating the donotrun file but root explorer just crashes. A dodgy SD card?

If I'm minded to have another go (which I'm not yet, twice bitten) presumably I should remove the external card first???? Will that work and solve the problem if it'll write to internal memory instead?
 
Last edited:
M

mervluk

Senior Member
Jan 30, 2013
272
79
[NUT] said:
@mervluk

Maybe it's better to make a backup of your sdcard1 content and then reformatting it using your pc. It sounds to me it might have some corruption...

Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse

Think it's defective then, as already re-formatted. Looks as though I can move songs/pictures to it OK, but for anything else trying to write to it - it's hopeless. But would removing it before trying to install solve it - would XZDualRecovery then write/work off the internal SD? It'd be lost on an upgrade presumably, but that's the lesser problem.
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
mervluk said:
Think it's defective then, as already re-formatted. Looks as though I can move songs/pictures to it OK, but for anything else trying to write to it - it's hopeless. But would removing it before trying to install solve it - would XZDualRecovery then write/work off the internal SD? It'd be lost on an upgrade presumably, but that's the lesser problem.
Click to expand...
Click to collapse

Actually, it tries to use your sdcard every boot, so that would only help if you remove it every single time...

What filesystem are you using on the sdcard?
 
M

mervluk

Senior Member
Jan 30, 2013
272
79
[NUT] said:
Actually, it tries to use your sdcard every boot, so that would only help if you remove it every single time...

What filesystem are you using on the sdcard?
Click to expand...
Click to collapse

FAT32, rather than ex-FAT32 according to the PC. The PC can't do anything with the card, saying it's write protected.

So after re-installing, presumably, without the SD card; I'd just need to remove the SD card before each reboot, and re-insert it afterwards? Each time, or only when I want to boot into recovery - as after a delay it seems to reboot normally at the moment? (Only problem may be when the phone occasionally reboots of its own accord).

I'll replace the SD card eventually with a better quality version (obviously), but not yet due to financial constraints.
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
mervluk said:
FAT32, rather than ex-FAT32 according to the PC. The PC can't do anything with the card, saying it's write protected.

So after re-installing, presumably, without the SD card; I'd just need to remove the SD card before each reboot, and re-insert it afterwards? Each time, or only when I want to boot into recovery - as after a delay it seems to reboot normally at the moment? (Only problem may be when the phone occasionally reboots of its own accord).

I'll replace the SD card eventually with a better quality version (obviously), but not yet due to financial constraints.
Click to expand...
Click to collapse

The best option you have is to create a backup of the sdcard and reformat it using the phone. My guess is that it does hold a partial exfat and it might be confusing your pc and XZDualRecovery, as it probably mounts it as exfat loading the modules as it does the preparation before starting the stage 2 file.

Sent from my C6603 using xda app-developers app
 
G

godjak

Member
Dec 3, 2010
31
0
Xperia Z is not booting in CWM!?

Hi everybody,
i've just installed the DualRecovery on my Xperia Z (locked,unbranded,.253 4.1.2,rooted with DoomLoard ERT),i followed the instructions for installation,Debbugging is ON i have installed SuperSU ,so i chosed supersu.bat for installation.Everything works just fine until the reboot.By the guide it seems that after the reboot the phone must enter automaticaly in CWM recovery,than i must reboot to system so the installation can complete.
But after the reboot the XZ stays with turned on black/blank screen and is not doing anything,the CMD stays on the line waiting the phone to reconnect to finish the process.I wait and i wait and after a while still connected i rebooted the phone.It booted normaly,everything seems to be ok ,and the CMD process said that installation is completed successfully.I tried several times to enter the CWM mode but i'm always getting this blank screen,but in fact i can enter in TWRP and i execute reboot to system from within.
So my question is ,what did i do wrong or how should i proceed from now to get this dual recovery working as it should.
Please give me some advices or guidelines.
10x in advance

Regards
godjak
 
Last edited:
U

ulakala

Senior Member
Apr 11, 2008
133
5
non enter recovery mode

sorry for my bad English ....
I can not get into recovery mode
I have stock fw 4.2.2
use SUPERSU
when I turn on xperia z does not turn on the green LED (only RED LED) does not go into recovery mode.
the first time it worked fine then nothing

What can I do?
 
Last edited:
YudiA1

YudiA1

Senior Member
Mar 30, 2013
101
27
jakarta
ulakala said:
sorry for my bad English ....
I can not get into recovery mode
I have stock fw 4.2.2
use SUPERSU
when I turn on xperia z does not turn on the green LED (only RED LED) does not go into recovery mode.
the first time it worked fine then nothing

What can I do?
Click to expand...
Click to collapse

I ever got that before. Check your busybox. My problem solved when im installing supercharger with busybox 1.19.4.
hope can solve your problem too..

Sent from my C6602 using xda premium
 
Last edited:
  • Like
Reactions: [NUT]
You must log in or register to reply here.

Similar threads

IgorEisberg
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.7.0]
Replies
3K
Views
3M
IgorEisberg
IgorEisberg
X
(PORT) (4.0+) (All Devices) (PS4 Remote Play Port)
Replies
2K
Views
1M
U
Unlinked
A
[TOOL] [UPDATE 04/09/2015] Flashtool version 0.9.19.10 - Windows / Linux / Mac
Replies
4K
Views
5M
Z
zdob
zxz0O0
Easy Root Tool for various Xperia devices
Replies
2K
Views
1M
L
lawrenceh
olokos
Unlock all bands of your Qualcomm device! Use your phone globally! No bs!
Replies
2K
Views
1M
Shahnewaz
Shahnewaz

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 691
    [NUT]
    [NUT]
    -=[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
    View
    250
    zxz0O0
    zxz0O0
    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
    View
    136
    [NUT]
    [NUT]
    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
    jdjta said:
    [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]
    Click to expand...
    Click to collapse

    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.
    View
    123
    [NUT]
    [NUT]
    Change log

    RELEASE Change log:

    http://nut.xperia-files.com/html/xzdualrecovery-change-log.html
    View
    122
    [NUT]
    [NUT]
    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.
    View

New posts