Apple has just rolled out the first beta of iOS 10 to registered developers, which comes with major new features and significant improvements. Users have been reporting that they are facing error 14 message in iTunes when attempting to update to iOS 10 beta 1:
The iPhone “iPhone” could not be restored. An unknown error occured (14).
The problem happens when users update to the latest operating system while restoring from backup at the same time. This was possible up until iOS 9 but with iOS 10, it seems that you cannot do both at the same time.
To fix the iTunes error 14 issue on your iPhone, iPad or iPod Touch, here are some solutions which you can try.
How to Fix iTunes Error 14
- First perform a backup of your device and then do a clean restore to the latest public release of iOS, which as of this writing is iOS 9.3.2. Once you’ve restored to iOS 9.3.2, don’t restore from your backup yet. Do a clean restore to iOS 10 using the IPSW file you downloaded from Apple Developer Center. After updating to iOS 10, you can then proceed to do a restore of your backup.
- As spotted on Apple Support page, you must first install the latest version of Xcode 8 on your Mac before installing the iOS 10 beta software on your device using the Restore image. Some users reported that performing a clean restore via Xcode 8 using the Option key works.
- Check your USB cable and make sure that it is working properly. It’s best to try a different cable and see if the problem gets fixed.
- An alternative method is to install the beta directly from your iPhone, iPad or iPod using a Configuration Profile as outlined in Apple Support page.
- As a last resort, you can put your device into DFU mode and restore it to iOS 10 using the IPSW file downloaded.
- If the issues still persist, you can try third-party softwares that aim to fix your device such as Dr.Fone iOS System Recovery tool.
These are some of the solutions that can hopefully fix the iTunes error 14 issue that you are facing when updating to iOS 10 beta 1 on iPhone, iPad or iPod Touch. If you’ve used any other solution to fix the issue then make sure to let us know in the comments section below.