SYNC3 3.0 17276_PRODUCT
Non Navigation
This is the file and autoinstall.lst you are using?
Did you check the APIM for DTC’s?
Yes *-AB.tar.gz
I dont know how to do that
This unit looks like it has never been updated. Looking at the picture above, if you are looking to update to Sync 3.4.21020, forget about running the Interrogator file, you will have enough free space to perform the upgrade for NON-NAV using the Syn3 Updater.
The files you need are:
5U5T-14G381-ER 847Mb Sync3 v3.4.21020
5U5T-14G391-BN 1.4Gb Sync3 v3.2.20339
And Gracenotes, either:
4U5T-14G423-BB 923Mb Sync3 v3.3.20178 1.1.1.2220 (GL-0011)
or
4U5T-14G423-EB 390Mb Sync3 v3.3.20178 1.1.1.2208 (CN-0020)
depending on what will fit on the storage.
OK I will try it
Thanks a lot
CYANLABS - SYN3 UPDATER - V2.5.7.0
Branch: Release
Operating System: Microsoft Windows 10 专业版 (2009)
PREVIOUS CONFIGURATION
Version: 3.0.17276
Region: CN
Navigation: False
Mode: reformat
DESTINATION DETAILS
Mode: Drive
Model: Kingston DataTraveler 108 USB Device 7.4GB
FileSystem: exFAT
Partition Type: MBR
REFORMAT.LST
VOICE=5U5T-14G391-BN_1615427750000.TAR.GZ
GRACENOTES=4U5T-14G423-BB_1598634411000.TAR.GZ
APPS=5U5T-14G381-ER_1615427592000.TAR.GZ
AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.x - reformat Mode - Sync 3.4.21020 CN
[SYNCGen3.0_ALL_PRODUCT]
Item1 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall
FILES (4)
1u5t-14g386-cb.tar.gz (8.5MB)
5U5T-14G391-BN_1615427750000.TAR.GZ (1.4GB)
4U5T-14G423-BB_1598634411000.TAR.GZ (923MB)
5U5T-14G381-ER_1615427592000.TAR.GZ (847.1MB)
LOG
[2021/4/15 10:34:31] Selected Region: CN - Release: Sync 3.4.21020 - Map Version: 非导航APIM
[2021/4/15 10:34:31] Install Mode: reformat
[2021/4/15 10:34:31] Checking Existing File: 1u5t-14g386-cb.tar.gz
[2021/4/15 10:34:31] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download)
[2021/4/15 10:34:31] Checking Existing File: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:34:31] Downloading: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:38:39] Validating: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:38:48] Downloaded: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:38:48] Checking Existing File: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:38:48] Downloading: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:41:57] Validating: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:42:02] Downloaded: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:42:02] Checking Existing File: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 10:42:02] Downloading: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 10:46:38] Validating: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 10:46:43] Downloaded: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 10:46:43] Preparing USB drive
[2021/4/15 10:46:43] Formatting USB drive
[2021/4/15 10:46:43] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[2021/4/15 10:47:04] Checking Existing File: 1u5t-14g386-cb.tar.gz
[2021/4/15 10:47:04] Copying: 1u5t-14g386-cb.tar.gz
[2021/4/15 10:47:08] Validating: 1u5t-14g386-cb.tar.gz
[2021/4/15 10:47:09] Copied: 1u5t-14g386-cb.tar.gz
[2021/4/15 10:47:09] Checking Existing File: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:47:09] Copying: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:52:59] Validating: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:54:26] Copied: 5U5T-14G391-BN_1615427750000.TAR.GZ
[2021/4/15 10:54:26] Checking Existing File: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:54:26] Copying: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:58:16] Validating: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:59:10] Copied: 4U5T-14G423-BB_1598634411000.TAR.GZ
[2021/4/15 10:59:10] Checking Existing File: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 10:59:10] Copying: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 11:02:32] Validating: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 11:03:22] Copied: 5U5T-14G381-ER_1615427592000.TAR.GZ
[2021/4/15 11:03:22] Generating reformat.lst
[2021/4/15 11:03:22] Generating autoinstall.lst
[2021/4/15 11:03:22] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
Try doing a master reset and then the USB again.
not work 
Use a decent drive
I have change 5 drive
got save error
If you:
- tried different drives
- made sure no other device is connected to the car (usb drive, phone, sd card, ANYTHING)
- tried different ports
Then I’d think it’s a HW issue… not sure what else you could try…
@Zhao - I’m in the same exact boat with you. I’ve followed all the advice, tried different drives and ports.
- When I create USBs with the Ford site, everything I plug in is ignored.
- When I create USBs with CyanLabs, everything I plug in gives, “The USB storage device has been changed or removed.”
Everyone on this board has been very helpful. I bet we both have the same HW issue.
@Zhao , @kturner367 ,
Make sure there are no other usb devices connected to the vehicle.
Remove power from the vehicle, disconnect battery for 15 minutes. Reconnect battery, start vehicle, motor running, try installation again. If you are NON-Nav, remove Gracenotes from the installation.
If this does not work, there is some kind of hardware conflict.
I will give it a try this weekend! I have come this far and everyone has tried so hard to help. Thanks, @F150Chief .
@F150Chief - Thanks again to you and everyone for all the help. I did it all. Disconnected battery. Used multiple thumb drives. Used Ford load. Use Cyanlabs.
- When I create USBs with the Ford site, everything I plug in is ignored.
- When I create USBs with CyanLabs, everything I plug in gives, “The USB storage device has been changed or removed.”
I am going to consider this case closed and attribute this to HW.
1 Like
The folder now contains a hidden folder
When i delete it the car return PKG_ERR003
It looks like a step forward 
That folder is completely irrelevant and caused by windows not your car.
Yes I know.
With it ,the program popup Installation Paused
Delete it ,popup PKG_ERR003
Still not related to that folder.
PKG_ERR03 – Error is PKG_UNTAR_FAILURE
So your file is likely corrupted
I agree that there is most likely a hardware issue in this case…glad to help.