iPhone restore failed...

[Cr00zng]

I was updating my iPhone 8 Plus to iOS 13.6.1 with iMazing version 2.12.0. Of course, the first step had been backing up the current system.

iMazing downloaded the iOS 13.6.1 and proceeded to update the iPhone. Once the system rebooted, iMazing gave me this error message:



The iPhone currently stuck on displaying a black and white screen, indicating that it is connected to my PC, with the support.apple.com/iphone/restore link on the top. The only thing it does is seemingly reboots periodically and displays the same black and white screen.

iMazing software suggests erasing the device and reinstall iOS:



At this point I am hesitant to do that, since it states "may solve installation issues". That does not give me much confidence to proceed, but may not have other options...

I did contact iMazing, but the response stated, someone will help me within 48 hours. While it's the weekend and I am somewhat ok with the paper weight, I need to restore my iPhone. On the iPhone in itself, I cannot do anything, there's no reponse to any of the buttons on the iPhone.

Is there other options to restore the iPhone, other than iMazing software suggestion?

TIA...

 

[ferrarr]

Unfortunately, when the iPhone is in this state, there really is nothing else that can be done. You have to install an OS onto the iPhone, before you can restore it from a backup. Luckily, iCloud backs up when it is plugged in to power and charging, while off. So iCloud will most likely have your most recent backup. You should be able to check where your most recent backup is, either in iMazing, iTunes or iCloud.

How to view and delete old iCloud backups on iPhone and Mac

Here's how to delete old iCloud backups you don't need

www.imore.com

Sent from my iPad using Mac-Forums

 

[Cr00zng]

Thanks ferrar...

I was affraid that you'd say that, even if that has been my believe as well. There isn't much in my iCloud, certainly not backups, they are stored locally.

If iMazing cannot install the iOS, do I have a paper weight then?

I guess I am asking, if iMazing does not reinstall the iOS, is there other options?

TIA...

 

[Cr00zng]

Well, as I suspected, reinstalling iOS after erasing the device didn't work either.



Erasing the device seemingly worked, there's no name for the iPhone anymore in the error message.

So, back to my question, is there a way to install an iOS on to this iPhone in this state?

TIA...

 

[ferrarr]

iTunes can install iOS.

Unless you specifically turned iCloud backup off, then iCloud does backup when plugged in, connected to Wi-Fi and not in use.

 

[Cr00zng]

Thanks ferrar...

I did specifically turned off iCloud backup, among other things. Just the most important data, my contact list is in iCloud. The rest of it backed up locally.

Off I go to my MBP to see if if iTunes can install iOS on my iPhone....

 

[ferrarr]

You can use iTunes on your winOS PC too.

 

[Cr00zng]

At this point, I am getting fedup with Windows and iMazing. Let's give a chance for MBP...

 

[Cr00zng]

Both iTunes, W10 and MBP, throws the same error message when trying to install iOS:



Attempting to restore original software (iOS 13.6.1) with the MBP had succeeded to plain vanila GUI. Logging in to my Apple ID had been tricky, like usual, due to the 2FA enabled for the account. Luckily, my MBP received the text message with the six digit number. I still don't know what people do in similar cases, if their single Apple device cannot receive the text message. Anyway...

iMazing did restore the last back, that had been created prior to all these troubles started. Within limits of course, fingerprints, wallet content, etc., had not been restored, they needed to be added manually.

Ferrar, thank you for your help during this process, much appreciated...

Maybe reinstalling a clean version of the iOS will also fix do not disturb automatic messages while driving. The one that never worked for me on any of the vehicles...

 

[Cr00zng]

This is the first time, that I've done a restore operation on the iPhone. It's been an interesting experience to say the least...

As usual, I did a root cause analysis for this issues. It isn't as much to know what exactly went wrong, it's more of a how to prevent during the next update the same issue rearing its head again.

• Root cause: iMazing. The software does have routine to present error messages, but does not have a process to roll back the image. As such, the iPhone could not be started, pretty much DOA.
• Remediation: iTunes on MackBook Pro. This software had no issues with installing iOS 13.6.1 version on the iPhone 8 Plus.
• Prevention of the same issue: Do not use iMazing for software update.

While it is possible, that Apple's security clave does not allow iMazing access to some area; nonetheless, iMazing should be aware of this and prevent update in that case.

Interestingly, this is the "help" that I have received from iMazing, quote:

Hi,

Sorry to hear about your issue.

The error originates from iOS itself, not iMazing.

Please follow this guide for troubleshooting:
https://support.apple.com/en-us/HT204770#usb

Let us know how it goes.

Kind regards,

I tend to disagree and replied as such, quote:

I tend to disagree with your assessment of root cause for this issue and let me explain.



