Hey,
I am looking for people who are on various SYNC versions, 1.x to 3.4 to test a simple update file, it won’t update the system it purely outputs a log file.
Even better if they are on different HW variants, like MY16, MY20 etc.
If you are able to test please use this file and provide your results via this Google Form
Cyanlabs Test 2 - Tested.zip (225.8 KB)
Thanks.
I can test it out for you
Please try this file,
[SEE NEW POST]
Note: Extract it to a USB formatted as ExFAT (MBR)
it will return the error
“Corrupt USB tool detected. Please update USB using dealership tool”
But you will have a logging.txt file in the root of your USB drive.
Please DM or post here the log file (your VIN is visible in it so redact that if you wish)
No joy.
2018 Fusion with a MY2020 APIM running 3.4.23188.
Updating system software message in screen, left it in for ~10 minutes, never generated the error or a log file.
Sorry there was a mistake in the autoinstall.lst as it replaces it when ran first time, forgot about that, try this
Cyanlabs Test 1 - Fixed.zip (225.8 KB)
2018 Fusion with a MY2020 APIM running 3.4.23188.
Updating system software message in screen
Followed by SyncUpdater banner
APIM rebooted, never saw the error.
logging.txt (712 Bytes)
Thanks, yes after further digging, if you are on the latest SYNC version already it has a slightly different output.
Interestingly i have about 6 reports at this point, yours is the only one with Model: 01, all others are Model: ALL i wonder if thats cuz it’s MY20 or something else.
It’s a 5U5T series running:
5U5T-14G371-CKF as the calibration level, so -EM in the F188 strategy and -BC on the F168
I can test. MY20 APIM with latest 3.4
EDIT:
Will have to wait until all the storms clear.
Sure thanks, i have modified the file very slightly, please share either redacted here or via DM your logging.txt file 
Cyanlabs Test 2 - Tested.zip (225.8 KB)
Please share your logging.txt file here
https://docs.google.com/forms/d/e/1FAIpQLScCH5eXNkABaxPC8CLgdUyYciYOpOBOkPgT7SUVNaE0riZ9FA/viewform?usp=sf_link
MK3 Focus RS 2017 (2015 model)
STARTING SCRIPT
Language detected: ENG
Language defaulted to ENU
Entering verificationCheck
Current version: 3.4.23188
Entering extractTar
Entering variableAssign
Successfully verified packages
PART_NUMBER = KU5T-14G386-AAL
SCRIPT_VERSION = v202403
INTERROGATOR = GB5T-14G386-AE
VCA = PU5T-14G386-BC
Entering leaseCheck
Date on vehicle: 05_08_2024
USB lease code: 508235303202820407624380455270559318602188943625410535402895
Entering checkOverlay
Hardware variant: 17
Entering B460Check
Entering screenCheck
Screen enum detected: 2
Screen size detected: 8
Entering checkRegion
Entering checkNav
Entering getVehicleModel
VIN: WF05XXGCC5HM70284
Could not determine model from VIN: WF05XXGCC5HM70284
Model: ALL
Module is up to date
Also…
Also filled in google form
MK2.5 Kuga 2018 68 plate
STARTING SCRIPT
Language detected: ENG
Language defaulted to ENU
Entering verificationCheck
Current version: 3.4.23188
Entering extractTar
Entering variableAssign
Successfully verified packages
PART_NUMBER = KU5T-14G386-AAL
SCRIPT_VERSION = v202403
INTERROGATOR = GB5T-14G386-AE
VCA = PU5T-14G386-BC
Entering leaseCheck
Date on vehicle: 05_09_2024
USB lease code: 508235303202820407624380455270559318602188943625410535402895
Entering checkOverlay
Hardware variant: 17
Entering B460Check
Entering screenCheck
Screen enum detected: 2
Screen size detected: 8
Entering checkRegion
Entering checkNav
Entering getVehicleModel
VIN: Wx0AxXWxMAxP1x6xx
Model: 11
Up to date version not detected for B460_8_11_EU_NAV
Entering safeExit
Safe to exit
Got the following screenshot after script had run
Posted to the google link as well.
Mine completed with a success screen just like Rollback’sn using test2
STARTING SCRIPT
Language detected: ENU
Entering verificationCheck
Current version: 3.4.23188
Entering extractTar
Entering variableAssign
Successfully verified packages
PART_NUMBER = KU5T-14G386-AAL
SCRIPT_VERSION = v202403
INTERROGATOR = GB5T-14G386-AE
VCA = PU5T-14G386-BC
Entering leaseCheck
Date on vehicle: 05_08_2024
USB lease code: 508235303202820407624380455270559318602188943625410535402895
Entering checkOverlay
Hardware variant: 1850
Entering screenCheck
Screen enum detected: 2
Screen size detected: 8
Entering checkRegion
Entering checkNav
Entering getVehicleModel
VIN: 3FA6P0xxxxxxxx
Model: 01
Entering upToDateCheck
Module is up to date
Thank’s guys, unfortunately i don’t think any of the information provided from these logs will assist in identifying MY20, i was hoping there was a reliable indicator but there isn’t.
You can’t win them all bro, you may still stumble on something.
STARTING SCRIPT
Language detected: ENU
Entering verificationCheck
Current version: 3.4.23188
Entering extractTar
Entering variableAssign
Successfully verified packages
PART_NUMBER = KU5T-14G386-AAL
SCRIPT_VERSION = v202403
INTERROGATOR = GB5T-14G386-AE
VCA = PU5T-14G386-BC
Entering leaseCheck
Date on vehicle: 05_10_2024
USB lease code: 508235303202820407624380455270559318602188943625410535402895
Entering checkOverlay
Hardware variant: 1850
Entering screenCheck
Screen enum detected: 11
Screen size detected: 8
Entering checkRegion
Entering checkNav
Entering getVehicleModel
VIN: Redacted
Model: 12
Entering upToDateCheck
Module is up to date
Is it possible to detect the installed drivers or the emmc of the unit tested without JB the unit?
I’m thinking he might have something based on the hardware variant as opposed to the model number returned.
You can only use packages that are signed by ford so if ford has a logging tool for listing drivers then yes, if not no. And AFAIK it doesn’t
