TSB 22-2150 Errors - Any help?

[redditn00b92]

I’ve performed a bunch of updates for my June 2021 CR1 Build. I can’t get the APIM Update to work however. I tried running TSB 22-2150 as it applies to my car. When I ran the module repair, I got an error saying it failed to download the diagnostic files from the server and that it could mean my VIN is locked out. However, looking at my vehicle history there’s no reason for it to be locked out. In fact, in FDRS it says that the module repair was successful on July 14. I thought I wouldn’t need to run the repair again and could just install the APIM update. My issue was that once I plugged the USB drive into the vehicle, SYNC never popped up with anything.

Can anyone offer any support? My SYNC system seems off. I don’t have notes, full screen car play etc. yet, the APIM update is all I am lacking at this point

Sponsored

 

[Mach-Lee]

And what is the current build that shows up on the screen? Part number you flashed?

 

[redditn00b92]

And what is the current build that shows up on the screen? Part number you flashed?

hmm…can I tell this info on the Vehicle
information screen?

 

[Mike G]

And what is the current build that shows up on the screen? Part number you flashed?

Currently showing Engineering part number: DSMU5T-14G670-CA Software part number: MU5T-14G676-CA

He only had a two day license. I just ran his VIN again.

He does show an APIM update available this morning with a tooltip version of "16.0" but that means nothing to me.

Do you think he should have another go since there is an APIM update showing that he can put on the USB stick? I know on the F-150 forum some guys have gotten unstuck by using FDRS to put the files on the USB stick and then just leaving the stick in the USB port until eventually the system updates the APIM. It does take a while for this to happen (think days running into weeks) but it does eventually work in all cases.

 

[Mike G]

hmm…can I tell this info on the Vehicle
information screen?

Do you have version information showing on your About Sync screen?

 

[WyldStallyn]

hmm…can I tell this info on the Vehicle
information screen?

I checked the other thread since there wasn't information about the APIM update failure in this thread.

Let's troubleshoot the USB update first ...

1. What size USB drive are you using? Have you tries both USB-A and USB-C?
2. Have you formatted the drive in ExFAT format?
3. Is there any USB compatibility error on the SYNC screen?

 

[redditn00b92]

I checked the other thread since there wasn't information about the APIM update failure in this thread.

Let's troubleshoot the USB update first ...

1. What size USB drive are you using? Have you tries both USB-A and USB-C?
2. Have you formatted the drive in ExFAT format?
3. Is there any USB compatibility error on the SYNC screen?

1. I am using a 64 GB drive. The download from FDRS is taking up about 3GB I believe. I’ve only tried USB-A but I have a USBA to USB-C adapter. Should I try using that?

2. I have formatted the drive toExFAT, yes.

3. No compatibility error. In fact, nothing comes up on the screen at all.

My 2 day license expired but I still have the APIM download on my USB drive. If I try using usb c, will it still recognize the update without being connected to FDRS? If it does, do I need a 12V supply or can will it be okay since the engine stays on?

 

[Mike G]

1. I am using a 64 GB drive. The download from FDRS is taking up about 3GB I believe. I’ve only tried USB-A but I have a USBA to USB-C adapter. Should I try using that?

2. I have formatted the drive toExFAT, yes.

3. No compatibility error. In fact, nothing comes up on the screen at all.

My 2 day license expired but I still have the APIM download on my USB drive. If I try using usb c, will it still recognize the update without being connected to FDRS? If it does, do I need a 12V supply or can will it be okay since the engine stays on?

If you have the files and it shows your .cer (certificate) in the root of the drive that's all you need to do this without FDRS. If it updates (it will let you know if successful) then the only thing you'd be missing in the process is the network scan that notifies the server that the APIM was successfully updated.

So if I recall you did successfully use that same thumb drive to update something else correct?

If that's the case I'd just go out and put the drive in the USB port with the car running and wait about 5 minutes to see if you get the message that it's updating. In fact you can just leave it in there until it's eventually recognized. Or you can download the other version I sent you the link to and put that on a freshly formatted drive and try it that way.

 

[Breinholm]

My Mach-E AWD is, unfortunately, suffering from the "inability to update" failure (TSB 22-2150).
My danish workshop tried to fix the problem on 19 Aug but did stop after 4 tries.
Today after more than 30 days he tried again. He updated all modules but ended up with an exception at the APIM module update repair.
When trying to download the diagnostic files he gets this message:
"Exception trying to obtain diagnostic files from the backend server required to repair this vehicle. This could indicate the VINhas been locked out!"

What is the fix to this problem?

My VIN is: WF0TK3SU5MMA16072
Sync version shows: --

Hope one of you can help us.
Thanks / Peter

 

[Mach-Lee]

My Mach-E AWD is, unfortunately, suffering from the "inability to update" failure (TSB 22-2150).
My danish workshop tried to fix the problem on 19 Aug but did stop after 4 tries.
Today after more than 30 days he tried again. He updated all modules but ended up with an exception at the APIM module update repair.
When trying to download the diagnostic files he gets this message:
"Exception trying to obtain diagnostic files from the backend server required to repair this vehicle. This could indicate the VINhas been locked out!"

What is the fix to this problem?

My VIN is: WF0TK3SU5MMA16072
Sync version shows: --

Hope one of you can help us.
Thanks / Peter

If I'm reading the TSB correctly, because it's been more than 20 days since Module Update Repair has started without a successful completion, I think your APIM is locked and will need to be replaced. It looks like it failed multiple times in August because they didn't have the adapters hooked up properly.

 

[Breinholm]

Thanks for your reply Mach-Lee,

The TBS 22-2150 has two mentionings of the timeout:
On page 12: "The application may only be run a maximum of 15 times within a 20 day timeframe for each VIN."

and on page 29:
"Due to Ford Cyber Security requirements, the maximum number of attempts has been reached to run this application. Up to 15 attempts or within 20 days, which ever comes first."

I interpret the first sentence like this: Within 20 days we have a maximum of 15 tries (They didn't do that - only 4 tries within two days).

The second sentence I interpret as: We have a maximum of 15 tries and a maximum of 20 days to finish the update - They exceeded the 20 days limit here (They clearly adapted to the first sentence and aimed at a reset of their tries after 20 days.)

I don't think it's smart that ford has so ambiguous sentences in the same TBS!

/Peter

 

[redditn00b92]

I am glad I’m not the only one who thought the language was ambiguous. I’ve been thinking about trying again, but if the second sentence is what’s actually in effect, it will be useless it sounds.

The only alternative to all of this that I’m aware of is another one I’m trying thanks to Mike G’s direction (from the forums here). I got the APIM software update to download on a USB and now I’m just leaving it in until It finally recognizes it. It’s been a while but I’ve heard this always works eventually.

 

[Mach-Lee]

The only alternative to all of this that I’m aware of is another one I’m trying thanks to Mike G’s direction (from the forums here). I got the APIM software update to download on a USB and now I’m just leaving it in until It finally recognizes it. It’s been a while but I’ve heard this always works eventually.

Yeah let us know how that goes either way. I have my doubts if that can overcome a stuck or locked APIM but worth a shot.

 

[Mike G]

Yeah let us know how that goes either way. I have my doubts if that can overcome a stuck or locked APIM but worth a shot.

It's been working for several folks on the F-150 forum. Although it has taken like almost a month in some cases, it always eventually works.

Mike

 

[Breinholm]

I am glad I’m not the only one who thought the language was ambiguous. I’ve been thinking about trying again, but if the second sentence is what’s actually in effect, it will be useless it sounds.

The only alternative to all of this that I’m aware of is another one I’m trying thanks to Mike G’s direction (from the forums here). I got the APIM software update to download on a USB and now I’m just leaving it in until It finally recognizes it. It’s been a while but I’ve heard this always works eventually.

Have you had any success?
I've been driving around with the USB stick inserted for 3 weeks now - no luck yet!
/Peter

Sponsored