I am trying to Immo-OFF my 2001 Audi TT ECU 8N0906018AT.  I soldered a jumper on pin 24 of the flash chip to short to ground, power on, wait 6-7 seconds, remove jumper, now I am in Bootmode I think.
I have a KKL  USB on COM 10 of my machine, and a bench ME7 harness

I can read out the 512 EEPROM bytes (95040) successfully.

Then I write a new file into the EEPROM.

C:\me7_95040_v1.31>me7_95040.exe --bootmode -wp10 off.bin
Ver: 1.31
Com Port: 10
Baud Rate: 10400
Opening COM10 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Writing EEPROM ......OK
Closing COM10

It says it wrote to EEPROM, no errors.
But when I do a read and print to file or to the screen to verify, there are bytes in the last several lines of the file that DID NOT GET CHANGED in the EEPROM.
It seems that all 512 bytes in my file not writing to all 512 bytes in the EEPROM.  Am I doing something wrong?

Here is the file I'm trying to write to the EEPROM.

Struggling hard here...
Get the same result whether im using a VM machine with WinXP  and a amazon kkl cable or win10 using a ross tech hex can1 with vcp drivers to create a com port. tried all the eproms, except one, keep getting "argument --in" message on eepromtool-0.4.

anyways, here's my script. any help would be immensely appreciated, been struggling for 3 weeks trying to get my skc code on my 2008 audi a4

C:\Users\Misha>C:\Users\Misha\Desktop\ME7EEPROM.exe --OBD -r -p 1 audi.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM1

Hi, bootmode worked for me, try --bootmode instead of --obd and short bootpin on power on