Requesting help unlocking X-470F Strix.

xlegacygt · September 1, 2020, 3:37am

Lost_N_BIOS:

@xlegacygt - Yes, NVRAM editing is kind of tricky. This may be required here for any menu or setting you couldn’t get to show up, we change it’s default in the module itself, and then the current applied/in-use value in NVRAM in several different NVRAM areas
I’ve explained this a few times to users, but not in-depth, I really need to make a guide about it but I never have any time. If you want to try and read, maybe figure some of it out, below is links I’ve saved where I tried to show users a few different times
But, as mentioned, this is only necessary, if there is something in PBS that you want to change away from it’s current default, that you don’t also see in some other area of the BIOS.

NVRAM edit explained - Determine configurable aperture size from BIOS file
Setup and NVRAM editing here as well - [Request] Unlock advanced menu on 2019 Acer Predator Helios 300 PH315-52 (5)

Be VERY careful with updating microcodes, you can brick your board if microcode edit done wrong.
These need done manually in your BIOS via extract padding, edit in hex and replace back in, unless UBU can now update microcodes in padding, not sure and from what you mention it sounds like it still cannot.
Your microcodes #1-11 are located in second padding at offset 60000h, the other four are already up to date so no need to mess with those.
If you extract this padding, then drop on MC Extractor, it will give you the exact offsets to go to for each, then just replace with new from here writing over old, since they are same size

Or, if you want, send me your current working BIOS and I will update those two old microcodes that need updated. I can do the network one too if you want?

Nice, I will definitely take a read! I mean, is there really big differences when upgrading modules? Do people mod modules as well?

Is it common that bios updates dont include the newest items?

These are the updates that come up:

Disk Controller
[Current version]
EFI AMD RAIDXpert2-Fxx - 9.2.0-00105
EFI AMD RAIDXpert2-Fxx - 9.2.0-00105
OROM AMD RAIDXpert2-Fxx - 8.1.0-00064
OROM AMD RAIDXpert2-Fxx - 8.1.0-00064

[Available versions for replacement]
1 - EFI AMD RAIDXpert2-Fxx - 9.3.0-00158
2 - OROM AMD RAIDXpert2-Fxx - 8.1.0-00064

Video OnBoard
[Current version]
EFI AMD GOP Driver - 2.7.0.0.0_signed
EFI AMD GOP Driver - 1.69.0.15.50_signed
OROM VBIOS Raven - 016.002.000.010.000000
OROM VBIOS Raven 2 - 016.002.000.010.000000
OROM VBIOS Picasso - 016.002.000.010.000000
OROM VBIOS Carrizo - 015.048.000.073.000000

[Available version]
EFI AMD GOP Driver - 2.12.0.0.0_signed
EFI AMD GOP Driver - 1.69.0.15.50_signed
OROM VBIOS Raven 2 - 016.002.000.011.000000
OROM VBIOS Raven - 016.002.000.011.000000
OROM VBIOS Picasso - 016.002.000.011.000000
OROM VBIOS Carrizo - 015.048.000.073.000000

Network
[Current version]
EFI Intel PRO1000 UNDI - 6.9.07
EFI Intel PRO1000 UNDI - 6.9.07
OROM Intel Boot Agent GE - 1.5.73
OROM Intel Boot Agent GE - 1.5.73

[Available version]
-\ for i82579/i217/i218/i219 chips
EFI Intel Gigabit UNDI - 0.0.29
OROM Intel Boot Agent CL - 0.1.16
-\ for i210/i211/i350 chips
EFI Intel PRO1000 UNDI - 9.3.10
OROM Intel Boot Agent GE - 1.5.88

As far as the Microcodes, Sonix said: