So if you go to owner.ford.com it comes back with incorrect VIN or shows no recalls?
Incorrect VIN can happen if you do a copy/paste from an email or web page, it can insert hidden spaces in the VIN.
Do you think using big uncle max reformat tool would work here in this situation?
Yes I have forscan and a elm327
CYANLABS - SYN3 UPDATER - V2.14.2.0
Branch: Stable
Operating System: Microsoft Windows 11 Home (2009)
PREVIOUS CONFIGURATION
Version: 3.4.23188
Region: NA
Navigation: True
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect
DESTINATION DETAILS
Mode: Drive
Model: SanDisk Ultra USB Device
Size: 14.6GB
FileSystem: exFAT
Partition Type: MBR
AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.14.2.0 Stable - Autoinstall Mode - Sync 3.4.23188 NA
[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-CS_1660783942000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G391-CS_1660783942000.TAR.GZ
Item3 = GRACENOTES - 4U5T-14G423-CC_1615429225000.TAR.GZ
Open3 = SyncMyRide\4U5T-14G423-CC_1615429225000.TAR.GZ
Item4 = APPS - NU5T-14G381-AD_1689364279000.TAR.GZ
Open4 = SyncMyRide\NU5T-14G381-AD_1689364279000.TAR.GZ
Options = AutoInstall
FILES (4)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)
LOG
[1/10/2026 2:33:02 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Keep Existing Maps
[1/10/2026 2:33:02 PM] Install Mode: Auto-Detect (autoinstall) Forced: False
[1/10/2026 2:33:02 PM] MY20 Protection: Auto-Detect
[1/10/2026 2:33:02 PM] Formatting USB drive
[1/10/2026 2:33:02 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[1/10/2026 2:33:12 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:33:12 PM] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:33:13 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:33:13 PM] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:33:13 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:33:13 PM] Downloading: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:33:30 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:33:33 PM] Downloaded: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:33:33 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:33:33 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:33:54 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:33:57 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:33:57 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:33:57 PM] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:34:33 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:34:38 PM] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:34:38 PM] Preparing USB drive
[1/10/2026 2:34:38 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:34:38 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:34:38 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:34:38 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ
[1/10/2026 2:34:38 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:34:38 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:35:17 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:35:30 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ
[1/10/2026 2:35:30 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:35:30 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:36:25 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:36:48 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ
[1/10/2026 2:36:48 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:36:48 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:38:28 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:39:20 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ
[1/10/2026 2:39:20 PM] Generating Autoinstall.lst
[1/10/2026 2:39:20 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
APIM Model: 5U5T-14G371-CKF
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 5.2G
Version 3.4.23188 (NU5T-14G381-AD)
1/10/2026 2:51:19 PM +00:00
Partition Type = Free / Total
/fs/sd/MAP/ = 10M / 1.3G
/fs/sd/MAP/ = 14M / 1.3G
/fs/sd/MAP/ = 13M / 1.3G
/fs/sd/MAP/ = 10M / 1.5G
/fs/sd/MAP/ = 4.2M / 879M
/fs/sd/MAP/ = 2.6M / 1.3G
/fs/sd/MAP/ = 14M / 1.7G
/fs/sd/MAP/ = 13M / 1.4G
/fs/sd/MAP/ = 6.4M / 1.3G
/fs/Nuance/ = 15M / 1.6G
/fs/Nuance/ = 10M / 1.1G
/fs/Nuance/ = 23M / 2.5G
/fs/Nuance/ = 3.2M / 465M
/fs/Nuance/grace = 5.8M / 775M
/fs/rwdata/ = 420M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 84M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 5.2G / 25G
Installed Packages
4U5T-14G423-CC
4U5T-14G421-CAG
4U5T-14G421-CBB
4U5T-14G421-CCB
4U5T-14G421-CDB
4U5T-14G421-CEB
4U5T-14G421-CFG
4U5T-14G421-CGB
4U5T-14G421-CHB
4U5T-14G421-CJB
5U5T-14G391-CS
4U5T-14G422-CAN
4U5T-14G422-CBE
4U5T-14G422-CCE
4U5T-14G424-CG
APIM AsBuilt
DE00: AA0A010300020B40048A
DE01: 55531003F482009B8000C405
DE02: 0100000300
DE03: 000032000F0001
DE04: 1AAE1A403E80
DE05: B2
DE06: 2D003A0000000003BE00005656AC00CF
this is what you needed right?
how did you get that to populate?
is that in the sync 3 updater?
SYNC 3 APIM Hardware Database - CyanLabs
When a vehicle is a 2020 you have to assume it has a 2020 APIM. The only way around that is to physiclly remove it to check the sticker and the build date.
im in the truck right now ripping apart the dash
Well you have the model number so it’s kinda known now.
and before any one gets on here and starts freaking out that it’s the wrong boot logo or says that’s the reason why. I know I just left it on there after I got done on forscan. It still happens with the ford logo one too.
Dumb statement
but on the apim it doesn’t have that model number from the log on it. It has the manufacturer date which is 2020 and it has this
ASSEMBLED IN MEXICO
CL - MJ49N0GL AG 728696
MFG Date: 05/28/2020
And then this is underneath it
WZ5WFVDW GR26A LC3T - 14G370 - BCH
Yup, 2020+ APIM
This is the model number. It is an L series. Those were for the 2020+ model vehicles.
I seen somewhere on here that you can use it on a MY20
Thanks for spreading the knowledge. I’m trying to get better with this. This my first ford so this is all new to me
1 Like
@SaNdMaN is this something that can be fixed with Forscan?
Or is there something that I have to do with the sync 3 updater or another tool
Forscan wont fix this. There are a few people on here that can fix it for you though. It would require you to ship your APIM to them. Or you just replace the APIM.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.