# Update capsule and trialboot rollback for base and advanced variants
The following table shows the availability of capsule update and trialboot rollback for base or advanced 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 rollback feature** | **Applicable variant** | **Notes** |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Yes | Yes | No | No | Yes | No | (Standard)Base + upstream distro | |
| Yes | Yes | No | Yes | No | No | Advanced | RPMB partition needs to be erased by OS when switching from advanced to base variant on the same device. To erase RPMB partition, run the following command.
>
>
> `fastboot oem rpmb_erase` |
| Yes | Yes | Yes | No | Yes | No | Advanced | |
| Yes | Yes | Yes | Yes | Yes | Yes | Advanced |
uefi_sec linux app is used to explicitly sync the UEFI variables to RPMB.
RPMB partition needs to be erased by OS when switching from advanced 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 + advanced + upstream distro | |
Note
- You can’t enable this UEFI variable on base variants, regardless of RPMB provision.
- In the base variant, the system triggers a capsule update if it finds the capsule in the EFI partition. It ignores the OsIndications variable and disables the trialboot and rollback features.
- The capsule updates advanced variants only after the system sets OsIndications and the OsTrialBootStatus variable is present.

## Base variant
The base variant of RPMB can be either provisioned or unprovisioned. However, UEFI variables such as OsIndications and OsTrialBootStatus remain 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 users can access through the kernel shell using the /sys/firmware/efi/esrt/entries/entry0/ path.
## Advanced variant
The advanced variant of RPMB can operate in two modes: provisioned or unprovisioned.
- Unprovisioned RPMB: You can initiate the capsule update even if RPMB isn’t configured. If UEFI detects a capsule, you can check the update status by viewing the ESRT table from the kernel shell. The trialboot and rollback features are available only when the system sets up RPMB.
- 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
See: [How to trigger capsule update](https://docs.qualcomm.com/doc/80-70030-4/topic/How-tos.html#how-tos).
Last Published: Jul 20, 2026
[Previous Topic
Set up the capsule update](https://docs.qualcomm.com/bundle/publicresource/80-70030-4/topics/capsule-update-and-recovery.md) [Next Topic
Generate the capsule](https://docs.qualcomm.com/bundle/publicresource/80-70030-4/topics/capsule-generation-in-uefi.md)