Arjunthebuster

Q: iphone 6 error 53 and APPLE WONT REPLACE OR FIX!

I purchased my Apple iphone 6 on januray 10th, 2015 in Dubai. i dropped my iphone in february and the top of the iphone(above the screen) got a minute crack. there wasn't any replacement option in India so i had no other option but to use that iphone and when i tried to update the iphone to iOS9.1 in November 2015 i got an error 53. Apple in india said they cant fix it here and i'll have to send it to dubai. I had to wait a month to send it to dubai and finally did. My warranty expires on january 11th, 2016. When given for service in dubai now, they're telling i'll have to pay 1240 aed to get a new phone because my warranty is void if the iphone is broken. BUT the error hasn't occured because i broke my phone(it was working fine for 10 months). I lost all my data because of this error. i don't want apple to fix my screen or anything! i just want them to fix the error 53 so that i can use my phone but they won't! and i haven't given the iphone for service outside yet! so it's still under warranty. please help me. i can't shed all my earning trying to fix a phone where the fault is on apple. PLEASE HELP. THANK YOU.

iPhone 6, iOS 9.0.2

Posted on Dec 31, 2015 2:25 AM

Close

Q: iphone 6 error 53 and APPLE WONT REPLACE OR FIX!

  • All replies
  • Helpful answers

