yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] theduke7:
i usually do mostly use TWRP, but as i said the last mod i flashed i did on Philz, so i thought it does mount system( and it does when flashing other mods, i just tried reflashing the 2 i have in my sign with Philz and they flash fine) ...but ofcourse this seems (at least for me) to be an issue flashing Xposedv65 with Philz, because i also flashed the previous Xposed version with Philz and it did work ...

but as you said, if one recovery is flashing it OK (TWRP), then the issue might be indeed on Philz, at least flashing Xposed 65.

---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------

i think this is the update log for v65 release , so i assume it's already included, because the other updates he mentions on the post are already included

i'm as confused as you are, a BusyBox file is no where to be found on the Xposed flashable zip...
[Sony Cross-Device General] McBane87:
Yeah, thanks.

But there it is called: "busybox-xposed". So if this name will be kept after installing, then this shouldn't interfere with XZDR.

And for first installation, where Xposed APP is not installed yet, it shouldn't interfere with anything. Because obviously not installed at this point.
[Sony Cross-Device General] theduke7:
yeah, it makes sense...

i also i think would work if system was mounted manually on Philz before flashing latest xposed, it's not a big issue for me, my only point was if Philz flashing and mounting system normally for other mods why this issue with latest Xposed
[Sony Cross-Device General] Yenkazu:
Yeah, you got it :3

Okay, for now, don't blame the Xposed .zip and .apk :p

Eh, actually it's something related with .zip signing ?

Rovo already explain that, maybe some recovery doesn't support it ?

EDIT:

It's here

http://xdaforums.com/showthread.php?t=3034811&page=2
[Sony Cross-Device General] McBane87:
But as we can see on Logs. The Recovery isn't refusing the flashable. It is executed the way it should be until the Script of the flashable isn't able to mount System-Partition.

---------- Post added at 01:04 PM ---------- Previous post was at 12:30 PM ----------

Maybe you could try this:

Move the marked two lines a little bit down in dualrecovery.sh (under PATH="/sbin") and change them a little bit.

(remove the "-l" from system and add "busybox" to odex line)

# Turn off LED
SETLED off

[COLOR="Red"]EXECL umount /system/odex
EXECL busybox umount -l /system	# System[/COLOR]

export PATH="/sbin"

# AS OF HERE NO MORE BUSYBOX SYMLINKS IN $PATH!!!!

After this it should look like this:

# Turn off LED
SETLED off

export PATH="/sbin"

[COLOR="red"]EXECL busybox umount /system/odex
EXECL busybox umount /system	# System[/COLOR]

# AS OF HERE NO MORE BUSYBOX SYMLINKS IN $PATH!!!!
[Sony Cross-Device General] kingvortex:
Just an FYI. This issue occurs on other (non Xperia) devices when trying to flash Xposed with Philz. I don't think this is a problem with XZDualRecovery.
[Sony Cross-Device General] deftoner:
Hi guys! quick question, I just upgraded to D6503 23.1.A.1.28 via flash tool (downloading the rom from the same program). I Flashed D6503_23.1.A.1.28_XZDRKernel2.8.20-RELEASE.flashable.zip, the phone works just fine, but not vol + or - trigger the recovery during boot. Nothing happend, I tried "adb reboot recovery" too but no luck, any idea?

Thanks!
[Sony Cross-Device General] mir2:
I understand what he says.

But in my case, before the 16 version 4.4.2 and 4.4.4 I have never had the problems I mentioned.

I never had power only when the telephone is off after completing their charge.

It is also much chance of that if the Recovery off the phone does not behave that way, so something will have also to Recovery.

It was getting LL, install the version 18 of its recovery and start all problems.

Many people have asked me if I was root, had improperly installed binaries and others but ultimately very few have been the solutions.

Now I understand why several have told me that they have not had problems like me.

Well it seems I've found joins explanation to my case if I can also understand that it has nothing to do with the DualRecovery or in part perhaps have to have everything.

Install EC1 LL 5.0.2 Generic ROM and saw that the phone worked me perfect, install the recovery nor gave me any problems.

I made one last try and reinstall the ROM 5.0.2 Generic ES LL, worked well but was install the Recovery and back problems.

So I got to install the ROM Kernel Generic LL EC1 5.0.2 and then the recovery and now I no longer turn only after charging and be off.

Maybe people or yourself tengais a different ROM to which we and many others have different problems.
[Sony Cross-Device General] McBane87:
Try to use Z1c-Version. It has same Resolution as yours.

Don't know if it will work. So do it at your own Risk.
[Sony Cross-Device General] theduke7:
sory m8, i i'm up sense 2 days ago, so i fell asleep :P

so, no , it didn't work , gives the same error.
[Sony Cross-Device General] random_n00b:
Just my 2 cents concerning the /system not mounting issue.

It works fine with TWRP and CWM on my Xperia ZL. Just Philz doesn't mount /system.

Also (maybe unrelated) I had some issues with Philz on my Nexus 10.

For me that means Philz is the problem, not XZDR or Xposed.
[Sony Cross-Device General] theduke7:
[MENTION=4712883]McBane87[/MENTION] , it might be a Philz issue, but it has to be an issue concerning the way This Xposed version is Installing.

i don't know if you looked at the xposed flash-script.sh , but this is from it...

if [ ! -f "system/xposed.prop" ]; then
echo "! Failed: Extracted file system/xposed.prop not found!"
exit 1
fi

echo "- Mounting /system read-write"
mount /system >/dev/null 2>&1
mount -o remount,rw /system
[Sony Cross-Device General] McBane87:
Yeah, looked already inside. Looks like normal mounting.

You can try to copy/paste those two commands via "adb shell"

For me it was working.
[Sony Cross-Device General] theduke7:
yes, that's what i mean...it's weird because it seems normal...
[Sony Cross-Device General] McBane87:
What you also could try, is copy newest busybox to current running Ramdisk like this:

mount /system
cp /system/xbin/busybox /sbin/busybox
umount /system

After that, try to flash Xposed.

PS: This is only temporarily change. After reboot PHILZ will have older Busybox again.
[Sony Cross-Device General] theduke7:
for some reason i don

t have terminal on Philz, also the aroma manager doesn't work... (doesn't exist on Clockworkmod folder

---------- Post added at 06:49 PM ---------- Previous post was at 06:37 PM ----------

@McBane87 well m8, this has to be delayed for a little bit (few hours), my phone battery is almost completely drained... also i'm not sure how to enter commands to Philz without terminal!
[Sony Cross-Device General] McBane87:
You mean adb isn't recognizing your device with philz?

If yes, try this:

1. Download ADB-Drivers from here: http://developer.android.com/sdk/win-usb.html

2. In Windows go into Device-Manager and search for your Device.

Normally it should be displayed on top with a Yellow exclamation mark (!)

3. Right klick --> Properties --> Details --> Hardware-IDs

You should see now something like this:

USB\VID_18D1&PID_D001

4. Open the android_winusb.inf FIle from Drivers you downloaded before

5. Copy the Hardware-ID from above in this file under the following two sections:

[Google.NTx86]

;<Your Device> PHILZ
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

[Google.NTamd64]

;<Your Device> PHILZ
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001

6. Go into Device-Manager again

7. Right klick on your Device and choose to install or update driver

8. In the new window, use the manual way by specifiying the folder where android_winusb.inf is inside.

9. Install

Sure. No problem :)
[Sony Cross-Device General] theduke7:
[MENTION=4712883]McBane87[/MENTION] adb turned out to be Java issue, :)
[Sony Cross-Device General] McBane87:
How is java able to interfere with ADB?
[Sony Cross-Device General] theduke7:
just tried your directions and i get this message on the attached file every time
[Sony Cross-Device General] McBane87:
Maybe you need windows to accept unsigned drivers. Just Google for it ;)
[Sony Cross-Device General] theduke7:
yes my friend i figured it all out...

