ota_from_target_files: Validate signatures after possible data wipe

If the data is being wiped, we want to validate the signature after
this step. This is also a good check that the data wipe succeeded.

Change-Id: Iaecfddfb2010944de0c97e7bb21d8e581f20deec

Conflicts:

	tools/releasetools/ota_from_target_files
Restore VerifySignature to edify_generator

Change-Id: If5fedb9b1b98394c0bee3efc3523d0e2f9499887
vanirified (cflag no-op on most devices): Apply correct, optimized mfpu compiler flag for ARMv7-A Cortex CPUs

For those ARMv7-A Cortex CPUs that can handle VFPv4 floating point,
We can set "-mfpu=neon-vfpv4" instead of generic "-mfpu=neon"
to gain extra performance improvements.

References :
 - GCC		: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
 - Cortex A15	: http://www.arm.com/products/processors/cortex-a/cortex-a15.php
 - Cortex A9	: http://www.arm.com/products/processors/cortex-a/cortex-a9.php
 - Cortex A8	: http://www.arm.com/products/processors/cortex-a/cortex-a8.php
 - Cortex A7	: http://www.arm.com/products/processors/cortex-a/cortex-a7.php
 - Cortex A5	: http://www.arm.com/products/processors/cortex-a/cortex-a5.php

Change-Id: Id8b1a251234014ecf7ffbc1ae14455ed1726e028
Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>

Conflicts:

	core/combo/arch/arm/armv7-a-neon.mk
determine recommended mfpu based on cpu_for_optimizations, in case TARGET_ARCH_VARIANT_CPU is set but TARGET_ARCH_VARIANT_FPU is not.

Change-Id: Idae1bba8411b64eb9c34882eee2cbe73d26d65ad
Merge branch 'bootzip' of github.com:bart452/build into HEAD
bump to 7.5+

Change-Id: I3bbdf875005b622e6c4eb57721425dd0aa2992c4