After the efi trick, that fiendish being is now under my order, she is equipped with i5-7000 series, which only has two cores. I think if my relative wants her back, then have to find a way to redo again like me or have to pay a reasonable dollars as I have spent at least four days with your suggestion to patch the fake core hole. (My client is using six actual cores at start because it is a desktop tuned by lenovo, It must be flashed-in before delivery)
If I decide to change pictues, I would disable the bios lock. At a moment, itās okay.
One down, three more to go as I rarely know which types of firmware user has been using. And again, I appreiate your suggestion and now doing actually things.
I do not understand this comment you said >> via a being you implied, have read the note
Yes, sorry I grabbed the latest BIOS, if you need me to confirm the 301 BIOS is same then I can, if you canāt get it done. Itās probably same, but there is no guarantee variables are the same always (But HT default setting will almost certainly be the same in all BIOS)
I only know grub I use for these purposes, you can download a copy of that on first post.
If you need more help let me know!
I have used the latest bios to take a look, I successfully disable the hyperthreading.
I might consider to change the splash screen for fun.
@1337umbra - Changing boot/splash image can be tricky, sometimes only certain format (bit depth and size/resolution, not just image type) can be used, so be careful and maybe only do this once you have a flash programmer and SOIC8 test clip cable in your hand
YOu can use AMI ChangeLogo 5.0.0.2 (Google, you will find, if not send me a PM)
I tried to but canāt do in fpt way.
So I stick with Command tricks, which might be essential for later models with the same company.
It is revealed there are two sets of menus in Firmware for ASUS TP501UQK 306.
I do not know what you mean, āyou canāt in FPT wayā?
If you want unlocked BIOS, I can do that for you, but you have to be able to flash mod BIOS or flash FPT (thus disable BIOS lock first)
Hi,
Trying to remove the bios lock default option from my Apex IX bios permanently. Found the variable in the bios dump afr and made note of all the 01 00 hex default values in a long string I searched for in uefitool. This led me to the setupefi Nvram module. There were three of them, but in the first one I found a byte by byte match corresponding to a half dozen default values forward and back. Only problem is this value reoccurs a dozen times in the nvram module. Do I change all of them?
Thanks
@davidm71 - change it in setup module only and test, that may be all you need to edit, this is usually the case. If that does not work, then yes, sometimes you may need to change the value in NVRAM (with BCP first so it also changes in AMITSE/SetupData)
Make 100% sure you are changing the correct thing at NVRAM when you change this, often yes there may be 2-4 etc instances. If you are working on a dump, there may be more, due to āsetupā is repeated copies many times in populated NVRAM volumes (check both volumes if it is dump from board)
If you want to edit the AMITSE/SetupData module manually, without BCP, then extract SetupData āBodyā and edit >> 3F165h change 01 to 00
Also check the default NVRAM (NVRAM External Defaults module >> SubModule >> StdDefaults) module thatās within the main DXE BIOS volume (usually, but not in this case),not the two top NVRAM volumes.
I found it twice in your BIOS, first at second to last volume and second time at last volume. This looks like this in UEFITool if you arenāt sure what I meant, and yes, this is your BIOS
When you edit those volumes, be sure on rebuild all "Padding" and Non-UEFI or Non-Empty-padding files remain there and look the same (may need to use UEFITool 25)
So editing the nvram volumes is optional only if editing the last byte code string from 01 to 00 doesnāt work. Ok. Also thanks for explaining why there were so many copies. Thank you.
Yes, usually you do not need to edit all that I mentioned above (plus the NVRAM volumes at top of BIOS that I assume you were referring to). Usually if you change it in setup module then itās disabled always, until you reflash another BIOS with it enabled.
Sometimes that doesnāt work, and in those cases, simple setting change with AMIBCP will get it. Itās when both donāt, then you dig into all we discussed, and Iāve rarely if ever ran into that
Hi!
I found ābios lockā may not be in the GUID - 899407D7-99FE-43D8-9A21-79EC328CAC21 in some mobos such as DELL T630.
Itās ābios lockā is in the GUID - ABBCE13D-E25A-4D9F-A1F9-2F7710786892
So,I could not modify it by grub.
Do you know how to modify it?Thanks!!!
Try using RU.efi app instead. RU is a great tool for not just changing the values of setup but other volumes. Though I wonder if via grub you can specify guid volumes specifically through other commands. Any how just use RU.
@davidm71
Thanks for your RU.efi
We usually use the "setup_var" to change the volumes of the setup,and I found the "bios lock" in the GUID - ABBCE13D-E25A-4D9F-A1F9-2F7710786892 which name is "platform"(check by the uefitool NE)
I will try the order "platform_var"~~~
Yes, sorry, I need to make clear in the guide if I did not already, BIOS Lock is not always in same GUID or same module by name even and name of module does not always matter for grub either (so always try, then check issue by error outcome).
Also, some modules contain āTextual Mentionā of BIOS lock, but do not control or contain itās setting, so you may be looking at a mention/reference of it and not the actual setting location.
Some BIOS you may need to use modified grub that has setup_var2 or setup_var3 commands. And if BIOS Insyde you may also need to use H2OUVE to change variable, and with that you can specify module you are needing to edit (setup, custom etc).
Some, only direct BIOS mod will work 
What error do you get with normal grub, show me an image of command entered and error given.
Found this guide regarding unlocking descriptors on a Dell laptop:
āME FW Image Re-Flashā and āDisable MEā bios options.
The guy figured out that disabling the variables āDisable MEā and enabling āME firmware reflashā will give him access to his whole bios albeit individually. So was wondering if the very same variables exist on other mainboards and if so help facilitate pinless modding of the firmware in the case of Coffeelake mods for example?
If anyone could do an afr dump of their setup and check? I would but am away from home.
Thanks
ME Re-Flash settings disable ME for one session, so that it can be re-flashed via FPT, this is on many standard Intel boards. Iāve only seen the āDisable MEā on certain (very few) Dellās, and many of those have jumpers for this anyway.
@davidm71 @Lost_N_BIOS
This is the Intel S2600CP
The "bios lock" is in the var 0xA60 and is in the guid "blank"(97E409E6ā¦ā¦) under the "setup".
And when I used the grub,it showed wrong message no matter I typed āsetup_varā or "setup_var2"
āDoes not match expected GUIDā means var 0xA60 donāt exist in the SETUP GUID?
@gloobox - yes that is correct for this BIOS. You may not be able to use setup_var for this BIOS since that is not in āSetupā Or, it may be working/correctly finding the proper module here, but canāt edit like this (Sometimes this happens, even with var2 or var3)
For this youāll have to try H20UVE, try all versions - if you need these let me know and Iāll send you in PM
H2OUVE.exe -gv vars.txt
H2OUVE.exe -gs -all Setup.txt
H2OUVE -gv var-GUID.txt -g 72C5E28C-7783-43A1-8767-FAD73FCCAFA4 -all (If error, remove -all)
You can try with GUID 97E409E6-4CC1-11D9-81F6-000000000000 but that may not work, since there is about 8 other modules with same GUID
The above is to dump only, to write back after edit
H2OUVE.exe -sv varsM.txt
H2OUVE.exe -ss -all Setup.txt
H2OUVE -sv var-GUID.txt -g 72C5E28C-7783-43A1-8767-FAD73FCCAFA4 -all (If error, remove -all)
After you write back anything, dump it again with new āmodā text name, and check that your correct edit was written in, if not write back the original (unless your new dump matches original, if that is the case re-check your write command and try again)
If all the above fails, your only option is mod BIOS
Wanted to share a more convenient way to access the Shell.efi environment without needing a usb drive. Someone else actually wrote about this elsewhere but good to know. Basically what you do is access your Windows system partition and mount it to a drive letter and copy the Shell.efi file to the root of the system partition. According to what I read you need to this under administrative priveledges by restarting explorer.exe under an admin command window. Once the file is copied all you have to do is go into bios and select boot into efi shell. Kind of cool little trick.
@davidm71 - good trick! Some BIOS may need that file named differently, some BIOS look for Shellx64.efi, Iām not sure how that would react in those cases. Maybe a copy of both in place would be OK?