Single setting has nothing to do with menus working, in regards to what we've been discussing past 2-3 pages. The EIST and related were bugged, possibly due to or relating to the HPET being bugged. The answer is the same, no matter the method used to enable a root folder, hardware does not apply to visible or not setting or sub-menu once root enabled.

Setting user to the unnamed folder, or settings within have no effect on visibility, it will remain hidden. Naming the folder breaks the entire BIOS too, so don't go there next. You were fine with the BIOS as-is now that HPET is working, don't waste time thinking back 9 pages to try and do something we've already been through
I used AMIBCP when testing with that stuff on 100 series board, there is no other method to mess with that folder because it's unnamed and not used in the actual BIOS setup like the rest of the settings.
Nothing more you can don on HPET except be happy that it's now working, and that you know how to change that setting again if you need set the other way in the future.

You cannot test at point "A" because you have not switched out hardware to know it's only doing that because of your particular hardware, it may do whatever you are observing with any/all hardware or it may not
Same applies towards "B/C" for some settings, they may not appear due to hidden, not just incompatible with current hardware, and even if tied to another setting above they still may be hidden when that setting is enabled or disabled, if not set to user available.

Hiding an option because one above it may disable/hide it depending on setting makes no sense (at you example 2), what if you don't set that setting to that and rather want to adjust those two settings you just said to hide due to above setting? If you know a certain setting abve negates one below, and you use that setting, obviously you'd know the setting below is not relevant or doesn't need changed due to what you set. But if you hide those, and then don't want to use that setting that disabled them, now you can't use the other options for those set of settings because you hid the other two based on a single choice for the above setting

You are thinking about this far too much, and too hard. Yes, some/few things may be how you think, but many are not even if you are observing them how you are now with only a single hardware test, I know from experience this is not the case/reason why settings are set or not set in the ways they are/can be.

We can go on forever, but you wanted all options exposed, so I did, then you didn't, but now you are in control of what is enabled for you so if you don't want to see something now matter what disable it and it's gone

You can ask, and I will try to answer, but when you don't understand/accept/believe my answer why ask and how can you learn. You cannot base your learning of "This is how it is/should be due to this" based on your single hardware exposure to that board and that BIOS, what you are seeing now only applies to your exact setup and your current desire to see things look how you want, and not everyone reading this thread or using these BIOS will have your exact setup, that is why I tried to steer you away from hiding or setting anything based on your hardware. Same applies here to you as well, what if you change out CPU in 6 months or a year, then you have to edit BIOS again to possibly expose settings you hid this time around when you could have enabled them and left even though your current CPU may not support. You can set how you want of course, but it only applies to you, your desires for how the BIOS looks, and the current hardware, it does not apply to the setting itself or how it should be set if wanting to enable for all users to use, that's just how you want it for your hardware and how you think things should be.

For the other methods used, normally you use one or the other, or both, and then user will have access to some settings at the root level, but not always, it all depends on how the OEM coded things out. Often you gain root visibility, but everything is blank, or maybe 1-2 settings out of 20+ in a section, so rest must be unhidden after that.
These methods only apply to hidden main folders like chipset or a second advanced when those are hidden, and the above is true for any method. Methods in this instance are AMIBCP, 46 02 (hidden) > 47 02 (visible), or Boolean String method 01000101 (Hidden menu in the middle) to 0101010101 (all menu visible)- example, not actual string to look for in BIOS.

Which method used depends on the BIOS too, some only have one method you can use, others like this one both may apply. There is nothing to play with in that regard on this BIOS, except for chipset which required both 46 02 > 47 02, or Boolean String method changes to the setup module before the menu was visible to you. That requires 3 tools, UEFITool (Or MMTool) to extract the setup module or it's PE32 image, and then Universal IFR extractor to find the location to change for chipset, and then hex editor to change both the 46 02 to 47 02 and to change the default Boolean string values for the entire main menu string. These methods are much more involved the opening a BIOS file in a program and changing a setting, but if you want me to show you more about this I can try as time permits.

Yes, mine are not either I guess Default setting is not correct setting for many options, if you want to use them, even for your hardware. You are correct though, you do not need to force user on everything, only what you want, but that does not mean things you do not want, use, or think apply, should remain hidden/default in an unlocked BIOS. I do get what you mean, but don't think you got what I meant, but in the end it doesn't matter only what you want to see in the BIOS is what you can set and next guy can have someone else unlock fully.

Yes, other methods are really only valid for the actual root folders, such as MAIN, Chipset, Advanced etc. Sub-folders below that can be enabled using AMIBCP once main root is enabled, in this instance that was only needed for chipset since Advanced was already visible.

I will fix BIOS from post #117 tonight!

*edit - @akm here is fixed BIOS files

https://www.sendspace.com/file/l57ff0

I get what you mean too, we just see it differently due to I'm always unlocking it all for people You are welcome, and I'm happy to have helped you reach your desired goal with the BIOS!

1. FIT Table correction, here is a simple guide, see also page 3 post 35 too - [GUIDE] AMI INTEL CPU Microcode Update Guide
2. ME Update is done via the ME Cleanup Guide here, tools and ME repositories are in other sticky threads in this section of the forum - [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
3. There is no guides for the unhide chipset methods, well here is partial guide on one of the two used methods 46 02 to 47 02 - https://puissanceled.com/vrac/Bios_modding/EN.html
The other method used this time around, changing the Boolean string from (non-valid example) 01010000010100 to 01010101010101 Is just something you learn to do from other posts on the subject
Such as magic string, unlock chipset string, etc, here is a general blog post about it - http://kulasov.blogspot.com/2013/08/over...book-n56vm.html
But you have to learn as you go, guess and test, know from past experience to recognize, compare setup module IFR, AMIBCP layout and actual BIOS images to see current displayed tabs etc.

For #3, not all methods are always required, sometimes you only need one of the three, other times two, sometimes three, sometimes only AMIBCP, and finally somettimes nothing works.
And it's always best to have a flash programmer and SOIC8 test clip cable in hand before flashing any modified BIOS, especially when you start doing your own modding to learn, they are so cheap there is no excuse for anyone to not have a set.

Forgot about CPU microcode update (always do that before FIT corrections, actually always make FIT correction the last thing you do). Microcode updates can be done many ways, using UEFITool and HEX, using UBU tool, using MMTool, using cbrom on certain older BIOS, all depends on the BIOS.
There's a few simple guides here in the sticky threads - [HOT] CPU Microcode Optimization

If you need help with the other laptops BIOS, let me know!

You're welcome! Yes, it will take some time to learn, and lots of editing and some mistakes probably too, that is why I said it's best to get a flash programmer now rather than later when you are forced to need it to recover.

On the FIT/Guide. I am not sure what you mean, step #5 is the only step that applies to correcting the FIT table, no steps above that apply to fixing FIT. The above steps are about actually updating/changing microcode versions in the BIOS (Not in FIT), which you are not doing, so you can ignore all that and only use step #5 and comments on page 3 too for better understanding of the math/tool to use etc. You are not adding or updating any microcodes at all when fixing FIT. All you are doing is correcting the FIT tables locations of the microcodes themselves, that are already/currently in the BIOS. If you don't understand from the guide what they mean, maybe I could explain it in a better way making a mini guide?

What is your full Samsung model name and I will see if I can find stock BIOS for you, but yes please go ahead and take backups using both those methods, so you have safe copy of board details.
Yes, if that FPT command passes without error then Flash Descriptor is unlocked, you can verify by opening dumped rom in UEFITool and select the descriptor entry and then look on right side and see if all is read/write for FD/BIOS/ME Etc.

Yes, those are fine if you can't find cheaper/better deals on ebay search. I've recently learned the black/gold CH341A is OK to use and maybe even better, so if you can find that one for similar price it may be best choice.

I know what you mean, I didn't get it either when I first started learning how to fix FIT. It may really require it's own little mini guide with a lot more steps/images shown to best understand how it all works, especially for those not familiar with editing BIOS already.
I will try to make one when I have some time!

Thanks, I will look into finding stock BIOS for that Samsung tonight, mainly so we can see default update tool.

The one you ordered is fine, just a little slower.

-bios is the only dump you need really, usually you can update ME via FW Update tool if needed, or possibly we can edit BIOS region to allow ME-reflash.

FD itself is almost always locked for write, but not for read. To verify what it has for read/write for all regions you take that flash descriptor region (desc.bin) and look in hex editor or copy the relevant lines into via hex editor into a BIOS you know has a descriptor in it, then save and check the BIOS with UEFItool
Section B here explains how to check via hex - [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing

BIOS region you posted opens fine for me in UEFITool NE Alpha 51 and UEFITool 22.4 or 25 - if you can't figure it out about the FD, upload that desc.bin and I will show you what it's setting.

I am not sure on BD-PROCHOT# I'd have to look at the BIOS. Are you sure PROCHOT# itself is not being tripped?

Does this Samsung BIOS updater allow you to download and save a BIOS file/update (Not flash, just download)?
https://drivers.softpedia.com/get/BIOS/S...Windows-7.shtml

If yes, please download (on the laptop) and send me the files it fetches.