Vin reset for used Light control module to remove tamper dot

[hungbaby]

The long story short. My Light control module (LSZ) dies on me so I bought an used one from Ebay and put it in. All is good and all the light are working now. However I got a tampered do next to the mile counter. This is due to the vin (or fg in german) stored in the module is different from the one store in the cluster module.

So now I need to write my vin (my actual vin that is stored in the cluster) on to the light control module.

So I have search and it seem WinKFP can re-flash a module and give it a new vin in the process. However I don't seem to find the correct module to flash in WinKFP. I might be that you can not flash the LSZ module in E46.

So some people suggest using Tool32 to write the value. I load Tool32 with LSZ_2.prg (my LSZ was running LSZ_2 production after 01 i think). In the job list you could see "c_fg_auftrag", which if ran with 18 digits vin argument would change the vin in the module. Now I looked at the vin and it has only 17 digits. I searched and some mentioned that you have to get the last checksum digit as well. So I tried two thing.

First I load NCSExpert and do the usual coding procedure by load Expert Mode profile, F1, F3, select E46, and select AKMB (instrument cluster module) which then load the FG (vin with checksum) and FA (vehicle order) from the module for coding. This give me a fg that look like this WBAAA00000-last 7 of my vin-4. This is not my vin but for some reason this is all that NCSExpert load out. So I tried to use this vin in the "c_fg_auftrag" job. It did not work, I got a ERROR_VERIFY job status.

So I tried the second approach. This time I tried to get NCSExpert calculate the checksum for my actual vin by doing the following in NCSExpert: load Expert, F1, F2 (Enter FA), Select E46, now a vin box appear and I can type my actual full vin in (17 digits) and check the Calculate checksum box, click ok and my FG was calculated with the check sum is K. I used this in Tool32 again but the same job status: ERROR_VERIFY.

So I tried to write FG using NCSExpert to see if it is possiple. I load Expert Mode, F1, F3, select e46, select AKMB, back, Process ECU, select ALSZ, change Job to FGNR_SCHREIBEN (which is FG write), and I got the same error: ERROR_VERIFY.

Now I don't know if this error mean that the Vin is not correct (the system could not verify it using checksum) or something that I miss. I tried to search but nothing shown up. Any input would be appreciated.

[Onizukachan]

You can do it with PA Soft, not aware of it being able to be done with NCS.
You have to set mileage to 0 on the module before you can change vin.

http://forum.e46fanatics.com/attachm...8&d=1450146986

[Thaniel]

Yes. I've done it on a couple with oa soft.

[tekoo]

I have the same exact problem you had a couple of years ago with resetting the VIN on a used light module. How did you end up solving the problem? Fg_auftrag_schreiben fails in tool32. I can’t figure out the Zusb # of ALSZ or find it in Winkfp. ISTA/P recognizes the different VIN on the used unit and fails to code it giving a COAPI1000 error. Thanks

[328 Power 04]

PA Soft BMW Scanner 1.4

[tekoo]

PA Soft BMW Scanner 1.4

Thanks 328 Power 04 for your response. I am not familiar with resetting the VIN and mileage with PA soft for ALSZ. Do you have any manual or a prior step-by-step write up of how to do it?

[Driiven]

easy job 2 minutes connect cable open pasoft go to lcm then click on programming and click write fgstnr. enter the last 7 digits of your vin number and your good to go

[tekoo]

easy job 2 minutes connect cable open pasoft go to lcm then click on programming and click write fgstnr. enter the last 7 digits of your vin number and your good to go

Thanks everyone for your help. I purchased the BMW scanner 1.4 from eBay and attempted to write the FGSTNR last night. It required that I do factory reset of the LCM first and when I attempt to do it, it fails to reset (E=2). I tried multiple times after restarting my laptop to no hope. Also tried to use various different algorithms. Most of them fail to change the FGSTNR and some get stuck in “writing FGSTNR” state for over 30 mins before I abort the process. Any ideas?
I would like to post some images for you but not sure how.

[tekoo]

C13D56E9-75CF-4D15-B9E9-26ECD75A1796.jpgD25B536C-8FEB-4351-89E3-1E06F59A9C64.jpg01AACDA2-22F0-48F8-BD16-2AF2883CE167.jpg

[legoman67]

you need to set it to the right algorithm for your LCM.

[tekoo]

you need to set it to the right algorithm for your LCM.

No one knows the right algorithm for my LCM. There is a list of different LCM part numbers in PA soft with the corresponding algorithm for each however my LCM BMW part number is not included. While trying to reset my module with each algorithm, there was a particular algorithm that caused my headlight to turn on and off briefly while none of the other algorithms did the same, so I’m assuming it’s the correct one for my LCM. Factory reset was still not possible with any of the algorithms. Here is the LCM part number.3F945CF1-8B68-443E-89E3-C081528C2133.jpg

[Lupin3te]

Sorry for reply this old Threads.
Thaniel how did you solve that without Scanner soft nur with the original once?