Contribute
Register

<< Solved >> ROM and SMUUID info getting tossed out! NVRAM Values in clover not taking?

Status
Not open for further replies.
Joined
Nov 24, 2018
Messages
273
Motherboard
ASUS TUF Z390M-PRO GAMING (WI-FI)
CPU
i9-9900K
Graphics
Vega 64
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
I hope this is the right forum. I have a really crazy issue that is manifesting a ton of problems.

Ok so what is going on it that the SMUUID and MLB that I have in my config.plist file are getting tossed out by MacOS. This just started out of the blue about a week and a half ago out of the blue. it started on 10.14.3 but I updated to 10.14.4 and it has persisted. I have even gone as far as doing a fresh install of the 10.14.4 on a clean new ssd and got the same result.

is a Gigabyte Z390 M Gaming with i9-9900k


When I run iMessage Debug again I can see that neither the hardware UUID or the System-ID are the same as the SMUUID in clover.

I on ROM and Board Serial I get:

ROM: failed
BoardSerialNumber: failed


Does anyone know why this would start on this board all fo the sudden I didn't make any hardware changes.

Oh an in addition to iMessage and FaceTime not working. when I try to edit a post that I wrote on here it gives and Oops Error. Not sure if it is related but it started around the same time.
 
I hope this is the right forum. I have a really crazy issue that is manifesting a ton of problems.

Ok so what is going on it that the SMUUID and MLB that I have in my config.plist file are getting tossed out by MacOS. This just started out of the blue about a week and a half ago out of the blue. it started on 10.14.3 but I updated to 10.14.4 and it has persisted. I have even gone as far as doing a fresh install of the 10.14.4 on a clean new ssd and got the same result.

is a Gigabyte Z390 M Gaming with i9-9900k


When I run iMessage Debug again I can see that neither the hardware UUID or the System-ID are the same as the SMUUID in clover.

I on ROM and Board Serial I get:

ROM: failed
BoardSerialNumber: failed


Does anyone know why this would start on this board all fo the sudden I didn't make any hardware changes.

Oh an in addition to iMessage and FaceTime not working. when I try to edit a post that I wrote on here it gives and Oops Error. Not sure if it is related but it started around the same time.

Which Aptio fix are you using? Have you tried other Aptio fixes? I NVRAM working correctly or are you using emulated NVRAM?
 
Using Nvram on the Motherboard.

I'm using OsxAptioFix2Drv-free2000.efi
Screen Shot 2019-04-22 at 6.20.26 PM.png
 
Using Nvram on the Motherboard.

I'm using OsxAptioFix2Drv-free2000.efi

Are you sure that native NVRAM is working? All that I've read indicates that native NVRAM is broken on Z390...

Please try the NVRAM test:
 
hmm so it looks like it is broken
still why would it work fine then all of the sudden flake out. is weird
So what do I do? Do I just add the EmuVariableUefi-64?


UPDATE: That seems to have fixed it. But I'm totally wondering why it was working before?
 
Last edited:
hmm so it looks like it is broken
still why would it work fine then all of the sudden flake out. is weird
So what do I do? Do I just add the EmuVariableUefi-64?

If you don't have native NVRAM, you will have to use Emulated NVRAM. Install EmuVariablUefi-64.efi to /EFI/CLOVER/drivers64UEFI/.

I don't know why it was working and stopped... I have this motherboard and played around with it for a day and also experienced lots of strange behavior.
 
Status
Not open for further replies.
Back
Top