Zebra SDM660 User Manual

1
Android 10 OS Update
Instruction for Family of
Products on SDM660
2
Contents
1. A/B (Seamless) OS Update implementation on SDM660 devices ................................................................................................... 2
2. How AB system is different to Non-AB system ............................................................................................................................... 3
3. Android AB Mode for OS Update .................................................................................................................................................... 4
4. Recovery Mode for OS Update ........................................................................................................................................................ 4
5. Reset Packages and special recovery packages ................................................................................................................................ 4
6. OS Upgrade and Downgrade ............................................................................................................................................................ 5
7. OS Upgrade and Downgrade via EMMs .......................................................................................................................................... 6
8. AB Streaming Update ....................................................................................................................................................................... 7
9. User Notification for Full OTA package Upgrade or Downgrade .................................................................................................... 8
10. Recovery Mode ........................................................................................................................................................................... 10
11. Status messages to EMMs .......................................................................................................................................................... 17
12. Possible device interruptions during Full OTA package: ........................................................................................................... 19
13. AB Fallback mechanism ............................................................................................................................................................. 20
14. Rescue Party Mode ..................................................................................................................................................................... 20
15. Recovery logs ............................................................................................................................................................................. 20
2
Zebra uses AB mechanism for OS Update on SDM660 products running Android O. This is a new OS Update mechanism which is unavailable on other Zebra products with Android O.
The intent of this document is to advise Zebra customers and service about
1. AB OS Update mechanism
2. How to apply OTA packages on SDM660
3. How AB devices are different to legacy Non-AB systems.
4. Fastboot flashing of AB devices.
List of supported devices on A10 are TC52, TC57, TC72, TC77, MC3300x, MC93, PS20, EC30, CC600, CC605, CC610, CC6000, VC8300, TC8300, ET51, ET56, L10AW, L10A, MC9300, TC8300, CC600, C6000, TC21, TC26, MC2200, MC2700, TC57X, TC52X, MC3300, EC50, EC55, TC72X, TC77X, WT6300
1. A/B (Seamless) OS Update implementation on SDM660 devices
Full OTA updates can occur while the system is running, without interrupting the user. This means users can continue to use their devices during an OTA. After the installation of OTA package is completed, device reboots into the updated image.
AB device are fault tolerant by providing a backup slot. If device fails to boot-up, then it will fall back to backup slot (slot with previous used good image/Baseline image) and device remains usable.
In AB Update updates can be streamed to A/B devices, removing the need to download the package before installing it.
3
2. How AB system is different to Non-AB system
4
3. Android AB Mode for OS Update
A full OTA package will be installed via Android AB mode. As part of this, a. Full OTA package will be applied on the device silently in the background.
b. User can continue using the device while Full OTA package will be applied. c. Once the Full OTA package is applied, device auto-reboots to boot into new installed image. d. Customers can also configure the device to wait for EMMs to notify device to reboot via CSP.
Full OTA package consists of following:
1. HLOS images (system, vendor, boot and dtbo)
2. Non-HLOS images (QCOM images)
Full OTA packages are used when we change to a new Baseline image.
4. Recovery Mode for OS Update
OTA Patch images reset packages and any special packages to update /persist or /odm partitions will be installed
via recovery mode. As part of this,
a. Device will be automatically reboot to recovery mode. b. OTA Patch, reset packages (Enterprise Reset, Factory Reset), special packages to update /odm or /persist will be
applied using recovery mode.
c. Device will reboot back to home screen after installation is completed in recovery mode. d. Customers can enter recovery mode using following key combinations of “PTT Key + Scan Key + Power button” or
using “adb reboot recovery” command.
OTA Patch image consists of following:
1. HLOS images (system, vendor, boot and dtbo)
2. Non-HLOS images (QCOM images)
OTA Patch image are used to provide incremental updates to device. The size of OTA Patch image is smaller compared
to Full OTA package and time taken to apply them is also very less.
5. Reset Packages and special recovery packages
Zebra devices support reset packages to erase userdata and enterprise partition. These packages will be applied via
recovery mode.
Enterprise Reset Erase userdata partition and persist enterprise partition Factory Reset Erase both userdata and enterprise partition Special recovery packages packages used to modify WLAN region code, audio tuning files etc can be applied via
recovery mode.
5
6. OS Upgrade and Downgrade
Customer can upgrade the device to another Baseline image or to a patch image on a given baseline. In both cases user data is persisted on all OS Upgrade operation.
Customers can perform OS downgrade to an older baseline or to a patch image belonging to an older baseline. If customer performs OS downgrade operation, forced auto data reset is performed. Data persistence is not supported on OS Downgrade.
On SDM660 O, following is the experience related to OS Update,
1. Customers shall be able to perform OS Upgrade (move to a higher version of OS Image) using Full OTA package.
2. Customers shall be able to perform OS Upgrade (move to a higher version of OS Image) using OTA Patch image.
3. Downgrade (move to an older/lower version of OS Image) operation will be disabled by default on SDM660 O.
4. Any customers who use existing CSPs to perform OS Update shall not be able to perform OS downgrade.
5. Existing OS update interface shall be able to perform only OS upgrade operation and not OS Downgrade operation
6. Using a new interface, customers shall be able to perform OS Downgrade operation with Full OTA / OTA Patch image.
7. The Downgrade interface shall be able to perform only downgrade operation and not OS Upgrade operation.
8. All OS downgrade operation will result in an Enterprise Reset operation. i.e user data is erased on OS downgrade operation.
9. Following parameters will be considered for OS downgrade operation a. OS Google Security patch level (ro.build.version.security_patch) b. OS patch version (ro.device.patch.version) c. OS Hotfix version d. Custom OS version
6
7. OS Upgrade and Downgrade via EMMs
Kindly refer to MX tech docs present on Zebra tech docs portal for more details on supported CSP interfaces for OS Upgrade and Downgrade.
http://zebra-stage.github.io/mx/
Recovery UI also has been modified for OS Upgrade and Downgrade. Separate OS Upgrade and Downgrade options have been enabled in recovery UI to perform OS Update operation.
Kindly visit below sections in this document for detailed explanation on recovery mode.
OS Update
via EMM
OS Upgrade
OS Downgrade
Intent
Action
com.symbol.intent.action.UPDATE_PACKAGE
com.symbol.intent.action.VERIFY_UPDATE_PACKAGE
com.symbol.intent.action.DOWNGRADE_PACKAGE
com.symbol.intent.action.VERIFY_DOWNGRADE_PACKAGE
Allowed OTA Packages
Full OTA Package, OTA Patch image, UPL
Full OTA Package, OTA Patch image, UPL
Data
persistence
YES
NO Auto data reset shall be performed
Allowed OS Update use
case
UPGRADE ONLY Upgrade from Baseline to a higher OS Patch version Upgrade from Baseline to a higher SPL version Upgrade from Baseline to a higher Baseline Upgrade from Baseline to a higher Hotfix version Upgrade from Patch to a higher Patch version Upgrade from Patch to a higher SPL version Upgrade from Patch to a higher Baseline Upgrade from Patch to a higher Hotfix version Upgrade from Hotfix to a higher Hotfix version Upgrade from Hotfix to a higher SPL version Upgrade from Custom OS to a higher Custom version Upgrade from Custom OS to a higher Custom OS SPL version Upgrade from Custom OS to a higher Custom Baseline
DOWNGRADE ONLY Downgrade from Baseline to a lower/older Baseline Downgrade from Baseline to a OS Patch version on lower/older Baseline Downgrade from Patch to a lower/older Patch version Downgrade from Patch to a lower/older SPL version Downgrade from Patch to a lower/older Baseline Downgrade from Patch to a lower/older Hotfix version Downgrade from Hotfix to a lower/older Hotfix version Downgrade from Hotfix to a lower/older SPL version Downgrade from Custom OS to a lower/older Custom patch version Downgrade from Custom OS to a lower/older Custom OS SPL version Downgrade from Custom OS Baseline to a lower/older Custom OS Baseline version Downgrade from Custom OS Baseline to a Custom OS Patch version on a lower/older Custom OS Baseline version
Loading...
+ 14 hidden pages