Hello,
I am looking for somebody to mod my BIOS so that I have access to the advanced tabs and advanced features of the Insyde H20 BIOS.
Let me know if you need a BIOS dump, and which tool you would like me to dump the BIOS with.
Thank you very much!
(Let me know if you need more information)
@Kittymatthew - Please link me to stock BIOS download page, and tell me what BIOS version you are using now (I don’t want BIOS download link, but the page you download from)
@Lost_N_BIOS - I download from this link, under the BIOS/Firmware Tab: https://www.acer.com/ac/en/CA/content/su…roduct/7602?b=1
I am currently using InsydeH20 v1.26, Rev 5.0
@Kittymatthew - Please run the 1.26 flash tool again, and show me the Insyde Flash window, so I can see which BIOS you are using (platform ID), this BIOS has two images inside DH53F_1A + DH53F_10
You may also be able to tell which applies to your system on the BIOS Main Page, I’m not sure. But, you should see it for sure in the bottom left side of the flashing program once it begins
@Lost_N_BIOS Attached is an image of the flashing tool. Oddly enough, it doesn’t show me the platform ID, just the DH53F portion.
I took a look at the platform.ini inside of the flashing tools, to see if I can see which one it flashes to my system, but no luck. There also isn’t a log file that this creates.
The main page of the BIOS was no help, either - showing no specifics of the platform ID.
I can re-flash the current version of the bios(by modifying the platform.ini) and see if there’s a log file or some indication of which platform ID I’m using.
@Kittymatthew - Bummer, yes, please do enable Log File with platform.ini and see if you can tell which it picks.
I could not tell either, I even checked microcodes and ME FW of each which can usually give us a clue once you check those on your end, but all same/same.
If there isn’t a way to tell from the log, then I’ll have you dump current and see if I can tell by digging around in it.
@Lost_N_BIOS Good news!
I was able to enable the log file, and even though it didn’t go through with the flash, it still gave enough information:
— Log started: 2020/07/30 17:14:49
Insyde H2OFFT Version 5.72 IHISI v2.1.1
Initializing…
Log file: H2OFFT.log
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
Support new via ESP behavior
platform [secure]
Settings file : C:\Users\XXX\Downloads\Windows\platform.ini (found)
Executable : C:\Users\XXX\Downloads\Windows\H2OFFT-Wx64.exe
Version : 5.7.2.0
Date : Thu Jul 30 08:54:40 2020
Preparation stage
m_strWholeImageFilename -
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
Processing parameters…
Image file : C:\Users\XXX\Downloads\Windows\DH53F_1A.fd
Loading new BIOS image file…
Opening file C:\Users\XXX\Downloads\Windows\DH53F_1A.fd
Error code: 1602(0x00000642)
— Log Stopped: 2020/07/30 17:14:55
Insyde H2OFFT Version 5.72 IHISI v2.1.1
Initializing…
Log file: H2OFFT.log
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
Support new via ESP behavior
platform [secure]
Settings file : C:\Users\XXX\Downloads\Windows\platform.ini (found)
Executable : C:\Users\XXX\Downloads\Windows\H2OFFT-Wx64.exe
Version : 5.7.2.0
Date : Thu Jul 30 08:54:40 2020
Preparation stage
m_strWholeImageFilename -
IsCondi_match() # (01) MEMORY,ff67003b,000000FF,00000001,DH53F_1A.fd
FD#XX=MEMORY
-------±----------------
PhyAddr FF67003B
mask FF
value 1
M-FD: Match!
M-FD: FD filename DH53F_1A.fd
M-FD matched
-------±----------------
FD DH53F_1A.fd
ME
Cfg
Processing parameters…
Image file : C:\Users\XXX\Downloads\Windows\DH53F_1A.fd
Loading new BIOS image file…
Opening file C:\Users\XXX\Downloads\Windows\DH53F_1A.fd
Error code: 1602(0x00000642)
— Log Stopped: 2020/07/30 17:14:55
(The error is just because the bios is the same version; changing one number will bypass if needed)
The log shows that I am using the DH53F_1A.fd firmware image.
@Kittymatthew - Yes, that’s all we needed to know >> DH53F_1A - thanks! 
Please download the following package, and run the command below from each versions folder that directly contains it’s exe.
Once done, copy the entire folder somewhere, delete everything but any created vars.txt and then repackage this and send to me, this way all created vars.txt remain in place in the folders of the version that created them.
http://s000.tinyupload.com/index.php?fil…212104496994806
H2OUVE.exe -gv vars.txt
@Lost_N_BIOS - Only two of those versions successfully work.
100.0.9.2 and 100.00.18.04 are able to create full-versions of the vars.txt file, in less than a second.
The other two versions(100.00.16.11 and 100.00.16.08) get stuck after running the command. They create a vars.txt file, although it’s completely empty. I’ve given both of them around 30 mins each, to no avail.
Oddly enough, I run the programs with the same administrative privileges, and arguments.
@Kittymatthew - Sorry, yes, I forgot to mention, that is why so many versions are included, not all work for all systems. Please upload all files as mentioned, blank or not.
@Lost_N_BIOS - Ah - I see.
I should’ve figured that from a semi-functional tool that was accidentally leaked XD
Anyways, here are all of the vars.txt in the folders: http://s000.tinyupload.com/index.php?fil…429308780769031
Thanks!
@Kittymatthew - All the versions work, just not on all systems. Generally the one that works for most users is one you said that fails for you (100.00.16.08)
Please put this modified vars into H2OUVE_100.0.9.2 folder, then run the following command from that folder and reboot (there will be list of success/fail, this is expected)
http://s000.tinyupload.com/index.php?fil…036351676011265
H2OUVE.exe -sv varsM.txt
After reboot, please do step #1-2 below, and tell me if #2 is success or error (if error, tell me error #) - To save you some time, you should need V12 ME System Tools Package, below is just copy/paste I keep handy
Send me file from step #1, this is what I will modify to unlock for you Also, ignore the “reflash stock BIOS” comments in this, you’re good to go directly to step #1-2 with BIOS as it is now, otherwise the modified vars would get reset and then step #2 will fail again
If you have already modified the BIOS in ANY way, you will need to re-flash it back to factory defaults using factory method (NOT FPT)!!!
Additionally, please remove all BIOS passwords, disable secure boot, and disable TPM or Encryption if you have enabled. Do this before moving on to below
If you do not have Intel ME drivers installed, install them now from your system driver download page, then start over here after reboot.
Check your BIOS’ main page and see if ME FW version is shown. If not then > DOWNLOAD HWINFO64 HERE <
Once HWINFO is open, look at the large window on the left side, expand motherboard, and find the ME area.
Inside that section is the ME Firmware version. Take note of the version. (ie. write it down or get a screenshot)
Once you have that, go to the thread linked below, and in the section “C.2” find and download the matching ME System Tools Package for your system.
(ie if ME FW version = 10.x get V10 package, if 9.0-9.1 get V9.1 package, if 9.5 or above get V9.5 package etc)
> DOWNLOAD " ME System Tools " packages HERE <
Once downloaded, inside you will find Flash Programming Tool folder, and then inside that a Windows or Win/Win32 folder (NOT x64).
Highlight that Win/Win32 folder, then hold shift and press right click. Choose “open command window here” (Not power shell! >> * See Registry file below *).
If you get an error, reply to this post with a screenshot of it, OR write down the EXACT command entered and the EXACT error given.
((If “open command window here” does not appear, look for the “Simple Registry Edit” below…))
Step #1
Now you should be at the command prompt.
You are going to BACKUP the factory un-modified firmware, so type the following command:
Command: " FPTw.exe -bios -d biosreg.bin "
>> Attach the saved "biosreg.bin ", placed into a compressed ZIP/RAR file, to your next post!!! <<
Step #2
Right after you do that, try to write back the BIOS Region dump and see if you get any error(s).
Command: " FPTw.exe -bios -f biosreg.bin "
^^ This step is important! Don’t forget! ^^
If you get an error, reply to this post with a screenshot of it, OR write down the EXACT command entered and the EXACT error given.
Here is a SIMPLE REGISTRY EDIT that adds “Open command window here as Administrator” to the right click menu, instead of Power Shell
Double-click downloaded file to install. Reboot after install may be required
> CLICK HERE TO DOWNLOAD CMD PROMPT REGISTRY ENTRY <
If the windows method above does NOT work for you…
Then you may have to copy all contents from the Flash Programming Tool \ DOS folder to the root of a Bootable USB disk and do the dump from DOS
( DOS command: " FPT.exe -bios -d biosreg.bin " )
Additionally, please remove all BIOS passwords, disable secure boot, and disable TPM or Encryption if you have enabled. Do this before moving on to below
If you do not have Intel ME drivers installed, install them now from your system driver download page, then start over here after reboot.
Check your BIOS’ main page and see if ME FW version is shown. If not then > DOWNLOAD HWINFO64 HERE <
Once HWINFO is open, look at the large window on the left side, expand motherboard, and find the ME area.
Inside that section is the ME Firmware version. Take note of the version. (ie. write it down or get a screenshot)
Once you have that, go to the thread linked below, and in the section “C.2” find and download the matching ME System Tools Package for your system.
(ie if ME FW version = 10.x get V10 package, if 9.0-9.1 get V9.1 package, if 9.5 or above get V9.5 package etc)
> DOWNLOAD " ME System Tools " packages HERE <
Once downloaded, inside you will find Flash Programming Tool folder, and then inside that a Windows or Win/Win32 folder (NOT x64).
Highlight that Win/Win32 folder, then hold shift and press right click. Choose “open command window here” (Not power shell! >> * See Registry file below *).
If you get an error, reply to this post with a screenshot of it, OR write down the EXACT command entered and the EXACT error given.
((If “open command window here” does not appear, look for the “Simple Registry Edit” below…))
Step #1
Now you should be at the command prompt.
You are going to BACKUP the factory un-modified firmware, so type the following command:
Command: " FPTw.exe -bios -d biosreg.bin "
>> Attach the saved "biosreg.bin ", placed into a compressed ZIP/RAR file, to your next post!!! <<
Step #2
Right after you do that, try to write back the BIOS Region dump and see if you get any error(s).
Command: " FPTw.exe -bios -f biosreg.bin "
^^ This step is important! Don’t forget! ^^
If you get an error, reply to this post with a screenshot of it, OR write down the EXACT command entered and the EXACT error given.
Here is a SIMPLE REGISTRY EDIT that adds “Open command window here as Administrator” to the right click menu, instead of Power Shell
Double-click downloaded file to install. Reboot after install may be required
> CLICK HERE TO DOWNLOAD CMD PROMPT REGISTRY ENTRY <
If the windows method above does NOT work for you…
Then you may have to copy all contents from the Flash Programming Tool \ DOS folder to the root of a Bootable USB disk and do the dump from DOS
( DOS command: " FPT.exe -bios -d biosreg.bin " )
@Lost_N_BIOS - Luckily, both steps were successful! I followed the instructions and used the WIN32 version of the flash tool(instead of WIN64) - and it worked perfectly - says it was successful.
Anyways, here is the biosreg.bin - http://s000.tinyupload.com/index.php?fil…617296188916014
Thank you very much for all your help so far!
@Kittymatthew - You’re welcome! And thanks, as expected, all unlocked now (unless flashing back in at step #2 caused it to lock again, if so, just reflash mod vars again, reboot, and then flash in the mod BIOS)
Anyway, for now, proceed as it’s unlocked and here is mod BIOS - http://s000.tinyupload.com/index.php?fil…376978869299846
Flash in via >> FPTw.exe -bios -f biosregm.bin
*** WARNING - To ANYONE with laptop and unlocked BIOS!!!
DO NOT try to enable this graphics card or disable that card, switch cards etc. Otherwise you will end up with no display output (ie black screen) and no way to recover except by blind flash or with flash programmer.
You can change graphics related settings, like changing memory sizes, or core speeds etc, just don’t try to disable one card or change which is main etc.
Additionally, be very careful when trying to undervolt CPU, you can leave BIOS unbootable due to CPU voltage too low (Sometimes even 0.05 is too much)
WARNING *** - This BIOS is user specific! If you are not user Kittymatthew at Win-RAID.com forum, DO NOT USE THIS BIOS!!
If you do, and you are not Kittymatthew, then you will loose your serial, UUID, OG NVRAM, and possibly LAN MAC ID as well.
You have been warned!!!
@Lost_N_BIOS - Thank you so much! As expected, BIOS is fully unlocked, I can access all menus.
Don’t worry, I promise I’ll be careful and not screw anything up 
Seriously though, thank you - I’ve wanted to do this for a while!
Have a great day!
@Kittymatthew - Thanks for quick report back, and great to hear all is unlocked without issue!
Yes, be careful, that is my general warning I post for all users with laptop and unlock BIOS
You’re welcome, and thanks, you have a great weekend too!
hi i would like to unlock advanced bios mode you could help me acer predator helios 300 i7 8750h bios v1.26
@rdsadrian - Please give exact full model, then I will merge this into the main thread (if it’s the model I’m guessing)
PH317-52
@rdsadrian - Thanks, it was not the model I expected, but we have a thread for that model, so will merge this now (removed your serial #'s)
Please do what is in post #8 and #12, and send me the files