here is my origin amitse setupdata and setup / modded (unsuppressed, access level 1) amitse setupdata and setup .
I changed it via UEFITOOL 0.28 and occured error 167 fprr lock
I used Modgrubshell 2.06 (in first post link) and change value.
setup_var_cv CpuSetup 0xE1 0x1 0x0
setup_var_cv PchSetup 0x683 0x1 0x0
setup_var_cv PchSetup 0x1C 0x1 0x0
first you cannot flash modified bios with fptw without removing first ERROR 167 and all bios lock error, i mentioned before at now you only use UEFI editor only for searching all lock enabled by default in bios, use uefi editor search funtion with keyword lock to find all value with graphical UI, and see value if it 01 (it enabled by default)
so you need modgrubsell uefi (temporary) at first to altering all BIOS lock in your running bios to disabled mode, after that unlocked we can can flash modified bios you do in UEFI Editor +Uefi Tools in fptw without restriction
Edit: try disable FPRR,BIOS LOCK with modgrubshell and post here screnshoot fptw error
I used modgrubshell uefi tool first. Not dumped it first.
First, I dumped it to find FPRR, BIOS LOCK VAROFFSET.
Second, I put my usb in the laptop for run modgrubshell 2.06.
Third, I changed varoffset value via setup_var_cv command
And I dump again, use for change my uefi setting. and replaced it via uefitool 0.28.
(extracted by UEFITOOL A62)
But nothing changed…
BTW, thanks for your discussion, i use it for change user level (09-> 1D)
(it’s verbosed txt file, and i found bios lock varoffset 0xE31)
(What’s different 0x1C{it found via UBU v1.79, and i checked it off}?)
Where did you read the instructions to use Intel FPT tool???
Your system uses Intel ME 11, not 15 and the respective driver also needs to be installed in the OS.
EDIT: Flash Programming Tool Version 15.40.16.2534, you blind or what?
first write it in uefi grub (Secure boot must disabled) setup_var_cv VarStore VarOffset Size Value
setup_var_cv PchSetup 0x683 0x1 0x0
after that confirmation value by read value with command setup_var_cv VarStore VarOffset Size
setup_var_cv PchSetup 0x683 0x1
you will succesfully dumped at first , FPRR lock do not prevent from dumping but doest now allow for flashing
i see your command in grubshell it only for writing data, you missing for reading current data, for now only focus only to 0x683 (FPRR) leaving 0x1c varstore
, it possible your bios setting get altered by some lock mechanism (set to default again) or we get wrong pchsetup (some bios use dual pch id with same id different but have sub id) we need confirm that first
1.Read current data
setup_var_cv PchSetup 0x683 0x1
see at info set offset 0x683 is: (see data given by Modgrubshell) it must 0x1 (enabled), if it disabled 0x0 so is wrong pch data we worked ) out there i see some vendor using dual id
try change to 0x0 (disabled)
setup_var_cv PchSetup 0x683 0x1 0x0
reboot PC and going again to Grubshell
3. read again data
setup_var_cv PchSetup 0x683 0x1
see at info set offset 0x683 is: (see data given by Modgrubshell) it must 0x0 , if it going back to 0x1 (there something make that setting going to default)
Notes
Recent firmwares often stores BIOS settings into multiple varstores, and sometimes most of them are not in default “Setup” name. setup_var_cv allows accessing varying size variables in varstore with the given name.
based on notes makesure GUID in IFR is same as in showing in UEFI Shell, liek this example
setup_var.efi <OFFSET> [<VALUE>] [-s <VALUE_SIZE>] [-n <VAR_NAME>] [-i <VAR_ID>]
OFFSET: The offset of value to be altered in the UEFI variable.
VALUE: The new value to write, capped at 64-bit. If not specified, the value at OFFSET will be read and shown.
VALUE_SIZE: Bytes of value to write, must be equal or larger than the size of <VALUE>, defaults to 0x1.
VAR_NAME: The name of UEFI variable to be altered, defaults to "Setup".
VAR_ID: Unique id for distinguishing variables with same name, which will be provided by setup_var.efi (when required).
OFFSET, VALUE, VALUE_SIZE and VAR_ID are numbers, and must be specified in hexadecimal with prefix "0x".
The program defaults to little endian for values ONLY while operating UEFI variables,
though it's recommended to only operate on one byte if you are not sure what this is or means.
Example: .\setup_var.efi 0x10E 0x1a -n CpuSetup
all config edited by ModGrubShell normally default is not change permanently or not affect the dumped bios or original bios, it only altered default position of uefi config (we called bios settings file), if we want to apply that to permanent it need to be flashing
