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

Sorry for my english :D

With CSM enable: clover GUI fallback to 800x600, also for stage 1. 

With CSM disable: clover GUI has max resolution: 3840x2160

 

I have try with Inject EDID, patch VBIOS, also without or only patch VBIOS/ inject EDID. None on them give me apple logo at stage 2. When inject EDID and Patch VBios at sametime, It's completed lost stage 1 and clover GUI.

 

Display in OSX: (2160x1440)

 

f46D39b.png

config.plist.zip

iMac.zip

device-properties.xml.zip

Share this post


Link to post
Share on other sites
Advertisement

Are you guys using video card with GOP?

Yes, but apparently disabling CSM in Bios doesn't really help for this case. It works fine for me with disabled CSM....but not for him. I don't use it this way cause I still need my Bios to let me choose the other drive, which is using MBR. Otherwise, I would have switched off CSM a long time ago.

Sorry for my english :D

With CSM enable: clover GUI fallback to 800x600, also for stage 1. 

With CSM disable: clover GUI has max resolution: 3840x2160

 

I have try with Inject EDID, patch VBIOS, also without or only patch VBIOS/ inject EDID. None on them give me apple logo at stage 2. When inject EDID and Patch VBios at sametime, It's completed lost stage 1 and clover GUI.

 

Display in OSX: (2160x1440)

 

If you've got a 4K monitor, why do you keep your OS at lower resolution...? OS X doesn't know 4K? Or you just don't like it? By the way, I would love to have that monitor! You're so lucky. :P

 

Anyway, I had a look at your config and device-properites. Looks ok... But in config.plist I couldn't find any reference to any Custom Logo... Did you set any? Not sure that's gonna make any difference (most likely not) but I'm trying to minimize the number of variables here.

 

Also, if you're on El Capitan and not dual-booting Yosemite/El Capitan, kext-dev-mode=1 is not necessary anymore. Just so you know. :)

 

So with CSM enabled + Patch VBios + Inject EDID, you get 800x600 in Clover GUI and also no first-stage boot logo?

 

Also, could you please, upload your images as "attachment" and not "image" since that will embed them into the post and make it huge? :D

Share this post


Link to post
Share on other sites

OSX does know 4k, but the text too small, default it set scale to 1080p, but I change it to 1440p for more space.

I do not have any custom logo, thought that will load default apple logo.

With CSM enabled + Patch VBios + Inject EDID: I get 800x600 in Clover GUI, but still got first stage boot logo (in 800x600 too)

 

 

 

Also, could you please, upload your images as "attachment" and not "image" since that will embed them into the post and make it huge?  :D

 

I will, sorry :D

Share this post


Link to post
Share on other sites

OSX does know 4k, but the text too small, default it set scale to 1080p, but I change it to 1440p for more space.

I do not have any custom logo, thought that will load default apple logo.

With CSM enabled + Patch VBios + Inject EDID: I get 800x600 in Clover GUI, but still got first stage boot logo (in 800x600 too)

 

 

I will, sorry :D

 

This is really weird... Do you have CSMVideoDrv installed? Maybe try with or without it? I don't need it. But...maybe you do.

 

So, to sum up:

 

1. With or without CSM disabled in Bios, you still don't have second stage boot logo.

 

2. If you enable CSM in Bios, PatchVBios + Inject EDID in Clover, you lose the first stage boot completely.

 

3. If you enable CSM in Bios but use only one of the two (Patch Vbios or Inject EDID), you have the entire UI scaled to 800x600, first stage boot logo, but still no second stage boot logo.

 

What if you try to disable CSM in Bios, disable Patch VBios + Inject EDID, and set the OS and also Clover resolution to native one? Just for testing.

 

We're half way there. :) The loading bar is back centered. So it's not all for nothing. Now we just need to bring that logo back somehow.

 

By the way, that Apple logo looks like a cherry on that huge resolution. :))

Share this post


Link to post
Share on other sites

With CSMVideoDrv installed, I get max resolution at 1600x1200 and another lower resolution, but all scale is 4:3.

I have try set OS and Clover GUI resolution back to 4k (3480x2160). Seem like stage 2 is lost or it doesn't load anymore. It's usually take around 2 - 3 second at stage 2, now it just flash and load login screen

 

I have take a capture about it: https://www.youtube.com/watch?v=BrDUhj-7UyI

Share this post


Link to post
Share on other sites

With CSMVideoDrv installed, I get max resolution at 1600x1200 and another lower resolution, but all scale is 4:3.

