Disconnects, enumeration loss, cable/port instability
Confirm host port, cable, device connector, USB-controller power and repeatability before NAND or sandwich work.
Interpret restore errors using the exact log, restore phase, USB transport state, NAND/baseband/security evidence and board measurements. Progress percentage alone is not a hardware verdict.
Error number + percentage + exact failing command + electrical evidence should agree before BGA or destructive repair.
The uploaded source divides restore into percentage windows. V2 preserves the stages but explicitly treats percentages as tool/build-dependent observations.
Select an error family to build a safe bench route.
Paste Apple Devices/Finder/iTunes/Configurator/3uTools log text or use a sample.
Uploaded-source values are kept as source references. Exact-model known-good measurements take priority.
| Domain | Rail / Signal | Source Voltage | Source GR | Resistance | Scope / State | What abnormal supports |
|---|
Classify the electrical state without turning it into an automatic IC diagnosis.
Use the exact symptom family before invasive board work.
Confirm host port, cable, device connector, USB-controller power and repeatability before NAND or sandwich work.
Confirm storage rails, reset/interface and repeated read/write failure. Error 9/4013 alone is not sufficient.
Check modem power/reset/clock/IPC and baseband identity before interposer rework.
Use exact restore-log text plus paired/peripheral state; do not map an 80% halt to Face ID/NFC universally.
Preserve data goals first. Do not recommend destructive erase as the first action when data recovery matters.
Check USB transport, PMIC/SoC/RAM rails and repeatability before CPU/RAM reball.
Generate a standardized record for future comparison.