System update fault, vehicle not driveable

[Nighsight]

Came out to the truck after work and this fault showed as soon as I opened the door. Vehicle powered down on its own. Started the vehicle and drove away. Anyone see this before?

Sponsored

 

[rugedraw]

I have not. Post or PM me your VIN and I can look up any DTC's your truck recorded and any recent updates your truck got that may have possibly caused that.

 

[thebigdu]

Came out to the truck after work and this fault showed as soon as I opened the door. Vehicle powered down on its own. Started the vehicle and drove away. Anyone see this before?

I know @Snakebitten will find a way to put positive spin on this with his effusive optimism , but I find it kind of unacceptable. I guess we're entering a "whole new world" with OTA updates to our vehicles, but under no circumstances should they be left undriveable due to a botched update. Individuals messing with FDRS or Forscan is one thing; the vehicle manufacturer causing this error is a different story. Now obviously this is not a common occurrence but crazy nonetheless.

 

[rugedraw]

I know @Snakebitten will find a way to put positive spin on this with his effusive optimism , but I find it kind of unacceptable. I guess we're entering a "whole new world" with OTA updates to our vehicles, but under no circumstances should they be left undriveable due to a botched update. Individuals messing with FDRS or Forscan is one thing; the vehicle manufacturer causing this error is a different story. Now obviously this is not a common occurrence but crazy nonetheless.

What I am thinking is that it was installing an update that requires the vehicle to be inhibited while it installs. If that's the case, then this is normal. A recent update allows you to access the vehicle while it is inhibited which is something you could not do before. That's why I wanted to check his OTA history and DTC.......to rule that out.

 

[Nighsight]

Pming you now.

 

[rugedraw]

Pming you now.

Did this happen today, or did you see that message on your truck 3 days ago? This is what I see on your OTA dashboard. You had an update 4.2.2 sent to you 2 days ago, and it failed with an error code I have never seen before. Screen shot is attached with your VIN removed. I do not know what code means, but it seems like your GWM did not like one of the files it downloaded and the update failed. In the red letters, you see file NU5T-14H214-ABE being reference, and that was one of the files your truck downloaded at 3:16pm. I have seen this update fail a few times recently for some weird reasons. On 5/1, your truck got OTA 4.2.1 successfully, and the next day is when OTA 4.2.2 failed.

Your truck has the cleanest DTC history I have seen on any truck I've looked up. There is not a single DTC recorded in the past 60 days. I don't have a good explanation for you as to what caused that error message or why that update failed, but I do think it was an isolated incident.

 

[Nighsight]

Tis happened

Did this happen today, or did you see that message on your truck 3 days ago? This is what I see on your OTA dashboard. You had an update 4.2.2 sent to you 2 days ago, and it failed with an error code I have never seen before. Screen shot is attached with your VIN removed. I do not know what code means, but it seems like your GWM did not like one of the files it downloaded and the update failed. In the red letters, you see file NU5T-14H214-ABE being reference, and that was one of the files your truck downloaded at 3:16pm. I have seen this update fail a few times recently for some weird reasons. On 5/1, your truck got OTA 4.2.1 successfully, and the next day is when OTA 4.2.2 failed.

Your truck has the cleanest DTC history I have seen on any truck I've looked up. There is not a single DTC recorded in the past 60 days. I don't have a good explanation for you as to what caused that error message or why that update failed, but I do think it was an isolated incident.

This happened yesterday at 2:06pm PST.

 

[rugedraw]

Very strange indeed. I don't think the dealer will be able to help, as there are no active DTC's or recorded DTC's that they will see on your truck.

 

[Nighsight]

Is there any way to trigger the update again or do I have to stop t and wait?

 

[rugedraw]

Is there any way to trigger the update again or do I have to stop t and wait?

There is no wat to create an OTA trigger for your truck. There is small sample size for these new string of 4.2.x updates, but the few people who I have seen that had 4.2.2 fail, got another trigger for it within days of the first one failing.

Either way, there is nothing new and flashy with these updates. They are to prep us for fun stuff coming in the future. You are not missing out on anything right now.

 

[Snakebitten]

I know @Snakebitten will find a way to put positive spin on this with his effusive optimism , but I find it kind of unacceptable. I guess we're entering a "whole new world" with OTA updates to our vehicles, but under no circumstances should they be left undriveable due to a botched update. Individuals messing with FDRS or Forscan is one thing; the vehicle manufacturer causing this error is a different story. Now obviously this is not a common occurrence but crazy nonetheless.

?
But was it left undriveable?
I mean, has @Nighsight been living out of the truck in the parking lot at work since Thursday?

That IS one scary looking alert on the Instrument cluster. I'll give you that. ?

But if Ruge is right and it was triggered by nothing more than a failed 4.2.2 update? Nothing to see here folks. Move along. ?

Hey, it's true that I do tend to roll with the punches. But that doesn't mean that I am impressed with the application side of Ford's OTA ambitions. I love their intent! But so far they really can and pretty much do suck at it.

Still, @Nighsight didn't even miss dinner.

 

[thebigdu]

?
But was it left undriveable?
I mean, has @Nighsight been living out of the truck in the parking lot at work since Thursday?

That IS one scary looking alert on the Instrument cluster. I'll give you that. ?

But if Ruge is right and it was triggered by nothing more than a failed 4.2.2 update? Nothing to see here folks. Move along. ?

Hey, it's true that I do tend to roll with the punches. But that doesn't mean that I am impressed with the application side of Ford's OTA ambitions. I love their intent! But so far they really can and pretty much do suck at it.

Still, @Nighsight didn't even miss dinner.

Okay, to be fair, I was probably fired-up about something totally unrelated to F150s when I posted the other day, and I shoud have taken a second to read @Nighsight's post a bit more carefully. I missed that crucial detail where he said he started it up and drove away. ?? You got me, Snake!

 

[fordtruckman2003]

The question for the OP is if this has come up again or anything changed in truck behavior. Looks like it must not have been critical if able to drive away, but who knows if that leaves it in a state unable to retry the update. Seems the Ford programming is often fail and never try again.

 

[Nighsight]

The question for the OP is if this has come up again or anything changed in truck behavior. Looks like it must not have been critical if able to drive away, but who knows if that leaves it in a state unable to retry the update. Seems the Ford programming is often fail and never try again.

You nailed it. Just took it into the dealer because it has not tried again. We will see what they find or do.

 

[Gulfstream]

Reviving this thread. Same thing happened to my wife today. She drove 5 minutes away to a grocery store and everything was fine. Came out of the store 10-15 minutes later and gets the 'System Update Fault, Vehicle Not Driveable' message as well as a 'Resume Control' screen after she started the truck. She asked if she should drive the truck home and since it seemed to running okay I told to drive it home. The resume control message stayed on the whole time until she got home. After shutting the truck off and letting it sit for about 5 minutes, the messages were not there any longer. I then checked the update status in SYNC and found a successful update message for "Ford Power-Up 4.3.6" (of course the message in SYNC did not show the date installed). But, checking the Ford Pass App for any update info, I found the last update reported in the app was Sept 25th and was for "Enhanced Stability" 24-PU0223-VI-RBS2.

Obviously not a normal occurrence, but any other insight on this issue would be greatly appreciated. A wink and a nod now aimed at @rugedraw

My VIN: 1FTFW1ED3MFB51153

Thanks to All!!

Sponsored