Jump to content
glasgood

[SUCCESS][GUIDE] Glasgood's High Sierra CoffeeLake: ASUS STRIX Z370-G - i7-8700 - GTX1080ti - UHD

294 posts in this topic

Recommended Posts

Hey @Glasgood,

 

I´ve followed your guide and redone things a few times, yet I have run into a problem when installing:

• When I get to the Boot screen with the High Sierra Installer, I do have a picture of the blurry High Sierra in the background, and 6 icons - but there are no Mac OS logos or any other way to pick an installer. (The image has moiré, my screen doesn´t look as weird as the pic indicates).

I´ve backtracked and tried retracing my steps, and even redone the installer several times on new USB key etc, but to no avail:

• RAM sticks are in A1 and A2 (Should I remove one?)
• I followed the guide for the USB stick

• OS High Sierra installer version 13.2.01

• Copied your EFI folder and files to the hidden EFI disk

• Removed the specific .aml file for your ASUS MB

• Tried several USB ports on new machine

• Updated BIOS to latest: 0802
• Changed the BIOS settings according to your guide

 

Any idea what is wrong and what to do?
:compress:  :)

post-1260652-0-66648500-1514379299_thumb.jpg

Share this post


Link to post
Share on other sites
Advertisement

Hey @Glasgood,

 

I´ve followed your guide and redone things a few times, yet I have run into a problem when installing:

 

• When I get to the Boot screen with the High Sierra Installer, I do have a picture of the blurry High Sierra in the background, and 6 icons - but there are no Mac OS logos or any other way to pick an installer. (The image has moiré, my screen doesn´t look as weird as the pic indicates).

 

I´ve backtracked and tried retracing my steps, and even redone the installer several times on new USB key etc, but to no avail:

• RAM sticks are in A1 and A2 (Should I remove one?)

• I followed the guide for the USB stick

• OS High Sierra installer version 13.2.01

• Copied your EFI folder and files to the hidden EFI disk

• Removed the specific .aml file for your ASUS MB

• Tried several USB ports on new machine

• Updated BIOS to latest: 0802

• Changed the BIOS settings according to your guide

 

Any idea what is wrong and what to do?

:compress:  :)

 

Try and upgrade Clover first >> Steps if problem persists then upload your EFI folder ?

Share this post


Link to post
Share on other sites

Sure can :)
 


I downloaded and installed Clover on my main drive - using the options you described (thanks!).
My EFI partition and USB stick were both mounted while I installed Clover, but not sure if it installed anything on these two drives.
Sorry - I´m probably slow, but do I need to choose the "hidden" EFI drive as destination for the install?
(If so, it´s not possible to install pref panel)

EFI.zip

Share this post


Link to post
Share on other sites

Sure can :)

 

I downloaded and installed Clover on my main drive - using the options you described (thanks!).

My EFI partition and USB stick were both mounted while I installed Clover, but not sure if it installed anything on these two drives.

Sorry - I´m probably slow, but do I need to choose the "hidden" EFI drive as destination for the install?

(If so, it´s not possible to install pref panel)

 

Hi BauerMac,

 

The EFI folder you uploaded works on my Hackintosh with no problems, double check your BIOS settings. If your screen resolutions different from 2560x1440, then try changing that value with Clover Configurator. 

 

[sharedmedia=core:attachments:278365:Screen Shot 2017-12-27 at 14.47.27.png]

post-1077361-0-33250000-1514386186_thumb.png

Share this post


Link to post
Share on other sites

FYI I noticed that I have several EFI partitions with the exact same size.
I actually managed to accidentally mount one that wasn´t connected to my OSX Installer USB, but hopefully didn´t mess anything up by copying elements to it :(

Anyways, here is a list of the disks I have.
Is there any chance that the Terminal commands in your guide can make an installation on the wrong EFI partition?
(I double-checked the USB stick and its EFI partition, and I DID copy your EFI folder over to that partition.)



 


Hi BauerMac,

 

The EFI folder you uploaded works on my Hackintosh with no problems, double check your BIOS settings. If your screen resolutions different from 2560x1440, then try changing that value with Clover Configurator. 

 

[sharedmedia=core:attachments:278365:Screen Shot 2017-12-27 at 14.47.27.png]

Cool, thanks for checking! :) :)

The only parts of your BIOS guide I´m unsure of are these two points:

1 Boot → CSM : Disabled ( If left enabled you will not have ugly resolution during boot) So I DISABLE it, right?
2 Ai Tweaker → Asus MultiCore Enhancement: Disable ( but only if you have intel stock CPU cooler ! ) I have a Noctua CPU cooler, so I do NOT disable, correct?

post-1260652-0-41494200-1514386391_thumb.png

Share this post


Link to post
Share on other sites

 

FYI I noticed that I have several EFI partitions with the exact same size.

