Sami Tolvanen 43b748f254 Don't remove existing explicitly stashed blocks
When automatically stashing overlapping blocks, should the stash
file already exist due to an explicit stash command, it's not safe
to remove the stash file after the command has completed.

Note that it is safe to assume that the stash file will remain in
place during the execution of the next command, so we don't have
take other measures to preserve overlapping blocks.

The stash file itself will be removed by a free command when it's
no longer needed.

Bug: 20297065
Change-Id: I8ff1a798b94086adff183c5aac03260eb947ae2c
2015-04-17 13:07:08 +01:00
2014-12-18 22:50:08 +00:00
2015-01-08 16:02:46 -08:00
2013-03-07 13:34:24 -08:00
2015-04-10 13:59:19 -07:00
2015-04-15 10:58:56 -07:00
2013-10-10 14:19:19 -07:00
2014-10-17 01:05:08 +00:00
2015-01-29 20:50:08 -08:00
2015-04-10 13:59:19 -07:00
2015-01-28 12:09:05 -08:00
2014-04-25 15:47:34 -07:00
2015-04-13 15:46:15 -07:00
2015-01-29 20:50:08 -08:00
2015-04-10 13:59:19 -07:00
2015-04-15 10:58:56 -07:00
2015-04-15 10:58:56 -07:00
2015-04-13 13:04:32 -07:00
2015-04-13 13:04:32 -07:00
2015-01-28 12:09:05 -08: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
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%