diff options
author | Doug Zongker <dougz@android.com> | 2012-01-09 15:16:13 -0800 |
---|---|---|
committer | Doug Zongker <dougz@android.com> | 2012-01-10 10:18:17 -0800 |
commit | 9270a20a801403c9f60d6a701b39eae70d380403 (patch) | |
tree | 5bdb058af5b05a65112297a504018ee356e0ddbb /device.h | |
parent | 210f887382e0fd7e51ec6ce071972374a76f0722 (diff) | |
download | bootable_recovery-9270a20a801403c9f60d6a701b39eae70d380403.zip bootable_recovery-9270a20a801403c9f60d6a701b39eae70d380403.tar.gz bootable_recovery-9270a20a801403c9f60d6a701b39eae70d380403.tar.bz2 |
support "sideload over ADB" mode
Rather than depending on the existence of some place to store a file
that is accessible to users on an an unbootable device (eg, a physical
sdcard, external USB drive, etc.), add support for sideloading
packages sent to the device with adb.
This change adds a "minimal adbd" which supports nothing but receiving
a package over adb (with the "adb sideload" command) and storing it to
a fixed filename in the /tmp ramdisk, from where it can be verified
and sideloaded in the usual way. This should be leave available even
on locked user-build devices.
The user can select "apply package from ADB" from the recovery menu,
which starts minimal-adb mode (shutting down any real adbd that may be
running). Once minimal-adb has received a package it exits
(restarting real adbd if appropriate) and then verification and
installation of the received package proceeds.
Change-Id: I6fe13161ca064a98d06fa32104e1f432826582f5
Diffstat (limited to 'device.h')
-rw-r--r-- | device.h | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -66,7 +66,7 @@ class Device { virtual int HandleMenuKey(int key, int visible) = 0; enum BuiltinAction { NO_ACTION, REBOOT, APPLY_EXT, APPLY_CACHE, - WIPE_DATA, WIPE_CACHE }; + APPLY_ADB_SIDELOAD, WIPE_DATA, WIPE_CACHE }; // Perform a recovery action selected from the menu. // 'menu_position' will be the item number of the selected menu |