2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[andrew nz]

hello all.

I am new to the programming and hacking world.
I have previously successfully installed 10.10.x from a usb installer.
This is my second attempt to increase the lifespan of my MacPro 1.1

i used 2 methods to install capitan to usb. The method in the text of this post and the slightly different version shown in the video.

I am using a Mac Pro 1.1 with yosemite 10.10.5 and attempted to make the boot usb. I also have a non flashed radeon 5770, which means using the option or C keys problematic and to add to the issue, a bluetooth apple keyboard, which means it does not always sync/connect during startup/boot at the correct time.

Once compiled i found cannot boot from the usb although files seem to be there yet invisible.

Also the script seems to create a 6G file in application support/pikify folder.
I later deleted it after the install attempt.

There is not startup option in system preference/startup disk, which would be a really useful option and would eliminate key combo startup dilemmas.

Is the apple createinstallmedia script not compatible with 10.10.5?

In disk utility i found that it recognised the usb is bootable.
If I try the option key routine the mac will not boot at all and seems to hang somewhere before anything is loaded from any bootable disk.

I would like to install el capitan and have a disk ready and dedicated for that.
i used the latest version of pikify attached to this thread.

what is the solution?



This is the text of my install from terminal. note the error at the end:

Last login: Sat Feb 11 20:48:52 on console
spectrum:~ destinyangel$ cd ~/Downloads/pikify3.1
spectrumikify3.1 destinyangel$ sudo -s
Password:
bash-3.2# sudo -s
bash-3.2# whoami
root
bash-3.2# cd /Users/destinyangel/Downloads
bash-3.2# cd /Users/destinyangel/Downloads/pikify3.1
bash-3.2# \s
bash: s: command not found
bash-3.2# ls
OSInstall.collection boot_grey_3_1.efi missing-fonts.tgz
boot.efi bootbase.efi pikify.pkg
boot_black_3_1.efi createpikeinstallmedia
bash-3.2# ./createpikeinstallmedia /Volumes/Untitled\ 1/




--------------------------------------------------------------------------------



--------------------------------------------------------------------------------

Saving an original copy of the Install OS X El Capitan InstallESD.dmg....

Open the InstallESD disk image

Turn off spotlight indexing for InstallESD.dmg
Piking the OSInstall collection
Saving the original copy of the BaseSystem.dmg....

Open the BaseSystem disk image

Turn off spotlight indexing for BaseSystem.dmg
Piking the Base System
Adding the missing fonts...

Close the BaseSystem disk image

