NefMoto

So I decided that it would be a good idea to try and read the ECU on my '03 allroad tip. Low and behold it didnt want to start up after I finished reading the ECU file. It has a 4Z7 907 551 S ECU file on it and I have since read that a 4Z7 907 551 R might remedy this.  I found a stock 4Z7 907 551 R file on nyets' server but when running a checksum on it with MECHECK it gets an 1 error. What should I start looking into next?

Thanks

==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file bins/4Z7907551R.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 06.02
-> EPK = 42/1/ME7.1.1/5/6030.03//25A/DstU2o/200602//
-> Contents of ECUID data table:
   - '0261207769'         (SSECUHN)
   - '1037366370'         (SSECUSN)
   - '4Z7907551R  '       (VAG part number)
   - '0003'               (VAG sw number)
   - '2.7L V6/5VT    '    (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


-> No errors found. File is OK.   *********************

ME7Tool (v1.0.3) [Management tool for Bosch ME7.x firmwares]
Inspiration from Andy Whittaker's tools and information.
Written by 360trev and nyet [BSD License Open Source].

Attempting to open firmware file 'bins/4Z7907551R.bin'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '42/1/ME7.1.1/5/6030.03//25A/DstU2o/200602//'
 Part Number : '4Z7907551R  '
 Engine ID   : '2.7L V6/5VT    '
 SW Version  : '0003'
 HW Number   : '0261207769'
 SW Number   : '1037366370'

Step #2: Reading ROMSYS ..
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x004AEB CalcAdd=0x004AEB  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
 @00803c Add=0x99D4E0 CalcAdd=0x99D4E0  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01e182 Add=0x00971D CalcAdd=0x00971D  ADD OK

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @ab6a0-ab720
           Modulus: @16a94-16b14
          Exponent: @16b14 = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @16a70 [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014382-0x00017F4E
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: 8f 35 55 cf 75 03 00 0c a4 3a 2d 8a 3a 3b 65 77
 CalcMD5: 8f 35 55 cf 75 03 00 0c a4 3a 2d 8a 3a 3b 65 77
  OK

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...missing
 Searching for main data CRC/csum blocks...OK
 Searching for main data CRC offsets...missing
 Searching for main data checksum offsets...OK
 Main Checksums:
 1) 0x010002-0x013FFE CalcCSM: 001277ED
 2) 0x014382-0x017F4E CalcCSM: 0029BE45
 3) 0x018192-0x01FBDC CalcCSM: 0047A323
 4) 0x026A00-0x02FFFC CalcCSM: 00A68EF3
 @abee6 CSM: 00A68EF3 CalcCSM: 00A68EF3  Main data checksum OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @27f90 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 475476BA
    0x00FC00-0x01FFFF CalcChk: 23D54E4C CalcCRC: 04156E6A SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: A58029FE CalcChk: A58029FE 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: 0E59D5C8 Boot: (whitelisted) OK
 2) <1fbee>  0x004000-0x007FFF Chk: 1077FB35 Boot: (whitelisted) OK
 3) <1fbfe>  0x000000-0x003FFF Chk: 0E59D5C8 CalcChk: 0E59D5C8 OK
 4) <1fc0e>  0x004000-0x007FFF Chk: 1077FB35 CalcChk: 1077FB35 OK
 Multipoint #2: [66 blocks x <16> = 1056 bytes]

*** Found 70 checksums in bins/4Z7907551R.bin

*** DONE! 0 error(s) in bins/4Z7907551R.bin! ***

When I run ME7Check I get 1 error but I seem to have an older version than you. me7sum says no errors so went out to try and flash the bin, but I can no longer connect to the ecu through nefmoto. VCDS connects through OBD but not the controller module. Is this looking like I'll have to do a bench flash? I got the galleto cable in yesterday which sort of spured my ambition today.

http://nefariousmotorsports.com/forum/index.php?topic=447.0title=

Thanks I had incorrectly downloaded a previous version from the post there. I removed my ECU but am currently having issues getting it into boot mode. I'm trying to uninstall all the drivers and load new ones in any common issues with ME7.1.1 ecus that I might be overlooking here?
Thanks

Yea setzi's version numbering scheme is kinda confusing.


Yes.

Sometimes you need to lower baud rate.

Some ME7.1.1 can be tricky to get into bootmode.

They can be finicky.

Is there any benefit to grounding pin 24 with a resistor? I've seen that said a couple times.

If you slip you are less likely to kill the ecu.

I'm having the worst time trying to get the galletto cable I have to work I've tried both Windows 7 and xp now. It keeps coming up as EOBD2 under unkown devices in device manager. I have installed the ftdi drivers from the website and when I try to point windows to the directory of the drivers it tells me there are no valid drivers in there. I had it working for a bit on Windows 7 but my computer crashed and it stopped working. I am getting really confused by all this and I can't view the cable with m-prog to check the serial number.

I'm just wondering originally I flashed an incorrect bin to my ecu its was an 8bo not a 4zy bin and that's what started my communication errors. Could it be that this ecu is toast? I tried using a Ross tech cable with  nefmoto and after I think I've placed the ecu in boot mode nefmoto cannot connect. If someone could lend some input here it would be much appreciated. I'm going to grab a couple new ecus but will have to figure out this boot mode situation in order to remove the immo. Currently have a pretty big paper weight holding the driveway down.

Nefmoto cannot program in bootmode. You'll have to use galletto.

I thought so but I'm not sure if its me, my computer, or my galletto cable but I can't seem to figure out the driver install for it. Windows just says unrecognized device even after I've installed the FTDI signed drivers. The weirdest part was that the cable was recognized briefly on my system until everything crashed and it disappeared again. I think once I can figure this out I'll be in better shape.

