Here comes the similar problem:
BMW F30 after desoldering 95128 eeprom all data lost (maybe overheated). Using xhorse vvdi prog and vvdi2.
In new eeprom i wrote data from another FEM but car now starts only from the emergency coil, remote did not works.
i try wrote many dumps from another fem. update FEM with ISTA , but remote still not working.
Tried to desolder with hot air, the eeprom may have been damaged.
Is it possible to restore data? What is the procedure to recover the FEM? Or do I need to buy new FEM?
Solution:
NO NEED TO BUY ANY NEW FEM.
Find any 95128 dump make all programming FEM with vvdi2.
Restore coding
Now in car key must start only from the emergency coil.
next
At first read isn by vvdi from the working key.
Erase key with vvdi.
Dissemble key.
Renew key by vvdi key tool or vvdi prog.
Program “old” -new key with vvdi2.
Also if it is manual gearbox you will need to virginize the elv.
AND ALL !!!!
You can also restore FEM with autohex, same procedure as above.
For the guys wondering why when a FEM flash fails you cannot fix it.
FEM has 2x SWFL, they control the ignition, if both SWFL become corrupted then the FEM does.
not know when and how to cycle the ignition, this is why you hear the relays clicking, if the bootloader is ok you may be able to restore the SWFL by updating istep, if the BTLD is corrupted then its likely a new FEM
if only 1 SWFL is corrupted and the other is ok then the FEM can be restored.
You also have other ways to program BMW FEM key, via clip solder free adapter or with bench test platform.
For example:
Program BMW F30 FEM All Keys Lost via Godiag
User feedback:
Car worked after writing file to new eeprom. Vvdi2 also let me correct the mileage.
2010 Ford Transit Mk7 all keys lost and active Cat1 factory alarm.
Key learning cannot be carried out by normal OBD operation with alarm active as key learning by OBD is blocked.
Removed BCM, read key data (chip MC9S12DG256) directly from the module using xhorse vvdi prog on the bench, added a new key on the bench with xhorse vvdi2, installed BCM back to the van, switch ignition on with registered key and alarm is deactivated.
Now we can erase all keys and add new all by OBD.
How-to: read EDC16U1 ECU CS, MAC code, change km and IMMO Off using Xhorse vvdi2 programmer.
Run vvdi2 software
Select VW program
Go to Special Function-> Engine Control Unit
Read memory data
Detect type as EDC16U1
Read CS and MAC successfully
Input KM you desired to change and press write KM
Switch ignition OFF for 5 seconds, then switch ignition ON
Write KM successfully
Select IMMO OFF
Switch ignition OFF for 5 seconds, then switch ignition ON
IMMO OFF with vvdi2.
Switch ignition OFF for 5 seconds, then switch ignition ON
2017 VW Jetta keyless NEC 24c64+MQB couldn’t read data with cluster in service mode by pogo pin with Xhorse VVDI2, had to read eeprom and write eeprom in service mode back but after had to turn ignition on to write original file. Figured you can hotwire few fuses together to turn ignition on without key.
I did dealer key myself with data I read of a car, the key I used is Xhorse Mqb universal smart key, I’ve just put vw logo on it.
Make sure you buy one with marking XSMQB that S stands for smart
Easy Job!
Today I have an instrument cluster from 2018 Audi Q3 with all keys lost. What I’m going to do is to turn the odometer on and extract immo data with Xhorse VVDI2. Once getting the immo data, I can make a key.
Let’s go start disassembling this cluster.
Connect the dashboard to VVDI2 programmer.
Open VVDI2 software to login.
NOTE: The dashboard will remain dark until “Reset Instrument”.
Reading data, please wait…
User “Reset Instrument” to active instrument after all the operation is finished.
Reading data success.
Save EEPROM data file.
Read IMMO data.
Save IMMO data file.
Now I’ve successfully got all immo info including VIN, CS, PIN, MAC and keys. With the file so that I can continue to prepare key and make dealer key.