yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] gamer649:
1) There is no stock recovery on Sony phones, which is why you rebooted into system. And this is why it is important to help devs test their work as they are the ones who provide us with recovery.

2) Choice, you aren't limited to one recovery and therefore aren't limited to learning/using only one recovery. And I'm not too sure about PhilZ, seems like it is just CWM but touch based. Never seen the point in it myself.
[Sony Cross-Device General] Advali:
I have a Z3 and was originally on version 2.8.7 dual recovery, then followed the steps on updating to a new version and flashed version 2.8.12. After that, the green LED just keeps blinking and the phone vibrating and it won't boot. Had to restore back the original chargemon in order to boot. Also had this problem when flashing version 2.8.10.
[Sony Cross-Device General] [NUT]:
:eek:

Why does stuff keep breaking when it worked fine for eons and eons!?

Thanks for the report and the fix, that makes searching for the cause a lot easier :highfive:
[Sony Cross-Device General] [NUT]:
2.8.13 Attempt 3 is now online

Removed chargemon executables, these where still included but are really, really old...

Changed the code for the hijack backup of the stock binary. It will check if the stock file is there and if the chargemon file in system/bin is a binary or a script before moving it away to the backup file. This should prevent a rare situation where chargemon and chargemon.stock end up being a script which is calling itself in every time it tries to end operations, effectively ending up in a bootloop of it's own making.

Removed some smaller redundant stuff, also tried to improve the failed installation detection and made sure some installer errors will stay away when an error is unnecessary.

The Linux/Mac installer now does not use sudo by default anymore. If installation on the Linux/Mac script fails (due to improper udev configuration), execute it using sudo to make it work.
[Sony Cross-Device General] anisingh62:
your recovery is not replacing the stock cyanogen recovery present in CM12.1, so kindly do something to delete the cyanogen recovery or to replace it with your one . Iam on xperia sp and yourrecovery is working fine but it is not replacing it so kindly give me some way or you include this feature to remove cyaNOGEN RECOVERY
[Sony Cross-Device General] [NUT]:
No, you are using the

LOCKED BOOTLOADER

package to replace something which it was NOT MEANT TO REPLACE!

Use the kernel builder to repack the CM12 kernel to replace CWM and include XZDR: http://nut.xperia-files.com/?a=xzdr
[Sony Cross-Device General] Bird40:
2.8.13 Attempt 3 works fine for my SGP521 and C6503.
[Sony Cross-Device General] Bartekreaper:
[Nut] i have problem [emoji14] I have 64gb SD card and recovery not see it. I want to make art permissive but how? I cannot find xzdr.prop. In system/xzdualrecovery arent there, In cache too :( Where is it?

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] anisingh62:
you have not built any kernel for cm12.1 xperia sp
[Sony Cross-Device General] AussieCable:
Installed rooted upgrade package .726 with 2.8.13 Attempt 3 on my D6503, with no discernible issue's.
[Sony Cross-Device General] flipside101:
hence the builder
[Sony Cross-Device General] [NUT]:
Sheez, why do you think it's called a 'builder'? Grab the cm12.1 boot.img, add cm12.1 to the firmware list of the sp, then upload the file to repack it.
[Sony Cross-Device General] v7:
He would need to add the fw in the list

Edit: [MENTION=4904057][NUT][/MENTION] Ninja'd me :D

Tapped from my furious ZR ;)
[Sony Cross-Device General] UncleDan:
Cannot install duel recovery on my Z1.

Hi there.

I have been cut off recovery because I packed a prerooted firmware with the installer zip, instead of the flashable one (please do nont comment:crying:)

The firmware is C6903_14.5.A.0.242_HK.ftf and is perfectly rooted with SuperSU, but obviusly without recovery.

The phone is recognized by the PC either in MTP or MSC mode.

USB debug is on.

I am trying to install the recovery with the installer, but I am stuck at Waiting for Device, connect USB cable now...

==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================

1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit

Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Waiting for Device, connect USB cable now...
=============================================

Any idea would be greatly appreciated.
[Sony Cross-Device General] [NUT]:
Reboot pc, make sure you don't have pc companion or seus/SUS running. Connect the usb lead, Unlock screen of the mobile, have it wait for something to happen. Open a CMD window and cd to the files directory. Then adb shell to the device.