still after the commands you gave me, Xposed installer gives the same error...

i made sure ADB was working i mounted /system from adb and checked on Philz and then unmounted and checked again... the command works but the workaround not.

also still TWRB flashes it normally with no issue.

---------- Post added at 08:42 PM ---------- Previous post was at 08:30 PM ----------

[MENTION=4712883]McBane87[/MENTION] may be it's because it's signed as Yenkazu said

http://xdaforums.com/showpost.php?p=61621483&postcount=5759

if there's any other signed flashable zips (non harmful :D ) i could try and see
[Sony Cross-Device General] McBane87:
Well thanks. It was worth a try :)

I still don't think it's because of signed ZIP-File. Because Rovo is saying:

And as you can see in the Log posted before, PHILZ was able to extract ZIP-File. If the Zip would be not extracted how should PHILZ be able to execute the Script inside this Zip, which we already analysed a bit ;)
[Sony Cross-Device General] McBane87:
You are in luck, because CyanogenMod isn't supported at the moment.

About the FAILED Message: It should be fixed on newer Versions of XZDR.
[Sony Cross-Device General] McBane87:
Just for your Information. I think I was able to find the Problem:

http://xdaforums.com/showpost.php?p=61640206&postcount=7965

The "updater-binary" inside his flashable isn't a real one. It looks like it's a modified busybox, which is used for running his script instead of the ones inside recovery. And this busybox seems to have trouble with some commands/options.
[Sony Cross-Device General] Rootk1t:
Great that you find it! Let's hope [MENTION=4419114]rovo89[/MENTION] will fix it in the next release of framework.
[Sony Cross-Device General] whalesplaho:
i cant get viper4android to work cos each time i open, it says i should install driver, so i notice its from busybox, i tried installing busybox & it remove my recovery & some apps until i flash tha recovery back! busybox was installed initially but tha location was system/bin instead of system/xbin cos this was where busybox installer installs it.
[Sony Cross-Device General] theduke7:
Great work m8,

That makes sense... It had to be something with how It installs
[Sony Cross-Device General] McBane87:
This recovery isn't doing it different. Busybox from installer or flashable will be installed to xbin. Don't know why your busybox was on bin.
[Sony Cross-Device General] alias_neo:
Cool, thanks.
[Sony Cross-Device General] tokomoto:
I appreciate you posting this, worked perfectly for me! Up during boot for CWM and down fro TWRP!
[Sony Cross-Device General] Tungstwenty:
[MENTION=4904057][NUT][/MENTION],

One thing that's bugging me for a while is the fact that I can't use ADB while the device is in either of the recoveries.

I have read the init*.rc scripts and it should work, but for some reason it doesn't.

Could you have a look into it? Is someone else experiencing the same?

Some of my findings:

The stock kernel's ramfs has a /init.usbmode.sh script that is called from the *.rc's whenever the usb mode changes, and which correctly assigns the following Hardware ID for the windows driver:

"USB\VID_0FCE&PID_5193&REV_0228&MI_01"

Under recovery, however, the product id will be 6182 instead of 5193 and the driver won't work. Not even after I edited the *.inf to add that combination on top of the other ones.

The TWRP init.rc script now has these lines:

write /sys/class/android_usb/android0/idVendor [B]18D1[/B]
write /sys/class/android_usb/android0/idProduct [B]D001[/B]
write /sys/class/android_usb/android0/functions adb

which reflect the vendor and product for the Google adb drivers, but nevertheless the device seen by Windows is 0FCE,6182.

Using TWRP's file browser and terminal command functions I was able to see that /sys/class... doesn't exist. I only found the idVendor, etc. entries under /sys/devices/virtual/...

But even after echoing the new values into there, stopping and restarting adbd, nothing changes.

