Request VIN Lookup Thread

[Chaos150]

1FTFW1E80MKD53460

21 F150. Doesn’t want to update with what I show to be an update both on the app and on the screen itself. 4.3.4 I did put a new battery in the truck a couple months ago. And it stopped wanting to attempt the update.

Sponsored

 

[rugedraw]

1FTFW1E80MKD53460

21 F150. Doesn’t want to update with what I show to be an update both on the app and on the screen itself. 4.3.4 I did put a new battery in the truck a couple months ago. And it stopped wanting to attempt the update.

That OTA expired on 11/15. You have to wait for it to be resent to try again at this point.

 

[Chaos150]

That OTA expired on 11/15. You have to wait for it to be resent to try again at this point.

Well that sucks. How long does that usually take?

 

[rugedraw]

Well that sucks. How long does that usually take?

No idea and there is no way to know.

 

[Chaos150]

No idea and there is no way to know.

Thanks for the info! Appreciate the help!

 

[Corral06]

The good news is, your truck is past the broken software where 2021's are known to get stuck. I see you got the old IPC update needed for BC to work, but your truck was skipped over the 2.8.x updated needed to get BC activated. Your VIN does have the 21G01 campaign open for the dealer to activate your BC. Make an appt with your dealer and tell them you need campaign 21G01 done to your truck to activate BC and they should be able to get you what you're missing.

thank you! I took my truck to the dealer for the update, they said the update has been completed but that my BC still doesn’t work. Any idea what the issue could be?

 

[CaptainRage]

Are you willing to check 1FTFW1ED5PFC84307

I received 6.1, 6.2 didn't complete on Dec 9 and sirius xm hasn't worked since. I took to the dealer and they say they updated all modules, but my screen still says 6.2 is not complete and sxm worked for 1 key cycle and stopped working again.

 

[DrTone]

I keep getting phantom updates that won't install. I assume it's 6.5. Can someone check for me please.

1FTEW1E81NFC06201

 

[rugedraw]

thank you! I took my truck to the dealer for the update, they said the update has been completed but that my BC still doesn’t work. Any idea what the issue could be?

Without FDRS, I can't pin-point what updates are missing for BC to work. When they tried to run the 21G01 program to activate it, the message below kept popping up:

Procedure Aborted Vehicle modules are not at the appropriate software levels for BlueCruise. Verify that all software updates directed by the 21G01 technical bulletin are completed before returning to this application.

The did update a lot of modules, but it is difficult for me to see what is missing with the tools I have at my disposal now. I can check FDRS for you later and if I can't figure out, I would PM Jesse.

 

[rugedraw]

Are you willing to check 1FTFW1ED5PFC84307

I received 6.1, 6.2 didn't complete on Dec 9 and sirius xm hasn't worked since. I took to the dealer and they say they updated all modules, but my screen still says 6.2 is not complete and sxm worked for 1 key cycle and stopped working again.

6.2.0 shows as it went through in PTS on 11/16. The OTA that failed on 12/9 and 12/12 is APIM update 23-PU1103-NAT-VCE. It failed due to a manifest mismatch, so the problem is on Ford's side.

They updated some modules, but definitely not all of them. I do not have FDRS access now to confirm, but you are on Sync 23045 so impossible they did them all. FDRS updates and OTA's do not communicate, so even if they updated your APIM (which they did not) to give you the update that failed, your touch screen would still show the same message it is showing now.

As far as your XM radio, I think I have read a few posts where people disconnect the battery for a bit and reconnect it and it fixes the issue, but I can't say that with 100% accuracy. It will not hurt to try.

I keep getting phantom updates that won't install. I assume it's 6.5. Can someone check for me please.

1FTEW1E81NFC06201

No OTA action since 6.4.0 on 12/12. Many people have reported these phantom updates with the 6.x.x updates. Ignore them; you can't do much else about it.

 

[CaptainRage]

6.2.0 shows as it went through in PTS on 11/16. The OTA that failed on 12/9 and 12/12 is APIM update 23-PU1103-NAT-VCE. It failed due to a manifest mismatch, so the problem is on Ford's side.

They updated some modules, but definitely not all of them. I do not have FDRS access now to confirm, but you are on Sync 23045 so impossible they did them all. FDRS updates and OTA's do not communicate, so even if they updated your APIM (which they did not) to give you the update that failed, your touch screen would still show the same message it is showing now.

As far as your XM radio, I think I have read a few posts where people disconnect the battery for a bit and reconnect it and it fixes the issue, but I can't say that with 100% accuracy. It will not hurt to try.



No OTA action since 6.4.0 on 12/12. Many people have reported these phantom updates with the 6.x.x updates. Ignore them; you can't do much else about it.

Thank you for the info!

 

[JEB]

Thank you for the info!

Don't disconnect the battery if you have a Powerboost. It won't work. All you'll do is drain and possibly damage the auxiliary battery under the rear seat.

 

[cc23]

Do you mind checking my 2021?
1FTEW1CP6MFC92257

It seems up to date, but am now getting the battery message on the Sync screen, and it will not turn interior lights on and electronics until I actually hit the start button on dash. Remote start doesn’t turn anything on but the engine.

Also looking for info on an auxiliary battery that may run the electronics because truck battery was tested and came back fine.
Thanks!

 

[rugedraw]

Do you mind checking my 2021?
1FTEW1CP6MFC92257

It seems up to date, but am now getting the battery message on the Sync screen, and it will not turn interior lights on and electronics until I actually hit the start button on dash. Remote start doesn’t turn anything on but the engine.

Also looking for info on an auxiliary battery that may run the electronics because truck battery was tested and came back fine.
Thanks!

You're missing the 6.x.x updates, so you aren't terribly behind. You've gotten updates as recent as last month, so nothing to be concerned about there.

Your truck is not recorded any low battery codes. If the battery was tested with a quick tester, that does not suffice. It would need to 2-3 hour long Rotunda test to properly test its capacity.

 

[rack04]

Would appreciate someone checking to see if I have any module updates available in FDRS. I have some time today and may fire up FDRS to perform any updates. Thanks.

Sponsored