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

Search This thread
By:
Advanced…
johan8

johan8

Senior Member
Nov 16, 2010
389
20
timberwolf60 said:
If I facing such a reboot problems. The easiest way is downgraded to 534, rooted and followed nut on the 4.3 xzrecovery thread. I am sure your problems will disappear.

Send from my C6903 using TapatalkPro
my device: Sony Z1C6903
Samsung I9506
Click to expand...
Click to collapse

I am using XZ C6603.
It will be a problem if downgrade, it will trigger NFC "upgrade" then cause reboot......
I don't want to wipe /data, I haven't do the latest backup....... :(
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
johan8 said:
Yes, I was just using XZ-lockeddualrecovery2.7.77-BETA.flashable.zip nothing else.
Still don't know what cause the reboot.
I have a bad feeling that "chargemon.stock" is corrupted(don't know why), I think I need to flash the rom again.....
I will try it later see if any luck.


And I have studied the script a little bit.
Is it possible to make it more safe by doing these: (little suggestion)
1. kill ric before everything
2. check /storage/sdcard1/xzdualrecovery/chargemonstock - (something like "donotrun") that force copy stock chargemon from microSD to /system/bin/chargemon.stock
Click to expand...
Click to collapse

1: ric isn't running at the time chargemon runs, it's started a few steps in the init process later. The only thing required when it concerns ric is the securityfs implementation on the Xperia Z1 which gets enabled right after the chargemon process runs... But as I said, it's for the Z1 and the XZ does not have this problem (yet?).

2: The problem with that is that the stock chargemon binary can be different between ROM versions. I already check if chargemon.stock exists and if so, the installer and flashable package don't touch it. If chargemon.stock is missing, the flashable package will check if chargemon is a script or a binary, if it's a script it _should_ not copy it to chargemon.stock.

Not sure what I can improve on that...

timberwolf60 said:
If I facing such a reboot problems. The easiest way is downgraded to 534, rooted and followed nut on the 4.3 xzrecovery thread. I am sure your problems will disappear.

Send from my C6903 using TapatalkPro
my device: Sony Z1C6903
Samsung I9506
Click to expand...
Click to collapse

Don't forget (just a FYI, NoFI!) XZDualRecovery is available for 5 different devices, johan8 has an Xperia Z, not a Z1: the installation is different between the Z1 and XZ, the XZ doesn't have the semi-root issues the Z1 has on 4.3...
 
  • Like
Reactions: timberwolf60
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
shteren said:
@Nut there is not thread foe your recoveries so i'll ask here. Itried with both xzdr 2.7.75 and 2.7.77 to backup using twrp to sd card and it told me it cannot access the folder, so I had to backup to internal memory... Older recoveries from you worked just fine. 2.7.71 backed up to sd card.
Btw I can confirm time and date fix for 2.7.77

Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse

Yes there is :D

http://xdaforums.com/showthread.php?t=2261606

Hmm... maybe TWRP simply doesn't need the SELinux fix that PhilZ does require ... I'll check it. Thanks for the report. :good:
 
johan8

johan8

Senior Member
Nov 16, 2010
389
20
[NUT] said:
1: ric isn't running at the time chargemon runs, it's started a few steps in the init process later. The only thing required when it concerns ric is the securityfs implementation on the Xperia Z1 which gets enabled right after the chargemon process runs... But as I said, it's for the Z1 and the XZ does not have this problem (yet?).

2: The problem with that is that the stock chargemon binary can be different between ROM versions. I already check if chargemon.stock exists and if so, the installer and flashable package don't touch it. If chargemon.stock is missing, the flashable package will check if chargemon is a script or a binary, if it's a script it _should_ not copy it to chargemon.stock.

Not sure what I can improve on that...
Click to expand...
Click to collapse

I understand the installation script won't overlap chargemon(script) as chargemon.stock.
And I won't change any of your scripts.
Just that don't know what cause the reboot, and no Red LED..... looks like chargemon.stock won't run.

What I did was:
- Boot into recovery (it was 2.7.76)
- flash XZ-lockeddualrecovery2.7.77-BETA.flashable.zip
- reboot....
I believe that is not your problem, but something goes wrong in my XZ.

EDIT:-
with "donotrun", I saw Red LED.....then reboot.....
tried downgrade..... but can't boot .....
need to wipe data.....
;(
 
Last edited:
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
shteren said:
No idea! How can I check? Tried a few apps from app store but alas... I have SanDisk 16gb class 4 card, 3 YO!

Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse

The (for me anyway) easiest way is to use the android terminal app. Start it and type the following:

Code: 
su
fdisk -l /dev/block/mmcblk1

It should give you a general ID of the partition type.


yurtseven said:
Hello, i rooted my phone and everything went smooth but after installing few apps i get the message "insufficient space" so now i can`t install any apk`s anymore.
And evertime i restart the phone i get the language and warranty disclaimer menu.
Click to expand...
Click to collapse

Well... Then I suggest you use Settings -> Storage to figure out where the space went... If not all is accounted for, use a root explorer to check the contents of /data/media to see if your backups done to internal storage are stored on a wrong location.

Besides this check, FYI: internal storage and the app storage are on the same partition, so if you have a lot of (or just large) backups or a lot of music this will also eat up app storage space.
 
S

shteren

Senior Member
Jul 9, 2013
588
109
[NUT] said:
Hmmph... That's strange. Are you sure there is enough space left on your sdcard to make the backups? Generally it takes about 1Gb of extra free space before twrp and Philz will allow a new backup to be created...
Click to expand...
Click to collapse

Yep. I have 6 gb... Wait, i'll try again and give you exact output

Sent from my C6903 using Tapatalk
@Nut this is the output

E: unable to create folder: external_sd/TWRP/BACKUPS/BH90L...
E: failed to maek backup folder.

now i've went in file browser in TWRP and this is the right path...
 
Last edited:
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
shteren said:
Yep. I have 6 gb... Wait, i'll try again and give you exact output

Sent from my C6903 using Tapatalk
@Nut this is the output

E: unable to create folder: external_sd/TWRP/BACKUPS/BH90L...
E: failed to maek backup folder.

now i've went in file browser in TWRP and this is the right path...
Click to expand...
Click to collapse

Hmm... this starts to sound like a maximum for FAT32 has been reached ...

Are you able to empty and reformat the sdcard to try what it does on an empty one? No need to rush it, but please do test that for me.

I'll request the MOD's to move the posts on XZDR to the XZDR thread, so if you come back here and find the posts are gone, be sure to visit the XZDR BETA thread in the Cross Device section :)
 
S

shteren

Senior Member
Jul 9, 2013
588
109
[NUT] said:
Hmm... this starts to sound like a maximum for FAT32 has been reached ...

Are you able to empty and reformat the sdcard to try what it does on an empty one? No need to rush it, but please do test that for me.

I'll request the MOD's to move the posts on XZDR to the XZDR thread, so if you come back here and find the posts are gone, be sure to visit the XZDR BETA thread in the Cross Device section :)
Click to expand...
Click to collapse

lol, hmm i really doubt that, as my card has been almost full in the last month and emptied again... i had 3 backups there and i just deleted them...

and in the past when the card was full it used to tell me the card is full and theres no space... never this error...
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
shteren said:
lol, hmm i really doubt that, as my card has been almost full in the last month and emptied again... i had 3 backups there and i just deleted them...

and in the past when the card was full it used to tell me the card is full and theres no space... never this error...
Click to expand...
Click to collapse

No it's not that, I was talking about the FAT32 file allocation table or number of files registered in it...

It's clear you have more then enough space free, I am suspecting it might be related to some of the limits of FAT32.
 
S

shteren

Senior Member
Jul 9, 2013
588
109
[NUT] said:
No it's not that, I was talking about the FAT32 file allocation table or number of files registered in it...

It's clear you have more then enough space free, I am suspecting it might be related to some of the limits of FAT32.
Click to expand...
Click to collapse

ohhh, ok, so what should i format it to? ext4 should work fine with both aosp and sony stock?

perhaps the card is too old and don't support ext4? i dunno. and we're talking about a full format here so that the file tree is cleared
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
shteren said:
ohhh, ok, so what should i format it to? ext4 should work fine with both aosp and sony stock?

perhaps the card is too old and don't support ext4? i dunno. and we're talking about a full format here so that the file tree is cleared
Click to expand...
Click to collapse

Yes, but you can use the PC for it too, connect it in MSC mode to allow the PC full access to it (this will make it unavailable from your phone while connected to the PC).

From that moment on it's a simple Mass Storage device and you can format it whatever you like. All kinds of formats are supported except NTFS.
 
Celestial Fury

Celestial Fury

Senior Member
Aug 19, 2013
1,000
1,434
Sim City
[NUT] said:
The (for me anyway) easiest way is to use the android terminal app. Start it and type the following:

Code: 
su
fdisk -l /dev/block/mmcblk1

It should give you a general ID of the partition type.
Click to expand...
Click to collapse

Is there another way to check the filesystem type of the SD Card - like using an App with a GUI? I am not comfortable using commands I'm unfamiliar with. I also cannot backup to my external SD Card with >40GB available space.
 
[NUT]

[NUT]

Senior Member
Oct 17, 2012
5,379
10,393
Cyberspace and the Universe
nut.xperia-files.com
Celestial Fury said:
Is there another way to check the filesystem type of the SD Card - like using an App with a GUI? I am not comfortable using commands I'm unfamiliar with. I also cannot backup to my external SD Card with >40GB available space.
Click to expand...
Click to collapse

None with a 100 accuracy... But you can use the pc with your phone connected in MSC mode and then some windows disk or partition tool...

Which recovery are you having this issue on?
 
  • Like
Reactions: Celestial Fury
Celestial Fury

Celestial Fury

Senior Member
Aug 19, 2013
1,000
1,434
Sim City
[NUT] said:
None with a 100 accuracy... But you can use the pc with your phone connected in MSC mode and then some windows disk or partition tool...

Which recovery are you having this issue on?
Click to expand...
Click to collapse

Z1-lockeddualrecovery2.7.76-BETA.installer. It only shows the internal SD Card directory and I can't go up a higher directory to get to the external SD Card or change to it somehow - unless I'm possibly missing an option?

Anyhow, I downloaded Z1-lockeddualrecovery2.7.77-BETA.installer and tried to install using both TWRP and PhilZ Touch by installing zip but both failed. Logs in PM (that last_log.4 refused to be copied! In the end I had to zip it internally before emailing it out). Version in my Sig.
 
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