neddludd

Hi all Im trying to find out why my evo5 is running at 10:1 AFR or below under boost since I purchased it.
I have tried a bunch of searching and not found any definitions for this rom ID
I have tried copying/inheriting from the closest model but doesnt result in any editable tables

Case has the RomID etched into it as if some one has identified and possibly tuned it already
I have tried capturing the rom while ecu unlocker is running,no difference

Should I just forget about whats on there and put a standard ROM/Ceddymod (which I have already downloaded/bought)

Case ID MD356472
Chips MH7202F
RomID 05092012
Ecuflash 1.44.4799
Openport Cable
Windows 10

I also have a lancer H8 ECU(MD360479 MH7204FA) I can attempt to put a generic hex I have obtained onto it eg
EM2349 - EVO5 - MD360216.hex
EM2362 - EVO5.hex

My last option is to pay for an evo 7 ecu and repin

ecuflash log
[20:09:00.396] Logging to file C:/Users/mike/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20200602t200900.txt
[20:09:00.396] EcuFlash Version 1.44.4799
[20:09:00.396] OS Version Windows 10
[20:09:00.396] Kernel Type winnt
[20:09:00.396] Kernel Version 10.0.18363
[20:09:00.396] CPU x86_64
[20:09:00.396] Product Name Windows 10
[20:09:00.396] Product Type windows
[20:09:00.396] Product Version 10
[20:09:00.396] Qt Version 5.6.0
[20:09:00.396] Qwt Version 6.1.2
[20:09:00.396] QwtPlot3D Version 0.2.6
[20:09:00.396] Boost Version 1.60
[20:09:00.396] FTDI Library Version 3.02.11
[20:09:00.396] Openport J2534 Library Version 1.02.4798
[20:09:00.397] 67 memory models read.
[20:09:00.397] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:09:18.130] 745 ROM metadata models scanned.
[20:09:18.131] checksum module "subarudbw" loaded.
[20:09:18.131] checksum module "subarudiesel" loaded.
[20:09:18.131] checksum module "subaruhitachi" loaded.
[20:09:18.131] checksum module "mitsucan" loaded.
[20:09:18.131] checksum module "mitsuh8" loaded.
[20:09:18.131] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:09:18.131] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:09:18.132] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[20:09:18.151] flashing tool "wrx02" loaded.
[20:09:18.176] flashing tool "wrx04" loaded.
[20:09:18.185] flashing tool "sti04" loaded.
[20:09:18.186] flashing tool "sti05" loaded.
[20:09:18.200] flashing tool "mitsucan" loaded.
[20:09:18.200] flashing tool "mitsukernel" loaded.
[20:09:18.200] flashing tool "mitsukernelocp" loaded.
[20:09:18.200] flashing tool "mitsubootloader" loaded.
[20:09:18.200] flashing tool "shbootmode" loaded.
[20:09:18.200] flashing tool "shaudmode" loaded.
[20:09:18.205] flashing tool "subarucan" loaded.
[20:09:18.205] flashing tool "subarucand" loaded.
[20:09:18.226] flashing tool "subarubrz" loaded.
[20:09:18.229] flashing tool "subaruhitachi" loaded.
[20:09:43.655] opening rom file C:/Users/mike/AppData/Roaming/Microsoft/Windows/Start Menu/Programs/EcuFlash/myevo5.srf
[20:09:43.666] no definition exists for this ROM file.
[20:09:43.672] 131072 byte image written.
[20:09:43.673] 0 byte image written.
[20:09:43.673] 0 byte image written.
[20:10:24.003] using metadata XML ID 05092012 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/05092012.xml
[20:10:24.016] using metadata XML ID 05092012 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/05092012.xml

rjwkerkhof

Hi There,

That ROM ID: 05092012 is unknown to I think most of us. It might be some EcuTek modified ROM perhaps.. What I have done is loaded your ROM in to a hex editor and modified the ROMID to the stock ROM ID of an E5 JDM to make it somehow readable. Looking at EcuFlash there are some shifts in table addresses but some seem to be correct. I have added the hex_dump to this reply for your interest.

Edit: Next to the above I have changed your ROMID to the CeddyROM ID and that gives me a perfect ROM so it must be a CeddyROM which is possibly sort of locked by the tuner by changing the ROMID, again I have added the file to this post. Good Luck!

neddludd

Thanks alot that makes alot of sense I will test this out! I attempted research but couldnt find exactly how to hexedit as you say, I found many dead links to romid search sites/downloads.

I appear to have bricked my H8 lancer ecu with my last attempt, test write fails so lets forget about that one. I probably forgot to change the XML memory field to "7203FA"
I have found another E5 ecu for $125 so that can be my backup

rjwkerkhof

That shouldnt brick the ECU from my experience, change the Memmodel to the correct one and try again

neddludd

Hi it appears I cannot read any ECU anymore, like when I first tried and battery voltage was too low.
I have started the car for 3minutes, and now have a battery charger continuosly connected - still init sequence 2, interface closed error
This occurs on my 7202F boards , one is for changing to stock/ceddymods the other is for backup

If you wanted to teamview to my computer I could paypal you some cash
I will install windows 7 or 8 and compare[13:50:23.304] using metadata XML ID 22580006 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/22580006 1998 JDM Lancer Evo 5 GSR.xml

which inherits XML ID evo5base from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/evo5base.xml

[13:50:23.304] ---notes for evo5base---

2012/11/19 [Tactrix] updated to include missing elements.

---notes for 22580006---

2012/11/19 [Tactrix] Updated to standardized file naming. Removed - from "Idle Stepper Look-up".

[13:50:23.356] J2534 API Version: 04.04

[13:50:23.356] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10

[13:50:23.356] Device Firmware Version: 1.17.4877

[13:50:23.356] Device Serial Number: TActIEG5

[13:50:25.899] sending init sequence 2

[13:50:27.905] interface close

AllanL

iTrader: (20)

have you tried re-installing ecuflash?

your ecuflash timestamp really shows Nov. 19, 2012?

neddludd

yep about 5 times
I think that log line is from evo5base.xml

<rom>
<romid>
<xmlid>evo5base</xmlid>
<flashmethod>mitsukernel</flashmethod>
<memmodel>H8539F</memmodel>
</romid>

<notes>
2012/11/19 [Tactrix] updated to include missing elements.

Here is todays logs from a few minutes ago
The openport 2 is glowing, the USB cable is 6months old and used about 30 x, 25 of which were failures due to low battery voltage- will replace it incase its slightly damaged
I have tried with and without the small plug going from the flash plug into the Openport 2 case
Key is turned to ON with dashboard lights glowing
Battery charger is connected
Windows 8 was freshly installed less than 24hrs ago and only has chrome and ECUflash installed
Windows 10 has had a years use and multiple uninstall and reinstallations of ecuflash,it has ceddymod definitions in the folder
Same laptop hardware

Unfortunately its very hard to see what is wrong I will start with the cable, then check resistance to the ecu pin on some of the wires

EDIT: I have now successfully read my existing Evo5 ECU which I uploaded before. Now attempting upload/view tables
USB cable replaced, and I started the car for 2minutes
Perhaps there is a minimum voltage of say 13.6v required, and my charger was at the end of its cycle providing 12.99

AllanL

iTrader: (20)