Zebra TC72, TC77, TC52, TC57, PS20 Installation Manual

...

Android O OS Update

Instruction for Family of

Products Including

TC72, TC77, TC52, TC57, PS20,

TC52HC, MC9300, TC8300,

VC8300, L10A, CC600, C6000,

ET51, ET56, EC30

1. A/B (Seamless) OS Update implementation on SDM660 devices: ................................................... 3

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 ................................................................................ 5

6. OS Upgrade and Downgrade............................................................................................................. 5

7. OS Upgrade and Downgrade via EMMs ............................................................................................ 7

8. User Notification for Full OTA package Upgrade or Downgrade ...................................................... 8

9. Recovery Mode ............................................................................................................................... 10

10. Status messages to EMMs .............................................................................................................. 19

11. Possible device interruptions during Full OTA package: ................................................................. 20

12. AB Fallback mechanism................................................................................................................... 20

13. Rescue Party Mode ......................................................................................................................... 20

14. Recovery logs .................................................................................................................................. 20

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.

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.

2. How AB system is different to Non-AB system:

OS Update Use Case

Non-AB

Notes

Flashing Full OTA Package

Recovery Mode

Android AB Mode

AB: Device shall apply Full OTA Package via Android AB mode when applied via EMM. User can manually enter recovery mode to apply Full OTA package too. Non-AB: Device shall boot into recovery mode to apply any OTA package

Flashing Diff OTA Package

Recovery Mode

AB: Device shall boot into recovery mode to apply any OTA Diff package Non-AB: Device shall boot into recovery mode to apply any OTA package

Flashing reset Packages

Recovery Mode

AB: Device shall boot into recovery mode to apply Enterprise Reset, Factory Reset package Non-AB: Device shall boot into recovery mode to apply Enterprise Reset, Factory Reset package

Device downtime for OS Update

AB: Full OTA updates can occur while the system is running, without interrupting the user. At the end,

device reboots into the new installed image.

Non-AB: Device reboots to recovery mode to install package. User cannot use device while installing OTA package.

Fault tolerance

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 Baseline image). Non-AB: If device fails to bootup, then device is bricked.

Patch upgrades

Y Y

Patch downgrades

Y Y SDM660 Android O has Version Binding implementation which will cause data reset on downgrade.

Hotfix patch support

Y Y

Patch Size

- + AB saves size from having no Rollback images.

Silent Update

X Y AB Full OTA update is silent to user

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

Diff OTA package, 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. Diff OTA package, 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.

Diff OTA package consists of following:

1. HLOS images (system, vendor, boot and dtbo)

2. Non-HLOS images (QCOM images)

Diff OTA packages are used to provide incremental updates to device. The size of diff OTA package 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.

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

Diff OTA package.

3. Downgrade (move to an older/lower version of OS Image) operation will be disabled by default

on SDM660 O. Any customers who use existing CSPs to perform OS Update shall not be able to perform OS downgrade.

4. Existing OS update interface shall be able to perform only OS upgrade operation and not OS

Downgrade operation

5. Using a new interface, customers shall be able to perform OS Downgrade operation with Full

OTA / Diff OTA package.

6. The Downgrade interface shall be able to perform only downgrade operation and not OS

Upgrade operation.

7. All OS downgrade operation will result in an Enterprise Reset operation. i.e user data is erased

on OS downgrade operation.

8. 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

+ 14 hidden pages