yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Android Development] Farv4:
I got the same problem, can't boot into recovery. For me the LED does change to yellow for a few seconds.

I also tried flashing the recovery I used before (twrp 3.0.2) seperately, but with the same result.

- Unpacking kernel

Found elf boot image

Kernel version: 3.10.84-perf-gf1cfa5f

Found appended DTB

- Detected vendor: somc (Sony), device: sumire (Xperia Z5), variant: row

- Unpacking initramfs

- Detected platform: 64-bit

- Detected Android version: 6.0.1

- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] Y

Disabling dm-verity

- Sony RIC is enabled. Disable? [Y/n] N

- Install TWRP recovery? [Y/n] Y

Installing TWRP

Compressing TWRP image

- Install busybox? [Y/n] N

- Found SuperSU-v2.74-2-20160519174328.zip. Install? [Y/n] Y

Stripping SuperSU app

Adding service entry for SuperSU

- Install DRM fix? [Y/n] Y

- Creating new initramfs

- Creating boot image

- Cleaning up

Done
[Xperia Z5 Android Development] tobias.waldvogel:
And what happens when you press volume up when the LED turns yellow?

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] KbaB.BroS:
Are you pressing the volume buttons when the LED becomes yellow?
[Xperia Z5 Android Development] Farv4:
Yes, Volume up or when I try to reboot to recovery via adb. Otherwise the LED does not turn yellow.
[Xperia Z5 Android Development] KbaB.BroS:
It's yellow when you're supposed to press and becomes orange when it's entering the recovery.
[Xperia Z5 Android Development] Farv4:
Oh, my bad. Before i could reboot into recovery via adb without pressing the volume button. Thank you!
[Xperia Z5 Android Development] Klaus N.:
The reason, why this isn't possible with rc1, was already explained by Tobias here.
[Xperia Z5 Android Development] xtacy!:
Thanks tobias and the rest who helped. I think I didn't press the volume up key at the right time. And my second question regarding why I could only enter TWRP manually instead of sending a command has been answered above (I'm using v5.0_rc1).
[Xperia Z5 Android Development] tobias.waldvogel:
It is written in the very first post in the FAQ section. Please take at least the time to read the section "Please read" ;)

In RC1 I did not evaluate the boot command line anymore in order to leave it to Sony FOTA upgrade, but as the OTA upgrade does not work anyway I added the option now in RC2 again.

Anyway personally I consider it pretty useless to use the command if you can enter recover just by pressing volume up.

RC2 includes a lot of work on the system-less xposed. There were issues in the past, especially on 32bit devices (like reboots or illumination not turning off).

The background is that I am using now a new integration method for drmfix, system-less xposed and system-less SuperSU. As a consequence the libraries are loaded into all processes, which is good, especially for the drmfix. But it requires at lot of extra effort to eliminate every dependency in these libraries.

RC2 should now work stable. I'm using it on a 32bit tablet Z2 and Z5 Dual without any issues.
[Xperia Z5 Android Development] Klaus N.:
I confirm v5 rc2 works both on windows10 and linux; on my E6653 everything works - no issues recognized.

Thank you very much, Tobias!
[Xperia Z5 Android Development] WildBit:
Had to roll back to rc1 for SU problems
[Xperia Z5 Android Development] tobias.waldvogel:
It would be helpful if you could describe which kind of problems you had and which version of SuperSU you used.

I am using SuperSU 2.76 on two different devices without any issues.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] chibikit0:
Z5 Compact (E5803) running firmware 32.2.A.0.253 here. I generated a kernel using rc2 with the following options:

- dm-verity off

- RIC on

- TWRP installed

- SuperSU installed

- drmfix installed

- busybox not installed

and also generated and flashed a DK.ftf using a TA backup that I know works (tested using relock previously).

Under the Security tests, MARLIN, WIDEVINE and CKB all show "[Key OK] [Active]". However, FIDO_KEYS still shows "Not provisioned, provision failed".

EDIT: This problem also appeared under rc1. I haven't tested the older versions yet.

Am I doing something wrong?
[Xperia Z5 Android Development] tobias.waldvogel:
5.0rc3

I just recognized that 5.0rc2 had an issue with the busybox installation related to a SE Linux rule.

I fixed this rule in 5.0rc3.
[Xperia Z5 Android Development] tobias.waldvogel:
I would imagine that your problem was not SuperSU but busybox related. You may want to try 5.0rc3
[Xperia Z5 Android Development] abdak55:
I think the FIDO KEYS are related to the choice in dev mod about oem unlock.

