[The Ace]

I wish that was the case for me. I'm working on the 2.7GB SYNC update, not the map update. USB in exFAT, cannot get the XML file written back onto it despite numerous attempts. I remove the stick once it gets to "already up to date, please remove USB drive".

It worked before (same USB drive) and I successfully confirmed on the website. Now website has gone back to saying I have a 2.7GB update available so I'm trying to regenerate an XML file to confirm it.

Steve

Exact same deal for my Kuga, original update didn't generate the xml file (for whatever reason), so I'm trying to force the system into generating the xml file through the "already up to date" process. No luck so far, and this is blocking me from updating the maps, which is really, really, really necessary: due to many new roads, especially highways, current maps version 6.1 shows my Kuga traveling through mountains or fields half the time....

 

[The Ace]

I think I should update this thread with my findings. After installing the update for the first time, I removed the USB before the system had the time to create the xml file, thus I was unable to update the Ford site and get the map update, since according to my info, I was still on Sync2.3 and needed to get to Sync3 before updating the maps. However, every time I tried to re-apply the Sync update, the system did not recognise the USB and/or the folders and/or didn't start the update at all.

Today, after repeating the same process (formating, downloading, unzipping), and since the system apparently did not want to "see" and start the update, I performed a master reset. Lo and behold, immediately after inserting the same flash disk (which didn't work before), the system started applying the update. In about 10 minutes I saw the "Update finished' message, removed the flash disk, and indeed there now was the xml file, nice and neat in the SyncMyRide folder.

Updated the Ford site with my xml, and immediately checked for a new update. Didn't expect anything, after hearing the delays some of you guys have seen, but to my surprise, the map update showed up right away. Downloading as I write these lines, hopefully I might be able to apply the map update today (if I find the time).

 

[The Ace]

Hmm, while the xml upload for the upgrade to Sync3 prompted me immediately to download the new maps, the xml upload for the upgraded maps is still not recognised (?) by Ford's server, and I still get the "maps download available" message when checking for updates with my VIN. Just a matter of time, I guess.... ?

 

[The Ace]

And again, the time limit (10', is it ?) is ridiculous...

Anyway, today the Ford site shows an available map update file, however this one has a different filename to the one I downloaded yesterday (and a fellow Greek owner told me that it also has different CRC and size). So it seems that, although the xml did take some time to get acknowledged, there is indeed a newer update for maps. Downloading right now, and will apply at earliest convenience...

 

[The Ace]

Downloaded latest map update file (files are dated Sep18, while previous update was Jul18), tried to apply and (a) first message was "update already applied, changes will take effect next key cycle", and (b) after key cycle, trying to update got the dreaded BGMAP_ERR message. Which persisted, even though I re-downloaded the files, reformatted and re-copied everything. Even tried a master reset, to no effect. Will see if a new USB flash remedies the problem, it is mentioned in the instructions that the USB might become "locked" by SYNC.

However my SYNC is updated, maps are F7, so I'm guessing the latest update has minor fixes or changes and does not contain a major update.

Updated work colleagues sync, it's now on 18025 however didn't generate an xml file so won't offer the map update. In theory can I use my map update file to update his maps??

In theory yes, but you have to search the xml file and replace all identifiers of SYNC and vehicle, such as VIN, serial numbers, versions etc....

 

[The Ace]

Well, don't know if it turned out that the "new" update wasn't actually new, or if something updated by itself via wifi (I'm certain that any attempt via USB failed with BGMAP_ERR), but checking the Ford site right now shows my Sync as fully updated.

So, all's well that ends well.... (?)

 

[The Ace]

More than happy to provide you with both xml files

Sync 3.0 Update

Maps Update

 

[The Ace]

You need to change the identifiers of the vehicle, but as far as I can see, you need to change 3 values: VIN, SYNC serial, and SYNC version. In theory it's just a matter of seconds, rename the file and change the 2-3 "serial" or "version" numbers within the xml file.

 

[The Ace]

I have a picture in my phone of my Sync's screen after the last update, but unfortunatelly it doesn't contain the serial, you'll have to wait until this afternoon when I'll get back home and check. Since it's the same number (along with VIN) in both files, it should be the serial...

 

[The Ace]

Glad it worked as intended! Update the maps and your (well, your mate's) Kuga will be all caught up Plus we have found a way to "force" the Ford site to serve us the next update...

 

[The Ace]

Well, something's gone wrong with one or more of these xml files, because now the Ford site tells me that my Kuga doesn't have a Sync unit

Will try to update via the Sync's built-in update, see if it helps...

 

[The Ace]

PS And Ace was going to borrow your XML file and update but that dropbox link previously posted appears broken (404 error).

I re-arranged the folder structure of my entire Dropbox so the link isn't valid anymore. Send me a PM with your email and I will send it asap
You want the map update xml, right ?

 

[The Ace]

Greek site is also still operational, the layout is identical to the UK site, so you can use it without understanding a single greek letter or word

Ford SYNC Update - Greece

 

[The Ace]

Just been back on site to see if records have been updated since xml file upload, and same as Anthony, my car now DOES NOT HAVE SYNC, what a **** company Fraud is

It's kind of a relief for me to know that I'm not the only one whose Sync pulled a Hudini...

 

[The Ace]

Sent email to Ford tonight asking why my ST Line now “does not have sync”, i await with the reply baited breath!!

Have sent similar email to Ford Greece since last Friday, still haven't received anything except the automated reply surprise:

 

[The Ace]

Have sent similar email to Ford Greece since last Friday, still haven't received anything except the automated reply surprise:

Just received a reply from Ford, they say it's a system error, i.e. site gives wrong message, instead of the usual "there is no available update".

It should be corrected "as soon as possible" (exact wording).

 

[The Ace]

Ahh, ZX Spectrum, so many memories

I have both Kuga and Fiesta booked for their annual service this Monday, so I'll probably ask the guys if there is any new development on this issue....

 

[The Ace]

I had a Spectrum with 16k and bought the 48k expansion unit, which was useless if it wobbled...

If you didn't have the Kempston, then you haven't really experienced the "wobbly-as-they-come" tenderness of Spectrum's expansion port...which would also fry the motherboard every-single-fricking-time crying:

 

[The Ace]

Apart from Nigel's post with Microsoft's article about this issue, an elevated prompt "attrib -r -s /s /d" or a recursive "File -> Change Attributes -> clear system or read-only" from an admin-priviledged Total Commander should do the trick

 

[The Ace]

....In light of this, I would recommend that you contact your local Ford Dealership, advise them of the concerns you are having with the website and obtain further guidance from them. We need to understand why your VIN is associating your vehicle to not having SYNC 3...

I did just that, since I had both Fords booked for their yearly service yesterday, and all I got from the tech consultant when I mentioned this error, was a blank stare and a "I really don't know what to tell you sir" plain:

I even mentioned ETIS, and if they could just plug it in the IDS to check, but in vain. If the same error continues for the next couple of weeks (i.e. it's not resolved on its own) I will follow up with another email to Ford's main offices....