-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not start service com.apple.mobilebackup2. #1546
Comments
Seems like you are using an old version, newer code prints an error description of why it doesn't work. Run with |
Thanks Nikias, The version I used is 1.3, which I believe is the current one. Furthermore, the Mac where I tested did not have any previous version. As to use -d, I will try later today but I don't expect much of it, as the message is clear: com.apple.mobilebackup2 did not start.... My question still is if didn't start because some I did or failed to do, or if it is being caused by an Apple issue with libimobile. |
Nikias, after running the command with -d, I got lots of info (400 lines or so on the terminal). At first, it seems to be ok: 15:29:05 lockdown.c:1168 lockdownd_start_session(): Session startup OK But then this happened: 15:29:05 lockdown.c:1239 lockdownd_build_start_service_request(): ERROR: Failed to retrieve the escrow bag from the device's record 15:29:05 lockdown.c:278 lockdownd_stop_session(): success 15:29:05 idevice.c:1208 idevice_connection_disable_bypass_ssl(): SSL mode disabled And ended as: 15:29:05 notification_proxy.c:299 np_get_notification(): NotificationProxy died! 15:29:05 idevice.c:1208 idevice_connection_disable_bypass_ssl(): SSL mode disabled Any help will be highly appreciated, Thanks! |
current version is HEAD from master branch, there is no tag for version that is working with newer ioses. |
Error using idevicebackup2 backup --full --password 'xxxx': Could not start service com.apple.mobilebackup2.
Is this caused for something I should have installed and I didn't or is a problem caused by an Apple recent change?
Running a MacBook Pro (Intel), macOS Sonoma and the connected iPhone is 13 Pro Max running iOS 17.3
Thanks!
The text was updated successfully, but these errors were encountered: