3 ms·
You can't 'take a snapshot of its RAM' - if you could, there would be no need for NAND write block, you'd just patch the PIN delay/limit functions directly in R
by 05 11y ago
You can't 'take a snapshot of its RAM' - if you could, there would be no need for NAND write block, you'd just patch the PIN delay/limit functions directly in RAM. CPU and RAM are stacked into the same IC package https://en.wikipedia.org/wiki/Package_on_package https://en.wikipedia.org/wiki/Package_on_package
Secondly, there is a separate issue of the SoC hardware state that's contained in registers separate from DRAM (including CPU state). Rewriting DRAM contents does nothing to change that state.
- mistaken 11y agoWouldn't it be possible to take a copy of the NAND and run the whole thing in an emulator? If they can reverse-engineer the decryption algorithm, they wouldn't even need that. Edit: It seems that there is a device specific encryption key that may be hard to extract. Bring on the electron microscopes! http://searchmobilecomputing.techtarget.com/tip/How-iOS-encryption-and-data-protection-work http://searchmobilecomputing.techtarget.com/tip/How-iOS-encr...
- 05 11y agoAnti-fuses seem to be difficult to read even with electron microscopes. http://chipdesignmag.com/display.php?articleId=5045 http://chipdesignmag.com/display.php?articleId=5045