Jump to content
InsanelyMac Forum
IIIdefconIII

Beginners guide to UEFI Triple/Dual boot OS X, Windows and Linux (Kali) on an single true-gpt ssd

Recommended Posts

 

Copyright © ctugt 2013 - end of time

 

:welcomeani:

 

If you applying this guide to a Acer S3-391 start at post #2. For other systems start at post #3.

 

This guide should work on OS X Mavericks, (im not sure about Mountain Lion), Windows 7 / 8 / 8.1 and Linux Distros with EFI support

Attention:

Before executing anything READ the full posts first! This will prevent any unnecessarily mistakes and questions.

Disconnect all other ssd/hdd/usb drives, just to be sure you don't mess it up! Keep it disconnected until you're done with everything!

 

 

Good Luck :thumbsup_anim:

 

Index

Usefull Guides

Requirements/Downloads

:star_smile:This wasn't possible for me without the following people :star_smile:

:star_smile:Thanks to Joseph51423, panpansh, iPoco, for helping me understand clover :star_smile:

:star_smile: Thanks to Download-Fritz for other support :star_smile:

:star_smile: Thanks to Enzo for letting me patch his original Chameleon's theme to a clover version :star_smile:

:star_smile:Special thanks to thevoiceover and pokenguyen :star_smile:

:star_smile:The most gratitude to EMlyDinEsH (Elan driver creator and DSDT specialist) :star_smile:

 

Thats awesome, OS X boots instantly!

But I cant figure out how to migrate to clover bootloader from chameleon. Heres why:

 

I installed clover to usb with boot0af and CLOVER EFI 64-bits SATA, that works for me and i can boot from usb with these settings. But when i tried to install clover to main hard drive with mavericks i got boot1: error. I installed for UEFI and the EFI was mounted, then i copied over the config.plist from the USB. What am I doing wrong? Ive read many posts but seems like you know what you are doing so better ask you... :)

Thank you

Share this post


Link to post
Share on other sites
Advertisement

Thats awesome, OS X boots instantly!

But I cant figure out how to migrate to clover bootloader from chameleon. Heres why:

 

I installed clover to usb with boot0af and CLOVER EFI 64-bits SATA, that works for me and i can boot from usb with these settings. But when i tried to install clover to main hard drive with mavericks i got boot1: error. I installed for UEFI and the EFI was mounted, then i copied over the config.plist from the USB. What am I doing wrong? Ive read many posts but seems like you know what you are doing so better ask you... :)

Thank you

this has somehting to do with youre hdd, you need custom patch for 1024 bootsector. There is alot info on insanely about it, good luck

Share this post


Link to post
Share on other sites

boot very fast!!

 

man, what theme are using?

Read the first ost, the them is posted in there

Share this post


Link to post
Share on other sites

ok, i downloaded

 

but everything blue.  :(

you need to read, the information is there somewhere, you have to edit the config.plist in youre /efi/clover/config.plist, and set the default theme to the theme name, just read its somewhere in my guide im sure

 

EDIT: its in the Installing Mac OS X Mavericks in EUFI mode post

Share this post


Link to post
Share on other sites

Hi, in my Samsung NP530U3B this tutorial partially worked. It helped me A LOT anyway.

The problem here was that I couldn't boot to another device after installing Windows. I had tone tee in Windows settings and look for advanced boot and select the device to start. It's just as if Windows became the owner of my BIOS, I can't press any button anymore during BIOS screen...

After selecting the USB, I can reach Clover's boot screen but Mac fails to boot. The same occurred when I selected the Clover installed on the HD. Maybe it is something related to my Phoenix BIOS.

So I could fix it by booting a live Linux and changing the files according to the tutorial, it worked flawlessly. :)

Share this post


Link to post
Share on other sites

My BIOS/UEFI does kind of the same thing. It shows the original boot logo with additional text (the screen where it prompts you for input to go to BIOS settings or choose boot device) for a very short time, then it flashes and shows ONLY the boot logo (without any additional text) and a Windows 8-like loading spinner.

 

You have to press F12 (or whatever key your motherboard uses for BIOS/UEFI settings) before this second screen shows (the one with the spinner).

Share this post


Link to post
Share on other sites

 

Hi:

I followed your excellent guide for a desktop.

Unfortunately Kali does not appear when I start the computer.

I send my config.plist.

 

https://www.mediafire.com/?ys75nhafd2ds543

 

Would you please tell me what I’m doing wrong?

 

Thanks in advance.

 

 

try this file i uploaded for you http://www.filedropper.com/config_9 and post results

Share this post


Link to post
Share on other sites

Hi ctugt:


 


It worked perfectly well! Thank you very much.


 


Two more things: 


                             Is it possible to hide Boot UEFI Internal from EFI ?


                             In Seven, two of the three Kali partitions are seen, is this normal?


 


Thanks in advance.


post-201840-0-96566600-1390333825_thumb.jpg

post-201840-0-23183700-1390333873_thumb.jpg

Share this post


