Interrogator returns "BLANK" for APIM AsBuilt and "Unknown" for APIM Model

Long story short, I just upgraded from 21265 to 22110 (hoping that might fix my issue with AA nav prompts killed my music volume, but it didn’t). I ran the interrogator before running that update to make sure I had room to proceed without removing Gracenotes first. The nice part is that I have 32 gigs of space, but none of the rest of the pertinent info populated.

What did I do wrong?

The update went fine, but I posted the log anyway.


SYNC Region: North America & Canada

Navigation Variant: No

Install Type: Retrofitted

Old SYNC Version: 3.4.21265

New SYNC Version: 3.4.22110

Do you have a error message, if so what is it?
VIN: 1FA6P8CFXF5353609
Version 5U5T-14G381-EZ
APIM Model: Unknown
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 23G
7/26/2022 9:40:37 PM +00:00

Partition Type = Free / Total
/fs/Nuance/ = 3.1M / 465M
/fs/Nuance/grace = 5.8M / 775M
/fs/rwdata/ = 996M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 23G / 25G

Installed Packages
5U5T-14G391-CR
4U5T-14G423-CC

APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.11.3.0

Syn3 Updater Documentation Read: Yes

Syn3 Updater Log File

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

PREVIOUS CONFIGURATION
Version: 3.4.21265
Region: NA
Navigation: False
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Disabled / Not MY20

DESTINATION DETAILS
Mode: Drive
Model: USB Device
Size: 29.5GB
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.11.3.0 Stable - Autoinstall Mode - Sync 3.4.22110 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = GRACENOTES - 4U5T-14G423-CC_1615429225000.TAR.GZ
Open1 = SyncMyRide\4U5T-14G423-CC_1615429225000.TAR.GZ
Item2 = APPS - 5U5T-14G381-EZ_1652218180000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G381-EZ_1652218180000.TAR.GZ
Item3 = VOICE - 5U5T-14G391-CR_1644007976000.TAR.GZ
Open3 = SyncMyRide\5U5T-14G391-CR_1644007976000.TAR.GZ
Options = AutoInstall


FILES (6)
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-14G381-AN_1552583626000.TAR.GZ (479.7MB)
5U5T-14G381-EZ_1652218180000.TAR.GZ (869.8MB)
5U5T-14G391-CR_1644007976000.TAR.GZ (385.5MB)

LOG
[7/26/2022 7:53:31 PM] Selected Region: NA - Release: Sync 3.4.22110 - Map Version: Non Nav APIM 
[7/26/2022 7:53:31 PM] Install Mode: Auto-Detect (autoinstall) Forced: False 
[7/26/2022 7:53:31 PM] MY20 Protection: Disabled / Not MY20 
[7/26/2022 7:53:31 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[7/26/2022 7:53:32 PM] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[7/26/2022 7:53:32 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:53:32 PM] Downloading: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/26/2022 7:54:09 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:11 PM] Downloaded: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:11 PM] Checking Existing File: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:54:11 PM] Downloading: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/26/2022 7:54:26 PM] Validating: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:54:27 PM] Downloaded: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:54:27 PM] Preparing USB drive
[7/26/2022 7:54:27 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[7/26/2022 7:54:31 PM] 4U5T-14G423-CC_1615429225000.TAR.GZ exists and validated successfully, skipping copy 
[7/26/2022 7:54:31 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:31 PM] Copying: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:47 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:52 PM] Copied: 5U5T-14G381-EZ_1652218180000.TAR.GZ 
[7/26/2022 7:54:52 PM] Checking Existing File: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:54:52 PM] Copying: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:55:00 PM] Validating: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:55:02 PM] Copied: 5U5T-14G391-CR_1644007976000.TAR.GZ 
[7/26/2022 7:55:02 PM] Generating Autoinstall.lst
[7/26/2022 7:55:03 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

This is on the 2015 Mustang with the retrofit Sync 3 installation?

What APIM did you install? You have the model number?
Try running the -AC file version of the Interrogator…

Yeah, but that’s the thing. The previous owner did the install and that’s why I’m trying to get this data from the interrogator because I don’t actually know which APIM he put in.

OK, so I ran it and the results look the same. Got a couple screenshots and I attached the XML file below.

There’s a way to get the part number via a button combo, isn’t there?

VIN: 1FA6P8CFXF5353609
Version 5U5T-14G381-EZ
APIM Model: Unknown
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 23G
7/27/2022 7:21:14 AM +00:00

Partition Type = Free / Total
/fs/Nuance/ = 3.1M / 465M
/fs/Nuance/grace = 5.8M / 775M
/fs/rwdata/ = 994M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 23G / 25G

Installed Packages
5U5T-14G391-CR
4U5T-14G423-CC

APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK


Sync_WVBXBQ47_1FA6P8CFXF5353609.xml (9.8 KB)

Do you have forscan?

It is a 32GB APIM. That parameter has nothing to do with the Sync information. It is capable of NAV. However, none of the system info is populating, which leads me to believe it’s been modified.

I do. I’ll have to charge my laptop and find my OBD2 adapter. What should I look for?

After I bought the car I was hoping to get in touch with the previous owner to find out where he sourced his parts for Sync3 as well as whatever other mods were done, but I never heard back. Everything is super clean except I had to use ForScan to correct my BT issues and the exhaust looked like it was installed by Stevie Wonder (it was an MBRP racing exhaust that I replaced with a Borla Touring setup).

You made a good choice…
Connect to the APIM and see if you can find the firmware and part numbers.

1 Like

I haven’t had a chance to run Forscan BUT I did have a few minutes to mess around in the “Testing Menu” since I got to work early. Got a few interesting pictures outside of the part numbers, like the APIM thinking I have a FWD car. LOL

Uploading these from my phone, so not sure if they’re in order.






First, don’t pay attention to the Configuration Status screens, as they are always wrong. This is little understood, but the information shown is the base configuration of the Sync software. It does not reflect the current asbuilt status. For the APIM, I can tell you that the previous owner bought a “hacked” APIM to put in the car, this is certain. It is no wonder you have issues with it.

The APIM unit is an HB5T-14G371-GBA, which is a NON-NAV APIM from a 2017 Ford Explorer. Yet, the interrogator reports that the unit has 32GB of storage. The interrogator utility is correct in this report, as it seems the unit is modified. When we look at the firmware files installed on the unit, there is the following:

APIM Serial Number :WVBXBQ47
Vehicle Identification Number (VIN) :xxxx…
Assembly Part Number :HBST-14G371-GBA
H/W Part Number :HBST-14G380-BA
CCPU S/W Part Number :5UST-14G381-EZ
VMCU S/W Part Number :GBST-14G374-CB (This is a later 2017 file)
Calibration S/W Part Number :GBST-14G375-GA (NAV ROW)

This aligns with the production release of:
3.0 APIM NAV Unit Firmware (Production Release, 2016-Early 2017, G-Early H Series)
GB5T-14G376-AA
GB5T-14G374-CA
GB5T-14G375-DA or GB5T-14G375-FA (GB5T-14G375-CA NON-NAV)
GB5T-14G379-AA
GB5T-14G379-BA

However, the calibration file is not correct for the unit being North America (NA).
XXXX-14G375-G*.vbf 32GB ROW with NAV (NNG)

It is obvious that the unit has been modified for more storage (duaghter board swap) to enable NAV and was loaded with ROW regional files to accomodate the swap. Whoever did the swap used an eMMC reader/writer to install a modified image which is not compliant with the Ford tools.

All that said, the APIM will still work, but unfortunately you will have the existing issues with it, and most likely you will not be able to solve them. I would suggest you replace the APIM if you wish to solve the issues.

Well, the only actual functional issue I’m having is the music volume dropping with Waze prompts, which seems to be an issue people have been complaining about on Android Auto in general. Otherwise it’s done everything I want perfectly.

There are a lot of complaints about that, but Waze is particularly problematic.

It’s crazy that it’s a Google product that seems to be broken in very non-Google ways. LOL

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