You can, but not supposed to. You have to change the file name instead to match the autoinstall. You could copy/paste file names from autoinstall file

 

I'll say this again, have you tried to update this via the OTA process when you are on WI-FI? If you have not, try it and see if it works. You might even get the 2.20 maps downloading as well.

There is a step that is being missed somewhere for doing this over USB.

 

In the one screenshot that you are showing the autoinstall.lst, the top of the window looks like you have that in a folder called "5U5T-14G381-ET

What are you copying to your USB?? Don't copy that folder over to the USB. You need the autoinstall.lst to be in the root of the USB.

In "Windows" terms... if my USB drive is E:\

You would have:
E:\autoinstall.lst
E:\DONTINDX.MSA
E:\SyncMyRide\4U5T-14G423-CC.tar.gz
E:\SyncMyRide\5U5T-14G381-ET.tar.gz
so on and so forth

You don't want to have the 5U5T-14G381-ET folder on the USB drive.

 

Yes, mine did the update over WiFi. I wouldn't even try over USB unless the Wifi update absolutely can not be done.

 

When I’m connected to WiFi and check for updates, nothing comes up

 

I have a few questions I am hoping someone can point me to the answers for. If there is a post in the thread that already addresses them, please let me know... it's a lot to read through.

My 2016 Lariat currently has 3.0 20204.
1) Is there a post that details the specific improvements I would see by going to 3.4? Aside from cosmetic... ie. CarPlay, other?
2) In the flowchart in first post, if I choose not to do that APIM update in the last step, what would I be losing? What does the APIM update give me? Is the APIM update the only risky part of this update process?
3) What is the difference between updating following the flowchart in post #1 (and downloads there) vs the CyanLabs auto updater created USB file set? Is it the same set of files I end up with on the USB stick, or different? How about down the road when I want to update to newer 3.4 version... any difference depending on which path I choose here for 3.0 to 3.4 update?

I am sure these have been discussed somewhere in this thread... but 4300 posts is a lot to skim through to find the info... If anyone can point me to the answers I would be very appreciative!

 

1. There is no changelog, read the thread for user reports of changes.
2. The biggest benefit of updating the calibration is the addition of lines that support hopspot options should you choose to try and retrofit a TCU.
3. Same result, although you are using a 3rd party application (Cyanlabs) in that case. While probably harmless, people need to do their due diligence to ensure any third party applications they run on their computer are safe (eg no viruses, malware, sending your info to Russia).

 

Also, Cyanlabs has their own forums for their "app". A lot of people put a lot of time and effort into this forum/thread. If you're seeking help, and using Cyanlabs, it's probably best to go ask them on their forum.

 

Cyanlabs works well. Sometimes a bit finicky and requires a few retries to download the files.

It might be a bit simpler than following the flowchart here but both work and they use the same files from Ford.

Many knowledgeable users here following the approach in this thread.

I was hesitant at first but see no downside after moving to the latest 3.4.

 

Have you had a problem with Android Auto incoming calls? Was waiting for a fix, and I heard it has been corrected in the latest update.