Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've read a report saying that should work if you have a version of iTunes older than 12.4.
Rolling back to 9.3.1 did not work. Still get the same error. I tried on iTunes 12.3. Still looking for a solution that does not involve sending the brick back to the repair center.
 
Rolling back to 9.3.1 did not work. Still get the same error. I tried on iTunes 12.3. Still looking for a solution that does not involve sending the brick back to the repair center.
Good to know. I won't try that then. I'm sure Apple will release a fix (an updated 9.3.2 or a 9.3.3) in a few yours.
 
I keep on seeing OTA mentioned in relation to this problem.
Does this mean that updating from iTunes is fine?
 
Last edited:
If you have an install base as big as Apple, it is absolutely inevitable to make any software issues, their suspected causes and potential workarounds openly available to the public eye, even if Apple are still in the process of "investigating the issue".

EVERY reputable software company who has understood his responsibility, in regards to his install base, does this.
 
I spent $1000 on a new iPad Pro 9.7 for my daughter who needs something for school. I convinced her to stay away from the macbook retina and go with the iPad Pro and keyboard. I told her today to update her new iPad for security reasons. IT WAS BRICKED. She is crying! She has a big test this week and her new laptop 'replacement' is BRICKED! She said, 'I told you dad never update!' from a 13 year old. Apple...WTF?!


Haha Apple made you look quite the fool in front of your child. She'll never look at you in the same way, fatherly respect evaporated. Will take a lot of work to get that back.

Who am I kidding, I have this niggle feeling Apple is making monkeys out of all of use for some time now. And yet we all keep coming back with 'please sir, may I have some more'
 
My iPad is also impacted. I did the OTA update and now getting the error. I tried restoring via iTunes, and got error 56. I tried rolling back to the previous version, and also got the same error. I hope they release a fix soon, as this is(was) my most used device.

In the past, I have usually waited a couple of weeks to update. The one time I don't wait.... *sigh*
 
Do we have to wait until the working day starts in California for this to get fixed?
 
Having used Apple stuff for over 10 years now, my current update cycle is as follows:

a) Update comes out - rejoice & read of what's new;
b) D3 after update release - check for any issues and, if anything is bricked, wait for a fix & back to step a);
c) D7 after update release - update, by which time Apple servers usually get less overwhelmed anyway.

The OSs get more & more complex, as for the Betas - the current iPad bug must have gotten in just before the public release, as their build numbers differ.
 
True however it looks really really bad when it is your new just released top of the line Pro. That I would have thought would have been one of the items over-tested.

That is a good point. Maybe because recent problems were with older devices they focus on those and neglected the newer one. In any case, it does look bad. I am not trying to justified it or make excuses for them. I've troubleshoot electronic hardware on production lines and finding root cause for problems can sometime be straight forward but sometimes it is like playing detective.
 
  • Like
Reactions: dk001
Thank you all for the warning. I turned off the wifi and shut down my iPP before getting the update notice. Good thing I have my rMBP and never considered the iPP anything but a music and video player for time on the treadmill. I agree with the 13 year-old daughter in comment #295: "I told you dad, never update"

There was a time when your could always rely on Apple to give you worthwhile updates. Those days are clearly over. Whatever Tim Cook has done to the tech staff, he'd better undo it yesterday or he will not only lose the loyal base, but word of mouth converts.
 
Anyone can post here and without any journalist validation the door is wide open to draw conclusions as long as it's accompanied with appropriately vague verbs like suggests." This author's style drives me crazy.

You dont see this article as a service to iPad Pro users? Considering there seem to be quite a few people in this thread alone who have bricked their devices, I think this article could save many others the temporary grief of being without their devices while Apple fixes this. Even if it ends up only 0.1% of users are effected, why would you care if MR report it based on speculation and *gasp* rumour?

Or are you referring to other posts on MR? No one has suggested this place is some journalistic highground, but some just cant seem to accept that Apple can make errors and get their panties in a twist when it happens.
 
  • Like
Reactions: Dave Walker
I am holding off on 9.3.1 with my Pro, I use it for quite a bit and do not have time currently to run to the Apple store and wait for someone to try and fix the issue. I'll give it a week.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.