@Fernando - I am LOST as-is, moving threads mid-discussion because someone mentioned bricked once (not the main thing here) makes me even more LOST
The brick mention was brief "hey, I bricked" then directly into how to insert NVME properly and what was wrong with previous insertion (and still on that as of last comments too)

You asked if it was OK/needed, I'm answering No, to me this discussion was always, and still is, about NVME BIOS modification/insert, and should be where it was all along.
This is just my opinion, but splitting up discussions and moving topics around like that all the time because someone talks briefly off-topic for a second about the same hardware device, makes for a much bigger mess, and more confusion within any thread and to all involved, at least to me anyway.
Taking a handful of comments outside of a 5K post thread doesn't help anyone find anything any easier later, search here is already terrible, and no one is digging through the thread page by page, so 5K or 10K on/off topic really doesn't matter
However, as mentioned, my entire goal in that discussion was about fixing BIOS with NVME for him properly and or how he maybe did it wrong so he could do it differently in the future.

You moving my topic works in my favour. I can get answer easier and dont need to skim through unrelated posts ;)
Reason " why " is unknown but i can tell that uefitool 0.26 produced bad bios after insertion of nvme, i tried flashing it with the programmer and it bricks the board. I am on stock now so still no boot from nvme. waiting for someone to review other two nvme mod attempts done with uefitool 0.25 and with mmtool.

So, two to one, I guess I loose (edited in more thoughts above)

I'll have to move the rest of you guys discussion back into the NVME thread, because it now has nothing to do with bricked BIOS which is the topic of this thread
I guess that would be all but post 1-6, since those are the only ones about bricked BIOS (recovery was done, not discussed, etc)

Although i agree with your point of view on the conversation @Lost_N_BIOS and the fact original posts were nvme related please also notice that current discussion about where the posts belong is totally offtopic, guess we might be better off leaving it as it now is. Besides who wants to argue with the boss ;) not me. I just want my nvme flashed ;) shall we continue the topic ? Thank you for reading another lengthy unrelated comment from myself.

Yes, that always happens too when threads are split, it's always undesired to me unless someone goes way off-topic for hours/days etc, but that is why I said "This is just my opinion"
I'm not trying to argue with anyone, only stating my own opinion/thoughts, since I was directly asked.

I think Fernando is helping you on the BIOS per post #15 which you never replied to, I am now lost and don't know what is going on here.
If you need help with NVME mod BIOS, you should ask in the NVME mod BIOS thread, do you want me to move this discussion/request to the proper thread (see what I meant all along)
As to your request to continue, my reply still stands at post #9 now, however I was able to download the BIOS zip you posted at post #7 today. Please wait, let me check
* Edit - both BIOS edits 25/26 look OK to me

@Fernando I think you are referring to post #15 as per @Lost_N_BIOS comment.
No, I cannot boot from NVMe natively yet. It works only if I use Clover installed on a secondary SATA drive.
The reason of first mod attempt failure is unknown, modding was done using UEFITool 0.26 as I already mentioned previously. On two occasions (first original flash with MFlash using UEFI, second with a programmer after fixing the board using stock bios) board was bricked. Hence the conclusion it wasn't bad flash, just bad BIOS. Hence I am on stock BIOS now.
I will probably attempt it once more after @Lost_N_BIOS comments that my other Bios mods look ok, they are different on the binary level than the first. I will not hesitate to share my findings.

The bricked BIOS was possibly due to your guide he was following and asking about initially, which I assume is why he posted his question there, and to me meaning even more reason that the reply/discussions (All) should remain in thread
Bricked BIOS was resolved at post #7, where we picked up yesterday and precisely where the posts were split off to it's own thread. No way am I moving this topic (nor part of it) back to another thread now, that was my point of laughter above at post 18+20
Split topics/discussions and moving stuff around at the drop of a hat drive me crazy, I know you enjoy that though it's your style, so up to you to do whenever you see fit.
Please pay no attention to my replies about this kind of thing if they bother you, I know we all have our style of doing things

@drewstew656 - Yes, if you programmed in 26 and it bricked too, then it's a bad flash. Try M-Flash of BIOS you edited with v25
I edited in my thoughts after checking both at post #20

I hope you dumped your BIOS with FPT and or programmer before you erased it, so you can later fix your serial and if necessary Ethernet MAC ID too (Since you mentioned programming in some stock edited BIOS it sounds like)

But, you already removed it, from the original location, that was my point However, it seems he used UEFITool 26, and then reconfirmed that mod BIOS bricks the board later with a second flash. And I doubt your guide tells anyone to use UEFITool 26, since I know you prefer AFU editing method
I always advise against anyone using UEFITool 26, it makes too many issues in random BIOS edits that V25 doesn't (not always), but that can apply to all tools/version too, so there can't be a general warning against v26 either, but I do always use and suggest v25 and I never use v26 except to confirm error for someone.

So the MMTool bios worked and after flashing it I had to edit my uefi boot entries with EasyUefi. Guess fresh reinstall would do the same but i had already working configuration.
There is "PATA:" device visible in bios but that would load OS in legacy mode. So on this board (MSI-Z68A-GD55) best to boot into UEFI as it is a prerequisite for EasyUEFI to run.
Now it boots from NVMe drive into Clover on EFi partition and then loads MAC OS, so guess you can also say your method for modding works on a Hack8ntosh.
Disclaimer: no drives, no data and no hardware was broken but use at own risk and backup before attempting it.

Transfers are pretty dire. It is Samsung Evo 970 1Tb after all. I was expecting twice as much but I am guessing that is due to hardware and OS driver and has nothing to do with modding BIOS, right?

Remove clover, otherwise no point in mod BIOS. Slower than expected speeds may be due to PCIE 2.0 and what lane width you've given it (probably can only use x2 or x4 lanes anyway), but real speed on these come from PCIE 3.0 (Doubles 2.0 bandwidth results usually)
Ideally, do a clean install to NVME, with no other drives installed into system, then fix or edit BCD later if you need to add other OS links.

So, you never flashed v25 mod BIOS? If not, why?

@Lost_N_BIOS. If I remove clover my hackintosh will not boot. That is the whole point of it to run MacOS from it. I can boot directly from UEFI into windows bypassing Clover (it is on another drive) to test the transfers if you are interested.
About UEFITool v25, no I haven't tried that Bios after all even though it was ready. The reason is - MMTool mod worked to my expectations.

Ohh, sorry, I assumed you were using Clover to boot NVME. Since you were already using clover, there should have been no need for NVME mod BIOS here, but you may have needed to adjust something clover-wise to boot NVME per this guide
[Guide] NVMe-boot without modding your UEFI/BIOS (Clover-EFI bootloader method)

@Lost_N_BIOS the need for NVMe driver in UEFI is so it boots Clover and the OS from one and the same drive. The other drive can be removed. Initial setup was that one drive was used to load clover (SATA) and the other to load the OS (NVMe). Hope it makes sense that new setup is more resilient, as SATA drive failure or removal doesn't affect NVMe drive.

Here are disk transfers on EFI volume under Windows (booted into Windows directly without Clover)

It seems to be using PCIe x4