[X-treme]

Thanks for helping out man really appreciate it. I merged the eeprom just the way you did (found out too late that you did it already haha). But it won't work, still got the error that the dme needs to be coded and the variant config error.
The chiptuner already ordered a new ecu, because the customer got angry and wanted his car back asap. New ecu now car is fine. I won't open the new ecu to read it, but if the tuner does than i'll ask for the files so we can compare. Still wanna know why this didn't work out :/

---

[quote="X-treme" pid='373218' dateline='1537421740']
[quote="Gabrola" pid='373213' dateline='1537419517']
[quote="X-treme" pid='373037' dateline='1537368847']


Also, don't read the hex string from Ncd Tool because it has a bug where the last byte in each NCD section is missing. Read it directly from the ncd in a text editor.  NCD files are in SREC (https://en.wikipedia.org/wiki/SREC_(file_format)) format and it is easy to read manually.

---

Yeah, found that already out 

[Gabrola]

Thanks for helping out man really appreciate it. I merged the eeprom just the way you did (found out too late that you did it already haha). But it won't work, still got the error that the dme needs to be coded and the variant config error.
The chiptuner already ordered a new ecu, because the customer got angry and wanted his car back asap. New ecu now car is fine. I won't open the new ecu to read it, but if the tuner does than i'll ask for the files so we can compare.  Still wanna know why this didn't work out :/

---

[quote="X-treme" pid='373218' dateline='1537421740']
[quote="Gabrola" pid='373213' dateline='1537419517']
[quote="X-treme" pid='373037' dateline='1537368847']


Also, don't read the hex string from Ncd Tool because it has a bug where the last byte in each NCD section is missing. Read it directly from the ncd in a text editor.  NCD files are in SREC (https://en.wikipedia.org/wiki/SREC_(file_format)) format and it is easy to read manually.

---

Yeah, found that already out 

Well yeah that sucks. Unfortunately, bad tuning files written through OBD can cause unrecoverable errors such as infinite boot loop. Only way to recover would be to open the ECU and do recovery in boot mode. It's still kind of weird what happened with your CAFD. Why don't you try to look at the ECU operating time through tool32 or ISTA and then search for that value or a value slightly greater than it in the eeprom dump?

[X-treme]

Well, the car did run, but only like 30 km/h. And guess what, this was read (by me) in boot mode. I think there is no other way to read/write the eeprom as full read. But what i don't understand is that his tool apparantely somehow managed to alter the wrong parts in the eeprom BY OBD. My guess is that it went wrong when patching the CVN. During writing the tune (via obd) the tool changes the CVN to the original value and modifies the programming counter so bmw doesn't immediately recognise that it is tuned. These values are also stored in eeprom so maybe this was where it went wrong in the first place.

[Gabrola]

Well, the car did run, but only like 30 km/h. And guess what, this was read (by me) in boot mode. I think there is no other way to read/write the eeprom as full read. But what i don't understand is that his tool apparantely somehow managed to alter the wrong parts in the  eeprom BY OBD. My guess is that it went wrong when patching the CVN. During writing the tune (via obd) the tool changes the CVN to the original value and modifies the programming counter so bmw doesn't immediately recognise that it is tuned. These values are also stored in eeprom so maybe this was where it went wrong in the first place.

I think it was running at max 30 km/h because in your CAFD VMAX was set to 0. CVN fix is inside the calibration file not the EEPROM, but yes programming counter is in EEPROM and it could have been messed up by new genius unlock due to conflict with magpro's unlock code. Magpro is a very good tool and is very well tested for f-series tuning, why car didn't start or be restored could be because of bad file or bad connection during flashing. What I think happened that caused is that when you write a tune for the very first time with any tool, it performs an ECU unlock, which I think it does by modifying some code in the bootloader. Different tools perform this unlock differently, whether it's magpro, bm3, new genius, etc. So what happened after VR was rewritten using new genius is that it did not detect that the unlock because it was done with another tool so it wrote it's unlock code in the bootloader on top of the unlock code by magpro, which caused a conflict and this corruption with your data. Only safe way to switch between different flashing tools or bm3 is to full flash (btld + swfl) the car back to stock using ISTA or E-Sys or use the re-lock/restore ORI function on the tool you used to originally write the tune before you make the switch.

[Dudi_1981]

Hi , any one know solution for this problem ?
We have exactly same situation
Thank You