Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've made it easier to update 10.9.2.

Instead of following the instructions above, just install the attached package. It will put the LaunchDaemon out there.

So here are the new steps.

1. Install TiamoMacProFix.pkg (attached to this thread)
2. Reboot (yes this is necessary)
2a. Reboot again if you want to then verify the date/time stamp on the two boot.efi files (/usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi) are updated properly. They won't be updated until the second shutdown/reboot. (optional step but a good one if you want to verify the files are updating properly)
3. Install 10.9.2 update.
4. ...
5. Profit.

Consider this a version .1 beta package. I'll work on building a new package file that won't require a reboot and will do additional checks (to make sure you're not installing this on something like a MacPro3,1+ and that you're definitely using 10.9.0 or greater, etc).

Again, after you install this package you can freely update to 10.9.2 and not worry about having to manually replace boot.efi files.

This was tested on a MacPro1,1 with a fresh install of 10.9.2 and updated using the AppStore on a single drive.
This was NOT tested on a fusion drive.


This Fixed Work like a Charm, I updated 10.9.2 smoothly, Thanks for writing this nice script for people like me who are lazy.. and hate writing terminal commands,etc..

I would recommend everybody get this emergency update security fix, and upgrade to 10.9.2 ASAP!.
 
Another MacPro1,1 rescued

Greetings from Italy to you all. This is my first post: I read this thread from the very start and I learned a lot, thanks to all the forum gurus and especially to Tiamo fo his awesome work on the "magic" boot.efi.

I'm happy to report another successful installation on a MacPro1,1 equipped with GeForce 8800GT (flashed) and 12 Gb RAM. I bought a new SSD and I connected to my MBP6,2 through an external USB-SATA case; I installed Mavericks and applied 10.9.2 update, then I replaced both boot.efi (using a little trick… I selected the external drive, then "Get Info" and checked “Ignore ownership on this volume”) and edited PlatformSupport.plist (I'm not sure if this step was required). Then i put the SSD into my Mac Pro and started holding the Alt-key: it booted smooth and fast :D

I'll try to find some time in the next few days to check it out, hoping not to find audio issues: anyway both SL and Lion are still there, just in case.

It seems too good to be true… I spent so much time fiddling with USB thumb drives and installers, that I just can't believe it was THAT easy, you know what I mean ;)
 
Last edited:
<snip introduction>

It seems too good to be true… I spent so much time fiddling with USB thumb drives and installers, that I just can't believe it was THAT easy, you know what I mean ;)

I very much agree! From Tiamo with the initial bootloader, to oemden with SFOTT to make the thumb drive, to tobyg with his app, it has developed into a complete, fully functional solution for the Mac Pros of 2006 and 2007. Lots of people can get on and off this installation train at their level of expertise.

My experience was with using chameleon to run ML then Mavericks, then I used Tiamo's bootloader as he detailed in his post at the top of page 2 of this thread. In the meantime I have tested all the other installation methods in this thread, I still cannot believe that SFOTT is so easy!

Thanks for stopping by jantoman and relating your experiences with Tiamo's bootloader.
 
In the meantime I have tested all the other installation methods in this thread, I still cannot believe that SFOTT is so easy!

Yes. And replacing boot.efi on a supported Mac installation is even easier... but I'm wondering if a proper installation on the target Mac would be safer. That's a big question, in fact. Anybody could clarify it? Thanks in advance.
 
Ok, let me try to explain, and excuse my clumsy English :eek:

I installed Mavericks on a Mac (MP1,1) starting from a different Mac (MBP 6,2) and I'm quite surprised that it's working at all… Seems like the Installer have created an "universal" OS that runs on both machines despite the hardware differences.

I thought the Installer would check the machine and pick up the correct piece of software for any specific device. But maybe I'm wrong... or just too old and confused by memories of Apple legacy OS (does anyone remember System Enablers?) :apple:

In other words, my concern is that my Mac Pro OS could be "incomplete" because it's been installed on a different Mac. Maybe it's a dumb question, but I'll appreciate if someone could give me a hint.
 
Ok, let me try to explain, and excuse my clumsy English :eek:

I installed Mavericks on a Mac (MP1,1) starting from a different Mac (MBP 6,2) and I'm quite surprised that it's working at all… Seems like the Installer have created an "universal" OS that runs on both machines despite the hardware differences.

I thought the Installer would check the machine and pick up the correct piece of software for any specific device. But maybe I'm wrong... or just too old and confused by memories of Apple legacy OS (does anyone remember System Enablers?) :apple:

In other words, my concern is that my Mac Pro OS could be "incomplete" because it's been installed on a different Mac. Maybe it's a dumb question, but I'll appreciate if someone could give me a hint.

Ah! Thanks, I understand now :)

No, it is my experience that Mac OS X now just installs a universal system no matter what it is installed upon (MacBook Air -> Mac Pro), unlike the System 7, 8, and 9 days (I started with System 7 in 1992…).

