Upgrader
|
Size: 1016
Comment:
|
Size: 1169
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| The client needs this API to inform the upgrader what to apply: __system_property_set | Store command into {{{/cache/recovery/command}}} * {{{--update_package=path}}} - OTA package file * {{{--wipe_data}}} - erase user data and reboot * System call: {{{__system_property_set}}} or shell out to {{{adb reboot recovery}}} |
WARNING: This page is still very much work in progress.
Upgrader
Introduction
The upgrader sits in its own partition and applies any update that the client passed it. Those are applied after being validated, any failure stops the upgrade process and attempts a reboot in standard mode.
Implementation
When rebooted into the upgrader partition, the phone will trigger the upgrader. The upgrader will check for any pending update, if found, it'll validate the signature and unpack them sequentially, then apply them to the device, when applied, the file is removed. On failure, the device is rebooted into normal mode with any failed/unapplied update kept on the file system.
When started without a list of update, a recovery menu will be shown to the user, allowing them to perform a factory reset or update from eMMC (from similar gpg signed update files).
Notes/TBD
Interfaces
Store command into /cache/recovery/command
--update_package=path - OTA package file
--wipe_data - erase user data and reboot
System call: __system_property_set or shell out to adb reboot recovery
ImageBasedUpgrades/Upgrader (last edited 2014-07-04 14:36:06 by sergiusens)