Screen messed up after OTA update

[Hog_Johnson]

I got an OTA update yesterday and now the screen is messed up. The Ford logo on startup, Android Auto and 360 cams show up fine, but everything else is dark and difficult to read. The 'Entertainment Source" screen is blank - no AM/FM, SiriusXM, etc. I tried resetting it 10+ times and disconnected the battery for about an hour, but it's still not working. Anyone else ran into this? It says update successful, but details are unavailable so I have no idea which one it was. The last one I got was 2.3.0 4 months ago.

Sponsored

 

[Jesse-Infotainment]

Did you have any forscan changes made? Someone had an issue with an update and they reverted all the changes they made and it fixed the issue.

If not send me your vin so I can take a look

 

[Hog_Johnson]

Yes, I had made a few Forscan changes. My VIN is 1FTFW1E52MFB95136

 

[Boji surfer]

I have experienced the exact same issues. I have not made any Forscan changes though.
VIN: 1FTFW1E89MFC06837

 

[speedracercjr]

Looks like he had the same thing I did @Jesse-Infotainment where an older version of the APIM got installed?

 

[Jesse-Infotainment]

Looks like he had the same thing I did @Jesse-Infotainment where an older version of the APIM got installed?

Oh yeah I remember yours too now.. Dang we had to PMI yours didnt we?

 

[speedracercjr]

Oh yeah I remember yours too now.. Dang we had to PMI yours didnt we?

no we just reloaded the most current APIM and it worked great

 

[Jesse-Infotainment]

OK.. Ill get teh files for him and send him a link

 

[Ford Motor Company]

I got an OTA update yesterday and now the screen is messed up. The Ford logo on startup, Android Auto and 360 cams show up fine, but everything else is dark and difficult to read. The 'Entertainment Source" screen is blank - no AM/FM, SiriusXM, etc. I tried resetting it 10+ times and disconnected the battery for about an hour, but it's still not working. Anyone else ran into this? It says update successful, but details are unavailable so I have no idea which one it was. The last one I got was 2.3.0 4 months ago.

Hello! Send us a private message with your VIN and the name and location of your local Ford dealer. I’d be happy to see what I can do to assist with this screen concern. Thanks!

 

[speedracercjr]

Hello! Send us a private message with your VIN and the name and location of your local Ford dealer. I’d be happy to see what I can do to assist with this screen concern. Thanks!

@Ford Motor Company you need to get your OTA team looking at this. They are sending out old OTA's to trucks that are current and it's causing issues. I had my second OTA attempted to be pushed to me. Luckily I turned off auto-updates as I got messed up the first time around.

 

[Ford Motor Company]

I have experienced the exact same issues. I have not made any Forscan changes though.
VIN: 1FTFW1E89MFC06837

Hi there. Can you send us a DM with your VIN and dealership info? I can look into this for you.

 

[Jesse-Infotainment]

Anyone having the Issue I can provide updates that will correct it. message me your vin

 

[Hog_Johnson]

Just to wrap this up, I got the correct software from Jesse and had everything working again in under an hour. Much easier than going back and forth to the dealer and letting them throw APIMs in it.

 

[speedracercjr]

Just to wrap this up, I got the correct software from Jesse and had everything working again in under an hour. Much easier than going back and forth to the dealer and letting them throw APIMs in it.

100% easier. A dealership may not have even been able to figure this out depending on their level of knowledge with this, which seems to be generally low around the country.

 

[Snakebitten]

100% easier. A dealership may not have even been able to figure this out depending on their level of knowledge with this, which seems to be generally low around the country.

You are being kind with "may not"

My opinion is that it would be highly unlikely that the dealership could do what Jesse is providing because they would only have the "go by the book" method of FDRS. I could be wrong but FDRS would NOT correctly be offering the necessary update for the truck?

I guess it's possible that a scan would trigger FDRS to offer an APIM update that resolves the issue, but if the AsBuilt records were keeping the versioning in proper order, as expected, the OTA update that's causing this issue wouldn't have be getting delivered in the first place.

Sponsored