Restore Errors

From The Apple Wiki

Here is a list of restore and update errors that could appear during a restore via iTunes, Finder, Apple Configurator 2, Apple Devices, and other third-party software that makes use of MobileDevice for this task. Some general errors encountered while attempting to use a device over USB are also included.

Some common errors can be found at Apple's Knowledge Base. However, the majority are either undocumented, or their documentation is too vague. This article serves to document the underlying cause of an error, and the solutions to try to resolve it.

Errors -31xx[edit]

Error -3198[edit]

Errors -100 ... -1[edit]

Error -2[edit]

Can occur due to NAND Failure or iPhone 7/7 Plus Baseband/Audio IC Failure or in rare circumstances an ever so slightly improperly connected battery. Generally something hardware related.

Error -1[edit]

Error occurs when one uses the "last ditch" method for preventing baseband updates on the iPhone 4. The baseband does not get updated using this method. Use TinyUmbrella or redsn0w to kick it out of Recovery Mode.

Also occurs in restore logs as "unable to convert ramrod 1004." Seemingly caused by a modem firmware chipset malfunction or faulty dock connector, the only fix is to either heat up the chipset or replace the dock connector.

Errors 0 ... 100[edit]

Error 1[edit]

  • You are attempting to downgrade an iPhone from iOS 5 to iOS 4.x. To resolve, use either custom firmware created by PwnageTool/sn0wbreeze or use notcom's FixRecovery utility available on his site [Archived 2011-08-30 at the Wayback Machine].
  • On an iPhone 4 downgrading from iOS 5, use the option in TinyUmbrella to allow a baseband "upgrade" to bypass the error and go back to basband 4.10.1.
  • Unable to downgrade. Try changing the USB port (if on a tower, use ports on the back) and restart computer.
  • The installed version of iTunes may also be too old. Update iTunes.
  • You are trying to downgrade an iPhone 4 to an earlier version of iOS 5, using redsn0w. To resolve, stitch your blobs to a "No_BB" ipsw of the firmware you are trying to downgrade to.

Error 2[edit]

  • ASR does not exist on ramdisk or is corrupt/not signed.
  • sn0wbreeze 1.6 Custom Firmware has a ASR patch problem. Use sn0wbreeze 1.7+ or PwnageTool. Device isn't bootable.

Error 6[edit]

  • The device did not enter Restore Mode, change USB port if on a tower, use ports on the back) and restart computer.
  • Unable to resize partition due to storage being full at final stage of updating firmware. The error may be bypassed (restart and do exit recovery) but you probably need to re-update it one more time.

Error 9[edit]

  • Due to asr being patched, the SHA signature is automatically changed and after being resigned the kernel will refuse to use it. Therefore proper kernel patches are required. If necessary kernel patches are not applied, it will fail to load asr and error 9 would occur during restore.
  • Connection with the device was lost. Check USB connections and try again.
  • Rebooting your Mac or PC may resolve this issue.
  • Can be a NAND issue as well, which requires a logic board swap.

Error 10[edit]

LLB is missing from the IPSW. The device cannot be booted up. The trick to skip the baseband update no longer works.

Error 11[edit]

  • Removed BBFW file in the firmware folder of an unzipped IPSW. Can also be used to prevent a baseband update. The device is bootable if you set the auto-boot to true or use TinyUmbrella and use "Kick Device out of Recovery".
  • You are trying to update to a custom firmware from PwnageTool 4.1+. You always have to go into DFU mode and restore from there.
  • Occurs when attempting to restore a signed custom firmware on the iPhone 4 using iTunes 11.1 or newer. Downgrade to an earlier iTunes to fix.
  • Installed version of iTunes is too old to recognize your device, update iTunes and try again.

Error 13[edit]

  • Occurs when you want to install an iOS 4.1 beta firmware with iTunes for Windows (actively blocked by Apple; beta users are developers and therefore must have a Mac).
  • USB problem. Check the USB connection and try other direct ports or maybe the USB cable is an older one. Device isn't bootable.
  • The installed version of iTunes may also be too old. For firmwares 4.0 and higher you need iTunes 9.2 or higher. Update iTunes.

