Cant update using the SYN3

yrndtn · 11 May 2025 06:41

Hello,
After trying to update my multimedia via USB or online, I tried the SYN3.
I followed the instructions, downloaded and created the USB drive, inserted it into the USB hub in the car, and returned to SYN3 with the XML file.
I got this error, which I can’t find how to process with the upgrade

SYNC Region: ROW

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 2.2.16280

New SYNC Version: 3.4

Do you have a error message, if so what is it?
The XML file you have selected does not contain the expected output.
SYN3 updater has determined you are on 2.2.16280 and may be using overlays
Syn3 updater is unable to determine the configuration of your APIM

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.13.2.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

<?xml version="1.0" encoding="UTF-8"?>
<p:OTAModuleSnapShot xmlns:d2p1="urn:ford/Vehicle/Module/Information/v3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="urn:ford/com/productdesign/ipp/ModuleSnapshot/v2.0" version="2025-05-07" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
<p:VIN>1FM5K7F87HGC95358</p:VIN>
<p:ModuleName>ECU</p:ModuleName>
<p:RequestRole>
  <d2p1:Role>CONSUMER</d2p1:Role>
  <d2p1:RoleSource>OTA</d2p1:RoleSource>
  <d2p1:RoleDesc>SYNC</d2p1:RoleDesc>
  <d2p1:RoleID>OTA</d2p1:RoleID>
</p:RequestRole>
<p:Node isFlashed="false" specificationCategory="GGDS">
  <d2p1:Address>7D0</d2p1:Address>
  <d2p1:ECUAcronym name="APIM">
    <d2p1:State>
      <d2p1:Gateway gatewayType="NONE">
        <d2p1:DID didFormat="ASCII" didType="Embedded Consumer Operating System Part Number" didValue="8033" responseLength="24">
          <d2p1:Response>HN1T-14G381-LG</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8060" responseLength="384">
          <d2p1:Response>484235542d3134473432312d464142000000000000000000484e31542d3134473339312d464600000000000000000000484235542d3134473432332d464100000000000000000000484235542d3134473338362d414845000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8061" responseLength="384">
          <d2p1:Response>000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="HEX" didType="ECU Checksum 1" didValue="D704" responseLength="4">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didType="Direct Configuraation DID DE07" didValue="DE07">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>true</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Cal-Config Part Number" didValue="F10A" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="On-line Diagnostic Database Reference Number" didValue="F110" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Calibration Data #1 Number" didValue="F124" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="Private Sub Node #1 Serial Number" didValue="F141" responseLength="16">
          <d2p1:Response>WW3YFVY7</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="State Encoded" didType="Software Download Specification Version" didValue="F162" responseLength="1">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Cal-Config #2 Part Number" didValue="F16B" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="Vehicle Manufacturer ECU Software Number" didValue="F188" responseLength="24">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="ASCII" didType="ECU Serial Number" didValue="F18C" responseLength="16">
          <d2p1:Response>Blank</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
          <d2p1:Response>98:5d:ad:67:c9:33</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
        <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
          <d2p1:Response>98:5d:ad:67:c9:34</d2p1:Response>
          <d2p1:IsConfig>false</d2p1:IsConfig>
        </d2p1:DID>
      </d2p1:Gateway>
    </d2p1:State>
  </d2p1:ECUAcronym>
  <d2p1:ODLNetwork d2p1:NetworkDataRate="500" d2p1:NetworkName="HS1" d2p1:NetworkProtocol="CAN" d2p1:DLCName="SAE J1962" d2p1:Pins="6,14"/>
  <d2p1:AdditionalAttributes logGeneratedDateTime="2025-05-07T13:16:32+00:00" RAM="1228763136" vmcuVersion="Vector_VMCU_02.02.20">
    <d2p1:PartitionHealth type="/dev/hd0t180" total="19624061952" available="54710240"/>
    <d2p1:PartitionHealth type="/dev/hd0t181" total="718364672" available="2097120"/>
    <d2p1:PartitionHealth type="/dev/hd0t177" total="136776704" available="2097152"/>
    <d2p1:InstallationLog/>
    <d2p1:SyncData>MIIEhAYJKoZIhvcNAQcDoIIEdTCCBHECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBADfpmALMPDQ+Tqf9y5HMYaG1MZ+yMeR61c6mP11voQTpI/JDKrI0om69GDUVPMb03/2PDTIx3hx+LmXTXtBZk/ntbI1NZQJ9iEvgGGfP1svsVtJjyhzVWiL3Yw/EYFoyjhTLiPtc2aPJE4Q4b+8oPtLPIrt5z9okcczZ+XSe6tT2ZnBluJhtP2RpLyEdqAZTNR10JMwJ+b3fdiCvOyMpmUldBwGN51pHaofwnaRuZGt6oUbwCal8WTw/Q3h+u5aSmqSEv/sfzMfZD7z42f+NesZ/FFCBbH5WumgnkTnqXFTIcEiUbbH9/LdlMgGYGONKLGk3/DlqqErGc+00YwJEyUwwggKuBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBBieFUnLQ3hOVqVEQXJX3DRgIICgExFpLHqY+v7YZDMtIbK5kj1+YBqHsuLsTDloqLM8lcRnQYdyVgDyNOajDgUXrDyULFiRC/G9LjUBz1MtIMoga9e+sNGnWCLQ/fO+b3LIkKb59k3GjVXlxWB0Q+biyshQ9DR1Ez1b1bvC5p10i1khwZ6qW4UDdXO+NfUMENeO6uNz2m5cgKy/pZn9efi0WfPmEW6JL7fW0IL2lMvSUjsgPbi2ZRIrUrtjv6T1feZaDlOWyp2j2kxT9l1gbE8Y6+fHj5FmZIt7zn8tc0u2TYgRrH1UhmJl/rxH44h18I9E3HhcAA/CoXq+2CDdo4CJXsYT99vELcnV2PjBqSZNp1kEK540ds6Yuh/j/w3S4MHJtl061iQn/0beSQ8Xs+buca0wrDk2Tn/H+O8g126eOKTntG2Uf1vl1ZDs87cg0QjZh1nKoq3hrCFrsT+p3unCTY+tvIyESjrS9uHPNgXf4I3vjYgeopx8FcUK58jLkeSbqQu8nglEZjyJLtt/rjl0LetdgcnN013m2ctNl4TYPpGYd5Isu3swjAj0VKj9zwBdVTcl0Tn9RJN3rgHEkQK72IJV+oQJK5aLP8rDMLzdoK4LpOftsCiJ09MfjPqMnWrKoS+aG3GSNImvm1NQiLfbm9U02sfIGejy71bP9PEBc0O+uxSzNkVMvyADSaSl5B/9jeNQ3dY6NQydurfV6+5Vw1oJOPejBYsWOHaS8BCPV2ATzs8Vai3TRl8dcHDoDcnGtXyEGZ1EZOjP01+i96qV3/yp4brU2aGmDPeIL3NLZXB4c5xUiP8Uors9GljbrSWEN/owQPAJwFrIN8KJTSd2K5suNCHCltCCaFwNBj13HB0MP4=</d2p1:SyncData>
  </d2p1:AdditionalAttributes>
