The most recent programming redesign for iPhone 6 handsets is supposedly rendering the gadgets pointless in the event that it recognizes repairs not did by Apple.
The issue is known as "blunder 53" and hashttp://miarroba.com/mehndidesigns showed up in Apple items some time recently.
The Guardian reports that clients' telephones were handicapped after the Touch ID home catch was repaired by a non-Apple engineer.
The issue seems to emerge once gadgets have been overhauled to the most recent working framework, iOS 9.
In its report, the Guardian refers to the encounters of an independent picture taker, Antonio Olmos, who says the issue happened on his telephone after he redesigned its product.
"Whenever Olmos, who says he has burned through a great many pounds on Apple items throughout the years, took it to an Apple store in London, staff let him know there was nothing they could do, and that his telephone was currently garbage," the paper notes.
Photographs "hopeless"
Numerous iPhone 6 clients have been examining blunder 53 on the web.
At Apple's exchange discussions, one client named wallihall composed: "With this upgrade I can't utilize the telephone, and still need to pay for the telephone itself.
"I did get the front screen supplanted, and I comprehend that it's presently considered "messed with", however at any rate let me utilize my iPhone on the old IOS framework... I can't recover old photographs or imperative reports I once had."
Apple told the paper that iPhone programming checks whether any repairs were approved by Apple.
A representative said: "When an iPhone is http://mehndidesigns.blogcindario.com/2016/01/00002-mehndi-designs-animals-henna-tattoo-designs-for-people-of-all-ages.htmloverhauled by an unapproved repair supplier, broken screens or other invalid segments that influence the touch ID sensor could bring about the check to fall flat if the blending can't be accepted.
"With an ensuing overhaul or restore, extra security checks result in a 'mistake 53' being shown."
Apple has prompted clients confronting the issue to contact Apple support.
No comments:
Post a Comment