Upgrader

Differences between revisions 2 and 3
Revision 2 as of 2013-05-02 21:39:35
Size: 892
Editor: stgraber
Comment:
Revision 3 as of 2013-05-02 22:19:14
Size: 1016
Editor: 66-192-7-242
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:

= Notes/TBD =
== Interfaces ==

The client needs this API to inform the upgrader what to apply: __system_property_set

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

The client needs this API to inform the upgrader what to apply: system_property_set

ImageBasedUpgrades/Upgrader (last edited 2014-07-04 14:36:06 by sergiusens)