Power-Up 2.3.0 OTA rolling out

[MikeYQM]

Well, I’ve started the formal complaint process and issued a demand to @Ford Motor Company Canada to have all modules updated and/or replaced by 2022-02-10, including BlueCruise.

On 2022-02-11 I go to the BBB and make my complaints public.

if that doesn’t work, by March it will be civil action.

along with the broken OTA system, BlueCruise delays, I’m also fighting the frozen door latch and spent an hour idling the truck and fighting with it only to have to ratchet strap it closed and drive to the dealer in -15C temps today. I’m well and truly fed up with getting screwed by Ford.

Sponsored

 

[speedracercjr]

SpeedracerCJR- I am in the dreaded 1.7.1 boat as well. I am still trying to get that update too.
I reset everything this morning and have the truck running as we speak. Been about an hour so far. I will let you know if anything happens but I have received no messages on the screen about "DO NOT REMOVE USB" so I'll keep you posted.

Appreciate it, she's been running for 3 hours now, no prompts that I can see. I got a full 36 gallon tank and alot of patience, we'll see which one runs out first.

 

[Snakebitten]

What's so strange is that if we purchased 10 pc's of the same make/model, and then proceeded to prepare all 10 for deployment, we would almost guaranteed have identical out-of-the-box experiences, including getting them all updated to the latest build/updates.

Yet with our trucks, I can stick the USB stick in with the truck running and it will only take seconds to recognize what is on the stick and initiate the update.

The next truck will act like nothing has happened.

Then my truck will get stuck in the "restart to finish" loop, only to instantly overcome the loop by me REMOVING the stick against instructions.

While the next truck doesn't get stuck in the restart loop.

The inconsistencies doesn't make sense in the normal ones & zeros digital realm.

But I do admit it makes for some adventure for those determined to do this themselves

 

[speedracercjr]

Ok question for the successful getting over the hump, when you formatted the USB stick did you find that a quick format or a long format with ExFAT as the type made a difference? What about the volume label, I've left it blank.

It's been running for 4 hours with nothing and I'm wondering if it's the USB stick now

 

[BHunted1]

Ok question for the successful getting over the hump, when you formatted the USB stick did you find that a quick format or a long format with ExFAT as the type made a difference? What about the volume label, I've left it blank.

It's been running for 4 hours with nothing and I'm wondering if it's the USB stick now

I tried both ways. No difference. Ya can name it whatever you want.

 

[Snakebitten]

I tried to overcome the restart-loop by formatting the stick the slow way. Made no difference.
And I tried 3 different brands of sticks all quick formatted WITH label "APIM" and they all initiated the update within seconds of inserting the stick.

Sync would show at the upper left hand corner recognition of "APIM" (label) and then "indexing APIM" (again the label), and then in just a few seconds "Updating"

Again, the inconsistencies between how our same Job1 trucks is strange.

 

[JEB]

Ok question for the successful getting over the hump, when you formatted the USB stick did you find that a quick format or a long format with ExFAT as the type made a difference? What about the volume label, I've left it blank.

It's been running for 4 hours with nothing and I'm wondering if it's the USB stick now

If you used FDRS to create the flash drive, it might be worth starting over at this point by erasing the drive, reformatting it and then performing the APIM update procedure from scratch. My first attempt to update the APIM failed the post-install validation. I started over and it went through fine the second time.

 

[TJSparky]

JEB this in reference to the 1.7.1 update that seems to be an issue. After this one your correct in following the FDRS but this one update seems to be a pain to kick off.
I've tried 3 different sticks and multiple times with FDRS for some reason this update is stubborn.

 

[JEB]

JEB this in reference to the 1.7.1 update that seems to be an issue. After this one your correct in following the FDRS but this one update seems to be a pain to kick off.
I've tried 3 different sticks and multiple times with FDRS for some reason this update is stubborn.

You are correct, of course. But a second try with FDRS might rule out some failure points. Besides, even if successful, you have to go back into FDRS anyway to validate the install. So, it’s not like you can just download a flash drive and be done with it. There’s still a post-install procedure to complete.

 

[TJSparky]

I tried to overcome the restart-loop by formatting the stick the slow way. Made no difference.
And I tried 3 different brands of sticks all quick formatted WITH label "APIM" and they all initiated the update within seconds of inserting the stick.

Sync would show at the upper left hand corner recognition of "APIM" (label) and then "indexing APIM" (again the label), and then in just a few seconds "Updating"

Again, the inconsistencies between how our same Job1 trucks is strange.

So Snake your saying you labelled it as APIM and it started the update right away? Or just the USB indexing message? I see that happen with every try inserting the USB sticks. Did you get the message pop-up stating "DO NOT REMOVE USB?"

 

[Snakebitten]

So Snake your saying you labelled it as APIM and it started the update right away? Or just the USB indexing message? I see that happen with every try inserting the USB sticks. Did you get the message pop-up stating "DO NOT REMOVE USB?"

I think that whatever word you use as a label when formatting you WILL see that label on the Sync screen twice. Once upon recognition it is there, and once for indexing. It does not show the label when indicating the update has began.

But I admit that the first time Sync said "Indexing APIM", for a second I thought huh? Lol

 

[iceman77]

Appreciate it, she's been running for 3 hours now, no prompts that I can see. I got a full 36 gallon tank and alot of patience, we'll see which one runs out first.

I don't think this is necessary. If your update does not kick in within minutes after starting the truck, chances are it wont kick in at all. The problem is, your APIM (and GWM) is stuck in the middle of installing 1.7.1 OTA (which obviously failed). You need to get those two out of this stuck loop. I have performed numerous master resets on the APIM, disconnected the battery, to shut down the TCU/GWM. Not sure if this helped, but after torturing my truck for a while by numerous APIM master resets and GWM resets I noticed that my Update Screen is not greyed out anymore. And if I recall correctly, that's when I had my USB update kick in! Within a minute of starting the truck! Hope this helps.

 

[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

 

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

Sponsored