[nyc4runnin]

following this ... need to do all these steps for direct CIC replacement ? factory CIC died...

[Emil98]

First of all, Thank you for this detailed DIY. Managed to successfully make the retrofit from M-ASKII to CIC Professional with all functions working including the navigation. The difference is indescribable.
The trickiest part was the FSC coding, and to write the new VIN to all modules. I found a different version of FSTool2 with preset files, and step by step guide and worked like a charm. It can do the 17, 19, 1b certificates.
The next problem was that if I entered the activated navigation menu, it immidiately asked me the activation code, but I couldn't check the actual version of the navi,
so I didn't know which version I should use to update and to generate the activation code.
Found this exact problem on a different thread, Tool32 can do the job to check which version has it.
If someone would ask which part was the most difficult, I would say get the tools for FSC Certification. I saved all the working stuffs in one place. So If anyone need, I can send it.
The next thing I would like to accomplish is the Hungarian Language.
But as I read in other threads the coding with NCS is not enough, you need to update the firmware versions in a correct order and with an appropriate tool which is an ICOM interface.
At first when you read the DIY it seems difficult and complex. When you finally spent $500 or more to the stuffs (I managed to do for $350)
and start to disassembly the old and assembly the new CIC, it seems less difficult, and when you reach to the coding you get excited not to mess up something.
My goal is to encourage everybody who thinking about this retrofit, because If I would do this again it probably would only took half of the time or less than for the first time
and furthermore your car looks many years younger than before.
Anyway anybody is interested in a working M-ASKII navi?
Ohh and be careful with the postal services because it can be tricky...

[juliano_ew]

Originally Posted by Emil98

First of all, Thank you for this detailed DIY. Managed to successfully make the retrofit from M-ASKII to CIC Professional with all functions working including the navigation. The difference is indescribable.
The trickiest part was the FSC coding, and to write the new VIN to all modules. I found a different version of FSTool2 with preset files, and step by step guide and worked like a charm. It can do the 17, 19, 1b certificates.
The next problem was that if I entered the activated navigation menu, it immidiately asked me the activation code, but I couldn't check the actual version of the navi,
so I didn't know which version I should use to update and to generate the activation code.
Found this exact problem on a different thread, Tool32 can do the job to check which version has it.
If someone would ask which part was the most difficult, I would say get the tools for FSC Certification. I saved all the working stuffs in one place. So If anyone need, I can send it.
The next thing I would like to accomplish is the Hungarian Language.
But as I read in other threads the coding with NCS is not enough, you need to update the firmware versions in a correct order and with an appropriate tool which is an ICOM interface.
At first when you read the DIY it seems difficult and complex. When you finally spent $500 or more to the stuffs (I managed to do for $350)
and start to disassembly the old and assembly the new CIC, it seems less difficult, and when you reach to the coding you get excited not to mess up something.
My goal is to encourage everybody who thinking about this retrofit, because If I would do this again it probably would only took half of the time or less than for the first time
and furthermore your car looks many years younger than before.
Anyway anybody is interested in a working M-ASKII navi?
Ohh and be careful with the postal services because it can be tricky...

I need help. My car initially came with the M-askII system, I replaced the radio and the screen with a professional CIC already in CIC.C1A version. To activate the navigation I bought an emulator, however, this only works with the radio with the VIN of the donor car. What bothers me is that this causes an incorrect vin error on the radio and I believe it is causing the car to run out of battery.
I removed the emulator, changed the VIN for my vehicle, generated the certificates and the FSC, however, in 00190001 I can only generate one certificate, the FSC is in red. I do all the steps correctly in FStools and CHECK_FSC from 00190001 gives an error.

Would you have the walkthrough to activate navigation?

[Emil98]

Originally Posted by juliano_ew

I need help. My car initially came with the M-askII system, I replaced the radio and the screen with a professional CIC already in CIC.C1A version. To activate the navigation I bought an emulator, however, this only works with the radio with the VIN of the donor car. What bothers me is that this causes an incorrect vin error on the radio and I believe it is causing the car to run out of battery.
I removed the emulator, changed the VIN for my vehicle, generated the certificates and the FSC, however, in 00190001 I can only generate one certificate, the FSC is in red. I do all the steps correctly in FStools and CHECK_FSC from 00190001 gives an error.