Put the modified BaseSystem back into the InstallESD disk image
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $EFFA939E: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $29CC3900: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $9F14DF31: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
..........................................................
(CRC32 $1BF2E71F: disk image (Apple_HFS : 4))
Reading (Apple_Free : 5)…
.............................................................................................
(CRC32 $00000000: (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
.............................................................................................
(CRC32 $9F14DF31: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
..............................................................................................
(CRC32 $37F5C3C9: GPT Header (Backup GPT Header : 7))
Adding resources…
..............................................................................................
Elapsed Time: 2m 2.316s
File size: 486376160 bytes, Checksum: CRC32 $16C41604
Sectors processed: 4144184, 2562716 compressed
Speed: 10.2Mbytes/sec
Savings: 77.1%
created: /Users/root/Library/Application Support/pikify3.1/ESD/BaseSystem.dmg

Close the InstallESD disk image

Rebuild the InstallESD
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $CD2DD671: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $9418AD42: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $D43195C8: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading EFI System Partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B : 4)…
..
(CRC32 $B54B659C: EFI System Partition (C12A7328-F81F-11D2-BA4B-00A0C93EC93B : 4))
Reading disk image (Apple_HFS : 5)…
............................................................................................
(CRC32 $BD5DEA16: disk image (Apple_HFS : 5))
Reading (Apple_Free : 6)…
.............................................................................................
(CRC32 $00000000: (Apple_Free : 6))
Reading GPT Partition Data (Backup GPT Table : 7)…
.............................................................................................
(CRC32 $D43195C8: GPT Partition Data (Backup GPT Table : 7))
Reading GPT Header (Backup GPT Header : 8)…
..............................................................................................
(CRC32 $04990E82: GPT Header (Backup GPT Header : 8))
Adding resources…
..............................................................................................
Elapsed Time: 3m 46.474s
File size: 6076976145 bytes, Checksum: CRC32 $1B2B86D5
Sectors processed: 13037600, 12552668 compressed
Speed: 27.1Mbytes/sec
Savings: 9.0%
created: /Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg

Running Apple's createinstallmedia tool...
Erasing Disk: 0%... 10%... 20%... 30%...100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.
Piking the .IABootFiles directory




######### DONE PIKIFYING ###########



2017-02-11 21:32:51.560 system_profiler[973:52390] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0
2017-02-11 21:32:51.566 system_profiler[973:52390] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0
bash-3.2#

 

[robogobo]

I have a working El Capitan install in my Mac Pro 1,1, and I though I'd make a clone just in case I need to swap in a new drive. However I can't get the clone to boot up. I used CCC and did the Recovery HD clone option.

Any thoughts why the clone wouldn't work? I went in and replaced the Pike boot.efi files manually and still nothing.

Thanks a 1,000,000

Update: I got it to boot from the clone after booting from the original working install and selecting the clone as the startup disk from System Preferences. But then it wouldn't boot again after removing the working disk and shifting the clone into bay 1. I have a GT120 with no boot screen so I don't what's showing up as boot options when I start up with option held down.

 

[andrew nz]

update:


I have a partial and inelegant solution to enable capitan installation for those who cannot see the boot screen and have problems using key C and opt combos.

The usb is indeed bootable but neither 10.7.5 or 10.10.5 will see it.

I remade the usb booter from 10.7.5 using the same method as previously and followed the video.

I found that i had to disconnect my firewire drive and place my target disk in position 1 / slot 1 in the Macpro. This means that when i blind booted using C or opt keys, i could not select any bootable disk and no way to identify what was happening.

After this the usb was able to see the target disk and after waiting a long time for the boot screen to appear and after the mac had booted into the usb installer, I installed capitan.

The installation took around 30 minutes and there were no issues with the installation apart from the time and many errors in the log.

This worked and i was able to start and restart capitan.
i reinstalled all my other disks and firewire drive.
All function well.


Could the creators of the installer make the usb booter visible in the system preference startup disk pane?

This will eliminate all problems with installation and blind selection of startup drives.

I also installed the boot64 file but have not upgraded the OS until there is more clarity about SIP and overwriting the boot.efi.

Currently capitan 10.11.0 is upgradable from software update to 10.11.6.

 

[rthpjm]

Could the creators of the installer make the usb booter visible in the system preference startup disk pane?

Hello Andrew,

The simple answer to that question is no (probably).

It is a combination effect of the way Apple's OS (control panels) detect bootable volumes, and the way Apple's createinstallmedia builds the installer (my script is simply a wrapper around Apple's)

 

[andrew nz]

Upgrades to:
10.11.1 okay
10.11.2 caution
10.11.3 okay
10.11.4 caution
10.11.5 caution
10.11.6 okay




What is the issue if any now with using the software update to 10.11.6 -using this threads techniques, from freshly installed 10.11 and boot64 installed?
[doublepost=1486891764][/doublepost]

Hello Andrew,

The simple answer to that question is no (probably).

It is a combination effect of the way Apple's OS (control panels) detect bootable volumes, and the way Apple's createinstallmedia builds the installer (my script is simply a wrapper around Apple's)

hello

if you want to look at a very easy way to install yosemite on a macpro 1.1, the usb thankfully is visible in startup disk.

http://www.lincade.org/yosemite-and-the-macpro-1-1-2-1/#comment-57462


the vid and all the tools are linked so archiving it is quite easy.

 

[andrew nz]

Follow these instructions if you have just installed El Capitan, or are already using El Capitan and want to automatically put the modifications in place during updates.

============== Edit ==================
This has been tested from initial install 10.11 to 10.11.1, and from 10.11.1 to 10.11.2.

Each successive release of El Capitan is making it harder to use this method, which is only to be expected. SIP (aka "rootless") is continually being developed and extended by Apple.

As a rule of thumb, if in doubt turn SIP off first.

If you are nervous about a particular update to El Capitan, then you should disable SIP entirely before you commence with the update. Search this thread for "csrutil" to find out how...

Upgrades to:
10.11.1 okay
10.11.2 caution
10.11.3 okay
10.11.4 caution
10.11.5 caution
10.11.6 okay

NOTE: If you install El Capitan and then use a "combo" updater usually downloaded from the Apple web site Support / Downloads section, then be aware ALL combo updates will replace the boot.efi files (perhaps with the exception of 10.11.0 -> 10.11.1)

===================================

hello

sorry to repeat the request.

is there any issue now to upgrade to 10.11.6 from the freshly installed 10.11.0 with boot64 installed with software update?

one thing i have noted, you cannot fix permissions on the capitan install from that boot or yosemite disk. is that important?

 

[rthpjm]

hello

sorry to repeat the request.

is there any issue now to upgrade to 10.11.6 from the freshly installed 10.11.0 with boot64 installed with software update?

one thing i have noted, you cannot fix permissions on the capitan install from that boot or yosemite disk. is that important?

Hello Andrew,

1. If you have just installed El Capitan, AND the download of the Install OS X El Capitan app was from the Mac App Store, AND the download happened recently, then you will already be at 10.11.6.

It's quite unusual to find someone who has started from 10.11.0.

If you have started from 10.11.0, you are effectively facing a cumulative install of the upgrades, a single upgrade to 10.11.6. In this case, yes the update will overwrite the two boot.efi files

2. If you have installed Boot64 (or CapitanPikeFix), then you should be okay to upgrade. Just be brave.
If it breaks, you just need to copy the Pike version of the boot.efi files into their two locations. Read this thread if you get into this position, the instructions have been repeated many, many times.

3. I presume you are referring to the fact that the Disk Utility no longer presents buttons to "Repair permissions"? That's because Apple took the decision to remove that feature from that App. We can only speculate as to why. My guess would be that with SIP enabled it's much, much more difficult to screw things up, and therefore the issue has been minimised to the point that Apple feel it's safe to remove the perceived need.
If you really, really want to repair your permissions, you can still do it from the command line. I'll leave that as an exercise for you to figure out (I.e. Don't ask me how...)

 

[andrew nz]

Hello Andrew,

1. If you have just installed El Capitan, AND the download of the Install OS X El Capitan app was from the Mac App Store, AND the download happened recently, then you will already be at 10.11.6.

It's quite unusual to find someone who has started from 10.11.0.

If you have started from 10.11.0, you are effectively facing a cumulative install of the upgrades, a single upgrade to 10.11.6. In this case, yes the update will overwrite the two boot.efi files

2. If you have installed Boot64 (or CapitanPikeFix), then you should be okay to upgrade. Just be brave.
If it breaks, you just need to copy the Pike version of the boot.efi files into their two locations. Read this thread if you get into this position, the instructions have been repeated many, many times.

3. I presume you are referring to the fact that the Disk Utility no longer presents buttons to "Repair permissions"? That's because Apple took the decision to remove that feature from that App. We can only speculate as to why. My guess would be that with SIP enabled it's much, much more difficult to screw things up, and therefore the issue has been minimised to the point that Apple feel it's safe to remove the perceived need.
If you really, really want to repair your permissions, you can still do it from the command line. I'll leave that as an exercise for you to figure out (I.e. Don't ask me how...)

Hello
I downloaded the capitan install app from somewhere that was not the app store but as far as I am aware is that installer, and made the usb installer. This is why I begin at 10.11.0.

2. Yes I have been searching for the paths so far read many pages.

3. I was curious why the feature was removed. If no longer needed by a user then provided nothing breaks, all is good.

 

[andrew nz]

Hello Andrew,

1. If you have just installed El Capitan, AND the download of the Install OS X El Capitan app was from the Mac App Store, AND the download happened recently, then you will already be at 10.11.6.

It's quite unusual to find someone who has started from 10.11.0.

If you have started from 10.11.0, you are effectively facing a cumulative install of the upgrades, a single upgrade to 10.11.6. In this case, yes the update will overwrite the two boot.efi files

2. If you have installed Boot64 (or CapitanPikeFix), then you should be okay to upgrade. Just be brave.
If it breaks, you just need to copy the Pike version of the boot.efi files into their two locations. Read this thread if you get into this position, the instructions have been repeated many, many times.

3. I presume you are referring to the fact that the Disk Utility no longer presents buttons to "Repair permissions"? That's because Apple took the decision to remove that feature from that App. We can only speculate as to why. My guess would be that with SIP enabled it's much, much more difficult to screw things up, and therefore the issue has been minimised to the point that Apple feel it's safe to remove the perceived need.
If you really, really want to repair your permissions, you can still do it from the command line. I'll leave that as an exercise for you to figure out (I.e. Don't ask me how...)

I am writing this from the upgraded safari 10.0.3 which is part of the direct upgrade from 10.11.0 to 10.11.6.
So far no issues on installation except i use dual monitors and transitioning between them a dragged item becomes transparent and partially disappears.
I will not be checking the recovery partition because i usually have no need of it.

I have a newish logitech m 560 mouse and does not require the logitech control centre to operate in 10.11.6 but was initially necessary in 10.10.5 because neither will recognise it as a bluetooth mouse.

There is now a security upgrade in app store 2016-003 10.11.6
Anyone installed and any issues?

 

[basilt]

thanks a lot
hwojtek,

rthpjm --- the re-installation is definitely a pain in the ass i guess. i will try to see how can i make the partition on a usb. thanks

 

[F1Mac]

I am writing this from the upgraded safari 10.0.3 which is part of the direct upgrade from 10.11.0 to 10.11.6.
So far no issues on installation except i use dual monitors and transitioning between them a dragged item becomes transparent and partially disappears.

This feature appeared with Mavericks so my guess is that maybe you forgot you disabled it, loooooong ago Mission Control>Displays have separate spaces - uncheck that box and voilà.

There is now a security upgrade in app store 2016-003 10.11.6
Anyone installed and any issues?

No problem whatsoever, security updates usually don't touch the boot.efi anyway.

 

[EmlynDewar]

I had only skimmed over this thread, as came into possession of a Mac Pro 1,1.
Used SuperDuper to clone my MBP 2008 El Cap 10.11.6 install, and replaced the boot files. Booted with no issue.

Great work by the people who worked on those files, made it incredibly easy!

 

[andrew nz]

This feature appeared with Mavericks so my guess is that maybe you forgot you disabled it, loooooong ago Mission Control>Displays have separate spaces - uncheck that box and voilà.



No problem whatsoever, security updates usually don't touch the boot.efi anyway.

i installed the security update. all seems ok.
[doublepost=1487473391][/doublepost]

i installed the security update. all seems ok.

the update is dated 13 january 2017
then i found this after search

https://www.jamf.com/jamf-nation/di...y-update-2016-003-for-os-x-el-capitan-10-11-6


and an apple response for another supplemental download dated 17 january 2017

https://support.apple.com/kb/DL1908?locale=en_US


the link is not operating, perhaps apple will make some kind of announcement.
anyone have similar issues with gui performance?

 

[rthpjm]

Upgrades to:
10.11.1 okay
10.11.2 caution
10.11.3 okay
10.11.4 caution
10.11.5 caution
10.11.6 okay




What is the issue if any now with using the software update to 10.11.6 -using this threads techniques, from freshly installed 10.11 and boot64 installed?
[doublepost=1486891764][/doublepost]



hello

if you want to look at a very easy way to install yosemite on a macpro 1.1, the usb thankfully is visible in startup disk.

http://www.lincade.org/yosemite-and-the-macpro-1-1-2-1/#comment-57462


the vid and all the tools are linked so archiving it is quite easy.

Hello Andrew

Well I took up the challenge. (To be honest, I had been working on some changes for a while!).

CALL FOR TESTERS​

I have uploaded Version 14 of my pikify script bundle.

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass (no need for a USB memory stick), and doesn't require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

I would appreciate some testers

Similar requirements

• A copy of Install OS X El Capitan inside your Applications folder
• Download a copy of pikify.3.1.v14.zip
• Unzip it
• Use a Terminal to run createpikeinstallmedia as the root user
• The difference is you pass the path to the disk you want to upgrade (instead of an installer volume/USB)
• it will reboot directly into the installer

I'm emulating the way Apple does an in-place installation now. Hopefully you'll find it easier....

Post #1390 on page 56

Oh, and yes it still requires more than 12Gb RAM

Have fun....

 

[andrew nz]

i installed the security update. all seems ok.
[doublepost=1487473391][/doublepost]

the update is dated 13 january 2017
then i found this after search

https://www.jamf.com/jamf-nation/di...y-update-2016-003-for-os-x-el-capitan-10-11-6


and an apple response for another supplemental download dated 17 january 2017

https://support.apple.com/kb/DL1908?locale=en_US


the link is not operating, perhaps apple will make some kind of announcement.
anyone have similar issues with gui performance?

update:
the "supplemental" link above is now working and the file is some 600G.
it installs without issue.

If it addresses the issues it claims, i do not know.

 

[jbarley]

the file is some 600G.

That is one very large security update...

 

[donjames]

NEW for 2017:

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass, and doesn't require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

I will upload a new video soon...

To use v14, pass the path to your target disk. Let's say you want to install El Capitan onto the Macintosh HD disk....

sudo ./createpikeinstallmedia /Volumes/Macintosh\ HD
[your password]

Hi rthpjm,

I tried Version 14 to install El Capitan on my Mac Pro 1,1 running Yosemite. It works great! Thank you for all of your hard work.

Sincerely,
Don James
Henderson, Texas USA


============== Previous Versions ===========================

Installing Mac OS X El Capitan 10.11.x with this pikify3.1 method is a two-step process

Step 1: Use the attached script and files, to build an installer volume, typically a USB memory stick, or a small disk partition.

Step 2: You will then boot off the installer, to run the installation process.

DO NOT be tempted to simply double-click the Install Mac OS X El Capitan on the install volume, you will be wasting your time. It will not work. You must reboot your MacPro and select the Install Mac OS X El Capitan volume from the boot chooser screen...

Once the installer finishes, you will have a working copy of El Capitan with no need to manually change the boot.efi files.

I keep forgetting to mention that this method also builds the Recovery Partition (Recovery HD) too!

Optional step: You can then choose to install the updated version of pikeyosfix now called CapitanPikeFix, or my Boot64 (both do pretty much the same thing), to allow you to run the Apple updates from either the App Store or from the DMG downloads. See the next post #1391...

READ ALL THE CAVEATS - memory, backup, fresh install, migration assistant, etc...

Use this if you have not yet installed El Capitan and you only have your Mac Pro available.
This is the installer (starting point) if you only have your Mac Pro to work with...
==============================================================

INSTRUCTIONS

Download the zip file attached to this post.

Unzip it.

You should have a folder named pikify3.1


In that folder should be a number of files, the script is createpikeinstallmedia. Keep all the files in one location. Some people have tried to use just the script on its own without the accompanying files and then come back for help because it didn't work. You can move the pikify3.1 folder wherever you please, just keep the contents of the folder together.

If you are not familiar with the Terminal and the command line, take a look at post #1569 it will probably help you.

Pre-requisites:

• Your running OS must be Lion (10.7) or better. I have tested Snow Leopard and the Apple createinstallmedia tool fails (Snow Leopard is just too old).
• As per Peter's guide, you will need a volume that can be overwritten by the installer
  • This could be a USB memory stick
  • A small disk partition from one of your hard drives (not the disk that you intend to use for El Capitan)
    • You need to be able to boot from this volume
• The installer volume needs to be at least 8GB
• Your copy of 'Install OS X El Capitan.app' should be located in your /Applications folder
• The pikify3.1 folder contains both the black and grey variants of the boot.efi file. When unzipped the boot.efi file is the grey one, if you want to change to the black background variant, simply copy the black one over the boot.efi before you start. e.g.

  cp -f boot_black_3_1.efi boot.efi

• It appears that MacPro1,1 and 2,1 need a lot of memory to achieve a successful install by this method. A minimum of 12GB seems to be required...

Usage:

• Open a terminal window
• Change directory to the pikify3.1 folder from the zip file. Let us assume that you downloaded the zip file to your Downloads folder and unzipped it there. (If you have put the pikify3.1 folder somewhere else, please alter the path to suit your location)
• Change [InstallerVolumeName] to the name of the USB memory stick or your small disk partition. For example if you are using a USB memory stick and it shows on the desktop with the name Untitled, then replace [InstallerVolumeName] with Untitled so that the path reads /Volumes/Untitled

cd ~/Downloads/pikify3.1

• You need to run the script as the root user

sudo -s
[your password]
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

• OR

sudo ./createpikeinstallmedia /Volumes/[InstallerVolumeName]
[your password]

• OR (optionally switch to the black background variant before you start)

sudo -s
[your password]
cp -f boot_black_3_1.efi boot.efi
./createpikeinstallmedia /Volumes/[InstallerVolumeName]

Be patient, the script will take some time to run through to completion, especially if your installer volume is a USB memory stick!

Once the script completes it will print ### DONE PIKIFYING ### and you should have an installer volume named 'Install OS X El Capitan'

After you build your pikify3.1 USB memory stick, but before you attempt to boot from it, try ejecting it, physically unplug it, wait a few seconds, then re-plug it in allowing it to mount.

• Reboot your MacPro with the newly created install media (partition or USB stick) attached
• Hold the ALT key down immediately after the startup chime to enter the boot chooser
• Choose the Install OS X El Capitan volume
  • For those people with graphics cards that don't show the boot screens
    • If you are using a USB stick (and it's the only one attached), immediately after the startup chime, hold down the C key. If your USB memory stick has an access indicator (blinking LED) you can visually confirm it is booting. Be patient, it takes about a minute before the screen shows anything. OR....
    • Get to the boot chooser as above then press the left-arrow key once, followed by the return/enter key. (Removable media generally shows up last in the horizontal list, pressing the left arrow key takes you from the automatic first entry and wraps the highlight round to the other end of the list, which is usually where the USB stick is presented). OR....
    • If you're using a small disk partition, get to the boot chooser as above then press the right-arrow key once, followed by the return/enter key). If you have just your main disk and the installer volume this should work. If you have more than just those two, experiment pressing the arrow key more than once until you find the installer volume! OR....
    • OR, consider getting hold of a DVI-vga adaptor. You should be able to find one of your DVI ports that will send out a VGA signal (to a VGA connected monitor) and show you the boot screen.
• Your machine should boot into the Installer, run the installer
  • You may need to click the Reboot button at the end of the install (for some reason, the 10 second countdown doesn't seem to automatically start)
• Your machine should reboot into the new El Capitan Installation and begin the OS X setup procedure.

I made a video! I hope you like it...

I used my iPhone for the second half, apologies for the moire patterns.

I decided to start from my MacPro running 10.7.x Lion, since this is the last officially supported version.
The only difficulty for people is to get hold of a copy of Apple's "Install Mac OS X El Capitan" app. I recommend using a newer "supported" Mac and then copying it to the MacPro....

One of the steps in the video shows me formatting my hard disk drive, do not do this step if you have data on your hard disk (unless you have a backup and are prepared to wipe the drive)

If you are upgrading I would suggest a clean install of El Capitan onto a spare disk, then use the Apple Migration Assistant to migrate your previous system and user files.
If you are brave and want to try an in-place upgrade, make sure you backup your current system first...

======================== UPDATE ================================

The original Apple BaseSystem.dmg appears to be missing a number of fonts. This causes the installer log file to fill up with thousands of unnecessary lines complaining about the missing fonts. I've updated the installer creation script to fix the missing fonts. It just makes the log file smaller and easier to read and follow.

See pikify3.1.v2.zip in the attachments...

==================== ANOTHER UPDATE =============================

I figured out how to set up El Capitan so that we can make it survive an Apple update. See my post at post #1391

I've modified the pikify3.1 set so that steps 1 - 4 of the process below (post 1391) are already in place. You still need to choose to install Boot64 or CapitanPikeFix (see below).

I'll leave v2 here in case anyone is paranoid, and doesn't want the slight lowering of SIP's security blanket!

==================== Version 5 ===================================

V5 includes some mods to the SIP exclusion paths file

==================== Version 7 ===================================
(includes version 6, which added support for home-baked fusion drives)
V7 adds error checking and a bit of an explanation to start

==================== Version 8 ===================================
V8 adds a check to ensure there is a copy of the Apple Install OS X El Capitan application located in the Applications folder!

==================== Version 9 ===================================
All previous versions would first write the Install media, and then modify that content. If the Install media is a USB memory stick, all those operations are slow due to the USB bus speed.

V9 attempts to speed up the operations. It will modify the /Applications/Install OS X El Capitan.app on the hard disk first (faster), and then write the contents to the USB memory stick. There is only one write across the USB bus.

Plus, the modifications are left in place. The script will detect if the copy of Install Mac OS X El Capitan has already been modified, giving you the option to reset to the Apple version, or to continue. If you choose to continue it will skip the modifications (because they're already present) and simply write a new copy to your USB memory stick (or installer partition)

It should be quicker

==================== Version 10 ==================================
Version 10 adds a check to see if the InstallESD.dmg and/or the BaseSystem.dmg are already mounted, if so it tries to detach them.

WARNING: It seems some people have tried V10 and it has caused problems.

==================== Version 11 ==================================
Version 11 fixes the issues with v9/v10. Basically I made an error in design when I created v9/v10. The resulting files were too big to fit onto an 8GB memory stick. Sorry folks!!

If you downloaded v9 or v10, please rapidly place them in their new home (the trash can), and re-download V11, it will now work much better

==================== Version 12 ==================================
Version 12 saves the unmodified software in a format that makes it easier to restore. Also adds more checks. The biggest change is that the disk images are now mounted on specific mount points so that my script doesn't conflict with the default mount points.

==================== Version 13 ==================================
Not released

==================== Version 14 ==================================
Version 14 is a major change in strategy. With this version you no longer need an intermediate installation media (USB memory stick). Version 14 emulates the way Apple is currently performing the installation. With version 14 you target the disk you want to install El Capitan onto (not the USB memory stick). I will leave v12 in place for a while. New users should use v14. If you encounter any issues, please post an entry on this thread.

One really big advantage to V14 is that it will reboot directly into the installer. This should be a great boon for those people with graphics cards that do NOT show boot screens. There's no more need to guess how to boot into the installer.

I will post an updated video later...


++++++++++++++++ MD5 ++++++++++++++++++++++++++++++++++++++++++

MD5 (pikify3.1.v2.zip) = 80333eda8eecc3094f06d175bdba0a64
MD5 (pikify3.1.v12.zip) = 170873c7029f611da798d07647766522
MD5 (pikify3.1.v14.zip) = e7b1699c8db8335c2331e1e8b247efa8

[doublepost=1487696380][/doublepost]

Hello Andrew

Well I took up the challenge. (To be honest, I had been working on some changes for a while!).

CALL FOR TESTERS​

I have uploaded Version 14 of my pikify script bundle.

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass (no need for a USB memory stick), and doesn't require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

I would appreciate some testers

Similar requirements

• A copy of Install OS X El Capitan inside your Applications folder
• Download a copy of pikify.3.1.v14.zip

• Unzip it
• Use a Terminal to run createpikeinstallmedia as the root user
• The difference is you pass the path to the disk you want to upgrade (instead of an installer volume/USB)
• it will reboot directly into the installer

I'm emulating the way Apple does an in-place installation now. Hopefully you'll find it easier....

Post #1390 on page 56

Have fun....

Hi rthpjm,

I tried it and it works great!

Thanks,

Don James
Henderson, Texas USA

 

[donjames]

Hello Andrew

Well I took up the challenge. (To be honest, I had been working on some changes for a while!).

CALL FOR TESTERS​

I have uploaded Version 14 of my pikify script bundle.

Version 14 marks a shift in technique. With V14 the installation process is much simpler, becomes a single pass (no need for a USB memory stick), and doesn't require the use of the EFI boot selector (which should be a great help to those people with graphics cards that do not show boot screens).

I would appreciate some testers

Similar requirements

• A copy of Install OS X El Capitan inside your Applications folder
• Download a copy of pikify.3.1.v14.zip

• Unzip it
• Use a Terminal to run createpikeinstallmedia as the root user
• The difference is you pass the path to the disk you want to upgrade (instead of an installer volume/USB)
• it will reboot directly into the installer

I'm emulating the way Apple does an in-place installation now. Hopefully you'll find it easier....

Post #1390 on page 56

Have fun....

Hi rthpjm,

I used version pikify v14 to install El Capitan on a Mac Pro 1,1. The install went okay. The copy of "Install Mac OS X El Capitan.app" that I used was version 10.11.5.

After the install, I ran your Boot64.v3.mpkg. I then ran Install Mac OS X El Capitan.app version 10.11.6. The system started the install, but when it restarted, it showed Disk Utility instead of the desk top.

In other words, the install seemed to not work after the reboot.

Was I supposed to reboot immediately after running Boot64.v3.mpkg?

Please help.

Sincerely,

Don James

 

[rthpjm]

Hi rthpjm,

I used version pikify v14 to install El Capitan on a Mac Pro 1,1. The install went okay. The copy of "Install Mac OS X El Capitan.app" that I used was version 10.11.5.

After the install, I ran your Boot64.v3.mpkg. I then ran Install Mac OS X El Capitan.app version 10.11.6. The system started the install, but when it restarted, it showed Disk Utility instead of the desk top.

In other words, the install seemed to not work after the reboot.

Was I supposed to reboot immediately after running Boot64.v3.mpkg?

Please help.

Sincerely,

Don James

Hello Don,

Thanks for the feedback.

I'll take a look at the code. I can't remember if Boot64 activates immediately or if a reboot is required. I think it should activate immediately.

I'll see if I have a copy of 10.11.5 installer and then try the same sequence. Don't hold your breath though, it might take me a while, need to find some time in my life

 

[donjames]

Hello Don,

Thanks for the feedback.

I'll take a look at the code. I can't remember if Boot64 activates immediately or if a reboot is required. I think it should activate immediately.

I'll see if I have a copy of 10.11.5 installer and then try the same sequence. Don't hold your breath though, it might take me a while, need to find some time in my life

HI rthpjm,

I just remembered that the computer didn't ask for my admin password when I ran Boot64. I think that Boot64 may not have run.

Don James

 

[rthpjm]

HI rthpjm,

I just remembered that the computer didn't ask for my admin password when I ran Boot64. I think that Boot64 may not have run.

Don James

Hello Don,

I went through the whole process (I'm composing a new video tutorial for V14 ). I figured start with 10.11.5, then I can test Boot64 out immediately after the build.

Here's what I did:

• partitioned a drive into two equal volumes
• installed Lion on the second half volume, leaving the first half volume as my target for pikify
  • Once El Capitan is installed I can destroy the second half partition and recover the space
• booted into Lion
• downloaded pikify V14
• ran pikify giving it my first Volume as the target
• it installed perfectly
• booted into El Capitan
• downloaded Boot64
• installed it (it should ask for your password, mine did)
• checked it was working (sudo /Library/Application\ Support/Boot64/ensureBoot.sh -g)
• open the Console
• select the system.log
• from a terminal: sudo touch /System/Library/CoreServices/boot.efi
  • after a couple of seconds you should see a log entry in the Console from ensureBoot
• opened the App Store
• Checked for updates
• Installed the updates
• reboot
• all works okay

So I think you must have messed up the Boot64 install (as you surmised).

 

[donjames]

Hello Don,

I went through the whole process (I'm composing a new video tutorial for V14 ). I figured start with 10.11.5, then I can test Boot64 out immediately after the build.

Here's what I did:

• partitioned a drive into two equal volumes
• installed Lion on the second half volume, leaving the first half volume as my target for pikify
  • Once El Capitan is installed I can destroy the second half partition and recover the space
• booted into Lion
• downloaded pikify V14
• ran pikify giving it my first Volume as the target
• it installed perfectly
• booted into El Capitan
• downloaded Boot64
• installed it (it should ask for your password, mine did)
• checked it was working (sudo /Library/Application\ Support/Boot64/ensureBoot.sh -g)
• open the Console
• select the system.log
• from a terminal: sudo touch /System/Library/CoreServices/boot.efi
  • after a couple of seconds you should see a log entry in the Console from ensureBoot
• opened the App Store
• Checked for updates
• Installed the updates
• reboot
• all works okay

So I think you must have messed up the Boot64 install (as you surmised).

Hi rthpjm,

Sounds right. Tell me exactly where to download Boot64.

Don

 

[fhenry]

works perfect with the last version. Thx you for that great improvement!

 

[rthpjm]

Hi rthpjm,

Sounds right. Tell me exactly where to download Boot64.

Don

Page 56 post 1391, the one right after the main pikify post

 

[sanimir]

HI.
I have MacPro 1.1 14gb ram 2,66 procesor and nvidia 8800 GT, 300 GB and 2TB HD.
Please what i need for el Capitan instalation?
From wher download OS, and other things and instalation steps
Sorry for the bad English, it is one of the reasons why I can not find the answer in the forum.