OTA 1.7.1 Stuck, anyone else have issue updating?

[Smolinski]

Well, the Consumer Report Annual Car survey should be coming to me soon. I wonder how I am going to respond

Sponsored

 

[Gimme_my_MME]

So nothing really new. Soon is the operative word, I guess.....

I think is a lot worse than they are saying. If there was a software patch that could fix this, it should have been done by now.

My guess is that they are fighting with the company that manufactured the APIM over who is going to pay for all of this and when they can supply all the new APIM's.....

Jim

Or, the fix is just being put through the ringer so that nothing further happens. As clearly something was missed during testing of the original OTA

 

[Tmarch]

Had some good luck so I thought I'd share my story here for others in the same boat. Here are some prerequisites. I own a Job 1 Mach-E Select AWD and took delivery in May 2020. The first OTA I received was 1.6.0. The second was 1.4.0. Got those some time in the summer, pretty much back-to-back. Car is usually plugged in at home, connected to my WiFi. It has its own access point right nearby, so it has a very good connection to my network. 2-3 bars of AT&T service as well. I did have the customer satisfaction updates run at the dealership in December (December 27) and can charge faster at over 80%.

The car's first attempt to download and update what I'm assuming was 1.7.1 was on November 26, 2021. I also had the 1.7.1 release notes with the Chinese character and "you are all set." The error was what MANY of you have seen, which is "expired" when looking at the OTA information from the Scriptable widget. That was combined with an inability to toggle automatic updates, set a schedule, and no version information. Believe this inability to toggle these features is not because they are broken, but because the car thinks it is mid update and won't let you change any settings. Here's why I think this is the case.

I've been talking to my dealer and a friend who has access to PTS (professional technician system) so what I've learned is that as soon as an OTA fails, the car immediately recycles that OTA. That doesn't mean it will try to install and download right away, but it knows it has failed and the troubleshooting solution is wiping everything and starting from scratch (ping the server, see if update available, download update, attempt to install). So during this process, it will not let you toggle updates, show version numbers, or let you schedule stuff. It is working on something!

Car re-tried on December 21 and expired again. Tried on January 4 and instead of expiring, it straight up failed. I saw "failure" in the Scriptable widget. What I noticed in PTS though was that the reason it failed was because "Update Manifest Available." As far as I can tell, it failed not because it struggled to install but because Ford pushed a new update manifest. Here's a screenshot showing everything I've talked about so far. Spoiler for the end of the story!

Last night I checked the widget OTA status for fun and saw this. Delivery queued! I'd never seen that before, but assumed it meant that the car had an update available and the update was queued for download. FYI OTAM_S1001 does not correspond to the update it is downloading, but the STATUS of the update.

Now I don't drive very much at the moment since I'm working from home and the wife is also home with our new baby. So the car sits in the driveway plugged in for literal days. Sometimes an entire week. From everything I understand, the car only downloads updates while it is running so I went out and turned it on (leaving it plugged in). I left it for maybe two hours. It was -10 here in Vermont so I didn't mind letting it warm up a bit anyway. Not like idling a gas vehicle! After two hours I checked again.

Installation queued! Must have downloaded I thought. I assumed from what I've read that the car primarily installs updates when it is powered off. So I went out to turn it off, left it plugged in, and continued with my night. One hour later I checked again.

SUCCESS?! I couldn't believe it. I didn't dare go out to the car. So I had my friend pull the PTS report you see above. It also said success. What the heck?!

It worked! So I was literally in the place many of you have been. Expired. Failed. Toggling updates issues. Failures in PTS. Updates available in FDRS. My dealer didn't try doing an APIM update. I think they missed it when I went in, even though I specifically requested it. Job 1 car. Prior to June. Weird 1.4.0 to 1.6.0 update cadence. Chinese character in 1.7.1 release notes, then they disappeared. No consumer facing failures, not in FordPass, not on the car. All the "failures" were in PTS or the Scriptable widget.

So what happened? I have theories. My first theory is that Ford pushed a new version of 1.7.1 that got passed the installation issues. Hence the "Update Manifest Available" error on one of the installations. If this is true, then I would imagine people will start seeing 1.7.1 succeed.

My second theory is that many of us in this thread are experiencing different problems that manifest as the same problem. My update expired two times, maybe because I don't drive very often? So it would always take too long to download because it was trying over cellular with 2-3 bars and not WiFi? Also the places I drive (rural area) are often without service, so even if I was driving it wouldn't be able to pull down the update? Then I just happened to hit the right cadence of turning the car on and off? It would make sense to me that the car prioritizes downloads while running, rather than while off...although that's a bit of a ridiculous implementation if you ask me, especially if plugged in. As a result, I think this theory is less likely. If this is the case however, maybe I didn't have a problem with the APIM module. Maybe the dealer would have had no trouble updating it! I did have an appointment for this Monday to try.

Here is to hoping 2.1.0 and 2.3.0 completes a little bit more smoothly...sound off with questions if you have them!

I'm going to try this. I'm in the same boat, since my update failure I've only put on 200 miles, and that's been very hit and miss driving (2 miles here, 1 mile there, stop at the gym, etc). I've got it running in the driveway, plugged in. Let's see what happens.

 

[Jim_I]

Or, the fix is just being put through the ringer so that nothing further happens. As clearly something was missed during testing of the original OTA

I truly hope you are right!

For a while I wondered if it may be that I have Android Auto enabled which disables or takes over some parts or all of the bluetooth connection to my phone. Hoping to report an AHA!!! moment. After 4 days, nothing....

In the mean time, I may try turning off the WiFi. And I am going to do a charge session tomorrow at a local EA station to see if the charging rate past 80% has been modified. Just chasing clues to see if that part of the 21P22 update actually installed properly.

My appointment is set for next Wednesday morning. Will keep everyone updated!

Jim

 

[SashaLondon]

Does anyone know why if the update expires during a time period they don't send it out again? I have an expired 1.7.1 from December and was wondering why they didn't try pushing it out again.

 

[FordMachEGo]

Does anyone know why if the update expires during a time period they don't send it out again? I have an expired 1.7.1 from December and was wondering why they didn't try pushing it out again.

I have the same question. Mine failed in December and expired around the same time according to the OTA data. Nothing since. Would it help to request that the dealer try and install CSP 21P22?

 

[SAM]

I have the same question. Mine failed in December and expired around the same time according to the OTA data. Nothing since. Would it help to request that the dealer try and install CSP 21P22?

That didn't help me. CSP 21P22 fully installed but Power-Up 1.7.1 still stuck, expired, stuck, nothing. Been stuck since mid-Nov.

CSP 21P22 may make some improvement in OTA that probably doesn't fix the APIM issue with 1.7.1 being stuck.

 

[benk016]

Does anyone know why if the update expires during a time period they don't send it out again? I have an expired 1.7.1 from December and was wondering why they didn't try pushing it out again.

I have the same question. Mine failed in December and expired around the same time according to the OTA data. Nothing since. Would it help to request that the dealer try and install CSP 21P22?

They may have stopped sending out 1.7.1 completely since it caused some issues with some cars, and since there is a newer sync version being pushed out in 2.3.0 now.

I wouldn't be too worried if you miss 1.7.1.

 

[SashaLondon]

Only as I contacted Ford about it and I have an email trail of the tech help trying to get me to make a service appointment. I will leave it and wait for some magic to happen.

 

[Rocky29670]

Back on November 4, 2021, I got an app message that a Power Up Software Upgrade was unsuccessful. The Update Details were for the FordPower-Up 1.7.1. Since then, the car has reverted back to an older version which killed PAAK, again. So, the upgrade the dealer did back in August for the PAAK fix seems to have been wiped out and I have to open the driver door before I can open the rear driver side door again, too.

Sigh...still waiting to get my car back from the body shop (waiting on a passenger side headlight which may be "released" from Ford by mid-January, 2022). Once I get it back and it is driveable, I will wait it out for Ford to give dealers the upcoming fix (Feb/Mar).

Excited for those 2.x OTA updates and hope I can get them by Spring.

Forgive me for being immature, probably a side effect of teaching middle schoolers all day, but I saw the vanity plate in your post; did you really get one that reads "IBLU MAX"? If so how many people ask you who Max is? My middle school wired brain reads that as "I blew Max". Just an FYI on how the rest of the world, who doesn't know Ford paint color names, is going to read that.

 

[stmache]

Forgive me for being immature, probably a side effect of teaching middle schoolers all day, but I saw the vanity plate in your post; did you really get one that reads "IBLU MAX"? If so how many people ask you who Max is? My middle school wired brain reads that as "I blew Max". Just an FYI on how the rest of the world, who doesn't know Ford paint color names, is going to read that.

Yeah, I blew (pun intended) it, when I sent this in. However, New York allowed it. I will change it probably next year. Should have done BLU3, eh?

 

[Twig]

Well I'm having same issue can't toggle on automatic updates can't schedule updates. I haven't received an update since I bought the car in June.

Are we simply suppose to wait and see how this plays out?

 

[Bookworm214]

Well I'm having same issue can't toggle on automatic updates can't schedule updates. I haven't received an update since I bought the car in June.

Are we simply suppose to wait and see how this plays out?

My Automatic Updates button was showing as ON this morning after not being selectable for a while. When I got home from some errands earlier, I left it in the driveway, running and plugged in to the charger. Maybe I'll get lucky today and it will install, who knows. It all seems very random.

 

[Smolinski]

My Automatic Updates button was showing as ON this morning after not being selectable for a while. When I got home from some errands earlier, I left it in the driveway, running and plugged it into the charger. Maybe I'll get lucky today and it will install, who knows. It all seems very random.

So here's what happened to me. Yesterday, I was able to turn Automatic Updates and could schedule a time/day. I choose two days from today (Saturday). This morning, I went to the car and check it again, it was enabled for Saturday. I checked my Sync version number (502) and got a number instead of --.

I then went out to do errands with the car and after coming back home, my automatics is off, cannot set time/date and my version was --.

So does this mean? I have no idea, except that it is broke.

 

[dml105]

So here's what happened to me. Yesterday, I was able to turn Automatic Updates and could schedule a time/day. I choose two days from today (Saturday). This morning, I went to the car and check it again, it was enabled for Saturday. I checked my Sync version number (502) and got a number instead of --.

I then went out to do errands with the car and after coming back home, my automatics is off, cannot set time/date and my version was --.

So does this mean? I have no idea, except that it is broke.

Do you have the FordPass widget, or can you go into the JSON on ford.com? What does it say?

Sponsored