Bruce Johnson5

Q: iTunes could not backup iPhone because the iPhone disconnected

I've tried seaching for an answer for this problem and can't find one that works. I've tried the basics and even restored my iPhone 4S (and restarted it). Yet, I still keep getting the above message every time I try to back up even though my iPhone is hardwired to my laptop. Any other ideas out there to solve this one?

 

Thanks!

iPhone 4S

Posted on Jan 28, 2012 4:51 PM

Close

Q: iTunes could not backup iPhone because the iPhone disconnected

  • All replies
  • Helpful answers

first Previous Page 17 of 23 last Next
  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 3:35 PM in response to petermac87
    Level 2 (355 points)
    iPad
    Sep 14, 2015 3:35 PM in response to petermac87

    "It is not a system wide bug, otherwise everyone would be seeing it. Very few are."

     

    It depends on how you define "system-wide bug". I have a feeling it involves some kind of setting corruption, and the backup software is not robust. So something hangs and times out, so it thinks there is a "disconnection". I have seen many times where corrupted settings caused problems. The software is not very tolerant.

     

    I suspect if I completely erase my phone and start from scratch (without restoring from backup, which would restore the corruption) the problem would disappear. But I'm not willing to go thru that headache, and I shouldn't have to.

  • by petermac87,

    petermac87 petermac87 Sep 14, 2015 3:41 PM in response to Frank Malloy
    Level 5 (7,402 points)
    Sep 14, 2015 3:41 PM in response to Frank Malloy

    I see iPhones every day but as yet have not seen this issue. Not to say that it doesn't occur. It is just not very common. Don't let those flogging off useless software try to make you believe it is.

     

    Cheers

     

    Pete

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 3:42 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 3:42 PM in response to Kelly Wilkerson

    Interesting. I never heard of the lockdown folder. Will try that. I'm also going to try another Reset and removal of the backup.

     

    Note that sync works fine. With the backup, I start the backup, then after a few minutes it disconnects. It says there's a disconnection in the Console log as well.

     

    I have a theory that something is corrupted, and if that gets saved in the backup, the next backup fails because it can't tolerate the corrupted data in the previous backup. I guess a backup somehow goes into the previous backup...

     

    My phone seems to be working ok. I'm not willing to wipe it clean and start all over, which I suspect will clear the problem. I highly doubt it's hardware.

  • by Kelly Wilkerson,

    Kelly Wilkerson Kelly Wilkerson Sep 14, 2015 3:49 PM in response to Frank Malloy
    Level 1 (63 points)
    Mac OS X
    Sep 14, 2015 3:49 PM in response to Frank Malloy

    Frank Malloy wrote:

     

    Interesting. I never heard of the lockdown folder. Will try that. I'm also going to try another Reset and removal of the backup.

     

    Note that sync works fine. With the backup, I start the backup, then after a few minutes it disconnects. It says there's a disconnection in the Console log as well.

     

    I have a theory that something is corrupted, and if that gets saved in the backup, the next backup fails because it can't tolerate the corrupted data in the previous backup. I guess a backup somehow goes into the previous backup...

     

    My phone seems to be working ok. I'm not willing to wipe it clean and start all over, which I suspect will clear the problem. I highly doubt it's hardware.

     

    I agree that yours doesn't sound like hardware either, since you can fairly reliably make the new backup.

     

    You are correct about the backup relationship -- the next backup is "incremental" and updates the previous backup with changes. In the usual case, this is great because it speeds up the backup time immensely

     

    Another thing that you might try before a lockdown reset is to try your backup with the iPhone in airplane mode. Although that may be something to try later at night so you don't miss messages if your backup is taking a long time to make.

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 3:56 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 3:56 PM in response to Kelly Wilkerson

    the next backup is "incremental" and updates the previous backup with changes.


    Aha. I suspect the software examines the previous backup looking for changes to determine the incremental backup needed, doesn't like something it sees, and hangs the backup routine, resulting in a timeout, thinking you've disconnected the phone.


    Will try your suggestions.

  • by Kelly Wilkerson,

    Kelly Wilkerson Kelly Wilkerson Sep 14, 2015 4:00 PM in response to Frank Malloy
    Level 1 (63 points)
    Mac OS X
    Sep 14, 2015 4:00 PM in response to Frank Malloy

    Frank Malloy wrote:

     

    the next backup is "incremental" and updates the previous backup with changes.


    Aha. I suspect the software examines the previous backup looking for changes to determine the incremental backup needed, doesn't like something it sees, and hangs the backup routine, resulting in a timeout, thinking you've disconnected the phone.


    Will try your suggestions.

    Yep, what you are describing is the most frequent cause that I see for backup problems.

     

    It's certainly interesting if you can reset network settings instead of deleting/archiving the previous backup, because that is a different presentation of the problem maybe. It's also interesting if you have to purge the backup every time, because normally one purge is enough to get people on the right track.

     

    Anyhow, would love to hear how your progress goes as you try again in the future!

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 4:08 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 4:08 PM in response to Kelly Wilkerson

    Will do some tests tonight and report back.

     

    In any case, their backup routines need to be more robust and do more error checking. A backup shouldn't hang like that no matter what.

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 5:10 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 5:10 PM in response to Kelly Wilkerson

    Ok, here's the results:

     

    Airplane Mode - didn't work.

     

    Reset the lockdown folder - didn't work.

     

    It starts the backup, then fails a minute or two later.

     

    Console log shows:

     

    9/14/15 5:02:52.278 PM AppleMobileBackup[6751]: WARNING: Backing up 1d4e77318a7a4e6910a8f46bf11aea6d736985409/14/15 5:02:58.969 PM iTunes[6155]: Entered:_AMMuxedDeviceDisconnected, mux-device:275

    9/14/15 5:02:58.969 PM iTunes[6155]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:275

    9/14/15 5:02:58.969 PM iTunes[6155]: tid:1d2b - Mux ID not found in mapping dictionary

    9/14/15 5:02:58.969 PM iTunes[6155]: tid:1d2b - Can't handle disconnect with invalid ecid

    9/14/15 5:02:58.970 PM AppleMobileBackup[6751]: AMDeviceConnect (thread 0x7fff7c78a300): Could not connect to lockdown port (62078) on device 275 - 1d4e77318a7a4e6910a8f46bf11aea6d73698540: 0xe8000084.

    9/14/15 5:02:58.970 PM iTunes[5647]: Entered:_AMMuxedDeviceDisconnected, mux-device:275

    9/14/15 5:02:58.970 PM iTunes[5647]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:275

    9/14/15 5:02:58.970 PM iTunes[5647]: tid:1683f - Mux ID not found in mapping dictionary

    9/14/15 5:02:58.971 PM iTunes[5647]: tid:1683f - Can't handle disconnect with invalid ecid

    9/14/15 5:02:59.236 PM AppleMobileBackup[6751]: 6751:2088280832|DeviceLinkListener.c:_copyMobileDeviceValue| ERROR: Could not connect to attached device: This device is no longer connected. (132)

    9/14/15 5:03:16.741 PM AppleMobileBackup[6751]: 6751:43008000|SocketStreamHandler.c:_SocketLogCallback| ERROR: SocketRecv (data): return of 0 bytes

    9/14/15 5:03:16.742 PM AppleMobileBackup[6751]: 6751:43008000|StreamHandler.c:_ReadFunc| ERROR: Error reading data: Can't read data

    9/14/15 5:03:16.743 PM AppleMobileBackup[6751]: 6751:43008000|DeviceLinkConnection.c:_DLHandlerThreadReadMessage| ERROR: Could not receive message: '(null)'

    9/14/15 5:03:16.744 PM AppleMobileBackup[6751]: 6751:2088280832|DeviceLinkConnection.c:_DLMainThreadMessagePortCallback| ERROR: Error creating components from read data: 'NULL data returned from read'

    9/14/15 5:03:16.744 PM AppleMobileBackup[6751]: ERROR: Connection to device lost (MBErrorDomain/200)

    9/14/15 5:03:16.744 PM AppleMobileBackup[6751]: ERROR: Backup error: -10

    9/14/15 5:03:16.747 PM AppleMobileBackup[6751]: 6751:43008000|SocketStreamHandler.c:_SocketLogCallback| ERROR: SocketSend (data): error 32: Broken pipe

    9/14/15 5:03:16.749 PM AppleMobileBackup[6751]: 6751:43008000|StreamHandler.c:_WriteFunc| ERROR: Error sending data: Can't send data

    9/14/15 5:03:16.752 PM AppleMobileBackup[6751]: 6751:43008000|DeviceLinkConnection.c:_DLHandlerThreadMessagePortCallback| ERROR: Could not send disconnect message: 'Error writing length of data'

  • by Kelly Wilkerson,

    Kelly Wilkerson Kelly Wilkerson Sep 14, 2015 5:23 PM in response to Frank Malloy
    Level 1 (63 points)
    Mac OS X
    Sep 14, 2015 5:23 PM in response to Frank Malloy

    I'm walking away from my desk for the evening in a moment, but in the morning I will reproduce a crashing backup and see if it looks like a disconnection like your log files, or if this is a real usb disconnection. They usually look really similar on the computer end of things (Windows or Mac) plus or minus a few log messages.

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 5:33 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 5:33 PM in response to Kelly Wilkerson

    Thank you for all your help!

     

    I deleted the existing backup and as expected, the full backup is running (it's more than 50% completed). After that I will try a second backup which I suspect will fail, following the pattern.

     

    I will also try another cable, but the pattern points to having an existing backup.

  • by fidnado,

    fidnado fidnado Sep 14, 2015 6:13 PM in response to Frank Malloy
    Level 1 (0 points)
    Sep 14, 2015 6:13 PM in response to Frank Malloy

    Frank, I tried deleting all backups and forcing it to build a new one from scratch twice. Each time it gave me the error at the end of the backup process saying iPhone disconnected again. If yours does the same I'm certain we are having an identical problem. I'm using latest Yosemite and iOS with a Mac Pro 2009 and iPhone 6+. What are you on?

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 6:19 PM in response to Kelly Wilkerson
    Level 2 (355 points)
    iPad
    Sep 14, 2015 6:19 PM in response to Kelly Wilkerson

    Ok, this is interesting. I remove the backup from the Preferences > Devices and start a new backup. All goes well up to about 3/4 of the way thru, almost an hour or backing up, then it fails:

     

    9/14/15 5:07:34.252 PM AppleMobileBackup[6762]: WARNING: Backing up 1d4e77318a7a4e6910a8f46bf11aea6d73698540

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:2088280832|SocketStreamHandler.c:_SocketLogCallback| ERROR: SocketRecv (data): return of 0 bytes

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:2088280832|StreamHandler.c:_ReadFunc| ERROR: Error reading data: Can't read data

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:2088280832|DeviceLinkConnection.c:_DLHandlerThreadReadMessage| ERROR: Could not receive message: '(null)'

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:45129728|SocketStreamHandler.c:_SocketLogCallback| ERROR: SocketSend (data): error 32: Broken pipe

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:45129728|StreamHandler.c:_WriteFunc| ERROR: Error sending data: Can't send data

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: 6762:45129728|DeviceLinkConnection.c:_DLSendBytesAndDisconnectOnError| ERROR: Could not send data: 'Error writing length of data'

    9/14/15 6:04:19.865 PM AppleMobileBackup[6762]: ERROR: Connection to device lost (MBErrorDomain/200)

    9/14/15 6:04:19.866 PM AppleMobileBackup[6762]: ERROR: Backup error: -10

    9/14/15 6:04:19.866 PM AppleMobileBackup[6762]: 6762:2088280832|DeviceLinkConnection.c:_DLMainThreadMessagePortCallback| ERROR: Error creating components from read data: 'NULL data returned from read'

    9/14/15 6:04:19.866 PM AppleMobileBackup[6762]: ERROR: Connection to device lost (MBErrorDomain/200)

     

    I am going to try again, but deleting the backup from ~/Library/Application Support/MobileSync/Backup and not iTunes.

     

    It's strange how it was 75% full before failing. Usually it fails within a few mins.

  • by fidnado,

    fidnado fidnado Sep 14, 2015 6:24 PM in response to Frank Malloy
    Level 1 (0 points)
    Sep 14, 2015 6:24 PM in response to Frank Malloy

    That's because it usually gives the error at the end of the Backup step but it only takes a few mins because it's an incremental backup not starting from scratch. My guess is your backup will fail again towards the end of the step.

  • by kiwimacguy,

    kiwimacguy kiwimacguy Sep 14, 2015 6:33 PM in response to Frank Malloy
    Level 1 (0 points)
    Sep 14, 2015 6:33 PM in response to Frank Malloy

    Hey Frank Malloy!

     

    Great to see Kelly at Decipher Tools has come to the party and doing her best to assist you Re: iTunes could not backup iPhone because the iPhone disconnected.

     

    Like I said Frank, If theres  anyone who can help you fix this nasty problem, its going be Kelly and the Decipher team!

     

    Good luck mate, Hope it works out!

  • by Frank Malloy,

    Frank Malloy Frank Malloy Sep 14, 2015 6:34 PM in response to fidnado
    Level 2 (355 points)
    iPad
    Sep 14, 2015 6:34 PM in response to fidnado

    Yep, now it's toward the end. Strange, the last time I deleted the backup and it finished...

     

    I'm on Yosemite on an iMac with an iPhone 6 running iOS 9.0. Yes, I know that it's not out until Wed. It was failing the same way on 8.4.1.

first Previous Page 17 of 23 last Next