You should get a prompt to accept the fingerprint from your PC. Once you have, you should be able to install xzdr after that.
[Sony Cross-Device General] luminoso:
tested 2.8.13 Attempt 3 with Z3C over 2.8.10 using installer in windows: everything OK!
[Sony Cross-Device General] SB13X:
[MENTION=4904057][NUT][/MENTION] What issues if any would installing the latest Busybox cause with Recovery. Someone claiming installing the latest version resolves issues with Xposed and looking at testing but wanted to check with you first because he says it broke Recovery for him.
[Sony Cross-Device General] anisingh62:
Please also tell me in some detail that what will happen afyer doing that please just a brief description.
[Sony Cross-Device General] gamer649:
Updating busybox always breaks recovery. [MENTION=4904057][NUT][/MENTION] please correct me if I'm wrong because this is hearsay. But I've heard that the busybox [NUT] uses for the dual recovery is a specially adapted version.

Take a look at the thread I'm going to link you to for a possible xposed fix.

http://xdaforums.com/showthread.php?p=60268402
[Sony Cross-Device General] v7:
Busybox https://play.google.com/store/apps/details?id=me.timos.busyboxonrails&hl=en

This busybox installer is compaitable with DualRecovery.Tested on Xperia ZR 4.4.4 XZDR 2.8.12.

Tapped from my furious ZR ;)
[Sony Cross-Device General] [NUT]:
I'm currently using the busybox from a CM12 repository, it's not the latest, but it is bionic aware (which means it uses Android's way of things to do instead of the linux way of things to do).

'The latest version' can mean many things, because there are a multitude of versions around. I'd like to know where to find the sources for that 'latest version' when/if it's adapted for use with Android/Bionic. (to see if it is, use that busybox to ping any host online, if it's not capable of producing an IP from a host and is unable to ping a straight IP, it's built with Libgc (which is linux' main core).

Good stuff, nice to know :)

--- RELATED ---

I am actually working on a solution for this, but I wanted to clear out any remaining issues before I did, otherwise it would get very confusing, very fast and possibly spiral out of control down a pit of snakes I wouldn't be able to pull it up from... :eek:

The change is to move my busybox to the .XZDualRecovery folder, creating an operating environment there instead of relying on system/bin and system/xbin. This will mean quite a big change, so I hope to do it soon, but also hope to avoid any big issues.
[Sony Cross-Device General] [NUT]:
Why not just try and see? I honestly don't know why you are so anxious to try...

Basically it rips apart the CM boot image, grabs the base ramdisk, throws away the CWM/Recovery ramdisk, modifies the init to include the key checking ability and repacks the lot including XZDR's recoveries, then creates a flashable zip from the boot image. You can flash it straight from CWM on the running kernel, reboot and you will have the same kernel with XZDR's recoveries included instead of CM's own recovery.
[Sony Cross-Device General] shoey63:
And if it's no good, simply flash the original cm boot.img again, no harm done. That's the beauty of having an unlocked bootloader ;)
[Sony Cross-Device General] Bartekreaper:
Can you answer me? :(

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] [NUT]:
Oh, missed that... sorry :o

What type of filesystem is on it?
[Sony Cross-Device General] dron39:
What is right way to update versions? Just to flash new package via recovery? Or i need to edit/set/add/delete something?
[Sony Cross-Device General] [NUT]:
Using just the flashable package should be enough.
[Sony Cross-Device General] russel5:
you are need format this card by phone, not windows

had the same problem few days ago
[Sony Cross-Device General] [NUT]:
I've added a link to [MENTION=6351145]ondrejvaroscak[/MENTION]'s workaround for Xposed on Lollipop to the Frequently Asked Questions section.

It's very clever use of a XZDualRecovery feature, called init.d :cowboy:

Great work buddy :good:
[Sony Cross-Device General] swagie:
[MENTION=4904057][NUT][/MENTION]

I have update my z1 from 2.8.3 to 2.8.10 to 2.8.12 on 4.4.4 rom.

Now I can't mount system in rw mode. Recovery can howewer install.

Can u please help in solving.
[Sony Cross-Device General] [NUT]:
Please install 2.8.13 Attempt 3, it should solve your remount issues.
[Sony Cross-Device General] pedro5148:
someone could send me the link of the version:

Z3C-lockeddualrecovery2.8.3-RELEASE.installer.zip

In http://nut.xperia-files.com/ site it exists no more
[Sony Cross-Device General] ondrejvaroscak:
Compliments to you, without init.d that trick would be very hard if not impossible..
[Sony Cross-Device General] [NUT]:
Install 2.8.12 or 2.8.13 Attempt 3, they will work just as well.
[Sony Cross-Device General] [NUT]:
Well, it's why I built in init.d a LOOOOOOOOONG time ago.

There was a time in the past (waaaaaaay back when the Sony Ericsson ARC was a brand new released phone) when init.d was the only way to hack some functionality in or add functionality to Gingerbread and Ice Cream Sandwich... with Jelly Bean and KitKat the need for init.d vanished a bit because it broke most of the functionality additions which worked fine on GB and ICS.

Good to see it finally found a benefit on Lollipop, validating it's existence :)

I have added init.d support to the kernel version as well (only for STOCK kernels!!), I will be releasing 2.8.13 Attempt 3 as 2.8.14 and that will also be the introduction version of init.d for the kernel builder.

That will enable UB/Kernel users to deploy the same workaround on Xposed issues from that version onwards.
[Sony Cross-Device General] swagie:
Ok thanks.

Solved it with installer on pc. Flashable didn't work thou.

Bedankt man, je bent goed bezig.
[Sony Cross-Device General] [NUT]:
Heh, I decided to discard an edit on my post saying just that. But I figured you would most likely try to install the latest using the installer it would sort itself out ;)

