Software ZEBRA Android 14 AOSP

Specificazioni

• Product Name: Android 14 AOSP Release 14-28-03.00-UN-U60-STD-ATH-04
• Supported Devices: TC53, TC73, TC22, HC20, HC50, TC27, ET60, TC58
• Conformità di a Sicurezza: Bollettinu di Sicurezza Android di u 01 di ghjugnu 2025

Introduzione

Zebra uses AB mechanism for OS Update on SDM660 products running Android O and above. 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

Lista di i dispositi supportati in A14 sò:
TC52, TC57, TC72, TC77, EC50, EC55, TC52X, TC57X, TC52AX, MC9300, TC21, TC26, MC3300, EC30, MC2200, MC2700, MC6300, WTMC20, VC271, CC8300, CC600, TC6000, ET8300, ET51, L56AW

Simboli è Note utilizati in stu documentu:

• Cuntestu di a nota Una nota impurtante o critica. L'utilizatori anu da esse cuscenti di stu cambiamentu.
• Cuntestu di a nota Una nota chì serve com'è infurmazione supplementaria à u lettore.

Cambiamentu impurtante per l'upgrade di l'OS A13 è sopra (Must Read)

Tutti i dispusitivi
Android 13 è sopra OS cambia u metudu di criptografia utilizatu per assicurà e dati di l'utilizatori in a memoria interna di u dispusitivu.

Per sustene l'aghjurnamentu di u SO da un dessert OS precedente (usendu FDE) à Android 13 o sopra (usendu FBE), Zebra hà attivatu dui meccanismi:

1. OS Upgrade with data reset (User data will be erased on upgrade)
   This is the default OTA upgrade process.
2. OS Upgrade with data persistence
   For users who prefer OS upgrade with data persistence please follow the process and steps documented here and here.

A/B (Seamless) OS Update implementation on SDM660 devices

• Full OTA and Delta OTA (Patch) updates can occur while the system is running, without interrupting the user. This means users can continue to use their devices during an OTA upgrade. 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 a backup slot (reboot back into the old partition) and the device remains usable.
• Updates can be streamed to devices supported by this document, removing the need to download the complete package before installing it.

Starting with Android 11

• Full OTA packages and Delta OTA packages of each LG release will be available on Zebra.com.
• Delta OTA packages can be streamed and installed on the device.
• AB updates can be streamed using LifeGuard Over the Air (OTA) 3.0 APIs.
• OTA Delta packages available on Zebra.com will be sequential in nature.
• For customers who are using Zebra LifeGuard Over the Air (OTA) solution, you can upgrade to the target OS LG software version in a single step with the help of a single OTA delta package. This OTA delta package is called true delta package which contains the exact delta required to install the target LG software version.
• This true delta OTA package will be serviced by LifeGuard Over the Air (OTA) solution and will not be available on zebra.com. You can find more details on LifeGuard Over the Air (OTA) solution at Zebra TechDocs portal.
• The size of OTA delta packages will be much smaller than Full OTA packages.

How AB system is different to Non-AB system

Casu d'usu di l'aghjurnamentu OS	non-AB	AB	Notes
Flashing Full OTA Package	Modu di ricuperazione	Modu AB Android	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 Delta OTA Package	Modu di ricuperazione	Modu AB Android	AB: Device will apply OTA delta package in background via Android AB mode. User can manually enter recovery mode to apply OTA delta package too. Non-AB: Device shall boot into recovery mode to apply any OTA package.
Flashing Reset Packages	Modu di ricuperazione	Modu di ricuperazione	AB: Device shall boot into recovery mode to apply Enterprise and Factory Reset packages Non-AB: Device shall boot into recovery mode to apply Enterprise and Factory Reset packages
Tempo di inattività di u dispositivu per l'aghjurnamentu di u SO	–	+	AB: Full and Delta OTA updates can occur while the system is running, without interrupting the user. At the end, device reboots into the new installed image. Rebooting to new OS image is the only   device   downtime   user   will   experience. Non-AB: Device reboots to recovery mode to install reset or special packages only. User cannot use the device while installing OTA package.
Tolleranza à i difetti	–	+	AB device are fault tolerant by providing a backup slot. If device fails to boot-up, then it will fall back to backup slot (reboot back into the old partition). Non-AB: If device fails to bootup, then device is bricked.
Patch upgrades	Y	Y
Patch downgrades	Y	N	Starting A11, patch downgrades are not supported. Users have the option to use Full OTA package of the specific patch to perform OS downgrade. SDM660 Android O and above has Version Binding implementation which will cause reset di dati on downgrade to an older Google SPL or older Dessert version.
Hotfix patch support	Y	Y
Dimensione di Patch	–	+	AB delta packages will be considerably small compared to Non-AB delta packages available for Zebra devices. I clienti chì utilizanu l'API LifeGuard Over the Air (OTA) puderanu aduprà un pacchettu True Delta.
Silent Update	–	Y	L'aghjurnamenti AB Full è Delta OTA sò silenziu per l'utilizatori