Link to post
Share on other sites

I think the way to hide them in Seven is to give the drives no Drive Letter using a partition manager. This way Seven will not see them.

 

Perfect!!!

Thank you very much

post-201840-0-66665700-1390345804_thumb.jpg

Share this post


Link to post
Share on other sites

Hi frankiee, ctugt,

 

I'm sorry to dig out this old stuff, but I'm really interested in the 'total-noob' tutorial you're talking about here:

 

PS: doing a dual UEFI bootstick goes like this:

 

1) Partition as MBR, partition 1 is Win (FAT), partition 2 is OS X Install (HFS+). Also created a 3rd one for drivers and support files.

2) Create win installer on partition 1

3) Create OS X installer on partition 2

4) Install clover on partition 1

5) Add appropriate boot entries to the respective bootloader .efi files

 

So the basic trick is to use the first partition as EFI _and_ win8 install partition. If you try to do it via GPT, you can copy the win bootloaders to the EFI partition, but it looses the connection to the actual installation files then and complains. You should also be able to solve this by editing the BCD, but imho this way is just a bit simpler.

 

I'm trying to create a USB stick containing Mavericks, Win8 and Ubuntu installers (all to be installed on a standard-BIOS non-UEFI system) and would love to use Clover to choose which installer I actually want to launch - Clover will of course also be used to actually boot the different OSs after installation from my HDD.

 

I have formatted my 32GB USB as MBR with 4 x 8 GB partitions

As per your instructions:

  • I copied Windows files into my first partition
  • typed; "sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Clover --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --no interaction" to copy my Mavericks Install.app in the 2nd partition that I had called Clover
  • copied the Ubuntu files into my 3rd partition
  • prepared a 4th partition for the basic software to be installed on the different OSes

I've actually been following this guide in parallel to yours to achieve my project - and obviously cannot find the EFI partition as my USB stick has MBR and not GPT

When I try to install Clover into the Win partition as per your above guide, I get an installation failure message...

 

I'm not familiar at all with boot in general.

 

Can someone help?

Share this post


Link to post
Share on other sites

I've actually been following this guide in parallel to yours to achieve my project - and obviously cannot find the EFI partition as my USB stick has MBR and not GPT

When I try to install Clover into the Win partition as per your above guide, I get an installation failure message...

 

I'm not familiar at all with boot in general.

 

Can someone help?

Here is my guide for creating a multiboot Windows/Linux/OSX USB installer with Clover -updated 03/02/15.  This guide is tailored for non UEFI machines and requires a 16GB or larger USB stick.  For this guide, I have used Windows 7 X64, Linux Mint 17.1 and OSX Mavericks but you can also apply the same procedure to create a multiboot Windows 8 X64/Ubuntu 14.04/OSX Yosemite installer.

 

1.    In Disk Utility, click on the partition tab....

 

post-846696-0-37387500-1425944134_thumb.

       a. Choose 4 Partition Layout with a 200MB FAT32 partition for CLOVER, 5GB FAT32 for WIN, 3GB FAT32 for LINUX, 8GB HFS+ for OSX (if using a 16GB or larger USB).

 

       b. Unmount, then format the 200MB CLOVER partition to FAT32 using terminal:

diskutil list
diskutil unmount /dev/diskXs1 (where X=disk number of USB)
sudo newfs_msdos -v CLOVER -F 32 /dev/rdiskXs1

       c. Under “Options”, choose MBR format

 

 

2.  Copy the Windows and Linux install files (from Install DVD or downloaded iso) into the respective FAT32 partitions.  Note in the files from the Linux Mint iso, there is a hidden folder named ".disk" that needs to be copied across, so I enabled "show all files" in Finder.

 

       a. Enable showing of hidden files in Finder by typing in terminal

defaults write com.apple.finder AppleShowAllFiles -boolean true ; killall Finder

       b. For Windows, make sure bootmgfw.efi is copied to /efi/Microsoft/boot and rename cdboot.efi to cdboot.bak.  You should also have a bootx64.efi file in the /efi/boot folder (actually bootx64.efi is just the renamed microsoft efi bootloader bootmgfw.efi). 

 

NB If your Windows install.wim is larger than 4GB, you will have to split the file using dism before you can transfer over to the FAT32 formatted WIN partition of your USB - procedure outlined here by nick@number11.

post-846696-0-16700500-1426025785_thumb.

       c. For Linux, make sure to create a folder inside the /efi folder for the bootloader eg “ubuntu” or “linuxmint” and copy grubx64.efi into it.

post-846696-0-55131600-1426025831_thumb.

 

 

 

3.  For the OSX partition, use the createinstallmedia method (ensure OS X installer app is in /Applications folder).

            a. Mavericks

sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/OSX --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --no interaction

            b. Yosemite

sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/OSX --applicationpath /Applications/Install\ OS\ X\ Yosemite.app

4.  Install Clover targeting the “CLOVER” partition.

 

post-846696-0-32644800-1425944297_thumb.

       a. I use the following custom install options...

 

