Living with auto updates would be easier if you wouldn't miss the info about TiamoMacProfix and PikeYoseFix
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
Living with auto updates would be easier if you wouldn't miss the info about TiamoMacProfix and PikeYoseFix
I've borrowed a MacBook Pro to install Yosemite on my Mac Pro 1.1 ssd hard drive no problem and download the pikes efi file, but I can't work out how to change the boot.efi files ? I've looked all over this thread and everyone just says to copy over the files but how the hell do u do it ? Is it all done in terminal ? Sorry for being so thick but I can't find a tutorial or video to show me , if anybody knows or can point me to a link I would be very great full
Others with more experience will hopefully confirm this, but If you have another Mac I think you should be able to install the Patched installer using Target Disk mode to the Disk of your Mac Pro and avoid the need for Terminal or swapping the efi files - the patched version already has the NEW efi files changed. No need for SFOTT either. Yosefix is still required to future proof updates but that is easy to install after Yosemite is installed but BEFORE you try to upgrade.
Terminal is only needed to make files visible and unlocked - I didn't use this method as I couldn't unlock one of the files and the patched installer was an easier option. Search for restoring the installer to a USB stick in Disk Utility and you can do it that way. It can look a bit confusing but isn't that hard to find the information.
This may help...
http://osxdaily.com/2014/10/16/make-os-x-yosemite-boot-install-drive/
I did this just yesterday. I had a 100% working Yosemite install on a regular drive and used Carbon Copy Cloner to clone that drive to a Patriot SSD. OS X booted without any hassle, and in less than half the time it usually takes too :-D
Last edited:
wierd HOST file in system ( i changed it to the usual, but this is how it is in Pikes Yosemite installer directory as well) :
starts from :
œ˙Ì˛Ä Ö H__PAGEZEROx__TEXT``__text__TEXT$π
$Ä__stubs__TEXTfi"∫fi"Ä__stub_helper__TEXTò&Fò&Ä__cstring__TEXT‡,°Â‡,__const__TEXTêÃê__unwind_info__TEXT\'H+\'__eh_frame__TEXT®RP
®Rx__DATA`∞`ê__got__DATA`P`ü__nl_symbol_ptr__DATAP`P`©__la_symbol_ptr__DATA``¯``´__const__DATA`ep
`e__data__DATA–oxz–o__bss__DATAPÍ‘__common__DATA0pH__LINKEDIT`"Ä0ıpxıH¿∏ì@ßßÿ∂xP•∞±J /usr/lib/dyldbÙ˙,ÖΩ;Yíç2Œì$
<the rest is in the attachment>
starts from :
œ˙Ì˛Ä Ö H__PAGEZEROx__TEXT``__text__TEXT$π
$Ä__stubs__TEXTfi"∫fi"Ä__stub_helper__TEXTò&Fò&Ä__cstring__TEXT‡,°Â‡,__const__TEXTêÃê__unwind_info__TEXT\'H+\'__eh_frame__TEXT®RP
®Rx__DATA`∞`ê__got__DATA`P`ü__nl_symbol_ptr__DATAP`P`©__la_symbol_ptr__DATA``¯``´__const__DATA`ep
`e__data__DATA–oxz–o__bss__DATAPÍ‘__common__DATA0pH__LINKEDIT`"Ä0ıpxıH¿∏ì@ßßÿ∂xP•∞±J /usr/lib/dyldbÙ˙,ÖΩ;Yíç2Œì$
<the rest is in the attachment>
Last edited:
Hi there, I'm brand new to this, so hoping someone can help me,
I have a Mac Pro 1,1 running Lion,
32GB Ram
Ati 5770
These are both recent upgrades I've made myself.
So far I have been unsuccessful with my attempts to upgrade my 1,1 mac pro to yosemite. I was following the PDF. Guide which led me to this forum. Everything was going quite well until I rebooted having installed chameleon. I had a kernel panic and now have the message in Bios,
memory allocation error! Addr : 0xdeadbeef, Size : 0x0, File:ati.c, Line 1834
This is a a non recoverable error! System HALTED!!!!
I'm by no means an expert and new to this whole process although I've done a fair bit of research before attempting the upgrade. I haven't a clue when it comes to doing anything in BIOS.
Any help would be great, I'm beginning to worry I've somehow bricked my machine !
I have a Mac Pro 1,1 running Lion,
32GB Ram
Ati 5770
These are both recent upgrades I've made myself.
So far I have been unsuccessful with my attempts to upgrade my 1,1 mac pro to yosemite. I was following the PDF. Guide which led me to this forum. Everything was going quite well until I rebooted having installed chameleon. I had a kernel panic and now have the message in Bios,
memory allocation error! Addr : 0xdeadbeef, Size : 0x0, File:ati.c, Line 1834
This is a a non recoverable error! System HALTED!!!!
I'm by no means an expert and new to this whole process although I've done a fair bit of research before attempting the upgrade. I haven't a clue when it comes to doing anything in BIOS.
Any help would be great, I'm beginning to worry I've somehow bricked my machine !
BIOS? - do you mean Terminal?
P1 of this thread has all the info you need. Chameleon is not needed - I think it was used in the early stages of getting past Lion on these Macs, but has not been required since SFOTT or other methods were created by some pretty smart people. I recommend you read a good part of this whole thread before jumping in - any issue you have will already have been experienced and probably resolved.
I tried to delete the bootcache.plist and the problem doesn't occur anymore. However I decided to investigate a little bit and with the help of a slow motion video taken with the iPhone I managed to capture the instant just before the first reboot.
Apparently the problem is that boot.efi is not in the boot cache, prelinked kernel or something like that.
I played a little with kextcache but I haven't figured out how to solve the issue yet.
I finally managed to solve the "double boot" issue by simply booting OS X into safe mode and then restarting (keep pressing shift until you get to the login window, even during the reboot, you should see "Safe" something written in red in the menu bar).
It seems that this procedure invalidates and rebuilds all the caches the system uses, including the boot cache that was my issue.
apple "support" has officially given up on my Message/Facetime problem, after numerous attempts to lift the formal ban and appealing to engineering department they returned my call 2 weeks later with refuse to assist further based on "obsloleteness" of macpro1.1(2.1)
I wonder if there is a way to change my hardware credantial to more acceptable without using clover/chameleon type of installation?
I wonder if there is a way to change my hardware credantial to more acceptable without using clover/chameleon type of installation?
Last edited:
P1 of this thread has all the info you need to do this. I have MP 1.1 upgraded to 2.1 and running 10.10.4 with Messages and FT working OK. Apple don't support this but it doesn't mean it isn't possible - they are not going to start advising you to change boot efi files on a 9 year old Mac. I used the Pre patched installer.apple "support" has officially given up on my Message/Facetime problem, after numerous attempts to lift the formal ban and appealing to engineering department they returned my call 2 weeks later with refuse to assist further based on "obsloleteness" of macpro1.1(2.1)
I wonder if there is a way to change my hardware credantial to more acceptable without using clover/chameleon type of installation?
apple "support" has officially given up on my Message/Facetime problem, after numerous attempts to lift the formal ban and appealing to engineering department they returned my call 2 weeks later with refuse to assist further based on "obsloleteness" of macpro1.1(2.1)
I wonder if there is a way to change my hardware credantial to more acceptable without using clover/chameleon type of installation?
Also running Yosemite on a 1,1 upgraded to 2,1. Used the app store 10.10.4 and simply replaced the boot.efi.
My FaceTime and iMessage work 100% and calls appear on the Pro as it does on my Macbook Pro and iPad when ever my iPhone rings.
I used the patched one as well, I would assume they could lift the ban on some "deeper" level, because after ban gets lifted by regular apple assistant it reappears somehow in their system. I'm not asking them to do anything else , I don't need technical support, i had tried all the usual remedies that mentioned here like deleted setting files, resetting pram and logging as guest admin user, none of those had effect.
I need the ban to be lifted permanently, they are too cautios about their hardware ID's and it does more harm than good, and now all the hackintoshes are good to go but my genuine old mac pro is banned, not fair at all.
Last edited:
Hmm...
Guys, those who have flashed 1.1 to 2.1 and have Messages running fine:
could you try to run ImessageDebug tool:
http://mac.softpedia.com/get/System-Utilities/iMessageDebug.shtml
and tell me if it shows "System-ID: failed" or not.
It shows Failed on my mac pro
==============THIS IS HOW IT SHOWS UP AT MINE ==========
Model: MacPro2,1
Board-id: Mac-F4208DC8
SerialNumber: CK70904MUPZ
Hardware UUID: 00000000-0000-1000-8000-0017F2071DCC
System-ID: failed
ROM: 0016cb790f4e
BoardSerialNumber: 9N705006FVNBA
Gq3489ugfi: 28f0b13d1f7352966e38f95f24744e0619
Fyp98tpgj: d5531b0be2e851c0d76612aa86e8db5dd0
kbjfrfpoJU: c454b9af0ee0d6302dbcfdaa6cda4f1cae
oycqAZloTNDm: 837784632293e03a5055587aaf4e027828
abKPld1EcMni: 1c56124cd2bb3ed8a877fb13551b8144e3
Guys, those who have flashed 1.1 to 2.1 and have Messages running fine:
could you try to run ImessageDebug tool:
http://mac.softpedia.com/get/System-Utilities/iMessageDebug.shtml
and tell me if it shows "System-ID: failed" or not.
It shows Failed on my mac pro
==============THIS IS HOW IT SHOWS UP AT MINE ==========
Model: MacPro2,1
Board-id: Mac-F4208DC8
SerialNumber: CK70904MUPZ
Hardware UUID: 00000000-0000-1000-8000-0017F2071DCC
System-ID: failed
ROM: 0016cb790f4e
BoardSerialNumber: 9N705006FVNBA
Gq3489ugfi: 28f0b13d1f7352966e38f95f24744e0619
Fyp98tpgj: d5531b0be2e851c0d76612aa86e8db5dd0
kbjfrfpoJU: c454b9af0ee0d6302dbcfdaa6cda4f1cae
oycqAZloTNDm: 837784632293e03a5055587aaf4e027828
abKPld1EcMni: 1c56124cd2bb3ed8a877fb13551b8144e3
Last edited:
That looks like what my Mac Pro UUID looked like. A bunch of zeros followed by your MAC address.
Never had an issue getting it activated, so I never ran the debug tool on it. Though I had to call about once a month and get it re-authorized.
On a hackintosh now and have zero issue with all user generated values.
Could you try running it on any Yosemite machine? it's a small terminal app, no installation.
http://mac.softpedia.com/get/System-Utilities/iMessageDebug.shtml
When I run it on my MacBook 6,2 it doesn't look like that. It looks more similar to something generated by typing uuidgen into terminal.