Hi @Sweet_Kitten , 
I have a Clevo NP70PNJ. Seem to be a NP5x_NP6x_NP7xPNK_PNH_PNJ series.
For the NP70PNJ, it features an Intel i7 12700H + RTX 3050, which is equivalent to a Gigabyte G7 GE based on the same Clevo platform and BIOS.
So, we’re dealing with Intel’s 12th generation.
.
However, based on what I see in your script:
if (:NP) then { echo looks like device 12-th Gen CPU, which BIOS can not be modified all the way through automatically }
.
And especially based on these posts:
Post #311
Hello, I’m sorry to resurrect an old post, I wanted to know if it’s possible to use this Mod for G5 KE 12500h rtx 3060. I tried to use it but it says “You ought to flash the Mod manually by some SPI prog. tool”. All good? Thanks in advance.
Post #312
That’s right, for new Gigabyte laptops with 12 gen CPU, the script is only capable of generating a “MOD.bin” file.
Gigabyte G5 is a Clevo barebone device. And they don’t allow to install customized BIOS anymore. I think that some register of PCH (platform controller hub) blocks operations with SPI if the CPU is NOT in SMM state. There’s no solution to this yet unless you’re willing to help.
Post #330
Sorry, BIOS chip memory is not writable for these: G5 KF, G5 MF, G5 GE, G5 KE, G5 ME.
It seems like modifying the BIOS for Intel 12th generation is a dead end.
.
In the case of Intel 12th gen, creating a backup of the current BIOS isn’t a problem: fptw… -d 𝗕𝗜𝗢𝗦.bin
Patching in *.txt format is a bit tricky, but it’s doable with HxD since similar patterns often recur: UEFIPatch… 𝗜𝗡.bin 𝘕𝘗.𝘵𝘹𝘵 -o 𝗠𝗢𝗗.bin But let be honest, I don’t kown where to start…
However, I stumbled upon this while trying to flash a modified BIOS for microcodes: Microcode Update of Insyde UEFI BIOSes. It seems that the major issue is writing the modified BIOS: fptw… -f 𝗠𝗢𝗗.bin -bios in the case of the 12th generation CPUs?
.
. We would need to be done manually in hexadecimal 
…
Intel to express my frustration 
with their increasing tendency to lock down their systems. They responded that it’s a security measure 
due to the Plundervolt vulnerability 
, and also because most end-users tend to brick 
their hardware when undervolting.
, it’s not Intel’s fault, but rather the manufacturers putting a 12500H or 12700H into a 2cm-thick laptop; it’s a design flaw, and undervolting isn’t meant to compensate for the manufacturers’ design flaws they said.
A notable point found on Reddit: if Intel allows it in the HK’s type, what’s the difference in terms of vulnerability with an H or P? It’s seem to be the perfect excuse to force you to go for an HX processor 
), and I have a BIOS with up-to-date microcodes ( 
1 [5,23 Mo]
(
:
