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

Search This thread

Lemmi1

Senior Member
Can someone check if the md5 checksumm is ok?

I just downloaded the versions of xperia zr new several times and I always get a wrong checksum.

I wondert why rooting and installing of dualrecovery gets wrong and now I checked md5 checksum with MD5Checker and I get a wrong number. Maybe this is the reason.

I rooted with dualrecovery for xperia zr my smartphone well before and now, when wanted to go to Android 5.1 it wont work. I get back to Android 4.4.2 with flashtool and want to root it like before, but it says wrong adb files or so. So right now I dont have root anymore.

I will root und install dualrecovery under windows 10, but I dont think this is the reason for fail. Tried same on laptop of my wife under windows 7 and same probleme there.
 
Last edited:

theduke7

Senior Member
Apr 8, 2011
1,631
1,124
Cairo
Samsung Galaxy A23
Thanks for the info. i had made my own pre-rooted firmware including recovery to keep the recovery.

I have NOT ODEXED my device. DSPmamager was the last mod i flashed and it works perfectly. 7 days later i enterd recovery mode and it still works but few weeks later recovery mode stopped working and my phone is having problem for no reason.

well' i don't know if Z3 have the same recovery issues as The XZ , looking at the logs you attached there're 3 log files (and other non-log files), 2 of the logs only contain data and the 3rd is empty, the 1st file shows normal behavior of you installing the dsp mod , it mounted and unmounted normaly ...
also the 2nd file showing you making a backup and also it mounted and unmounted normally ... so no error appear on those logs.
when you 1st posted i thought you had XZ (my mistake) so i advised based on that, but now i know its a Z3C , and with what you're describing on the last post it appears that our recovery Issues are different , the issue we're facing that the recovery is unable to mount system therefore unable to flash, from what you're saying you're issue is not being able to enter recovery? am i right?
to know what problem the recovery has i need to know what the problem is
& a log that shows the problem. anyways, if you're unable to access recovery my only suggestion is to install the official recovery (download it from the OP) for your device (install the installable package from computer) , on [NUT] website there's a specific version for your device . try to mount and unmount or flash or back up things and if there is an issue create a log and share that... you can also try to uninstall the recovery before installing it again (check the OP) .

regarding the app optimization,( i'll explain it simply), Odex is the default state, which means the apps on your device are packaged in a specific way the requires 2 files tje apk file and an odex file that exists on a folder named "arm" with the apk, so you're already odex unless you Deodexed your rom before flashing it, and if only you used prfcreator to get a rooted rom with recovery , you have a odex rom , Now, the mods have Deodexed app, which are unpckaged and require only the apk to run, some mod creators add a script to there mod to delete the arm folder, but from reading your log file , the dsp mod doesn't do that it only extracts files, so you need to know (ask the developer of that mod) which original files his mod replaces with a deodexes apk .
From your log this doesn't seem to be the case < the mod didn't replace any apk that i can see but it did replace some other files shown below
Code:
mounting system
 
updating system files
minzip: Extracted file "/system/app/DSPManager.apk"
minzip: Extracted file "/system/etc/audio_effects.conf"
minzip: Extracted file "/system/etc/audio_policy.conf"
minzip: Extracted file "/system/lib/soundfx/libaudiopreprocessing.so"
minzip: Extracted file "/system/lib/soundfx/libbundlewrapper.so"
minzip: Extracted file "/system/lib/soundfx/libcyanogen-dsp.so"
minzip: Extracted file "/system/lib/soundfx/libdownmix.so"
minzip: Extracted file "/system/lib/soundfx/libreverbwrapper.so"
minzip: Extracted file "/system/lib/soundfx/libvisualizer.so"
minzip: Extracted file "/system/vendor/etc/audio_effects.conf"
 
unmounting system
 
Done!
also shown on the log that this mod is originally for Jelly beans not Lollipop (i don't know if it was updated) , so the files it replaces although might work will be different from the LP ones, and this might be whats is causing the issue, if you're sure it's not, all you need is still get recovery working and clear Delvik.

---------- Post added at 12:40 PM ---------- Previous post was at 12:36 PM ----------

Can someone check if the md5 checksumm is ok?

I just downloaded the versions of xperia zr new several times and I always get a wrong checksum.

I wondert why rooting and installing of dualrecovery gets wrong and now I checked md5 checksum with MD5Checker and I get a wrong number. Maybe this is the reason.

I rooted with dualrecovery for xperia zr my smartphone well before and now, when wanted to go to Android 5.1 it wont work. I get back to Android 4.4.2 with flashtool and want to root it like before, but it says wrong adb files or so. So right now I dont have root anymore.

I will root und install dualrecovery under windows 10, but I dont think this is the reason for fail. Tried same on laptop of my wife under windows 7 and same probleme there.

for ZR on LP 5.1.1 you need to implement the fix on this post Or wait for an updated Official version.

---------- Post added at 12:43 PM ---------- Previous post was at 12:40 PM ----------

Hard to say what was going wrong without any logs.
If it happens the next time, please provide the logfiles mentioned int the first post

well m8, he actually provided some logs Here :)
but i can't see any problem in them, you could check them, you're surely better than me on this .
 
  • Like
Reactions: McBane87

McBane87

Senior Member
Jun 29, 2012
292
259
well m8, he actually provided some logs Here :)
but i can't see any problem in them, you could check them, you're surely better than me on this .

Ah, Sorry.
Well, first Stage (preperation.log) looks OK except this:
Code:
10:17:51 >> insmod /system/lib/modules/nls_utf8.ko
insmod: can't read '/system/lib/modules/nls_utf8.ko': No such file or directory
10:17:51 >> RET=1
This is a Module, which is providing "Native Language Support (UTF8)". I'm not sure this is causing some trouble. But I think not. And then the Log is saying that it will now start Stage2 (XZDualRecovery.log) by executing init.sh (=dualrecovery.sh) , but those logs are empty. So maybe dualrecovery.sh was missing?
 
  • Like
Reactions: theduke7

theduke7

Senior Member
Apr 8, 2011
1,631
1,124
Cairo
Samsung Galaxy A23
Ah, Sorry.
Well, first Stage (preperation.log) looks OK except this:
Code:
10:17:51 >> insmod /system/lib/modules/nls_utf8.ko
insmod: can't read '/system/lib/modules/nls_utf8.ko': No such file or directory
10:17:51 >> RET=1
This is a Module, which is providing "Native Language Support (UTF8)". I'm not sure this is causing some trouble. But I think not. And then the Log is saying that it will now start Stage2 (XZDualRecovery.log) by executing init.sh (=dualrecovery.sh) , but those logs are empty. So maybe dualrecovery.sh was missing?

that's why i thought maybe if he re installed the recovery it might fix it, or at least show what's wrong...
 

gegu2

Member
Dec 25, 2014
27
13
Code:
10:17:51 >> insmod /system/lib/modules/nls_utf8.ko
insmod: can't read '/system/lib/modules/nls_utf8.ko': No such file or directory
10:17:51 >> RET=1
Above lines indicate that ntfs partition can't be mounted due to missing nls_utf8 module. Please see the first message at 10:17:51 available in preparation.log. It states that sdcard1 is ntfs type. Later in the same log file we can observe that exfat partition on sdcard1 was mounted. So the question is how the sd card is partitioned.


---edit---
I've checked last_log log files attached in recovery folder and i've found that once 32GB card with vfat was recognised (was used/present in phone and once there was 64GB card with exfat, so the answer for my question can help to solve the issue.

Sent from my D5803 using XDA Free mobile app
 
Last edited:

Lemmi1

Senior Member
Think I will wait till the fix is in the dualrecovery file for Xperia ZR. Dont know how to implement the fix myself.

Checksum now works. Used wrong tool to check ist. I used md5 instead of sha.

Right now I am without root and recovery on my Xperia ZR on Android 5.1.1 and hope that you may fix it ;)

But one small question. I was on Android 4.4.2 and dualrecovery could not root my XZR. Could the reason be my SD card? I used a 64 GB SD Card from SanDisk and it was split in two partitions cause of using link2sd before under Android 5.0.2. ? I think I read somewhere something about 64 GB SD Cards that could cause problems.
 
Last edited:

Linkinsoldier

Senior Member
Jun 26, 2009
355
52
Munich
In restore menu, make sure only boot, system and data boxes are ticked.

Thank you. What I dont understand: I have the same software and the same recovery running on both phones, but in recovery on my new one I can't find my backup from my old phone. Is there anything I forgot? Backup on the old one to sd card, put SD card into new phone and go to restore + select external storage (nothing there :( ).

Please help me!
 

gegu2

Member
Dec 25, 2014
27
13
@Lemmi1
You may find information that 64 or 128GB cards can cause some problems, but this can happen only if are formated to exfat. I'm using 64GB card divided into two primary partitions. First partition for data (~50GB) is formated to fat32 (vfat) and the second one for link2sd (~6GB) is formated to ext4. All is working fine. Currently i'm on stock KK, but previously i didn't notice any problems related to fat32/sd card with this configuration on stock LP 5.0.2.

Sent from my D5803 using XDA Free mobile app
 

McBane87

Senior Member
Jun 29, 2012
292
259
Thank you. What I dont understand: I have the same software and the same recovery running on both phones, but in recovery on my new one I can't find my backup from my old phone. Is there anything I forgot? Backup on the old one to sd card, put SD card into new phone and go to restore + select external storage (nothing there :( ).

Please help me!

Looks line you used TWRP for Backup?
TWRP is saving its backups in a folder wich is named like the Serialnumber of your phone. So if you want to see the backups of your old phone you have to rename the old Folder with your new serianlnumber.
 

Linkinsoldier

Senior Member
Jun 26, 2009
355
52
Munich
Last edited:

stoff212

Senior Member
Feb 18, 2009
54
5
Can not install, Get this message: adb server didn't ack
Error unknown host service
Device found, but nothing happens
Android 5.0.2 rooted unlocked bootloader Xperia Z.
 

Linkinsoldier

Senior Member
Jun 26, 2009
355
52
Munich
stupid question: After restoring the backup from my old z3c on my replacement z3c I can no longer take pictures with the main camera? It stays black and makes no picture. Front camera is working fine though :(
sound like I am not the only one :(
http://forums.androidcentral.com/as...ct-rear-camera-turn-black-when-i-try-use.html
Any idea? Does anyone know if this is a hardware or a software fault?

Resetting did fix it --> I am giving it another try :(
 

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.