Here is the link to the ipconfig. https://www.dropbox.com/s/4huacdol16f2foq/ipconfig.PNG?dl=0
And no I wont be flashing the bus the corrupted it.
@Lost_N_BIOS

Thanks, now I see the one I found in your original BIOS dump. See it, there in the middle under Main Wireless LAN Wifi - BC:83:85:23:AA:53 This is good, it means even without wifi entry in your NVRAM in BIOS, this MAC is used, must also be stored in the actual wifi adapter module itself too.
They usually are like that, but since I see that entry for wifi in your original BIOS dump I assumed maybe it also needed to be there, but since we can see it and it's working all is fine without a BIOS entry

So, I will now make changes to two SMBIOS modules, and change all the NVRAM entries back to their original values for family, SKU, brand, type etc.

BUS Corrupted flashing? What's that mean? You should be able to flash an update after we fix all these details. I assumed you'd flash in the corrected BIOS, and then try a new BIOS update (not one that originally bricked it)

Oh ok that's good. Thanks a lot for your help. I have been trying to learn little by little but its complicated. So much information.

I meant I would not be doing the update that bricked it.

You're welcome! Yes, some of this can be complicated if you are not used to doing it all the time.

Big surprise! I go to change out your SMBIOS (This usually where all boards keep a main DMI (system ID stuff) details entry copy) And I see OEMAP in your original backup! But I see it's "generic" info like 123123, 456456, 789789. And this module is identical to the one in the current problem BOS

So maybe Microsoft sometimes uses this OEMAP in some way, but the way your other messed up BIOS is signed OEMAP and has actual numerical details like a real serial number instead of 123456 etc means that other BIOS must have been setup/used on something before.
I will leave this module as it is for now, most data/ID will be pulled from NVRAM which is not saturated with OEMAP everywhere in your original BIOS dump

I think you can either re-try that update, since you can recover, it could have been a random glitch that caused it, or find a newer version if possible. Were you sure you had the correct update?

Oh ok so Microsoft uses The OEMAP in some way.
I highlighted in this screenshot what I was able to find.
https://www.dropbox.com/s/l56xmlj0mjdzsd2/Capture01.PNG?dl=0

In your image, that's all in the NVRAM module of the BIOS, it's what I'm correcting right now. And yes, Microsoft must use OEMAP, since it's in your original backup BIOS.
It's probably some generic thing, but wow, that current BIOS dump has it everywhere, as data value entries, serials, ID's, etc and even in secure file signatures too and signed certificates.

@eknsibby - Let's try this direct swap of your original NVRAM first, it's much easier that way vs editing NVRAM entries one by one (I always break NVRAM links and takes me forever to correct), if this one boots all done at once.
If there is a corrupted bit in there it wont be bootable, sorry, that may be why it bricked initially, only this test will let us know.
http://s000.tinyupload.com/index.php?fil...675779164157524

If this fails to boot, sorry and go ahead and put back in your backup BIOS. If it does fail you'll have to wait on me to correct the entries one by one, so please be patient it may take me a while.
It's not simply copy/paste names/ID's etc links/offsets/file sizes, file state etc, for each entry also then have to be corrected since the values of what we change are not same size, if it was all same size then no problems and I'd be done with that method already.

Ok I will try this out when I get home. How should I go about flashing this?
@Lost_N_BIOS

@eknsibby - With programmer, and due to it's direct swap in from your bricked BIOS, be ready to recover to your known working good BIOS.
This test saves me a lot of time doing tedious edits that may not be needed, so best to try this first, then do the tough way if necessary.

Ok. So I wont be able to do it without having to take apart huh. If so I can try and get it done today. Also is there a way to be able to reflash later on without having to take apart?
@Lost_N_BIOS

@eknsibby - You can flash it in, I forgot and was thinking this was entire dump edit. Yes, if it will let you go ahead and flash in via FPTw.exe -bios -f filename.bin
Yes, if you always want to be able to flash any region, you can unlock FD, but to do that I need an entire dump to edit, then you program it back in, then that will be last time you need to do that.

@Lost_N_BIOS So I tried using FPTw.exe to flash but I get a Error 368 : Failed to disable write protection for the BIOS space. FPT Operation Failed. So It looks like I will have to use programmer huh.

@eknsibby - No, for error 368 use my guide - [GUIDE] Grub Fix Intel FPT Error 368 - BIOS Lock Asus/Other Mod BIOS Flash
Alt boot to grub when no boot to EFI on exit page - [Help needed] Hidden Advanced menu Bios HP Z1 J52_0274.BIN (2)

However, you'll have to wait until I can find your variables to use, right now I can't find your setup module. Please show me a few images of the BIOS so I can see some settings, hopefully that will help me find the module.
If we can't end up finding, then yes you may need to use a programmer if normal flash method wont update it for you.

@Lost_N_BIOS Ok do I use a the program for the earlier post for the BIOS pictures you want?

@eknsibby - If "F12" does not put screenshot of BIOS onto USB Stick, then you will need to use a camera, then zip up the images and upload/send me link.

https://www.dropbox.com/s/vib0c1fpishios...61837e.rar?dl=0
Here is the link
@Lost_N_BIOS