2023 Lariat Powerboost - all FDRS updates fail with power cutout as flash begins

[rugedraw]

How strange. I'm stumped, tbh. I guess it could be a bad Mongoose.

Sponsored

 

[JohnTrigger]

Maybe some laptop computer issue???:

When you uninstalled and reinstalled FDRS did you select the option to “remove user data” as part of the clean install? Or perhaps try click the envelope in upper right corner and clear FDRS cache and reread the VIN? Reboot computer? Antivirus program blocking the downloads? Have another laptop to try?

 

[JayRay]

Probably not helpful, but worth asking, when you say that the power is cut to the truck, are you just describing the first step in programming where all other controllers are commanded to go silent before it will program the controller? It will seem like everything in the truck turned off, but it is just a safety mode to make sure no controllers are acting on CAN data that may not be good during the programming stage. What are your actions after the power seems to cut? Are you just waiting and not touching anything and waiting for FDRS to report the programming error?

 

[jtrimm]

Probably not helpful, but worth asking, when you say that the power is cut to the truck, are you just describing the first step in programming where all other controllers are commanded to go silent before it will program the controller? It will seem like everything in the truck turned off, but it is just a safety mode to make sure no controllers are acting on CAN data that may not be good during the programming stage. What are your actions after the power seems to cut? Are you just waiting and not touching anything and waiting for FDRS to report the programming error?

Correct. I’m not touching anything until FDRS reports that it failed. FDRS talks to the modules, gets stuff from corporate server, and as soon as it starts to update the modules, the power to truck cuts completely. I sit and wait, and ~10 seconds later an error comes up saying that the update fails. Then I spend 5-20 minutes using a combination of FDRS and Forescan to get rid of a parade of DTC’s that are thrown during the failed update.

 

[superfordman]

Pretty sure I'm in the exact same boat now as well. Had a handful of updates so pulled the trigger on the wonderful new 2 day pass, updated FDRS to 46.5.6, went to try an update, and insta fails a few seconds after the BCM pulls cab power/everything goes dark. Tried every update I had and same on everyone, DDM, PDM, PCM, TRM, wireless charger, etc.

It does give me the option to Retry or Exit, but retry never does anything and luckily after Exit, everything on the truck comes back to life without issue.

Only thing that has changed in my setup since I last did updates without issue in April, is updated FDRS to latest version and my computer updated to Win 11, so my money is on a fun new FDRS issue. I looked through the logs best I could, and seems like it isn't downloading the new files or something right as the programming starts. That seems to be the common theme as my Mongoose it talking and seeing the modules just fine.

In the process of getting the dust blown off my old laptop and will try it out to see what sticks. Its been a while since I've used it so Imagine I'll need to load 46.5.6 to even get the new license working on it so sounds like using an older version is already out the window.

 

[jtrimm]

After you log into FDRS, are you selecting the correct VCI in the menu? Mongoose in the dropdown and not one of the preselected Ford/Rotunda devices (e.g. VCMII).

It is possible there is something wrong with the Mongoose. A call to Opus/IVS tech support might be worthwhile.

Also, a while back a member saw some funky things happen with his Mongoose and it turned out to be a bad USB cable.

Yeah, I select the Mongoose under “Other Device” in the dropdown. I also have a Topdon Rlink device (alternative to the Mogoose) that also exhibits the same exact behavior, so it would seem to rule out a bad Mongoose if both are behaving the same way.

 

[superfordman]

Yeah, I select the Mongoose under “Other Device” in the dropdown. I also have a Topdon Rlink device (alternative to the Mogoose) that also exhibits the same exact behavior, so it would seem to rule out a bad Mongoose if both are behaving the same way.

Mine looks identical so I doubt the Mongoose is to blame

 

[jtrimm]

Pretty sure I'm in the exact same boat now as well. Had a handful of updates so pulled the trigger on the wonderful new 2 day pass, updated FDRS to 46.5.6, went to try an update, and insta fails a few seconds after the BCM pulls cab power/everything goes dark. Tried every update I had and same on everyone, DDM, PDM, PCM, TRM, wireless charger, etc.

It does give me the option to Retry or Exit, but retry never does anything and luckily after Exit, everything on the truck comes back to life without issue.

Only thing that has changed in my setup since I last did updates without issue in April, is updated FDRS to latest version and my computer updated to Win 11, so my money is on a fun new FDRS issue. I looked through the logs best I could, and seems like it isn't downloading the new files or something right as the programming starts. That seems to be the common theme as my Mongoose it talking and seeing the modules just fine.

In the process of getting the dust blown off my old laptop and will try it out to see what sticks. Its been a while since I've used it so Imagine I'll need to load 46.5.6 to even get the new license working on it so sounds like using an older version is already out the window.

Let me know if you have any luck. This is the hellscape I’ve been in for the past week… I have another older laptop I can try tomorrow. Has Windows 11 on it, but is probably several months behind in MS updates…. I’ll be shocked if that fixes it, but who knows. I also grabbed 46.5.4, so I’ll try that as well. It’s the oldest version I’ve been able to find (link is in an earlier post on this thread). The last few days I’ve been using 46.5.6 exclusively. I bought a 30-day subscription, so I have 20 days left to get this thing to update.

 

