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

Hey guys,

This is a tutorial on how to fix (or at least try to fix) the second stage boot, when you're having these issues: missing logo and loading bar being displayed on the bottom left corner of the screen.

 

Might or might not work for other issues. So proceed with caution.

This is an issue that I experienced starting with early stages of development in Yosemite. Still continued in El Capitan. So this thread is primarily for these two versions of Mac OS X. Not sure it will work on earlier versions, cause I never tried it. So far it worked in Yosemite, El Capitan and Sierra.

Please, note that I did not test this on all video cards. So it might or might not work, depending on that. Don't take this as a final solution for everything. Also, I'm pretty sure this won't work with iGPUs. So I would strongly suggest to look around for solutions if that's your case.

This tutorial is not for multiple display setups! Please, don't use it for that! Especially not in iGPU + dedicated GPU combos.
 

Known issue: if you're using the auto-login feature, try to disable it and use the regular login screen. Otherwise you won't get the second stage boot (confirmed as fixed in Sierra).

 

This tutorial would have not been possible without the help and insight of:
Pike R. Alpha
cecekpawon
Mirone
Riley Freeman
 
So all the credit goes to them. I just put this together based on my successes and failures.

Succesfully tested with:
 
NVidia cards:

  • GeForce 210
  • GT 640
  • GTX 650
  • GTX 660
  • GTX 670 Superclocked+ 4GB - works partially (ok for 1080p, with CSM disabled, but no second stage in higher resolutions)
  • GTX 750 Ti - works partially (ok for 1080p, but no Apple logo for second stage in higher resolutions)
  • GTX 760
  • GTX 780
  • GTX 960
  • GTX 970 - works partially (ok for 1080p, and 1440p with CSM disabled, but no second stage in higher resolutions)

ATI cards:

Might work on other graphic cards, as well. But these are the ones that worked so far. Please, share if you got good results with another video card.

Also, the same thing can be achieved by modding your DSDT. Unfortunately this thread does not make the object of that method, nor am I able to help you with that, since I really have no idea how to mod a DSDT, so far. Also, to be honest, this method seems a bit easier.

Nonetheless, try this at your own risk! I'm not responsible for any damage that you might cause to your computer/components etc.
Also, please, note that this tutorial is not perfect. I'm doing my best to make it as easy to understand as possible. Also, I'm opened to suggestions and I'm doing my best to improve this in the future. Still, it's not perfect. So keep that in mind. Suggestions are appreciated though.

Please, note that, if you've got a video card with GOP UEFI Bios, you most likely don't need this tutorial in the first place. All you need is to disable CSM in BIOS (motherboard dependent). Note that, by doing this, only GPT drives will be loaded. So if you've got Windows installed on another drive, for example, you won't be able to select it anymore, if it's installed in "legacy" mode.


With that being said, let's get to work. :)

Prerequisites:

Mandatory:

  • a computer running Mac OS X Yosemite or newer
  • Clover bootloader (changes are gonna be saved to the config.plist file)
  • IORegistryExplorer v 2.1 (attached)
  • gfxutil (attached)
  • gfx_hex (attached) - script credit to cecekpawon

Optional:

  • Sublime Text Editor
  • Clover Configurator
  • a Windows PC for reading the graphic card's VBios version. So far, I couldn't find a way to do it from OS X. But if you know how to do it, please, share. I'll update this accordingly. An alternative (though not really the same thing) is this.
  • an USB installer might come in handy, so keep one close by.

Extra:

  • If you want to try the modded Bootx64.efi (rev 3279), thanks to cecekpawon, featuring an option to easily enable/disable string injection in Clover (in case you're stuck outside your OS, and don't have a USB drive or something else to boot from), click here to get it. Please, note that this revision might not work with newer versions of OS X/macOS.
    You will need to replace the one in your EFI/EFI/CLOVER folder. If you want to revert to the previous one, you can either reinstall Clover, or make a backup of your current one before replacing it.

I would recommend creating a single folder with all the necessary files and tools and putting it on your Desktop, just to have all the needed things in one place.

Note: If you use a custom SSDT/DSDT, I would try first without it, and using Clover's patches instead, so that you minimize the risk for failure due to custom DSDTs. I don't use a custom DSDT, didn't test in collaboration with a custom DSDT, so I don't know if it will work. If you wanna try it this way, I would love to know your results.

What to do:

Step 1 (establishing the port):

