Your device is corrupt - error pops up during boot after OTA update.

• /e/OS version:
  • e-3.0.1-t-20250606498724-official-two
  • e-3.0.4-beta-t-20250707507202-official-two
  • e-3.0.4-t-20250709507786-official-two
  • e-3.1-beta-t-20250714509197-official-two
• Device model(s): Murena Two
• Impacted Application: /e/OS Updates
• Affected application/URL: n/a
• Browser/client and version: n/a
• Bootloader: UNLOCKed

The problem

After the OTA update the system does not start properly. The following warning pops up:

The system can still boot up if the power button is pressed within the 5 second window, showing the (usual? due to unlocked bootloader?) Orange State message:

Only after a forced rewrite of the vbmeta partitions can the first "Your device is corrupt" message be removed (with only the Orange State warning remaining):

fastboot flash vbmeta_a  --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_b  --disable-verity --disable-verification vbmeta.img

fastboot flash vbmeta_system_a  --disable-verity --disable-verification vbmeta_system.img

fastboot flash vbmeta_system_b  --disable-verity --disable-verification vbmeta_system.img

fastboot flash vbmeta_vendor_a  --disable-verity --disable-verification vbmeta_vendor.img
fastboot flash vbmeta_vendor_b  --disable-verity --disable-verification vbmeta_vendor.img

Steps to reproduce

OTA update with the unlocked bootloader should lead to the problem.

Technical details

FILTERED_OTA_update3.0.4._to_3.1-beta.log

FILTERED_OTA_after_update_to_3.1.log

Finally, after forcing vbmeta partitions rewrite with fastboot flash, adb logcat shows:

FILTERED_OTA_after_forcing_vbMeta_rewrite.log