remove unused variable

Change-Id: I0f66df38964baccd1c8e58fa7006cb9db5fc6df5
Make legacy prop environment available to recovery

Google changed the in-memory format for storing properties in 4.4.
Zips containing an older update-binary expect the old format, otherwise
assertions on properties in the update script fail.

This is just enough of the old property service to copy the properties
to the legacy format before running the updater.

Note: this commit has been amended from the original version by _that.
1) It has been trimmed to only provide the legacy prop environment.
Edits to install.c are done in a separate commit from scratch to
maintain apache2 licensing in this repo.
2) Return values are given to check whether prop environment was setup
successfully.
3) Slight formatting changes.

Change-Id: I1fa9f96fa7a62c7eaba852e4d62e793cd6818907
Use legacy property environment if old update-binary

If an installation package contains an update-binary that is
incompatible with the kitkit bionic property environment, set a legacy
property environment. This removes the need for a fallback update-binary
which is often incompatible with older update-scripts.

Method of setting prop environment based on cyanogen's commit:
"Set ANDROID_PROPERTY_WORKSPACE in exec." Tip to rename
/dev/__properties__ so that the legacy property workspace is actually
used comes from conversation with _that.

Change-Id: I5268f67537ad03c077fa05cbb98dfd4da194ffb8
Revert "Add a copy of the updater binary to the recovery resources"

No longer necessary when a legacy property environment is available.

This reverts commit 1153ae5ad9a25198e4edfa7ff9b0bce7f9d40220.

Change-Id: I9726f45d896eb3e14b80e2ddf1df5e6acea83323
Only init legacy property environment once

Installing multiple pre-kitkat packages in succession may cause
legacy_properties_init() to fail. Only initialize the workspace once and
then just do path renames for all subsequent requests to enable legacy
props.

Change-Id: Ida528aca9322f77935411b270fdf182828abab8a
loki updates:

- fix fstat could fail on getting open partition size
- sync latest sources to support new devices
- match original loki upsteram sources
- fix all loki_recovery compiler warnings
- one binary for all functions patch/flash/find
- Makefile and Android.mk to compile new multi-binary tool or lib
Change-Id: I050a673f39b32136c817b69c00939818696e2c56
allow using custom recovery_ui.c

Change-Id: Ib89c3fc7783dcb384af0964892ce5b200f5433a5
mounts: add find_mounted_volume_by_real_node
this function finds a mounted volume by the real device node(resolved symlink)

Change-Id: Iff28cf7dd088f73248e23d99bf321f2bb61e1cc2
add basic support for native dualboot

Change-Id: I3808c5e77007d27311d7dfe0e3b1f52bc01a9794
allow changing menu color

Change-Id: I0b78c1ec93fc13796f49c275c308192cf744aa61
dualboot: add truedualboot support

Change-Id: I33dec96da48700307550be05807a6b78d5e8b08c
dualboot: add menu item under advanced to set bootmode
- also refresh dualboot entries everytime before calling 'get_filtered_menu_selection'
  to sync changes

Change-Id: I717cef001733d5edf1edea73ecc724edb1fd3fa2
dualboot: handle 'format_device'

Change-Id: I674608c2402f618502dee75148eb13b8836bb3e9
Version 6.0.4.8

Change-Id: I05cc1417f906cf2d3696bee457f4b095ee201a85
Merge remote-tracking branch 'cm/cm-11.0' into kk4.4