Getting MY20+ Screen to work with older APIM

Hi folks,
I’ve been reading a couple of post here but did’t find a working solution for my problem. I’m trying to retrofit a Sync3 system to my 2020 Transit custom PHEV that came with a 4" screen and without APIM (I’m guessing that’s what’s know as sync2.5).
I bought an APIM from a Ford Focus (4U5T-14G371-GJA) and a screen from a Ford Puma (K1BT-18B955-FD) from EbayUK and wanted to test if everything is working on the bench before I move everything to the car.
So I built the bench test setup described in another post (Sync 3 APIM Bench Test Project Completed) and turned on the APIM on my desk.
I was not surprised that my screen did’t turn on since I read that the older APIM units don’t have the right drivers.
So I figured when I update to a more recent Sync3 version, the screen would come alive.
And to my great joy the screen showed some nice splash screens during the update from 3.4.21194 to 3.4.23118. Now I knew the screen works. However, it turned back to black when the update finished successfully.
Then I tried the solution in this post (SYNC 3 Software and Upgrading Screen Hardware) and used ForScan to set the config in 7D0-03-01: xxxx-**xx-xxxx to 00. Unlucky for me, that didn’t change anything.

So right now, I’m out of ideas and would be really happy if someone could give me a hint what could be done (except getting an older screen). I will attach the interrogator log for the current version as well as the AsBuiltdata.

While I#m writing this I was just thinking maybe it is the firmware of the APIM that also needs an update, but then I have no clue how that would be done.

Any help would be much appreciated!
Veit from Kiel, Northern Germany

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.21194

New SYNC Version: 3.4.23118

Do you have a error message, if so what is it?
no, just a black screen

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version:

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

Branch: Stable
Operating System: Microsoft Windows 10 Pro (2009)

Version: 3.4.21194
Navigation: True
Install Mode: Automatische Erkennung (downgrade)
Install Mode Overridden: False
My20 Protection Enabled: Automatische Erkennung

Mode: Drive
Model: VendorCo ProductCode 3.0 USB Device
Size: 982,4GB
FileSystem: exFAT
Partition Type: MBR


; CyanLabs Syn3Updater Stable - downgrade  Mode - Sync 3.4.23188 EU

Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = TOOL - GB5T-14G386-SC_85041.tar.gz
Open2 = SyncMyRide\GB5T-14G386-SC_85041.tar.gz
Item3 = APP - 4U5T-14G381-AN_1552583626000.TAR.GZ
Open3 = SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ
Options = AutoInstall
Item1 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall,Include,Transaction

FILES (22)
4U5T-14G381-AN_1552583626000.TAR.GZ (479,7MB)
GB5T-14G386-SC_85041.tar.gz (1,8KB)
1u5t-14g386-cb.tar.gz (8,5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3,2KB)
5U5T-14G391-AT_1660763323000.TAR.GZ (1,5GB)
4U5T-14G423-AC_1615425645000.TAR.GZ (689MB)
1U5T-14G658-AH_1644006443000.TAR.GZ (57,5MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869,8MB)
1U5T-14G421-BAK_1682464992000.TAR.GZ (2,3GB)
1U5T-14G421-BBK_1682466740000.TAR.GZ (541,8MB)
1U5T-14G421-BCK_1682467250000.TAR.GZ (1,7GB)
1U5T-14G421-BDK_1682467734000.TAR.GZ (1,1GB)
1U5T-14G421-BEK_1682467790000.TAR.GZ (1,7GB)
1U5T-14G421-BFK_1682467908000.TAR.GZ (2,5GB)
1U5T-14G421-BGK_1682467948000.TAR.GZ (2GB)
1U5T-14G421-BHK_1682468092000.TAR.GZ (2,7GB)
1U5T-14G421-BJK_1682469041000.TAR.GZ (25,6MB)
1U5T-14G424-BM_1683133039000.TAR.GZ (1,7KB)
4U5T-14G422-BAK_1682464728000.TAR.GZ (2,3GB)
4U5T-14G422-BBK_1682464776000.TAR.GZ (2,2GB)
4U5T-14G422-BCK_1682464838000.TAR.GZ (1,7GB)
4U5T-14G422-BDK_1682464885000.TAR.GZ (2GB)

