Jump to content
arsradu

[HOW TO] Fix second stage boot logo and loading bar for some dedicated desktop video cards

389 posts in this topic

Recommended Posts

Advertisement

In my experience, you don't need a custom one. Clover does a good job at injecting the correct EDID for you monitor.

 

But on some monitors, especially on higher resolution ones (over 1080p) some people were saying that they don't have the Apple logo for the second stage boot.

 

Try to set Clover resolution to 1080p and also OS X resolution to 1080p. Just for testing purposes. See if it makes any difference.

 

Also, if your motherboard supports this feature and if you don't have any MBR-booted drives (legacy drives), you can try to turn OFF CSM in your UEFI Bios. See if that works for you.

 

Exactly, have a little bit other configuration,

2560x1440 on 13inch screen...

 

What i can say, if i set clover to 1280x720 and OS X to 1280x720 = perfect logo + perfect loading bar

if i use default 2560x1440 both, i get with "second boot fix" perfect logo + loading bar little bit distored...

without the bin patch it is completely distored on 2560x1440...

 

so I'm using hidpi mode, 1600x900 = 3200x1800, but i can't set that resolution to clover because clover can't patch integrated graphics vbios as far i know, since this vbios is inside laptops bios in core_dxe... 

edid patching won't help here, since a new modeline makes a distored screen on first draw... if you changing resolution and change back, its working... but you won't do that every time after system start :-)

 

So what i can say, use a 16:10 screen for OS X or 16:9 but anything greater 2800+ (2880xxx, 3200xxx...)

there is a hole in OS X for 16.9 resolutions from 1920xxxx till 2800xxxx...

what i mean with the hole is, distorted boot or not working hiDPI modes on 16:9 screens...

 

Dunno why, but i tested some other systems, everything else is fine :-)

 

Cheers :-)

Share this post


Link to post
Share on other sites

Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! :D

Share this post


Link to post
Share on other sites

Just did this with my 970 on a 1440p DVI-DL screen (along with setting 1440p within Clover) and it works perfectly. The second stage isn't glitched at all - the loading bar is centered and looks perfectly and the Apple logo looks great! :D

 

Thank you very much for your feedback! And glad to hear that this works for you too.

 

What about the resolution in OS X? Is it set to 1440p, as well?

Share this post


Link to post
Share on other sites

Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest.

 

Really, all I had to do was adding this entry:

"@2,AAPL,boot-display", 
Buffer (One)
{
    0x00
}, 

to my GPU Device in my SSDT.

 

The whole entry currently looks like this: (I have a NVIDIA card)

Device (_SB.PCI0.NPE3.PXS1)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            If (LEqual (Arg2, Zero))
            {
                Return (Buffer (One)
                {
                    0x03
                })
            }

            Return (Package (0x12)
            {
                "AAPL,slot-name", 
                Buffer (0x0B)
                {
                    "PCI Slot 1"
                }, 

                "@0,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@1,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,AAPL,boot-display", 
                Buffer (One)
                {
                    0x00
                }, 

                "@3,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@4,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@5,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "hda-gfx", 
                Buffer (0x0A)
                {
                    "onboard-1"
                }
            })
        }
    }   

Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System.

 

Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that.

Edit: if you do that, you will have multiple loading bars. So it should be only one entry that matches the connected main display. Just FYI

Share this post


Link to post
Share on other sites

Dunno if that was mentioned before, but at least for me, the solution was way simpler as described in this guide, so it might be of interest.

 

Really, all I had to do was adding this entry:

"@2,AAPL,boot-display", 
Buffer (One)
{
    0x00
}, 

to my GPU Device in my SSDT.

 

The whole entry currently looks like this: (I have a NVIDIA card)

