Pages: [1]
Author Topic: if I edit the 95040, vin & immo ID: XXXXXXXXXXXXXXXXXX  (Read 10080 times)
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140


« on: March 06, 2013, 12:55:26 PM »

I can flash Keith’s passat 95040 to an unrelated VW Golf bin, and when I boot the ECM, The extra fields (of VCDS or VAG K+Commander) show the VIN and Immo ID defined in the 95040 (as they should).

As soon as I alter the VIN and IMMO ID and correct the checksums, when I reboot the ECM, both the VIN and IMMO-ID are xx-ed out.

The ECM (on the bench) doesn’t seem to care that the 95040 doesn’t match the ECM, but altering the VIN ans/or IMMO seems to trip an alarm? Is this where PRJ would tell me to disassemble the code to figure out how the ECM calls on that data? Am I missing something obvious?
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: March 06, 2013, 02:19:23 PM »

lol.

He had issues with that always being x'd out after adaptation. Just use one of my off bins posted in the eeprom dumps section of the cluster/immobilizer boards.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140


« Reply #2 on: March 06, 2013, 03:11:14 PM »

aw, I'm sure any of your off bins would work (I have several), but I was hoping for the keys to making everything look super legit...

I'll first take the time to see if this franken-ecu-experiment will even work, but I haven't given up on the legit factor just yet  -even if it is WAY over my head.
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #3 on: March 06, 2013, 03:25:46 PM »

Use one of my bins and turn the immo back on-it's just 2 bytes.

What year/ecu do you have? I'll upload an on bin for you with all your details (vin, immo-id, skc) in it. Just shoot me a PM.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140


« Reply #4 on: March 06, 2013, 03:44:21 PM »

(skeptic face) it's just two bytes. exactly. 32 and 33, then correct the sums -I'm comfy with that part...

it's the adaptation part and the xxxxx's after putting my own info in that I couldn't get straight, but... okay, fluck-it, I'll PM you the 95040.bin that I tried to make good. It'll have the vin, immo and skc in it.

thanks DD (shaking my head)

Logged
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140


« Reply #5 on: March 07, 2013, 12:16:15 PM »

to close the loop:

It seems that I was trying to modify a shifty 95040 to begin with.  I do see that you (DD) modified the same 95040.bin that you supplied in your immo-tutorial (05557), so I'll be saving THAT as my base template for IMMO III from here on, thanks again.
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #6 on: March 07, 2013, 12:18:57 PM »

I like that bin, I've used it more times than I can count.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655


« Reply #7 on: March 07, 2013, 12:19:10 PM »

why do you need a base file? i dont understand why people dont just modify the original eeprom. using a non-original file should be an absolute last resort.
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #8 on: March 07, 2013, 12:26:06 PM »

I use it when I need to put an immobilizer equipped flash on an ecu that didn't already have any immobilizer data in the 95040. That's the reason I uploaded it, but I'm sure there are other circumstances that necessitate its use.

Also, another (potentially significant) effect of using someone else's 95040 are the adaptations. As the 95040 stores adaptations if the file you start with has been lemmi'd or otherwise altered you're in for a tuning nightmare. Just make sure to reset all adaptations prior to tuning.
« Last Edit: March 07, 2013, 12:28:05 PM by ddillenger » Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140


« Reply #9 on: March 07, 2013, 12:26:11 PM »

kompresd, I agree that the easiest and safest thing to do is modify your own 95040, and that is what I have done up to this point.  

I am now experimenting with switching to an immoIII bin, which uses immo-info that my 95040.bin does not contain.  I simply don't have an "original" 95040 to work from, which is why I'm trying to create something from nothing.

early 2000 2001 vw's were immo II, and then 2001 to 2002 they switched to immo III for the exact same engine (vr6 12v AFP).

the switch is apparent by comparing the vcds scans for 021906018M to 021906018T.  The T-scans will show vin and immo-id in the extra fields, whereas the M-scans will not.
« Last Edit: March 07, 2013, 12:33:39 PM by cyril279 » Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.017 seconds with 18 queries. (Pretty URLs adds 0s, 0q)