It's weird though, because the flashable is doing exactly the same stuff... I wonder why this happens to some people :eek:

Anyway: Ik doe mijn best ;)
[Sony Cross-Device General] UncleDan:
Thank you for your answer. Unfortunately adb shell tells no device connected (but I see on my computer!!!) and nothing appears either on the phone or on the PC. Is there any way to "force" fingerprint recognition?
[Sony Cross-Device General] [NUT]:
Are you 100% sure you have enabled USB Debugging?

Because if your USB cable is confirmed working OK, that would be the only reason why it doesn't work.
[Sony Cross-Device General] [NUT]:
XZDualRecovery 2.8.14-RELEASE released!

RELEASE Change log:

Version 2.8.14:

Removed some unneeded file inclusions.

Improved the failed installation detection. Some people would get a 'enjoy the recoveries' notification while they where never installed :eek:

Updated the stock binary backup checking routines for chargemon, because in some rare situations it would create a bootloop by replacing the chargemon.stock file with a copy of the hijack script...

Introduced init.d functionality to the XZDR Kernel, I actually forgot to add this ever since I started work on the kernel version :o

Modified TWRP's postrecoveryboot.sh to not throw an error anymore if there is no reason for it to throw it.

Updated the script function DRSET-/GET-PROP to return null instead of false. If a switch was set to false it would add it to the config as if it wasn't there...

Updated TWRP to 2.8.6.0 again (see the changelog for XZDR 2.8.4 for the TWRP changelog).
[Sony Cross-Device General] luminoso:
I confess that I am a lot more curious why when installing busybox 1.23.1 does not require this workaround. Does busybox 1.23.1 defaults to ulimit 2046? hummm
[Sony Cross-Device General] Wolfbreak:
Did you managed to get TWRP 2.8.6.0 fully working?
[Sony Cross-Device General] ondrejvaroscak:
By the way I think you have small microbug in init.sh in part where it test runs init.d scripts to output names into logfiles...

...
else

KEEPBYESELINUX=$(DRGETPROP dr.keep.byeselinux)

# init.d support
if [ "$(DRGETPROP dr.initd.active)" = "true" ]; then

ECHOL "Init.d folder found and execution is enabled!"
ECHOL "It will run the following scripts:"
[COLOR="Red"] [B]run-parts -t [/B]/system/etc/init.d 2>&1 >> ${LOG}[/COLOR]
ECHOL "Executing them in the background now."
nohup run-parts /system/etc/init.d &

else

ECHOL "Init.d execution is disabled."
ECHOL "To enable it, set dr.initd.active to true in XZDR.prop!"

fi

In my opinion should be "run-parts --test"

---------- Post added at 14:51 ---------- Previous post was at 14:48 ----------

Find out by executing ulimit -nS from both adb shell and from android terminal...
[Sony Cross-Device General] [NUT]:
You're right, that's a difference in switches between the old and the new busybox. Thanks for catching that.
[Sony Cross-Device General] [NUT]:
It seems so, as nobody complained about TWRP since 2.8.13 Attempt 3 went online, a few days ago. (no bad news is good news, right?)
[Sony Cross-Device General] coch:
I'm getting the same with 2.8.14. Had to "Swipe to unlock" 4 times to get access. I thought I "swiping it wrong" but then I remember this post from a few days ago.
[Sony Cross-Device General] Bird40:
2.8.14 works fine for my C6503 and SGP521
[Sony Cross-Device General] [NUT]:
I'll see if I can find a solution to this for the next release, which should be the last RELEASE version of 2.8.

