With Android 13, Google has done its job so that the Pixel 6, 6 Pro, and 6a are Cannot reinstall Android 12 In order to address a security issue. When this vulnerability is addressed, another issue may appear, and Google has issued instructions on how to avoid hacking your device if you have flashed Android 13.
What’s different about Android 13 update for Pixel 6
There is a vulnerability in the previous bootloader in the Pixel 6 series, and Android 13 is making it so that the vulnerable version associated with Android 12 cannot be reinstalled.
However, even after flashing the Android 13 factory image – which is different from OTA image sideloading – On Pixel 6 series and updated successfully, Android 12 version is still on your phone. This is due to Android A/B system updates (seamless)which aims to provide redundancy:
A/B system updates use two sets of partitions referred to as slots (usually slot A and slot B). The system operates from the current slot while the partitions in the unused slot are not accessed by the operating system during normal operation. This approach makes updates error-resistant by keeping the unused slot as a fallback option: if an error occurs during or just after an update, the system can roll back to the old slot and continue to run with the operating system.
As such, “the inactive slot contains an older bootloader whose anti-rollback version has not been increased.” Mismatches can cause problems if you flash your device and something fails to install. By design, Android will attempt to boot from the inactive slot, but this goes against the vulnerability protection. Since it’s Android 12 (and older bootloader), your phone won’t boot.
If you flash Android 13
Google Thursday afternoon Instructions provided on how to avoid the appearance of this particular problem. It includes flashing the inactive slot from Android 12 to Android 13. The simplest option is to sideload the OTA image – which updates the inactive slot – but steps for using factory images are also provided.
This process is aimed primarily at those (i.e. repairers) who will reflash their device with either a factory or custom image (AOSP built).
Meanwhile, Google in the coming days will update a file Android Flash Tool – which flashes the active aperture, like fastboot – With inactive slot flash prompt with Android 13 bootloader.
If you are using Android 13 OTA
Those who have uploaded – a to treat Without wiping the device/data – Android 13 OTA image or accepted OTA on the device (which is Google’s recommended installation method) and Don’t intend to blink (Again, different from sideloading) “their phone doesn’t need to take any action at this time”.
| Aperture | aperture b |
| Android 12 (July 2nd 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 running into the problem for the vast majority of users who have a locked bootloader. The next OTA (presumably the September security patch) or sideloading will update the inactive slot.
Kyle Bradshaw and Dylan Russell Contribute to this article.
FTC: We use affiliate links to earn income. more.
“Alcohol maven. Evil bacon lover. Wannabe social media geek. Travel guru. Amateur introvert. Pop culture nerd.”