I actually managed to accidentally mount one that wasn´t connected to my OSX Installer USB, but hopefully didn´t mess anything up by copying elements to it :(

 

Anyways, here is a list of the disks I have.

Is there any chance that the Terminal commands in your guide can make an installation on the wrong EFI partition?

(I double-checked the USB stick and its EFI partition, and I DID copy your EFI folder over to that partition.)

 

 

 

 

Cool, thanks for checking! :) :)

 

The only parts of your BIOS guide I´m unsure of are these two points:

1 Boot → CSM : Disabled ( If left enabled you will not have ugly resolution during boot) So I DISABLE it, right?
2 Ai Tweaker → Asus MultiCore Enhancement: Disable ( but only if you have intel stock CPU cooler ! ) I have a Noctua CPU cooler, so I do NOT disable, correct?

 

 

It looks like you have managed to install Clover onto all your discs, are you also trying to dual boot with El Capitan ? You should only have Clover installed on one drive, thats the drive that contains High Sierra. You will have to remove the extra EFI partitions from 5 of those discs. Im assuming High Sierra is installed on disk0. If thats the case, use ESP mounter pro to mount the extra EFI partitions and then remove Clover content. Back up your Data before you proceed!  :)

 

Terminal commands, no.

Yes, disable CSM.

I would disable MCE to be on the safe side. You would have to test it and see what temps are like with your cooler.

 

post-1077361-0-09607200-1514386722_thumb.png

post-1077361-0-09607200-1514386722_thumb.png

Share this post


Link to post
Share on other sites

OK, tried updating Clover on the EFI partition using the configurator.
Also tried checking screen resolution.
 

I´m possibly too dense or ignorant to understand this - but when importing the config file from my USB/High Sierra Installer (EFI partition) it seems I cannot update that file to a newer version. At least that´s what I conclude:

When choosing e.g. NVRAM or Themes Editor only my config from my EL CAPITAN install (old mac) shows up, so I figure I will be updating THAT version rather than the EFI partition, and I don´t feel like messing with that right now. 
I hope this makes sense - the Configurator doesn´t seem very intuitive - at least to me :)
If anyone has input, I´ll appreciate it.

 


It looks like you have managed to install Clover onto all your discs, are you also trying to dual boot with El Capitan ? You should only have Clover installed on one drive, thats the drive that contains High Sierra. You will have to remove the extra EFI partitions from 5 of those discs. Im assuming High Sierra is installed on disk0. If thats the case, use ESP mounter pro to mount the extra EFI partitions and then remove Clover content. Back up your Data before you proceed!  :)

Yes, I think you might be right. The Terminal command probably made an installation on all of them :o
I don´t have High Sierra on my current system, only on the 16 GB USB installer > does that change anything?

No, I´m not trying to have dual boot with El Capitan. That´s an error if it looks like that :)
"EL CAPITAN" Is my current boot drive.

I´ll try to mount them all and delete all the Clover content from them (except the USB and EL capitan boot drive).

However - that shouldn´t affect the USB, should it?

 

UPDATE:
• Removed Clover files from one, unrelated disk (storage unit).
• Cant figure out how to update Clover on USB (if possible).
I would think the Clover files from your EFI folder (that I copied) would be relatively updated. Will research.

• Can´t figure out how to change screen res on new machine vs Clover, and dunno if it´s relevant. Looks fine to me, but perhaps the missing boot/installation drives don´t show up because of screen size. Not sure.

 

Share this post


Link to post
Share on other sites

OK, tried updating Clover on the EFI partition using the configurator.

Also tried checking screen resolution.

 

I´m possibly too dense or ignorant to understand this - but when importing the config file from my USB/High Sierra Installer (EFI partition) it seems I cannot update that file to a newer version. At least that´s what I conclude:

When choosing e.g. NVRAM or Themes Editor only my config from my EL CAPITAN install (old mac) shows up, so I figure I will be updating THAT version rather than the EFI partition, and I don´t feel like messing with that right now. 

I hope this makes sense - the Configurator doesn´t seem very intuitive - at least to me :)

If anyone has input, I´ll appreciate it.

 

 

Yes, I think you might be right. The Terminal command probably made an installation on all of them :o

I don´t have High Sierra on my current system, only on the 16 GB USB installer > does that change anything?

 

No, I´m not trying to have dual boot with El Capitan. That´s an error if it looks like that :)

"EL CAPITAN" Is my current boot drive.

 

I´ll try to mount them all and delete all the Clover content from them (except the USB and EL capitan boot drive).

 

However - that shouldn´t affect the USB, should it?

 

The terminal commands diskutil list and mount would not write any data to those partitions. If installing the Clover package, then Clover installer would write data to a partition. 

 

No need to delete EFI content from USB installer. In short, use the USB installer to install High Sierra onto your internal disc. Then copy the EFI folder from your USB installer, and paste it onto the EFI partition on the disc that contains High Sierra. 

