Change-Id: I418680e59372160dabfe3e2d5f0208229aa151ae

When creating a new file using open(..., O_CREAT), it is an error
to fail to specify a creation mode. If a mode is not specified, a
random stack provided value is used as the "mode".

This will become a compile error in a future Android change.

Change-Id: I73c1e1a39ca36bf01704b07302af4971d234b5a8

Due to a kernel bug and no available sources we have to work around the
MEMERASE ioctl - if used, it hangs and never returns. I straced the original
recovery executable and could see that it is simply calling write() with a
bunch of zeroes instead of using MEMERASE.

Added a hack that does the same and now the resulting TWRP recovery image works.

Change-Id: I1b1c1c9e870e350776346bdca5d442c7ef565aa0

- Until the encrypted partition is decrypted, treat it as a disk image
  instead of a filesystem so that it is properly backed up using dd.
- Make Partition::Wipe() use the filesystem from fstab for disk images
  so that wiping an undecrypted /data makes it a plain unencrypted
  partition again.

Change-Id: I78db977d6348cfa66b0cfbc492fb5776f84db48d

Change-Id: I6c4cee5b038fd0c39c8723412dd8f421f7794a00

Change-Id: I206d34936388c1b072eaaec50e0492710cb80f2e

Change-Id: I8f2b5b68a8c3ede74858d53002efab997174ee65

Change-Id: Ie44958a148d00cadd2ba3c51255f7fd9d8a651e7

Allow to decrypt /data even if decryption was skipped during the initial
loading of recovery

Change-Id: If2251757a276dd069578e93e5a038b25a825bff6

Change-Id: Ibbc3bf3d3264fb9852f8312ece0567950aace496

Also fixed inability to delete backups with a space in the name.

Change-Id: I2f6639d33caa3c4542960f76adbd59b25ab64f5d