</p:Node>
</p:OTAModuleSnapShot>

SaNdMaN · 11 May 2025 10:30

Hello.

Your APIM is not showing which model it’s. Unless you are 150% sure the unit is stock from 2018, do not proceed until confirming which model it’s.

Here are a few things you can try:

manually upgrade to a newer 2.x or 3.0 Sync3 version, and run the interrogator once more
unmount the unit to gain access to the sticker on the APIM’s back. Share a picture of it.
if you have Forscan and an adapter, you can read the APIM model from there.

Regardless of the chosen path, make sure Car Play works on your current build before moving to 3.4.

warlock12118 · 11 May 2025 19:34

What build of Sync3 does thd Ford owner site offer you when you put in your VIN?

F150Chief · 12 May 2025 02:17

Your APIM is running Sync 3.0 version 2.2.16280 (HN1T-14G381-LG). Run the Interrogator Utility version -AB to determine the specifics as -AD is for Sync 3.4.

The SN of the APIM does match the OEM asbuilt.
1FM5K7F87HGC95358.xml (35.8 KB)

1FM5K7F87HGC95358
WW3YFVY7
APIM PN HB5T-14G371-GCA, 32GB
7D0
F110>DSGB5T-14G371-CB
F111>HB5T-14G380-BA
F113>HB5T-14G371-GCA
F124>GB5T-14G375-GA
F141>WW3YFVY7
F188>GB5T-14G374-CB
F1D0>985DAD67C933
F1D1>98:5D:AD:67:C9:34

The APIM is not MY20+, ECU Core Assembly Number is HB5T-14G380-BA. This is Pre18.5 MY.
Run the Interrogator Utility version -AB to determine the specifics before you try anything to verify.

yrndtn · 12 May 2025 11:14

Hello,
Thanks for your replies.
When I check online for update by VIN, I get Update Available 3.0.23219, so i guess the syn3 updater is trying to update for an unsupport firmware (Still it doesnt explain why I couldnt update via Ford file or online).
I’m not sure I was using the syn3 correctly, there is no firmware files on the USB. Is there any turorial on how to do it correctly with the above firmware?

warlock12118 · 12 May 2025 12:30

Sync3 isn’t firmware, its an APP with an update to the QNX Auto OS.
3.0.23219 is the highest version Ford supports on your car, if the car won’t take that update the odds of getting the updater to get you to 3.4.x aren’t all that great. It typically means you have another issue, eg bad USB hub, cheap USB flash drive, bad APIM.
The updater reformats the APIM to a new file structure which 3.4.x requires, if you have issues with 3.4.x the only way to revert to 3.0.x is to replace the APIM.

yrndtn · 12 May 2025 19:56

I understand that SYN3 is only a tool. Now I understand how it works…
I want to use it to upgrade my multimedia to the latest version supported by FORD. Should I use the SYN3? is there any walk through guide to use the SYN3 to upgrade to 3.0.23219 ?

warlock12118 · 12 May 2025 22:01

The updater is built around getting you on 3.4.x.
Ford has the full step by step instructions on their site.
https://www.ford.com/support/sync-maps-updates/

F150Chief · 12 May 2025 22:05

Please run the Interrogator Utility, version -AA or -AB and post the xml here.

Preparation and Execution

Download the appropriate file for your Sync version based on the production date and software. (Based on Ford recommendations and update packaging.)

For Sync 3.0 version 1.0/2.2/2.3, use file GB5T-14G386-AA. (Released 2016-05-26)
For Sync 3.2/3.3 all versions, use file GB5T-14G386-AB. (Released 2018-10-11)
For Sync 3.4.18347 to 3.4.20237, use file GB5T-14G386-AC. (Released 2020-02-19)
For Sync 3.4.20282 to present, use file GB5T-14G386-AD. (Released 2020-10-07)

NOTE:
If you have installed Sync 3.2+ (3.2, 3.3, 3.4) on an older APIM that was previously running Sync 3.0, you may find that the xml file may not populate the information properly. If the -AD file version does not work properly, use the -AC or -AB file version. A Master Reset may be required in some cases.

This installation will be run identically to an app or voice file install. Follow the instructions below:

Create a USB drive (format as EXFAT) with a SyncMyRide folder.
Copy the utility file downloaded above into the SyncMyRide folder.
In the root of the USB is the autoinstall.lst and DONTINDX.MSA files which you can obtain from any upgrade you previously performed.
You will need to edit the autoinstall.lst file so it looks like the example below, using the filename for the file you downloaded. This is an example for version -AA:

 [SYNCGen3.0_ALL]
 Item1 = GB5T-14G386-AA.TAR.GZ
 Open1 = SyncMyRide\GB5T-14G386-AA.TAR.GZ
 Options = Delay,Include,Transaction

Insert USB in vehicle and wait for the installation to complete. You should see a message indicating completion.
Remove the USB drive. On your computer, insert the drive and browse to the USB drive\SyncMyRide and open the xml file. Scroll to the bottom of the file to see your storage. The asbuilt info is also in the file near the top identified by the entries ‘Direct Configuration DID DE00’ thru ‘…DE06’. Be aware the data presented does not include the asbuilt checksum data for each code line.

From the log above this is what is installed on your APIM.

HN1T-14G381-LG
HN1T-14G391-FF
HB5T-14G421-FAB
HB5T-14G423-FA
HB5T-14G386-AHE
Note: There are no Nav Voice files for ROW.

There is an overlay installed on the APIM.
HB5T-14G386-AHE 863Kb overlay (ifs с /apps/APP_SUM)
This needs to be removed. DO NOT use any Ford installation package for Sync 3.0 or you will have issues. To remove the overlay, you will need to use a utility file.
HB5T-14G387-AAB 5kb "# This utility uninstalls overlay1.img which has the IVSU fix on MY17.x Versions.
This is to be used in conjunction with a Sync app installation.

I can make an autoinstall file for you to run with the overlay delete, but I need to know what country you reside and the language you need for the Sync voice to install 3.0.23219.

yrndtn · 15 May 2025 14:32

Hi,
I follow this instruction, along with video tutorial I watch on youtube.
After preparing the SYN3 with all the details, included the APIM number and hit the start button, xit looks OK at the begining , downloading files for reasonable time (about 20 min). When its done, I see on the local folder (syn3 updater) 5.7GB size files but the USB contain only 416KB size files (DONTINDX.MSA, autoinstall.lst, SyncMyRide\GB5T-14G386-AA_56065.tar.gz). It seems like I missing something, but I dont know what…

yocomy30 · 15 May 2025 14:25