Then I will be implementing a change so big it requires a BETA stage as 2.9 before I release it with a RELEASE tag again, which will become 3.0.
[Sony Cross-Device General] UncleDan:
Definitely it was a hardware problem. I did the exact same procedure on my office PC with another cable and it was successful. Thanks.
[Sony Cross-Device General] AussieCable:
Running 2.8.14 on my D6503 and in TWRP if I want to wipe internal storage (/data/media) it seems to be ok, but end with an error:

E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255

I will attach log shortly. Apart from this, everything is just fine.

---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------

Ohh this sounds interesting indeed ;)

Will be interested to see the finished product.
[Sony Cross-Device General] ondrejvaroscak:
Sound thrilling *-:)
[Sony Cross-Device General] prietpraat1972:
xzdr.prop isnt readable (half of it)

Hi [MENTION=410007]Nut[/MENTION],

I'm sure i'm missing something but i noticed that xzdr.prop file on my external sd card is unreadable, that is the first half of it (it is there but in chinese characters), the 2nd half is readable >> byselinux lines. Is there anything i can do to change that? I've tried to use a different encoding type but to no avail.. Any ideas? i wanted to set init.d support to true and try the xposed work around.. ( im on 2814 btw)

Thanks in advance for your answer!
[Sony Cross-Device General] ondrejvaroscak:
Try to create it from scratch in editor..
[Sony Cross-Device General] prietpraat1972:
Sure,

but i dont know what the input is supposed to be.. can you send my a copy of yours? thx in advance..
[Sony Cross-Device General] [NUT]:
Just delete it and reboot, it will be recreated :)
[Sony Cross-Device General] eagle25884:
2.8.14 successfully installed over 2.8.12 without any problems.

Thanks [MENTION=410007]Nut[/MENTION]
[Sony Cross-Device General] [NUT]:
:angel: Guess I made it a little too sensitive then :silly:
[Sony Cross-Device General] AussieCable:
Here is that log!

It should show a couple try's of wiping data and fresh install of prerooted .726 update package however, apart from the error, I can't find any other issue with 2.8.14.
[Sony Cross-Device General] AussieCable:
I find for me this only happens 2 times, on the second swipe it will unlock.
[Sony Cross-Device General] ondrejvaroscak:
Swipe is bit sensitive in twrp, I need to do it slowly :)
[Sony Cross-Device General] PVL_93_RU:
So I suppose installing Xposed still results in boot loops?
[Sony Cross-Device General] [NUT]:
See the faq in post 2
[Sony Cross-Device General] Bananebieger:
Hey all!

Thank you all for your great work. I read the whole thread and saw the development of a working dual recovery for Lollipop in this thread! Just great work!

Hope you can help me, but I think I have the right solution for my problem ;)

I am still on 2.8.3 and used the byeselinux zip to re-enable booting to custom recovery. Do I just install the latest dual recovery to get rid of the mount system problem?
[Sony Cross-Device General] [NUT]:
Well, yes... Why ask a rhetorical question? :p
[Sony Cross-Device General] _mysiak_:
[MENTION=4904057][NUT][/MENTION] - My 64GB FAT32 SD card is not mounted during boot and as such I have to modify /cache files if I want to change some XZDR.prop options. From log it seems that recovery is mounting SD as exFat which is not successful. I could try to modify chargemon.sh script to force mount as FAT, but maybe you have a nicer fix or I missed something :)
[Sony Cross-Device General] [NUT]:
Well, according to the log, fdisk (a linux partitioning tool) says it's a HPFS/NTFS formatted sdcard... which implies exFAT or NTFS. If exFAT isn't working, it should then ignore it as there is no NTFS support on the kernel.

In any case, FAT32 should be working fine, using vfat as filesystem (which supports all fat filesystems excluding exFAT). Put your sdcard in a card reader and connect it to the PC, what does windows think it is?

If it shows it as exFAT or even FAT32, then you might want to make a backup from it's contents on the PC and reformat it on the phone (using the FW's own facilities). Some manufacturers (still!) use a draft version of the exFAT specification, which is not entirely compatible with the final version of the specification. The texfat module included in the Sony FW's does not care about the 'draft' and ignores it. FUSE on the other hand will be able to mount it with a little trick. To keep things simple, I decided a long time ago not to use FUSE.

