2

I wrongly click the button to book a update for Android System.

How can I cancel it before Nov 22 after 02:00

enter image description here

0
2

You can not cancel the update itself because it has already been applied.

Modern Android devices have the system partition twice (called A/B partition). One that is currently active and one that can be used for installing updates "seamless" (so called by Google). Which partition is currently active on next boot can be changed.

The screen you show means that an update has been downloaded and installed on the non-active partition. The only step left is rebooting into the updated partition.

I am not sure if you do the reboot but not switch to the updated partition. No matter even if you would manage to do so I assume that the system would start to download and re-apply the update again on the other partition and then ask for rebooting into it to finish the update.

Prevent updates via Developer options

Edit: Even if it is too late for you I stumbled over a settings that might be helpful in similar situations:

On a Pixel 3a running Android 11 I saw in the Developer options and entry called Automatic system updates - Apply updates when device restarts

Therefore if you have such an option and disable it while there is already a pending update plus a scheduled reboot you can cancel the update installation.

If you decide later to install the update you can do that by manually triggering it in the Android system settings.

enter image description here

4
  • Is there a way for one to verify if the system update has indeed been applied?
    – Firelord
    Nov 21 '20 at 15:20
  • 2
    @Firelord The screenshot shows the "restart now" button. As far as I know on systems with A/B partitions the updates are always installed in background and not between reboots. Hence if the update allows you to "reboot now" this means that the update already had been applied.
    – Robert
    Nov 21 '20 at 15:40
  • Turning off the "Automatic system updates" just worked for me on Pixel 4a/Android 11 preventing booting from the newly applied slot. Thanks!
    – sergey.n
    Jul 5 '21 at 6:58
  • 1
    @Firelord In A/B scheme when Android starts "applying" freshly-downloaded system update (which happens right immediately after the update is downloaded), it marks the slot to which the updates is applied (or you can say "flashed" I guess) as "unbootable" - source.android.com/devices/tech/ota/ab#life-of-an-a-b-update. This should be reversed once the update is fully applied. If you really want to find out the state of the slots and of the whole OTA process, you can adb shell reboot bootloder, then fastboot getvar all and look at the all variables that have "slot" in their names :)
    – sergey.n
    Jul 5 '21 at 7:01
1

Reboot into bootloader/fastboot mode.

$ fastboot getvar all | grep current-slot
$ fastboot --set-active=a
$ fastboot reboot

You can set the active slot to be a or b depending on which slot is currently used, from the output of the first command. For example, if you see (bootloader) current-slot:b, you set a as active instead. You can rerun the first command to verify that the change was made successfully.

Once you reboot, you will see a notification saying that the update has failed, which is what you want.

0

There is one simple solution to this thing, I have not experimented on Google Pixel. If the Install later option is showing then you can choose the option to stop the software from being upgraded or the download files will be present in the download folder. From thereafter file gets downloaded you can go there and delete the file before installing it.

I have done this experiment on the Samsung Galaxy Phone.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.