I hope someone can shed some light on this subject :(

A few other comments:

- external_sd can't be accessed from CWM (my external sdcard is exfat), despite the fact that etc/recovery.fstab mounts mmcblk1p1 as auto instead of vfat, as older versions did

- for reboot into recovery, it might be worth skipping the green led and the 2s pause, and jump straight to the pink led

- I found a tiny glitch on the supersu.sh / superuser.sh installation scripts, line 58 - missing "n" in .hidenandroidprogress

Cheers!
[Sony Cross-Device General] My Gnexi:
I just flashed XZDR on my Tablet Z SGP311. TWRP is wrong orientation as expected, but CWM does not start at all! The back light turns on and off every few seconds, but the LCD remains black.

It worked on 2.5.1

If this version is not currently supported in Tablet Z you may want to state it in OP as it is currently listed as supported/experimental.

BTW I used to have restarts when entering some folders on ES File Explorer with root permission, seems like you fixed it in this version.
[Sony Cross-Device General] [NUT]:
http://xdaforums.com/showthread.php?t=2317432

That thread contains the fix also applied by this version of XZDualRecovery.

I am working on a solution to suit all needs, including landscape TWRP for tabz... Hang in there for the next release.
[Sony Cross-Device General] My Gnexi:
Waiting:p

Let me know if I can help (mainly on Windows .bat scripting :), or testing)
[Sony Cross-Device General] kehinde:
such a breeze! Thanks.
[Sony Cross-Device General] brosenz:
Does it work with the Xperia Z Ultra?
[Sony Cross-Device General] [NUT]:
It should, just try it :)
[Sony Cross-Device General] yeeson:
Xperia Z Ultra，can use, but use will restart automatically in a few minutes

PS：Xperia Z Ultra，Flash Recovery，Headphone no Working！
[Sony Cross-Device General] N0wy0ud1e:
Wondering if this works with T-Mobile C6606.... Thread is over 50+ pages long so I wasn't sure how to search. Didn't see anything like that on the OP where it says C6603 at the most.
[Sony Cross-Device General] [NUT]:
It will work on the C6606, I was too lazy to update the OP :p
[Sony Cross-Device General] N0wy0ud1e:
Lol, regardless, thanks for the response. Also I'm trying to understand the benefits of having a dual recovery system. I would like to do this so I can flash stock ROMs with a locked boot loader.
[Sony Cross-Device General] [-Amrish-]:
Installed it and it works fine.

Easy steps to install a recovery!

Thanks NUT!
[Sony Cross-Device General] N0wy0ud1e:
Got it installed, thanks.
[Sony Cross-Device General] brosenz:
Is it stable?, I've seen feedback that it will self reboot on the Xperia Z Ultra
[Sony Cross-Device General] N0wy0ud1e:
I only used TWRP so far, but yeah it looks very responsive and works just fine. UI is a bit laggy since this is an unofficial port for the Xperia Z phone, but nonetheless it functions just as fine. From what I've read you have 10 minutes to use it on the Ultra before it decides to reboot.
[Sony Cross-Device General] uwillknow:
installed, but can't get into any of the recoveries after boot...there's no green led lights on, any clue?
[Sony Cross-Device General] adhiefadillah99:
please create for xperia L !
[Sony Cross-Device General] YudiA1:
try this way. in this thread too.

http://xdaforums.com/showthread.php?p=43974375
[Sony Cross-Device General] cashflow67:
Z1 lockeddualrecovery.flashable WORKS

hi [MENTION=410007]Nut[/MENTION], your latest version Z1 lockeddualrecovery 2.8.20.flashable.zip works like a charm. I am on locked bootloader and stock kernel. RockZL Lollipop Rooted Rom, I flashed it from twrp recovery then I rebotted into recovery again, it worked. There is no problem :)

Thanks for your effort :)
[Sony Cross-Device General] Faakarna:
Im loosing recovery everytime i flash stuff . What to do?
[Sony Cross-Device General] McBane87:
Which "stuff" do you flash?
[Sony Cross-Device General] Faakarna:
Fx lspeedmod. Other mods and tweaks Will cause the same issue when flashing. So annoying. Have to install dualrecovery from pc, with adb each time.
[Sony Cross-Device General] igotroot:
New to z3 d6616

