WINFKP 2005 320i - can't find ECU family

[frenzix]

Hello,

I have been trawling through posts and trying out different suggestions but have come to a brick wall.

I have imported the e89 DATEN files, the vehicle is a 2005 320i e90.
When I get the identification details on INPA - it states that the DME is MEV9N46L part number 7565300.

Should I be using a different DATEN pack? or am I doing something else wrong?

All I need to do is to change the VIN on the ECU to match the vehicle (original ECU was damaged and can't be read).

Thanks,

[wjgud123]

Hi

Did you correct import all files, also update winkfp + assembly line?
I check my daten and I have pn: 7565300 under MV946

img.PNG

Repeat all steps with update WinKFP and assembly line

[frenzix]

entries.txtHello, yes, I have just imported all of those files again, what daten file are you using ?

Thanks for the help..

- - - Updated - - -

Sorry, just checked the daten RAR and the imported files and that file is in there.. but doesn't show on WINFKP

I have uninstalled EVERYTHING and reinstalled and imported all the daten files again, still exactly the same result.
This time I though to try and log into the ecu anyway using MV946, and was able to get in and reset the VIN. It looks like I was successful although the car still isn't starting and throwing up the following errors;

ECU errors stored.JPG

[frenzix]

Here you can see the updated entry in number 4.

Entry 3:


Vehicle identification number: WBAVA76070NK16009
Date: 07.11.2007
Change index:
Software number: 7568657
Office number: 7528590
Assembly identification number: 7568658
Seral number: 12345
Program number: 0087360T410B
Kilometer: 43200
Dealer number: 011111


--------------------------------------
Entry 4:


Vehicle identification number: WBAVA72010AH22855
Date: 01.02.2020
Change index:
Software number: 7600315
Office number: 7528590
Assembly identification number: 7600272
Seral number: NFS01
Program number: 0087360T410B
Kilometer: 0
Dealer number: 000240


--------------------------------------
End of user info field

[wjgud123]

Hi

So: 2F44 is error with immobiliser system.
Did you syncronize new DME with EWS? Immobiliser cannot recognized ecu and prevent start engine.

[frenzix]

Hi

So: 2F44 is error with immobiliser system.
Did you syncronize new DME with EWS? Immobiliser cannot recognized ecu and prevent start engine.

Ahh interesting. No I didn't. Can I do that through INPA ? Thanks for the help.. really appreciated. If I can get this going, I'm going to donate !!

[328 Power 04]

Did you copy the original DME ISN to the donor DME?

VIN has nothing to do with not starting, it's all about the immobilizer.

[wjgud123]

Did you copy the original DME ISN to the donor DME?

VIN has nothing to do with not starting, it's all about the immobilizer.

I think he don't have AutoHex or FVDI to read and write ISN in module; so probably ISN isn't copied.


However here is how to make sync in inpa; in ISTA is much easier :p

Re-align the DME and EWS


How you do it?


1- Launch inpa
2- Select the engine
3- Choose the model of the engine
4- Select option: activate (usually F5 but check in your inpa)
5- Select option: EWS
6- Select option: reset ----> in progress ----> click ok
7- Bak to the main menu, ie, back, back, back, and close the INPA
8- Open the inpa and check the errors. That errors should have gone by now.
9- Turn the ignition off, remove the obd connector and start your car.

[328 Power 04]

You can't sync EWS on that car/module if you don't copy static ISN from original module, or virginize the MEV1746 ** (edited).


EWS sync won't work.

[frenzix]

Thanks. The old DME was water damaged and it couldn't be read. How can you virginize the ME9.2?

[328 Power 04]

Do a boot mode read (KTAG, or other tuner interface) of the complete memory, and then send it to me or anyone friendly to virginize it. After that, write the data back and it will accept an EWS sync from INPA.






Confirmed: the MEV1746 isn't capable of virginize nor EWS sync. It uses long ISN SK (128-bit).

If possible to get any kind of read from the original DME, then it would help. If not, you have to get a read of the CAS (it may be encrypted), and transfer ISN to DME.

[TerraPhantm]

Confirmed: the MEV1746 isn't capable of virginize nor EWS sync. It uses long ISN SK (128-bit).

Huh, I thought EWS4 wasn't a thing until MY2008 or so.

[328 Power 04]

Maybe, I found it odd too, regarding the dating of it. I found a few tricore reads from a mev1746 and I will see if I can find ISN, but searches only revealed 128-bit SK.

It would be great if it could be virginized, but i haven't found any mentions of it.
My home computer will know more.

[frenzix]

Do a boot mode read (KTAG, or other tuner interface) of the complete memory, and then send it to me or anyone friendly to virginize it. After that, write the data back and it will accept an EWS sync from INPA.






Confirmed: the MEV1746 isn't capable of virginize nor EWS sync. It uses long ISN SK (128-bit).

If possible to get any kind of read from the original DME, then it would help. If not, you have to get a read of the CAS (it may be encrypted), and transfer ISN to DME.

Thank you for all of this information. I feel as though I'm having a crash course on reprogramming the DME.. it's great.
by KTAG, is that included in the INPA or Easy BMW Tools package? pardon my ignorance, I just looked KTAG up and it seems like seperate software or equipment. Can I just use my current Interface cable?

Cheers,