Conversation

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

It will automatically fall back to the alternate partition set after failing to boot a certain number of times. The failure count is one of the values retrieved via `fastboot getvar all`. It will only be bricked if neither of the partition sets is working which is very unlikely.

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

It's not possible to disable OEM unlocking via the standard interface until the bootloader is already locked, so you need to be able to successfully boot in order to do that. I think it's very unlikely devices are being bricked in any reasonable flashing / development workflow.

Replying to

and

Once the bootloader is locked, you'll be installing updates via update packages, either via recovery or a system update app. Those get installed to the alternate partition set and if they fail to boot a single time it will automatically fall back to the previous installation.

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

There is no separate recovery image anymore. There's a unified boot image and recovery is one of the boot targets. Sure, it's possible that a custom OS has a broken recovery target, but that means the OS is extremely broken. That's one of the most basic things that gets tested.

Replying to

and

It's not risky to flash a custom Android Verified Boot key and then lock the bootloader with a custom OS since you can always unlock in the worst case, there's automatic rollback for updates that fail to boot and there's the near stateless recovery with the option to wipe too.

Replying to

and

On the other hand, it's definitely dangerous and ill advised to disable OEM unlocking with a poorly tested or untested OS. I think that should go without saying, You definitely don't want OEM unlocking disabled on the devices you're using to initially test your builds.

11:38 AM · Feb 21, 2019Twitter Web Client