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

Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Thanks again

Mr. Zarniwoop said:
The correct sequence:
  • first, install PikeYoseFix
  • if exceptionally cautious and running Trim Enabler, you may want to disable it
  • you must reboot before installing an OS X Update that overwrites Pike's boot.efi so the PikeYoseFix script installs fully for future automatic execution
  • only then install OS X Update
  • safe to re-enable Time Enabler if you disabled it earlier
Click to expand...

Thanks again Mr. Zarniwoop. These 10.10.2 instructions worked like a charm for me. Even though I have no idea what either the Trim or Time Enablers might be. It's references like those, in conjunction with the horror stories here that panic the hack-baffled and code-clueless such as myself :-D

Also thanks to the guys who put the PikeYoseFix script together. I'm so happy here that I'd leave a two-beer tip in your Paypals if I knew them.
 
Macbook Pro 2,2 2007 10.10.2

This tiamo/piker solution to getting yosemite running looks very neat. I have been playing with it trying to get it to work this weekend and can't seem to get it going.

In each situation I'm booting off a USB disk. I tried different methods such as

1) https://forums.macrumors.com/posts/20537556/ (which is the prepatched yosemite installer) and it just complains that I already have yosemite installed. Do I have to erase my target drive totally? Trying to install over my 10.7.5 install on my internal drive.

2) SFOTT. This would just reboot when I tried to boot of the key.

3) Clover method. Got the boot loader going but cannot start the clover patched installer disk

4) Manually patching the yosemite installer by copying over boot.efi, and modifying the platformsupported.plist and distribution files. Followed this guide http://lowendmac.com/2014/modernizing-the-mac-pro-11-and-21/
This one went through the whole install process and when it reboot for the 1st time. It just went back to my old 10.7.5 set up.

Which method seems to work the best for 10.10.2? Anyone get an install working with this version? I see lots of posts on how to get the yosemite working after patching with 10.10.2 but not a full install with 10.10.2.

Thanks in advance.
 
dagonmac said:
This tiamo/piker solution to getting yosemite running looks very neat. I have been playing with it trying to get it to work this weekend and can't seem to get it going.

In each situation I'm booting off a USB disk. I tried different methods such as

1) https://forums.macrumors.com/posts/20537556/ (which is the prepatched yosemite installer) and it just complains that I already have yosemite installed. Do I have to erase my target drive totally? Trying to install over my 10.7.5 install on my internal drive.

2) SFOTT. This would just reboot when I tried to boot of the key.

3) Clover method. Got the boot loader going but cannot start the clover patched installer disk

4) Manually patching the yosemite installer by copying over boot.efi, and modifying the platformsupported.plist and distribution files. Followed this guide http://lowendmac.com/2014/modernizing-the-mac-pro-11-and-21/
This one went through the whole install process and when it reboot for the 1st time. It just went back to my old 10.7.5 set up.

Which method seems to work the best for 10.10.2? Anyone get an install working with this version? I see lots of posts on how to get the yosemite working after patching with 10.10.2 but not a full install with 10.10.2.

Thanks in advance.
Click to expand...

I managed to get a working installation of 10.10.2 with SFOTT beta and after the usb stick creation I manually copied the Kernel (see first thread with the manual provided for a manual usb stick creation; just do the Kernel part with pacifist).

I'm just struggling to get it working on my RAID, as for a standard HDD or SSD it worked perfectly.

----------
F.A.D. said:
The problem seems to be my SSD RAID-0 consisting of four SSD's. I took all four SSD's out and installed it onto a HDD with no problems.

The problem now is to get it run on my SSD RAID-0.