Open up your IOreg file (or just open IORegistryExplorer if you don't want to save it as a separate file), and search for "display".

You should see something like this:

post-1303722-0-18242900-1444055080_thumb.png

Now, depending on your card, you might have more or less ports. The important thing is to note the one that has the AppleDisplay attached to it. In this example, the second port (B@1) is the one in use. So that's the one we need to set as default. Please, note that they start at 0, so first port is A@0, the second one is B@1 and so on so forth.

Step 2 (extracting device-properties.hex):

Open up a terminal window, navigate to the desktop folder you're using, and do this (make sure gfxutil is present into that folder):

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml"

This will extract two new files into that folder: device-properties.hex and device-properties.xml

Step 3 (modding the device-properties.xml):

Open up the xml file using any text editor (I'm gonna use Sublime here) and ADD the number of ports you need for your card (the same number of ports, with the same name as in the IOreg) and the rest of the information, as described in the example below (use the attached xml as reference):

post-1303722-0-46844400-1445715282_thumb.png

Don't forget that the first port is port 0!

In this example, we're using an MSi GTX 650 OC with 2GB of RAM, which has 3 ports, and we want to set as default port #2 (B@1).
Attached you can find my device-properties.xml file, if you wanna use it as reference.

The first section will set port B@1 as default. Change this according to your case.

<!-- Primary display -->
<key>@1,AAPL,boot-display</key>
<string>0x00000001</string>

Whereas on the bottom you can see regular values. Here we can set the amount of VRAM, the name of the card and the VBios version.
 

<key>VRAM,totalMB</key>
<string>0x00000800</string> // for 2048 MB or 2 GB of RAM
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>MSi GeForce GTX 650</string> // Name of your card
<key>rom-revision</key>
<string>80.07.35.00.04</string> //VBIOS version

In my experience, these values are rather cosmetic than anything else. For an accurate version of your VBios, you can use either the Nvidia driver on Windows, or any hardware information software like GPU-Z, aida64 or nvflash.
 
Here's a little table with hex values for different amounts of RAM. If you need other values than the ones specified in this table, please, ask. Also, if you spot a mistake, let me know so I can correct it.
 
Amount of memory  Hex value
128 MB                      0x00000080
256 MB                      0x00000100
512 MB                      0x00000200
1024 MB (1 GB)        0x00000400
2048 MB (2 GB)        0x00000800
3072 MB (3 GB)        0x00000C00
4096 MB (4 GB)        0x00001000
5120 MB (5 GB)        0x00001400
6144 MB (6 GB)        0x00001800
7168 MB (7 GB)        0x00001C00
8192 MB (8 GB)        0x00002000
9216 MB (9 GB)        0x00002400
10240 MB (10 GB)    0x00002800
11264 MB (11 GB)    0x00002C00
12288 MB (12 GB)    0x00003000
13312 MB (13 GB)    0x00003400
14336 MB (14 GB)    0x00003800
15360 MB (15 GB)    0x00003C00
16384 MB (16 GB)    0x00004000
 
Once we're done modding, we're gonna save the changes and convert the xml file back into hex, using this command:

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

Step 4 (reading the modded hex):

Unpack gfx_hex (attached) file into your working directory and double click to run it.
 
It should output the content of your modded hex into a terminal window, and it should look something like this:
 
post-1303722-0-85170500-1444154243_thumb.png
 
Select and copy that code. After that, open up Clover Configurator and paste that hex code in Devices -> Properties section (see below) and check the box for Inject. You can also add this manually into the config.plist file, if that's more of your thing.

post-1303722-0-50532800-1444057472_thumb.png

Step 5 (setting up final arrangements):

We're almost done. But, if your experience is the same as mine, at this point you only got the loading bar back centered. Which, of course is a step forward. But we're not quite there yet.

So, to add the logo as well, we will check the boxes for Patch VBios and Inject EDID in Clover Configurator (Graphics section). You can inject your own EDID if you have one. Though, in my experience, Clover does a really good job in adding the correct one itself. So you don't really need to add a custom EDID. Just to use Clover's InjectEDID feature.

post-1303722-0-91610300-1444057617_thumb.png

Also, in my experience, you don't need CsmVideoDrv.efi for this to work. And I've got pretty similar results with and without it. So, if you have issues with it, you can try without it, and vice-versa.

When it's all done, save the changes to your config.

Now, I would highly recommend you to make a backup of your current config.plist from EFI/EFI/Clover/config.plist anywhere you want. You might need it later.

When that's done too, replace the config.plist in your Clover folder with the one you just modded, and restart.

Keep your fingers crossed (toes too). And hope for the best. If everything ok, you should have a pretty close to perfect second stage boot. If not, you might have nothing or an unbootable system.

To fix this, boot from your USB installer, or use boot flag nv_disable=1 (for Nvidia cards), upon booting, and revert the changes. Or, if you already know where is the problem, fix that and restart.

That's it.

Please, let me know if it worked for you.

gfx_hex.zip

IORegistryExplorer.app.zip

gfxutil.zip

device-properties.xml

Share this post


Link to post
Share on other sites
Advertisement

Great guide mate!!! I was going to pm you to ask for help on this exact matter... Kudos!!  :thanks_speechbubble:  :thanks_speechbubble:

Share this post


Link to post
Share on other sites

Great guide mate!!! I was going to pm you to ask for help on this exact matter... Kudos!!  :thanks_speechbubble:  :thanks_speechbubble:

You're welcome.

 

If there's anything that's not clear enough or if you have any suggestions to make this tutorial clearer/better, please, don't hesitate to tell me and I'll see what I can do. :)

Share this post


Link to post
Share on other sites

Hi arsadu

great guide, very detailed!

would you mind testing something?

instead of this patch,

can you try this 3 settings in clover:

I think the result might be the same. Although I don't see anything related to Patch VBios. Which is needed to get the logo back (or at least it was in my case).

 

Nonetheless, I'll try this, and update this post when done. :)

 

UPDATE:

post-1303722-0-56151500-1444063873_thumb.png post-1303722-0-75926300-1444063885_thumb.png post-1303722-0-19369900-1444063898_thumb.png

 

With this configuration, and with or without Patch VBios and Inject EDID, I got the old issue back: no logo and loading bar on the bottom left corner. Without PatchVBios and Inject EDID I also got the first stage boot resolution higher than it should be. :)

