recovery: don't overallocate for get_android_secure_path

We simply need the space to fill both strings and a final null.

a char pointer is a lot larger than a char ;)

Change-Id: I3472e1a9978fb2f6d439d4af9c072a98cec0cd19
recovery: fix --update_package using legacy path

When using legacy path, recovery will not be able to mount the
correct device. Fix by resolving the symlink before installing.

Change-Id: Ibb268908458c49de09204a1a0ba3143e83ccc0c4
Merge "recovery: fix --update_package using legacy path" into cm-10.2
Revert "recovery: fix --update_package using legacy path"

Backing this out for now to prevent a tragic recovery loop
where it'll keep restarting to flash from /cache/recovery/command
and crash from signature verification bug. The loop can only
be ended by removing the command file via adb.

This reverts commit ca028615e43fe09c3dcceeb47ca8cf3ceb08c2b4.

Change-Id: Iea29ee04871e136c680df699f5d19570aba44113
Merge "Revert "recovery: fix --update_package using legacy path"" into cm-10.2
recovery: Don't link with minivold

 * There are issues with conflicting symbols in OpenSSL that cause some
   nasty problems. Let's just build minivold as a standalone binary so
   we avoid anything like this in the future as well.

Change-Id: I691a403bb377171989cba4ff74a515050862be40
Revert "Revert "recovery: fix --update_package using legacy path""

This reverts commit ea09a67a552e58835f82382cc76b59b892535468.

Change-Id: I172ec887dd52e373d249d61b22eccaaae03dfb75
Recovery: Loki patching support

Add support for automatically checking and making loki images
for locked bootloader bypass on loki supported devices. Loki
support is enabled with ENABLE_LOKI_RECOVERY.

Change-Id: I81fe267d58f0dda18a790e25df223f011dca3e37
Don't print any messages regarding sd-ext to the UI

 * It is ancient.

Change-Id: Ie2e31f9e3c8a2753dccb1bd42425cd5b0ce7780b
Merge "Recovery: Loki patching support" into cm-10.2