Brilliant! Well spotted! That might have to be a Sunday morning job for me this week due to the time it’ll take so I’ll report back then unless I can squeeze it in sooner. Thank you.
@F150Chief Just a quick query regarding that latest autoinstall file, are the items listed in there supposed to have the full name including the long number at the end? Currently it lists files like this:
HB5T-14G386-TJB.tar.gz
Should they be listed in there like this instead:
HB5T-14G386-TJB_133301.tar
Also in the autoinstall file they have .tar.gz, should they be just .tar?
Not doubting you, you just checking.
The file names must be identical. They should always be listed with the .tar.gz extension.
Item = the name of the file or function. Does not need the extension. This is a description.
Item1 = HB5T-14G386-TJB
Open = the file or process. This must be exactly as found in the enclosing folder.
Open1 = SyncMyRide\HB5T-14G386-TJB.tar.gz
If the file in the SyncMyRide folder includes the Epoch date, then it must be included in the Open line. Ford usually changes the filenames to NOT include the epoch date for the files used for the map and other updates when using the Ford autoinstall.
1 Like
@F150Chief I’ve manually added the full file names then to include the long number at the end to match the files in the SyncMyRide folder so now it looks like this:
autoinstall.lst (864 Bytes)
So I should be good to go now?
I didn’t check the epoch dates (numbers) but that looks good.
In case you are unfamiliar with Epoch time…
Epoch Converter - Unix Timestamp Converter
1 Like
Just double checking them now myself and then i’ll go stick it in the van. I don;t technically have time to sit in it and watch it this time around but I have every faith in you so I’m going to leave it unattended and check on it every so often to see what’s going on.
Just make sure the car does not shut off…
Will do, I’ll leave the engine running with stop/start disabled and i’ll lock it manually with my spare key.
For reference in case something fails so I can check back through it for potential mistakes on my part, this image below is exactly what my USB looks like now.
@F150Chief I think you’ve only gone and done it! Install went smoothly, no loops or weirdness.
Bezel diagnostics shows IVSU versions as follows:
AX - 3.0.2024
AE - 3.2.19056
AB - 3.0.17024
BH - 3.2.22023
BG - 3.2.22023 
And the Interrogator log is here:
Sync_LW3D00F8_WF0RXXWPGRHM78267.xml (10.3 KB)
I locked and unlocked it a couple of times and didn’t get any pop-ups about installation so hopefully that’s it, I guess i’ll keep an eye on it and report back if anything weird happens over the next few days. I haven’t yet done a Master Reset but i’ll get that done tomorrow at some point.
I honestly can’t thank you enough for the time you’ve put into this and the help you’ve given me, you really got me out of a jam with this 
1 Like
Just monitor it for a few key cycles. It’s most likely all good now. The log file agrees with the IVSU data.
JR3T-14G391-AE
JR3T-14G421-BH
JR3T-14G424-BH
JR3T-14G422-BG
JR3T-14G423-AB
You storage is exactly where it should be.
<d2p1:PartitionHealth type=“/fs/tmpfs/” total=“128M” available=“126M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“1.1G” available=“6.2M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“19G” available=“28M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“18G” available=“48M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“1.9G” available=“7.6M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/grace” total=“1.0G” available=“6.1M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1024M” available=“707M”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1024M” available=“40M”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“55G” available=“12G”/>
Looks fixed to me!
I am happy to help. See your messages…
1 Like
@F150Chief Awesome!
This is just a followup from my research, no action needed. I found an old post by ACool on the F150Forum about the JR3T-14G421-CD file:
You have to list it twice. There are two files in that update. If you don’t list it twice then it thinks the entire file has to be installed at once. There’s not enough room for that entire package to be installed at once.
[SYNCGen3.0_2.0.16074_PRODUCT]
Item1 = JR3T-14G421-CD.tar.gz
Open1 = SyncMyRide\JR3T-14G421-CD.tar.gz
Options = AutoInstall
[SYNCGen3.0_ALL]
Item1 = JR3T-14G421-CD.tar.gz
Open1 = SyncMyRide\JR3T-14G421-CD.tar.gz
Options = Delay, AutoInstall, Include, Transaction
I just found this today by chance looking for another file…
1 Like
Haha brilliant, well you figured it out anyway luckily for me.
You’re up early…!
1 Like
@F150Chief yeah I get up at 05:00, I work 05:30 - 13:30 weekdays 
Hi guys,
Just wanted to leave a comment, that I have been having the exact same issues, literally with the same SYNC 3 v2.2 update to v3.0. Laggy and unusable SYNC stayed in loop of installation forever. However, going through your conversations, several tryings, files uploaded and solutions, I have managed to fix it, too. I cannot thank you enough for this thread and all of your input. I was pulling my hair out, for why I wanted to update my SYNC.
Luckily, all sorted with one difference only, that although my gracenote version is not showing, my SYNC is not showing any installation in progress message without the USB stick plugged in. So I am thinking to leave it as it is, as it works now without lagging. Scared that if I touch it one more time, will cause further issues.
Anyways, massive thank you to you all!
Daka
1 Like
Sounds like it should be ok to remove the USB stick and just see what happens, removing it shouldn’t mess anything up. If it lags when it’s removed then the problem isn’t completely sorted yet.
Sorry, I meant to say the USB is not and was not plugged in at all after the map installation.
No gracenote version, but the F11 map updated and no lag.
@Daka that seems like a stage that I was at at one point, everything looked ok and the screen was showing maps as F11 but the bezel diagnostics was showing that part of the maps wasn’t installed correctly and I had no version number next to Gracenote. Not exactly sure at which point in this thread that those particular problems got solved as it took quite a few different install attempts to sort everything. I’m sure @F150Chief won’t leave you hanging, maybe he just needs a rest after having just sorted mine out 
1 Like
Do you care about it?.
If so, create an interrogator log to see what’s on the unit and report the results back.
If they are not installed and you have enough free space on the APIM, you can try manually installing it.
2 Likes