OTA 1.7.1 Stuck, anyone else have issue updating?

[Illinibird]

Took Mach E (stuck on 1.7.1) in on 02/07 to give Ford Dealer another try to upgrade (2nd attempt). Ford engineering wanted dealer to retry to make sure the dealership's firewall was not blocking anything. This failed (I am not surprised) and they went back to Ford engineering.
Called dealership 02/15 to get an update on the issue, Ford engineering states that they are releasing software for the programmer at dealership (expected 03/01) that "should" address the issue.
Anyone else get this from their dealer?

I have not heard anything officially from Ford but I have had contact in the past by someone working on this issue that told me a "fix" would be available "soon." I have also heard rumors that the "fix" planned turned out that some cars weren't fixed and that they are still working on it so all cars affected will be corrected by the update (whatever that update will be). Don't know how reliable this information is. I'm still waiting like everybody else. Let's hope March 1st IS the date!

Sponsored

 

[ZuleMME]

As of March I plan to take my car in and demand replacement parts to fix this if there is no update. Tired of waiting.

 

[Illinibird]

As of March I plan to take my car in and demand replacement parts to fix this if there is no update. Tired of waiting.

Do I hear Class Action lawsuit? ?

 

[Jonrd2000]

Wondering, is anyone who is stuck also has their Audio button grayed out? I had CSP 21P22 done and TSB 21-2310 done (APIM failure), but can't remember if it was grayed out before.

 

[macchiaz-o]

Wondering, is anyone who is stuck also has their Audio button grayed out? I had CSP 21P22 done and TSB 21-2310 done (APIM failure), but can't remember if it was grayed out before.

The audio button changes depending on your active audio source. Try checking it while listening to FM radio.

 

[Jonrd2000]

The audio button changes depending on your active audio source. Try checking it while listening to FM radio.

Thanks, I will give that a try. I am always on CarPlay so maybe that's the issue.

 

[MachTee]

Keeping users in dark looks like their corporate policy. I'm watching Ioniq 5 stock now.

Seriously, which auto manufacturer has ever been credited for having great communications? Aside from my MME I have an Ioniq PHEV and Lexus hybrid so I also hang out on those forums. Same kind of complaints there regarding lack of communications. I'm not making excuses for Ford here, and as seemingly useless as it may seem, at least Ford has a rep on the forum here.

 

[Jim_I]

Alright, this is secret stuff so let's just keep it between us, ok?

Update 1.7.1 caused an issue with the base firmware of the APIM (the module it was updating), overall nothing that major.

Now, to do an update either via FDRS or OTA those systems have to do a check of what hardware there is and what software they are running so it can provide the right update files, which are then encrypted for the specific modules on that specific VIN. As has been reported by those with the stuck 1.7.1 the sync software version displays "--", which is what it reports back, which clearly isn't a valid software level.

Which brings us to where things are: stuck. The module will not install software it can't authenticate. It can't verify the new software to update because it can't authenticate the software it has.

The good news is a software fix has been developed. The bad news is an issue was found in testing that could make the problem worse in the unlikely event the phase of the stars aligned while a cat walked under a ladder while smashing a mirror. BUT, in order to not make things even worse for anyone, after that issue was fixed the testing efforts were increased even more which is why the timing is fuzzy.

Just know, there are some people who are still fighting for you, people stuck on 1.7.1!



I may have added a little flourish to the story. Or maybe I made it all up. Either way I don't know when the fix will be released for certain

========================================================

I appreciate what you are saying, and understand how hard it can be to fix a problem remotely. I have been in the computer hardware and software business for over 40 years.

But why does it take three months to tell us anything?

I can deal with a problem if I am being treated honestly.

But when I get nothing despite repeated requests and three trips to my dealer to try to get this corrected, I begin to doubt that it will get corrected.

And you have an even worse problem. My wife is starting to ask if this was the correct vehicle to purchase............... That is not where you want to be!

