ECU module programming guide using FDRS

[BHunted1]

I received 2.1.0 OTA few days after I manually updated the APIM to 1.7.1 OTA equivalent

Soooo, that’s a yes as long as 1.7.1 gets loadEd from flash drive?

Sponsored

 

[tkljr]

Thanks iceman77 for this. Being stuck on 1.7.1 for a couple of months i'm thinking it's worth the $150 investment to not have to deal with the Ford service department but I do have a question.... At the point a USB is inserted for FDRS to write the needed software can the VCX Nano be removed? My PC has only one USB port.

 

[iceman77]

Thanks iceman77 for this. Being stuck on 1.7.1 for a couple of months i'm thinking it's worth the $150 investment to not have to deal with the Ford service department but I do have a question.... At the point a USB is inserted for FRDS to write the needed software can the VCX Nano be removed? My PC has only one USB port.

Yes, you won't need PC or FDRS up until the USB update finishes, then you will need to reconnect your VCX Nano and run module configuration etc

 

[iceman77]

Soooo, that’s a yes as long as 1.7.1 gets loadEd from flash drive?

I my case yes, I started getting OTAs once my APIM got updated to 1.7.1 OTA equivalent via USB flash drive

 

[BHunted1]

I my case yes, I started getting OTAs once my APIM got updated to 1.7.1 OTA equivalent via USB flash drive

Just wrote this here:
https://www.f150gen14.com/forum/threads/power-up-2-3-0-ota-rolling-out.7724/post-155682

 

[tkljr]

I my case yes, I started getting OTAs once my APIM got updated to 1.7.1 OTA equivalent via USB flash drive

I'm mainly interested in getting past the failed 1.7.1. OTA. Will FDRS have any indication as to which module updates are related to specific OTA revisions or do you use another source to determine the OTA equivalent?

 

[iceman77]

I'm mainly interested in getting past the failed 1.7.1. OTA. Will FDRS have any indication as to which module updates are related to specific OTA revisions or do you use another source to determine the OTA equivalent?

Unfortunately FDRS will not tell you what SW revisions are available, it only shows that SW update is available for specific module. It is possible to determine SW revision though by looking at the file names on the USB flash drive, once created by FDRS

 

[imnuts]

Btw, the VCX Nano works perfect with ForScan as a J2534 pass-through device. In fact, its much faster than their official ELM327 interface. I have used it to make quite a few changes on my truck (including the Glarefree lightning which involved updating multiple modules on the truck)

I wish when you first posted this info in the other thread was a few months ago before I bought the ODB Ex cable.

 

[Snakebitten]

Well I had a good time figuring out how to take matters into my own hands. Discovered a mess of updates that my 2021 Powerboost Platinum was eligible for.

I decided to leave the BIG one(s) for last and promptly applied the other 11 updates. Piece of cake!

Then I chose that scary and stubborn APIM.

It LOOKED like it too was going to go off without a hitch, but I am hung in the "Need to restart to complete the update" loop. ?

I've done the door open 10 minutes
I've done the door open 30 minutes

It was 2am so I took my freezing weary bones to bed, so I left the door open 6 hours!

Each time you could see the truck finally go "dormant" after about 10 minutes. So I know I was accomplishing whatever that accomplishes, but I still got the dang "restart to finish the update".

I don't know exactly what to try next?

FRDS does a check against the files on the APIM and several "fail" the audit due to wrong file rather than expected file.

Any of you gurus got a kick-in-the-pants idea?

 

[JEB]

Well I had a good time figuring out how to take matters into my own hands. Discovered a mess of updates that my 2021 Powerboost Platinum was eligible for.

I decided to leave the BIG one(s) for last and promptly applied the other 11 updates. Piece of cake!

Then I chose that scary and stubborn APIM.

It LOOKED like it too was going to go off without a hitch, but I am hung in the "Need to restart to complete the update" loop. ?

I've done the door open 10 minutes
I've done the door open 30 minutes

It was 2am so I took my freezing weary bones to bed, so I left the door open 6 hours!

Each time you could see the truck finally go "dormant" after about 10 minutes. So I know I was accomplishing whatever that accomplishes, but I still got the dang "restart to finish the update".

I don't know exactly what to try next?

FRDS does a check against the files on the APIM and several "fail" the audit due to wrong file rather than expected file.

Any of you gurus got a kick-in-the-pants idea?

First thing I would try is this: Erase the flash drive and make sure it is absolutely empty—no residue from previous module installs or attempts. Then, try to get the TCU to update. After applying the update, open and close the door and wait 30 minutes before completing the process of validating the install.

After updating the TCU, erase the flash drive again. This is really important to avoid getting validation failures. Then try to install the APIM again using the same process you used to install the TCU.

 

[heffer86]

Well I had a good time figuring out how to take matters into my own hands. Discovered a mess of updates that my 2021 Powerboost Platinum was eligible for.

I decided to leave the BIG one(s) for last and promptly applied the other 11 updates. Piece of cake!

Then I chose that scary and stubborn APIM.

It LOOKED like it too was going to go off without a hitch, but I am hung in the "Need to restart to complete the update" loop. ?

I've done the door open 10 minutes
I've done the door open 30 minutes

It was 2am so I took my freezing weary bones to bed, so I left the door open 6 hours!

Each time you could see the truck finally go "dormant" after about 10 minutes. So I know I was accomplishing whatever that accomplishes, but I still got the dang "restart to finish the update".

I don't know exactly what to try next?

FRDS does a check against the files on the APIM and several "fail" the audit due to wrong file rather than expected file.

Any of you gurus got a kick-in-the-pants idea?

I had the same issue with my APIM the first time (I had two APIM updates so far). My issue was my battery was to low in voltage. Do you have your battery power supply/charger hooked up? It might not hurt to drive for 10-15m to get your battery up to voltage. Get home power-down and leave it it for 10-30min. Then restart (as in the engine) the vehicle. That is that I had to do one of the times to get my APIM update to take.

 

[Snakebitten]

Thanks fellas!

I did go fetch 2 brand new usb sticks to eliminate that possibility.

And I do have a charger on the battery. Note that the voltage has never dropped below 12.8v in FRDS.

My assumption that the USB stick was not the issue is that the truck almost immediately notices it and prompts "system updating" I thought that was the issue that some folks experienced..... That the truck acted like there wasn't an update to perform.

Anyways, I'm at it again!
Sunshine is out. At least I'm not freezing in the truck anymore.

 

[JEB]

I just reread your install saga. In addition to my suggestion that you make sure you start the process with a clean flash drive and @heffer86’s suggestion that you use a battery tender, open and CLOSE the door and just walk away for 30 minutes before completing the post-validation operation.

 

[Snakebitten]

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?

 

[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.

Sponsored