Sync 3 Retrofit - Display Output Not Matching Screen Size

Hey fellas, I recently tried to retrofit a sync 3 headunit into my 2015 Fiesta ST and am having a few problems. The APIM I purchased was supposed to come from a 2016 fiesta, but when I installed it and turned it on I got a Lincoln splash screen. Then when it fully booted up, it appears to be using the Lincoln 10 or 8 inch output. Due to this, the screen is zoomed in on the upper left hand side to the point that I cannot navigate to the settings or anything of the sort.

I found an Asbuilt file for a 2016 Fiesta ST that came with Sync 3 and flashed it with Forscan, but unfortunately it does not appear to fix it. The splash screen on boot-up is now a ford one, but once it boots up it is still zoomed in. Oh and whenever I turn it off, it has a Navigator splash screen. I tried using a 2019 Fiesta ST asbuilt file as well to no avail.

I created an Interrogator USB, and I believe I have copied the log output of that below. I have also put the saved asbuilt from before I started tinkering with it below for reference.

Basically what I am asking for is what should I do next? Should I attempt to update the sync version without knowing what it currently is? Do I need to update the firmware on the APIM?

Thanks in advance everyone, I’ve been reading throughout this site to get ready to do this retrofit, and it truly is a treasure trove of information.

APIM P/N (on the back of the unit): gb5t-14g371-cg

Starting Asbuilt file saved via ForScan:

;Block 1
7D0G1G1B22A8010084D
7D0G1G283801001AA98
;Block 2
7D0G2G143480004C029
7D0G2G202005000204D
7D0G2G380005C
;Block 3
7D0G3G10000020000DD
;Block 4
7D0G4G10100000000DD
7D0G4G20000DD
;Block 5
7D0G5G10000000000DD
7D0G5G200DE
;Block 6
7D0G6G100DE
;Block 7
7D0G7G10A00000000E9
7D0G7G20000000000E0
7D0G7G30000000000E1
7D0G7G400E2
;Block 8
7D0G8G10C00000000EC
7D0G8G20000000000E1


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: Retrofit

Old SYNC Version: 2

New SYNC Version: 3

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.13.0.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

VIN: 3FADP4GX9FMXXXXXX
APIM Model: GB5T-14G371-CFC
APIM Type: Navigation 
APIM Size: 32GB 
APIM Free Space: 8.1G 


Partition Type = Free / Total
/fs/usb0/ = 58G / 58G
/fs/tmpfs/ = 127M / 128M
/fs/sd/MAP/ = 41M / 1.5G
/fs/sd/MAP/ = 57M / 9.1G
/fs/Nuance/ = 243M / 4.7G
/fs/Nuance/ = 13M / 475M
/fs/Nuance/grace = 5.1M / 1.0G
/fs/rwdata/ = 761M / 1024M
/fs/mp/ = 289M / 1024M
/fs/images/ = 8.1G / 26G

Installed Packages
1U5T-14G421-CA
1U5T-14G391-CA
1U5T-14G422-CA
1U5T-14G423-CA




APIM AsBuilt
DE00: 2330610500029817080A
DE01: 555301060AE2242030000005
DE02: 0000010000
DE03: 010007E1200000
DE04: 168A16442640
DE05: 80
DE06: 1000330000000002A60000043052005A

Is your screen 4 inches then ?
Also, provide the XML file for the log…

No it’s a 6.5 inch display. And my bad, I just uploaded the text from the decoder in the Syn3updater. Here is the xml file:
<redacted>

EDIT: I also did replace the display as part of the retrofit, as the old 6.5 inch display is not compatible. The P/N of the new display is G1BT-18B955-TD

Thanks for the file, I’ve redacted your message since the VIN is included in the file’s name and content, and since you masked it on your original post, I guess you care about it not being public… so it’s no longer publicly accesible…

That’s an odd log, I will tell you that, but I think it’s safe to assume the unit is running some 3.0 build…

Since you have Forscan, can you check what’s the value for this? → DE02/7D0-03-01 xxxx-**xx-xxxx

Thanks for that! forgot to rename the file lol.
Currently the value is: 01
Originally it was: 02

Out of curiosity, do you have a photo of what you are currently seeing?.

Yup

Thanks, it’s easier that way…

One last thing: do you have a picture of what the screen is currently displaying?.

Yup, here is what it looks like currently. Ignore the USB error, I need to install a new USB connector that is currently in the mail. But that should be in the center of the screen and it obviously isn’t.

That’s ok, but that’s also an odd picture haha… your unit is just odd…
There’s something that is worth mentioning: your APIM is almost ancient… It’s really really old… and you know what it’s said about old tech… they can be a little temperamental…

Having said that, there’s something you could try: installing the latest 3.0 build for 6.5 / 8’’ screens… The package name is JR3T-14G381-AY, you could try installing that and see if it makes any difference…

I do not have a link for what I think it’s your current package, but there are others from that “branch” that are newer… According to the log, your unit is running “JL7T-14G381-BA002”, which is a non existant package… But I think it’s some kind of JL7T-14G381-B* package…

Fair enough, I’ll give that a shot tonight. I remember building my first computer when the Ryzen 1600 came out and that was a royal pain haha. If that doesn’t work, do you think I should just return this APIM and get a different newer one?

If it does not work you have another options, like going straight to the latest 3.4 with maps… since it’s an old APIM it can be reformatted…

About a newer APIM it’s also welcomed, but not strictly required…