yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] pvnsai73:
Here is the log of t2ultra dual on stock lollipop 5.0.2

https://docs.google.com/file/d/0BxAHIwYT1eNlUGZ5dmllQmlMaVk/edit?usp=docslist_api
[Sony Cross-Device General] [NUT]:
Please provide me with all the init files from rootfs as well, zipped up.

Is root working ok? If so, can you install using the installer and copy the installer output to a file and attach here too?
[Sony Cross-Device General] sekac55:
I have problems with the kernel, D6603_23.2.A.0.278_R13C_XZDRKernel2.8.14-RELEASE.flashable

I will fastboot it : FAILED (remote: size too large)

finished. total time: 0.786s

When i flashed it in Recovery everything is ok but when i reboot no bootlogo

Edit: I tried to flash dualrecovery in recovery and it reboots the recovery.
[Sony Cross-Device General] [NUT]:
Hmm, that's not good... How big is the boot.img in bytes according to windows?
[Sony Cross-Device General] sekac55:
24318 KB
[Sony Cross-Device General] [NUT]:
Holy sh1t! That's a LOT bigger then the size of the boot partition o_O

Please upload a correct kernel.sin to the builder for your fw.

- Edit -

Wait, you really checked the boot.img from the tmp folder and not the zip itself?

-- EDIT 2 --

Okay, unpacked the boot image from that file to see what was going on... I found 2 things:

1: It is not a stock kernel which has been used to create that package (so I will be removing it from the built files)

2: I modified the kernel builder to remove more recovery packages from the sbin folder when it's a custom kernel, because there was a TWRP image from the original kernel still included, which bloated the kernel image to a size too big for your device.

Grab a kernel.sin and upload that to repack it with XZDR.

-- EDIT 3 --

I modified the kernel builder to abort when the kernel size goes above 20MiB, which is the boot partition size for most of the supported models.
[Sony Cross-Device General] pvnsai73:
Here you go dev

https://docs.google.com/file/d/0BxAHIwYT1eNlNXdtd2NTeXMwWGs/edit?usp=docslist_api

Hoping that uvl soon fix the bug because we all r waitn to flash many things on our phne nd pretty excited as we received lollipop yesterday

Thanks in advance

---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------

Yeah root is working fine with system rw and we rooted by using prf creator

Thanks in advance
[Sony Cross-Device General] [NUT]:
Is the preparation log from right after the reboot by the installer?
[Sony Cross-Device General] pvnsai73:
Yes bro

---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------

Once again uploading the log

https://docs.google.com/file/d/0BxAHIwYT1eNlOElSWWhQWnpBdTg/edit?usp=docslist_api
[Sony Cross-Device General] [NUT]:
Weird sh1t...

Can you reboot and right after the reboot grab /proc/kmsg (using root, otherwise it will be empty) and attach it here?
[Sony Cross-Device General] Theliakos:
hey [MENTION=4904057][NUT][/MENTION] got a question on xperia sp section and android 5.1 we cant have a kernel in .sin but only a kernel in .img and when i upload a kernel.img the webpage stucks and doesnt say to download anything
[Sony Cross-Device General] [NUT]:
Please attach that kernel here for me to try/debug.
[Sony Cross-Device General] Theliakos:
here [MENTION=4904057][NUT][/MENTION] ! this is android 5.1.1 kernel from unofficial build for huashan ! :)
[Sony Cross-Device General] pvnsai73:
Its gng on like that frm minutes so I stopped at 1mb here is the attached kmsg

https://docs.google.com/file/d/0BxAHIwYT1eNlSDJRbldhdnR6MlE/edit?usp=docslist_api

Thanks in advance
[Sony Cross-Device General] puppet13th:
The solution already exist,please rename busybox to sh and place it in /system/xbin. use #!/system/xbin/sh for script shell.

when compiling busybox make sure you have these in the config:

CONFIG_FEATURE_PREFER_APPLETS=y
CONFIG_FEATURE_SH_STANDALONE=y
[Sony Cross-Device General] [NUT]:
Ohh, I never knew this feature existed... I'll read up on that and will see how to incorporate it in to xzdr, thanks for pointing that out!
[Sony Cross-Device General] [NUT]:
Will have a look at it tomorrow, lack of time right now.

