Use TiamoMacProfix from Mavericks thread. It's always better to use boot.efi made specifically for OS you want to run.
Got a tip for us?
Let us know
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
- Thread starter Mr. Zarniwoop
- Start date
- Sort by reaction score
Use TiamoMacProfix from Mavericks thread. It's always better to use boot.efi made specifically for OS you want to run.
I was able to do further testing on this problem that we share.
I did a clean install of Yosemite to a spare SSD. I ran the patch file from post 2166 (the gray one), and then rebooted a couple of times to ensure the script was working properly. I then did the 10.10.2 update from the app store and, this time, it was a success. I am typing this now on 10.10.2.
So, this means the following can be confirmed:
1) The issue is NOT with the NVIDIA GTX 570. The default drivers that Apple provides work fine. I have dual-monitor support, everything works.
2) The issue MIGHT be with the SSD RAID; however, I find this very unlikely given that it has never previously presented a problem.
3) The issue MIGHT be with some incompatible software element residing on the Mac Pro drive: some previous hack script, for example, that I may have completely forgotten I installed.
I think option 3 above is the most likely. My main drive has gone all the way through Mavericks into Yosemite without a fresh install (always overwrites), and once I tried the fresh install, everything worked perfectly.
Just to confirm; for all those who have had a problem installing 10.10.2 on their SFOTT-hacked MacPro's. The above procedure worked perfectly for me!
Many thanks to Hennesie2000 for all the help!!
What ever it was, it's gone. Left it running 10.10.2 overnight and came back up ok with both drives. Weird.
For those with Firewire cable and 2 machines
I have 2 Mac Pros 1,1 (2006/2007) and had to install 10.10.2 on one just watch it fail to boot (before I came across this forum), so I decided to dig out what happened. Booted sick mac to Target Mode (hold T while powering up) and hooled it up to the one still running 10.10.1. In Terminal, I ran a few commands to find boot.efi files and see which one had timestamp at the time I installed update which tells me that it was modified:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 29 Jan 00:57 /System/Library/CoreServices/boot.efi
Check the same file on your mounted volume from the non booting one (check the name in Finder), go to that drive using
cd /Volumes
ls
cd NameOfExternalDrive
Change NameOfExternalDrive to real name of the external drive (see it in Finder).
Check the timestamp on boot.fi on that drive:
ls ./System/Library/CoreServices/boot.efi
Don't forget the . in front! The output might look like:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 30 Jan 11:57 /System/Library/CoreServices/boot.efi
Do the same for the file at /usr/standalone/i386/boot.efi
ls -latr /usr/standalone/i386/boot.efi
ls -latr ./usr/standalone/i386/boot.efi
Check the dates. If they are modified at the time of failed upgrade replace the files with the ones from working Mac Pro which is still at 10.10.1:
Step1: Remove flags since these are locked:
sudo chflags nouchg /usr/standalone/i386/boot.efi
sudo chflags nouchg ./usr/standalone/i386/boot.efi
Step 2: back up "bad one":
sudo mv ./usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi.bkp
Step 3: copy good one to where bad one was:
sudo cp /usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi
Step 4 : Put locks back:
sudo chflags uchg /usr/standalone/i386/boot.efi
sudo chflags uchg ./usr/standalone/i386/boot.efi
Repeat the same procedure for file at /System/Library/CoreServices/boot.efi and ./System/Library/CoreServices/boot.efi if needed (depends on timestamps)
This may sound complicated, but that was my case, I have 2 machines that have SFOTT so this kind of workaround worked. Use at you own risk, this is working for me on 2 machines.
When done, unmount (eject) external drives that were mounted using Target Mode. Reboot the non booting Mac and hope for the best
HTH
I have 2 Mac Pros 1,1 (2006/2007) and had to install 10.10.2 on one just watch it fail to boot (before I came across this forum), so I decided to dig out what happened. Booted sick mac to Target Mode (hold T while powering up) and hooled it up to the one still running 10.10.1. In Terminal, I ran a few commands to find boot.efi files and see which one had timestamp at the time I installed update which tells me that it was modified:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 29 Jan 00:57 /System/Library/CoreServices/boot.efi
Check the same file on your mounted volume from the non booting one (check the name in Finder), go to that drive using
cd /Volumes
ls
cd NameOfExternalDrive
Change NameOfExternalDrive to real name of the external drive (see it in Finder).
Check the timestamp on boot.fi on that drive:
ls ./System/Library/CoreServices/boot.efi
Don't forget the . in front! The output might look like:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 30 Jan 11:57 /System/Library/CoreServices/boot.efi
Do the same for the file at /usr/standalone/i386/boot.efi
ls -latr /usr/standalone/i386/boot.efi
ls -latr ./usr/standalone/i386/boot.efi
Check the dates. If they are modified at the time of failed upgrade replace the files with the ones from working Mac Pro which is still at 10.10.1:
Step1: Remove flags since these are locked:
sudo chflags nouchg /usr/standalone/i386/boot.efi
sudo chflags nouchg ./usr/standalone/i386/boot.efi
Step 2: back up "bad one":
sudo mv ./usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi.bkp
Step 3: copy good one to where bad one was:
sudo cp /usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi
Step 4 : Put locks back:
sudo chflags uchg /usr/standalone/i386/boot.efi
sudo chflags uchg ./usr/standalone/i386/boot.efi
Repeat the same procedure for file at /System/Library/CoreServices/boot.efi and ./System/Library/CoreServices/boot.efi if needed (depends on timestamps)
This may sound complicated, but that was my case, I have 2 machines that have SFOTT so this kind of workaround worked. Use at you own risk, this is working for me on 2 machines.
When done, unmount (eject) external drives that were mounted using Target Mode. Reboot the non booting Mac and hope for the best
HTH
Last edited:
I have 2 Mac Pros 1,1 (2006/2007) and had to install 10.10.2 on one just watch it fail to boot (before I came across this forum), so I decided to dig out what happened. Booted sick mac to Target Mode (hold T while powering up) and hooled it up to the one still running 10.10.1. In Terminal, I ran a few commands to find boot.efi files and see which one had timestamp at the time I installed update which tells me that it was modified:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 29 Jan 00:57 /System/Library/CoreServices/boot.efi
Check the same file on your mounted volume from the non booting one (check the name in Finder), go to that drive using
cd /Volumes
ls
cd NameOfExternalDrive
Change NameOfExternalDrive to real name of the external drive (see it in Finder).
Check the timestamp on boot.fi on that drive:
ls ./System/Library/CoreServices/boot.efi
Don't forget the . in front! The output might look like:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 30 Jan 11:57 /System/Library/CoreServices/boot.efi
Do the same for the file at /usr/standalone/i386/boot.efi
ls -latr /usr/standalone/i386/boot.efi
ls -latr ./usr/standalone/i386/boot.efi
Check the dates. If they are modified at the time of failed upgrade replace the files with the ones from working Mac Pro which is still at 10.10.1:
Step1: Remove flags since these are locked:
sudo chflags nouchg /usr/standalone/i386/boot.efi
sudo chflags nouchg ./usr/standalone/i386/boot.efi
Step 2: back up "bad one":
sudo mv ./usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi.bkp
Step 3: copy good one to where bad one was:
sudo cp /usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi
Step 4 : Put locks back:
sudo chflags uchg /usr/standalone/i386/boot.efi
sudo chflags uchg ./usr/standalone/i386/boot.efi
Repeat the same procedure for file at /System/Library/CoreServices/boot.efi and ./System/Library/CoreServices/boot.efi if needed (depends on timestamps)
This may sound complicated, but that was my case, I have 2 machines that have SFOTT so this kind of workaround worked. Use at you own risk, this is working for me on 2 machines.
When done, unmount (eject) external drives that were mounted using Target Mode. Reboot the non booting Mac and hope for the best
HTH
The boot.efi file located in the i386 folder is not a locked file. Just an FYI.
I have 2 Mac Pros 1,1 (2006/2007) and had to install 10.10.2 on one just watch it fail to boot (before I came across this forum), so I decided to dig out what happened. Booted sick mac to Target Mode (hold T while powering up) and hooled it up to the one still running 10.10.1. In Terminal, I ran a few commands to find boot.efi files and see which one had timestamp at the time I installed update which tells me that it was modified:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 29 Jan 00:57 /System/Library/CoreServices/boot.efi
Check the same file on your mounted volume from the non booting one (check the name in Finder), go to that drive using
cd /Volumes
ls
cd NameOfExternalDrive
Change NameOfExternalDrive to real name of the external drive (see it in Finder).
Check the timestamp on boot.fi on that drive:
ls ./System/Library/CoreServices/boot.efi
Don't forget the . in front! The output might look like:
beast2:~ sleepy$ ls -latr /System/Library/CoreServices/boot.efi
-rw-r--r-- 1 root wheel 349696 30 Jan 11:57 /System/Library/CoreServices/boot.efi
Do the same for the file at /usr/standalone/i386/boot.efi
ls -latr /usr/standalone/i386/boot.efi
ls -latr ./usr/standalone/i386/boot.efi
Check the dates. If they are modified at the time of failed upgrade replace the files with the ones from working Mac Pro which is still at 10.10.1:
Step1: Remove flags since these are locked:
sudo chflags nouchg /usr/standalone/i386/boot.efi
sudo chflags nouchg ./usr/standalone/i386/boot.efi
Step 2: back up "bad one":
sudo mv ./usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi.bkp
Step 3: copy good one to where bad one was:
sudo cp /usr/standalone/i386/boot.efi ./usr/standalone/i386/boot.efi
Step 4 : Put locks back:
sudo chflags uchg /usr/standalone/i386/boot.efi
sudo chflags uchg ./usr/standalone/i386/boot.efi
Repeat the same procedure for file at /System/Library/CoreServices/boot.efi and ./System/Library/CoreServices/boot.efi if needed (depends on timestamps)
This may sound complicated, but that was my case, I have 2 machines that have SFOTT so this kind of workaround worked. Use at you own risk, this is working for me on 2 machines.
When done, unmount (eject) external drives that were mounted using Target Mode. Reboot the non booting Mac and hope for the best
HTH
Thanks, going to try this today.
so I took the plunge this morning. Created a USB drive following the guide, everything went very well. I was shocked at how well it went.
Installed, then rebooted with a flashing finder (?) so couldn't complete the install.
It then occurred to me that I had downloaded Yosemite from the App Store this morning. Turns out I downloaded 10.10.2 (of course).
Should that cause any issues - or should my Pro have booted into Yosemite? I'm confused now.
I guess I might have to rebuild and reinstall with a 10.10.0 system?
TIA
Installed, then rebooted with a flashing finder (?) so couldn't complete the install.
It then occurred to me that I had downloaded Yosemite from the App Store this morning. Turns out I downloaded 10.10.2 (of course).
Should that cause any issues - or should my Pro have booted into Yosemite? I'm confused now.
I guess I might have to rebuild and reinstall with a 10.10.0 system?
TIA
Interesting. Im pretty sure i haven't done a fresh install on this machine since 10.6 honestly. I really didn't want to put any more money in this machine. I bought it when it first came out and at this point i'm just getting sick of having to hack at it just in order to update it.
Im going to dig through and see if there is anything i can clean. I'm also curious if i try that pike black screen boot.efi if that would make a difference. actually now that i'm thinking about it. I wonder if i installed yosemite if i used the black of grey boot efi. I didn't think it would make a difference but maybe it does?
Edit: Well tried with the black boot.efi and it made no difference. I'm in windows now and what really sucks is that I can't get to my mac drive because its over 3TB, and windows wont read it.
Last edited:
Disabling OS update?
Hi, I've read a lot of the difficulties people have been describing here with the 10.10.2 update and honestly don't have the time to sort out a possibly problematic EFI overwrite to my Mac Pro 2,1. I'm currently at 10.10.1 through all the genius EFI and script coding you guys here have provided. I donated to Tiamo back on Maverick's and the 25 euros to Piker-Alpha and would donate to more of you coders if I knew where to send it. at least enough for a beer or two
My question is: after a scary 10.10.2 Notification Center popup here this morning I went fishing for a way to disable that update from installing itself unbidden but I found nothing in the App Store. I also checked System Preferences for anything related to automatic updates. The notification seems to be claiming to have already downloaded it and wants my permission to install and restart. I seem to recall the last time I ignored a Yosemite OS update it went ahead and did install 10.10.1 at the next restart anyway. Ugh, what do I do?
TIA for any advice.
Hi, I've read a lot of the difficulties people have been describing here with the 10.10.2 update and honestly don't have the time to sort out a possibly problematic EFI overwrite to my Mac Pro 2,1. I'm currently at 10.10.1 through all the genius EFI and script coding you guys here have provided. I donated to Tiamo back on Maverick's and the 25 euros to Piker-Alpha and would donate to more of you coders if I knew where to send it. at least enough for a beer or two
My question is: after a scary 10.10.2 Notification Center popup here this morning I went fishing for a way to disable that update from installing itself unbidden but I found nothing in the App Store. I also checked System Preferences for anything related to automatic updates. The notification seems to be claiming to have already downloaded it and wants my permission to install and restart. I seem to recall the last time I ignored a Yosemite OS update it went ahead and did install 10.10.1 at the next restart anyway. Ugh, what do I do?
TIA for any advice.
System Preferences > App Store
I just updated my MacPro2,1 to 10.10.2 with no issues but I previously had the PikeYoseFix installed. Others who had their Piker boot.efi overwritten by the 10.10.2 update either installed PikeYoseFix and then didn't reboot, so it never actually ran, or don't use the script at all.
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 Trim Enabler if you disabled it earlier
Attachments
Last edited:
Update: Luckily I had my 10.10.1 image on a replaced drive. I merely copied boot.efi from 10.10.1 drive to the updated 10.10.2 drive. Applied the necessary chmod lock modification to the boot.efi in CoreServices directory. Now the system boots. Thanks for the pointers in this thread that helped me resolve this.
One more update...
I installed Yosemite onto a freshly cleaned and empty RAID 0 array. After installing the (gray) patch, rebooting, and doing the App store update, I am now successfully booted into 10.10.2. It wasn't without drama, though, as it didn't boot initially after the update, and defaulted to another drive. I tried one more reboot and it worked.
So I can certainly now confirm the issue is NOT with RAID 0 array, and was likely caused by some random piece of hack software or script that I previously installed and simply totally forgot about.
A bit of a pain in the ass to have to migrate all my data and apps back, but it's done.
Yes you're right, I stand corrected
I wrote this from memory, and /System/Library/CoreServices/boot.efi is locked as far as I remember.
Just installed 10.10.2 onto my 2006 Mac Pro for the first time and it all went smoothly! Been using it for an hour and have had no problems at all. Got to say a big thanks to everyone who's had a hand in making this work.!! Very awesome.
One question though, why do you need to repair the disk permissions after copying the boot.efi file?
The way I did it was load 10.10.2 onto the drive through my MacBook Pro and then copy over the boot.efi. I then was able to boot the 2006 Mac Pro straight away. (Forgot to repair permissions but it doesn't seem to matter?)
The only other thing I noticed was that my 10.10.2 drive was almost instantly full (30GB) which I thought was very weird for a clean install. After a bit of snooping I realised the MacBook Pro had activated the sleepimage which was chewing into space and not needed on the Mac Pro anyway, so I've disabled it.
If anyone else has this problem you can disable sleep mode in Terminal: "sudo pmset -a hibernatemode 0" and also delete the sleepimage "sudo rm /private/var/vm/sleepimage".
I'll update if I come across anything else unusual, but for now pretty happy with this upgrade.
One question though, why do you need to repair the disk permissions after copying the boot.efi file?
The way I did it was load 10.10.2 onto the drive through my MacBook Pro and then copy over the boot.efi. I then was able to boot the 2006 Mac Pro straight away. (Forgot to repair permissions but it doesn't seem to matter?)
The only other thing I noticed was that my 10.10.2 drive was almost instantly full (30GB) which I thought was very weird for a clean install. After a bit of snooping I realised the MacBook Pro had activated the sleepimage which was chewing into space and not needed on the Mac Pro anyway, so I've disabled it.
If anyone else has this problem you can disable sleep mode in Terminal: "sudo pmset -a hibernatemode 0" and also delete the sleepimage "sudo rm /private/var/vm/sleepimage".
I'll update if I come across anything else unusual, but for now pretty happy with this upgrade.
Upgraded to 10.10.2 how can i boot my old drive
Hello guys, I am truly sorry if my question has been answered before.. Ive been searching this thread but couldn't find a straight forward answer to my problem..
I upgraded my Mac Pro 1,1 SFOTT from 10.10 to 10.10.2 without realizing its going to break my boot.efi .. Now I am trying to restore or downgrade back to 10.10 to be able to apply the patch... I don't want to erase HD since I Have so many things on it I need...
Is there any straight forward instructions to getting my machine back up and running??
Thank you so much in advance!
Hello guys, I am truly sorry if my question has been answered before.. Ive been searching this thread but couldn't find a straight forward answer to my problem..
I upgraded my Mac Pro 1,1 SFOTT from 10.10 to 10.10.2 without realizing its going to break my boot.efi .. Now I am trying to restore or downgrade back to 10.10 to be able to apply the patch... I don't want to erase HD since I Have so many things on it I need...
Is there any straight forward instructions to getting my machine back up and running??
Thank you so much in advance!
fresh SFOTT with 10.10.2 does not boot after install
Hello my friends,
I just created a SFOTT usb stick with the 10.10.2 installer and manually copied the Kernel to the Kernels folder.
It booted just fine and installed Yosemite.
After the restart it just shows the white Apple logo and freezes there. I did a reinstall etc. but after a successful installation it freezes on the white apple logo and does not boot any further.
Has anyone experienced something similar or have a clue what is happening here?
I'm on a 1,1 MacPro flashed to 2,1 MacPro
Best regards,
David
Hello my friends,
I just created a SFOTT usb stick with the 10.10.2 installer and manually copied the Kernel to the Kernels folder.
It booted just fine and installed Yosemite.
After the restart it just shows the white Apple logo and freezes there. I did a reinstall etc. but after a successful installation it freezes on the white apple logo and does not boot any further.
Has anyone experienced something similar or have a clue what is happening here?
I'm on a 1,1 MacPro flashed to 2,1 MacPro
Best regards,
David
So I figured out how to solve my own issue.. For those who ran into updating to 10.10.2 without realizing it would break the boot.efi file follow the following steps.
1, On a separate drive, install 10.10
2, run PikeYoseFix to patch 10.10 and ready it for 10.10.2
3, update to 10.10.2 from app store
4, locate broken boot.efi file on original drive. YOURDRIVE/System/Library/CoreServices/boot.efi
5, open terminal run command "sudo chflags nouchg" followed by a single space. DO NOT PRESS ENTER. Drag the broken boot.efi to the terminal window and press enter.
6, Now copy and replace new boot.efi to old boot.efi location
7,Restart
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