Zitat von lordkag im Beitrag #923

---

Why is there a 111.bin in Modules\lan\FFS folder?

---

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

Zitat von f3bandit im Beitrag #925

---

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

---

Zitat von SoniX im Beitrag #926

---

Zitat von f3bandit im Beitrag #925

---

Zitat von lordkag im Beitrag #922
"Haswell-Broadwell VBIOS 5.5.1030"

this vbios is old, The most up to date so far is 5.5.1215 as mentioned earlier in this thread.

---

You can put here OROM VBIOS version 5.5.1215?
Very interesting to see... ;)

---

I have verified the one you uploaded is newer! "5.5.1215" is the one you uploaded! if you hex edit the vbt files under folder 1028 the bios signon header reads 1215

[quote=SoniX|p8377] New OROM VBIOS here

What bios did you pull the GOP vbios from? I would reason to guess the gop driver is newer as well!?! Can you upload or attach the bios you scavaged the vbios from please?

@f3bandit

Sonix was right. What you think is a VBIOS is actually a VBT = Video BIOS table. The legacy VBIOS is easily modified using the appropriate tools, so it doesn't need an extra file, OEMs just replace the original Intel VBIOS with a patched one. The VBIOS follower in UEFI system is named GOP = Graphics Output Protocol and has many new good things, one of them being the ability to sign the UEFI drivers, which is why the GOP needs an extra file to accommodate the needed OEM settings, because the GOP cannot be modified.

You are lucky that your system still works after your "update", you probably boot in pure UEFI or use a separate GPU. Something to remember:

- The VBT is small - 5-6 KB, the VBIOS is larger - 64 KB.
- The VBT starts with $VBT and is located in GUID 878AC2CC-5343-46F2-B563-51F89DAF56BA, the VBIOS starts with hex 55AA and is usually located in CSMCORE.
- The VBT has no PCI ID, the VBIOS has one and it is found after string PCIR, stored in hex little indian.

okay I see what I did wrong and thx. surprisingly the adapter works fine actually! lol

But I did update the bios the proper way! thx guys!


Select option for update

1 Intel RST(e) OROM and EFI SataDriver
OROM IRST SATA - 13.2.0.2134
EFI IRST SATA - 13.2.0.2134
2 Intel OROM VBIOS and EFI GOP Driver
OROM VBIOS Haswell - 1030
EFI GOP Driver Haswell - 5.0.1037
3 LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Intel PXE - 1.5.56
OROM QCM-Atheros PXE - 2.1.1.5
7 Update Intel CPU MicroCode Haswell/Broadwell
CPU Microcode 0306C3 - 1C
9 Look the Version of all UBU modules in VerDID.txt
0 Exit
Press ENTER - Re-Scanning ALL EFI modules.

Enter number:

[s]Can someone explain better how to use Intel® Binary Modification in order to be able to flash the last OROM?.

I managed to extract the VBIOS OROM from my BIOS using MMTool Aptio but i have no clue what to do on Intel BMP.

When i go to File - Open... i'm being asked for two files, one is a Binary data file, i guess i have to select my extracted VBIOS OROM here but i don't know what i have to select on BMP Script File?, is it the .bsf of the VBIOS version i want to flash?, already tried to do so but then i dont know how to proceed.[/s]

Edit: Never mind, i'm blind and didn't read all the thread, here is the answer :P

Zitat von SoniX im Beitrag #909

---

The process itself is simple.
With the help of UBU look what version OROM VBIOS. For example in 2170.
1. With the help of MMTool extract OROM VBIOS from BIOS file. Usually this VID-DID 8086-402/c02/412/c12.
For example we want to upgrade from 2170 to 2180.
2. In a separate folder, copy the files:
- OROM VBIOS extracted from the BIOS
- script BSF for 2170
- reference DAT and script BSF 2180.
3. Run BMP.
4. Loading OROM VBIOS 2170, and his script BSF, also in 2170.
5. Choose from the menu "BIOS Setting" - "Save All..." and save the settings in SSF-file.
6. In the saved file SSF find and delete one string "STRING $Signon......."
7. Load reference and script files version 2180.
8. Choose from the menu "BIOS Setting" - "Apply All..." and select the previously saved file SSF.
9. After filling in all settings save the file as VBIOS.DAT and copy this file to folder \Modules tool UBU.
Everything is now possible to update the correct BIOS.
This is a simple procedure and works correctly in most cases.

---

@SoniX Is there a X99 compatible version of this slated for the near future? I've seen that X99 motherboard makers can't seem to update their newly released BIOSs either. Thank you.

Zitat von MacG32 im Beitrag #933

---

@SoniX Is there an X99 compatible version of this slated for the near future? I've seen that X99 motherboard makers can't seem to update their newly released BIOSs either. Thank you.

---

Realtek UEFI UNDI Driver 2.029

@SoniX

Time for another round. Found some old Intel RAID 13.1.0.2088 in Toshiba Satellite P50W-P55W-P50Wt-P55Wt, BIOS here from Toshiba updates here. It also had an ASIX Ax88179 Lan UNDI 2.2.0_X64, but this is for laptops mostly.

Found in X99 BIOS different versions of Intel Lan UNDI 6.0.24, let's hope they don't go this route for future versions. Intel Lan UNDI 6.1.14 X99 is not affected, same content every time.

I have some other things about OROM Lan PXE section, but I need to investigate further.

Found many new things in Mini Series (Bay Trail-D)(L0.99) BIOS : EFI Marvell 91xx-92xx RAID 1.1.0.1015 (so now you have AHCI and RAID latest 1.1.0.1015), older EFI Marvell 91xx-92xx AHCI 1.1.0.1007, new 1B4B-9172 Marvell RAID 1.0.0.0034 (UBU has 1.0.0.0032).

OROM Marvell 917x/918x needs a little change. This is for 9172 vs 917A:



And this for 9182 vs 918A:



It is the only new difference I detected, the rest is the same as in UBU. So only change those two bytes in 917A and 918A, from 0106 to 8F01.

And a request for the guys with newest Win 8.1.1.1...... and updates, can you look in "C:\Windows\System32" and upload "mcupdate_AuthenticAMD.dll", "mcupdate_GenuineIntel.dll" and also post the CRC so others don't reupload the same thing? I'm interested to see if there are any new microcodes in there, especially from the AMD side. Right now I have these two:

Here you go...

Thank you for the upload, Hanson. But they have the same CRC as the ones I posted, so nothing new from MS, it seems.

Here is the content of AMD dll:



And here for Intel: