Attempted APIM update on my 2016 Fiesta ST utilizing FDRS. Programming failed at the end of the procedure & now the screen is solid black & no reponse to the APIM/ACM/FDCIM. USB ports are no longer illuminated as well. Disconnected battery for an entire day w/ no change. Attempted soft resets via FDCIM controls & module reset via FORSCAN. Is the APIM bricked w/ no chance of recovery or is there a way to salvage this? Unsure of exact Sync version I believe it was 2.2 or in that range.
Part Number via FORSCAN: CB5T-14G371-CFC
Calibration Number via FORSCAN: CB5T-14G371-CFC
SYNC Region: NA
Navigation Variant: Nav
Manufacturer Year: Pre MY20
Install Type: OEM
Old SYNC Version: 2.2
New SYNC Version: 2.2
Do you have a error message, if so what is it?
General lost communication codes stored in various modules.
I’m a dealer technician & the vehicle was not responding to a formatted Sync USB drive. So I performed a standard programming via FDRS & after block erase procedure programming failed resulting a now unresponsive unit. I should of used CyanLabs from the start considering all the issues I have w/ Ford software as is it. I’m trying to see if there is any back door methods or alternative procedures on this forum to possibly save the APIM. At this point all testing leads to a bricked APIM, thank you.
Are you sure that’s not Part Number via FORSCAN: GB5T-14G371-CFC?
If so, you are lucky to have a corrupted firmware file which can be restored. Since this is a 2016 APIM, not MY20+, you didn’t brick it to where it’s not recoverable, most likely anyways. I think you could use FRDS to do the following, FORScan is probably your best bet. You will need a paid licensed version to update the firmware.
If you look at the calibration and strategy files loaded on the APIM, you will likely find a GB5T-14G374-AF.VBF strategy file. The original GB5T-14G374-AF.VBF from Ford is broken, bad addresses. Use the file from FORScan support. Uploading strategy file GB5T-14G374-CB may brick the module. Solution is to upload GB5T-14G374-CD instead of GB5T-14G374-CB.
Look at the firmware load on the APIM and see if the -AF file is specified. It is used for NON-NAV units, but this procedure will work to fix NAV units also.
For NAV:
SBL: (shouldn’t have to change this) GB5T-14G376-AA.VBF
Strat: GB5T-14G374-CA.VBF (Use GB5T-14G374-CD to update)
Cal: GB5T-14G375-DA.VBF
For NON-NAV: (G-2016 thru H-2017)
SBL: (shouldn’t have to change this) GB5T-14G376-AA.VBF
Strat: GB5T-14G374-AF.VBF (Use GB5T-14G374-CD to update)
Cal: GB5T-14G375-BA.VBF (or -BB)
Keep in mind that the 2016 is supported by IDS, not completely by FDRS.
If I remember correctly when you flash a 2016/2017 APIM with FDRS you have to use a USB Ethernet adapter plugged into the car and a crossover Ethernet cable connecting it to the laptop.
Unable to gain access to module configuration due to no communication w/ the module. When trying to access Module Configuration the service procedure is interrupted & goes no further. I have attached a snippet of the fault. Any further recommendations?
I had Forscan set to AUTO for Baud rate. I went through & changed it to each setting w/ no change in outcome. I then went into StnFirmwareUpdater & updated my OBDLinkEx to the latest version & adjusted the Baud rate on that software on each setting w/ no change in effect. When attempting module configuration on a fresh Forscan session it does state a message regarding “Sync 1.” I assume this a normal warning message regarding module configuration & nothing more? I have attached a snippet of the message.
Changing connection type then reconnecting to the vehicle exhibits no change in outcome. I even changed it to J2534 Adapter & used my Ford VCM3. I’m unable to gain access to APIM configuration & programming. I suspect due to block delete process during Ford programming it completely wiped any memory stored on the APIM so now its essential a blank/dead module? Let me know what you think, thanks again