I checked before deactivating and after and the keys are back. You need to reboot after modifying the choice.

I'm on z5 .200 LP, androplus kernel, and used this tool for drm fix with my own keys.
[Xperia Z5 Android Development] chibikit0:
Turned it on and rebooted, then turned it off and rebooted. Still no change both times.

Do you mean that the OEM unlock option should be off before I flash the kernel or something?
[Xperia Z5 Android Development] RyTekk:
You defined any keys for Yes and N key for No. right?
[Xperia Z5 Android Development] ratelutz:
installation supersu failes with rc3

Hi i repacked the kernel with rc3. When i try install SuperSU using TWRP it give me the error:

- BAD RECOVERY DETECTED, NO UNZIP, ABORTING

Update process ended wit ERROR: 1 ERROR installing zip file ......

any idea?
[Xperia Z5 Android Development] tobias.waldvogel:
My apologies. TWRP uses absolute paths to /sbin.

Corrected int RC4 ( Busybox is now installed back in /sbin)
[Xperia Z5 Android Development] ratelutz:
confirmed: flash supersu workes again with rc4
[Xperia Z5 Android Development] Nown:
Hi, I am having some trouble here... I rooted .253 on my Z5C with rc4, SuperSU-v2.76-20160630161323, RIC: enabled, dm-verify: enabled, busybox: no, TWRP: yes, drmfix: yes.

(BTW: It would be great if your script wrote a log file every time)

I flashed and everything booted fine at first (supersu working, all nice). Then, I booted TWRP to see if it worked. I did nothing in it, and tried to reboot the system. Now, I am stuck forever on the white "Sony Xperia" screen. I tried rebooting a few times, wiped cache, etc. I can still boot TWRP but not the system... Any idea?

Update: more info: I flashed everything on top of a .224 kernel rooted with v4.51 of this script.
[Xperia Z5 Android Development] chibikit0:
Redo the process, but this time disable dm-verity.
[Xperia Z5 Android Development] pw1nce:
hey bro im also stuck , can you pls tell me step by step on how to do this all ? or you have team viewer to remotely do for me? i have lp n mm both fw's and ta backup too , thnx

---------- Post added at 02:15 PM ---------- Previous post was at 01:56 PM ----------

can someone help me witha video tutorial if possible or help me via team viewer remotely? ill be so grateful , i cant go past extracting kernal.elf
[Xperia Z5 Android Development] tobias.waldvogel:
You should better use the stock kernel as a base, just in case. But your issue actually sounds like TWRP has modified something in /system, which breaks dm-verity. In this case you may try to disable dm-verity as recommended before.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] Nown:
Thanks a lot for the answer, Tobias. The kernel I rooted was extracted from the stock version .253, and this is also the version I flashed with flashtool before fastboot-flashing the modified kernel. Is this not what we are supposed to do? When I mentioned flashing on top of a rooted .224 system, I meant that this was the system I had installed before upgrading to .253.

I will disable dm-verity as you both suggest. However, this is a little disturbing, because I don't see any reason why TWRP should have modified anything on my system partition...
[Xperia Z5 Android Development] chibikit0:
When you start TWRP, there's a screen where you are given the option of either pressing a button and leaving system unmounted/read-only, or swiping a bar and mounting it as writeable. If you did the latter, maybe TWRP mounting system as writeable was enough to trigger dm-verity?
[Xperia Z5 Android Development] RyTekk:
I think you had better force dm-verity to be disabled by default, no need a question for it. Btw, can you add enabling for adb debugging and insecure?
[Xperia Z5 Android Development] WildBit:
You´re absolutely right man, sorry for not explaining. It was late and probably should have gone to bed... I always use the last available stable version so in this case we´re talking 2.76. I only have had that issue with RC2, all others by reflashing supersu through recovery but not with rc2. Anyway, I´m on rc4 and everything is cool. Been using your scripts since the start and decided to help out the project with a paypal donation.

Thanks for your gr8 work, I have a advanced stock kernel the same day the fw gets released, That´s Impressive! :good:
[Xperia Z5 Android Development] mhaha:
Hi, I'm unable to install busybox with rc3 nor rc4. In both cases, I get a message that says installation was unsuccessful, then the app force closes.

On the main install page in the busybox app, a message states "Free space unavailable for /su/bin"

Z5 compact E5823, stock 32.2.A.0.224 downloaded with XperiFirm

Using stock kernel extracted from stock ROM, config:

dm-verity disabled

Sony RIC disabled

TWRP installed

SuperSU 2.74 BETA installed

busybox not installed

DRM-fix enabled
[Xperia Z5 Android Development] palmacas:
DRM Fix on Z5C

So, I run the script and obtained this log:

------------------------------------------------------------------------------------------------

Z:\Downloads\rootkernel_v4-2>rootkernel kernel.elf boot.img

- Unpacking kernel

Found elf boot image

Kernel version: 3.10.84-perf-gf1cfa5f

Found appended DTB

- Detected vendor: somc (Sony), device: suzuran (Z5C), variant: row

- Unpacking initramfs

- Detected platform: 64-bit

- Detected Android version: 6.0.1

- Disabling dm-verity

- Sony RIC is enabled. Disable? [Y/n] N

- Install TWRP recovery? [Y/n] Y

Installing TWRP

- Install busybox? [Y/n] N

- Install DRM fix? [Y/n] Y

Configuring keyprovd

Configuring tpm-service

Configuring credmgrd

Configuring secd

Configuring wvkbd

Configuring drmserver

- Creating new initramfs

- Creating boot image

- Cleaning up

Done

------------------------------------------------------------------------------------------------

Then flashed the boot image and everything works fine. Now my Z5C (E5823) runs 32.2.A.0.253 firmware and has all the Sony functionalities back.

Thanks tobias!

PD: Why I still get "FIDO_KEYS: Not provisioned, provision failed"?
[Xperia Z5 Android Development] tobias.waldvogel:
/su is in the init ramdisk and not writable. If you want busybox then the easiest way is just to use the option in the script. In most cases busybox is installed anyway and just deleted during boot if you select no. [emoji6]

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] tobias.waldvogel:
Do you have TA backup and used flash_dk? If not FIDO keys will not work.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] tobias.waldvogel:
Thanks for your support [emoji2]

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] wd121366:
can you make kernel for X Performance ,this twrp can't work for X Performance,but root and other work ok. Thank you ,I'm chinese,my english is not good.
[Xperia Z5 Android Development] tobias.waldvogel:
What happens when you try to enter TWRP?

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] wd121366:
when I enter the twrp,the screen was black,and the screen flicker and the screen had dark light.But I can't enter the twrp.
[Xperia Z5 Android Development] KbaB.BroS:
[MENTION=357342]tobias.waldvogel[/MENTION]

Any way to make a kernel bootable with another recovery than the included one? Or can you please fix this issue I have?

The recovery installed with the script won't allow me to flash Xposed sysless 86.2. Even though I have installed SU 2.76 (tried from both the recovery and the script) Xposed doesn't notice SU installed and gives me an error 1. I also need XtremeMusic which is sysless dependent and this also doesn't work. When I tried other separate recoveries sysless worked fine. I'm suspecting the sysless method most files use doesn't support the way you've modified it.

Tried all your scripts from beta10 and forward.

My device is E6853.

Edit:

Ramdisk by Androplus works according to two users.
[Xperia Z5 Android Development] riedenthied:
You could use romracer's sysless v86. Works fine.
[Xperia Z5 Android Development] KbaB.BroS:
But XtremeMusic won't so I'm still stuck at square one. Seems like this recovery can't take advantage of the new sysless method in SU 2.76. The Xposed sysless 86.2 and XtremeMusic tries to take advantage of this. Xposed sysless 86.1 worked fine but that doesn't make use of the method in SU 2.76.
[Xperia Z5 Android Development] riedenthied:
I started to analyse this some days ago. The problem is this version check in the 86.2 installer script. If I try to run /su/bin/su -v from TWRP's console it shows me an error message about a missing 32 bit library or so. If I try to run it with ADB it works.

However, I installed the systemless Xposed v86 build from romracer which doesn't have such version check things. For me it works like a charm with 2.76.
[Xperia Z5 Android Development] palmacas:
No, I don't have a backup. Your DRM fix works well for me.

Just for general knowledge: What does the FIDO Keys do?
[Xperia Z5 Android Development] tobias.waldvogel:
I'm sorry but without TA backup there is currently no way to make them work. As far as I know they can be used for two factor authentication for certain services.

But all important things like x-reality, camera de-noise etc work

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] tobias.waldvogel:
Well, the actual idea is using the system-less xposed feature provided by the script itself. It works with the standard xposed installer zip.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] osm0sis:
tobias, [MENTION=4675598]shoey63[/MENTION] and I were experimenting with the new unpackelf in the recent bootimg binary you included in the rc builds and found it's not dumping usable offset values when it unpacks; it's dumping the raw header addresses rather than the computed (address - base = offset) value that mkbootimg requires to generate a booting standard image.

