yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] costel90:
by chance

Hello NUT! Is there any chance that any of this recoveries work with d2203 like that for t2 ultra for example?
[Sony Cross-Device General] hispanico957:
...Dear NUT... regarding this problem:

i dont's understand: must be in /system/app/NDRUtils which inside NDRUtils.apk or not ?

Thank

Hispa
[Sony Cross-Device General] Linkinsoldier:
Just installed 2.8.12 with Lollipop over pre-rooted zip file: Worked perfectly, however I had to remove the apk again even though I deleted it before flashing... is this a known bug?

thank you very much for your work. It works very good and I am very happy with my new Software on my Xperias. :)

I made a small donation to support your work! Keep up the great work you are doing!
[Sony Cross-Device General] m_k1815:
I installed 2.8.12.works Perfectly on Prerooted Bulid Lolipop 276 and others.Appricate and thanks to NUT
[Sony Cross-Device General] AussieCable:
More Info? Sure.........

If you are running 4.4.4, the NDRUtils.apk will be in /system/app however if you are running lollipop, and the NDRUtils.apk is in /system/app folder, then remove it as there will already be a folder within /system/app called NDRUtils with NDRUtils.apk in that folder.

4.4.4:

/system/app/NDRUtils.apk

Lollipop:

/system/app/NDRUtils.apk <<<--- Remove this one ONLY!

/system/app/NDRUtils/NDRUtils.apk

Oh and if this is incorrect, please do make sure you correct me :good:
[Sony Cross-Device General] [NUT]:
1: euh? Since when is this? Because since 2.8.0 PhilZ has not changed one bit...

2: Yes, that's a bug in TWRP, which should be fixed in 2.8.6.0, but as it has quite a few issues itself, I am waiting for them to be resolved before I update the included TWRP.

Not until XZDR 2.9 BETA.

Hmm... I will have to double check the scripting which installs it...

You're spot on :good:
[Sony Cross-Device General] [NUT]:
Bug identified and fixed. Creating QuickLinks to my downloads should now create working URL's again :)

Example: http://nut.xperia-files.com/?ql=a2f39501a3a5bea544e58ca4215bcbac303198da
[Sony Cross-Device General] Pandemic:
Great job bro [MENTION=4904057][NUT][/MENTION]

Flashed today 2.8.12 on my Z2 with LP 5.0.2 on FW .726 and all works flawlessly ^^

Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
[Sony Cross-Device General] tiunilohmu:
I still have the updating screen when booting up, "optimizing 1 of 1" even deleted "/system/app/NDRUtils.apk"

Anyone still having this updating problem after deleted this "/system/app/NDRUtils.apk"
[Sony Cross-Device General] AussieCable:
I am running 5.0.2, build number .726 with 2.8.12 on a D6503 and I do not have this issue.

Mind you it is only one upgrade message, so it should not take long, have you rebooted once more to see if it has gone?
[Sony Cross-Device General] tiunilohmu:
No, it's every boot. I even did a fresh install, then debloated and installed xposed. Using gravity, apm. And superuser mod.
[Sony Cross-Device General] Wiltron:
Good evening Mr. [MENTION=4904057][NUT][/MENTION]

Installed a different 5.0.2 ROM and all was good! I was rooted, and wrote some files to system to confirm, all was good. I rebooted and updated apps, had access to recovery (2.8.12). I made a nandroid of the first bone-stock non-updated LP install, and then updated it and made some changes to platform.xml to allow write access to external SD, rebooted and it was still great! Made another nandroid of this install.

As soon as I wiped internal storage, and cleared both caches, boot loop. I did not do a permissions fix.

Restoring of either of the two above nandroids didn't rectify the issue. even after wiping everything but external SD before restoring either of the above.

I'm back on KK, and once my battery charges back up, I'll try flashing the 5.0.2 again and see if I can get the above confirmed, and narrow down which cache it is that's buggering it up, or if it's the internal storage being wiped that's causing this.

To recap: I get all the way to the rebuilding of the apps, screen dims as it's "starting applications", and then freezes, reboots.
[Sony Cross-Device General] DennisDD78:
Good day everyone..

