@ibsajc - Great to hear you've got it all sorted out now!
I use UEFITool 51 NE, side by side with stock BIOS (extracted from Capsule in Asus Case) vs mod BIOS. and then check ALL volumes which you touched (in this case =1) and make sure all match inside module-wise, no added or removed padding or other modules
Also make sure "Parser" tab at bottom matches, and "FIT" tab When doing other edits, also always check any sub-volume you touch just like I mentioned above. Plus always double click on FIT first entry and it will take you to FIT location in file, make sure padding above/below it always same before and after
Then search GUID >> 17088572-377F-44EF-8F4E-B09FFF46A070 << This = microcode volume/s, some BIOS have 1, some have 3-5, when several usually one is empty. Anyway, compare all these locations side by side, make sure padding is above, in before, after, or not, side by side - should always match.
Other than that, I'd have to explain specific issues, things to check on case by case basis per some specific edit. The above is my general, always check all this, before/after for all mod BIOS.

Anytime you see "Parser" differences, or an added or removed padding, or non-UEFI/Pad file, that can = bricked BIOS, sometimes, but not always, and only way to know is test flash, so not ideal unless you have programmer.
So, in such cases you find issue, work around, use other tool, other method, make sure it does not happen
Also, any time you see FIT blank at mod BIOS side, or partially blank, vs stock (Which should not be blank, but sometimes manufacturer ), that should be fixed as well
Here in-depth guide to fix, I need to update, there is easy way now

Been reading these forums for the past couple of weeks so I can try and fix my MSI Mortar b350. There has been some really useful information, so thanks!

I've managed to get a programmer (CH341A + 1.8v adaptor) and flash a file using flashrom which completes and verifys i've successfully flashed something but my computer still doesn't post.
The chip is MX25U12873F but identifys as MX25U12835F in flashrom and CH341A.

I want to double check the image i'm trying to flash is correct. I tried downloading the latest non beta bios from https://www.msi.com/Motherboard/support/B350M-MORTAR, extracting the bios file and flashing that. I then thought perhaps this file was just an update rather than the full bios so I tried v1 which still doesn't post either.
Is anyone able to confirm that these are the right images or perhaps provide me with one?

Alternatively do you have any ideas why the computer turns on but just has a locked CPU led and doesn't post. The GPU briefly spins up but then stops.

@Lost_N_BIOS
Regarding #571 thanks again for your advice.
For now, I think I will stop with the BIOS mod to have time to deepen what I know.
Updating the microcode version in BIOS from what I read in your link is a bit more complicated and my working principle is to choose the safest and easiest way.
There are other solutions related to updating the processor microcode (I am now speaking as a network administrator):
1. in Windows there are already installation packages (.msu) for Intel microcode updates depending on the type of processor (CPU ID) here. They can be downloaded here.
2. Linux has a specific microcode update mechanism at system initialization (initrd-early loading) extremely easy to use.
https://www.kernel.org/doc/html/latest/x86/microcode.html
For both operating systems this solution does not involve any risk, both can be brought to the initial state, by uninstalling the update in Windows or removing it from the initrd in the case of Linux.

@bib - For MX25U12873F use one in folder of package below named >> CH341A v1.31(1.4) (CH341AFree), be sure to choose correct chip type (25) and size before you start doing anything.
http://s000.tinyupload.com/index.php?fil...213094641136166
** And, see also, this post about version/method, see end of post #126, (DO do the erase, he already did is why he skipped) - https://www.badcaps.net/forum/showpost.p...5&postcount=126

Send me your original dump of BIOS chip from BEFORE you did anything, so I can compare to the stock BIOS and see if those are partial or full BIOS files.
The downloaded BIOS from MSI looks complete, but I don't look at AMD as often as Intel, so I can't be 100% sure without seeing dump from your board first.

@ibsajc - You're welcome! The more you play, the more you learn Yes, updating microcode can be tricky sometimes, several ways to do it, but the guide I linked was more about fixing FIT after that.
Other times it's simple, use MMTools and confirm FIT OK, then confirm all rest OK and you're done. All depends on the BIOS.
No one wants windows controlling microcodes, plus Win10 already does it automatically if you don't use a newer one than theirs in BIOS, or disable them from being able to do it.
Linux, yes, you can do similar, if you want.

@Lost_N_BIOS https://filebin.net/8mnop6k6mw6vneqi/backup.bin?t=m0ztlskg

Chances are this file is broken in some way as it was taken when I think my clipper cables were too long as I couldn't get a clear write. Since shorterning the cable i've been able to get verifys. I just ran a flash using CH341A 1.31 free and it wrote but failed to verify. Booting gave me no beeps and just the CPU led showing with no post.

I'll try another flash.

Flashed and verified but still doesn't post or beep

@bib - Do you have power cables connected, or not? If yes, remove them, if not, try with them connected. Some boards need one way or the other, sounds like you may be running into this issue because 1.31Free has been confirmed working for this BIOS
To confirm your write is actually OK do this >> Select correct chip type (25) then correct size, always do that first.
Then >> Erase chip, blank check, then open BIOS file, write, verify, then close the program. Open, pick correct size/type, read, verify, save and compare that saved file with what you wrote in hex editor, if 100% match then write is OK

