@vismut1822 - You didn't answer my first questions above?? The two before jumper was mentioned. And on jumper, it may not be by the memory, I only mentioned that as a place to not forget to look.

If you want to try to continue past error 167 without using programmer, do the following
Using RU method >> Go to section 2.2 and make bootable USB with RU program, then read 2.3-2.5
http://forum.notebookreview.com/threads/...-issues.812372/

Only you will make changes in "PCHSetup" GUID 4570B7F1-ADE8-4943-8DC3-406472842384 NOT in "Setup" as the guide outlines

Go to the two following offsets in PCHSetup, if either is 01, change to 00 then save and reboot back to windows and try FPT again
0x17
0x6DA

If you just want to use programmer instead, let me know and I will make you BIOS to program in

So.
As for RU, I could not start it. Instead of starting, the usual DELL logo hangs
Secure boot is disabled.
I don't understand why it won't start.
Also you asked me what you can do the modification through the programmer.
I don't want everyone to take apart the back cover of a laptop.
I am ready to sew with the programmer only if there is 100% confidence that it will be possible to flash it the first time.
In this case, if there is no such confidence, then we will use FPT.
But how to use it if I can't start RU.
You also asked that I did not answer the previous two questions.
I personally did not find jumpers. Maybe it is, only on the back of the motherboard. But I refuse to disassemble the motherboard. And there is no certainty that it will be on the back side.

I want to unlock all the defenses of this BIOS as much as possible. But how can we do this, if even the simplest program such as RU cannot be started...
----------------------------

I don't understand, for modifying the BIOS we are not given Measured Boot and Verified boot?
And why do we get a brick through the programmer? Maybe this is the culprit of Boot Guard?
And can FPT help us (if we can bypass error 167 at all?) In modification, since the programmer cannot cope with its task?

I took a close look at my motherboard and found out more about the jumper.
In general, in most cases on motherboards, it lies next to the RAM.
Looking for information on my laptop, I found high resolution pictures of my motherboard
After looking at the photos, I finally realized that there are no jumpers.

@Lost_N_BIOS Can you make a modification?
Thank you in advance

@vismut1822 - To run RU, you need to disable Secure boot, and boot in legacy mode. Can you boot to DOS? If not, how are you making the DOS USB Stick? If Rufus, try this method instead, do only step #1-2

No, jumper would be on the front of the board only, so no need to check back Plus, I did not know this was laptop, there will be no jumper in laptop only desktop.
No, in general it's by bottom of board, near USB headers, only sometimes by memory, but again sorry, I did not know this was laptop so you will not find in laptop
However, this is the question I meant that you didn't answer >> How did you flash BIOS region before when I sent to you? Was you using programmer only/always?

If you can't get RU to boot, and we can't use FPT (Already confirmed at post #27 + 29), then you will have to use programmer.

Sorry, I don't understand what you're asking about Boot Guard? FPT error is not related to boot guard, but rather FPRR (Flash Protected Range Register) or BIOS Lock.
I only see BIOS lock enabled at BIOS settings (setup, NVRAM), FPRR is not, so maybe if we disable BIOS lock 167 goes away, if not then it's in a BIOS module and I may not be able to find to edit/bypass. Plus, it may be in area we can't edit
We can maybe disable the cause of FPT error 167 IF the only way FPRR or BIOS Lock is set is in the BIOS settings, if it's in a BIOS module as well then we may or may not be able to.
If it's only in module, and I can find, then yes, maybe, IF it's not in boot guard covered area

Here is two BIOS below, try this BIOS (winbondMVSSBIOSLock) first, program only 16MB chip and see if boots OK (if yes, test FPT #1-2 from post #28, delete any previous created file first!)
If fails to boot, then there is some check I'm not seeing, and maybe nothing we can do here

Also, then please test this BIOS (winbondSettingCNGTstOnly), this is one of the BIOS/changes from #26 but programmable since you could not test those via FPT
This is test to start checking again to see if we can edit BIOS menu or not. This does not have the bypass 167 changes made above, so both BIOS need to be tested, so we can know if BIOS above lets you FPT past 167 or not, then if so we'll add that to this edit too if this one also works

https://ufile.io/i6hbb2js

So. I asked for the first modification (winbondMVSSBIOSLock)
The laptop started up from him.
I tried to make my dump and flash it (as from post # 28). But there were strange circumstances. Somehow magically the VSS.bin dump began to weigh 768KB !!! How can I understand?
I was still trying to flash it, but we got back to error 167 again.
Sadly I went to flash the second modification (winbondSettingCNGTstOnly)
But the cunning laptop refused to start over. Brick again
In general, error 167 cannot be defeated

@Lost_N_BIOS Hello.
How are you doing with the modification?
Thank you in advance

@Lost_N_BIOS Hello. Is it possible to modify the BIOS?
This is very important to me.

@vismut1822 - vss dump is supposed to be 768KB, this is expected. Program back in winbondMVSSBIOSLock, then try put system to sleep (S3, not hibernate) for one minute, then wake it up and try FPT 1-2 from #28 again (delete any previous created file first)
Since winbondSettingCNGTstOnly bricked, the only way we can change settings here is via NVRAM/Vss change, to current applied setting value only) << These changes can be made by FPT dump/reflash, maybe, if we can get past 167, if not then only via programmer dump/edit/reprogram

@Lost_N_BIOS Tell me, I want to start Thaiphoon Burner, but when I try to press SPD Read, it gives an error.
Can I get around it?

@Lost_N_BIOS Hello.
Unfortunately, I am not able to test the version of the bills with unlocking all hidden settings.
Then let us not continue to study, or rather close this topic due to changes in plans.