Hi MaXXeH,
To be fair to AMD it sounds like they are doing it the right way!
For the 2.0 TFSI’s with the ME9 ECU there are a lot of different original files
SOME WITH THE SAME HARDWARE AND SOFTWARE NUMBERS BUT MOST DEFINATELY DIFFERENT FILES WITH HUGE DIFFERENCES IN THE SOFTWARE CODE AREA!
All they are doing is covering their arses rather than gambling with a customers’ car for which you can’t really knock them.
It is always best to have the original file for a vehicle than to use a tuners best guess.
With the older Golf V’s there seems to be only 1 or 2 variations for each hardware/softrware version where as later ME9’s (S3/TTS) there are way more:
0261S02721-1037501227 is for 09, 10 + 11 plate S3/TTS and so far we have found 5 different versions of original file with the same Hardware and Software numbers!
They have massive differences in the software code area.
Nick (RT) is right though, the Maps locations and values are generally the same so provided you have a read out of the file currently in the car and compare the maps with another original with matching hardware/software numbers you could ‘make’ an original but this would always be a last resort for us.
I suspect what’s happened with AMD is Angel tuning have locked out the OBD read function meaning they can only get the hardware and software numbers but no actual OBD read and for the reasons stated above it would be a risky process to flash another file into it without being able to see what is currently in there. Perhaps they are trying to avoid having to remove the ECU?

Also, size of file depends on what tool you use for OBD read and write............ most tools only read a partial file hence the need for ‘full BDM’ read out as suggested by Nick, we use CMDFlash for these which reads/writes the full 16Mbit (2048k) file via OBD ;-)
239HP sounds like a good file BTW – does it drive nicely on the road, good linear power delivery?
Keep us all posted.........
Nick – Carbon Chiptuning