It's weird though, I wonder what the difference is between the z2 and T2 Ultra lollipop kernel, because it seems to fail at loading the byeselinux module...
[Sony Cross-Device General] pvnsai73:
Yup thanks
[Sony Cross-Device General] :
Hey [NUT],

thanks for all your hard work, newest version runs pretty slick on my Z3C :cool: I am using a "materialized" theme for trwp from this thread: http://xdaforums.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

However I would also like to change the default splash screen to match my theme. Instructions are here: http://xdaforums.com/showpost.php?p=56224204&postcount=2

Sadly, I never found a "stock" TWRP version for Z3C (which is needed for editing the splash screen), so I thought: "Well, [NUT]s recovery includes TWRP so maybe I can use the mentioned method, not on a stock but on his recovery". So I took a look at your installer and your flashable .zip but I found nothing that looks familiar.

So is there even a stock TWRP existing for our Z3C or a way to change it in your dual-recovery?

Grettings from Germany! :victory:
[Sony Cross-Device General] pvnsai73:
[MENTION=4904057][NUT][/MENTION] r u there

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

[/COLOR [MENTION=4904057][NUT][/MENTION] Bro plzz fix t2ultra dual recovery soon as Xperia xposed also out today so plz this is my humble request to fix the byeselinux.ko bug that our kernel not accepting it....dnt be angry as we r eager so that's y Iam messaging this many times

Or even plz reply so that we vl knw that ur active or inactive
[Sony Cross-Device General] Renmazuo:
Seriously man. NUT is already aware of the issue, no need to rush him. I am looking forward for an working recovery after the 470 update, as much as you. But more than anything else, we got to respect the dev (and XDA as well, as pressure and ETA requests are forbidden here).
[Sony Cross-Device General] cashflow67:
Hi man. Thanks for your all efforts for recovery. But I want to ask you something. I am using RockzL v1.1 Rom. Stock Lollipop, Rooted,De-odexed. Now There is your recovery in it v2.8.10. But I want to update recovery to latest version 2.8.14. Can I flash 2.8.14 flashable.zip over it? Or if I can, Can you tell me how I can. Because untill this version, I tried to update recovery, but it hanged at sony logo.
[Sony Cross-Device General] Pandemic:
Brother [MENTION=4904057][NUT][/MENTION]

2.8.14 works just great on my Z2 with LP no issues at all :good:
[Sony Cross-Device General] m_k1815:
NUT

your work is great.Either 2.8.14 or 2.8.12 is works at all on LP and KK.Thanks bro.

NO bugs
[Sony Cross-Device General] [NUT]:
You SHOULD be able to update using the flashable zip without issues. Please report any issues you encounter with a full set of logs (from both the recovery and XZDualRecovery folders).
[Sony Cross-Device General] [NUT]:
Thanks for this log, this answered my doubts.

Can you connect your device, open a CMD window and cd to the files directory inside the installer zip? Then follow these instructions:

adb push byeselinux\byeselinux.sh /data/local/tmp/byeselinux.sh
adb push byeselinux\byeselinux.ko /data/local/tmp/byeselinux.ko
adb push byeselinux\modulecrcpatch /data/local/tmp/modulecrcpatch
adb shell
su
cd /data/local/tmp/
chmod 755 byeselinux.sh
chmod 755 byeselinux.ko
chmod 755 /modulecrcpatch
./byeselinux.sh

And then report what ever the output might be?

Please send me a zipped copy of the contents of your /system/lib/modules folder and attach it here.
[Sony Cross-Device General] pvnsai73:
It says "error patching kernel module file not found"

Here are files yu asked and yu written last code wrong :P

https://docs.google.com/file/d/0BxAHIwYT1eNlblY5c3NwYURZRlk/edit?usp=docslist_api

Thanks Dev fr working on our phne
[Sony Cross-Device General] Renmazuo:
I tried it here too, but i think something went wrong. My result:

C:\lockeddualrecovery\files>adb push byeselinux\byeselinux.sh /data/local/tmp/by
eselinux.sh
1 KB/s (1357 bytes in 1.000s)

C:\lockeddualrecovery\files>adb push byeselinux\byeselinux.ko /data/local/tmp/by
eselinux.ko
2944 KB/s (30148 bytes in 0.009s)

C:\lockeddualrecovery\files>adb push byeselinux\modulecrcpatch /data/local/tmp/m
odulecrcpatch
663 KB/s (13592 bytes in 0.019s)

C:\lockeddualrecovery\files>adb shell
shell@D5322:/ $ su
su
root@D5322:/ # cd /data/local/tmp/
cd /data/local/tmp/
root@D5322:/data/local/tmp # chmod 755 byeselinux.sh
chmod 755 byeselinux.sh
root@D5322:/data/local/tmp # chmod 755 byeselinux.ko
chmod 755 byeselinux.ko
root@D5322:/data/local/tmp # chmod 755 modulecrcpatch
chmod 755 modulecrcpatch
root@D5322:/data/local/tmp # ./byeselinux.sh
./byeselinux.sh
sh: ./byeselinux.sh: No such file or directory

The .470 update has another issue, which may explain the byeselinux module problem. Since the update, we can't mount system as R/W. Root with SuperSU works, most of the root functions work too, but we can't write to system. I've noticed it when i tried to uninstall a system app and install busybox pro, as both failed. You think this might be related to the recovery issue, as ADB depends on its SuperSU permission (i think)?
[Sony Cross-Device General] pvnsai73:
"Use ric killer by mohammed or just run t2u dual recovery installer 2.14" then yu have system r/w option its jus because of wpmod.ko
[Sony Cross-Device General] Renmazuo:
It works! The recovery installer did the trick. Thanks man.

Sorry for the offtopic NUT, system R/W is not related after all.
[Sony Cross-Device General] boilavera1980:
So after flashing the newest recovery im stuck in a bootloop right after the sony logo ... sigh... any ideas??

Clean flashing newest LP with newest Recovery results in the same ... **** what is going on ??!?! hmmm....

Edit:

Hell...now i finally booted into a LP firmware... before flashing i deleted the whole xdblabla folder, dont know if that did anything or what o dont know... i just sat here 4 hours figuring out what is going on since older versoion ran flawless!!! wtf

Edit2: Okay, now i cant access recovery and i am really afraid to use the installer so that everything will f4ck up again, i get a green led and 2 vibrations .. i really need help with this one since i cant figure out what is going on

Edit3: Ran installer but cant access recovery .. hmmm

Edit4: okay changed default to twrp in the .prop and spammed vol down .. did that change?!
[Sony Cross-Device General] Pandemic:
Why you mess around with the .prop ?

Dont change anything on your own buddy, now you messed it up by your own and ask us for howto fix, how we should knew it what you did, its your fault not ours, use the recovery installer for pc, that works for me very well !! ^^
[Sony Cross-Device General] russel5:
Hello [MENTION=4904057][NUT][/MENTION] it's me again and i have some bad news for you :)

In this code

if [ "$(DRGETPROP dr.pwrkey.node)" = "" -o "$(DRGETPROP dr.pwrkey.node)" = "false" ]; then
DRSETPROP dr.pwrkey.node $(pwrkeySearch)
fi
if [ "$(DRGETPROP dr.gpiokeys.node)" = "" -o "$(DRGETPROP dr.gpiokeys.node)" = "false" ]; then
DRSETPROP dr.gpiokeys.node $(gpioKeysSearch)

you are have a bug. If use flashable package and delete all folder XZDualRecovery on sdcard1.

We can't enter recovery by pressing vol keys after that^^

Because your script only check already founded gpio and pwr keys, but if this string not exist at all nothing happend and script not add this string

Sorry for my English i think you understand ;)

