commit | 8569142147f8ba7ec6a3431f96aa00d66b45db61 | [log] [tgz] |
---|---|---|
author | Johan Harvyl <johan.harvyl@sonymobile.com> | Fri Aug 05 15:42:59 2016 +0200 |
committer | Johan Redestig <johan.redestig@sonymobile.com> | Mon Aug 08 08:28:30 2016 +0200 |
tree | c2f0d66fee901caecd5954f4d2b0aea101be4264 | |
parent | 61240f88ead5c68424eab72194641a2310e59c3b [diff] |
Handle error from fopen_path in finish_recovery The fopen_path will fail here e.g. if /cache is corrupt and could not be mounted. Not properly handling an error code from fopen_path() results in a boot loop into recovery as fwrite() on a NULL FILE object will crash the recovery app. Change-Id: I1ccff5a8cb620a32f32adfe97a3fae8e5e908f39
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