Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Hennesie2000, did you see my message about revising your guide to use the "createinsallmedia" command to replace many steps?

Testing it out now... I assume it will work and if it saves steps I will certainly update my guide. I am more of a manual method type of person because I like to know what is going on but will happily simplify things for others.

In response to changing the return false to return true, I have tried that before and it didn't work for me but perhaps it was an issue with quotation marks when entering the board IDs. It's been a while.

----------

new commit is out: 129ea3ca16 (it's not compiling...).

We should just wait. Pike is making a lot of changes right now and it is back to verbose mode for testing.
 
Last edited:
I've tested the 'Boot_Verbose' version: Compiling was ok. Boots the patched Installer (5 times PIKE: Kernel cache located), doesn’t boot the installed Yosemite (10 times PIKE: Kernel cache located, hangs with a underscore then), doesn’t boot ML as well as Mavericks.
 
Last edited by a moderator:
I've tested the 'Boot_Verbose' version: Compiling was ok. Boots the patched Installer (5 times PIKE: Kernel cache located), doesn’t boot the installed Yosemite (10 times PIKE: Kernel cache located, hangs with a underscore then), doesn’t boot ML as well as Mavericks.

exactly the same over here. how did you get the error message??? I had to use the SloMo cam of the iPhone to capture it.
 
Hennesie2000, did you see my message about revising your guide to use the "createinsallmedia" command to replace many steps?

After testing, using the command createinstallmedia does not work in this situation because we need to be able to modify the boot.efi files. When you use that command you end up with a read-only InstallESD.dmg that has a read-only hidden BaseSystem.dmg where those boot.efi files are located.
 
After testing, using the command createinstallmedia does not work in this situation because we need to be able to modify the boot.efi files. When you use that command you end up with a read-only InstallESD.dmg that has a read-only hidden BaseSystem.dmg where those boot.efi files are located.

just as I predicted ;)
 
I don't think anyone has been able to. I personally have not tried.
nope, it's not working. no matter what I try, it seems impossible to boot the recovery partition. I spent lots of time trying this and that, but no success... drives me bonkers, not knowing what the cause is.

Haaaaaa..... Ok I was afraid to be the stupid...

Ok so I'll post Sfott as is, and I'll see if I can cheat for the Recovery.
I have ideas but it's gona take some time with this mini...
And I've prepared code long time ago I did not work on for ages. It's gonna be time to go back on it.

EDIT : just saw the new boot.efi testing right away.
 
After testing, using the command createinstallmedia does not work in this situation because we need to be able to modify the boot.efi files. When you use that command you end up with a read-only InstallESD.dmg that has a read-only hidden BaseSystem.dmg where those boot.efi files are located.

Hmmm this is the first method I tried back when I started SFOTT for Mavericks.

I did patch all the Dmgs - BaseSystem.dmg inside InstallESD.dmg AND of course InstallESD.dmg.
I Patched all plist and Mpkg etc.. but did not succeed. It booted and Installer launched but then told me the installer was "corrupted" (or something like that) and asked to redownload the installer.... so I gave up.

However, I'l give a second try to the method as I now, for Yosemite - add the checksum (even if I'm quite sure I did it at least one or two last year)

First I'll post Sfott as is and "forget" about the Recovery for now.
Then I'll try the recovery stuff and the createinstallmedia
 
Hmmm this is the first method I tried back when I started SFOTT for Mavericks.

I did patch all the Dmgs - BaseSystem.dmg inside InstallESD.dmg AND of course InstallESD.dmg.
I Patched all plist and Mpkg etc.. but did not succeed. It booted and Installer launched but then told me the installer was "corrupted" (or something like that) and asked to redownload the installer.... so I gave up.

However, I'l give a second try to the method as I now, for Yosemite - add the checksum (even if I'm quite sure I did it at least one or two last year)

First I'll post Sfott as is and "forget" about the Recovery for now.
Then I'll try the recovery stuff and the createinstallmedia

I am going to leave my guide as is because it is easier for someone following it to not have to worry about patching dmg's and it works.
 
Edited: Sorry, I see the subsequent posts now.

----------

In response to changing the return false to return true, I have tried that before and it didn't work for me but perhaps it was an issue with quotation marks when entering the board IDs. It's been a while.

Unlike the "createinstallmedia" suggestion, I've actually tried this. It works fine. There are no quote issues - you delete the ENTIRE contents of that function, and replace them with a "return true;".
 
So is it possible to safely put Yosemite on a Mac Pro 1,1 or not?


44 pages and I don't have a clue.

From what I understand, yes it's possible. But the recovery partition doesn't work (yet). I never had to use it once since I installed Mavericks so I don't see why that would change with Yosemite ;)

As soon as Yosemite is available on the Canadian store, I'll give it a go.

You might find this thread helpful as well: https://forums.macrumors.com/threads/1761432/
 
Were you running the previous OS using a bootloader in Legacy mode? You cannot use the bless command when using Clover or Chameleon.

I had tried it with my MacBook as well without success.. Honestly I think it was the USB drive. As others have noted, these early models of MacPro's are pretty picky about booting from USB drives, even using key commands on booting I've had issues in the past.

Regardless I have all my systems running the latest build of the beta, of course on the day that the actual version comes out. The only issue I have is an error reading PCI cards (not sure why but this hasn't worked since Mavericks). iMessage gave me the support number this time, now it is working without issue.
 
I can totally understand the "can we" mentality of everyone making this happen, but what about the "should we" aspect?


Is Yosemite on a Mac Pro 1,1 actually worth doing? Does it run well? Is it stable?

What are the pitfalls?
 
I can totally understand the "can we" mentality of everyone making this happen, but what about the "should we" aspect?


Is Yosemite on a Mac Pro 1,1 actually worth doing? Does it run well? Is it stable?

What are the pitfalls?

Yes can someone quickly tell us how it runs, as I'm backing up my stuff as we speak ready to go.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.