# Update capsule and trialboot rollback in base and advance variants The following table shows the availability of capsule update and trialboot rollback in base/advance variants based on the availability of the capsule (in EFI), RPMB provisioned and the UEFI variables. | **Capsule found** | **RPMB Provision** | **OsIndications variable present** | **OsTrialBootStatus variable present** | **Availability of capsule update feature** | **Availability of TrialBoot and RollBack feature** | **Applicable variant** | **Notes** | | --- | --- | --- | --- | --- | --- | --- | --- | | Yes | Yes | No | No | Yes | No | (Standard)Base + upstream distro | | | Yes | Yes | No | Yes | No | No | Advance | RPMB partition needs to be erased by OS when switching from Advance to Base variant on same device. To erase RPMB partition, run the following command.



>
>
> `fastboot oem rpmb_erase` | | Yes | Yes | Yes | No | Yes | No | Advance | | | Yes | Yes | Yes | Yes | Yes | Yes | Advance |

  1. uefi_sec linux app is used to explicitly sync the UEFI variables to RPMB.


  2. RPMB partition needs to be erased by OS when switching from advance to base variant on same device. To erase RPMB partition, run the following command.





>
>
> `fastboot oem rpmb_erase` | | Yes | No | No | No | Yes | No | Base + advance + upstream distro | | Note - Base variants won’t have this UEFI variable enabled irrespective of the RPMB provision. - In the Base variant, capsule update is triggered if capsule is found in EFI partition. OsIndications variable is ignored and trialboot and rollback features are disabled. - If OsTrailBootStatus variable is present, capsule won’t be updated for advance variants until the OsIndications is set. ## Base variant The base variant of RPMB can be either provisioned or unprovisioned. However, UEFI variables such as OsIndications and OsTrialBootStatus remains disabled. The system triggers a capsule update in this configuration only if it detects a capsule file in the EFI partition, at /EFI/UpdateCapsule/. After the system initiates the capsule update process, it updates the ESRT table, which can be accessed through the kernel shell using the /sys/firmware/efi/esrt/entries/entry0/ path. ## Advance variant The advanced variant of RPMB can operate in two modes: provisioned or unprovisioned. - Unprovisioned RPMB: You can still start the capsule update even if RPMB isn’t set up. if RPMB isn’t setup. If the EFI finds a capsule, you can check the update status by looking at the ESRT table from the kernel shell. However, the trialboot and rollback features works only when RPMB is setup. - Provisioned RPMB: In contrast, when you provision RPMB, you use the UEFI variables to determine whether to trigger the capsule update and enable trialboot and rollback features. ## Trigger capsule update For information, see: [How to trigger capsule update](https://docs.qualcomm.com/doc/80-70020-4/topic/How-tos.html#how-tos). Last Published: Jun 25, 2025 [Previous Topic Set up the capsule update](https://docs.qualcomm.com/bundle/publicresource/80-70020-4/topics/capsule-update-and-recovery.md) [Next Topic Generate the capsule](https://docs.qualcomm.com/bundle/publicresource/80-70020-4/topics/capsule-generation-in-uefi.md)