[Snakebitten]

I don't know how nerdy you are willing to get, but you might want to open your FDRS log file and scroll to the bottom of it and read "up" and looked for clues.

Do this right after a failure alert.

The log file is intensely granular, so be prepared for multiple lines, each with its own timestamp, all related to a short moment in time.

Maybe you'll find a hint.
I was failing on multiple updates on my Mach-E, but not having issues with the Powerboost. Same Mongoose, same laptop, same.......

The log files revealed that the checksum and/or file size on SOME downloaded files did not match the "expected file size". When this would happen, I would harvest the URL for the specific file and manually download it and place it in the appropriate folder or USB stick. At that point the update would succeed.

It was a painfully laborious effort, but it worked. And eventually the issue just ceased to occur. My theory is Ford discovered the issue and resolved it themselves.

Anyways, just a consideration. You'll have to browse your hard drive and find the directory that FDRS keeps the logs. You'll find it though. It's just a text file.

 

[JohnTrigger]

46.5.5 was bad version that couldn’t clear DTCs properly and they quickly put out 46.5.6 two days ago to repair it just before the weekend. Maybe the same incompetent computer software team wrote 46.5.6 too, since a couple of you above are experiencing similar things. That said, at least one member on different forum had this version work for him for a handful of updates this weekend. Maybe your different laptop computers will succeed since it’ll be a complete clean install and reading of your VIN. I’d certainly try to get your $ back or an extension on your 2-day/monthly licenses. This is disheartening to hear and I can imagine super frustrating to be personally experiencing it.

 

[rugedraw]

Yea, I think FDRS is the problem. One person with the issue is a coincidence, but two is a problem.

 

[jtrimm]

46.5.5 was bad version that couldn’t clear DTCs properly and they quickly put out 46.5.6 two days ago to repair it just before the weekend. Maybe the same incompetent computer software team wrote 46.5.6 too, since a couple of you above are experiencing similar things. That said, at least one member on different forum had this version work for him for a handful of updates this weekend. Maybe your different laptop computers will succeed since it’ll be a complete clean install and reading of your VIN. I’d certainly try to get your $ back or an extension on your 2-day/monthly licenses. This is disheartening to hear and I can imagine super frustrating to be personally experiencing it.

So tried a 2nd laptop, first with FDRS 46.5.6, and then again with FDRS 46.5.4. Fresh installs with both. When Inuninstalled 46.5.6 to install 45.6.4, I confirmed the entire FDrS application directory and everything in it was completely deleted (the uninstall did in fact wipe everything). Virus scanning and firewalls turned off, strong wi-fi in driveway. Mongoose works fine with both FDRS and Forscan. Same result as before with both FDRS versions on a virgin laptop. Power cuts as soon as the module write operation starts after it reads a bunch of things, talks to corporate server, and the flash begins. This was with a minor module.. OCSM. Same result regardless of module. Also same result with either the Mongoose or TopDon cables. Tried on just battery, and battery with Clore in power supply mode at 13.8v.

I am at my wits end… Is there an older FDRS version available that still supports subscriptions where you have a login screen? I don’t know what else to try…

 

[jtrimm]

I don't know how nerdy you are willing to get, but you might want to open your FDRS log file and scroll to the bottom of it and read "up" and looked for clues.

Do this right after a failure alert.

The log file is intensely granular, so be prepared for multiple lines, each with its own timestamp, all related to a short moment in time.

Maybe you'll find a hint.
I was failing on multiple updates on my Mach-E, but not having issues with the Powerboost. Same Mongoose, same laptop, same.......

The log files revealed that the checksum and/or file size on SOME downloaded files did not match the "expected file size". When this would happen, I would harvest the URL for the specific file and manually download it and place it in the appropriate folder or USB stick. At that point the update would succeed.

It was a painfully laborious effort, but it worked. And eventually the issue just ceased to occur. My theory is Ford discovered the issue and resolved it themselves.

Anyways, just a consideration. You'll have to browse your hard drive and find the directory that FDRS keeps the logs. You'll find it though. It's just a text file.

Thanks for this suggestion. I checked the error log. Searched through the whole log file. No file errors, just a stack trace of when the update failed (see attached photo). installation and files log both didn’t indicate any file download errors.

 

[JohnTrigger]

I am at my wits end… Is there an older FDRS version available that still supports subscriptions where you have a login screen? I don’t know what else to try…

As far as I know, 46.5.4 or later is required for the new security login measures when they went to the $120 subscription method a few weeks ago. And 46.5.5. had issues with clearing DTCs. And (maybe based on how it’s going for you) 46.5.6. has issues too. Since you’ve tried .4 and .6, I don’t think this is your answer either.

 

[JohnTrigger]

Maybe version 46.5.7 will be quickly coming out on Monday or Tuesday since dealerships probably were closed and not using .6 over the weekend. They show up Monday and can’t fix anything and report to corporate hopefully. Although with Thanksgiving this week, who knows.

Sponsored