-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrade
While it should work without any harm it is a good idea to ensure your backup is current before flashing an upgrade, always!
If you are using Magisk hide (i.e. re-packaging Magisk with a different name) you have to un-do this before upgrading. Otherwise you will likely end with 2 Magisk apps.
If that happens you need to remember the hidden package name and:
- reboot after the upgrade once
- find that package name in the Apps drawer and try to start it
- try to un-hide from there, even if that fails try another reboot
- if that still fails: remove the Magisk app and if still there the re-packaged name and re-flash the AXP.OS package via ADB
- Signature check
- Package integrity check
The most convenient & recommended way to upgrade AXP.OS is by using OTA (Android settings -> System -> Updater).
On A/B devices the upgrade will happen in the background and you get informed when a reboot is required. On older / non A/B devices the device will reboot and upgrade within the recovery instead.
While it is much more convenient to use OTA on A/B devices it takes quite longer (depends on device + installed apps), i.e it can easily take 10-30 mins to complete before you see the reboot prompt.
If you are in hurry you can do an upgrade in recovery as this will save time but requires a PC to sideload the package.
- Signature check*
- Package integrity check*
Doing an update in recovery has the advantage that it will be much quicker for A/B devices (only). It has no speed increase for non A/B devices as those will reboot to recovery during the OTA process anyways.
The disadvantage is that it requires you to download the OTA package manually and you need a PC to adb sideload the package.
If you do not trust the recovery verification check or you have another recovery installed you can manually verify the signature by following the topic "Manually verify OTA packages" at the top of this page.
- boot into recovery
- select "Apply update"
- select "Apply from ADB"
- execute on your PC:
adb sideload <package.zip> - once finished check for any errors and do not reboot if you see any (ask for support if that happens)
- reboot (if asked select to not flash any additional packages)
*Keep in mind that signature + package integrity will be checked and verified when using the AXP.OS recovery only! If you have TWRP or any other recovery flashed this cannot be ensured and is NOT recommended.
All AVB keys and OTA signing keys can be found here. The process for verifying an OTA package is described there as well.
(AXP.OS keys for OTA's are in the format <device-codename>_AXP.OS_pubkey)