There are drivers on the MacBook Air that I am writing this on, for devices that could NEVER be installed within, or attached to it. This could be argued to be somewhat disk space inefficient, but in these times of relatively cheap disk space, apparently it does not matter so much.

The side effect of all this of course, is that we can attach our MPs in target disk mode and install OS X easily.
 
I've made it easier to update 10.9.2.

Instead of following the instructions above, just install the attached package. It will put the LaunchDaemon out there.

So here are the new steps.

1. Install TiamoMacProFix.pkg (attached to this thread)
2. Reboot (yes this is necessary)
2a. Reboot again if you want to then verify the date/time stamp on the two boot.efi files (/usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi) are updated properly. They won't be updated until the second shutdown/reboot. (optional step but a good one if you want to verify the files are updating properly)
3. Install 10.9.2 update.
4. ...
5. Profit.

Consider this a version .1 beta package. I'll work on building a new package file that won't require a reboot and will do additional checks (to make sure you're not installing this on something like a MacPro3,1+ and that you're definitely using 10.9.0 or greater, etc).

Again, after you install this package you can freely update to 10.9.2 and not worry about having to manually replace boot.efi files.

This was tested on a MacPro1,1 with a fresh install of 10.9.2 and updated using the AppStore on a single drive.
This was NOT tested on a fusion drive.

Hey thanks for the info. I had already updated may mac pro1,1 to 10.9.2 updating both files manually. Just for the heck of it I tried using Tiamos Mac Pro Fix app you posted and what I noticed is that it updated the boot.efi file on core services but the boot.efi file at /usr/standalone/i386 remained unchanged. Is it because I already was running the updated Mavericks 10.9.2?

And by the way BIG Thanks.. to all of you guys for sharing your knowledge it really helps us guys that are not as smart. I am really glad I joined this forum its been a life saver....
 
Hey thanks for the info. I had already updated may mac pro1,1 to 10.9.2 updating both files manually. Just for the heck of it I tried using Tiamos Mac Pro Fix app you posted and what I noticed is that it updated the boot.efi file on core services but the boot.efi file at /usr/standalone/i386 remained unchanged. Is it because I already was running the updated Mavericks 10.9.2?

And by the way BIG Thanks.. to all of you guys for sharing your knowledge it really helps us guys that are not as smart. I am really glad I joined this forum its been a life saver....

No it should update both. Are you using a fusion drive?
You rebooted, right?
 
Updated with no problem what so ever on a Mac Pro 1,1 to 10.9.2 simply by installing the combo and restarting in Lion and replacing the boot efi

I also got rid of my Nvidia 8800GT as this card is to old and caused crashing in lots of apps like Pixelmator. Applying a drop shadow on text would crash the app everytime. My system also crashed a lot using iMovie.

I use a flashed ATI 5770 to power 2 monitors and the 8800GT to power a third. I swapped the old Nvidia for a newer and dead cheap GTX610 which worked out the box and stopped the crashing. It also draw little power and is silent.

If you have a 8800GT and experience crashing look for a replacement, it's just too old and out of date
 
Hey Guys this might be a stupid question but do we have to Change the boot.efi every time apple releases a update?

When OSX 10.9.3 come out do i have to do the same process again?
 
Hey Guys this might be a stupid question but do we have to Change the boot.efi every time apple releases a update?

When OSX 10.9.3 come out do i have to do the same process again?

If the update contains an EFI file, then yes, we will have to replace it with Tiamos EFI. If you go on the previous page you can find the recipe on how to script this so it happens automatically at every boot, meaning you shouldn’t have to worry about this and can update any way (App Store or Combo) you please.
 
No it should update both. Are you using a fusion drive?
You rebooted, right?

Sorry I got busy and was away from my computer awhile... To answer your question Yes.. I rebooted twice like indicated but it only changed the boot.efi file in core services and not /usr/standalone/i386 I also noticed there were two boot.efi files in /usr/standalone/i386 location. I don't know if they were left there from when I was doing the manual replacement from before I deleted one of them and rebooted and everything is working fine. I will try running Tiamos MAC Pro fix again and see if it replaces both files this time.
 
Sorry I got busy and was away from my computer awhile... To answer your question Yes.. I rebooted twice like indicated but it only changed the boot.efi file in core services and not /usr/standalone/i386 I also noticed there were two boot.efi files in /usr/standalone/i386 location. I don't know if they were left there from when I was doing the manual replacement from before I deleted one of them and rebooted and everything is working fine. I will try running Tiamos MAC Pro fix again and see if it replaces both files this time.

The fix puts a copy of tiamo's boot.efi in /usr/standalone/i386 called boot.efi.tiamo. It then copies that boot.efi.tiamo to /usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi every time the system is rebooted.

Reinstalling the PKG won't put another copy of the boot.efi out there. The copy is done by the LaunchDaemon file in /Library/LaunchDaemons called com.tiamo.macprofix.plist.

Are you running a fusion drive?
 
The fix puts a copy of tiamo's boot.efi in /usr/standalone/i386 called boot.efi.tiamo. It then copies that boot.efi.tiamo to /usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi every time the system is rebooted.

