ECU module programming guide using FDRS

[JaHoova]

K, forget my last response. What was wrong doing the APIM update? Failure, error popped up?

USB inserted and never kicked off. Have driven it multiple times, however have only given it a day or two vice the weeks some have given. Similar to what I've seen others experience. Eventually it is supposed to just kick off at some point and everything is good from there on out. My understanding from reading the TSB and looking at the procedure referenced by it in FDRS is 22-2117 resets APIM and TCU tables which is supposed to fix whatever is preventing 1.7.1 from starting from USB. I have the referenced symptoms:

• 2021 F-150/Mustang Mach-E
• Ford Power-Up software update failure message via the vehicle display or FordPass
• Inability to update the APIM or TCU using the FDRS and USB drive

Regarding:

I went back and looked through the 5 posts you made and saw this. Let me ask you a question, have you tried another 64GB USB stick maybe a USB 3.0 one?

I was probably a little hasty in posting that because it was very late at night. Traced that issue to bad wifi. Eventually FDRS downloaded all of the required files including the "error" ones and prompted me to create the USB. It's a 128GB USB 3.0 exFAT formatted with no files on it. Which is when nothing happened. I'll keep driving around with it inserted in the meantime and see if it finally goes.

Sponsored

 

[abd79]

For those on here that have made changes to different modules and had problems updating them what changes did you make and to what modules?

I think it would be a good idea to get a general consensus of the changes that should be reverted back to stock before doing any updates. Maybe captured in the guide as a warning and a prerequisite before proceeding?

 

[Bob_Mac]

For those on here that have made changes to different modules and had problems updating them what changes did you make and to what modules?

I think it would be a good idea to get a general consensus of the changes that should be reverted back to stock before doing any updates. Maybe captured in the guide as a warning and a prerequisite before proceeding?

It's going in my guide. Right now it's only limited to the IPC and APIM modules. I've tagged @Livnitup in a previous post as there have been several reported issues I helped resolve based on the error that popped up during the updates.

 

[Ajzride]

For those on here that have made changes to different modules and had problems updating them what changes did you make and to what modules?

I think it would be a good idea to get a general consensus of the changes that should be reverted back to stock before doing any updates. Maybe captured in the guide as a warning and a prerequisite before proceeding?

i believe the one that hit me was changing the IPC to prevent the truck from turning off after 30 minutes idle in park.

 

[imnuts]

After seeing the last several pages of posts, I feel like I should get some lottery tickets. I didn't undo any FORScan changes before updating anything and other than a U2100 DTC after the IPC update that cleared after a single PMI, I didn't run into any other issues. The last APIM update did undo some FORScan mods I did, but they were ready enough to redo.

 

[Shoebox72069]

After seeing the last several pages of posts, I feel like I should get some lottery tickets. I didn't undo any FORScan changes before updating anything and other than a U2100 DTC after the IPC update that cleared after a single PMI, I didn't run into any other issues. The last APIM update did undo some FORScan mods I did, but they were ready enough to redo.

I feel like dealing with a U2100 on the IPC is like trying to figure out a cat.

I tried 3 PMI's with no joy. The IPC update DID allow a TCU/GWY update. Once I updated the GWY after the TCU, my U2100 went away.

Ironically my Mongoose showed up today and I'm in the midst of another IPC update...

 

[Snakebitten]

Ironically my Mongoose showed up today and I'm in the midst of another IPC update...

The good news is that with the Mongoose, you are standing at the plate with a bat that is capable of batting 1000
It's so much nicer knowing that you can use FDRS without avoiding network scans.

Just don't rush FDRS each time you cycle the key off/on. Let the network wake up and finish all the handshakes before any mouse clicks on the laptop.

 

[Shoebox72069]

The good news is that with the Mongoose, you are standing at the plate with a bat that is capable of batting 1000
It's so much nicer knowing that you can use FDRS without avoiding network scans.

Just don't rush FDRS each time you cycle the key off/on. Let the network wake up and finish all the handshakes before any mouse clicks on the laptop.

I'm debating keeping mine once its all topped off. I'd think there will be "updates" even for things that don't get tickled by the OTA.

My Mongoose was opened but that seemed to be the consensus... and it's working so no complaints here.

 

[Snakebitten]

I will not be caught dead without a mongoose for the rest of my Ford ownership life. ?

 

[christophers]

I'll add in a bit of info on the 1.7.1 TSB that just came out.

there were a few of us that waited nearly a full month (i was 30 days exactly) from putting the APIM USB in the console and having it actually kick off the update.

my guess what some are going to do is, instead of wait one month (especially those with shorter FDRS licenses) people will try to "force" the 1.7.1 so they can proceed with the other updates.

just my two cents as someone who purchased a few day license and had to buy another one.

 

[christophers]

The good news is that with the Mongoose, you are standing at the plate with a bat that is capable of batting 1000
It's so much nicer knowing that you can use FDRS without avoiding network scans.

Just don't rush FDRS each time you cycle the key off/on. Let the network wake up and finish all the handshakes before any mouse clicks on the laptop.

this is the key. i had zero issues and i followed the "slow and steady" process.

i'll also note i had lots of forscan changes that i didn't re-apply via backups (nor did i even re-apply them manually) and i think everything stayed (adaptive headlights, bambi mode, seat belt minders, and a few others)

 

[Slappy McGee]

I'll add in a bit of info on the 1.7.1 TSB that just came out.

there were a few of us that waited nearly a full month (i was 30 days exactly) from putting the APIM USB in the console and having it actually kick off the update.

my guess what some are going to do is, instead of wait one month (especially those with shorter FDRS licenses) people will try to "force" the 1.7.1 so they can proceed with the other updates.

just my two cents as someone who purchased a few day license and had to buy another one.

This is the boat I'm sitting in. Sit around waiting for (potentially) a month with a USB stick, fearing that I'll somehow miss the "magic button" while backing up, using Nav, or doing things that one would normally do in a vehicle versus buying more goofy cables, FDRS licenses, and tollerating the sad looks from my wife and kids when they walk by and we have this conversation:

FAM: "What are you doing?!??!"
ME: "Trying to get the truck to do stuff that I paid for that doesn't actually work."
FAM: "Can't the dealer fix it?"
ME: "No."
FAM: "How long will this take?"
ME: "The internet says somewhere between 5 hours and 30 days"
FAM: "Do you actually know what you're doing?"
ME: "Nope!"

 

[Jaug]

I have completed all updates and everything looks good for module data. When I go to the widget and look at the OTA Info it just has my schedule now. It used to have that and the failed 1.7.1 update info there. I am wondering if Ford now has me as fully updated in their servers and ready to receive future OTAs now. I am kinda hoping for a regular OTA to start coming out so I can test to see if I can receive OTAs again.

 

[christophers]

I have completed all updates and everything looks good for module data. When I go to the widget and look at the OTA Info it just has my schedule now. It used to have that and the failed 1.7.1 update info there. I am wondering if Ford now has me as fully updated in their servers and ready to receive future OTAs now. I am kinda hoping for a regular OTA to start coming out so I can test to see if I can receive OTAs agai.

i dont know that we have that answer yet. but one day, you'll either 1) get an update notification, or 2) see someone else here that is getting OTAs, so we will have the answer soon enough

 

[Ajzride]

Now run a PMI on the IPC and report back.

PMI of IPC still fails. Software Part number is still incorrect by one letter (-CPB instead of -CPC)

I had a backup of my IPC from stock. I went through every bit and made sure there are no more forecan changes.

EDIT:

My Forscan changes keep repopulating themselves somehow.

EDIT EDIT:

It appears running "Module Configuration" Was what restored my changes. I won't be running that again.

EDIT EDIT EDIT

You know you are screwed when all of your google searches lead you back to your own forum posts.

Sponsored