Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I get this error when plugging in my iPhone 3GS. What does it mean?

enter image description here

share|improve this question

1 Answer 1

up vote 8 down vote accepted

Here's what worked for me (from

When your device is plugged in, close out the error. Then run

idevicepair unpair && idevicepair pair

Then unplug your device and plug it back in.

Also, if it worked in the first place, but then you reset the iPhone (used Erase all Content and Settings option in the Reset menu in Settings) and it stopped mounting, then the solution is to remove the ~/.config/libimobiledevice/ directory and then replug your iPhone.

share|improve this answer
Sorry for the long delay. Yes, if you upgrade libimobiledevice1 to 1.0.4, and usbmuxd to 1.0.6, it should solve this error. I can confirm the fix on my system. Since both versions are included in Debian unstable, I'm closing the bug report. Feel free to reopen it if it's not solve. Regards, Julien Lavergne From here:… I personally am part way through testing this. Dave – user38438 Dec 18 '11 at 22:57
But I am already using libimobiledevice 1.1.1 and usbmuxd 1.0.7. – wim Dec 20 '11 at 8:19
Yeah I have seen that, but I am more interested in what is the cause and what is an "Unhandled Lockdown error", because it was reoccurring problem for me – wim Feb 2 '12 at 6:08
This worked for me on 11.04 with iOS 5.0. However, I needed to run the command sudo apt-get install libimobiledevice-utils first before I could run idevicepair unpair && idevicepair pair. (More info here.) – Ray Vega Feb 11 '12 at 6:22
Can't comment on san's response because I don't have the rep. san's response works; if however after following the unpair/pair instructions and unplugging/plugging your device you still get the error you may need to unlock your device (and, if needed, insert your PIN) and unpair/pair while the device is unlocked. While a device is locked it cannot be paired. wim: In reply to your other comment I believe it may have been because your device was paired with another machine. Unless it's a recurring problem in which case I couldn't say. – VodkaSurprise Feb 16 '12 at 21:38

protected by Community Apr 19 '12 at 13:38

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.