-
Notifications
You must be signed in to change notification settings - Fork 387
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
iOS upgrade fail #1
Comments
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. |
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 How to proceed in order to retrieve my contacts I (hope I) saved using |
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:
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 notifications@github.com 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. |
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 notifications@github.com wrote:
|
What I tried so far:
So I doubt some Windows pairing file would make a difference. |
On Dec 17, 2013, at 5:07 PM, Amoremio notifications@github.com wrote:
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.
No, the trust is a secure negotiation between the device and the host computer, so the USB parameters are not enough.
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 |
@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. |
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. |
Try this procedure and report back the output of usbmuxd, idevicepair, and ideviceinfo:
Aaron On Dec 19, 2013, at 12:26 PM, Amoremio notifications@github.com wrote:
|
cleaned up unnecessary stuff
with the new iOS upgrade for iPhones I tried updating my iPhone4 using the current version of idevicerestore. It was not able to use the apple ipsw file online.
So I downloaded the file which was successfully identified and entered it in idevicerestore manually
There seems to be some upgrading, but mounting fails and iPhone freezes in the connect-to-iTunes screen. I cannot even restore it by
it reboots and shows the same screen as before, also not working is idevicebackup
Same result giving the UDID.
That is all information I can think of giving to you and hope it may be helpful
in order to solve the problem. As my phone is literally crippled now, I'll have to go to my provider's service store tomorrow.
My notebook is running with xubuntu,
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
The text was updated successfully, but these errors were encountered: