If your objective is to sell a stolen iPhone then you still have to know the owners Apple ID and password due to activation lock. Being able to bypass Touch ID isn't going to help you.
The last SoC where this has been the case is the A5 (using the the ARM Cortex-A9 MP). The Apple A6 and A7 don't use ARM cores and neither does Qualcomm in their Snapdragon SoCs.
The CPU? ARMv8 isn't a thing, it's an instruction set specification, just like x86, implemented by various micro-architectures. Samsung doesn't do that (yet).
> You could create a new account for each kid. At a mininum, this means that you have to re-purchase all the paid apps from every account.
Not necessarily, you could have separate iCloud accounts for each family member and one shared iTunes/App Store account. You can use a different account for iTunes and the App Store, so you don't have to change accounts all the time. At least that's what we do.
Cook: "I have, yes. Both of those—and some others. What I see, for me, is that some of these are confusing, multiple OSs with multiple UIs [user interfaces]. They steer away from simplicity. ..."
> Unfortunately, it used big endian, whereas the DCPU-16 specifications called for little endian. This led to a severe bug in the included drivers, causing a requested sleep of 0x0000 0000 0000 0001 years to last for 0x0001 0000 0000 0000 years.
Not really a "secure" workstation if you can't have a secure bootchain. An open, secure platform would allow you to fuse your own root key.