Jump to content
About Just Joined group Read more... ×
arsradu

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

391 posts in this topic

Recommended Posts

Short answer is yes on x64 versions of Windows 7 (and even Vista SP1 X64 :)).  With Clover, I have always installed Windows 7 in UEFI mode on a pure GPT drive....

 

attachicon.gifWIN7X64 UEFI mode.png

 

Long answer is a qualified yes (should be OK on PCs) because these operating systems still assume the presence of legacy BIOS INT10 support in the firmware - see UEFI Firmware - TechNet - Microsoft.  Interestingly, it is almost impossible to install Windows 7 in EFI mode on Macs because of its reliance on legacy video BIOS calls but Windows 8 and 10 are OK because they supply fully UEFI compatible GOP video drivers.

 

Awesome reply, as usual. :) Thank you!

 

Thing is...I had Windows 8 installed before. Also had Windows 10 installed for a while, and didn't like it at all. Now, I don't use Windows 7 as often (actually only when there is no way I can do that thing from Mac). So I guess I could install Windows 8 then. What would you recommend? 

 

I'm using Windows 8.1 at work, had Windows 8 before, and I can't say I'm very impressed with it. After all, it's Windows. :)) But some tools are (still not compatible) with Windows 8 or run poorly on Windows 8 (especially the ones requiring drivers to be installed). For example, there is a flash tool for my phone. And in order to install the drivers that come with it, I had to switch to test mode or something, so that it would let me install those drivers.

 

I didn't have this issue with Windows 7. Also, I don't flash my phone every day. So...I don't know. What's your experience with it so far? And also, does it run better in UEFI mode than it does in legacy mode?

7 can boot from GPT, although I think it could be a little tricky getting it to install if you have multiple drives. I have three drives here (1xSSD and 2xHDD with OS X on one of the HDDs) and the 7 installer would get confused by the multiple EFI partitions. I had an old legacy install on my SSD that I eventually converted to UEFI before moving to 10. I did this by backing up the 7 partition to a file, installing 7 in UEFI mode and then overwriting it with my original 7 image. I think I may have had to disconnect the hard disks first so the install would complete successfully.

 

Here's the device properties I'm currently using for the 670. It also has those display-cfg values set as they default to ffffffff otherwise. I don't think they make any difference but I have them in there right now. I'm also injecting my audio as you can see.

 

 

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
	<dict>
		<key>@0,AAPL,boot-display</key>
		<string>0x00000001</string>
		<key>@0,display-cfg</key>
		<string>0x00030103</string>
		<key>@1,display-cfg</key>
		<string>0x0100ffff</string>
	</dict>
	<key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
	<dict>
		<key>PinConfigurations</key>
		<data>
		</data>
		<key>layout-id</key>
		<string>0x00000001</string>
	</dict>
</dict>
</plist>

 

 

Yeah, that's pretty much what I did.

 

Except I didn't add display-cfg for either one of the ports. I didn't know what should I add...if I was supposed to add something.

 

Thanks for the info on Windows 7.

 

And, you know, even Ubuntu does this (to me it was surprising, and not good surprising), if you don't remove the other drives, except for the one you're attempting to install the operating system on.

 

I had Ubuntu + Windows on one HDD (still have), on /sdb. And OS X on /sda (I think Linux users know what I mean)

 

And I reinstalled Ubuntu, without unplugging the other HDD. Guess what happened? It installed GRUB in EFI, on my /sda HDD, although I specifically mentioned NOT to do that. Because...reasons. Didn't they test this with more than one HDD? Who has only one HDD nowadays anyway?

 

It wasn't a big thing to remove it after that. But I'm just saying.

 

With Windows, if you have more than 1 HDD when installing it, it will tell you that you have too many primary partitions. :)))) With a very non comprehensive error. In the old Windows spirit, of course. Which I found to be both insanely stupid and annoying, but also extremely hilarious. Too many primary partitions??? When I'm trying to install Windows on THE SAME partition as before, without adding/removing any other primary partitions in the meantime? I mean, seriously! What the hell did it do? Count all the partitions from all the hard drives? I can't imagine another way.

 

Anyway, yes, when you have multiple Hard drives/SSD, best way is to unplug all the drives you don't need. It's the best way.

Share this post


Link to post
Share on other sites
Advertisement

Those display-cfg values for first and second port seem to be generic. They make no difference with the 670 and I've booted it just fine without setting them. The only time I saw them make a difference was with the 210 where removing them cause a brief flicker between stages 1 and 2.

 

I can't think of why you had trouble booting with the stock drivers, it doesn't make much sense.

Share this post


Link to post
Share on other sites

My recommendation would be to only boot OS X! :)

 

All windows installs in a VM environment.

 

I boot win 10 in VMware when I must use it.

Share this post


Link to post
Share on other sites

@Robert, thank you!

 

You also have both VRAM,totalsize (128 MB) and VRAM,totalMB (4096 MB). And since you see 4096 MB in About this Mac, it clearly ignores VRAM,totalsize.

 

Also, I was just talking about this with a good friend of mine on the forum, and he suggested that VRAM,totalsize might actually be used for iGPUs. So, for dedicated graphics, we don't need it.

 

I haven't tried booting with my internal GPU yet, to confirm this.

 

I did however try VRAM,totalMB with my GTX 650. And everything ok. It shows 2048 MB, as it should.

 

So I'll get to upgrading the tutorial to reflect these changes (switch to VRAM,totalMB and updating the hex values to reflect that).

 

 

Uhm, and Riley, if I'm not mistaken, I think this one goes to you, man. Thank you.

Share this post


Link to post
Share on other sites
Also, I was just talking about this with a good friend of mine on the forum, and he suggested that VRAM,totalsize might actually be used for iGPUs. So, for dedicated graphics, we don't need it.

 

That makes sense. The i7 in my Z68 has integrated graphics (which I'm obviously not using) and VRAM,totalsize appears in the IOReg. The i7 in my X79 doesn't have integrated graphics and there's no VRAM,totalsize in the IOReg.

Share this post


Link to post
Share on other sites

That makes sense. The i7 in my Z68 has integrated graphics (which I'm obviously not using) and VRAM,totalsize appears in the IOReg. The i7 in my X79 doesn't have integrated graphics and there's no VRAM,totalsize in the IOReg.

Wanna hear something funny? I've got an internal GPU, as well. But I have no VRAM,totalsize in IOreg, unless I manually add it. Do I have to boot from that GPU in order to be able to get something in IOreg?

Share this post


Link to post
Share on other sites

I don't think so. I've never booted with the internal GPU here. I'll check the laptop later as it uses HD4000 gfx. Either way it seems VRAM,totalMB is the way to go.

It is the way to go up to 16 GB of VRAM on the first post :P

 

Check it out. :)

Share this post


Link to post
Share on other sites

My recommendation would be to only boot OS X! :)

 

All windows installs in a VM environment.

 

I boot win 10 in VMware when I must use it.

 

One more reason to switch to Mac.

 

post-1303722-0-57978000-1445162114_thumb.png

 

Left side - El Capitan = around 40 GB used, with all my programs and tools and stuff installed.

Right side - Windows 7 = around 60 GB used, with none of my programs installed. The mystery of the disappearing storage. I think Microsoft knows everything about it.

 

Sorry about the off-topic. Just wanted to share this with you guys real quick.

Share this post


Link to post
Share on other sites

Hello arsradu!

I don t use DSDT or SSDT.

 

device-properties.xml

 

DPH https://www.dropbox.com/s/4us6ddcyb0yfy06/device-properties.hex?dl=0

 

post-404665-0-46760200-1445698708_thumb.png

 

https://www.dropbox.com/s/gw4zly2cfvg04ec/config.plist?dl=0

 

My video card: http://www.evga.com/Products/Product.aspx?pn=02G-P4-3757-KR architecture Maxwell

 

How did these values?

 

<!-- Port: DVI-D -->

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>
 
<!-- Port: VGA -->
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>@1,display-cfg</key>
<string>0x00030103</string>
 
<!-- Port: HDMI -->
<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>
 
Thanks

Share this post


Link to post
Share on other sites

 

Hello arsradu!

I don t use DSDT or SSDT.

 

attachicon.gifdevice-properties.xml

 

DPH https://www.dropbox.com/s/4us6ddcyb0yfy06/device-properties.hex?dl=0

 

attachicon.gifScreen Shot 2015-10-24 at 12.57.14 PM.png

 

https://www.dropbox.com/s/gw4zly2cfvg04ec/config.plist?dl=0

 

My video card: http://www.evga.com/Products/Product.aspx?pn=02G-P4-3757-KR architecture Maxwell

 

How did these values?

 

<!-- Port: DVI-D -->

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>
 
<!-- Port: VGA -->
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>@1,display-cfg</key>
<string>0x00030103</string>
 
<!-- Port: HDMI -->
<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>
 
Thanks

 

 

I don't quite understand the question.

 

Judging by your IOreg, your display is connected to port B@1, which in your case I think it's HDMI. So you need to set boot-display to @1 like so:

 

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

The comments on top of the code are obviously for my card. If you don't have the same card, your ports are most likely going to be different. I think I'll remove those comments and reupload, just to avoid confusion in the future.

 

@Guys, I've noticed this before: a card with 3 ports like this GTX 750 shows 4 ports in IOreg. Or one with 4 ports shows 5 ports? Why is that? Any idea?

Share this post


Link to post
Share on other sites

It has three entrances. DVI, HDMI and DP.

Yes is connected to the HDMI. Okay I'll try that.

 

