You may run into this if you forget to replace /.IABootFiles/boot.efi with the v3.0 copy of boot.efi from the download page.
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
[Then, after installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi and repair permissions.]
So I just copied the boot.ini file in two locations not three as you say. What part have I missed?
1. From a Yosemite or Mavericks installation from which the El Capitan installation is accessible, make the recovery partition visible via the following command executed from terminal -
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
2. Launch Disk Utility and mount the El Capitan recovery partition.
3. Replace the boot.efi found in com.apple.recovery.boot with Pike's new version.
Unlock the file by right click - get info - unlock
Overwrite the original boot.efi , and re-lock it.
And... another question: Does it mean that you can update from App Store as if you had a compatible MAC?
Yes, but until a mechanism like PikeYosFix is developed, it will be necessary to repeat these steps after each update.
So I just copied the boot.ini file in two locations not three as you say. What part have I missed?
1. From a Yosemite or Mavericks installation from which the El Capitan installation is accessible, make the recovery partition visible via the following command executed from terminal -
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
2. Launch Disk Utility and mount the El Capitan recovery partition.
3. Replace the boot.efi found in com.apple.recovery.boot with Pike's new version.
Unlock the file by right click - get info - unlock
Overwrite the original boot.efi , and re-lock it.
And... another question: Does it mean that you can update from App Store as if you had a compatible MAC?
Yes, but until a mechanism like PikeYosFix is developed, it will be necessary to repeat these steps after each update.
Thank you very much, OGNerd, I really appreciate your reply. But I don't know exactly how to repeat these three steps when you're already run El Capitan. Do you have to unmount your SSD and to do it with another compatible Mac or can you do it within El Capitan? I mean switching them while you're running the Capitan?
Please help: So I bought a new monitor and noticed that it was making a high-pitched noise. I decided to change the refresh rate to see if it would help... but then my mouse pointer started skipping and lagging. I restarted my machine, and now the darn thing won't boot.
I tried two other GPUs, but the thing still won't boot. The one GPU that displays boot screens has shown that the progress bar makes it almost all the way and then simply hangs.
I'm running El Cap; I tried replacing the boot EFI again, but it's still not booting. Anyone have ideas?
I tried two other GPUs, but the thing still won't boot. The one GPU that displays boot screens has shown that the progress bar makes it almost all the way and then simply hangs.
I'm running El Cap; I tried replacing the boot EFI again, but it's still not booting. Anyone have ideas?
Yep. As an update, I was able to boot into my old Mountain Lion hard drive. I have no idea why El Cap decided to cr@p out on me all of a sudden. Replacing the boot EFIs again didn't work.
EDIT: So I replaced the boot EFIs again, but from that Mountain Lion disk of mine. I also made sure to check and see if the drive needed to be repaired. I guess doing it from this drive worked this time. It was odd how, on my MBP (supported), I couldn't get it to boot. I mean, that's the machine I used in the first place to get this MP up and running with El Cap; perhaps I made some mistake.
The thing that pains me, though, is the fact that things acted up in the first place. I hope nothing fishy is going on. All I know is that my secondary HDD (for back-ups) was acting up and needed to be repaired. It couldn't be, though, so I had to end up formatting it. Not sure if this has anything to do with it--it shouldn't.
ANOTHER EDIT: Well, it seems like El Cap isn't recognizing my GPU anymore; I am currently using a spare. Both my AMD/ATI GPUs won't display anything, yet my 8800GT works just fine. This is a bit concerning. IDK--all of a sudden it did this...
Last edited:
No, you will not be able to do it from your running El Capitan installation (except possibly from a Mavericks or Yosemite virtual machine).
I've done the following steps :
1) I've downloaded and checked with md5 and sha1 a new copy of boot.efi
2) I've put it in /usr/standalone/i386/, /System/Library/CoreServices, /.IABootFiles replacing the one in place.
3) I've cleaned my system (repair permissions, cleaning caches, dylib, ...) with Onyx and done a reboot.
4) I've synced my System partition with my clone
5) I've downloaded and launched the El Capitan installer with the MAS
When the installer reboot my Mac, it fails to start in the installer. I have to boot on my clone to be able to reboot on my system partition.
Before the reboot (step 5) you need to replace /.IABootFiles/boot.efi with mine or it cannot boot (the 64-bit boot.efi is copied to this location). Check the md5/sha1 checksum and you'll quickly realise that the file isn't the one you need there.
Note: I have an yet to be released launch daemon for this procedure.
I've done that, but it doesn't work. The file is the good one :
pwd
/.IABootFiles
Mac-Pro-de-Laurent:.IABootFiles Laurent$ openssl md5 boot.efi
MD5(boot.efi)= b57d13b87226d72a31bf0aa527bc5f1f
Mac-Pro-de-Laurent:.IABootFiles Laurent$ openssl sha1 boot.efi
SHA1(boot.efi)= e8b2f26fa5b11fb0552ce4cf7c2740dbd5e4c9e6
Mac-Pro-de-Laurent:i386 Laurent$ pwd
/usr/standalone/i386
Mac-Pro-de-Laurent:i386 Laurent$ openssl md5 boot.efi
MD5(boot.efi)= b57d13b87226d72a31bf0aa527bc5f1f
Mac-Pro-de-Laurent:i386 Laurent$ openssl sha1 boot.efi
SHA1(boot.efi)= e8b2f26fa5b11fb0552ce4cf7c2740dbd5e4c9e6
Mac-Pro-de-Laurent:i386 Laurent$
Mac-Pro-de-Laurent:CoreServices Laurent$ pwd
/System/Library/CoreServices
Mac-Pro-de-Laurent:CoreServices Laurent$ openssl md5 boot.efi
MD5(boot.efi)= b57d13b87226d72a31bf0aa527bc5f1f
Mac-Pro-de-Laurent:CoreServices Laurent$ openssl sha1 boot.efi
SHA1(boot.efi)= e8b2f26fa5b11fb0552ce4cf7c2740dbd5e4c9e6
Is there a log file showing what is happening when boot fails ?
No it's not what I did.
I have a Mac Pro 1.1 at home and a Mac Pro 5.1 in my business.
On my Mac Pro 1.1 I have two SSDs.
A 256 GB with my current system, 10.6.8.
The second 1TB is a clone of the 256 GB with 10.6.8.
I installed the 10.6.8 clone into the Mac Pro 5.1, and then boot on it, make the update El Capitan.
I can boot on this disk in the Mac 5.1.
Then I put the disc on my Mac 1.1.
- I started on the first disc 10.6.8.
- With the terminal I unlocked the two boot.efi (.../CoreServices and .../ i386)
- I made the commands "sudo chown root:wheel boot.efi", "sudo chmod 644 boot.efi" and "sudo chflags uchg boot.efi" on both boot.efi files.
- I turn off the Mac.
- I restart by pressing the "Alt" key.
- I select the disk with El Capitan
- After a few secons, the Mac starts on the first disc 10.6.8
If I remove the 10.6.8 disk, leaving only the El Capitan disk, at the startup I have a folder with a question mark.
Ok. You have the correct copies of boot.efi in place. Please try our latest nightly of boot.efi and see if that helps.
@helmer,
You too
Ok. You have the correct copies of boot.efi in place. Please try our latest nightly of boot.efi and see if that helps.
@helmer,
You too
It still doesn't work. Here are the md5 and sha1 for these files to see if they are correct :
Mac-Pro-de-Laurent:.IABootFiles Laurent$ openssl md5 boot.efi
MD5(boot.efi)= 0f2b540ecdd35632b1eb258108584260
Mac-Pro-de-Laurent:.IABootFiles Laurent$ openssl sha1 boot.efi
SHA1(boot.efi)= d118a2379b112e965ba7952cd6efae494c2ab534
Hi,
My question may seems a little silly but I don't see the .IABootFiles folder even though I can see all the other hidden files
Thanks
My question may seems a little silly but I don't see the .IABootFiles folder even though I can see all the other hidden files
Thanks
I still can't get acceleration for ATI Radeon HD4890 - I used "Easykext Utility" to install the files downloaded from here: http://www.insanelymac.com/forum/files/file/415-qe-ci-exotic-patch/?st=10#commentsStart
Can anybody please help?
Can anybody please help?
Please, always include a link to your original post describing the problem, because people, me included, will get confused as to what isn't working. Remember. There are 37 pages right now, and several different people asking questions so I am getting lost about what the issue is. May be simple for you, but I have to deal with not one but many different posts/problems.
Hi all, same problem with my yosemite upgrade to el capitan. I've follow the istruction step by step but
without result. i've tested the last nightly boot.efi with the same result. Start the installation but when restart open another disk that i've with yose....mmmmmmmmh i don't know if the problem is that i've installed yosemite with sfott sistem
Thank's Pike for your extraordinary work hope you help us.....
Hello everyone:
On my MacPro1,1, I have encountered the same problem as LaurentR2D2 and gw463.
My Yosemite install is on an SSD; I have cloned a backup to a hard drive.
When I run the installer, my machine re-boots on the hard drive backup, even though I selected installation on the SSD.
I then can select the SSD as startup disk, and reboot to it, still running Yosemite. If I remove the hard drive backup, and try to install again, I see the blinking folder with a question mark, like there is no bootable device.
I notice that there is a folder at the root level on my SSD "OS X Install Data" which has a boot.efi in it. This is not the good one from Pike R Alpha.
I tired replacing the /OS X Install Data/boot.efi with the good one from Pike R Alpha, and running the installer again, but the installer overlays it every time with the boot.efi from Apple.
I can't find any .IABootFiles folder, even from a terminal with all hidden files shown.
I'm thinking about creating a USB flash drive installer, like the SFOTT process I followed for Yosemite.
Thanks in advance for any help on this.
On my MacPro1,1, I have encountered the same problem as LaurentR2D2 and gw463.
My Yosemite install is on an SSD; I have cloned a backup to a hard drive.
When I run the installer, my machine re-boots on the hard drive backup, even though I selected installation on the SSD.
I then can select the SSD as startup disk, and reboot to it, still running Yosemite. If I remove the hard drive backup, and try to install again, I see the blinking folder with a question mark, like there is no bootable device.
I notice that there is a folder at the root level on my SSD "OS X Install Data" which has a boot.efi in it. This is not the good one from Pike R Alpha.
I tired replacing the /OS X Install Data/boot.efi with the good one from Pike R Alpha, and running the installer again, but the installer overlays it every time with the boot.efi from Apple.
I can't find any .IABootFiles folder, even from a terminal with all hidden files shown.
I'm thinking about creating a USB flash drive installer, like the SFOTT process I followed for Yosemite.
Thanks in advance for any help on this.
Here is a screenshot of my system folder with the .IABootFiles shown :
$ pwd
/Volumes/SysteÌme
$ ls -alh
total 125
drwxrwxrwx 43 Laurent staff 1.5K Oct 18 20:01 .
drwxrwxrwx 43 Laurent staff 1.5K Oct 18 20:01 ..
-rw-rw-r--@ 1 root admin 10K Oct 18 20:01 .DS_Store
d--x--x--x 8 root wheel 272B Oct 18 19:59 .DocumentRevisions-V100
drwx------ 8 Laurent staff 272B Oct 18 16:40 .IABootFiles
-rw-r--r-- 1 root staff 305B Oct 18 16:47 .IAProductInfo
-rw-r--r-- 1 root staff 3.9K Oct 18 16:47 .OSInstallerMessages
-rw-rw-r-- 1 root admin 183B Jan 29 2012 .PR007377
drwx------ 5 root wheel 170B Dec 20 2014 .Spotlight-V100
-rw-r--r-- 1 root staff 1.3K Oct 18 16:45 .TALRestoreApps
drwxrwxrwt@ 3 root wheel 102B Feb 12 2015 .TemporaryItems
So I've succesfully replaced my previous boot-efi on El Capitan with version 3.0. Everything works fine, replaced it /System/Library/CoreServices, /usr/standalone/i386 and on the RecoveryHD, in com.apple.recovery.boot.
A few things though:
- I downloaded the black version, and noticed my startup screen is black ONLY when booting into Recovery. Normal boot is still grey.
- my board id is still F4208DC8.
...Yes I got it from http://piker-alpha.github.io/macosxbootloader/ and yes openssl md5 gives me
b57d13b87226d72a31bf0aa527bc5f1f
A few things though:
- I downloaded the black version, and noticed my startup screen is black ONLY when booting into Recovery. Normal boot is still grey.
- my board id is still F4208DC8.
...Yes I got it from http://piker-alpha.github.io/macosxbootloader/ and yes openssl md5 gives me
b57d13b87226d72a31bf0aa527bc5f1f
Here is a screenshot of my system folder with the .IABootFiles shown :
$ pwd
/Volumes/SysteÌme
$ ls -alh
total 125
drwxrwxrwx 43 Laurent staff 1.5K Oct 18 20:01 .
drwxrwxrwx 43 Laurent staff 1.5K Oct 18 20:01 ..
-rw-rw-r--@ 1 root admin 10K Oct 18 20:01 .DS_Store
d--x--x--x 8 root wheel 272B Oct 18 19:59 .DocumentRevisions-V100
drwx------ 8 Laurent staff 272B Oct 18 16:40 .IABootFiles
-rw-r--r-- 1 root staff 305B Oct 18 16:47 .IAProductInfo
-rw-r--r-- 1 root staff 3.9K Oct 18 16:47 .OSInstallerMessages
-rw-rw-r-- 1 root admin 183B Jan 29 2012 .PR007377
drwx------ 5 root wheel 170B Dec 20 2014 .Spotlight-V100
-rw-r--r-- 1 root staff 1.3K Oct 18 16:45 .TALRestoreApps
drwxrwxrwt@ 3 root wheel 102B Feb 12 2015 .TemporaryItems
I had the same problem as michmcca, LaurentR2D2 and others: No .IABootFiles folder on my system (Yosemite 10.10.5 on a Mac Pro 2,1). I tried to create the folder and put the new boot.efi in it, and then run the installer with the new boot.efi placed in the three other locations, but that failed when the installer rebooted. The following error message only displayed for a second or so, so excuse the potato quality.
I don't have any problem with .IABootFiles folder. My screenshots were meant to help you find it on your hardware
I don't have any problem with .IABootFiles folder. My screenshots were meant to help you find it on your hardware
Sorry I included you, my mistake.
Sorry for being such a novice. Someone, it may have been MacVidCards, said he posted about how to replace boot.efi on the Recovery disk, but I am unable to locate it. Can someone please direct me to the method of replacing the boot.efi in Recovery? In the com.apple.recovery.boot file, I cannot unlock the old boot.efi file to replace it. I replaced the other two. I made an El Capitan bootable USB drive, copied the El Capitan installer to my desktop. The first time I tried to update, it seemed like it was going to do it, but it hung up for 30 secs and then booted back into Yosemite. When I tried it again, it now says "This version of OS X cannot be installed on this computer". I re-verified the boot.efi's in the folders on my main drive, and they are correct. Thanks.