Page 1 of 2
Can't read the rom 2005-STI Please help
Posted:
Tue May 23, 2006 4:33 pmby awdmonsta
I have EcuFlash v 1.27 with a cobb access port cable. It does the denso challenge but I guess the response doesn't match because I can't read the rom.
I've connected the green cable and followed the instructions. I have a USDM 2005 STI. What am I doing wrong?
Posted:
Tue May 23, 2006 5:17 pmby cboles
This has been covered many times. EcuFlash will not work with this cable. You need a OpenPort 1.2 or higher cable from tactrix.com
Posted:
Tue May 23, 2006 5:55 pmby awdmonsta
Thank you. I did a few searches but couldn't get find a straight answer.
Would a tuner's Ecutek flashing cable work? I'm going to buy the cable but I'm not sure if I can get one by tomorrow.
Do I need flash block connectors for the 05 sti? I know I have the green connectors.
I ordered the cable from your site.
Posted:
Fri May 26, 2006 4:54 pmby awdmonsta
Got the cable today. It says ssm2_init several times then says kernel get version. Then says validating denso kernel ram area address. Then the software flashes an error occured. What do I need?
2005 USDM 2.5 STI
Posted:
Fri May 26, 2006 5:17 pmby cboles
you probably haven't selected the correct COM port from Options | Ports...
Posted:
Fri May 26, 2006 5:24 pmby awdmonsta
do you have aim? I'm trying to do this right now. I've matched to com4 in both device manager and ecuflash.
my aim is awdmonsta......
Any need to change the baud rate?
Posted:
Fri May 26, 2006 5:33 pmby cboles
no aim.
no need to adjust the baud rate. do you have the green test connector plugged in? is this a stock ecu?
Posted:
Fri May 26, 2006 5:35 pmby awdmonsta
green connector connected. 05 stock ecu with dyno tuned ecutek map
Posted:
Fri May 26, 2006 5:39 pmby awdmonsta
how crutial is the timing from when you turn on the ignition and click ok? It seems like it's trying it just needs something else little. This is the furthest I've gotten.
Posted:
Fri May 26, 2006 5:48 pmby Nuked
Ecutek tunes are not readable, atleast not in the Evo's.
Jason
Posted:
Fri May 26, 2006 5:50 pmby awdmonsta
Nuked wrote:Ecutek tunes are not readable, atleast not in the Evo's.
Jason
If that's the case I'm not going to be a happy camper. That's the only reason I bought the tactrix cable because I was told it would work. Also the only reason I needed the cable because I already have a cobb access port cable.
Posted:
Fri May 26, 2006 6:33 pmby cboles
Who told you that EcuFlash would read EcuTek flashed STi ECUs? They may have changed the challenge response algorithm table or other things to render the standard initialization sequence inoperative. I would expect that you should be able to get a response to the SSM init request though...
Colby
Posted:
Fri May 26, 2006 11:19 pmby daddyhaw
ECuflas can read Eccutek Flashed Sti Ecus ( the JDm ones i am sure)
Posted:
Sat May 27, 2006 4:29 amby awdmonsta
There are other tricks to reading out uncooperative ECUs...
- you need to wire things up inside the ECU to do it though. It can't simply be done over the OBDII interface. I have heard mixed reports of reading E*ut*k'd ECUs, so I think the additional security is something that was perhaps added recently. When was your car flashed?
cboles wrote:Who told you that EcuFlash would read EcuTek flashed STi ECUs? They may have changed the challenge response algorithm table or other things to render the standard initialization sequence inoperative. I would expect that you should be able to get a response to the SSM init request though...
Colby
Calvin told me that. So you're saying I can't read them no chance at all? Damn this sucks.
Posted:
Sun May 28, 2006 8:20 amby AutoXer
awdmonsta wrote:Calvin told me that. So you're saying I can't read them no chance at all? Damn this sucks.
I'm in the same boat with my Evo and it does suck. I just want my immobilizer code out of the thing.