Would you have the walkthrough to activate navigation?

You probably missed the new VIN writing to your CIC. The CIC headunit coded to the donor car. You need to set your VIN to the Headunit.

There is a step by step guide.
Open TOOL32 and find this 3 modules: CICR_GW.PRG, CICR.PRG, CICR_HD.PRG.
You will need to do the same thing in all modules. So first select one of these and in Tool32 on the Jobs list select "aif_lesen" => you will read infos with it.
On the right list "results" tab select these options together: aif_fg_nr, aif_fg_nr_lang

Will pop up a new result window where you will see the last 7 characters of the VIN coded to the CIC. We only need to modify this VIN to yours.

So on the jobs list you select "aif_schreiben" => this job will write the parameters to the CIC, and on the arguments field you need to write the arguments in the correct order with the ";" separator.

It will wait 9 arguments and you need to change the first argument to your VIN(the last 7 character of your VIN) and copy the remaining arguments from the info which you've read before. I don't remember the args order but it will tell you exactly what parameters it waits and in what order.

Example: lets assume your VIN is: A123456
Then the args which you need to set is looks like this:

A123456;13.11.2013;9284329;0000000;0000000;011111; 12345;61200;020260F80AA

I copied the reamining 8 args from my CIC.
And you need to do this same steps on all the 3 modules mentioned below.
After you done with it, you can do the FSC coding.
I would recommend you to use FSTOOL_v20211. I used it and worked like a charm.

Hope it helps,
Cheers

[PandaNL]

Hi All,

Does anyone have a new link for the 6FL cable ~3 metres from usb plug to combox? The one linked by the OP is no longer valid. Preferably one in europe.

[MadJoe]

I'm about to do the combox retrofit to my new-to-me E93 and was wondering if there was any PNP kits for the retrofit anymore? It seems the only people who made them are no longer stocking them, and/or their email is down (CICretrofit@gmail.com gets returned undeliverable).

[Mc 007]

Hello
Need help after Combox installing,mic don’t work,no one hear me,can someone help? I put on pin 26 the blue&black wires,is this the problem?
Thx

[arber.m]

Hello everyone

Can somebody provide a download link for FSTOOL_v20211

[PichaDis11]

Years later this DIY is still of great help. I've gone through so many emulators; the last being the most expensive and it still got wrecked. If you are still on here, I Just want to say thank you.

[nsjames]

just checking back in.

hosed my retrofit coding trying to track down a comfort access problem, came back here, followed the vehicle order coding bit and now I'm back to working bluetooth on my combox.

[Luxy]

Hello, Recently, I retrofitted CIC in a BMW E92, and the donor CIC is C1A. However, currently, my navigation appears to be gray. When I retrieved data from "aif_schreiben" using Tool32, I obtained the following information: "P075502,09.08.2011,9273158,9273161,0000000,000000 ,00000,0,0202JP0F78RA". It seems like there are too many zeros in some parameters. Additionally, when I try to execute STORE_SIG_CERT and CHECK_SIG_CERT in "FSTool2," I encounter an error (attached in the appendix).
I have also noticed that some people fetch "FSCS Certificate" from "Configuration" -> "Certificates" -> "FSCS Certificate" by accessing the SWTPatcher-v2 -> 03_FSC_Templates -> 001B0001.fsc folder. However, when I attempt to retrieve these files, I encounter an error (also attached in the appendix).

[GDeeniss]

Hi,

I just came back to this post after following the coding part step-by-step and everything went as smooth as butter, you have perfectly described every step and answered all of the questions that would occasionally pop up into my head.
I have made the switch from M-ASKII to CIC Professional with Combox, hands down best upgrade there is.
If you are still in here and read these, thank you a lot!

[KoktGrus]

I got issues with fstool. Got all working except for 9C. It gets rejected.

Can someone with a working environment help me generate a 9C?

[BRG_N54]

Originally Posted by KoktGrus

