NefMoto

Howdy, I've been reading on this forum for quite some time now and have always been able to find an answer to my questions until now. I found three other instances where this question was asked but it seemed to be ignored. I am attempting to use the ME7EEPROM tool to delete an immobilizer, but it always stops at error=0x21007 or error=0x50001. There seems to be a random chance of either error code resulting since they will sometimes be thrown immediately after each other if the exact command is run. What might be causing this error? I'm using a dumb K-Line cable, have tried many a KKL cable, Galletto just for grins, genuine Ross-Tech, Ross-Tech clone, Chinese FTDI cable, and three other random cables I could find, yet this failure still haunts me. I've also tried different memory types, none of which resulted in a change.

Try different baud rates.  10400 seems to be the standard. 

I always had better luck with 1.31 and run the highest baud 50xxx because some cables dont seem to like the low bauds. Oh also its 95% likely it wont work in car obd.

I suppose I neglected to mention that I am doing this on a bench setup, not in the vehicle.
10400 baud is not an available option in the drop-down menu for any of my K-Line cables, however I switched to 9600 baud and received the same error code. any idea how I could get the cable to operate at 10400 if it is not a provided option?
Ill also try 1.3 at the highest baud.

Thanks for the quick response.

Tried 1.3, but I couldn't get the baud rate to change with the -b function. Am I using it correctly? I tried placing it in different places, but I'm sure the first location was correct.

Tried the highest Baud rate in 1.4 with no luck.

Do you have a software that works with it? Something like rosstech?  Even use a different module just to confirm everything  is wired correctly and you have no weird shit going on with your laptop/pc. 

I can connect to the ECU with VCDS, Galletto, and Nefmoto. There are no issues performing any actions in any of them including reading and flashing.

Worth noting:

Sometimes I need to try like 20 times before it will finally work. Some ecu's seem to like 1.31 better but sometimes 1.4 does the trick for me. Great tool, except has quite some issues and sadly is not open source.

I've tried it upwards of fifty times now with little tweaks here and there with no change except to my sanity. Anyone know of any other possible things I could try with this tool or another method to delete the immo?

Hmmm the way the 5 bit baud initialization works is by doing a bunch of break state and  rts on off.  Because rs232 devices just don’t go that low for baudrate.  So it’s “tricked” if you like.  I say rs232, but I’ll table that discussion for another day.  All of the info can be found here.  https://www.blafusel.de/obd/obd2_kw1281.html
You would really need to look at what is happening with the signal on a scope and if you can see what’s going on it’s gonna be hard to modify without source code.  It’s possible it’s doing it too fast or too slow.  You can maybe try reducing the cores on your pc.   Use a usb 2.0 port instead of usb 3.0 that might help too.  I only say that because I’ve had issues with other devices in the past with a shitty usb supposed to be backwards compatible port.

Stop wasting your time and get the ecu out on bootmode. it wont work reliably in car.

Have you tried the freely available K+CAN VAG COMMANDER?  I just mentioned it as you have not listed it. I don't like it much, but you should investigate it to see if it is compatible with your car. It can do IMMO stuff on the motor ecu

Thanks all for the suggestions and responses in general. For anyone that comes across this problem in the future, I fiddled with it for many hours and finally came to the conclusion that when this happens on only certain ECU models, you need to write the commands as you would to read in OBD, but simply replace the --OBD command with the --bootmode *memorytype* command. It may seem like an obvious simple solution, but it had me hung up for the better part of a day, and perhaps it will keep someone else from having such an issue.

This. OBDII mode is not worth your time.

me7eeprom.exe --bootmode (chip) --CSpin (Pin) -r  -p (your port) (name the file)

Done.

Your ecu can not work in obd mode, try bootmode!