iOS upgrade fail about idevicerestore

[FunkyM]

Thanks for the extended report. Just pass "-e" to enable erase restore mode to idevicerestore and run it again. This should work for an iPhone 4 just fine with the current git master. You also need to use "idevicebackup2" and not "idevicebackup". Latter only works up to iOS 3.x afair. We also noticed that when doing "update restores" of major versions (example: iOS 6 to iOS 7), fsck will always complain and fail which appears to be "by design" from Apple. Therefore an "erase restore" is required here.

[Amoremio]

Thanks, I ended up with a working iPhone4 iOS7. No contacts or other data though.

Also, my iPhone does not connect to my computer anymore not even idevice_id recognises the phone and asks whether it is plugged in. The iphone keeps asking whether to trust the computer but nothing else happens.
However, the file manager displays the phone even though not accessible.

How to proceed in order to retrieve my contacts I (hope I) saved using idevicebackup2 in a filefolder before the erase-restore odyssey to iOS7?

[aburgh]

The "-e" option to idevicerestore repartitions the flash, creating new System and Data partitions. You must restore from backup and re-sync your media to get the device back to the state before the upgrade. You should start by restoring your backup. I think you want:

$ idevicebackup2 restore --system --reboot /path/to/backup

If the backup is encrypted, you will also need the "--password" option. If it's not encrypted, the Keychain, containing all your passwords, is not included in the backup. Thus, that is a practical reason to enable encrypted backups even if you are not concerned about the security of your backup. The reason your attempt to restore before did not work is that the device was in Recovery Mode; the backup service that idevicebackup{2} backs up and restores your user data, and it requires the device to be fully booted and operating normally to operate. idevicerestore installs or updates the OS and does not operate on your data, except that doing a full restore erases everything, including your data.

Hope this helps,

Aaron

On Dec 17, 2013, at 8:02 AM, Amoremio [email protected] wrote:

Thanks, I ended up with a working iPhone4 iOS7. No contacts or other data though.

Also, my iPhone does not connect to my computer anymore not even idevice_id recognises the phone and asks whether it is plugged in. The iphone keeps asking whether to trust the computer but nothing else happens.
However, the file manager displays the phone even though not accessible.

How to proceed in order to retrieve my contacts I (hope I) saved using idevicebackup2 in a filefolder before the erase-restore odyssey to iOS7?

—
Reply to this email directly or view it on GitHub.

[Amoremio]

Thanks Aaron, that would probably help going forward. If only the iPhone would show up on the computer when connected. I assume there may be some sort of firewall coming with the new OS which keeps asking me whether to trust the computer, but I cannot identify the idevice nor send a command as reboot. In brief, iPhone keeps asking whether to trust the computer it's connected to and computer keeps asking whether iPhone is plugged in.
Any idea on how to troubleshoot that first?

[aburgh]

When you run a utility like "ideviceinfo", does that trigger the "Trust this Computer" dialog? If so, that indicates that the device is visible on the USB bus and your problem is with establishing a trust. Without the trust, the utilities will be denied and they will report the message you see. I've had some luck by repeatedly running ideviceinfo and responding to the dialog as quickly as possible. Usually, by the second or third attempt it has been able to pair (establish a "trust") with the device. But, I'm on Mac OS X, not Linux, so YMMV.

The libimobiledevice maintainers were working on some fixes to improve the pairing process. If you can't get it paired, I will double-check to see if their fixes have been committed.

Another option may be to connect it to an OS X or Windows machine to create a pairing file, then copy that to the appropriate location on your Ubuntu machine. I think libimobiledevice is using a compatible file format for the host pairing file.

Aaron

On Dec 17, 2013, at 12:19 PM, Amoremio [email protected] wrote:

Thanks Aaron, that would probably help going forward. If only the iPhone would show up on the computer when connected. I assume there may be some sort of firewall coming with the new OS which keeps asking me whether to trust the computer, but I cannot identify the idevice nor send a command as reboot. In brief, iPhone keeps asking whether to trust the computer it's connected to and computer keeps asking whether iPhone is plugged in.
Any idea on how to troubleshoot that first?

