commit | b08381861248ee9bb3c134fcb4371398fbef32b0 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Thu Jun 02 11:16:50 2016 -0700 |
committer | Tao Bao <tbao@google.com> | Fri Jun 03 14:43:05 2016 -0700 |
tree | 544d88513b20b0b097676df8347e1bb7002449ba | |
parent | 01fcbe160bd49891c0680b80c5688cd4feb2adbc [diff] |
recovery: Add support to brick a device. When recovery starts with --brick, it tries to brick the device by securely wiping all the partitions as listed in /etc/recovery.brick. This is designed to support bricking lost devices. Bug: 27253717 Change-Id: Ib0bd4f0a3bdaca4febc91fce6b682e3ec74354e2 (cherry picked from commit 862a4c11190d72851a72a2b97375ec2698078358)
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test