You should have something like this in your device-properties.xml:

 

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

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>

<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>

<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>

<key>@3,compatible</key>
<string>NVDA,NVMac</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>NVDA,Display-D</string>

<key>VRAM,totalMB</key>
<string>0x00000800</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>EVGA GeForce GTX 750</string>
<key>rom-revision</key>
<string>80.07.35.00.04</string>

Share this post


Link to post
Share on other sites

 

 

You should have something like this in your device-properties.xml:

 

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

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>

<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>

<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>

<key>@3,compatible</key>
<string>NVDA,NVMac</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>NVDA,Display-D</string>

<key>VRAM,totalMB</key>
<string>0x00000800</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>EVGA GeForce GTX 750</string>
<key>rom-revision</key>
<string>80.07.35.00.04</string>

 

Just centralized.

 

I do the process again several times and check that only
 
<key>@1,AAPL,boot-display</key>

<string>0x00000001</string> 

 
always disappears from device-properties.xml

Share this post


Link to post
Share on other sites

 

Just centralized.

 

I do the process again several times and check that only
 
<key>@1,AAPL,boot-display</key>

<string>0x00000001</string>

 
always disappears from device-properties.xml

 

<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key><dict>
<!-- Primary display -->
<key>@1,AAPL,boot-display</key>
<string>0x00000001</string>

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>

<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>

<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>

<key>@3,compatible</key>
<string>NVDA,NVMac</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>NVDA,Display-D</string>

<!-- start: regular values -->
<key>VRAM,totalMB</key>
<string>0x00000800</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>EVGA GeForce GTX 750</string>
<key>rom-revision</key>
<string>80.07.35.00.04</string>
<!-- end: regular values -->
</dict>

If you still have issues please, upload your device-properties.xml and config.plist (without changing the file to .txt).

Share this post


Link to post
Share on other sites
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key><dict>
<!-- Primary display -->
<key>@1,AAPL,boot-display</key>
<string>0x00000001</string>

<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>NVDA,Display-A</string>

<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>

<key>@2,compatible</key>
<string>NVDA,NVMac</string>
<key>@2,device_type</key>
<string>display</string>
<key>@2,name</key>
<string>NVDA,Display-C</string>

<key>@3,compatible</key>
<string>NVDA,NVMac</string>
<key>@3,device_type</key>
<string>display</string>
<key>@3,name</key>
<string>NVDA,Display-D</string>

<!-- start: regular values -->
<key>VRAM,totalMB</key>
<string>0x00000800</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>EVGA GeForce GTX 750</string>
<key>rom-revision</key>
<string>80.07.35.00.04</string>
<!-- end: regular values -->
</dict>

If you still have issues please, upload your device-properties.xml and config.plist (without changing the file to .txt).

 

Thanks arsradu

 

device-properties.xml

config.zip

 

This code does not write in my xml file:

 

<key>@1,AAPL,boot-display</key>

<string>0x00000001</string>

Share this post


Link to post
Share on other sites

Thanks arsradu

 

attachicon.gifdevice-properties.xml

attachicon.gifconfig.zip

 

This code does not write in my xml file:

 

<key>@1,AAPL,boot-display</key>

<string>0x00000001</string>

 

You already have it. Look under the keys starting with:

<key>@1....</key>

Anyway, I reattached it, making it a bit clearer now. :)

 

Now you have to convert it back into device-properties.hex, use the hex code in config.plist, and enjoy.

device-properties.xml.zip

Share this post


Link to post
Share on other sites

Sorry you're right. Just not at the beginning of the code. How could I be so stupid? Thank you.

 

Yep. You're welcome. Let me know if it works for you. :) Hope it does.

Share this post


Link to post
Share on other sites

Yep. You're welcome. Let me know if it works for you. :) Hope it does.

Well, well

With or without nVidia Web Driver - centered

With or without mask Clover DSDT 0 - centered

Maybe for my GTX 750 this method doesn't really work!

Share this post


Link to post
Share on other sites

Well, well

With or without nVidia Web Driver - centered

With or without mask Clover DSDT 0 - centered

Maybe for my GTX 750 this method doesn't really work!

 

I don't get it. What exactly are you trying to do? What is the issue you're trying to fix with this tutorial?

Share this post


Link to post
Share on other sites

I'm trying fix second stage boot logo and loading bar being displayed on the bottom left corner of the screen.

I don't know if it's right. As it's in the videos is right?

https://www.dropbox.com/s/3qmnyjqmyjgy8tq/Boot_Movie.mp4?dl=0

https://www.dropbox.com/s/kscfsrpvckzcas4/Boot_Movie_Verbose.mp4?dl=0

 

The loading bar should still appears?

Thanks!

Share this post


Link to post
Share on other sites

I'm trying fix second stage boot logo and loading bar being displayed on the bottom left corner of the screen.

