Tonight, I'm going to try this. I'm also going to take out my old video card that's still taking up a PCIe slot.
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.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
Tonight, I'm going to try this. I'm also going to take out my old video card that's still taking up a PCIe slot.
...10.11.4 update went smooth directly from the App Store (I'm using CapitanPikeFix)
After the first restart (once the update completed) I noticed an incorrect report about my RAM. System profiler said 14 GB - I have 16. Not to worry thgough...I shut down the mac, thought a shot of air duster couldn't hurt in the memory department, reset my SMC, restarted, and now everything is back to normal. I never had this issue before, I guess it's not a big deal, but I wonder what could have caused it. Everything is running fine now.
After the first restart (once the update completed) I noticed an incorrect report about my RAM. System profiler said 14 GB - I have 16. Not to worry thgough...I shut down the mac, thought a shot of air duster couldn't hurt in the memory department, reset my SMC, restarted, and now everything is back to normal. I never had this issue before, I guess it's not a big deal, but I wonder what could have caused it. Everything is running fine now.
This issue is being reported more widely at AppleInsider and indeed at MacRumors as being a server-side (Apple) issue
http://iphone.appleinsider.com/arti...-facetime-for-mac-users-including-new-owners-
https://www.macrumors.com/2016/03/23/mac-users-facetime-imessage-login-issues/
I'm not so sure that it's the same issue. The issue you mention is from folks who a) upgraded to 10.11.4 and b) couldn't log into FaceTime or iMessage.
I have not upgraded to 10.11.4. And I haven't tried to log into iMessage or FaceTime. I don't believe I've see folks with this issue mention a similar problem with the App Store.
I'll blow away the account folder tonight and have it get rebuilt. We'll see if that does the trick.
And rm'ing the entire contents of my account folder did the trick. I opened up the App Store. Now I can try to update to 10.11.4. Since I installed boot64, I'm not expecting any issues.
[doublepost=1458865353][/doublepost]
I'm trying the route with no specific SIP disabling. Just going to rely on Boot64. I'll let you know how it goes.
And done. Cake. I went downstairs to eat dinner instead of watching it. Up and running on 10.11.4 with no specific SIP disabling. Just Boot64. h/t to rthpjm.
I just want to thank you for all your hard work on this project. Pikify3.1 worked like a charm and upgraded my hacked Yosemite to El Capitan without a single hitch. You don't know how much this means to me to have my Quad-core Xeon MacPro 1,1 working with the latest OS. Thank you, thank you, thank you!
That's weird because I am on a Quad-core Xeon MacPro 1,1 running a Pikified El Capitan and my FaceTime works like a charm.
This issue has been identified and has nothing to do with the method to boot ElCapitan on 1,1/2,1 with a modified boot.efi, but is a bug in the FaceTime/iMessage http://9to5mac.com/2016/03/23/cant-log-in-to-imessage-facetime-os-x-10-11-4/
[doublepost=1459009138][/doublepost]Superb work! Just used Pikify3.1.8 to successfully update 10.11.3 to .4. Easy as can be. Brilliant! Thank you!
hello!
I want to tell my experience. I have a Mac Pro 1.1 8 core, that upgrade to 2.1. I use this tutorial to install elcapitan :
At the firs moment everything works fine, include FaceTime. Today I'm upstate to 10.11.4, change boot.efi and works fine, even FaceTime. I use pike's 3.1 . Not pike 3.1.8
Maybe this post it's repeat. But I want to share my experience .
I want to tell my experience. I have a Mac Pro 1.1 8 core, that upgrade to 2.1. I use this tutorial to install elcapitan :
Maybe this post it's repeat. But I want to share my experience .
How can I do this without the ability to re-download the efi files. I can't seem to boot the pikify stick anymore and I feel like I'm totally out of options.
The pikify bootstick has to be blessed prior to use it again. It is described earlier in this this thread. (around page 55, if I'm remembering it right)
EDIT: I found the terminal line to bless the pikify stick:
Code:
sudo bless --folder /Volumes/Install\ OS\ X\ El\ Capitan/.IABootFiles --file /Volumes/Install\ OS\ X\ El\ Capitan/.IABootFiles/boot.efi
Last edited:
Hia all,
I have just tried to upgrade to 10.11.4 and like every one else I have found my self in recovery mode. :-( Unlike even one else my programming skills are non existent. With much kind help from rthpjm I was able to get to 10.11.3 using his
pikify3.1 and his fantastic instructions in post #1569
I admit i am completely lost on post #1989
But post #1997 seems reasonable enough, I have downloaded the EFI files, from the top of the page of http://piker-alpha.github.io/macosxbootloader/ but I'm not sure which one to put in which folder.
Do i put the boot.efi in /System/Library/CoreServices/boot.efi
and then the boot_grey.efi (after changing the name to boot.efi) into /usr/standalone/i386/boot.efi
Over righting the existing boot.efi files in there?
I can boot off my old 10.7.5 HD and find the folders using EasyFind, probably not the most efficient way but seems to work.
Would some one be kind enough to put in to idiot terms what i need to do?
Thank you.
I have just tried to upgrade to 10.11.4 and like every one else I have found my self in recovery mode. :-( Unlike even one else my programming skills are non existent. With much kind help from rthpjm I was able to get to 10.11.3 using his
pikify3.1 and his fantastic instructions in post #1569
I admit i am completely lost on post #1989
But post #1997 seems reasonable enough, I have downloaded the EFI files, from the top of the page of http://piker-alpha.github.io/macosxbootloader/ but I'm not sure which one to put in which folder.
Do i put the boot.efi in /System/Library/CoreServices/boot.efi
and then the boot_grey.efi (after changing the name to boot.efi) into /usr/standalone/i386/boot.efi
Over righting the existing boot.efi files in there?
I can boot off my old 10.7.5 HD and find the folders using EasyFind, probably not the most efficient way but seems to work.
Would some one be kind enough to put in to idiot terms what i need to do?
Thank you.
Doesn't the video in post 2015 help you? shows the easy way to change the boot.efi files.
Nevertheless, here is a quick "Noob Guide"
You don't need to download any files, as long as you have the pikify3.1 folder. In this folder you will find a file called boot.efi, that is the most useful file, nothing else needed.
1. Boot with 10.7.5 (Or any other system), search for the file boot.efi in the pikify3.1 folder. You will need it! Maybe it is a good idea to copy it to your desktop to have easy access to this file....
2. Open Finder, navigate to System/Library/CoreServices from your ElCapitan Hard drive. (You don't need any app to get there, just press the alt-key when clicking "go to" in finder. Select the System folder and it will open.
3. Open Terminal and type sudo chflags nouchg (with a space at the end) Do not press enter!!!!!
4. Drag and drop the file "boot.efi" from the finder window into the terminal window. Now press enter!
5. Type your password (it's invisible in terminal) and press enter. Now your boot.efi isn't protected anymore and you can drag the boot.efi file you put on the desktop into the folder. You have to answer the safety question and then it's almost done.
6. Last you have to re-protect the boot.efi again (nearly the same procedure like unprotecting it). Type in Terminal: sudo chflags uchg (plus space) and drag the file into terminal window. Then press enter again and its protected again.
The same boot.efi file has to be altered in the usr/standalone/i386/ folder. This file isn't protected, you can simply drag the pikify-version into the finder window and answer the security question.
Now you can reboot with ElCapitan and it will work perfectly on your MacPro 1.1
Doesn't the video in post 2015 help you? shows the easy way to change the boot.efi files.
Nevertheless, here is a quick "Noob Guide"
You don't need to download any files, as long as you have the pikify3.1 folder. In this folder you will find a file called boot.efi, that is the most useful file, nothing else needed.
1. Boot with 10.7.5 (Or any other system), search for the file boot.efi in the pikify3.1 folder. You will need it! Maybe it is a good idea to copy it to your desktop to have easy access to this file....
2. Open Finder, navigate to System/Library/CoreServices from your ElCapitan Hard drive. (You don't need any app to get there, just press the alt-key when clicking "go to" in finder. Select the System folder and it will open.
3. Open Terminal and type sudo chflags nouchg (with a space at the end) Do not press enter!!!!!
4. Drag and drop the file "boot.efi" from the finder window into the terminal window. Now press enter!
5. Type your password (it's invisible in terminal) and press enter. Now your boot.efi isn't protected anymore and you can drag the boot.efi file you put on the desktop into the folder. You have to answer the safety question and then it's almost done.
6. Last you have to re-protect the boot.efi again (nearly the same procedure like unprotecting it). Type in Terminal: sudo chflags uchg (plus space) and drag the file into terminal window. Then press enter again and its protected again.
The same boot.efi file has to be altered in the usr/standalone/i386/ folder. This file isn't protected, you can simply drag the pikify-version into the finder window and answer the security question.
Now you can reboot with ElCapitan and it will work perfectly on your MacPro 1.1
Amazing thank you mmonse_de I didn't view the video as i thought it was for starting from scratch only. But will refer back to it another time.
Your idiot guide worked a treat, 10.11.4 up and running.
Thank you.
Ok I will give this command line a try when I am back from work. I took a look back to page 55 and then the old Yosemite forum regarding the bless command and have learned a lot. I never quite came across this specific command line. You are a saint my friend, I will update when I can give it a go.
But don't forget: the command only works, if the pikify-stick isn't renamed! The command uses the original name given by the script.
[doublepost=1459180701][/doublepost]
Never said "idiot", just "noob".....Amazing thank you mmonse_de I didn't view the video as i thought it was for starting from scratch only. But will refer back to it another time.
Your idiot guide worked a treat, 10.11.4 up and running.
Nice to see another good old MP1.1 running into a bright future...
I hope my English is good enough for those "technical advices", as English isn't my native language.
And btw. a short click on the "thumbs up"-button is quite good for my "newbie-karma" on this forum...
Thank you very much again for your help! I am back up and running after being out of commission for almost a week. My ultimate solution was wiping my OSX partition (very painful to do) and then blessing the pikify stick. After that, I booted up holding the alt key to select the stick and it worked. My boot efi got replaced during the -.4 update so hopefully people can follow this thread to solve the problem themselves.
Hello James,
I am sorry to read that you had a painful experience, although glad you have it sorted now. Hindsight is a great thing. Here is my hindsight view, I hope that it will help you in the future:
Make sure your Recovery HD partition is working. Typically reboot into the Boot Chooser (hold down the Alt key immediately after the chime). You should see at least one Recovery partition, select it and attempt to boot. If it boots, you will usually see a utilities selection window. There will also be a Utilities menu, in this menu is a Terminal app. You can launch a Terminal from here. If you can boot from the Recovery partition, then it will contain a compatible Pike version of the boot.efi file, you can use this as the source to overwrite the Apple (updated) version on your main partition. If we assume your recently updated main partition is called Macintosh HD, boot into the Recovery HD, launch a Terminal, then type the following
Code:
chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi
cp /Volumes/Image\ Volume/com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi
cp /Volumes/Image\ Volume/com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/usr/standalone/i386/boot.efiIf your Graphics card does not show the boot screens try rebooting and holding down Command R (also known as Apple R). If that doesn't work try rebooting and holding down Alt, wait a few seconds let go of Alt, press the right arrow key once, then hit the Return or Enter key.
If you cannot boot from your Recovery HD, try to find an older bootable Mac OS X installation DVD, boot off that. I believe you can access the Terminal from here too.
If you have a spare HDD bay, and a spare SATA disk drive, it might be worth installing that and putting a second operating system on here. Since we will sometimes find ourselves in non-bootable situations, having a second functioning partition will make it easier to recover. (Or even use Disk Utility to add a partition to an existing disk, and install your second OS here).
Apple sometimes updates the recovery partition too (IIRC 10.11.2 had a Recovery update). I wrote a derivative script to recover the Recovery HD, rrhd. You can find it at post #1607 on Page 65
If you have access to another Mac (with Firewire), you can put your Mac Pro into target disk mode and connect it to the other machine. Your hard disks will show up as externally connected... Reboot and hold the T key down immediately after the boot chime...
If you have Boot Camp set up with Windows AND your Windows OS has the Apple drivers for HFS loaded, then you should be able to boot into Windows and perform the copy from there!
Last edited:
Hi guys, I could do with some tips. I have 10.11.3 installed on my Mac Pro, and just updated to 10.11.4 and I think I've bodged something. Now on the El Capitan drive when I try and boot I just get a circle with a line through it. I also get it on the El Capitan recovery drive. The El Capitan drive also has Windows 7 64bit installed. I still have 10.7.5 in my 4th bay and I have Time Machine backups on my mirrored 2/3 bays.
I've tried using the 10.7.5 recovery drive to restore the El Capitan backup but it won't let me. The original Pikify USB installer I created no longer boots (I've waited over an hour and it doesn't load).
I can't think of a simply way to restore my 10.11.3 install and then I can try it again.
I've tried using the 10.7.5 recovery drive to restore the El Capitan backup but it won't let me. The original Pikify USB installer I created no longer boots (I've waited over an hour and it doesn't load).
I can't think of a simply way to restore my 10.11.3 install and then I can try it again.