Share this post


Link to post
Share on other sites

Thanks - but... ;)

Maybe there is a basic misunderstanding here.

 

1) I am using my OLD/current Hackintosh to prepare a USB etc for my NEW, fresh, clean Hackintosh. There is currently nothing on my new machine other than an empty SSD and an updated BIOS.

2) I am not trying to install Hifg Sierra on my old machine ( the Hackintosh running El Capitan)

3) The screenshot with the missing High Sierra boot/install icon is from my NEW machine.

4) right now my issue is that I cannot install anything on my new Hackintosh since I cannot use the USB and/or cannot access the boot/install process on my new machine.

 

Hope this helps or removes any possible misunderstandings?

Share this post


Link to post
Share on other sites

Thanks - but... ;)

Maybe there is a basic misunderstanding here.

 

1) I am using my OLD/current Hackintosh to prepare a USB etc for my NEW, fresh, clean Hackintosh. There is currently nothing on my new machine other than an empty SSD and an updated BIOS.

2) I am not trying to install Hifg Sierra on my old machine ( the Hackintosh running El Capitan)

3) The screenshot with the missing High Sierra boot/install icon is from my NEW machine.

4) right now my issue is that I cannot install anything on my new Hackintosh since I cannot use the USB and/or cannot access the boot/install process on my new machine.

 

Hope this helps or removes any possible misunderstandings

 

I see,

 

So at the moment you have a a computer build, as per the specifications on your signature ? 

 

Core i7 - 8700K • ASUS Maximus X Hero Z370 • Inno3D iChill GTX 1080 TI • 32 GB HyperX DDR4 • PSU: Corsair RM750X • CPU fan: Noctua NH-D15 • Samsung 500GB 850 EVO M.2 SSD • 7 HDD/SSD drives total • Corsair C70 modded case • Primary use: Creative work, video editing

 

When you boot from the USB Installer, your disc M.2 SSD is not recognised ?

 

If the M.2 ssd is not recognised, then you will have to initalise it. You can initialise the drive following steps in the guide. 

Share this post


Link to post
Share on other sites

I see,

 

So at the moment you have a a computer build, as per the specifications on your signature ? 

 

Core i7 - 8700K • ASUS Maximus X Hero Z370 • Inno3D iChill GTX 1080 TI • 32 GB HyperX DDR4 • PSU: Corsair RM750X • CPU fan: Noctua NH-D15 • Samsung 500GB 850 EVO M.2 SSD • 7 HDD/SSD drives total • Corsair C70 modded case • Primary use: Creative work, video editing

 

When you boot from the USB Installer, your disc M.2 SSD is not recognised ?

 

If the M.2 ssd is not recognised, then you will have to initalise it. You can initialise the drive following steps in the guide. 

Yes, my new build is the one in the signature :)

And yes, I cannot use my M.2 drive ATM (It´s in my BIOS so it´s working), so I´ll try to initialize the drive when I get to that.

 

Right now I simply can´t get to the install process, so I seem to be stuck at the screenshot I uploaded.

No icon to click, no way to install anything as far as I can tell.

 

It seems as if something is missing, whether it´s the config file or some other command that makes the install disk/icon show up on the boot screen.

Share this post


Link to post
Share on other sites

Yes, my new build is the one in the signature :)

And yes, I cannot use my M.2 drive ATM (It´s in my BIOS so it´s working), so I´ll try to initialize the drive when I get to that.

 

Right now I simply can´t get to the install process, so I seem to be stuck at the screenshot I uploaded.

No icon to click, no way to install anything as far as I can tell.

 

It seems as if something is missing, whether it´s the config file or some other command that makes the install disk/icon show up on the boot screen.

 

 

Try,

 

1. Check AHCI is enabled in BIOS: 

 

post-1077361-0-23172100-1514393944_thumb.png

 

 

 

2. Insert a Hard Drive from your other machine into the new build Hackintosh and check if it's recognised when booting with the USB installer.

 

If no joy with steps 1 and 2 then,

 

3. Recreate High Sierra USB installer, use >> ESP Mounter Pro to mount the USB EFI partition.

4. Copy downloaded EFI and paste into the EFI partition on USB installer. 

post-1077361-0-23172100-1514393944_thumb.png

Share this post


Link to post
Share on other sites

Try,

 

1. Check AHCI is enabled in BIOS: CHECK. OK from the beginning.

 

2. Insert a Hard Drive from your other machine into the new build Hackintosh and check if it's recognised when booting with the USB installer. A bootable disk? Or just a storage unit? (Not sure anything but bootable disks will show up when booting, but I can try.)

 

If no joy with steps 1 and 2 then,

 

3. Recreate High Sierra USB installer, use >> ESP Mounter Pro to mount the USB EFI partition.