OS Update from Zebra.com and LifeGuard Over the Air (OTA)

Casu d'usu di l'aghjurnamentu OS	Zebra.com	LifeGuard Sopra l'aria (OTA) 3.0	Notes
Full OTA OS Upgrade	Y	Y
Full OTA OS Downgrade	Y	N	LifeGuard Over the Air (OTA) 3.0 does not support OS downgrade. EMM can downgrade to an older version by downloading  a  Full  OTA  package  of  an  older  version. Zebra.com customers can downgrade by pulling the Full OTA package of target OS version from zebra.com and pushing the OTA package to the device from their EMM console.
Delta OTA Upgrade	YSequential Delta	YTrue Delta	LifeGuard Over the Air (OTA) 3.0 – Delta OTA packages will be streamed for customers using LGE solution. Zebra.com – Delta upgrades are sequential and can be installed using StageNow/EMM o da u modu di Recuperazione.
Delta OTA Downgrade	N	N	I pacchetti Delta OTA ùn ponu micca esse usatu per Downgrade à una versione di patch più antica.
Supportu di streaming	N	Y	A soluzione LifeGuard Over the Air (OTA) 3.0 permetterà u streaming AB di pacchetti OTA Full è Delta. Zebra.com customers will have to manually download full OTA or delta packages to the device and install the same. OTA packages downloaded from zebra.com can be streamed to device, this requires customers to set up their AB streaming server and host the OTA package downloaded from zebra.com
Reset Packages or Special Packages	Y	N	LifeGuard Over the Air (OTA) 3.0 APIs do not support flashing of Reset or Special packages. Zebra.com customers can download, and flash Reset packages or any special packages available to them.

Sequential nature of Delta OTA packages

Per aghjurnà da u Patch 1 (U01) à u Patch 5 (U05), bisogna ancu applicà tutti i pacchetti delta intermedi (vale à dì, U01, U02, U03, U04 è U05) in u listessu ordine.

Patch	Build ID (XXX – Platform code)	SPL
U01	13-16-17.00-TG-U01-STD-XXX-04	aprile 2023
U02	13-16-17.00-TG-U02-STD-XXX-04	maghju 2023
U03	13-16-17.00-TG-U03-STD-XXX-04	ghjugnu 2023
U04	13-16-17.00-TG-U04-STD-XXX-04	Lugliu 2023
U05	13-16-17.00-TG-U05-STD-XXX-04	Aostu 2023

Per fà e cose più faciule, l'utilizatori ponu saltà l'applicazione di pacchetti delta in sequenza è lampà direttamente u pacchettu Full OTA di U05.

Android AB Mode for OS Update

Full and delta OTA packages will be installed via Android AB mode. As part of this:

• Full and delta OTA package will be applied on the device silently in the background.
• User can continue using the device while OTA packages will be applied.
• Post installation is complete, a device notification will be displayed confirming the installation is completed and device shall auto-reboot after 15 secs.
• Device will auto-reboot to boot into newly installed OS image after the OTA package installation is completed successfully.
• Customers can also configure the device to wait for Update clients (e.g., FOTA) or EMMs to notify device to reboot.
• AB streaming mode will be used by default for customers using LifeGuard Over the Air (OTA) solution to update the device. The OTA package will not be completely downloaded and saved on device before starting the installation. Rather the OTA package contents will be streamed to the device and installed.
• StageNow tool can be used to perform OS Update using an OTA package in manual mode (without the need to go into Recovery mode). Please search and click on Power Manager section in the link provided.

OTA package consists of following

1. HLOS images (system, vendor, boot and dtbo)
2. Non-HLOS images (QCOM images)

Recovery Mode for OS Update
Reset packages and any special packages to update Zebra Device Management partitions will be installed via recovery mode.

As part of this:

• The device will be automatically reboot to recovery mode.
• Reset packages or special packages will be applied using recovery mode.
• Device will reboot back to home screen after installation is completed in recovery mode.
• Customers can enter recovery mode using key combinations or using “adb reboot recovery” command.

Reset Packages and special recovery packages
I dispositi Zebra supportanu i pacchetti di reset per sguassà i dati di l'utilizatori è a partizione di l'impresa. Questi pacchetti seranu applicati via u modu di ricuperazione.

Pacchettu	infurmazione
Reset di l'impresa	Erase userdata partition and persist enterprise partition
Reset di fabbrica	Sguassà i dati d'utilizatore è a partizione di l'impresa
Special recovery packages	Pacchetti usati per mudificà e partizioni Zebra Device Management o pacchetti per aghjurnà u codice di a regione WLAN, sintonizazione audio files etc pò esse appiicata via modu ripresa.

Tutti i dispusitivi
Ùn aduprate micca vechji pacchetti di reset da Oreo/Pie/A10/A11 in A14 OS.

OS Update Operations – Upgrade and Downgrade

• U Cliente pò aghjurnà u dispositivu à una versione iniziale di dessert OS più recente O à qualsiasi versione di patch LG più recente in u stessu dessert O in a versione più alta di dessert se u nivellu di patch di sicurezza di Google di l'imaghjina OS da installà hè più altu ch'è u livellu di patch di sicurezza di Google in u dispusitivu.
• Se u dispusitivu hè in esecuzione nantu à un livellu di patch di sicurezza Google più altu cumparatu cù l'imaghjini di u SO da esse installatu, u cliente ùn pò micca aghjurnà à una tale maghjina. Stu cumpurtamentu segue i requisiti di sicurezza di Google per prutege u dispositivu da sfruttà qualsiasi vulnerabilità di sicurezza cunnisciute. I dati di l'utilizatori sò persistenti in tutte l'operazioni di l'upgrade OS.
• I clienti ponu fà un downgrade OS à una vechja maghjina di dessert OS o à una maghjina di patch LG (Using Full OTA) avè un livellu di patch di sicurezza di Google più bassu cumparatu à u nivellu di patch di sicurezza di Google in u dispositivu. Se u cliente esegue l'operazione di downgrade di l'OS, u dispositivu riavviarà è i dati di l'utilizatori seranu sguassati automaticamente.

Tutti i dispusitivi
A persistenza di dati ùn hè micca supportata in u downgrade OS.

Nant'à SDM660 O è sopra, seguite l'esperienza ligata à 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 delta OTA image.
3. Starting from A11 on SDM660 devices, customers can downgrade (move to an older/lower version* of OS Image) operation using Full OTA packages only.
4. Separate interfaces are provided to perform OS Upgrade & OS downgrade operations.
5. All OS downgrade operation will result in an Enterprise Reset operation. i.e., user data is erased on OS downgrade operation.

** higher version → Following parameters will be considered to identify if an OS image to be installed is higher or lower compared to device OS version.

• OS Google Security patch level (ro.build.version.security_patch)
• OS software version (ro.device.patch.version)
• OS Hotfix version
• Custom OS version

OS Upgrade and Downgrade via EMMs

Per piacè riferite à i documenti di tecnulugia MX presenti nantu à u portale Zebra TechDocs per più dettagli nantu à l'interfacce CSP supportate per l'upgrade è u downgrade OS.
https://techdocs.zebra.com/mx/powermgr/

Actualizazione di l'OS via EMM	Upgrade OS	OS Downgrade
Reset Azzione	10 – OS Upgrade	11 – OS Downgrade
Allowed OTA Pacchetti	Pacchettu OTA cumpletu, immagine Patch OTA, UPL	Pacchettu OTA cumpletu
Data persistence	IÈ	INNÒ Auto data reset shall be performed
Allowed OS Update use case	UPGRADE ONLY Upgrade from current OS to a higher OS software version Upgrade from current OS to a higher SPL version Upgrade from current OS to a higher version of OS Upgrade from current OS to a higher Hotfix version Upgrade from Patch to a higher software version Upgrade from Patch to a higher SPL version Upgrade from Patch to a higher version of OS 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 version of OS	DOWNGRADE SOLU Downgrade from current OS to a lower/older OS version Downgrade from current OS to a OS software version on lower/older OS version Downgrade from Patch to a lower/older OS version 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 software version Downgrade from Custom OS to a lower/older Custom OS SPL version Downgrade from Custom OS version to a lower/older Custom OS version Downgrade from Custom OS version to Custom OS software version on a lower/older Custom OS version

Tutti i dispusitivi
Suppress reboot flag ùn deve esse cunsideratu in casu di downgrade OS.

Tutti i dispusitivi

• A realizazione di l'aghjurnamentu di u SO à un dessert più altu, ma avè un SPL più bassu risultatu in un reset di dati.
• L'UI di ricuperazione hè stata mudificata ancu per l'upgrade è u downgrade OS. Opzioni separati di l'upgrade di l'OS è u Downgrade sò stati attivati ​​in l'UI di ricuperazione per eseguisce l'operazione di l'aghjurnamentu di u SO.
• Per piacè visitate e sezioni sottu in stu documentu per una spiegazione dettagliata nantu à u modu di ricuperazione.

AB Streaming Update

• Un pacchettu OTA pò risiede in u servitore è i dispositi supportati ponu trasmette u pacchettu da u servitore direttamente à u dispositivu senza salvà u pacchettu OTA in u dispositivu. L'aghjurnamentu di u SO hè in sfondate è una notificazione di l'utilizatori deve esse affissata per indicà chì l'operazione di aghjurnamentu di u SO hè in corso.
• U pacchettu OS Update pò esse trasmessu à i dispositi A / B, eliminendu a necessità di scaricà u pacchettu OTA à u dispusitivu prima di stallà. Cù l'aiutu di u modu AB Streaming, l'utente pò fà operazioni di aghjurnamentu di u SO ancu s'è u spaziu di discu hè pocu. U stessu pacchettu OTA pò esse usatu per l'aghjurnamenti in streaming AB è AB senza saldatura.
• U modu di streaming AB serà utilizatu per automaticamente per i clienti chì utilizanu LifeGuard Over the Air (OTA) 3.0 soluzione per aghjurnà u dispusitivu.
• U pacchettu delta OTA ùn serà micca telecaricatu cumpletamente è salvatu in u dispositivu prima di inizià a stallazione. Piuttostu, u cuntenutu di u pacchettu delta OTA serà trasmessu à u dispusitivu è installatu. In listessu modu, l'aghjurnamenti di streaming AB seranu utilizati s'ellu ci hè bisognu di installà un pacchettu Full OTA da a soluzione LifeGuard Over the Air (OTA) 3.0.
• Customers who self-manage their devices will have to download the required OTA package from zebra.com and copy the same to the device. AB Streaming update will not be applicable for this use-case.

A tabella sottu mostra l'argumenti da esse aduprati per l'aghjurnamentu di streaming AB:

Operazione	Reset Azzione	Dettagli
UPGRADE	12 – OS Upgrade Streaming	Lancia un pacchettu cumpletu / patch OS Upgrade via u servitore di streaming.
DOWNGRADE	13 – OS Downgrade Streaming	Launches a full-package OS Downgrade via streaming server.

• Mentre l'aghjurnamentu di streaming AB hè in corso, una barra di prugressu mostrarà u prugressu di l'operazione. Dopu chì l'aghjurnamentu di streaming AB hè finitu, u dispositivu mostrarà una notificazione chì in 15 seconde u dispusitivu si riavviarà automaticamente. Dopu à 15 seconde, u dispositivu riavviarà automaticamente in una nova immagine OS. U statutu di l'aghjurnamentu di u SO hè dispunibule ancu via OEMInfo.
• U dispositivu deve esse autenticatu cù u servitore prima chì u pacchettu OTA chì reside nantu à u servitore pò esse trasmessu. A suluzione EMM o a soluzione FOTA chì inizia u travagliu di l'aghjurnamentu di u SO duverà generà l'ID di autentificazione è sparte cù u dispositivu utilizendu Power Manager CSP.

