@Thunder0616

Thanks for the file.

If I understand correctly, then the platform of your BIOS is Instde H20.
That is what it is:
1 - GUID 501737AB-9D1A-4856-86D3-7F1287FA5A55
- OROM IRST v9.5.0.1037
2 - GUID B017C09D-EDC1-4940-B13E-57E95660C90F
- OROM Intel AHCI v1.20E
3 - GUID 4C316C9A-AFD9-4E33-AEAB-26C4A4ACC0F7
- OROM Intel LAN GE v1.3.37

Also OROM in FFA Intel VBIOS & 2 OROMs nVIDEO & mCode in Padding

Unfortunately,UBU can only EFI Drivers replace in such BIOS. Since it is difficult to guess which sections (RAW, FreeForm, etc) may be OROM files.
Therefore, the replacement of the necessary files and microcodes must be done manually.

By the way, I see no reason to replace the IRST, since you obviously do not plan to create an RAID array. But AHCI OROM can be replaced with version 2.00.

Hi Sonix, can you update all microcodes with updates for MDS vulnerabilities?
https://www.techpowerup.com/255545/intel...rthed-on-may-14

EDIT by Fernando: Post moved into the correct thread (the other one is reserved for the UBU maker SoniX).

@jlmcr87:
Some of these (probably most of them) new microcodes are already in UBU.

EDIT by Fernando: Refered post moved into the correct thread and customized this one.

It is possible that yes.
But if they indicate revisions of microcodes then it will be exactly known.

In general, there is no point for panic. How many years nobody knew about these vulnerabilities and did not care about anyone.

Gigabyte released a new BIOS for some of their X470 boards. Has a new microcode. I uploaded the .bin

http://download.gigabyte.us/FileList/BIO...-7-wifi_f40.zip

Sometimes it is very expensive for many

Zitat von SoniX im Beitrag #172

---

Usually, we look at the version in the EFI Shell, loading the driver. If the version is displayed, then we are looking for possible options in the hex editor. Some files GOP AST version is not specified at all.

---

OROM VBIOS Weston Pro - 015.049.000.017.029087 (new item)

EFI AMD RAIDXpert2-Fxx - 9.2.0-00105 (>9.2.0-00087)

Zitat von westlake im Beitrag #204

---

EFI AMD RAIDXpert2-Fxx - 9.2.0-00105 (>9.2.0-00087)

---

Hello I have an Asus Z87ws bios 2004
https://dlcdnets.asus.com/pub/ASUS/mb/so...S-ASUS-2004.zip

upon opening the latest : UBU_v1_74_0_1

- Once scanned i have :

Scanning BIOS file bios.bin.
Please wait...
BIOS platform - AMI Aptio 4
BIOS version - 2004
Manufacturer - ASUSTeK COMPUTER INC.
Model - Z87-WS

[EFI Drivers - Find and Extract]
Intel GOP GUID 5BBA83E6-F027-4CA7-BFD0-16358CC9E123
Intel RST GUID 91B4D9C1-141C-4824-8D02-3C298E36EB3F
Marvell AHCI GUID 4331898D-CCB8-4108-898C-A5CC81442B28
Intel 1Gb GUID 4953F720-006D-41F5-990D-0AC7742ABB60
Realtek Undi GUID 2EAA04AA-5EED-4C27-B9EE-26916EC25A8F

[OROM - Find and Extract]
VBIOS in Padding
VBIOS in GUID A062CF1F-8473-4AA3-8793-600BC4FFE9A8
OROM in GUID A062CF1F-8473-4AA3-8793-600BC4FFE9A8

- I want to update the : Intel RST GUID 91B4D9C1, It gives this in the menu.

1 - Disk Controller
EFI IRST RAID for SATA - 12.7.0.1936
OROM IRST RAID for SATA - 12.7.0.1936


- I tried to understand all the infos on the web pages, Sorry to say im totally lost for the next steps

- Im confused between the pages :

Intel's RST/RST(e) AHCI/RAID Drivers
and the
Intel EFI "RaidDriver" (="SataDriver") and "GopDriver" BIOS Modules

- I dont use the board in raid, i only use it in jbod (thru hot swap caddys)

- If i understand i need :
Intel RST(e) EFI "RaidDriver" modules v13.5 series:

>Intel RST(e) EFI "RaidDriver" v13.5.0.2164 GUID 90C8D394< (>MIRROR<)
>Intel RST(e) EFI "RaidDriver" v13.5.0.2164 GUID 91B4D9C1< (>MIRROR<)
>"pure" Intel RST(e) EFI "RaidDriver" v13.5.0.2164 (without header)< (>MIRROR<)

- Once downloaded the "91B4D9C1" corresponding files, i have *.ffs files in them, not the files to be renamed RaidDriver.efi or SataOrom.bin ??? and match them for the Raid drivers ???

- Where do i mess things up ? sorry im french native, not understanding eveything well in english


- I have tons of old UBU versions, Example : UBU_v1.69.17.4\Modules\IRST\13_2
- I place the files in the newest UBU version i have : EFI IRST RAID for SATA - 13.2.0.2134 version

- Is it okay to update with this version ???

thks

Edit 1: if i do the update, save the file before UBU exit, it create the file mod_bios.bin not the Z87WS.CAP i need to flash it ??????

i have the 2x mmtools renamed inside the UBU folder (mmtool_a4.exe and mmtool_a5).exe

Edit 2: the last working UBU for me is 1.69.17.4, since the v17 versions something is broke and nothing works well for me anymore ?
Just tried once again and it gives me the Z87WS.CAP file i need.

@SoniX

I do not know whether it is 1.74.0, but it was MAC address 88.88.88.88.87.88 when raising the version of Lan. I did not notice this.
Look at the router's log and noticed that I have a MAC address that I have never seen.
Is this a specification? Or is there another cause?
What should I do?

I fixed it by myself with TMAC V6. I restored it, but I'm sorry to bother you.
But If you back up using FTK and use FD44Editor, you will see MAC address 88.88.88.88.87.88. What will be bad?
I think that it was probably because had bricked Bios in the matter of JMicron.
I also wrote the correct MAC address to Bios.
I tried because there is a spare machine, but I did not get MAC address 88.88.88.88.87.88.

Windows 7 Pro 64bit P8Z68-V/GEN3

MAC address error

@Lost_N_BIOS :

thank you for your reply. I had used 0X258 Vss to Unhidden the Menu, but it still not with efi/legence option.
then I hacked the 0x27 OP-Code, Suppress_if_true, changed to 0x28H, Suppress_if_false. then the efi menu displayed.
But I find it could not search the efi boot device, and have other problem with halting and system unstable.
I used Uefitool to expend it and see that there are not Fat.dxe and other pei modules.
I think maybe we need to add some modules to it so it can boot to efi.
Thank you.

@Thunder0616 - please make a new thread about this and I will move these posts to that thread, since this has nothing to do with UBU.
In that thread, please answer my question from post 191, or better explain your goal/what you want to do etc. Because again, I see in your actual BIOS images now, same as I found in your BIOS, EFI is already enabled and is the default.
If you are trying to boot legacy, what's inside the legacy section of the BIOS shown in your image, or is it blank like the EFI one? Anyway, if you want to boot legacy you need to change that first setting to legacy instead of EFI, and then disable UEFI Boot

@Fernando After having chosen the option "M" ---> fix to R