verifier: update to support certificates using SHA-256

Change-Id: Ifd5a29d459acf101311fa1c220f728c3d0ac2e4e
start healthd in recovery

Change-Id: I16e3e0ddb8ca062431deb4be83c5be5eb786d76f
recovery: copy logs to cache more aggressively

Copy logs to /cache immediately upon a package installation failure;
don't wait for recovery to finish.  (If the user reboots without
exiting recovery the "right" way, the logs never get copied at all.)

Change-Id: Iee342944e7ded63da5a4af33d11ebc876f6c0835
recovery: preserve recovery logs across cache wipes

When doing a cache wipe or a factory reset (which includes a cache
wipe), save any last* log files in the /cache/recovery directory and
write them back after reformatting the partition, so that wiping data
doesn't lose useful log information.

Change-Id: I1f52ae9131760b5e752e136645c19f71b7b166ee
fix secure adb in recovery

Recovery's init.rc was missing a line (added to the main system's
init.rc in change Ic97fd464440ff4a29fc9da7ad15949ac5215ade3) is
required for secure adb to work.

Change-Id: Id79b94d2abb4cbe3cca7cabeb4bc5faf7205e56b
recovery: fix mounting voldmanaged volumes

Starting from 4.4, voldmanaged volumes now have the mount point set
to "auto", which recovery will have to handle.

This is done by setting the mount point to /storage/[label], and
modifying vold to mount to /storage/[label] instead of
/mnt/media_rw/[label].

Other explored, but dropped, options include:
 - Setting the mount point directly to /mnt/media_rw/[label] does not
   work because vold expects the volume to be in form of /storage/[label]
 - We can also also use a symlink to /mnt/media_rw/[label], but that
   requires mangling with mtab when checking which partitions are mounted
   and also breaks install scripts which make certain assumptions
   (particularly, aries)

Requires http://review.cyanogenmod.org/53733

Change-Id: I4d35fd81edbc9cbed1812caa5c93e5fb5384154a
Signed-off-by: Chirayu Desai <cdesai@cyanogenmod.org>
Merge remote-tracking branch 'cm/cm-11.0' into kk4.4-temp