[Xperia Z4/Z3+ General] Sacktreter:
Hi [MENTION=410007]Nut[/MENTION]

sorry for late answer but I have wife, family, dog, a job and I'm a newbie at recovery. :D

your scripts i changed to Z3+ path's working. I took the path

"/dev/block/bootdevice/by-name/" rather than this "/dev/block/platform/f9824900.sdhci/by-name/" for better compatibility.

During installtion when installrecovery.sh runs an error message appears at cmd window. Here is part of installrecovery.sh line 168 - 177.

I changed your script, because there is needed unload kernel only when kernel was loading before.

And here are questions:

1. When byeselinux.ko is not installed yet (first installation and byeselinux.ko is not in phone) is it possible to start byeselinux.ko right after install it for test?

2. When byeselinux.ko is already installed at phone and i do a 2nd or later installation, why can't insmod insert byeselinux.ko and why can't start it? Origin message: "That module is not accepted by the running kernel, will replace it now."

Is this maybe 64 bit? Take a look at the scripts and logs

[COLOR=SeaGreen]# Beginn at line 168 - installrecovery.sh [/COLOR]
echo "The byeselinux module exists, testing if the kernel accepts it."
${BUSYBOX} insmod /system/lib/modules/byeselinux.ko
[COLOR=Blue]if[/COLOR] [ "$?" != "0" -a "$?" != "17" ]; [COLOR=Blue]then[/COLOR]
echo "That module is not accepted by the running kernel, will replace it now."
${BUSYBOX} chmod 755 /data/local/tmp/recovery/modulecrcpatch
${BUSYBOX} chmod 755 /data/local/tmp/recovery/byeselinux.sh
/data/local/tmp/recovery/byeselinux.sh
[COLOR=Blue]fi[/COLOR]
--> [COLOR=DarkRed]/system/bin/rmmod byeselinux[/COLOR]
[COLOR=Blue]fi[/COLOR]
[COLOR=SeaGreen]#End at line 177[/COLOR]

MY SUGGESTION

[COLOR=SeaGreen]# Beginn at line 168 - installrecovery.sh[/COLOR]
echo "The byeselinux module exists, testing if the kernel accepts it."
${BUSYBOX} insmod /system/lib/modules/byeselinux.ko
[COLOR=Blue]if[/COLOR] [ "$?" != "0" -a "$?" != "17" ]; [COLOR=Blue]then[/COLOR]
echo "That module is not accepted by the running kernel, will replace it now."
${BUSYBOX} chmod 755 /data/local/tmp/recovery/byeselinux.sh
${BUSYBOX} chmod 755 /data/local/tmp/recovery/modulecrcpatch
/data/local/tmp/recovery/byeselinux.sh
[COLOR=SeaGreen]# BOF - @sacktreter - to avoid wrong error message[/COLOR]
[COLOR=Blue]else[/COLOR]
[COLOR=DarkRed]/system/bin/rmmod byeselinux[/COLOR]
[COLOR=Blue]fi[/COLOR]
[COLOR=SeaGreen]# EOF - @sacktreter - to avoid wrong error message[/COLOR]
[COLOR=Blue]fi[/COLOR]
[COLOR=SeaGreen]#End at line 177[/COLOR]

Here is part of the log in the cmd-window when byeselinux.ko already exists in phone

Log-file of install.bat[COLOR=SeaGreen]...
##########################################################
#
# Installing XZDR version 2.8.21 RELEASE
#
#####[/COLOR]

Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
The byeselinux module exists, testing if the kernel accepts it.
[COLOR=Red]insmod: can't insert '/system/lib/modules/byeselinux.ko': invalid module format
That module is not accepted by the running kernel, will replace it now.
Module installed succesfully.
rmmod: delete_module 'byeselinux' failed (errno 2)[/COLOR]
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Copy init's *.rc files in to /system/.XZDualRecovery.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
XZDualRecovery will unload byeselinux every boot.
Speeding up backups.
...

In my opinion the lzma-file is the problem. But i didn't find a way to log the init process.

I made so many things: correct the rights, owner, checked the files in recovery with mine in phone, changed them to test, compared default.prop und build.prop with mine in phone and so on.

I installed VM virtualbox with Linux to be able to give pemissons and rights in the right way, to build gpio-lzma-file in Linux and endless more.

For me it was funny to test, not for my wife. But not even one time successful is hard.

Now i made logfiles for you. Sorry for uploadnet, but i dont have any other account for upload files. Now i got this message from xda:

"ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. "

Download (put the 2 pieces into one internetadress): http (+) ://ul.to/cw3ed00w

I hope together we can get recovery but its a hard way. :good: :)