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.
1
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.
1
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.
1
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
Replying to and
No, you can't erase or format partitions with a locked bootloader. However, I'm extremely doubtful that this is actually happening. The device will not boot a single time with a modified system partition and locked bootloader. Locking the bootloader enables verified boot.
1
Replying to and
I've had a lot of experience with these devices and also with users making mistakes and then doing a bad diagnosis of what happened based on a lack of understanding and incorrect assumptions. Stock OS and AOSP don't support disabling OEM unlocking until the bootloader is locked.
1
Replying to and
Bootloader locked implies a pristine stock OS or a custom OS with a custom verified boot signing key that has been flashed via a mechanism that was not even publicly documented or mentioned anywhere until we discovered it via reverse engineering and submitted the documentation.
1
Show replies