Immobilizer not correct
#1
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.
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.
#2
Account Disabled
iTrader: (91)
Join Date: Sep 2003
Location: 2003 Evo VIII - Silver
Posts: 16,850
Likes: 0
Received 0 Likes
on
0 Posts
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.
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
#3
Former Sponsor
iTrader: (14)
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.
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
#4
Account Disabled
iTrader: (91)
Join Date: Sep 2003
Location: 2003 Evo VIII - Silver
Posts: 16,850
Likes: 0
Received 0 Likes
on
0 Posts
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
of course the amazing ecu flash has made all this difficult process very irrelevant
Thread
Thread Starter
Forum
Replies
Last Post