My Predator Helios 300 (PH317-54) will not boot. The keyboard lights up and the fans go on but no logo or boot.
My research indicates this is likely a corrupt bios.
I have found instructions (download firmware for this model, unzip it and unzip the exe, get the .fd file and put it alone on a usb stick, press FN+ESC+Power and it should load from the usb).
I have followed these steps but I never get the fast fans or see any blinking on the USB stick.
I assume I have the file name incorrect. The two bios firmware versions available on the support site are 1.04 and 1.06 and the file names are Bios_1.04.fd and Bios_1.06.fd respectively. I have tried them both unsuccessfully on several different USB sticks to ensure it is not a problem with the usb drive.
Can someone please advise me if I have the name of these files incorrect? Or if there is some step I am missing, or is there a different bios file I should be using?
Thank you in advance for any advice.
BTW, I found a youtube video on how to use a hex editor to find the .fd name, but a search of both files does not show and encrypted .fd name, so I assume that does not apply to this version.
My research indicates this is likely a corrupt bios.
I have found instructions (download firmware for this model, unzip it and unzip the exe, get the .fd file and put it alone on a usb stick, press FN+ESC+Power and it should load from the usb).
I have followed these steps but I never get the fast fans or see any blinking on the USB stick.
I assume I have the file name incorrect. The two bios firmware versions available on the support site are 1.04 and 1.06 and the file names are Bios_1.04.fd and Bios_1.06.fd respectively. I have tried them both unsuccessfully on several different USB sticks to ensure it is not a problem with the usb drive.
Can someone please advise me if I have the name of these files incorrect? Or if there is some step I am missing, or is there a different bios file I should be using?
Thank you in advance for any advice.
BTW, I found a youtube video on how to use a hex editor to find the .fd name, but a search of both files does not show and encrypted .fd name, so I assume that does not apply to this version.