Error 14[edit]

  • Custom firmware update fail (PwnageTool until 4.0.1). You have to restore the device with a custom firmware. Update to a custom firmware isn't working. Device isn't bootable. 2
  • USB Problem. Check the USB connection and try other direct ports or maybe the USB cable is an older one. Device isn't bootable.
  • You're trying to 'update' to a beta firmware instead of performing a restore. Device is still bootable if you kick it out of recovery mode.
  • Rebooting your Mac or PC may resolve this issue.
  • Root file-system partition size was set too small in the ramdisk's options plist, or the root filesystem size somehow exceeds the storage capacity of the device ("not enough space in /dev/disk0s1 to restore" according to ASR)
  • Root filesystem dmg is corrupted or ASR has not been correctly patched. Re-download your IPSW or correctly patch ASR (see Making PwnageTool Bundles - ASR).
  • Potential symptom of NAND failure, restoring a few times in succession can sometimes bypass this but beware that it may not be a permanent fix.
  • Storage may be full while updating, try restoring.

Error 17[edit]

  • Device failed to display the applelogo img3 which results in this error.
  • One or more of the nand0/nor0 flash images were missing from the IPSW.

Error 18[edit]

This occurs when the media library on the device is corrupt and cannot be modified or updated.

Updating to the latest version of iTunes and then restoring should resolve this issue

Error 20[edit]

Reportedly happens during failed downgrade attempts (iPhone OS 2.0 to 1.1.1, iOS 5 beta to 4.3.3).

Some have seen success afterwards by doing the downgrade from DFU mode instead of recovery mode.

Error 21[edit]

  • Custom firmware restore fail (PwnageTool since 4.1). You have to put your device into the DFU mode and not into recovery mode. Device won't boot correctly an stuck at the Apple logo after the error. Press and hold power and home button until it reboots.
  • Error when using Saurik's server for a restore with iOS 5.x in the recovery mode, usually with A5 devices.
  • This error can also happen when you try to restore an iPod with hardware dfu. Use iREB r5 to solve this.
  • You are trying to update to a beta firmware without UDID activation.

Error 23[edit]

Cannot restore or update due to hardware problems.

  • In software you have to set default web browser.
  • In hardware, it's a communication problem. Check all connections, also try to change battery.
  • Faulty baseband flash or processor
  • Happens frequently after water damage. Clean or replace the logic board.

Error 26[edit]

  • Values or variables in the options property list within the ramdisk are incorrect.
  • False version of the NOR flash firmware. Use the correct sn0wbreeze version.

Error 27[edit]

  • Trying to flash iOS 5 from an iPhone 3GS on a 3G Phone. Modify the restore.plist so it would flash and also exchanged RestoreRamDisk and kernelcache.
  • Failed attempt of upgrading an iPod touch (5th generation) from an older iOS to iOS 9.0 beta. Can be resolved by restoring to the latest public version and trying the upgrade again.

Error 28[edit]

  • Hardware error, usually a bad dock connector.
  • If you have tried almost everything, reset the logic board (leave uncharged for five days or remove battery for half an hour), then pwn and restore. If this doesn't work, the memory of your device is damaged.
  • Hardware is incompatible with iOS Version. Typically seen with iPhone 4 GSM models trying to be restore to iOS 4.0. Can also be seen when trying to restore any geekgrade iOS 4 IPSW on an 8GB iPhone 4 (iPhone3,1).
  • The device has a non-original display, some don't work when restoring to iOS 5.

Error 29[edit]

See Apple's discussion thread number 2329795 [Archived 2010-08-21 at the Wayback Machine] about this problem. You might need to change the battery.

This error is common on iPhone 4S devices with low quality aftermarket batteries.

Error 31[edit]

Error 34[edit]

There is not enough space on your computer to download the IPSW

Error 35[edit]

Either a USB communication Failure or NAND Failure. If changing USB port and/or cable doesn't work, repair or replace your logic board.

Error 37[edit]

  • iPod touch (2nd generation) LLB patched with the 0x24000 Segment Overflow was used on an iPhone 3GS custom firmware. Known on damaged bundles from unofficial PwnageTool distributions or bundles.
  • sn0wbreeze 2.0.1 bug, which was fixed in 2.0.2.
  • Recent sn0wbreeze can cause this issue. Deselect all custom boot logos, recreate IPSW. If received on an iPhone 3GS, select "new boot-rom" and deselect all custom boot logos, then recreate the IPSW.
  • Attempting restore with an IPSW that was stiched with blobs not for your device (Usually a good thing if restoreing with a geekgrade beta IPSW or with your own creation). To boot, simply open redsn0w. Do fix recovery and tether boot after. Do not lock or device's LCD will fail.

