Quick update- I downloaded 45.6.8, uninstalled 46.5.6, installed 45.6.8, and the updates are working now!!! I got occupant detection module updated as well as the DCDC module! Thank god… Thank you for everyone’s help troubleshooting. Shoutout to SuperFordMan for figuring out that going back to...
I tried 46.5.6 and 46.5.4 (since 46.5.5 is known to be bad). I can’t find any links to download the older 45.6.8 FDRS. Does that support logging in with the FDRS subscription login page vs. the old activation code? Does anyone have a link to the older 45.6.8 version?
BTW… thanks for this...
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.
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)...
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...
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. 😕
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...
Did both things above- fully uninstalled and reinstalled FDRS. Opus toolbox worked and pulled VIN. Same behavior when flashing as before- power cuts when module writes begin. 😞
Ugh… I disconnected both batteries, waited 30 minutes, and reconnected- backup battery first, then the main battery. Same behavior: start the update, in this case something simple like Passenger Door Module, FDRS is talking with the module, connecting to corporate server, and as soon as it...
Yes, I push the start button when the Clore is in Power Supply mode. Just disconnected both batteries for 30 minutes and am about to try again after that. Fingers crossed! 🤞
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...
Thanks, I’ll give this a shot Saturday morning. Fingers crossed.. Thank god I got the one month FDRS subscription instead of the two-day… 🙄 Trying to get to BC 1.4 before our 9 hour drive with the family to see my folks for Thanksgiving On Tuesday.
It was actually in charging mode topping off the battery when I took that picture, not power supply mode. I’ve tried every voltage point from 13.6-14.1v in power supply mode, all with the same behavior of the power cutting off at the beginning of the update. 😕
I have a 2023 Lariat Powerboost I bought CPO from a local dealer with 19k miles on it when I bought it 4 weeks ago. My dealer can’t/won’t upgrade Blue Cruise 1.0 to 1.4 for me. There has just been one HVAC OTA update I’ve received in the month I’ve owned it. Truck hooked to WiFi. My goal is...