OTA 1.7.1 Stuck, anyone else have issue updating?

[Gimme_my_MME]

so, guys this is very odd, my dealer called me yesterday and they said that when they put my vin in their system it shows that the TSB 22-2117 isn't applicable for my vehicle...

any ideas why? I'm def stuck since November on 1.6 and I have all the symptoms.

May not have populated all the VINs in the system yet. But if you have the symptoms then it applies to you

Sponsored

 

[benk016]

so, guys this is very odd, my dealer called me yesterday and they said that when they put my vin in their system it shows that the TSB 22-2117 isn't applicable for my vehicle...

any ideas why? I'm def stuck since November on 1.6 and I have all the symptoms.

The only requirements are that its a 2021 Mach E or F150, and that it has the update failure or no OTA history, and APIM or TCU updates fail.

It shouldn't be VIN specific.

 

[SashaLondon]

Could it that there isn’t an OTA in the cloud to download after this fix for me?

 

[SashaLondon]

Maybe I could give my vin to someone who can check what is outstanding in fdrs? Then can see more info maybe?

 

[trenz]

Could it that there isn’t an OTA in the cloud to download after this fix for me?

I believe you should be seeing a version number for sync and power ups

 

[ZuleMME]

Actually I’m curious if after this fix does the serial number for the APIM show up in bezel diagnostics?

 

[Jonrd2000]

I'm scheduled, first available appointment was next week.

Optimistic view - I'll get it fixed that much sooner.
Pessimistic view - I'll be towards the front of the line for an APIM replacement order

I also just got scheduled for Thursday. Going for broke.

 

[Jonrd2000]

I’ll think we’ll know soon whether this broadly works or not by next week, just checking this thread. Seems already many appts for next week.

 

[RSH]

The only requirements are that its a 2021 Mach E or F150, and that it has the update failure or no OTA history, and APIM or TCU updates fail.

It shouldn't be VIN specific.

One requirement according to an earlier post is that you receive failure to update notices onscreen or in fordpass. I never have gotten a failure notice in those places. I do see failure notices in the widget. Hope that's not what's going on.

 

[benk016]

One requirement according to an earlier post is that you receive failure to update notices onscreen or in fordpass. I never have gotten a failure notice in those places. I do see failure notices in the widget. Hope that's not what's going on.

Those failure notices on fordpass or the car clear after so long though. Even on Ford's side the OTA history is only kept for 60 days.

 

[trenz]

Those failure notices on fordpass or the car clear after so long though. Even on Ford's side the OTA history is only kept for 60 days.

For me the message in Ford pass is still there since November, I never deleted it.

 

[benk016]

For me the message in Ford pass is still there since November, I never deleted it.

Oh nice. I've had some of mine clear out on their own. But I've also never had a failure notice so maybe some messages don't clear on their own from fordpass.

 

[Gimme_my_MME]

But I've also never had a failure notice

That must be nice

 

[troublebot]

Could it that there isn’t an OTA in the cloud to download after this fix for me?

My understanding is that OTAs couldn't be applied via FDRS (I could be wrong), maybe this procedure just unbricks the system from not accepting updates and 1.7.1 will casually roll in? Or maybe the tech didn't do the last one or two steps of the TSB that tell them to go perform additional updates? Dunno, as a stuckee I surely hope this is a guaranteed fix.

 

[Jeffvisor]

I will be curious when we get the fix if they update us to the current powerup or just unfreeze Powerup 1.7.1 and we have to get the rest of the many Powerups we missed via OTA.

Sponsored