I work with the KISS principle (Keep It Simple Stupid, for those who don't know it), only complicating things when it needs a straightforward procedure to be able to trace it in the logs... :angel:
[Sony Cross-Device General] ondrejvaroscak:
Be nice :D... some people need little caressing and reassurance :))))
[Sony Cross-Device General] [NUT]:
I was being nice there... I'm allergic to rhetorical questions :p
[Sony Cross-Device General] _mysiak_:
[MENTION=4904057][NUT][/MENTION] - it's FAT32 for sure, I have deliberately formatted it as FAT32, because I had very bad experience with exFat (and most probably in combination with TWRP) in the past - it somehow damaged the file system and then locked the card in read only mode (lost 2x 128gb + 1x 64gb cards already). Fdisk really reports HPFS/NTFS file system :confused:, but Windows sees it correctly as FAT32.
[Sony Cross-Device General] [NUT]:
Well... TWRP in XZDR is using texfat instead of their own exfat support, so don't worry about that with XZDR ;)

I suggest you format it using your phone, you will end up with a FS which works for XZDR 100% of the time.
[Sony Cross-Device General] _mysiak_:
Thanks for the suggestion, but I will not risk exfat again. Will stay with FAT32 and use /cache for XZDR :)
[Sony Cross-Device General] caqo71:
I have a 64gb exFAT factory formated sdxc memory, and i have no issues with it. It mounts ok.

Enviado desde mi D6603 mediante Tapatalk
[Sony Cross-Device General] _mysiak_:
Well, 64gb exfat worked for about 2 years, until I switched from CWM to TWRP. Then I had 128gb for few months and another 128gb died within 2 days. Switched back to 64gb few months ago, but this time with FAT32. So far everything works fine. Maybe it was a big coincidence (it always happened with TWRP though), or some kind of incompatibility or.. In each case, I do not have enough faith in exfat and TWRP anymore :)
[Sony Cross-Device General] myeepad:
I have a Samsung 128GB for over a year and using it on TWRP as long as I have it. The only problem that I had is it won't work well with the Windows' format utility and I have been using SDFormatter to format all my SD / MicroSD cards. It works very well.
[Sony Cross-Device General] AussieCable:
I did learn a lesson very quickly after destroying an SD card. It was my own fault, mainly because I did not understand the significance of using only the phones OS format facility, where it uses the correct file system.

What I did to destroy my first 64GB card was to use Windows to format it then use it in my phone. I am sure one of the recoveries was the last straw before that SD card died.

Now what I have done is format on the phone OS ONLY, and have never had any issue with my 128GB SD card ever. I never intend to ever use Windows again to format my SD cards, and ONLY use my phones format facility.

In fact, I dont ever remove the SD card either as USB is fast enough to transfer files.

I would strongly recommend that everyone

never

format using Windows! ONLY use your phone's format facility, and

never

remove your SD card and use it in Windows, use USB to transfer files, it is fast enough.
[Sony Cross-Device General] ondrejvaroscak:
While your recommendation is correct, there is no chance that it was Windows that destroy the card. Using Windows formatting capability is not recommended but it doesn't destroy the card.
[Sony Cross-Device General] AussieCable:
Never said it was Windows that destroyed the SD Card. Re-read my post :good:
[Sony Cross-Device General] ondrejvaroscak:
More probable is that is was already bad from production and got killed by excessive writes...
[Sony Cross-Device General] Bananebieger:
I actually wanted an answer to my question ;) just wasn't sure if I can use it due some users modified prop files, selinux States, scripts and so on to get rid of the problem.

But now I know what to do.

Thanks again :)
[Sony Cross-Device General] NHOman14:
Help :(

Hi sir why am i having an error in installing XZ-lockeddualrecovery2.8.14-RELEASE.installer

i have a rooted xz c6603..
[Sony Cross-Device General] AussieCable:
Would you happen to be running an application on your PC called 'BlueStacks'?

Shut it down (BlueStacks) and retry XZDR.
[Sony Cross-Device General] NHOman14:
Thanks, ill try ☺
[Sony Cross-Device General] Sun24664:
Not working on D5322. :(

Lollipop ? version 19.3.A.0.470
[Sony Cross-Device General] pvnsai73:
Serious bug- xz dual recovery is no more working on Xperia t2 ultra dual lollipop in boot red light is indicating instead of green light

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

[Nut] serious bug-its no more working on t2ultra dual lollipop 19.3.A.0.470 its indicating red light instead of green light and its not gng to recovery
[Sony Cross-Device General] Andrey Piekas:
Which logs you need, because the T2 Ultra is not working in 5.0.2!

After installation, direct start the system.
[Sony Cross-Device General] prog666:
How to Root C6833 on Lollipop 14-5-a-0-242-5-0-2