Power-Up 2.3.0 OTA rolling out

[iceman77]

The USB drive format should not be an issue here. I have installed updates (GWM, APIM as well as TCU) from different flash drives, using both USB2.0 as well as USB3.0. Both were quick formatted to exFAT. Doing long format is not necessary, the only thing it does it scrubs the drive and checks for bad sectors, and it takes awfully long. Also, drive label does not matter IMO. I had one named "FDRS" another was blank

Sponsored

 

[Snakebitten]

The USB drive format should not be an issue here. I have installed updates (GWM, APIM as well as TCU) from different flash drives, using both USB2.0 as well as USB3.0. Both were quick formatted to exFAT. Doing long format is not necessary, the only thing it does it scrubs the drive and checks for bad sectors, and it takes awfully long. Also, drive label does not matter IMO. I had one named "FDRS" another was blank

Agreed. Completely.

My labeling the sticks was because I had 2 identical brand new sticks, one for APIM and one for TCU. The label was just to keep it straight AND to start with either if I couldn't get the other to succeed.

 

[iceman77]

Agreed. Completely.

My labeling the sticks was because I had 2 identical brand new sticks, one for APIM and one for TCU. The label was just to keep it straight AND to start with either if I couldn't get the other to succeed.

I have also used separate flash drive for TCU and separate for APIM. Both got recognized right away, basically within a minute after "indexing" message on SYNC screen.

If for some reason your truck does not like your flash drive you would get "USB error" message on your SYNC screen in lieu of "indexing".

 

[speedracercjr]

Man this is bloody frustrating, like Snake said the difference between comparable Job 1 trucks and how they react is just ludicrous. I said it somewhere else, it's absolutely no wonder that Ford service techs either can't or don't want to deal with this crap.

 

[Snakebitten]

There IS one thing that can be different from one truck to the next regarding APIM update..... The starting point.

Even if you had 2 identical APIM modules, hardware wise, they could be running on different software, thus behaving accordingly.

I wonder if we have enough data collected to know if the trucks having difficulty kicking off the 2.3.0 USB update are running a build different than the ones that immediately recognize the USB upgrade?

I know that I was already 21146 when I started my FRDS adventure.

 

[Snakebitten]

Also..... A long shot maybe, has anyone tried the USB-C slot?

 

[TJSparky]

Yes I have tried the C slot as well

 

[Snakebitten]

Thinking outside the box.....
Wonder if there is a Forscan or FRDS routine of some kind that is a "type of reset" that is different than the power/forward-seek soft reset.

Or perhaps a Forscan restore of the APIM from the original As-built file. Anything that would shake things up.
Or IS it the APIM module that directly reads the USB interface?

 

[speedracercjr]

Well I tried literally every single USB stick in my house (7 of them) all of different sizes and makes. Nothing worked at all. I master reset every single time, and forced the APIM to reboot once the truck was running. I'll go back to leaving the 64gb stick in the USB until god knows when.

 

[JEB]

Thinking outside the box.....
Wonder if there is a Forscan or FRDS routine of some kind that is a "type of reset" that is different than the power/forward-seek soft reset.

Or perhaps a Forscan restore of the APIM from the original As-built file. Anything that would shake things up.
Or IS it the APIM module that directly reads the USB interface?

This is something to run by Jesse. I know that one small APIM update I did manually went through the CAN bus. No USB/flash drive involved. And in the event of failure, it is my understanding that techs can opt for for an alternative update via the CAN bus as a fail safe. It’s brutally slow for large updates—hours— but my understanding is that it is an option for at least some cases where software won’t install any other way. I haven’t done it myself and I don’t know if it would work for the APIM. Jesse would know how to do it.

But I think Iceman is right—for now, you gotta do something to interrupt the loop of the APIM attempting to install 1.7.1 OTA. A master reset might be the only way to do it.

 

[iceman77]

Thinking outside the box.....
Wonder if there is a Forscan or FRDS routine of some kind that is a "type of reset" that is different than the power/forward-seek soft reset.

Or perhaps a Forscan restore of the APIM from the original As-built file. Anything that would shake things up.
Or IS it the APIM module that directly reads the USB interface?

Either APIM, or the GWM. @Jesse-Infotainment might know better. FORScan can "reset" your modules. I use this feature quite often actually. Its under Service Procedures (Wrench Icon) in FORScan

 

[Jesse-Infotainment]

THe APim is not available for the canbus route to update. The files are just way too big. In same cases of a small strategy file or something then yes but for the updates like these there just would be no way for canbus and its not even an option if you select programming failed. The USB is the only option.

As far as reset.. forscan has a reset in it like iceman mentioned. The only way to reall ytruely reset the module is through a master reset. Any other way is just a reboot.

The as built data is really difficult. Once you make changes they will be reflected on fords side. SO its best to always save the original as built data for every module and store it in case you need it. Once it changes with Ford that is what will be there if its ever programmed by ford at dealer level.

The updates kicking off has been a strange thing. I have had great luck in my truck. My bench update system has been great most the time. I have had to master reset a few modules to get them to kick off. Anything I suggest has come from me actually running into it and working through it. The other thing is there seems to be no right way other than making sure the usb is formatted correctly. Possibly formatted as MBR. I hear that is suggested. I have used a 128GB 3.0 and have had success. I have also used 64 2.0

Even though the SYnc 4 has a USB c it really is not usb c, the actual USB port on the apim is still mini USB so data speeds will still be 2.0

 

[LHoffmanjr22]

Can you post a screenshot so I can compare ? Also, what version of sync are you running ?

Sorry I’m just getting this out now. I’m pretty sure I’m on 2.0.0 sync, and his is iOS 15.3. The black outline has been there since I got the truck as far as I can remember.

 

[iceman77]

Sorry I’m just getting this out now. I’m pretty sure I’m on 2.0.0 sync, and his is iOS 15.3. The black outline has been there since I got the truck as far as I can remember.

I assume Sync does not show version and your OTA buttons are disabled.

You can check SYNC version in General -> SYNC version (scroll down)

 

[mj1angier]

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....

Sponsored