Magisk v21.4 wipes boot-appended vbmeta, unbootable on Unihertz Titan (and other Mediatek devices with Android 10)

[ValdikSS]

Unihertz Titan does not have dedicated vbmeta partition, Android 10 image on this device has vbmeta appended to boot.img, which is padded to partition size.

Magisk Manager 8.0.7 (4832), upon Magisk 21.4 (21400) installation, wipes vbmeta header and footer from boot.img on this device, making it unbootable.
Magisk Manager does not offer to preserve dm-verity on this device, and the log file does not contain any strings regarding AVB (as it was with Android 9 on this device).

Adding blank vbmeta with disabled verification manually into the patched image allows device to boot again.

Please check the following archive with three files:

• boot_10.img — original boot.img from the firmware
• magisk_patched.img ­— the file patched by Magisk Manager
• magisk_patched_noavb_manual.img — patched file with manually added vbmeta data and footer.

https://files.catbox.moe/9cp3eo.zip

Log file of direct (re)installation on top of already patched image. The resulting image came without vbmeta, rendering device unbootable.
magisk_install_log_2021-01-17T22:37:05Z.log

[nift4]

This affects other MediaTek devices like the Gigaset GS290 and the Volla Phone too

[osm0sis]

Any improvement on latest Canary?

[ChrisPHL]

+1
This seems to have severe impact. :-/ My GS290 does not boot after patching with the Magisk versions seen in the starting post.

[nift4]

Canary works fine here

[ChrisPHL]

Oh, I'm not familiar with "canray" what exactly does that mean? Where can I download the canary version of Magisk? Does "canary" mean something like "latest"?

[ValdikSS]

commit 027ec70 fixes the issue, canary build works fine.

[nift4]

@ChrisPHL it is the development version of Magisk