Can't read 03 evo?
#1
Newbie
Thread Starter
iTrader: (11)
Join Date: Oct 2007
Location: Charlotte NC
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Can't read 03 evo?
Guys I have a tetrix 2.0 cable and im trying to read the rom on an 03 evo using ecuflash. It makes 3 attempts but get no responce. Strange thing is I can log the car fine with evoscan. I know my cable is good as I can read anouther 03 and an 06 fine. What am I missing? Any help I would appreciate. Thanks.
#2
Evolving Member
iTrader: (16)
Join Date: Sep 2006
Location: Jacksonville, FL
Posts: 143
Likes: 0
Received 0 Likes
on
0 Posts
You ecu may be locked, has it been tuned before by anyone. Tuners will sometimes change the init code inside your ecu say that the nomal ECUFLASH settings will not allow you to read your rom. The easiest way for you to do it would be to use the ECUFLASH unlocker program. and once you are in change your init code back to 0001
Trending Topics
#9
Newbie
Thread Starter
iTrader: (11)
Join Date: Oct 2007
Location: Charlotte NC
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Ok I can read and burn now but when I load the stock rom file for an 03 the car wont start. I notice the init code (highlighted in blue) and imob caint be changed either. How can I edit this sucker? Looks like whoever flashed it previously scrambled the hex.
I compressed the flash but its 118k so I caint post it.
Any ideas on what I am missing here? thanks
I compressed the flash but its 118k so I caint post it.
Any ideas on what I am missing here? thanks
#10
Evolved Member
iTrader: (5)
Ok I can read and burn now but when I load the stock rom file for an 03 the car wont start. I notice the init code (highlighted in blue) and imob caint be changed either. How can I edit this sucker? Looks like whoever flashed it previously scrambled the hex.
I compressed the flash but its 118k so I caint post it.
Any ideas on what I am missing here? thanks
I compressed the flash but its 118k so I caint post it.
Any ideas on what I am missing here? thanks
If the hex is scrambled just means the internal rom id has been messed with.
Likely the immobilizer is not correct for your car on the stock rom and its dying you can disable it in the periphery bits FAA.
#11
Newbie
Thread Starter
iTrader: (11)
Join Date: Oct 2007
Location: Charlotte NC
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Change your user level to developer or advanced in the file - options that way you can mess with those fields.
If the hex is scrambled just means the internal rom id has been messed with.
Likely the immobilizer is not correct for your car on the stock rom and its dying you can disable it in the periphery bits FAA.
If the hex is scrambled just means the internal rom id has been messed with.
Likely the immobilizer is not correct for your car on the stock rom and its dying you can disable it in the periphery bits FAA.
#12
Evolved Member
iTrader: (5)
Ok so I have a vista (x86) laptop and running the latest ecuflash (1.42) and following the wiki to add the periphery bits in notpad it will not let me save it as vista says the file dosent exsist? Witch is dumb cause how can I add code to the file if it dosent exsist? What am I missing? Thanks