Guys/Gals,

Coming from a Sammy S4..

I am researching getting root, and obtaining a recovery with a locked bootloader.. I have found info on getting root, but since coming across this forum (all almost 600 pages), I'd like to get clarification please:

1. With all the talk about loosing DRM keys, etc, if after obtaining root, and then electing to get this dual recovery am I able to have stock recovery & TWRP, Stock recovery & Phil's or any combo as such?

2. Will this dual recovery, since it can be obtained with a locked bootloader, leave the TA file / DRM keys intact thus no longer ever having to worry about the TA file / DRM keys at all? I do understand that a Stock Sony Kernal must be retained... I presume another kernel will not work with a locked boot loader.

As with Samsung S4/S5 will we have to use some type of a Loki Doki type of file to flash Custom Roms, or, since the stock kernal is used we won't need such a patcher.

Again, I'm new to the Z3 (5 days so far), and I appreciate the feedback. Thanks!
[Sony Cross-Device General] gel14a:
Will it work on C6602 Lollipop?

Hi I've tried old versions and I got bootloop. Will this version work on my C6602 Lollipop? Because I'm tired of installing lollipop over and over again(while trying to install the recovery). And of course I have locked bootloader.
[Sony Cross-Device General] McBane87:
Don't worry about your TA-Partition or DRM-Keys. They only get lost if you unlock your bootloader. So as long as you leave your bootloader as it is, there will be no problem with it. And this recovery will NOT touch/unlock your bootloader.

After installing this Recovery you will have 3 Recoveires: CWM, PHILZ, TWRP.

PHILZ is loaded by repeatedly prssing Vol+ on boot.

TWRP is loaded by repeatedly prssing Vol- on boot.

CWM will only be accessable by using NDR-Utils App, which will also be installed with this Recovery-Installer.

About Stock-Recovery:

I'm not sure if any of those Z-Devices out there have a "real" Stock-Recovery.

I think no.

---------- Post added at 09:13 PM ---------- Previous post was at 09:09 PM ----------

L SpeedMod is real deep intrusion to your system. Maybe it is somehow destroying/affecting XZDR.

Did you ever tried XZDR without L SpeedMod?

---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------

Since 2.8.19 it should work on Z-Series with Lollipop. But in the End you have to test it on your own, because some people where reporting success with Xperia Z and others still reported bootloops....
[Sony Cross-Device General] Faakarna:
Yeah i know. Just love the effect of this mod. I installed dualrecovery from adb, and then its ok. But when flashed lolliviper i lost recovery again. So annoying.
[Sony Cross-Device General] igotroot:
Niiiice! You ROCK!

And to think, people in the store were snickering that I turned down the LG G4 and Sammy S6.. I think the support here for Xperia is great, and its a great damn phone. Thanks again!

So this is really a Tri-Recovery, but I understand why its called dual.
[Sony Cross-Device General] whalesplaho:
i know dats where it should be... i ll try do some workaround & see!

thanks.
[Sony Cross-Device General] emeemisri:
Please my friend, next time dont qoute the whole OP

Pardon me for my very bad english
[Sony Cross-Device General] RedSkyRoad:
I want to remove this dual recovery but in the instructions it tells me to delete the following (which I cannot find). Are they suppose to be there?

/system/bin/charger
/system/bin/ric
[Sony Cross-Device General] [NUT]:
no.

You would have been quicker to flash the removaltool from the toolbox folder on my downloads site. It will remove all of XZDR, leaving nothing behind.
[Sony Cross-Device General] sebarkh:
I tried flashing nthe last CyanogenMod 12.1 in TWRP but it failed.

I have a Scorpion_windy device. And TWRP didn't allow me flashing because it recognized my device as Scorpion (not scorpion_windy).

And it showed "wrong device" error.

I suppose it has something to do with the recovery that has the false info about the device...
[Sony Cross-Device General] Yenkazu:
Nothing wrong with recovery. . .

