Request VIN Lookup Thread

[yaojunliu]

Help me look at mine Thank you！1FTFW1E81MFC08243

Sponsored

 

[Fordphanatic]

After 2 days at the dealership and multiple updates I’m still on the same outdated system so where do I go from here

After 2 days at the dealership and multiple updates I’m still on the same outdated system so where do I go from here

https://www.f150gen14.com/forum/threads/ecu-module-programming-guide-using-fdrs.8249/

I would start here. When the dealor fails you this is your only hope. It's not cheap but you CAN do it.

 

[Kanuck]

Morning people...
@rugedraw hinted there were some updates on his 21.... could someone see if I have them as well.

1FTFX1E81MKE01710

Thanks
Don

 

[rugedraw]

Help me look at mine Thank you！1FTFW1E81MFC08243

No OTA history in the past 60 days and no OTAs in queue right now.

Morning people...
@rugedraw hinted there were some updates on his 21.... could someone see if I have them as well.

1FTFX1E81MKE01710

Thanks
Don

No OTA's since you got 3.5.3 on 1/25.

 

[Kanuck]

No OTA's since you got 3.5.3 on 1/25.

Thanks

 

[nicholsbradley]

Has anyone that manually installed noticed any difference with the latest PCM update?

 

[Demps]

@Demps You show to have an apim OTA Downloading now

[/QUOTE
Hopefully Ford is still sending files. Vin 1FTFW1ED1MFB59560

I'm trying to remember that "A watched pot never boils." Tempted, but haven't tried sorcery, yet.

 

[Grafx36510]

@rugedraw can you check my VIN, I used the website method, but it looks like 3.5.4 may have failed. Thanks. 1FTEW1E85NFC22840

 

[rugedraw]

@rugedraw can you check my VIN, I used the website method, but it looks like 3.5.4 may have failed. Thanks. 1FTEW1E85NFC22840

It failed twice. Reason for failure both time is:

"errorCode":"FailedToVerifyFileHash(326)""errorCategory":"ERROR_CATEGORY_AGENT(2)""ecuId":"1876""fpn":"MU5T-14H090-AJK"

I have no idea what that means. Seems like your GWM didn't agree with one of the files in the update.

 

[Cheez_Greater]

It's been a few months since I did an FDRS update, could somebody please check 1FTFW1E81MKE11947 in FDRS? Thank you.

 

[pavementends]

It failed twice. Reason for failure both time is:

"errorCode":"FailedToVerifyFileHash(326)""errorCategory":"ERROR_CATEGORY_AGENT(2)""ecuId":"1876""fpn":"MU5T-14H090-AJK"

I have no idea what that means. Seems like your GWM didn't agree with one of the files in the update.

Looks like (in hidden OTA info) my 3.5.3 failed yesterday, exactly 2 weeks after it was sent. Did mine show the same reasons? 1FTFX1E8XMKE93061

 

[Grafx36510]

It failed twice. Reason for failure both time is:

"errorCode":"FailedToVerifyFileHash(326)""errorCategory":"ERROR_CATEGORY_AGENT(2)""ecuId":"1876""fpn":"MU5T-14H090-AJK"

I have no idea what that means. Seems like your GWM didn't agree with one of the files in the update.

Thank you very much!

 

[Texas2022XLT]

I'll have to check tomorrow. I can't see FDRS history from the app.



Lmfaooooo! Did they really say that?!?!?

Your update is trying to download the files like everyone else's. I don't know why it's not downloading, but I can tell with with 100% that's not the reason, and it's a damn shame that was the excuse they gave you.

Any update on the FDRS? Dealer is wanting to replace my APIM for the compass not working correctly but I don't feel that is the issue. I think its with the TCU from the TSB...however my dates don't match the build time they have listed in the TSB. Ford Motor Company (nhtsa.gov)

 

[rugedraw]

Any update on the FDRS? Dealer is wanting to replace my APIM for the compass not working correctly but I don't feel that is the issue. I think its with the TCU from the TSB...however my dates don't match the build time they have listed in the TSB. Ford Motor Company (nhtsa.gov)

I don't have FDRS. What did you want checked?

 

[Texas2022XLT]

I don't have FDRS. What did you want checked?

If there was a TCU update.

Sponsored