Flashrom also works, here is Linux/Ubuntu method/guide - [GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!)
And here is Windows version someone made (post 510) - [Guide] Using CH341A-based programmer to flash SPI EEPROM (34)

Yes, your dump is corrupted, from bad dump method (wrong software, version, setup for the board/BIOS as mentioned above re power), not from bad BIOS flash
BIOS download does look like a complete BIOS though, I just hoped to double check to confirm with your dump, but that's not an option now.
I'm 99.999% sure it's bootable 100% complete BIOS on their site, pretty much confirmed by others recovering similar MSI B350's in google via programmer using stock BIOS

Thanks, i'll specifically try the power cable approach later today and do a dif of the rom to the dump.
I have tried cable in and outs before but only when using flashrom in Lubuntu, so i'll try it again with CH341A in Windows.

I've probably flashed the chip 20 times now between flashrom and CH341a, so i'm fairly comfortable with the flashing process.

The original dump was taken with flashrom, which detects the chip. I'm fairly sure the issue was cable length, as I kept getting errors when verifying and once I shortened the cable this stopped happening.
------------------------------------

Interesting. So CH341a verified my write with the file I was flashing but doing a diff there are empty blocks, missing parts from the original.
I tried that just now with nothing connected to the computer for power.

Previously I did have an issue where cable length seemed to effect writing but since shortening the cable, verifies started work

------------------------------

Re-reading and saving gives me a different dump, that had far fewer differences.... So I can't be sure that it's actually reading it correctly.

Interestingly starting the computer gives me behaviour from when I tried to do the first flash.
Computer turns on briefly, CPU led comes on and then CPU fan slows down and then seeds up with led going on and off.

Taking all sticks of ram out makes it beep.

So perhaps the flashed has worked now and something else is bust.

@bib - see my edit at 574 - And please use edit instead of making multiple posts in a row - thanks
Detecting the chip, and looking like OK operation does not mean anything, if not compatible, read or write can verify but still be corrupted << As you just notice happen
When you do dump to compare like this, make sure you close the app, then re-open, and DO NOT try to power on system between write and this read/verify/save to dump and compare.
Yes, it's possible something else is bad, but I would try again until you can get a write, then a manual dump/compare to work 100% properly, then you will be 100% sure the BIOS write was OK.
See my edit above about 1.18 (and note what I mentioned, always do erase then blank check, he didn't erase before blank because he did it previously)

Thanks. I've now tried another motherboard and it behaves in the same way with CPU led on and computer not posting and restarting. Think the CPU might be broken so I'm starting a warranty request. Thanks for your help.

@bib - Sorry to hear CPU may be dead! But, maybe that is good, you will get new CPU and board will be OK once programmed again.
The new board, was it's BIOS up to date, and should be OK with the CPU you tested? If yes, then as you mentioned, probably bad CPU

I didn't run a bios update on the new motherboard but it was from the same generation as the processor b450. So it would have been compatible out of the box.

I'm hopeful that I've managed to return my old motherboard to its original state due to it behaving the same way as before I started flashing it. However you might see me back in a few weeks.

@bib - That does not always mean compatible. Check the BIOS version and CPU QVL list to be sure it should be compatible, before you decide for sure it's dead CPU.
Yes, please stop back in once your other CPU arrives to let us know how it goes

I was in a process of upgrading my X9SRL-F BIOS using CH341a programmer because couldn't be able to upgrade the BIOS through normal means or Recovery mode by creating SUPER.ROM. I managed to get the image dump from the corrupted X9SRL-F bios, but also i have similar motherboard as a spare just in case i loose my current motherboard with image dump taken from it also. i was in a process to follow this guide https://forums.servethehome.com/index.ph...slm-ln4f.27652/ . which he stated that at the end “At this point I downloaded the latest bios update from supermicro website and opened the file in the programming tool” that means he didn’t do any modifications and everything went well. My questions:

1- Can I download the latest image from supermicro support and flash as it after erasing the bios?
2- Can I flash an image taken from identical motherboard without modification?
3- if none of the above what is the best methods available?

Hey @Lost_N_BIOS ! I hope you're doing well. I don't know if you remember me, but I accidentally broke my BIOS. Here's my original post:

Zitat von ToxicCow19 im Beitrag #532

---

Hi! I had a problem with the BIOS on my laptop, it’s a Lenovo Y700-15ISK. It got corrupted after changing the secure boot settings and now it’s stuck in a boot loop.

I watched a video on reflashing UEFI BIOS and apparently you have to extract the motherboard’s serial number, UUID, and MAC address from the old image and then inject them into the new image. The problem is that in the video they use the FD44Editor for Asus boards, but obviously my board isn’t Asus.

My BIOS is an InsydeH2O UEFI BIOS. Is there a tool to extract and edit such numbers or can I do it with a normal hex editor? And if so, what should I look for when using a hex editor?

And second question, my BIOS update file comes as an .exe. How can I extract the bin or rom or fd file from there?

I’m still waiting for my ch341a to arrive, so I want to learn as much as I can in the meantime.

Thank you!

---

Zitat von Lost_N_BIOS im Beitrag #559

---

Maybe eventually @C:/con/con will reply back, and if he has board still and sends dump, then we can see if two MAC ID"s in his or if only one in BIOS and one in FW etc

---