banner



Can An Amibios Be Repaired/rebuilt?

Jump to forum

Howdy there,

Recently I flashed a BIOS update to my M5A88M-EVO board (AMI BIOS) using the linux tool flashrom. However, that appears to have been a fault on my part, as the flashrom tool apparently overwrote the lath'south MAC address for its onboard ethernet, its serial number etc.

I searched effectually this forum and saw that some of you wizards are apparently capable of modifying the BIOS image to include the right values for a specific board, as long as you are provided with the pertinent numbers.

I have attempted to include as much information nigh my board as I could in the M5A88M-EVO_files.nil zipper (a copy of the BIOS that contains bad values and needs to exist modified, output of lspci -vvnn and dmidecode) and I've attached pictures of both the box w/serial number, the wink chip and the series number on the board (a bit blurry, but information technology matches the series number on the box).

I was lucky enough to accept saved the board'due south onboard MAC accost in my router'south DHCP charter table besides as its wake-on-lan tabular array. The "existent" MAC address is f4:6d:04:59:07:f1. Currently, I'm forcing said MAC address in my systemd-networkd configuration (Exherbo Linux).

Information technology won't be a trouble to flash the modified BIOS containing the correct values to my board equally I can just use flashrom once again.

I hope some kind soul here will be able to assistance me fix this mess.

All the best from Aarhus, Denmark.

ermo has attached images to this mail


Linux daily driver: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph Two X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


go to top Scroll up

You tin can open up your Bios file with UEFI Tool and look for GUIDE with starting proper name FD44820B.
Excerpt body of its raw department.
There you put all wished values for MAC, UUID, serial in and load information technology upward again. That all.
These are but fake numbers,
but compi gives you the feeling, that there is only one compi in world with this values
Dietmar

PS: This works just for newer ASUS AMD Bios.
On Asus boards, you can also use the tool FD44Editor.exe.

EDIT: I just endeavor it for your lath. It does not work. The only idea I have is,
to look for a full Bios excerpt from a working board and compare it with Hexeditor with a new Bios (same version) file.
In the full Bios extract you can search with Winhex for the 6 MAC Hexvalues (12 digits).

EDIT2: May be it is in your Bios starting from adress 0013E97C (xvi Places with FF need to exist filled with UUID, Mac adress at the terminate of UUID).


become to acme Scroll up

Need images of all stickers on your lath, be sure to look on side of 24pin and all top/bottom sides of PCI/PCIE slots too.
The "Serial" shown in your starting time image is not ever the same one they put in BIOS, depends on board series and what Asus is doing at that time. Sometimes the BIOS serial is made from a "Standard" set up of starting digits, or mm/yy of manufacture + some digits from the long white sticker.
The sticker with MAC address is missing in the in a higher place images, it's often on the 24pin or SATA slots. Are you certain that is correct MAC yous mentioned? If you are not certain, ostend on this sticker

You made a backup earlier you flashed incorrectly, or non?

What is the current invalid MAC address, all zeros or all FF? Sorry, the txt file you included that may contain this info are a mess

If the higher up fails for the MAC, I've asked someone to give me their MAC, Serial etc, and I already have their dump, from a similar board, so I will hopefully be able to give you lot all the correct locations and formats for the data soon

Comparison what @diderius6 mentioned above @0013E97C with some other CH341A dumped BIOS and I meet same FF's in all locations at this area, and so I don't think whatever of those FF'south demand to exist changed, this is not right location
Notwithstanding, you can test, maybe that dump I am checking was incorrectly flashed with stock BIOS earlier the user redumped with CH341A? It'south possible, and would cause that to exist all FF likewise

Edit by Fernando: Lost_N_BIOS hasn't been online since Jan 2022.


become to top Scroll up

Zitat von Lost_N_BIOS im Beitrag #3
Demand images of all stickers on your board, be sure to look on side of 24pin and all top/bottom sides of PCI/PCIE slots also.
The "Serial" shown in your kickoff image is not always the same one they put in BIOS, depends on lath series and what Asus is doing at that fourth dimension. Sometimes the BIOS series is fabricated from a "Standard" set of starting digits, or mm/yy of manufacture + some digits from the long white sticker.

The sticker with MAC address is missing in the in a higher place images, it's often on the 24pin or SATA slots. Are you certain that is correct MAC you mentioned? If you lot are non sure, confirm on this sticker


I'm sure.

But I need to change the cooler on the board since it'south as well noisy under load (Exherbo is a from-source Linux distribution, so I compile packages all the time) so I'll pull out the board from the case and have a good look around.

EDIT: Uploaded a photo of the MAC sticker in the 1st post. The MAC accost matches what I wrote.

