You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My phone is a Redmi Note 11S.
The seccfg partition is V4.
In unlock mode, field critical_lock_state is incorrectly set to 1 (instead of 0).
It has no effect with Android 11, but with Android 13, dm-verity complains at startup!
This can be fixed in bootloader mode: fastboot oem cdms fix
This simply sets critical_lock_state to 0 in seccfg partition (+rehashing...).
My phone is a Redmi Note 11S.
The seccfg partition is V4.
In unlock mode, field
critical_lock_state
is incorrectly set to1
(instead of0
).It has no effect with Android 11, but with Android 13, dm-verity complains at startup!
This can be fixed in bootloader mode:
fastboot oem cdms fix
This simply sets
critical_lock_state
to0
in seccfg partition (+rehashing...).This patch works for me:
If this is specific to my hardware, maybe there could be a flag to set
critical_lock_state
with a custom value?The text was updated successfully, but these errors were encountered: