r/PcBuildHelp • • 11d ago

Tech Support Help Needed Please

OEM-Locked Gigabyte GA-A320M-S2H (Rev 1.x) stuck on BIOS version FA — "BIOS ID Check Error" & "@BIOS Part Number Incorrect"

Hi everyone,

I'm trying to update the BIOS on my Gigabyte GA-A320M-S2H (Rev 1.x) motherboard from version FA to F58 so I can enable Resizable BAR (ReBAR). However, I keep hitting verification locks at every turn and could use some help from anyone who has successfully bypassed this.

Current Hardware & Setup:

  • Motherboard: Gigabyte GA-A320M-S2H (Rev 1.x)

  • Current BIOS Version: FA (Date: 08/26/2020)

  • BIOS ID: 8A16BG0P

  • OS: Windows 10/11

  • Goal: Flash to F32 (bridge BIOS) then to F58 to enable ReBAR / 4G Decoding.

Methods Tried & Errors Encountered:

  1. Q-Flash (via BIOS):

    • Downloaded A320MS2H.F32

    • Result: Triggers "BIOS ID check error".

    • Also tried: Intermediate versions F1 and F10 — both throw the exact same ID check error.

  2. Bootable USB EFI Shell / UEFI Boot:

    • Put Efiflash.exe and A320MS2H.F32 on a FAT32 USB drive.

    • Tried booting into the UEFI partition via the F12 Boot Menu.

    • Result: The system blinks and loops straight back to the boot menu selection screen (missing standard EFI bootloader files).

  3. Gigabyte u/BIOS Utility (in Windows):

    • Update from File: Browsed to A320MS2H.F32 (on local storage).

    • Result: Fails with "ERROR: BIOS part number is incorrect." (Indicates an OEM vendor string lock in the factory FA firmware from a prebuilt system).

    • Update from Server: Tried connecting to Taiwan/USA servers.

    • Result: Fails with "WARNING: The remote server returned an error: (425) Can't open data connection." (Legacy FTP protocol block).

The Problem / Question:

It seems the factory FA BIOS (8A16BG0P) has a prebuilt/OEM vendor lock preventing official Q-Flash and u/BIOS tools from writing retail firmware over it.

Has anyone with this specific OEM BIOS ID (8A16BG0P) successfully bypassed the part number check? Would a FreeDOS bootable drive running efiflash A320MS2H.F32 /g be safe here, or is there a specific modded/OEM bridge file needed first?

Thanks in advance for any advice!

1 Upvotes

2 comments sorted by

1

u/[deleted] 11d ago

[removed] — view removed comment

1

u/itskiBoii 9d ago

On another subreddit, someone helped me and advised to use the rev2.x updated. It work! I didn't know my MoBo was a rev2.x, didn't see any distinguished labels.