4. Copy downloaded EFI and paste into the EFI partition on USB installer. Will do regardless.

 

Thanks a bunch again for your help an patience :)

Really dont know what the issue is, but it´s highly frustrating that I cant access the installer.

 

Share this post


Link to post
Share on other sites

Thanks a bunch again for your help an patience :)

Really dont know what the issue is, but it´s highly frustrating that I cant access the installer.

 

 Try connecting a storage unit via sata cable.

Share this post


Link to post
Share on other sites

Right now I can even start my old Hackintosh. (Had to restart it trying to create a new USB with an unmentionable alternative)

Nothing happens. Just a black screen - so for now Ill have fun trying to rescue that. FML.

Share this post


Link to post
Share on other sites

Right now I can even start my old Hackintosh. (Had to restart it trying to create a new USB with ##### as alternative)

Nothing happens. Just a black screen - so for now Ill have fun trying to rescue that. FML.

 

:)

Share this post


Link to post
Share on other sites

Right now I can even start my old Hackintosh. (Had to restart it trying to create a new USB with an unmentionable alternative)

Nothing happens. Just a black screen - so for now Ill have fun trying to rescue that. FML.

 

I uploaded a YouTube 720p video on how to create USB installer and copy over the EFI folder.

 

 

Share this post


Link to post
Share on other sites

I uploaded a YouTube 720p video on how to create USB installer and copy over the EFI folder.

 

 

Thank you SO much for taking time to do this! 

Not sure it will help me, though. 

I think I accidentally updated Clover on my current/old Hackintosh, and that´s why I get a black screen after the Clover bootloader page.

 

This is the Clover installer log.

Can you make anything of it? And can you tell me how to roll back to the previous version?

As far as I can tell, Clover made a backup, so perhaps I can somehow copy the backup files back into the EFI folder?

 

Just want to ask someone who knows what they are doing, before I F it all up even more.

Thank you!

 

:::::::::::::::::::::::::

 
Clover EFI installer log - Wed Dec 27 15:44:52 CET 2017
Installer version: v2.4k r4359 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:         GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MUSIK GRAFIK & FOTOS    499.8 GB   disk0s2
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS EL CAPITAN HD           499.2 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS VIDEO & SFX             499.8 GB   disk2s2
/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS VIDEO PROJEKTER         499.8 GB   disk3s2
/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                  Apple_HFS ARBEJDE                 999.9 GB   disk4s2
/dev/disk5 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk5
   1:                        EFI EFI                     209.7 MB   disk5s1
   2:                  Apple_HFS ARKIV & MUSIKPROD       999.9 GB   disk5s2
/dev/disk6 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *16.1 GB    disk6
   1:                        EFI EFI                     209.7 MB   disk6s1
   2:                  Apple_HFS Install macOS High S... 15.7 GB    disk6s2
======================================================
Backing up EFI files
 
Backing up /Volumes/EL CAPITAN HD/EFIROOTDIR/EFI folder to /Volumes/EL CAPITAN HD/EFI-Backups/r3423/2017-12-27-15h44/EFI > These are the files from the hidden EFI drive, right?
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
 
Removing drivers64UEFI/VBoxHfs-64.efi driver because HFSPlus driver present > SIGNIFICANT?
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================

And FWIW: Here is a screenshot of the EFI backups on my El Capitan main drive.

Dont quite understand why there are changes to several folders yesterday. I thought each folder represented a Clover version, but perhaps it means something different.

post-1260652-0-75519200-1514475917_thumb.png

Share this post


Link to post
Share on other sites

Thank you SO much for taking time to do this! 

Not sure it will help me, though. 

I think I accidentally updated Clover on my current/old Hackintosh, and that´s why I get a black screen after the Clover bootloader page.

 

This is the Clover installer log.

Can you make anything of it? And can you tell me how to roll back to the previous version?

As far as I can tell, Clover made a backup, so perhaps I can somehow copy the backup files back into the EFI folder?

 

Just want to ask someone who knows what they are doing, before I F it all up even more.

Thank you!

 

:::::::::::::::::::::::::

 
Clover EFI installer log - Wed Dec 27 15:44:52 CET 2017
Installer version: v2.4k r4359 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:         GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MUSIK GRAFIK & FOTOS    499.8 GB   disk0s2
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS EL CAPITAN HD           499.2 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS VIDEO & SFX             499.8 GB   disk2s2
/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS VIDEO PROJEKTER         499.8 GB   disk3s2
/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                  Apple_HFS ARBEJDE                 999.9 GB   disk4s2
/dev/disk5 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk5
   1:                        EFI EFI                     209.7 MB   disk5s1
   2:                  Apple_HFS ARKIV & MUSIKPROD       999.9 GB   disk5s2
