2014 Escape with 2018 APIM Doesn't Save Settings

I swapped my 2014 Sync 2 unit for a Sync 3 unit from a 2018 Escape a couple years ago. Everything worked fine with the AS-BUILT data the seller programmed.

Today, I decided to use your tool to try to upgrade it from software version 3.0 17194 to 3.4 build 21265, and although there were no errors, the unit became hung at the radio display and would not shut down if the ignition was switched off. It then went into a reboot loop for some time, showing the Ford loading logo and would immediately go to the auto-power-down timer screen regardless of if the engine was on or not.

I did a manual master reset by disconnecting the vehicle battery for 30+ seconds. After this, the unit has never ran into that specific hang issue, but it refuses to save any settings. Every time I turn my car on and off, and the unit loads up, it prompts me to select auto-update and diagnostic settings as if it’s being factory reset. I tried doing a Master Reset in the software menus, but just pauses with a loading icon for a while, returns to the home screen, and continues to have issues remembering any settings. If I change the wallpaper, it will reset after a minute or two. If I plug in my iPhone, it detects it and offers to enable car play, but it will not actually enable CarPlay projection. Plugging the phone back in again causes it to act as if it’s seeing the phone for the first time, and it makes the same prompts.

Something is clearly messed up with my head unit’s ability to remember settings, even while it’s powered on. Any ideas? I can try disconnecting the battery again. So far, I can’t find any forum posts with this exact issue, but people have said, in general: If you experience “a lot of glitches downgrade to version 19101.” I am not sure if I should just do that.

Update: I just tried downgrading to 19101. I got an INSTL_ERR12 code. Searching these forums, it means the filesystem is corrupt and could explain why settings don’t save and why a soft master reset does nothing. Any ideas, or am I SOL and in need of buying a new APIM?

Thanks


SYNC Region: North America & Canada

Navigation Variant: Yes

Old SYNC Version: 17194

New SYNC Version: 21265

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 3.4.21265

Syn3 Updater Documentation Read: Yes

Syn3 Updater Log File

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

