iphone 6 error 53 and APPLE WONT REPLACE OR FIX!

Fat_Monkey wrote:

Why ask me what Apples motivation is for disabling all these phones when there is alternative options. Possibly that all these people would have to buy a new one? That's just speculation I would suggest you ask them.

You're the one that asked: "If it was a security feature why not completely disable the Touch ID if it had been altered?"

If you want us to speculate, why can't he ask you to speculate?

So, once again: what motivation would Apple have to intentionally disable these iPhones?

You said: So they have to buy a new one?

How ridiculous. Many of Apple's customers automatically purchase a new version as soon as it's announced, even if they have the next most recent version. They don't NEED to 'trick' anyone into buying the new devices. It happens anyways. And when people buy new devices, they tend to sell or give away the old ones if they still work. And that means another person becomes an iPhone user, and usually they create an Apple ID & start spending money in the iTunes & App Store, where Apple makes a very, very significant portion of their profits.

So, if Apple were to actually intentionally attempt to 'run' customers devices just so they would buy the new one, then those users wouldn't have the option to pass along the old device, and Apple misses out on an easy revenue source.

How many parents do you know that have passed down their 'old iPhones' to their kids? And how many of those kids do you think then convinced Mommy & Daddy to let them make some in-app purchases?

Why would Apple intentionally shut off such an easy source of revenue? New users that are using older devices still spend money with Apple.

Apple may be greedy, but they aren't stupid.

Fat_Monkey wrote:

Why ask me what Apples motivation is for disabling all these phones when there is alternative options. Possibly that all these people would have to buy a new one? That's just speculation I would suggest you ask them.

I will do no such thing, it's a pointless question, you should ask it.

Arjunthebuster wrote:

I Wrote that on 2nd January,2016! Tryna act smart huh?

You'll notice that I was replying to Csound1, not to you.

Perhaps you should direct your comment to him?

So you're saying that the phone worked perfectly for a while after the drop but just by coincidence, the phone stopped working after the upgrade but caused by the drop? Even you don't believe that. Gee what a coincidence. And BTW, any and all technicians will tell you that if a device stops working just after something was done to it, then it was that event that caused the device to stop working, not something that happened way before it.

OK let's go with your explanation. If the chip couldn't take the increased heat then the chip was faulty and that means that it wasn't the fault of the owner. It means that it was Apple's responsibility to warn the owners that an update would cause problems due to the increased heat. How was the owner supposed to know this? And in that case IT WAS THE UPDATE THAT CAUSED THE PROBLEM SINCE THE UPDATE CAUSED THE INCREASED HEAT!!!

Ad it's still the update that caused the bricking. If there was no update then the phone would still be working wouldn't it. It was Apple that put in the update code to brick the phone if it was repaired by a 3rd party. No update=working phone.. Update = bricked phone. Now you tell me how it wasn't the update. And keep in mind this wasn't an isolated case. If this happens constantly then it's Apple not the 3rd party repair. repeating what others have stated, if you take a car under warranty to a private repair shop, the warranty is not voided. If you replace a transmission that's a 3rd party transmission then the transmission is not warrantied by the manufacturer but the engine still is.

ajs42548 wrote:

So you're saying that the phone worked perfectly for a while after the drop but just by coincidence, the phone stopped working after the upgrade but caused by the drop? Even you don't believe that. Gee what a coincidence. And BTW, any and all technicians will tell you that if a device stops working just after something was done to it, then it was that event that caused the device to stop working, not something that happened way before it.

Funny. I'm a 'technician' in charge of a lot of equipment, and while that's the first place I would start looking, I've never made the blanket statement that whatever you just did to it is always the cause. And there are enough instances that a past event caused a dormant latent fault and was only revealed later that the fault was present,t hat there's actually something out int he real world to cover that.

It's called a defect warranty. If you TRULY believe that the only cause of a fault is something that JUST happened to a device, then all manufacturer hardware defect warranties can now be 24 hours. Because by your logic, if my television set stops working a week before my 5 year warranty expires, then it cannot possibly be a defect in manufacturing, because I've used it for 5 years since it was manufactured.

Do you realize the horrible and ridiculous precedent you're trying to set here? You're actually proposing to absolve manufacturers of virtually ALL responsibility. A defect can, over time, become worse and finally cause a noticeable problem when it didn't do so before.

By the same token, damage can, over time, become worse and finally cause a noticeable problem when it didn't do so before.

"You buy a set of four snow tires with a warranty. But then you take the car offloading, and the tires get damaged and fail to perform properly. Is the tire manufacturer liable because you used the product in a manner in which it was not intended?"

Yes but if you buy a set of tires and the engine goes, can the manufacturer then tell you that they aren't responsible for the engine because you replaced the tires? That's exactly what happened here.

The ID on the phone was working so it couldn't be the cracked glass. If the cracked glass was the reason the ID stopped working then it wouldn't have worked all that time. It stopped working immediately after the upgrade and not a moment before. I will use my car analogy again. If you crack your windshield and have it repaired by a 3rd party shop, then you go to the dealer and have your ECM updated and the car won't work right after, can the dealer tell you that they aren't responsible because you had the windshield replaced by a 3rd party shop? Car worked before upgrade = all systems are good.. Car doesn't work right after upgrade = upgrade is the problem not the replaced windshield.

And I hold A+ certification as well. Yes there can be latent problems with something that happened in the past but I don't believe in coincidences. Your trying to tell me that the upgrade had nothing to do with the bricking. You're trying to ell me that after all that time of the phone working after it was dropped that it just happened to stop working immediately after the upgrade bu coincidence. You're saying that if the OS was not upgraded that the phone would have Error 53 anyway just at that moment anyway. Do I have that right?

