Would love to update but wont take the risk..this is nuts Apple releases an update that causes an iPad to crash..now I understand that updates causes some people's devices to have issues, always happens when people update their PS4, I update mine and never have a problem but this seems to be much more widespread than that..my Ipad Pro is too good a shape to even risk this
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
My replacement iPad came within a day! 
Of course there is still the inconvenience of restoring from my iCloud backup (my iTunes backup is a few weeks old), and I'm not even going to try putting iOS 9.3.2 until I see a report about a fix, but at least I'll be back up and running soon.
Of course there is still the inconvenience of restoring from my iCloud backup (my iTunes backup is a few weeks old), and I'm not even going to try putting iOS 9.3.2 until I see a report about a fix, but at least I'll be back up and running soon.At least Microsoft could claim that they had a lot of 3rd-party software and hardware to support .. an insane number of possible configurations. The iPad's software and hardware are all controlled by Apple and there is only a very limited number of configurations - and they can't get that right!
Apparently, Apple isn't even remotely as capable as MS.
So, how do we know if the 9.3.2 update our iPads have downloaded is the fixed version or not (whenever the new one is completed and starts rolling out)? IIRC, Apple screwed up an earlier update (9.3.1?) and then released a patched version without changing the number. That is like having twins and giving them the same names just because you weren't expecting two babies. It makes no sense and violates the very principle of even having names. At least the patched update should be 9.3.2.1.
FWIW, the update my 32GB WiFi iPad Pro 9.7 has downloaded is 181MB. I think it was only eighty-something MB a couple of days ago (Settings - General - Storage & iCloud Usage - Manage Storage - (scroll down till you find it (iOS 9.3.2 181MB for me)).
Do I have a patched 9.3.2 update already? How can Apple put one out with no way to tell which version it is?
FWIW, the update my 32GB WiFi iPad Pro 9.7 has downloaded is 181MB. I think it was only eighty-something MB a couple of days ago (Settings - General - Storage & iCloud Usage - Manage Storage - (scroll down till you find it (iOS 9.3.2 181MB for me)).
Do I have a patched 9.3.2 update already? How can Apple put one out with no way to tell which version it is?
Last edited:
They have to much crap on their plate with all these iPads and all that type of ish (think feces)
I'm never going to install it. This phone will likely stay at 9.3.1 forever.
[doublepost=1463626682][/doublepost]So Last night my husband updated his new 3 week old iPad Pro and yes - just like the picture! Its a brick...Error 56.
iOS 9.3.2 is causing problems for some 9.7-inch iPad Pro owners, with multiple MacRumors readers and Twitter users reporting issues shortly after installing the update over the air. Affected users are seeing an "Error 56" message that instructs them to plug their devices into iTunes.
While not all 9.7-inch iPad Pro users have reported problems, there have been a number of reports on the MacRumors forums and on social networks, suggesting the problem is widespread. Attempting to restore through iTunes doesn't appear to resolve the issue. From MacRumors user NewtypeCJ:
According to Apple's error code support document, error 56 is a hardware issue. The document recommends installing the latest version of iTunes, checking for issues with third-party security software, and attempting a restore twice. Apple recommends customers who are still seeing the error message contact Apple support.
With a number of users affected by the bricking issue, Apple will likely need to release an updated version of iOS 9.3.2 that solves the problem.
Update May 17, 10:47 PM: Apple has issued a statement to iMore's Rene Ritchie, simply stating the company is "looking into a small number of reports" regarding this issue.No cause or specific solution has apparently been determined.
Article Link: iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message [Updated]
He spent hours downloading iTunes and trying the restore but it reported that the iPad could not be restored.He then took it to Apple shop this morning. They said they had never heard of this happening. <Um ever tried google??> and gave him a new one.They said that the bricked one will be melted down - weird why would you melt down something that has a software update issue? He is not going to try the update again - tho I reckon he should just to rule out insanity??
What bugs are you referring to? I remember both of these pretty well, and don't remember ANY ongoing problems with either OS. In fact, I NEVER had to do an OS reinstall on any version of Mac OS X right up to Snow Leopard in the ENTIRE time of owning three Macs (with always two owned at once, and a total of 23 years of computer use when added together). Reinstalls started with Mac OS Lion, which has been called "The Vista of OS X," and have continued ever since.
I don't understand Apple these days. They obviously didn't check something properly and now it is costing them lots of money in tech support cost and retail device replacements.
I have to wonder if this slip in quality is because of the release date schedule. Before things were just released "when they are ready". Now it seems like updates come out for all the products..iOS, Mac, Apple TV, WatchOS all on the same day. They are all different products though. I find it hard to believe that they all have the same development cycle.
They will have to step up their reliability game before they release the Apple Car. Could you imagine THOSE getting bricked? "I'm sorry sir, please try plugging you car into iTunes". "I can't it's stuck in the desert". "Oh, well in that case hold tight, and we'll ship another one to you in 3-5 business days". Yeah...that's not going to fly.
I have to wonder if this slip in quality is because of the release date schedule. Before things were just released "when they are ready". Now it seems like updates come out for all the products..iOS, Mac, Apple TV, WatchOS all on the same day. They are all different products though. I find it hard to believe that they all have the same development cycle.
They will have to step up their reliability game before they release the Apple Car. Could you imagine THOSE getting bricked? "I'm sorry sir, please try plugging you car into iTunes". "I can't it's stuck in the desert". "Oh, well in that case hold tight, and we'll ship another one to you in 3-5 business days". Yeah...that's not going to fly.
I'm not going to update my iPad Pro 9.7" until we have the 'all clear'.
Is it possible to remove the red notification icon from the Settings icon? I have deleted the iOS 9.3.2 file from my device that it had automatically downloaded and was waiting to install.
Is it possible to remove the red notification icon from the Settings icon? I have deleted the iOS 9.3.2 file from my device that it had automatically downloaded and was waiting to install.
Did you get the error and issue while doing the update or did it happen right after the update or hours later? I updated this morning before I saw this issue. Just trying to figure out if I'm in the clear an hour after the update or will the issue rear its ugly head at some random time.My Pro 9.7 128 WIFI+Cell also died via OWA update. Apple Support said it would need to be replaced. They set up the appt and got to the store, they were able to recreate the issue. They had none in stock, but took new one out of the box for me and replaced. The Store said that Apple HAS PULLED THE UPDATE so that IPAD-PRO will not see the update. Will not try
If your iPad came back up, you should be in the clear on the error 56 issue. This particular issue happens immediately after the update.
iOS 9.3.2 is causing problems for some 9.7-inch iPad Pro owners, with multiple MacRumors readers and Twitter users reporting issues shortly after installing the update over the air. Affected users are seeing an "Error 56" message that instructs them to plug their devices into iTunes.
While not all 9.7-inch iPad Pro users have reported problems, there have been a number of reports on the MacRumors forums and on social networks, suggesting the problem is widespread. Attempting to restore through iTunes doesn't appear to resolve the issue. From MacRumors user NewtypeCJ:
According to Apple's error code support document, error 56 is a hardware issue. The document recommends installing the latest version of iTunes, checking for issues with third-party security software, and attempting a restore twice. Apple recommends customers who are still seeing the error message contact Apple support.
With a number of users affected by the bricking issue, Apple will likely need to release an updated version of iOS 9.3.2 that solves the problem.
Update May 17, 10:47 PM: Apple has issued a statement to iMore's Rene Ritchie, simply stating the company is "looking into a small number of reports" regarding this issue.No cause or specific solution has apparently been determined.
Article Link: iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message [Updated]
I have only seen reports about the 9.7" Pro. None about the larger model.
(Also a couple of reports of iPhones being bricked. Not sure if it's the same error.)
256GB 9.7 Pro updated last night with 9.3.2 and has been "Error 56ed." Have appointment at Genius Bar tomorrow afternoon... when I asked the Apple Support guy during our chat last night what possible fix there could be, he said they'd have to "inspect" my iPad. Considering it is about 5 weeks old and has been treated with kid gloves, I'm reading between the lines that the only remedy is likely a new iPad.
Last edited:
Soon as the update "finished" It downloaded it then rebooted, then came up with the dreaded Hook to itunes. From there NOTHING. As least Apple stepped up and gave me a brand new device. Am still not happy that the update is still available. Apple said it will be fine to update. Yeah DO NOT THINK SO. Do not want to go and brick another device as I have heard of more failures then success.
[doublepost=1463664355][/doublepost]
While I was at the Apple store geting my Bricked IPAD PRO 9.7 replaced there were a few folks also there for the same thing. Once was the larger pro but most were the 9.7. A coworker did say his iPhone 6s was bricked.
The major difference is that these updates must interact properly with the anti-tamper features on the secure enclave. These errors happen when the security handshakes effectively fail and the secure enclave ends up treating the update as malware. Of course the details usually differ, but the underlying issues are all related.
It is probably best for us, the users, that the secure enclave errs on the safe side and bricks the device, rather than behaving in a way that would allow someone else to own our device.
The modern iOS upgrade process is way more complex than the upgrade process on prior generations of hardware.
[doublepost=1463666259][/doublepost]
I don't know if I'm just using my hardware improperly, but we have two '09 MacBook Pros, '13 iMac, had an '08 iMac and '09 MacBook, also have a '15 iMac and a year old hackintosh, all of this currently runs Yosemite, and I've never had to reinstall anything. I have *chosen* to do a couple of major OS X version updates as reinstalls, but this was never in response to any sort of an issue. Just so that I don't appear unrealistic, I must state that OS X versions past Mountain Lion perform much worse than expected on mechanical hard drives. OTOH, the now 7 year old Apple hardware we still use works great if you use a decent SSD. The only device on a mechanical drive is the '13 iMac, and I'll be upgrading that to a 1TB SSD soonish, it'll work way better then.
[doublepost=1463666698][/doublepost]
The update has failed most likely because the secure enclave is treating your device as tampered with. IOW, due to a bug in the updated OS X and/or the update process itself, the device is in a state where the secure enclave has dropped the encryption keys to the iOS volume and to parts of the secure enclave firmware and permanently disabled access to the device. The secure enclave is a tamper-proof piece of hardware that's not treated as a replaceable part, so the entire device is a paperweight at this point.
It should be pointed out that although this is a bug, it's a reassuring one. The security system has acted as designed, protecting you from potentially malicious tampering. Sure, you didn't really attempt to tamper with the device, but it'd be worse if the design would permit changes it was "unsure" about. The only safe thing to do in such a case was exactly what happened: a bricked device. That's exactly what should be happening when someone attempts to tamper with your device, e.g. if law enforcement tried to sniff around your device without your permission, etc.
Sure it's kind of a fail when genuine Apple update is treated as malware, but hey, you got a hardware refresh out of it
Having tried to get a bunch of MS Surface 3s replaced under warranty was a much more drawn-out process, if you care for my own anecdote.
You can't remove the icon but you can stop it from auto-checking for updates, which will also stop the auto-download.
Go to
settings
iTunes & app stores
updates
slide the updates button to 'off'