“Apple has today pulled iOS 9.3.2 for the 9.7 inch iPad Pro, following reports that users were seeing their iPads bricked after updating to the latest iOS release on Monday,” Benjamin Mayo reports for 9to5Mac. “The bug does not affect the larger, 12.9 inch iPad Pro.”
“After updating, users seeing the bug would be prompted to Connect to iTunes on the iPad display,” Mayo reports. “However, aside from an Error 56 debug message, the device could not be restored through iTunes or DFU.”
“We have heard a few reports that Apple will replace the iPad Pro at the Genius Bar with new hardware, if bricked by Error 56,” Mayo reports. “This is the latest public comment from Apple, as of yesterday. ‘We’re looking into a small number of reports that some iPad units are receiving an error when updating the software. Those unable to restore their device through iTunes should contact Apple support.'”
Read more in the full article here.
MacDailyNews Take: “Apple Quality Control.” Going from boast to joke posthaste.
SEE ALSO:
Apple preps fix for 9.7-inch iPad Pros bricked by iOS 9.3.2 – May 18, 2016
Open letter to Tim Cook: Apple needs to do better – January 5, 2015
I love it when MDN tosses rocks at Apple on this issue, when none of their staff has probably written a line of code in their lives, and even if they did, is probably next to nothing in comparison to the complexity of the code in IOS. I am sure that Apple tested it, and like many complex software projects, when released to a wide audience, something else crops up,
Apple would not have released 9.3.2 if they had any idea that it would affect one of their models, and it didn’t affect them all, there was not 100% fail rate.. Once of these days before MDN spouts junk on Apple Quality control, perhaps they need to use some real perspective..
First iOS release after the first pro was released caused the pro to freeze with blank screen after “long” charges. Second pro..first iOS release after second pro is released causes new pro to get bricked. I think pointing this out is more than justified.
Yeah, my grandma was sharing her thoughts with me, she could not believe how Apple’s iPad went from something that worked to something that bricks in less than 7 years. Told her that’s why I am still on iPad 1 (64Gb Wi-Fi+3G iOS 5.1) Best device ever!
I bet that nobody from MDN has built their own Apple hardware either…that means they can’t comment on it? Get real. MDN is right to throw rocks when Apple deserves it and they’re right to gloat by the same measure. Apple software QC has slipped. I wish it weren’t true, but MDN is right. I personally won’t update for at least a week or more after any patch these days. Bricking and other odd issues happen far too often.
I wish there was a way to kill the daily popup that prompts you to update to the latest iOS software. I try to hit remind me later as I don’t want to yet. Whose brilliant idea was that?
All the billions that Apple makes can’t afford enough engineers to improve OS quality control. That’s the biggest joke.
The constant nagging really is incredible. And unwelcome.
As for OS quality control…follow the money. Sad.
That’s how Apple gets those stats of number of people using the latest OS version that they have heretofore been so proud of in the past. I now ignore the messages for a month to wait and see what issues other victims have before I decide to potentially jump in the victim pool.
Imagine how more varied the iOS versions in the wild would be if users could rollback their OS update on encountering slowdown/compatibility problems till it gets fixed.
Should have pulled it before releasing it.
The hardware is so different on the pros..seems strange that Apple wouldn’t just tailor an iOS version that was pro specific instead of just adding code to the general iOS release. This would also avoid the cartoonish look of iOS on the larger pro..iOS, in a way, is holding back the possibilities the pro’s hardware has to offer. Instead, Apple chose to let the hardware on all iOS devices get phased in to match the pro (talking about the screen..which is significantly different).
It is interesting how OSX has now been splintered into many forks for the many different consumer devices Apple now makes. It’s clear that managing and coordinating all those teams is becoming a mess. Also clear to me is that “Pro” doesn’t mean anything in the iOS world. iOS in any of its iterations is not designed at all for professionals; it is designed to drive consumers to rent icloud space and force app sales through the walled garden stores. Nothing wrong with that if you honestly portray the limitations and show that it’s all for consumer convenience. But to pretend that any iOS device is usable for professional business … sorry, that’s just not so. The iPad Pro is an accessory that needs a hell of a lot of backend hardware in order to share anything. Any self-respecting professional would own that backend — keeping his master files on an X-serve, for example. If only Apple actually delivered such professional products, that is.
I have to disagree, to some extent… I use my iPad Pro in a professional setting, and it really does shine. That said, what I use it for is very niche (planning surgery and research at work, ProCreate for art at home).
Perhaps a hypothetical would help…. based on real experience.
Let’s say you’re a surgeon using an iPad Pro. You have a medical image that you’re marking up as part of a surgery plan. Not only is personal medical information proprietary, but the plans you make (and data integrity thereof) can make the difference between life and death. You need to coordinate this plan with your colleague halfway around the world, in a foreign country, who uses non-Apple hardware. The medical device you will be implanting as part of a study is highly proprietary and cannot be shared with any 3rd party.
How do you share a file from the iPad Pro with a colleague in a way that you guarantee:
1) complete privacy
2) secure backup accessible only by the file creator or authorized employee
3) protection against middle man interception
4) interoperability with non-iOS software & hardware
The iCloud user agreement tells you all you need to know about how inappropriate it is to store any critical information of any kind. You need other computers to manage the data, encrypt the data, and transmit it to your colleague.
Hospitals do this by carrying massive IT overhead, with servers and software from non-Apple vendors because Apple won’t serve them. iCloud is a non-starter because it fails on all 4 criteria above. What did the iPad do you you? It just became another screen to secure and manage, and perhaps allowed a bit more flexibility for the user who prefers that form factor. That’s it.
So if you’re an artist, then great, the big iPad is wonderful. Consumers who can afford it think it’s really neat too. Ultraportability does have its attractions. It just doesn’t trump the realities of professional computing. iOS just fails as a practical platform for professional use because it was never designed to serve pros. Moreover, if you need precision input, Wacom + a Mac is your better choice as well.
The fact that Apple doesn’t see the huge needs of important industries like ours is proof positive that Cook is making Apple less relevent to pros. He’s just catering to consumers now.
Lol, you are overthinking this a bit. I actually use procreate in the or. Send png files over airdrop, then scetch on the image during surgery (I’m not the surgeon). I export the image back to png, and do the rest on my Mac for presentation.
Our IT department has fully integrated iOS, btw.
Just the start of iOS fragmentation at the same version number?
…Eventually, we’ll learn what’s causing the bricking ‘a few’ 9.7″-inch iPad Pros. Let’s save up our ammo for bombing Apple until then. For now, the cause of the problem is undefined. I think we have the patience to wait.
But has Apple pulled boners like this before? Oh hell yes. Apple is never perfect. And no, boners like this have no correlation with Steve Jobs being dead. This is a repeated issue throughout Apple’s history, and for that matter Windows PCs as well.
Good perspective there, Derek. Thanks for the reminder.
Yeah, I’d really like to know what causes some specific iPad Pro 9.7″ devices to get bricked with this update. Mine updated just fine, so what’s different about mine?
I suspect that the number of devices affected isn’t as large as the noise level makes it sound. But, bricking is mission critical and deserves immediate attention. There must be some hardware compatibility issue that the iOS update hits for parts from a particular supplier.
I just took the risk and updated my 12″ iPad Pro without incident. I can’t join in the drama.
Error 56 is supposed to be hardware based.
I remember when Apple had a batch of motherboards (*DURING THE JOBS ERA*) that had leaking capacitors causing the motherboards to FAIL. It wasn’t all motherboards. It wasn’t all capacitors. And it wasn’t just Apple that suffered.
Capacitor plague
These problems, believe it or not, are what a CEO must try and prevent. This damages the brand. No matter how many trees Tim hugs or how many or which bathroom people enter, these kinds of errors hurt Apple sales. Is it really necessary to know so much about the CEO’s personal life in order to sell a product?
Sometimes simplicity is all that’s needed, but building simplicity is often extremely hard. Apple doesn’t need a cheerleader. The products and service should speak to the public and say, “we just work and work well”. I see nothing wrong with adding, “we work well with others too”.
These kinds or problems seem to be happening a lot of late.
Hm.
Those of you that look to blame diversity, come on, they just started to implement a diversity program.
A primary job of the CEO is to be the company’s cheerleader. He/she sets the image for the company. His VPs are the day to day operational bosses. The CEO sets the vision, resolves the internal leadership conflicts, and seeks out relationships with other companies and countries to grow the business.
And yes, the CEO needs to take the lead when a portion of the company fails to meet its performance objectives. Scott Forstall’s departure demonstrated how TIm has the fortitude to make such decisions, and I applaud him for it. I’m sure the latest obvious internal conflicts that are affecting performance are being addressed. Apple’s internal structure is very focused on improving and moving forward.
I hold Tim Cook responsible for this disaster.
The man is simply not interested in software quality.
Cook came from Compaq. What do you expect?
He’s an inventory manager who’s got his current job because a visionary genius got cancer and died. Yet, Steve Ballmer is still with us, alive and kicking. God is a cruel jokester.
Well somebody needs to be fired. One of their previous releases virtually bricked my 2nd generation mini. Apple have no excuses. They own all the hardware and all the software. We pay a premium for this kind of thing NEVER to happen.
Dear Birdbrain: As I noted above, Error 56 is listed as a HARDWARE error. You could have bothered to look it up yourself.
Dummies like you are simply not interested in reality. You only want something to hate.
Apple should issue an apology, too.
Total agreement there!