OTA 1.7.1 Stuck, anyone else have issue updating?

[macchiaz-o]

It was.

I went out and switched it to automatic updates. 20 minutes later Fordpass showed a successful update...but I still have no idea which update it is.

And, the notice on Fordpass won't go away, there's no clear or delete available. It just says Update Successful, check out what's new and goes on with happy talk about bug fixes.

All I want to know is what number update is it?

Oh, and I pressed the volume control.... no calm screen so I didn't get THAT one.

Reaching inner zen requires holding in the volume wheel for at least half a second. And Power-Up 1.7.1 or 2.3.0, of course. ?

Sponsored

 

[RSH]

It was.

I went out and switched it to automatic updates. 20 minutes later Fordpass showed a successful update...but I still have no idea which update it is.

And, the notice on Fordpass won't go away, there's no clear or delete available. It just says Update Successful, check out what's new and goes on with happy talk about bug fixes.

All I want to know is what number update is it?

Oh, and I pressed the volume control.... no calm screen so I didn't get THAT one.

Do you have Notes now?

 

[Ajax]

My contact at the Ford OTA IVT escalations has informed me that the engineering team is actively working on a fix for this exact issue, but the ETA is not yet known. An ETA should be forthcoming, according to her, by mid next week.

It's not much, and I'm as frustrated as you are. But they are trying to make it happen as an OTA for those of us who are stuck.
The last resort will indeed be a full APIM replacement if that fails. But at least it's under warranty!

I'm happy to wait a week or two for such a fix, but it's getting frustrating being stuck at a half-downloaded 1.7.1 for 2 months. Keep us posted on any ETA you get, otherwise I will probably schedule service at my dealership to see how competent they are at servicing a Mach-E. Thanks for this update!

 

[Carsinmyblood]

Do you have Notes now?

No, it doesn't seem so.

 

[Smolinski]

So, I used to work in the computer field, so a problem could be hardware or software. So, you had two paths to follow. Also, how often the problem occurs played a factor. If the problem only happens once a month, it would take a long time to identify and fix.

So, with this problem occurring quite frequently, they should have a good idea of what is happening.

To fix it is an interesting point. If it is truly a hardware problem then a part has to be swapped in. You just have to worry about logistics and costs.

If it is software, then you have to write the code, test it and then deploy it. The question is how to deploy it when the OTA is broken. It may mean a trip to the dealer to install it.

If the piece of software is the firmware (which lies deep in the hardware), then the solution would be to swap the hardware or install the firmware, probably with the USB interface.

I had the problem for about a month. I am sure that other folks are in the same category, so I cannot believe that Ford has not seen it and identified it already.

Since the problem occurs so frequently, there have to be several solutions for this problem. Again, it comes down to cost and logistics.

So acknowledgment that is a common issue, where they are in solving it, what is the ETA for that and the course of action would be appreciated.

So at least the forum is a good idea and keeping each other informed is good.

 

[Bookworm214]

Like several other people in this thread, I'll add my Mach-E to the list of those stuck with a failed 1.7.1 update. It failed sometime back in November. It just says that it's "Up to date" with no version number. I can't schedule a time to update or turn on automatic updates. Touching the automatic update toggle doesn't move it to the On position and sliding it to the right doesn't change the color to indicate it's on. I have an appt. for the glass recalls on the 24th so I guess I'll wait until then to have the dealer check it out.

 

[Jeffvisor]

Hello! Send us a private message with your MachE’s VIN and current mileage. Allow me to see what I can do to assist. Thanks!

Yea I did that you referred me to tech named Charles Chapman who told me to tell the dealer my problem and they know how to fix it. Here is my story bottom line is it was not fixed because dealer does not know how to fix it.....

I have been stuck on update 1.7.1 since the beginning of Oct. I got the 21P22 and still stuck. My car was just returned yesterday from the dealer who had it for 3.5 weeks doing the windshield and glass roof repair. I been in contact with @Ford about my stuck update. I had a technician tell mee from Ford just tell the dealer your stuck they will know what to do. Well no offense but I didnt trust the dealer to know so I researched it and printed out the the 3 TSB's other in here said they used to fix the stuck problem 21-2249, 21-2310, 21-2405. I gave them all to the dealer to do. After having the car for 3.5 weeks and multiple text messages to the dealer telling them to please do the updates while my car was there almost a full month he calls and says you car is ready I asked if he did the software updates he said no. I was upset sent him the message from the Ford technician Charles Chapman telling me what to tell the dealer. He kept it an extra day says in the work order he updated to Power up 1.7.1 (which i heard the dealer cant do). I finally got my car back yesterday and still stuck on 1.7.1. Never got updated. UGH!!!! Charles Chapman instead of asking me to tell the dealer what to do should have called the dealer with specifics of what to do. Either do all the updates or replace the APIM which i also mentioned to the dealer might be the issue.

 

[Jim_I]

So, I used to work in the computer field, so a problem could be hardware or software. So, you had two paths to follow. Also, how often the problem occurs played a factor. If the problem only happens once a month, it would take a long time to identify and fix.

So, with this problem occurring quite frequently, they should have a good idea of what is happening.

To fix it is an interesting point. If it is truly a hardware problem then a part has to be swapped in. You just have to worry about logistics and costs.

If it is software, then you have to write the code, test it and then deploy it. The question is how to deploy it when the OTA is broken. It may mean a trip to the dealer to install it.

If the piece of software is the firmware (which lies deep in the hardware), then the solution would be to swap the hardware or install the firmware, probably with the USB interface.

I had the problem for about a month. I am sure that other folks are in the same category, so I cannot believe that Ford has not seen it and identified it already.

Since the problem occurs so frequently, there have to be several solutions for this problem. Again, it comes down to cost and logistics.

So acknowledgment that is a common issue, where they are in solving it, what is the ETA for that and the course of action would be appreciated.

So at least the forum is a good idea and keeping each other informed is good.

-------------------------------------------------------------------------------------

I have also been in the computer hardware and software business for over 40 years. I agree with most of what you say. IMHO, it is a hardware problem in a small batch of parts that came to light from an unintended consequence of the 1.7.1 software update it was trying to load. Most likely in the APIM. I only say this from reading all the posts here, where a replacement of the APIM seems to have corrected the issue. Again, this is totally a guess on my part.

So lets assume Ford knows exactly what the problem is with the Job 1 cars that are stuck in 1.7.1 update limbo. And they realize they are most likely going to have to replace X number of these modules.

With worldwide chip shortages, Ford may not be able to quickly get enough of the replacement parts they need to both continue production of new vehicles and repair the units that have failed.

So what do they do? Do they shut down the assembly line to satisfy the purchasers of exiting vehicles for a positive customer experience, or do they lay off several hundred employees and shut down production? That of course makes new purchasers unhappy, the stock holders furious, and gives the press a chance to pounce on these types of issues. That decision is way above my pay grade!!

Another option is to try to write a software workaround for the hardware issue. This can work for this particular issue, but what else might that affect in the future? In other words, it could ease the current pain, but come back in a year or so and everyone is right back in the same situation.

I have always believed in telling my customers exactly what is going on. And give them a real timeline of when they can expect to have the problem corrected. Not getting anything directly from Ford management is what has me upset the most.

JMHO.

Jim

 

[MachTee]

I feel like I really lucked out. Quite recap, my car was stuck for about 2 months. It attempted the install twice and failed. Third time was about a week after I PM Ford here with my VIN and it successfully installed. And 2.1.0 just installed couple days ago with no issue.

 

[Illinibird]

-------------------------------------------------------------------------------------

I have also been in the computer hardware and software business for over 40 years. I agree with most of what you say. IMHO, it is a hardware problem in a small batch of parts that came to light from an unintended consequence of the 1.7.1 software update it was trying to load. Most likely in the APIM. I only say this from reading all the posts here, where a replacement of the APIM seems to have corrected the issue. Again, this is totally a guess on my part.

So lets assume Ford knows exactly what the problem is with the Job 1 cars that are stuck in 1.7.1 update limbo. And they realize they are most likely going to have to replace X number of these modules.

With worldwide chip shortages, Ford may not be able to quickly get enough of the replacement parts they need to both continue production of new vehicles and repair the units that have failed.

So what do they do? Do they shut down the assembly line to satisfy the purchasers of exiting vehicles for a positive customer experience, or do they lay off several hundred employees and shut down production? That of course makes new purchasers unhappy, the stock holders furious, and gives the press a chance to pounce on these types of issues. That decision is way above my pay grade!!

Another option is to try to write a software workaround for the hardware issue. This can work for this particular issue, but what else might that affect in the future? In other words, it could ease the current pain, but come back in a year or so and everyone is right back in the same situation.

I have always believed in telling my customers exactly what is going on. And give them a real timeline of when they can expect to have the problem corrected. Not getting anything directly from Ford management is what has me upset the most.

JMHO.

Jim

Agree with your logic and I have mentioned this to the Ford rep(s) I have talked to asking them if they are trying to prevent having another TSB to replace the APIM. I forgot about the logistics of doing this with the current chip shortage and you have brought that back into focus. I’m sure this is why they would prefer a software solution. I have been told when the “fix” is announced that it will have to be done at the dealer (and I conjecture they can either flash the module or replace it if there are sufficient numbers of the APIM modules available). All of this is above my pay grade too so it’s pure speculation right now.

 

[ZuleMME]

I too am in the stuck state. Been through two cycles of it. If you aren’t aware the FordPass widget for iOS or the website viewing thread can show you the dates set for the ota. Once it expires the sync system seems to reset within a couple drives and go back to its previous release. Then it tries again if they send a new ota request to the car… my next expire date is 1/11.

 

[dougni]

I too am in the stuck state. Been through two cycles of it. If you aren’t aware the FordPass widget for iOS or the website viewing thread can show you the dates set for the ota. Once it expires the sync system seems to reset within a couple drives and go back to its previous release. Then it tries again if they send a new ota request to the car… my next expire date is 1/11.

I got my first OTA on Dec 14th. It was 1.6 then it changed to 1.4. Not sure what happened. Then, on the 16th started 1.7.1. Now it shows expired since Dec 30. Hasn't attempted a new install/download since.

 

[slambertr]

I'm still stuck - from November 24th. Today the app randomly stopped updating my charging status. Honestly - I'm afraid to take it to the dealer until (thanks to all of you) we know they can actually fix it and get me to the promised land (aka 2.3.0). I also had to have the axles replaced in early November.
I love this car but, yeah, its frustrating....

 

[SashaLondon]

I have a Ford contact trying to get me to make an appointment to get the dealer to fix the update. Not sure if I should and also it’s a full day off for me to do this.

 

[Bookworm214]

Does your option for automatic updates still let you turn it off and on?

If that's still working, You're probably good to go.

That's one of the symptoms my car is showing. I can't turn automatic updates on or set a scheduled time.

Sponsored