Well, the LM is not fixable in comfort mode, can you please let me know how to flash in expert mode? Tried many times, due to the ZUSB being garbled, it is not taking comfort mode flashes. EDIT: I tried your numbers, same exact numbers I had as well. No idea how the ZUSB number got corrupted.

 

Okay, I guess I do not get help with this? I gave the information asked of me and I have tried all suggestions.

 

You haven't been getting help? I think I've been trying to point you in the right direction since the beginning. Issues like this don't get much traction because it's something no one hardly does anymore and if they do you're going to pay and rightfully so. There's a lot that goes into knowing what you're doing programming these cars as you can see. For me to help I need to have free time as my time is valuable. All these things are from memory and have not done it in a while just like other coders which have moved on to the newer models which use completely different programs. Below is one way I'd go about it. It's about as close to a how to you're going to get. Good luck

Expert mode:

- Create develop folder in C:/EC-APPS/Data
- Place these files in it only everything else in it delete: 9203082A.opa, A0000000.0da
- go to C:/NFS/CFGDAT open COAPI.ini
- change ZB&SW nummber to 9203082
- WINKFP configuration: check: voltage, checksum, bootsector and all UIF
- comfort mode
- enter zusb 9203082
- select as ok
- VIN - enter vin
- go to done
- ecu address will show and PABD, P-SGBD
-close out and reopen
- enter Zusb and select
- enter VIN
- expert mode and load ecu address from previous, PABD, P-SGB then program program file only.
-complete.

 

Your time and help is invaluable, I have thanked you many times, you are appreciated.

Thanks to Expert Mode in WinKFP and your instructions, my LM is programmed and has the right Zusb programmed in. Success! THANK YOU!

