When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Just got a message this morning that the 2.3.0 OTA failed and not sure why. Anyone know if it will try again or anything I may be able to do to make it try again? My internet was down for most of the day yesterday and wondering if that had anything to do with it.
I got the same thing on 1/21 but that was the day after I updated the TCU/APIM myself so I figured that was why but I doubt in your case it was because of your internet being down; I've seen other OTA updates that were cancelled by Ford last minute. Below is what mine shows and if you want to pm me your VIN I can look at the reason why yours failed.
There's a difference between canceled and failed. My guess is because it's the middle of winter the GWM / BMS may have surpassed a battery temp threshold. (It's too cold to attempt a lengthy APIM update on battery charge). Some people can log online and get the full details of why an update failed or canceled, but I don't have those privileges. The other likely scenarios is a DTC from the target module can interrupt updates. Anyone who's used ForScan may have inadvertently caused some.
Last edited by Airborne_Ape; Feb 6, 2022 at 10:33 AM.
My truck tried to install the 2.3.0 update the other day, but it failed according to the message on the trucks screen. The following day, Fordpass website updated it was successfully, but it looks like it installed 2.1.1 again.
I looked at the widget information and it looks like 2.3.0 still failed.
I got the same thing on 1/21 but that was the day after I updated the TCU/APIM myself so I figured that was why but I doubt in your case it was because of your internet being down; I've seen other OTA updates that were cancelled by Ford last minute. Below is what mine shows and if you want to pm me your VIN I can look at the reason why yours failed.
There's a difference between canceled and failed. My guess is because it's the middle of winter the GWM / BMS may have surpassed a battery temp threshold. (It's too cold to attempt a lengthy APIM update on battery charge). Some people can log online and get the full details of why an update failed or canceled, but I don't have those privileges. The other likely scenarios is a DTC from the target module can interrupt updates. Anyone who's used ForScan may have inadvertently caused some.
Mines a failure.. I changed the time for updates to see if after midnight tonight it starts back up... I'll check for DTC's and report back. IIRC, I had one that showed up in ForScan for the APIM and it might be back.
