The one they paid $1,000,000 for in the San Bernardino terrorist case works only on the older iPhone 5c and backwards. It cannot work on the iPhone 5s and later that have the Secure Enclave. . . those are entirely different devices that have far more secure approaches to encryption than those older iPhones which were pretty secure themselves.
The newer ones use four different ICs that are inter-registered so that any attempt to unlock them have to be attempted ON THE DEVICE. Removing any one of those four ICs will brick the device. Even re-installing the removed IC requires that all four of the ICs have to be re-registered with the others and only Apple has the proper equipment and algorithms to do that.
The Encryption Engine processor, with its Secure Enclave, is not even touchable by the A11 data processor. . . so nothing that can be loaded on to the iOS device can affect the data stored in the Secure Enclave or ever read it. There literally is no access. . . and even external test equipment cannot reach it to attempt to read it.
The Secure Enclave is where the Encryption Key is constructed anew each time the user inputs his passcode . . . which is only a small portion of the actual encryption key itself. That encryption key is extremely complex, made up of a hidden Universally Unique ID for the device, assigned at the time the IC is burned and not recorded anywhere, the Model ID, a truly random number generated by the device from environmental inputs from the device's cameras, microphones, movement sensors, and GPS, at the time the user first inputs his AppleID, and the user's passcode, and entangled according to a hidden algorithm also assigned at the time the IC was burned and stored in the Secure Enclave. . . and the user's passcode is not even stored in the device itself, but a one-way HASH is stored instead, and re-calculated each time it is entered according to another algorithm and compared. ONLY if the comparison matches is all the above done to re-create the encryption key and placed into a volatile storage location for use oto decrypt the data as necessary.
The ONLY way all of the above could be discovered is electron microscopic shaving which is destructive of data. . . and requires the removal of the target IC's memory to do. Oops. That won't work because of the destruction of the multilayer ICs just to get at the data locations.
This all has been extremely well engineered to keep hackers out.
That's one of the reasons I upgraded my iPhone when I finally got around to it. That, and the fact that it was no longer able to get security updates because it was too ancient.
I was hoping you'd show up on the thread to combat the FUD.