Share this post


Link to post
Share on other sites

So I enabled patch vbios and inject edid turned off verbose boot and rebooted. then my motherboard died, I blame this thread. Had to run out and buy a new one...typing from it now, that is all. asus z97-a I was running pci and integrated gfx at the same time. now  on z97-e but no usb3.1 support in 10.11 oh well.

Share this post


Link to post
Share on other sites

So I enabled patch vbios and inject edid turned off verbose boot and rebooted. then my motherboard died, I blame this thread. Had to run out and buy a new one...typing from it now, that is all. asus z97-a I was running pci and integrated gfx at the same time. now on z97-e but no usb3.1 support in 10.11 oh well.

I don't see how patching the video bios could damage the motherboard. Were you running dual monitors? How exactly were you running two graphic sources at the same time?

Nonetheless, I'm sorry about your motherboard. I still don't know how could this thread contribute to that, but I feel obligated to remind you what I wrote above:

1. I am not responsible for any damage that you might do to your hardware

2. This has not been tested on all video cards and under all circumstances.

So you're doing it at your own risk.

 

Could you please tell me which dedicated graphics card are you using?

Share this post


Link to post
Share on other sites

Added more option to en/disable EFI Strings injection for your risk free if you want to, BOOTX64.efi rev 3279

 

GTCKdlV.jpg

 

Dump device-properties

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml"

Small util to show gfx hex (place in same directory with "gfxutil" & "device-properties.xml") for easy to copy & paste into config.plist. Save as "gfx.command" & chmod +x:

#!/bin/bash

cd "`dirname "$0"`"
./gfxutil -i xml -o hex "device-properties.xml" "device-properties.hex"
cat <<EOF
---
`cat device-properties.hex`
---
EOF

VRAM values table would be nice too, 0x40000000 = 1024 | 0x80000000 = 2048 | etc : )))

Edited by cecekpawon

Share this post


Link to post
Share on other sites

Added more option to en/disable EFI Strings injection for your risk free if you want to, BOOTX64.efi rev 3279

 

GTCKdlV.jpg

 

Cool, but what exactly does this do? Also, will you be able to do it for newer Clover versions (like 3280 now), in case people want it?

 

Dump device-properties

ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml"

 

I'll add this to the thread. Thank you. So with this, the user doesn't need to use DarwinDumper anymore to extract the device-properties.hex file, since the command automatically outputs both the hex and the xml files in the same folder. Nice!

 

Small util to show gfx hex (place in same directory with "gfxutil" & "device-properties.xml") for easy to copy & paste into config.plist. Save as "gfx.command" & chmod +x:

#!/bin/bash

