Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

AJsAWiz

macrumors 68040
Original poster
Jun 28, 2007
3,259
346
Ohio
Just installed IOS 8.1.2 and was disappointed to see that my iPhone 5S no longer supports the third party cable I used for charging my phone before the update. :eek: When I plug it in I get the old "not supported" message and it will not charge at all. This is the exact same cable I used to charge my iPhone 5s before the update.

Anyone else having this problem?
 

AJsAWiz

macrumors 68040
Original poster
Jun 28, 2007
3,259
346
Ohio
Update

Yeah, I'm not gonna do that. :confused:

The cable I used before which is not working now was a Belkin. I tried another third party cable (Griffin, I believe) and it works. So, that leads me to believe that my Belkin cable just went bad and that the issue is not related to my IOS 8.1.2 update. Perhaps the timing was just coincidental. I can't recall having an issue with third party cables (and yes, I use the original Apple cable too) before. The main reason why I sometimes use third party cables is that they are available in a longer length than the Apple cables.
 

flyinmac

macrumors 68040
Sep 2, 2006
3,579
2,463
United States
To be permitted to operate without the warning message, the cables need to contain a chip licensed from Apple. It's a moneymaking scheme.

If your cable worked fine with 8.1.1 then it would presumably have had the proper license. As I had cables flagged with 7.0. So most likely the cable failing to pass authentication now is about something in Apple's update.

And by the way, I've even had my genuine Apple cable that came with my phone stop authorizing after certain updates and then resume passing authorization in later updates.

It's just Apple's unnecessary money making scheme tripping you up. You can buy a high-end properly licensed cable and Apple will deactivate it later.
 

AJsAWiz

macrumors 68040
Original poster
Jun 28, 2007
3,259
346
Ohio
To be permitted to operate without the warning message, the cables need to contain a chip licensed from Apple. It's a moneymaking scheme.

If your cable worked fine with 8.1.1 then it would presumably have had the proper license. As I had cables flagged with 7.0. So most likely the cable failing to pass authentication now is about something in Apple's update.

And by the way, I've even had my genuine Apple cable that came with my phone stop authorizing after certain updates and then resume passing authorization in later updates.

It's just Apple's unnecessary money making scheme tripping you up. You can buy a high-end properly licensed cable and Apple will deactivate it later.

Good point! I was just about to toss it but now I'll keep it and see if it works later. Thanks!

----------

We've been using only Apple or MFI-certified cables for several months now. All work with 8.1.2.

I believe you are right. I just checked with someone else who was using a third party cable and it still works after the 8.1.2 update.
 

fnegrin

macrumors newbie
Oct 11, 2014
8
0
I have the same issue. I use a third party hdmi adaptor cable to watch my ipad 3 content on my tv and it was working fine until this morning, then I updated to 8.1.2 and the cable is no longer working now. Several internet forums are discussing this issue byvthe way, so it is a real issue
 

iBreatheApple

macrumors 68030
Sep 3, 2011
2,889
828
Florida
To be permitted to operate without the warning message, the cables need to contain a chip licensed from Apple. It's a moneymaking scheme.

In my opinion, yes and no. Yes because... well that's obvious. But moreso no, because I think it's more of a 'we don't want to hear about (or be responsible for) any third party issues, charging problems, fried batteries, et cetera' type thing.
 

AJsAWiz

macrumors 68040
Original poster
Jun 28, 2007
3,259
346
Ohio
I have the same issue. I use a third party hdmi adaptor cable to watch my ipad 3 content on my tv and it was working fine until this morning, then I updated to 8.1.2 and the cable is no longer working now. Several internet forums are discussing this issue byvthe way, so it is a real issue

Not sure what's going on. My other third party cables work fine. Thinking that the cable was bad I was going to dispose of it. However, on second thought, I decided to hold on to it to see if it works with later IOS updates.
 

fnegrin

macrumors newbie
Oct 11, 2014
8
0
It clearly will not. That particular cable simply does not give your device the info the new iOS is now requiring , while your other cables do. Different brands, different criteria etc etc Newer updates of iOS will get fusdier, not more liberal with non apple products!!!
 

sanke1

macrumors 65816
Nov 9, 2010
1,067
435
Apple blacklists those chips which are hacked or are replicas of original chips through point updates to iOS. Hence suddenly non MFI cables stop syncing or charging.

Apple can also blacklist cables of manufacturers who once had passed MFI certification but tried to violate licensing agreements by selling more number of cables than licensed.

So genuine paying customers loose.

My Belkin MFI cable stopped working suddenly. I also hate original Apple cables as they fray at ends so easily. Maybe Apple does it on purpose so that we end up buying more cables.

Gotta love Apple for their customer friendly policies!
 

iBreatheApple

macrumors 68030
Sep 3, 2011
2,889
828
Florida
And for what it's worth, my cables have since been yielding these incompatibility messages as well. Only sometimes, though...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.