[Request] Modded Acer Predator Helios 300 PH315-54-760S BIOS

Laptop doesnt seem to want to accept the filename. Is there another file name I can try to see if laptop flashes.


Bruh not the 16mb bios file, use the extracted bios from the BIOS installer from Acer and make sure its the same version that your laptop is/was running before it got bricked.
Filename should be GH53Gx64.fd

Laptop doesn’t read usb for bios recovery. My USB seems to blink once and that’s it.

Any help I still can’t seem to recover the bios of this laptop?

I opened up the laptop but the bios chip is too small to clamp with ch431a. Not able to make good contact. I also tried holding down the power button for roughly a minute but same problem.

A script for semi-automatic unlocking.

I have the exact same model of laptop. Will this script work one my laptop?

It should if you successfully complete all the on-screen instructions. For this you just need to confirm the continuation several times by pressing any key and have PowerShell in the system (starting from Windows 7 it is installed by default).

  1. Run 'SET VARS.bat" and reboot.
  2. Run “FLASH.bat”.

"Error 167: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable
Protected Range Registers.

FPT Operation Failed."
I get this error while running the program

Did the uve.log file appear in the working directory? I want to know its contents.

No arguments
Command process done.
Release driver
Show help message
Insyde H2OUVE (UEFI Variable Editor) Version 200.00.01.00
Copyright (c) 2012 - 2018, Insyde Software Corp. All Rights Reserved.

@Morpheus9000
I can’t even reproduce the “No arguments” error, so I don’t understand how it’s possible. I see that arguments are specified, but even so, if they are not specified, it will give a list of available commands instead of an error.
Pleace, replace the file “H2OUVE-W-CONSOLEx64.exe” in a folder with a new one.
uve.log content is welcome.

“Command is: -sv
Initialize driver
Search SMI command and function number
Start command process…
Now Parsing File From varsNEW.txt.
Read EFI Variables in TXT file
Succeed to read varsNEW.txt file.
Init BIOS runtime variable object from IHISI.
Variable Index[001]: Set successfully!
Done.
Release BIOS data information
Release BIOS variable object.
Command process done.
Release driver”

"Error 167: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable
Protected Range Registers.

FPT Operation Failed."

I am still getting this error!

At least this is a step forward, it did recognized the arguments.

Did you reboot the device before running “FLASH.bat”? It is important.

yes

Good to know, thank you.
Now it has been fixed. As always, I forgot which version of Intel Management Engine is used. Now the script works with version 15.

Sorry!
It’s still giving the same error.
"Command is: -gv
Initialize driver
Search SMI command and function number
Start command process…
Export EFI Variables to TXT file
Now parsing Variable Information.
Init BIOS runtime variable object from IHISI.
Release BIOS data information
Release BIOS variable object.
Complete parsing Variable Information!!!
Saving Variable Information to file: vars.txt
Command process done.
Release driver
"
"
Error 167: Protected Range Registers are currently set by BIOS, preventing flash access.
Please contact the target system BIOS vendor for an option to disable
Protected Range Registers.

FPT Operation Failed.
"

Backup

Vars.txt

Ok, I’ve done a BIOS MOD for you manually: Morpheus9000.zip.
Absolutely in the same way as I did it for the 4 previous users.

1 Like