post-846696-0-33877800-1425944317_thumb.

 

       b. Copy the config.plist, DSDT/SSDT.aml file(s) which are specific to your system into the Clover folder:

           - Put config.plist in /EFI/CLOVER directory

           - Put DSDT.aml in /EFI/CLOVER/ACPI/patched

           - Put FakeSMC.kext and other kexts required in EFI/CLOVER/kexts/10.x (where x is your version of OSX)

 

 

 

5.  Boot from the USB and you should see the following options at the Clover Main Menu (select each item, then press <spacebar>):

 

post-846696-0-45181100-1425944355_thumb.

  • “Boot Microsoft EFI boot menu from WIN” ---> boots Windows installer via bootmgfw.efi
  • “Boot Linux Mint EFI boot menu from LINUX” ---> boots Linux installer via grubx64.efi
  • “Boot OS X Install from Install OS X …” ---> boots OSX installer via boot.efi

Share this post


Link to post
Share on other sites

Hi,

 

Followed the instructions above about the muti-boot USB installer.

I have managed to split my install.wim file into install.swm & install2.swm files and copied all of my Windows ISO to my WIN partition (FAT32)

Installed Clover with the above recommended parameters, I unchecked the "Install Clover in ESP" button.

Clover installation went successful, then I copied the FakeSMC.kext and HFSPlus.efi file into the folders as shown in post#1.

I also copied the fusion71au-provided config.plist into the Clover folder.

 

Wasn't able to extract the bootmgfw.efi from my install.wim file though (I'm running Win7 for now)

 

I tried to boot from my USB with only Clover & Windows installer but I get the following message:
 

blf: init

blf: error

 

The 32GB stick was the one I used to actually install Mavericks before thinking multiboot, which confirms my USB can boot, am I wrong?

Share this post


Link to post
Share on other sites

Preperations for other systems then the Acer S3-391 (skip if you have the same notebook as post #2)

 

No, if you don't have the Acer S3-391 then don't use my specific system files, but instead, you need to have a working clover OS X installed and backup these files.

  • Custom kernal extentions;
  • DSDT.aml;
  • /EFI/CLOVER/config.plist;
  • /EFI/CLOVER/driver64UEFI/ all *.efi files

Extract my uploaded Acer_Aspire_ S3_391_OSX_EFI_Clover.zip and replace neccersairly files with you're own working files.

  1. Replace /EFI/CLOVER/ahci/patched/dsdt.aml with you're OWN;
  2. Replace /EFI/CLOVER/config.plist with you're OWN;
  3. Remove kext from /EFI/CLOVER/kext/10.9 and put you're OWN kext here;
  4. Remove *.efi files from /EFI/CLOVER/driver64EFUI and put you're OWN *.efi files here;

After this is done, everytime i tell you to use my files from Acer_Aspire_ S3_391_OSX_EFI_Clover.zip, Use this extracted/modified folder you just made yourself.

 

I'm confused on this step. What if i dont have a existing working OSx with clover installed. what are my options?

Share this post


Link to post
Share on other sites

I'm confused on this step. What if i dont have a existing working OSx with clover installed. what are my options?

Well, you can try and do alot research but then again, only follow this guide if you have a working osx with clover. If you dont understand hackint0sh with clover this whole guide is useless to you.

Share this post


Link to post
Share on other sites

COuld you please tell me why do I always boot into recover / repair ?

 

 

Try do delete the bootx64.efi cause you proberly dont need it, then re-do my tutorial and replace the bootmgr.efi files again with originals, maybe they {censored}ed it up. Then last what you can try is restart the guide cause youre recovery partition is in the first section, should be efi, for as i know. Good luck!

Share this post


Link to post
Share on other sites

Are there any differences in this guide if I install Mavericks like you said and then install Windows on a second hard drive?

I'm guessing it will still work the same but I don't know...

Share this post


Link to post
Share on other sites

Are there any differences in this guide if I install Mavericks like you said and then install Windows on a second hard drive?

I'm guessing it will still work the same but I don't know...

its almost the same but you need to set the correct UUID on the clover config.plist

Share this post


Link to post
Share on other sites

its almost the same but you need to set the correct UUID on the clover config.plist

Thanks for the tip!

 

It was actually even easier than your guide.

 

On my second HDD, I had a "data" partition (HFS+) for Mac and some free space. In the Windows install, I had to follow the manual partition instructions from this thread (using diskpart to make the MSR and primary partition and dism to copy the Windows build). But the EFI was installed to this second HDD.

 

So I have:

 

SSD (disk1) GPT

EFI partition - Clover

Mac Primary partition (HFS+)

Mac recovery

 

HDD (disk2) GPT

EFI partition - Windows

Mac Data (HFS+)

Windows MSR

Windows Primary (NTFS)

 

And Clover automatically detected the Windows EFI. With a small tweak I fixed it so it was not labeled as "Internal EFI....", but "Windows 8.1".

 

Thanks for the guide!

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 frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×