Error 40[edit]

  • Hacktivation bug in sn0wbreeze 2.0.1, which was fixed in sn0wbreeze 2.0.2.
  • NAND chip is most likely dead (confirm with ASR output from restore log).

Error 45[edit]

  • Same with Error 6, in terms of resizing partition issue. But this may occur at the very beginning of restore process.

Error 48[edit]

  • Dead/malfunctioning baseband chip during restore/update, try again and if it doesn't work, repair or replace your logic board

Error 53[edit]

  • Happens on devices with damaged Touch ID, cause is most likely water damage, replaced sensor, or a broken cable. DFU restoring to iOS 9.2.1 (13D20) or later will let the device boot but Touch ID will fail to work. Bring the device to Apple if possible, as Touch ID can only be repaired by Apple.
  • Can be an error with iTunes. In this case, change your DNS to and try again.

Error 56[edit]

  • Most likely a dead/glitched Touch ID sensor. If seen on iPads, try restoring to latest firmware in DFU mode. If error still occurs, bring your device to Apple. On iPhones, take out the SIM card and try restoring in DFU mode. If it still occurs, bring the device to Apple for repair.

Error 68[edit]

  • So far seen when attempting to downgrade iOS 17 or later to another signed version of iOS when using Update mode to preserve data. This is not possible and Erase (Restore) Mode should be used instead.

Error 100[edit]

  • Disconnect all cables except for the battery, screen, and charging port and try updating again.

Errors 10xx[edit]

Error 1002[edit]

Unknown error when restoring.

Error 1004[edit]

