can't recognize rom nor find the correct xml for evo 9 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community

Notices
EcuFlash
Sponsored by:
Sponsored by:

can't recognize rom nor find the correct xml for evo 9

Reply

 
 
 
Old Sep 12, 2018, 12:34 PM
  #1  
Newbie
Thread Starter
 
iienigmaii's Avatar
 
Join Date: Sep 2018
Location: italy
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
can't recognize rom nor find the correct xml for evo 9

Ops,
double post.
iienigmaii is offline  
Reply With Quote
Old Sep 12, 2018, 12:37 PM
  #2  
Newbie
Thread Starter
 
iienigmaii's Avatar
 
Join Date: Sep 2018
Location: italy
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
Hello,
new here and newbie to ecuflash; i'm just trying to help a friend hope you understand

So,
he's trying to open a rom given by another guy but ecuflash says "Unknow ROM image" etc etc.
As I understood it works with definitions, xml files, and I guess he doesn't have the right one.




This is the ROM infos:



He has a lot of xlm's file but anything with 88627779 ID.

He is sure that is a tephra modded rom but i can't find anything searching online for that ID.
No google results, no forums results, downloaded tephra rom definitions on his website, also from here but no file with that id.

Any clue?
may I try forcing others tephra/default xml? (is it even possible?) because i tried to modify a couple of xml, but then ecuflash crash.

He already tuned some evo 8's and 9 but always from stock rom; first time he got stuck.

any other infos that you guys need?
Thanks
iienigmaii is offline  
Reply With Quote
Old Sep 12, 2018, 12:43 PM
  #3  
Evolving Member
iTrader: (2)
 
Project_Broke's Avatar
 
Join Date: Jul 2014
Location: Indianapolis
Posts: 282
Thanked 8 Times in 7 Posts
If it's a pretuned ROM, the ID was probably changed to prevent tampering.

You can try changing the rom id to the Tephra V7 IX rom ID number and see if it breaks down. That's how I solved mine.
Project_Broke is offline  
Reply With Quote
Old Sep 12, 2018, 12:56 PM
  #4  
Newbie
Thread Starter
 
iienigmaii's Avatar
 
Join Date: Sep 2018
Location: italy
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
yeah, I thought the same thing few minutes ago, really ^_^
random ID modified by the tuner.

So you suggest to try all the tephra xml i found and manually change the ID? (or change the rom ID with and hex editor....is it at 0xF52 always?
any other alterations that could be done? for example switching whole map parts inside the file and then manually fix the adresses in the xml file? or it will end to an useless file or bricked ecu if trying to flash it?
iienigmaii is offline  
Reply With Quote
Old Sep 12, 2018, 01:49 PM
  #5  
Evolving Member
iTrader: (2)
 
Project_Broke's Avatar
 
Join Date: Jul 2014
Location: Indianapolis
Posts: 282
Thanked 8 Times in 7 Posts
I didn't need to change the ID in the actual hex file. I just needed to change it on ecuflash's side. I cannot remember specifically where I did it.

Most of the info on the forums do have you change it in a hex editor. Most of the time, I do believe its in 0xF52.

I will try and update when I get to my tuning computer.
Project_Broke is offline  
Reply With Quote
Old Sep 12, 2018, 01:49 PM
  #6  
Newbie
Thread Starter
 
iienigmaii's Avatar
 
Join Date: Sep 2018
Location: italy
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
I modified the rom ID using an hex editor at address 0xFCA trying all the tephra ID i have and only one is kind of working.
The file loaded from ecuflash is the genuine "TephraMOD-88590715-v7.xml" and of course is the one for evo IX.

BUT if i open some tables they don't make any sense.
Values on axis and inside cells are totally wrong.
I think the adresses are wrong.

So, others alterations are mode for sure i guess.....what could it be?

thank you

Originally Posted by Project_Broke View Post
I didn't need to change the ID in the actual hex file. I just needed to change it on ecuflash's side. I cannot remember specifically where I did it.

Most of the info on the forums do have you change it in a hex editor. Most of the time, I do believe its in 0xF52.

I will try and update when I get to my tuning computer.
Ok thanks

Last edited by iienigmaii; Sep 12, 2018 at 02:01 PM.
iienigmaii is offline  
Reply With Quote
Old Sep 13, 2018, 02:03 AM
  #7  
Newbie
Thread Starter
 
iienigmaii's Avatar
 
Join Date: Sep 2018
Location: italy
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
Good Morning Guys,
I think I made it

Yesterday I tried only EDM-USDM roms because the file is from an European market car so......why try totally different files?
Well, it seems to be replaced with an AUDM rom.......why :|
By the way ecuflash now loads the rom correctly and all the tables, axis values, cells values etc are good

So thank you Project.

Last thing,
when the rom is loaded I got this in the log window:
[10:53:44.280] using metadata XML ID 88580714 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/TephraMOD-88580714-v7.xml
which inherits XML ID 88580014 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/ecuflash/branches/r3compile/88580014.xml
which inherits XML ID 88580013 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/ecuflash/branches/r3compile/88580013.xml
which inherits XML ID evo9base_20081101 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/mitsubishi/evo/ecuflash/branches/r3compile/evo9base_20081101.xml
what does it mean exactly?
Does it kind of load multiple definitions from different file?

And which is the safest way to manage the file?
Changing the rom ID in the ROM file? or keep it as saved from the ecu and modify the xml instead?
iienigmaii is offline  
Reply With Quote
Old Sep 13, 2018, 04:48 AM
  #8  
Evolving Member
iTrader: (2)
 
Project_Broke's Avatar
 
Join Date: Jul 2014
Location: Indianapolis
Posts: 282
Thanked 8 Times in 7 Posts
Originally Posted by iienigmaii View Post
Good Morning Guys,
I think I made it

Yesterday I tried only EDM-USDM roms because the file is from an European market car so......why try totally different files?
Well, it seems to be replaced with an AUDM rom.......why :|
By the way ecuflash now loads the rom correctly and all the tables, axis values, cells values etc are good

So thank you Project.

Last thing,
when the rom is loaded I got this in the log window:


what does it mean exactly?
Does it kind of load multiple definitions from different file?

And which is the safest way to manage the file?
Changing the rom ID in the ROM file? or keep it as saved from the ecu and modify the xml instead?

It's just inheriting from several ROM IDs, as long as the tables display correctly, and you can flash. It's completely fine.
Project_Broke is offline  
Reply With Quote
 
 
 


Thread Tools
Search this Thread

Contact Us Archive Advertising Cookie Policy Privacy Statement Terms of Service

We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.