I got issues with fstool. Got all working except for 9C. It gets rejected.

Can someone with a working environment help me generate a 9C?

Try this version of FSTool2, only way I got 9C to apply.

[Captain Buumer]

This is a good thread for various information.

Recently i retrofitted Combox to a car that did not have TCU or MULF and i'll provide some hopefully useful information.
Originally car had:
M-ASK & Basic audio 2007 year e90.

Now it has CIC + Combox + MMI Carplay. The upgrade is massive.
(before Combox i used Dension 500S BT but it has some problems with lower frequencies - they are reduced for some reason - and bluetooth connection is pretty limited - contact list is not pulled to CIC + aftermarket mic was just terrible no matter what i tried + it displayed max 30 songs a page so it was super annoying to navigate through 16+ pages).

I didn't care for telematics/BMW assist functions.

It is a big job actually since you need to do following things:
(It's preferred to have complete set stripped from other car = less problems)

• Bring optical cable to the MOST diagnostic port under the steering wheel. Modify the loop so it it is complete. I took out the driver seat so i can raise the carpet and place the fiber safely in the corner tunnels. Or take most of the interior out if you want to do it the "OEM" way.
• Bring power cable from fusebox (10A fuse)
• Bring ground from random ground point near rear.
• Route USB to center console
• Route Bluetooth antenna wiring to under steering wheel cover that has the pedals lightning plastic piece (remove the foam to reveal the antenna slot).
• Route AUX to center console (4 wires)
• Route microphone wiring from Combox to FZD (use quality cable that has shielding - don't cheap out here to get noise free microphone). Preferably it is twisted cable with shielding. Also route it around the left rear seat to center console. Then behind the CIC. Then above the glovebox to the A pillar. This way you avoid any power cables and have almost no static noise in the MIC.

Minimal Combox wiring to get basic functions working USB/Microphone/Bluetooth:
(BN2000 Black connector model that is Telematics + Media)
Pin nr/Purpose/wiring color

• 2 Power T30 Fuse 59(10a) Red/brown or Red/Green
• 10 Aux GND Purple
• 11 MIC SHIELD Clear with silver core -> Does not connect to MIC just to reduce electronic magnetic interference
• 12 MIC - Blue -> Microphone pin 2
• 14 Ground Brown
• 22 Aux (SHIELD) Clear with silver core
• 23 Aux NF-L Red on White
• 24 Aux NF-R Green on White
• 25 MIC + White -> Microphone pin 1
• USB from combox
• Bluetooth from combox

Edit: Don't need CAN wires. Coding Combox is somehow done by CIC over MOST network (Using NCS Expert).

The coding part is pretty standard -> tell car she is now older -> default code modules (CIC & MEDIA) based on FAs
What i did was only the below 4 changes to FA:

• #0311
• $644 PREPARATION F MOBILE PHONE W BLUETOOTH
• $6VC DUMMY-SALAPA (ECUs can now see Media Module)
• $6FL USB/AUDIO INTERFACE

My CIC is .C10 version and combox works fine. Don't need C1A or C16A or C13A.
It's script activated (For script activation i needed to bring ethernet signals from CIC to diagnostic ODB2 port and use ENET cable = could access the files in CIC using Filezilla and write the little startup script using Notepad++ that has EOL conversion -> Unix command under Edit menu. This is important so you don't corrupt the startup script when editing it under windows machine).
I also replaced CIC HDD with SSD (Compact flash with adapter) so i have backup and it is at max speed at all times).
Avoid using emulators for CIC. I also had power draw issue with emulator + random errors in ISTA related to modules in CAN network.

CIC VIN is not changed.
Combox VIN i didn't change either.

Also Combox can play .wav files which are better quality compared to 320kbps .mp3 (provided you have good source files). It loads about 600 songs almost instantly since they are uncompressed (magic of .wav format).
Also supports 128GB USB 3.0 drive.
I think Combox was on UPD01005 software and Pixel 7 pairs just fine. I didn't bother updating the software on combox either since everything (bluetooth music and calling) works fine.

Some images of install:
It took two days (basically half a weekend) to get everything properly installed + coding.




