[OTA] 1.7.1 Appears to be incoming

[Mirak]

Thats great! It means your VIN has been approved for the update.

So this is normal?

Sponsored

 

[generaltso]

So this is normal?

I wouldn’t know because my VIN hasn’t been authorized yet. But you’ve made progress.

 

[JamieGeek]

Rumor has it that this update is a lot of files and if the car can't FTP* them all down you get this error...

?‍

* I hopefully doubt the car uses FTP!

 

[louibluey]

I did the update this afternoon with Mongoose/FDRS 29.5.4/100A Flash power supply. The highest current from the power supply (to maintain 13.4V) was 36A today. The 12V power supply was left connected from start to finish, both TSB 21-2245, and TSB 21-2310.

Used a SAMSUNG 64 GB "FIT Plus" USB 3.2 Flash Drive. The drive comes formatted in exFAT, no preparation necessary.

GWM was already current, so I proceeded to APIM as per TSB 21-2310 (both TSBs posted by Sam earlier). It took about 20 minutes to write all the files to the USB drive. With heavy rain, I worked in the garage, not the usual good line of sight to my fast WIFI router and fast Internet, no idea if that made things slower or not.

The steps worked fine until it was supposed to say okay to remove USB. When I restarted the car in one of the later TSB steps, I just got: update on USB already installed. TSB 21-2310 took me about an hour all together. No glitches, all steps (except okay to remove USB) went okay in succession.

I gave up after 20+ minutes and moved on, leaving the USB drive plugged into the MME. During the later TSB 21-2245 restarts, I thought I saw a blue box go by, that might have been all that was left of the okay remove USB now. I removed the USB after those updates, and nothing complained. I forgot to jot down times, I think TSB 21-2245 was about 30 minutes or less. Updating SOBDM just automatically causes the rest of the modules on the TSB list to update, no need to manually select them one at a time as the TSB infers.

All DTCs cleared, all modules green at the end.

 

[Kamuelaflyer]

Thats great! It means your VIN has been approved for the update.

The update didn't update, for any variety of reasons. It'll go again at some point a

Rumor has it that this update is a lot of files and if the car can't FTP* them all down you get this error...

?‍

* I hopefully doubt the car uses FTP!

There can be any variety of issues causing it to fail. Winds are too strong for the smoke signals. Passenger pigeons went extinct, they had to send to the U.K. for carrier pigeons in a hurry. Or technical stuff.

 

[PeeKay]

After updating all other modules via FDRS, Im stuck with the APIM. While others have stated that the APIM download is about 9GB, I only seem to be downloading 3.3GB, multiple times with different devices.
And each of those devices comes up with the dreaded "USB Error" after about 10minutes into the process.

I do have the VIN numbered file name, so not sure if my download is incomplete in some way.

 

[louibluey]

After updating all other modules via FDRS, Im stuck with the APIM. While others have stated that the APIM download is about 9GB, I only seem to be downloading 3.3GB, multiple times with different devices.
And each of those devices comes up with the dreaded "USB Error" after about 10minutes into the process.

I do have the VIN numbered file name, so not sure if my download is incomplete in some way.

FDRS reported 3GB when I downloaded the update. I think an earlier poster reported success with a 16MB flash drive.

Not sure why TSB 21-2310 requires 32GB for the GWM update (if needed), and then requires 64GB for the APIM update. Also, double check exFAT formatting. I was able to use this SAMSUNG 64GB flash drive out of the package, no prep, no formatting needed. It took 20 minutes to load the (relatively fast USB 3.1) 64GB drive with an i7 Thinkpad (I was working in a different place than usual and the link to the WIFI router through the home may have contributed some to the slowness). I guess if FDRS is downloading as it goes, the Ford server plays a role in time to finish as well.

On the USB unplug from MME too soon @ProximusAl has cautioned about removing the USB drive too soon. This note is interesting (the SSM was posted earlier elsewhere): SSM 50140 - 2021 Mustang Mach-E/F-150/Edge - Gateway Module - (GWM)/Telematic Control Unit (TCU) Programming Failure - Some 2021 Mustang Mach-E, F-150, and Edge vehicles may experience a GWM and/or TCU - programming failure with an error message displayed in the Ford Diagnosis and Repair System (FDRS) stating The Programming Or Part Number Validation Process Has Failed. This may be due to the USB flash drive being removed from the vehicle media hub before fully completing reprogramming.

 

[i8iridium]

After updating all other modules via FDRS, Im stuck with the APIM. While others have stated that the APIM download is about 9GB, I only seem to be downloading 3.3GB, multiple times with different devices.
And each of those devices comes up with the dreaded "USB Error" after about 10minutes into the process.

I do have the VIN numbered file name, so not sure if my download is incomplete in some way.

Ensure the USB drive is properly set up. Google how to use diskpart to clean a drive. Sometimes it’ll have some wonky partitions on it that’ll cause issue when trying to update the APIM.

 

[PeeKay]

@louibluey , thanks for confirming that the APIM download is close to 3GB. I've used a 8Gb, 16Gb and a 32Gb stick. Looked at file sizes to confirm that they are all the same. Perhaps I should check the md5 just to be sure.

Also used a Sandisk media hub that shows an exFat device via USB. All end up with the USB Error.

Not sure what other things to try...

 

[BMT1071]

@louibluey , thanks for confirming that the APIM download is close to 3GB. I've used a 8Gb, 16Gb and a 32Gb stick. Looked at file sizes to confirm that they are all the same. Perhaps I should check the md5 just to be sure.

Also used a Sandisk media hub that shows an exFat device via USB. All end up with the USB Error.

Not sure what other things to try...

Another user ended up using an external hard drive. @mpshizzle IIRC.

 

[louibluey]

@louibluey , thanks for confirming that the APIM download is close to 3GB. I've used a 8Gb, 16Gb and a 32Gb stick. Looked at file sizes to confirm that they are all the same. Perhaps I should check the md5 just to be sure.

Also used a Sandisk media hub that shows an exFat device via USB. All end up with the USB Error.

Not sure what other things to try...

Here are some screen shots showing samples of my Sync update:
PROPERTIES SAMSUNG out of package (weird (?) that the TSB "requires" 64GB or greater for the APIM update)

PROPERTIES AFTER download & FDRS download directories

UPDATE FILES (probably unique to my VIN) (I probably cannot share the files, but they might only work for my VIN anyway)

 

[mpshizzle]

Another user ended up using an external hard drive. @mpshizzle IIRC.

Not me ?? I used a basic 16GB SanDisk flash drive

 

[BMT1071]

Not me ?? I used a basic 16GB SanDisk flash drive

@ProximusAl maybe? ?

 

[louibluey]

@ProximusAl maybe? ?

yes, I think he reported using a 500GB SSD drive that worked.

 

[ProximusAl]

yes, I think he reported using a 500GB SSD drive that worked.

I did use a 500Gb SSD external drive that worked fine…..however…to fix the USB error, I had to completely clear the FDRS cached files so it redownloaded them again. I can only assume one file got corrupt during download as the same drive worked second time around after this.

Sponsored