MSI Claw 8 AI+ A2VM — Second Fan Stopped Working After BIOS Update (EC 255.255)

[lalala333]

Hello everyone,

I need help with restoring the EC (Embedded Controller) firmware on my MSI Claw 8 AI+ A2VM handheld console.

Situation:

I purchased an MSI Claw 8 AI+ A2VM (Serial: A2VM-027CN-BSU7258V32GXXDX11NGCP).
Out of the box, both fans were working, but always at 100%.
I wanted to update Windows and BIOS to improve fan control.

What I did:

Updated Windows 11 and installed all drivers from MSI’s website.

Installed MSI Center M.

Following advice from Reddit, I updated BIOS/EC firmware separately using MSI’s official file:
E1T52IMS.10F (2025-09-26)

After the update, the second fan stopped working completely, and the EC version now shows 255.255 in BIOS.

BIOS reports:

BIOS Version: E1T52IMS.10F
Mainboard: MS-1T52 Rev 1.0
EC Version: 255.255

I reinstalled Windows clean, reset BIOS, tried EC reset — nothing helped.

The seller sent the BIOS zip file, but it contains only .CAP, .INF, .BAT — no EC, and flashing it gives “wrong model name image”.

Current status:

Only one fan is working (at 100%).

Second fan does not spin at all.

EC in BIOS = 255.255.

Device overheats under load.

Questions:

Does anyone have a working EC firmware dump (.bin or .rom) for MS-1T52 Rev 1.0 board (Claw 8 AI+ A2VM)?

Is it possible to restore EC using a programmer (SPI/CH341A) or MSI EC flashing utility?

Can someone share the EC chip contents from a working Claw 8 AI+?

Additional info:

I understand that BIOS ≠ EC, and the EC controls fans, power, and other system functions.
Flashing the BIOS from MSI only updated the BIOS — the EC seems corrupted or mismatched.
Official EC firmware files are not available separately.

Request:

If anyone owns the exact same model (MS-1T52 Rev 1.0, A2VM), please:

Create an EC dump using a programmer or service utility.

Even a partial dump or EC version info will help understand what should replace “255.255”.

Thank you in advance for any help
Any information — EC dump, instructions, or confirmation that this issue exists — is highly appreciated.