Blank screen after attempted update

Ford SYNC 3 Support CyanLabs Update Support
, , , , , ,
1

Hello, I was looking to update sync 3 on my 2017 Lincoln Continental with navigation. I first attempted to use the official OTA method where I connected to my home wifi to download the update. After checking for software updates in the UI, it didn’t seem to download anything. When I searched online, I came across syn3updater and decided to update using this method. I created a USB stick following the instructions in the prompts and documentation.

Later in the day when I plugged the USB drive with the update to the car, after a few moments I get a message that it is downloading the update. It let it go through and got to the screen where it asks me to restart the car. I waited for it to go to the reformat screen for about 10-15 minutes, but nothing happened. So, I restarted the car with the USB plugged in. Since then the screen has gone blank. I can see the backlight and my phone still works via bluetooth. I can switch to fm, AM or android auto using the steering wheel controls. However, the display is not working.

Is there any way to recover this back from here? I also looked at the forum for similar issues and most of it seem to be due to MY20+ APIMs which is not the case for me. In hindsight, I probably should not have tried OTA and USB method and just stuck to one, but I didn’t realize it at the time.

I also have forscan and pulled the APIM details if that helps:
APIM - Accessory Protocol Interface Module
Part number: HP5T-14G371-CCA
Calibration level: HP5T-14G371-CCG (latest known: HP5T-14G371-CGF)
Strategy : GB5T-14G374-CB
Calibration: GB5T-14G375-CA

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 2.2.16280

New SYNC Version: 3.4.23188

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0 Stable

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

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

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

DESTINATION DETAILS
Mode: Drive
Model:  USB  SanDisk 3.2Gen1 USB Device
Size: 28.7GB
FileSystem: FAT32
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ
VOICE_NAV=4U5T-14G422-CCN_1709611788000.TAR.GZ
VOICE_NAV=4U5T-14G422-CBN_1709611416000.TAR.GZ
VOICE_NAV=4U5T-14G422-CAN_1709610798000.TAR.GZ
MAP=4U5T-14G421-CJG_1709610049000.TAR.GZ
MAP=4U5T-14G421-CHG_1709609492000.TAR.GZ
MAP=4U5T-14G421-CGG_1709608813000.TAR.GZ
MAP=4U5T-14G421-CFG_1709608559000.TAR.GZ
MAP=4U5T-14G421-CEG_1709607297000.TAR.GZ
MAP=4U5T-14G421-CDG_1709589204000.TAR.GZ
MAP=4U5T-14G421-CCG_1709587982000.TAR.GZ
MAP=4U5T-14G421-CBG_1709587496000.TAR.GZ
MAP=4U5T-14G421-CAG_1708029977000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - reformat  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 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open2 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (17)
1u5t-14g386-cb.tar.gz (8.5MB)
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)
4U5T-14G422-CCN_1709611788000.TAR.GZ (540.7MB)
4U5T-14G422-CBN_1709611416000.TAR.GZ (793MB)
4U5T-14G422-CAN_1709610798000.TAR.GZ (1.2GB)
4U5T-14G421-CJG_1709610049000.TAR.GZ (707.8MB)
4U5T-14G421-CHG_1709609492000.TAR.GZ (1023.3MB)
4U5T-14G421-CGG_1709608813000.TAR.GZ (1.2GB)
4U5T-14G421-CFG_1709608559000.TAR.GZ (1.1GB)
4U5T-14G421-CEG_1709607297000.TAR.GZ (1.1GB)
4U5T-14G421-CDG_1709589204000.TAR.GZ (1.3GB)
4U5T-14G421-CCG_1709587982000.TAR.GZ (1.1GB)
4U5T-14G421-CBG_1709587496000.TAR.GZ (1.1GB)
4U5T-14G421-CAG_1708029977000.TAR.GZ (1014.9MB)