For some reason, the COAPI.ini was programming in a blank ZUSB (WinKFP was showing <ZUSB 0000000 as set by coapi.ini> (something like that. I fixed it by putting everything in expert mode, and then flashing in comfort mode). Now it has the proper 9203082 in INPA and I could reflash it if I wanted. I set it up exactly how you said to and even checked another guide, so no idea what it is flashing 0000000 as the ZUSB, shrug? In any case, I got it done and got it coded back to stock. (FA_Write, SG_CODEREIN in Expert Mode).

I got the ICOM A2 + ICOM B, both are working great. It arrived Saturday and I have been using it since. Yet I still cannot use ISTA-P because I am not getting MOST signal at the port in the glove box! Talk about a nightmare!

I am getting the red light at the modules in the trunk. There is no red light at the MOST port in the glovebox. Strangely, it comes on after the car has been to sleep, then goes out. I think it's because my MMI/CCC and CCC are stuck in programming state. I tried flashing them in the proper order, but it gets to around 29% in WinKFP and then fails. MMI/CCC and CCC are module 4 and 5 in order to flash, but even expert mode is failing on both. I think maybe because my CDC is not functional (red in ISTA+) because of the MMI/CCC and CCC, that is why my glovebox MOST connector is not working.

According to ISTA+, both are stuck in programming mode (just like pictured above). This is also making my Radio, AMP, POC, CDC, and something else is not working and not visible in INPA (AIF). I tried to remove the Navigation DVD, holding the two eject buttons and the mute button. I also tried coding them to default in NCSExpert, it works or fails, but they are still stuck in programming mode and my IDRIVE is not working.

I know everything works, hardware wise. Back when my radio system was working, the red light was on in the glovebox MOST connector. ISTA-P has proven to be my unicorn, I cannot make it work always because of something, be it hardware, now due to my MMI/CCC and CCC stuck in programming mode. IMO the MOST bus is the dumbest design on these cars. No wonder they got rid of it with the later cars.

I was outside from 11:30 am to 7:50 PM, the LM took an hour to setup (power, laptop, power supply, hookup), and flash. The rest of the time I spent trying to run ISTA-P, failing every time because no MOST signal. I then went to ISTA+, scratching my head by it working perfectly yet ISTA-P is not. I reset adaptions, turned the system time back on, and basically spent a little time learning it and clearing the fault codes. From 4:30 until it got bitter cold, I tried fixing the MMI/CCC and CCC with WinKFP and NCSEXPERT.

3/5 modules flash fine and are able to get the VO programming from NCSExpert, MMI/CCC and CCC refuse to flash, even in expert mode. Banging my head on a wall!

 

Yea coapi by default is zeroed out that's why I wrote to input the ZB number to assist the program. Either way you got it figured out. you can't flash on the MOST if it's down so you have to work around it. Your downfall right now is that your ISTA/P is not working

 

It's a downfall alright! I did a little investigating today and found out that whoever last programmed my car in 2006 (treated with ISTA-P 2.59.x) actually programmed in some E90 modules for my radio. That could explain why I cannot get it to take the E60 MMI/CCC and CCC coding, both FSW_PSW and Bimmercode is showing that certain things are showing E90 (guess which two modules!), that could explain it as I only have the BASE and E60 for each DATENS I have, no other models, to save laptop space. Going to try and see what I can do with it with Bimmercode. If not, it looks like I will be taking apart my dash, glovebox, and trunk. I miss having a radio, a lot. Those same modules were also programmed in with another VIN code when I initially got the car. Some modules has the "yyyyyyyy" for VIN, others had some BX6003 (mine would be CM38388).

In hindsight, I wish I learned German in high school. Thankfully, translators and NCS Dummy exist.

 

If it was a retrofit it was configured correctly. You don't change or program CCC to VIN. You just default code it.

 

Progress update: I got all of the modules except the MOST BUS/CCC related ones programmed in. I actually got my radio to where it is showing the I-drive menu and the PDC sensors (big step up from the BMW logo. I just cannot get my MMI/CCC programmed in, then my Radio. It goes to 100%, then goes to the next screen, gets to 29% after about 20 minutes, then fails and says it is a security access error. The radio fails, because the MMI/CCC is not programmed in.

Still missing:
CDC (Red in ISTA+)
AMP
IBOC

Still in programming mode:
MMI/CCC
Radio

I ordered both a Bimmergeeks Pro K+DCAN and an OPTICAL male/female bypass loop. My amp and MULF are getting solid red signals, so I am going to take apart the radio this weekend and check everything. Isolate the problem, hopefully divide and conquer!

 

@seanjordan20 I have an ICOM. Literally the only thing I cannot do is get my radio working. It shows the PDC, but the iDrive is not working at all. Stays stuck at the BMW logo and will shift to PDC sensors if I am near something.

• All fuses have been checked and are good for all radio modules. Including fuses behind Radio and CDC.
• I have coded the MMI/CCC, CCC, and everything to my VIN with Tool32 and it took them (18 digit VIN w/checksum)
• NCSExpert will not code my CHOST or actual radio with SG_Coderein. Tried coding with NCSExpert in the proper order of the five modules, does 3/5 of them.
• WinKFP will not update the MMI/CCC, with either my ICOM or K+DCAN. It gets to 100%, then goes to 29% and gives a security access error.
• Tried using a CCC recovery CD, burned. It starts to load the firmware and gives an error "221" and ejects the disc. Think that is the same error number that WinKFP is giving (security access error).
• Took apart the entire MOST system, from the trunk modules to the radio itself. I think my MMI/CCC not working is making the MOST connector in the glovebox fail to light up. Module bypass did not help, all the trunk modules seem to be getting a steady red light. Behind radio and glove box MOST connectors are dark and not showing red light at all.

What can I try next? My car has been sitting for a couple of weeks, power supply hooked up to it when flashing/coding. It has given me a low battery warning for the last week, every day after sitting for a night.. Could this possibly be why my radio refuses to work, be updated, or programmed? It seems like my MOST bus went out about the same time my battery started giving low battery warnings. I did use my 30+ year old Sears(!) 40 AMP charger and no more low battery warning for today, not sure about tomorrow. I plan on getting a new battery this Friday coming up. My battery is 6 years old according to the last changed date, so sitting has likely killed it. It was showing holding 87% charge a few days ago, now only 73%.

Rest of car is working beautiful;, engine seems faster/smoother than ever and it runs great. How can I fix the last piece of the puzzle without getting a new unit? I am not worried about bricking it, it's bricked right now basically. MMI/CCC and CCC still in blue, is there a way I can get it out of programming mode with Tool32 or something?

 

Get your ISTA/p working would be your best bet. I'm not going to go through all the steps it's going to take to get your MOST back working. It's too much. There no reason checking any parts in the car because your issue is purely a programming issue which was caused when you flashed without knowledge. By now you could have gotten the program working and been done with it. There's steps to undo what you did and programs needed you have but don't know how to use. Get ISTA/p working and don't waste time and money on things that's not your issue