Mavericks did install fine on the same setup with a SFOTT-stick! I tried to use SuperDuper to make a bootable copy from the Yosemite HDD install to the the RAID-0 but it will still not boot from the SSD RAID-0 :-( The white apple logo is then flickering with a folder with a question mark on it.

I also made a timemachine backup to an external Firewire 800 drive but the SFOTT Stick does not have the option to make a recovery from a Time Machine backup :-(

Any help is much appreciated!

Thank you all in advance!

Best regards,

David
Click to expand...

Installation on a single SSD also works fine but RAID does not work :-(

Mavericks installed just fine on my RAID-0 with SFOTT. I need the RAID-0 to get max speed due to the Bus Limit of around 220 MB/s.

Does anyone know if I can get a recovery from Time Machine option when booting from a usb stick? The SFOTT stick does not show this option.

As always thank you guys for the support!
 
F.A.D. said:
Installation on a single SSD also works fine but RAID does not work :-(

Mavericks installed just fine on my RAID-0 with SFOTT. I need the RAID-0 to get max speed due to the Bus Limit of around 220 MB/s.

Does anyone know if I can get a recovery from Time Machine option when booting from a usb stick? The SFOTT stick does not show this option.

As always thank you guys for the support!
Click to expand...

I just created a standard Yosemite stick which shows this option! Fingers crossed it will be able to recover my HDD Yosemite install onto the RAID with time machine.
 
dagonmac said:
This tiamo/piker solution to getting yosemite running looks very neat. I have been playing with it trying to get it to work this weekend and can't seem to get it going.
Click to expand...

It is very neat indeed, and it works well, as documented at the beginning of this thread. Some people have stated they've encountered difficulties in following the detailed procedure. Such difficulties may be summarised as follows:

  1. Some people have no clue as to what they are doing. This makes it hard for them to follow even simple steps. For them the whole thing is a conundrum, and, no matter how much detail you provide, every sentence opens up a wide gap of interpretive dilemmas. For the such, there's little hope that any of this will ever work.
  2. Some people simply can't read (this would be a subset of the above). For instance, it has been known all along that 10.10.2 would overwrite boot.efi, thereby crippling all machines relying on Tiamo/Pike's boot.efi. It has been equally known that there's an automatic script capable of restoring the patched boot.efi so that no harm will be done, but these people are surprised that they've bricked their computers, and imagine that they've come across some unforeseeable difficulty.
  3. Some people have unusual setups. In fact, they are so unusual that they themselves can't describe what the setup is. They may have even installed other patches that might interact with the boot mechanism, but they are no longer conscious of what they installed. Naturally, for someone else to imagine what such users might have installed may require a crystal ball.
  4. Some people are knowledgeable and smart, but simply have bad luck in the choice of auxiliary hardware to effect the initial installation procedure. It appears that several brands of pen drives fail to boot as expected.

For the last group, and possibly as a general recommendation, I would suggest that, instead of using a USB pen drive, Yosemite be installed by creating the customised installer on a hard drive in one of Mac Pro bays. That is faster than a pen drive, more fool-proof, it can't be misplaced, so that you can easily reboot into the installer, should that be required at any time (for instance, if one's clumsiness causes the patched boot.efi to be replaced by a software update), et cetera.
 
PeterHolbrook said:
It is very neat indeed, and it works well, as documented at the beginning of this thread. Some people have stated they've encountered difficulties in following the detailed procedure. Such difficulties may be summarised as follows:



  1. Some people have no clue as to what they are doing. This makes it hard for them to follow even simple steps. For them the whole thing is a conundrum, and, no matter how much detail you provide, every sentence opens up a wide gap of interpretive dilemmas. For the such, there's little hope that any of this will ever work.
  2. Some people simply can't read (this would be a subset of the above). For instance, it has been known all along that 10.10.2 would overwrite boot.efi, thereby crippling all machines relying on Tiamo/Pike's boot.efi. It has been equally known that there's an automatic script capable of restoring the patched boot.efi so that no harm will be done, but these people are surprised that they've bricked their computers, and imagine that they've come across some unforeseeable difficulty.
  3. Some people have unusual setups. In fact, they are so unusual that they themselves can't describe what the setup is. They may have even installed other patches that might interact with the boot mechanism, but they are no longer conscious of what they installed. Naturally, for someone else to imagine what such users might have installed may require a crystal ball.
  4. Some people are knowledgeable and smart, but simply have bad luck in the choice of auxiliary hardware to effect the initial installation procedure. It appears that several brands of pen drives fail to boot as expected.



For the last group, and possibly as a general recommendation, I would suggest that, instead of using a USB pen drive, Yosemite be installed by creating the customised installer on a hard drive in one of Mac Pro bays. That is faster than a pen drive, more fool-proof, it can't be misplaced, so that you can easily reboot into the installer, should that be required at any time (for instance, if one's clumsiness causes the patched boot.efi to be replaced by a software update), et cetera.
Click to expand...


+1

I have never encountered any of the errors reported recently and it was known that 10.10.2 overwrote the boot.efi since 10.10.2 beta 1.

If you follow the instructions it works fine. When you start throwing unknown variables into the situation then you have problems.
 
Thanks guys for the input. I've been reading posts for half an hour now I have to admit I belong to the people who barely know what their doing.

Like a lot of people I ran a Mac Pro 2,1 flawlessly with a 10.10.1. So flawlessly that I didn't even think there could be problems with a 10.10.2 update. I should have checked more thoroughly, but I didn't and now I feel stupid. But what's done is done and now I have to find a way to correct my mistake. I can only hope you guys will help me even though I was an idiot.

So here goes. Yes, my screen is booting all black since the 10.10.2 update and restarting just has the same effect.

In the past the SFOTT method has worked for me. I tried the other methods but they didn't work. SFOTT did, so I'm trying this again. Only problem is I need a working Yosemite Installation file to make the SFOTT USB drive, so I'm downloading that as we speak on my laptop which I'm also using to write this. The Mac Pro is still running the black screen.

Now here's my question: As far as I can remember it's a SFOTT Beta which will look for the Developer Preview of Yosemite Installation file. If I remember correctly I simply changed the name of the file so it said "Install OS X Yosemite Developer Preview". Is that still the way to go?

Second question: when I have fabricated my SFOTT USB key, I put that in the Mac Pro and boot from it. But what then? Is there some way I can "repair" the EFI without re-installing Yosemite?

Maybe I have asked questions that were answered somewhere else here. If that is the case I'm sorry.

At this point I would be thankful for every tip you could give me. Maybe I don't have to use the SFOTT method. Maybe there is a very simple method to change the EFIs on my Mac Pro without having to re-install anything.
 
RX2904 said:
Thanks guys for the input. I've been reading posts for half an hour now I have to admit I belong to the people who barely know what their doing.

Like a lot of people I ran a Mac Pro 2,1 flawlessly with a 10.10.1. So flawlessly that I didn't even think there could be problems with a 10.10.2 update. I should have checked more thoroughly, but I didn't and now I feel stupid. But what's done is done and now I have to find a way to correct my mistake. I can only hope you guys will help me even though I was an idiot.

So here goes. Yes, my screen is booting all black since the 10.10.2 update and restarting just has the same effect.

In the past the SFOTT method has worked for me. I tried the other methods but they didn't work. SFOTT did, so I'm trying this again. Only problem is I need a working Yosemite Installation file to make the SFOTT USB drive, so I'm downloading that as we speak on my laptop which I'm also using to write this. The Mac Pro is still running the black screen.

Now here's my question: As far as I can remember it's a SFOTT Beta which will look for the Developer Preview of Yosemite Installation file. If I remember correctly I simply changed the name of the file so it said "Install OS X Yosemite Developer Preview". Is that still the way to go?

Second question: when I have fabricated my SFOTT USB key, I put that in the Mac Pro and boot from it. But what then? Is there some way I can "repair" the EFI without re-installing Yosemite?

Maybe I have asked questions that were answered somewhere else here. If that is the case I'm sorry.

At this point I would be thankful for every tip you could give me. Maybe I don't have to use the SFOTT method. Maybe there is a very simple method to change the EFIs on my Mac Pro without having to re-install anything.
Click to expand...

I installed Lion on an extra HDD when I had the same problem under mavericks. I then booted Lion and replaced the boot.fi on the mavericks installation and that was it: unplugged the Lion disk and Mavericks booted fine.
This should work here too.

By the way the SFOTT beta allows to use the newest 10.10.2 official release, no need to rename it etc.

----------

The first post states:

"With Pike's boot.efi, holding Command-R to start the OS X Recovery System that gets installed with Yosemite is supported"

On my systems its not working it always boots into the system and does not load the recovery system.

Any suggestions?
 
F.A.D. said:
I installed Lion on an extra HDD when I had the same problem under mavericks. I then booted Lion and replaced the boot.fi on the mavericks installation and that was it: unplugged the Lion disk and Mavericks booted fine.

This should work here too.



By the way the SFOTT beta allows to use the newest 10.10.2 official release, no need to rename it etc.

----------

The first post states:



"With Pike's boot.efi, holding Command-R to start the OS X Recovery System that gets installed with Yosemite is supported"



On my systems its not working it always boots into the system and does not load the recovery system.



Any suggestions?
Click to expand...


Are you using the latest boot.efi file?

----------
RX2904 said:
Thanks guys for the input. I've been reading posts for half an hour now I have to admit I belong to the people who barely know what their doing.

Like a lot of people I ran a Mac Pro 2,1 flawlessly with a 10.10.1. So flawlessly that I didn't even think there could be problems with a 10.10.2 update. I should have checked more thoroughly, but I didn't and now I feel stupid. But what's done is done and now I have to find a way to correct my mistake. I can only hope you guys will help me even though I was an idiot.

So here goes. Yes, my screen is booting all black since the 10.10.2 update and restarting just has the same effect.

In the past the SFOTT method has worked for me. I tried the other methods but they didn't work. SFOTT did, so I'm trying this again. Only problem is I need a working Yosemite Installation file to make the SFOTT USB drive, so I'm downloading that as we speak on my laptop which I'm also using to write this. The Mac Pro is still running the black screen.

Now here's my question: As far as I can remember it's a SFOTT Beta which will look for the Developer Preview of Yosemite Installation file. If I remember correctly I simply changed the name of the file so it said "Install OS X Yosemite Developer Preview". Is that still the way to go?

Second question: when I have fabricated my SFOTT USB key, I put that in the Mac Pro and boot from it. But what then? Is there some way I can "repair" the EFI without re-installing Yosemite?

Maybe I have asked questions that were answered somewhere else here. If that is the case I'm sorry.

At this point I would be thankful for every tip you could give me. Maybe I don't have to use the SFOTT method. Maybe there is a very simple method to change the EFIs on my Mac Pro without having to re-install anything.
Click to expand...


If you have a bootable USB you could use terminal to copy the boot.efi files off the USB to the Yosemite installation.
 
RX2904 said:
At this point I would be thankful for every tip you could give me. Maybe I don't have to use the SFOTT method. Maybe there is a very simple method to change the EFIs on my Mac Pro without having to re-install anything.
Click to expand...

Not being there with you, it's hard to say if the amount of damage done to your Yosemite installation by the 10.10.2 update or other processes involves more than the mere replacement of the two instances of boot.efi. If we assume that this is the only problem you have, the solution would be extremely simple, if you know how to use Terminal:

  1. You need a valid copy of Pike's boot.efi. It may reside, for instance, on a USB stick.
  2. You need to boot from some reliable medium, such as a Snow Leopard or Lion boot disk, DVD or USB stick. For instance, a Snow Leopard install DVD would be fine.
  3. Once you boot, you need to run Terminal. You should enter something like this 'cd "/Volumes/Macintosh HD/System/Library/CoreServices"' (WITHOUT the single quotation marks, and assuming "Macintosh HD" is the name of your Yosemite partition.
  4. Next enter "sudo chflags nouchg boot.efi" (without the double quotes).
  5. You'll be asked for an administrative password. Enter it.
  6. Next, copy Pike's boot.efi on top of the mess you caused to appear there. Enter "cp /Volumes/MyUSBDrive/boot.efi ." (without the double quotes), assuming the name of your USB stick is "MyUSBDrive".
  7. Next enter "sudo chflags uchg boot.efi" (without the double quotes).
  8. Now, enter 'cd "/Volumes/Macintosh HD/usr/standalone/i386"' (without the single quotes).
  9. Repeat the above procedure, without the "sudo" lines (not necessary for that folder).
  10. Reboot.
 
Last edited:
PeterHolbrook said:
Not being there with you, it's hard to say if the amount of damage done to your Yosemite installation by the 10.10.2 update or other processes involves more than the mere replacement of the two instances of boot.efi. If we assume that this is the only problem you have, the solution would be extremely simple, if you know how to use Terminal:

  1. You need a valid copy of Pike's boot.efi. It may reside, for instance, on a USB stick.
  2. You need to boot from some reliable medium, such as a Snow Leopard or Lion boot disk, DVD or USB stick. For instance, a Snow Leopard install DVD would be fine.
  3. Once you boot, you need to run Terminal. You should enter something like this 'cd "/Volumes/Macintosh HD/System/Library/CoreServices"' (WITHOUT the single quotation marks, and assuming "Macintosh HD" is the name of your Yosemite partition.
  4. Next enter "sudo chflags -nouchg boot.efi" (without the double quotes).
  5. You'll be asked for an administrative password. Enter it.
  6. Next, copy Pike's boot.efi on top of the mess you caused to appear there. Enter "cp /Volumes/MyUSBDrive/boot.efi ." (without the double quotes), assuming the name of your USB stick is "MyUSBDrive".
  7. Next enter "sudo chflags -uchg boot.efi" (without the double quotes).
  8. Now, enter 'cd "/Volumes/Macintosh HD/usr/standalone/i386"' (without the single quotes).
  9. Repeat the above procedure, without the "sudo" lines (not necessary for that folder).
  10. Reboot.
Click to expand...

Step #4 can be replaced with "sudo rm -rf boot.efi".
 


----------
F.A.D. said:
I installed Lion on an extra HDD when I had the same problem under mavericks. I then booted Lion and replaced the boot.fi on the mavericks installation and that was it: unplugged the Lion disk and Mavericks booted fine.
This should work here too.

By the way the SFOTT beta allows to use the newest 10.10.2 official release, no need to rename it etc.

----------
Click to expand...


I'm having problems telling the system to boot from the bootable USB stick. I'm pressing down ALT while booting and I should be able to get a select a start volume right? My screens stays black. I'm afraid I'll have the same problem when I install Lion on an extra HDD. How do i select the start volume if the screen stays black?

:(
 
RX2904 said:


----------



I'm having problems telling the system to boot from the bootable USB stick. I'm pressing down ALT while booting and I should be able to get a select a start volume right? My screens stays black. I'm afraid I'll have the same problem when I install Lion on an extra HDD. How do i select the start volume if the screen stays black?

:(
Click to expand...


What GPU do you have?
 
RX2904 said:
Uhm... I bought it used so I could run Mavericks and I haven't done anything to it ever since.



Is there any way I can tell if it's been flashed by the former owner?
Click to expand...


I'm not sure but if it isn't flashed the you won't ever see a boot screen when holding option. Do you see an Apple logo when booting or is it just a blank screen until you see the login or desktop?
 
Hennesie2000 said:
I'm not sure but if it isn't flashed the you won't ever see a boot screen when holding option. Do you see an Apple logo when booting or is it just a blank screen until you see the login or desktop?
Click to expand...

First of all in case I forget it, thank you so much for taking the time trying to help me. I know there's nothing in it for you. I really appreciate it. I promise if we get this done there is a PayPal Thank you coming your way!

To answer your question until a couple of hours ago I did run 10.10.1 with this thing and no, I never got the apple logo, it was just a blank screen until the desktop came up. Now obviously it just stays black.

Now that you mention it, I have never tried to use the option key to select a boot volume ever since I have had the new GPU.
 
RX2904 said:
First of all in case I forget it, thank you so much for taking the time trying to help me. I know there's nothing in it for you. I really appreciate it. I promise if we get this done there is a PayPal Thank you coming your way!



To answer your question until a couple of hours ago I did run 10.10.1 with this thing and no, I never got the apple logo, it was just a blank screen until the desktop came up. Now obviously it just stays black.



Now that you mention it, I have never tried to use the option key to select a boot volume ever since I have had the new GPU.
Click to expand...


Sounds like it is not flashed so you would need to set the Startup Disk in system preferences. You can't use option without an EFI card.
 
Hi guys,

I just had the same problem (10.10.2 bricking my Yosemite install on MacPro 1,1). I recreated a USB bootable key and I'll booting on it soon. I was wondering what steps should I follow now. Should I reinstall my entire system or is there a way to just apply the patched efi again?


Thanks for any help :)
 
Hennesie2000 said:
Sounds like it is not flashed so you would need to set the Startup Disk in system preferences. You can't use option without an EFI card.
Click to expand...

Sounds plausible but how do i get to the system preferences if i can't even boot? :confused:

Hennessie,

I've been thinking... How about

1. I install LION on an unused HDD,
2. I pull the HDD with my now broken Yosemite out of the MacPro slot
3. Swap it for the aforementioned Lion HDD
4. Then I boot with just the Lion HDD in it. This should cause the computer to boot from the only system available right? So that's Lion. Once it's booted, I go to System Preferences, make sure that it's using the Lion HDD to boot from now on.
5. Powering down and then putting the Yosemite HDD in slot 2
6. Booting again and now I am in Lion and I should see the Yosemite HDD as an internal hard drive and I can swap the EFIs

Would that work?
 
hubchau said:
Hi guys,

I just had the same problem (10.10.2 bricking my Yosemite install on MacPro 1,1). I recreated a USB bootable key and I'll booting on it soon. I was wondering what steps should I follow now. Should I reinstall my entire system or is there a way to just apply the patched efi again?


Thanks for any help :)
Click to expand...


This was just covered 10 post back by PeterHolbrook.

----------
RX2904 said:
Sounds plausible but how do i get to the system preferences if i can't even boot? :confused:



Hennessie,



I've been thinking... How about



1. I install LION on an unused HDD,

2. I pull the HDD with my now broken Yosemite out of the MacPro slot

3. Swap it for the aforementioned Lion HDD

4. Then I boot with just the Lion HDD in it. This should cause the computer to boot from the only system available right? So that's Lion. Once it's booted, I go to System Preferences, make sure that it's using the Lion HDD to boot from now on.

5. Powering down and then putting the Yosemite HDD in slot 2

6. Booting again and now I am in Lion and I should see the Yosemite HDD as an internal hard drive and I can swap the EFIs



Would that work?
Click to expand...


Exactly
 
Hennesie2000 said:
This was just covered 10 post back by PeterHolbrook.

----------




Exactly
Click to expand...

Good. Now there is a problem. I can't get my head wrapped around it but for you it's probably nothing...

1. I have an empty HDD now connected to this MacBook (running Yosemite) I'm typing on. As mentioned I want to put Lion on the empty HDD.
2. When I'm trying to install Lion it says now I can't because the MacBook is running a newer OSX than what I'm trying to install. I don't even get to the point where I can tell it, "Don't worry, I want to put it on this extra drive, not overwrite Yosemite on this MacBook".

What do I do? Please don't tell me I need a Lion machine to install Lion someplace else. :(
 
RX2904 said:
Good. Now there is a problem. I can't get my head wrapped around it but for you it's probably nothing...



1. I have an empty HDD now connected to this MacBook (running Yosemite) I'm typing on. As mentioned I want to put Lion on the empty HDD.

2. When I'm trying to install Lion it says now I can't because the MacBook is running a newer OSX than what I'm trying to install. I don't even get to the point where I can tell it, "Don't worry, I want to put it on this extra drive, not overwrite Yosemite on this MacBook".



What do I do? Please don't tell me I need a Lion machine to install Lion someplace else. :(
Click to expand...


Use the Mac Pro to install lion on the hdd.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back