I have try set OS and Clover GUI resolution back to 4k (3480x2160). Seem like stage 2 is lost or it doesn't load anymore. It's usually take around 2 - 3 second at stage 2, now it just flash and load login screen

 

I have take a capture about it:

So this is with CSM disabled, max resolution in Clover UI and OS X, and you have no second stage at all.

 

What if you temporarily remove the injected properties (the hex code you initially injected in Clover config.plist) and let it load, in full resolution, with CSM disabled, just like before? Will the second stage appear but loading bar will drop back to the bottom left corner?

 

In theory, and in my tests so far (though I'm on a 19" 1440x900 monitor, so you can understand why I'm drooling for that 4K of yours :)) ), you should not need anything if you disable CSM in Bios. At least I don't...

As I said, I keep it enabled just for my other drive. Still, you've got so many issues with pretty high end hardware.

 

By the way, are you using SSD? Cause that boot is just too freaking fast!!

Share this post


Link to post
Share on other sites

So this is with CSM disabled, max resolution in Clover UI and OS X, and you have no second stage at all.

 

What if you temporarily remove the injected properties (the hex code you initially injected in Clover config.plist) and let it load, in full resolution, with CSM disabled, just like before? Will the second stage appear but loading bar will drop back to the bottom left corner?

 

In theory, and in my tests so far (though I'm on a 19" 1440x900 monitor, so you can understand why I'm drooling for that 4K of yours :)) ), you should not need anything if you disable CSM in Bios. At least I don't...

As I said, I keep it enabled just for my other drive. Still, you've got so many issues with pretty high end hardware.

 

By the way, are you using SSD? Cause that boot is just too freaking fast!!

 

 

Yea, I'm using 2x Samsum 850 for windows and osx.

If I removed injected properties, the bar will drop back to the bottom left corner, with any resolution on osx or clover and the second stage still load (without logo). I will try with custom logo from clover efi :D

Share this post


Link to post
Share on other sites

I uncheck Inject EDID and Patch VBios. From GUI, set resolution to 4k, and checked use custom logo.

Here are result by changing resolution in osx:

- Default scale (1080p): It's show correct like real mac, I got apple logo and loading bar at center  (stage 1 and 2 )

- 1440p, 2160p (4k): It just flash like video above and enter direct to login screen (No stage 2).

 

I do not have any 5k IMac to test how it appear when scale to 1440p or 4k resolution :D, so I just think that apple do not have stage 2 config for 1440p or above, hope someone who has 5K imac can confirm it for me :D

 

p/s: Your patch are work for me, with default setting. Thank you a lot for helping me and post a nice tutorial :)

 

Attached my current clover config, It may help someone else.

config.plist.zip

Share this post


Link to post
Share on other sites

I uncheck Inject EDID and Patch VBios. From GUI, set resolution to 4k, and checked use custom logo.

Here are result by changing resolution in osx:

- Default scale (1080p): It's show correct like real mac, I got apple logo and loading bar at center  (stage 1 and 2 )

- 1440p, 2160p (4k): It just flash like video above and enter direct to login screen (No stage 2).

 

I do not have any 5k IMac to test how it appear when scale to 1440p or 4k resolution :D, so I just think that apple do not have stage 2 config for 1440p or above, hope someone who has 5K imac can confirm it for me :D

 

p/s: Your patch are work for me, with default setting. Thank you a lot for helping me and post a nice tutorial :)

 

Attached my current clover config, It may help someone else.

I'm just curious. Does it work in 1080p, with no Custom Logo in config?

 

Also, does it still work with enabled CSM + PatchVbios, at 1080p?

 

What I wanna know is: was it just a matter of resolution? Was the CSM enabled/disabled relevant for this to work? 

I mean, for centering the logo, CSM disabled/enabled doesn't make any difference. It works either way. But what about the logo?

 

Also, is your VRAM correctly recognized?

 

 

And yeah, 5k iMac would be awesome... I can't even afford a 1k iMac. :))

 

By the way, thank you very much for testing. Not many people are willing to try all these different scenarios. So thank you!

 

And if you find a way to have that logo in 4K, please, do let me know. 

 

I don't even know how to consider this. OK? Not ok? Not...quite ok? :)) I mean, I want to add your card to the first post. But we still don't know how to make it work in native resolution. It works in 1080p, which is good. But it doesn't quite work in 1440p or 4K. Until further research is confirmed on this setup, I'll consider this as "partially supported" or something like that. And maybe link to your post, if you don't mind.

