ECU module programming guide using FDRS

[rugedraw]

To 2021 owners on the the broken Sync (20262, 20301, 20301 or blank Sync) and want to get it out of OTA purgatory:

There is currently an issue where once you get to Sync 22087, the APIM can no longer be updated. As of this past week, 4 different truck owners have embarked on this journey and all have hit the same wall once they get to Sync 22087. I have made Ford aware of the issue, but there is no time line as to when this will be "fixed".

Does it apply to ALL 2021 trucks? I have no idea. But 4 trucks in one week all getting stuck in the same exact Sync version is more than a coincidence.

@Cleandetail93 @JDJ89 @4 Fan Flyer

@pdubs (F150forum)

Sponsored

 

[digitaltrucker]

To 2021 owners on the the broken Sync (20262, 20301, 20301 or blank Sync) and want to get it out of OTA purgatory:

There is currently an issue where once you get to Sync 22087, the APIM can no longer be updated. As of this past week, 4 different truck owners have embarked on this journey and all have hit the same wall once they get to Sync 22087. I have made Ford aware of the issue, but there is no time line as to when this will be "fixed".

Does it apply to ALL 2021 trucks? I have no idea. But 4 trucks in one week all getting stuck in the same exact Sync version is more than a coincidence.

@Cleandetail93 @JDJ89 @4 Fan Flyer

@pdubs (F150forum)

But for someone like me already at 24127, that does not apply right?

 

[rugedraw]

But for someone like me already at 24127, that does not apply right?

Correct. As long as you have updates showing for the sync modules, you should be able to do them.

 

[PDubs]

@rugedraw made it over, thanks for looping me in here. Will monitor this thread and abandon the other.

 

[SilverPigeon]

To expand a little for those on APIMs at or earlier than 23187:

 

[rugedraw]

To expand a little for those on APIMs at or earlier than 23187:

This is not the problem with them; at least not yet. FDRS shows a pending update for the APIM for them, but it fails to install. Fdrs specifically says there are more updates for the APIM, TCU, GWM and IPC once the APIM is updated.

With the exception of one truck, they all show a pending APIM update and the one truck that doesn't show a pending APIM update may have a bad APIM.

 

[SilverPigeon]

I'm betting it still applies, just that ford haven't done proper "housekeeping" to remove it and those updates with which it is a dependency from the list of available

 

[Cleandetail93]

To 2021 owners on the the broken Sync (20262, 20301, 20301 or blank Sync) and want to get it out of OTA purgatory:

There is currently an issue where once you get to Sync 22087, the APIM can no longer be updated. As of this past week, 4 different truck owners have embarked on this journey and all have hit the same wall once they get to Sync 22087. I have made Ford aware of the issue, but there is no time line as to when this will be "fixed".

Does it apply to ALL 2021 trucks? I have no idea. But 4 trucks in one week all getting stuck in the same exact Sync version is more than a coincidence.

@Cleandetail93 @JDJ89 @4 Fan Flyer

@pdubs (F150forum)

Appreciate all of your efforts to help us. Hopefully we have a resolution sooner than later. It’s unfortunate that the price to attempt anything in FDRS nearly doubled. If there’s any info I can help with let me know!

 

[rugedraw]

In the case of @4 Fan Flyer , he was able to get over the hump and is not on Sync 22293. He pulled the negative cable from the battery for 20 minutes and reconnected. Tried running the APIM update again and told FDRS the APIM update had gone through. This cleared the APIM from the SW updates tab and released and IPC and GWM for him.

@4 Fan Flyer Did your truck show it was Sync 22177 immediately after the battery pull or after you ran the APIM update again? Please share your experience here to see if it helps these other guys out.

@Cleandetail93 More than doubled. In your case, it may be a bad APIM. Not sure if it is worth spending $120 to try this. Did you try a battery disconnect when you were going through this and your license was active?

 

[Snakebitten]

The increase in FDRS subscriptions isn't good news, of course. Especially if it's described as more than doubling.

Still, 48-72 hours of FDRS access co$t le$$ than 1 hour of service labor.

It's all how you choose to look at it.

 

[4 Fan Flyer]

In the case of @4 Fan Flyer , he was able to get over the hump and is not on Sync 22293. He pulled the negative cable from the battery for 20 minutes and reconnected. Tried running the APIM update again and told FDRS the APIM update had gone through. This cleared the APIM from the SW updates tab and released and IPC and GWM for him.

@4 Fan Flyer Did your truck show it was Sync 22177 immediately after the battery pull or after you ran the APIM update again? Please share your experience here to see if it helps these other guys out.

