|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Search | Today's Posts | Mark Forums Read |
|
BMW 3-Series (E90 E92) Forum
>
HELP MSV80 cranking, not start after failed flash
|
|
09-29-2023, 09:51 PM | #1 | |
New Member
2
Rep 12
Posts |
HELP MSV80 cranking, not start after failed flash
Hello, good morning and afternoon everyone.
I hope someone can shine some light into what I've done wrong, my car is now cranking without starting. an TLDR: I goofed up my flashing procedure after I attempted to flash the car with a tune with the car turned off, and only my key in the slot, no accessories turned on. This is when my winKFP became unresponsive, and I had to force close it, at this point the car then started cranking but not starting, whilist displaying a lot of error lights on the dash. Some context, please bare with me... Quote:
When scanned I get a lot of error codes. Codes being, driver mirror defective 009cd0, and 009ccf, no communication with control unit S0114, 00A3Ad, and a3ae which say "faulty receiver klombbi, transmitter dme-dde" for both, cas starter motor teminal 50 00a0b3, and even S0085 no communcation with DSC. Before the failed flash I only had 0093c3 my passenger seat occupency sensor, and AUC sensor 00a6cf. Code:
[C:\EC-APPS\NFS\BIN\MSV80.ctl] [29.09.2023, 22:00:00] [MULTIFLASH] MF_FG_NUMMER= MF_PABD=12msv80.ipo MF_PSGBD=12MSV80.prg MF_SG_ADR=12 MF_NAAB_DATEI= MF_PROGRAMM_DATEI= MF_DATEN_DATEI=MSV80_S8608441_x28i_to_x30i_NoMAF_waterpumptriggercel.0da MF_DIAGNOSEPROTOKOLL= HW interface activted. PABD set. P-SGBD set. ECU-Address set. Data and/or program and/or NAAB file set. INFO000=Error: Error 212: Error on checking data consitency -> in data datafile (DAF) INFO001=Error: Error 2021: Error LFCDHDIA.CPP (12msv80.IPS/IPO) CDHapiResultText 1 Datatransmission to ECU disturbed IFH-0010: Datatransmission to controlunit disturbed 12MSV80 INFO002=Error: Error 2021: Error COAPI2.CPP coapiRunCabd 6 Datatransmission to ECU disturbed SG_AIF_LESEN INFO003=Error: Error 2021: Error COAPIKF.CPP coapiKfKonvertGetRef 1 Datatransmission to ECU disturbed Data will be programmed. INFO004=Error: Error 211: Error on flash programming! INFO005=Error: Error 2021: Error LFCDHDIA.CPP (12msv80.IPS/IPO) CDHapiResultText 1 Datatransmission to ECU disturbed IFH-0010: Datatransmission to controlunit disturbed 12MSV80 INFO006=Error: Error 2021: Error COAPI2.CPP coapiRunCabd 6 Datatransmission to ECU disturbed SG_AIF_LESEN INFO007=Error: Error 2021: Error COAPIKF.CPP coapiKfProgSgDevelop 1 Datatransmission to ECU disturbed ERG=Programming not ok. Fatal Error Batch mode ended Edit: My english is terrible I apologize, I tried to edit out my rambling and have more information towards the error. Last edited by need4sleep; 10-01-2023 at 01:24 AM.. |
|
09-29-2023, 11:07 PM | #2 |
New Member
2
Rep 12
Posts |
After more digging, I did find a user named Pinscher, who seems to have the same error if not worse.
https://www.e90post.com/forums/showp...postcount=2111 they unfortantely do not state how they fixed it, but they follow up with saying https://www.e90post.com/forums/showp...postcount=2129 so I am not sure if this is releated at all, but perhaps I have done the same? |
Appreciate
0
|
09-29-2023, 11:58 PM | #3 |
New Member
2
Rep 12
Posts |
The more I read the worse it gets. Honestly I wish to just drive the car again, I really should not have even attempted it after the first fail.
I am reading more about replacing the dme.. worse and worse it gets. Can someone point me in any direction I should go about fixing this? Should I contact someone nearby that works with them, should I contact the stealership.. really at a loss here... and panicking |
Appreciate
0
|
09-30-2023, 12:29 AM | #4 |
Captain
196
Rep 803
Posts |
Go into inpa > e90 > functional jobs > f3 UIF and see if dme shows there. See if there is a zb number that populates or if the entries are empty/blank.
If you can see the dme there then you are fine. If you don’t see the dme it’s unresponsive and nothing you can do obd wise to get it to turn back on. If it’s responsive, just use winkfp comfort mode. F1, f3 update ecu and choose ecu, f4 enter vin. F8 done. F3 prog zb update. That will reflash the ecu with stock software and get you back up and running. I didn’t read you entire post as it’s quite long, so apologies if I missed something. But the above is general steps to getting dme back online after failed flash. |
Appreciate
0
|
09-30-2023, 11:05 AM | #5 | |
New Member
2
Rep 12
Posts |
Quote:
I have done as you said with Inpa, and it looks like good news. here is a screenshot of inpa during that. Last edited by need4sleep; 09-30-2023 at 03:29 PM.. |
|
Appreciate
0
|
09-30-2023, 01:13 PM | #6 | |
New Member
2
Rep 12
Posts |
Update, I attempted above, but no dice. I believe my winkfp configuration is now at fault somehow.
Quote:
I do have a tender on the car while doing this just in case I kill the battery. I checked the uif field again in INPA, and still populating the zb and vin okay. Last edited by need4sleep; 09-30-2023 at 09:07 PM.. |
|
Appreciate
0
|
09-30-2023, 01:56 PM | #7 | ||
New Member
2
Rep 12
Posts |
Here is what my ini configuration in winkfp is. I've updated the datens in winkfp via coding tool with 2016 datens, and now comfort mode is showing correct 12msv80.ipo.
Quote:
Quote:
Last edited by need4sleep; 09-30-2023 at 08:56 PM.. |
||
Appreciate
0
|
09-30-2023, 02:11 PM | #8 | ||
New Member
2
Rep 12
Posts |
After the daten updates, I figured the comfort would be fully functional, which it actually was, thankfully something going right.. Anyways I followed the steps, entered my vin, f8 done, and zb prog, but I got the same error as before unfortunately.
I am starting to think my cable is no good anymore, its been beat up over the years, thrown around in the car etc. Maybe its finally crapped out. I checked my com settings again, my port is set to 1, but my latency seems to have reset back to 16, and I know it should be a 1. I am not sure if latency would affect this or not. After reading this thread, I seen another user experience same error with disturbed ecu, and what seemed to work for them was laptop configuration, even a user mention the latency could be an issue. I am going to look over my laptops settings once more to match theirs in com port and even plug the laptop in during the process. Quote:
Quote:
Last edited by need4sleep; 09-30-2023 at 03:23 PM.. |
||
Appreciate
0
|
09-30-2023, 04:28 PM | #9 |
New Member
2
Rep 12
Posts |
So tried once more with flashing stock with winkfp in comfort mode and the newly updated com port settings of latency to 1 ms and suspend idle to 3600.
Getting new error, Error 704 assembly identification number not found in "xxkfconf.da2" file. To my understanding, I don't seem to have the correct zb prog file located in my C:\EC-APPS\NFS\DATA\MSV80 folder even after the coding tool updates. When attempted it with the updated comport settings, a tiny window popped up from winkfp asking to choose the zb number, and I selected 7574710 as it said do you wish to use the same etc, but I am now seeing I don't have the correct file, and wondering if I should attempt a different zb number. I have tried searching through all my datens, but I don't seem to have a 7574710.0pa file in any msv80 folder. I am unsure what my original ZB number was for my DME back when I flashed it a fear years ago when I successfully flashed the rsa and nomaf tune from bimmer labs BL shows some different stock tunes on the site, I am just not sure which one to try from BL as I can find 7602220A.0pa, and 8613000A.0pa in my C:\EC-APPS\NFS\DATA\MSV80. I think the process is: f1 comfort, f2 choose “8608332” from msv80, f4 enter vin, f8 done, then f3 prog zb update. Or choose “8608330” in f2, how would I confirm what zb # my DME previously was? Last edited by need4sleep; 09-30-2023 at 09:05 PM.. |
Appreciate
0
|
09-30-2023, 11:07 PM | #10 |
Captain
196
Rep 803
Posts |
If you’d like to read your flash history/what previous zb numbers were on the dme follow these steps:
F1 comfort mode F3 choose ecu F4 enter vin F8 done Choose expert mode Choose no/cancel on the popup box that appears Select done Select special Select read UIF You’ll see a text file open up with all the date stamps and zb numbers previously flashed onto the dme. |
Appreciate
0
|
09-30-2023, 11:39 PM | #11 |
New Member
2
Rep 12
Posts |
Okay, this should be okay todo while the DME is like this? I still have the fuel pump running non stop.
I may just try running one of the stock files from bl to get it to stop, and try this if not. Thank you, I really do appreciate your help. |
Appreciate
0
|
10-01-2023, 11:08 AM | #12 |
New Member
2
Rep 12
Posts |
Alright, update! Good news it seems my entire laptop configuration was just junk.
After setting latency to 1, and timeout from 5 to 3600, I also updated my datens via coding tool, plugging in my laptop and changing its power settings, I also set the laptop on a desk so the cable had no chance of moving, and running the batch file in a admin console. It has taken the noMaf tune successfully and is back to its original configuration before I screwed things up. In the end I didn’t go with the winkfp stock method as I figured I’d have to redo rsa and noMaf in the future, so I took the risk to flash the noMaf back, knowing I already had done rsa previously to it. Thank you sd-bmw I do appreciate saying it was fixable. To anyone in the same boat as me in the future, some other threads that help me understand the process more. RSA Delete Failed during WINKFP flash, now won't start BMW coding. How to update/Flash DME with WINKFP. Safe travels everyone! Last edited by need4sleep; 10-01-2023 at 02:25 PM.. |
Appreciate
1
gogaffffdd110.00 |
10-06-2023, 04:01 AM | #13 | |
New Member
0
Rep 6
Posts |
Quote:
thaks for links bro! I have same, today i will try respawn my car |
|
Appreciate
0
|
Bookmarks |
Thread Tools | Search this Thread |
|
|