Please see unpackbootimg for the calculation of base and then the offsets from that. Any chance you'd be able to fix this and output the base as well so we'll have everything required for mkbootimg?

Do you have any feedback on the issue with the older ELF+RPM images I reported back here?

I'm also still hoping you'll upload the latest unpackelf source to your GitHub like you'd mentioned so I can clone and cross-compile more easily. You've very nearly got a universal ELF unpacker here and it's fantastic! :)
[Xperia Z5 Android Development] tobias.waldvogel:
Thanks for your input. [emoji6] I'm currently on a business trip but next week I will fix that and publish it. I already created a github repository for that.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] austinsilvester:
Hi [MENTION=357342]tobias.waldvogel[/MENTION],

thanks alot for this tool. i've got a small issue. im unable to create DK.ftf from the backed up TA partition. i tried using all versions, but didnt have any success. this is the error im getting.
[Xperia Z5 Android Development] RyTekk:
I wonder if your tool cause "libselinux returns unknown state" since I search on Google and most results give back to busybox.
[Xperia Z5 Android Development] tobias.waldvogel:
Well, sestatus is a busybox command.

What are you looking for anyway?

busybox is statically linked against libselinux and it seems that it doesn't the current SELinux version. Therefore it doesn't report it.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] sandeep121sp121:
What is the issue ??

I have installed latest superuser 2.76

Rc4
[Xperia Z5 Android Development] tobias.waldvogel:
How did you install it? With the integration of the script? Did you try to use su from a terminal?

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] sandeep121sp121:
No, i did not try terminal .i put the supersu zip to the kernel folder and it was integrated in the boot.img.

Should i try to flash superSU.zip manually ???
[Xperia Z5 Android Development] tobias.waldvogel:
No, the idea is to include it with the script.

Did you install the SuperSU app before already at some time? In that case you may try to uninstall it.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] sandeep121sp121:
Yes, actually i tried old boot.img from firmware .224. and it was working fine but i notice fast battery drain.

So i tried this , but failed to get root access. With the version rc1 everything was fine but i failed to mount sytem r/w.

And should i uninstall superuser and flash it again?

What you suggest?
[Xperia Z5 Android Development] Klaus N.:
Yes, try to uninstall SuperSU and fastboot flash the boot.img. If you followed the script in the startpost, SuperSU is already included in the boot.img; you don't have to flash it separately.
[Xperia Z5 Android Development] sandeep121sp121:
Yes bro. I know that its already included in the boot.img , but i m asking about reflashing superuser solve the problem or not.

Hope u understand.
[Xperia Z5 Android Development] Klaus N.:
No, uninstall SuperSU and flash the boot.img after via fastboot.
[Xperia Z5 Android Development] RyTekk:
Hmm, I did enable permissive mode in both config and cmdline when build kernel, but dunno why selinux status is enforcing. It's strange.
[Xperia Z5 Android Development] tobias.waldvogel:
Android init initialises SELinux and sets it to enforcing as far as I remember. But why do want to set it to permissive for normal operation? This is really dangerous

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] RyTekk:
Yah, I don't know what I want from permissive mode :laugh:, I just wonder whether your tool cause it.
[Xperia Z5 Android Development] tobias.waldvogel:
Anyway if you need permissive mode at any time you can just run setenforce 0 at any as root

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] pikakolendo:
It's a nice tool. Thanks.

However when I patched the stock lollipop kernel (3.10.49) of z5c it said

Skipping TWRP recovery. No kernel modules for 3.10.49-perf-g75e6207 available

And there's no yellow LED at booting.

I'm a bit sad.:crying:
[Xperia Z5 Android Development] KbaB.BroS:
For people having problem regarding sysless method in SU 2.76 and TWRP recovery.

I managed to flash Xposed sysless 86.2 using Flashfire instead of TWRP recovery included here.
[Xperia Z5 Android Development] tobias.waldvogel:
Well Lollipop is already outdated some time. You might want to update to 6.0.1

Which firmware version are you using exactly?
[Xperia Z5 Android Development] tobias.waldvogel:
Did you try to integrate SuperSU and xposed via the script? It integrates both into the booimg.

If you flash SuperSU from recovery it creates a new filesystem as overlay and a malicious program could add/modify this filesystem.

