MiniOS, also known as the Network Based Recovery (go/cros-nbr), is a “mini” version of CrOS designed specifically for device recovery. It is used to recover ChromeOS devices that are unable to boot normally.
MiniOS can be used to repartition the disk, wipe the stateful partition and all user data, and update to the latest stable version of ChromeOS.
MiniOS is brought up with Upstart, similar to ChromeOS. The majority of the scripts are located in platform2/init/upstart with some MiniOS specific processes located in minios/init.
MiniOS graphics are done with frecon-lite and can show images and draw shapes. The layout of MiniOS elements is based on the frecon canvas size and scaling factor which are from frecon.conf. The images are created with Pango during build time with no run time size or color changes supported.
KeyReader is how MiniOS processes input. There are two types of input KeyReader handles.
The first type is basic navigation using the up, down, and enter keys. This is used to navigate between screens and make basic selections. This type of input uses an Epoll file descriptor which sends all input to ScreenController so each screen can decide what action to take based on user input.
The other kind of functionality KeyReader supports is taking in alphanumeric input, which is used for things like the network password; this does not use the watcher. For this type of input, KeyReader must be given a keyboard layout to correctly map key codes to characters. Currently, there is no foolproof way to do this, but the region information is read from VPD and then mapped to a list of supported chrome keyboard layouts using cros-regions.json. Due to the size and complexity constraints of MiniOS, only standard ASCII characters are processed. Other special characters such as “ê” are ignored even if they are a part of the keyboard layout.
To build MiniOS image, create ${OUT_DIR} and run
# ${VERSION} can be an arbitrary string build_minios --board ${BOARD} --kernel-only --kernel-output ${OUT_DIR} \ --version ${VERSION} --mod-for-dev --force-build
Alternatively, to manually build the MiniOS kernel and pack it, run
# Build /build/${BOARD}/boot/vmlinuz # ${KERNEL_EBUILD} is chromeos-kernel-6_6 for example USE="minios minios_ramfs" emerge-${BOARD} ${KERNEL_EBUILD} # Pack vmlinuz as ${OUT_IMAGE} vbutil_kernel --pack ${OUT_IMAGE} \ --keyblock /usr/share/vboot/devkeys/minios_kernel.keyblock \ --signprivate /usr/share/vboot/devkeys/minios_kernel_data_key.vbprivk \ --version 1 \ --arch ${ARCH} \ --config ${KERNEL_CONFIG} \ --vmlinuz "/build/${BOARD}/boot/vmlinuz"
Currently update_kernel.sh doesn't support flashing MiniOS kernels (partitions 9 and 10). Therefore, scp the image to DUT and run dd.
To modify MiniOS configs on DUT, run
/usr/share/vboot/bin/make_dev_ssd.sh --minios_key --partitions '9 10'
along with other flags (such as --enable_earlycon or --set_config).
To flash MiniOS partitions from an OS image, pass --minios-update to cros flash.
MiniOS can be test on devices which don't have the newer partitions for miniOS. The way to test is by repartitioning the device.
On locally available DUTs:
minios USE flag.chromeos-install the image from USB.On lab DUTs:
# Find the correct SERVO_PORT (e.g. 9996, 9997) $> start servod PORT=$P $> dut-control -p $P power_state:off # Only for devices with battery and type-c connection to servo with PD. $> dut-control -p $P servo_pd_role:snk # Download a image to flash or use a cache server URL. # The flashing of USB might take some time. $> dut-control -p $P download_image_to_usb_dev:$PATH_OR_URL $> dut-control -p $P image_usbkey_direction:dut_sees_usbkey $> dut-control -p $P power_state:rec
# Verify that the DUT has booted from USB. $> rootdev -s # should be /dev/sd* $> /usr/sbin/chromeos-install $> reboot
The device will now use the newer layout with miniOS support.