NefMoto

Hi, hope some can help here!?

My car is a 2000 B5 A4 Quattro with 2.7T engine swop. The ECU I had in car for a while (4B0907551G, from a 2.7T A6 I think - got it from a scrap yard) I flashed numerous times (M-box files and K-box files) - more than 60 times using OBD in-car flashing, with Ross-Tech USB-HEX cable in dumb mode, NefMoto flash tool, and a battery charger hooked up. I have never with all the times I have flashed this way, had any problems. Btw I have tried flashing boot-mode at some point some time ago but never got it right, not once, so I just continued my own way that has worked for so long without fail.

Yesterday I tried a new file - only changed CWMDAPP to 8 and some changes to KFLDRAPP, from an existing working file, and flashed the (my) normal way. After NM Flasher reported 100% success, I exited NM tool, cycled the ignition and started VCDS to check a few things out - only problem was that VCDS couldn't see the ECU. I cycled the ignition a few more times and even disconnected the battery, still no success. Obviously with the battery connected the car just cranked but it just wouldn't start. I also tried connecting to the ECU with the NM Flasher - still no success.

The only other change to my system was that I upgraded my PC from Windows 7 to 10 - this resulted in a new HW ID and after a few emails exchanged with MTX I realized I needed  new ME7 plug-ins and license key (which are free now, btw). I got TunerPro to work again and the CSs seemed OK! Any ideas??

Herewith the latest file I flashed (yesterday)..

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\luke skyline>CD DESKTOP

C:\Users\luke skyline\Desktop>CD ME7SUM



Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '40/1/ME7.1/5/6024.02//23g/DstW1o/051000//'
 Part Number : '8D0907551K  '
 Engine ID   : '2.7l V6/5VT     '
 SW Version  : '0001'
 HW Number   : '0261207001'
 SW Number   : '1037360387'

Step #2: Reading ROMSYS ..
 ** ERROR! First word is zero... corrupted bin? **
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x008611 CalcAdd=0x008611  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
 @00803c Add=0x9FDB80 CalcAdd=0x9FDB80  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01bef8 Add=0x00971D CalcAdd=0x00971D  ADD OK

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...missing
 Searching for RSA offset #1...missing

Step #4: Finding CRC table(s) ..
 Searching for CRC table(s)...OK
 CRC table(s) OK

Step #5: Reading Main Data Checksums ..
 Searching for main data CRC pre block...OK
 Searching for main data CRC/csum blocks...OK
 Searching for main data CRC offsets...OK
 Searching for main data checksum offsets...missing
 Main CRCs:
 0) 0x0183E9-0x0183F2                      CalcCRC: F9A70C59
 1) 0x010002-0x013FFE @90000 CRC: C7B29A7B CalcCRC: C7B29A7B(r) CRC OK
 2) 0x014252-0x017F4E @90006 CRC: 89F24A80 CalcCRC: 89F24A80(r) CRC OK
 3) 0x018192-0x01FBDC                      CalcCRC: 18E8BCB6(r)
 4) 0x026A00-0x02FFFC @9000c CRC: D941FAC2 CalcCRC: D941FAC2(r) CRC OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @1f348 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 4669A054
    0x00FC00-0x01FFFF CalcChk: 25DF3FF8 CalcCRC: B556860C SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: 534C03DD CalcChk: 534C03DD OK (i)

Step #7: Reading Multipoint Checksum Blocks ..
 Searching for multipoint block descriptor #1...missing
 Searching for multipoint block descriptor #2...OK
 1) <1fbde>  0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK
 2) <1fbee>  0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK
 3) <1fbfe>  0x000000-0x003FFF Chk: 0F8B0B41 CalcChk: 0F8B0B41 OK
 4) <1fc0e>  0x004000-0x007FFF Chk: 0ECB545D CalcChk: 0ECB545D OK
 Multipoint #2: [66 blocks x <16> = 1056 bytes]

*** Found 71 checksums in 8844.BIN

*** ABORTING! 1 uncorrectable error(s) in 8844.BIN! ***

C:\Users\luke skyline\Desktop\me7sum>

The same info in short format: you messed up and zeroed first 2 bytes in your binary. Time for boot-flashing.

EDIT: make it a good habit to run the bin through me7check prior to flashing to avoid this in the future.

This isn't the first time I've seen this... I'm wondering what program or process is causing this to happen? TP? MTX?

Hi thanks for your help - BUT I have no clue what is going on - I usually do the CS test after every modification using EasyChecksum an dI have checked it now again, and it passes...? ???

me7check won't always detect the zeroed bytes.

Ok I didn't know that...!?

So there is a better program to use?

After a successful CS check, I would transfer the file via USB stick to a laptop and then flash it onto the car - I'm going to check the file on the laptop now also...

File on the USB stick and on the laptop passes the CS test using me7check...

me7sum will detect the zeroed bytes.

I wish I could say how that happened! :o

B.t.w my numerous attempts at boot flashing all failed... :(

Restore the first two bytes to stock


You'll want to have a properly working boot mode flashing set up before you do any flashing so you have a fall back in case something bad happens.

Thanks - I suppose it is available somewhere here? I'll start searching in the meantime...

Yip - thanks, will do...

I realize that, but like I said, somehow I just never got it to work - time to get to know some people!

I have a spare ECU (T-box) onto which I flashed an old M-Box tune - it needs some work but at least I'm mobile...

Thanks again!

uh. my sig?
the s4wiki lists it?

Hi Nyet, the other times you refer to where you have seen this, is it always the first two bytes that goes zero?

Yep. Inexplicable.

I think it has to do with MTX or TP though.

At least then another method of checking (double check / tripple check??) would be to look at the first two bytes using a hex editor  ;)
Btw I found Me7sum...