Sync 1.0.15139 updating to 3.3.19052 NA

Hello all. So I’m trying to update my 2016 ford flex from 1.0.15139 to 3.3.19052 NA. My goal is to get apple car play. I started on the ford website to find no updates are available for my car so I came here. I have seen in other posts that I need to update to version 2.2 first but that file is not listed in the choices in the SYN3 updater. So I downloaded 3.3 to my usb drive successfully. The log is below. I have never done anything like this and a little nervous about trying this. I only have one car and a 19 month old baby so I don’t want to lose the HVAC functions if the APIM gets locked up. I have been an automotive tech for 15 plus years and understand automotive systems in detail but this is my first venture into programing of any kind. I just got this car and it has been beating me to death with repairs big and small so I’m hoping to not have to buy a replacement APIM right now. I also have the updated usb interface module from ford. Any help or guidance would be appreciated!

DESTINATION DETAILS
Mode: Drive
Model: Generic Flash Disk USB Device
Size: 15GB
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
APPS=4U5T-14G381-AN_1552583626000.TAR.GZ
VOICE=4U5T-14G391-CJ_1552513842000.TAR.GZ
GRACENOTES=4U5T-14G423-CA_123766.tar.gz

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - reformat Mode - Sync 3.3.19052 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz
Open2 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (5)
1u5t-14g386-cb.tar.gz (8.5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
4U5T-14G381-AN_1552583626000.TAR.GZ (479.7MB)
4U5T-14G391-CJ_1552513842000.TAR.GZ (381.5MB)
4U5T-14G423-CA_123766.tar.gz (724.2MB)

LOG
[8/12/2024 8:46:44 PM] Selected Region: NA - Release: Sync 3.3.19052 - Map Version: Non Nav APIM
[8/12/2024 8:46:44 PM] Install Mode: Auto-Detect (reformat) Forced: False
[8/12/2024 8:46:44 PM] MY20 Protection: Auto-Detect
[8/12/2024 8:46:44 PM] Formatting USB drive
[8/12/2024 8:46:44 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[8/12/2024 8:47:21 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz
[8/12/2024 8:47:21 PM] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download)
[8/12/2024 8:47:21 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[8/12/2024 8:47:21 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download)
[8/12/2024 8:47:21 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ
[8/12/2024 8:47:25 PM] Validated: 4U5T-14G381-AN_1552583626000.TAR.GZ (Skipping Download)
[8/12/2024 8:47:25 PM] Checking Existing File: 4U5T-14G391-CJ_1552513842000.TAR.GZ
[8/12/2024 8:47:27 PM] Validated: 4U5T-14G391-CJ_1552513842000.TAR.GZ (Skipping Download)
[8/12/2024 8:47:27 PM] Checking Existing File: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:47:31 PM] Validate: 4U5T-14G423-CA_123766.tar.gz (Failed!, Downloading)
[8/12/2024 8:47:31 PM] Downloading: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:50:10 PM] Validating: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:50:13 PM] Downloaded: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:50:13 PM] Preparing USB drive
[8/12/2024 8:50:13 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz
[8/12/2024 8:50:13 PM] Copying: 1u5t-14g386-cb.tar.gz
[8/12/2024 8:50:14 PM] Validating: 1u5t-14g386-cb.tar.gz
[8/12/2024 8:50:15 PM] Copied: 1u5t-14g386-cb.tar.gz
[8/12/2024 8:50:15 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[8/12/2024 8:50:15 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ
[8/12/2024 8:50:15 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ
[8/12/2024 8:50:15 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ
[8/12/2024 8:50:15 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ
[8/12/2024 8:50:15 PM] Copying: 4U5T-14G381-AN_1552583626000.TAR.GZ
[8/12/2024 8:52:22 PM] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ
[8/12/2024 8:52:51 PM] Copied: 4U5T-14G381-AN_1552583626000.TAR.GZ
[8/12/2024 8:52:51 PM] Checking Existing File: 4U5T-14G391-CJ_1552513842000.TAR.GZ
[8/12/2024 8:52:51 PM] Copying: 4U5T-14G391-CJ_1552513842000.TAR.GZ
[8/12/2024 8:54:54 PM] Validating: 4U5T-14G391-CJ_1552513842000.TAR.GZ
[8/12/2024 8:55:17 PM] Copied: 4U5T-14G391-CJ_1552513842000.TAR.GZ
[8/12/2024 8:55:17 PM] Checking Existing File: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:55:17 PM] Copying: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:59:13 PM] Validating: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:59:58 PM] Copied: 4U5T-14G423-CA_123766.tar.gz
[8/12/2024 8:59:58 PM] Generating reformat.lst
[8/12/2024 8:59:58 PM] Generating autoinstall.lst
[8/12/2024 8:59:58 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!


SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 1.0.15139

New SYNC Version: 3.3.19052

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

Update Method: CyanLabs Manual Method

Hello.

Syn3updater does not work with < 3.3, so you will have to manually create an upgrade USB for 2.2.xxxxx… take this guide as reference → 2016 Mustang Sync3 1.0 updated to 3.0 and no Apple Carplay! - #10 by SaNdMaN

Also, for a 2016 vehicle you may need to change the USB HUB → Media Hub, CarPlay Compatible - 2015-2020 Ford/Lincoln - SYNC 3

Before spending money, try updating it to 2.2.xxxx and check if Android Auto works.

Do not go to 3.3 yet, it’s recommended to validate CP/AA works on previous builds. And before going to 3.3 or 3.4, make sure the unit is not MY20.

Also, try using a quality device instead of “Generic Flash Disk USB Device”…

1 Like

When updating to 2.2 do I have to edit the vin in the update file or will my APIM retain the original vin?

Unsure where you read that you need to edit a VIN on a file…

You will not have to do that…

Is the unit stock?.

I did not read it I was just curious since most modules have the vin stored on them.

I just tried to update to 2.2 in my car. I inserted the usb and the screen is black now. It will not turn on. I followed the instructions in the 2016 mustang thread perfectly.

Edit. i unplugged the usb module in the center console. Restarted the car and now it is updating.

A black screen?, that’s odd… Good that it recovered, but that’s odd…

You haven’t answered if the unit is stock (unmodified).

Yes the unit is the stock sync 3. Sorry to be so post happy I thought it was bricked.

That’s ok. Once you are done, before actually reformatting the unit (should you decide to), run the interrogator log to double check the APIM’s model. Since you are running 1.x it’s highly unlikely it’s a replacement APIM, but you never know…

What would be the reason to reformat the system? I thought reformatting was to “downgrade” update versions.

You should read the instructions… It’s all really well documented…

In order to go to 3.3 or 3.4 you need to reformat the unit…

Most modules do not have the VIN in the AB. The VIN is read from the BCM over the CanBus. There are only 4-5 modules that do have the VIN in them. The APIM is one of the modules that reads the VIN from the CanBus.

So I updated to 2.2 using the 2016 mustang forum intrusions. After replacing the usb plug in the center console Apple car play works flawlessly! Thank you so much for your help.

I was just asking about the vin coding because most of the time in my shop when replacing modules they have to get programmed. We sub that out to another company so the liability is in someone else’s hands sorry for any confusion.

As far as reformatting I was under the impression that the syn3 updater did the reformatting. Since car play is working with no issues I do not plan on updating any farther. What benefits would I get if I did go farther? My apologies again if I missed information or misinterpreted it.

Thank you again for your help. Having car play made our family vacation from NJ to Virginia a lot more convenient.

1 Like

Reformatting is only necessary to get new maps that are ESN locked.

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