Same problem with the Sony Xperia XZ2.
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597
It uses Android Verified Boot 2.0.
A dtb partition is storing the dtb overlay of the kernel, which was previously included into the bootimage.
If you don't flash the correct dtbo data intothis partition, you can't boot the new kernel. -> Of course you can include the drb data into the bootimage again, only the standard way changed.
Aaaaand it is now using a vbmeta partition storing the hashes and crypto stuff to know if a partition is corrupted or changed or whatever and then refuses to boot.
We can't even use
and need to flash it first with
Code:
fastboot flash boot twrp.img
.
I managed to figure out the exact steps which needs to be done to initial install twrp.
Also then you can't boot into the system image again at our site.
In TWRP we need to flash the boot.img file into the boot partition again and after that we need to extract the RAMDISK from the previously named twrp.img into the bootpartition.
It doesn't matter that the twrp.img includes the exactly same kernel and ramdisk.
And after that we need to install magisk in twrp or the device would bootloop.
I've never seen this before and it is new with the snapdragon845 and its qualcom bootloader.
The previously XZ1 with the snapdragon 835 hasn't this problem.
The XA2 with the Snapdragon 630 hasn't it, too.