OTA 1.7.1 Stuck, anyone else have issue updating?

[Jim_I]

Fingers crossed this thing finally comes out. Every day we wait is getting more and more aggravating.

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

I have just resigned myself to keep calm and enjoy the car until the fix comes through....

Not that I am counting or anything, but there are 31 days until the end of February!!!!

Jim

Sponsored

 

[SashaLondon]

Which is for the US then it takes another month to show up in the UK and then in Europe by the looks of it.

 

[sid234]

If you look on the updates page in the car can you toggle Automatic Updates off and on? That's another one of the symptoms with this failure. My car has failed to update to 1.7.1 at least twice, possibly three times. Also the version number for the Sync software will show---- for the number.

The auto update button was frozen for me until yesterday when I got the car back from the dealer following module updates.

Yesterday evening I noticed that it has changed to ON, I will try toggling back n forth today and report back. I go in on Feb 28 for the glass recall, so maybe there's a fix by then that I can ask them to implement

 

[Bookworm214]

The auto update button was frozen for me until yesterday when I got the car back from the dealer following module updates.

Yesterday evening I noticed that it has changed to ON, I will try toggling back n forth today and report back. I go in on Feb 28 for the glass recall, so maybe there's a fix by then that I can ask them to implement

My Automatic Updates button was on this morning too so I just backed out of the page and left it alone. This has randomly happened before and then the next time I looked it was back to unresponsive.

 

[Bookworm214]

My Job 1 Select is stuck on 1.4.0, though I think it previously installed 1.6.0, built in May but took delivery on 10/11. I’m concerned that the lifecycleMode is TRANSPORT, the car is definitely not in transport mode. Any ideas on how to push things along? I have an appointment for the windshield recall and 21P22 scheduled for the 31st, wonder if that might fix things on Ford’s side?

Hmm, mine says "Normal".

lifeCycleModeStatus: {lifeCycleMode: "NORMAL", oemCorrelationId: "0", vehicleDateTime: "2021-04-05T07:14:56Z",…}
lifeCycleMode: "NORMAL"

 

[sdespain]

So with the announcement of the OTA's OR going to the dealer to get the updates for the Blue Cruise activation in the Feb/March time frame, I am starting to think that for those stuck with the 1.7.1 OTA it will require a dealer visit to get the updates and get our APIM module out of stuck mode. I would think if Ford could do the activation for 100% of the cars via OTA, they would not give the option to go to a dealer for the updates. Again starting to think the option is not going to really be an option for those that are stuck with the 1.7.1 APIM update.

 

[Bookworm214]

So with the announcement of the OTA's OR going to the dealer to get the updates for the Blue Cruise activation in the Feb/March time frame, I am starting to think that for those stuck with the 1.7.1 OTA it will require a dealer visit to get the updates and get our APIM module out of stuck mode. I would think if Ford could do the activation for 100% of the cars via OTA, they would not give the option to go to a dealer for the updates. Again starting to think the option is not going to really be an option for those that are stuck with the 1.7.1 APIM update.

Hoping I get "unstuck" at my Feb. 21st recall appointment.?

 

[CHeil402]

So with the announcement of the OTA's OR going to the dealer to get the updates for the Blue Cruise activation in the Feb/March time frame, I am starting to think that for those stuck with the 1.7.1 OTA it will require a dealer visit to get the updates and get our APIM module out of stuck mode. I would think if Ford could do the activation for 100% of the cars via OTA, they would not give the option to go to a dealer for the updates. Again starting to think the option is not going to really be an option for those that are stuck with the 1.7.1 APIM update.

We'll see if it's available OTA or not, but I wouldn't interpret this to mean it can't be fixed OTA. More options are always a good thing and been asked for multiple times on these forums, so I just take it that Ford is listening to feedback of early adopters.

The BlueCruise OTA might take some time to fully roll out... look at the timing of OTA 1.6.0 even though that one didn't cause a wide issue, it was delivered months apart for some users. It puts the dealers in an awkward position if people are asking for something they should have if they don't at least have the option of installing it for vocal customers.

