View Single Post
Old 05-20-2015, 22:43   #2 (permalink)
Junior Member
Join Date: Apr 2015
Posts: 2
Member: 2383261
Status: Offline
Thanks Meter: 0
Before You Start

As always:

Use the latest version of iTunes
Make sure iPhone has enough space to bring in a new update. A gig or more is recommended.
Also make sure the iPhone is not low on battery.

The Real Problem
Error 4014 (or 4013) is usually associated with a hardware problem Ė a faulty cable, a faulty port etc. On the surface, your iPhone connects to the computer, iTunes recognizes the device but somewhere down the line, iTunes thinks that the cable is not really that good. Or may be the port isnít.

The first thing you try should be change the USB port to which you connect the iPhone. Next up, change the cable that you use. Arguably, this has worked not for everyone but for a few people.

As an extreme measure, you can also try updating from some other computer which has the latest iTunes installed.

Backing Up and Going Into Recovery Mode

If you are trying to update the firmware without doing a clean restore but running into this error (even after changing the cables), itís time to cut the chase. This method is usually recommended as the last-thing-to-try but I think itís easier to get this done with right away.

Connect your iPhone to the computer. Fire up iTunes.
Backup your iPhone.
Now disconnect the iPhone, quit iTunes.
Put the iPhone in recovery mode. The short version goes like this: press and hold power and home buttons till the screen goes blank.
Open iTunes on PC.
Connect the iPhone. iTunes should indicate (through a dialog box) that an iPhone is detected in recovery mode.
Now go ahead and restore the device as new. This will erase everything but you will have the backup to restore from.
Some Notes

Occasionally, the error seems to vanish when people update to the last iOS 6.x version and then update to iOS 7. (This applies when you are on iOS 6.0, 6.1).
Clear out apps and app memory to free up space on your iPhone. Although this sounds very unrelated to this error, it has helped.
  Reply With Quote
Page generated in 0.20036 seconds with 6 queries