What's new
By:
PinoyTechnician

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

DOWNLOAD IOS Devices Restore Error Code and Causes

G

gerrero

Registered
Joined
Aug 7, 2014
Messages
224
Reaction score
11
Points
1
error codes n puede natin ma-encounter pag nagrerestore tayo ios devices at ang posibleng mga dahilan ng error. Sana makatulong..
iTunes Restore Error Codes

Errors -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 alsoKB TS1276.

Error -9814
Set exact date, restart computer. See alsoKB 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 alsoKB TS1276.

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

Errors -32xx
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
Errors -31xx
Error -3198

Errors -100 ... -1
Error -54
Permission error either on your computer or the device.

Error -50
Reinstall iTunes. See also KB TS1583.

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. UseTinyUmbrella or redsn0w to kick it out ofRecovery Mode.

Errors 0 ... 100
Error 1

  • You are attempting to downgrade an iPhone from iOS 5 to iOS 4.x. To resolve, use either custom firmware created byPwnageTool/sn0wbreeze or usenotcom's FixRecovery utility available onhis 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 4to 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 aASR 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.

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.
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. 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.
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 (iOS 2.0 to 1.1.1, 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 5G 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 number2329795 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 2G LLB patched with the0x24000 Segment Overflow was used on an iPhone 3GS custom firmware. Known on damaged bundles from unofficialPwnageTool 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, recreateIPSW. If received on an iPhone 3GS, select "new boot-rom" and deselect all custom boot logos, then recreate theIPSW.
  • 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 53

  • Happens on devices with damaged Touch ID, cause is most likely water damage. 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 theBaseband Noncecurrently in memory to thenoncereturned in theBaseband FirmwareSHSHblob. This happens if you edited thehosts file(Saurik's Server) or you are usingTinyUmbrella. UseTinyUmbrellaand "Kick Device Out Of Recovery" to boot.1

Error 1011
This is caused by recovery mode being in userland (1.1.1 firmware). The fileiTunesMobileDevice.dllis 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 theiPhonewith 1.0.2 firmware downgraded from 1.1.1)
Error 1014
This occurs when you try to downgrade your device'sbaseband.

Error 1015
This error is common when downgradingiPhonesand 3GiPads. The problem occurs when the device'sbasebandhas a higher version number than the baseband in the firmware you restored to. Just set auto-boot true iniRecoveryor useiREB/TinyUmbrella/RecBoot.1In case this is not working use Pwnage Tool to create a custom firmware WITHOUT the iPad baseband, put your device in pwnedDFU Modeand restore viaiTunes.

Error 1050
Bad response from gs.apple.com OR neediREBfor preparing the device for restoring to customIPSW

Errors 13xx
Error 1394
WhenSpirit2Pwnflashes parts of the boot chain oniOS4, the device may crash intoDFU Mode. See alsoa topic on iH8sn0w forums.

Errors 14xx
Error 1413
Restart computer; change USB port; reinstall system. See alsoKB 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 withDFU Mode. The software of the device isn't patched. Using a jailbreak tool, enter a pwnedDFU Mode. During that process the software gets patched and the custom firmware should run without any problems.
  • APTicketproblems if you try to restore to iOS 5.x in theDFU Mode.
  • If trully 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
SeeKB TA38633.

Error 1602

  • Restart computer; change computer; reinstall system.
  • If this error occured during anApple TVrestore, then unplug theApple TVfrom the power cable, after you entered therecoveryorDFUmode, and then try it again.
Error 1603
Falsekernelcachepatch. Known on damaged bundles from unofficialPwnageTooldistributions or bundles. See also Apple'sKB 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 theIPSW.

Error 1611
iTunestried to enter theRestore Mode, but the device turned back to theRecovery Mode. This can happen when updating aniPad 2jailbroken withSaffrongets updated toiOS5. In this case simply retry, as it is inRecovery Modethen 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 inWindows 8for reasons currently unknown.

Error 1619
iTunesis too old and couldn't read the iPhone in Recovery or DFU Mode. Please updateiTunesand try it again.

Error 1644
IPSWwas moved during prepare withiTunes. Try it again and don't move the IPSW.

Error 1646
iTunes expected the device to be in a different state (Example: booted intoiOSrather than jumping toiBEC).

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 (fromKB 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 forError 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 inDFU Mode. It can be resolved by updating to 10.5.7 (or later), or using a USB hub.
  • Closelimera1n.
Error 2002
iTunescan'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.
  • sn0wbreezefailed to restoreIPSW; 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, seeError 1604above. 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 outSHSHsfor the device/firmware combination.
  • Or a timeout checking Apple server - retry later.
  • This error also happens if you try toUpdatewith a local TSS server (TinyUmbrella tool) and probably also when connecting toCydia Server. UseRestoreinstead.
  • Error 3002 represents no update ramdisk when pressing Shift+Check for updates.
Error 3004

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

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 beforeiTuneswill work. Windows users, also try turning off Compatibility Mode for QuickTime


  1. Right-click onC:\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 theSHSH blobbacked up and modify the hosts file to point toSaurik'sCydia Serverwhere 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

Errors 32xx
Error 3200
You are trying toupdateto a firmware, when infact, there is only aRestore 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.
Errors 98xx
Error 9807
Unknown error; 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 onjailbrokendevices. Create new user, try syncing with new user's library. If that fails, restore. If it doesn't fail, then something on YOURiTunesLibrary is causing the error.
  • IniOS3.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.
 
You must log in or register to reply here.
Back
Top