/dev/disk6 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *16.1 GB    disk6
   1:                        EFI EFI                     209.7 MB   disk6s1
   2:                  Apple_HFS Install macOS High S... 15.7 GB    disk6s2
======================================================
Backing up EFI files
 
Backing up /Volumes/EL CAPITAN HD/EFIROOTDIR/EFI folder to /Volumes/EL CAPITAN HD/EFI-Backups/r3423/2017-12-27-15h44/EFI > These are the files from the hidden EFI drive, right?
======================================================
Installing BootSectors/BootLoader
 
Stage 0 - Don't write any of boot0af, boot0md, boot0ss to /
Stage 1 - Don't write any of boot1h2, boot1f32alt, boot1xalt to /
 
Removing drivers64UEFI/VBoxHfs-64.efi driver because HFSPlus driver present > SIGNIFICANT?
 
======================================================
=========== Clover EFI Installation Finish ===========
======================================================

And FWIW: Here is a screenshot of the EFI backups on my El Capitan main drive.

Dont quite understand why there are changes to several folders yesterday. I thought each folder represented a Clover version, but perhaps it means something different.

 

 

If the most recent version of Clover r4359 caused problem with your Hackintosh install, then you could roll back to Clover r4003. You would just drag and drop the Clover r4003 EFI folder into your system EFI partition,  thats the EFI partition on the disc that you have Mac OS installed on.

Share this post


Link to post
Share on other sites

If the most recent version of Clover r4359 caused problem with your Hackintosh install, then you could roll back to Clover r4003. You would just drag and drop the Clover r4003 EFI folder into your system EFI partition,  thats the EFI partition on the disc that you have Mac OS installed on.

Cool. Just to be sure:

I don´t make ANY changes to the HIDDEN EFI partition?

I simply replace the current EFI folder on my EL Capitan drive (El Capitan HD > EFI ) with the EFI folder from the backup:

El Capitan HD > EFI-Backups > R4003 > and then which folder? "2017-02-16-22h57" or "2017-12-27-15h38" including the boot-file?

 

I´m thinking the folder created yesterday would also contain updated (and problematic) files - but perhaps it´s simply a timestamp for when the files was backed up?

Share this post


Link to post
Share on other sites

Cool. Just to be sure:

I don´t make ANY changes to the HIDDEN EFI partition?

I simply replace the current EFI folder on my EL Capitan drive (El Capitan HD > EFI ) with the EFI folder from the backup:

El Capitan HD > EFI-Backups > R4003 > and then which folder? "2017-02-16-22h57" or "2017-12-27-15h38" including the boot-file?

 

Yes, replace current EFI folder with backup "2017-02-16-22h57".

Share this post


Link to post
Share on other sites

OK, I replaced the EFI folder on the EL Capitan HD drive (not the hidden EFI partition).
Nothing changed. Still a black screen.

Tried diff boot options, including non-Nvidia, boot w/ Nvidia web drivers, safe mode, verbose etc. Nothing.

 

Im guessing I need to replace the EFI on the HIDDEN EFI partition with the backup...or?
(FYI: The current EFI folder on the hidden partition doesnt seem to have been updated yesterday.)

Share this post


Link to post
Share on other sites

Why do you have an EFI folder on your hard drive's OS partition?  You should only have the EFI folder on the EFI hidden partition; I suggest you remove everything else elsewhere so you just have ONE EFI folder on ONE hidden EFI partition.  

 

Focus on fixing that. 

Share this post


Link to post
Share on other sites

OK, I replaced the EFI folder on the EL Capitan HD drive (not the hidden EFI partition).

Nothing changed. Still a black screen.

 

Tried diff boot options, including non-Nvidia, boot w/ Nvidia web drivers, safe mode, verbose etc. Nothing.

 

Im guessing I need to replace the EFI on the HIDDEN EFI partition with the backup...or?

(FYI: The current EFI folder on the hidden partition doesnt seem to have been updated yesterday.)

 

As per bluesceens above, it's better to remove / disconnect those storage discs from your Hackintosh machine and keep only one drive connected, and thats the system drive that you intend to restore or reinstall macOS.  Once you can successfully boot to OS X desktop, then reattach the storage discs. 

 

My approach on this would be:

 

1 - Remove the system drive that has OS X installed from your computer.

2 - Keep the Storage Drive attached to your computer.

3 - Download GParted.

4-  Boot from GParted and carefully delete the EFI partitions form your storage drives.

5 - Then, remove storage drives from computer.

6 - Connect your OS X drive

7 - Troubleshoot and get OS X working.

8 - Then add your storage drives back.

Share this post


Link to post
Share on other sites

Why do you have an EFI folder on your hard drive's OS partition?  You should only have the EFI folder on the EFI hidden partition; I suggest you remove everything else elsewhere so you just have ONE EFI folder on ONE hidden EFI partition.  

 

Focus on fixing that. 

Hey @Bluescreens,

