2014 RA ECUflash XML file
Dec 25, 2017, 05:19 AM
#1
Newbie
Thread Starter
2014 RA ECUflash XML file
So I just went through the effort to reflash with the GST basemap. I've got a 2014 RA and my ROM ID is actually 59570005. However, the only ROM definitions available are for 59570004. I imported the cars ROM but ECUflash wasn't able to read it. I haven't really seen people post about having that issue even with the newer RAs.
So what I did to be able to read the ROM was to edit the definition file. I changed the name of the file from 59570004 to 59570005. Then I edited the actual file. Within the first few lines of code, you can see the ROM ID twice. I changed that value as well from "59570004" to "59570005". After that, I was able to read and write to the ECU.
would doing it this way cause the logging issues I'm having?
So what I did to be able to read the ROM was to edit the definition file. I changed the name of the file from 59570004 to 59570005. Then I edited the actual file. Within the first few lines of code, you can see the ROM ID twice. I changed that value as well from "59570004" to "59570005". After that, I was able to read and write to the ECU.
would doing it this way cause the logging issues I'm having?
Last edited by Kaitos; Dec 25, 2017 at 05:27 AM. Reason: I wasn't finished.
Jan 1, 2018, 06:24 PM
#2
What logging issues are you having?
what you did does not sound like a good idea...THERE is a reason the ids were different. Sometimes you can update the rom but you really need to know what's going on to do that..tgats where folks like razorlab, golden, and tephra come in
what you did does not sound like a good idea...THERE is a reason the ids were different. Sometimes you can update the rom but you really need to know what's going on to do that..tgats where folks like razorlab, golden, and tephra come in
Jan 1, 2018, 06:35 PM
#3
Newbie
Thread Starter
What logging issues are you having?
what you did does not sound like a good idea...THERE is a reason the ids were different. Sometimes you can update the rom but you really need to know what's going on to do that..tgats where folks like razorlab, golden, and tephra come in
what you did does not sound like a good idea...THERE is a reason the ids were different. Sometimes you can update the rom but you really need to know what's going on to do that..tgats where folks like razorlab, golden, and tephra come in
The following users liked this post:
RalliBastar (Oct 7, 2020)
Oct 6, 2020, 06:23 PM
#4
well I'm not having any logging issues anymore (Was having some non-related logging issues before/after reflash due to not using the right ECU) The IDs are different because the year of car is different. The 04 number is for the '13 model and there are no available definition files for '14 and '15. With my ID being 05 instead, the 04 file will not let ecuflash read my ROM. Everybody on here says that the 04 file should work for the '14, which should mean that all I have to do is make ecuflash recognize my ROM by changing what it "looks for" from the '13s ROM to a '14s ROM.
You must manipulate the .xml in notepad and change the <xmlid>59570004</xmlid> to <xmlid>59570005</xmlid> on line one within the <romid>
Also change line 3 <internalidhex>59570004</internalidhex> to <internalidhex>59570005</internalidhex>
Also change the 9th line <year>2013>/year> to <year>2014>/year>
Save the file as an .xml in C/programfiles/x86/OpenECU/EcuFlash/Rommetadata/mitusbishi/evo
close ECUFlash and reopen. You should now be able to read your stock .rom for this model and year using ECUflash
when you read from ecu memory the ROM should open without asking you to use the wizard.
Hope this helps someone.
Thread
Thread Starter
Forum
Replies
Last Post