This is caused by a failure to match the Baseband Nonce currently in memory to the nonce returned in the Baseband Firmware SHSH blob. This happens if you edited the hosts file (Saurik's Server) or you are using TinyUmbrella. Use TinyUmbrella and "Kick Device Out Of Recovery" to boot. 1

Error 1011[edit]

This is caused by recovery mode being in userland (1.1.1 firmware). The file iTunesMobileDevice.dll is damaged or updated.

Error 1013[edit]

  • iPhone 4
    • This means that the baseband did not get updated. Either remove the entry from your hosts file and let the baseband upgrade or if you want to preserve the baseband just jailbreak at this point to boot it up.
  • Other Devices
    • Restart computer; change computer; reinstall system, if the device is always in restoring mode: XP users can jump from restoring mode with ibus; MAC users can use iNdependence. (usually on the iPhone with 1.0.2 firmware downgraded from 1.1.1)

Error 1014[edit]

This occurs when you try to downgrade your device's baseband.

Error 1015[edit]

This error is common when downgrading iPhones and 3G iPads. The problem occurs when the device's baseband has a higher version number than the baseband in the firmware you restored to. Just set auto-boot true in iRecovery or use iREB/TinyUmbrella/RecBoot.1 In case this is not working use Pwnage Tool to create a custom firmware WITHOUT the iPad baseband, put your device in pwned DFU Mode and restore via iTunes.

Error 1050[edit]

Bad response from OR need iREB for preparing the device for restoring to custom IPSW

Errors 13xx[edit]

Error 1394[edit]

When Spirit2Pwn flashes parts of the boot chain on iOS 4, the device may crash into DFU Mode. See also a topic on iH8sn0w forums.

Errors 14xx[edit]

Error 1413[edit]

Try restarting computer, or change USB port (on a tower, ports on the back are better), or change cable. See also KB TS1927 [Archived 2011-11-15 at the Wayback Machine].

Error 1415[edit]

Try restarting computer, or change USB port (on a tower, ports on the back are better), or change cable.

Error 1417[edit]

Try restarting computer, or change USB port (on a tower, ports on the back are better), or change cable.

Error 1418[edit]

Try restarting computer, or change USB port (on a tower, ports on the back are better), or change cable.

Error 1428[edit]

Try restarting computer, or change USB port (on a tower, ports on the back are better), or change cable.

Error 1432[edit]

Occurs while upgrading an iPod classic's storage. Boot the iPod into Disk Mode and format it in Disk Utility before restoring in iTunes.

Errors 16xx[edit]

Error 1600[edit]

  • Custom firmware can't be restored on a device with DFU Mode as the device is not in a pwned DFU Mode.
  • APTicket problems if you try to restore to iOS 5.x in the DFU Mode.
  • If truly stuck (even with an regular iTunes Restore), edit the hosts file and comment out the "" line so you can get valid blobs from Apple
  • GetDeviceID: failed for iBoot (experienced on Windows 8)

Error 1601[edit]

See KB TA38633.

Error 1602[edit]

  • Restart computer; change computer; reinstall system.
  • If this error occured during an Apple TV restore, then unplug the Apple TV from the power cable, after you entered the recovery or DFU mode, and then try it again.

Error 1603[edit]

Bad kernelcache patch. Known on damaged bundles from unofficial PwnageTool distributions or bundles. See also Apple's KB TA38604 [Archived 2011-10-10 at the Wayback Machine]

Error 1604[edit]

Device was not pwned (signature checks were not blocked). Custom firmware can't be restored. Can also happen when there's a problem with the IPSW.

Error 1611[edit]

iTunes tried to enter the Restore Mode, but the device turned back to the Recovery Mode. This can happen when updating an iPad 2 jailbroken with Saffron gets updated to iOS 5. In this case simply retry, as it is in Recovery Mode then anyway.

Error 1618[edit]

Missing system files or corrupt data in iTunes installation. Uninstall iTunes and Apple Mobile Device Driver, restart computer, and then install iTunes again. This error also occurs for iTunes in Windows 8 for reasons currently unknown.

Error 1619[edit]

iTunes is too old and couldn't read the iPhone in recovery or DFU Mode. Please update iTunes and try it again.

Error 1644[edit]

IPSW was moved during prepare with iTunes. Try it again and don't move the IPSW.

Error 1646[edit]

iTunes expected the device to be in a different state (Example: booted into iOS rather than jumping to iBEC).

Error 1667[edit]

Occurs when device is unplugged while the "iTunes will erase and restore your iPhone to iOS #.# and will verify the restore with Apple." dialog is shown. Check USB connections and try again.

Errors 20xx[edit]

Errors 2000-2009 (from KB TS3694): If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, displays, reset the SMC, and then try to restore. If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore. If that does not resolve the issue, try the USB issue-resolution steps and articles listed for Error 1604. If the issue persists, it may be related to conflicting security software.

Error 2001[edit]

  • The Mac OS X kernel extension "IOUSBFamily" that was bundled with late 2008 / early 2009 MacBooks, as well as the 10.5.6 update, has a bug where it fails to properly recognize an iDevice in DFU Mode. It can be resolved by updating to 10.5.7 (or later), or using a USB hub.
  • Close limera1n.

Error 2002[edit]

iTunes can't connect because another program is using it or it's disconnected during the Apple Server check.

Error 2003[edit]

  • Connection problem; change USB cable and/or USB port (on a tower, ports on the back are better)
  • sn0wbreeze failed to restore IPSW; unplug and plug iDevice and try again

Error 2005[edit]

iTunes couldn't connect to the device. Reinstalling Apple Mobile Device Driver can solve the problem, but it is typically a hardware issue.

Error 2006[edit]

Replace the USB cable with a newer one and/or disconnect all other USB devices, then retry.

Error 2009[edit]

If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, displays, reset the SMC, and then try to restore.

If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore.

If that does not resolve the issue, see Error 1604 above. If the issue persists, it may be related to conflicting security software on your computer.

Errors 30xx[edit]

Error 3002[edit]

  • iTunes hasn't checked with Apple to see what the latest version is and so it is attempting to update to a firmware that is no longer signed.
  • The update server may also be down - try again later.
  • It can also happen if you attempt to perform an Update restore with a local TSS server, or the Cydia server. Click Restore instead.
  • Error 3002 represents no update ramdisk when pressing Shift+Check for updates.

Error 3004[edit]

  • There is no internet connection. Make sure you can connect to on ports 80 and 443.

Error 3011[edit]

  • Your hosts file may be malformed - remove any lines with in it.

Error 3014[edit]

  • Your hosts file may be malformed - iTunes didn't get a response from the TSS server. Make sure you can connect to on ports 80 and 443, or make sure you can connect to TinyUmbrella/the Cydia server/

Errors 31xx[edit]

Error 3194[edit]

  • Occurs when TSS is not signing the version you are restoring to.
  • If not using TinyUmbrella/the Cydia server, use an ipsw that is signed by Apple.
  • If you are using TinyUmbrella/the Cydia server, make sure you have blobs stored there for the ipsw you are attempting to use.
  • Another message that this error can display is "not eligible for requested build".

Error 3195[edit]

  • The blob iTunes downloaded isn't valid for your device and firmware combination.

Errors 32xx[edit]

Error 3200[edit]

You are trying to update using an ipsw that does not have an update ramdisk. Select the Restore button instead.

Errors 40xx[edit]

Error 4005[edit]

  • Miscellaneous peripheral fault. Check Earpiece speaker, charging port, front/rear camera, anything disconnect-able.

Error 4010[edit]

  • Linked to hosts file blocking of Apple services or problems with Firewall/Antivirus.

Error 4013[edit]

  • Generally related to a hardware fault, if not the cable used to connect the device to the PC
  • Commonly general hardware failure. Common culprits are NAND, earpiece speaker, and faulty CPU power. If the device is an iPhone 7/7 Plus, it can also be a result of a dead baseband.
  • Faulty NAND, CPU power, and baseband require a logic board repair or replacement. To verify other components are not the cause, switch the logic board into another housing if you can.
  • Potentially a bad Lightning/30-Pin connector causing disconnects.

Error 4014[edit]

  • Inconclusive error, commonly triggered as a result of tether downgrading an iOS device and being stuck in LLB rather than DFU mode or Recovery Mode.

Error 4047[edit]

  • The device's NAND is likely dead. You may see this instead of 4013

Errors 90xx[edit]

Error 9008[edit]

  • An error occurred while attempting to download the ipsw to restore the device. Try again.

Errors 98xx[edit]

Error 9807[edit]

  • An unknown error occurred. Try again and see if it goes away. If not, try switching computers.

Higher Errors[edit]

Error 20000[edit]

  • This error can be caused by the iDevice rebooting during the "Extracting Firmware" stage of restore.

Error 20008[edit]

This happened on a Mac with TinyUmbrella running before restoring a firmware to the Apple TV.

Error Texts[edit]

This device isn't eligible for the requested build (TATSU declined to authorize this image on this device for this user)[edit]

Apple doesn't sign the firmware anymore. If your device has an S5L8920 or S5L8922 SoC or an A4 to A11 SoC and you have saved your SHSH blobs for the firmware you are restoring to, you are doing something incorrectly. If you don't have SHSH blobs for the firmware you are restoring to, there is nothing you can do. If you are restoring to a device with an A12 or newer SoC, there is no (publicly disclosed) bootrom exploit to restore to older versions of iOS. You should still save your SHSH blobs in case an exploit is discovered. However, Odysseus, OdysseusOTA or OdysseusOTA2 can be used if the user has SHSH blobs, but it only works on some iOS versions and requires the device to be currently jailbroken.

The (Apple TV/iPhone/iPod/iPad) "XXXXXX" could not be restored because the firmware file is not compatible.[edit]

You are using the wrong firmware file (or it's corrupt). Download the correct firmware file that matches your device. The firmware file's filename will contain the internal identifier of the device it's intended for.

To determine which firmware should be downloaded, find your device's model numbers on Models. Look at the "Identifier" column; when downloading firmwares, the URL must contain that string. Alternatively, if you have iTunes 11 or later, you can click the device and click where the serial number is three times to show the "Product Identifier", which will show you what firmware you need. Once you have the identifier, visit Firmware and find the version you want for your device.

The (Apple TV/iPhone/iPod/iPad) "XXXXXX" cannot be restored at this time because the iPhone software update server could not be contacted or is temporarily unavailable.[edit]

If you want to upgrade or downgrade the baseband, make sure you didn't change the hosts file to add the Cydia Server. Cydia cannot handle the requests for the baseband certificates. Maybe you tried to use SAM Activation method.

There was a problem downloading the software for the (Apple TV/iPhone/iPod/iPad) "XXXXXXX" the network connection was reset, make sure your network settings are correct and your network connection is active, or try again later.[edit]

You need to disable both your Anti-Virus and your windows/security firewall in order for the update/restore to go through.

  • 1 Use TinyUmbrella (Kick Device out of Recovery), iRecovery or redsn0w Lite and enter "setenv auto-boot true", "saveenv", "reboot" to boot.
  • 2 Device isn't bootable, but a custom firmware can be restored if it has a jailbreak and the requirements.