Hi, i have a Asus Z170-A without the possibility of turning on the computer by USB-keyboard (latest BIOS). According to this thread on a similiar board: https://rog.asus.com/forum/showthread.ph…nymore-on-Z170I
it was an option in earlier BIOSes, but Asus removed it. So it seems like making the BIOS option " XHCI-Handoff" visible should make it work again. I tried looking in amibcp but couldnt find anything. Anyone have any idea here?
@friskies - XHCI Hand-off is still enabled by default, just hidden from user (@ Advanced >> USB Config). What you need enabled is Wake on (Power on by) Keyboard (PS/2) enabled, with default of USB Keyboard and Mouse Simulator left to enabled
This wake option is in Advanced >> APM Configuration << Can you see that submenu? If yes, show me image of what you see, I will make all the hidden settings there visible for you (there is many "Power on by" options)
In APM menu i have: ErP Ready, Restore AC power loss, Power on by PCI-E/PCI, Power on by ring and Power on by RTC
@friskies - Please send me your FPT BIOS region dump, after you unlock BIOS lock via grub
Check BIOS main page and see if ME FW version is shown, if not then download HWINFO64
Then on the large window on left side, expand motherboard and find ME area, inside that get the ME Firmware version.
Once you have that, go to this thread and in the section “C.2” download the matching ME System Tools Package
(ie if ME FW version = 10.x get V10 package, if 9.0-9.1 get V9.1 package, if 9.5 or above get V9.5 package etc)
Intel Management Engine: Drivers, Firmware & System Tools
Once downloaded, inside you will find Flash Programming Tool folder, and inside that a Windows or Win/Win32 folder.
Select that Win folder, hold shift and press right click, choose open command window here (Not power shell).
At the command prompt type the following command and send me the created file to modify >> FPTw.exe -bios -d biosreg.bin
Right after you do that, try to write back the BIOS Region dump and see if you get any error >> FPTw.exe -bios -f biosreg.bin
If you do get error, show me image of the command entered and the error given
^^ This is important step, don’t forget ^^ - You can skip this, we know outcome = error 280 or 368, see guide linked below to unlock
If you are stuck on Win10 and cannot easily get command prompt, and method I mentioned above does not work for you, here is some links that should help
Or, copy all contents from the Flash Programming Tool \ DOS folder to the root of a USB Bootable disk and do the dump from DOS (FPT.exe -bios -d biosreg.bin)
https://www.windowscentral.com/how-add-c…creators-update
https://www.windowscentral.com/add-open-…menu-windows-10
https://www.laptopmag.com/articles/open-…ator-privileges
Or here is simply registry edit that adds “Open command window here as Administrator” to the right click menu
Double-click to install, reboot after install may be required
http://s000.tinyupload.com/index.php?fil…134606820377175
Here’s how to disable BIOS Lock and SMI Lock, follow this guide, start at step #6 since I’ve done 1-5 for you and info is below
[GUIDE] Grub Fix Intel FPT Error 280 or 368 - BIOS Lock Asus/Other Mod BIOS Flash
Rename your .efi file to >> Shell.efi
BIOS Lock Variable to change >> 0x8C6
So, at grub prompt you will type the following, then enter, then reboot and make new FPT BIOS region dump and send to me (Case sensitive) >> setup_var 0x8C6 0x0
Cool, i sent the link to the file on PM. It is only about 14MB, i guess that`s correct as it is only a region
Yes, that is correct, it would only be 13.5MB - You did the BIOS Lock disable via grub, correct? You have to do that before you can flash back in BIOS region
* Edit - @friskies - PM w/ Mod sent - made visible Power on by KB + Mouse
Flash back via >> FPTw.exe -bios -f biosregm.bin
Ok, now it i have "power on by PS/2 keyboard" visible in BIOS, but it doesn`t seem to work with my USB keyboard, USB Keyboard and Mouse Simulator enabled
Test with and without USB Keyboard Sim enabled. And yes, it may not be compatible with 100% of all USB Keyboards, especially not wireless ones too. And ones with USB > PS/2 adapter may not work as well.
Test other USB Keyboards, and all USB Slots (USB 2.0 probably best chance to function properly)