It is iMazing software that had not been able to update the iOS. Not only it wasn't able to update, the software had not been able to restore the previous version from the image that it had created during the process. Nor could it reinstall a clean version of the iOS.



In both cases, iMazing presented similar error message, but it had no routine to prevent this error. Instead, iMazing pretty much broke my iPhone that would not start.



The main reason for my disagreement is, that with iTunes on MacBook Pro there had no issues with restore the original software version. It's not hard to see, that the iOS and the iPhone where this has taken place are the same.

Maybe it is just my system and the latest version of iMazing software. In either case, the update routine should check for conditions and prevent updating, instead of rendering the iOS unbootable.

 

[ferrarr]

I have had this issue happen to me on two of the four iPhone versions I have owned. It happened on my iPhone 4s & 6. It didn't happen when I was using iMazing, but was when I was either backing up/syncing or updating the iPhones while connected to my Mac. That is the main reason I leave iCloud backup enabled, because I don't have to think about it or remember to do it.

As an FYI, when I used iMazing (2), they gave me a license for two PC's, so I installed one on my Mac, and the other on my wife's Dell.

 

[MacInWin]

I got rid of iMazing. It's fallen far from where it was originally. And with Catalina, I like the Finder interface to the iDevices better than iTunes.

 

[ferrarr]

I also got rid of iMazing a few months ago and I stopped backing up my iPhone to my Mac. I'm only using iCloud backups now. At this time I do still back up my iPad to my Mac, about once a month.

 

[chscag]

I agree with Jake on getting rid of iMazing. I too got rid of it some time ago. For some reason, it became too complicated and most of the time did not work right. It also took up more drive space than MS Office 365, if you can believe that.

I disagree with Bob above about not making backups to your Mac or PC. I recommend making a backup to both iCloud and your Mac/PC. Depending on iCloud to restore when there are no other backups available can be a disaster in waiting.

 

[MacInWin]

I back up to my Mac as well. And then that is backed up to my Time Machine. While iCloud is a good option, I prefer to have my backups where I can get to them on my schedule, not just when I have connectivity.

 

[IWT]

I backup all my iDevices to iCloud, iTunes and iMazing.

A number of posts, including those above, have made me wary of iMazing in much the same way that I gave up on iExplorer some time ago.

They hit the sweet spot for a while then fade away.

iTunes and iCloud continue to be the best options.

Ian

 

[Cr00zng]

Now you guys/gals tell me how bad is the iMazing software?

Anyway...

iMazing support changed its stance from Apple software issue to USB hardware issue, quote:

Hi,

The error code specifically refers the USB connection issue, so iMazing cannot be a part of it. Most likely when you've tried restoring using iMazing there was a poor connection for some reason. It can be as simple as having a little bit of dust on a USB cable/port.

Kind regards,

My response, quote:

Initially, you’ve stated that this “error originates from iOS itself”. Based on your latest response, that’s no longer the case, since your reasoning now is “a little bit of dust on a USB cable/port”. In another word, we’ve moved on from software to hardware issue as the root cause. May I gently remind you, that the same USB cable had been used for iTunes to restore the original software from Apple.

I’d much prefer, if support would admit, that the iMazing software isn’t that amazing after all. Especially when it comes to updating iOS version, possibly other features as well that I had not encounter as of yet.

Maybe it’s time for iMazing developers to get back to the drawing board, instead of forcing end users to do a “wild goose chase”.

Regards,

As they say, you give them enough rope....

At this point, I am just having fun with tech support. They had given me enough greaf and time to let them have some...

 

[chscag]

At one time, iMazing software worked well and we recommended it to our members. That is no longer the case. As a matter of fact, my personal recommendation is to not use it at all and if you have a copy installed, to uninstall it from your Mac or PC.

 

[MacInWin]

The USB thing was part of the issue with iMazing. I kept getting a message that the USB connection was bad and that iMazing could not connect. I use the same port for many USB purposes with zero errors. I replaced the cable with a brand new one from Apple, no change. I moved to a different USB port, no change. iMazing just seemed unable/unwilling to connect to my iPhone.

Finder, btw, worked perfectly, did the backups, syncing, updating that iMazing claimed to do. The final straw for me was that the backup of my iPhone, which has 512 GB of storage, with 160 GB in use, almost completely filled a 1TB drive for ONE backup. Close to 700 GB space taken for ONE backup of 160 GB of data. Figuring something had to have gone wrong, I deleted it and started over. Same result. iMazing got uninstalled that day. Between false error reports on fully functioning hardware and quadrupling of space for a backup, iMazing is definitely off my list, and my iDevices.

 

[Slydude]

This has been an interesting thread. I haven't had the issues with iMazing that you guys seem to have had recently. I'm not sure why.

I had an issue about a month or two ago that seems to have been the extent of it. It has been a while since I attempted a restore though so maybe that's why I haven't experienced issues.