Well first off all you'd need to fix up KUMSRL and other related maps which in turns messes up a whole load of other modules so you gonna need to fix them up aswell.

Why "No"?

Just started to look at maps of my A3 1.8TFSI convertible, which I stroked to 2.0.
First thing I noticed when I drove it with stock 1.8 tune - there is more torque low down even compared to stock 2.0TFSI which is a little strange.

I decide to copy KFZWx and KFZWOPx from 2.0 file, but it was strange for me that in my 1.8 file there was low-mid rpm zones with more advanced timing compared to those in 2.0 file. It is quite contra intuitive for me but it was obvious Maybe this is part of the reason that I can feel this stroker more torquer than stock 2.0. Another thing is that 1.8 request more load before 2000rpm, because of the smaller displacement.

Another thing I've noticed - I think KFMIOP/KFMIRL seems that wasn't been calibrated @ high load ranges (not used in stock tune). Nevertheless 2.0 file looks much better even in those ranges.

As for the knock control - sure there is quite a difference there and I find it to be normal. We use same length rods with longer stroke (for EA888 difference between 1.8 and 2.0 is only stroke) and in my opinion this changes will make a difference in normal noise frequencies.

That's why I really wonder why it is not needed to recalibrate knock control when stroking those engines.

Kind Regards,
Chris

Some people in the Big turbo 1.8t FB group claim their ME 7.5 ECU did not run very well with strokers apparently ignition and knock sensor causing issues and all sorts of stuff... I call bullshit on that, since there have been cases on this forum where people run me7.5 on strokers fine if you adjust all the stuff needed.

There are still "loads" of companies that just flash off the internet files, or flash one file made for a car to multiple ones..

Try tuning the cars first. Before gutting kr

And here comes another problem - what tool to use.
For my previous Med17.5 car (2012 A3 8p 1.4TFSI) I bought a Russian tool PCMflash which is perfect for DIY, because it is not prohibitively expensive.
However in "virtually read" files (based on SGO originals) there is no file for my ECU number 8P7 907 115 H 0030.
However there is a file for 8P7 907 115 K 0030, and looking at pictures in internet it seems both ECUs share the same hardware number 8P0 907 115 Q and both part numbers are used on CDAA 1.8TFSI engines.
Now I'm thinking to crossflash my ECU with K lettered ago with ODIS-E, and after that to work on K file and finaly use PCMflash to write it to the car.
What do you think - should I try this plan, or to search for another solution?