im currently tuning a 06A906032HN box, year 03.
using KKL ebay cable with FTDI driver tested and reccomended here.
also using MTX me7-2002 checksum plugin and tunerpro(latest build and not RT).

when i use the "Check if flash matches" button in nefmoto 1.8.0.0, and the original bin, the file matches the flashmemory.
now if i change a few bytes in the bin, and get a "checksums updated succesfully" message, when i try the "Check if flash matches" before i flash this modified bin, it sais the flash doesnt match.. so one question is.. should it match?

me7checker reported all checksums OK for the file, so i went ahead and flashed even tho it said it didnt match..

result, check engine and EPC light flashing and the throttle opening and closing in a cycle.. car starts but revs up and down..
NOW i cannot seem to connect to the ECU ever again.. not with vag-com, and not with nefmoto, so i cannot seem to restore the original flash.. and i dont really understand what is wrong.. all i can think of is the me7-2002 checksum plugin corrupting the file in some way..
that or if there is something wrong with the cable im using.. it does seem to appear a bit sporadic in the devices box in nefmoto.. as if it wasnt really ready..(same in vag-com).. but then i press refresh and its there.. and all communication seems to work.. file took 3:18 to flash.

any help/advice would be greatly appreciated.

i know i can recover the ecu using boot-mode.. but after that i want to be able to flash my new bin file to it with the changes without it going corrupt again.. =/

Could it be you changed some wrong bytes??  Just with checksums failures you should
never see the strange effects you described.
Probably you can post the changed and orig bins to be checked here.

thank you for all replies, this gives me hope =)
here are the original file..
then then 0001 file which should disable "sekundärluftpumpe" and rear O2 sensor for cat diagnosis.. also there is a bit changed for turning off the diagnosis on camshaft.. as i am using a different version of the tensioner(which gave me intermittent fault on over retarded intake camshaft).
this 0001 file flashed and the car ran great.. all DTCs i had earlier were removed.. but when i flashed it i got that flash file does not match flash memory message.. SHOULD it match??
something where spooky with this flash as the abs controller reported "an implausible message", other then that, it ran just fine.

so i proceeded to the next stage, where i wanted to try and add some more boost..
after logging AFR and making sure i was on the safe side of things.. i studied some examples and read all info available.. and came up with this 0002 file.. mainly modified kfmiop load axis, kfmirl, ldrxn, ldrxnzk, kfldhbn.. to see what happened.

i flashed this file after checking it with me7checker and all was ok..  AND here we are, the car is flashing EPC and check engine lights at me, throttle opens/closes and everything is spooked.. cannot for the world get in contact with the ecu again.. =(

any thoughts on using this cable? or if the nefmoto program should say that the file matches the memory? so i dont end up doing this allover again..

i was just about to start the fun part tweaking the life out of this old k03..

there we go, something is definitely wrong with the checksum correction plugin, and i was using an older version of the checker, as you said.

awesome setzi, now we know what is causing these spooks, lots of thanks! =)

=========================================
ME7Check v1.11 (c) mki, 06/2004-07/2011
Checking file Golf 1.8t 180bhp AUQ 06A906032HN 0261207440 363908.bin (size=104876)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4019.02//24C/Dst02o/220202//
-> Contents of ECUID data table:
   - '0261207440'         (SSECUHN)
   - '1037363908'         (SSECUSN)
   - '06A906032HN '       (VAG part number)
   - '0002'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


Page checksum failure(s) found
RSA signature failure found
Overall checksum failure found
-> Found 3 errors!!!   *******************************
=========================================

this is what i get when changing ONE bit in a known working original file for this ecu.. and letting the me7-2002 checksum plugin calculate and save the file.. surely something is wrong with the checksum calculation..

Gonzo: any thought on what could be causing this behavior besides the cheksums?

no known issues like these with the ebay KKL cables using FTDI d2xx drivers?

Weird.

I have tested files with wrong RSA checksum and worked perfectly. Oh well...

The image _0002 crashes with stack overflow after about 0.5 seconds!

In both modified images, _0001 and _0002 there is a modification in the code area,
so it is just luck that the image _0001 did not crash.

Here is the relevant diff from orig to 0001 and from 0001 to 0002:
At 83'F8EC there is a change:
< 0003f8e0: d4a942f4 80328d29 9a092750 9a0e0de0  ..B..2.)..'P....
---
> 0003f8e0: d4a942f4 80328d29 9a092750 0a0e0de0  ..B..2.)..'P....

< 0003f8e0: d4a942f4 80328d29 9a092750 0a0e0de0  ..B..2.)..'P....
---
> 0003f8e0: d4a942f4 80328d29 9a092750 ec0e0de0  ..B..2.)..'P....

This changed an instruction "JMP somewhere"  to a "PUSH PSW; JMP somewhere else",
the result is clear 

gonzo: i AM using tunerpro latest build with the MTX checksum plugin.. but the plugin apparently misses something in the calculation.

setzi: i dont think this is something i could have done in tunerpro while i set the disable bit for the camshaft diagnosis?
this is caused by the checksum plugin altering the code somewhere it shouldnt if i understand you correctly..?