@Cleandetail93 More than doubled. In your case, it may be a bad APIM. Not sure if it is worth spending $120 to try this. Did you try a battery disconnect when you were going through this and your license was active?

I went through this just now with some help from rugedraw. I read the first few pages this forum thread, and the last 5 pages. I definitely wasn’t reading all 1089 pages. The FDRS purchase and login has changed somewhat in the past few weeks. Make sure you download the .6.8 version, it’s a little bit lower on the download page (sorry don’t have a picture)

I had to go through 3 APIM updates over a several hour period this evening. I went from no version, to 22087, then to 22177, then 22293 (a 5gb update!) which gave me full screen car play. After the 22087 update rugedraw advised me to pull the negative battery terminal and let the truck sit for 20 min. I don’t know if this did the trick, or if something happened in the background that triggered FDRS to push several more updates. Sorry, I wasn’t paying attention enough to notice if the sync version read 22177 immediately after the battery pull.

I did not run the engine as FDRS advised for the updates, just left the truck hooked up to a power supply. Each APIM update took about an hour to complete, except 22293 which took almost 3hrs. 22293 took about 45 minutes just to download, another 15 to write to the memory card, then I let the usb stick sit in the car with the ignition on for about 2hrs. The update triggered as normal, but eventually the truck went to “sleep” except for a small banner on top of the main screen that said “update in progress”. I let the truck sit until this banner disappeared about 2hrs later.

When it was done I turned the truck on, the font for the sync screen looked significantly different and I had the option for full screen CarPlay.

 

[rugedraw]

I did not run the engine as FDRS advised for the updates, just left the truck hooked up to a power supply. Each APIM update took about an hour to complete, except 22293 which took almost 3hrs. 22293 took about 45 minutes just to download, another 15 to write to the memory card, then I let the usb stick sit in the car with the ignition on for about 2hrs. The update triggered as normal, but eventually the truck went to “sleep” except for a small banner on top of the main screen that said “update in progress”. I let the truck sit until this banner disappeared about 2hrs later.

.

This part is interesting. I had no idea the update would continue in the background if the ignition went off. Glad it worked for you. As far as the other guys, unfortunately, it will now cost you $120 to try. Plus, I would need to send one of the Mongoose back to you to try if you were borrowing one.

 

[JDJ89]

After getting stuck at 22087, I decided to just go for it and give the above a try this morning. I removed the negative battery cable for 20 minutes, purchased the 2 day subscription, reconnected and low and behold it worked! I had another APIM update or two and a couple GWM and TCU updates that went through without a hitch.

About 2 hours later I was up to 22293 and after that there was no other APIM, GWM, TCU or IPC updates presented. I had several other modules that had updates and have completed all those except for the sccm, CCm and pcsm. I plan to tackle those when I get back this afternoon as they will take a little bit longer to complete.

I'm assuming after those are done and no other updates are showing on the SW updates tab that I will be as updated as I can be for now. I’m glad to at least be able to have full screen car play now and have other modules updated that needed it!

 

[rugedraw]

After getting stuck at 22087, I decided to just go for it and give the above a try this morning. I removed the negative battery cable for 20 minutes, purchased the 2 day subscription, reconnected and low and behold it worked! I had another APIM update or two and a couple GWM and TCU updates that went through without a hitch.

About 2 hours later I was up to 22293 and after that there was no other APIM, GWM, TCU or IPC updates presented. I had several other modules that had updates and have completed all those except for the sccm, CCm and pcsm. I plan to tackle those when I get back this afternoon as they will take a little bit longer to complete.

I'm assuming after those are done and no other updates are showing on the SW updates tab that I will be as updated as I can be for now. I’m glad to at least be able to have full screen car play now and have other modules updated that needed it!

Correct. If you are on Sync 22293 and had nothing else showing, then the SSM that @SilverPigeon posted earlier applies to you at this point.

Question: All you did was disconnect the battery and reconnected it and when you fired up FDRS, you just ran the APIM update procedure from the beginning and it worked? You didn't have to tell FDRS the update went through even though it didn't?

 

[JDJ89]

Correct. If you are on Sync 22293 and had nothing else showing, then the SSM that @SilverPigeon posted earlier applies to you at this point.

Question: All you did was disconnect the battery and reconnected it and when you fired up FDRS, you just ran the APIM update procedure from the beginning and it worked? You didn't have to tell FDRS the update went through even though it didn't?

That’s correct. FDRS just ran the APIM update as it would have normally, no error messages or anything. I didn’t have to do anything any different from the normal procedure.

Sponsored