Request VIN Lookup Thread

[Ffdlt371]

3.5.2 was sent to you on 1/11, but it failed due to a software mismatch error. Nothing you did wrong; you just gotta wait for them to send it again/

Thank you

Sponsored

 

[rugedraw]

Could I get my checked please,
1FTFW1E8XMKD19798

You were sent a bluecruise map update that failed to install on 12/7 due to software mismatches. I can only see 60 days back, so not sure if you got all the older updates 2021 owners are supposed to get. No OTA in your queue at this time.

 

[ksimon123451]

You were sent a bluecruise map update that failed to install on 12/7 due to software mismatches. I can only see 60 days back, so not sure if you got all the older updates 2021 owners are supposed to get. No OTA in your queue at this time.

Thank you,
I updated to 539 2228_product at the end of November.

 

[trojandawg3]

Could you check mine please? I've been getting deep sleep messages and wondering if that's because of or affecting an update. Thanks in advance!

@rugedraw

1FTFW1E86NFA03311

 

[Mike G]

Thank you. What you showed above will not update over the air, correct?

Well the APIM can be updated OTA and usually is. The rest except for the WACM can get updated by OTA but probably won't, and the WACM is 'hands-on' only.

 

[Mike G]

Could I get my checked please,
1FTFW1E8XMKD19798

You have just an APIM (Sync) update in your FDRS list.

 

[fluffernutter]

If someone could check mine, it would be greatly appreciated:
1FTFW1ED4NFB05462

 

[rugedraw]

Could you check mine please? I've been getting deep sleep messages and wondering if that's because of or affecting an update. Thanks in advance!

@rugedraw

1FTFW1E86NFA03311

You're the 5th or 6th truck I check today that shows 3.5.2 was sent to them on 10/27 and it failed due to a server/cloud issue. Looks like Ford bit off more than than can chew when they tried to mass release that update on that particular day. Nothing in your history since then.

 

[rugedraw]

If someone could check mine, it would be greatly appreciated:
1FTFW1ED4NFB05462

No OTAs in the past 60 days and none in your queue now.

 

[Mike G]

70646[/ATTACH]t: 307341, member: 10439"]
If someone could check mine, it would be greatly appreciated:
1FTFW1ED4NFB05462

From FDRS just now:

 

[trojandawg3]

You're the 5th or 6th truck I check today that shows 3.5.2 was sent to them on 10/27 and it failed due to a server/cloud issue. Looks like Ford bit off more than than can chew when they tried to mass release that update on that particular day. Nothing in your history since then.

But I show that as my latest update that did take. Are you saying it did not take? Thanks for the information!

 

[Spacewhite2021]

Would someone be willing to check my VIN for me? I appreciate the help.
1FTFW1E82MKD96732

 

[rugedraw]

But I show that as my latest update that did take. Are you saying it did not take? Thanks for the information!

According to PTS, the OTA trigger expired. If your truck says you have 3.5.2, then you should have it. But your PTS OTA history shows otherwise. I wonder if this is the same for all the people that show this update failed on 10/27?

 

[rugedraw]

Would someone be willing to check my VIN for me? I appreciate the help.
1FTFW1E82MKD96732

No OTA's in the past 60 days and none in queue. Job 1 truck with a blank sync version. Your truck may be stuck in OTA limbo. Post a pic of what your update menu looks like on your truck.

Disregard: Your truck is not a job 1 truck. The blank Sync version could be due a failed APIM OTA that no longer appears on your history.

 

[trojandawg3]

According to PTS, the OTA trigger expired. If your truck says you have 3.5.2, then you should have it. But your PTS OTA history shows otherwise. I wonder if this is the same for all the people that show this update failed on 10/27?

I'll double check what my truck says after work today. Thanks again!

Sponsored