ajs42548 wrote:

OK let's go with your explanation. If the chip couldn't take the increased heat then the chip was faulty and that means that it wasn't the fault of the owner. It means that it was Apple's responsibility to warn the owners that an update would cause problems due to the increased heat. How was the owner supposed to know this? And in that case IT WAS THE UPDATE THAT CAUSED THE PROBLEM SINCE THE UPDATE CAUSED THE INCREASED HEAT!!!

Ad it's still the update that caused the bricking. If there was no update then the phone would still be working wouldn't it. It was Apple that put in the update code to brick the phone if it was repaired by a 3rd party. No update=working phone.. Update = bricked phone. Now you tell me how it wasn't the update. And keep in mind this wasn't an isolated case. If this happens constantly then it's Apple not the 3rd party repair. repeating what others have stated, if you take a car under warranty to a private repair shop, the warranty is not voided. If you replace a transmission that's a 3rd party transmission then the transmission is not warrantied by the manufacturer but the engine still is.

If you report a defect to Apple within your warranty period, and there are no other issues such as damage or abuse, then you're covered. That's the ENTIRE POINT of a defect warranty. "Hey, customer, this product should be just fine, but if it's not, let us know in this time period and we'll take care of it for you."

And the root cause of this issue is the failure of the Touch ID to properly pair up. While part of a normal update is to prompt the Touch ID to pair up, that also is the case if the EXACT SAME OPERATING SYSTEM was reinstalled. All the update/restore does is force the Touch ID to show proper authentication. If it fails to do so, then the error occurs. The iOS checking the Touch ID is a normal security feature. The update wouldn't have caused any problems if the Touch ID hadn't been futzed with. And if there was a problem and the Touch ID was not modified improperly, well guess what... Apple would take care of that under warranty. Amazing.

The update didn't cause it directly. All it did was require the Touch ID to validate itself. Because the Touch ID couldn't do so, the error occurs.

If a cop check's a driver's license, and it turns out that the license is expired, and the cop issues a ticket... who's fault is that? The cop's? All he did was check the license and follow his procedures. Is it the state's fault?

Or is it the driver's fault for not having a valid license on his person?

And finally, in regards to your auto repair example, a car is not an iPhone. You can get authentic legitimate parts for your car at AutoZone, both from the manufacturer or authorized third-parties. However, no one other than Apple has authentic legitimate parts. So the comparison is invalid.

ajs42548 wrote:

"You buy a set of four snow tires with a warranty. But then you take the car offloading, and the tires get damaged and fail to perform properly. Is the tire manufacturer liable because you used the product in a manner in which it was not intended?"

Yes but if you buy a set of tires and the engine goes, can the manufacturer then tell you that they aren't responsible for the engine because you replaced the tires? That's exactly what happened here.

The ID on the phone was working so it couldn't be the cracked glass. If the cracked glass was the reason the ID stopped working then it wouldn't have worked all that time. It stopped working immediately after the upgrade and not a moment before. I will use my car analogy again. If you crack your windshield and have it repaired by a 3rd party shop, then you go to the dealer and have your ECM updated and the car won't work right after, can the dealer tell you that they aren't responsible because you had the windshield replaced by a 3rd party shop? Car worked before upgrade = all systems are good.. Car doesn't work right after upgrade = upgrade is the problem not the replaced windshield.

Sorry, but modifying my example doesn't work. I was specifically talking about whether or to you do something allowed within warranty.

And the rest of your analogy is flawed from a basic level. You're operating on a baseless assumption. I've explained how this happened in another post. No going to do it again.

ajs42548 wrote:

And I hold A+ certification as well. Yes there can be latent problems with something that happened in the past but I don't believe in coincidences. Your trying to tell me that the upgrade had nothing to do with the bricking. You're trying to ell me that after all that time of the phone working after it was dropped that it just happened to stop working immediately after the upgrade bu coincidence. You're saying that if the OS was not upgraded that the phone would have Error 53 anyway just at that moment anyway. Do I have that right?

Just read what I wrote:

The root cause of this issue is the failure of the Touch ID to properly pair up. While part of a normal update is to prompt the Touch ID to pair up, that also is the case if the EXACT SAME OPERATING SYSTEM was reinstalled. All the update/restore does is force the Touch ID to show proper authentication. If it fails to do so, then the error occurs. The iOS checking the Touch ID is a normal security feature. The update wouldn't have caused any problems if the Touch ID hadn't been futzed with. And if there was a problem and the Touch ID was not modified improperly, well guess what... Apple would take care of that under warranty. Amazing.

The update didn't cause it directly. All it did was require the Touch ID to validate itself. Because the Touch ID couldn't do so, the error occurs.

If a cop check's a driver's license, and it turns out that the license is expired, and the cop issues a ticket... who's fault is that? The cop's? All he did was check the license and follow his procedures. Is it the state's fault?

Or is it the driver's fault for not having a valid license on his person?

First of all my car analogy is a perfect one. One system has nothing to do with the other.

Secondly, the ID system was not affected by the 3rd party repair. The fact that others had the same Error 53 whenever a 3rd party repair was done to their phone and later exactly after the update happened, shows that it was the update that caused it. If 100 people have a 3rd party repair and all of the phones worked perfectly as before but then get an Error 53 exactly after the upgrade, then guess what, it was the upgrade that was responsible. As a technician you should know that.

Sorry but my analogy is a good one. All phones that stop working immediately after an upgrade months after a 3rd party repair means it's the upgrade. You know that Apple put that Error 53 in there otherwise so many people with a 3rd party repair wouldn't get that exact error.

If it's so good why is it necessary to keep telling us that. if it's perfect wouldn't that be obvious?