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.
These folks will never see your position as reasonable, just as we will not see theirs as compassionate. A free-thinking person might say something like "I probably wouldn't have done it this way, but we are just the sycophants here, we don't drive the bus, we just cheer it on." Instead, you get this almost religious mantra about who is not following the rules and why you should not expect a corporation which could be reasonable, to actually be reasonable. It's a lost cause. And my final words because they do have one point: this is not the place for this. People will vote with their wallets.
Then create your own forum.
It's not a "new policy". It's an error message indicating a critical failure in the touch ID hardware. A restore will fail with an error on any device that returns a hardware failure notification to iTunes when the restore or update is attempted.
Please, take your ranting somewhere else.
bobfromlosangeles wrote:
People will vote with their wallets.
They should have done that when they made the original purchase. These policies are well-known and are nothing new.
I don't disagree that it was an extremely consumer-unfriendly method of going about "protecting" our privacy, and I've not been impressed with the response given by the Apple spokespeople. Too much like listening to the never-ending political garble that we have all been subjected to for almost a year now..... 😐
I also appreciate your very civil response. Thanks for that.
Best,
GB
Facebook and Twitter to name a couple....
GB
Interesting reply to the technical points raised. Quite revealing.
Protecting!?!?!!
My partner works in Africa, Abidjan. Smashed the screen and fixed it in town ... and no: It was not an Apple Store. They don't exist there .... think for fixing the phone, would have been 3 days taken out of the calendar and a trip to Lisbon or Madrid ...
Love the planet, Apple.
This is a new policy, apple released software updates that bricks peoples phones. This is a deliberate act. It is affecting people who have never had a third party repair.
If you think its fine to brick phone that have had a third party repair you are wrong. if you think its fine to brick peoples phones for faults with apples own manufacturing process you are crazy.
Your sense of self entitlement is ponderous.
jakob.joergensen wrote:
Protecting!?!?!!
My partner works in Africa, Abidjan. Smashed the screen and fixed it in town ... and no: It was not an Apple Store. They don't exist there .... think for fixing the phone, would have been 3 days taken out of the calendar and a trip to Lisbon or Madrid ...
Love the planet, Apple.
There is an excellent example of someone that should have purchased a competitive product, one more in line with your partner's needs. It's called "personal responsibility."
It's not a new policy.
That is not a helpful comment.
Telling people 'After' you brick their device that they should have bought a different product is not helpful.
Apple have never said that they would brick your device.
Credit where credit is due. You were right. I did not read the very reasonable alternative you laid out to the handling of this error. And you were right again in splitting hairs on the the security claim. But the words are right there as you stated, so you are right about what you said. I don't know if I can disprove or prove the claim about it being the most secure in the world. Wouldn't even know how to measure that. I don't think it is, but that is purely opinion. The bounty claim, as I said, was one of the more spectacular ones and I dont care if it is true or not given the plethora of other exploits which taken together could get an attacker to where he/she wants to be. But this is besides the point. Your comment that they could have handled this better is a critical one I did not see and for that I apologize. But being lazy, i am not going to go modify the rest of my posts. I will however, drink a glass of my own Kool-Aid. Fowl taste.
Exactly!!
**********
<Edited by Host>
These policies have been in place and widely known for many years. Yes, the whiners should have purchased a different product. It's called "personal responsibility."
iPhone restore error 53 - not listed anywhere, what is the problem? has anyone seen it before???