iPhone 13 Pro update fails: Error 100, insufficient space
Hi everyone,
I’m trying to update/revive my iPhone 13 Pro, but it keeps failing with:
- AMRestoreErrorDomain error 100
- Restore Checkpoint Fingerprint: 06A6.0064
- failed to install splat
- install_splat / Cryptex1,SystemOS
The device is currently detected by Apple Configurator as:
- deviceType: iPhone14,2
- bootedState: Restore
- isRestorable: true
- pairingAllowed: false
- isPaired: false
I have already tried:
- macOS is up to date
- Apple Configurator revive
- Finder/Updater update path
- signed IPSW only
- official Apple cable
- direct connection, no USB hub
- Recovery mode
- I have not intentionally selected Erase/Restore yet because I’m trying to preserve data
The most important part of the log seems to be this:
text ramrod_splat_install: Installing Cryptex1,SystemOS -> /mnt9/cryptex1/current/os.dmg Transfer: Receiving 2013265920 bytes, writing 5236588544 bytes Transfer: Failed preallocation of 5236588544 bytes for /mnt9/cryptex1/current/os.dmg Transfer: Failed preallocation due to space. No hope in this succeeding, bailing. ramrod_splat_install: install handler failed CHECKPOINT FAILURE:(FAILURE:100) [0x06A6] install_splat Restore Checkpoint Fingerprint: 06A6.0064
Earlier in the same log, the update path says:
text requested restore behavior: Update Found variant: Customer Upgrade Install (IPSW)
So this was an update attempt, not an intentional erase/restore.
My questions:
1. Has anyone successfully recovered from Error 100 / 06A6.0064 / failed to install splat without erasing the iPhone?
2. Would DFU + Apple Configurator “Revive Device” have a real chance of preserving data in this specific case?
3. Is this more likely caused by low iPhone storage, APFS/container corruption, Cryptex/SystemOS install failure, or NAND/storage failure?
4. Is there any known way to free space or complete the update while the device is stuck in Restore mode?
5. If the log says “Failed preallocation due to space,” is Restore/Erase the only realistic solution?
I’m trying to avoid data loss if possible. Any advice from people who have seen this exact checkpo