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
I just tried to update to 9.3.2 and I do get error 56. Very frustrating. Just after finished to verify the update and once it starts to update the firmware (9.7 iPad Pro 128 wi-fi)
I received this error, and i'm fairly certain there are more than "5 people" getting this error, so I do think it's a valid article.
iPad Pro 9.7"
- First update was via OTA. When I looked after lunch it had the connect to iTunes screen.
- I then tried iTunes 12.4 on 10.11.5 and received Error 56.
- I tried ipsw of 9.3.1 and still receive error 56.
iPad Pro 9.7"
- First update was via OTA. When I looked after lunch it had the connect to iTunes screen.
- I then tried iTunes 12.4 on 10.11.5 and received Error 56.
- I tried ipsw of 9.3.1 and still receive error 56.
Add me to the list, error 56, iPad Pro 9.7 128GB. Have the error since the last beta and reported it to Apple. I'm still waiting for UPS to pick it up.
Maybe now I should wait if there is a chance that the device doesn't need to be replaced.
In the iTunes update log it stops while writing the firmware part.
Are the bricked ones only 128GB?
Maybe now I should wait if there is a chance that the device doesn't need to be replaced.
In the iTunes update log it stops while writing the firmware part.
Are the bricked ones only 128GB?
[doublepost=1463432415][/doublepost]I think it's funny in these updates, people are always complaining, but in all the years I've had apple products and dealing with iOS, it's been smooth sailing for me, never had an issue with any update ever...wtf is wrong with people lol
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.
Article Link: iOS 9.3.2 Bricking Some 9.7-inch iPad Pro Devices With 'Error 56' Message
When you have so much control over the product from end-to-end like Apple does... It's shameful that this happens. No, it's pathetic that it happens to anyone actually.
Microsoft I could see and almost excuse... so many drivers and manufacturers making crap with millions of configuration options out there in the wild... but Apple?
One (and only) good thing is that Apple will most likely get you out of the jam one way or another.
Microsoft I could see and almost excuse... so many drivers and manufacturers making crap with millions of configuration options out there in the wild... but Apple?
One (and only) good thing is that Apple will most likely get you out of the jam one way or another.
No problems here -- first of all, I downloaded and installed the latest OS update, which included the newest version of iTunes, and then after that plugged in each of my iOS devices one-by-one and updated them while they were connected physically to the computer and iTunes. I always do things this way because in the long run it just seems safer than doing it OTA. After I finished updating my iOS devices (one iPhone, two iPads) then I moved on to update the Apple watch, too..... a busy updating day here!
I am a software developer, and the beta process goes through several stages for a reason — so the version that comes out at the end has all of the wrinkles ironed out. That's how it's supposed to work, and Apple is failing somewhere.
The fact that only some iPad Pros are being affected suggests that there's a difference with the hardware of those particular devices that Apple didn't test thoroughly enough. Two iPads may contain parts from different vendors. We know this. Just like computers of the same model may have hard drives from different vendors... some may be from HP, others may be Samsung, etc. All vendors are required to meet Apple's specifications so that the user experience is the same. But that does not mean that the internal components are identical in every way.
I wouldn't call this complaining. If it was just bugs I have no problem dealing with that. It's the fact that it rendered my device unusable. I updated iTunes and OS X to today's versions and no luck.
It's a good point to be fair, I see very few Apple fans left anymore - just a lot of hate, moaning and negativity. I wonder if its iPhone owners who hate Macs and Android users who are just here waiting to mock... not sure.
For certain I see "Apple Fanboy" used as a pejorative on here a lot more than I see actually biased fanboyism.
I remember the days when Microsoft was like this. It's a shame that Apple is now the same way. I wish Steve was still here.
I'll stick with the armchair manager, because you sound entirely too comfortable with failure.
[doublepost=1463433419][/doublepost]
No one claimed the issue impacted every 9.7" iPad Pro. Nice straw man, though.
I remember the days when Microsoft was like this. It's a shame that Apple is now the same way. I wish Steve was still here.
Microsoft is much better now, Apple is just plain incompetent with its software. I use windows 10 and a xbox one, they are always getting thoroughly updated, and plus, Microsoft is listening to feedback from its users, something Apple rarely does.
Apple cloud services are horrible, I have a fast internet connection, yet I can't download anything on the app store with fast speeds. Apple Music is a disaster, it's songs take 1-2 seconds to load, whereas Spotify is instantaneous, The "For You" suggestions are broken, I see albums repeating over and over when I scroll down. Complete crap, this will be my last month using Apple Music.
Wow, $10B in annual R&D spending and Apple can't get a decent software update out the door. Way to go Apple, looks like your software philosophy is following closely behind your inability to release new, competitive products. I guess there's always this car thing that's coming in four years, but that's a long time to wait for something new from Apple.
Hey, I have an idea. Why don't you bring Ive back from getting knighted by the queen and hob-snobbing with the fashionistas to actually do his job. The state of Apple's industrial design is seriously languishing and it's pretty obvious why. Mac Pro hasn't been updated in over 3 years, what on earth is Phil Schiller doing with his time? Certainly iterative updates of the iDevices cannot be taking up so much of the senior executive's time that we cannot have decent updates of the desktop products?
If ever Apple needed a leader, now is the time.
Hey, I have an idea. Why don't you bring Ive back from getting knighted by the queen and hob-snobbing with the fashionistas to actually do his job. The state of Apple's industrial design is seriously languishing and it's pretty obvious why. Mac Pro hasn't been updated in over 3 years, what on earth is Phil Schiller doing with his time? Certainly iterative updates of the iDevices cannot be taking up so much of the senior executive's time that we cannot have decent updates of the desktop products?
If ever Apple needed a leader, now is the time.
There was never such a thing as bug-free updates.
I think the main difference now is how quickly people can communicate to a large group of people and how the media is getting into the bug reporting business... even if it's affecting a small number of users... which makes it seem far worse than it really is. Remember bendgate?
I don't know if this particular issue is widespread or not, but I do wonder how many users here would even know about this, or any of the other bugs that MR reports if they hadn't reported it.
Did you join today just to tell us this?