[18.02.2024 13:07:36] Selected Region: EU - Release: Sync 3.4.23188 - Map Version: F12 (2022) - EU (05 2022) (Updated Voice) 
[18.02.2024 13:07:36] Install Mode: Automatische Erkennung (downgrade) Forced: False 
[18.02.2024 13:07:36] MY20 Protection: Automatische Erkennung 
[18.02.2024 13:07:36] Formatting USB drive
[18.02.2024 13:07:36] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[18.02.2024 13:07:44] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[18.02.2024 13:07:46] Validated: 4U5T-14G381-AN_1552583626000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:46] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[18.02.2024 13:07:46] Validated: GB5T-14G386-SC_85041.tar.gz (Skipping Download) 
[18.02.2024 13:07:46] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18.02.2024 13:07:46] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
[18.02.2024 13:07:46] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18.02.2024 13:07:46] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:46] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[18.02.2024 13:07:52] Validated: 5U5T-14G391-AT_1660763323000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:52] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[18.02.2024 13:07:55] Validated: 4U5T-14G423-AC_1615425645000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:55] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[18.02.2024 13:07:55] Validated: 1U5T-14G658-AH_1644006443000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:55] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18.02.2024 13:07:59] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[18.02.2024 13:07:59] Checking Existing File: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[18.02.2024 13:08:09] Validated: 1U5T-14G421-BAK_1682464992000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:09] Checking Existing File: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[18.02.2024 13:08:11] Validated: 1U5T-14G421-BBK_1682466740000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:11] Checking Existing File: 1U5T-14G421-BCK_1682467250000.TAR.GZ 
[18.02.2024 13:08:19] Validated: 1U5T-14G421-BCK_1682467250000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:19] Checking Existing File: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[18.02.2024 13:08:23] Validated: 1U5T-14G421-BDK_1682467734000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:23] Checking Existing File: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[18.02.2024 13:08:30] Validated: 1U5T-14G421-BEK_1682467790000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:30] Checking Existing File: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[18.02.2024 13:08:41] Validated: 1U5T-14G421-BFK_1682467908000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:41] Checking Existing File: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[18.02.2024 13:08:49] Validated: 1U5T-14G421-BGK_1682467948000.TAR.GZ (Skipping Download) 
[18.02.2024 13:08:49] Checking Existing File: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[18.02.2024 13:09:00] Validated: 1U5T-14G421-BHK_1682468092000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:00] Checking Existing File: 1U5T-14G421-BJK_1682469041000.TAR.GZ 
[18.02.2024 13:09:00] Validated: 1U5T-14G421-BJK_1682469041000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:00] Checking Existing File: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[18.02.2024 13:09:00] Validated: 1U5T-14G424-BM_1683133039000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:00] Checking Existing File: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[18.02.2024 13:09:10] Validated: 4U5T-14G422-BAK_1682464728000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:10] Checking Existing File: 4U5T-14G422-BBK_1682464776000.TAR.GZ 
[18.02.2024 13:09:20] Validated: 4U5T-14G422-BBK_1682464776000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:20] Checking Existing File: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[18.02.2024 13:09:27] Validated: 4U5T-14G422-BCK_1682464838000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:27] Checking Existing File: 4U5T-14G422-BDK_1682464885000.TAR.GZ 
[18.02.2024 13:09:35] Validated: 4U5T-14G422-BDK_1682464885000.TAR.GZ (Skipping Download) 
[18.02.2024 13:09:35] Preparing USB drive
[18.02.2024 13:09:35] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[18.02.2024 13:09:35] Copying: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[18.02.2024 13:10:39] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[18.02.2024 13:10:59] Copied: 4U5T-14G381-AN_1552583626000.TAR.GZ 
[18.02.2024 13:10:59] Checking Existing File: GB5T-14G386-SC_85041.tar.gz 
[18.02.2024 13:10:59] Copying: GB5T-14G386-SC_85041.tar.gz 
[18.02.2024 13:10:59] Validating: GB5T-14G386-SC_85041.tar.gz 
[18.02.2024 13:10:59] Copied: GB5T-14G386-SC_85041.tar.gz 
[18.02.2024 13:10:59] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18.02.2024 13:10:59] Copying: 1u5t-14g386-cb.tar.gz 
[18.02.2024 13:11:00] Validating: 1u5t-14g386-cb.tar.gz 
[18.02.2024 13:11:00] Copied: 1u5t-14g386-cb.tar.gz 
[18.02.2024 13:11:00] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18.02.2024 13:11:00] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18.02.2024 13:11:00] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18.02.2024 13:11:00] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18.02.2024 13:11:00] Checking Existing File: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[18.02.2024 13:11:00] Copying: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[18.02.2024 13:12:48] Validating: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[18.02.2024 13:14:00] Copied: 5U5T-14G391-AT_1660763323000.TAR.GZ 
[18.02.2024 13:14:00] Checking Existing File: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[18.02.2024 13:14:00] Copying: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[18.02.2024 13:14:46] Validating: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[18.02.2024 13:15:16] Copied: 4U5T-14G423-AC_1615425645000.TAR.GZ 
[18.02.2024 13:15:16] Checking Existing File: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[18.02.2024 13:15:16] Copying: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[18.02.2024 13:15:21] Validating: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[18.02.2024 13:15:21] Copied: 1U5T-14G658-AH_1644006443000.TAR.GZ 
[18.02.2024 13:15:21] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18.02.2024 13:15:21] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18.02.2024 13:16:21] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18.02.2024 13:16:59] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18.02.2024 13:16:59] Checking Existing File: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[18.02.2024 13:16:59] Copying: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[18.02.2024 13:19:42] Validating: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[18.02.2024 13:21:28] Copied: 1U5T-14G421-BAK_1682464992000.TAR.GZ 
[18.02.2024 13:21:28] Checking Existing File: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[18.02.2024 13:21:28] Copying: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[18.02.2024 13:22:05] Validating: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[18.02.2024 13:22:28] Copied: 1U5T-14G421-BBK_1682466740000.TAR.GZ 
[18.02.2024 13:22:28] Checking Existing File: 1U5T-14G421-BCK_1682467250000.TAR.GZ 
[18.02.2024 13:22:28] Copying: 1U5T-14G421-BCK_1682467250000.TAR.GZ 
[18.02.2024 13:24:26] Validating: 1U5T-14G421-BCK_1682467250000.TAR.GZ 
[18.02.2024 13:25:46] Copied: 1U5T-14G421-BCK_1682467250000.TAR.GZ 
[18.02.2024 13:25:46] Checking Existing File: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[18.02.2024 13:25:46] Copying: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[18.02.2024 13:27:01] Validating: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[18.02.2024 13:27:49] Copied: 1U5T-14G421-BDK_1682467734000.TAR.GZ 
[18.02.2024 13:27:49] Checking Existing File: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[18.02.2024 13:27:49] Copying: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[18.02.2024 13:29:46] Validating: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[18.02.2024 13:31:03] Copied: 1U5T-14G421-BEK_1682467790000.TAR.GZ 
[18.02.2024 13:31:03] Checking Existing File: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[18.02.2024 13:31:03] Copying: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[18.02.2024 13:33:58] Validating: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[18.02.2024 13:35:54] Copied: 1U5T-14G421-BFK_1682467908000.TAR.GZ 
[18.02.2024 13:35:54] Checking Existing File: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[18.02.2024 13:35:54] Copying: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[18.02.2024 13:38:13] Validating: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[18.02.2024 13:39:48] Copied: 1U5T-14G421-BGK_1682467948000.TAR.GZ 
[18.02.2024 13:39:48] Checking Existing File: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[18.02.2024 13:39:48] Copying: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[18.02.2024 13:42:54] Validating: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[18.02.2024 13:44:57] Copied: 1U5T-14G421-BHK_1682468092000.TAR.GZ 
[18.02.2024 13:44:57] Checking Existing File: 1U5T-14G421-BJK_1682469041000.TAR.GZ 
[18.02.2024 13:44:57] Copying: 1U5T-14G421-BJK_1682469041000.TAR.GZ 
[18.02.2024 13:44:59] Validating: 1U5T-14G421-BJK_1682469041000.TAR.GZ 
[18.02.2024 13:44:59] Copied: 1U5T-14G421-BJK_1682469041000.TAR.GZ 
[18.02.2024 13:44:59] Checking Existing File: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[18.02.2024 13:44:59] Copying: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[18.02.2024 13:44:59] Validating: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[18.02.2024 13:44:59] Copied: 1U5T-14G424-BM_1683133039000.TAR.GZ 
[18.02.2024 13:44:59] Checking Existing File: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[18.02.2024 13:44:59] Copying: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[18.02.2024 13:47:41] Validating: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[18.02.2024 13:49:29] Copied: 4U5T-14G422-BAK_1682464728000.TAR.GZ 
[18.02.2024 13:49:29] Checking Existing File: 4U5T-14G422-BBK_1682464776000.TAR.GZ 
[18.02.2024 13:49:29] Copying: 4U5T-14G422-BBK_1682464776000.TAR.GZ 
[18.02.2024 13:52:02] Validating: 4U5T-14G422-BBK_1682464776000.TAR.GZ 
[18.02.2024 13:53:43] Copied: 4U5T-14G422-BBK_1682464776000.TAR.GZ 
[18.02.2024 13:53:43] Checking Existing File: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[18.02.2024 13:53:43] Copying: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[18.02.2024 13:55:40] Validating: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[18.02.2024 13:56:55] Copied: 4U5T-14G422-BCK_1682464838000.TAR.GZ 
[18.02.2024 13:56:55] Checking Existing File: 4U5T-14G422-BDK_1682464885000.TAR.GZ 
[18.02.2024 13:56:55] Copying: 4U5T-14G422-BDK_1682464885000.TAR.GZ 
[18.02.2024 13:59:16] Validating: 4U5T-14G422-BDK_1682464885000.TAR.GZ 
[18.02.2024 14:00:48] Copied: 4U5T-14G422-BDK_1682464885000.TAR.GZ 
[18.02.2024 14:00:48] Generating reformat.lst
[18.02.2024 14:00:48] Generating autoinstall.lst

