Yes, and it maybe all due to you used BIOS region not meant for your system. I want you to test that with proper BIOS for your system, almost done
Works for your system and works fully and properly may not be the same thing. You’ll have to test mod BIOS made from your system BIOS, with the updated microcodes and see if you have same issue, if so then I’ll hide that option in microcode update BIOS, or you just don’t force a shut down manually
This setting should be rebooting for you anyway, why are you forcing a shut down to begin with? No matter what works, or doesn’t, you shouldn’t be forcing a shut down unless absolutely have to, and if you do in this new BIOS I make for you, then you’ll have to either not use that option, or reflash the second BIOS I make with hidden setting
I’ll include the third BIOS in your package too, updated microcodes, but no pushbutton setting, so you can use if you want, rest of public posted BIOS I will remove that option, no one needs it anyway since BIOS you can reboot via save and exit, or discard and exit, and if you need windows boot options push F8 on bootup as normally would do.
*Edit - @bzv - here is three corrected BIOS regions for you, flash these via FPTw -bios -f filename.bin (you can shorten the names I used, just remember which is which)
http://s000.tinyupload.com/index.php?fil…251007078828816
Please test the updated microcode one first (bzv-Orig-Mod-Micro.bin), since this now has your proper dual NVRAM volumes, I want to see if you still have that same issue with the pushbutton shut down.
If you do still have the issue, then I will hide that option in the microcode updated BIOS packages (already included for you >> bzv-Orig-Mod-Micro-NoPush)
The file named bzv-Orig-Mod.bin is your original FPT dump, with the mods applied correctly, and nothing else changed (So still old microcodes)
All have your serial, UUID etc, as in original dump.
@Lost_N_BIOS
The orig_mod_micro remains black after flashed in can’t boot.
And the orig_mod can boot but doestn’t have unlocked config. The SN and UUID exist in this version.
Sorry @bzv - maybe I mixed up the files during your edit! I’ll move it all to one folder for you only and do it again!
Give me a minute if you’re hear reading this now. * Edit - yes, that’s what happened, I checked your orig-mod and it’s missing the unlock mod, due to that I probably messed it all up since all others built from that one once I was done with it.
Repack coming for you shortly!
* Edit @ bzv - sorry about that mixup! Here is corrected BIOS files for you, should all be OK this time!
http://s000.tinyupload.com/index.php?fil…578819751382472
The updated microcode version still can’t boot.
Non microcode update version can works and have unlocked settings. I think there may be some problem with the microcode.
@bzv - Thanks for report back! Must be UEFITool messing with a padding file somewhere maybe, I saw new version removed it, so used older as usual and it stayed, maybe I missed one. I’ll have to check again or use MMTool.
Well send you repack in a second… again 
Sorry about this!
*Edit - @bzv - It’s weird that the other BIOS with microcode update worked for you previously, I don’t remember using MMTool on that BIOS for the original microcode edits, but maybe that BIOS handles the changes differently than your original?
The microcodes are fine, you’ve already used them before. Who knows, I can’t see any issue with the mod files once done? Try these now instead - http://s000.tinyupload.com/index.php?fil…152676088294219
@Lost_N_BIOS This version bzv-Orig-Mod3Micro.bin works well without any problem. Force close at any situation (including push button reset) also no influence. I think this time microcode update works correctly.
Thank you very much.
@bzv - thanks for update and you’re welcome, glad it’s finally OK! So, no need to hide pushbutton then either you agree? Maybe it was only fluke with last batch, since it worked OK for pcfr33k, or due to you using on that system maybe?
But thanks and I’m glad we had issue this time, for all from now on I will use MMTool to do microcode just in case 
Sorry all, I’ve been on work travel and plan to catch up with PMs and the thread the next few days … @Lost_N_BIOS , I will send you my full BIOS dump later if no one else has done so.
@nimaim - good to see you back! I’ve got a dump from pcfr33k, so no need now but thank you. I think the best move is our last PM I sent you early this morning, working on finishing that up tonight
Copy that, thank you very much for doing that, it’s much appreciated. I know it takes a lot of time to put together a complete step by step guide.
Thanks @nimaim - hopefully it will be clear and easy enough for all to follow along!
Got tied up into some BIOS editing for someone yesterday, so didn’t have time to wrap that up yet, hopefully I can do it tonight
@Zeddi - BIOS unlock on all these models achieved, if you need mod BIOS send me a BIOS region dump via FPT and I will send you unlocked BIOS region back.
I have a BIOS mod guide done for this for all models, with modified files and instructions on how to use/apply, just trying to find time to final it all up and get posted for everyone
Due to how the BIOS is secured, we can’t pass out stock modified BIOS for flashing, because only way to flash mod BIOS is via FPT, so user must dump their own BIOS region via FPT, and apply the modified files to that, then reflash it via FPT
It’s three BIOS modules you replace, that’s it, then reflash modified region.
Yes flashing via AFU is not working (secure policy fail, it does not like modded, unsigned BIOSes) and would require a lot of time to try various ways around it. At this point I wouldn’t be able to test much as I now set up my laptop and need it for work and I also think LNB has spent more than enough time helping us through this (thread is going on 15 pages!). I think users doing their own FPT mods (with the help of LNB’s guide, which is coming soon) is best. That way, we are also not responsible for anyone bricking their laptops either, as it is on them to mod and flash it.
@nimaim - Pcfr33k and I spent a good week or more, probably tested at least 50+ or more AFU command line assembly edits, sometimes close, but never any cigars 
. Maybe if I setup a similar system here with this type of internal BIOS security capsule I could figure it out.
But I think it’s probably just easier to put out a good guide and the modified files and then users can mod and flash at their own risk, or request help to make mod BIOS from their dump if they still can’t follow guide.
And I will add to the end of the guide, CH341A and SOIC8 test clip cables = $5 or so
Everyone flashing in mod BIOS should get a set due to new revealed options may leave some with black LCD while trying to mess with video and even @pcfr33k method to blind flash here #169 and here #181 may not be digestible by everyone that causes this on their end.
Oh wow, did not know you guys spent so much time on that. Thank you @pcf33k and @Lost_N_BIOS. I guess it was worth trying the easy / standard methods.
Yep guide is just easier for everyone. That way we also don’t need to bug you every time a new version is released 
@nimaim - yes, we spent a lot of time editing and testing many changes in PM’s while you were gone for a while.
Since you mentioned new version BIOS releases, which should probably have mod redone again directly in case of module size changes or settings additions/removals, do you think I should go ahead and add the “how to mod for pro’s” to the end of the guide too, in a spoiler too?
That would be the mod info I posted here in #94/99 (I think), but refined.
It’s easier to have everything in one place so I would say yes please, if you get a chance, just throw it in there as an "all in one how to" guide. Or you can just link to those posts, whatever is more convenient. Otherwise it is hard to track down individual posts in such a long thread.
@nimaim :
Thanks for having started this interesting discussion, which contains a lot of information about how to unlock the related BIOS options. Since your thread has become quite popular, I have stickied it today.
Here is a tiny suggestion: It would be fine, if you could shorten the thread title (it is effectively too long).
What about "[SOLVED] How to unlock BIOS options of rebranded TONGFANG chassis systems?"
Thanks!
Dieter (alias Fernando)
Sure no problem, will change it as soon as I get on my PC …
EDIT: @Fernando sorry I must be blind but I don’t see where the option is to change thread title. If you wish, feel free to do it as I’m perfectly fine with the title you suggested. Otherwise, please let me know where I would do it.