antipop2323

if you open plist in plist editor, then you should get your MAC address (6 bytes) inside < and >. Your example above looks ok, except it has letter 'g' which is not possible - not a hex digit.

But again, from the current user experience, ROM value must be present but it's not required to be MAC address to sign in to iMessage. For now.

Just a note: ROM is suppose to contain MAC address of your primary network card. Although, it seems it's not important at all for now.

But, if you still want to set ROM to your MAC address, then do it like this: if MAC address is f1:2a:14:52:9a:60 (note: it's 6 bytes) then do
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%f1%2a%14%52%9a%60

It may be somewhere here

for (Link = gMemoryMap.ForwardLink; Link != &gMemoryMap; Link = Link->ForwardLink) {
	 Entry = CR(Link, MEMORY_MAP, Link, MEMORY_MAP_SIGNATURE);
	 if ((Entry->Attribute & EFI_MEMORY_RUNTIME) != 0) {
	 if (Entry->Type == EfiACPIReclaimMemory || Entry->Type == EfiACPIMemoryNVS) {
		 DEBUG((DEBUG_ERROR | DEBUG_PAGE, "ExitBootServices: ACPI memory entry has RUNTIME attribute set.\n"));
		 Status = EFI_INVALID_PARAMETER;
		 goto Done;
	 }
	 if ((Entry->Start & (EFI_ACPI_RUNTIME_PAGE_ALLOCATION_ALIGNMENT - 1)) != 0) {
		 DEBUG((DEBUG_ERROR | DEBUG_PAGE, "ExitBootServices: A RUNTIME memory entry is not on a proper alignment.\n"));
		 Status = EFI_INVALID_PARAMETER;
		 goto Done;
	 }
	 if (((Entry->End + 1) & (EFI_ACPI_RUNTIME_PAGE_ALLOCATION_ALIGNMENT - 1)) != 0) {
		 DEBUG((DEBUG_ERROR | DEBUG_PAGE, "ExitBootServices: A RUNTIME memory entry is not on a proper alignment.\n"));
		 Status = EFI_INVALID_PARAMETER;
		 goto Done;
	 }
	 }
}

We can't debug at this place because these codes from UEFI ROM.

So,
1. if you stop Clover from injecting USB device values with USBInjection=No, then you are missing some USB device values that would allow you to wake with USB mouse/keyboard
2. but if you let Clover to inject USB device values, then Clover injects values which are not good for your system

This sounds like you need to inject USB stuff, but a bit different then Clover is doing by default. You can check what Clover is injecting by using DarwinDumper to dump "Device Properties". And you can inject your own values to USB devices in DSDT.


Yes, mouse does not work in UEFI boot here also. It's not related to AptioFix. It's just that mouse driver built inside our UEFI does not behave as it should (as specified by UEFI spec), and Clover does not get proper movement values from it.