Something wrong in your update-script in your ROM zip or your build.prop. . .

Please check it first :)
[Sony Cross-Device General] kt-Froggy:
What he said. ^^^

The easiest "quick and dirty" way around this problem is to disable (comment out) device check in the updater script. But it's there for a good reason, so do it at your own risk, only if you know that the package you are flashing is actually intended for your device...
[Sony Cross-Device General] Pandemic:
Installed yesterday the latest XZDR 2.8.20 and Xposed Framework and all works fine as usual, thanks bro [MENTION=4904057][NUT][/MENTION] :cool:

Sended From My Z3 On Moonwalker Provolution V1.5 To Your Eyes !
[Sony Cross-Device General] gitzz:
Thank you NUTS, finally today because of you my phone is awesome again!! I rooted with Kingroot, installed ur Recovery, then clean wipe all, installed prf with supersu and xposed zip with it, phone started up, root was there, but recovery was gone, installed the recovery again and now I m way happy because of your this awesome tool
[Sony Cross-Device General] [NUT]:
Okay, it seems most if not all issues have been resolved, I will finalize the 2.8 RELEASE stream of packages with one last release, taking care of some smaller bugs and issues.

From that moment onward, unless something disastrous happens and XZDR breaks completely again, there will be no more updates and work on XZDR 2.9 BETA begins.

2.9 BETA will contain so many changes it will most likely cause issues, so it won't be for the faint hearted, but I really do need people to test it thoroughly.

So, for 2.8, please report any remaining issues now, so we can release a fix in the final version.
[Sony Cross-Device General] _SIL_:
Small error report for on Xperia ZL.

1. There is error with usb-otg in fstab.qcom:

/devices/platform/msm_hsusb_host/usb ... - usb-otg not worked (currently)

/devices/platform/msm_hsusb_host ... - usb-otg worked

2. In twrp.fstb. No any errors, but for better compatibility:

/external_sd	auto	/dev/block/mmcblk1p1 /dev/block/mmcblk1	flags= ...

/usb-otg	auto	/dev/block/sda1 /dev/block/sda	flags= ...
[Sony Cross-Device General] Foch155:
Well it works just lovely!!

Just for the list <3

Sony Xperia T2 Ultra (5306)

Lollipop 5.0.2 (19.3.A.0.472)

Thx alot [MENTION=4904057][NUT][/MENTION] and team!!
[Sony Cross-Device General] AussieCable:
I'm in for testing.
[Sony Cross-Device General] juanpirulo:
I am HERE for some testing on z1 if you needed. Cheers
[Sony Cross-Device General] caqo71:
So, the installer version and the flashable version both works ok?. Seems that flashable one doesn't works when included in PRFCreator.
[Sony Cross-Device General] pvnsai73:
Im also here for testing on t2ultra [MENTION=4904057][NUT][/MENTION]
[Sony Cross-Device General] Rootk1t:
http://xdaforums.com/showpost.php?p=61721766&postcount=431
[Sony Cross-Device General] caqo71:
Well, i.have a z3

Enviado desde mi D6603 mediante Tapatalk
[Sony Cross-Device General] McBane87:
Well without any further Information, like Logs or Error-Messages, I'm afraid nobody will be able to help here.
[Sony Cross-Device General] _SIL_:
Another small adjustment for TWRP smooth animation of indeterminate images 378x30, without jerks. ;)
[Sony Cross-Device General] caqo71:
Sorry mate, i just wrote that as a way to say that all works ok on z3.

Enviado desde mi D6603 mediante Tapatalk
[Sony Cross-Device General] papperlapapp:
Oh... Well, it works flawlessly with CM 12.1 on my Z1.

CM just wipes the dual recovery after updating it.

After updating the nightly I just installed dual recovery 2.8.20 again and this time with no "FAILED" message.

I experience no errors with CM 12.1.

Why does it need to support CM?

Isn´t the recovery independent from the OS on top of it?

Thanks