Unsure of which Part # to order

Hi amazing people,

I have a 2016 Mustang GT Premium with Sync 3 from factory. It’s currently at Version 1.0.15139.
I am aware I need to get my Sync 3 to V 3.0 for this part to work.
My only objective is CarPlay, nothing more. On this site I saw a post that showed what I need but I still don’t understand which part I need. (Sorry)

""HU5Z-19A387-*
HU5Z-19A387-A (BLUE BACKLIGHTING) Ford (Wide 1 USB-A Port, w/Pass Through)
HU5Z-19A387-B (BLUE BACKLIGHTING) Ford (Wide 1 USB-A Port, w/Pass Through)
HU5Z-19A387-C (BLUE BACKLIGHTING) Ford (Wide 1 USB-A Port, w/Pass Through)
Interchange Part Number:
HU5T-14F014-AA, HU5T-14F014-AB, HU5T-14F014-AC, HU5T-14F014-AD, HU5Z-14F014-BB
2016-2019 Ford Mustang
2016-2019 Ford Focus
2016-2019 Ford Explorer
2016-2017 Ford Transit

Based on that info found on this very site, which Part number is needed for CarPlay for my 2016 Mustang GT Premium?
Is it HU5Z-19A387-*A, B, or C?


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 1.0.15139

New SYNC Version: 1.0.15139

Do you have a error message, if so what is it?

Update Method: Official Ford

I’m going to make a guess without having a pic that you have one USB port forward and one in the console?
This is what Ford parts gives me for a 2016 Mustang - HU5Z-19A387-C

That is correct, I have one up forward and one in the center console. I figured as much but I just wanted to confirm. I purchased that part HU5Z-19A387-C, hoping it works. Thanks for letting me know. Any advice updating my sync 3 from version 1.0 to 3.0? Some YouTube videos show its possible, but people one here say you need to first upgrade version 2.2 before going to 3.0. Any advice?

There’s a change that enabled Car Play correctly around 2.2.16171.
Take it to that first, then use the update available from owner.ford.com for your VIN
H3BT-14G381-LC - SYNC 3 APIM Software (IVSU) Database - CyanLabs

Format a good USB (eg San Disk, PNY, Lexar) as exFat.
Make a folder on it called SyncMyRide
Download the autoinstall to the root of the drive
Download the IVSU (H3BT-14G381-LC_57565.tar.gz) to the SyncMyRide folder.
Perform an eject on the USB, you’ve now got a 2.2.16171 app install USB

When you do the install make sure nothing else is plugged into the other USB, not even a charge cable, take the car for a short drive while it runs, normally takes about 20 minutes.

If I could hug you right now, just know I would. I have a 128gb Sandisk 3.0 formatted to ExFat. Please pardon my low iq but two questions now

  1. Does “the root of the drive” just mean directly to the USB outside of any folders? Or is this something techy I have to do differently?

  2. Do I extract the (IVSU) zipped file and leave the extracted files in SyncMyRide folder?

I just really want to do this right

To the root is outside of any folder.
You don’t extract, just drop the IVSU directly into the folder

Let us know if you have any more questions or problems.

Not to doubt you, but before I go an attempt this 2.2 update tomorrow? Are you sure this is for the 2016 Mustang GT with NAV / Sync 3 v1.0?
I’m seeing a Moderator “SandMan” and another forum showing different IVSU links to get 2.2. Just want to make sure is all

2.2.17011 another user found success with this version and has the same vehicle as me. The one you linked is different is all. I copied it below for reference

HN1T-14G381-SA
Type: APPS
Version: 2.2.17011
Regions: ALL
FileSize: 460.01 MB
Source:
Nav Type: all
Notes: 11.01.2017
Filename: HN1T-14G381-SA_64817.tar.gz

@SaNdMaN May I ask you what IVSU you would recommend for the 2.2 intermediate step? The one Warlock is saying or this one 2.2.17011?
I have a 2016 Mustang GT Premium just wanting CarPlay (Usb hub on the way ordered)

I’ve been recommending 2.2.17011 and it has worked fine until now… That does not mean another 2.2.xxxxx would not work, but I would stick with what’s been used so far…

You can always try another build to see if it works, and if not, you can go to 2.2.17011…

1 Like

Ok will do , going to try it later today. Thanks guys

Process is the same, the biggest thing is to do the 2.2.x stop along the way from 1.x to 3.x

You can check to see if CP works after getting to 2.2.x before making the update to 3.x

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.