Need help recovering a bricked 2023 replacement APIM (JK2T-14G371-BDB) after non-MY20 reformat

Hello everyone,

I’m looking for some advice before I make things worse.

Vehicle

  • 2018 Ford EcoSport (GCC/UAE)
  • Originally fitted with SYNC 3

APIM

  • Part Number: JK2T-14G371-BDB
  • Manufacturing Date: 26-Jul-2023
  • This appears to be a replacement APIM, not the original 2018 module.

What happened

I attempted to update the APIM and did not select the MY20 option because I assumed my 2018 vehicle used pre-MY20 hardware.

After the update, the APIM became unresponsive.

Current status

  • Black screen
  • FORScan previously communicated with the APIM, but it no longer boots normally.
  • I removed the APIM from the vehicle.
  • Installed Ubuntu 22.04 LTS.
  • Successfully built bigunclemax’s sync3flash.
  • Obtained MLO and QNX-IFS-REFORMAT.
  • Connected the APIM via direct Mini-USB.
  • Used the recovery pad (V31 → GND) procedure from the GitHub guide.

However, sync3flash remains at “Waiting for device…”.

Running lsusb in Ubuntu never shows the APIM as a USB device.

My questions

  1. Is JK2T-14G371-BDB (manufactured July 2023) considered a MY20+ APIM?
  2. Could selecting the non-MY20 reformat have bricked this newer hardware?
  3. Does this APIM require a different MLO or patched QNX-IFS-REFORMAT than older Sync 3 APIMs?
  4. Has anyone successfully recovered this exact APIM revision with sync3flash?
  5. Are the V31/GND recovery pads the same on this board revision, or did Ford change them on later hardware?

Any guidance or recovery files specific to this APIM revision would be greatly appreciated.

Thank you!


SYNC Region: ROW

Navigation Variant: Non Nav

Manufacturer Year: MY20

Install Type: OEM

Old SYNC Version: 3.20204

New SYNC Version: 3.4

Do you have a error message, if so what is it?
Black screen not tuning on i guess

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: Latest one

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

Na

My answers:

  1. Are you really asking if a unit from 2023 is considered 2020+? :slight_smile:
  2. Yep, as clearly warned in many / multiple places
  3. No that I know
  4. Since we do not support the 3rd party tool, it’s hard to say.
  5. Since we do not support the 3rd party tool, it’s hard to say.

I think it’s better for you to contact the creator of the tool.