cd `dirname $0`
./gfxutil -i xml -o hex "device-properties.xml" "device-properties.hex"
cat <<EOF
---
`cat device-properties.hex`
---
EOF
VRAM values table would be nice too, 0x40000000 = 1024 | 0x80000000 = 2048 | etc : )))

 

 

Ok, I'll add this, as well. So with this we don't need HexEdit anymore. :) Interesting.

 

I'll also add a little table or something close to that (though I'm still not sure this forum supports tables). I guess I could do it in xls and take a screenshot of it.

 

Thank you! :)

Share this post


Link to post
Share on other sites

I don't see how patching the video bios could damage the motherboard. Were you running dual monitors? How exactly were you running two graphic sources at the same time?

Nonetheless, I'm sorry about your motherboard. I still don't know how could this thread contribute to that, but I feel obligated to remind you what I wrote above:

1. I am not responsible for any damage that you might do to your hardware

2. This has not been tested on all video cards and under all circumstances.

So you're doing it at your own risk.

 

Could you please tell me which dedicated graphics card are you using?

 

Running triple display with dvi+hdmi on gtx970, and hdmi on hd4600. After setting patch vbios and inject edid I did reboot, and it froze at the login prompt. after rebooting it wouldn't even post, just rebooting over and over. This is what I get for trying to fix something that isn't broken. Off to fill out some RMA forms!

 

Also if I disable verbose boot I get the loading screen just fine, so I'm pretty sure I did this for no reason other than to destroy stuff.

Share this post


Link to post
Share on other sites

Running triple display with dvi+hdmi on gtx970, and hdmi on hd4600. After setting patch vbios and inject edid I did reboot, and it froze at the login prompt. after rebooting it wouldn't even post, just rebooting over and over. This is what I get for trying to fix something that isn't broken. Off to fill out some RMA forms!

 

Also if I disable verbose boot I get the loading screen just fine, so I'm pretty sure I did this for no reason other than to destroy stuff.

Did you try booting from a USB installer?

 

This tutorial is not for multiple display setups. I will add this to the thread. You are adding the default display port. This doesn't even consider the possibility of a multiple display setup. Also, I did mention it's not for iGPUs.

Share this post


Link to post
Share on other sites

Cool, but what exactly does this do? Also, will you be able to do it for newer Clover versions (like 3280 now), in case people want it?

 

To en/disable inject if something goes wrong (ex: failed to boot / screwed display) when playing with those efi / properties strings.. fully optional

<key>Devices</key>
<dict>
  <key>Inject</key>
  <true/>
  <key>Properties</key>
  <string>...</string>
</dict>

Share this post


Link to post
Share on other sites

Works here @0, thanks 

 

edit: that was with minimal DSDT edit, RADEON_FB @0,AAPL,boot-display

with full DSDT edit, FUTOMAKI_FB, had to change it to @2,AAPL,boot-display

You're welcome! Glad it worked.

 

So you have a Sapphire Toxic R9 270, right? This would be the first ATI card tested so far. :)) So, you've got the same issue (no second stage boot logo and loading bar in the bottom left corner of the screen)? Just trying to understand if this tutorial only works for this specific issue or can do other things as well.

 

Also, since I'm no expert with ATI cards, could you describe a little bit what did you do, in case other people want to get their ATI cards fixed, as well? I would be glad to point to your post, as reference, if you would be kind enough to do that. Or if you want, I can add it to the initial post.

 

Also, does this work only with Clover DSDT patches? Did you try it? I mean...I see no reason why it wouldn't work but just making sure. I'm trying to keep this thread as close to minimal edits as possible. And adding DSDT editing here is not quite part of my plans. :D Not that I wouldn't love to learn more about that. But I find it a tad more complicated than this.

Share this post


Link to post
Share on other sites

To en/disable inject if something goes wrong (ex: failed to boot / screwed display) when playing with those efi / properties strings.. fully optional

<key>Devices</key>
<dict>
  <key>Inject</key>
  <true/>
  <key>Properties</key>
  <string>...</string>
</dict>

 

Could you please, try the attached script on your computer?

 

I can't seem to get it to work.

 

It always says: "./gfxutil: No such file or directory"

 

gfxutil is, of course, present in that directory. Along with device-properties hex and xml. So I'm not really sure what's wrong.

gfx.zip

Share this post


Link to post
Share on other sites

- cd to your working dir (with gfxutil there)

 

- OR -

 

- save as "gfx.command" in gfxutil & "device-properties.xml" directory

- chmod +x "gfx.command"

- double click to execute

Share this post


Link to post
Share on other sites

