NefMoto

Noob Zone => Noob Questions => Topic started by: ralfi2000x on January 22, 2019, 06:01:26 PM



Title: Death code in EEPROM ME7.5 06A906032MJ
Post by: ralfi2000x on January 22, 2019, 06:01:26 PM
Hi,
I need help with ME7.5. It had stage1 tune, then some tuner made me pop and bangs (Launch Control too) and then it started. The car dies after 20km or few warmups after flash and p0601.
Now I have from that guy new eeprom with disabled checksum as he said,
second thing that I made stage1 again on ori file, because he had suspicious, that file is bad. Now I think that problem is with pop and bangs, because on ori file everything works fine.
Can You help me please? I wroted maybe 10 times new repaired maps and eeproms from him and still problem. 
My client want to cut my balls...
Checksums with winols fails


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: fredrik_a on January 22, 2019, 10:25:48 PM
So basically, what you are saying is that you took money from a customer and flashed his car with a file that have no idea whether it works or not, and now the conclusion is that there is probably something wrong with the file and you want someone on the forum to fix that for you?


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: nyet on January 22, 2019, 11:54:04 PM
Checksums with winols fails

Why not fix the checksums then?


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: Kompiesto on January 23, 2019, 12:51:14 AM
Use efiso checksum corrector. Maybe variables for LC are in wrong areas or use wrong ram loc for temp data. I had one situation after flash good file car works fine on dyno 2-3min and after that, car die. I reflashed the same file in bootmode and car work fine.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: ralfi2000x on January 23, 2019, 02:43:35 AM
No, basically the car had stage , I took clients car, I paid for file service some guy for add LC, car went okay, but after some days died, and now I figured out, that file service don't know what to do...
Yes I took money from customer, but basically my lessons now cost me much more than I took... lol

So basically, what you are saying is that you took money from a customer and flashed his car with a file that have no idea whether it works or not, and now the conclusion is that there is probably something wrong with the file and you want someone on the forum to fix that for you?

I tried my own to fix with me7 corrector, but when I give file, there is error of bad location of file. I tried on 2 systems, and just didnt work.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: nyet on January 23, 2019, 02:56:24 AM
I tried my own to fix with me7 corrector, but when I give file, there is error of bad location of file. I tried on 2 systems, and just didnt work.

Copy/paste the output of what you tried. Please do not post screen shots.

If you are taking money from people, you should at least go through the trouble of learning how to run command line programs.

Quote
My client want to cut my balls...

considering your laziness, I don't blame him.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: ralfi2000x on January 23, 2019, 05:46:39 AM
Yes I tried to do checksums with winols, and it said that it's ok.
Car still dies,
Me7chk  in command line (Yes I know it and use it) shows that this file is OK, Now I know where is problem with It, I downloaded chkcorrektor without Me7sum.
Okay I repaired Chksums with ME7sum, but will It work, and wont set death code for EEprom, I will see today.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: adam- on January 23, 2019, 05:53:48 AM
You need to remove deathcode from EEPROM.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: ralfi2000x on January 23, 2019, 07:39:12 AM
Yes, in Eprom I got this, and I changed death cote to zero

FF   20   20   20   20   5A   FF   07   09   32   31   30   33   30   33   5A
05   01   04   00   01   00   00   00   00   00   00   00   33   00   C1   FF
05   01   04   00   01   00   00   00   00   00   00   00   33   00   C0   FF
04   01   A0   0B   60   B2   4C   89   C4   AC   B9   00   01   00   3C   FB
04   01   A0   0B   60   B2   4C   89   C4   AC   B9   00   01   00   3B   FB
07   02   66   02   D1   01   FE   FF   2A   04   6D   0C   07   00   0D   FC
00   00   A5   0D   3B   0E   00   00   47   03   00   00   00   00   B5   FE
05   04   01   30   31   00   00   05   00   00   F6   2C   00   00   67   FE
05   04   01   30   31   00   00   05   00   00   F6   2C   00   00   67   FE
00   80   80   80   80   00   00   80   00   80   80   FF   00   00   78   FB
00   80   80   80   80   00   00   80   00   80   80   FF   00   00   78   FB
05   07   00   00   20   56   53   53   5A   5A   01   00   00   00   18   FE
05   07   00   00   20   56   53   53   5A   5A   01   00   00   00   18   FE
5A   31   4D   5A   33   52   31   33   30   35   34   30   53   01   BB   FC
5A   31   4D   5A   33   52   31   33   30   35   34   30   53   01   BB   FC
45   5A   37   5A   30   43   31   39   39   39   37   34   32   01   D4   FC
45   5A   37   5A   30   43   31   39   39   39   37   34   32   01   D4   FC
00   00   36   78   56   29   00   00   00   00   00   00   00   00   11   11

Like here,

FF   20   20   20   20   5A   FF   07   09   32   31   30   33   30   33   5A
05   01   01   00   E9   2C   00   00   00   00   8E   5A   00   D2   E1   FC
05   01   01   00   E9   2C   00   00   00   00   8E   5A   00   D2   E0   FC
04   01   A0   0B   60   B2   4C   89   C4   AC   B9   00   01   00   3C   FB
04   01   A0   0B   60   B2   4C   89   C4   AC   B9   00   01   00   3B   FB
07   02   98   02   D8   01   FD   FF   28   04   03   10   07   00   3D   FC
[/size][/size][/size]
But It Didn't help. I will see if the file with me7sum will work.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: Risky on January 23, 2019, 08:01:46 AM
Zero the death code in bin. Use 95040sum to checksum.


Title: Re: Death code in EEPROM ME7.5 06A906032MJ
Post by: dilly on January 24, 2019, 04:28:09 PM
May have missed it in text as I am on mobile but isn’t this the common problem with using the nls/al script? Easy but the wrong type of fix is ecufix?
You should be shunned for bragging about taking money for flashing a file that is unknown to you then paying for a script that you could have done for free.
Sharing files is one thing but charging for it? Come on man.
This forum is for diy learning. As I have learned a metric ton of info maybe you should sit down for a few hours or months and read.