Johan HarvylandJohan Redestig 8569142147 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
2016-08-08 08:28:30 +02:00
2016-06-10 13:45:35 -07:00
2016-04-18 12:29:30 -07:00
2013-03-07 13:34:24 -08:00
2016-06-16 19:57:20 -07:00
2016-08-01 11:32:28 -07:00
2016-04-18 12:29:30 -07:00
2016-06-10 13:45:35 -07:00
2015-01-28 12:09:05 -08:00
2016-06-10 13:45:35 -07:00
2016-06-09 21:46:13 -07:00
2014-04-25 15:47:34 -07:00
2016-06-10 13:45:35 -07:00
2016-03-02 17:31:05 -08:00
2016-06-10 13:45:35 -07:00
2016-06-10 13:45:35 -07:00
2016-02-04 10:11:30 -08:00
2016-06-10 13:45:35 -07:00
2016-04-18 12:29:30 -07:00
2015-06-02 22:15:40 -07:00
2016-04-15 20:27:44 -04:00
2016-04-18 12:29:30 -07:00

The Recovery Image

Quick turn-around testing

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

Running the tests

# 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
S
Description
No description provided
Readme
102 MiB
Languages
C++ 50.2%
C 43.6%
Makefile 1.9%
Java 1.8%
Roff 1%
Other 1.4%