Need help! Tried updating BdyCM firmware, it failed

Ford Other Support
, , ,
1

I have a ELS27 4.0 and I tried flashing the BdyCM firmware on my '19 Fusion Sport and it failed. Tried going back to factory, but that didn’t work either. I fear I have bricked my car.

Two little side displays on the instrument panel come on and nothing else. Any ideas on what I can I do to fix this?

(OK) [12:38:10.708] APIM Module firmware update has been started
(WARN) [12:38:10.722] Reading vehicle info…
(WARN) [12:38:33.252] Downloading firmware files from the Internet…
(OK) [12:38:35.292] Downloading GB5T-14G376-AA: OK
(WARN) [12:38:59.747] Downloading files from the Internet…
(OK) [12:39:02.808] Downloading 3FA6P0VP7KR164222.ab: OK
(WARN) [12:39:03.831] Loading and parsing factory As Built file…
(WARN) [12:39:43.155] Total size: 1.3 Kb. Estimated duration: ~1m
(WARN) [12:39:52.035] Loading SBL to primary module…
(WARN) [12:39:53.131] Loading block 1/1…
(OK) [12:39:53.294] SBL loaded successfully
(OK) [12:39:53.659] Service procedure completed successfully.
(OK) [12:40:12.934] APIM Module firmware update has been started
(WARN) [12:40:12.945] Reading vehicle info…
(OK) [12:40:32.594] No changes, nothing to do
(OK) [12:40:32.596] Service procedure completed successfully.
(OK) [12:41:07.713] PAM Module firmware update has been started
(WARN) [12:41:07.720] Reading vehicle info…
(WARN) [12:41:13.766] Unable to read current firmware p/n, use stored in profile: FU5T-14C090-BL
(WARN) [12:41:15.627] Unable to read current firmware p/n, use stored in profile: HS7T-14C647-VB
(OK) [12:41:44.834] Service procedure completed successfully.
(OK) [12:42:01.751] BdyCM Module firmware update has been started
(WARN) [12:42:01.760] Reading vehicle info…
(WARN) [12:42:45.248] Downloading firmware files from the Internet…
(OK) [12:42:49.321] Downloading JU5T-14C184-AAN: OK
(OK) [12:42:49.337] Downloading KS7T-14F390-BAD: OK
(OK) [12:42:49.353] Downloading KS7T-14G163-DAD: OK
(WARN) [12:43:30.227] Total size: 752 b. Estimated duration: ~1m
(WARN) [12:43:40.594] Loading SBL to primary module…
(WARN) [12:43:41.303] Loading block 1/1…
(OK) [12:43:41.437] SBL loaded successfully
(OK) [12:43:42.420] Service procedure completed successfully.
(OK) [12:43:53.726] BdyCM Module firmware update has been started
(WARN) [12:43:53.739] Reading vehicle info…
(WARN) [12:44:31.856] Total size: 1.45 Mb. Estimated duration: 2m - 4m
(WARN) [12:44:34.707] Loading SBL to primary module…
(WARN) [12:44:35.451] Loading block 1/1…
(OK) [12:44:35.554] SBL loaded successfully
(WARN) [12:44:35.627] Loading firmware to ECU: Strategy JU5T-14C184-AAN
(WARN) [12:44:35.630] Erasing block 1/2…
(WARN) [12:44:35.889] Erasing block 2/2…
(WARN) [12:44:41.913] Loading block 1/2…
(WARN) [12:44:44.870] Operation failed, retrying…
(ERR) [12:44:48.837] Loading firmware failed
(ERR) [12:44:49.813] Service procedure has been interrupted
(OK) [12:47:40.419] BdyCM Module firmware update has been started
(WARN) [12:47:40.437] Reading vehicle info…
(WARN) [12:47:41.897] Unable to read current firmware p/n, use stored in profile: JU5T-14C184-AAK
(WARN) [12:47:41.904] Unable to read current firmware p/n, use stored in profile: KP5T-14F389-DA
(WARN) [12:47:41.912] Unable to read current firmware p/n, use stored in profile: JU5T-14F391-AAB
(WARN) [12:47:41.913] Unable to read current firmware p/n, use stored in profile: KS7T-14G162-EA
(WARN) [12:47:41.921] Unable to read current firmware p/n, use stored in profile: KS7T-14C636-AGD
(WARN) [12:47:41.922] Unable to read current firmware p/n, use stored in profile: KS7T-14F390-BAC
(WARN) [12:47:41.932] Unable to read current firmware p/n, use stored in profile: KS7T-14G163-DAC
(WARN) [12:47:50.164] Loading and parsing factory As Built file…
(WARN) [12:47:59.219] Downloading firmware files from the Internet…
(OK) [12:48:02.281] Downloading JU5T-14C184-AAK: OK
(OK) [12:48:03.298] Downloading KP5T-14F389-DA: OK
(OK) [12:48:03.368] Downloading JU5T-14F391-AAB: OK
(OK) [12:48:03.383] Downloading KS7T-14G162-EA: OK
(OK) [12:48:03.398] Downloading KS7T-14C636-AGD: OK
(OK) [12:48:04.370] Downloading KS7T-14F390-BAC: OK
(OK) [12:48:04.453] Downloading KS7T-14G163-DAC: OK
(WARN) [12:48:44.526] Total size: 752 b. Estimated duration: ~1m
(WARN) [12:48:47.037] Loading SBL to primary module…
(WARN) [12:48:47.800] Loading block 1/1…
(OK) [12:48:47.926] SBL loaded successfully
(OK) [12:48:48.293] Service procedure completed successfully.
(OK) [12:49:13.679] BdyCM Module firmware update has been started
(WARN) [12:49:13.692] Reading vehicle info…
(WARN) [12:49:14.336] Unable to read current firmware p/n, use stored in profile: JU5T-14C184-AAK
(WARN) [12:49:14.369] Unable to read current firmware p/n, use stored in profile: KP5T-14F389-DA
(WARN) [12:49:14.394] Unable to read current firmware p/n, use stored in profile: JU5T-14F391-AAB
(WARN) [12:49:14.418] Unable to read current firmware p/n, use stored in profile: KS7T-14G162-EA
(WARN) [12:49:14.442] Unable to read current firmware p/n, use stored in profile: KS7T-14C636-AGD
(WARN) [12:49:14.469] Unable to read current firmware p/n, use stored in profile: KS7T-14F390-BAC
(WARN) [12:49:14.502] Unable to read current firmware p/n, use stored in profile: KS7T-14G163-DAC
(WARN) [12:49:22.891] Loading and parsing factory As Built file…
(WARN) [12:49:40.763] Total size: 1.47 Mb. Estimated duration: 2m - 4m
(WARN) [12:49:44.191] Loading SBL to primary module…
(WARN) [12:49:44.891] Loading block 1/1…
(OK) [12:49:45.032] SBL loaded successfully
(WARN) [12:49:45.167] Loading firmware to ECU: Strategy JU5T-14C184-AAK
(WARN) [12:49:45.170] Erasing block 1/2…
(WARN) [12:49:45.433] Erasing block 2/2…
(WARN) [12:49:51.485] Loading block 1/2…
(WARN) [12:49:53.828] Operation failed, retrying…
(ERR) [12:49:57.797] Loading firmware failed
(ERR) [12:49:58.798] Service procedure has been interrupted
(OK) [12:50:08.686] BdyCM Module firmware update has been started
(WARN) [12:50:08.695] Reading vehicle info…
(WARN) [12:50:09.384] Unable to read current firmware p/n, use stored in profile: JU5T-14C184-AAK
(WARN) [12:50:09.419] Unable to read current firmware p/n, use stored in profile: KP5T-14F389-DA
(WARN) [12:50:09.445] Unable to read current firmware p/n, use stored in profile: JU5T-14F391-AAB
(WARN) [12:50:09.471] Unable to read current firmware p/n, use stored in profile: KS7T-14G162-EA
(WARN) [12:50:09.499] Unable to read current firmware p/n, use stored in profile: KS7T-14C636-AGD
(WARN) [12:50:09.523] Unable to read current firmware p/n, use stored in profile: KS7T-14F390-BAC
(WARN) [12:50:09.550] Unable to read current firmware p/n, use stored in profile: KS7T-14G163-DAC
(WARN) [12:50:24.758] Total size: 1.47 Mb. Estimated duration: 2m - 4m
(WARN) [12:50:27.459] Loading SBL to primary module…
(WARN) [12:50:27.698] Loading block 1/1…
(WARN) [12:50:30.567] Operation failed, retrying…
(WARN) [12:50:33.544] Loading block 1/1…
(WARN) [12:50:35.813] Operation failed, retrying…
(ERR) [12:50:39.162] Loading SBL failed
(ERR) [12:50:39.439] Service procedure has been interrupted

2

OK I fixed it myself.

Followed advice on forscan troubleshooting page. Waited a few hours with the battery disconnected. Attached a battery charger and tried again (factory this time). This time it flashed.

I no longer have a 4000lb paperweight in my driveway.

3

I read the additional post about the fix. You should ALWAYS use a battery charger when flashing firmware. This is specified by FORScan in the tutorial. In this case this was likely the issue.

Additionally…
Which ELS27 (STN1170/2120) adapter do you have?
ELS27 4.0 is not listed specifically by FORScan as supported, although the article is older. There are warnings about clones of these.
Attention - bad clone of ELS27 - FORScan forum

4

Thanks for the update. I was in panic mode for a bit so I walked away and was able to solve the problem.

As for the ELS27, it is a real one ordered direct from the company and it is on the recommended list along with the 5.6.5 firmware

  1. There are still enough users trying to use non-recommended adapters. Currently recommended adapters for version 2.4 are OBDLink EX, ELS27 (with firmware 5.6.5 or newer), vLinker FS.

I also own an OBDLink EX but my kid “borrowed” it.

And finally, yes the charger was on the car the first time, but the extension cord wasn’t actually plugged in.

Again thanks for replying

5

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