Device (_SB.PCI0.NPE3.PXS1)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            If (LEqual (Arg2, Zero))
            {
                Return (Buffer (One)
                {
                    0x03
                })
            }

            Return (Package (0x12)
            {
                "AAPL,slot-name", 
                Buffer (0x0B)
                {
                    "PCI Slot 1"
                }, 

                "@0,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@1,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@2,AAPL,boot-display", 
                Buffer (One)
                {
                    0x00
                }, 

                "@3,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@4,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "@5,connector-type", 
                Buffer (0x04)
                {
                    0x00, 0x08, 0x00, 0x00
                }, 

                "hda-gfx", 
                Buffer (0x0A)
                {
                    "onboard-1"
                }
            })
        }
    }   

Note that I did not have to add "Load VBIOS" in Clover, and also not "Inject EDID". Actually I was surprised that the solution was so minimalistic. Works in both 10.10 and 10.11. Of course you might need to change the connector from "@2" to something that corresponds on your System. Maybe it even works if you add this entry to all availbale connectors in the SSDT, but I have not tried that.

 

I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. :))

 

Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post :P). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it.

 

Thanks for sharing! And also, glad it works for you! :D

Share this post


Link to post
Share on other sites

I did mention in the initial post (pretty long one, I know, but this is somewhere on the top) that this can also be achieved by using DSDT editing. Actually a few of my friends got it fixed this way. However I do not know how to do it right now (I'm still very much a noob in DSDT editing), so I can't teach others ether. :))

 

Also, you don't have to Inject EDID and Patch VBIOS if you're using an UEFI GOP Vbios (this is also mentioned on the first post :P). And even if you're not using a UEFI VBIOS, apparently not all the people need that. I needed it, so I mentioned it for other people to know about it.

 

Thanks for sharing! And also, glad it works for you! :D

 

Yeah, sorry if I may have overlooked something ;)

 

And I am absolutely no expert in DSDT editing, so if I can do it, everyone can ;)

 

So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course.

Share this post


Link to post
Share on other sites

Yeah, sorry if I may have overlooked something ;)

 

And I am absolutely no expert in DSDT editing, so if I can do it, everyone can ;)

 

So you also have some type of SSDT patch for your GPU, right? So apparently, the only thing needed is to add this entry in the _DSM method, using the correct connector adress of course.

 

I'm not using any kind of patched SSDT/DSDT files. Only Clover patching. :D

 

I'll try to learn a bit more about it and, maybe I'll add that part as well. I think it would be a nice addition.

Share this post


Link to post
Share on other sites

Ah, understand. Even if I am not an expert I still try to avoid Clover patches when possible. And there is always something new to learn ;)

Share this post


Link to post
Share on other sites

If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method,

                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x12)
                        {
                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@0,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@1,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@1,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@2,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@2,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@3,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@3,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }
                        })

Share this post


Link to post
Share on other sites

 

If you would like to avoid having to patch your DSDT ever time your change your monitor setup or default you can use this DSM method,

                Device (GFX0)
                {
                    Name (_ADR, Zero)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x12)
                        {
                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@0,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@1,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@1,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@2,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@2,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "@3,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "@3,connector-type", 
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            }, 

                            "hda-gfx", 
                            Buffer (0x0A)
                            {
                                "onboard-2"
                            }
                        })

 

So..basically setting the same boot-display property for all ports? Did I get that part right?

Share this post


Link to post
Share on other sites

So..basically setting the same boot-display property for all ports? Did I get that part right?

 

@asradu

 

This above seems for me like boot display for every frame buffer... dunno if this is useless or not...

 

But, there must be some registers, which changes, based where your display is connected,

just need to read in the Nvidia/Amd Specification sheet...

 

Like Rehab found the BAR1 register in the Intel Graphics specification sheet... (different thing, because BAR1 is for brightness)

 

But theoretically i think its possible...

 

If we find the register it should be very easy to make an ACPI Method for this...

 

 

PS: i don't have here Nvidia/Amd Graphics, since i have on my laptop only Iris5100...

So i can't test... Im Sry...

 

