recently updated ME Firmware to Latest available (v11.8.60.3561) using FWUpdate, also replaced Bios Logo with Custom Logo
but can’t enable Hidden Menus. tried AMIBCP that didn’t change anything so i reverted to original Bios.
i’m interested in SATA, I2C and GFX related settings (DVMT) but having everything unlocked will be much better.
attaching FPT Bios dump
Edit* added Pictures of current Bios Setup Menu
bios.zip (3.29 MB)
Menu Pictures.zip (1.03 MB)
@chilledHamza - Great you added stock BIOS Images, thanks. Are you familiar with hex editing and using UEFITool?You added exit page twice and no boot image, can you please correct, and also add full image of MAIN page too (Blur out what you want, I just need to see all options/settings/info entries there) - never mind, not relevant since BIOS only has one of each
When you say you tried AMIBCP, do you mean you set User here? If yes, OK, asking to be sure you were trying correct location before doing anything.
Sometimes you still need to set User there, but on top of other changes first, other times only other changes are needed
If you are familiar with hex editing, I can tell you how to unlock, if not let me know and I can do it.
Yes i did change it to user, and all (almost) the sub menus in there too.
i know hex editing (not much), i can give it a try.
but i’d prefer you to do it, as i’m new to this. i still would like to know the process though.
This BIOS needs an edit at AMITSE PE32 module, and then may or may not still need AMIBCP Access set to User at root of setup for the main menus as shown above (I’ll make you both, one BIOS without AMIBCP change, one with + AMITSE edit).
Then some submenus may still need further enabled, same for some individual settings too. This may need done at the root of the main menu holding the sub, or directly at individual settings.
That may still not make some subs/settings visible, a further edit may be required on certain ones to unsuppress them within the Setup PE32 module (This is done via IFR and Hex edit)
I can’t tell on my end which those will be, you’ll have to try any making the AMIBCP changes for any you see missing still, and then if no luck let me know exactly what sub or settings you need made visible still.
If you want to try the AMITSE edit yourself, this one is easy, extract the AMITSE PE32 body via UEFITool, and then edit, then replace body. Here is the edit
@463C0
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 10 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 12 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00 << FF the >> 12 27
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 13 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00 << FF the >> 13 27
So it looks like this after edit
@463C0
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 10 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 FF FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
4a 10 59 7b 0d c0 58 41 87 ff f0 4d 63 96 a9 15 FF FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Or, here is mod BIOS if you don’t want to jump in, try M1 first (this is without AMIBCP edits), then if no Advanced or Chipset, then use M2.
And from there, you can further enable submenus or settings inside if they are missing, any you can’t make appear let me know and I will edit or show you those edits (These will be at Setup PE32 Module)
Flasback via >> FPTw.exe -bios -f filename.bin
http://s000.tinyupload.com/index.php?fil…794912025135726
Thank you very much for your help,
I flashed both and they look same to me (with Advanced/Chipset visible in both + sub menus); everything else is fine, only thing missing that i want to try is Touch Panel setting.
other than that everything else looks fine.
Thanks again
@chilledHamza - Thanks, and good to hear it! So, use BIOS M1 and build from there then, that means M2 w/ AMIBCP edit not needed for Adv/Chipset at root level, only that AMITSE edit I showed above.
On the touch panel setting, did you try to set Access to User on touch panel setting (On both options), and still didn’t show up? If yes, then you need to make this change, or use the BIOS I’ll provide below.
In UEFITool, find “Setup” module via Search >> GUID >> 899407D7-99FE-43D8-9A21-79EC328CAC21, then expand and extract the PE32 module as-is and edit as follows using hex editor, then once done editing replace PE32 module as-is
One Of: Touch Panel, VarStoreInfo (VarOffset/VarName): 0x2AD, VarStore: 0x1, QuestionId: 0x969, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 D6 0F D7 0F 69 09 01 00 AD 02 10 10 00 01 00} << Search via hex to find this string, following that will be the settings below
One Of Option: SPI Touch, Value (8 bit): 0x0 (default) {09 07 D8 0F 30 00 00} << Move this “30” to below setting to make it “Default”, change “30” here to "00"
One Of Option: I2C Touch, Value (8 bit): 0x1 {09 07 D9 0F 00 00 01} << “30” from above will go here, so you’re switching the default location of “30” from one to the other
One Of: Auto Detect Touch Panel, VarStoreInfo (VarOffset/VarName): 0x274, VarStore: 0x1, QuestionId: 0x9A0, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 FE 0F FF 0F A0 09 01 00 74 02 10 10 00 01 00} << Search via hex to find this string, following that will be the settings below
One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 07 99 00 30 00 00} << Same as above, change 30 to 00 here
One Of Option: Enabled, Value (8 bit): 0x1 {09 07 98 00 00 00 01} << Same as above, change 00 here to 30
And here’s how that will look after being edited
One Of: Touch Panel, VarStoreInfo (VarOffset/VarName): 0x2AD, VarStore: 0x1, QuestionId: 0x969, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 D6 0F D7 0F 69 09 01 00 AD 02 10 10 00 01 00}
One Of Option: SPI Touch, Value (8 bit): 0x0 (default) {09 07 D8 0F 00 00 00} << “Default” comment will move in IFR output to setting below once this edit is applied
One Of Option: I2C Touch, Value (8 bit): 0x1 {09 07 D9 0F 30 00 01}
One Of: Auto Detect Touch Panel, VarStoreInfo (VarOffset/VarName): 0x274, VarStore: 0x1, QuestionId: 0x9A0, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 91 FE 0F FF 0F A0 09 01 00 74 02 10 10 00 01 00}
One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 07 99 00 00 00 00} << Same as above
One Of Option: Enabled, Value (8 bit): 0x1 {09 07 98 00 30 00 01}
http://s000.tinyupload.com/index.php?fil…981492038190975
I didn’t try the AMIBCP edits (not on your provided .bin, but I did try in the past without the AMITSC), also I fashed provided m1-touch.bin but Touch Panel settings didn’t show up.
You only need to do the edit now within the menus themselves, not at the root level (At least not Adv or Chipset), since the AMITSE edit unlocked them. Sorry, I didn’t include this BIOS too, but you probably just needed to do the AMIBCP edit to the m1-touch.bin too, after the setup edit I described above.
I didn’t think it would be needed, but I should have included as secondary test anyway 
I set a few things to user at root of SerialIo Configuration and within Serial IO I2C1 Settings (you can see it all in AMIBCP now, anything missing in there you can adjust similarly now with AMIBCP)
http://s000.tinyupload.com/index.php?fil…495674540341959
A few settings for that is also in >> Serial IO I2C1 Settings & Finger print sensor is in Serial IO SPI1 Settings (If you needed that one too)
this one works, Touch Panel setting is visible, turns out it does nothing, also didn’t try the Finger print Sensor settings you mentioned (doesn’t apply to my machine as my laptop doesn’t have a Finger Print Reader)
Thank you very much for your help.
What was the touch panel? I assumed not same as touchpad, maybe something onscreen and you need to install the software once you enable it? But, then you’d also need a touchscreen too if that’s what it is.
You’re welcome! Hope you find some other goodies in the unlocked BIOS
(i think) Tocuh Panel is type of Touchscreen (or touchscreen controller), by default its set to SPI, but in DSDT Table definition, it is I2C device connected to I2C2 bus (8086:9D62), working fine on windows and Linux but on macOS it doesn’t work. so i thought changing Touch Panel to I2C Touch might help. but it didn’t, same error on macOS as before. Touch Pad is standard PS2 Device.
also yesterday i tried to disable I2C0 (rotation sensor, buggy driver on Linux and don’t really use it on windows) but disabling it also disabled I2C1/I2C2 (grayed out). nothing connected to I2C1 bus, but I2C2 bus have Touch Screen connected.
I didn’t know it was working on one system, just not another. Sounds like something I think they’d maybe be able to solve that with the MAC pro’s on those MAC/OSX Specific forums, have you asked there for some modified files or methods to resolve the issue
Yes, i am working on it. developer of VoodooI2C Kernel Extension, is busy now a day. he might be able to help when he gets some time.
i tried the methods documented at https://voodooi2c.github.io ; but that doesn’t help.
Sorry I can’t help with that, I only know the few BIOS mods required for MAC/OSX to work on a basic level (MSR 0x2E/CFG lock mod, and maybe another basic one I forget right now)
Hopefully they can help you with this touchpanel thing, I assume it’s a driver issue or maybe some ACPI edit is needed, or the kexts stuff I always see you guys editing pre-install? 
?
Touchscreen is working now. driver/kext was fine, just required a little ACPI edit. injected required/missing methods with SSDT. also i’m not sure what ‘MSR 0x2E/CFG lock’ does. only issue now is the Embedded Controller (or its firmware, not sure. but its buggy and not working properly). ACPI edits might fix it too, but not sure what is wrong.
@chilledHamza - cool you got it working now! ‘MSR 0x2E aka CFG lock’ is the standard mod everyone does to BIOS to allow MAC/OSX to run on mainstream desktop boards, it’s the powermanagement mod.
You probably did this edit first, or some standard batch/process you followed covered this early on in the setup process.
Sorry, I can’t really help on the EC FW 
Hopefully you can get it sorted out