Hi everyone

I need a bit of your knowledge to try to solve my problem with my motherboard bios.

A few weeks ago I updated the bios of my MB (MSI Z490 GAMING EDGE WIFI)

To my bad luck MSI uploaded a corrupted bios that basically causes brick on several z490 models

MSI support does not reach my country I had to use the CH341A tool to try to solve the problem

At first the MB turned on but marked CPU error (Error caused by the corrupt bios that MSI uploaded)

After using the CH341A tool, the MB does not give a sign of life, it does not turn on any LEDs or the fans turn

The bios flash process was achieved without errors with the CH341A tool so I have no idea what could have happened



*My English is not good , sorry :(

Dump the firmware again with your programmer, save it and post the file.

Whcih file did you use to flash?

Did you dump the spi before overwriting it (= did you back up the contents of the bricked bios)?

Use the bios that is published on the msi page

Before writing to the bios make a backup copy of the content

I have tried to write the firmware in the bios again but the result is the same

lfbe Asked u to share here or in a sharing host service the 2 files, the original corrupted backup and the a new dump of the new current flashed file.

I have used the "CH341A MINI 2.2.1.0" software, it is the only one I could find that works with the "MX25L25673G" chip.

All the processes the program performs without errors

I don't know what the problem could be, before using the CH341a tool the motherboard turned on the LEDs but after trying to write to the bios the motherboard is completely dead, it does not give any signal

He also tries to change the CMOS battery but still does not give a sign of life

Here I leave the backup of my bios and the current bios of my motherboard:

***Backup bios motherboard MSI MPG Z490 GAMING EDGE WIFI BIOS VER. 19

drive.google.com/file/d/1cKM-mr7M4HAfRib3Q0rSsWtaMd-fFPM4/view?usp=sharing

Current Bios:

drive.google.com/file/d/1FxjXeC5fsmGY_dAjT8KxGjl9esiChV3H/view?usp=sharing

The BACKUP (u named Backup bios corrupted) bios is v19... the last bios update on site is v18... and i dont see any mentions around the web about a beta or non-public version v19.
The dump (u named Current bios) of the current bios is v17...
Where did u get the v19 bios file?
U sure the SPI is an MX25L256(73G)?


This is from latest v18 from MSI page product support of the MPG Z490 GAMING EDGE WIFI:

Flash chips in VSCC table:
EF4018 (Winbond W25Q128)
C22018 (Macronix MX25L128)
C84018 (GigaDevice GD25x128)
EF6017 (Winbond W25Q64)
C22017 (Macronix MX25L64)
EF4017 (Winbond W25Q64)
C22016 (Macronix MX25U16)

The v19 MSI removed it because it was corrupt, the people who updated with that bios gave him CPU LED error and the board did not respond

I decided to put v17 because there are also reports that v18 gives some problems


But the result is the same, the plate still shows no sign of life


I leave an image of my bios chip

i.imgur.com/LteMsan.jpg

Strange... i read a bit about exactly the same issue u have in ur motherboard model with v17 only... but never found a user talking about a v19 bios... have u found any user with a v19 bios???
A lot, really a lot of MSI Z40 broken like urs... my only advice is to try other software for programming, theres plenty that works with that USB CH341A (Black one i presume...)
Flashrom, Neo programmer, Colibri...etc.
Search on the web or in the next 2 threads:

[GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!)
[Guide] Using CH341A-based programmer to flash SPI EEPROM

Good luck.

The bios V19 was online for a short time because it was a bios with errors, in the official MSI forum there are several people affected so many with the bios v18 and v19

This is the link to some reports

forum-en.msi.com/index.php?threads/warning-z490-boards-problem-with-recent-bios-updates.367575/



I have tried using other software but have not found any that support the "MX25L25673G" chip specifically

Only recoverable option here would be a bad flash. Therefore I asked for a fresh dump from your board to know what's inside this SPI chip right now. Don't rely on 'verify messages' ot that you 'think' you did the flash properly.

- Backup bios you linked is a stock bios, not a backup of a machine that has run before (NVRAM empty/ just standard setting, no machine specific data)

- Bios you claim being current bios is 100% identical to stock v17. If you really read it back (and did not just post stock bios V17) then reason for brick is no longer the firmware and we're finished here.

Use the CH341A MINI 2.2.1.0 software to read the stock bios and then hit the "save" button and create the .bin file that I uploaded.

To write to the bios chip I am using the bios that is on the official msi website

I don't know what I can be doing wrong, it's the first time I've tried something like this

Zitat von Hidenz im Beitrag #11

---

Use the CH341A MINI 2.2.1.0 software to read the stock bios and then hit the "save" button and create the .bin file that I uploaded.....

---

I bought a bios backup in vinafix thinking that my backup could be with some problem


But the result is the same, the motherboard is still completely dead, it does not give any sign of life


This time use the software "neoprogrammer 2.2.0.10"

-Is it possible that the bios chip has been damaged?

If so, is it possible that the motherboard does not show a sign of life?

When you can read/dump the content of the chip with the programmer in a separate process, save it to a new file and this file is a 100% identical to the original file you programmed, then the programming process is OK and the chip is OK, too.

Apparently the data is the same

The bios chip when connected, the programmer receives and writes data

What seems strange to me is that the board does not turn on any lights, the fans do not turn

try

-buy a new CMOS battery


-Test the power source by bridging

-Test the font on another PC and it worked


The board turned on before using the programmer but after using it it no longer turned on


Are these symptoms possible due to a damaged or badly programmed bios?