- Joined
- Apr 16, 2017
- Messages
- 418
- Motherboard
- Gigabyte X299 WU-8
- CPU
- i9-7980XE
- Graphics
- RX 580
- Mobile Phone
I think the GUID on that Skylake SP is the same as X299 ( 299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9 ) - Extracted from Bios -#Silnit. I don't think I have the time nor the expertise to parse that extra line in to the end of patches.txt. P??????It looks like only values in static XCPM arrays need to be patched. They should not change often. Coderush showed the code for 0xE2 lock on a Gigabyte board here, https://pikeralpha.wordpress.com/2015/10/20/new-gigabyte-motherboard-are-msr0x2e-locked/ . Good luck GUID hunting.
This is where Dominus extreme BIOS 0601 locks 0xE2
seg000:0000000001AF3D5B xor edi, edi
seg000:0000000001AF3D5D mov [rsp+24h+var_14], edi
seg000:0000000001AF3D61 test byte ptr [rsi], 1
seg000:0000000001AF3D64 mov [rsp+24h+var_10], edi
seg000:0000000001AF3D68 jz short loc_1AF3DC9
seg000:0000000001AF3D6A mov ecx, 0E2h
seg000:0000000001AF3D6F rdmsr
seg000:0000000001AF3D71 mov ecx, eax
seg000:0000000001AF3D73 mov ebx, 8000h
seg000:0000000001AF3D78 and ecx, ebx
seg000:0000000001AF3D7A or ecx, edi
seg000:0000000001AF3D7C jnz short loc_1AF3D97
seg000:0000000001AF3D7E or eax, ebx
seg000:0000000001AF3D80 mov [rsp+24h+var_10], edx
seg000:0000000001AF3D84 mov [rsp+24h+var_14], eax
seg000:0000000001AF3D88 mov edx, [rsp+24h+var_10]
seg000:0000000001AF3D8C mov eax, [rsp+24h+var_14]
seg000:0000000001AF3D90 mov ecx, 0E2h
seg000:0000000001AF3D95 wrmsr
After patching it this is the message I get:
#
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseVolume: unknown file system 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
parseFile: non-empty pad-file contents will be destroyed after volume modifications
No patches can be applied to input file
#
Still trying though..Coderush & Pike obviously retired ( for different reasons ) . Can you do it? I'm sure the community will be more than grateful to you.
Last edited: