With Android 13, Google made the Pixel 6, 6 Pro, and 6a unable to reinstall Android 12 to fix a security issue. By patching this vulnerability, another issue could arise, and Google has released instructions on how to avoid tinkering with your device if you’ve flashed Android 13.
What’s different with Android 13 update for Pixel 6
A security vulnerability exists with the previous bootloader on the Pixel 6 series, and Android 13 makes the vulnerable version associated with Android 12 unable to be reinstalled.
However, even after flashing an Android 13 factory image – which is different from sideloading an OTA image – to the Pixel 6 series and successfully updating, an Android 12 version remains on your phone. This is due to Android’s A/B (transparent) system updates, which are intended to provide redundancy:
System A/B updates use two sets of partitions called slots (usually slot A and slot B). The system runs from the current slot while the partitions of the unused slot cannot be accessed by the running system during normal operation. This approach makes updates resilient to failures by keeping the unused location as a fallback: if an error occurs during or immediately after an update, the system can revert to the old location and continue to have a system functional.
As such, the “inactive slot contains an older bootloader whose anti-rollback version has not been incremented”. This incompatibility can cause problems if you flash your device and something fails during installation. By design, Android will try to boot from the idle location, but this defeats vulnerability protection. Since this is Android 12 (and the old bootloader), your phone won’t turn on.
If you flashed Android 13
Google on Thursday afternoon provided instructions on how to prevent this particular problem from occurring. This involves flashing the idle location from Android 12 to Android 13. The easiest option is to load an OTA image – which updates the idle location – but the steps for using factory images are also provided.
This process is primarily for those (i.e. DIYers) who are going to reflash their devices with a factory or custom image (built from AOSP).
Meanwhile, Google will update the Android Flash tool – which flashes the active slot, like fastboot – with a prompt to flash the inactive slot with the Android 13 bootloader in the coming days.
If you used the Android 13 OTA
Those who have downloaded – a deviceless / data wipe process – an Android 13 OTA image or accepted the OTA on the device (which is Google’s recommended installation method) and don’t intend to flash (again, different from sideloading), their phones “don’t need to take any action yet”.
|Slot A||Slot B|
|Android 12 (July patch)||Android 12 (June)|
|Android 12 (July)||Android 13 (August)|
|android 13 (September)||Android 13 (August)|
The company also tells us that there is a very low chance of encountering the problem for the overwhelming majority of users with locked bootloaders. The next OTA (presumably the September security patch) or sideload will update the inactive slot.
Kyle Bradshaw and Dylan Roussel contributed to this article.
FTC: We use revenue-generating automatic affiliate links. After.
Check out 9to5Google on YouTube for more info:
#Google #releases #additional #instructions #Pixel #owners #flashed #Android