P.S. And yes, i test this and yes, problem exist
[Sony Cross-Device General] [NUT]:
Whoops, I know why that happens... if you change false in the if statements to 'null' then they will kick back to life again.

Thanks for spotting this bug! :good:
[Sony Cross-Device General] [NUT]:
Can you both follow the same guide but add these steps before you already tried:

1: adb push busybox /data/local/tmp/busybox (make sure you also chmod 755 busybox later on)

2: set SELinux to permissive (can be done by typing echo "0" > /sys/fs/selinux/enforce)

3: mount /system R/W before you attempt to execute this script again

Then please after running the script grab /proc/kmsg using the same root shell, the last 300 lines will be enough. You can use busybox for that, while still connected to adb shell as root:

busybox tail -n 300 /proc/kmsg > kmsg

Using root explorer / es file explorer you should be seeing a small file called kmsg there now, attach that here.
[Sony Cross-Device General] devilmaycry2020:
HI all

Installed on Xperia TX running CM12.1, i neither boot to PhilZTouch nor CWM, only boot to TWRP 2.8.6.0, so how can i manage it to boot to another recovery mode ?
[Sony Cross-Device General] cashflow67:
Hey man, I tried and hanged sony logo again. By the way, I am at locked bootloader and stock kernel. 2.8.12 to 2.8.14 failed again :)
[Sony Cross-Device General] [NUT]:
The locked bootloader variant is meant for STOCK rom's only, not for CM...