I`m installed the lasest version 2.8.12 on my locked Z3, everything works fine, but TWRP version is still 2.8.5.0, not 2.8.6.0 as it listed in title, is it normal ?
[Sony Cross-Device General] v7:
Some apps on 4.4.4 isnt compaitable with the busybox.Can someone give me a busybox installer compaitable with the dualrecovery?

Some of the busybox installer breaks the recovery.

Thanks
[Sony Cross-Device General] costel90:
a date

Would you give me One aproximative date when xzdr 2.9 beta Will come. Thank you
[Sony Cross-Device General] mishrapankaj:
Hi,

I'm having D5833 running stock 5.0.2 unrooted with no custom recovery. Can I flash it with XZDualRecovery 2.8.12 without any issues. Please confirm the steps.

Thanks,

Pankaj
[Sony Cross-Device General] norti:
TWRP 2.8.6.0 has bugs that's why 2.8.5.0 is included in the latest DualRecovery.
[Sony Cross-Device General] monx®:
May I know what is/are the bugs. Ive been using it since 1st released not found any bugs yet.

■ monx® // xperia
[Sony Cross-Device General] norti:
Changelog and read back the posts before that.
[Sony Cross-Device General] monx®:
If i read correctly 'mount & wipe' issue. And not only me doesnt hv the prob. maybe device specific. No issue with Z3 at least.

■ monx® // xperia
[Sony Cross-Device General] [NUT]:
That can very well be the case, as some people where not experiencing any issues, but others where...

I'll be updating twrp in a new testing release soon, to replace 2.8.7 which has some other issues which where solved in 2.8.12, maybe that will solve the twrp issues as well.
[Sony Cross-Device General] Desperanto86:
the same...no problems with TWPR 2.8.6.0 as in kernel on UB (Z2, Z3 Dual) such in system/bin on LB (Z3 Dual)
[Sony Cross-Device General] juanpirulo:
[MENTION=4904057][NUT][/MENTION] Again thanks for your work and replay to our multiple questions, really apreciatted. I tried your workaround and i had this problem.

first i updated the chargemon.sh in the dualrecovery and updated my prerooted zip i just writted like this.

fi
TECHOL "dr.initd.active will be set to false (default)"
DRSETPROP dr.initd.active false
TECHOL "dr.ramdisk.boot will be set to false (default)"
DRSETPROP dr.ramdisk.boot false
if [ -f "/system/bin/ramdisk.stock.cpio.lzma" ]; then
TECHOL "dr.ramdisk.path will /system/bin/ramdisk.stock.cpio.lzma"
DRSETPROP dr.ramdisk.path /system/bin/ramdisk.stock.cpio.lzma
else
TECHOL "dr.ramdisk.path will be empty (default)"
DRSETPROP dr.ramdisk.path
fi
if [ "$ANDROIDVER" = "lollipop" ]; then
DRSETPROP dr.keep.byeselinux false
fi
fi

DRSETPROP dr.keep.byeselinux true

# Initial button setup for existing XZDR.prop files which do not have the input nodes defined.
if [ "$(DRGETPROP dr.pwrkey.node)" = "" -o "$(DRGETPROP dr.pwrkey.node)" = "false[STRIKE]" [/STRIKE]]; then
DRSETPROP dr.pwrkey.node $(pwrkeySearch)

Then I changed in my xzdr.prop the " dr.keep.byeselinux to false" go to twrp wipe system and reflash my preroot with the updated chargemon.

the result was like before i made the changes and with the byeselinux set to false (No modify bootanimation and the log xperia init has stopped appear). Look at the xzdr.prop and dualrecovery writted "DRSETPROP dr.keep.byeselinux true" two times. cheers

I wonder if could be like this. Changing the setversion.sh

where is

if [ "$(DRGETPROP dr.keep.byeselinux)" != "[COLOR="Olive"]true[/COLOR]" ]; then
#echo "Will[COLOR="Olive"] unload [/COLOR]byeselinux every boot"
DRSETPROP dr.keep.byeselinux false
else
DRSETPROP dr.keep.byeselinux true
fi

change it to

if [ "$(DRGETPROP dr.keep.byeselinux)" != "[COLOR="Olive"]false[/COLOR]" ]; then
#echo "Will [COLOR="Olive"]load [/COLOR]byeselinux every boot"
DRSETPROP dr.keep.byeselinux true
fi
]
[Sony Cross-Device General] Jonathan Hew:
I am not sure if this is related to the current releases of DualRecovery or is it related to Lollipop. I have an Xperia Z1 on 5.02 pre-rooted firmware and verified all root access.

1.) I've been having some issues with the recovery missing sometimes, meaning there is no Green or Purple light at boot and i would have to reinstall recovery.

2.) I can't browse my internal SDcard folder when recovery is available, internal SDCard folder shows as empty although it's definitely mounted. When recovery is not available (No Green or Purple light at boot), i am able to see the files in my root folder.

Anyone has any ideas?
[Sony Cross-Device General] AussieCable:
Maybe.............

Do you have other .apk's that are in the /system/app folder without their own folders? If so, you need to create folders for them and place the .apk within that folder.

So for instance (as an example), you have an .apk called CalculatorPlus.apk in /system/app/, then you need to create a folder exactly as the apk name is, then place the apk within that folder:

/system/app/CalculatorPlus/CalculatorPlus.apk

Not:

/system/app/CalculatorPlus.apk

The folder within /system/app must be: rwxr-xr-x (or 0755)

The app then must have these permissions: rw-r--r-- (or 0644)

Reboot and you should be good to go after this. You will probably see the "optimizing x of x", first boot ONLY.

Anyways, I dont see how this would be an issue of XZDR if you do not have any apks out of place.
[Sony Cross-Device General] mnsk:
For this set keep.byeselinux=true in XZDR.prop and reboot.
[Sony Cross-Device General] slipsystem:
Hey man Im having an issue with aroma installer.

when I try flash an aroma zip. it just freezes before entering the installer and the phone reboots.

I am ussing the Z3 D6603 with Z3-lockeddualrecovery2.8.7-RELEASE
[Sony Cross-Device General] [NUT]:
I assume you mean sideload? I didn't try to fix that yet. TWRP is the same version but monx and me both did it ourselves.
[Sony Cross-Device General] zanndoth:
damn daylight saving...

thanx for pointing it out. =D
[Sony Cross-Device General] petrifyre:
I think he mean that mounting sdcard to pc in recovery cause before this using s3, I can mount sdcard to pc inside recovery in Mount option
[Sony Cross-Device General] Teo032:
Quick question guys. I can't seem to flash the recovery via recovery. It'll say successful when flashing but it doesn't seem to stick. It looks like I'm able to flash via fastboot fine but other than that the old recovery seems to remain intact. Is there a step I'm leaving out?
[Sony Cross-Device General] [NUT]:
Ah. Lol, I never tried that to be honest, so I don't know...

:eek: don't flash these things using fastboot bro... That can fubar your phone...

If you send me the logs from /cache/recovery right after a new attempt to flash it using recovery, I might be able to find what is causing it to fail.
[Sony Cross-Device General] caqo71:
That's correct, thanks for clear things up

Really you don't, it's very useful, sometimes when you go to recovery to wipe data before flashing, and you forgot to copy the rom, addons, etc. it's very useful to mount sdcard to pc to copy files to flash, if not, you may have to flash a whole ftf rom just to get acces to your sd card to copy rom files, just to flash the ROM.

FYI, this feature is broken on TWRP and on CWM 6.x, sd card is not visible on pc mounting it from a recovery. :(
[Sony Cross-Device General] [NUT]:
Ah, that's useful indeed ... came across that situation more then once myself ;)

I'll have a poke around and see if i can fix that.
[Sony Cross-Device General] shoey63:
Have a look here https://github.com/PhilZ-cwm6/philz_touch_cwm6

and here

http://xdaforums.com/showthread.php?p=39433458

He seems to have solved the problem
[Sony Cross-Device General] Teo032:
oops sorry i meant other recoveries in general, all the zips won't flash, even that XZrecovery app that is suppose to install it didn't work. Only method that stuck are the fastboot ones.

here's the log

last_log
[Sony Cross-Device General] [NUT]:
Hmm... Looking at the logs, it worked just fine... What ROM do you currently have on your device? Do you use a custom kernel?
[Sony Cross-Device General] Teo032:
running eXistenZ Ultra I originally attempting on stock kernel, but didn't work so now I'm running DoomLord's v9 now. Do recoveries not apply to custom kernels? New to X Z or sony devices in general, getting use to it.
[Sony Cross-Device General] [NUT]:
Heh, you actually don't need this package, as DooMKernel has them built-in already... :)

[MENTION=2784807]DooMLoRD[/MENTION] will update his to the latest versions soon enough :)

When rebooting your phone, look at the LED during the DooMKernel logo. As soon as it turns purple, press VOLUME-UP for CWM and VOLUME-DOWN for TWRP :)
[Sony Cross-Device General] Teo032:
lol yeah i can get into recovery, I'm just a little confused while flashing didn't work before on stock kernel, and now while using Doomkernel. Seems like everything was pushed through on stock, the files were there, but it was still launching the old recovery. Wouldn't flashing your zip update the recovery on doomkernel though? or does that not work like that on this phone with custom kernels? Bothers me when I don't know how everything exactly works lol, just trying to clarify things for myself lol
[Sony Cross-Device General] [NUT]:
Oh lol :D NOW I get it... Didn't you notice you also see a green led flash a few seconds after the purple one? Try the volume buttons during the green led :)
[Sony Cross-Device General] Teo032:
Ohhh now I get out also lol. So that's how it works. So technically I have 4 recoveries lol
[Sony Cross-Device General] AndroPlus:
[MENTION=4904057][NUT][/MENTION],

could you make default path for internal storage to /data/media, not /sdcard?

I have a problem with /sdcard and TWRP showed only two folders, clockworkmod and TWRP.

When I access /data/media, TWRP shows all folders and files and can install zip.

I'm using Xperia Z, TWRP 2.6.0.0
[Sony Cross-Device General] [NUT]:
Yeah :) To explain a little (as you said you are new to Xperia phones):

Sony and SonyEricsson phones have a quirk in comparison with Samsung and HTC phones in that it lacks the recovery partition. The recovery can only be included in the kernel boot image or from the OS by hijacking one of the core applications during boot. The kernel image can only be updated by the kernel dev or by replacing the ramdisk in it yourself. There is no other way to update it.

I'm also running DooMKernel and have XZDualRecovery installed as well :)

I'll see what I can do, it might be wise to use that instead. Thanks for the suggestion!
[Sony Cross-Device General] Teo032:
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
[Sony Cross-Device General] Traxx67:
Hello all,

i have a question, i'am on monxDIFIED ESSENTIAL i1 v1.03 with DooMKernel v09.

Can i do the update?

Thank you for your answer.
[Sony Cross-Device General] shoey63:
Just flashed on CM10.1 and it works just fine:thumbup: Now I have 2 CWM and 1 TWRP recoveries:p

Boot sequence is :-

-Volume up on purple LED to enter CM10.1 CWM recovery

-wait a little longer for green LED then Volume up for [MENTION=4904057][NUT][/MENTION] 's 6.0.3.3 CWM, OR Volume down for TWRP 2.6 :cool:

---------- Post added at 05:35 PM ---------- Previous post was at 04:54 PM ----------

Sure, why not? Seems to work on any kernel, any ROM, whether or not bootloader is locked or unlocked.

Only need to wait for green LED before pressing volume up/down.

Just try it and report back;)

Edit: To enter DualBoot, wait for green LED, press volume up, wait for purple LED, THEN press volume up/down to enter either CWM or TWRP
[Sony Cross-Device General] [NUT]:
Heh... I believe I know why: chargemon has a simplified version of DRSETPROP, which is meant to create a configuration file only...

Change of plan: remove the line from chargemon and put the DRSETPROP in dualrecovery.sh, line 133. There the DRSETPROP function exists and you will be able to change the setting in the prop file.
[Sony Cross-Device General] joseangel.alv:
Again... Thanks a lot! ;)
[Sony Cross-Device General] ulum.misbahul:
Hey guys, i still can't reboot into ClockWorkMod (CWM) mode on dual recovey 2.8.12 or 2.8.13

My phone xperia z1 compact lollipop, thank for your work.
[Sony Cross-Device General] [NUT]:
2.8.13 is now online, with TWRP 2.8.

6

.0 again. Please give this a try as well.

THIS IS A TESTING RELEASE, BE AWARE THIS MIGHT BE UNSTABLE!!

Another change on this version is that it should clean up NDRUtils when it's in the wrong location (on lollipop). NDRUtils was still being included in the system/app folder of the flashable version, which was not supposed to be there...
[Sony Cross-Device General] juanpirulo:
[MENTION=4904057][NUT][/MENTION] Sorry again this is running the same problem (doble line byeselinux set on true) and the system dont start. If take out the sd card and deleted (on the pc) one of the lines system reboots ok .cheers

I am just changing byeselinux from false to true in the xzdr.prop to check this (i am telling you in case i am doing something wrong)
[Sony Cross-Device General] infinitylook:
This is a noob question, is there a difference if i use 2.8.3 recovery then use the byeselinux fix? Or 2.8.10 is just the same. Will amplify xposed module work on 2.8.3 just like how 20mp superior auto works on 2.8.3 with byeselinux fix as what others are reporting here.
[Sony Cross-Device General] sgiannouris:
D6603 LB

I flashed the .zip from TWRP, rebooted to system, rebooted again to recovery, went to save recovery log to SD, and I got

E:/sbin/postrecoveryboot.sh process ended with ERROR=1

On the messages screen of TWRP.

Root is working, system is able to be mounted r/w. I haven't tried backup or restore.

recovery log attached.

Need anything else from me?
[Sony Cross-Device General] Bird40:
When I made a backup on my C6503 and GSP521 I also received a message

E:/sbin/postrecoveryboot.sh process ended with ERROR=1
[Sony Cross-Device General] Wiltron:
Backup/Restore works even with Error = 1

I just tried a full backup on my C6906 / LB running KK 157 on 2.8.13. I wiped the entire device then restored the backup, and even with the error, it was fine. Booted normally, still rooted.

I'm also able to access media on both internal/external SD card from within recovery.
[Sony Cross-Device General] [NUT]:
The postrecoveryboot.sh error can actually be ignored. I'll rework that script to throw an error when there really is a reason to do so...
[Sony Cross-Device General] [NUT]:
Hmm... That doesn't make much sense (that it fails to replace the value I mean). I'll see what I can do about that...
[Sony Cross-Device General] Wiltron:
[MENTION=4904057][NUT][/MENTION]

Managed to get Error=255 when mounting system and wiping it..

Thoughts?

Everything seemed OK though - unsure if the system was actually wiped though :/
[Sony Cross-Device General] tiunilohmu:
Thanks for your help, but I dont have any other apk inside the /system /app.

The problem occur after I updated from 2.8.3 to 2.8.7 and on.

Maybe, it's not the XZDR issue.
[Sony Cross-Device General] Space_pilot:
Hi, noticed that in line "dr.ramdisk.path=" there no any value after "=".

Also i had 2 lines "dr.keep.byeselinux=false", so i deleted one. Is it all ok?

2.8.12(flashable) 6603 LB LP

Wbr.

P.S. Oh again ;)
[Sony Cross-Device General] Ratha ITC:
I updated my Z1 from 2.8.10 to 2.8.12 without any problem but some people get stuck after updating. Is there any solution? :)
[Sony Cross-Device General] juanpirulo:
anyway , do you have an idea why has to be set byeselinux to true with the modified rom and why is doing fine with pure stock? I just modified systemui services.jar (for superusermod) and home apks. cheers
[Sony Cross-Device General] Wiltron:
Oh yeah.. found a bug in 2.8.13.. this image sums it up perfectly :P

In all seriousness.. when the lockscreen timer goes out, and the screen turns off (from it being dim), it adds a lockscreen on top of a lock screen. If you let it sit there, say, when you're doing a nandroid backup, you'll have to slide to unlock about 3 or 4 times before you can use the system again :P
[Sony Cross-Device General] [NUT]:
Yes, that you forgot to go to Advanced and hit the Copy Log to SD button to attach it here :p
[Sony Cross-Device General] [NUT]:
Make sure people delete the XZDR.prop file when using custom ROM's to eliminate double entries, I think that's what juanpirulo (below) is experiencing too..

You modified the files (most likely on windows) and because of that the files lose their SELinux context... Either restore the SELinux context on the modified file OR disable SELinux to solve ;)

I LOL'ed there :D

Yes, I experienced it once too while testing the build, but I thought it was a fluke :p

Must be counted as a bug then :)
[Sony Cross-Device General] juanpirulo:
mmm AS this is the first time I am going to attemp this its something like restoring in ubuntu this modified files with this command?

should i restore the hole system

restorecon -R /system

or just the files that i modified

restorecon SystemUI.apk

cheers.
[Sony Cross-Device General] [NUT]:
To be honest, I am not entirely sure, because the command on linux is way more complicated then the one in 'toolbox' which is included in the ROM (the restorecon binary is a link or copy of toolbox, which is a kind of busybox) and even busybox does it in a different way.

If I where you I'd check the update-binary in the SuperSU flashable zip, it holds a wealth of information for those who are interested as it's not a true binary but a script :)

I am currently building 2.8.13 Attempt 2, to replace the files currently online, this holds a patch to the DRGETPROP/DRSETPROP functions. My logic in them was flawed, so it would keep adding the same value over and over again if any of them would be set to 'false' :o

It also includes a new postrecoveryboot.sh script in TWRP which should now not bunk out over nothing :)

-- EDIT --

Attempt 2 is now online.
[Sony Cross-Device General] v7:
Made XZR kernel using kernel builder on my Xperia ZR.Works great.Thanks [MENTION=4904057][NUT][/MENTION]:)
[Sony Cross-Device General] AussieCable:
2.8.13 Attempt 2

I am happy to report no current issue's on my D6503 - all very happy indeed :good:

I should mention running .726 prerooted update package with XZDR 2.8.13 A2 flashable.
[Sony Cross-Device General] Bird40:
2.8.13 Attempt 2 works fine on my devices SGP521 and C6503.
[Sony Cross-Device General] apexofservice:
why so many recoveries

I'm sure this is a stupid question but I'm coming from 5 years with an old samsung that I had cwm recovery on and it worked great.

Now, I've got an z3c and I've got it rooted and I want to put some kind of recovery on that I can use to make a nandroid backup. But I noted that (1) when I do `adb reboot recovery' I seem to come back up to system (weird, eh, is there no recovery mode on a stock sony phone?) and (2) what's going on with dual recovery? That is, why would I ever need more than one recovery? I clearly need a good one so that I can do backup and restore (and flashing and cetera) but what's with the dual thing? Ie, why would I want dual recovery instead of just TWRP or CWM or PhilZ (last one I haven't ever tried or heard of).

Thanks for any insight!

EDIT: I ran the installer and I note a couple of things:

1) I was able to install it and now I'm making a backup using TWRP (yay!)

2) script doesn't actually need su (assuming you have the udev rules correctly setup for your device), I changed the shebang to fix this "#!/bin/sh"

3) I had issues using your adb binary (it seems to be out of date). I first tried to fix it by just changing your ADBBINARY Environment variable to "`which adb`" but that didn't work because you're using local paths "./${ADBBINARY}" below, so had to also do %s/\.\/\${ADB/\${ADB/g to get all the substutions cleaned up.

4) After this, it went off like a charm! Thanks alot and let me know if you can answer my questions from above.