OTA 1.7.1 Stuck, anyone else have issue updating?

[dml105]

Well, my car is finally at the body shop, having the tail light replaced from the unwarranted parking bollard assault earlier this fall. I did play around with the URL posted in this thread: https://www.macheforum.com/site/threads/ota-status-hidden-in-the-ford-website.12367/ and got some interesting information. It looks like it may have tried to get most of the way through 1.7.1?

Just took a swing through that page. Sure enough, it reports a 1.7.1 failure.

{displayOTAStatusReport: "UserAllowed", ccsStatus: {ccsConnectivity: "On", ccsVehicleData: "On"},…}
ccsStatus: {ccsConnectivity: "On", ccsVehicleData: "On"}
displayOTAStatusReport: "UserAllowed"
error: null
fuseResponse: {,…}
fuseResponseList: [{vin: "3FMTK3SU5MMAxxxxx", oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304",…}]
0: {vin: "3FMTK3SU5MMAxxxxx", oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304",…}
additionalConsentLevel: 1
communicationPriority: "HIGH"
deploymentCreationDate: "2021-11-10T17:38:12.615+0000"
deploymentExpirationTime: "2021-11-17T17:38:12.615+0000"
deploymentFinalConsumerAction: "Not Set"
deploymentId: "99d6d023-92ff-4401-8a45-258b87500ced"
inhibitRequired: false
latestStatus: {aggregateStatus: "failure", detailedStatus: "OTAM_E1016",…}
aggregateStatus: "failure"
dateTimestamp: "2021-11-11T17:59:31.645+0000"
detailedStatus: "OTAM_E1016"
oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304"
otaTriggerExpirationTime: "2021-10-01T13:44:30.201+0000"
packageUpdateDetails: {,…}
tmcEnvironment: "PRD"
triggerType: "SOFTWARE"
type: "NEW_FEATURE"
vin: "3FMTK3SU5MMAxxxxx"
languageText: {Language: "English (US/NA)", LanguageCode: "ENU", LanguageCodeMobileApp: "en-US",…}
otaAlertStatus: "YOU ARE ALL SET"
tappsResponse: {vin: "3FMTK3SU5MMAxxxxx", status: 200, vehicleInhibitStatus: null,…}
updatePendingState: null

Sponsored

 

[MachTee]

So, reading that Mach-e updates while you are driving (which I find weird, honestly), how long do you have to drive in order for the update to complete? Is my problem that since the pandemic started, I've mostly only taken my car out for short drives not long enough to update?

What if I left it "ON" in my garage for a few hours? How long is long enough?

The first time I pressed the 1.7.1 update button in my car, I shut it off right away. Ended up with the stuck update and I questioned myself if it was because I shut it off.. Router showed it downloaded ~5GB of stuff. (My first 3 OTA updates prior to 1.7.1 - bug fix, 1.4 and 1.6 - I also shut it off after I pressed the update button and they went fine.)

About 3 weeks later I pressed the 1.7.1 update button for the second time, as soon as I saw the down arrow appeared on the screen and I pulled into the garage. I left the car on. Made no difference, was stuck once again. Router showed it download about 4GB of stuff.

Another couple of weeks later I pressed the update button for the third time. As above I left it on as soon as I pulled into the garage, and monitored the download on my laptop right in the car. It stopped at 4GB again. Thinking it failed came here and posted/whined about it while still in the car, and shut off the car. Watched my wifi traffic for the next 10 minutes or so, no further download activity. Started the car a few minutes later expecting to be greeted with -- on the Sync version again. Nope, it showed updated version. It successfully installed 1.7.1.

Sorry for the long winded post, but I thought I'd be as detailed as possible in how my install process went, as perhaps it was some magic involved with the steps I took. Also, between steps 2 and 3, Ford contacted me here over PM and opened a case for me. I don't know if they did something on their end, so you might want to replicate that step too.

Good luck.

 

[Jimrpa]

Just took a swing through that page. Sure enough, it reports a 1.7.1 failure.

{displayOTAStatusReport: "UserAllowed", ccsStatus: {ccsConnectivity: "On", ccsVehicleData: "On"},…}
ccsStatus: {ccsConnectivity: "On", ccsVehicleData: "On"}
displayOTAStatusReport: "UserAllowed"
error: null
fuseResponse: {,…}
fuseResponseList: [{vin: "3FMTK3SU5MMAxxxxx", oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304",…}]
0: {vin: "3FMTK3SU5MMAxxxxx", oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304",…}
additionalConsentLevel: 1
communicationPriority: "HIGH"
deploymentCreationDate: "2021-11-10T17:38:12.615+0000"
deploymentExpirationTime: "2021-11-17T17:38:12.615+0000"
deploymentFinalConsumerAction: "Not Set"
deploymentId: "99d6d023-92ff-4401-8a45-258b87500ced"
inhibitRequired: false
latestStatus: {aggregateStatus: "failure", detailedStatus: "OTAM_E1016",…}
aggregateStatus: "failure"
dateTimestamp: "2021-11-11T17:59:31.645+0000"
detailedStatus: "OTAM_E1016"
oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-405484-435304"
otaTriggerExpirationTime: "2021-10-01T13:44:30.201+0000"
packageUpdateDetails: {,…}
tmcEnvironment: "PRD"
triggerType: "SOFTWARE"
type: "NEW_FEATURE"
vin: "3FMTK3SU5MMAxxxxx"
languageText: {Language: "English (US/NA)", LanguageCode: "ENU", LanguageCodeMobileApp: "en-US",…}
otaAlertStatus: "YOU ARE ALL SET"
tappsResponse: {vin: "3FMTK3SU5MMAxxxxx", status: 200, vehicleInhibitStatus: null,…}
updatePendingState: null

Thanks! I wonder what the status means?

 

[RonTCat]

The first time I pressed the 1.7.1 update button in my car, I shut it off right away. Ended up with the stuck update and I questioned myself if it was because I shut it off.. Router showed it downloaded ~5GB of stuff. (My first 3 OTA updates prior to 1.7.1 - bug fix, 1.4 and 1.6 - I also shut it off after I pressed the update button and they went fine.)

About 3 weeks later I pressed the 1.7.1 update button for the second time, as soon as I saw the down arrow appeared on the screen and I pulled into the garage. I left the car on. Made no difference, was stuck once again. Router showed it download about 4GB of stuff.

Another couple of weeks later I pressed the update button for the third time. As above I left it on as soon as I pulled into the garage, and monitored the download on my laptop right in the car. It stopped at 4GB again. Thinking it failed came here and posted/whined about it while still in the car, and shut off the car. Watched my wifi traffic for the next 10 minutes or so, no further download activity. Started the car a few minutes later expecting to be greeted with -- on the Sync version again. Nope, it showed updated version. It successfully installed 1.7.1.

Sorry for the long winded post, but I thought I'd be as detailed as possible in how my install process went, as perhaps it was some magic involved with the steps I took. Also, between steps 2 and 3, Ford contacted me here over PM and opened a case for me. I don't know if they did something on their end, so you might want to replicate that step too.

Good luck.

Yes, process matters. It shouldn't, but it does.

 

[Jonrd2000]

I have been in contact with the Early Access Team, and had told them I had an appointment with my dealer next week for the CSP. They just told me not to take it in, that the issue everyone is having is a special issue (and I am inferring that taking it in for the CSP won't fix it). They are preparing a communication to the owners of the affected vehicles.

 

[Dylancch]

I got mine manually installed by dealer all I have noticed is that I'm able to charge 30kw when I'm over 80%. And that's with a cold battery so might be more it's-25c outside

 

[Jonrd2000]

I got mine manually installed by dealer all I have noticed is that I'm able to charge 30kw when I'm over 80%. And that's with a cold battery so might be more it's-25c outside

Are you saying that you were previously stuck on 1.7.1, the dealer installed CSP 21P22, and you are still stuck?

 

[Dylancch]

Not sure what version it is. Doesn't say but they had it for 5 hours updating and they said they did all available updates

 

[Illinibird]

So update, I finally got my car back after having the apim replaced. It seemed to fix the update issue as I now have note and a (non working) frunk button. Also not sure how, but my car now fast charges past 80% all the way up to 90% I was getting between 40 and 50 kw charging

I'm bringing my car back for the dealer to perform Startup 1.7.1 because they failed to do it on the previous visit. I'm going to ask to have the APIM module replaced if they cannot program the car. Charity, from Ford EAP, said the dealer would have to replace the "module" without specifying which one. I hope I have your luck if we go this route because OTA 1.7.1 has failed to download and update for the last 2 months..

 

[CHeil402]

Charity, from Ford EAP, said the dealer would have to replace the "module" without specifying which one. I hope I have your luck if we go this route because OTA 1.7.1 has failed to download and update for the last 2 months..

I've also been working with their team on this issue since my PowerUp 1.7.1 has also be stuck for a few months. The latest update I received was that if you're in the same boat, all that a dealer can do at this point is replace the APIM module to resolve the issue. They're currently working on a remote software fix such that replacing the APIM module isn't necessary, nor would be a trip to the dealer. I'm letting them use my car as a guinea pig on the fix on everyone's behalf. I'll keep everyone posted.

In summary, if you can't wait for a remote fix, the only course of action would be to have a dealer replace the APIM. If you can wait, as I'm doing, there should hopefully soon be a remote fix for this. Aside from obviously not having the update which would improve a few things, my car is perfectly fine so I'd rather not have my dealer take the car apart to replace a module and risk any side effects with that... at least until there are no other options.

 

[Illinibird]

I've also been working with their team on this issue since my PowerUp 1.7.1 has also be stuck for a few months. The latest update I received was that if you're in the same boat, all that a dealer can do at this point is replace the APIM module to resolve the issue. They're currently working on a remote software fix such that replacing the APIM module isn't necessary, nor would be a trip to the dealer. I'm letting them use my car as a guinea pig on the fix on everyone's behalf. I'll keep everyone posted.

In summary, if you can't wait for a remote fix, the only course of action would be to have a dealer replace the APIM. If you can wait, as I'm doing, there should hopefully soon be a remote fix for this. Aside from obviously not having the update which would improve a few things, my car is perfectly fine so I'd rather not have my dealer take the car apart to replace a module and risk any side effects with that... at least until there are no other options.

She told me the same thing actually. It’s been over two months and I’m losing confidence in the EAP/OTA Teams being able to correct this. I thought replacing the APIM module might be a quicker fix than waiting who knows how long. But I agree with you that I’m not wild about them messing with replacing the module in case they cause other damage to the car. I’m going to think about this and maybe cancel Monday’s appointment. My car is running well and the two glass recalls went smoothly. I’m just impatient I guess.

 

[Logal727]

She told me the same thing actually. It’s been over two months and I’m losing confidence in the EAP/OTA Teams being able to correct this. I thought replacing the APIM module might be a quicker fix than waiting who knows how long. But I agree with you that I’m not wild about them messing with replacing the module in case they cause other damage to the car. I’m going to think about this and maybe cancel Monday’s appointment. My car is running well and the two glass recalls went smoothly. I’m just impatient I guess.

I wouldn't let the dealer touch the car if you can avoid it (outside recalls, of course). So many chances of things getting dinged up or software made worse cause these vehicles are so new, maybe once there's more around I'd feel more comfortable.

 

[Jeffvisor]

Are you saying that you were previously stuck on 1.7.1, the dealer installed CSP 21P22, and you are still stuck?

Yes for me. Stuck 1.7.1 had CSP-21O22 done and still stuck.

 

[theganyo]

When my update failed, it disabled automatic updates and I can’t turn it back on. I recently opened a case with Ford over this issue and after having me do a “key cycle” and “module reset” without effect they said I’d have to take it to a dealer.

 

[Jonrd2000]

Yes for me. Stuck 1.7.1 had CSP-21O22 done and still stuck.

This is very helpful, thanks.

Sponsored