When reading the XML, updater is telling me It cannot determine if I have MY20 or not

I updated my Gen 2 sync Hardware to Gen 3.4 2 years ago. It has been working well. I was wanting to update to the latest version as it has 3.4.22111.
When following the steps, and I acquire the xml from the APIM, it tells me it cannot determine if I have MY20 or not. Is there a next step or just leave it alone so as not to brick.


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Unknown

Install Type: Replica

Old SYNC Version: 3.11

New SYNC Version: 3.4.2211

Do you have a error message, if so what is it?
This page contains the following errors:
error on line 66 at column 28: PCDATA invalid Char value 11

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

This page contains the following errors:
error on line 66 at column 28: PCDATA invalid Char value 11
Below is a rendering of the page up to the first error.
1FT8W3BT4FED27183 ECU CONSUMER OTA SYNCGEN3 OTA 7D0 5U5T-14G381-EZ false 345535542d3134473432312d434a44000000000000000000345535542d3134473432312d434844000000000000000000345535542d3134473432312d434744000000000000000000345535542d3134473432312d434644000000000000000000345535542d3134473432312d434544000000000000000000345535542d3134473432312d434444000000000000000000345535542d3134473432312d434344000000000000000000345535542d3134473432312d434244000000000000000000345535542d3134473432312d434144000000000000000000355535542d3134473339312d435200000000000000000000345535542d3134473432322d43434a000000000000000000345535542d3134473432322d43424a000000000000000000345535542d3134473432322d43414a000000000000000000345535542d3134473432332d434300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 false 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 false Blank false Blank false Blank true Blank true Blank true Blank true Blank true Blank true Blank true

If you have upgraded from 2.0 to 3.4 than you have done the reformat and it’s not a MY20 APIM. You must have a setting wrong that is now causing it to tell you this. Had you not done the reformat before I would tell you to assume it is a MY20 APIM unless you take it out and look at the sticker on it.

I’m not sure what you shared before, so share the XML file.

If the model can’t be determined:

  • take it apart and take a look at the sticker
    Or
  • use Fmods’ universal reformat package to reformat the unit to install 3.4 (that tool is MY20 compatible)

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.