I don't know if it's right. As it's in the videos is right?

https://www.dropbox.com/s/3qmnyjqmyjgy8tq/Boot_Movie.mp4?dl=0

https://www.dropbox.com/s/kscfsrpvckzcas4/Boot_Movie_Verbose.mp4?dl=0

 

The loading bar should still appears?

Thanks!

 

Hi

 

The only thing missing in your boot is the second stage Apple Logo. You don't have any loading bar on the bottom left corner of the screen, unless the videos you uploaded are not actually yours.

 

YES, the loading bar is intended, and in your case it's right where it should be (and not at the bottom left side of the screen). So nothing to fix there.

 

You can attempt to fix your Apple Logo by checking Patch VBios and Inject EDID options in your config.

Share this post


Link to post
Share on other sites

Hi

 

The only thing missing in your boot is the second stage Apple Logo.

 

YES, the loading bar is intended, and in your case it's right where it should be (and not at the bottom left side of the screen). So nothing to fix there.

 

You can attempt to fix your Apple Logo by checking Patch VBios and Inject EDID options in your config.

Patch VBios and Inject EDID options in my config is checked.

Maybe I need my own EDID.

So, it's another case. Thanks arsradu!

Share this post


Link to post
Share on other sites

Patch VBios and Inject EDID options in my config is checked.

Maybe I need my own EDID.

So, it's another case. Thanks arsradu!

 

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.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By gekko.be
      I have an old Hackintosh that I have brought back to life. An ASUS P5KPLAM-SE mobo, Intel Core 2 Quad, with a Sapphire HD 5670 1GB graphics card. It used to work just fine on High Sierra 10.13.3 (I think it was .3) However I only used the DVI port. Updated to 10.13.6 and with AMD kexts rollback to the previous versions I got everything o wrk just fine: boot, HDMI video, HDMI audio etc etc. The only problem I face is that my USB keyboard and mouse freeze/hang seemingly very random... I can not seem to get it right. Unplugging and replugging the USB device makes it work again, sometimes for a few seconds sometimes for an hour ... No idea what's wrong... Have tried tons of options in clover, USBInjectall.kext with port limit patch, whatever I could find... Would there be anyone out there who would have an idea of what could be the problem?
    • By macinsane
      *This guide is deprecated and will not be maintained anymore*

      Update: Now running Mojave! Thanks to mojave2core! Yeah   Still using C2D in 2019!
      Inserted a nice and cheap GT710 that is not relying on nVidias Webdrivers and runs OOB under Mojave.
       
      Nice, seeing High Sierra running on this old but capable system! It rocks with a new ASUS GT1030
       
      Config:
      Gigabyte EP43-DS3L
      Core2Quad Q9300
      6 GB DDR2 RAM
      Asus GT1030 2GB
      Sandisk SSD 128GB
      TP-Link AC1200 Wifi USB
      Inateck KT4006 USB 3.0 PCIe (No boot)
       
      SMBIOS: iMac14,1
      Clover: 4297  4360
       
      A good deal of DSDT editing was necessary to get this machine to boot High Sierra but finally it works flawlessly, even sleep and wake!
      You NEED to have the DSDT put in place for installation because otherwise macOS doesn't recognize the SATA ports.
      There are a few important BIOS settings: SATA hast to be set to AHCI and "native" and HPET has to be run "64-bit", I'd recommend to disable IDE and the serial and parallel port.
      For the GT1030 nVidia Webdrivers are needed, have to boot with nv_disable=1 until you have them installed.
      You have to install Clover in legacy mode because this old fella does not support UEFI.
       
      Only downside: The so often recommended Inateck USB-card isn't recognized by BIOS, so you cannot boot from it. It works perfectly within macOS though, have the ac-Wifi connected to it.
      config.plist.zip
      DSDT.aml.zip
    • By eLDeus
      Hello, can't figure out why there's no Line-In input option with VoodooHDA, but I definetly have it in my built-in audio card on the motherboard.
      Thanks!
    • By Rajan Pandit
      Hai, I have i5 2500k with 8GB Ram, GA-Z86 AP-D3 Rev. 1 (F3 Bios) with Samsung EVO SSD... 
      I Installed High Sierra 10.13.6, I use ##### to activate boot... everything is fine..
      but sometime my system Freeze..... and sometimes screen freeze but mouse worked
      means system is running.. mouse is also moving.. but Screen got freeze...
      please help me to resolve.. I really frustrated now. I install many times...
      but same problem... There is no graphic card in my system...
       
      please help me.. I am attaching my clover folder.. please help
      CLOVER.zip
    • 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.  Edit: Recommend 16GB or larger for macOS Catalina 10.16 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.6_18G103
      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.
       
      Updated Download Links for macOS Catalina 10.15.6_19G73
      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  
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
      InstallInfo.plist_edited_10.15.6.zip
×