ECU module programming guide using FDRS

[heffer86]

I have been leaving the door open.
I thought that was suggested? Lol

I just finished the 30 minute door open with the fresh new usb

By the way, during the 30 minute wait, I DO hear the truck "clunk" twice. Once at about 10 minutes, and once again maybe 10 minutes later. It sounds like it comes from inside the dash internally. I assumed it was hard shutdowns of some kind. Perhaps relays getting switched to off?

I feel your pain. I though my update would never take. Like other users have mentioned you could try fresh again by taking out the USB and cycling the ignition and putting the drive back in. I took the route of just waiting. It took two days before my first one would take. Keep us updated. Second one took after a 30min wait.

 

[JEB]

I have been leaving the door open.
I thought that was suggested? Lol

I just finished the 30 minute door open with the fresh new usb

By the way, during the 30 minute wait, I DO hear the truck "clunk" twice. Once at about 10 minutes, and once again maybe 10 minutes later. It sounds like it comes from inside the dash internally. I assumed it was hard shutdowns of some kind. Perhaps relays getting switched to off?

Yes. Shut the door. Leaving it open leaves some systems powered up, like interior lights.

The clunks are normal. But what you’re really looking for is full shutdown. If you see the lights around the USB ports in the rear seat area go out you know for certain you are in full shutdown.

 

[Snakebitten]

You fellas are encouraging!
I'm not giving up if Yaw ain't.

I'm trying a door closed, me out of the truck, and the Fob nowhere near it attempt this time.

 

[Jesse-Infotainment]

Yeah.. I had that issue as well. I forced a reboot of the apim a few times through the power and seek forward at the controls above hvac or the volume down and seek up on steering

the hard part is done you just need it to kick over to the update because the files are installed.

make sure the key is away from the truck

leave door open and Walk away as long as you can. It took me a few times and it finally kicked over.
Just make sure to leave the usb in.

 

[Jesse-Infotainment]

I appreciate that everyone is assisting. I don’t think there is any right way so just try until it kicks off. I also would maybe pull the charger at this point if you haven’t.. it may be keeping something awake.

 

[iceman77]

I had the same issue, the APIM and TCU update was stuck in this “Restart Required” loop. I tried waiting 10mins, then 15 with door left open, with door closed. Then I disconnected the battery to let the truck completely (and I meant COMPLETELY) shut down. After that I retried the update. This time the update stuck! Not sure if it was the battery disconnect or that I waited 30 minutes (instead of 15), what matters that it installed.

 

[speedracercjr]

I got VCX Nano in, borrowed a buddies battery tender and have the software all installed and ready. I'm on the 1.7.1 stuck OTA and was wondering if there was a minimum I could update in order to get "over the hump" and get the OTA's flowing again. Thoughts?

 

[iceman77]

I got VCX Nano in, borrowed a buddies battery tender and have the software all installed and ready. I'm on the 1.7.1 stuck OTA and was wondering if there was a minimum I could update in order to get "over the hump" and get the OTA's flowing again. Thoughts?

Make sure your gateway module (GWM) is up to date prior attempting APIM and/or TCU.

 

[JEB]

I had the same issue, the APIM and TCU update was stuck in this “Restart Required” loop. I tried waiting 10mins, then 15 with door left open, with door closed. Then I disconnected the battery to let the truck completely (and I meant COMPLETELY) shut down. After that I retried the update. This time the update stuck! Not sure if it was the battery disconnect or that I waited 30 minutes (instead of 15), what matters that it installed.

Battery disconnect probably didn’t do it if you have a PB. The PB has an auxiliary 7.5Ah battery under the passenger side rear seat that retains some power to the systems for times when the main starting battery alone isn’t sufficient—usually during cranking.

 

[iceman77]

Battery disconnect probably didn’t do it if you have a PB. The PB has an auxiliary 7.5Ah battery under the passenger side rear seat that retains some power to the systems for times when the main starting battery alone isn’t sufficient—usually during cranking.

You are correct. Pulling battery on a PowerBoost would have no effect. My truck is 3.5L EcoBoost perhaps it helped in my case

 

[Snakebitten]

OK, nobody NOBODY is going to believe me. Ever never NEVER ever...... I'll probably get kicked out of the thread.... ???

But this IS what happened and I didn't imagine it:

So as documented earlier this morning, I couldn't get past the "restart loop". And I had tried every nuance possible that this thread and others mentioned. All of them. I promise.
While burning yet another 30 minute wait I came across this: (another thread)

I said to myself "myself, that's ME"! I'm the guy with one of the trucks that fails the APIM update OTA, FRDS, USB.... Whatever. And the good news is Ford knows about it.

So I just reached over and shut the truck down. I then pulled the USB stick out.

But I thought I might browse around in FRDS to learn some of its features and DTC diagnostics before I quit for the day. So I started the truck back up and was launching a fresh session (network scan) when I noticed that the sync screen FORD logo was squished into the left 3rd of the screen. WTH?
Then a few seconds later the screen started over with the normal full screen logo. Then Sync opened to the Audio screen, which was where I last was.

But something was different!

It was subtle, but it was fresh and laid out with a new icon for "Radio"? I immediately thought "how the heck can this be? Is it what I think it might be?"

Then, WALLAH!

My USB stick was NOT in the truck!
I had already removed it when I shut the truck down.

I was stunned. So I immediately checked and :

No longer 21146

But that's not all!

I had thought that I read that the main issue my early build truck had was that OTA was broken because my Gateway module needed to be upgraded and Ford couldn't push an update to it so you needed an FRDS (dealership) update of that module in order to catch up on other updates. But FRDS never even indicated that I needed an update:

But, after the APIM finally succeeded, a fresh scan showed a new update available for the Gateway module!

Oh happy day. Lol

I'm up to date!

My only disappointment is that my FordPass App still doesn't recognize my connection as Bluetooth, thus will not offer me the extended functionality for the generator. Oh the irony. That feature is what served as the catalyst for me to "take matters into my own hands". And it's the only feature that appears to still needs me to figure it out.

 

[Snakebitten]

Soooooooo, unless I get censored from this thread, if you get stuck in the loop....... There is one more thing to try and it doesn't hurt to try.....

Turn the truck off BEFORE removing the USB stick. Then start the truck.

I'm only guessing, but having the stick in would imply that it would still be necessary for copying files? But that part has already happened. So something in the "update routine" is getting nixed when the Sync/APIM reboot and then looks at the stick?

No stick and it just went on and finished the update procedure.

 

[JEB]

OK, nobody NOBODY is going to believe me. Ever never NEVER ever...... I'll probably get kicked out of the thread.... ???

But this IS what happened and I didn't imagine it:

So as documented earlier this morning, I couldn't get past the "restart loop". And I had tried every nuance possible that this thread and others mentioned. All of them. I promise.
While burning yet another 30 minute wait I came across this: (another thread)

I said to myself "myself, that's ME"! I'm the guy with one of the trucks that fails the APIM update OTA, FRDS, USB.... Whatever. And the good news is Ford knows about it.

So I just reached over and shut the truck down. I then pulled the USB stick out.

But I thought I might browse around in FRDS to learn some of its features and DTC diagnostics before I quit for the day. So I started the truck back up and was launching a fresh session (network scan) when I noticed that the sync screen FORD logo was squished into the left 3rd of the screen. WTH?
Then a few seconds later the screen started over with the normal full screen logo. Then Sync opened to the Audio screen, which was where I last was.

But something was different!

It was subtle, but it was fresh and laid with a new icon for "Radio"? I immediately thought "how the heck can this be what I think it might be?"

Then, WALLAH!

My USB stick was NOT in the truck!
I had already removed it when I shut the truck down.

I was stunned. So I immediately checked and :

No longer 21146

But that's not all!

I had thought that I read that the main issue my early build truck had was that OTA was broken because my Gateway module needed to be upgraded and Ford couldn't push an update to it so you needed an FRDS (dealership) update of that module in order to catch up on other updates. But FRDS never even indicated that I needed an update:

But, after the APIM finally succeeded, a fresh scan showed a new update available for the Gateway module!

Oh happy day. Lol

I'm up to date!

My only disappointment is that my FordPass App still doesn't recognize my connection as Bluetooth, thus will not offer me the extended functionality for the generator. Oh the irony. That feature is what served as the catalyst for me to "take matters into my own hands". And it's the only feature that appears to still needs me to figure it out.

Well done. As for the bluetooth for the Pro Power generator, make sure you in fact have a bluetooth connection to your phone. Ignition has to be on. Once you’ve verified the connection, then open FordPass and see if Pro Power reflects the connection. You might have to refresh the app a couple of times before it recognizes the new connection.

One final piece of advice. Do another network scan tomorrow in FDRS. There is another APIM update that should come down. It’s a small one that doesn’t require a flash drive.

Again, well done. Enjoy.

 

[Snakebitten]

Well done. As for the bluetooth for the Pro Power generator, make sure you in fact have a bluetooth connection to your phone. Ignition has to be on. Once you’ve verified the connection, then open FordPass and see if Pro Power reflects the connection. You might have to refresh the app a couple of times before it recognizes the new connection.

One final piece of advice. Do another network scan tomorrow in FDRS. There is another APIM update that should come down. It’s a small one that doesn’t require a flash drive.

Again, well done. Enjoy.

Will do! (on the FRDS scan)

I do make sure that I have a Bluetooth connection to the truck before launching FordPass. But the ProPower page still says "cellular"

I had this feature back when I purchased the truck in May. I USED the feature several times. Then I noticed folks on this forum complaining about having to go to the truck to launch ProPower. I posted several times that you shouldn't have to if you connect Bluetooth first. Then a month later I lost the functionality.

Your post showing that yours worked was the first I've seen in about 3 months.

I'm going to get it back! I'm stubborn as a mule now. Lol

Thanks again Jeb. /)

 

[iceman77]

Soooooooo, unless I get censored from this thread, if you get stuck in the loop....... There is one more thing to try and it doesn't hurt to try.....

Turn the truck off BEFORE removing the USB stick. Then start the truck.

I'm only guessing, but having the stick in would imply that it would still be necessary for copying files? But that part has already happened. So something in the "update routine" is getting nixed when the Sync/APIM reboot and then looks at the stick?

No stick and it just went on and finished the update procedure.

Why would you get censored? We are all here so we can help each other! I am personally very happy that you managed to finally update your APIM. Any suggestion in this thread is valuable. What I wrote up in the original guide is what worked for me. But as we can all see, there are multiple solutions to the same problem! And that’s what this thread is about. To share the knowledge and help each other out!

At last, welcome to the “updated myself” club!

Sponsored