Dear MrChromebox Community,
I’m currently working on modifying the full replacement BIOS for my MrChromebox device, and I’m encountering some challenges in the customization process. I’ve followed the guides on MrChromebox.tech, but I need assistance with specific steps and validations. Here’s my setup and what I’m trying to achieve:
My Environment:
●
Local Machine: Windows PC with Xlaunch (for Linux GUI) and Xshell/Xftp installed.
●
Server: Ubuntu Linux server for command-line operations.
●
BIOS Files: I’ve downloaded the full replacement BIOS from MrChromebox.tech and successfully backed up my original ROM using a CH341A programmer.
Goals & Modifications I Need Help With:
1.
Synthesize the Full Replacement BIOS:
○
Inject my device’s original VPD data (Serial Number, MAC Address, etc.) and HWID into the MrChromebox Full ROM.
○
Validate the injection process using cbfstool and gbb_utility on my Ubuntu server.
2.
Deep BIOS Modifications (Need to be “hard-coded” into the ROM):
○
Temperature Wall (T-Wall): Change PROCHOT limit to 100°C (currently set to 90°C even after flashing the full ROM).
○
TDP Settings: Adjust PL1 to 35W and PL2 to 55W.
○
Intel PTT (Platform Thermal Technology): Enable this feature.
○
Intel XTU Unlock: Disable CFG Lock and Overclocking Lock to allow XTU to modify CPU parameters freely.
○
BIOS UI Fullscreen: Modify the BIOS Setup interface to display in fullscreen mode (no need for third-party help with this part; I’ll handle it externally through Xianyu services).
3.
Tools I’m Using/Planning to Use:
○
Windows Tools: UEFITool NE, UEFITool 0.28, Universal IFR Extractor, HxD (Hex Editor).
○
Linux Tools: cbfstool, gbb_utility, flashrom, ifdtool.
Challenges & Questions:
●
Synthesis Validation: How can I confirm that VPD and HWID injection was successful before flashing the modified ROM?
●
IFR Editing for Deep Mods: I need step-by-step guidance on how to extract the Setup module (likely named Setup or PlatformSetup), parse the IFR data using Universal IFR Extractor, locate the correct VarOffsets for T-Wall, TDP, PTT, and XTU Unlock, and modify the default values directly in the binary using HxD.
●
Potential Risks & Validation: I understand the risks of pushing PL1/PL2 beyond the stock 15W design (cTDP-up 25W). However, I’m willing to accept the risk. How can I test the stability of the modified BIOS before committing to a permanent flash? Are there any logs or monitoring tools I should use during stress tests?
What I’ve Done So Far:
●
Downloaded all necessary tools on both Windows and Ubuntu.
●
Backed up my original BIOS and verified the integrity with MD5 checks.
●
Injected VPD and HWID into the Full ROM using cbfstool and gbb_utility on the Ubuntu server.
Request for Assistance: Could someone please provide clear, step-by-step instructions or point me to relevant resources for:
1.
Validating the injected VPD/HWID.
2.
Locating and editing the specific Setup Variables (VarOffsets) for T-Wall, TDP, PTT, and XTU Unlock in the IFR data.
3.
Testing the modified BIOS safely (e.g., using QEMU emulation or a temporary flash to test functionality before a permanent write).
Any advice, tips, or troubleshooting guidance would be greatly appreciated. I’m comfortable with advanced command-line operations and hex editing, but the IFR manipulation part is new to me.
Optional Attachments:
●
setup_ifr.txt (IFR parsed text file for reference).
●
Output of cbfstool akemi_full.rom print showing injected VPD/HWID.
Thank you in advance for your help!
Best regards, [Your Forum Username]
P.S.: I’m unable to use tools like ThrottleStop due to concerns about game anti-cheat detections, so BIOS-level modifications are necessary.