Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
From your last, edited post.
The first one booted up Yosemite just like with Piker's boot.efi.

Try this one, this is the same build but a x86 version. I am using these with a Yosemite GM1 installer on a USB stick.
 

Attachments

  • boot.efi.zip
    233.7 KB · Views: 324

Hammido

macrumors newbie
Oct 5, 2014
20
3
Stockholm, Sweden
Try this one, this is the same build but a x86 version.

Will do now! Thankfully, Windows (Boot Camp HDD) lets me write files to my Macintosh HD! :cool:
Thanks again!

EDIT: Or not. Connecting HDD externally to MacBook Air and replacing the faulty boot.efi's from there.

UPDATE: Your last posted boot.efi worked, but with no different boot time than the original. I admire the fact that you've made a bootable, working installation key!
 
Last edited:

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Will do now! Thankfully, Windows (Boot Camp HDD) lets me write files to my Macintosh HD! :cool:
Thanks again!

EDIT: Or not. Connecting HDD externally to MacBook Air and replacing the faulty boot.efi's from there.

UPDATE: Your last posted boot.efi worked, but with no different boot time than the original. I admire the fact that you've made a bootable, working installation key!

What Yosemite build are you using?
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

I'm using the latest Public Beta (4) which is working well with your x86 version boot.efi and the one released last Friday.

You suggest I upgrade to GM Candidate 1.0?


Let me do some more testing. It is odd that it will boot the installer but the x64 version is doing the same thing for me where it is trying to boot my Windows install instead, even with the active partition set to the Yosemite partition.

The x86 version works fine and boots very quickly for me.
 
Last edited:

LaurentR2D2

macrumors member
Jul 24, 2011
97
10
Paris - France
I've tried to prepare a bootable key with the boot.efi the same way I use to prepare my key to install/upgrade Mavericks, this key was seen as bootable in the Boot disk pane of the System preferences, but I haven't been able to boot on it. I have a Mac Pro rev 1,1 with an ATI Radeon HD 5870 1024 Mo from Apple.
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

I've tried to prepare a bootable key with the boot.efi the same way I use to prepare my key to install/upgrade Mavericks, this key was seen as bootable in the Boot disk pane of the System preferences, but I haven't been able to boot on it. I have a Mac Pro rev 1,1 with an ATI Radeon HD 5870 1024 Mo from Apple.


You probably didn't get the kernel, it wasn't required for Mavericks. You need to use pacifist to extract it from the Essentials.pkg. Then create a folder named Kernels in /System/Library and put the extracted kernel in that folder. There are also a few other differences when making the Yosemite installer compared to a Mavericks one.

Follow the beginning part of this guide and then add in the kernel part and boot.efi part.

https://mega.co.nz/#!S0R3lISD!dmAs0LtVZzXb66OYKSz-vNNk1yzK3WeJBMNBIu281nw

There are also some other modifications that must be done to the installer package files in order for "allow" the install. If you made an installer using Tiamo's boot.efi then you have done those modifications before.
 
Last edited:

gpatpandp

macrumors 6502
Aug 16, 2010
309
11
For those compiling an installer, my error was not in the boot.efi file I was using rather it was my incorrect placement of where I was extracting the "kernel" too. As Hennesie2000 clarified, the kernel goes in it's own folder entitled "Kernels" and placed in the System/Library folder of your installer. Once the "Kernels" folder is there, extract the "kernel" inside that folder and NOT in the root of the installer image as I had mistakenly been doing.

Also while not entirely certain that script made for Mavericks works in Yosemite and if your not very versed on terminal commands, an easy way to replace each boot.efi file is to create a "root" account on the secondary drive/partition that you will be mounting your Yosemite system on. Simply log in as the "root" and replace both files in seconds.
 
Last edited:

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Pike's boot.efi and Mavericks/Mountain Lion

Does anyone know whether Pike's boot.efi is backwards compatible with Mavericks and Mountain Lion?
 

ProfDrLuigi

macrumors member
Jun 19, 2010
71
1
Try this one, this is the same build but a x86 version. I am using these with a Yosemite GM1 installer on a USB stick.

My 1,1 booted up fine and quick with your boot.efi on an already installed system. Confirmed that it works. :D Haven´t check it with the installer.

Build 14A379b, Public Beta 4
 

tombosch

macrumors newbie
Oct 7, 2014
8
0
Hennesie2000 boot.efi

I just replaced the boot.efi on a Yosemite DP7 install and removed the clover bootloader. Everything seems to work great. Including audio and WiFi. Indeed no iMessage at this time.

Hopefully the boot.efi will be changed to boot in non verbose mode.

Thanks everybody for the good work!
 

LaurentR2D2

macrumors member
Jul 24, 2011
97
10
Paris - France
You probably didn't get the kernel, it wasn't required for Mavericks. You need to use pacifist to extract it from the Essentials.pkg. Then create a folder named Kernels in /System/Library and put the extracted kernel in that folder. There are also a few other differences when making the Yosemite installer compared to a Mavericks one.

Follow the beginning part of this guide and then add in the kernel part and boot.efi part.

https://mega.co.nz/#!S0R3lISD!dmAs0LtVZzXb66OYKSz-vNNk1yzK3WeJBMNBIu281nw

There are also some other modifications that must be done to the installer package files in order for "allow" the install. If you made an installer using Tiamo's boot.efi then you have done those modifications before.

I've started to read the guide. Is it mandatory to have a special installer partition ? I don't use Chameleon, so I guess I don't need the 1 Gb partition. For the moment, I just create a 8 Gb usb key as I do for Mavericks, and add the kernel file as you explain above. I've created a 100 Gb partition on one of my hard drives for Yosemite. The installer starts, I can choose the partition where I want to install Yosemite, the installation starts showing the remaining time, but after less than 1 mn, it stops with an undefined error (0)
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
I've started to read the guide. Is it mandatory to have a special installer partition ? I don't use Chameleon, so I guess I don't need the 1 Gb partition. For the moment, I just create a 8 Gb usb key as I do for Mavericks, and add the kernel file as you explain above. I've created a 100 Gb partition on one of my hard drives for Yosemite. The installer starts, I can choose the partition where I want to install Yosemite, the installation starts showing the remaining time, but after less than 1 mn, it stops with an undefined error (0)


No you don't need an installer partition. That guide is for a certain type of setup. When ever you see "installer partition" just mentally replace that with "thumb drive". Did you modify the OSInstall.mpkg, the InstallableMachines.plist, and the PlatformSuppot.plist?
 

H2SO4

macrumors 603
Nov 4, 2008
5,832
7,110
What’s going to be interesting is what AAPL replace on the point updates. Might be a little bit more work than before?
 

gpatpandp

macrumors 6502
Aug 16, 2010
309
11
Does anyone know whether Pike's boot.efi is backwards compatible with Mavericks and Mountain Lion?

I can confirm that the latest "Pike" boot.efi compiled build booted the OS X 10.8.5 64 bit "Mountain Lion" hack on my 2006 iMac 5,1. Suffice it to say, it would appear that the revolutionary Mac OS X Bootloader known as Tiamo's boot.efi while not forgotten has now officially become obsolete.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
I can confirm that the latest "Pike" boot.efi compiled build booted the OS X 10.8.5 64 bit "Mountain Lion" hack on my 2006 iMac 5,1. Suffice it to say, it would appear that the revolutionary Mac OS X Bootloader known as Tiamo's boot.efi while not forgotten has now officially become obsolete.

Excellent news. That will probably make updating from Mavericks to Yosemite even easier if we replace Tiamo's boot.efi (and its backup boot.efi.Tiamo) in Mavericks with Pike's boot.efi, thereby preventing the danger of having the newer, Yosemite-compatible boot.efi inadvertently replaced with Tiamo's Yosemite-incompatible boot.efi.
 

Hennesie2000

macrumors 68000
Sep 29, 2007
1,514
42
Maryland
Excellent news. That will probably make updating from Mavericks to Yosemite even easier if we replace Tiamo's boot.efi (and its backup boot.efi.Tiamo) in Mavericks with Pike's boot.efi, thereby preventing the danger of having the newer, Yosemite-compatible boot.efi inadvertently replaced with Tiamo's Yosemite-incompatible boot.efi.


Is it safe to assume Tobyg's script will work with Yosrmite?
 

666sheep

macrumors 68040
Dec 7, 2009
3,686
292
Poland
Suffice it to say, it would appear that the revolutionary Mac OS X Bootloader known as Tiamo's boot.efi while not forgotten has now officially become obsolete.

Not exactly. To give credit where it's due, it's still Tiamo's bootloader (sources), but now PikerAlpha's branch ;)
 

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Just compiled the latest version - will be trying it out on a test MacPro1,1 shortly.
 

LaurentR2D2

macrumors member
Jul 24, 2011
97
10
Paris - France
No you don't need an installer partition. That guide is for a certain type of setup. When ever you see "installer partition" just mentally replace that with "thumb drive". Did you modify the OSInstall.mpkg, the InstallableMachines.plist, and the PlatformSuppot.plist?

Yes, but the undefined error : 0 remains when the installer starts to copy the files on the disk.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.