Because my carplay wasn’t working, I decided to try reinstalling sync 3.423188. I used the reformat tool (FMods), but after inserting the stick made with Syn3Updater, I received the error ‘‘update packages not found’’ and sync remained stuck in the loop.

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.23188

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Error update package not found

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: Syn3Updater

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.13.3.0
Branch: Stable
Operating System: Microsoft Windows 11 Pro (2009)

PREVIOUS CONFIGURATION
Version: 3.4.23188
Region: EU
Navigation: True
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: Kingston DataTraveler 3.0 USB Device
Size: 57,7GB
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.3.0 Stable - Autoinstall Mode - Sync 3.4.23188 EU

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = VOICE - 5U5T-14G391-AT_1660763323000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G391-AT_1660763323000.TAR.GZ
Item3 = GRACENOTES - 4U5T-14G423-AC_1615425645000.TAR.GZ
Open3 = SyncMyRide\4U5T-14G423-AC_1615425645000.TAR.GZ
Item4 = ENH_DAB - 1U5T-14G658-AH_1644006443000.TAR.GZ
Open4 = SyncMyRide\1U5T-14G658-AH_1644006443000.TAR.GZ
Item5 = APPS - NU5T-14G381-AD_1689364279000.TAR.GZ
Open5 = SyncMyRide\NU5T-14G381-AD_1689364279000.TAR.GZ
Options = AutoInstall


FILES (5)
PU5T-14G386-BB_1690840002000.TAR.GZ (3,2KB)
5U5T-14G391-AT_1660763323000.TAR.GZ (1,5GB)
4U5T-14G423-AC_1615425645000.TAR.GZ (689MB)
1U5T-14G658-AH_1644006443000.TAR.GZ (57,5MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869,8MB)

LOG
[15.05.2025 10:39:00] Selected Region: EU - Release: Sync 3.4.23188 - Map Version: Keep Existing Maps 
[15.05.2025 10:39:00] Install Mode: Auto-Detect (autoinstall) Forced: False 
[15.05.2025 10:39:00] MY20 Protection: Auto-Detect 
[15.05.2025 10:39:00] Formatting USB drive
[15.05.2025 10:39:00] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[15.05.2025 10:39:08] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:39:08] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[15.05.2025 10:39:08] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:39:08] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:39:08] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:39:08] Downloading: 5U5T-14G391-AT_1660763323000.TAR.GZ
[15.05.2025 10:41:35] Validating: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:41:39] Downloaded: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:41:39] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:41:39] Downloading: 4U5T-14G423-AC_1615425645000.TAR.GZ
[15.05.2025 10:42:42] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:42:44] Downloaded: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:42:44] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:42:44] Downloading: 1U5T-14G658-AH_1644006443000.TAR.GZ
[15.05.2025 10:42:49] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:42:49] Downloaded: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:42:49] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:42:49] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[15.05.2025 10:44:10] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:44:12] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:44:12] Preparing USB drive
[15.05.2025 10:44:13] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:44:13] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:44:13] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:44:13] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[15.05.2025 10:44:13] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:44:13] Copying: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:45:02] Validating: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:45:07] Copied: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[15.05.2025 10:45:07] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:45:07] Copying: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:45:32] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:45:33] Copied: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[15.05.2025 10:45:33] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:45:33] Copying: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:45:34] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:45:35] Copied: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[15.05.2025 10:45:35] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:45:35] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:46:09] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:46:11] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[15.05.2025 10:46:11] Generating Autoinstall.lst
[15.05.2025 10:46:11] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

al3xp · 15 May 2025 14:39

You need Cyanlabs in reformat mode, the fmods reformat tool is looking for a different files list than autoinstall.

yocomy30 · 15 May 2025 14:43

Where can I download it, how do I do it? Thanks

yocomy30 · 15 May 2025 15:47

Thanks for the support. I managed to do it.

SaNdMaN · 16 May 2025 00:41

Do not make multiple threads for a related “issue”.
I’ve merged your threads.

yrndtn · 18 May 2025 12:26

Thanks,
What should I choose for MY20 protection?
My car is Ford Explorere Limited 2018

Another question:
I see there is a map update just release by Ford last week.
I probabely wont use it, but if I’m updating my system, should I wait for the new release to be available on SYN3 or I’ll be able to update it later?

warlock12118 · 18 May 2025 15:34

If you reformat the APIM in an effort to fix your 3.4.23188 and don’t select to update the maps (even to the version you currently have) you’ll have a NAV error on restart as the reformat deletes the existing map files.

F150Chief · 18 May 2025 18:22

yrndtn · 21 May 2025 06:16

Thanks,
What should I choose for MY20 protection? Disable or Not MY20?
My car is Ford Explorere Limited 2018

wiz043 · 22 May 2025 05:38

The latter.