When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I will do the 2 resets in the morning. I am using an Apple cert lightning cable.
Regrettably, I believe it’s the hub as well
. I ordered from an eBay retailer, first one arrived, it illuminated when installed but did not connect nor even supply power to any device, I deemed it defective got sent a replacement with better results, it connects but and here I am still without CarPlay. Visually on screen it seems exactly like what I replaced.
Both of the new units have a sticker label that I have seen in all the videos with that HC3Z-19A387-B part number.
Both came in unmarked unsealed packages.
I understand your frustration. I helped someone locally with the exact same issue before and when we both thought it was the USB hub, he disconnected his truck battery for a few minutes expecting absolutely nothing to change and we both laughed when CarPlay started working immediately afterwards.
As a last ditch approach, try that.
The other thing which I doubt is your issue is that the USB hub must be connected to the left (black) USB port on the back of your Sync 3 assembly. It would be near impossible for Ford to connect the correct harness to the incorrect USB port given that the ports have keyed plastic nubs, but you said you bought your truck used so I can rule that out until you look at it. Maybe someone installed Sync 3 into your truck and did it wrong.
The black port on the backside of Sync 3 is power and data while the grey port is power only.
Last edited by Airborne_Ape; 04-19-2018 at 10:32 PM.
I understand your frustration. I helped someone locally with the exact same issue before and when we both thought it was the USB hub, he disconnected his truck battery for a few minutes expecting absolutely nothing to change and we both laughed when CarPlay started working immediately afterwards.
As a last ditch approach, try that.
The other thing which I doubt is your issue is that the USB hub must be connected to the left (black) USB port on the back of your Sync 3 assembly. It would be near impossible for Ford to connect the correct harness to the incorrect USB port given that the ports have keyed plastic nubs, but you said you bought your truck used so I can rule that out until you look at it. Maybe someone installed Sync 3 into your truck and did it wrong.
The black port on the backside of Sync 3 is power and data while the grey port is power only.
I'm not 100% sure but i think you can't physically connect the black plug to the gray port, unless you broke some plastic things.
So I just tried the master reset and hard reset, clearing all previous bluetooth pairings from truck and phone, to not luck. Going to do battery disconnect next, after that im just ordering a new USB hub from reputable source, anyone have best recommendations, searching the part renders mostly ebays with a few other ecommerce results. Some screen shots to show what im working with if anyone spots anything.
Anyone know if the 18039 release fixes the center screen dimming issue? Also, anyone have any hint about the file? I tried to download it with the previous paths that have worked, but I get a blob missing error.
Anyone know if the 18039 release fixes the center screen dimming issue? Also, anyone have any hint about the file? I tried to download it with the previous paths that have worked, but I get a blob missing error.
Thanks in advance.
they changed the lib related to the ilklumination, and imho it's it works better now.
The package is still on the blob storage, so you are typing a wrong a name.
I will no provide the link (even if it's public and there shouldn't be any problem in doing that) but the correct name is JR3T-14G381-AM_117055.tar.gz so append this to the http address you have and you should find it.
Yeah, some users (included me) noticed a stuttering transition. Actually, it seems to be random.... someone never noticed this, someone have this issue since 2.3 firmware.... i can confirm that (at least for me) the 18093 fixed this issue.
04-19-2018, 10:17 PM
