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
On Android 12, userspace enforces vbmeta signature verification based on
the bootloader lock state, which is read from verifiedbootstate. This
means that spoofing verifiedbootstate=green causes init to bail out
during early boot if vbmeta doesn't pass verification:
[ 9.229305] init: [libfs_avb]ERROR_VERIFICATION / PUBLIC_KEY_REJECTED isn't allowed
[ 9.237357] init: Failed to open AvbHandle: No such file or directory
[ 9.244103] init: Failed to setup verity for '/system': No such file or directory
[ 9.252018] init: Failed to mount /system: No such file or directory
[ 9.258648] init: Failed to mount required partitions early ...
[ 9.264738] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
Given that this workaround is no longer sufficient for passing SafetyNet
anyway due to the opportunistic use of hardware-backed attestation,
revert it to fix issues booting on Android 12.
Stock + custom kernel: FAIL due to hardware attestation
Stock + root: PASS with Universal SafetyNet Fix + MagiskHide (which
sets the same props)
Custom ROM with SafetyNet workarounds: PASS without custom kernel
This workaround alone doesn't really help anyone pass.
Signed-off-by: Danny Lin <danny@kdrag0n.dev>
Signed-off-by: K A R T H I K <karthik.lal558@gmail.com>
0 commit comments