Iphone disconnected problem during backup

THIS IS THE REAL DEAL.

This is the issue...at least it was for me. And it makes sense:

* Why do some people get this and others don't despite the same OS?

--> Not everyone has Non-ASCII characters on their Filesystem.

* Why do some devices have this issue and others don't despite being owned by the same person?

--> Not all exact content is on all devices.

* Why is this fixed for some people by "deleting their largest apps" but not for others?

--> Because the larger the app, the more data that app stores, meaning the more likely that data is to hold a character that will corrupt the backup.

To be clear:

Using iMazing - The FREE Version (not a promotion) - I backed up my iPad via the software with the console open and with a search string of "No operation found for path"

The moment the backup broke iMazing's console showed me this exact path and I noticed that an e-book had an author's name with an accented "a" character in the title.

I went into my e-book software, renamed each e-book by that author to remove the accent "a" and replaced it with a normal "a", and re-ran a backup.

My iPad now backs up without a hitch.

Again:

* I did not delete any programs.

* I did not delete any data

* I did not reinstall any applications.

* I did not have to back up with Airplane mode or reset network settings or any other of the many "fixes" for this problem.

* The ONLY thing touched during this entire process was to remove the Accented Character from book titles through renaming.

I will re-link the document that everyone needs to pay attention to here:

https://imazing.com/blog/ios-10-3-3-device-disconnected-error-during-backup-fix

This solved my problem, your mileage may vary. That said, if your device is failing backup at about the same place every time it backs up, and you've tried on multiple computers and with multiple cables, there is a HIGH likelyhood this is a fix...

This is not a hoax, this is no joke, this is the real deal.

Massive Kudos to iMazing and those who tracked down this issue.

Just to add to this. I used the imazing approach suggested by several people here. It did identify the file that was causing the crash. However, as some have pointed out it can be difficult to figure out what app and what file this actually is (as the app name is just a long sequence of letters and digits, and file name is abbreviated). I found out that using iExplorer (Mobile Download · iExplorer) was useful - as this lets you search for files within apps on your iPhone.

Renamed the offending file (turned out to be a gps location I had added to a navigation app), and now backup works again,

Had the same issue as everyone, tried a number of things (new cables, restarting, disconnecting other devices, background app refresh, etc, etc).

iMazing was what worked for me, following these instructions found elsewhere in this thread: https://imazing.com/blog/ios-10-3-3-device-disconnected-error-during-backup-fix.

Found out it was FIRECHAT app causing the issue.

I deleted FireChat from my iPhone, then deleted again using iMazing App mgmt when the phone is plugged in (for some reason it was still showing up w/in iMazing but not on my phone).-->Restarted iphone/itunes/iMazing, ran backup via iTunes and it's now working.

(Other variables that may/may not have contributed: Just prior to my backup working, I renamed my phone on the iTunes side bar when it was plugged in. My carrier settings update from AT&T a while back changed it back to just “iPhone”, so I changed it to what it had been previously, although I doubt this had any affect.)

The "disconnected" message usually means that the phone is not getting enough power from the computer. It needs a minimum of 1/2 amp, and works better with 1 amp. If you have any power-hungry USB devices connected to the computer (like a USB external drive that does not have its own power supply plugged into the wall) try disconnecting it/them.

@ dcook1967 the file that cause the problem was JPG, after i find the error code in iamazing i did not find the current UDID for the application which make it complicated, i have an old backup since a month i use i backupbot and search with the file, found it under the application name so i delete the whole app, it work like a charm, the real problem exactly in the UNI-CODE of the ASCII ... i spent an hour to find it

I was able to back my iPhone up right after I upgraded to iOS 11 and have backed it up since, with no issues at all. I was one of the ones who was never able to back up previously & have posted in a couple of threads about it, so I recommend the upgrade!

