For NON-NAV, -CA would be correct then…
It’s not a bad idea about flashing the firmware, but a matter of what it will get you. In this case, flashing the firmware will not enable any new features, since you are rather recent anyways. But it won’t hurt anything either.
Thanks…I’ll report back after flashing it
By the way, there is a much newer version of FORScan 2.4.3 beta available (2021-02-24). You appear to be using a build from 2020-09-20. If you are going to be doing any sort of flashing it would probably be best to grab the newest beta build to be safer as it also has a new recovery mode function in case things go wrong.
OK, so it boils down to a hardware limitation. Thanks. I was hoping to avoid sourcing a new APIM, but there seems to be no way around that in my case.
Also, thanks for the link though I’m already up to date on that thread. I didn’t find a whole lot more information relating to updating the firmware on ‘G’ APIMs, other than a generalized statement that some users have reported difficulty. Your earlier post was the first instance I could find of someone seeming to know more details related to it!
Thanks! I noticed this too and did update to the 2021-02-24 release shortly after capturing that screen grab. 
I was actually thinking I may even have to downgrade to 2.4.0 as there were some earlier posts about 2.4.3 having bugs that were causing issues. Not entirely sure if they’ve been addressed in the latest release of 2.4.3. But it seems my best route will be to source a newer APIM anyway, so once I get that newer APIM up and running, then I may go back and play around with the original APIM to see what damage I can do ahaha
If I recall correctly, FORScan 2.4.3 beta available 2021-02-24 and 2020-09-20 were never released on the FORScan website. These were test builds to resolve issues. The last release on the website was 2.4.2.
2.4.0 has issues on it’s own. I would stick with the latest build unless you experience issues.
As far as the APIM, that really is the best way to go and it will just work. I’ve done a few and it makes life so much easier…and breaking the old APIM is one of the reasons I learned so much about this.
Hey all,
Any chance I can come back from a bricked apim? Tried to update for logos and I did not work.
See the other thread you posted in…
Good morning to you. I have a question. For several cars, for example: Ford Ecosport 2018 with radio, nav and DAB, I updated to the latest version 3.4…351 or something. Also on the Custom Tourneo with radio and DAB. During this update, I see radio logos without any Forscan intervention.
I have a Ford S_max 2019, radio only. I can’t see the logos and my Forscan doesn’t have a firmware update. However, I see radio logos in the settings, I once enabled them using Forscan and it doesn’t do anything.
I’m interested in the possibility of enabling DAB radio using Forscan and actually getting radio logos?
Because two cars that have DAB logos have and have never had them before.
Thank you
Hi folks,
today I tried to get the radio logos in my car - so I need to flash the APIM. My current strategy (CAN, F188) is GB5T-14G374-CB - After Forscan updated the APIM with HB5T-14G374-CA my radio display in the car stays black (forscan comes up with a message programming error - Module is bricked) and in the display between the speedo and tach it says something like “lost communication with audio unit…” - I am able to flash back to GB5T-14G374-CB which brings back my unit to live - this is no problem…what can it be when the display stays black ? does anybody had the same problems ?
This hardware is too old to update to the latest firmware levels with reliable results and performance. Not that you can’t, but you probably shouldn’t. This is a common issue with the Gen 1 Sync units. The J and K series units are far more reliable.
Dear F150 Chief, Thx for the info - I try to find a newer (used) unit - is there something special I have to look for ??
Greets
Have you definitely got the Enh DAB logo package installed on the second vehicle? And is it definitely on the very latest sync 3 version?
Ideally, you want a unit from a MY18.5+ vehicle. This should be a unit with the part number beginning in Jxxx (4xxx) or Kxxx (5xxx) (Example: KU5T-14G371-GJA. This is the ECU Delivery Assembly Number.) These will most likely just work without any need for firmware updates. K series would be preferable. Always look at the build dates on the unit stickers.
A good place for reference is the hardware database here on the site.
You will probably want NAV, so look for 64GB units:
5U5T-14G371-GKC
5U5T-14G371-GKF
KU5T-14G371-GDE
KU5T-14G371-GFA
KU5T-14G371-GJA
You’re the man - thanks a lot !!!
I actually had 20282 or something and I updated to the last one:
CYANLABS - SYN3 UPDATER - V2.4.2.0
Branch: Release
Operating System: Microsoft Windows 10 Pro (2009)
PREVIOUS CONFIGURATION
Version: 3.4.20282
Region: EU
Navigation: False
Mode: autoinstall
DESTINATION DETAILS
Mode: Drive
Model: USB SanDisk 3.2Gen1 USB Device 28.6GB
FileSystem: exFAT
Partition Type: MBR
AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.x - Autoinstall Mode - Sync 3.4.20351 EU
[SYNCGen3.0_ALL_PRODUCT]
Item1 = ENH_DAB - 1U5T-14G658-AF_1598633324000.TAR.GZ
Open1 = SyncMyRide \ 1U5T-14G658-AF_1598633324000.TAR.GZ
Item2 = APPS - 5U5T-14G381-EM_1611967752000.TAR.GZ
Open2 = SyncMyRide \ 5U5T-14G381-EM_1611967752000.TAR.GZ
Item3 = VOICE - 5U5T-14G391-AM_1598633466000.TAR.GZ
Open3 = SyncMyRide \ 5U5T-14G391-AM_1598633466000.TAR.GZ
Options = AutoInstall
[SYNCGen3.0_ALL]
Item1 = GRACENOTES - 4U5T-14G423-AB_1598633764000.TAR.GZ
Open1 = SyncMyRide \ 4U5T-14G423-AB_1598633764000.TAR.GZ
Options = Delay, Include, Transaction
FILES (4)
1U5T-14G658-AF_1598633324000.TAR.GZ (58.8MB)
4U5T-14G423-AB_1598633764000.TAR.GZ (684.9MB)
5U5T-14G381-EM_1611967752000.TAR.GZ (848.6MB)
5U5T-14G391-AM_1598633466000.TAR.GZ (1.5GB)
LOG
[19.03.2021 19:12:50] Selected Region: EU - Release: Sync 3.4.20351 - Map Version: Bez Navigácie APIM
[19.03.2021 19:12:50] Install Mode: autoinstall
[19.03.2021 19:12:50] Checking Existing File: 1U5T-14G658-AF_1598633324000.TAR.GZ
[19.03.2021 19:12:50] Validated: 1U5T-14G658-AF_1598633324000.TAR.GZ (Skipping Download)
[19.03.2021 19:12:50] Checking Existing File: 4U5T-14G423-AB_1598633764000.TAR.GZ
[19.03.2021 19:12:53] Validated: 4U5T-14G423-AB_1598633764000.TAR.GZ (Skipping Download)
[19.03.2021 19:12:53] Checking Existing File: 5U5T-14G381-EM_1611967752000.TAR.GZ
[19.03.2021 19:12:57] Validated: 5U5T-14G381-EM_1611967752000.TAR.GZ (Skipping Download)
[19.03.2021 19:12:57] Checking Existing File: 5U5T-14G391-AM_1598633466000.TAR.GZ
[19.03.2021 19:13:05] Validated: 5U5T-14G391-AM_1598633466000.TAR.GZ (Skipping Download)
[19.03.2021 19:13:05] Preparing USB drive
[19.03.2021 19:13:05] Formatting USB drive
[19.03.2021 19:13:05] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[19.03.2021 19:13:13] Generating Autoinstall.lst
[19.03.2021 19:13:13] Checking Existing File: 1U5T-14G658-AF_1598633324000.TAR.GZ
[19.03.2021 19:13:13] Copying: 1U5T-14G658-AF_1598633324000.TAR.GZ
[19.03.2021 19:13:14] Validating: 1U5T-14G658-AF_1598633324000.TAR.GZ
[19.03.2021 19:13:14] Copied: 1U5T-14G658-AF_1598633324000.TAR.GZ
[19.03.2021 19:13:14] Checking Existing File: 4U5T-14G423-AB_1598633764000.TAR.GZ
[19.03.2021 19:13:14] Copying: 4U5T-14G423-AB_1598633764000.TAR.GZ
[19.03.2021 19:13:31] Validating: 4U5T-14G423-AB_1598633764000.TAR.GZ
[19.03.2021 19:13:34] Copied: 4U5T-14G423-AB_1598633764000.TAR.GZ
[19.03.2021 19:13:34] Checking Existing File: 5U5T-14G381-EM_1611967752000.TAR.GZ
[19.03.2021 19:13:34] Copying: 5U5T-14G381-EM_1611967752000.TAR.GZ
[19.03.2021 19:14:00] Validating: 5U5T-14G381-EM_1611967752000.TAR.GZ
[19.03.2021 19:14:04] Copied: 5U5T-14G381-EM_1611967752000.TAR.GZ
[19.03.2021 19:14:04] Checking Existing File: 5U5T-14G391-AM_1598633466000.TAR.GZ
[19.03.2021 19:14:04] Copying: 5U5T-14G391-AM_1598633466000.TAR.GZ
[19.03.2021 19:15:11] Validating: 5U5T-14G391-AM_1598633466000.TAR.GZ
[19.03.2021 19:15:17] Copied: 5U5T-14G391-AM_1598633466000.TAR.GZ
[19.03.2021 19:15:17] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
But still in the settings I see only enable logos, but I can’t. I don’t know, is it because I once allowed it for a test at Forscan? So should I turn it off there? : confused:
That’s why I asked to fool it by setting up DAB in Forscan.
Please download the latest beta of FORScan 2.4.3:
It should then give you the option to download firmware files. You will need a paid extended license. Note this is still an un-released beta and you will have little support from FORScan if the firmware update process fails.
Thanks I’ll try that tomorrow