Following Authentication modes are supported for AB streaming mode.

• Token Auth
• Username & Password (Basic Auth).
• Nisuna autentificazione

Device supports following protocols to perform AB streaming:

• http
• https (recommended for better security)
• L'installazione di pacchetti Full (upgrade / downgrade) è Delta OTA pò esse realizatu cù l'aghjurnamentu di streaming AB. Tutti l'altri casi d'usu di l'impresa di Zebra ùn ponu esse supportati da l'aghjurnamentu di AB Streaming.
• Installing multiple OTA packages using UPL is not supported by AB streaming update.

User Notification for Full OTA package Upgrade or Downgrade

• SPR 36526 was fixed in 01-18-02.00-OG-U00-STD/01-18-02.00-ON-U00-STD OS version. With this fix, we now bring user notification when a Full OTA package is being installed. Earlier OS versions had implemented a silent OS update and thus user was unaware of the background OS Update process.
  Few of the features of this user notification:
  1. This is applicable for Full OTA package and OTA Patch image.
  2. On start of Full and Diff OTA package installation, an Icon (android system icon) will be displayed on the Status Bar.
  3. On pulling down the notification drawer, a notification will be displayed informing that OS Update is in progress and device will Reboot automatically on completing the same.
  4. User will have no control over this notification. i.e., User CANNOT
     • Pause/Snooze the OS Update request
     • Cancel OS Update request
     • Prevent Reboot of device
  5. Notification can be cleared by User. Once notification is removed, no new notification shall be displayed again.
  6. If EMMs have selected “Suppress Reboot” option while installing a Full OTA package, then device will not auto-reboot. User Notification too indicates the same and waits for EMMs to reboot the device.
  7. The notification will also display system interrupts blocking OS Update process. E.g., Low Battery, Media Eject etc.
• In prior desserts, if the device was flashed with an OS dessert or version that is not supported by the device a notification used inform user that a sub-optimal version of OS is running.

Tutti i dispusitivi
This notification is removed from Android 11 onwards.

OS Update – Screenshots

• A stallazione di u pacchettu OTA cumpletu hà iniziatu
• A stallazione di u pacchettu OTA cumpletu
• A Ful l OTA package installation has failed to apply
• Notificazione per l'annullamentu di u travagliu di l'aghjurnamentu di u SO

Modu di ricuperazione
Da a ricuperazione, i clienti di l'UI ponu installà pacchetti OTA cumpleti, immagini OTA Patch è resettate pacchetti. SDM660 Recovery UI furnisce e seguenti opzioni per fà diverse operazioni in modu di ricuperazione è applicà diversi pacchetti:

• Reboot system now
• Apply upgrade from ADB
• Apply upgrade from SD card
• Apply upgrade from USB drive
• Apply downgrade from ADB
• Apply downgrade from SD card
• Apply downgrade from USB drive
• View logs di ricuperazione
• Power off
  • Different UI options within Recovery mode and their functionalities are explained below in detail.
  • All Devices Please ignore Device Name and Build Fingerprint displayed on the screenshots.
• Reboot system now
  Quandu sta opzione UI hè selezziunata da l'utilizatori, u dispositivu avviarà à u SO.
• Apply upgrade from ADB
  Upgrade packages via adb will be applied when we select this option. User can only perform OS Upgrade operation and not downgrade operation using this option. L'utente deve inserisce u nome di u pacchettu via l'interfaccia adb sideload.
• Apply upgrade from SD card
  Upgrade packages via External SD card will be applied when we select this option. User can only perform OS Upgrade operation and not downgrade operation using this option. Utilizendu sta opzione, i clienti ponu eseguisce l'upgrade di l'OS cù pacchetti Full OTA, OTA Patch images è installà Reset Packages da a carta SD.