For reference to those that haven't read the other thread, here's the one referring to the BlueCruise updates: https://www.macheforum.com/site/thr...ting-q1-q2-2022-for-21my-job-1-mach-es.13872/ It also mentions there reference to more rapid OTAs in the future which I pin down to them getting over this 1.7.1 issue.

 

[backwardsfish]

My Job 1 Select is stuck on 1.4.0, though I think it previously installed 1.6.0, built in May but took delivery on 10/11. I’m concerned that the lifecycleMode is TRANSPORT, the car is definitely not in transport mode. Any ideas on how to push things along? I have an appointment for the windshield recall and 21P22 scheduled for the 31st, wonder if that might fix things on Ford’s side?

{
    "displayOTAStatusReport": "UserAllowed",
    "ccsStatus": {
        "ccsConnectivity": "On",
        "ccsVehicleData": "On"
    },
    "error": null,
    "fuseResponse": {
        "fuseResponseList": [
            {
                "vin": "3FMTK1SS5MMXXXXXX",
                "oemCorrelationId": "FIRE-PRD-SOFTWARE-FNV2-453716-446171-3951",
                "deploymentId": "40062bef-1af2-424d-ba50-9d31dc75e2b0",
                "deploymentCreationDate": "2021-11-26T16:24:58.517+0000",
                "deploymentExpirationTime": "2021-12-03T16:24:58.517+0000",
                "otaTriggerExpirationTime": "2021-11-29T16:24:24.947+0000",
                "communicationPriority": "low",
                "type": "ENHANCEMENT",
                "triggerType": "SOFTWARE",
                "inhibitRequired": false,
                "additionalConsentLevel": 1,
                "tmcEnvironment": "PRD",
                "latestStatus": {
                    "aggregateStatus": "success",
                    "detailedStatus": "OTAM_S1010",
                    "dateTimestamp": "2021-11-26T17:12:38.561+0000"
                },
                "packageUpdateDetails": {
                    "releaseNotesUrl": "https://mmota.autonomic.ai/1/bytestream/custom-release-note-1624900253745-fe2b4fde-a3e1-43c9-a11c-751d0037f578",
                    "updateDisplayTime": 0,
                    "wifiRequired": false,
                    "packagePriority": 1,
                    "failedOnResponse": "none",
                    "cdnreleaseNotesUrl": "http://vehicleupdates.files.ford.com/release-notes/custom-release-note-1624900253745-fe2b4fde-a3e1-43c9-a11c-751d0037f578"
                },
                "deploymentFinalConsumerAction": "Not Set"
            }
        ],
        "languageText": {
            "Language": "English (US/NA)",
            "LanguageCode": "ENU",
            "LanguageCodeMobileApp": "en-US",
            "Text": "FordPower-Up 1.4.0\n\nNew SecuriAlert™\n\nSecuriAlert gives you extra peace of mind by alerting you through the latest version of the FordPass™ app (3.26) whenever a door is opened. Ongoing updates like this help ensure that you’re always driving the best possible version of your Mustang Mach-E."
        }
    },
    "tappsResponse": {
        "vin": "3FMTK1SS5MMXXXXXX",
        "status": 200,
        "vehicleInhibitStatus": null,
        "lifeCycleModeStatus": {
            "lifeCycleMode": "TRANSPORT",
            "oemCorrelationId": "0",
            "vehicleDateTime": "2021-07-07T07:04:27Z",
            "tappsDateTime": "2021-11-22T23:17:12.595Z"
        },
        "asuActivationSchedule": {
            "scheduleType": "",
            "dayOfWeekAndTime": null,
            "activationScheduleDaysOfWeek": [],
            "activationScheduleTimeOfDay": null,
            "oemCorrelationId": "",
            "vehicleDateTime": "",
            "tappsDateTime": ""
        },
        "asuSettingsStatus": null,
        "version": "2.0.0"
    },
    "updatePendingState": null,
    "otaAlertStatus": "YOU ARE ALL SET"
}

I too just noticed mine reports
"lifeCycleMode": "TRANSPORT"


While I see most of you with successful updates says life is NORMAL.

My Job 1 Select is stuck on 1.4.0, though I think it previously installed 1.6.0, built in May but took delivery on 10/11. I’m concerned that the lifecycleMode is TRANSPORT, the car is definitely not in transport mode. Any ideas on how to push things along? I have an appointment for the windshield recall and 21P22 scheduled for the 31st, wonder if that might fix things on Ford’s side?