So in the end Combox is very nice upgrade and definitely worth the effort. Sound quality from USB stick is excellent.

[CrackedatBMW]

Originally Posted by FaxData

Activating locked features (Navigation):
Voice control, navigation, sat radio, bmw apps and Arabic language (why lock only this language??) are locked to the native VIN of the CIC; a method must be chosen to unlock them. So I went with the CIC patcher method, which is the most flexible but also the most difficult. Before I explain how, here are the four methods:

Buy all new certificates - Legally purchase all the features for your VIN. Pros: legal, as OEM as it gets. Cons: expensive; the cost of buying all the certificates might be enough money to buy a newer model car instead...

Hardware emulator - a CAN filter sitting between the CIC and the rest of the CAN topology that prevents the CIC from successfully checking the VIN. Pros: straight-forward hardware install, easy map updates, no mucking around with CIC software. Cons: costs money (and shipping time), requires cutting CAN wires on factory harness if you don't pay for the more expensive plug-and-play harness, cannot add certificates that the original VIN did not have (locked features e.g. sat radio, bmw apps).

Script activation - a small shell script (written by intel123) that runs at boot to activate all the certificates that are locked due to mismatched VINs. Pros: Free, super easy to install. Cons: Cannot add certificates that the original VIN did not have (locked features e.g. sat radio, bmw apps). Still requires a working coding environment with FSTool2 or equivalent to update maps, unless you are willing to cut the CAN wires.

CIC patcher V2 - a small shell script (written by intel123) that modifies how the CIC reads and accepts the root security certificate, allowing you to upload forged certificates. Pros: Allows you to add all the certificates available, including certificates that did not come with the donor car. Cons: Only works CICs from USA or ECE regions running C1A firmware. Additionally, the CIC will now reject the genuine certificates from the donor car, so this is a one-way street (unless you flash it back to stock C1A or replace /mnt/HBpersistence/rcert.swt).

I went with the patcher, which should've been easy but took me a surprising amount of research and trial-and-error. First I couldn't get the software, then I couldn't get it to load, then I couldn't get the CIC to accept any certificates, then I got certificates 17, 19, 1B working, but couldn't get 9C, 6F, etc etc. Weeks went by.

So... in the end, this can be complicated, or it can be easy. The easy way:

1. Get a working coding environment (working EDIABAS). If you've made it this far and have a working NCS Expert with working SP-Daten files, you're good to go here.

2. Use Tool32 to set the VIN in the CIC to your car's VIN. Note the tutorial incorrectly says 17 alphanumeric digits but it's actually 18 digits (17 for the VIN and 1 for the checksum).

3. Get and install Java Runtime Environment 1.5.0 update 22 (Jave SE Runtime Environment 5.0u22). (Some tutorials say 1.4.0 is fine, but I found FSTool2 to be buggy with 1.4.0.)

4. Get FSTool2 version 02.02.00. Look for the installer file called setup_fstool2_02.02.00.exe. Please don't bother with any other version. Run the installer, it will install CarServer, FSTool2, and extra EDIABAS configuration files. It will handle 6F and 9C. BTW if you install it and try to run it without Java, it will not give any errors. It just won't run.

5. Find BMW CIC Patcher v2 by intel123. You will find it on the first post of a super long (80+ page) forum thread. Keep this thread open. Unzip the files. There are 4 folders, 00_PRIVATEKEYS, 01_PATCHER, 02_CERTS and 03_FSC_TEMPLATES.

6. Copy the copie_scr.sh file from 01_PATCHER\USB_AUTORUN onto the root folder of a USB drive, and plug it into the glovebox USB (the one directly connected to your CIC). It will run, and the CIC will reboot.

7. Go to CIC patcher v2 thread post #746 for the pdf guide on installing certificates for e90 (cic_fsc_Ex_en.pdf). It is NOT complete enough to use, but I will refer to it in a second.

8. Run FSTool2 using the desktop icon. Go to Configuration (the last tab), set the language to English. Scroll to the bottom. Under "Certificates" set FSCS, Root and Sig certificates to 02_CERTS\fscs.der, 02_CERTS\root.der and 02_CERTS\sigs.der, respectively. Under "Keys" set the private key to 00_PRIVATEKEYS\fscs.der. Go to Connection (first tab) and hit Connect.