Cheers :-)

Share this post


Link to post
Share on other sites

This above seems for me like boot display for every frame buffer... dunno if this is useless or not...

 

Imho, it is. When I do this, I get the Apple Logo, but also a second loading bar bottom-left, just like without the patch.

Share this post


Link to post
Share on other sites

I followed the guide and got my 2nd stage boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes?

 

Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner.

 

I'm guessing this is an EDID issue with my monitor?

Share this post


Link to post
Share on other sites

I followed the guide and got my 2nd boot screen 95% working but for some reason my monitor still blinks blank before the logo/loading screen finishes?

 

Before it did the same but I didn't have the logo/loading screen properly centred as it just showed the bar on the bottom left hand corner.

Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong.

 

So far, that's the best we can have. When there will be a solution for that as well, I'll post it.

Share this post


Link to post
Share on other sites

Yeah, that's a glitch that most of us have (especially desktop users). Interestingly, even some real iMacs have it too. And no, I'm not sure it has anything to do with the EDID. But I might be wrong.

 

Ah OK. I thought I was alone. Seems like a weird glitch -- it would be nice to have a fix for it sometime but it's already much better than before. Thanks for the guide!

Share this post


Link to post
Share on other sites

So..basically setting the same boot-display property for all ports? Did I get that part right?

 

Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port...

 

I guess OS X thinks the displays are mirrored for the boot process maybe?

Share this post


Link to post
Share on other sites

Yes that's all I did... Makes not difference on my end with multi-monitors or single monitor switched to a different port...

 

I guess OS X thinks the displays are mirrored for the boot process maybe?

 

That is really interesting. :D I wonder if it works with the device-properties method. Should work..I guess. I just can't test this. :))

Share this post


Link to post
Share on other sites

Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas?

I'm using the VGA port BTW.

Please have a look at the file (attached) I edited using @1 as the default.

device-properties.xml

Share this post


Link to post
Share on other sites

Hi I've followed steps 1-4 but the only thing I got from step 5 is the loading bar at the center with no logo. Patch Vbios and Inject EDID made the first stage logo bigger with the loading bar at the center with no logo on the second stage. I've tried with/without CsmVideoDrv.efi but to no avail. My bios, tho UEFI, had no CSM option (it's an H61M). I'm booting in UEFI and I'm not using DSDT/SSDT coz Clover does the good job already. I'm using Manli GeForce 210 on this one. Any ideas?

I'm using the VGA port BTW.

Please have a look at the file (attached) I edited using @1 as the default.

 

1. What's your display resolution? What's the resolution set in Clover? What's the resolution set in OS X?

2. Did you set a specific display-cfg in Clover config or anywhere else? Does it work without it?

 

Also, something seems a bit off in your xml... Is this the one that you edited or the one generated after reboot, when extracting it again from the system?

 

Also, a screenshot of your IOreg might help in this case.

Share this post


Link to post
Share on other sites

My display resolution is set to 1600x900 in OS X and in Clover.

 

No I didn't set any display-cfg in Clover. 

 

The xml I sent was the edited xml already.

 

What seems to be off in the xml?

 

Here's my ioreg. Thanks

post-942609-0-96357200-1447537139_thumb.png

Share this post


Link to post
Share on other sites

My display resolution is set to 1600x900 in OS X and in Clover.

 

No I didn't set any display-cfg in Clover. 

 

The xml I sent was the edited xml already.

 

What seems to be off in the xml?

 

Here's my ioreg. Thanks

 

 

I'm pretty sure hda-gfx is not in the initial tutorial. I'm not sure it's the cause of the issue. Probably not. But let's just do it exactly like it is on the first page for once.

 

So, could you please, try the hex txt in the attachment? Please, make a copy of your current one, just to be safe. And let's see if that makes any difference. Also please, try with and without PatchVbios.

hex_txt.txt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.5_18F132
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.5.zip
       
       
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×