• Apply upgrade from USB drive
  Upgrade packages via USB drive will be applied when we select this option. User can only perform OS Upgrade operation and not downgrade operation using this option.Using this option, customers can perform OS Upgrade using Full OTA packages, OTA Patch images and install Reset Packages from USB drive.
• Apply downgrade from ADB
  Downgrade packages via adb will be applied when we select this option. User can only perform OS Downgrade operation and not upgrade operation using this option.
  Once selecting this option user should enter the package name via adb side load interface.
• Apply downgrade from SD card
  Downgrade packages via External SD card will be applied when we select this option. User can only perform OS Downgrade operation and not upgrade operation using this option.
  Using this option, customers can perform OS downgrade using Full OTA packages, OTA
  Patch images and install Reset Packages from SD card.
• Apply downgrade from USB drive
  Downgrade packages via USB drive will be applied when we select this option. Using this option, customers can perform OS Upgrade using Full OTA packages, OTA Patch images and install Reset Packages from USB drive.
  User can only perform OS Downgrade operation and not upgrade operation using this option.
• View logs di ricuperazione
  Selezziunendu sta opzione, l'utente pò view logs di ricuperazione.I logs di ricuperazione seranu dispunibili in /tmp/recovery.log Selezziunendu Back, pudemu turnà à u menu principale.
• Power off
  By selecting this option user can power off device.

Installation from Recovery Mode

Se vulete realizà l'aghjurnamentu di u sistema da un aghjurnamentu file scaricatu da u Zebra.com support page there are two options. Both methods are summarized below:

• For a single upgrade the upgrade file can be loaded onto a removable memory device and inserted into the device to be upgraded.
• For multiple devices to upgrade it may be easier to use the ADB command method. (ADB or Android Debug Bridge is a tool used to communicate with Android devices from a host computer. Information can be found here: https://developer.android.com/studio/command-line/adb)
• Performing a System Update Using SD Card or USB Drive
  1. Select appropriate upgrade file da u supportu Zebra web pagina.
  2. Scaricate l'aghjurnamentu file à un computer host.
  3. Copy Upgrade file to the removable memory (either SD card or USB drive) root directory using the host computer.
  4. Remove the memory device from the host computer (be sure it is properly ejected first) and install into the device being upgraded.
  5. Make sure the device battery level is at least 30%. Invoke recovery mode on device. To restart the device press and hold the power button and select restart from on screen menu.
  6. Customers can enter recovery mode using the following key combinations:

TC5x, TC7x

• Device is being restarted PTT Key
• Device is powered off PTT Key + Power Button

Tutti i dispusitivi

• Please refer to product specific documentation for key combinations.
• Press and hold the indicated buttons until the Zebra screen appears. OR
• using “adb reboot recovery” command.

1. From the on-screen menu using volume keys scroll to “Apply upgrade from SD Card” or “Apply upgrade from USB Drive”. When the selection is highlighted press the power key to select.
2. When the install is complete select the reboot option and press the power button to reboot the device.

• Performing a System Update Using ADB Commands from Host Computer
  1. Select appropriate upgrade file da u supportu Zebra web pagina.
  2. Scaricate l'aghjurnamentu file à un computer host.
  3. Assicuratevi chì i drivers ADB sò stallati nantu à l'urdinatore host.
  4. Connect the device to the host computer with the proper USB cable. Make sure the device has at least 30% battery level before starting the upgrade process.
  5. Go to the Settings application on the device and enable Developer options by following this link: https://developer.android.com/studio/debug/dev-options
  6. Select on the Settings application: System > Advanced > Developer options.
  7. Slide the switch for Developer Options to the ON position.
  8. Slide the switch for USB Debugging to the ON position. The Allow USB debugging? dialog box appears.
  9. Touch OK. This allows the host computer and the device to communicate via USB.
  10. On the host computer, open a command prompt window and use the adb command:
      dispusitivi adbTutti i dispusitivi
      Se u numeru di u dispositivu ùn appare micca, assicuratevi chì i driver ADB sò stallati bè.
  11. Type the following command and press Enter: adb reboot recovery
  12. A pantalla di Recuperazione di u Sistema appare nantu à u dispusitivu.
  13. Press the Volume Up and Volume Down buttons on the device to navigate to Apply upgrade from ADB.
  14. Press the Power button to select this option.
  15. On the host computer command prompt window type:
      adb sideloadfile> induve: <file> = u caminu è filenome di u zip file.
  16. Press Enter on Host PC at the prompt. The System Update starts installing (progress appears as percentage in the Command Prompt window) and then the System Recovery screen shows update progress information on the device.
  17. When the update is complete select the reboot option and press the Power button to reboot the device.

Verificà l'installazione di l'aghjurnamentu di u sistema

1. Andà à Settings.
2. Toccate À propositu di u telefunu.
3. Scroll down to Build number.
4. Assicuratevi chì u numeru di custruzzione currisponde à u novu pacchettu di aghjurnamentu di u sistema file numeru.

UPL (Update Package List) mechanism
UPL allows user to perform anyone of the below use-cases in a single step for device administrator

• Apply multiple firmware OTA packages along with an OS OTA package
• Apply any configuration OTA packages along with an OS OTA package
• Apply reset packages after installing an OS image
• Perform device reset using commands instead of packages

Un UPL file can consist combinations of following package types:

• Full OTA package
• Delta OTA package
• Reset packages
• Resettate i cumandamenti
• Firmware update packages
• Configuration packages

Finu à A10 nantu à SDM660, un UPL file puderia avè un pacchettu Full OTA di una linea di basa seguita da un pacchettu OTA delta di una versione di patch LG chì appartene à a stessa linea di basa. Questu permetterà à l'amministratore di u dispositivu per aghjurnà à u patch LG necessariu nantu à una linea di basa in un solu passu.

• Tutti i dispusitivi
  A partire da Android 11, un UPL file ùn pò micca esse cumpostu da u pacchettu Full OTA è Delta OTA.
• Tutti i dispusitivi
  I clienti ponu installà direttamente u pacchettu Full OTA di a versione LG OS necessaria.

The Full OTA package can be downloaded from zebra.com. If customer is using the LifeGuard Over the Air (OTA) 3.0 solution, then device can be directly updated to the required LG patch version using a delta OTA package provided by LifeGuard Over the Air (OTA) 3.0.

Rules to build an UPL. On A11 and above, UPL can consist of the following combinations:

• Full OTA package + Reset/Special package
• Full OTA package + Reset command
• OS Patch image (e.g., LG patch) + Reset/Special package
• OS Patch image (e.g., LG patch) + Reset command

Following combinations are supported only when downgrading from A11 to A10 or below:

• Full OTA package + OS Patch image (e.g., LG patch)
• Full OTA package + OS Patch image (e.g., LG patch) + Special package
• Full OTA package + OS Patch image (e.g., LG patch) + Reset command

U dispusitivu pò esse resettatu utilizendu i seguenti cumandamenti UPL è sò supportati in A10 è sopra. Questu evita a necessità di spinghje un pacchettu di resettore mentre usa UPL.

• EnterpriseReset
• Factory Reset

UPL files should NOT be configured as below:

• Combination of Full OTA packages or Delta/OS Patch images (e.g., LG patch)
• New lines present after the last line in UPL file
• Trailing tab spaces present after each line in UPL file
• Unwanted characters present after each line in UPL file
• Contain only UPL commands

Pochi ex validiample di l'UPL files sò cum'è quì sottu:

Sample1.upl	Sample2.upl
package: Full_OTA_Package.zip	package :Full_OTA_Package.zip
package: FactoryReset.zip	command: FactoryReset
Sample3.upl	Sample4.upl
package: Patch_OS_Package.zip	package: Patch_OS_Package.zip
package: FactoryReset.zip	command: FactoryReset
Sample5.upl	Sample6.upl
package: Baseline_Delta_Package.zip	package: Baseline_Delta_Package.zip
package: FactoryReset.zip	command: FactoryReset

• Per installà una UPL, copia UPL file è i so pacchetti OTA currispondenti à u listessu locu in u dispusitivu. Sceglite UPL filenome per installà i pacchetti è micca i nomi di pacchetti OTA individuali.
• Se i pacchetti UPL è OTA sò stati copiati in memoria interna (/sdcard o /data/tmp/public) allora questi files ùn deve esse riusu.
• Tutti i dispusitivi
  UPL files and OTA packages residing in internal memory of device should be deleted after they have been applied. Do not re-use the same packages or UPL files.
• Tutti i dispusitivi
  UPL file ùn pò micca esse installatu cù u modu adb sideload.
• Tutti i dispusitivi
  Device will reboot after applying an OTA package if Reset is included in UPL

If UPL consists of a Full or Diff OTA package and a special package:

• Full OTA package shall get installed in Android AB mode (background update)
• Special packages will be installed in recovery mode.
• Device will auto reboot to recovery mode after Full OTA package installation has completed.
• Suppress reboot flag shall not be considered in UPL update.

Status messages to EMMs
U statutu di l'aghjurnamentu di u SO hè mandatu cum'è un intentu. Data Analytics cattura u listessu è u almacena in u fornitore di cuntenutu OEMInfo. L'EMM ponu leghje u fornitore di cuntenutu OEMInfo per piglià u statu esatta di l'operazione di Actualizazione di u SO. U dispositivu ùn mostra micca alcuna notificazione UI quandu una Actualizazione di u SO hè in corso / applicata / falluta.

18. Possibile interruzzioni di u dispusitivu durante un aghjurnamentu di pacchettu OTA
While a Full OTA Package is installed via AB mode in background, user of the deice will be able to use the device. Thus, device might be put to various states which can interrupt the ongoing OS Update. Device states which can interrupt the OS Update are:

1. Low Battery condition. If Battery falls below 30% capacity, ongoing OS Update will be interrupted and resumed only after connecting to a battery source.
2. Device can be shutdown, enter critical battery state, media ejected (external SD Card), or low Storage in userdata partition (<200MB). In all the above scenarios, ongoing OS Update will be cancelled.
3. If device is rebooted in middle of an OS Update operation, the ongoing job will be suspended for seamless update and cancelled for steaming update. On reboot of device, OS Update job will be resumed and completed only in case of a seamless update.

AB Fallback mechanism

• In u sistema Android AB, se un OTA ùn riesce à dumandà (per esample, because of a bad flash), the user will not be affected. The user will continue to run the old OS (existing OS image), and the customer can re-attempt the update.
• If an OTA update is applied but fails to boot, the device will reboot back (fallback) into the old/existing OS image and device remains usable. This allows our customer to re-attempt the update.

Rescue Party Mode

• Calchì volta i dispusitivi ponu finisce in cicli di reboot, chì causanu i clienti file support tickets or warranty inquiries. This process is frustrating for customers and expensive.
• Android on SDM660 includes a feature that sends out a “rescue party” when it notices core system components are stuck in crash loops. Rescue Party then escalates through a series of actions to recover the device. As a last resort, Rescue Party reboots the device into recovery mode and prompts the user to perform a factory reset.
• Rescue party logs can be collected using RxLogger. One must enable RxLogger plugin for recovery mode to collect rescue party logs.

Recovery logs
L'utilizatore pò piglià logs di ricuperazione cù RxLogger. Unu deve attivà u plugin RxLogger per u modu di ricuperazione per cullà i logs di ricuperazione.

• User will not be able to pull recovery logs from /data/tmp/public/recovery path which was available in Android Oreo & Pie.
• Last 10 Recovery logs are saved under this folder for debug purposes.

FAQ

• Q: Quali dispositi sò supportati da sta versione?
  • A: This release supports TC53, TC73, TC22, HC20, HC50, TC27, ET60, TC58 devices. Refer to the Addendum Section for more details.
• D: Cumu possu assicurà chì u mo dispositivu sia cunforme à l'aghjurnamenti di sicurezza?
  • A: Download and install the LifeGuard Update 14-28-03.00-UG-U60 for compliance up to June 01, 2025.

Documenti / Risorse

Software ZEBRA Android 14 AOSP [pdfGuida di l'utente TC53, TC73, TC22, HC20, HC50, TC27, ET60, TC58, Software Android 14 AOSP, Android 14, Software AOSP, Software

Referenze

• Manuale d'usu