NefMoto

Hello, newbie here.
Long story short, I flashed with Nefmoto software this ECU about 15 times. Everytime checksum was checked and corrected with ECM Ti. Normaly I would change maps with tuner pro and then check it with ECM. Last time I downloaded Tuner Pro plug in from MTX Electronix, so it should have corrected it I guess. ECM said checksum was fine, but the file was modified and changes not saved. Everytime I saved those changes and then flash. This time I just checked and not saved changes.
Not the worst part. I tried Galetto with two cables. Both have I what looks like fake FTDI chips, but worked fine with VCDS and Nefmoto. I did search and read many topics on this forum, but to no help. Just says "BOOTMODE INACTIVE" Tried with 2 laptops, Win 7 x64 and XP.
Any suggestions? Desolder 95040 on bottom and then try?(https://i.ibb.co/4t5PwZZ/0101viber-image-2020-07-05-11-51-52.jpg) (https://ibb.co/MS3MyDD)
(https://i.ibb.co/BZtX5cT/0102viber-image-2020-07-05-11-51-51.jpg) (https://ibb.co/850WLNP)

Sorry for the mess on pictures. Can anybody please comment on setup. Is everything connected right?

No idea.

What have you tried for bootmode?

Why not use ME7Sum to make sure your csums are correct?

I was lazy checking two times, and learned lesson the hard way.

me7check v1.12 (c) mki, 06/2004-05/2012
Checking file c:\000\T.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4018.20//24B/Dst01o/140801//
-> Contents of ECUID data table:
   - '0261207751'         (SSECUHN)
   - '1037362999'         (SSECUSN)
   - '8N0906018BH '       (VAG part number)
   - '0001'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'

Page checksum failure(s) found
Data area checksum failure(s) found
-> Found 6 errors!!!   *******************************
So checksum was wrong, and I need to go to bootmode now. Seems that it is rare for ECU to fry-brick itself for good. But for me it is a little nightmare. Is it possible that I must use galetto cable only? No FDTI chip mod

Power Pin 121.

Engine control relay. Ok, will try that. Thanks for fast reply  :)

Why are you not using ME7Sum?

If you are using the galletto tool you have to use a galletto cable or hexedit the tool.

Noo, powering pin 121 von't let ECU to get in boot mode.
Boot mode is done without powering 121 pin.

To OP, can you read eeprom in boot mode?

I did edit the cable with mprog3.5 in case of plain OBD cable. I also hex edit software in case of VCDS clone. Both of them try to connect, but Galetto sowtware says BOOTMODE INACTIVE.
me7-eeprom-1.40:
"... FAIL error =0x21007 "
Looks like OBD can't access boot mode. Is galetto cable somehow different hardware wise? I made it work with these cables. If not modded, sowtware would write "OPENING PORT IMPOSSIBLE"

Does anyone know what is power consumption of this ecu when on bench? On this setup, it is 0.285A @ 13.5V. Is this normal?
Also , chip circled red, heats a little (about 55C). Main chip Infineon heats about 48C)
(https://i.ibb.co/1RtgRGd/viber-image-2020-07-06-05-31-080202.jpg) (https://ibb.co/ygc9gFY)

describe how you are trying to get to boot mode

I connected cable as on pictures, that is ECU side: ground at pins (1,2), + is an pins (3,21,62), kline (43)
on cable side ground  (4,5), + (16), k line (7)
While powering on, ground pin 24 at mass - and after 5 seconds remove that.
Funny thing, I can see it reacts whan I ground 24, seeing powersupply adds 0,001Amp or so. Also, I see on some youtube clip that ecu from 2001 draws 0,19Amp which is less. I also remember that first time I tried it also showed 0,19 for sec or so, and then went up to current level of 0,29Amp. Maybe some component failed, but there are to clues on board like overheating or burn traces

I have about 0.2amp in normal mode, and 0.17 in boot mode. 12.00V
The main MCU and chip you point are heating as you described.
HINT: I don't put power to pin 21, that is pin get 12V tru the relay coil, I don't see any ponit to feed 12V directly to that pin.
I done many ME7 ECUs of all kind (only I never had a ME 7.1.1 on bench) and never have need to power that pin.
When I do boot mode, I only power pin 3 and pin 62,
When I flash with nefmoto i put aditional 12 V to pin 121

Yes, it seems that 0,17-0,19 is normal draw. That is what I saw first time I powered it. Then is shoot up to 0,28 and stayed there. It seems that ECU is still alive but something is in the way. Really strange not to be able to enter boot mode, or connecting to ecu in right way.
Can you tell me if I change ECU, do I have to resolde 95040 chip which as I understood, contains IMMO data for ECU to pair with cluster IMMO

Funny thing, I tried nefmoto boot mode, and it fails when normal procedure is done.
If I disconect power while it looks for bootmode it says
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Received device ID response for init zero byte.
Successfully uploaded bootstrap loader.
Failed to receive bootstrap loader started status message.
Disconnected

Can you put output log from eeprom 1.40?
Try to read eeprom in boot mode

It wont connect via OBD. Tried with ME7EEPROM.exe and ME7EEPROM.exe

Can you put log? Copy CMD output

C:\000>me7_95040 --bootmode -p 9 -b 9600 -r def.bih
Ver: 1.31
Com Port: 9
Baud Rate: 9600
Opening COM9 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM9

Procedure with pin 24 to the ground was done

Sorry to repeat question, but justo be sure:
Is there no chance that Galetto cable (from Aliexpress, ebay) would somehow be different from these FTDI bases that I have. So maybe it would work. Or some other programmer like KESS? Thank for answer in advance

Yes, you could be having cable problems if this is the only ECU you have ever tried to get into bootmode and you have never succeeded in getting any ECU in bootmode with that cable.

But that also means you might also just be doing it wrong.

I will try third cable. You can see on posted pictures in my firast post, how setup works. I don't think there is something wrong because someone would spot it

I don't think anybody can spot anything from those pics; I, for one, am not looking at them closely.

Also you didn't answer if you have gotten boot mode to work on any other ECU yet with your setup, nor the process you are using to get into bootmode (where you are getting ground from, the timing you are using)

Ground can be placed on outer trace (fat one), also tried ground from power supply etc. Ah well, I must buy another one used and compare them

And your timing?

The galletto cables should be all ftdi based, because the galleto software uses the ftdi drivers and they will not work with ch340 ( I've tried), unless it has been completely hacked or something. Unless you bought a cable advertised as galletto cable it should be ftdi, there is only one ch340 chip that stores proper serial id and I doubt it would work with galletto soft even with serial change.

Bust the cable open before you buy a new one to confirm.

I did open both of them. They have FTDI chip in them. Shallow print, so probably fake one as talked here on forums

This is what works for me on ME7.5 ecu from a 1.8 turbo:
1. Solder a 10k resistor between pin 24 and ground, and leave it connected until ecu is flashed again.
    It must be same ground as the ecu and MPPS cable is connected to.
2. connect power to the ecu, using these connections:
    pin 1 to ground.
    pin 3,21,62 to +12v.
    pin 43 to k line.
3. power up ecu, and flash it with MPPS.( i have a v13 cable, and i run it in recovery mode under speed settings).
4. disconnect power from ecu.
5. remove 10k resistor and reassemble ecu.
6. mount ecu in car and erase all fault codes.
7. done  ;)

hope this can help others, who has bricked an ecu.