Wiki

Flash and firmwareFree

iPhone restore failed? Restore error codes and the recovery console

Updated 7 min read

A failed restore leaves two questions: where did it stop, and why. BenchDock keeps a log of every restore it runs and rebuilds each attempt in the Recovery console. Error codes from BenchDock, Finder, iTunes, Apple Devices or 3uTools can be looked up in the knowledge base, which explains 73 codes with the cause and what to check.

Open the recovery console

  1. Click Flash & firmware in the sidebar.
  2. Open the tab Recovery console. The list on the left shows every restore run on this PC, newest first, with the model, date, restore type and iOS versions.
  3. Click an attempt. A green dot means Completed, red means Failed, orange means Interrupted.
Two failed attempts and one completed attempt on the same device. The reconstruction shows how far each attempt got.

What the console shows

Summary. When the attempt started and how long it took, update or clean install, the firmware, the iOS version before the restore, the chip ID (ECID) and the mode the device is in now: connected in normal mode, in recovery mode, in DFU mode, in restore mode or not connected.

What went wrong and what to do. For a failed attempt, BenchDock names the cause it found in the log and the next step:

CauseWhat BenchDock advises
Apple key serverThe file system transfer failed after a key request to Apple. After an update: retry with Update and do not erase. After a clean install: check the connection to Apple and try again.
Signing (TSS)Apple did not sign the installation. Check that the version is still signed.
NetworkThe connection to Apple failed. Try another network.
USB connectionCommunication with the device failed. Check the cable and port.
UnknownSee the log for the cause.

After a failed update, the advice always keeps the data in mind: the data may still be on the phone, so retry with Update and do not erase.

Failed at the same point. If earlier attempts on the same device stopped at the same step, the console says so, for example Failed at the same point 3 times. Retrying with the same setup rarely helps then. Change the network, the cable, the USB port or the firmware file first.

Reconstruction. Every phase of the restore in order, with the time and the log line where it happened:

  1. Device detected
  2. Signing by Apple (SHSH)
  3. Into recovery mode
  4. Restore bootloader sent
  5. Restore system sent
  6. Device in restore mode
  7. Storage prepared
  8. Boot firmware written
  9. Keys from Apple requested
  10. iOS system being sent
  11. System verified
  12. Modem firmware
  13. Component firmware
  14. Final steps
  15. Restore finished

Below the phases you see the last phase reached, the last completed checkpoint of the restore process on the phone (with the number of completed checkpoints and any failed one), and the last communication with the device. That last line tells you whether the phone was still talking to the PC when it went wrong.

Error codes in this log. Numeric codes found in the log, each with its meaning and steps. BenchDock's restore tool rarely prints a number; the category above is then the best clue.

Relevant error lines and Attempts on this device complete the picture: the raw error lines, and all restores of the same device side by side with the phase and checkpoint where each one ended. Log opens the complete log file.

Read the reconstruction

Where an attempt stops says a lot about the cause:

  • Around signing by Apple: a network problem, or the version is no longer signed. Check the plan again; BenchDock tests Apple's servers before it starts.
  • While sending the restore bootloader or system: usually the USB connection. Use an original cable directly in the PC and another port.
  • At the key request or while the iOS system is sent: often the network. Some networks drop IPv6 connections to Apple's key server; see how to turn off IPv6.
  • Later, while storage or modem firmware is written, and again at the same point with a good cable and network: suspect the hardware. In workshop experience that is often the storage (NAND) or the baseband.

Restore error codes

Apple groups the error codes of Finder, iTunes and Apple Devices by cause. BenchDock uses the same groups. The table lists the codes in BenchDock's knowledge base.

CodesMeaningWhat to do
9, 4005, 4013, 4014The device disconnected during the update or restoreUse an original cable directly in the PC. Retry with Update before you try a clean install. Try another port and another computer.
17, 1109, 1638, 1639, 3000, 3002, 3004, 3013, 3014, 3015, 3194, 3200The computer cannot reach Apple's serversCheck the internet connection, turn off VPN, proxy and security software, check the hosts file for Apple entries. BenchDock only offers signed versions, so with BenchDock these codes point to the network.
2, 4, 6, 1611Security software blocks the connectionUpdate or temporarily turn off antivirus and firewall software, then check the USB connection.
13, 1600–1604, 1611, 1643–1650, 2000, 2001, 2002, 2005, 2006, 2009USB connection problemUse the original cable or another Apple-certified cable, another USB port (not on a keyboard or hub), or another computer.
1, 3, 11, 12, 13, 16, 20, 21, 23, 26–29, 34–37, 40, 56, 1002, 1004, 1011, 1012, 1014, 1667, 1669Possible hardware problemCheck the security software and make sure cable, computer and network are reliable. If the error comes back, the device may need a hardware repair.
10The iOS on the device is newer than the software on the computerUpdate Windows, Apple Devices or iTunes, and BenchDock.
14Low storage on a device with iOS 13Restart the device if it stays on the Apple logo, then update with data kept to the signed version.
53The Touch ID check failedTry an update first. If Touch ID already failed before the error, the sensor needs service.
1015The required resource can't be found: a downgrade, or a modified (jailbroken) systemInstall the latest signed version from recovery mode.
1671The computer is still downloading softwareWait until the download is complete, then try again.
4037The device is locked with a passcodeUnlock the device and keep it unlocked during the update.

Apple's article on network errors also names the ranges 3000–3020 and 3100–3999 as network-related.

Workshop experience

Besides Apple's groups, the knowledge base shows hints from repair practice, marked Workshop experience. They are not confirmed by Apple:

  • 9, 4013, 4014: keeps failing at the same point with a good cable and another port? Measure the NAND and its supply. NAND work means data loss.
  • 40: storage (NAND) or logic board.
  • 29: battery. Test with a known-good battery charged above 30 %.
  • 1: baseband. Check for liquid or drop damage near the modem.
  • 53: a replaced Touch ID sensor cannot pair with the board. Reconnect the original sensor and check the home button flex.
  • 1110: hardware.

Look up a code

  1. Click Knowledge base in the sidebar.
  2. Type the number in the search field at the top. The table Restore and update error codes shows the meaning, whether hardware is likely and whether the customer's data is at risk.

More about the knowledge base: Knowledge base.

Before the next attempt

  1. Read the cause in the console and change one thing: the cable, the USB port, the network or the firmware file.
  2. Check the drivers if the phone disconnected.
  3. After a failed update, retry with Update. Only choose a clean install when the data is not needed or no update succeeds.
  4. If the phone is stuck in recovery mode while iOS is intact, try Exit recovery mode on the Flash tab first.