Contribute
Register

Using Unibeast to create a Clover Installer:

Status
Not open for further replies.
Joined
May 12, 2011
Messages
2,581
Motherboard
GA-X99M-Gaming 5
CPU
i7-5930K
Graphics
GTX 970
Mac
  1. MacBook Pro
Classic Mac
  1. Color Classic
Mobile Phone
  1. Android
Tonymacx86 members are familiar with and rely on the great tools provided here to get their Hack’s up and running. Some have become curious and asked for advice on how to test Clover. The safest and easiest way to test is to install Clover on a fat32 formatted USB partition. This allows you to boot and test Clover with different configurations while leaving you current install intact. If you decide you like what you see, you may decide to take advantage of Clover features like UEFI booting, selected kext injection, Recovery Partition and screaming boot times. To do this we need to create a Clover UEFI Installer, we can do this using the tools you’re already familiar with. Remember that this site supports their tools and this post is not offered as a sanctioned/approved Tonymacx86 process.

Let’s build a Unibeast/Clover Installer… I'm assuming we're building a Mavericks installer so follow the instructions here to create a Unibeast USB. The only thing we’re going to do different is format the USB as GUID instead of MBR.

partition.png

Once the build process is complete we need to install Clover to the Unibeast USB.

Download the latest version of Clover here. Then install it with these settings:

Screen Shot 2013-10-30 at 3.27.37 AM.png

When the Clover install completes you'll see a mounted partition on the desktop called EFI. In that partition you'll find a folder called EFI, open it and it will look like this:

efi folder.png

We need to add a few kexts to get our installer running. Navigate to EFI/Clover/kexts and copy FakeSMC and your ethernet kexts to the 10.9 folder.

kexts3.png

Now we're ready to install Mavericks. Boot the box and choose UEFI:USB as your boot device. Use arrow keys the highlight OSX Installer, press space bar and choose "With Kexts", press enter to start installation. On the second boot, again choose UEFI:USB, navigate to the drive you installed OS X to and hit spacebar and choose "WithKexts" and complete install.

Now run Multibeast and install FakeSMC and your audio and ethernet kexts.

Install Clover to HD with same settings as above. No need to move any kexts to Clover as MB has already installed them to S/L/E.

Reboot to UEFI: "Your HD" and you should be go to go...

Luck with it.

EDITED and TESTED! 10/30

Tip: Copy the tools you may need to the Installer before doing the Install so they're available to you after the final install phase completes.

tip.png
 
As written, this isn't working properly for me.

for clarification, you may want to label the kext directory and taken from efi/clover. It shows a kext in the root of clover of AppleIntelE1000e,kext, which doesn't work for me in either folder as well if put in 10.9 like some other guides state. FakeSMC wsorks fine though or it will give me the bluetooth error if I don't include it.

Does the kext need to be installed somehow? or just copy and paste from a working 10.9 HDD that was installed with unibeast/multibeast I have?

When I finish and try to boot, the HDD doesn't come up UEFI device, only legacy.

Don't I need to also install clover onto the HDD as well?

I ran multibeast anyway with no results.

Also, when I ran multibeast I didn't use the DSDT free or easy beast so it never installed a bootloader. It didn't say to run anything but FakeSMC, Internet, and Sound.

At first I thought it was working as I had my usb still pluggged in, but after all was done, I removed all drives and usb and it drops back to BIOS. I think it was just dropping to USB before and gave me the clover menu instead of dropping to bios.

EDIT:
I just reboted and it went to the installer menu for some reason. Not sure what happened. anyway, rebooted and reinstalled and now I'm trying to get ethernet up.

I find a command to manually load kexts and I move AppleIntelE1000e.kext to my home folder as that's where terminal puts me. I then type in:
Code:
sudo kextload AppleIntelE1000e.kext

and I get error:
/Users/mark/AppleIntelE1000e.kext failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(8).

not sure where the logs are and too late to find now. maybe tomorrow.
 
I'll rework this shortly...
 
As written, this isn't working properly for me.

for clarification, you may want to label the kext directory and taken from efi/clover. It shows a kext in the root of clover of AppleIntelE1000e,kext, which doesn't work for me in either folder as well if put in 10.9 like some other guides state. FakeSMC wsorks fine though or it will give me the bluetooth error if I don't include it.

Does the kext need to be installed somehow? or just copy and paste from a working 10.9 HDD that was installed with unibeast/multibeast I have?

When I finish and try to boot, the HDD doesn't come up UEFI device, only legacy.

Don't I need to also install clover onto the HDD as well?

I ran multibeast anyway with no results.

Also, when I ran multibeast I didn't use the DSDT free or easy beast so it never installed a bootloader. It didn't say to run anything but FakeSMC, Internet, and Sound.

