Hello, I have a problem with the log file too. Can I send you mine? I don’t know how to send PM here
I confirm that after the update to version 3.4.23088 the xml file no longer contains invalid fields and I could upload it to Ford website. I did not find the xml on the pendrive therefore I’ve used Interrogator_AD to generate it after the upgrade. I would say that Ford has fixed it.
1 Like
wow 
that’s the time when i do the update then. thanks a lot @aepm cheers!
quick q: Never used Usb3_updater before, thus wondering will be still able to update official releases in future by Ford.co.uk/support if this version 23088 is installed on my vehicle?
Another question: how to generate log xml file now 23088 successfully applied into vehicle?
The Ford update system wont want to know you anymore.
1 Like
I really do not understand why people are interested in letting Ford know that they have abandoned Ford’s upgrade path and performed an upgrade on your own, thus voiding any warranty that may be active…
If you are using Cyanlabs, it’s because Ford has forgotten about you… And yet, they still try to make Ford remember…
An exception of course: if you used Cyanlabs to go to where Ford wants you to be.
If you have a TCU they know. I have noticed Oasis shows any upgrade I do even though I dont report it.
But that won’t change what Ford will push your way if outside Ford’s path, right?.
That was my understanding: if Ford wanted you to be at 3.0, even though you upgrade to 3.4 with Cyanlabs and push that information their way (TCU, XML, or whatever method available), they may acknowledge you are on 3.4, but still won’t send you any future update.
That’s why I said before that to me it’s futile trying to let Ford know that you upgraded, if you left their path, then you are alone.
We did have cases from users that got stuck following the Ford’s path and used Cyanlab to solve that, but they didn’t leave Ford’s path so it made sense for them to inform the upgrade completion.
And since we are talking about XML files, it’s good to know that the last 23088 build seems to solve that.
My experience:
I was on v3.0 in the Ford website. I gave my VIN to one of the users and he updated it to 3.4 on the website.
It showed my version is 3.4.22251 and up to date even after the latest release. Also I couldn’t upload the xml file. I dug into the source and extracted the ford APIs which you could interact with Ford. I uploaded the xml for the latest version but nothing changed, so I decided to upload the original v3.0 xml and surprisingly it got back to v3.0 in the website. After that I tried to upload the latest one but it stuck on the v3.0. 
1 Like
Correct. I was just saying Ford knows what we do.
: )
Having next version installed is my direction, without being worried too much who knows what @SaNdMaN You are correct about being forgotten by Ford and that is why is good CyanLabs is taking resolutions. This won’t be a blocker if i keep use up(r)dates from Ford.co.uk i believe.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.