* We are aren't launched with Android at all to, but
our partitions were origianlly set up to match
foster, as it is our closest hardware counterpart.
* Those partition sizes are now to small to fit
almost any form of GMS.
* The fact that users have to exploit their console,
run a custom first stage bootloader (Hekate), and
applications bootloader (u-boot) that we control
means that instead of retrofitting dynamic partitions
we can just _launch with them_ (as we have yet to ship
this device).
* Treat this device as if it has always had dynamic
partitions and let Hekate set us up to reflect that.
* Do away with SAR in the process, as Hekate can turn
that off.
* Nuke MDA, we don't support hardware backed encryption
anyway, so it doesn't make any sense to house.
Reference: https://github.com/CTCaer/hekate/pull/922
Change-Id: I1e5d8c309d08559873ea3c93ac5b4b6e197b528e
tmakin
14af49d754