iPhone restore error 53 - not listed anywhere, what is the problem? has anyone seen it before???
has anyone come accross restore error 53 on an iPhone 6???
iPhone 6
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
💡 Did you know?
⏺ If you can't accept iCloud Terms and Conditions... Learn more >
⏺ If you don't see your iCloud notes in the Notes app... Learn more >
⏺ If you can't accept iCloud Terms and Conditions... Learn more >
⏺ If you don't see your iCloud notes in the Notes app... Learn more >
has anyone come accross restore error 53 on an iPhone 6???
iPhone 6
Hi, poppyseed83.
Thank you for visiting Apple Support Communities.
I would recommend going through the steps in the article below.
Resolve iOS update and restore errors in iTunes
http://support.apple.com/kb/TS1275
Cheers,
Jason H.
If you see an error 53 message in iTunes and “Connect to iTunes” on your iOS device, use the steps in this article to restore and recover your device using iOS 9.2.1 and iTunes on your Mac or PC.
Apple has just released an official fix for Error 53.
Perhaps my sentiment of a week ago or so (that I would not buy an iPhone 6), which generated so much complaining by people with huge numbers of posts, in its small way helped to prod Apple into fixing this.
Glad to see apple have back tracked on this one, they were clearly in the wrong.
So much for the isheep and there claims that Apple were right.
Well, I guess the threat of a massive lawsuit has changed everything.
Apple says sorry for iPhone Error 53 and issues iOS 9.2.1 update to fix it
But it is sad that that is what it took. So, now let us see how quickly and adroitly all of you who defended this outrageous behavior on the part of Apple can now change your viewpoints to mesh with the new reality. If any of you actually suffered a broken phone from this debacle, you should do the honorable thing, stand by your statements and NOT take Apple up on its offer to refund repairs and replacements.
bobfromlosangeles wrote:
Well, I guess the threat of a massive lawsuit has changed everything.
What "massive lawsuit?" Every large company gets threats of lawsuits daily. It's a long way (and a long time) from someone saying they are going to sue, and anything actually happening. Most of them just disappear, and the one in a hundred (or maybe a thousand) that actually get to court take years. And contrary to what you might like to believe, the only ones who benefit from a class action suit are lawyers. I was once cheated out of $4,000 by a crooked stockbroker (back when that was a lot of money). After 7 years in the courts I got $83. The lawyers who brought the case got $50 Million. I was also party to a suit against AT&T. I got a 50 cent credit on my bill.
What really happened is that Apple investigated the issue, discovered it was a software error, and fixed it because it was the right thing to do.
Whatever the reason why they looked into the matter, it took an awful long time before coming up with a solution. This thread started in September 2014.
It just doesn't look good from Apple's side. But also from the support community. Go to Samsung or LG is never a good solution.
Seriously, the phrase came about for very good reason and is so widely used for the same reason. People who drink the Kool-Aid are indeed unquestioningly obediant. The shoe and the phrase fit.
<Edited by Host>
bobfromlosangeles wrote:
People who drink the Kool-Aid are indeed unquestioningly obediant.
So you think that your imagined issues with an iPhone equate to an incident involving nearly a thousand deaths?
<Edited by Host>
Care to tell us now what that reason might be? Totally unrelated to maintaining security as has now been completely proven by Apple. So, what does that leave as a valid reason now?
bobfromlosangeles wrote:
...but you didn't.
And you know that how?
By the way, I happen to agree that your comparison with 1000 deaths is offensive. Your opinions carry no weight.
Nothing wrong with my speling. Ants which follow without analysis or question are obediants.
bobfromlosangeles wrote:
Nothing wrong with my speling.
I want to personally thank you for my first chuckle of the day.
See, I don't think you understand that this is not Twitter or Facebook. So posting things just to be offensive is a) against the TOU, b) not a technical question or a request for help from fellow users, b) offensive.
Apple did what Apple did. We have no control over any of it, and it is also against the TOU for us to speculate about the what and the why.
So, maybe you could just stop being so insulting. I've not seen anything but insults posted by you in this thread, so if that is your sole purpose here, let us know so we can alert the hosts.
GB
Apple released a new version of iOS 9.2.1 today (Feb 20) or yesterday (Feb 19). This was supposed to fix that problem error message and allow you access to your phone again. I think it will disable the ability to use your fingerprint as they have detected a security breach. you will have to use your passcode from now on or take the phone to an Apple store and have the button replaced. I don't know why they did not call it 9.2.2 or 9.3.0 or something different from the same version already installed. It cannot be installed from the phone itself, you must do it from your desktop with the phone connected. around 2.2 gig on iPhone 6S+ and 2.0 gig on iPhone 6+.
iPhone restore error 53 - not listed anywhere, what is the problem? has anyone seen it before???