Power-Up 2.3.0 OTA rolling out

[Jesse-Infotainment]

I hate even to suggest this, because it’s a long shot. But about two days after I updated my APIM, a second APIM update came down. Very small and went through the CAN bus. I don’t know what it fixed, but maybe it will be enough of a tweak to correct the display errors. Keep an eye out for it. Also, are there any other out of date modules? Might as well update them to rule out any interaction issues. I’m not optimistic about either of these alternatives, unfortunately.

Jesse: Are there any other sources for pre-update as-built files for the APIM? Just wondering if it were possible to reload the as-built configuration using the FDRS tool for programming newly installed replacement modules.

His situation looks bad. I realy think they sent the wrong file out for his truck. It loaded them and screwed it up. That is 100% the 8inch look. The 12” even if the as built was wrong would still have the side bar. The 8” and 12” are identical and load based on what the manifest calls for. And it called for the wrong setup. His only hope at this point would be another update.
I am more than willing if he sends it to me to try and rectify it.
I have not seen the update that you got on my truck if heard from anyone else that had it. I really am not certain what it was.

this issue would happen with guys on3.4 they have a sync 3 and a sync 3 lite. Guys would download a update from online and load the update and all the sudden their sync unit would display in 4” size. That’s because they loaded the 4” update which were the same different resolution.
I think his is toast. If he sends it to me I can try to downgrade and then go back up.
Outside a future update he will be stuck like that. He is limited in what he can do. I have way more capacity in my office because I have so many tools.
I am sorry it isn’t his fault it is fords servers. They detected something wrong. This is a fluke. He just got the wrong update and there is NOTHING HE DID OR COULD HAVE DONE to cause it

Sponsored

 

[JEB]

His situation looks bad. I realy think they sent the wrong file out for his truck. It loaded them and screwed it up. That is 100% the 8inch look. The 12” even if the as built was wrong would still have the side bar. The 8” and 12” are identical and load based on what the manifest calls for. And it called for the wrong setup. His only hope at this point would be another update.
I am more than willing if he sends it to me to try and rectify it.
I have not seen the update that you got on my truck if heard from anyone else that had it. I really am not certain what it was.

this issue would happen with guys on3.4 they have a sync 3 and a sync 3 lite. Guys would download a update from online and load the update and all the sudden their sync unit would display in 4” size. That’s because they loaded the 4” update which were the same different resolution.
I think his is toast. If he sends it to me I can try to downgrade and then go back up.
Outside a future update he will be stuck like that. He is limited in what he can do. I have way more capacity in my office because I have so many tools.
I am sorry it isn’t his fault it is fords servers. They detected something wrong. This is a fluke. He just got the wrong update and there is NOTHING HE DID OR COULD HAVE DONE to cause it

Yeah, that’s what it sounded like to me too. I got a very queasy feeling when I read this. Ford sending the wrong update could happen to anyone. That’s why I was hoping maybe an earlier build before this last update could fix the problem because he said he was fine through 2.1.1.

 

[saluki1969]

Anyone getting a white splash screen when you open the driver door after 2.3.0 OTA update ?

Yes

 

[Hauk]

His situation looks bad. I realy think they sent the wrong file out for his truck. It loaded them and screwed it up. That is 100% the 8inch look. The 12” even if the as built was wrong would still have the side bar. The 8” and 12” are identical and load based on what the manifest calls for. And it called for the wrong setup. His only hope at this point would be another update.
I am more than willing if he sends it to me to try and rectify it.
I have not seen the update that you got on my truck if heard from anyone else that had it. I really am not certain what it was.

this issue would happen with guys on3.4 they have a sync 3 and a sync 3 lite. Guys would download a update from online and load the update and all the sudden their sync unit would display in 4” size. That’s because they loaded the 4” update which were the same different resolution.
I think his is toast. If he sends it to me I can try to downgrade and then go back up.
Outside a future update he will be stuck like that. He is limited in what he can do. I have way more capacity in my office because I have so many tools.
I am sorry it isn’t his fault it is fords servers. They detected something wrong. This is a fluke. He just got the wrong update and there is NOTHING HE DID OR COULD HAVE DONE to cause it

His situation looks bad. I realy think they sent the wrong file out for his truck. It loaded them and screwed it up. That is 100% the 8inch look. The 12” even if the as built was wrong would still have the side bar. The 8” and 12” are identical and load based on what the manifest calls for. And it called for the wrong setup. His only hope at this point would be another update.
I am more than willing if he sends it to me to try and rectify it.
I have not seen the update that you got on my truck if heard from anyone else that had it. I really am not certain what it was.

this issue would happen with guys on3.4 they have a sync 3 and a sync 3 lite. Guys would download a update from online and load the update and all the sudden their sync unit would display in 4” size. That’s because they loaded the 4” update which were the same different resolution.
I think his is toast. If he sends it to me I can try to downgrade and then go back up.
Outside a future update he will be stuck like that. He is limited in what he can do. I have way more capacity in my office because I have so many tools.
I am sorry it isn’t his fault it is fords servers. They detected something wrong. This is a fluke. He just got the wrong update and there is NOTHING HE DID OR COULD HAVE DONE to cause it

So here is my as built information I pulled from Forscan, if it is of any value. One thing to note is that the bottom bar stretches across the entire bottom of the screen, and doesn't cut off where the right side menu bar should be. It's almost like it is posting images from the 8 and 12 inch versions in different spots.

Jesse, if I did send you my apim module, do you think it would be possible to get it reversed? Would I still be able to drive the truck with it removed? Thanks again for your help!

 

[Jesse-Infotainment]

Your as built is correct. It was a long shot.

I cant make a promise that I can, wish I could but I will do all I can. Yes you can drive the truck. you just wouldnt have audio and access to menus.

 

[Snakebitten]

I wish there was some kind of edit, ANY kind available with FRDS or Forscan, that could trigger an FRDS module scan to recognize something being "off" on a module and cause FRDS to render the latest update as available.

Or put another way, too bad the update library becomes unavailable in FRDS regardless of whether you have applied one or not.

As an analogy, Windows update works similar to FRDS and scans and then makes updates available. And similar to FRDS, after an update has been applied it will no longer populate the update screen as available. BUT, all those updates really are available individually and you can fetch them and attempt to apply them again. (Although they might report that the system already has the update)

Again, just thinking out of the box. We need Forscan to THINK his APIM is not running the latest version.

 

[Jesse-Infotainment]

I have a pathway in my head to correct it but I need it here. There is really no way to edit the manifest. THe update changed the reslution the only way to fix it is rerun the update and I dont know of a way to edit the manifest and it maintain its signature. There may be some people on this forum that are smarter than I am(I am certain of it) that can take care of the json stuff and edit it and maintain the signature or hash. If that were possible then we could then take the version checker out. He could then run the update but the update he has is wrong so he would need one that is right.

I can run it here in my system and have much more flexibility within what is allowed in the existing files.

THere is no way with forscan to make the version change in the apim.


This is another shot in the dark. @Hauk but try to run a PMI on the APIM in FDRS. IT MAY allow you to redownload the files it MAY see a weird version in its check and download a new update. It may also boot you since its already the existing APIM. Its something to try while you have FDRS

 

[superfordman]

My Job1 early MY20 updated to 2.3.0 this last night much to my surprise and like the improvements and changes I've seen so far. I like the layout of the Audio tab much better and the info it gives you, and they finally fixed the bug where my bluetooth phone info didn't show up all the time at the top left! They also changed something with how the at speed camera menu works as that is different now than it was before, but need to play around with it more. Still no normal reverse camera view at speed though for me, still only the hitch camera shows at speed. The volume pop up screen font is also different from what I can tell

To others having issues, when I turned my automatic updates off for a day then back on a few weeks ago, that seemed to have woke everything back up and reinvigorated it, as I've been getting OTA updates just fine ever since and quite frequently.

 

[MikeYQM]

I know there is a way to add additional cards to the sync with ForScan, cards like bed camera and trip info. Perhaps if additional cards can be added, the default cards can be removed if the as built is corrupted somehow.

I don’t have the link off hand, but I would try to add the additional cards to see if that produces anything.

 

[uavmx]

So I got the 2.3.0 update yesterday- as I was driving 65 mph down the road! Cluster and info screen both went black for 15 sec or so. Freaked me out to start, but realized that truck was still running and responding. Cluster came back up first, then info screen. Then phone alerts me with "update successful'. Thanks Ford, but lets not do that when driving, lol.

Also after I restarted it to leave from work I get a gray alert box in cluster "Brake applied. Power reduced" for about 2 sec. From what I can find it means break and gas peddles were both pushed at same time, sometimes caused by floor mat getting on top of gas peddle. I will check this morning but mat has not be moved in 2 weeks....

I would report the install while driving to @FordMotorCompany. That's dangerous

 

[Hauk]

I have a pathway in my head to correct it but I need it here. There is really no way to edit the manifest. THe update changed the reslution the only way to fix it is rerun the update and I dont know of a way to edit the manifest and it maintain its signature. There may be some people on this forum that are smarter than I am(I am certain of it) that can take care of the json stuff and edit it and maintain the signature or hash. If that were possible then we could then take the version checker out. He could then run the update but the update he has is wrong so he would need one that is right.

I can run it here in my system and have much more flexibility within what is allowed in the existing files.

THere is no way with forscan to make the version change in the apim.


This is another shot in the dark. @Hauk but try to run a PMI on the APIM in FDRS. IT MAY allow you to redownload the files it MAY see a weird version in its check and download a new update. It may also boot you since its already the existing APIM. Its something to try while you have FDRS

You were right, the PMI procedure did not allow me to finish and kicked me out with the below message.

One other thing I wanted to verify was the screen size setting on the testing menu page. The text is jumbled but I can read out 1900x1200 resolution. Is this correct for the 12 inch screen?

 

[Jesse-Infotainment]

Yeah.. that is wrong the resolution thats the 8"

Try the PMI again. Make sure you have a good internet connection.. Fortunately that wasnt a complete fail it tried. So try again.. and again until you get passed that message. You may get somewhere. That message is a failure to download not a failure of a condition it detects in the truck such as part or software.

 

[Hauk]

Yeah.. that is wrong the resolution thats the 8"

Try the PMI again. Make sure you have a good internet connection.. Fortunately that wasnt a complete fail it tried. So try again.. and again until you get passed that message. You may get somewhere. That message is a failure to download not a failure of a condition it detects in the truck such as part or software.

Ok I will try again. Also when prompted should I tell the system that the original module is currently installed or that the replacement is already installed?

 

[Hauk]

Yeah.. that is wrong the resolution thats the 8"

Try the PMI again. Make sure you have a good internet connection.. Fortunately that wasnt a complete fail it tried. So try again.. and again until you get passed that message. You may get somewhere. That message is a failure to download not a failure of a condition it detects in the truck such as part or software.

Also what is the correct resolution for the 12 inch screen? Would it be worth trying to update the resolution on those text boxes on the screen size screen or is that not going to do anything?

 

[Jesse-Infotainment]

Ok I will try again. Also when prompted should I tell the system that the original module is currently installed or that the replacement is already installed?

Say a replacement

Sponsored