[frankk]

Hey everybody, I'm also pretty new here and pretty new about all these things, but I thought I would give it a shot, so my problem is that the code is invalid.
I got the 1b.hex file using glovebox usb slot, and when entering the code I got from the FSC generator the car just says that the code is invalid, no error from the program or anything. Would really appreciate some help

[txomin]

Originally Posted by Jagaer

txomin

It is possible the sources I used to reference what is a "valid" VIN are out of date, but yours doesn't seem to be valid.

For BMW, the first digit should be the plant assembly number, which should be one of: A, B, C, D, E, F, G, J, K, L, M, N, P, V, W.

I'm not certain what plant is "0". If you have an X4, I'd expect it to be built in Spartanburg (until Trump tariffs force it to move), which is Plant Code "L" and "M".

@Jagaer
I’ll PM VIN info... if you want to check.
Thank you

[Jagaer]

Originally Posted by frankk

Hey everybody, I'm also pretty new here and pretty new about all these things, but I thought I would give it a shot, so my problem is that the code is invalid.
I got the 1b.hex file using glovebox usb slot, and when entering the code I got from the FSC generator the car just says that the code is invalid, no error from the program or anything. Would really appreciate some help

There have been a few people which have had issues with the Hex file retrieved using the USB port.

Infrequently the program used to cut the 319 byte "chunk" of the persistence file, does not grab the correct part.

The other issue is if you are using an emulator. Depending on how the emulator is activated, the VIN in the Hex file does not match the vehicle VIN. This is easily changed within the 1B file itself.

[frankk]

Originally Posted by Jagaer

There have been a few people which have had issues with the Hex file retrieved using the USB port.

Infrequently the program used to cut the 319 byte "chunk" of the persistence file, does not grab the correct part.

The other issue is if you are using an emulator. Depending on how the emulator is activated, the VIN in the Hex file does not match the vehicle VIN. This is easily changed within the 1B file itself.

Maybe grabbed the wrong part indeed, in case of that should I just retry doing it? Also how could I try to change the VIN inside the 1B file?
I'll add the file here just in case you could maybe help me out.

[txomin]

Originally Posted by Jagaer

txomin

It is possible the sources I used to reference what is a "valid" VIN are out of date, but yours doesn't seem to be valid.

For BMW, the first digit should be the plant assembly number, which should be one of: A, B, C, D, E, F, G, J, K, L, M, N, P, V, W.

I'm not certain what plant is "0". If you have an X4, I'd expect it to be built in Spartanburg (until Trump tariffs force it to move), which is Plant Code "L" and "M".

Hi Jagaer,

This is my complete VIN:
https://www.etkbmw.com/bmw/EN/vin/de...10000L88505/EN

There is obviously some different standard other than the one you posted... let me try to found details about it.

My car’s VIN pics:
https://www.dropbox.com/s/5spr5lewq9...arge.jpeg?dl=1
https://www.dropbox.com/s/azp07vofcm..._1800.JPG?dl=1




EDITED @1430UTC
Ok, I got an answer directly from my BMW dealer:
Looks like that my plant manufacter is “L” wich in my case is the 12th VIN digit. This happens since the production plant letter for BMW is attached to the car’s serial number with no leading zeroes.
Basically the first vehicles of the serie are the 00000L1, 00000L2, etc... eventually the plant identifier reaches the 11th place after the 99,999 vehicle (0L99999), from that point on the 11th digit corresponds to the plant.

Makes sense to me since my X4 was produced in Oct 2014, at the very early stages of the model production.

[Jagaer]

@txomin.

Thanks for the explanation, the generator has been updated to allow the '0' digit for the first character of the VIN

[aTasca]

hi,

I have been using the generator for maps activation in 5-6 units now and all worked just fine.

Last I have used it (2014 F10 LCI with NBT), pulled the DE file with esys and enet cable, all looks fine, is 319 bytes long, looking inside I can see the VIN and the production date timestamp, all looks fine.

however when feeding it into the generator the resulted code is displayed as invalid - tried one-time and life-rime code, same thing.

any ideas on this?

thanks

[Jagaer]

Originally Posted by frankk

Maybe grabbed the wrong part indeed, in case of that should I just retry doing it? Also how could I try to change the VIN inside the 1B file?
I'll add the file here just in case you could maybe help me out.

Based on the 1B file you attached, I'm guessing you are using an emulator or script activation. (File starts with 123456 instead of 773487, and your VIN is 1234567)

The keys within the file appear to be correct, and are in the correct location.

