Libiphone libiphone

Comments and changes to this ticket

• 

  Nikias Bassen June 8th, 2010 @ 03:00 PM

  • State changed from “new” to “open”
  • Assigned user set to “Nikias Bassen”

  Did you compile libimobiledevice yourself? If so, re-configure it with --enable-debug code and install it. If you installed packages, you can install the debug-version of libimobiledevice, libimobiledevice1-dbg. Look at my latest reply to ticket #147 there's a howto for using the packages from Paul McEnery's PPA for ubuntu.

  Then, you can run
  

  idevicebackup -d backup BACKUPDIR > idevicebackup.log
  

  to produce verbose error output logged to file idevicebackup.log which you then append here.
  I can then hopefully see what's wrong.

  Greetings
  Nikias

• You flagged this item as spam.
  

  E. Loralon June 8th, 2010 @ 03:07 PM

  Thank you Nikias,

  I will do as recommended tonight and post the result here. I did compile libimobiledevice myself.

  Have a great day.

  Loralon

• You flagged this item as spam.
  

  criley98 June 8th, 2010 @ 06:42 PM

  I installed the package via Synaptic. Here is my log regarding the above error.

  • idevicebackup.log 57.9 KB
• 

  Martin S. June 8th, 2010 @ 07:44 PM

  Can you post the output of "ideviceinfo -q com.apple.disk_usage" please?

• You flagged this item as spam.
  

  E. Loralon June 9th, 2010 @ 08:15 AM

  Hi Martin and Nikias,

  After following your recommendation I just tried now to backup my iPhone and it failed again. I have attached the log files as requested.

  Thank you again for helping.

  • idevicebackup2.log 38.7 KB
  • ideviceinfo.log 474 Bytes

• You flagged this item as spam.
  

  E. Loralon June 21st, 2010 @ 05:28 PM

  Hello Martin and Nikias,

  I haven't heard from you since I posted the logs. I am still having problems with the backup process of my phone. Would you please help on this?

  Thank you.

• 

  Martin S. June 21st, 2010 @ 10:15 PM

  Please run "idevicesyslog", then in parallel run idevicebackup and post the output. It should give us more hints.

• You flagged this item as spam.
  

  E. Loralon June 25th, 2010 @ 08:06 AM

  Hello Martin,

  Just reading now your reply. After trying I now get the following error:

  Started "com.apple.mobilebackup" service on port 58752.
  Reading Info.plist from backup.
  Starting backup...
  Reading existing Manifest.
  Could not read Manifest.plist, switching to full backup mode.
  Creating Info.plist for new backup.
  Requesting backup from device...
  ERROR: Could not start backup process: device refused to start the backup process.

  I believe this is because I have already upgraded to iOS 4.0.

  I guess I will have to wait until there is support iOS 4 before trying to backup again.

  Thank you very much for this project again.

• You flagged this item as spam.
  

  ronin-106998 (at lighthouseapp) July 13th, 2010 @ 07:50 AM

  • Milestone order changed from “0” to “0”

  I have the same problem when trying to backup my iPhone 3GS, running iPhone OS 3.1.3, jailbroken with Spirit.

  Short log:
  Started "com.apple.mobilebackup" service on port 60236.
  Reading Info.plist from backup.
  Starting backup...
  Reading existing Manifest.
  Could not read Manifest.plist, switching to full backup mode.
  Creating Info.plist for new backup.
  Requesting backup from device...
  Full backup mode.
  Please wait. Device is preparing backup data...
  idevicebackup: /build/src/libplist-1.3/src/plist.c:544: plist_get_uint_val: Assertion length == sizeof(uint64_t)' failed.

  So I recompiled libimobiledevice with --enable-debug-code and ran idevicebackup again, as well as the syslog and the output of "ideviceinfo -q com.apple.disk_usage". Here are the logs.

  Running Arch Linux x86_64, imobiledevice 1.0.2, usbmuxd 1.0.4, libusb 1.0.8.

  • disk_usage 474 Bytes
  • idb-log 60.1 KB
  • isyslog 32 KB
• 

  Martin S. July 18th, 2010 @ 12:09 AM

  Mind that iOS 4 is not supported as there now is a completely new backup protocol...
  @Schnouki: Please run idevicesyslog in parallel. Then start the backup process. Then copy the new output here. It must should some issue.

• You flagged this item as spam.
  

  rryder July 25th, 2010 @ 10:37 PM

  I hit this problem 100% of the time previously. After pulling the latest git commits this works great. I suspect the fix is from commit 930ad759419712e6dd939953ef4a1f0c5a655086

• 

  Martin S. July 26th, 2010 @ 12:28 PM

  • State changed from “open” to “resolved”
  • Assigned user changed from “Nikias Bassen” to “Martin S.”

  @rryder: Yes, that should fix it. If anyone has still issues with this please reopen this bug.