Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Brief description
Without workarounds, the bootloader can no longer be locked again after returning to stock from a custom ROM, or when switching from one custom ROM to another. I was able to verify this issue with the latest 15.1 bootloaders; 15.0 and prior bootloaders, on the other hand, are not affected. Specific versions are referenced below.
There is apparently a problem with the way boot.img is flashed in relation to AVB. See Workarounds and steps to reproduce for details of this.
Impact
Affected devices
Affected source custom ROMs, as tested
If coming from any of these ROMs (and perhaps others), and going to an affected destination release, you will not be able to lock the bootloader without workarounds:
Unaffected source custom ROMs, as tested
If coming from any of these ROMs (and perhaps others), and going to an affected destination release, locking will still work fine:
Affected bootloaders / destination releases, as tested
Unaffected bootloaders / destination releases, as tested
Affected flash methods
Unaffected flash methods
Steps to reproduce for troubleshooting or testing:
fastboot flashing unlock
).Real-world steps to reproduce
fastboot flashing lock
), but you do not need to lock it.fastboot flashing lock
).invalid android images, skip locking
. This also happens if you try to install another custom ROM using fastboot, e.g. CalyxOS.Workarounds
Workaround 1
Flash a 15.0 bootloader and reboot into it. Then, flash boot.img again, and locking will work. Before locking, you can flash the 15.1 bootloader if you'd like, reboot into it, and then lock.
Workaround 2
Flash boot.img yet again in userspace fastboot. Unsure why this helps.
Workaround 3
flash boot
line afterupdate-super
.Further info
Downstream issue for CalyxOS:https://gitlab.com/CalyxOS/calyxos/-/issues/2907