[Jagaer]

Originally Posted by aTasca

I have been using the generator for maps activation in 5-6 units now and all worked just fine.

Last I have used it (2014 F10 LCI with NBT), pulled the DE file with esys and enet cable, all looks fine, is 319 bytes long, looking inside I can see the VIN and the production date timestamp, all looks fine.

however when feeding it into the generator the resulted code is displayed as invalid - tried one-time and life-rime code, same thing.

any ideas on this?

Everything seems to be correct, the only other thing I can think of is if the vehicle is from a different region.

The CIC/NBT needs to be "activated" for a region of the world, then maps are "activated" for that region.

If the car was originally from a different region (Turkey, Egypt...), attempting to activate Europe maps will fail.

Other than that, I do not know why it would not work...

[rob325]

Thanks a lot for making this all available and your explanations Jagaer.

After reading, viewing and experimenting with some basic coding on my e91 lci the last year, your generator made it possible to get the right keys for a navi update.
I've just updated my E91 to 2018-2 and did the same with my F20.

[Axlbmw]

Hello all, i am new to the forum and allso glad to be here found a lot of new and cool information, but now enough with this i should get to the point , i ectracted my 1b file from the car with the usb it was ok untill i placed it in the generator , the code was invalid when i tryed to update the maps, i opened the hex file and i saw there 123456 numbers, what can i do?i do not know exactly how to modify the hex file. The maps are europe east premium 2018-2 1 usb. Please excuse mu bad english as is not my first language the car is 2009 LCI e60 520d. Thank you in advance

[Jagaer]

Axlbmw Did your car come with a CIC from the factory? Typically, if your VIN is "123456" it is using an emulator or is script activated.

If you post your 1B file here, someone here can take a look at it, to see if the file looks right.

[Axlbmw]

Originally Posted by Jagaer

Axlbmw Did your car come with a CIC from the factory? Typically, if your VIN is "123456" it is using an emulator or is script activated.

If you post your 1B file here, someone here can take a look at it, to see if the file looks right.

Well i guess the car came with a factory cic, beeing built in 12.2009 as fahr as i know all models built in europe have cic not ccc. But on the other hand i did not buy the car new, i got it second-hand it was built in Italy and now i use it in Romania. So i do not know that much aboit it...but i guess if it was scripted the one who did it could have changed allso the voice commands

[Jagaer]

Axlbmw The 1B file appears to be correct, what is the last 7 of your VIN?

[Axlbmw]

C096398 is the VIN

[Jagaer]

Axlbmw 1B modified with your VIN attached.

[Axlbmw]

Thank you verry much for your time and effort Jagaer!
If it is not too much to ask, what went wrong with the extraction? If the file was ok..why didn't it complete the file with the propper vin number?i am trying to understand a little what i am doing here , not only to do it mechanicaly

[alexiliev83]

Hello,

I am facing hard times generating a FSC code for my NBT Navigation. The problem is that when i ty to enter my vin number i do not have the manifacturing date for it. And both the closer once does not work.

My vin is : WBA5D31020D574437

Correct me if i am wrong but i read that the vin should be D574437?


I am looking for fcs code for 2018-2 Europa NEXT Navi

The CIC/NBT Generator recognize this VIN code, but it does not allows me to generate correct code.

The car is manifactured 13.10.2013
Looking for HELP.

Thanks,
Alex

[rote]

As a recent CIC retrofitter, I'm happy to report that I was also successful in pulling the 1b file and generating the FSC code. Just wanted to give a huge thanks to Jagaer (and portalseo)

[opjose]

Originally Posted by alexiliev83

Hello,

I am facing hard times generating a FSC code for my NBT Navigation. The problem is that when i ty to enter my vin number i do not have the manifacturing date for it. And both the closer once does not work.

My vin is : WBA5D31020D574437

Correct me if i am wrong but i read that the vin should be D574437?


I am looking for fcs code for 2018-2 Europa NEXT Navi

The CIC/NBT Generator recognize this VIN code, but it does not allows me to generate correct code.

The car is manifactured 13.10.2013
Looking for HELP.

Thanks,
Alex

You have to pull the file from the car and use that.

Don't use the VIN entry option.

[alexiliev83]

Originally Posted by opjose

You have to pull the file from the car and use that.

Don't use the VIN entry option.

Thank you for your reply.
Unfortunately i don't have the nescessery cable in order to pull the 1b file.
This is the reason why i am asking for help.

Thank you,
Alex

[opjose]

You will either have to pull the file or purchase the code from a vendor.