iphone 6 error 53 and APPLE WONT REPLACE OR FIX!

roger_m wrote:

Actually, I did read before posting. The phone was working fine before being updated, and if there was a way to revert back to an older version of iOS the original poster would have been able to get their phone to work again, without the need to for it to be repaired.

No the phone was not fine before updating. He dropped it and cracked the screen, possibly breaking the touch ID in the process. It was broke from that moment on and was not a complete working phone.

Arjunthebuster wrote:

Hey, I think it's you Who should read the thread properly! I got the phone in January 2015 alright! I dropped it around february And I guess it was iOS 8 back then and there had been several software updates after that and all of them updated properly! i didn't get any error 53s! Only after the update From iOS 9.0.2 to iOS 9.1 my phone got bricked! Isn't that clear enough to see that the iOS update caused the issue and not the hairline crack from months before???

NO YOU DROPPING YOUR PHONE CAUSED THE ISSUE. WHAT PART OF THAT DO YOU NOT GET. JUST BECAUSE YOU THOUGHT THE PHONE WAS WORKING PROPERLY IT WASN'T AFTER YOU DROPPED IT. IT HAD DAMAGE THAT YOU COULD NOT SEE.

KC7GNM wrote:

No the phone was not fine before updating. He dropped it and cracked the screen, possibly breaking the touch ID in the process. It was broke from that moment on and was not a complete working phone.

Maybe it was not a "complete working phone," but it was working, and he was able to use it. If the Touch ID was broken, it did not matter, since he was still able to use his phone until he updated it.

roger_m wrote:

KC7GNM wrote:

No the phone was not fine before updating. He dropped it and cracked the screen, possibly breaking the touch ID in the process. It was broke from that moment on and was not a complete working phone.

Maybe it was not a "complete working phone," but it was working, and he was able to use it. If the Touch ID was broken, it did not matter, since he was still able to use his phone until he updated it.

And again you are not listening or reading correctly. The phone was broken the moment he dropped it. If he had restored the phone to his previous iOS he would have got the same thing. Pointless trying to tell you anything because you keep spouting the same old stuff that most of us here have already disproved.

KC7GNM wrote:

And again you are not listening or reading correctly. The phone was broken the moment he dropped it.

The phone may have been "broken" but it was still working, until the update killed it. Or to put it anotherwy, if he had chosen not tp update his phone, it would proabably still be working now.

roger_m wrote:

KC7GNM wrote:

And again you are not listening or reading correctly. The phone was broken the moment he dropped it.

The phone may have been "broken" but it was still working, until the update killed it. Or to put it anotherwy, if he had chosen not tp update his phone, it would proabably still be working now.

Yes but he chose to upgrade a broken phone. A phone he should have had assessed properly straight after the drop. End of story.

Pete

petermac87 wrote:

Yes but he chose to upgrade a broken phone. A phone he should have had assessed properly straight after the drop. End of story.

Pete

He had no need to assess anything, as his phone was still working. To suggest otherwise is just ridiculous, and completely unreasonable.

He did know (and there is no reason he should have known) that updating his phone would destroy his working phone.

End of story.

roger_m wrote:

petermac87 wrote:

Yes but he chose to upgrade a broken phone. A phone he should have had assessed properly straight after the drop. End of story.

Pete

He had no need to assess anything, as his phone was still working. To suggest otherwise is just ridiculous, and completely unreasonable.

He did know (and there is no reason he should have known) that updating his phone would destroy his working phone.

End of story.

Then you stick with your opinion and others can stick by theirs. Pretty useless arguing it here in user to user forums and expecting action, but rant away. Just stay within the Terms Of Use that you agreed to (yes you did) when you joined these forums so you don't get yourself banned.

Cheers

Pete

http://www.forbes.com/sites/ewanspence/2016/02/06/what-caused-iphone-error-53/#6 d2f4a66e297

Looks like Forbes may have seen motivation behind Apple bricking these phones.

seems error 53 made a debut the same week as trade in your broken iPhone

http://www.forbes.com/sites/amitchowdhry/2016/02/05/do-you-have-a-broken-iphone- apple-will-let-you-trade-it-in-for-credi…

petermac87 wrote:

Pretty useless arguing it here in user to user forums and expecting action,

I'm not expecting action. However I am totally dumbfounded as to how any of the posters here can see that bricking a working phone is not a serious issue, and Apple should be held accountable.

roger_m wrote:

petermac87 wrote:

Pretty useless arguing it here in user to user forums and expecting action,

I'm not expecting action. However I am totally dumbfounded as to how any of the posters here can see that bricking a working phone is not a serious issue, and Apple should be held accountable.

As I said, you are entitled to your opinion.

Pete

And what if you didn't want to have your screen repaired because the damage was only minor, and it was otherwise working fine (in this case for 10 months)?

Indeed, imagine putting a ding in your car. An ugly scratch, but you can still drive home. And you can still drive to work and back home every day for the best part of a year. Now it's service time - you drop it into your local dealer to get a routine service, but when you go back later that day to pick it up they won't give it back to you because it's got the 10-month-old ding in the bodywork. So now you're unexpectedly without your car and its contents until you replace all the bodywork with new panels.

Yeah, sounds fair alright.

You're also spouting the same old stuff. We all know the phone wasn't 100% working, but it was 99% working and now it's 0% working after an update. It shouldn't be up to Apple to decide whether we want to continue using a phone that might be damaged but still working well enough for our needs. We should be allowed to decide that.

There are plenty of things I own that don't work 100%, but I'm happy with them as they are:

The rear window washer on my car doesn't work (and hasn't done for years) - does that mean I shouldn't be allowed to use my car?

There's a bulb gone in my bathroom - does that mean I shouldn't be allowed to use my bathroom? Or my apartment for that matter?

The battery in my 1st gen MBP isn't working - does that mean I should be denied access to the data on it? And what if I replace it with a 3rd party battery? Should I still be allowed to use it then?

My PC laptop has a crack in the case plastic and a missing key on the keyboard - does that mean I shouldn't be allowed to use it?

There's no point in posting Forbes links. Forbes will not allow you to access the site if you have an ad blocker installed, in spite of the fact that Forbes has been known to present ads that contain malware.