Share this post


Link to post
Share on other sites

It's still work on 1080p without CustomLogo, so I guess custom logo doesn't effect to apple logo at stage 2.

Somehow it cache my login screen resolution. All video above show that I got 1440p or 2160p login screen, but when I changed osx resolution to 1080p (default for display in Settings), then change it back to 1440p or 2160p, it still show me 1080p login screen, after login it scale to large display, which are in osx display setting (1440p or 2160p). This thing didn't happened before.

 

It doesn't work with CSM enabled and PatchVBios at all resolution, the bar fail back to bottom left corner

 

I just realize that my VRAM is 0MB, something happen here, I was get 4GB VRAM before I inject the hex. Problem must come from my injected hex, maybe the value 0x100000000 is incorrect?

 

I will let you know when I make it work native resolution :D

Share this post


Link to post
Share on other sites

It's still work on 1080p without CustomLogo, so I guess custom logo doesn't effect to apple logo at stage 2.

Somehow it cache my login screen resolution. All video above show that I got 1440p or 2160p login screen, but when I changed osx resolution to 1080p (default for display in Settings), then change it back to 1440p or 2160p, it still show me 1080p login screen, after login it scale to large display, which are in osx display setting (1440p or 2160p). This thing didn't happened before.

 

It doesn't work with CSM enabled and PatchVBios at all resolution, the bar fail back to bottom left corner

 

I just realize that my VRAM is 0MB, something happen here, I was get 4GB VRAM before I inject the hex. Problem must come from my injected hex, maybe the value 0x100000000 is incorrect?

 

I will let you know when I make it work native resolution :D

I guess you need to restart your computer after each change in OS X display resolution for the changes to take effect? Weird...

 

About the VRAM, I'll double check that value. It might be wrong indeed.

 

Thank you! :)

 

Update: yep, I'm pretty sure values past 4GB are wrong. So I removed them. I'm working on getting the correct ones up, as soon as I get them.

 

In the meantime, what if you remove the VRAM section of the xml and convert to hex?

 

Meaning remove this:

<key>VRAM,totalsize</key>
<string>0x80000000</string>

Do you get the right value? 

Share this post


Link to post
Share on other sites

After remove VRAM from xml, i got 256MB ram on my 970  :angel_not:

Got following size with some tries:

 

2560MB with 0xA0000000

3584MB with 0xE0000000

 

1st number give us 256MB, so max memory we can get: 256x15 (F) = 3840MB

2nd number give us 16MB, so max memory we can get: 16x15 = 240MB

3rd number give us 1MB: so max memory we can get: 1x15 = 15MB 

 

With 0xFFF0000 I get 4095MB vram, as it detected by default (without inject the hex to fix loading bar)

 

So if we devide 1MB = 1024KB to 16, we will get 4th number value is 64KB, max we can get is 64 x 15 = 960kb

So on, 5th is 4KB each, max we can get is 4x15 = 60kb

6th is 4x1024 = 4096bytes, devide to 16 we have 256 bytes each 6th, max we can get is 256 x 15 = 3840 bytes ~ 4KB.

same for 7th and 8th

Sum the total from 1 -> 8, i still got 4095MB at 0xFFFFFFFF . Some how the value from 4th are not calculate to total of VRAM, if it does, I should get 4096MB VRAM  :D

 

P/S: I always get lower value than real value from bios/windows on osx, at yosemite, my processor show 3.99ghz only, ram at 2285MHZ, GTX 970 at 4095 VRAM. After upgrade to el capitan, my processor goes back to 4GHZ, other value still same as before. On windows and bios, my Ram running at 2400MHZ, not a big problem because my ram also has xmp profile for 2285MHZ too.

Share this post


Link to post
Share on other sites

Hello everyone,

 

I just wanted to chime in on the subject with a very similar situation to wrk73 when booting my single 4K monitor and my EVGA 670 4GB over DP (UEFI GOP) with El Capitan.

 

I have both the first and second stage working by adding @3,AAPL,boot-display to my DSDT, but the second stage (with centered Apple logo and progress bar) only displays properly when my Display is set to the default resolution in system preferences. Other scaled resolutions higher then 1920x1080 will interfere with the second stage and transition to desktop/login screen.

 

I've also noted that the first stage and second stage display at different resolutions. First stage displays at monitor defaults. The second stage displays at system preference defaults (1920x1080), its also larger in appearance then first. I'm thinking this might be the reason for the 1second blackout between the two stages at least in my case.

 

