I have HP Z420 Workstation which came with traditional BIOS but it has some UEFI capability too (I think as I saw in BIOS). I want to install Samsung PM981 Nvme SSD as boot device. It has an empty PCI-e x16 (ver 3.0) slot and I have the adapter. Can you please help me with BIOS mod so that I can install it with full Nvme support for booting. Here is the link to BIOS exe file download on HP site:

https://support.hp.com/us-en/drivers/sel...station/5225033


The older BIOS settings can be seen in this video:

https://www.youtube.com/watch?v=GOsaR8S35mg&t=264s

I am a newbie and will help if you please give clean instructions as what needs to be done later.

Many thanks in advance

It's easy to mod but flash
You must to flash it by a hardware programmer

Thanks for your post. I need some clarification.

It is my understanding that the current version of HP BIOS is an exe file which can
be simply installed by double clicking it. If the modified BIOS needs some other method
then can you please point me to a guide for it. I may be able to do it.

Hoping for your answer.

I've tried many ways to solve it but only using programmer.
Although I did the trick once through the "fpt",but,you see, only once~~~~It's not worth

@gloobox - what stops FPT from writing BIOS region here, something other than BIOS lock? BIOS lock we can get around, and FPRR (protected range register) I know how to get around too (but need programmed in without that lock first, unless PRR/PRR2 works for this system)
If this system has "Sure Start" then nothing will help anyway, BIOS will be auto recovered to stock BIOS if you modify anything inside certain regions of the BIOS (mainly the one needed to be modified here)

bios lock and smi lock
prr
prr2
the three things I've tried but it still failed
I tried it in several borads of HP,but no board was OK
So I think the only way to flash it is by programmer

@gloobox - BIOS lock and SMI lock easy to change via grub using setup_var or via H2OUVE vars edit.
If you are getting FPT error 28x (protected range register lock) and PRR/PRR2 fail, that can be fixed easily via assembly/hex edit, but the unlocked BIOS needs to be programmed in or otherwise force flashed before that unlock is live onboard (Force with H2OFFT command line options, or simply flash normally with that tool via command line)
Those only apply for certain HP BIOS too. Ans, some HP boards can be flashed via AFUxxx tools as well, or winphlash, depending on stock BIOS package or actual BIOS type.

Do you have this model? If yes, show me error you get in FPT when trying to write BIOS region before and after BIOS/SMI lock removed.
Dump BIOS using H20FFT-W via command line >> H20FFT.exe backup.bin -g
& do this one too >> H20FFT.exe backup1.bin

With this tool, you can also put in manufacturing mode and that may allow reflash anything or change some protected settings such as PRR option to disabled in the BIOS and SMI/BIOS Lock while you're there too
H20FFT-W.exe /mfg

Download V1.1 package here, has all the H2OFFT versions
https://github.com/mikebdp2/Insider_BIOS...rchive/v1.1.zip

@Lost_N_BIOS

I have a programmer and a Z620 if this helps. I can play on the weekends and would love to get the Z420 and Z620 tuned up to use these NVME drives.

I have a v1 board and have updated the boot block date to match the v2 boards for future CPU updates. ;)

@jetman6 - send me some dumps and I can mod for you

Zitat von Lost_N_BIOS im Beitrag #9

---

@jetman6 - send me some dumps and I can mod for you

---

@jetman6 - If you dump with updated boot block or microcodes, then it will remain no matter what I change. I mean, any changes I make would not affect this, even if it's included in a dump, so your fine to send dump with any updates you made.
Unsure what is your goal, what do you need changed? Or were you only sending a dump for me to locate and test removing the PRR lock? If yes, are you willing to test mod BIOS after that to see if you can then FPT reflash (ie lock removed)?

Zitat von Lost_N_BIOS im Beitrag #11

---

If you dump with updated boot block or microcodes, then it will remain no matter what I change.

---

Zitat von Lost_N_BIOS im Beitrag #7

---

BIOS lock and SMI lock easy to change via grub using setup_var or via H2OUVE vars edit.

---

Zitat von Lost_N_BIOS im Beitrag #11

---

@jetman6 - If you dump with updated boot block or microcodes, then it will remain no matter what I change. I mean, any changes I make would not affect this, even if it's included in a dump, so your fine to send dump with any updates you made.
Unsure what is your goal, what do you need changed? Or were you only sending a dump for me to locate and test removing the PRR lock? If yes, are you willing to test mod BIOS after that to see if you can then FPT reflash (ie lock removed)?

---

Yes @jetman6, any time you reflash stock BIOS it's going to re-write whatever microcodes are in there. Checksum error? What gives you that?

Unlock BIOS Lock via grub guide is here - [GUIDE] Grub Fix Intel FPT Error 368 - BIOS Lock Asus/Other Mod BIOS Flash
Alt boot to grub when no boot to EFI on exit page - [Help needed] Hidden Advanced menu Bios HP Z1 J52_0274.BIN (2)

This only needs to be done to flash via FPT, you can do it before you dump if you want, then it would be unlocked in the dump. This will also be reset any time you flash in stock BIOS, unless you unlock it in the BIOS first.

Is the above a programmer dump? When you do try to flash BIOS region via FPT, you get error 368 correct? If yes, unlock BIOS and SMI lock, then try again with FPT, and then show me new error.
Since you have programmer none of this applies to you directly, you can program in any mod BIOS I make you, but this will help me determine the exact issue causing others to not be able to FPT in a mod BIOS region (or reflash FPT dumped and then untouched BIOS region)