Gesendet: Dienstag, 17. Dezember 2013 um 15:07 UhrVon: "Aaron Burghardt" [email protected]: libimobiledevice/idevicerestore [email protected]: Amoremio [email protected]: Re: [idevicerestore] iOS upgrade fail (#1)

The "-e" option to idevicerestore repartitions the flash, creating new System and Data partitions. You must restore from backup and re-sync your media to get the device back to the state before the upgrade. You should start by restoring your backup. I think you want:

$ idevicebackup2 restore --system --reboot /path/to/backup

If the backup is encrypted, you will also need the "--password" option. If it's not encrypted, the Keychain, containing all your passwords, is not included in the backup. Thus, that is a practical reason to enable encrypted backups even if you are not concerned about the security of your backup. The reason your attempt to restore before did not work is that the device was in Recovery Mode; the backup service that idevicebackup{2} backs up and restores your user data, and it requires the device to be fully booted and operating normally to operate. idevicerestore installs or updates the OS and does not operate on your data, except that doing a full restore erases everything, including your data.

Hope this helps,

Aaron

On Dec 17, 2013, at 8:02 AM, Amoremio [email protected] wrote:

Thanks, I ended up with a working iPhone4 iOS7. No contacts or other data though.

Also, my iPhone does not connect to my computer anymore not even idevice_id recognises the phone and asks whether it is plugged in. The iphone keeps asking whether to trust the computer but nothing else happens.

However, the file manager displays the phone even though not accessible.

How to proceed in order to retrieve my contacts I (hope I) saved using idevicebackup2 in a filefolder before the erase-restore odyssey to iOS7?

—

Reply to this email directly or view it on GitHub.

—Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[Amoremio]

What I tried so far:
using 'lsusb' to list all usb devices, the iPhone clearly registers as connected. However it does not throw a "trust" query on the phone. A following 'ideviceinfo' says there is no device plugged in and it doesn't even trigger a "trust query on the phone. There is no trust query at all anymore using any idevice* command. Only when newly plugged into the usb port a single query is encountered and fails no matter which answer I give.
I have tried to enable the wifi hotspot on my phone which lead to several "trust" queries but even after 24 trustful answers was not successful in producing any kind of data connection.
May it be a timing problem between the computer trying to connect hence waiting for positive response and the user being able to "trust" only after a certain time interval the phone needs to even pop up the dialog?
As for the pairing file - my computer says it already paired with the phone (as says 'idevicepair list'). But validation fails with

mynotebook@home:~$ sudo idevicepair -u 2a527e79fe* validate
No device found with udid (null), is it plugged in?

So I doubt some Windows pairing file would make a difference.
Could one implement a way to pair via the known usb details from the 'lsusb' response? Or some way to refresh the trust query?
Thanks a lot for your responses so far and for the considerations.
Amo

[aburgh]

On Dec 17, 2013, at 5:07 PM, Amoremio [email protected] wrote:

What I tried so far:
using lsusb to list all usb devices, the iPhone clearly registers as connected. However it does not throw a "trust" query on the phone. A following ideviceinfo says there is no device plugged in and it doesn't even trigger a "trust query on the phone. There is no trust query at all anymore using any idevice* command. Only when newly plugged into the usb port a single query is encountered and fails no matter which answer I give.
I have tried to enable the wifi hotspot on my phone which lead to several "trust" queries but even after 24 trustful answers was not successful in producing any kind of data connection.
May it be a timing problem between the computer trying to connect hence waiting for positive response and the user being able to "trust" only after a certain time interval the phone needs to even pop up the dialog?

On my OS X machine, I see regular connects and disconnects via wifi, so it appears either the device or the computer is polling at a regular interval, even after a trust is set up. In your case, I perhaps the polling is occurring and triggering the trust dialog.

As for the pairing file - my computer says it already paired with the phone (as says idevicepair list). But validation fails with
mynotebook@home:~$ sudo idevicepair -u 2a527e79fed0f065c3fe1d001089ca2a954124a4 validate No device found with udid (null), is it plugged in? So I doubt some Windows pairing file would make a difference.
Could one implement a way to pair via the known usb details from the lsusb response?

No, the trust is a secure negotiation between the device and the host computer, so the USB parameters are not enough.

Or some way to refresh the trust query?
Thanks a lot for your responses so far and for the considerations.
Amo

Getting a file from a Windows machine may work. Your existing one won't validate because the corresponding file on the device got erased when you restored, so you need to set up a new trust, which will create new files on the computer and the device. The pairing file on the computer side does not have any host info in it, so it can be moved to other machines (although they can be made machine-specific with the Apple Configurator or other MDM solutions).

Aaron

[FunkyM]

@Amoremio Are you using the latest usbmuxd, libusbmud and libimobiledevice git master or some version installed from packages? For iOS 7 support, currently the latest git master of the listed libraries is required.

[Amoremio]

I have compiled and installed all packages from github.com/libimobiledevice including usbmuxd, libusbmuxd and libimobiledevice (except for sbmanager as the libbz2 package reference seems to be out-of-date being replaced by bzip2). In the current state meaning as they are at the moment on the web.

[aburgh]

Try this procedure and report back the output of usbmuxd, idevicepair, and ideviceinfo:

1. Disconnect the phone
2. start usbmuxd with "usbmuxd -f -v -v" (it runs in the foreground)
3. connect the phone
4. If prompted, tap "Trust" on the phone
5. When the output from usbmuxd settles, note the point in the output
6. attempt to pair, with the debug flag: "idevicepair -d pair"
7. If prompted, tap "Trust" on the phone
8. run "ideviceinfo -s" (this queries the device without requiring a trust)

Aaron

On Dec 19, 2013, at 12:26 PM, Amoremio [email protected] wrote:

I have compiled and installed all packages from github.com/libimobiledevice including usbmuxd, libusbmuxd and libimobiledevice (except for sbmanager as the libbz2 package reference seems to be out-of-date being replaced by bzip2). In the current state meaning as they are now. I keep installing the new one since I do not know of any options within the 'idevice*' commands or any other simple way to make the terminal print out a version number for the usbmuxd, libusbmuxd or libimobiledevice which I could compare to something. (ifuse has a such option though.)
I'll have another look whether there may be a conflicting package installed..

—
Reply to this email directly or view it on GitHub.