{
    "displayOTAStatusReport": "UserAllowed",
    "ccsStatus": {
        "ccsConnectivity": "On",
        "ccsVehicleData": "On"
    },
    "error": null,
    "fuseResponse": {
        "fuseResponseList": [
            {
                "vin": "3FMTK1SS5MMXXXXXX",
                "oemCorrelationId": "FIRE-PRD-SOFTWARE-FNV2-453716-446171-3951",
                "deploymentId": "40062bef-1af2-424d-ba50-9d31dc75e2b0",
                "deploymentCreationDate": "2021-11-26T16:24:58.517+0000",
                "deploymentExpirationTime": "2021-12-03T16:24:58.517+0000",
                "otaTriggerExpirationTime": "2021-11-29T16:24:24.947+0000",
                "communicationPriority": "low",
                "type": "ENHANCEMENT",
                "triggerType": "SOFTWARE",
                "inhibitRequired": false,
                "additionalConsentLevel": 1,
                "tmcEnvironment": "PRD",
                "latestStatus": {
                    "aggregateStatus": "success",
                    "detailedStatus": "OTAM_S1010",
                    "dateTimestamp": "2021-11-26T17:12:38.561+0000"
                },
                "packageUpdateDetails": {
                    "releaseNotesUrl": "https://mmota.autonomic.ai/1/bytestream/custom-release-note-1624900253745-fe2b4fde-a3e1-43c9-a11c-751d0037f578",
                    "updateDisplayTime": 0,
                    "wifiRequired": false,
                    "packagePriority": 1,
                    "failedOnResponse": "none",
                    "cdnreleaseNotesUrl": "http://vehicleupdates.files.ford.com/release-notes/custom-release-note-1624900253745-fe2b4fde-a3e1-43c9-a11c-751d0037f578"
                },
                "deploymentFinalConsumerAction": "Not Set"
            }
        ],
        "languageText": {
            "Language": "English (US/NA)",
            "LanguageCode": "ENU",
            "LanguageCodeMobileApp": "en-US",
            "Text": "FordPower-Up 1.4.0\n\nNew SecuriAlert™\n\nSecuriAlert gives you extra peace of mind by alerting you through the latest version of the FordPass™ app (3.26) whenever a door is opened. Ongoing updates like this help ensure that you’re always driving the best possible version of your Mustang Mach-E."
        }
    },
    "tappsResponse": {
        "vin": "3FMTK1SS5MMXXXXXX",
        "status": 200,
        "vehicleInhibitStatus": null,
        "lifeCycleModeStatus": {
            "lifeCycleMode": "TRANSPORT",
            "oemCorrelationId": "0",
            "vehicleDateTime": "2021-07-07T07:04:27Z",
            "tappsDateTime": "2021-11-22T23:17:12.595Z"
        },
        "asuActivationSchedule": {
            "scheduleType": "",
            "dayOfWeekAndTime": null,
            "activationScheduleDaysOfWeek": [],
            "activationScheduleTimeOfDay": null,
            "oemCorrelationId": "",
            "vehicleDateTime": "",
            "tappsDateTime": ""
        },
        "asuSettingsStatus": null,
        "version": "2.0.0"
    },
    "updatePendingState": null,
    "otaAlertStatus": "YOU ARE ALL SET"
}

Me too, TRANSPORT Mode.

Mean anything?

 

[Kabish]

So a little update on my 1.7.1 Update issue.

I took it into the dealer, they had it about 4hrs and applied the TSB 21-2310 to the car and got it "unstuck" and 1.7.1 was working on the car finally. Today I got a FordPass message saying 2.3.0 installed, checked the car and sure enough its installed!

I was really worried that the TSB was only a workaround and I'd still have issues with OTA. But it seems like, at least for my VIN, the above TSB fixed the 1.7.1 issue and also allowed sucessful OTA about three weeks later.

 

[Illinibird]

So a little update on my 1.7.1 Update issue.

