The Complete DIY Guide to Updating Your Mach-E with FDRS

[Snakebitten]

Those values certainly match my 2023.5 BC 1.3 as shipped from factory.

I can't vouch for them working on any other Mach-E though.

Sponsored

 

[Helly]

I believe you have already looked at the FDRS log to decipher where the update is failing?

You simply start a new session in FDRS, and pay close attention to your timestamp as you start an update and it suddenly errors out or fails.

Then grab a copy of the FDRS log file (I don't use the active copy) and scroll to the timestamp that matches the minute/seconds around the moment of failure.
For me, since the failure is almost always during the first file download, the log file will reveal the file/URL that failed.

If you are failing for the same reason, you can do the same. Once you manually download the file in a browser, and then copy it to the appropriate folder for FDRS, restart the update a second time. FDRS will see the first file is already present and will move on to the second file.

It will likely fail as well, and back to the log file again to harvest the URL.

The only confusing part is knowing where FDRS expects to find the file(s)

It's not always the ........\vehiclesoftware\downloads folder.
Sometimes it's the ........\vehiclesoftware\
Sometimes it's ........\vehiclesoftware\strategy\ folder.
Or
........\vehiclesoftware\strategy\downloads folder.

You kind of have to watch your hardrive closely while FDRS is attempting to download the next file and see if it created a folder and has a temporary placeholder of the filename with 0 bytes

See why I hesitated to send anyone down this rabbit hole? Lol

I don't want someone to come along and read this stuff and think it applies to their Mach-E. It'll intimidate and make them hesitate to "take matters into their own hands" with getting their Mach-E updated at least to the point they aren't waiting for the good stuff.

As far as I can tell, very few folks will have this bug. And I'm hoping that Ford discovers it and addresses it in a new FDRS build?

This does NOT affect OTA delivery of an update. I want to be clear about that. It's a bug in FDRS being able to write a file from memory to the disk. And it's not happening with every update. But for my Mach-E specifically, it does affect the majority of the updates.

I'm all caught up after dancing through the IPC today.
And the Powerboost is up to date too.

Both vehicles are fully functional with all the features, including "coming soon" ????

I love my Ford products I currently have. Fantastic engineering. But Ford is tripping all over themselves with the delivery mechanism behind OTA. I just don't choose to live with their stumbling if I don't have to.

I will try today to execute FDRS as administrator. I haven't try this but it could be the solution FDRS write in c:\programdata a directory which be protected by windows. may be it will be the real solution...

Edit: I try but not working...

 

[Helly]

may be I find what's the problem it seems that when we download the tcu or IPC package the FDSP token server doesn't respond http 400 exemple:
2024-05-13T13:17:36,727 INFO resource.util.ResumableFileTransfer - Attempting to download LJ8T-14C025-LF from https://vehiclesoftware.ford.com/06b4de12-ef52-4b2f-b03b-61ed878ac2a9_LJ8T-14C025-LF.vbf. Initial size: 0. Expected size: null.
2024-05-13T13:17:36,727 INFO util.download.QueuedFileDownload - Request headers: {Range=bytes=0-}
2024-05-13T13:17:37,465 I/O client.fdsp.AbstractRestService - [REST] Request sent to https://www.fdspcl.dealerconnection.com/AuthorizationService/getFdspToken
2024-05-13T13:17:38,371 I/O client.fdsp.AbstractRestService - [REST] Unsuccessful response - status code: 400
for other function this token server answer me with a http 200 so work...

 

[Mike G]

may be I find what's the problem it seems that when we download the tcu or IPC package the FDSP token server doesn't respond http 400 exemple:
2024-05-13T13:17:36,727 INFO resource.util.ResumableFileTransfer - Attempting to download LJ8T-14C025-LF from https://vehiclesoftware.ford.com/06b4de12-ef52-4b2f-b03b-61ed878ac2a9_LJ8T-14C025-LF.vbf. Initial size: 0. Expected size: null.
2024-05-13T13:17:36,727 INFO util.download.QueuedFileDownload - Request headers: {Range=bytes=0-}
2024-05-13T13:17:37,465 I/O client.fdsp.AbstractRestService - [REST] Request sent to https://www.fdspcl.dealerconnection.com/AuthorizationService/getFdspToken
2024-05-13T13:17:38,371 I/O client.fdsp.AbstractRestService - [REST] Unsuccessful response - status code: 400
for other function this token server answer me with a http 200 so work...

@Helly you're going to have some difficulty today I suspect. They did something to one or more of the servers on Sunday, and there's a lot of garbage data being returned in FDRS and PTS.

 

[Helly]

@Helly you're going to have some difficulty today I suspect. They did something to one or more of the servers on Sunday, and there's a lot of garbage data being returned in FDRS and PTS.

Oh if they add more problem i m not close to solve my ipc download problem

 

[Robob]

Has anyone with 2023 had the new APIM pop up in FDRS yet? I have been too busy and have not been around checking VINs lately, but still haven't had anything pop for me besides the new powertrain updates which has been working good no issues so far.

 

[Helly]

Has anyone with 2023 had the new APIM pop up in FDRS yet? I have been too busy and have not been around checking VINs lately, but still haven't had anything pop for me besides the new powertrain updates which has been working good no issues so far.

I have a 2023.00 I try FDRS 2 Hours ago but no new APIM update. I get the new powertrain update which correct the one pedal problem 2 week ago

 

[rugedraw]

Got through them without issue thankfully. Does anyone know if these have the "goodies" for BC 1.4 included in them or will there be some other update that actually activates them?

Yes, BC 1.4 is in there. If your vehicle shipped with BC 1.2 or 1.3, then you are now on 1.4. If you vehicle shipped with 1.0, then you have greatly improved BC stability, but no lane change assist. in-lane repositioning etc yet.

 

[rugedraw]

I have a 2023.00 I try FDRS 2 Hours ago but no new APIM update. I get the new powertrain update which correct the one pedal problem 2 week ago

Unfortunately, I was not able to get you the bootloader file you wanted. Hopefully you can figure out a way to get it done.

 

[Snakebitten]

Has anyone with 2023 had the new APIM pop up in FDRS yet? I have been too busy and have not been around checking VINs lately, but still haven't had anything pop for me besides the new powertrain updates which has been working good no issues so far.

2023.5 here.

Do you mean the 23352?
Yes sir.

 

[Helly]

Unfortunately, I was not able to get you the bootloader file you wanted. Hopefully you can figure out a way to get it done.

after reading other forum F150 one, some have the same problem it has been resolve by using an other computer....

 

[rugedraw]

after reading other forum F150 one, some have the same problem it has been resolve by using an other computer....

Interesting. Let me know how it goes. I'm curious about your case.

 

[Robob]

2023.5 here.

Do you mean the 23352?
Yes sir.

Did that update show up in FDRS recently for you? or did you have to trick it with cert files etc?

 

[Snakebitten]

Did that update show up in FDRS recently for you? or did you have to trick it with cert files etc?

It showed up a couple of weeks ago.
I applied it on May the 6th I believe.

 

[spicy_taco]

Did that update show up in FDRS recently for you? or did you have to trick it with cert files etc?

Adding another data point. That APIM update (with the new buttons) showed up for my 2023 (Job 1) in FDRS mid-March.

Sponsored