[BimmerExperts]

You can repair these units witj any programmer avaiable on the market.
Upa, smok jtag, vvdi prog, xprogm, etc.
Read dflash, extract eep from it, make partition again in MCU, write eep, done.

I’m sure it will be fixed with another programmer, but I’d like to just use hexprog for its ease of use. That’s why I’m trying to see if my issues are singular to my specific hexprog or if anyone else has been having this issue, that’s really the reason for my post not necessarily fixing the frm’s that haven’t been fixable.

---

I think there are some steps missing the way you`re doing.
when you read eeprom and get pertition 94e or similar you have to read p-flash first and then click on the repair option. then you get VIN number and message that it has been repaired.
Then don`t read eeprom straight after repair as you will get strange message that you use wrong version or something (this started happening for me a few month ago with some new Hexprog updates, but Microtronik never explained why)
what I do after repair message I go from the FRM menu and then go back to FRM3 and the read eeprom and always it works for me.

Hello, has anyone been having issues with FRM3 repair using Hexprog? Hexprog support hasn't really explained why this happens and are not providing solutions, I'm most likely going to purchase another tool to repair frm's but figured I'd ask here to see if anyone else has been having the same issue.

Connect Hexprog to dead frm3
Read eeprom
Partition 94e error
Click repair, repair completes and Hexprog shows car's correct VIN
Click read eeprom (I do this to confirm eeprom populates and in fact repaired)
Partition error 94e again
Click repair again, hexprog says complete but shows yyyyyyyy for vin (still gives partition error 94e when trying to read eeprom)
I try loading eeprom dump manually to frm using hexprog, hexprog goes to 100% and says complete. Read eeprom and partition error 94e again

This has happened 3 times so far, out of probably 40 repairs with the tool. The last 2 of the 3 though have happened in the last few weeks. My old xprog is not working so I haven't confirmed if these specific frm's are repairable with another tool yet.

Partition error 94e is completely normal for frm3, that’s just confirming there is an eeprom issue with the frm3 and it’s dead. Reading pflash and then clicking repair is no different than clicking repair first. Repair function doesn’t touch pflash.

The issue you’re talking about after clicking read eeprom after repair is normal too, I saw it after the tool forced you to go online instead of using offline. It says cannot get data from server or something but if you click read eeprom again after that error it’ll read eeprom. The frm3 is physically still dead which is the issue, the program should not be giving partition 94e errors after repaired correctly and i don’t know if it’s an issue with my hexprog specifically since I bought it when it very first came out, issue with them forcing the tool to go online or if it’s a common issue that everyone else has been experiencing too.