PREVIOUS CONFIGURATION
Version: 3.0.17194
Region: NA
Navigation: True
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: Samsung Flash Drive FIT USB Device
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
VOICE=5U5T-14G391-CP_1626959995000.TAR.GZ
APPS=5U5T-14G381-EU_1634769242000.TAR.GZ
MAP=4U5T-14G421-CJD_1615428865000.TAR.GZ
MAP=4U5T-14G421-CHD_1615428793000.TAR.GZ
MAP=4U5T-14G421-CGD_1615428721000.TAR.GZ
MAP=4U5T-14G421-CFD_1615428639000.TAR.GZ
MAP=4U5T-14G421-CED_1615428554000.TAR.GZ
MAP=4U5T-14G421-CDD_1615428467000.TAR.GZ
MAP=4U5T-14G421-CCD_1615428361000.TAR.GZ
MAP=4U5T-14G421-CBD_1615428261000.TAR.GZ
MAP=4U5T-14G421-CAD_1615428059000.TAR.GZ
MAP_LICENSE=4U5T-14G424-CD_1616778089000.TAR.GZ
VOICE_NAV=4U5T-14G422-CAJ_1626961442000.TAR.GZ
VOICE_NAV=4U5T-14G422-CBJ_1626962550000.TAR.GZ
VOICE_NAV=4U5T-14G422-CCJ_1626963400000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.10.8.0 Stable - reformat  Mode - Sync 3.4.21265 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (17)
1u5t-14g386-cb.tar.gz (8.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
5U5T-14G391-CP_1626959995000.TAR.GZ (385.4MB)
5U5T-14G381-EU_1634769242000.TAR.GZ (847.2MB)
4U5T-14G421-CJD_1615428865000.TAR.GZ (657.9MB)
4U5T-14G421-CHD_1615428793000.TAR.GZ (989.6MB)
4U5T-14G421-CGD_1615428721000.TAR.GZ (1.1GB)
4U5T-14G421-CFD_1615428639000.TAR.GZ (1GB)
4U5T-14G421-CED_1615428554000.TAR.GZ (1GB)
4U5T-14G421-CDD_1615428467000.TAR.GZ (1.2GB)
4U5T-14G421-CCD_1615428361000.TAR.GZ (1GB)
4U5T-14G421-CBD_1615428261000.TAR.GZ (1.1GB)
4U5T-14G421-CAD_1615428059000.TAR.GZ (1.1GB)
4U5T-14G424-CD_1616778089000.TAR.GZ (1.7KB)
4U5T-14G422-CAJ_1626961442000.TAR.GZ (1.3GB)
4U5T-14G422-CBJ_1626962550000.TAR.GZ (772.4MB)
4U5T-14G422-CCJ_1626963400000.TAR.GZ (549.6MB)

LOG
[2/13/2022 5:53:53 PM] Selected Region: NA - Release: Sync 3.4.21265 - Map Version: 2.20 (2020) - NA 
[2/13/2022 5:53:53 PM] Install Mode: Auto-Detect (reformat) Forced: False 
[2/13/2022 5:53:53 PM] MY20 Protection: Auto-Detect 
[2/13/2022 5:53:53 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[2/13/2022 5:53:53 PM] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
[2/13/2022 5:53:53 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2/13/2022 5:53:54 PM] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[2/13/2022 5:53:54 PM] Checking Existing File: 5U5T-14G391-CP_1626959995000.TAR.GZ 
[2/13/2022 5:53:55 PM] Validated: 5U5T-14G391-CP_1626959995000.TAR.GZ (Skipping Download) 
[2/13/2022 5:53:55 PM] Checking Existing File: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[2/13/2022 5:53:57 PM] Validated: 5U5T-14G381-EU_1634769242000.TAR.GZ (Skipping Download) 
[2/13/2022 5:53:57 PM] Checking Existing File: 4U5T-14G421-CJD_1615428865000.TAR.GZ 
[2/13/2022 5:53:59 PM] Validated: 4U5T-14G421-CJD_1615428865000.TAR.GZ (Skipping Download) 
[2/13/2022 5:53:59 PM] Checking Existing File: 4U5T-14G421-CHD_1615428793000.TAR.GZ 
[2/13/2022 5:54:02 PM] Validated: 4U5T-14G421-CHD_1615428793000.TAR.GZ (Skipping Download) 
[2/13/2022 5:54:02 PM] Checking Existing File: 4U5T-14G421-CGD_1615428721000.TAR.GZ 
[2/13/2022 5:54:04 PM] Validated: 4U5T-14G421-CGD_1615428721000.TAR.GZ (Skipping Download) 
[2/13/2022 5:54:04 PM] Checking Existing File: 4U5T-14G421-CFD_1615428639000.TAR.GZ 
[2/13/2022 5:54:07 PM] Validated: 4U5T-14G421-CFD_1615428639000.TAR.GZ (Skipping Download) 
[2/13/2022 5:54:07 PM] Checking Existing File: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 5:54:07 PM] Downloading: 4U5T-14G421-CED_1615428554000.TAR.GZ
[2/13/2022 5:56:29 PM] Validating: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 5:56:31 PM] Downloaded: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 5:56:31 PM] Checking Existing File: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 5:56:31 PM] Downloading: 4U5T-14G421-CDD_1615428467000.TAR.GZ
[2/13/2022 5:59:39 PM] Validating: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 5:59:42 PM] Downloaded: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 5:59:42 PM] Checking Existing File: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 5:59:42 PM] Downloading: 4U5T-14G421-CCD_1615428361000.TAR.GZ
[2/13/2022 6:02:14 PM] Validating: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:02:16 PM] Downloaded: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:02:16 PM] Checking Existing File: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:02:16 PM] Downloading: 4U5T-14G421-CBD_1615428261000.TAR.GZ
[2/13/2022 6:04:55 PM] Validating: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:04:57 PM] Downloaded: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:04:57 PM] Checking Existing File: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:04:57 PM] Downloading: 4U5T-14G421-CAD_1615428059000.TAR.GZ
[2/13/2022 6:07:18 PM] Validating: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:07:20 PM] Downloaded: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:07:20 PM] Checking Existing File: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:07:20 PM] Downloading: 4U5T-14G424-CD_1616778089000.TAR.GZ
[2/13/2022 6:07:21 PM] Validating: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:07:21 PM] Downloaded: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:07:21 PM] Checking Existing File: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:07:21 PM] Downloading: 4U5T-14G422-CAJ_1626961442000.TAR.GZ
[2/13/2022 6:10:10 PM] Validating: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:10:13 PM] Downloaded: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:10:13 PM] Checking Existing File: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:10:13 PM] Downloading: 4U5T-14G422-CBJ_1626962550000.TAR.GZ
[2/13/2022 6:11:54 PM] Validating: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:11:56 PM] Downloaded: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:11:56 PM] Checking Existing File: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:11:56 PM] Downloading: 4U5T-14G422-CCJ_1626963400000.TAR.GZ
[2/13/2022 6:13:09 PM] Validating: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:13:10 PM] Downloaded: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:13:11 PM] Preparing USB drive
[2/13/2022 6:13:11 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[2/13/2022 6:13:11 PM] Copying: 1u5t-14g386-cb.tar.gz 
[2/13/2022 6:13:11 PM] Validating: 1u5t-14g386-cb.tar.gz 
[2/13/2022 6:13:11 PM] Copied: 1u5t-14g386-cb.tar.gz 
[2/13/2022 6:13:11 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2/13/2022 6:13:11 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2/13/2022 6:13:57 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2/13/2022 6:13:59 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2/13/2022 6:13:59 PM] Checking Existing File: 5U5T-14G391-CP_1626959995000.TAR.GZ 
[2/13/2022 6:13:59 PM] Copying: 5U5T-14G391-CP_1626959995000.TAR.GZ 
[2/13/2022 6:14:33 PM] Validating: 5U5T-14G391-CP_1626959995000.TAR.GZ 
[2/13/2022 6:14:34 PM] Copied: 5U5T-14G391-CP_1626959995000.TAR.GZ 
[2/13/2022 6:14:34 PM] Checking Existing File: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[2/13/2022 6:14:34 PM] Copying: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[2/13/2022 6:15:05 PM] Validating: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[2/13/2022 6:15:07 PM] Copied: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[2/13/2022 6:15:07 PM] Checking Existing File: 4U5T-14G421-CJD_1615428865000.TAR.GZ 
[2/13/2022 6:15:07 PM] Copying: 4U5T-14G421-CJD_1615428865000.TAR.GZ 
[2/13/2022 6:15:32 PM] Validating: 4U5T-14G421-CJD_1615428865000.TAR.GZ 
[2/13/2022 6:15:34 PM] Copied: 4U5T-14G421-CJD_1615428865000.TAR.GZ 
[2/13/2022 6:15:34 PM] Checking Existing File: 4U5T-14G421-CHD_1615428793000.TAR.GZ 
[2/13/2022 6:15:34 PM] Copying: 4U5T-14G421-CHD_1615428793000.TAR.GZ 
[2/13/2022 6:16:35 PM] Validating: 4U5T-14G421-CHD_1615428793000.TAR.GZ 
[2/13/2022 6:16:37 PM] Copied: 4U5T-14G421-CHD_1615428793000.TAR.GZ 
[2/13/2022 6:16:37 PM] Checking Existing File: 4U5T-14G421-CGD_1615428721000.TAR.GZ 
[2/13/2022 6:16:37 PM] Copying: 4U5T-14G421-CGD_1615428721000.TAR.GZ 
[2/13/2022 6:17:53 PM] Validating: 4U5T-14G421-CGD_1615428721000.TAR.GZ 
[2/13/2022 6:17:55 PM] Copied: 4U5T-14G421-CGD_1615428721000.TAR.GZ 
[2/13/2022 6:17:55 PM] Checking Existing File: 4U5T-14G421-CFD_1615428639000.TAR.GZ 
[2/13/2022 6:17:55 PM] Copying: 4U5T-14G421-CFD_1615428639000.TAR.GZ 
[2/13/2022 6:18:33 PM] Validating: 4U5T-14G421-CFD_1615428639000.TAR.GZ 
[2/13/2022 6:18:35 PM] Copied: 4U5T-14G421-CFD_1615428639000.TAR.GZ 
[2/13/2022 6:18:35 PM] Checking Existing File: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 6:18:35 PM] Copying: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 6:19:52 PM] Validating: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 6:19:54 PM] Copied: 4U5T-14G421-CED_1615428554000.TAR.GZ 
[2/13/2022 6:19:54 PM] Checking Existing File: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 6:19:54 PM] Copying: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 6:21:30 PM] Validating: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 6:21:33 PM] Copied: 4U5T-14G421-CDD_1615428467000.TAR.GZ 
[2/13/2022 6:21:33 PM] Checking Existing File: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:21:33 PM] Copying: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:22:37 PM] Validating: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:22:39 PM] Copied: 4U5T-14G421-CCD_1615428361000.TAR.GZ 
[2/13/2022 6:22:39 PM] Checking Existing File: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:22:39 PM] Copying: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:23:50 PM] Validating: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:23:53 PM] Copied: 4U5T-14G421-CBD_1615428261000.TAR.GZ 
[2/13/2022 6:23:53 PM] Checking Existing File: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:23:53 PM] Copying: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:24:51 PM] Validating: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:24:54 PM] Copied: 4U5T-14G421-CAD_1615428059000.TAR.GZ 
[2/13/2022 6:24:54 PM] Checking Existing File: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:24:54 PM] Copying: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:24:54 PM] Validating: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:24:54 PM] Copied: 4U5T-14G424-CD_1616778089000.TAR.GZ 
[2/13/2022 6:24:54 PM] Checking Existing File: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:24:54 PM] Copying: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:25:51 PM] Validating: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:25:54 PM] Copied: 4U5T-14G422-CAJ_1626961442000.TAR.GZ 
[2/13/2022 6:25:54 PM] Checking Existing File: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:25:54 PM] Copying: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:26:26 PM] Validating: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:26:28 PM] Copied: 4U5T-14G422-CBJ_1626962550000.TAR.GZ 
[2/13/2022 6:26:28 PM] Checking Existing File: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:26:28 PM] Copying: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:26:48 PM] Validating: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:26:49 PM] Copied: 4U5T-14G422-CCJ_1626963400000.TAR.GZ 
[2/13/2022 6:26:49 PM] Generating reformat.lst
[2/13/2022 6:26:49 PM] Generating autoinstall.lst
[2/13/2022 6:26:49 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

Hello.

Well, you have a lot going on.
Lets try breaking those down.

INSTL_ERR12
This error means there was an issue while creating an directory.
This is not a common error, and points to an unhealthy APIM.
Have you tried creating an interrogator log and running it against the UNIT?.
If not, do it please, and post the results here. Redact your VIN from the file’s content and title if you care about it being publicly shown. (since it’s not your original unit, I’m not sure which VIN would it display).

General Issues after Upgrading
Since your unit had a lot of as-built modifications, most likely the upgrade restored some defaults values. Do you have Forscan and a compatible scanner?. You will need to reprogram the APIM again.

This does not really look good, but lets see what the interrogator log show.

Yeah unfortunately I don’t know if anyone who has fixed this error without replacing the emmc or the whole APIM unfortunately, fwiw one of my test apims has the same issue

Unfortunately, that is exactly the case.

Thanks. I’m going to run an interrogator log just for the benefit of this community and its developers, but based on the other responses, I got a new pre-programmed Sync 3.4 APIM en route.

I got it from this seller, who claims he has compatible APIMs for a 3.0 > 3.4 conversion, which implies it must be a late 3.0 model that had official support for an upgrade to 3.4 and should be compatible with my screen. I told him of my predicament and prior 2.0 > 3.0 conversion, and he said he’s fairly confident this should work out-of-the-box.

Thank you.

The funny thing is that maybe the log will show everything right, who knows…
But when there are issues with the module’s storage, well… Things can get a bit weird…

But it would be interesting to see what information is shown, like the APIM model, to see if an older HW.

According to the link that you provided, that APIM is not MY20, which is good since will give you freedom to reformat it if needed.

NO Sync 3.0 unit from Ford has official support for upgrade to Sync 3.4. I think he is saying it would be compatible, and it is. However, this is an older model APIM (HP5T-14G371-AEG) which is 2017 production part number, but manufactured 09/20/2019. This indicates it is a service replacement module for the China market. US APIM’s are made in Mexico.

Your screen will work with the unit. You should either send the seller your APIM asbuilt, or you will most likely need to make changes for your vehicle, since it is a 2014 Escape.

Oooh, ok. That explains why it’s a 32GB APIM, then. The China market probably needs more memory to store navigation maps. I’m also glad t hear this is very likely an unused APIM if it’s a service part and not something scrapped from a wreck.

So if I understand, this seller is more than likely just pre-flashing the APIM to Sync 3.4 using the same Syn3 tool that I’d attempted to use on my original APIM. Which is good, because if the eMMC fails, the liability is on them before it ships out.

Yes, they did ask for my VIN. I also have the AS-BUILT from my original APIM backed up. Despite my hardware failure, the AS-BUILT seemed to work fine and was detecting every feature in my vehicle like back when it was on 3.0.

Correct, mostly. They probably use FORScan or other software to edit the asbuilt also.

Just to bring some closure to this, the APIM swap with the unit I received on Amazon went well. My failed APIM had the following lingering behaviors:

  • Settings would not persist across resets or would even revert back during uptime
  • CarPlay would not work
  • Display would flicker badly when being turned on or off
  • GPS was not detected
  • Master reset would fail
  • Any attempt to insert a USB drive with a SyncMyRide directory present would result in a “INSTL_ERR12” code.

Because of that last issue, I could unfortunately not even get an interrogator log to run. If anybody would strongly want the failed APIM, I can ship it, but it sounds like even some here have seen failures, and it’s probably just the Syn3 update failing as a victim of a latent eMMC failure. I’m sure if I tried a master reset even back on Sync 3.0, there’d be signs of issues due to eMMC failure.

In any case, the replacement I unit came with build 20021 and also had flickering issues, but it was only while driving at dusk and was probably the daylight sensor bug that impacts the Escape and Focus. I upgraded it to 21265, which fixes that bug as I see in the community changelogs. now, I have a fully functioning APIM again that acts and feels indistinguishable from a stock unit unless somebody knew the car never came with it. Everything works.

1 Like

Thank you for posting the update. Glad you got everything fixed. Enjoy.

Could you do a favor and run the Interrogator Utility on the new unit and post the file, redact your VIN. That unit looks like a service replacement assembly made for the H Series APIM’s. (HP5T-14G371-EAG)
It’s fine, but I want to make sure about the eMMC version it contains.

Here you go. If you see anything of concern, please let me know, but as said, it seems to be working extremely well.

Sync_VVA00DFD_VIN_REDACTED.xml (11.4 KB)

How did you update it?.
Did you reformat it?.

I’m asking because the manufacture date is 2019 for a series that’s not from 2019, so as F150chief said maybe it has newer hardware than the original H series ones.

Syn3 Updater recommended the auto-install method since it came with 20021. It updated to 22165 just fine. There was also a gracenotes and voice update that installed fine.

Ok, do not reformat it until more information is obtained about the unit, since it may contain MY20/+ hardware even being an H series APIM.

Thanks for the warning. The APIM came with FMODS installed on it, although I didn’t know what I was looking at originally until I researched it. Updating to 22165 seemed to get rid of it, and then I ended up missing some of the tweaks and re-jailbreaking it, but now I may need to be careful not to install a mod I don’t care for. I think an auto-install downgrade would wipe away any mods and return it to stock, according to their forum posts. But in any case, I won’t reformat it.

You are correct, installing any update will wipe out the mods. However, it does not negate the JB file.

As far as the new unit, you have 5 DTC’s that should be addressed on the APIM. I don’t know what they are because it does not tell the coding. You can see these in FORScan.

The installed packages are:
5U5T-14G381-EU
4U5T-14G423-CC
4U5T-14G421-CAD
4U5T-14G421-CBD
4U5T-14G421-CCD
4U5T-14G421-CDD
4U5T-14G421-CED
4U5T-14G421-CFD
4U5T-14G421-CGD
4U5T-14G421-CHD
4U5T-14G421-CJD
4U5T-14G422-CAH
4U5T-14G422-CBH
4U5T-14G422-CCH
5U5T-14G391-CP

The APIM serial number is VVA00DFD.
Calibration>GB5T-14G375-AA.
Strategy=GB5T-14G374-CB
This is not a MY20+ APIM. You don’t need to worry about the reformat issue.
(For those wondering, The V series serial numbers were discontinued when the MY20+ APIM’s started.)
Storage: <d2p1:PartitionHealth type="/fs/images/" total=“25G” available=“4.3G”/>
Just what it is supposed to be for a NA APIM with NAV.

Here is what Forscan says. It only raises a single non-critical DTC:

Code: U2101 - Control Module Configuration Incompatible

Status: 
 - DTC Present at Time of Request
 - Malfunction Indicator Lamp is Off for this DTC

Module: Accessory Protocol Interface Module

Clear all the DTC’s and then drive the car for a few days and check again for DTC’s. I think those might have been from the previous issues. If they come back, let us know and we can help you track down the issue.

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