system_recovery is the primary executable in the recovery system. The recovery system is a second, standalone instance of Fuchsia that runs on devices to recover the primary Fuchsia system when the primary Fuchsia system is inoperative.
You can build the recovery image using the following command:
$ fx build build/images/recovery
This command builds several
recovery-*.zbi files in
obj/build/images/recovery, which are self-contained archives of the recovery system.
After building the recovery image, you can run the image in QEMU using the following command:
$ fx run-recovery -g
The easiest way to run recovery on hardware is to netboot a device into a newly built recovery image:
$ out/default/host-tools/bootserver --board-name device-name --boot out/default/obj/build/images/recovery/recovery-eng/recovery-eng.zbi
device-name can be found with
NB If you only have one device or have used the
fx set-device command you can omit the
After building the recovery image, you can flash it via the following commands:
fastboot erase vbmeta_a && \ fastboot erase vbmeta_b && \ fastboot flash vbmeta_r recovery-eng.vbmeta && \ fastboot flash zircon_r recovery-eng.zbi && \ fastboot stage /home/fuchsia/.ssh/authorized_keys oem add-staged-bootloader-file ssh.authorized_keys && \ fastboot continue
The above block will disable the A/B slots so that we default into recovery, provisions the R slot with recovery-eng, then stages the SSH authorized keys for recovery-eng to enable SSH access. The device can then be accessed via the standard ssh-based fx commands like
Build the core product with recovery:
$ fx set core.x64 --with //src/recovery $ fx build
Load the system you've just built onto your device.
Run the system recovery unit tests:
$ fx test -s 5 system_recovery_tests
Note that test_ui requires display access, so using a product other than “core” will likely cause these tests to fail.
Run the recovery integration test:
$ fx test -s 5 recovery_integration_test
TODO: Need to create end-to-end tests.