Try iExplorer (iPhone Music, Messages & File Transfer for Mac & PC · iExplorer; not Internet Explorer). This will let you browse and search all your user files on the phone. Start by searching for the file extensions of the offending files (you'll see an abbreviated filename in the iMazing log). Since the filename is abbreviated It took me a little while to find exactly which app/file was causing the problem. But when I found it, I simply changed 1 letter in the file name and this fixed the problem.

Today I finally was able to backup my iphone since July, I look for documents with special characters, I found some in NOTES. I also erase some new apps I install after July and it works. I do not know if was the name change on the NOTES documents or the apps clean up, but it work for me, good luck.

I have this problem too, but finally fixed it today, I can backup to iTunes now

The problem has its roots in APFS, Apple's new file system introduced in iOS 10.3.0. To summarize, some special characters have 2 distinct Unicode representations: the Spanish ñ for example has a precomposed variant (Unicode U+241) and a decomposed variant (Unicode U+110:n and U+771:̃).

(Not Promotion)

https://imazing.com/blog/ios-10-3-3-device-disconnected-error-during-backup-fix

Thank you very much, i had found a similar problem with FLAC player app which had special characters on multiple files.

Removing the app fixed the problem for me.

I posted my solution in another post too (check my profile),credits to iMazing team.

I will try to describe the steps:

The is a bug in iOS 10.3.3 that prevents the backup due too special characters in the files.So you have to find that app and uninstall it.

I will try to describe the steps:

-Install iMazing

-Run a back up (with iMazing not iTunes) and check the process bar % and remember the number where the backup will fail

-From iMazing start menu press "show device console",move the windows somewhere near and press PAUSE

-Start a backup again and 5-10 % before the error happens, press RESUME on device console.

-As soon as the backup fails,pause the console and press SAVE,to create a txt file.

-Now it the file search for "No operation found for path"

-You will see a line like "'No operation found for path: /var/mobile/Containers/Data/Application/9944C65F-F8E5-4CA5-951B-7B6AF0A40D1D/Documents/File-Name-With-Special-Characters'

-The first bold string is the Unique ID of the rogue APP and the second it the rogue file name.

-Try to identify the file from the type or name by googling and delete it.

I am also one of the "unlucky" ones with backup to iTunes impossible after (and only after, never had this problem before) IOS 10.3.3 installation on iPhone 6S (disconnection message during backup/syncing through iTunes on Windows 10). Application of several suggestions found on internet fora, such as

> iPhone airplane mode,

> iPhone network settings reset,

> deletion of backups from iTunes preferences,

> manual deletion of backup folders from %appdata%,

> change of USB port,

> change of cables (all original ones),

> iPhone reboot with cable connected,

> iPhone hard shutdown/reboot,

to no avail... I concur that this is a problem Apple should consider immediately!!

I should add, I did the iMazing suggestion & found files with non-ascii characters but was unable to identify the app or file in order to remove it or change the name. I did NOT contact iMazing but they possibly could have helped.

Hi all,

I found the cause and workaround solution for this case. If you received this error, the reason that you have some apps that size is too large (may be more than 3 GB size or something). At normal, such app should be file explorer or container or media player or some thing. Then, itune will show that iphone disconnected problem during backup. For my case that is related that my media player have around 50GB media files inside.

It cause this problem.

You have several workaround ways to resolve this issue.

Case 1. Don't use such app. remove it.

Case 2. Use such app and store the data into clouds and reduce local storage

Case 3. Some apps contain function not to perform backup through iTune. Enable such feature

Hope this work around can help you. In addition, this should be the bug in Apple iOS and iTune. Hope Apple will resolve this issue asap.

So you are practically saying the problem (probably) is the media files (audios, videos, books, mags) or large games stored within the device and you suggest removing them in order to keep backups on IOS 10.3.3... so why we even bother buying 64 or more GB iphones if we should keep it practically empty just to be able to backup? If this is not the very definition of a bug, I do not know what is...

Anyway, benso888 you are very much appreciated for this research/effort, but before we empty our iphones, can anybody else confirm this workaround/solution, or at least find the limit that constitutes this "too large" of an app/file? Is it per app (player) or per file/medium?