ECU module programming guide using FDRS

[rugedraw]

I have an early build 2021 F150 that’s stuck on an old SYNC version with the version/revision fields showing blank. After being failed by my dealer and reading through the last ~100 pages of this thread, I decided to try fixing it myself with a Mongoose cable and an FDRS subscription. I’m now stuck and could use some guidance.


What I’ve done so far:

• FDRS showed a pending APIM update (nothing for GWM, but there were many others that I decided to wait on until the APIM is at least unstuck).
• I connected the truck to a 20A power supply and ran the APIM update.
• After a long download, FDRS prompted me to insert a USB drive. I used a 32GB SanDisk formatted exFAT and named “FDRS.”
• Plugged into the truck, the update immediately started and later asked for a restart.
• I let the truck sit 10+ minutes, then restarted and sat for 10+ min. I never got an “update successful” message, but FDRS asked whether it succeeded. I clicked “yes,” and FDRS then indicated the update failed.

I tried again with a freshly formatted USB drive. The download was much faster, but the update didn’t start right away. A couple days later, during my drive to work, the truck finally reported that an update was in progress. It finished, asked for a restart, and I let it sit for a few hours before restarting. Again, no confirmation message. It’s now been a few days, the USB is still plugged in, and SYNC still shows blank version/revision fields, so it seems like the update didn’t take.

My 2 day FDRS subscription has expired, so I can’t check anything further there. I’m unsure whether I should wait to see if the truck eventually reports success/failure or go ahead and renew FDRS and attempt the APIM update again.

I’ve also seen that disconnecting the negative battery terminal for 20+ minutes might help SYNC recognize the update or at least refresh the version reporting. Maybe I should try that next...


If anyone has advice, I’d really appreciate it. This forum has been incredibly helpful, especially after getting nowhere with my dealer.

Thanks in advance.

USB will most likely have be left in there for weeks before the apim will update. It's a normal part of the process for trucks on your situation. You can update the other modules showing for now. Once the apim update goes through, you need another fdrs license and you'll be and to update the GWM, TCU, APIM and IPC. Maybe not to the most current version, but well past where you are now.

Sponsored

 

[joeco]

Have you verified that the Sync version didn't change?
And also try a Sync reset just in case it's hung up?

the sync version is still blank. I did try a reset via holding the power button and forward button for 10 seconds. I have not tried a master reset yet.

 

[joeco]

USB will most likely have be left in there for weeks before the apim will update. It's a normal part of the process for trucks on your situation. You can update the other modules showing for now. Once the apim update goes through, you need another fdrs license and you'll be and to update the GWM, TCU, APIM and IPC. Maybe not to the most current version, but well past where you are now.

Copy, thanks. As long as I can get full screen CarPlay at some point, I’ll be satisfied.

 

[rugedraw]

Copy, thanks. As long as I can get full screen CarPlay at some point, I’ll be satisfied.

Worse case scenario, it will only let you update up to sync 22293 which is the version that gives you exactly that. Just be patient..... drive it like you would every day and when you least expect it, you'll get a message about the update wanting to go through.

I would also at some point after you're done with FRDS, disconnect the negative cable of the 12v battery (or both 12v batteries if it's a powerboost) for 20 minutes jic that helps with the process down the line. I don't think that will help the update take any sooner, but it won't hurt to try.

 

[jtrimm]

I’m having a hard time getting FDRS module updates to succeed on my 2023 F-150 Powerboost Lariat 502A. Power keeps cutting out in the truck every time a module update is attempted, regardless of what module Is updated. Full details in this thread: https://www.f150gen14.com/forum/thr...fail-with-power-cutout-as-flash-begins.44708/

Reaching out for any suggestions and advice before my sanity slips away. I’m banging my head against the wall on this one… -Jeff

 

[joeco]

So while waiting for the “update successful”, the truck prompted another “update in progress” with a restart required on my drive home today. I shut the truck off, opened the door, and let it sit for 10+ min before restarting. I let it idle in the driveway for 30+ min with no update successful or fail message. The sync version and revision have remained blank at all times. I have yet to remove the USB drive from the truck.

I seem to be stuck in this loop…

