A device should be listed under adb devices, either in recovery or sideload state. eng or -userdebug build variants, or ro.debuggable=1 in /fault), adbd service is enabled and started by default, which allows adb communication. When running recovery image from debuggable builds (i.e. Test will pass if this file has expected contents. The test should save the contents of pmsg buffer into /data/misc/recovery/inject.txt. Reboot the device immediately and run the test again. The test should fail but it will log some contents to pmsg. And we need to follow special steps to run tests for them.Įxecute the test on an A/B device first.
Recovery-refresh and recovery-persist executables exist only on systems without /cache partition. # Running the tests on device (under normal boot).Īdb shell /data/nativetest/recovery_unit_test/recovery_unit_testĪdb shell /data/nativetest64/recovery_unit_test/recovery_unit_test Running the tests # After setting up environment and lunch. # To boot into the new recovery image without flashing the recovery partition:įastboot boot $ANDROID_PRODUCT_OUT/recovery.img Mm -j & m ramdisk-nodeps & m recoveryimage-nodeps Nexus) # After setting up environment and lunch. # Manually choose `Recovery mode` from bootloader menu.ĭevices with a separate recovery image (e.g. # Pixel devices don't support booting into recovery mode with `fastboot boot`. Pixels, which set BOARD_USES_RECOVERY_AS_BOOT) # After setting up environment and lunch. The Recovery Image Quick turn-around testingĭevices using recovery-as-boot (e.g.
0 kommentar(er)
