Update Failed.....But did it?

[71Flipper]

Hi all, apologies for being a bit vague regarding the error message but I am a bit perplexed! I ran the update on my Sync and at the end it stated that the update failed. In my haste I didn’t record the failed message.

The bit I’m confused about is the fact that it does seem to have updated. The UI is different and the maps have updated (I live on a road that wasn’t on the original map), so I’m not sure what has failed. Should I just use the original data on the USB and try again?

Any help is much appreciated.

Thanks, Paul

PS I did use the CyanLabs Syn3 Updater to install not Ford, but I can’t seem to change that info in the edit!!

---

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.23219

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Erm…‘Update Failed’

Update Method: Official Ford

[Rollback_Jockey]

Run an interrogator log application and post results here.

[71Flipper]

I’ve tried it twice and it both times the Sync screen shows this error message. Is this in reference to trying to run the interrogator or what the original problem was?

When I put the USB back into the computer, the USB doesn’t seem to have anything saved under the Interrogator log.

[warlock12118]

First this can’t be “official Ford” for an upgrade method since you went from Sync3 3.0.x to 3.4.x
What are you trying to install now?
That error is the kind of thing that shows if your on 3.4.x and try to do a reformat without selecting “downgrade” as the reformat tool is not supported by Sync 3.4.x

[71Flipper]

Hi Warlock, did you read the bit that say ‘PS’, I did the upgrade via Cyanlabs Syn3 Updater. I had ticked the wrong box!

Thanks, Paul

[warlock12118]

Did not see the PS.
What are you trying to upgrade now that its throwing the error?

[71Flipper]

Not trying to upgrade anything anymore, I’m just trying to run an interrogator log as suggested by Rollback_Jockey

[SaNdMaN]

For the USB you are using, share the contents of the .lst files located on the root.

[71Flipper]

This??

; CyanLabs Syn3Updater 2.13.0.0 Stable - Autoinstall Mode - Interrogator Log Utility EU

[SYNCGen3.0_ALL_PRODUCT]
Item1 = TOOL - GB5T-14G386-AA_56065.tar.gz
Open1 = SyncMyRide\GB5T-14G386-AA_56065.tar.gz
Options = AutoInstall

[SaNdMaN]

Yes, that. It seems you didn’t update Syn3Updater with your current build, you should not be using that interrogator package.
So correct that and recreate the interrogator log since it’s version dependant.

[71Flipper]

To get the above I just opened the .Ist into notepad and then copied and pasted the result above. I know a little knowledge is a dangerous thing, but given the ‘PKG_ERR04’ in the picture I posted above the FAQs are stating…

** One of the packages you are trying to install has been blacklisted on the version you are presently using.*
** The most common time this happens is when trying to use the [reformat] utility. Downgrade your apps version to 3.4.19101 or lower, or use the ‘downgrade’ functionality of the [Syn3 Updater], then re-run [reformat] utility.*

Should I just follow the instruction above?

[71Flipper]

OK, I apologise for my complete ignorance here, but how do I do that?

Thanks, Paul

Scrap that, I DO know what you mean…

Its late now, I’ll do it tomorrow and update, thanks for your help.

[71Flipper]

Hi Sandman

I have changed the CYAN to reflect the correct build (3.4.23188) and run the interrogator log three times, it has successfully installed but when I put the USB back into the computer and click to open the interrogator log the file is empty! I have no idea why, or what is going wrong.

As per your original instruction I have shared the contents of the .Ist file if thats any help for you.

Thanks in advance

; CyanLabs Syn3Updater 2.13.0.0 Stable - Autoinstall Mode - Interrogator Log Utility

[SYNCGen3.0_ALL_PRODUCT]
Item1 = TOOL - GB5T-14G386-AD_1606255780000.TAR.GZ
Open1 = SyncMyRide\GB5T-14G386-AD_1606255780000.TAR.GZ
Options = AutoInstall

[SaNdMaN]

Your unit is acting strange… If you haven’t performed a master reset it’s a good time to do so, then try running the interrogator again.

If that keeps producing a blank file, then you should manually create an interrogator log with the -AC package…