- cd to your working dir (with gfxutil there)

 

- OR -

 

- save as "gfx.command" in gfxutil & "device-properties.xml" directory

- chmod +x "gfx.command"

- double click to execute

Apparently it can't run from the working directory. Be it a simple gfx executable file or gfx.command file. Actually I couldn't find any difference between the two approaches. Is there any actual difference between these two? At least in this context?  :)

 

Now, it does however work if you're cd-ing into the working directory and running the executable from there. I'm just not sure why it doesn't do that when you're launching it from the directory itself.

 

Launching with double-click (which is what I would like to achieve):

post-1303722-0-94877900-1444113902_thumb.png

 

Launching by browsing into the working directory and ./ from there:

post-1303722-0-09148200-1444113961_thumb.png

 

Maybe the way I'm making the script is wrong...

 

I'm doing

cd [directory path]
pico gfx.command

[paste the content here]

 

CTRL+X to exit. ENTER to save the name

 

Then

chmod +x "gfx.command" \\ (with or without quotes seems to be the same)

And double click to execute.

gfx.command.zip

Share this post


Link to post
Share on other sites

Sorry @arsradu, edited my post please review.. Problem was path with "space" : "GFX test", fixed by quoting them

 

Both ways are basically the same, please do not confuse, do whatever you like: direct from terminal / by double clicking it 

Share this post


Link to post
Share on other sites

I have to chime in this one with the note that it was I who discovered that you need @1,AAPL,boot-display... feel free to verify this in the other Apple logo related thread.

Is that the only variable that affect the 2nd stage boot?

Share this post


Link to post
Share on other sites

I have to chime in this one with the note that it was I who discovered that you need @1,AAPL,boot-display... feel free to verify this in the other Apple logo related thread.

 

I take it that modesty is not your strong suit. :P However, I am a guy who considers that credit should be given where credit is due. And, with this, I also want to thank you for your help and insight in this. It's definitely helping. Also, just so you know, skipping you from the credits list was nowhere near my intentions. :) I was just not aware of the origin of the idea/research.

 

So, again, thank you. And I just added you to the list of people that contributed with very good ideas/research on getting this issue fixed.

 

Hope it's ok now.

Share this post


Link to post
Share on other sites

 

So my name should be
added to that list does not it?
 

 

 

Of course! 

 

Anyone else wants his name on the first page of this thread? :P I'm feeling generous today.

 

Joking. I will add the names of the ones that contributed to this. I feel like it's the right thing to do. I hope the list doesn't get longer than the thread itself though...

Edited by Micky1979

Share this post


Link to post
Share on other sites

One of the last mysteries is screen flash before last stage, real mac saw the same problem too? Who can figured it out?

Yeah, this is an issue with hackintosh desktops... Laptops seems seems to be ok, for some reason.

 

And I don't think real macs (as in Mac Pros or iMacs) have this issue... I might be wrong though. I will check it out today, if I have a bit of time.

 

Update: on an iMac 27" late 2010, running Yosemite (10.10.4), the boot process is identical! Meaning WITH that gap between first stage and second stage. It might be faster and less noticeable on SSDs. But I think the HDD might play some role in the transition speed between the two stages.

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 Shogun
      Hi,

      I'm trying to get a clean install of High Sierra, but didn't manage to get too far... stuck on pre-installer with some errors.

      General flow that i've tried, following relevant guides and some success stories:
      1. Used [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] to create bootable usb drive.
      2. Tried to use different options, UEFI boot mode, Legacy boot mode, with and without Clover configuration...

      In legacy mode it restarts after last error, while in uefi it hangs on kextd stall...

      Screens with error and clover folder/config attached.

      Motherboard: ASUS P8P67 EVO
      CPU: i7 2600K (not overlocked)
      Graphics: Sapphire Pulse Radeon RX 580 8GB
      Memory: Kingston 16 GB (2x8gb) 1333MHz
      Storage: SSD Samsung 860 EVO 500GB + Samsung 860 EVO 1TB

      Are this components compatible with High Sierra? From what i see on other threads, people got it working somehow.
      Should i use Legacy boot mode as of advice from [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or is possible to get it working with UEFI? Which one is better?

      How to get rid of "Unsupported CPU for reporter"?

      Any help would be highly appreciated. I'm desperate on wasting time to get it working. 

      Thanks!


      CLOVER.zip
      config.plist
    • By JackRabbitSlim
      Hi everyone,
      This is my first hackintosh. To be completely honest there's still a lot I'm trying to figure out... And considering I can't even get the installer to begin, seems like there's something I'm just not understanding. Any help would be greatly appreciated!!
       
      I've specced the machine based on a multiple successful builds I've seen in various vanilla forums.
      I've set the recommended BIOS, double-checked, but can't even get to an installer screen despite following a Vanilla guide from a popular hackintosh youtuber.
      (Not sure if her links can be mentioned, posted etc... Just playing it safe since this is my 1st post...)
       
       
       
      THE BUILD:

      Gigabyte Z390 Designare
      i9 9900k
      Sapphire Radeon RX580 Pulse - 8 GB
      G.Skill TridentZ 3200 - 64 GB
      Samsung EVO 840 (This is a scrap drive. Planned on using it to get the build running first, then cloning my MP 5,1 HS image after.)
      Other Stuff: Bluetooth, USB, iGPU, etc not important yet... Current goal is just to get the machine booting... I'll focus on WIFI/BT etc after...
       
      I've tried multiple SMBIOS profiles, (listed below). All of them prevent me from even booting the installer with the message below.
      At this point I'm wondering if the issue is HS related, or if there's a step that, although obvious to some, isn't obvious to me and overlooking somehow.
       
      Message returned when attempting to boot the installer. (Pic attached):
       
      This version of Mac OS X is not supported on this platform!
      Reason: Mac-AA95B1DDAB278B95
       
      I also get an error when I click update in Clover saying: Package is incompatible with this version of OS X and may fail to install
      ^ Seems like this indicates I've missed a step or done something wrong?
       
      Here's a list of the complete steps I've taken so far:
       
      Double-checked BIOS settings according to each build.
      Built a vanilla installer based on the video I mentioned above, steps listed below... (I've done this twice now, confirming I followed the steps in the guide.)
       
      Vanilla Installer Steps:
      Wiped and formatted my thumb drive with GUID Partition, HFS Extended (Journaled) Used terminal to create a bootable installer from a 10.13.6 installer I downloaded last june/july. Installed Clover Bootloader onto the Install macOS High Sierra partition of the thumb drive, and ticked: Clover for UEFI booting only, Install Clover into the ESP, VBox HFS-64, APFSDriverLoader-64, AptioMemoryFix-64 (leaving everything else unticked.)  
      Clover Configurator Steps:
      Mounted the Thumb Drive's EFI folder, opened C.C. and "downloaded" Lilu, WhateverGreen, & FakeSMC to the Other folder, & installed sensors. Deleted the default plist and manually created one using the Coffee Lake 'sample plist' from r/Vanilla Hackintosh Desktop Guide. Copy plist to the mounted EFI folder.  
      Open the plist with CC and did the following:
      Confirmed the following flags were set in CC's Boot section - Verbose (-v), dart=0, debug=0x100, & keepsyms=1 Tried 5 different SMBIOS profiles - iMac 18,1 ,  iMac 18,3 ,  iMac 19,1 , iMacPro 1,1 , and MacBookPro 15,1.  
      All result in the same Mac OS X is not supported on this platform message. The one suggestion I've found so far that seemed like it might work was to add the boot argument:
       -no_compat_check
       
      Same results, installer won't start and I get the same message...
       
      Seems like there must be something I've missed or I've done something wrong... I've spent the weekend searching, reading, etc, no luck so far...
       
      A few questions:
       
      I made the installer on my MacBook, not the build I'm trying to hack. Could this be related to the issue?            (I.e. - Does the vanilla method mean you need to create your SMBIOS profile on the actual machine you'll be Hackintoshing?)
       
      Is there a 9900k or Sapphire RX580 compatibility patch needed for 10.13 I haven't seen mentioned in the Mojave builds?  
      Does the Clover update message package is incompatible with this version of OS X and may fail to install indicate something isn't right with my installer setup?  
       
      Please excuse me if anything above isn't clear, I'm brand new to all this and frankly I'm having a hard time wrapping my head around a lot of it!
       

    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • 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, 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 Candrahm
      Hi everybody,
       
      I'm new here and French. 
      I success to hack my Asus X751LJ and pass it to High Sierra 10.13.6, not easily, and everything works except the keyboard and the touchpad.
      I tried VoodooPS2Controller, ApplePS2SmartTouchpad, even VoodooI2C, but nothing works...
      Could someone help me? Is there a DSDT problem? Witch kext should I use?
      I post my ACPI and Kexts folders and my IOReg.
      Please... Help me. I'm desperate...
      MacBook Pro de Candrahm.ioreg
      Archive.zip
×