usually I get
FAIL (error=0x01)

with other tool that I have, I can read it fine via OBD without any issue, but this tool seems to have some bugs

first: big thx to Argdub, this tool is really great!
but i have a question:
i scanned the eeprom of a ME7.5 twice: first in OBD-Mode and a second time (1 minute later) in bootmode. and the files differ. Can anyone tell me which kind of info is stored in this area and why its different in the 2 files?
thx and kind regards

elRey: have you already tried to read it via bootmode to see whether the error still occurs?

Yes, in the "Options" screen, there is a check box for selecting "Force Dumb mode". Check this box then close VCDS. Until changed back, the cable will operate in Pass through mode, that is, it won't translate protocols or commands passed over the cable.

I could be wrong, but I'm pretty sure if the write fails the previous code will remain.
I just dealt with this the other day, I too had many difficulties writing the EEPROM to an ME7.1.1 on my 04 A6 2.7t.  I originally had a P0601 bad checksum error so I zeroed out the 33's at 1c and 2c.  I probably made 15-20 attempts, changing baud rates (in the VCP and the command line argument), and using different versions of argdub, I even tried the other 7.1.1 files posted on this thread (model specific, of course) to no avail.  Finally, I got a successful write. 
I took my original 95040 file and zeroed out the checksum errors @ 1c/2c, but this time I also removed immo AND I used the version from page 4 (http://nefariousmotorsports.com/forum/index.php?action=dlattach;topic=1168.0;attach=1931).  I'm not sure if it was the version I used, the fact that immo was removed, or if it was just dumb luck, but it wrote successfully.  The car hadn't started for days, but "lucky" for me I got it working just in time to be able to drive to the in-laws for Thanksgiving.
I'll paste my command prompt so you can see part of what I went through.  If you look at it closely you will see the different files/settings/versions I tried, but the last one is indeed successful.  As the great ddillenger told me, the later ME7s are very stubborn, so if it doesn't succeed, try try again.


c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 95040fixed.
bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 95040fixed.
bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xAA. Unknown ID. (error=0x40201)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 95040fixed.
bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xAA. Unknown ID. (error=0x40201)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b19200 --bootmode 95040 -wp4 95040fixed
.bin
ME7_EEPROM v1.40
COM: 4, Baud Rate: 19200
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b19200 --bootmode 95040 -wp4 summed.bin

ME7_EEPROM v1.40
COM: 4, Baud Rate: 19200
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b19200 --bootmode 95040 -wp4 ME7.1.1 OF
F.bin
ME7_EEPROM v1.40
Error: too many arguments specified. (error=0x10A01)

c:\Users\Public\Documents\ME7>ME7EEPROM -b19200 --bootmode 95040 -wp4 "ME7.1.1 O
FF.bin"
ME7_EEPROM v1.40
COM: 4, Baud Rate: 19200
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b57600 --bootmode 95040 -wp4 summed.bin

ME7_EEPROM v1.40
COM: 4, Baud Rate: 57600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xE0. Unknown ID. (error=0x40201)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b57600 --bootmode 95040 -wp4 summed.bin

ME7_EEPROM v1.40
COM: 4, Baud Rate: 57600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x20D07)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 "ME7.1.1 OF
F.bin"
ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 immosum.bin

ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... FAIL ... No ECU response. (error=0x20F07)
Closing COM4

c:\Users\Public\Documents\ME7>ME7EEPROM -b9600 --bootmode 95040 -wp4 immosum.bin

ME7_EEPROM v1.40
COM: 4, Baud Rate: 9600
Memory type: 95040, size: 512
Opening COM4 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM4

c:\Users\Public\Documents\ME7>ME7_95040 -b9600 --bootmode 95040 -wp4 immosum.bin

Error: unrecognised option `--bootmode'. (error=0x01)

c:\Users\Public\Documents\ME7>me7_95040 -w -b 9600 -p4 immosum.bin
Opening COM4 ... 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 ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00FF ... Expected 0xF0 or 0xF2. (error=0x00)
Closing COM4

c:\Users\Public\Documents\ME7>me7 -w -b 9600 -p4 immosum.bin
Ver: 1.31
Error: 'OBD' or 'bootmode' option not specified. (error=0x01)

c:\Users\Public\Documents\ME7>me7 --bootmode -w -b 9600 -p4 immosum.bin
Ver: 1.31
Com Port: 4
Baud Rate: 9600
Opening COM4 ... 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 ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Writing EEPROM ................................ OK
Verifying EEPROM write ... OK
Closing COM4

c:\Users\Public\Documents\ME7>

Tried this tool today(V1.31) over OBD on my Euro S4(G-box) and it worked right on first try

many thanks

What ecu are you running?

This worked the first time both ways on my 2004 Allroad BEL ME7.1.1
All of this while in the car. Read through OBD my stock ECU and then bootmode the spare one that I couldn't match with VCDS although I had all PIN #s...
The bootmode worked the first time around, even on the moody 7.1.1 to my surprise.  I was ready for it though with the little tool I made and described below changed to a 5k resistor and removing the cluster fuse (#15 on the C5).

I wanted to give some guidance as to how to get into bootmode while in the car AND not requiring help from someone else:
I bought a few things at RadioShark and I also pictured the receipt so you can get just show up at the store and ask for the same reference #s.

I used some cable from a charger. You need 2 cables, long enough to go from the battery to the inside of the car (4 to 5 feet), the other one long enough to go from the inside back to the ECU location (2 to 3 feet).
On one end of long cable, I stripped for connection to the battery. About of 1/2 inch of visible copper should be good. The other end of the long cable connect (welded for me) to one side of the switch. Top side on picture below:

The other cable will have this perfect croc pliers small enough to pinch PIN 24 without touching the other pins on one end:

on the other end, a 1K resistor (I had to go to 5k to work with the 7.1.1 so I ended up welding the 5 1k resistors in the Radioshark package in series, no picture) and then the resistor to the other side of the switch as seen above on the bottom side. Tested the whole thing, pretty good at 982 ohms on and infinite off. Perfect!
Switch ON

Switch OFF


More pictures of the in situ action:
pin side :

It looks like it could on this picture but the neighbor PINs are not touched by the pliers:

Battery side:


Finally, the switch getting inside the car:


Got into boot mode right away once I had the 5k resistance and defused the cluster. You have to turn the switch on before you turn the ignition and wait for about 3-5 seconds. I did all this on the battery no charger but all accessories off, because the 7.1.1 is so picky and doesn't like voltage above 12.5v...
No more excuses. Might have to relocate this post somewhere else Tony....