For the second stage not displaying properly at res other then 1080, more investigation is required. A retina iMac and real MacPro6,1 with 4/5K display would be very helpful with this investigation.

 

Hope this information helps someone else.

 

I'll post back again If I find more details or a solution to my OCD.  :)

 

Gratitude,

 

Robert aka Mrengles

Share this post


Link to post
Share on other sites

For the second stage not displaying properly at res other then 1080, more investigation is required. A retina iMac and real MacPro6,1 with 4/5K display would be very helpful with this investigation.

 

Well, no magic here, this depend by your bootloader if pass/set the right argument to the kernel....if not report a bug to the devs of your bootloader and ask if that is implemented:

 

#define kBootArgsFlagHiDPI        (1 << 1)

 

https://opensource.apple.com/source/xnu/xnu-2782.1.97/pexpert/pexpert/i386/boot.h

 

But probably depend also from the Vesa res detected (not always is acquired correctly)

 

EDIT

check for the right BooterConfig if you are using Clover..

Edited by Micky1979

Share this post


Link to post
Share on other sites
I've also noted that the first stage and second stage display at different resolutions. First stage displays at monitor defaults. The second stage displays at system preference defaults (1920x1080), its also larger in appearance then first. I'm thinking this might be the reason for the 1second blackout between the two stages at least in my case.

 

Hope this information helps someone else.

 

Gratitude,

 

Robert aka Mrengles

 

Hi, Robert

 

Well, the first stage boot is displayed by the bootloader (Clover, I assume), so resolution should probably be tweaked from there.

The second stage is displayed by the kernel, so system settings kick in here.

 

The gap between the two is most likely not due to the difference in resolution. I've got the same resolution throughout the entire boot (both stages) and still have that small gap. Nothing to be concerned about. But not yet perfect either. Although, as I said, some older iMacs have it too. So..yeah. :)

Share this post


Link to post
Share on other sites

Well, no magic here

 

Is both apply to igpu & discrete Micky1979?

 

According to Pike, need to have "IOFBNeedsRefresh" with "false" value, have you check it Mrengles?

 

IvpJHX5.png

Share this post


Link to post
Share on other sites

Is both apply to igpu & discrete Micky1979?

 

Sure, but this has only to do with apple logo and progress bar sizing (if the bit is set on a low screen res it should work anyway.. only a big logo/progress bar..or viceversa)

Share this post


Link to post
Share on other sites

Hey Guys

 

I'm actually using Ozmosis r1479 on this setup at the moment, but checking with clover is no problem. It will just have to wait until after I get home from work.

 

Yes IOFBNeedsRefresh=false when checking ioreg. This wasn't the case until I edited my DSDT and added @3,AAPL,boot-display to my GFX0 device injections.

 

I do have the iGPU enabled for AirPlay video support, but using an Ivy bridge frame buffer with no physical ports (just like the iMac13,2) so that I can boot with my discrete graphics set as default in my AsRock UEFI/Bios.

 

If anyone would like me to post IOReg, DSDT or anything else just let me know.

Share this post


Link to post
Share on other sites

Hey Guys

 

I'm actually using Ozmosis r1479 on this setup at the moment, but checking with clover is no problem. It will just have to wait until after I get home from work.

 

Yes IOFBNeedsRefresh=false when checking ioreg. This wasn't the case until I edited my DSDT and added @3,AAPL,boot-display to my GFX0 device injections.

 

I do have the iGPU enabled for AirPlay video support, but using an Ivy bridge frame buffer with no physical ports (just like the iMac13,2) so that I can boot with my discrete graphics set as default in my AsRock UEFI/Bios.

 

If anyone would like me to post IOReg, DSDT or anything else just let me know.

 

I'm also curious if this works for you with Clover and injecting the device properties hex. :D I would love to add your GTX 670 to the list of successfully tested video cards (even if it's with limited support, for now), just like it was for wrk73. I don't see why it wouldn't work with that method. So far, people who tried them both said that it works with either one of them.

 

Also, for as far as I can see, you also have a video card with 4 GB of RAM. Do you also see 4095 MB in About This Mac, without "forcing it" to display a specific value? Cause I don't see 2047 on mine. :)) I've got 2048 MB, as I think is intended. So not sure why would you have 1MB less in your case. But I'm just asking.

 

Also, if you could share your opinion on the hex value we might need to use for 4096 MB of VRAM, that would be really nice. Apparently 0x100000000 is not ok, for some reason. So I'm trying to fix this, as well (even if it's just a cosmetic issue). So feedback is really appreciated.

