Rom Id Problem--HELP
Oct 18, 2008, 12:30 PM
#1
Rom Id Problem--HELP
Hi Guys,
I am trying to read the rom on a 2006 Evo 9. The car was flashed before. Once I download the rom and look in the Rom Internal Id I see "read_evo9." I have never come across this before.
When I DL the rom I get the "unkown rom image" pop-up window. I then select the "copied from definition below" radio button and select the "2006 Mitsubishi USDM Lancer Evo (88590015)." Then I press next. I get another pop-up window "Rom Identifier." It has two slots:
Address (in hex): f52
Length (in bytes): 4
Below these two slots there is an Identifier box with a new number given for the new rom definition.
The next window is the Rom info window whcih lists the Evo model details and the new xml ID.
After that I can read the rom.
My question is the immobilizer code in the rom accurate? Is the new xml id reading what it is supposed to be reading?
I am concerned about taking the immobilizer code from this badly tuned rom and coping it into one of my base rom and then flashing the car and having it NOT start.
Please help out.
I am trying to read the rom on a 2006 Evo 9. The car was flashed before. Once I download the rom and look in the Rom Internal Id I see "read_evo9." I have never come across this before.
When I DL the rom I get the "unkown rom image" pop-up window. I then select the "copied from definition below" radio button and select the "2006 Mitsubishi USDM Lancer Evo (88590015)." Then I press next. I get another pop-up window "Rom Identifier." It has two slots:
Address (in hex): f52
Length (in bytes): 4
Below these two slots there is an Identifier box with a new number given for the new rom definition.
The next window is the Rom info window whcih lists the Evo model details and the new xml ID.
After that I can read the rom.
My question is the immobilizer code in the rom accurate? Is the new xml id reading what it is supposed to be reading?
I am concerned about taking the immobilizer code from this badly tuned rom and coping it into one of my base rom and then flashing the car and having it NOT start.
Please help out.
Oct 18, 2008, 11:01 PM
#5
96940011 is the 2005 USDM ROM ID. My guess is that this is the typical change-the-ROM-ID "copy protection" that some tuners think is a good idea. Basically, they've edited the four bytes at 0xf52, and replaced them with something completely wrong.
I suspect if you were to change those four bytes to 0x88590015, you'd be in business.
This is the same thing that happened with my own car; when I bought it the car originally and pulled the image, it was clearly an aftermarket tune, and the ROM ID had been changed to a bogus value (some 2004 ROM ID), but the rest of the ROM was still a perfectly normal 96940011 image. There were also a lot of 8s in the high-octane timing map.
I suspect if you were to change those four bytes to 0x88590015, you'd be in business.
This is the same thing that happened with my own car; when I bought it the car originally and pulled the image, it was clearly an aftermarket tune, and the ROM ID had been changed to a bogus value (some 2004 ROM ID), but the rest of the ROM was still a perfectly normal 96940011 image. There were also a lot of 8s in the high-octane timing map.
Oct 18, 2008, 11:26 PM
#6
96940011 is the 2005 USDM ROM ID. My guess is that this is the typical change-the-ROM-ID "copy protection" that some tuners think is a good idea. Basically, they've edited the four bytes at 0xf52, and replaced them with something completely wrong.
I suspect if you were to change those four bytes to 0x88590015, you'd be in business.
This is the same thing that happened with my own car; when I bought it the car originally and pulled the image, it was clearly an aftermarket tune, and the ROM ID had been changed to a bogus value (some 2004 ROM ID), but the rest of the ROM was still a perfectly normal 96940011 image. There were also a lot of 8s in the high-octane timing map.
I suspect if you were to change those four bytes to 0x88590015, you'd be in business.
This is the same thing that happened with my own car; when I bought it the car originally and pulled the image, it was clearly an aftermarket tune, and the ROM ID had been changed to a bogus value (some 2004 ROM ID), but the rest of the ROM was still a perfectly normal 96940011 image. There were also a lot of 8s in the high-octane timing map.
Now, how do I go about changing the four bytes? What should I enter in the Address slot and the Length slot?
Was the immobilizer code the same before and after you fixed the rom? I really do not care about fixing the rom. I just want to be sure that the immobilizer code is accurate. I would hate to flash the car with the immobilizer code that I DLed from the copy protected rom and have the car not start.
Trending Topics
Oct 19, 2008, 12:41 AM
#8
Evolved Member
I was trying to find a link to VXI32, and found this one.
Should be ok and free.
http://www.softcircuits.com/cygnus/fe/
Should be ok and free.
http://www.softcircuits.com/cygnus/fe/
Oct 19, 2008, 01:11 AM
#10
wow thats weird..I think the program I use is called xvi32..https://www.evolutionm.net/forums/sh...itor+scrambled
Last edited by PeteyTurbo; Oct 19, 2008 at 01:25 AM.
Thread
Thread Starter
Forum
Replies
Last Post
RngrYogi
Evo X Engine Management / Tuning Forums
7
Jul 9, 2011 07:12 AM
