Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)

Hello,

I am requesting an engineering escalation regarding a critical bug in
Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in
recovery mode during an official Finder update from iOS 16.6 to iOS 18
(27.2.1, 24B156) on macOS 14.5. 

The device hardware is 100% healthy (Apple MRI diagnostics all green),
the passcode is known, and 101,175 MB (341,967 files) of user data remain
intact on the flash storage. However, the device cannot boot or complete
an update due to a corruption caused by Apple's own restore tools.

---

### What Happened (Verified in Logs):
1. **Initial Full Storage State:** The device had ~105 GB utilized and
was updated via Finder using "Update" (not Restore).
2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran
`/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck
erroneously flagged 8,182 live omap mappings as "orphans" and deallocated
them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed
by the flash controller).
3. **Split Failure:** In pass 4, the iOS 18 System volume installed and
sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator`
encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ
/ error 92).
4. **False Error 1110 Loop:** Every subsequent attempt now halts
immediately at `space_checks` with Error 1110.

---

### Reverse Engineering Proof:
Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8)
confirms a major error-handling bug:
When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails
with `EILSEQ` (92). Instead of handling this error, `restored_update`
executes:
  `mov x19, #-1; mov x0, x19; ret`
The caller receives `-1 bytes of free space`, logs:
  "Data volume requires splitting. Splitter will leave -1 bytes of free
  space after completion. Current free space on device: 6620069888 bytes.
  Insufficient space on device to run splitter"
and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**.

The device is NOT out of space (it has 6.3 GB free); it is blocked solely
because `restored_update` misinterprets an EILSEQ filesystem error as
negative free space.

---

### Current State & Request:
- The encryption keys and SEP/gigalocker are intact (`gigalocker:
ONLINE`).
- In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on
`/mnt2`.
- Zero APFS snapshots remain on the volume, meaning the extent-ref tree
is theoretically fully reconstructible from the valid fsroot inode tree.

I am requesting assistance from CoreOS / APFS engineering:
1. Is there an engineering update ramdisk or build that can bypass the
`splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the
update can finalize?
2. Alternatively, can an engineering liaison facilitate a non-destructive
extraction given that the volume mounts read-write and the user passcode
is known?

I can immediately provide full terminal transcripts, Finder updater logs
(`iPhoneUpdater-*.log`), and disassembly details.

Thank you,
Samuel Journo
Answered by DTS Engineer in 917610022

The Apple Developer Forums are here to help developers use Apple APIs, developer tools, and developer services. We can’t help you with this device recovery issue.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

The Apple Developer Forums are here to help developers use Apple APIs, developer tools, and developer services. We can’t help you with this device recovery issue.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"