Hmm.........I'm surprised too!
OBD11 has been able to make EEPROM changes for some time now - but it's very clunky and at least from a user perspective, it's ONE memory address at a time!!
Even at a cost of 400 Credits, I'm very surprised that the One-Click-App (OCA) has the smarts to detect the required flash-file, then to automatically upload the parameter-file - all without ANY user intervention!!
And in any event, a Audi A5 has a MLB platform build whereas OP's 2018 golf Alltrack has a MQB platform - it's beyond belief that a 400 Credit OCA didn't flag this difference during the compliance testing phase of operation and refuse to implement!!
Anyway, the most impacting aspect of OP's problem is that OCAs don't disclose the changes that they make - which means understanding how to revert values back to their original settings is very much a guess (even if OP has knowledge of how the tweak is manually coded).
My hunch is that the ONLY practical way to address this problem is by contacting the OBD11 help-desk because ONLY the deities on the OBD11 mother-ship know what changes are made. The rest of us may have good intentions - but we are just guessing (no offense intended)
If OP has contacted the help-desk without reply, then more vigorous attempts are needed- with stronger (but polite) words about the accountability of OBD11 fix this problem because they have taken the money!!
But perhaps the most important lesson from this case to all OBD11 users is the resounding message: never use OCAs unless you are prepared to accept the near-impossible task of unwinding coding changes that are not disclosed!!
As I've said before - Using OCA's is like rolling-the-dice: sometimes you win and sometimes you lose! And extending this analogy - the more that you gamble with OCAs - the greater the chance of losing (it's just a matter of luck and time)!!
In OP's case - it's
Don
Bookmarks