Making bricks out of Apples: iOS 9.3.2

[pwalker8]

Originally Posted by WT Sharpe

You're a better man than I am, Gunga Din!

I gave it a few days, but given how little buzz there was about problems, I figured it was some odd local issue. Just made sure that I have a good signal when I downloaded the update. I get the distinct impression that the majority of bricked devices are either corrupt download or jail broken devices. Most of the time, if you wait a couple of days so the update servers won't be so over loaded, then you won't have any problems.

[Wearever]

I'm waiting to update my phone & mini & Air, although the nagging is relentless on all three. My husband updated yesterday on his phone and it froze, he was able to bring it back by holding the top on\off button & the home button simultaneously, for 10 seconds. So I'll wait a couple more days, just in case. Although neither of us has the Ipad Pro.

[FlorenceArt]

iPad Pro 9.7" is still nagging me twice a day to upgrade, and then after I've gone through all the steps and accepted whatever it is that I'm accepting, it tells me it can't verify the upgrade because I have no internet connection. My Internet connection is working fine for everything else. This is starting to be just a little bit annoying.

Originally Posted by FlorenceArt

iPad Pro 9.7" is still nagging me twice a day to upgrade, and then after I've gone through all the steps and accepted whatever it is that I'm accepting, it tells me it can't verify the upgrade because I have no internet connection. My Internet connection is working fine for everything else. This is starting to be just a little bit annoying.

It might be the connection is broken on Apple's end. Apple servers are notoriously slow with update downloads and rather finicky at times too.

ETA: I see on the Mac Rumors website that the Apple servers are reportedly having issues today. http://www.macrumors.com/2016/06/02/...icloud-outage/

[FlorenceArt]

Originally Posted by jswinden

It might be the connection is broken on Apple's end. Apple servers are notoriously slow with update downloads and rather finicky at times too.

ETA: I see on the Mac Rumors website that the Apple servers are reportedly having issues today. http://www.macrumors.com/2016/06/02/...icloud-outage/

Mmm, maybe. This has happened two days (and three attempts) in a row though.

[Bookworm_Girl]

Apple had stopped allowing iPad Pro 9.7 devices to install the update. I read on MacRumors that yesterday they released a new version of 9.3.2 so you should be able to install it now. There is also a support document now on how to fix the Error 56 problem as well as one other issue that may happen during the update installation.

The nagging is really, really annoying. I think I'm going to wait a week or so to make sure there are no more complaints with the new 9.3.2 before I update my iPad Pro 9.7.

[FlorenceArt]

I agree bout the nagging. And also about waiting a few more days.

[dandelioncottage]

I bought an IPad Pro 9.7 last weekend, and the Apple Store guy told me the bricking problem was only with the cellular version. However, he still advised me to wait a few weeks on the upgrade.

Originally Posted by FlorenceArt

I agree bout the nagging. And also about waiting a few more days.

[pwalker8]

Originally Posted by dandelioncottage

I bought an IPad Pro 9.7 last weekend, and the Apple Store guy told me the bricking problem was only with the cellular version. However, he still advised me to wait a few weeks on the upgrade.

Interesting. I suspect that if you upgrade over wifi, you are fine. A lot of the brinking problems over the years can be attributed to having a bad connection when you try to upgrade. Rule number 1 - make sure you have a good internet connection before upgrading.

[HarryT]

Originally Posted by pwalker8

Interesting. I suspect that if you upgrade over wifi, you are fine. A lot of the brinking problems over the years can be attributed to having a bad connection when you try to upgrade. Rule number 1 - make sure you have a good internet connection before upgrading.

This really shouldn't be an issue. The update file has a checksum associated with it, and the first stage of the upgrade process is to verify that the update file is not corrupted. If the checksum doesn't match, the upgrade doesn't go ahead.

[cedhax]

According to MacRumors.com news on June 2, a new version of iOS 9.3.2 has fixed the bricking issue.

The new version of iOS 9.3.2 has a build number 13F72, which is different from the build number of the old version of iOS 9.3.2 launched on May 16. Thus, the iOS 9.3.2 you download on different days may not be the same at all. One may be broken; another may be fixed. This practice may be confusing sometimes, but overall this seems to benefit Apple's PR image.

[pwalker8]

Originally Posted by HarryT

This really shouldn't be an issue. The update file has a checksum associated with it, and the first stage of the upgrade process is to verify that the update file is not corrupted. If the checksum doesn't match, the upgrade doesn't go ahead.

Shouldn't be and is, are two different things. I've never had an upgrade problem with Apple and I never had a virus issue with my various Windows computers simply because I follow certain guidelines. In theory, those guide lines shouldn't be needed, but life rarely follows theory.

[HarryT]

Originally Posted by pwalker8

Shouldn't be and is, are two different things. I've never had an upgrade problem with Apple and I never had a virus issue with my various Windows computers simply because I follow certain guidelines. In theory, those guide lines shouldn't be needed, but life rarely follows theory.

I don't disagree with any of that, but I'm interested to understand how you know that "A lot of the brinking problems over the years can be attributed to having a bad connection when you try to upgrade." I honestly can't recall ever hearing of such a thing. An update either installs or it doesn't; a corrupted installation file is extremely unlikely to run at all. How do you know that a lot of bricking problems are due to corrupted files?

[pwalker8]

Originally Posted by HarryT

I don't disagree with any of that, but I'm interested to understand how you know that "A lot of the brinking problems over the years can be attributed to having a bad connection when you try to upgrade." I honestly can't recall ever hearing of such a thing. An update either installs or it doesn't; a corrupted installation file is extremely unlikely to run at all. How do you know that a lot of bricking problems are due to corrupted files?

I don't know that a lot of bricking problems are due to corrupted files, however, I do read the Apple boards and noticed that a lot of people over the years who complained about a bricked device mentioned that they didn't have a good connection. Keep in mind that you are not downloading the installation file, you are downloading a image that is installed. Until fairly recently, this all happened on your computer rather than your device.

In computer programming, many programmers never really learn how to handle exception conditions well. It's not easy and most programming classes tend to gloss over it. So it's not terribly surprising that exception conditions cause the most issues.

I also tend to avoid peak times as well, simply because that's when the servers are being swamped and more likely to generate a bad download.

[Bookworm_Girl]

I updated my iOS devices finally last weekend. Everything has been functioning normally as expected, including my iPad Pro 9.7.