Zitat von Lost_N_BIOS im Beitrag #3
You made a backup before you flashed incorrectly, or not?

Sadly no, which was very sloppy of me.

To add together insult to injury, ASUS's official 1901 download is actually the 1401 BIOS version (I haven't contacted them nearly it though).

I institute the proper 1901 version elsewhere.

Zitat von Lost_N_BIOS im Beitrag #three
What is the electric current invalid MAC address, all zeros or all FF? Pitiful, the txt file you included that may comprise this info are a mess

The files were created on Linux. Then you lot need to employ Unix line endings for things to look nice in a Windows text editor.

The invalid MAC accost is

ed:0b:00:00:e0:00

(line 8 in the bad_default_MAC file).

Zitat von Lost_N_BIOS im Beitrag #three
If the above fails for the MAC, I've asked someone to requite me their MAC, Series etc, and I already take their dump, from a like board, so I will hopefully be able to requite you all the right locations and formats for the data soon

The invalid MAC and Serial numbers are as well shown in the dmidecode_output file (once more, utilise Unix line endings to read the file).

It looks equally if the Ethernet card Serial number (line 512 in lspci_output) should be changed from

00-00-00-00-00-00-00-00

to

FF:<re-ordered MAC>:FF

I think?

Looking at another lath (an M4A78E-SE where it seems I've besides used flashrom and inadvertently clobbered the serials), it seems the order needs to be switched around a bit:

MAC

00:e0:12:34:56:78

becomes Ethernet menu Serial

ff-34-56-78-00-e0-12-ff

-- so perhaps that is useful to you?

The lath serial number on the stickers is a 12 grapheme cord.

In the dmidecode_output file (line 59), the board is given a xiii character default Serial cord, which is represented equally

MB-1234567890

where I'chiliad guessing the nuance "-" is something dmidecode adds.

On that footing, it might be prophylactic to just insert the board series number from the stickers?

Zitat von Lost_N_BIOS im Beitrag #three
Comparing what @diderius6 mentioned to a higher place @0013E97C with some other CH341A dumped BIOS and I encounter same FF's in all locations at this area, and then I don't retrieve whatsoever of those FF's demand to be inverse, this is non correct location.

However, y'all tin exam, perchance that dump I am checking was incorrectly flashed with stock BIOS before the user redumped with CH341A? Information technology'south possible, and would cause that to exist all FF too


This BIOS editing business concern is all gobbledigook to me at this point -- I'm request you wizards for aid because I don't know how to do this myself (and I very much appreciate the input you have already provided!)


Linux daily driver: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph 2 X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T Be, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


get to top Scroll up

The MAC number ed:0b:00:00:e0:00
is not in your Bios readout
Dietmar


go to summit Scroll up

Zitat von diderius6 im Beitrag #5
The MAC number ed:0b:00:00:e0:00
is not in your Bios readout
Dietmar

Scheiße.

How about 00-00-00-00-00-00-00-00 (which is the decadent/empty ethernet series number)?


Linux daily commuter: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, Loftier Sierra | BeBox: Ph 2 X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


become to top Scroll up


Linux daily driver: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph II X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


go to top Scroll up

Some BIOS the MAC is at end of UUID, others information technology's not, and some when it is the UUID or MAC can be inserted in various ways non straight forward.
No one can locate 00-00-00-00-00-00-00-00 in a BIOS, that would give 1000's of results

What you mentioned about your text files helps me none, deplorable.
Ideal solution to detect verbal locations of this is a known dump from a board that has not been messed up, since all this varies wildly in how Asus puts this info info BIOS for each series.

Wow, larger images are needed J/K Hither, delight exam this and allow me know how information technology goes
http://s000.tinyupload.com/index.php?fil...595303120890739

If this does non work, until I tin can detect a proper backup from this serial, you tin effort this method
https://www.biosflash.com/e/bios-error-messages.htm

Edit by Fernando: Lost_N_BIOS hasn't been online since January 2022.


go to peak Scroll up

Here is the file compare between the 2 bios
Dietmar


go to top Scroll up

Yes, I could have gave that info (Since I added information technology)?? So, did information technology work, can you lot use LAN now or nevertheless no?

Edit past Fernando: Lost_N_BIOS hasn't been online since Jan 2022.


go to top Scroll up

Flashing the modified BIOS resulted in the motherboard starting upward in ASUS CrashFree BIOS where it wants me to recover a working BIOS via either a USB stick or a DVD.

It's getting late now, but I'll attempt doing a CMOS reset tomorrow and meet if that helps whatever. If it doesn't, I'll have to somehow get the board working and then re-flash the 1901 BIOS I used before.

Cheers for the help so far -- much appreciated!


Linux daily driver: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph II X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Fill-in Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


go to top Scroll up

Sorry about that! Approximate that method is a no-go. Yes, you will need to recover BIOS again, and clearing CMOS volition not set this.
Hopefully y'all can recover BIOS from USB

I still tin't find a proper dump from this exact model, or even one from the same series/similar model That is all we need to fix this, actual dump from any M5A88M or M5A88xx etc

Edit by Fernando: Lost_N_BIOS hasn't been online since January 2022.


get to top Scroll up

No worries mate -- I accept recovered the BIOS and am writing this from the recovered system.

FWIW, the board runs OK nether Linux every bit long equally I manually specify the MAC accost in the systemd-networkd configuration files. So it's working for at present -- it'd just be more than convenient if I could at to the lowest degree recover the MAC address. The UUID and the Arrangement Serial are generally cosmetic for my purposes, but information technology'd be nice to accept them restored in any case.

For time to come reference, information technology turns out the BIOS didn't like FAT32 drives, then I had to create an oldsk00l 512MB FAT16 partitioning (to keep the cluster size reasonable) on my 4GB USB bulldoze before the CrashFree3 BIOS recovery function could actually read information technology.

I created a backup of the currently running 1901 BIOS before I attempted to flash the modified BIOS. And then it was as simple as copying the backup to the root of the FAT16 USB drive, re-naming it M5A88MEV.ROM and then booting up the stricken board with the USB stick inserted in a USB port and permit the CrashFree3 tool do its thing. Pretty painless really.

As an aside, I remember the days when I had to offset up some other lath in DOS, remove its BIOS chip while it was running, insert the corrupted BIOS chip, flash it and then re-insert the original BIOS chip and move the newly recovered BIOS scrap to the stricken board. "Fun".

As an bated, I've also cropped and resized the sticker photos in the OP per your tongue-in-cheek comment. Sorry for uploading huge pictures in the first place; I originally just copied them from my 1+3T without editing them.

Thanks again for your efforts!


Linux daily commuter: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph II X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


go to top Scroll up

Glad you lot recovered! Deplorable again also, that always sucks!

I need to find a dump from this series before we can set up properly, if you find i let me know. Hey, you caught my comment I e'er say it out loud hither, people upload 3-5MB epitome but to show a BIOS setting sometimes, drives me crazy somedays I get a 60MB package only to run across v images

For at present, on the MAC, did you try what I linked in post #8? This often will gear up it on some systems.

Edit past Fernando: Lost_N_BIOS hasn't been online since January 2022.


go to peak Scroll up

Zitat von Lost_N_BIOS im Beitrag #14
Glad you recovered! Distressing again as well, that always sucks!

I demand to find a dump from this series before we can fix properly, if you lot find ane let me know. Hey, y'all defenseless my comment I always say it out loud hither, people upload iii-5MB image just to show a BIOS setting sometimes, drives me crazy somedays I get a 60MB package just to run across 5 images

For at present, on the MAC, did you try what I linked in post #8? This frequently will prepare information technology on some systems.


Re. mail #8, I'1000 not certain I quite understand what else information technology is you want me to endeavour in that location, apart from trying to flash your modified BIOS (which went all pear-shaped)?

What am I missing?

And where would you propose trying to solicit BIOS dumps from working M5A88-M EVO boards?


Linux daily driver: FX-8350, 32GB, HD7970, Solus/KDE | Linux laptop: i5-430M, 4GB, iGP+HD5470, Solus/MATE
Linux Solus dev: FX-8350, 16GB ECC, GF GTS450, Solus/KDE | Linux toy: FX-8350, 16GB ECC, HD6570 + iGP, Exherbo/Xfce
Hackintosh: i7-2600K, 32GB, HD7970, High Sierra | BeBox: Ph Ii X4 955BE, 8GB, HD5770, Haiku
Wintendo: R7 2700X, 32GB, 2x RX Vega 64 (air), W10Pro | HTPC: Q9400, 8GB, GF GT240, Solus/Budgie
Server: PhII X6 1090T BE, 8GB ECC, iGP, F30/Srv | Backup Server: PhII X4 940BE, 8GB ECC, iGP, F30/Srv


become to tiptop Scroll up

Please enter a reason for alert.

Reason beneath posting.

{[userwarning_empty_error]}

The reason mentioned in a higher place will exist used. Click hither, to arrange the content of the private message.

Define the content of the pm-notification here.

Source: https://www.win-raid.com/t4981f16-REQUEST-Help-adding-back-MAC-address-and-board-serial-number-in-AMI-BIOS-file-for-ASUS-M-A-M-EVO-board.html

Posted by: scottlaing1940.blogspot.com

0 Response to "Can An Amibios Be Repaired/rebuilt?"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel