My son had the phone. His was affected. It's just the way he held it kept it from losing signal. Then there's all the people that use cases. What evidence is there that all the phone's weren't affected?
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.
Apple Pulls iOS 9.3.2 Update for 9.7-Inch iPad Pro After Bricking Complaints
- Thread starter MacRumors
- Start date
- Sort by reaction score
My son had the phone. His was affected. It's just the way he held it kept it from losing signal. Then there's all the people that use cases. What evidence is there that all the phone's weren't affected?
Two times in a row an operating systems is pulled, a little embarrassing
I updated my iPad Pro (9.7") without incident before finding out about the problem, thank god. (Note: I'm typing this post on it right now.) Is there any rhyme or reason to what devices are getting hit by the error? Is it for those who update through iTunes vs. over-the-air? Cellular+Wifi vs. Wifi-only? Storage? Or just completely random as far as stuff the user is aware of?
I think the point I was trying to make is that it seems like "this is affecting a small number of users" is the standard apple response regardless of how many users the issues is affecting. This goes back to the days of Steve Jobs "you're holding it wrong" with the iPhone 4 (and probably even before that as well).
Or perhaps because only 0.55% of users were crazy enough to jump on the update immediately.
[doublepost=1463780550][/doublepost]
Yes, that is the standard line. Apple has never come out and said it affects every one of this device made, even when it has been a known manufacturing defect affecting all the devices in a particular product line.
No wonder when they update every Year and now with fragmenting Devices. Why can't they let live an OS and update slower with good testet Software? **** i hate this yearly OS update's, slow down that unneeded 1 Year Cicyle (and then i even can't go back to the old system, they should allow at least 1 Step back, so i won't update my 5s this year, due i know it will slow down the device and then it's ****ed up) I want/need an OS that works proper and stable and is optimized to it's best, which of course, i guess due lack of time, will never happen again. Don't look back, carry on, just program new buggy crap and make functions worse and just focus on new devices....
3 Weeks ago i wanted to install an 10.9.5, just to find out they got now a built in timer in the .dmg files you loaded from the store, so that you can't install after 90 Days or you have to turn back the time, WTF i spent 3 hours to find out about the problem......... Thx Guy's for that super duper Idea.
Absolutly a no go, remember the 1984 Video-Commercial? -> Now in 2016, all the grey guy's must be Apple User's -> and the coloured girl then must be Ubuntu 15.xx LTR.......
And by the Way, the iPad is not post PC, it's just a nice couch playtoy. And muisc runs through Apples DNA,yes yes, then why the hell is the remote App still absolutely crap and why did you turn iTunes in such a beast? In 2001, when i work at a apple retailer, i got a Apple T-Shirt marked "What a wonderful digital world" , 2016 i made my own Shirt: what a ****ed up digital world.
3 Weeks ago i wanted to install an 10.9.5, just to find out they got now a built in timer in the .dmg files you loaded from the store, so that you can't install after 90 Days or you have to turn back the time, WTF i spent 3 hours to find out about the problem......... Thx Guy's for that super duper Idea.
Absolutly a no go, remember the 1984 Video-Commercial? -> Now in 2016, all the grey guy's must be Apple User's -> and the coloured girl then must be Ubuntu 15.xx LTR.......
And by the Way, the iPad is not post PC, it's just a nice couch playtoy. And muisc runs through Apples DNA,yes yes, then why the hell is the remote App still absolutely crap and why did you turn iTunes in such a beast? In 2001, when i work at a apple retailer, i got a Apple T-Shirt marked "What a wonderful digital world" , 2016 i made my own Shirt: what a ****ed up digital world.
Last edited:
I'm not sure if that's used all the time, and I don't think that it is necessrily. But that doesn't mean that plenty of times it isn't in fact true and applicable.
[doublepost=1463781226][/doublepost]
Except there were all kinds of bugs and issues with Steve around as well and I don't recall people being fired or anything in particular happening in relation to it at those times.
Yeah, this problem appears to be bigger than we're being led to believe. I know someone who already had their 9.7" Pro replaced because of this. It's really a shame that these brand new iPad Pros are getting bricked because of Apple's crappy software testing. It might make some people rethink their plans to purchase another Apple product. At the very least, some people (myself included) might from now on wait at least a month to upgrade to new firmware.
It's not about the phones being affected, it's about the users being affected. The phones were all the same (at least the GSM (aka AT&T) versions, the Verizon versions were slightly different), it's the way people held their phones (from hand and finger size and dexterity to personal holding preferences) plus their skin conductivity, plus probably the weather (humidity, temperature) and how good the cell network was in their locations.
I never noticed any particular differences between the iPhone 3G, iPhone 4 or iPhone 5 but I chalk this down to the way I happened to hold my phones.
[doublepost=1463783740][/doublepost]
Define 'crappy'. How many incidences of bricking does it need for you to define testing as crappy? And what meaning would that term actually have if almost every manufacturer were affected?
Wouldn't be the last time either.
No one has mentioned the 12-inch in any of this.... whats unique about the 9.7-inch ipad Pro that is NOT in the 12-inch? I bet Apple will have trouble explaining this one..
Tim Cook: "We have so many innovative things in the pipeline. We are starting with pulling back the updates! Every company push the updates! We are the first one to pull the updates back! It is not an easy thing to do. But in our case, the pull just works!"
It might not be related to just hardware, could be a particular app or combination of apps which cause this as its not affecting every 9.7 pro
So true. As an engineer I can see (having been there way too many times) the frustration when you know that "X" should be performed and management deems the risk level low enough and says "No."
Things I am guessing:
Surely the betas attracted a fair % of the Pro users out there. The bug wasn't found in the betas because it was introduced in the final build.
As has been suggested, it has something to do with the security hardware not trusting the update.
Is the Touch ID/Secure Enclave the same on the two sizes of Pro?
If not then is it possible 2GB of RAM v 4GB has anything to do with it?
Surely the betas attracted a fair % of the Pro users out there. The bug wasn't found in the betas because it was introduced in the final build.
As has been suggested, it has something to do with the security hardware not trusting the update.
Is the Touch ID/Secure Enclave the same on the two sizes of Pro?
If not then is it possible 2GB of RAM v 4GB has anything to do with it?
Windows 10 at LEAST allow enterprise users to disable Windows Update, sort of.
I don't find any method to disable Apple Software update from either a Mac or an iOS device, yet.
[doublepost=1463791892][/doublepost]
Maybe. But it prompts you to update over and over, in a daily basis I suspect.
Apple is doing the same thing Microsoft is attempting to do in Windows 10.
My MacBook Airs & Pro's ranged from $1649 to over $2600. I could have bought some very fancy PC's for 50% less than that...I'm not about to but I had to correct your reply.
Posted this in the original post thread, also putting it here because it is still relevant.
This appears to be related to an attempt to update the firmware of the NFC IC/chip during the update/restore process.
Multiple mentions in the update logs regarding opening and failing serial UART commands on the NFC IC. Oddly (and suspiciously) the logs show the restore/flashing tool for the NFC IC is being told to load firmwares for two different NXP NFC ICs. After the tool fails to flash the NFC IC it triggers the restore to fail with code 56 as I'm guessing a CRC integrity check for the NFC chip fails due to the failed/corrupt flashing of the firmware. The sporadic nature of the failure is confusing, but I'd take a stab at a bad UART clock signal somewhere.
This will likely be resolved by changing the images that the tool is trying to flash to the NFC IC or by being a bit safer with how the serial sessions are opened. It is, however, incredibly annoying.
For the record: 128GB 9.7" WiFi and Cellular model here with the same symptoms.
Some serial functions on the NFC IC that you would expect to be working, are not working after the attempted flashing of the NFC IC. While this shouldn't affect future flashing, it does point towards this being the problem that is occurring. Even getting serial numbers and firmware versions are failing. Doesn't bode enormously well for flashing process Apple uses, but the serial commands used in flashing appear to be unaffected.
This appears to be related to an attempt to update the firmware of the NFC IC/chip during the update/restore process.
Multiple mentions in the update logs regarding opening and failing serial UART commands on the NFC IC. Oddly (and suspiciously) the logs show the restore/flashing tool for the NFC IC is being told to load firmwares for two different NXP NFC ICs. After the tool fails to flash the NFC IC it triggers the restore to fail with code 56 as I'm guessing a CRC integrity check for the NFC chip fails due to the failed/corrupt flashing of the firmware. The sporadic nature of the failure is confusing, but I'd take a stab at a bad UART clock signal somewhere.
This will likely be resolved by changing the images that the tool is trying to flash to the NFC IC or by being a bit safer with how the serial sessions are opened. It is, however, incredibly annoying.
For the record: 128GB 9.7" WiFi and Cellular model here with the same symptoms.
Some serial functions on the NFC IC that you would expect to be working, are not working after the attempted flashing of the NFC IC. While this shouldn't affect future flashing, it does point towards this being the problem that is occurring. Even getting serial numbers and firmware versions are failing. Doesn't bode enormously well for flashing process Apple uses, but the serial commands used in flashing appear to be unaffected.
Me too, except update is getting increasingly forceful. One "wait til later" is not enough anymore. XP anyone?
[doublepost=1463797472][/doublepost]
Very true. The head of QA responsible for all these debacles is still there despite the Apple Maps fiasco and yet Forstall fell on the sword instead.