APIM_20240219_184506.abt (495 Bytes)
Sync_LY9L02RC.xml (11.1 KB)


That’s not accurate. New screens can work with old APIMS without issues, screens are “basically interchangeable”. What should not be done is a reformat on MY20 hardware, that is, on a MY20 APIM or a MY20 screen. Other than that, it just does not matter.

Post your full APIM asbuilt, you get that using Forscan.

Both of these units are 2019 production year and not MY20+. There should be no contention of firmware or software.

Have you tried this combination in the vehicle? Make sure that if you are doing this on the bench that the wakeup is being sent over CAN to the APIM, and the ignition keep alive is consistent. (Or whatever it’s called. See the bench test thread.)

I retrofitted my Fiesta MK8 which previously had Sync 2.5, originally equipped with the 8" K1BT-18B955-FC display and I fitted an APIM Part number: H1BT-14G371-AFC
Strategy: 1U5T-14G374-HA Calibration: 1U5T-14G374-EH and everything works correctly, but I remember that my friend had tried to mount an 8" display on his Fiesta taken from a Puma and had the same problem as you.

Likely firmware.

Thanks a lot for your replies! Gives me some hope, as it sounds like its not a general issue with hardware/software incompatibility.

I uploaded the asbuit file that ForScan gave me when prompted “Save All” with the original post. Please let me know if thats not what you meant and I will try to get the information needed.

