Do the boot problems in QPR2 have anything to do with dm-verity?

[SowTag]

Acknowledgements

• I have chosen an appropriate title.
• All requested information has been provided properly.
• This is not a feature request.
• This issue is not a duplicate of an existing issue.
• The issue is solely related to this GSI.
• This issue occurs with the latest available build.
• I am not running a custom vendor on my device.
• This issue is not kernel related.
• This issue is not related to Magisk/KernelSU/APatch.

Info

• Device: Motorola one fusion
• GSI version: v2024.4.14 QPR2 UDC
• Vendor version: R-based

Expected Behavior

Normal boot

Current Behavior

The device boot loops. I have access to the bootloader logs and found this line:

[ 2072] E - SSM: verity error counter is 1

Whenever the system boots properly the message is as follows:

[ 2236] I - SSM: verity error counter is cleared

So it may have something to do with dm-verity.

Yes, the blank vbmeta.img is flashed, even with --disable-verification and --disable-verity. I can confirm verity should be off because the custom OS warning shows the SHA hash as N/A.

Possible Solution

No response

Steps to Reproduce

1. Flash latest QPR2
2. Boot
3. Don't

Logs

Relevant bootloader logs are in the current behavior section.

pstore still pending a custom patch from my side as it gets cleared on boot

Additional context

Note I'm on kernel 4.9 with no modifications. I have bootloader logs since the very power on moment up until when ABL switches to Linux, but considering it throws a verity error it may not even do so.

[ponces]

Answer is no.
Please, check latest release which should fix your issues.

[SowTag]

Confirmed as fixed. Thank you.