ECUFLASH EVO 8 ROM Definition Error

I just recently purchased a non running evo 8, that needed new fuel injectors, the injectors have been replaced and now I need to scale them properly. The previous owner used ECU Flash to tune with I think... (The car came with a v1.3 tactrix cable). When trying to launch ECU Flash it will read the ECU information then pop up a window stating the program could not recognize the ROM image using any of the current definitions and gives me 3 options.

1. Abort using ROM

2. Continue using this ROM with no definition (no editing or viewing, but saveable)

3. Use wizard to create a new definition (Not recommended!!!- For developers only)

I've looked at an original hex data from an untouched stock evo 8 ROM vs the one that I was able to extract from the car. The raw data looks completely different on many of the data lines and the 0000f50 data blocks are vastly different (what my research has told me that is where the ROM ID's are located.) I have added the tephra v7 xml patches to the list and still having the same result. I have Uninstalled the program and reinstalled with the tephra v7 patches added still the same result. I have not had any luck reaching out to tactrix on this matter and am hoping someone can shed some light on what I'm missing as this vehicle is set up with a fair bit of aftermarket goodies and running on speed density and would be nice to be able to pick up where it was last left since the car ran good with the stock sized injectors previously. I'm not sure if I should post up the hex file here or what direction I should take this. Thanks in advance I'm still a newbie so please any info is greatly appreciated.

Double click your rom, it will open with ECUflash, but you will get an error that says "Unknown Rom Image". Instead of selecting "abort using this rom image", select "Use wizard to create a new definition", then click "Next"It will give you 3 options to choose from, select "Inherited from definition below", then in the pull down menu, select a definition that closely matches what may be on the car, then click "Next".In the next screen that comes up, there will be a box on the bottom half that says "Identifier". Inside that box will be your rom ID.

this works most of the time with the Xs. I cannot recall specifically, but I believe f52 block in the hex code should be the rom I’d.

it may not make sense as the tuner could have changed it to something random. You will need to return it to what it should be in order to read it properly.

Can you upload your hex file here?

Thanks for the responses! Here is the file packet that came from the ECU read. I tried the above suggestion and was unsuccessful. The dropdown menus did not have any suggestions and when I tried to just click next to see what would happen ECU FLASH would just close the program. I don't know if this is relevant but I have heard of people changing a small sample of data in the hex to prevent others from tampering with their custom maps but I don't even know where to start to look for something like that or if it's just me going down the wrong rabbit hole. Again I really appreciate all the info and help and cannot wait to be able to post and share our findings with others so that if someone else is experiencing this that we can make a sort of road map to guide noobs like me down the right path.

This is not hex file...you need to get the hex file. Try to read Evo tuning guide by Merlin first...

Oops I forgot to say this is the raw data scan that came out of the ecu. I had to plug this into the HxD converter that I have. Thanks for the tip about Merlins guide I have been reading it over and over for the past few weeks to see if there is any info I missed but it seems I cannot find anything new. I also pulled an untouched hex file from evo ecu wiki to compare against. The issue that I am stuck on is I cannot even get to the stage of reading the immobilizer data or pull up maps to get to the hex file. Nothing pulls up on the lower section where the maps normally would be except an empty rom data info tab. Again thank you so much for taking the time to respond and having a look at my info! Living on a tiny island with 0 tuner shops get good info from this is truly a lifeline!

Try another version of Ecuflash, older one...

Good afternoon, I have a 2003 Evo 8 USDM with the rom ID 96940013 i am trying to find my immobilizer code so i can reflash it with tephramod v7.

when i read my ecu and go to view the maps they are all greyed out and when i click on them i get

"The current MAP description is invalid or incomplete. Please editthe map description to fix the proplem and the map will be viewable again"

Does anyone know where i can get the popper definition files for me to view everything in my rom image?

thanks in advance

Hi. Did you read this topic ( maybe it can help to solve the issue)?

https://www.evolutionm.net/forums/ecu-flash/434280-rom-version-96940013-a.html

Yes I did, also posted there, haven’t found anything to help view the tables or find my immobilizer code

Can you send me your rom file? georg1970@bk.ru

Just sent you an email. Thanks for the help

Just sent you an email. Thanks for the help

Got it. Will get back to you soon.

What version of Ecuflash are you using? It works just fine with 1.44 version.

You need to open xml file and remove the number after "evo7base" and you should be fine. A have attached two pics before and after.

So I am in a similar boat. I also have a failing ECU, so I have pulled the ROM file and I am running into the same lack of definition. I have purchased a Link G4X to replace it. With the MIVEC needing to have a dyno for proper tuning, it was suggested on another thread from HP Academy that I copy the current numbers over. I have purchased a different ECU from Iceland for a housing for the Link ECU, and checked it. It is a USDM ECU and has an internal ID that I can read. But when I looked at it through an HEX converter as suggested above, there isn't a F52 line that I can find. There is a 00000F50 line. I will attach snipits from the Iceland ECU so you can tell me Im a moron and looking in the wrong spot. I am also new to this. I will also attach my actual ecu ROM to if you would like. I would like to understand what I am looking at. Im running ECUFLASH 1.44. I am able to read my tune from back in 2017 before all of the current MODS using it and all of the definition bin files that come from tephra v7 files.

I cant attach SRF files and the Hex converter is only letting me save it as a excel file. I am using parallels.

Have you tried older version of ECU flash?

No

I see that You have suggested that before. What does that do? Wouldn't an updated version be able to read what the previous version would of been able to do?

Not all the new versions of ECU flash work properly with Evo. Older version like 1.3 work way better

so delete 1.44 and try locating and using 1.3?

You can have both but installed in different directory and run from there. Or you can delete 1.4 and install 1.3 instead...

Ok i will give that a try. Did you look at the hex file? Was I looking at the right location?