Notices
ECU Flash

Immobilizer not correct

Thread Tools
 
Search this Thread
 
Old Jul 7, 2006 | 09:52 PM
  #1  
TTP Engineering's Avatar
Thread Starter
Account Disabled
iTrader: (465)
 
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
Immobilizer not correct

Somehow the Immobilizer code function of ECUFlash is not correct. For example I have read 8801 in ECUFlash and 0031 in EcuTeK.

Any time I have changed the immobilizer in EcuTeK, it has successfully worked.

Something is definately not correct in ECUFlash.

204A for example as pulled from EcuTeK when input into ECUFlash, it changes it to 888D. WTF? So when I program it as the forced input and read it again through EcuTeK, it reads 888D as 11B1.

Calling the big dogs to help me figure this one out.

MalibuJack? Colby? Anyone?

I'm at a loss here.
Reply
Old Jul 7, 2006 | 10:05 PM
  #2  
DynoFlash's Avatar
Account Disabled
iTrader: (91)
 
Joined: Sep 2003
Posts: 16,850
Likes: 0
From: 2003 Evo VIII - Silver
Originally Posted by TTP Engineering
Somehow the Immobilizer code function of ECUFlash is not correct. For example I have read 8801 in ECUFlash and 0031 in EcuTeK.

Any time I have changed the immobilizer in EcuTeK, it has successfully worked.

Something is definately not correct in ECUFlash.

204A for example as pulled from EcuTeK when input into ECUFlash, it changes it to 888D. WTF? So when I program it as the forced input and read it again through EcuTeK, it reads 888D as 11B1.

Calling the big dogs to help me figure this one out.

MalibuJack? Colby? Anyone?

I'm at a loss here.


FYI. . . . . Ecutek has encripted the imobilizer code so what ever number is reported in your Ecutek softwear is not what is in the ecu
Reply
Old Jul 7, 2006 | 10:07 PM
  #3  
Sean@Iveytune's Avatar
Former Sponsor
iTrader: (14)
 
Joined: Mar 2004
Posts: 1,849
Likes: 1
From: Linden, NJ
Originally Posted by TTP Engineering
Somehow the Immobilizer code function of ECUFlash is not correct. For example I have read 8801 in ECUFlash and 0031 in EcuTeK.

Any time I have changed the immobilizer in EcuTeK, it has successfully worked.

Something is definately not correct in ECUFlash.

204A for example as pulled from EcuTeK when input into ECUFlash, it changes it to 888D. WTF? So when I program it as the forced input and read it again through EcuTeK, it reads 888D as 11B1.

Calling the big dogs to help me figure this one out.

MalibuJack? Colby? Anyone?

I'm at a loss here.

Scott,

They masked that # a while back to combat the Techtom guys who used it to put back in the techtom.
That # isn't the correct #.

Sean
Reply
Old Jul 7, 2006 | 10:10 PM
  #4  
DynoFlash's Avatar
Account Disabled
iTrader: (91)
 
Joined: Sep 2003
Posts: 16,850
Likes: 0
From: 2003 Evo VIII - Silver
Way back in the day . . . in the stone age of flashing, trying to unlock the imobilizer code was a difficult understaking which required the flasher to develop an algorithm to determine the codce based upon the base map sum code

of course the amazing ecu flash has made all this difficult process very irrelevant
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
David Buschur
ECU Flash
29
Feb 5, 2011 04:30 PM
GetterDragun
Evo X General
14
Nov 25, 2009 06:54 AM
ez
ECU Flash
30
Apr 18, 2008 04:30 AM
Ichigo
ECU Flash
5
Aug 8, 2006 01:55 PM
AutoXer
ECU Flash
19
May 26, 2006 03:36 PM




All times are GMT -7. The time now is 03:44 AM.