Bricked APIM with 2.4.4

[Deathmachine]

Sticker on the back of my apim is model 14g370 mfg date 10/29/2016 hl3t-14g370-gcd

Forscan 2.4.4 screen before flash

brick.png (54.76 KiB) Viewed 5883 times

I downloaded the factory and new files
Firmware updated crashed...
reload of orginal files crashed
tried recovery crashed.

By chance are the Forscan files listed wrong for my apim. If so what are the correct ones and how do I get them to fix this. Or have I destroyed a $500 dollar module with a $20 piece of software?

D.

[fordsmax471]

if the car profile is still there, we can try
what cable do you have

[Deathmachine]

OBDLink EX FORScan OBD Adapter

[Deathmachine]

100% props for the quick support and help fixing my APIM. I seems it was my fault as I did not pay close enough attention to the connection settings and the windows driver settings. After getting that sorted out the firmware flash and the Apim came back to life.. Again thanks

[Focus-MK4]

Can you explain what settings exactly were wrong?

[fordsmax471]

Can you explain what settings exactly were wrong?

FORScan connection settings:

OBDLink® EX USB
connection type "FTDI"
FTDI driver settings: latency timer (msec) "1 or 2"
all other settings "AUTO" , not automatic connection
ticked the "Auto -increase"
ticked the "Debug mode"

[pfeilmayer]

Sticker on the back of my apim is model 14g370 mfg date 10/29/2016 hl3t-14g370-gcd

Forscan 2.4.4 screen before flash
brick.png

I downloaded the factory and new files
Firmware updated crashed...
reload of orginal files crashed
tried recovery crashed.

By chance are the Forscan files listed wrong for my apim. If so what are the correct ones and how do I get them to fix this. Or have I destroyed a $500 dollar module with a $20 piece of software?

D.

viewtopic.php?p=58692#p58692

[davetcollection]

Can you explain what settings exactly were wrong?

FORScan connection settings:

OBDLink® EX USB
connection type "FTDI"
FTDI driver settings: latency timer (msec) "1 or 2"
all other settings "AUTO" , not automatic connection
ticked the "Auto -increase"
ticked the "Debug mode"

Is that list everything that was wrong with his connection settings, or what it should be?

[mmorey79]

Can you explain what settings exactly were wrong?

FORScan connection settings:

OBDLink® EX USB
connection type "FTDI"
FTDI driver settings: latency timer (msec) "1 or 2"
all other settings "AUTO" , not automatic connection
ticked the "Auto -increase"
ticked the "Debug mode"

Is that list everything that was wrong with his connection settings, or what it should be?

That's the standard answer for "correct" settings. Need to open the COM port for the FTDI in device manager and set 1-2 msec and the auto increase for baudrate, otherwise flashes fail due to timeouts etc. As long as you don't delete your vehicle profile before ensuring all modules are up and running you'll be ok in most cases, ford isn't in the blowing stuff up business even at the dealer and things do go wrong there too so they tend to still be able to take a flash at a low level even after a bad attempt. I blew up a BodyCM in our Fusion the other day and spent a couple hours thinking I had ruined the car, then had some hope when I figured out how cheap a BodyCM was, then finally got things straightened out after a second programming attempt with the faster settings.

[spcaa]

Sticker on the back of my apim is model 14g370 mfg date 10/29/2016 hl3t-14g370-gcd

Forscan 2.4.4 screen before flash
brick.png

I downloaded the factory and new files
Firmware updated crashed...
reload of orginal files crashed
tried recovery crashed.

By chance are the Forscan files listed wrong for my apim. If so what are the correct ones and how do I get them to fix this. Or have I destroyed a $500 dollar module with a $20 piece of software?

D.

Try to install older version of Forscan like 2.4.3 or 2.4.1 and program all files without ECU/Configuration/Illumination Strategy.