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?
Can't read the rom 2005-STI Please help
24 posts
• Page 1 of 2 • 1, 2
Can't read the rom 2005-STI Please help
by awdmonsta » Tue May 23, 2006 4:33 pm
- awdmonsta
- Posts: 8
- Joined: Tue May 23, 2006 4:26 pm
by awdmonsta » Tue May 23, 2006 5:55 pm
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.
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.
- awdmonsta
- Posts: 8
- Joined: Tue May 23, 2006 4:26 pm
by awdmonsta » Fri May 26, 2006 4:54 pm
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
2005 USDM 2.5 STI
- awdmonsta
- Posts: 8
- Joined: Tue May 23, 2006 4:26 pm
by awdmonsta » Fri May 26, 2006 5:50 pm
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.
- awdmonsta
- Posts: 8
- Joined: Tue May 23, 2006 4:26 pm
by cboles » Fri May 26, 2006 6:33 pm
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
Colby
- cboles
- Site Admin
- Posts: 1233
- Joined: Wed Dec 29, 2004 5:45 pm
- Location: Seattle, WA
by awdmonsta » Sat May 27, 2006 4:29 am
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?
Calvin told me that. So you're saying I can't read them no chance at all? Damn this sucks.
- 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.
- awdmonsta
- Posts: 8
- Joined: Tue May 23, 2006 4:26 pm
24 posts
• Page 1 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 0 guests