Yeah, I don’t blame you, lots of OEMs lock down their hardware for no reason in particular.
And, sorry, I checked, I am not good enough in assembly to find where it’s locked down 
But, good thing, once you have programmer, you’ll only need to program in the unlocked BIOS once 
Okay, I got the programmer. Can you tell me how to flash the modified BIOS to the chip?
@brian105 - First you need to dump the chip. What is the BIOS chip ID, so I can tell you best software/version to dump the chip with?
Then I will give you link to guide with lots of images on how to setup and use, and link you to software package
Every time I write out your name I write brain105
I will look for the BIOS chip on the board soon. Will reply with its model/ID.
---------------
Actually, I might have the ID already…
Intel (R) Flash Programming Tool. Version: 11.8.77.3665
Copyright (c) 2007 - 2019, Intel Corporation. All rights reserved.
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
W25Q64FV ID:0xEF4017 Size: 8192KB (65536Kb)
Is this a valid ID, or is it unrelated?
@brian105 - Please look on the chip itself, FPT output is not always correct. If it is W25Q64FV, then you should use software 1.30 or 1.34 and W25Q64BV ID
Here is software package - http://s000.tinyupload.com/index.php?fil…213094641136166
And here is guide how to use programmer - [GUIDE] Flash BIOS with CH341A programmer
Hello, I have gotten the full name from the chip:
Winbond 25Q64JVSIQ 1715.
Is this the same as what I found before?
-----------------
Good news, the chip did read successfully and I got a dump:
http://a.tmp.ninja/pFGr7HUBmENi.bin
Tinyupload was giving me problems.
Bump, seems this got buried under a lot of new posts.
@brian105 - For W25Q64JV, use 1.30 and BV ID as well, this is update version of FV/BV
Yes, some days Tinyupload fails, sometimes it wont upload for a few days at a time too I used to think it was just them blocking me, but later learned it’s same for everyone when it’s failing.
What software/version did you dump the above file with? Anyway, can’t download from there, blocked by malwarebytes, please upload here >> https://uploadfiles.io/
Oof yeah didn’t notice that the site was sketchy, I uploaded from a different computer without Malwarebytes. I will upload the file within a few hours because I don’t have access to that computer.
I dumped the .bin with one of the softwares you included in your software package link, version 1.34.
Did you use BV ID? If not, do it again with BV ID, then upload both as single zip, when you can, thanks.
Yes, I used the BV ID. Here is the file:
https://ufile.io/7ncjszax
Alternate link:
https://cdn.discordapp.com/attachments/5…452/g3_bios.bin
Bump
Other bump. If you’re inundated with work, just tell me, otherwise I’ll be waiting on the edge of my seat for however long there aren’t any responses. I can wait for however long is needed.
@brian105 - Yes, sorry, I am always buried here and can never keep up with all the new requests/posts each day. So yes, I am always inundated with tons of stuff I can’t get to in a hurry
Here is unlocked BIOS, program back by this method >> Erase chip, blank check, open BIOS file, write >> verify
https://ufile.io/0wysv23u
*** 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 brian105 at Win-RAID.com forum, DO NOT USE THIS BIOS!!
If you do, and you are not brian105, then you will loose your serial, UUID, OG NVRAM, and possibly LAN MAC ID as well.
You have been warned!!!
It worked! Thank you so much! I had to clear CMOS first, but it works properly now.
@brian105 - Thanks for the quick test and report back! Yes, usually you may need to reload optimized defaults, then reboot back to BIOS to make all new changes again before you get into windows.