At first I thought it was working as I had my usb still pluggged in, but after all was done, I removed all drives and usb and it drops back to BIOS. I think it was just dropping to USB before and gave me the clover menu instead of dropping to bios.

EDIT:
I just reboted and it went to the installer menu for some reason. Not sure what happened. anyway, rebooted and reinstalled and now I'm trying to get ethernet up.

I find a command to manually load kexts and I move AppleIntelE1000e.kext to my home folder as that's where terminal puts me. I then type in:
Code:
sudo kextload AppleIntelE1000e.kext

and I get error:


not sure where the logs are and too late to find now. maybe tomorrow.

Updated!
 
Here's the FakeSMC database at sourceforge:
http://sourceforge.net/projects/hwsensors/files/

I think maybe your system is choking on the memory. Do you have non-ECC memory you can try, maybe even 1600Mhz?

As far as I know, i7 and i5 don't support ECC, I've only heard of i3 supporting ECC.

Maybe Asus has allowed this option, but OS X may think this is in error, as Intel doesn't allow this, and causes the install to abort.

It might be worth a try if you can borrow memory from another machine or friend.

Also, are you following this thread 100%? I find mixing threads to never work properly. Unibeast is already ready to go, and the other thread, I think, is for real Macs only. So it may do something different. I tried that method first and it failed for me. When I came back the next day to try again, I found this thread and it worked for me.
 
Thanks dude, do you have a link to that version of FakeSMC?

below is a series of images taken from within Clover Options menus. Notice un SMBIOS menu if recognises the Gryphon board an and identifies it as an iMac 14,2 which is think is the most accurate.

No matter what I've tried (3 days now) i'm still getting a boot kernel panic AppleACPIPlatformExpert. Basically the logic board driver. Maybe you can post a system log with listings of your last successful boot on the Gryphon? I'm not sure exactly what the problem is. My Gryphon board is revision 1.03. BIOS version 1504. I'm using 3x1GB sticks of ECC 1066Mhz RAM from my Mac Pro. I thought my Mavericks Install App is suspect, very strange things going on, like no mach_kernel inside the 'BaseSystem.dmg' and one isn't created when restoring it to the USB 3.0 disk. Now I can't get the EFI partition to mount at all with Disk Utility.


View attachment 71830View attachment 71832View attachment 71833View attachment 71834View attachment 71835View attachment 71836View attachment 71837View attachment 71838View attachment 71839View attachment 71831
first of all for instalation of mavericks u cannot use vboxhfs driver becouse it dont support hardlinks soo u need hfsplus.efi
some explanation on projectosx
http://www.projectosx.com/forum/index.php?s=&showtopic=2562&view=findpost&p=35896

Second problem its that u have too many dsdt fixes for this board turn off all of them and try.
 
xpamamadeus: I've seen that post yet I have done many clean Mav installs in the past few days and numerous installs using the default vboxhfs driver without issue. I'm not a dev or coder and can't debate the info in that post, but I can say my experiences question the validity of the "you can't install Mav with vboxhfs" statement. Certainly anyone having install problems could try using hfsplus.efi in and effort to resolve them...

Regards
 
xpamamadeus: I've seen that post yet I have done many clean Mav installs in the past few days and numerous installs using the default vboxhfs driver without issue. I'm not a dev or coder and can't debate the info in that post, but I can say my experiences question the validity of the "you can't install Mav with vboxhfs" statement. Certainly anyone having install problems could try using hfsplus.efi in and effort to resolve them...

Regards
I wass not clear when i say this.
U can install it only if u are using EFI clover(that dont use drivers64 folder) but vbox driver cannot install GM when u create usb using apple method to create usb installer.
I dont know how Unibeast work becouse i never used it,but anything that are not vanilla install without modifing original untouched MAS app are frankenstein app to me.

Other things that i see are making problems like no installed theme and people using sample config.plist that come from installer becouse sample one have too many DSDT fixes that break OSX from start.
Best thing its to have DSDT fixes and P and C states generate to fals for begining.

We will need new guide to make Clover USB Installer more easy for people that use it first time.
Maybe i even make new installer with more "Universal" settings to make things easy without many user intervention.
 
I only put this post together to make it easy to create a UEFI Clover installer using the tools people here are already familiar with. Notice nothing here helps people wanting to run legacy. I agree a new process is desirable. I've never understood why some Clover install annoyances continue to exist like default config.plist calling the metal theme but not installing it. I'm not clear if anyone but Slice can create a more universal default config.plist.

We will need new guide to make Clover USB Installer more easy for people that use it first time.
Maybe i even make new installer with more "Universal" settings to make things easy without many user intervention.
I up for this and will help/test as necessary.
 
I'm not clear if anyone but Slice can create a more universal default config.plist.
ofcourse we always can make more universal config.plist.
I my opinion Slice has bigger things in mind for clover than making more universal config.plist.
 
Status
Not open for further replies.
Back
Top