I honestly have no idea. I didn´t put it there, so I figured it was part of the Clover install. :worried_anim: 

Maybe it was installed when I upgraded to El Capitan back in February. No clue.

 

I´ll try removing the whole EFI folder from "El Capitan HD", keep everything on the (hidden) EFI partition, and see if that helps. 

If not, I´ll try the suggestions from @Glasgood.

 

PS: Any idea if I should also delete the "boot" and "nvram.plist" files from my "El Capitan HD" drive/folder?

 

 

Thanks again, gentlemen! I´m really happy to have someone smarter than me helping me out  :thumbsup_anim: 

 

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 cvad
      Small tool to download, compile and build the latest Clover X64 package,
      possible include HFSPlus-64.efi.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
      Clover_Builder.app.v1.2.0.zip
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione
      nel caso guardate...
       Mojave in HFS 
       
       
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      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    Oracle VM VirtualBox v 5.0.34    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#75    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.  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.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  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.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      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 named my 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.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      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.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      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...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By fantomas1
      -----------------------------
      Mise à jour 12/07/2018
      -----------------------------
       
      La sortie de macOS 10.14 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       

       
      -----------------------------
      Mise à jour 09/06/2017
       
      -----------------------------
       
      La sortie de macOS 10.13 Beta m'oblige à mettre ce topic à jour. Plus de détails dans ce post.
       

       
       
       
      -----------------------------
      Mise à jour 15/06/2016
      -----------------------------
       
      Une petite mise à jour du topic pour confirmer le bon fonctionnement du patch à la volé de Clover (r3561) avec macOS Sierra.
       

       
       
       
      -----------------------------
      Mise à jour 24/08/2015
      -----------------------------
       
      ok, très bien,
       
      comme pour la HD6770, la nouvelle méthode du patch à la volé est de nouveau fonctionnel et avec les dernières versions de Clover.
       
      pour ma part, je suis sur El Capitan DB7 et Clover r3259
       

       
       
      par contre, je suis toujours obligé de m’aider de l’astuce avec FakeSMC pour que mes kexts soient toujours chargés, mais au moins cela marche.   
       
       
       
       
      et pour config.plist, cela donne ça :
       

       
       
      ceci est juste un exemple avec ma HD4830, il va de soi que vous devez mettre Device-ID de votre carte graphique !!!
       
       
       
       
       
      Salut à tou(te)s
       
      Comme certain(e)s le savent, les cartes graphiques dites "Exotiques" ne sont pas supportés par le système d'exploitation d'Apple.
      En sus d'ajouter l'identifient de la carte graphique (Device ID) dans l'Info.plist du ou des kexts concernés, il faut aussi interagir sur la partie "binaire" du kext par le biais du "patching".
       
      Dans notre cas, les cartes graphiques exotiques sont les cartes AMD (anciennement ATI) de la série HD 48xx, et plus précisément les HD 4830, HD4850, HD4870x2 et HD4890.*
       
      Donc le but est de faire fonctionner ces cartes graphiques de manière stable et fluide en activant QE_CI, chose nécessaire pour en profiter pleinement du système d'exploitation.
       
      * Juste avant de commencer, vous l'avez peut-être remarqué, la HD4870 n'est pas sur la liste suscitée et pour cause c'est que cette carte graphique est nativement supportée par le système d'exploitation d'Apple. Son Device ID est 0x94401002 que vous pouvez trouvé dans l'Info.plist des kexts concernés et c'est celui-ci que nous allons utiliser afin de le remplacer par le Device ID de notre carte graphique.
       
      ** Ce tuto est fait pour fonctionner sous OS X Mavericks, mais il doit fonctionner aussi avec les autres. La seule chose différente c'est l'adresse binaire à patcher.    
       
       
      Très bien, comme le titre le suggère, nous allons voir comment faire reconnaître ces cartes graphiques sous Clover et obtenir par la même un QE_CI activé et parfaitement fonctionnelle.
       
      Je vais utiliser ma Sapphire HD4830 512 MB GDDR3 PCI-E (comme cobaye    ) pour ce test et qui a pour Device ID 0x944c1002.
       
      Pour que ce test réussisse, nous allons donc utiliser ces 2 kexts, à savoir AMD4800Controller.kext (pour la partie QE) et ATIRadeonX2000.kext (pour la partie CI) et allons ajouter notre Device ID dans l'Info.plist. via le tweak "KernelAndKextPatches"
       
      Donc les valeurs à entrer dans notre config.plist sont celle-ci :
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>     </array> Comme vous pouvez le voir, la clé "InfoPlistPatch" sert à injecter notre Device ID "uniquement" dans Info.plist, sans y toucher à la partie "binaire" de nos kexts. La clé "Find" a pour fonction de trouver le Device ID que l'on veut remplacer par le notre en utilisant la clé "Replace".
       
      Très bien, maintenant comme nous l'avons dit au début de ce tutoriel, ajouter notre Device ID n'est pas suffisant pour faire fonctionner pleinement notre carte graphique, il faut encore interagir sur la partie "binaire" de nos kexts. Dans notre cas, il va falloir agir uniquement sur un kext, çàd sur ATIRadeonX2000.kext et plus particulièrement sur ATIRadeonX2000.kext/Contents/MacOS/ATIRadeonX2000
       
      Et pour cela, nous allons faire comme ceci :
      <key>KextsToPatch</key> <array> <dict>     <key>Name</key>     <string>ATIRadeonX2000</string>     <key>Find</key>     <data>0F8394010000</data>     <key>Replace</key>     <data>909090909090</data> </dict> </array> Là nous pouvons voir que la clé "InfoPlistPatch" n'est pas utilisée et donc ces valeurs n'auront aucun effet sur l'Info.plist mais agiront uniquement au niveau de la partie "binaire". 
       
      Et voici les valeurs en leur forme complète que vous devrez ajouter dans votre config.plist
      <key>KernelAndKextPatches</key>     <array>         <dict>             <key>Name</key>             <string>AMD4800Controller</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>InfoPlistPatch</key>             <string>Yes</string>             <key>Find</key>             <string>0x94401002</string>             <key>Replace</key>             <string>0x944C1002</string>         </dict>         <dict>             <key>Name</key>             <string>ATIRadeonX2000</string>             <key>Find</key>             <data>0F8394010000</data>             <key>Replace</key>             <data>909090909090</data>        </dict>     </array> Très bien, maintenant il ne nous reste plus qu'à autoriser l'injection des kexts, sans quoi le patch ne fonctionnera pas. Et nous allons le faire via le tweak "InjectKexts" comme ceci :
      <key>SystemParameters</key> --> clé principale <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key> --> sous clé       <string>Yes</string> </dict>  
       
      Si certain(e)s d'entre vous préfèrent utiliser le logiciel "Clover Configurator" pour plus de facilité, voici comment entrer ces valeurs :
       
      Allez sur l'onglet "Kernel And Kext Patches" et faites comme ceci :
       
       
       
      *Ne faites pas attention sur le majuscule/minuscule, cela ne fait aucune différence
       
       
      Et pour injecter les kexts, aller sur l'onglet "System Parameters" et mettez l'option Inject Kexts sur Yes comme ceci :
       

       
       
      Voilà, vous n'avez plus qu'à enregistrer les ajustements, redémarrer votre pc et apprécier le résultat.
       
       
      MAIS ... seulement voilà ... il y a un problème ... 
       
      Quoi ? 
       
      Initialement, les kexts ne sont pas présents dans le kernelcache à cause de "OSBundleRequired=Safe Boot" (ils ne sont pas chargés en local par défaut mais en mode sans échec) et donc le patchage "à la volé" (on the fly) ne fonctionnera pas.
       
      Donc quoi, tout ça pour rien ?
       
      Non, bien-sûr, voici l'astuce pour remédier à cela :
       
      Dans un premier temps, il vous faut booter l'OS sans kernelcache. Si vous utiliser Clover Configurator, il vous suffit juste de cocher l'option "No Caches" dans l'onglet "System and Parameters" ou bien vous le faites directement dans votre config.plist :
      <key>SystemParameters</key> <dict>       <key>InjectSystemID</key>       <true/>       <key>InjectKexts</key>       <string>Yes</string>       <key>NoCaches</key>       <true/> </dict> Ceci aura donc pour effet de bloquer kernelcache et obliger boot.efi de charger le kernel et les kexts séparément. Clover et FSInject vont ensuite intercepter tous les chargements des kexts par boot.efi et changer "OSBundleRequired=Safe Boot" en "OSBundleRequired=Root" à la volé (on the fly) et forceront boot .efi à charger les kexts. Et ensuite dans un second temps, Clover va patcher l'Info.plist de ces deux kexts et la partie binaire de ATIRadeonX2000, kernel va les charger et ils seront rattachés à votre carte graphique.
       
      Une fois ceci fait (donc les kexts utilisés), il vous suffit de faire sudo touch /System/Library/Extensions. Ceci créera un nouveau kernelcache qui cette fois-ci contiendra vos kexts utilisés. Ensuite il ne vous reste plus qu'à redémarrer normalement (en décochant l'option No Caches dans Clover Configurator) et le patch fonctionnera à merveille.
       
       
      Oui, mais ... là aussi ...
       
      Quoi encore ?
       
      Seulement voilà, pour une raison ou une autre, il peut arriver que kernelcache se reconstruit tout seul et le patch "à la volé" ne fonctionne plus.
       
      Alors je fais quoi moi en attendant ?
       
      L'astuce la plus efficace pour le moment est d'injecter les infos de vos kexts à l'intérieur de l'Info.plist de FakeSMC.kext comme des IOKitPersonalities additionnels.
       
      ????Kézako????
       
      Ces infos vous les trouverez dans l'Info.plist de ces 2 kexts, sous IOKitPersonalities. Les voici :
       
      Pour AMD4800Controller.kext
      <key>Controller</key> <dict>         <key>ATY,Cardinal</key>         <dict>                 <key>aty_config</key>                 <dict>                         <key>CFG_NO_PP</key>                         <true/>                 </dict>          </dict>          <key>CFBundleIdentifier</key>          <string>com.apple.kext.AMD4800Controller</string>          <key>IOClass</key>          <string>AMD4800Controller</string>          <key>IOMatchCategory</key>          <string>IOFramebuffer</string>          <key>IOName</key>          <string>AMD4800Controller</string>          <key>IOPCIMatch</key>          <string>0x94401002 0x944a1002</string>          <key>IOProbeScore</key>          <integer>65050</integer>          <key>IOProviderClass</key>          <string>IOPCIDevice</string>         <key>aty_config</key>          <dict>                 <key>CFG_NO_PP</key>                  <false/>                  <key>CFG_PAA</key>                  <integer>0</integer>                  <key>CFG_USE_USCN</key>                  <false/>          </dict>          <key>aty_properties</key>          <dict>                  <key>PP_GFXClockGatingEnabled</key>                  <integer>1</integer>          </dict> </dict> Et pour ATIRadeonX2000.kext
      <key>ATIRadeonX2000</key> <dict>         <key>ATIEnableWideBlitSupport</key>         <true/> <key>ATIUseTearingWideBlit</key> <false/> <key>CFBundleIdentifier</key> <string>com.apple.ATIRadeonX2000</string> <key>GpuDebugPolicy</key> <integer>0</integer> <key>IOCFPlugInTypes</key> <dict> <key>ACCF0000-0000-0000-0000-000a2789904e</key> <string>ATIRadeonX2000GA.plugin</string> </dict> <key>IOClass</key> <string>ATIRadeonX2000</string> <key>IODVDBundleName</key> <string>ATIRadeonX2000VADriver</string> <key>IOKitDebug</key> <integer>0</integer> <key>IOMatchCategory</key> <string>IOAccelerator</string> <key>IOPCIMatch</key> <string>0x94001002 0x94011002 0x94021002 0x94031002 0x95811002 0x95831002 0x95881002 0x94c81002 0x94c91002 0x95001002 0x95011002 0x95051002 0x95071002 0x95041002 0x95061002 0x95981002 0x94881002 0x95991002 0x95911002 0x95931002 0x94401002 0x94421002 0x944A1002 0x945A1002 0x94901002 0x949E1002 0x94801002 0x95401002 0x95411002 0x954E1002 0x954F1002 0x95521002 0x95531002 0x94a01002</string> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>IOSourceVersion</key> <string>8.24.11</string> <key>IOVARendererID</key> <integer>16908288</integer> <key>sensor-properties</key> <array> <dict> <key>device_type</key> <data> Z3B1LXNlbnNvcg== </data> <key>location</key> <string>GPU</string> <key>name</key> <string>gpu-sensor</string> <key>polling-period</key> <data> AAAAAQAAAAA= </data> <key>reg</key> <data> AAAAAg== </data> <key>sample-period</key> <data> AAAAAACYmAA= </data> <key>sensor-id</key> <data> AAAABg== </data> <key>version</key> <data> AAAAAg== </data> <key>zone</key> <data> AAAAAg== </data> </dict> </array </dict>  
      Et voici donc l'Info.plist de FakeSMC.kext dans son intégrité, vous pouvez jeter un oeil, histoire de voir à quoi cela ressemble :
       
      FakeSMC_Info.plist.zip
       
      Et pour les moins casse-têtes, voici FakeSMC.kext modifié que j'utilise pour charger les 2 kexts :
       
      FakeSMC.kext.zip
       
       
      Voilà, avec ceci, vous n'aurez plus besoin de savoir si oui ou non les kexts sont dans le kernelcache.
       
       
      Crédits attribués à :
       
      netkas  pour son incontournable QE_CI Exotic patch (même s'il n'importe plus son support)
       
      Slice  & co. pour leur bébé nommé Clover
       
      dmazar  pour son astuce avec FakeSMC.kext   (pour plus d'info, voir ici)
       
      duffs (rarement ici, plus sur le site de netkas) pour son astuce de comment patcher la partie binaire avec Clover, ce fût lors de la sortie de OS X Mavericks DP1
       
      nyolc8  pour le support de QE_CI Exotic patch pour Mavericks
       
      fantomas1  pour ......... pour ... quoi déjà ? Ah ben non ... non ... pour rien ...
    • By Slice
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
       
×