first Previous Page 9 of 17 last Next
  • by TJBUSMC1973,

    TJBUSMC1973 TJBUSMC1973 Feb 6, 2016 9:58 AM in response to TJBUSMC1973
    Level 5 (7,636 points)
    Feb 6, 2016 9:58 AM in response to TJBUSMC1973

    LOL, what part of that had to be edited?

  • by IdrisSeabright,

    IdrisSeabright IdrisSeabright Feb 6, 2016 10:08 AM in response to TJBUSMC1973
    Level 9 (59,729 points)
    iPhone
    Feb 6, 2016 10:08 AM in response to TJBUSMC1973

    TJBUSMC1973 wrote:

     

    LOL, what part of that had to be edited?

    I suspect it was part of the quote. Probably the part about the people in the profession that Shakespeare recommend getting rid of first thing.

     

    "The first thing we do, let's kill all the lawyers" from Henry VI, Part II?

  • by TJBUSMC1973,

    TJBUSMC1973 TJBUSMC1973 Feb 6, 2016 10:16 AM in response to IdrisSeabright
    Level 5 (7,636 points)
    Feb 6, 2016 10:16 AM in response to IdrisSeabright

    Meg St._Clair wrote:

     

    TJBUSMC1973 wrote:

     

    LOL, what part of that had to be edited?

    I suspect it was part of the quote. Probably the part about the people in the profession that Shakespeare recommend getting rid of first thing.

     

    "The first thing we do, let's kill all the lawyers" from Henry VI, Part II?

     

    Ah, I see that now!  Wisenamed got edited, and the Host did a good followup and edited my quotation of him.  Good work, Host, lol!

  • by ajs42548,

    ajs42548 ajs42548 Feb 6, 2016 1:56 PM in response to Csound1
    Level 1 (0 points)
    Feb 6, 2016 1:56 PM in response to Csound1

    So you're saying that a cracked screen causes error 53? Even further, you're saying that all damage to Iphone 6's will cause error 53? What about all the other first 52 errors?

    Error 53 is a specific error and it only appears after an upgrade.

    Do you really expect us to believe that all problems with the phone will cause an error 53? And that error 53 only comes up after an upgrade? How come the error 53 never appeared on anyone's phone anytime before an upgrade? Any diagnostic technician will tell you that if a problem appears just after an event but never before that, then the event was the cause of the problem, especially when that is the case 100% of the time.

  • by TJBUSMC1973,

    TJBUSMC1973 TJBUSMC1973 Feb 6, 2016 2:03 PM in response to ajs42548
    Level 5 (7,636 points)
    Feb 6, 2016 2:03 PM in response to ajs42548

    ajs42548 wrote:

     

    So you're saying that a cracked screen causes error 53? Even further, you're saying that all damage to Iphone 6's will cause error 53? What about all the other first 52 errors?

    Error 53 is a specific error and it only appears after an upgrade.

    Do you really expect us to believe that all problems with the phone will cause an error 53? And that error 53 only comes up after an upgrade? How come the error 53 never appeared on anyone's phone anytime before an upgrade? Any diagnostic technician will tell you that if a problem appears just after an event but never before that, then the event was the cause of the problem, especially when that is the case 100% of the time.

    Get help with iOS update and restore errors - Apple Support

     

    Actually, error 53 can occur for other reasons.  However, it is a common error when Touch ID is damaged or faulty.  Now, if it's manufacturing defect, then that's within Apple's responsibility.  However, if there's been any unauthorized modifications, then Apple isn't responsible anymore.

     

    This is very simple.  I'm having a difficult time understanding why people don't understand this.

  • by roger_m,

    roger_m roger_m Feb 6, 2016 4:37 PM in response to TJBUSMC1973
    Level 1 (0 points)
    Feb 6, 2016 4:37 PM in response to TJBUSMC1973

    This is more than ridiculous.  A phone which is working fine, can be bricked just by updating to the latest version of iOS, and posters here don't think it's a serious issue?

     

    It wouldn't be so bad if you could revert to the previous vesion of iOS to get the phone working again.  But, you can't.  I understand that an iPhone's warranty will be voided by getting it repaired by a 3rd party repairer, and this is only reasonable.  However the issue is that phones bricked with error 53, were working fine before the update, and would continue to work if they had not been updated.

     

    I personally, don't see anything wrong with people taking thier phones to 3rd party repairers when their warranty has expired.  For example, in my case, the nearest Apple store is 350 miles away.  If I had and iPhone which needed repairs, and I had the choice of sending it away to be fixed, and waiting at least a few days before I got my phone back, or getting it repaired the same day locally, I know I would choose the local repair option.

  • by Philly_Phan,

    Philly_Phan Philly_Phan Feb 6, 2016 4:53 PM in response to roger_m
    Level 6 (13,576 points)
    iPhone
    Feb 6, 2016 4:53 PM in response to roger_m

    If you purchased a used iPhone, wouldn't you want some assurance that the touch-ID security is still intact?

  • by roger_m,

    roger_m roger_m Feb 6, 2016 5:29 PM in response to Philly_Phan
    Level 1 (0 points)
    Feb 6, 2016 5:29 PM in response to Philly_Phan

    I didn't mention used phones in my post.  I'm talking about people who had a phone which was bricked by updating iOS, but was working fine beforehand.

  • by ajs42548,

    ajs42548 ajs42548 Feb 6, 2016 6:14 PM in response to TJBUSMC1973
    Level 1 (0 points)
    Feb 6, 2016 6:14 PM in response to TJBUSMC1973

    I'm having a difficult time understanding why you can't understand that this problem only occurs after an upgrade. I'll repeat this again... When there is a common problem occurring after an event (in this case an upgrade), then the problem was caused by that event, in this case the upgrade. Any and all technicians will tell you to go back to the way the device was before the event, whether it's a hardware or software reversal. If the upgrade never happened then the phones would still be working perfectly. One second before the upgrade = working phone...One second after the upgrade = bricked phone. Diagnosis = upgrade caused the problem. There can be no other conclusion.

  • by KC7GNM,

    KC7GNM KC7GNM Feb 6, 2016 10:22 PM in response to Arjunthebuster
    Level 4 (2,893 points)
    Feb 6, 2016 10:22 PM in response to Arjunthebuster

    Arjunthebuster wrote:

     

    It was under warranty when I claimed and now Since i've paid for and got the new replaced iPhone it has an extended service warranty for 2 or 3 months(Don't remember exactly). If you still want a binary answer then YES the iPhone is still under warranty.

    No it was out of warranty when you cracked the screen. You still do not get it. They will not replace the phone under warranty once you broke it due to your negligence.

  • by KC7GNM,

    KC7GNM KC7GNM Feb 6, 2016 10:39 PM in response to roger_m
    Level 4 (2,893 points)
    Feb 6, 2016 10:39 PM in response to roger_m

    roger_m wrote:

     

    This is more than ridiculous.  A phone which is working fine, can be bricked just by updating to the latest version of iOS, and posters here don't think it's a serious issue?

     

    It wouldn't be so bad if you could revert to the previous vesion of iOS to get the phone working again.  But, you can't.  I understand that an iPhone's warranty will be voided by getting it repaired by a 3rd party repairer, and this is only reasonable.  However the issue is that phones bricked with error 53, were working fine before the update, and would continue to work if they had not been updated.

     

    I personally, don't see anything wrong with people taking thier phones to 3rd party repairers when their warranty has expired.  For example, in my case, the nearest Apple store is 350 miles away.  If I had and iPhone which needed repairs, and I had the choice of sending it away to be fixed, and waiting at least a few days before I got my phone back, or getting it repaired the same day locally, I know I would choose the local repair option.

    You obviously have not read this entire thread. No one has said that. What we have said is that if damage was done to the phone then it is not apple's fault. If someone decided to have a 3rd party fix the phone it voids the warranty. The error 53 comes up with a faulty or counterfeit touch id. If the OP had gotten his phone repaired at an authorized apple store then he would not have had this problem. He chose to ignore the cracked screen. The drop probably caused more damage than just what he could see visually outside the phone. When he updated it came up with an error 53. He then tried to get the warranty to pay for the repair but because he dropped it the warranty was voided. He could have chosen to repair the screen for a cheaper price like some have suggested but he chose to come on here and complain about apple not giving him a free phone.

     

    Next time actually read the thread before you post.

  • by roger_m,

    roger_m roger_m Feb 6, 2016 10:56 PM in response to KC7GNM
    Level 1 (0 points)
    Feb 6, 2016 10:56 PM in response to KC7GNM

    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.

  • by petermac87,

    petermac87 petermac87 Feb 6, 2016 11:44 PM in response to roger_m
    Level 5 (7,402 points)
    Feb 6, 2016 11:44 PM in response to roger_m

    Apple have never supported the downgrading of iOS. Arguing that here is futile. You can tell them at Feedback but good luck with that. It's an old argument and one that Apple has not accommodated to date, and I doubt will.

     

    Cheers

     

    Pete

  • by Arjunthebuster,

    Arjunthebuster Arjunthebuster Feb 6, 2016 11:54 PM in response to KC7GNM
    Level 1 (0 points)
    Feb 6, 2016 11:54 PM in response to KC7GNM

    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???

  • by petermac87,

    petermac87 petermac87 Feb 7, 2016 12:03 AM in response to Arjunthebuster
    Level 5 (7,402 points)
    Feb 7, 2016 12:03 AM in response to Arjunthebuster

    Arjunthebuster wrote:

     

    Isn't that clear enough to see that the iOS update caused the issue and not the hairline crack from months before???

    Not really. Who's to say the touch ID mechanism wasn't damaged somewhat with the drop.

     

    Cheers

     

    Pete

first Previous Page 9 of 17 last Next