If you integrate it via the script it is completely read-only, which is much more secure. Of course you need to repack the kernel again if you want to update SuperSU or xposed, but honestly I did not see any reason to update it lately other than for the sake of updating it. ;)
[Xperia Z5 Android Development] KbaB.BroS:
How do I install Xposed via the script? Haven't quite understood that part.
[Xperia Z5 Android Development] tobias.waldvogel:
Just place the normal xposed install zip in the same folder and you will be asked.

Gesendet von meinem E6683 mit Tapatalk
[Xperia Z5 Android Development] riedenthied:
Do I have to uninstall Xposed and SuperSU that I flashed with TWRP? Or do I have to do a full flash again?
[Xperia Z5 Android Development] Klaus N.:
Uninstall SuperSU, then reboot into recovery and flash the proper xposed-uninstaller-20150831-xxx.zip before fastboot flash the boot.img.
[Xperia Z5 Android Development] pikakolendo:
I've just downgraded to lollipop from mm, for a game went wrong in mm.

Exactly I'm using 32.0.A.6.200.
[Xperia Z5 Android Development] devilmaycry2020:
Hi all

Which is the correct folder to install busybox. This tool integrated busybox to vendor/bin but updater-script seem using "/sbin/busybox" to mount something. please help. thank you.
[Xperia Z5 Android Development] dr4go:
@ tobias: Thanks for the awesome work.

Cheers. :) 9B372286Y9305070Y
[Xperia Z5 Android Development] nabeelrazanaqvi:
where can i download it?

---------- Post added at 06:46 AM ---------- Previous post was at 06:42 AM ----------

where can i find rc1 ?

thanks in advance
[Xperia Z5 Android Development] KbaB.BroS:
RC4 as of now is the latest one so download that.
[Xperia Z5 Android Development] nabeelrazanaqvi:
where can i find that i can not find the link can you post please

thanks in advance
[Xperia Z5 Android Development] KbaB.BroS:
Did you check the OP? Because the download links are there.
[Xperia Z5 Android Development] nabeelrazanaqvi:
sorry i am new to this i dont know about OP can you guide me please

thanks in advance
[Xperia Z5 Android Development] sandeep121sp121:
Go to the first page and see at the bottom of the first post.
[Xperia Z5 Android Development] nabeelrazanaqvi:
Edit : I have found it thanks again dear
[Xperia Z5 Android Development] xerxess:
this is work for z5 dual sim?
[Xperia Z5 Android Development] RyTekk:
It does, next time before you intend to ask a question, remember to use the search box.
[Xperia Z5 Android Development] xerxess:
sory dont want to be rude, but i did research before i post..

maybe not enough..

btw thank you
[Xperia Z5 Android Development] AforAnonymous:
Any chance you could add support for the M4 Aqua? It's not a Z series phone, but due to the newly shared base in Marshmallow, I suspect it would not be much effort.

dtbinfo from the M4 Aqua MM image for the E2303 variety:

DTB_model="Qualcomm Technologies, Inc. MSM 8916 CDP"

DTB_compatible="qcom,msm8916-cdp"

a MM compatible TWRP recovery.img for the M4 Aqua can be found here: http://xdaforums.com/m4-aqua/general/dev-start-developing-m4-t3311715/post67203931#post67203931
[Xperia Z5 Android Development] WildBit:
Well, ran into an isolated issue using the DRM key emulation. I´ve just gained access to Eir Sports through my broadband subscription and I get an error from it after launch. "error generating DRM license for your device". I believe this is the first time running into problems and not sure if it can be fixed or not.

I´m willing to test options if they exist but it´s not a deal breaker :)
[Xperia Z5 Android Development] KbaB.BroS:
Those are what your FIDO keys exist for if I'm not wrong. Unfortunately they aren't emulated by this script and the only way to make them work is having your TA backup. That's why this tool has an option to include your TA in the modded kernel.
[Xperia Z5 Android Development] WildBit:
I have the original TA backup and unless you´re are talking about restoring your original TA partition and re-locking the boot loader, I see no other solution since I´ve been using Tobias script since it was first released. It´s the only app that has given problems
[Xperia Z5 Android Development] KbaB.BroS:
Did you also use flash_dk?
[Xperia Z5 Android Development] WildBit:
but of course... as mentioned it's the first app that gives some kind of drm problems, still very impressive in my opinion
[Xperia Z5 Android Development] KbaB.BroS:
You know your things, I'm sorry for asking these questions. Seems like that app doesn't like Sony, but seriously, no idea what it might be then.