There were instances of windows killing cloned FTDI chips. That is reportedly over, but........

Use the drivers in the "Galletto edited with proper english" sticky.

Ok I'll give that a shot when I'm home from work. Think I may stock up on some cables as well.

Check the device IDs on your ftdi cable, I had my cable 'killed' after the problem was apparently over, see my post here:
http://nefariousmotorsports.com/forum/index.php?topic=7101.msg67570#msg67570

If the device ID on your cable has been set to 0x0000 then you need to change it back to 0x6001 using linux. Then disable windows update for drivers and delete the drivers from windows: run 'pnputil -e > tmp.txt' to get a dump of all the drivers installed on your system. Grep it for 'FTDI' and do 'pnputil -f -d oem<number>.inf to delete each of them in turn, then use the drivers that daz recommended to install.

Ok I'm deffinatly going to delete all the drivers I've also got a win 7 32 bit machine to use. What are you using to edit the pid of the cable in Linux? I've got a bunch of Ubuntu disks floating around so I'll give it a check to see if windows played with it.

I followed the instructions here, running a fairly old copy of Ubuntu - have heard that newer linux drivers will also brick, but cant confirm this.

http://www.minipwner.com/index.php/unbrickftdi000

Well the cable had deffinatly been changed so I switched it all back and it started working still having a hell of a time getting into bootmode. I have 13.5 volts off a battery to run with, I've connected 12V to my cable, pin 63, and pin 21. Ground is connected to pins 1 and 2 as well as the cable. K-line is on 43. I have a switch connected to pin 3 to simulate ignition. I am grounding pin 24 with a 1k resistor and then turning on ignition while holding the pin for aprox 5 sec after flipping the switch. Each time I am getting a bootmode inactive in galletto. Is there something that is popping out as wrong here? Further is there a tuner that would could be recomended in Ontario to possibly fix this for me? If I can't figure this out after a bit more fiddling I'll have to figure out a plan b as a week without a car is enough makes commuting interesting.
Cheers

You're definitely bricked?  You cannot connect with the ecu installed?

Vcds fails to see it in car and nefmoto can't connect either even at different baud rates

Best bet may be to grab a new one off of Ebay, there's one on there now for $100/free shipping. I never was able to get this ecu into bootmode, either, although others have.

Yea picked up a new one for 150 from a local wrecker just a little apprehensive about the immo.  There's two more for 100 each so I'll probably pick one of them up to play with

In for a penny, in for a pound...  a Willem GQ-X3 or X-4 and test clip works great in situ to immo-off and no need to worry about bootmode.  Just a thought.

Is there somewhere that a write up on this is done the car is hitting the immo currently so looking for the quickest solution to remove going to do some digging tn.

Can anyone post success stories with getting me7.1.1 ecus into bootmode and anything special they did to do so?

My story:

I have been successful getting ecus into bootmode.

My method:

I ground the bootpin and power the ecu up.

But seriously, what are you hoping for? Get your drivers and hardware working properly, and it'll work as it does with every other ecu.

I already sorted out the drivers and in terms of what I am hoping for it seems that through reading on these forums as well as others me7.1.1 ecus don't go into bootmode as easily as the me7.1s. Simple things live voltage and resistors on the ground pin varying from 1k to 5k resistance have done the trick for others. The more tricks I can try the better. I just got an ic pin clamp to facilitate the grounding so I'll see how that goes with the new ecu. The original ecu might be dead as its unresponsive to vcds as well as basic obd2 pings

There is no trick needed on that ecu. Just ground the pin as you power the ecu up.

I could never get this one (to be clear, 551R running 551S software) into bootmode, either.  Tried every trick identified at the time (2012).

Did 3 today :P

No resistor, no fancy counting. Just ground it, power it up, remove the ground.

Well I'm pretty jealous of you right now haha. I got a used ECU but am as expected running into IMMO issues. Is the only way to remove the immo to use argdubs tool to flash the eeprom off? Or how is it that the s4 mbox bins do not ask for the immo data is this something that can be coded into the 551R bin as well? Think I may have to bite the bullet and call up the dealer tomorrow.
Thanks again

Send me the ecu, I will do it for you. Otherwise, just keep trying!

You'll get it.

I'll pm you. I think the added stress of no backup ecu adds to the frustrations right now

Hey all dillenger was kind enough to sort out my ECU issue for me. The car is not starting now and continues to just crank over. I checked and its pushing fuel through so that doesnt seem to be an issue. Next thing I was going to check was if its sparking. Whats the best way to check for this?
Thanks

Sorry But I just got back on here after taking a couple months break.  I have an 03 A6 ME7.1.1
 To get the car in boot mode..  USE MPPS......!!!!   end of story. Saved my life when all else failed

After DD helped me with mine. I could identify my problem as a bad clone cable. When he sent the ecu back I tried my cable to connect with nefmoto and it didnt want to. So i purchased another cable and it works perfect for everything.

Yea I've been meaning to order a MPPS cable. I used a ross-tech cable in dumb mode seems to work fine. Think what did the first one was loading the wrong bin on then a faulty boot harness. Since getting the car running on the new ECU I can't get the air suspension to work so the cars on the bump stops. I didn't think the ECU was tied to the level controller. But if anyones had experience with having the self level, ESP, and ABS lights all on and can offer soem insite much appriciated.
thanks

I don't know what I did , but I used to use vcds in dumb mode..  but now my cabe is dead and not seen by vcds

That's odd haven't had issues with the Ross-tech cable I know my galleto clone got erased so I had to reset the ftdi numbers