Good to know! I didn’t find much information about the screen. And the sticker on the back (photo attached) had something that looked like a manufacturing date starting with 21.xx.yy, so I figured.

I have had the setup in the car in order to get the right ForScan profile, however not all wires were connected. I’ve essentially only connected the OBD 06 → APIM HS CAN H, PIN 53 and OBD 14 → APIM HS CAN L, PIN 54. I was able to update Sync3.4 with the APIM on the bench, so I think the ignition keep alive is good. But good point, I will finish up the full harness and recheck the bench test post for additional infos to see if the unit will turn on the screen.

Good to hear you were successful! :muscle:
And maybe my case will also help your friend finding a solution.

I have Part number: 45T-14G371-GJA
Calibration level: 45T-14G371-GDY
Strategy : 1U5T-14G374-DA
Calibration: 1U5T-14G375-HA

Which doesn’t quite align with the rest of what I got when I look this up in the firmware post: APIM Firmware Production Releases. Where imy strategy is listed as:
3.2/3.3 APIM NAV & NON-NAV Unit Firmware (Production Release, 2018.5, Late J thru K Series)
… which also serves your point:

So, just to reassure: you think I should update the firmware as written down in this post Updating Sync 3 APIM Firmware Using FORScan 2.4.x Release which forces me to bring the whole system to the car anyhow :grinning:

Thanks again for all the input so far!

SYNC Screen Hardware Database - CyanLabs

Excluding wiring problems you could try to update APIM Calibration and Strategy to the same versions I have (obviously it depends on whether your APIM is NAV or NNAV and from which GWM you own), furthermore based on experience my friend had you may have to replace the display with the same one I have (P/N: K1BT-18B955-FC), but these are suppositions and I don’t want to give you bad advice.

My apologies, I didn’t see the files at the bottom of your first post. I will try to check them later.

EDIT: while I’m reviewing some information, what’s the status of the unit?.
I know the screen does not come up, but is the unit operational at some level?.

If you ran the downgrade log you provided, you reformatted the unit.
From what you said, I assume you saw the mustang logo, the progress bar and the green screen at the end of the process, right?. If that’s the case, you can be 100% certain you do not have any MY20 hardware.

Also, try configuring these (take note of your current values):
7D0-02-01: xxxx-15xx-xxxx
7D0-03-01: xxxx-00xx-xxxx
7D0-01-02: 0xxx xxxx xxxx

Change those and reset the module.

Thanks for the replies, everybody!

Yes. Thats exactly what I saw.

Okay, I will try this first. Maybe a dumb questio, but: How do I reset the module without screen? Do you mean a master reset or just a power cycle?

I will try all your suggestions and come back here when I can report something or have more questions.

You have plenty of options: a soft reset, a power cycle, key cycle, pulling the fuses, preforming the module reset from Forscan. The idea is for the unit to restar and take the changes, to see if something is shown. What you are doing is changing the boot splash screen and theme values, the ones you currently have are described as “not used on 3.4” in our DB… So it’s worth a try …

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