ITunes Errors

Most of the errors can be found at Apple's Knowledge Base. Here is a list of iTunes errors that could appear during a restore or a USB connection via iTunes:

Negative -98xx

Error -9843

This error happens if you are logged out, try to download something from the iTunes Store and if you click on "Download" and enter an account, which doesn't have this article, this error will occur.

Error -9815

Set exact date, restart computer. See also KB TS1276.

Error -9814

Set exact date, restart computer. See also KB TS1276.

Error -9812

Check system time, reset Internet connection, update root certificates. See also KB 3222.

Error -9808

Computer system time incorrect.

Error -9800

Set exact date, restart computer. See also KB TS1276.

Negative -50xx

Error -5000

There is a problem with the permissions of the Mobile Application folder. The App you've tried to download in iTunes couldn't be saved.

Negative -32xx

Error -3253

• The network connection was reset.

Error -3259

• Connection timeout, try again.

Error -3221

• Permission levels for iTunes not set correctly in McAfee Personal Firewall Plus; see HT203182 for more information

Negative -1 ... -100

Error -54

Permission error either on your computer or the device.

Error -50

Reinstall iTunes.

Error -35

Error when downloading songs purchased on iTunes. Also see KB TS1475.

Error -1

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.

Below 100

Error 1

• 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.
• 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 (the back one of chassis is better) 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

• 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

• Not enter the downgrading mode, change USB port (the back one of chassis is better) and restart computer.
• Unable to resize partition due to full storage problem 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

• 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.
• Rebooting your Mac or PC may resolve this issue.

Error 10

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

Error 11

• 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

• 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

• 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. ²
• 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 file-system dmg is corrupted or ASR has not been correctly patched. Re-download your IPSW or correctly patch ASR (see PwnageTool Bundles - ASR).

Error 17

• 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

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

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 the normal Recovery mode.

Error 21

• 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 Sauriks server for a restore with iOS 5.x in the recovery mode at least on a A5 device.
• 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

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. Remove and clean motherboard.

Error 26

• 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

• 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

• Hardware error. Return your device to Apple if possible. The problem is a bad dock connector on the iPhone. Must change the 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).
• Device has counterfeit display that is incompatible with a certain iOS versions (Typically iOS 5.X)

Error 29

See Apple's discussion thread number 2329795 about this problem. You might need to change the battery.

Error 31

Main article: DFU Loop

Error 34

Hard disk is run out of space when trying to download. Clear space and then continue downloading.

Error 37

• 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

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

Error 45

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

Error 48

• Dead/Malfunctioning baseband chip during restore/update, try again and if it doesn't work, a hardware fix will be necessary.

Error 53

• Happens on devices with damaged Touch ID, cause is most likely water damage. 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.
• Can be an error with iTunes. In this case, change your DNS to 8.8.8.8 and try again.

Error 56

• Most likely a dead/glitched Touch ID sensor. If seen on iPad's, try restoring the 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 still occurring, bring your device to apple.

Errors 10xx

Error 1002

Error when restoring.

Error 1004

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. ¹

Error 1011

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

Error 1013

• iPhone 4
  • This means that the baseband did not get updated. Either remove the gs.apple.com 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

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

Error 1015

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.¹ 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

Bad response from gs.apple.com OR need iREB for preparing the device for restoring to custom IPSW

Errors 13xx

Error 1394

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

Error 1413

Restart computer; change USB port; reinstall system. See also KB TS1927.

Error 1415

Restart computer; change USB port; reinstall system.

Error 1417

Restart computer; change USB port; reinstall system.

Error 1418

Restart computer; change USB port; reinstall system.

Error 1428

Restart computer; change USB port; reinstall system. (downgrade from www.iphonebus.com)

Errors 16xx

Error 1600

• Custom firmware can't be restored on a device with DFU Mode. The software of the device isn't patched. Using a jailbreak tool, enter a pwned DFU Mode. During that process the software gets patched and the custom firmware should run without any problems.
• 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 "guzzoni.apple.com" line
• GetDeviceID: failed for iBoot (experienced on Windows 8)

Error 1601

See KB TA38633.

Error 1602

• 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

False kernelcache patch. Known on damaged bundles from unofficial PwnageTool distributions or bundles. See also Apple's KB TA38604

Error 1604

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

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

Missing system files or corrupt data in iTunes installation. Try to uninstall iTunes, restart computer, install again. This error also occurs for iTunes in Windows 8 for reasons currently unknown.

Error 1619

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