I'm afraid the TWRP you are looking at is the one integrated in the kernel.
[Sony Cross-Device General] [NUT]:
*sigh* ...

What version FW are you using right now?
[Sony Cross-Device General] cashflow67:
RockzL v1.1 Lollipop .242 Rooted, Deodexed, supersu beta v2.49, nut recovery 2.8.12
[Sony Cross-Device General] [NUT]:
Turn off your mobile, connect the charger when it's off, what happens next? Does it boot or does it only charge?
[Sony Cross-Device General] cashflow67:
Wow, thanks to you I discovered a new thing. It doesn't charge, directly I boots to my home :D
[Sony Cross-Device General] pvnsai73:
[MENTION=4904057][NUT][/MENTION] BRO will you plz tell me wt to do now from first after connecting my phne to pc

Iam little bit confused ?

Plzzz

Sry fr inconvenience
[Sony Cross-Device General] devilmaycry2020:
Yeah, This CM12.1 have TWRP integrated in the kernel. anyway you have the page to building the XZDualRecovery 2.8.14 Advanced Stock/CM/AOSP/Omni Kernel but not yet support TX
[Sony Cross-Device General] [NUT]:
Ask your ROM dev what he did to the original chargemon binary to find out how to fix your ROM. Because this offline charge function should still work if he did it right.

So... what do you think my next answer will be?
[Sony Cross-Device General] [NUT]:
adb push busybox /data/local/tmp/busybox
adb push byeselinux\byeselinux.sh /data/local/tmp/byeselinux.sh
adb push byeselinux\byeselinux.ko /data/local/tmp/byeselinux.ko
adb push byeselinux\modulecrcpatch /data/local/tmp/modulecrcpatch
adb shell
su
cd /data/local/tmp/
chmod 755 busybox
chmod 755 byeselinux.sh
chmod 755 byeselinux.ko
chmod 755 /modulecrcpatch
./byeselinux.sh
./busybox tail -n 300 /proc/kmsg > kmsg

It's not that complicated :p
[Sony Cross-Device General] devilmaycry2020:
Are you kidding me ? :)

The question is clearly enough. The answer is make dual recovery support Cm12, overwrite TWRP integrated in the kernel
[Sony Cross-Device General] [NUT]:
So, you'll have to wait until I do :p
[Sony Cross-Device General] boilavera1980:
But i couldn't boot into TWRP! It just didn't work. I spammed volume up like a idiot, only on volume down it let me into recovery but philz one. Since i don't like that i changed the default one to TWRP and it worked. I messed nothing up, didn't mention something like that after I changed the line.

It messed up the first time after i flashed the newest version, something borked really up and i think i now know why. But whatever, did a super clean flash, relocked the device since i wanted stock and flashed myself a custom FW, Now everything is fine.
[Sony Cross-Device General] cashflow67:
I did it man :D I rebooted to philz in ndr utils, then I rebooted to system. Then I rebooted to twrp in ndr utilis, then I flashed your 2.8.14 flashable.zip, then I rebooted to recovery, now I have 28.14 dual recovery and twrp 2.8.6.0 :D

I dont know what happened between recovery switches but it worked :D
[Sony Cross-Device General] [NUT]:
[MENTION=5970477]pvnsai73[/MENTION] and [MENTION=6389135]Renmazuo[/MENTION]

I just realised I made a mistake in the very first guide already... Please make sure you are using /data/local/tmp/recovery instead of /data/local/tmp. Before you follow the last version of my guide I wrote to [MENTION=5970477]pvnsai73[/MENTION] adb shell and type:

mkdir /data/local/tmp/recovery

This creates the appropriate directory.

I modified the installer scripts to use that path... So a big chance is that the first version failed because of that.
[Sony Cross-Device General] ondrejvaroscak:
you need rooted phone to install recovery
[Sony Cross-Device General] Svarojitch:
I've already rooted my phone with easyroottool and installed SuperSu
[Sony Cross-Device General] ondrejvaroscak:
open adb and remount /system rw
[Sony Cross-Device General] Svarojitch:
How can I do that ?
[Sony Cross-Device General] ondrejvaroscak:
holy cow....

open adb and type:

su

mount -o remount,rw /system
[Sony Cross-Device General] Svarojitch:
Ok, i've done what you said and i still have the same "mkdir: can't create directory blabla". How can i check if my phone is realy on rw mode ? Because when i type the command "mount -o remount,rw /system" and press return, nothing happen
[Sony Cross-Device General] ondrejvaroscak:
type just "mount" and you will see list of mounted partitions. if your root is OK system will be listed last after you remounted it rw.
[Sony Cross-Device General] Renmazuo:
It seems like the byeselinux module installed successfully after we pushed the files to the tmp/recovery folder. No boot to recovery yet, however. Log:

c:\ldr\files>adb push busybox /data/local/tmp/recovery/busybox
3002 KB/s (719520 bytes in 0.234s)

c:\ldr\files>adb push byeselinux\byeselinux.sh /data/local/tmp/recovery/byeselin
ux.sh
264 KB/s (1357 bytes in 0.005s)

c:\ldr\files>adb push byeselinux\byeselinux.ko /data/local/tmp/recovery/byeselin
ux.ko
2264 KB/s (30148 bytes in 0.013s)

c:\ldr\files>adb push byeselinux\modulecrcpatch /data/local/tmp/recovery/modulec
rcpatch
1895 KB/s (13592 bytes in 0.007s)

c:\ldr\files>adb shell
shell@D5322:/ $ su
su
root@D5322:/ # echo "0" > /sys/fs/selinux/enforce
echo "0" > /sys/fs/selinux/enforce
root@D5322:/ # cd /data/local/tmp/recovery
cd /data/local/tmp/recovery
root@D5322:/data/local/tmp/recovery # cd /data/local/tmp/recovery
cd /data/local/tmp/recovery
root@D5322:/data/local/tmp/recovery # chmod 755 busybox
chmod 755 busybox
root@D5322:/data/local/tmp/recovery # chmod 755 byeselinux.sh
chmod 755 byeselinux.sh
root@D5322:/data/local/tmp/recovery # chmod 755 byeselinux.ko
chmod 755 byeselinux.ko
root@D5322:/data/local/tmp/recovery # chmod 755 modulecrcpatch
chmod 755 modulecrcpatch
root@D5322:/data/local/tmp/recovery # ./byeselinux.sh
./byeselinux.sh
Module installed succesfully.
root@D5322:/data/local/tmp/recovery # ./busybox tail -n 300 /proc/kmsg > kmsg
./busybox tail -n 300 /proc/kmsg > kmsg

I've attached the kmsg created during the procedure. Thanks for the support man.
[Sony Cross-Device General] pvnsai73:
Yup the module installed successfuly

---------- Post added at 06:01 AM ---------- Previous post was at 06:01 AM ----------

@[nut]
[Sony Cross-Device General] [NUT]:
even though some stuff didn't work as intended, from what I see it should still work OK. Recovery isn't working after this? You seem to have no sdcard inserted, is that correct?
[Sony Cross-Device General] [NUT]:
[MENTION=5970477]pvnsai73[/MENTION], I will need that kmsg log still... because the one [MENTION=6389135]Renmazuo[/MENTION] attached is so freaking weird I need to cross-reference it with yours to make heads or tails from the one he sent... There is so much garbage in the kmsg that I wonder how Sony even got the device to boot with this kernel :eek:

Please, PLEASE also give me a zipped up copy of your /system/lib/modules folder, because I need them to to reference stuff from the modules present on your devices.

Also, as the module installation succeeded, please follow the next guide to see what happens (again, use a CMD window and go to the files directory to execute it):

