No su (N/A) despite patched boot.img successfully flashed (Philips TPM191E)

[classiphil]

Device: Philips TV 50PUS8535/12 (TPM191E same as @fusebyte #6427)
Android version: 9 & 11.0 (Android TV)
Magisk version name: 22000 - 27002
Magisk version code: 27002

logcat | grep magisk
Ignoring /data/data/com.topjohnwu.magisk/lib with unexpected GID 0 instead of 10115

I patched the vbmeta with the fastboot command. I have a/b Slots and always patch both. Booting fine. No boot loops. But no "su" in /sbin or elsewere, afaik.

boot-patch.log
log.txt
magisk_log_2024-06-29T12.06.47.log
orig.tar.gz
27002_bootpatch.log 81658d4

Does it matter, that Magisk announces the platform "armeabi-v7a" when altering the boot.img but my uname -a shows "armv8l"?

cat /proc/cpuinfo
processor : 0
model name : ARMv8 Processor rev 2 (v8l)
Processor : AArch64 Processor rev 2 (aarch64)

... yeah... good old Mediatek ...

[yujincheng08]

need bugreport as soon as your device boots.

[classiphil]

Thanks yujincheng08.
I hope I generated them correctly. Directly after boot.
bugreports.tar.gz

[classiphil]

Does anyone see, what is going on? I've tried all firmwares for the TV now, combined with every Version of Magisk since V22. Thanks for taking a look into it.

[BlankFX1]

This appears to be a more frequent issue recently.
I just updated LineageOS on my Samsung A52s (model SM-A528B) and got the exact same issue after properly sideloading the patched boot.img.

A few weeks ago, when I had installed LOS and Magisk for the first time (new phone), everything went smooth.

Another user on XDA seems to have the issue too: https://xdaforums.com/t/guide-magisk-on-lineageos.4371987/#post-89765140

bugreport-a52sxqxx

[timothy-b]

Make sure you don't have a previous installation of Magisk installed and hidden with Magisk Hide. That's what tripped me up when I updated LineageOS across major versions.

[BlankFX1]

I didn't use Magisk Hide and only auto-updated LOS from a small regular Update within LOS 21.
Of course I had Magisk itself installed before the minor Update. Is that an issue?
AFAIK the LOS Update overwrites Magisk and only leaves behind the App.

//Edit: I was able to use the custom recovery method, although I didn't like having to go this way.
Renamed the apk, used LOS Recovery to patch it in and was asked by Magisk to re-install it again from inside the App.
Worked fine, at least this time.