I took it into the dealer, they had it about 4hrs and applied the TSB 21-2310 to the car and got it "unstuck" and 1.7.1 was working on the car finally. Today I got a FordPass message saying 2.3.0 installed, checked the car and sure enough its installed!

I was really worried that the TSB was only a workaround and I'd still have issues with OTA. But it seems like, at least for my VIN, the above TSB fixed the 1.7.1 issue and also allowed sucessful OTA about three weeks later.

This is what they say about TSB 21-2310:

Bulletin Number: TSB 21-2310

Replacement Service Bulletin Number: N/A

NHTSA Item Number: 10202700

Date Posted: 10/12/21

Component Name: 353630 EQUIPMENT: ELECTRICAL: INFOTAINMENT: BLUETOOTH/WIFI

Make: FORD

Model: MACH-E

Year: 2021

Date Added: 11/2/21

Summary: Some 2021 Mach-E/F-150 vehicles may experience at least one of the following symptoms: audio settings resetting after a key cycle, Android Auto connection concerns, Sirius presets missing more than three pages after a key cycle, Information

It doesn't address the problem we are having with 1.7.1 so I don't know how it "fixed" the 1.7.1 problem. It was added 11/2/21 and you would think if that is what is needed we all would have heard something about it already. I have been told a "fix" won't happen until February.

 

[Kabish]

It doesn't address the problem we are having with 1.7.1 so I don't know how it "fixed" the 1.7.1 problem. It was added 11/2/21 and you would think if that is what is needed we all would have heard something about it already. I have been told a "fix" won't happen until February.

Not sure why I would have any reason to come on here lying, just sharing my experience.

My car attempted 1.7.1 back in like September maybe... My car's display went black, before I knew that was a symptom of 1.7.1 installing, so I rebooted Sync to get my display back. About an hour later I got the message saying the update failed. I dunno, maybe a month or two later I started to have the odd ball symptoms of 1.7.1 installing again. This time however I never got any status update. I did get a screen that said 1.7.1 once, then I never saw it again. When going to the car to check for updates just said it was up to date, and the option to turn on auto update would not set. I would turn it on, and it would just toggle off right away. Same thing with the schedule aspect, tried to turn it on and it would go right back off. So there was no way to allow the car to receive an OTA because 1.7.1 mucked things up.

Attached are the service notes. My car was stuck on 1.7.1 for a good amount of time, after they did that I had a working 1.7.1 and now working 2.3.0. It is what was done to my car that corrected the issue at least for me.

 

[Gimme_my_MME]

There are a few known error states resulting in 1.7.1 to fail and it to lock up. Over the last week or so, some have been able to be corrected, but not many. The ones that can't will need the other fix to get past 1.7.1

 

[Illinibird]

Not sure why I would have any reason to come on here lying, just sharing my experience.

My car attempted 1.7.1 back in like September maybe... My car's display went black, before I knew that was a symptom of 1.7.1 installing, so I rebooted Sync to get my display back. About an hour later I got the message saying the update failed. I dunno, maybe a month or two later I started to have the odd ball symptoms of 1.7.1 installing again. This time however I never got any status update. I did get a screen that said 1.7.1 once, then I never saw it again. When going to the car to check for updates just said it was up to date, and the option to turn on auto update would not set. I would turn it on, and it would just toggle off right away. Same thing with the schedule aspect, tried to turn it on and it would go right back off. So there was no way to allow the car to receive an OTA because 1.7.1 mucked things up.

Attached are the service notes. My car was stuck on 1.7.1 for a good amount of time, after they did that I had a working 1.7.1 and now working 2.3.0. It is what was done to my car that corrected the issue at least for me.

I just printed out what was said about that TSB. I didn't accuse you of lying. I'm not sure either what's happening with 1.7.1 just that I've been told by some of the Ford insiders that the fix for our problem won't happen until sometime in February. If your problem was fixed then I'm glad for you and wonder why Ford is telling us they are developing a fix if they already have one. It is confusing. Bottom line, I wonder what's going on with this issue. I defer to the post before this by Gimme_My_MME.

 

[macchiaz-o]

Which is for the US then it takes another month to show up in the UK and then in Europe by the looks of it.

Sure, due to global shipping delays, lack of boats, crew members, etc. ?

Sponsored