Iphone disconnected problem during backup

I confirm that the backup disconnection problem apparently was (in my case, at least) the non-ASCII (Greek in my case) filenames of files in some of the apps in my iPhone, such as SmartOffice, MotionX-GPS and others, that were previously allowing non-ASCII filenames (while having English menus in iPhone IOS) and after 10.3.3 this ability was broken (APFS normalization sensitive/insensitive problem).

Renaming to ASCII/removing through the iTunes Apps file contents list (going through any potential app which allowed file management in iTunes) resolved my problem and I obtained a full backup successfully. I did not try to reproduce the problem afterwards (save a Greek filename within app or in iTune file manager and test for sequential backup), can anyone try it?

I'm having the same iPhone disconnected issue after starting backup in iTunes. No issue when my iPhone was on 10.3.2. Since updating to 10.3.3 it started.

Running macOS Sierra 10.12.6 on MBPro mid 2015.

iOS is 10.3.3 on iPhone 7 plus - 128gb

iTunes is 12.6.2.20

Oddly I am still able to add music to the phone when syncing but cannot add apps or backup.

I will note however that I have no disconnect issue when backing up my iPhone 6 plus - 64gb or iPad which are running iOS 10.3.3. Its only affecting the 7 plus.

I have tried the suggestions noted in this string but have had no success in getting rid of the issue. I hope we see a resolution from Apple.

I finally was able to back up my iPhone 7 since August 4, 2017! I had to figure it out for myself.

In iTunes, Instead of trying to backup from where you usually do go along the left side of ITunes and right click under devices the device you want to backup.

First sync in the right click menu. Then backup under the same right click menu. Finally it backed up!

I spent hours on the phone with Apple yesterday with two different men and after reinstalling ITunes numerous times he said it had to be my computer or cord. Sheesh! The problem appears to be an ITunes software problem. This worked for me and I hope it does for you!

Another thing I noticed which allowed me to do the above procedure was even though I was ejecting my iPhone it wasn't ejecting so that was why I was able to see it under devices and do the above procedure.

Sadly this did not work for me. I still cannot do the backup as it always shows the disconnected message. I've tried the imazing product suggested earlier by another user and that failed on me in the same way it did in itunes. I suppose we have to wait to see what Apple will do. Cheers

This is the English language self-help bulletin board. Think of what the posts sound like in the Spanish, Portuguese, French and German languages. And that's just Western Europe. The majority of the world uses lots of non-ASCII characters in their docs. A major faux pas.

After doing my workaround way to backup I tried to backup up the old way again and now that works too. My phone backs up fine now. I really don't know how it fixed itself but after three weeks of not working now it is working.

Hi!

I have seen this at iMazing. Looks like the way to go, but I have one doubt yet. Any clue or suggestions in order to identify the App using the App UID? I have lots of apps installed and can't determine where the file is.

Thank you in advance!

I hadn't done a sync on my iPad Air 2 for a few weeks. I got the famous 'disconnect' message but knew where to look to find the offending files. Since I put different FLAC files in different devices, it's not a cookie cutter solution. I went to iTunes under my device info, then scrolled down the right pane to get to 'File Sharing', then my Onkyo HF Player app. Next I looked through the original FLAC files on my PC to find those transferred with non-ASCII characters.

Found them ...

Orchestre Du Conservatoire - Ravel - Complete Orchestral Works - 01 - Ravel - Boléro.flac

Orchestre Du Conservatoire - Ravel - Complete Orchestral Works - 02 - Ravel - Rapsodie Espagnole - Prélude À La Nuit.flac

Orchestre Du Conservatoire - Ravel - Complete Orchestral Works - 03 - Ravel - Rapsodie Espagnole - Malagueña.flac

Orchestre Du Conservatoire - Ravel - Complete Orchestral Works - 06 - Ravel - La Valse - Poème Choréographique.flac

Tracks 04 and 05 worked, but I pulled out the entire album.

Offending characters éè À ñ in these four files make the entire backup crash.

Please note you don't need to remove any music or videos that you sync the usual way...

MP3s, AACs, M4As, M4Vs, MP4s, etc with non-ASCII characters in their titles will probably cause no issues.

Voila.

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

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,

@ 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

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.

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!

Did you have an old backup? I don't have any and wonder how that will work with the upgrade. Another solution told me to try deleting my old backups, so I am concerned with losing information in the upgrade.