@Binarycraft - See E.1 here, then once done w/ E.1 (pinmod), you need to see section B, spoiler 2, image 1 or 2 from the same thread. Once you do this, do not reboot until you’ve written back in modified FD with FPT
[Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing
Dump FD >> FPTw.exe -desc -d fd.bin
Flash back mod FD >> FPTw.exe -desc -f modfd.bin
This only works once pinmod is applied. Tape off all other pins so you don’t kill your audio 
@Lost_N_BIOS , BIOS1 does not switch to BIOS2 while working in BIOS, in Windows the same thing.
Next to the BIOS chips is a 10-pin connector (1-pin broken), that is, 9-pin, is it designed to connect the programmer?
I remembered about "pinmod", I read about it before, my audio chip = Realtek ALC1220 (1-pin DVDD + 5-pin SDATA_OUT), which is relabeled in SupremFX.
@Binarycraft ,
If your board is anything like my Apex IX you have an SPI header on your board that you can attach a programmer to reflash your specific rom chip depending on which jumper is attached to left or right designating correct bios chip. In this case using a programmer pin mod or unlocked bios is not necessary. Thats only for doing it the flashback way. Specifics on how to wire up a programmer is available on Elmors lab site. I also posted notes in another thread here on Winraid somewhere. Only thing is be very careful if you hot flash ie reposition jumper after booting and running FPTW. I know a guy that borked his board doing that though could have been due to other reasons. Depending on what you want to do though you would need a bios with its write descriptors unlocked in anycase. Should have no problem doing a basic bios upgrade modded or not however coffeelake mods need a completelt unlocked bios.
@Binarycraft , it does in both, ignore the LED’s, BIOS is not active or in use in either situation I mentioned.
Yes, pinout you mention can be used to program BIOS, only the active one while board is powered down. Do as I mentioned and you will have this sorted out, trust me!
@davidm71 - what I said is the only way he can fix his BIOS, in the current situation, aside from having a flash programmer, this is why I explained options to him in that way. He is not trying to normally flash any BIOS, nor flashback etc.
BIOS switch can be moved while in windows or EZ Flash, BIOS is already loaded into memory while in EZ Flash thus not active and in windows it’s not active at all. So whatever you saw mess up someone’s board with switch and FPT was something he did wrong with FPT
If he wants to go the safe and easy way, best to order a flash programmer and SOIC8 test clip with cable if BIOS is soldered to board, or U Type Flat IC extractor if BIOS is in socket. Otherwise, due to his current situation and what he needs to fix, how I described above is only way to do that.
Sorry I misunderstood.
Just to add s.th. about USB Sticks. About many users using higher capacity USb flash drives on later dates of times, as of today, there quite many USB flash drives offered e.g. with minimum 32GB at quite low costs.
I had issue with e.g. Asrock Instant flash (Asrock Z77 Pro4, even with UEFI), that it didn’t detect my 32GB USB flash drive, (even when freshly zeroed Partiton table, and freshly partitioned, formatted with FAT32 or FAT16 etc),. Also taken one Primary Partition from start sector 2048, as the other drive has, that was detected by Instant flash very well.
The workaround was, for also to make the 32GB USB flash drive work, was to create a Primary Partition not using whole USB pen drive (e.g. 32GB),
so to create smaller partiton only (16GB). After that Asrock Instant Flash also detected the 32GB USB-stick by using a smaller partition (16GB).
Maybe this applies here too, as many flash drives today have often higher capacities, which can make problems with certain programs, not alaways programmed so good.
Hi friend.
I cannot unlock Lenovo V130-15IKB bios for flash. tell me how to make changes (change "bios lock"). Address 0x17 is not real.
1) fptw -d b.rom -bios = OK
2) fptw -f b.rom -bios = error: Error 368: Failed to disable write protection for the BIOS space. FPT Operation Failed.
3) uefitool 0.27 search "bios lock" and "extract as is" "1.sct"
4) uefitool NE_A51 extract as is "Section_PE32_image_E6A7A1CE-5881-4B49-80BE-69C91811685C_Setup.sct"
5) run two copy Universal IFR Extractor7.exe and extract files (1 IFR.txt and Section_PE32_image_E6A7A1CE-5881-4B49-80BE-69C91811685C_Setup IFR.txt)
6) bios lock search result in "1 IFR.txt" :
"0x8157A Form: Security Configuration, FormId: 0x103D {01 86 3D 10 FA 05}
0x81580 Subtitle: Statement.Prompt: Security Configuration, Flags: 0x0 {02 87 FA 05 00 00 00}
0x81587 End {29 02}
0x81589 Subtitle: Statement.Prompt: , Flags: 0x0 {02 87 02 00 00 00 00}
0x81590 End {29 02}
0x81592 One Of: RTC Lock, VarStoreInfo (VarOffset/VarName): 0x16, VarStore: 0x5, QuestionId: 0x95A, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 FC 05 FD 05 5A 09 05 00 16 00 10 10 00 01 00}
0x815A3 One Of Option: Disabled, Value (8 bit): 0x0 {09 07 04 00 00 00 00}
0x815AA One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 07 03 00 30 00 01}
0x815B1 End One Of {29 02}
0x815B3 Suppress If {0A 82}
0x815B5 QuestionId: 0x211 equals value in list (0x1) {14 08 11 02 01 00 01 00}
0x815BD One Of: BIOS Lock, VarStoreInfo (VarOffset/VarName): 0x17, VarStore: 0x5, QuestionId: 0x95B, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 FE 05 FF 05 5B 09 05 00 17 00 10 10 00 01 00}
0x815CE One Of Option: Disabled, Value (8 bit): 0x0 {09 07 04 00 00 00 00}
0x815D5 One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 07 03 00 30 00 01}
0x815DC Default: DefaultId: 0x0, Value (Other) {5B 85 00 00 08}
0x815E1 Value {5A 82}
0x815E3 64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}
0x815ED End {29 02}
0x815EF End {29 02}
0x815F1 End One Of {29 02}
0x815F3 End If {29 02}
0x815F5 End Form {29 02}"
boot from uefi usb flash: enter (for check) setup_var 0x17 - result : 0x00
But it should be 0x01. And address 0x17 looks unreal. what to change? how to do? help me please
0x17 - unreal address
Bios dump (via fptw) and ifr text file attached.
help me please
1 IFR.txt (1.59 MB)
b1.zip (5.03 MB)
I want to report to anyone who will be interested that after reading similar situations on the forum, I found these variables (bios lock) in the "pchsetup" area.
Also I see there are similar variables that are in other areas for example: bios guard in area "cpusetup", me fw Image re-flash in area "mesetup".
I just ask you to tell me how to understand which variable is related to which area after unpacking the ifr extractor?
can I use this method for dell’s laptop bios ?
@alllus - BIOS Lock variable is never same in all BIOS, you have to check what the variable is for your own system
As for Insyde BIOS, this is best done by dumping vars (NVRAM) with H2OUVE, edit, then flash back. Sometimes this does not work and you need flash programmer, maybe 10-20% of the time
Make a thread for your specific board and will help you do all this. From what you show above, I did not check personally, but it does look like 0x17 is your correct BIOS Lock variable (Yes, that is correct, and real, if that is your IFR output above)
For Insyde you may also need to check SMI lock, or FPRR. BIOS lock already 00, means nothing to do there, this is not the cause of 368.
Sometimes, BIOS Lock, or SMI lock, or FPRR is set within a module, not BIOS settings/NVRAM, and in those cases is where you would be forced to use flash programmer like CH341A
ONce you make a thread, please link stock BIOS download page (not the BIOS), and give full model of system there too.
Then, also tell me what it is you are trying to do, and show me output of this command >> FPTw.exe -i
BIOS Guard is not related to anything here
@cuongvfc - Some yes, some no, all depends on the BIOS type
how do I know what’s my bios type? can you show me how to check that ?
@cuongvfc - You can show me image of the BIOS, or link me to the BIOS Download page (Not direct BIOS Link), and I will tell you.
Many Dell (not Alienware) BIOS, there is not much to edit/reveal, what are you wanting to do?
This error happend when i was flashing my asus modded bios. Help me please.
Error 201: [FPTw64.exe] cannot be run on the current platform.
My board is p8z77vlx, modded bios from a backup one.
@sonbd2
I already saw ur other posts… this command is to run in a CMD Admin window, when running the command, the path given to the command and the place of the files must be the same.
Ex: C:\FPT (files r here), then the the command must be C:\FPT\FPTw64.exe (options next)
FPT.exe for 32bit OS and FPTw64.exe for 64bits OS, u cant run 64bits apps in a 32bits OS.
Usually a user that doesnt know this easy steps… is a user in great risk of breaking the systems when playing with bios mod files…
The tool Intel FPT can be very dangerous and powerfull for such users, ur warned.
I did like: press Shift + right click in the folder to open elevated command, so i think it’s hard to be wrong path.
@sonbd2
There is an Asus Suite 2 trick flashing method for your board. If the method does not work correctly, this post may help.
Hello,
Please, help me with p. 3
3. Open Universal IFR Extractor and browse to the module you extracted above. "Protocol" will show Green UEFI, this means IFR can be extracted from this module.
Wait a few seconds, then hit extract and save txt file with similar name so you know what module you obtained the IFR from, usually this will be auto-named for you but not always.
I have got red text "protocol unknown". How to find exact what must export "as is" under UEFItool by PE32 / guid? I dont understand. I tried by guid from example, but it is incorrect as I understood.
I trying got vars for unlocking but still unsuccesful 
My backup of main bios in attach and full bios dump also.
bios_dumps.zip (5.67 MB)
It is on the Setup Section, Found it on GUID 899407D7-99FE-43D8-9A21-79EC328CAC21, here i attach the .sct and IFR.txt you needed. if you want to edit the .sct files, use Hex editor such as HXD. if you want to replace the section in subguid 97E409E6-4CC1-11D9-81F6-000000000000, then use the editted .sct file, and right click on the subguid 97E on Setup section, choose replace as is, and save the file.
setup.rar (267 KB)
TUF GAMING H570-PRO
Can you help with Error 167: Protected Range Registers are currently set by BIOS, preventing flash access?
i tried your guide and it didn’t help, anyway getting this error
When i type Bios Lock in search in UEFItool it sends me in right place PE32 but theres two findings
After extract it finds Bios Lock but it is named “Variable”
i tried to turn off this thing, everything went well but i still getting error in FPT