Share this post


Link to post
Share on other sites

I just realize that my VRAM is 0MB, something happen here, I was get 4GB VRAM before I inject the hex. Problem must come from my injected hex, maybe the value 0x100000000 is incorrect?

 

I'm been monkeying around with my 670 here. The correct value for 4GB is 0xfff00000.

 

Not much in the way of success though. The screen still goes out for the second stage. But when the desktop comes up the Apple logo and progress bar are there fading out. I didn't get that before (it was just the progress bar).

 

Unfortunately injecting my gfx card properties seems to interfere with Clover's HDA injection. I get no pin config and the layout ID is set to 0. When I disable injecting the gfx card properties, it works again.

 

I've also been trying this stuff out with a HD5450 but without much success either. It behaves similarly to this 670: no second stage and logo and bar fading out when the desktop appears. However there's also a band of graphic corruption at the end of the first stage that wasn't there on Mavericks. I guess it's something similar to the second stage corruption that Intel gfx get. I had a quick look but couldn't find a IOGraphics patch for ATI (I tried the Intel one but it didn't fix it).

Share this post


Link to post
Share on other sites

Alternatively, you can inject your audio to device properties, or DSDT

<key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
<dict>
  <key>PinConfigurations</key>
  <data></data>
  <key>layout-id</key>
  <data></data>
</dict>

With your current method, i need to set FIXHDA=true in config to inject layout-id

Share this post


Link to post
Share on other sites

Sir, I translated this post and reposted it on a Chinese form, I would be very glad if you could approve of this.

link:http://bbs.pcbeta.com/viewthread-1648662-1-1.html

Hello

 

I approve.

 

However, you might want to add this part, between [ code ] tags, as well :) :

 

./gfxutil -i xml -o hex device-properties.xml device-properties.hex

Also, if you think screenshots might help, maybe add those as well.

I'm been monkeying around with my 670 here. The correct value for 4GB is 0xfff00000.

 

Not much in the way of success though. The screen still goes out for the second stage. But when the desktop comes up the Apple logo and progress bar are there fading out. I didn't get that before (it was just the progress bar).

 

Unfortunately injecting my gfx card properties seems to interfere with Clover's HDA injection. I get no pin config and the layout ID is set to 0. When I disable injecting the gfx card properties, it works again.

 

I've also been trying this stuff out with a HD5450 but without much success either. It behaves similarly to this 670: no second stage and logo and bar fading out when the desktop appears. However there's also a band of graphic corruption at the end of the first stage that wasn't there on Mavericks. I guess it's something similar to the second stage corruption that Intel gfx get. I had a quick look but couldn't find a IOGraphics patch for ATI (I tried the Intel one but it didn't fix it).

 

Thank you, Riley!

 

For your missing second stage boot, did you try changing the resolution to 1080p? Or is it 1080p already? You seem to be having the exact same issue as wrk73 mentioned above.

 

As for the VRAM, isn't 4 GB supposed to be 4096 MB? Is it supposed to be 4095 MB? Cause that's pretty much what that hex outputs. I don't have 2047 MB on my 2GB card. I have 2048 MB. Why would it be any different for 4GB? Also, I'm curious what it should be for 5GB and above, if 4095 MB is the correct value for 4GB instead of 4096 MB... I'm honestly confused. You can't write it as 0x100000000 cause you will reach (actually exceed) the max value for the 32bit integer. Then...how the hell do you do it? Switch to 64bit? :)) I mean, there are cards out there with 16GB of video memory! How do they do it?

 

0xfff00000 = 4293918720 (bytes) = 4095 (MB)

 

Right? If so, what am I missing here?

Share this post


Link to post
Share on other sites

Good point about the VRAM. With the nVidia web drivers it's always been reported as 4095MB. I'll change to the stock Apple ones and check again.

 

I'm running at 1080p here (and 1680x1050 on the X79 where I'm testing the HD5450).

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   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?

      How to make 10.13 installer for MBR (MBR-Automatic-Method)?
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, new for 10.13+.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       


       
    • By t0mmenhansen
      I havent used my hackintosh in a while. I wanted to boot to my mac drive. This error comes up when i try to boot. Ive tryed using explorer++ and update the lilu kext and whatevergreen kext, no luck yet. Any ideas?
       
      9700k
      16GB corsair
      1080 nvidia card
      z370-f mobo
      mac drive is an SSD from kingston
      Display port outpoot
       
×