What should I try next? Options that seem viable are 1) sync master reset, 2) disconnect negative terminal of battery for 20+ min (non PB) and restart, or 3) buy another FDRS 2 day license to do PMI on the APIM and select no for original equipment.

Any suggestions or other ideas?

 

[SilverPigeon]

In terms of least to most inconvenient and costly:
1. Disconnect the battery
2. Sync master reset
3. Try FDRS again. But before doing so, see if @rugedraw can shed any light on the truck reporting any status to the ford servers.

 

[rugedraw]

@joeco Did you see USB error message on the screen at any time? If so, what number did it show? 0? 6?

@jtrimm Did you try the 20 minute battery disconnect?

 

[joeco]

@joeco Did you see USB error message on the screen at any time? If so, what number did it show? 0? 6?

@jtrimm Did you try the 20 minute battery disconnect?

No, never saw a USB error.

If it’s helpful context, when the update in progress initiates, it says downloading 36 files.

 

[rugedraw]

No, never saw a USB error.

If it’s helpful context, when the update in progress initiates, it says downloading 36 files.

I don't remember how many files are in the update. I think both a master reset and the battery trick and worth a shot. After you do the master reset, do not pair your phone or do anything. Leave as much space on the APIM as possible to help the update go through.

If it USB error 0, the APIM either has no space or there is hardware/software mismatch. The only thing you can try would be to make the USB update with FDRS again, but remove the voice files first to make more room in the APIM. If you still get USB error 0, then your APIM may be one of the rare ones that is actually f*cked and needs to be replaced.

If you get USB error 6, then you need a new 12v battery for it to install.

 

[bigbearbruin]

I don't remember how many files are in the update. I think both a master reset and the battery trick and worth a shot. After you do the master reset, do not pair your phone or do anything. Leave as much space on the APIM as possible to help the update go through.

If it USB error 0, the APIM either has no space or there is hardware/software mismatch. The only thing you can try would be to make the USB update with FDRS again, but remove the voice files first to make more room in the APIM. If you still get USB error 0, then your APIM may be one of the rare ones that is actually f*cked and needs to be replaced.

If you get USB error 6, then you need a new 12v battery for it to install.

Would manually removing the voice files through FDRS help force along the update?

 

[rugedraw]

Would manually removing the voice files through FDRS help force along the update?

If the reason the update is failing is due to lack of space, then yes. I've seen it go through without removing the voice files and I've seen cases where they have to be removed. You never know what you're gonna get.

 

[superfordman]

Anyone else running into issues trying to update here this weekend? Pretty sure I'm seeing the same issues as @jtrimm on his thread.

Bought a wonderful new two day pass, updated FDRS to 46.5.6, and insta fails every update on my list as soon as the cab goes dark and the programming kicks off. I can Retry or Exit the programming, but retry doesn't do anything and luckily exit wakes everything back up again like it should. Only thing that has changed in my setup since I last updated back in April is updated FDRS and my computer updated to Win 11, everything else is the exact same.

Going to try my old laptop here and see what it does. So I guess that is only plus of the new $120 license, multiple computers and no license key anymore...

 

[joeco]

I don't remember how many files are in the update. I think both a master reset and the battery trick and worth a shot. After you do the master reset, do not pair your phone or do anything. Leave as much space on the APIM as possible to help the update go through.

If it USB error 0, the APIM either has no space or there is hardware/software mismatch. The only thing you can try would be to make the USB update with FDRS again, but remove the voice files first to make more room in the APIM. If you still get USB error 0, then your APIM may be one of the rare ones that is actually f*cked and needs to be replaced.

If you get USB error 6, then you need a new 12v battery for it to install.

No luck with a battery disconnect or master reset.

Do you think running PMI on the APIM would be helpful at all? I’m not sure I fully understand what PMI is, but it seems it’s along the lines of a reset.

 

[rugedraw]

No luck with a battery disconnect or master reset.

Do you think running PMI on the APIM would be helpful at all? I’m not sure I fully understand what PMI is, but it seems it’s along the lines of a reset.

PMI will make the USB update again. No harm in trying. If FDRS gives you an option to remove voice files, select yes.

Sponsored