[Request] Unlocked Tongfang GM5TGFO Laptop BIOS

Hello there, I obtained original bios file for my rebranded tongfang laptop. I would like to access the hidden advanced tab for undervolting. Any help appreciated.

  • GM5TGFO - Tongfang

Here is the link : Unique Download Link | WeTransfer


Edit by Fernando:
Thread moved into the “BIOS Modding Requests” Category and title specified

Thanks for your reply, the thing is the file’s link is dead i think? and op is long way gone. any help on that? can you share a link if you still got the file ? I am willing to do it myself.

Sorry but any personal links outside the forum cant be recovered.
Also im not sure what file you’re trying to download and failed…
This is a guide and all the tools mentioned are present in the forum.
The guide, in my opinion, in not directed to unskilled users or without proper knowledge of the terms used, its detailed but technical as its also the required operation goals.

More recently a new user tool for general, modern AMI V bioses emerged and you may want to take a look:
[TOOL] UEFI Editor - BIOS/UEFI Modding / BIOS Modding Guides and Problems - Win-Raid Forum (level1techs.com)
[GUIDE] Usage of AMI’s AptioV UEFI Editor + FPT Flash Method - BIOS/UEFI Modding / BIOS Modding Guides and Problems - Win-Raid Forum (level1techs.com)

Other than this, if the goal is ask for a ready mod file, do a post with the proper guidelines, as you can see in the requests section… not just asking “help”.
Thats all i can help in this matter, good luck.

Hi, different chassis than yours (mine’s an Avell A60 MUV, QC71/QCCFL357 — Cannon Lake i7-9750H, not sure if same generation as your GM5TGFO), but similar category of problem with a rebranded TongFang unit, so hoping it’s okay to ask here too since I’m not yet able to start a new topic as a new member.

My issue isn’t hidden menus — it’s that both official firmware update paths (F7 USB flash and the Windows EBU installer) fail on my unit. The EBU exits with ExitCode 73 without ever calling the Windows firmware capsule API (confirmed via Process Monitor). Reverse engineering the installer showed it checks the ACPI FIDT (platform identity table) before proceeding, and my package — sourced from an XMG-branded release for the same QC71 chassis — doesn’t recognize my Avell board identity, even though the underlying .CAP firmware payload is SHA-256 identical to the official Intel-hosted package for this platform.

I confirmed via MEInfo that Verified Boot/Measured Boot are Enabled on my ME, so I’m being cautious about any raw flash workaround given the brick risk. Avell has discontinued this line, so there’s no official support path left for me.

If @Lost_N_BIOS or anyone else familiar with this specific QC71/Cannon-Lake variant (as opposed to the Coffee Lake GK5CN6Z chassis discussed elsewhere in this section) has pointers on getting EC/ME updated safely despite the OEM identity lock, I’d really appreciate it. Happy to provide FPT dumps of my current flash.

QC71/QCCFL357] Complete evidence chain for isolated EC flash — need guidance on IT8528E flashing procedure

Following up on my earlier posts about this platform (Avell A60 MUV / TongFang QC7 / Intel LAPQC71A, board MBPGK5CQ7C-TN11 / GK5CXXT V1.1). After extensive analysis, I’ve built a complete evidence chain and am now specifically looking for guidance on the actual flashing step — not whether it’s theoretically safe, but how to do it correctly on this specific chip.

Confirmed facts (not hypotheses):

  1. BIOS 0158 installed (manual EFI region flash), EC stuck at 1.16.09, ME at 12.0.40.1433.

  2. Both F7 and EBU.exe fail identically regardless of BIOS version (tested on original 0048 and current 0158) — confirms the block is a fixed platform-identity check, not version-related.

  3. QC0158.CAP is SHA-256 identical across Avell/XMG/Intel-community sources — firmware content is not brand-specific.

  4. Extracted the Boot Guard Key Manifest via UEFIExtract from both QC0144.CAP and QC0158.CAP: Key Manifest Public Key Hash (SHA256) = 7E80094F934984BD0281B0887EB84FCA615AEB9E1BCD67B443E31454A6BEE712, which matches exactly my board’s own “OEM Public Key Hash” as reported by MEInfo (FPF/UEP/ME FW all consistent). This confirms cryptographic trust-chain compatibility between my board and this package.

  5. Confirmed via Windows ESRT (Get-PnpDevice -Class Firmware) that my system natively reports UEFI\RES_{c418661e-707a-57de-ac46-511a5d080b34}, matching a genuine Windows Update firmware CAB for this platform (BIOS 0144). Installed it via pnputil /add-driver /install — Windows correctly bound the driver (FriendlyName changed to “QC0144”, HardwareID showed REV_9E=158 as currently installed), but declined to apply it since it’s numerically older than my current 158. This confirms the ESRT delivery mechanism works correctly and is NOT blocked by the OEM identity check that blocks F7/EBU — only version ranking prevented application.

  6. Extracted the EC firmware blob from within QC0158.CAP via UEFIExtract: located at GUID path 4F1C52D3-D824-4D2A-A2F0-EC40C23C5916 / 207F94A8-238E-11E8-B467-0ED5F89F718B / Raw section, 98,304 bytes. Verified as genuine 8051 code (reset vector 02 00 70 = LJMP, followed by valid interrupt vector table), contains string “ITE EC-V14.6”.

  7. Extracted the same GUID/path from QC0144.CAP — SHA-256 identical to the EC blob in QC0158.CAP. Since XMG’s official changelog confirms BIOS 0144 ships EC 1.33.09 (the documented battery-swelling-prevention fix), this proves the EC binary sitting inside my QC0158.CAP right now IS EC 1.33.09 — it has simply never been written to my physical chip.

  8. Chip is believed to be ITE IT8528E based on a stock firmware filename match found elsewhere for this exact board (MBPGK5CQ7C-TN11/GK5CXXT V1.1), though I haven’t independently confirmed the physical chip marking yet.

What I’m asking:

Given the extracted EC binary is verified-correct and I have full backups (FPT dumps of BIOS/ME/Descriptor regions taken beforehand), what’s the safest known procedure to flash just this EC blob to an IT8528E on this chassis, bypassing the OEM-locked orchestrator entirely? Specifically:

  • Is ITE’s own flash utility (referenced in Schenker’s EFI Shell guide, e.g. “ITE Flash Utility”) usable standalone with a raw extracted blob like this, or does it require a specific header/wrapper I’m missing?

  • Any known gotchas specific to IT8528E (e.g. required unlock sequence, risk of bricking keyboard/fan control if interrupted)?

  • Is there a safe way to verify chip identity in software before flashing, to confirm IT8528E without opening the chassis?

Full FPT dumps and the extracted EC blob available to share if useful. Really trying to do this the careful, verified way rather than guessing — appreciate any guidance from anyone who’s done isolated EC flashing on this TongFang QC71 family.