Figure it out. Put enough people on it to get it corrected. Give me a REAL timeline that you don't miss! And don't waffle back and forth. If it can be done OTA, GREAT! If not, make sure the dealers have everything they need to fix it without the endless back and forth to tech support with no result.

Sorry for the vent.

Jim

 

[Illinibird]

You have that right to vent; I do that too when I am frustrated. This situation has gone on too long and I agree with you that something needs to be done. If there is a"fix" on March 1st then I will be content with that. If not, I think we all should consider our next steps because the car is not working as advertised and so far Ford hasn't been able to figure it out and resolve it.

As far as keeping customers in the dark, I'm helping my Grandson purchase a 2022 Honda Civic Si and Honda doesn't say anything to the customer either. The dealer is pretty much in the dark too until it ships then they can track it. Also, the dealer is allocated a car and they have no say as to what color it will be. I don't know how people who want a certain color get it. In my case, the Si the dealer is getting is the exact color my Grandson wants so he lucked out.

 

[Rob FFE]

I certainly don't want a "fix" that is known to cause more trouble in even a small number of cases. Please, Ford, fix this properly and properly validate the fix. Not doing this is what caused this problem in the first place. At least I, and it seems like the others with the "stuck OTA update", have drivable cars.

 

[Jonrd2000]

I certainly don't want a "fix" that is known to cause more trouble in even a small number of cases. Please, Ford, fix this properly and properly validate the fix. Not doing this is what caused this problem in the first place. At least I, and it seems like the others with the "stuck OTA update", have drivable cars.

I agree. The thought of a bricked Mach E would be a nightmare.

 

[Chudsaviet]

My wife is starting to ask if this was the correct vehicle to purchase...............

I'm already thinking that because of all the problems we have, Mach-E was not a correct vehicle to purchase, and I'm actively looking for another one.
But dealers are going so rampart now so its impossible to buy Ioniq 5 or EV6 with no markup.

 

[Chudsaviet]

I certainly don't want a "fix" that is known to cause more trouble in even a small number of cases. Please, Ford, fix this properly and properly validate the fix. Not doing this is what caused this problem in the first place. At least I, and it seems like the others with the "stuck OTA update", have drivable cars.

There is also a possibility that these "more troubles" are a lie. We haven't got any official feedback other that "the fix is expected in February".

 

[Smolinski]

This is a repeatable software issue. It does not happen once every 3 months, not once every month, but every time. Unless the base code was written that there is no way to change the firmware. All my computer systems allow for firmware changes. Thirty years ago, changing firmware on a computer was iffy, and held your breath that nothing goes wrong. But that was a long time ago.

So, with a repeatable problem and being software, firmware, base code or whatever, it could they are trying methods to hack the code they download so they do not check for base levels or such.

As a support software manager, if I had a Customer that has a problem like this and it dragged on this long, I would be probably be picking up the computer hardware for the bank site. I would be also be updating my resume.

 

[Illinibird]

Part of the problem is that we are the minority of owners experiencing this and apparently they may feel there is no urgency to correct it. I have heard otherwise but with it dragging on I really wonder. I think they are trying to fix the problem by changing the software (or firmware) but they may have to just bite the bullet and have a recall or TSB and replace the APIM module (and any other modules that are involved with the problem). I would imagine that a new APIM module would have new software (and/or new firmware) that functions correctly like the Mach E's not affected. This is out of my pay grade but I know it's gone on way too long and they may have to accept defeat on the work around. Like others, I would hate to "brick" the car with a faulty "fix." Also, I'm not wild to see my dashboard torn up but those who have had that module replaced say their dashboards are fine. It's like the hesitancy we all have with the recall to take the windshield off, re-glue it and re-install it. I never thought I would have all these problems when I bought the car and my wife loves to chide me and say "I told you so" about buying the first model year of the Mustang Mach E. It's ironic that CEO Farley wanted a car with no problems and this ain't it.

Sponsored