adb push busybox /data/local/tmp/recovery/busybox (only if you previously removed the recovery folder or tried to use the installer again!)
adb shell
su
cd /data/local/tmp/recovery
chmod 755 busybox
busybox lsmod
busybox insmod /system/lib/modules/byeselinux.ko
busybox lsmod

And then please copy and paste the output here.

[MENTION=5970477]pvnsai73[/MENTION] I need your output as well, the same way as [MENTION=6389135]Renmazuo[/MENTION] does, because I need both your output logs to cross-reference the outcome or results, just a 'yes that worked' or a 'the module installed correctly' is not enough...
[Sony Cross-Device General] Renmazuo:
I believe that kmsg is really messed up. It takes too long to copy to sdcard0, and ends with this weird file when i cancel the copy operation. I grabbed another one, and i'm going to let it stay a few hours copying the file (:silly:)

I've tried the new guide, but something happened during insmod.

c:\ldr\files>adb shell
shell@D5322:/ $ su
su
root@D5322:/ # cd /data/local/tmp/recovery
cd /data/local/tmp/recovery
root@D5322:/data/local/tmp/recovery # chmod 755 busybox
chmod 755 busybox
root@D5322:/data/local/tmp/recovery # busybox lsmod
busybox lsmod
Module Size Used by Tainted: G
wlan 3718156 0
wp_mod 12580 0 [permanent]
root@D5322:/data/local/tmp/recovery # busybox insmod /system/lib/modules/byeseli
nux.ko
usybox insmod /system/lib/modules/byeselinux.ko <
insmod: can't insert '/system/lib/modules/byeselinux.ko': Invalid argument
22|root@D5322:/data/local/tmp/recovery # busybox lsmod
busybox lsmod
Module Size Used by Tainted: G
wlan 3718156 0
wp_mod 12580 0 [permanent]
root@D5322:/data/local/tmp/recovery #

I've attached both lib/modules folder and kmsg below. Maybe this update is just messed up after all. The same lollipop update was released to C3 Dual, with no complaints so far...
[Sony Cross-Device General] [NUT]:
You know what, try the full guide (the first part and the second part too, after each other) once more and instead of using 'busybox tail -n 300 /proc/kmsg', use 'dmesg > kmsg' and then attach that kmsg file. Maybe busybox' tail applet fubars the output...

But from what I see here, it seems the module patch succeeds and fails at the same time, that's why I needed a copy of the modules folder and the insmod information to troubleshoot this.
[Sony Cross-Device General] pvnsai73:
usybox insmod /system/lib/modules/byeselinux.ko <

insmod: can't insert '/system/lib/modules/byeselinux.ko': Invalid argument

Here is the kmsg

https://docs.google.com/file/d/0BxAHIwYT1eNlaE9SMzFJZ3RZUlk/edit?usp=docslist_api
[Sony Cross-Device General] [NUT]:
*sigh*

Why don't you post the entire output from the CMD window?! It contains info I need...
[Sony Cross-Device General] pvnsai73:
root@D5322:/data/local/tmp/recovery # busybox lsmod

Module Size Used by Tainted: G

wlan 3718156 0

wp_mod 12580 0 [permanent]

usybox insmod /system/lib/modules/byeselinux.ko <

insmod: can't insert '/system/lib/modules/byeselinux.ko': Invalid argument

22|root@D5322:/data/local/tmp/recovery # busybox lsmod

Module Size Used by Tainted: G

wlan 3718156 0

wp_mod 12580 0 [permanent]

root@D5322:/data/local/tmp/recovery #

Is this ok
[Sony Cross-Device General] [NUT]:
It's not all I need, but it will do for now.
[Sony Cross-Device General] joseangel.alv:
Beware the fury of a patient man! :p
[Sony Cross-Device General] Pandemic:
[MENTION=4904057][NUT][/MENTION]

I have found an issue finally with cwm recovery:

My settings are gone and Xperia Home when i restore my back up, howto fix that !

Edit:

Nevermind, solved :)
[Sony Cross-Device General] kamalmawa:
I deleted XDdualRecovery folder from SD card and not I can't enter the recovery neither can I boot to the system due to exposed. Can anyone share their XdualRecovery folder from the SD card ? Thanks

Update: Never mind it's get created, something else prevents it from going to recovery.. Edited XZDR.prop values manually on SDCARD using notepad all good now