LOG
[6/26/2024 3:32:01 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: 2.23 (2023) - NA 
[6/26/2024 3:32:01 PM] Install Mode: Auto-Detect (reformat) Forced: False 
[6/26/2024 3:32:01 PM] MY20 Protection: Auto-Detect 
[6/26/2024 3:32:01 PM] Formatting USB drive
[6/26/2024 3:32:01 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[6/26/2024 3:32:45 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:32:45 PM] Downloading: 1u5t-14g386-cb.tar.gz
[6/26/2024 3:33:10 PM] Validating: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:33:10 PM] Downloaded: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:33:10 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:33:10 PM] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[6/26/2024 3:33:31 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:33:31 PM] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:33:31 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:33:31 PM] Downloading: 5U5T-14G391-CS_1660783942000.TAR.GZ
[6/26/2024 3:33:49 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:33:50 PM] Downloaded: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:33:50 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:33:50 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ
[6/26/2024 3:34:19 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:34:20 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:34:20 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:34:20 PM] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[6/26/2024 3:35:01 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:35:03 PM] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:35:03 PM] Checking Existing File: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:35:03 PM] Downloading: 4U5T-14G422-CCN_1709611788000.TAR.GZ
[6/26/2024 3:35:28 PM] Validating: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:35:29 PM] Downloaded: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:35:29 PM] Checking Existing File: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:35:29 PM] Downloading: 4U5T-14G422-CBN_1709611416000.TAR.GZ
[6/26/2024 3:36:07 PM] Validating: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:36:09 PM] Downloaded: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:36:09 PM] Checking Existing File: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:36:09 PM] Downloading: 4U5T-14G422-CAN_1709610798000.TAR.GZ
[6/26/2024 3:37:11 PM] Validating: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:37:14 PM] Downloaded: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:37:14 PM] Checking Existing File: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:37:14 PM] Downloading: 4U5T-14G421-CJG_1709610049000.TAR.GZ
[6/26/2024 3:37:46 PM] Validating: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:37:47 PM] Downloaded: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:37:47 PM] Checking Existing File: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:37:47 PM] Downloading: 4U5T-14G421-CHG_1709609492000.TAR.GZ
[6/26/2024 3:38:37 PM] Validating: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:38:39 PM] Downloaded: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:38:39 PM] Checking Existing File: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:38:39 PM] Downloading: 4U5T-14G421-CGG_1709608813000.TAR.GZ
[6/26/2024 3:39:35 PM] Validating: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:39:37 PM] Downloaded: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:39:37 PM] Checking Existing File: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:39:37 PM] Downloading: 4U5T-14G421-CFG_1709608559000.TAR.GZ
[6/26/2024 3:40:31 PM] Validating: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:40:33 PM] Downloaded: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:40:33 PM] Checking Existing File: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:40:33 PM] Downloading: 4U5T-14G421-CEG_1709607297000.TAR.GZ
[6/26/2024 3:41:27 PM] Validating: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:41:29 PM] Downloaded: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:41:29 PM] Checking Existing File: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:41:29 PM] Downloading: 4U5T-14G421-CDG_1709589204000.TAR.GZ
[6/26/2024 3:42:32 PM] Validating: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:42:35 PM] Downloaded: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:42:35 PM] Checking Existing File: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 3:42:35 PM] Downloading: 4U5T-14G421-CCG_1709587982000.TAR.GZ
[6/26/2024 3:43:33 PM] Validating: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 3:43:35 PM] Downloaded: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 3:43:35 PM] Checking Existing File: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 3:43:35 PM] Downloading: 4U5T-14G421-CBG_1709587496000.TAR.GZ
[6/26/2024 3:44:28 PM] Validating: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 3:44:30 PM] Downloaded: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 3:44:30 PM] Checking Existing File: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 3:44:30 PM] Downloading: 4U5T-14G421-CAG_1708029977000.TAR.GZ
[6/26/2024 3:45:18 PM] Validating: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 3:45:21 PM] Downloaded: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 3:45:21 PM] Preparing USB drive
[6/26/2024 3:45:21 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:45:21 PM] Copying: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:45:21 PM] Validating: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:45:21 PM] Copied: 1u5t-14g386-cb.tar.gz 
[6/26/2024 3:45:21 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:45:21 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:45:21 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:45:21 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[6/26/2024 3:45:21 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:45:21 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:45:35 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:45:37 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[6/26/2024 3:45:37 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:45:37 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:45:56 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:46:00 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[6/26/2024 3:46:00 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:46:00 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:46:29 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:46:35 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[6/26/2024 3:46:35 PM] Checking Existing File: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:46:35 PM] Copying: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:47:01 PM] Validating: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:47:05 PM] Copied: 4U5T-14G422-CCN_1709611788000.TAR.GZ 
[6/26/2024 3:47:05 PM] Checking Existing File: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:47:05 PM] Copying: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:47:50 PM] Validating: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:47:56 PM] Copied: 4U5T-14G422-CBN_1709611416000.TAR.GZ 
[6/26/2024 3:47:56 PM] Checking Existing File: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:47:56 PM] Copying: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:49:08 PM] Validating: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:49:17 PM] Copied: 4U5T-14G422-CAN_1709610798000.TAR.GZ 
[6/26/2024 3:49:17 PM] Checking Existing File: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:49:17 PM] Copying: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:49:58 PM] Validating: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:50:03 PM] Copied: 4U5T-14G421-CJG_1709610049000.TAR.GZ 
[6/26/2024 3:50:03 PM] Checking Existing File: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:50:03 PM] Copying: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:51:30 PM] Validating: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:51:38 PM] Copied: 4U5T-14G421-CHG_1709609492000.TAR.GZ 
[6/26/2024 3:51:38 PM] Checking Existing File: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:51:38 PM] Copying: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:53:23 PM] Validating: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:53:38 PM] Copied: 4U5T-14G421-CGG_1709608813000.TAR.GZ 
[6/26/2024 3:53:38 PM] Checking Existing File: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:53:38 PM] Copying: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:55:18 PM] Validating: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:55:33 PM] Copied: 4U5T-14G421-CFG_1709608559000.TAR.GZ 
[6/26/2024 3:55:33 PM] Checking Existing File: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:55:33 PM] Copying: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:57:13 PM] Validating: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:57:21 PM] Copied: 4U5T-14G421-CEG_1709607297000.TAR.GZ 
[6/26/2024 3:57:21 PM] Checking Existing File: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:57:21 PM] Copying: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:59:20 PM] Validating: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:59:36 PM] Copied: 4U5T-14G421-CDG_1709589204000.TAR.GZ 
[6/26/2024 3:59:36 PM] Checking Existing File: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 3:59:36 PM] Copying: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 4:00:45 PM] Validating: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 4:01:02 PM] Copied: 4U5T-14G421-CCG_1709587982000.TAR.GZ 
[6/26/2024 4:01:02 PM] Checking Existing File: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 4:01:02 PM] Copying: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 4:02:08 PM] Validating: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 4:02:25 PM] Copied: 4U5T-14G421-CBG_1709587496000.TAR.GZ 
[6/26/2024 4:02:25 PM] Checking Existing File: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 4:02:25 PM] Copying: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 4:03:24 PM] Validating: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 4:03:35 PM] Copied: 4U5T-14G421-CAG_1708029977000.TAR.GZ 
[6/26/2024 4:03:35 PM] Generating reformat.lst
[6/26/2024 4:03:35 PM] Generating autoinstall.lst
[6/26/2024 4:03:35 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
2

Hello.

So the unit is operational but with a black screen… does the rear view camera work ?..

Do you see any splash screen when it turns on?.

Since you have Forscan, is there any DTC present?.

3

When I turn on the car, the backlight turns on and it tries to display something (maybe the splash screen) for a fraction of a second and then turns blank.

Rear view camera does not work.

There is a DTC at the APIM, not sure if it is relevant. The seat controls work fine.

Code: U024C - Lost Communication with Seat Control Module ‘H’

Status (-08):

  • Previously Set DTC - Not Present at Time of Request
  • Malfunction Indicator Lamp is Off for this DTC

Module: Accessory Protocol Interface Module

4

You could try a soft reset…hold sync power button and seek button >> together for 10 seconds or so to see if it reboots.
Apart from that perhaps try a new USB stick download via Cyanlabs and see if it will upload in the car and then follow instructions.
Often you get a message a short time into the upload asking you to remove the USB but you should leave it in for the system to reboot and continue with the map upload etc. as you probably know.
When the upload is finished, in perhaps 30 minutes or so, you should get a green stripe with the message to remove the flash drive.
Then you should always do a master reset.

5

Sounds like it wasn’t finished when you restarted the car.
I’ve had G/H series APIMs (2016/2017) take 30 minutes before the reboot to the reformat kicked off.

6

I tried a soft reset. It seems to restart the APIM because I can see the backlight turn off and on again, but it still doesn’t show any display.

I also created a new USB stick with just 4U5T-14G381-AN_1552583626000.TAR.GZ (3.3.19052), plugged it into the car with the engine running for atleast 30 min. It didn’t seem to take any action. Is there a specific version I should try this with, or would it not matter?

I wasn’t aware that I should wait upto 30 min before reboot to the reformat kickoff. It would have been helpful to point this out in the documentation where it just says “it will restart automatically in a few moments.”

7

Can you create and run an interrogator log against the unit? See if it produces any output… Since no reformat phase has initiated as per your comments, I would set your current Sync3 version as the latest known installed version. If that fails, set the 3.3.19xxx as current (the build you tried last)

8

Sorry…I didn’t mean that it should take 30 minutes to reboot, I just meant the whole upload should take 30 minutes or so to complete.
The message you mention during the upload…‘it will restart automatically in a few moments’ is accurate and the system should do this.

9

To clarify, I did get to this message on my unit:

However, it didn’t restart from that point after waiting 10-15min. The display went blank after I manually restarted the car following that.

@SaNdMaN I didn’t realize setting the version number was necessary for the interrogator utility. I had it set to 2.2.16280 from my previous USB creation. That didn’t give me any output when I plugged it into the car. There was no xml left in the USB. I’ll try again with 3.3.19052 (and 3.4.23188) and report back.

10

If that message appeared after some time perhaps you could try again and just follow the request after closing the message.
That is based on a new upload attempt working for you.

11

Yep, depending on what the unit is running, Syn3updater will select the correct interrogator package for that build… Also, remember to check both the USB’s root and SyncMyRide folder for the XML…

Since you have Forscan, can you please share a screenshot of your current ASBUILT values for the APIM?.

12

I’ve attached the asbuilt data. Here’s a snapshot of it if that’s easier:

asbuilt_snap
asbuilt_snap1536×846 69.9 KB

1LN6L9NC6H5636635_APIM_20240802_204023.abt (349 Bytes)

Also still trying to get interrogator tool working by cycling through the versions that could be on the unit. I appreciate all the help so far!

13

Thank you for the screenshot, it’s easier that way, I will review some theme related things.

There are 2 things to review:

Both seem to be correct in your case: master theme, boot splash and theme are Lincoln’s, I do not see an issue there. You could try changing them all to Ford’s just to see if that changes anything, but since you do not even see a boot splash logo I’m not sure if that’s even relevant.

Have you tried resetting the module from Forscan?.
I remember a case like yours, I will try to find it and see how it went…

Just keep track of the interrogator package used by each version… I do not remember which package corresponds to which versions, but if you change versions and the package used is the same, there’s no need to recreate the USB…

14

I tried different versions of interrogator tool, but no xml output from any of them. I checked in the root and Sync folders in the USB.

I also connected to forscan and tried other theme combinations (old lincoln and ford), but didn’t make any difference.
No luck with module reset in forscan (I had tried it before as well).

I looked into sync3flash method to write directly to the eMMC. This seems like a task for the next weekend though. Any other ideas before I go down this road?

15

I’m running out of ideas… Sync3flash is not exactly for this case, since it’s for bricked APIMs, which is not your case since the unit is 100% operational, but it’s not showing any image…

Let’s see if anyone else has an idea how this can be recovered…

EDIT: Take a look at this thread → Black Screen after update … there are a few things that you could try…

1 Like
16

Thanks for sharing that thread. Here are a few things I should try based on what I’ve read:

  1. Update the strategy file for my H series APIM following this guide APIM Firmware Flash Rescue
    According to that article, the strategy GB5T-14G374-CB has an issue which might have caused this issue. Well, turns out my APIM had that strategy from the factory. Updating to HB5T-14G374-CA is the suggested solution following the correct programming order for SBL, strat, calibration etc. I don’t have a battery charger, so I should pick one before I attempt to program the APIM.
    update
    update3200×1800 314 KB

Is there a general recommendation on the amperage requirement for the battery charger? I understand it might vary from model to model based on its draw from accessories and modules. Will I be ok at 6A, should I go higher?

  1. eMMC could be failing which means I’m SOL. Hopefully that is not the case here.
17

You want one that can put out 15A continuously (without being in start mode).
Also make sure your headlights/markers are turned off as well as the radio and HVAC.

1 Like
18

I followed the APIM recovery guide referenced earlier and flashed the available strategy and calibration file for my apim module. It seems to go through the process successfully, but then ends with the message "Programming was successful, but something went wrong. Module seems to be “bricked” :frowning: "

Here’s the log from forscan:

(OK) [20:02:44.072] APIM Module firmware update has been started
(WARN) [20:02:44.092] Reading vehicle info…
(WARN) [20:02:44.407] Unable to read current firmware p/n, use assembly p/n: GB5T-14G379-AA
(WARN) [20:02:44.457] Unable to read current firmware p/n, use assembly p/n: GB5T-14G379-BA
(WARN) [20:03:19.469] Downloading firmware files from the Internet…
(OK) [20:03:21.496] Downloading GB5T-14G376-AA: OK
(OK) [20:03:22.514] Downloading HB5T-14G374-CA: OK
(OK) [20:03:22.537] Downloading HB5T-14G375-CA: OK
(OK) [20:03:22.552] Downloading GB5T-14G379-AA: OK
(OK) [20:03:22.567] Downloading HB5T-14G379-BA: OK
(WARN) [20:04:04.317] Total size: 1.3 Kb. Estimated duration: ~1m
(WARN) [20:04:18.804] Loading SBL to primary module…
(WARN) [20:04:19.925] Loading block 1/1…
(OK) [20:04:20.056] SBL loaded successfully
(OK) [20:04:20.368] Service procedure completed successfully.
(OK) [20:04:51.321] APIM Module firmware update has been started
(WARN) [20:04:51.342] Reading vehicle info…
(WARN) [20:04:51.572] Unable to read current firmware p/n, use assembly p/n: GB5T-14G379-AA
(WARN) [20:04:51.633] Unable to read current firmware p/n, use assembly p/n: GB5T-14G379-BA
(WARN) [20:05:10.889] Loading and parsing factory As Built file…
(WARN) [20:08:07.662] Total size: 657.8 Kb. Estimated duration: 1m - 2m
(WARN) [20:08:15.135] Loading SBL to primary module…
(WARN) [20:08:16.127] Loading block 1/1…
(OK) [20:08:16.232] SBL loaded successfully
(WARN) [20:08:16.251] Loading firmware to ECU: HB5T-14G374-CA
(WARN) [20:08:16.252] Erasing block 1/2…
(WARN) [20:08:16.458] Erasing block 2/2…
(WARN) [20:08:22.444] Loading block 1/7…
(WARN) [20:08:23.169] Loading block 2/7…
(WARN) [20:08:23.225] Loading block 3/7…
(WARN) [20:08:23.282] Loading block 4/7…
(WARN) [20:08:23.498] Loading block 5/7…
(WARN) [20:09:06.747] Loading block 6/7…
(WARN) [20:09:06.919] Loading block 7/7…
(OK) [20:09:06.956] Firmware loaded successfully
(WARN) [20:09:06.990] Loading firmware to ECU: HB5T-14G375-CA
(WARN) [20:09:07.077] Loading block 1/1…
(OK) [20:09:07.170] Firmware loaded successfully
(ERR) [20:09:07.527] Programming was successful, but something went wrong. Module seems to be “bricked” :frowning:
(OK) [20:09:21.710] Service procedure completed successfully.

When I turn the car on, it seems the APIM is completely off. I no longer see the backlight and there’s no audio coming through.

Searching for the error message in this forum, I came across this post that seems to follow the same pattern as my case. Both starting to flash from 2.2.16280 and running into the same issue: similar post

To me, this seems there might be something wrong with eMMC. Any other ideas?

UPDATE: Oops, rookie mistake. I panicked after seeing the bricked message and forgot to follow through with flashing the ecu configuration for sound and illumination. I’m back to the blank screen with backlight now after flashing those. Still no display :frowning:

19

You’re confusing flashing the APIM (which is hardware firmware) with SyncFlash which is for the Sync3 software application.

ForScan will not let you recover a bad Sync3 update.

20

Wanted to give an update to this post. I ended up buying a replacement APIM and swapping it out with my unit. Lincoln made it harder than it needed to be to replace the APIM, because I needed to remove the upper floor console to get to a few bolts holding the display. Nevertheless, It worked out fine in the end.

I created a new profile in forscan so it can detect the new module. Then replaced the asbuilt from my car. Had to zero out 7D0-08-x & 7D0-00-x because those addresses were not present in my asbuilt. Performed a master reset once the display loaded and everything seems to work fine!

Thank you to everyone in thread who offered advice and support, I appreciate it!

Now that I have the old unit out, maybe I can try flashing it using the sync3flash tool and see if I can revive it. Could a weekend project for winter.