Reinstalling the PKG won't put another copy of the boot.efi out there. The copy is done by the LaunchDaemon file in /Library/LaunchDaemons called com.tiamo.macprofix.plist.

Are you running a fusion drive?

Im not running a fusion drive I have Mavericks on an SSD drive,
So its okay to see both the original boot.efi file and boot.efi.tiamo residing at /usr/standalone/i386 On the /system/library/coreservices side it just shows me that the boot.efi file was modified at the time I ran Tiamos fix.
 
I've made it easier to update 10.9.2.

Instead of following the instructions above, just install the attached package. It will put the LaunchDaemon out there.

So here are the new steps.

1. Install TiamoMacProFix.pkg (attached to this thread)
2. Reboot (yes this is necessary)
2a. Reboot again if you want to then verify the date/time stamp on the two boot.efi files (/usr/standalone/i386/boot.efi and /System/Library/CoreServices/boot.efi) are updated properly. They won't be updated until the second shutdown/reboot. (optional step but a good one if you want to verify the files are updating properly)
3. Install 10.9.2 update.
4. ...
5. Profit.

Consider this a version .1 beta package. I'll work on building a new package file that won't require a reboot and will do additional checks (to make sure you're not installing this on something like a MacPro3,1+ and that you're definitely using 10.9.0 or greater, etc).

Again, after you install this package you can freely update to 10.9.2 and not worry about having to manually replace boot.efi files.

This was tested on a MacPro1,1 with a fresh install of 10.9.2 and updated using the AppStore on a single drive.
This was NOT tested on a fusion drive.

Worked perfectly thanks a bunch!!
 
@tobyg

Quick question... would running your package work on a system that is currently running 10.9.1 using Chameleon?

This process: install your package, reboot, reset nvram (to kick the mac out of legacy boot), let the machine boot using Tiamo's boot.efi files.
 
@tobyg

Quick question... would running your package work on a system that is currently running 10.9.1 using Chameleon?

This process: install your package, reboot, reset nvram (to kick the mac out of legacy boot), let the machine boot using Tiamo's boot.efi files.

I've never tried it. But if the process of converting to Tiamo's method from Chameleon just involves replacing the boot.efi files and rebooting essentially, then I suspect it would. You'd have to reboot twice though. Reboot once after installing the software and then reboot once more for the software to replace the files after the 2nd reboot.

But I can't guarantee anything. I've never used Chameleon on a real Mac Pro. I never attempted to go beyond 10.7 on a real MacPro1,1 or 2,1 prior to Tiamo's method (the chameleon method always seemed very half-assed, I never wanted to make my Mac Pro a Hackintosh)
 
Hi everyone,
I did the update to 10.9.2 before installing the new patch. And now it won't boot,
I'm screwed up with a question mark in a folder who flashing.

I wanna know if I need to make a fresh install of OS X 10.9 and apply patch to finally install 10.9.2.

Or if a solution to recover my actual "corrupt" 10.9.2 exist.

Regards,
Jonathan
 
Hi everyone,
I did the update to 10.9.2 before installing the new patch. And now it won't boot,
I'm screwed up with a question mark in a folder who flashing.

I wanna know if I need to make a fresh install of OS X 10.9 and apply patch to finally install 10.9.2.

Or if a solution to recover my actual "corrupt" 10.9.2 exist.

Regards,
Jonathan

You either need to boot using an older 10.6/10.7 install, boot into target disk mode or remove and attach the 10.9.2 drive to another Mac using USB. Then replace the boot.efi files. Then boot to the 10.9.2 drive on the Mac Pro. It's not corrupted it just can't find a supported boot.efi file.

----------

I've never tried it. But if the process of converting to Tiamo's method from Chameleon just involves replacing the boot.efi files and rebooting essentially, then I suspect it would. You'd have to reboot twice though. Reboot once after installing the software and then reboot once more for the software to replace the files after the 2nd reboot.

But I can't guarantee anything. I've never used Chameleon on a real Mac Pro. I never attempted to go beyond 10.7 on a real MacPro1,1 or 2,1 prior to Tiamo's method (the chameleon method always seemed very half-assed, I never wanted to make my Mac Pro a Hackintosh)

Ok thanks. I'll have my friend be the guinea pig since he is still using Chameleon on his 1,1. I already converted to Tiamos method before 10.9.1.
 
You either need to boot using an older 10.6/10.7 install, boot into target disk mode or remove and attach the 10.9.2 drive to another Mac using USB. Then replace the boot.efi files. Then boot to the 10.9.2 drive on the Mac Pro. It's not corrupted it just can't find a supported boot.efi file.

Ok, but after that, I'll be able to boot even if I haven't run the new TiamoMacProFix.pkg?

Regards,
Jonathan
 
Ok, but after that, I'll be able to boot even if I haven't run the new TiamoMacProFix.pkg?

Regards,
Jonathan

If you manually replaced the boot.efi files properly then yes. That's how I upgraded to 10.9.2 before his package was available. I used an existing 10.7 install I have.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.