9. Go to Parameter, and set Diagnose address to 63, Appl.-Nr. to 19 (or whatever certificate you are uploading), Upgrade index to 1, and VIN to the last 7 digits of your car's VIN.

10. Go to Enabling Codes. Click load from file, go to 03_FSC_TEMPLATES, open 00190001.fsc. Click Edit. Put the last 7 digits of your VIN in "VIN short." Click Sign, click Check signature, click Save as (not needed but you can sign all the certs ahead of time!) and click Apply.

11. Go to SWT Develop. (Open the PDF guide from step 7 above! Jump to page 4, do step 6 through step 12.) Click STORE_SIG_CERT, click =>. Click CHECK_SIG_CERT, click =>. Click Execute, look for two successful statuses. Remove STORE_SIG_CERT and CHECK_SIG_CERT using the <= button. Click SET_VIN, click =>, click Execute, look for success, remove using <= button.

12. (PDF guide steps 13-14) STORE_FSCS_CERT, =>, CHECK_FSCS_CERT, =>, STORE_FSC, =>, CHECK_FSC, =>, Execute. Look for four successes.

13. Repeat Step 10 above with 001B0001.fsc. (Load, Edit, Sign, Check signature, [Save], Apply) Check tab Parameter to make sure the application changed from 19 to 1B (old versions of FSTool2 do not auto-update). Now repeat Step 12 above (STORE_FSCS_CERT, =>, CHECK_FSCS_CERT, =>, STORE_FSC, =>, CHECK_FSC, =>, Execute). You do not need to repeat step 11. Repeat steps 10 and 12 for all the certificates you would like to insert (which certificates do what are on page 8 of the PDF guide).*

14. Reboot the CIC. You could a. let the car sit for a bit, b. disconnect / reconnect the battery, c. FA/VO code the CIC (SG_CODIEREN), or d. login with telnet and run "slay HmiMain" - I'm not covering the latter in this DIY though.

15. Assuming you installed at least the 19 and 1B certificates, Navigation should now be selectable. BUT when you select it, it will ask you for an activation code. Pull your 1b file via USB stick**, and use it in Jaeger's FSC generator. If you know what year the maps are in the CIC, you can generate that specific year, otherwise just generate a lifetime code and use that.

Done! Navigation should now be working. You can check your other certificates individually in FSTool2 using GET_STATUS, or all at once using a tool called FSC Tools.

*Inserting certificates only unlocks the feature for cars that are programmed to have the feature, it doesn't add the feature. So if you want voice control for example, you do need certificate 17, but you need to also add the hardware (microphone to headunit - different from the bluetooth microphone that goes to the TCU/MULF/Combox, as well as activation button e.g. multifunction steering wheel $249) and code in $620 (and $249 I think) to CAS/NFRM and default code your CIC. BMW apps requires certificate 9C, a combox, 6FL or 6NF and coding in $6NR (see next post). Satellite radio requires certificate 6F, running an extension to your satellite prep in the trunk (or a full antenna to your shark fin if you don't have prep) and coding in $693->$655 (delete 693, add 655). Disclaimer: I have not tried adding satellite radio to my car, and I already had voice control and TCU.

**An aside - You don't need an IP connection to your CIC for this DIY, unless your CIC is old enough that the USB script fails. If you're getting the generic VIN, you will need to telnet or FTP into the CIC to get your 1b file instead. Forum members will say you can either run ethernet to your OBD2 port, or attach a USB-ethernet adapter to the glovebox USB port. Most USB-to-Ethernet adapters don't work and the old referenced D-Link one is not available; instead get one with the ASIX AX88772 chipset. I bought this one, it works. I think a clue that it will work is that the adapter advertises compatibility with Nintendo Wii / WiiU, but I'm not sure on that.

Good evening I wanted to ask something when I want to load the 03_templates fstool gives an error? could someone help me with this? see the screenshot what I add in fstool

thanks a lot in advance