Error 1644

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

Error 1646

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

Error 1667

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

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

• 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

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

Error 2003

• Connection problem; change USB cable and check USB port.
• sn0wbreeze failed to restore IPSW; unplug and plug iDevice and try again

Error 2005

Problem connecting. Probably a hardware failure.

Supposedly reinstalling the USB drivers fixed the problem.

Error 2006

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

Error 2009

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

Error 3002

• Update to an older firmware isn't working, because Apple is no longer handing out SHSHs for the device/firmware combination.
• Or a timeout checking Apple server - retry later.
• This error also happens if you try to Update with a local TSS server (TinyUmbrella tool) and probably also when connecting to Cydia Server. Use Restore instead.
• Error 3002 represents no update ramdisk when pressing Shift+Check for updates.

Error 3004

• No internet connection during the firmware restore.
• iTunes can't connect to gs.apple.com. Maybe Port 80 and Port 443 is blocked. Open it on your router.

Error 3014

• Bad hosts file. The SHSH request couldn't be completed. No connection to the Apple Server, Cydia Server or localhost (for TinyUmbrella).
• iTunes can't connect to gs.apple.com. Maybe Port 80 and Port 443 is blocked. Open it on your router.

Error 3011

• Bad hosts file. The SHSH request couldn't be completed. No connection to the Apple Server, Open your host file and remove any lines with gs.apple.com."

Errors 31xx

Error 3123

Something dealing with movie rentals.

Error 3191

QuickTime may be corrupted. You must reinstall it before iTunes will work. Windows users, also try turning off Compatibility Mode for QuickTime

1. Right-click on C:\Program Files\QuickTime\QuickTimePlayer.exe (Program Files (x86) for 64-bit Windows) and choose Properties from the shortcut menu
2. In the Properties window, click on the Compatibility tab. Deselect the checkbox labeled "Run this program in compatibility mode for"
3. Select "Windows XP"
4. Click Apply
5. Close the Properties window

Error 3194

Occurs when trying to install an old firmware and Apple's server disallows the installation. The only solution is to have the SHSH blob backed up and modify the hosts file to point to Saurik's Cydia Server where they are backed up (or localhost if you have it yourself). Also happens if restoring to the latest iOS and the hosts point to Cydia. Remove gs.apple.com lines in hosts file. Another message that this error can display is "not eligible for requested build".

Error 3195

• There is no SHSH blob for the firmware.
• This is the same as "This device isn't eligible for the request build." but with an cache error.

Errors 32xx

Error 3200

You are trying to update to a firmware, when infact, there is only a Restore Ramdisk.

Errors 40xx

Error 4013

• Connection to device is lost after the "Preparing iPhone for Restore" step but before the phone is actually wiped causing it to boot normally. Check USB connections and try again.

Errors 90xx

Error 9008

• Error downloading, try again.

Higher Errors

Error 11222

A security software you have installed may be conflicting with iTunes.

Error 11556

You're trying to access a section or a functionality that is not available in your country, for example iCloud in some countries.

Error 13019

• Seems to be an issue with syncing media to the device... It only seems to happen on jailbroken devices. Create new user, try syncing with new user's library. If that fails, restore. If it doesn't fail, then something on YOUR iTunes Library is causing the error.
• In iPhone OS 3.0-3.1.0 this was a known bug related to the sync process accessing iTunes-renamed Voice Memos.

Error 20000

• Is caused by a custom theme pack on your Windows. Use default Theme.
• This error can also be caused by the iDevice rebooting during the "Extracting Firmware" stage of restore.

Error 20008

?

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

Hex Codes

0x80090318

Something dealing with programs monitoring Winsock; see TS4123 for more information

0xE800000F

Unknown error

0xE8000001

Device was suddenly unplugged. iTunes couldn't connect with the device. Try it again

0xE8000022

Error in your firmware files. Restore.

0xE800003D

False permissions in the Carrier Bundle folder. Restore, update or fix the permissions from the carrier bundle to update the carrier settings via iTunes.

0xE800006B

Device was suddenly unplugged. iTunes couldn't connect with the device. Try it again.

0xE8000065

sn0wbreeze custom firmware error on USB connection. Unplug the device, reboot it, and plug it in again.

0xE8008001

Main article: MobileInstallation

IPA signature verification failed.

0xE800001F

Unknown error

0xE8800084

Unknown error

Error Texts

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

Main article: SHSH

See also: TinyUmbrella

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.

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.

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.

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

---

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