The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "ITunes Errors/16xx"
(→Error 1600) |
m (Fix typo) |
||
(8 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
=== Error 1600 === |
=== 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 |
||
− | - APTicket problems if you try to restore to iOS 5.x. |
||
+ | * GetDeviceID: failed for iBoot (experienced on Windows 8) |
||
=== Error 1601 === |
=== Error 1601 === |
||
− | See |
+ | See [http://support.apple.com/kb/TA38633 KB TA38633]. |
=== Error 1602 === |
=== Error 1602 === |
||
* Restart computer; change computer; reinstall system. |
* 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 Mode|recovery]] or [[DFU Mode|DFU]] mode, and then try it again. |
+ | * If this error occured during an [[List of Apple TVs|Apple TV]] restore, then unplug the [[List of Apple TVs|Apple TV]] from the power cable, after you entered the [[Recovery Mode|recovery]] or [[DFU Mode|DFU]] mode, and then try it again. |
=== Error 1603 === |
=== Error 1603 === |
||
− | False [[kernelcache]] patch. Known on damaged bundles from unofficial [[PwnageTool]] distributions or bundles. See also Apple's [http://support.apple.com/kb/ |
+ | False [[kernelcache]] patch. Known on damaged bundles from unofficial [[PwnageTool]] distributions or bundles. See also Apple's [http://support.apple.com/kb/TA38603 KB TA38604] |
=== Error 1604 === |
=== Error 1604 === |
||
Line 19: | Line 20: | ||
=== Error 1611 === |
=== Error 1611 === |
||
[[iTunes]] tried to enter the [[Restore Mode]], but the device turned back to the [[Recovery Mode]]. |
[[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 |
+ | 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 === |
=== Error 1618 === |
||
Missing system files or corrupt data in iTunes installation. Try to uninstall iTunes, restart computer, install again. |
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. |
+ | This error also occurs for iTunes in [[wikipedia:Windows 8|Windows 8]] for reasons currently unknown. |
=== Error 1619 === |
=== Error 1619 === |
||
− | [[iTunes]] is too old and couldn't read the iPhone in Recovery or DFU Mode. Please update iTunes and try it again. |
+ | [[iTunes]] is too old and couldn't read the iPhone in Recovery or DFU Mode. Please update [[iTunes]] and try it again. |
=== Error 1644 === |
=== Error 1644 === |
||
Line 32: | Line 33: | ||
=== Error 1646 === |
=== Error 1646 === |
||
− | iTunes expected the device to be in a different state (Example: booted into iOS rather than jumping to iBEC). |
+ | 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. |
||
+ | |||
+ | [[Category:Errors]] |
Latest revision as of 10:12, 25 October 2018
Contents
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.