Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

fossxplorer

macrumors newbie
Nov 15, 2016
2
0
This is exactly what i did.
1. Installed a MacPro 5,1 with Sierra
2. Connected the disk from 3,1 into 5,1 and started in Restore mode. Restored Sierra into the disk from 3,1
3. Deleted the SupportedPlatform.plist (if you don't you will see a grey STOP sign when you boot the 3,1 with Sierra).

Works perfectly!


you can just remove that plist, much easier.
 

tpiselli

macrumors newbie
Jun 16, 2016
16
11
PASSED-Ran the following command from the Terminal to get the board id and saved the it on the iMac:
ioreg -lp IOService | grep board-id
PASSED-Connected mac3,1, via firewire, to my 2010 iMac which is Sierra supported.
PASSED-Downloaded Sierra on the iMac
PASSED-Booted mac3,1 in target disk mode; both drives showed up on the iMac.
PASSED-Launched the Sierra installer.
PASSED-Selected the disk "extra" as the target for the installation.

NOT SURE-The installer started and after copying some files the iMac restarted and went directly into the installer. The installation continued without error until it finished at which time the iMac restarted again.

Things started as described, however, I stepped away, and I'm not exactly sure what I returned to find. :(

NOT SURE-The restart caused the iMac to run Sierra (using the "extra" drive from mac3,1) and was waiting for me to enter a password to continue. At this point I shutdown both computers. I restarted the iMac and held down the Option key which allowed me to select the iMac's normal start up disk. Once the iMac restarted I once again restarted mac3,1 in target disk mode.

My Mac Pro actually shut down (at some point), not restarting as described above. And, my MacBook Pro3,1 remained in Target Disk Mode. When I started the Pro, I didn't seem to have to change the Startup Disk.

FAILED (miserably)-Once the drives were again visible on the iMac I used the Terminal to edit the PlatformSupport.plist file. The command I used was: sudo view /Volumes/extra/System/Library/CoreServices/PlatformSupport.plist
The view command is a variant of Vi so you'll need to know Vi to edit the file. I added a line for the board id for the value we got from the command we ran earlier and a line for the model properties using the value of MacPro3,1.
Of course the command:
sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist
can work just as well.

I could not, for the life of me, edit the .plist file, which appeared as Locked in TextEdit. And I "googled" and tried everything I could possible find. This command thing is not really my forte, and so, even though I understand the adding a line concept, it didn't happen, as much as I would have liked things to work.

Any words of wisdom?

Could it be that my MacBookPro3,1 doesn't have the necessary processor capabilities to handle the upgrade to Sierra? Someone mentioned the following, which nobody else seemed to touch upon: "The MacBookPro 3,1 isn’t supported by this patch, due to the CPU not supporting SSE4.1." Unfortunately, I'm not really sure what it means.

So close, yet so far.

NEVER GOT HERE-After editing and saving the PlatformSupport.plist file I shutdown mac3,1. I then restarted mac3,1 while holding the Option key which allowed me to select the drive "extra" to startup from. The computer started and asked me for my password after which the setup program started and eventually I was in macOS Sierra.

So that's it. This is the same process I used for my 2008 Xserves for OS X 10.9 and 10.10 and should work with some of the other computers that are now no longer supported. Enjoy
[/QUOTE]

So, a couple of things:
- Based on this thread: https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/ your computer won't be able to run Sierra as the the CPU doesn't have the instructions (SSE4.1) that Sierra now requires.

-As for editing the .plist file you mentioned using TextEdit. If you want to use TextEdit you'll need to launch TextEdit as root (or whichever user owns the file). That's why the command that's run from the Terminal app starts with sudo.
 

StuLaFish

macrumors newbie
May 12, 2007
4
0
Westchester County, NY

So, a couple of things:
- Based on this thread: https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/ your computer won't be able to run Sierra as the the CPU doesn't have the instructions (SSE4.1) that Sierra now requires.

***Isn't a MacBookPro3,1 a MacBookPro3,1? Why would my CPU be any different from the others' who have successfully installed Sierra on their machines?

-As for editing the .plist file you mentioned using TextEdit. If you want to use TextEdit you'll need to launch TextEdit as root (or whichever user owns the file). That's why the command that's run from the Terminal app starts with sudo.[/QUOTE]

***Is the "sudo" command run in lieu of launching TextEdit as root? Or, do both have to occur?

Thanks.
 

nigelbb

macrumors 65816
Dec 22, 2012
1,150
273

So, a couple of things:
- Based on this thread: https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/ your computer won't be able to run Sierra as the the CPU doesn't have the instructions (SSE4.1) that Sierra now requires.[/QUOTE]
It's the Woodcrest & Clovertown Xeons in the MacPro 1,1 & 2,1 that don't have the SSE4,1 instructions. The Harpertown Xeons in the Mac Pro 3,1 do have the SSE4,1 instructions.
 
  • Like
Reactions: Synchro3

tpiselli

macrumors newbie
Jun 16, 2016
16
11
So, a couple of things:
- Based on this thread: https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/ your computer won't be able to run Sierra as the the CPU doesn't have the instructions (SSE4.1) that Sierra now requires.

***Isn't a MacBookPro3,1 a MacBookPro3,1? Why would my CPU be any different from the others' who have successfully installed Sierra on their machines?

-As for editing the .plist file you mentioned using TextEdit. If you want to use TextEdit you'll need to launch TextEdit as root (or whichever user owns the file). That's why the command that's run from the Terminal app starts with sudo.

***Is the "sudo" command run in lieu of launching TextEdit as root? Or, do both have to occur?

Thanks.[/QUOTE]
Ok; so I think I see the confusion on my part. The computer you keep mentioning is a MacBookPro3,1, where as this thread is about the MacPro3,1 (please notice the presence/absence of the word Book). If you have a MacPro3,1 then yes, your CPU is fine and will run Sierra without any issues. If you have a MacBookPro3,1 then it won't run Sierra. I hope this clears things up.

As for the plist file, you'll need to use one method or the other, not both. However, I tried running TextEdit with elevated privileges and got the following:
driftingfeather:~ tpiselli$ sudo "/Applications/TextEdit.app/Contents/MacOS/TextEdit"
Password:
Illegal instruction: 4

So, the easiest way may be to simply delete the file if your not comfortable with editing files via the command line. You may want to also try using an app like TextWrangler which I believe can elevate privileges when needed. I'd get TextWrangler from the BareBones website rather then the app store (if it's even still in the app store).
[doublepost=1479658838][/doublepost]
So, a couple of things:
- Based on this thread: https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/ your computer won't be able to run Sierra as the the CPU doesn't have the instructions (SSE4.1) that Sierra now requires.
It's the Woodcrest & Clovertown Xeons in the MacPro 1,1 & 2,1 that don't have the SSE4,1 instructions. The Harpertown Xeons in the Mac Pro 3,1 do have the SSE4,1 instructions.[/QUOTE]

I agree but, the author of the post I was responding to keeps mentioning the computer as a MacBookPro3,1 and not a MacPro3,1. If he has a MacPro3,1 then yes, the CPU supports the instructions but, a MacBookPro3,1 doesn't.
 

StuLaFish

macrumors newbie
May 12, 2007
4
0
Westchester County, NY
My MacBook Pro 3,1 has a 2.4 GHz Intel Core 2 Duo processor. I found the following online at cpu-word.com:

Core 2 Duo

  • » Core microarchitecture
  • » 0.045 and 0.065 micron
  • » Desktop CPU
  • » Dual core
  • » Up to 3.33 GHz
  • » Up to 6 MB L2 cache
  • » Up to 1333 MHz FSB
  • » 64-bit
  • » Execute Disable bit
  • » SSE3, SSSE3, SSE4.1
  • » Virtualization
  • » Trusted Execution
Socket 771
Socket 775

Is the SSE4.1 mentioned above not an accurate representation of the processor? Am I interpreting it incorrectly?

Thanks.
 

tpiselli

macrumors newbie
Jun 16, 2016
16
11
My MacBook Pro 3,1 has a 2.4 GHz Intel Core 2 Duo processor. I found the following online at cpu-word.com:

Core 2 Duo

  • » Core microarchitecture
  • » 0.045 and 0.065 micron
  • » Desktop CPU
  • » Dual core
  • » Up to 3.33 GHz
  • » Up to 6 MB L2 cache
  • » Up to 1333 MHz FSB
  • » 64-bit
  • » Execute Disable bit
  • » SSE3, SSSE3, SSE4.1
  • » Virtualization
  • » Trusted Execution
Socket 771
Socket 775

Is the SSE4.1 mentioned above not an accurate representation of the processor? Am I interpreting it incorrectly?

Thanks.
So, as I mentioned earlier, according to the first post of this thread:
https://forums.macrumors.com/threads/macos-10-12-sierra-unsupported-macs-thread.1977128/
your MacBookPro3,1 isn't supported due to the lack of SSE4.1. If we look up all of the laptops that are designated as MacBookPro3,1, say here:
http://www.everymac.com/ultimate-mac-lookup/?search_keywords=MacBookPro3,1
we see that the 2.4 GHZ laptops have the T7700 CPU in them. If we look up the specs for the T7700, say here:
http://www.cpu-world.com/CPUs/Core_...bile T7700 LF80537GG0564M (BX80537T7700).html
we see that this CPU does not have the SSE4.1 features.
Finally, as nigelbb mentioned, this forum is for the Mac Pro desktops and not the MacBook Pro laptops so we should probably end this here.
 

jmp473

macrumors member
Apr 25, 2011
41
6
Atlanta
Success! (after too many futile attempts)

In order to install Sierra on my Mac Pro 3,1 (early 2008) I had to both use an original 2600 XT graphics card, and install from an internal drive (found 16GB for a partition on the drive I use for backup/timemachine). Flash-drive didn't work and other graphics cards - flashed 5770, GeForce GT120, Radeon RX 460, each prevented the installer from booting.



And Foxlet's thing-a-majig allowed it to update to 10.12.2 - kudos and to dosdude1 and LarrikinAus
and vivo's instructions were a great help. Many many thanks!!!

Everything so far is now working better than ever !!!

Screen Shot 2016-12-20 at 7.17.25 PM.png



(although quite curiously the RX 460 (which only shows up as R9 xxx 2048 gets fastest and highest scores with the 2600 XT also installed - but not connected to my monitor - and if I do connect both, then App Menu's don't appear correctly in the menu bar) ??? )
 

rotarypower101

macrumors 6502
Sep 28, 2007
264
3
Portland Oregon
Is there a way to load a preconfigured image for the base machine?

Are there any reasons that wouldn't work ?


How is this working for those that have had time on it?
Any issues not mentioned here?
Any specific features making it worthwhile ?
Not all experiencing the loss of Wifi/BT with the " Broadcom BCM43xx "?

What are people using for a mic for SIRI?
 

nickbatz

macrumors member
Jan 3, 2017
36
29
I have a new (to me) 5,1 that had a startup drive containing Sierra. If I remember right I went through the setup process.

Then I decided to try simply taking my startup SSD out of the 3,1 this machine is replacing. Surprise, it worked with very little intervention. Finally, I updated it to Sierra. It's been running beautifully for two weeks now.

So my question is whether I can simply remove that plist from the original Sierra drive with it on my 5,1 (while started up from the SSD), then pop it in my 3,1 and have a nice day?

Or will i have to start up from the recovery partition to do that.

TIA
 

666sheep

macrumors 68040
Dec 7, 2009
3,686
292
Poland
I again altered well known script which allows 1,1s and 2,1s survive 10.9, 10.10 and 10.11 system updates.
Known as Tiamo MacPro Fix, Pike Yose Fix and Capitan Pike Fix.
Purpose is the same as it has been before – care free OS updates.

This version's name is Sierra MP31 updates fix

What does it do:
– adds Launch Daemon which removes PlatformSupport.plist before each restart/shutdown (if it's present in CoreServices)

How to use it:
– disable SIP first (to get to the Recovery on a 3,1, you need to delete PlatformSupport.plist from com.apple.recovery.boot folder)
– install .pkg before updating the OS
– reboot twice (Launch Daemon will load on a next boot after .pkg installation)
– you can update your Sierra now
 

Attachments

  • Sierra_MP31_updates_fix.pkg.zip
    2.4 KB · Views: 467
Last edited:
  • Like
Reactions: idealtracks

Ludacrisvp

macrumors 6502a
May 14, 2008
797
363
I again altered well known script which allows 1,1s and 2,1s survive 10.9, 10.10 and 10.11 system updates.
Looks like the new thing is to add a boot.plist option to bypass the platformsupport.plist entirely.
The first flag bypasses PlatformSupport, the second allows you to use Apple USB SuperDrives on any Mac, not just ones that didn't come with a superdrive.


Code:
$ cat /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Kernel Flags</key>
    <string>-no_compat_check mbasd=1</string>
</dict>
</plist>

The SuperDrive patch seems to work, but I can't test it as my Apple USB SuperDrive seems to be faulty (won't spin up discs), but at least it shows up in my Eject menu. Note that the USB keyboard port doesn't supply enough power to recognize the drive.

Code:
Apple SuperDrive:
  Firmware Revision: 2.00
  Interconnect: USB
  Burn Support: Yes (Generic Drive Support)
  Profile Path: None
  Cache: 1536 KB
  Reads DVD: Yes
  CD-Write: -R, -RW
  DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
  Write Strategies: CD-TAO, CD-SAO, CD-Raw, DVD-DAO
  Media: To show the available burn speeds, insert a disc and choose File > Refresh Information
 
  • Like
Reactions: broadbean

robby0648

macrumors newbie
Nov 10, 2013
3
0
Brussels
I just installed 10.12 on my Mac Pro 2008 from 8 gb USB Stick.

Worked fine.

I want also to upgrade my MacPro early 2008 3.1 (MP31.006C.B05). Which upgrade guide did you use?

I did an upgrade of my other MacPro early 2009 from 4.1 to 5.1 and then to Sierra (now showing MacPro 5.1), before upgrade did csrutil DISABLE and after upgrade csrutil ENABLE again, all works fine except WiFi although I replaced the card with the recommended Apple Airport Wireless Card For Mac Pro - Network Adapter - 802.11b, 802.11a, 802.11g, 802.11n (draft) (66436H). It's no problem though because MacPro is hardwired.
 

Isidore

macrumors member
Feb 13, 2004
55
43
London
I've been following this thread for some time- I run a 3.1 as a server. I have been dithering about getting it to run Sierra to take advantage of the latest server updates and now that High Sierra will not change the hardware requirements I decided to make the move to sierra and beyond. As a first step I changed the airport and bluetooth cards for the approved later combi card and find that while airport works fine, bluetooth is just 'off' and shows 'no information found' in system report. Is this just a consequence of running an unpatched system, El Cap, so it does not expect to find such a airport/ bluetooth card, or do I have a more fundamental problem? Broken card or something else? One other question: I am slightly unclear if it is possible to run Sierra in patched form with SIP turned on. My reading of the various threads shows some conflict on this point. I really would prefer to have sip on, especially as this is a server, anyone have any advice?

Thanks in advance!
 

drolson

macrumors member
Sep 17, 2015
58
23
WI
Mac Pro 3,1, just get rid of the bluetooth card( is better anyway iMac card has bluetooth 4 ) and change the wifi card to a all in one iMac card, go to dosdude 1.com and get Sierra or Mojave, DONE!
 
  • Like
Reactions: FarmerBob

pullman

macrumors 6502a
Feb 11, 2008
771
121
¯\_(ツ)_/¯
I'm very happy I found this thread. For several days I've been banging my head against imaginary walls to get Sierra onto my 3,1 but the installer freezes each time.

I'm going to try the target disk option, but would like to know if I must edit PlatformSupport.plist using Terminal or if I couldn't just edit it in TextEdit or Smultron with the 3,1 in target disk mode from my MacBook Pro?

I'm not familiar with the rm and view commands to edit a plist.

Thank you in advance
Philip


I read this thread few times. So, the process can be simplified to 2 big steps.

1) boot as target disk mode and install Sierra by another supported Mac.

2) Reboot into recovery partition, and use terminal to run "sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist"

Am I miss something?
So here's what I have and did. Please note that I installed Sierra the day after it was available and had to go out of town shortly thereafter so I haven't played around with it very much after it was installed. My mac3,1 has two drives one of which has the current version of El Capitan while the other had an older version of OS X which I'd forgotten about. I installed Sierra on the second drive (named "extra") overtop of the existing OS X install.
-Normally I run the mac3,1 as a headless computer which I access via screen sharing but, for this install I added a monitor, keyboard, and mouse.
-Ran the following command from the Terminal to get the board id and saved the it on the iMac:
ioreg -lp IOService | grep board-id
-Connected mac3,1, via firewire, to my 2010 iMac which is Sierra supported.
-Downloaded Sierra on the iMac
-Booted mac3,1 in target disk mode; both drives showed up on the iMac.
-Launched the Sierra installer.
-Selected the disk "extra" as the target for the installation.
-The installer started and after copying some files the iMac restarted and went directly into the installer. The installation continued without error until it finished at which time the iMac restarted again.
-The restart caused the iMac to run Sierra (using the "extra" drive from mac3,1) and was waiting for me to enter a password to continue. At this point I shutdown both computers. I restarted the iMac and held down the Option key which allowed me to select the iMac's normal start up disk. Once the iMac restarted I once again restarted mac3,1 in target disk mode.
-Once the drives were again visible on the iMac I used the Terminal to edit the PlatformSupport.plist file. The command I used was: sudo view /Volumes/extra/System/Library/CoreServices/PlatformSupport.plist
The view command is a variant of Vi so you'll need to know Vi to edit the file. I added a line for the board id for the value we got from the command we ran earlier and a line for the model properties using the value of MacPro3,1.
Of course the command:
sudo rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist
can work just as well.
-After editing and saving the PlatformSupport.plist file I shutdown mac3,1. I then restarted mac3,1 while holding the Option key which allowed me to select the drive "extra" to startup from. The computer started and asked me for my password after which the setup program started and eventually I was in macOS Sierra.

So that's it. This is the same process I used for my 2008 Xserves for OS X 10.9 and 10.10 and should work with some of the other computers that are now no longer supported. Enjoy
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I'm very happy I found this thread. For several days I've been banging my head against imaginary walls to get Sierra onto my 3,1 but the installer freezes each time.

I'm going to try the target disk option, but would like to know if I must edit PlatformSupport.plist using Terminal or if I couldn't just edit it in TextEdit or Smultron with the 3,1 in target disk mode from my MacBook Pro?

I'm not familiar with the rm and view commands to edit a plist.

Thank you in advance
Philip
Any text editor can do the job, but you may need to fix permission afterward.

Anyway, it seems you don't need to edit anything, just remove that file. (of course, you can add the 3,1 info into that list. It's up to you)
 
  • Like
Reactions: pullman

pullman

macrumors 6502a
Feb 11, 2008
771
121
¯\_(ツ)_/¯
Thank you, I'll try that too if I can't edit.

Any text editor can do the job, but you may need to fix permission afterward.

Anyway, it seems you don't need to edit anything, just remove that file. (of course, you can add the 3,1 info into that list. It's up to you)
[automerge]1593516849[/automerge]
Thank you, but unfortunately High Sierra doesn't run well on my system. I posted about it in the High Sierra thread. I keep getting weird behaviour in Finder and bluetooth (on a supported wifi+bt card) does not work reliably. That's why I'm looking at Sierra.

Or, at this point, you can use the patcher tool: http://dosdude1.com/highsierra/
 

pullman

macrumors 6502a
Feb 11, 2008
771
121
¯\_(ツ)_/¯
When I run the Install macOS Sierra app from my MacBook Pro (2013) there's an error "This copy of the “Install macOS” application is too old to be opened on this version of macOS."

I'm not sure how to get around this. There are suggestions that I need to use a bootable USB or external drive. But in that case, how do I access the Mac Pro over target disk mode?

Thanks in advance
 

pullman

macrumors 6502a
Feb 11, 2008
771
121
¯\_(ツ)_/¯
Eventually it worked on my 3,1 (SIP disabled and BCM94360CD wifi+bt card installed).

At first I couldn't create a bootable usb installer. My MBPr (2013/Mojave) kept complaining that the target volume (a USB-attached 2,5" drive) wasn't "a valid mount point". The solution here helped me edit the installer version number in the relevant info.plist. Then I could create a bootable installer using the createinstallmedia command.

I booted the Mac Pro in target disk mode and rebooted my MBP from the installer volume. Then I selected the Mac Pro target disk and installed away. It went well, though it seemed possibly to go a little bit slower than I'm used to, likely due to the USB2+thunderbolt+firewire connection.

I then rebooted the MBP from its normal boot volume and added my board ID and computer spec to PlatformSupport.plist. I encountered no permissions problem but could save the file.

Then I booted into Sierra and it seems to work like a charm.
 

cap_walker_666

macrumors member
Aug 3, 2020
71
5
Key Notes:


As Apple has decided to not support Sierra on the MacPro 3,1 , there needs to be modifications performed to allow Sierra to be installed on the Mac Pro 3,1

This installation guide ONLY applies for the Mac Pro 3,1.

I performed these steps on El Capitan - I have no idea if they will work on OS’s prior to that.

Note that the only way you’ll be able to install Sierra is to create a boot partition of the Sierra install - you won’t be able to simply double click on the install from a running OS.

——————————————
WARNING:

This could bork your machine. Do this at your own risk. I offer no guarantees or any sort of assurance that this will even work.

Ensure you have a full backup of your drive and also have an El Capitan (or whatever OS) install disk available in the event you need to roll back and restore.

——————————————--
Known issues in Sierra for Mac Pro 3,1

WIFI does not work and therefore location services does not work.

Fix: Purchase one of these http://www.osxwifi.com/apple-broadc...-4-0-with-adapter-for-imac-2007-and-imac-2008 and install it. It is natively supported by OSX and will give you Wifi AC and Bluetooth 4.0. All the functionality shown at WWDC should (can’t promise it will) work with that card.Without it, a lot of the functionality shown at WWDC will not work (such as auto unlock / universal clipboard / apple pay).

——————————————
THINGS YOU WILL NEED BEFORE YOU START

1. A copy of Sierra OSX - save it on your DESKTOP

2. A partition on your SATA hard drive – minimum 10 gig – that will be your initial boot / install drive for OSX - this will also be your recovery drive so its something you’ll need to keep on an ongoing basis to maintain the system. This hard drive must be plugged into your SATA port. Note that this CANNOT be a USB Stick or USB drive – I tried this and it failed. I could only get this to work using a partition on my hard drive plugged into my SATA port.

3. A copy of this file OSInstall.mpkg (save it somewhere as you’ll need it later in the steps listed below) - http://s000.tinyupload.com/index.php?file_id=09475824704156756445

4. A copy of this file IORegistryExplorer 3.0 - can be downloaded from here. Save it and keep it in a safe place as we’ll need it in the steps below later. http://www.osx86.net/files/file/3600-ioregistryexplorer/

5. THIS ONLY APPLIES IF YOU HAVE A PC BASED NVIDIA CARD: NVIDIA Web Driver for Sierra MacOS - save this file for later - do not run it now. http://www.insanelymac.com/forum/to...ver-updates-for-macos-sierra-update-06132016/

6. A Mac EFI supported card that does not require the NVIDIA web driver

——————————————
1. Open Disk Utility

2. Select the SATA partition you are going to use for the initial install / boot drive (note that this is NOT the same drive as the DESTINATION drive you’ll actually install Sierra on - this is your initial boot drive that you’ll use purely to install Sierra onto your main boot drive). You will need a minimum of 10 gig - I set mine to 20 gig to be safe. Select a volume name. For the sake of this tutorial, we’ll assume you set the VOLUME name to BOOTIE - I will refer everything going forward as BOOTIE but if you call it something else, then replace my BOOTIE name with whatever you called it.

3. Format this partition using OSX Extended Journaled and GUID Partition

4. When this has completed, open up terminal.

5. Type this command into terminal and hit enter: defaults write com.apple.finder AppleShowAllFiles TRUE (you do not need to use SUDO)

6. Type this command into terminal and hit enter: killall Finder (you do not need to use SUDO)

7. Leave the terminal window open but go back to your desktop.

8. Right click on the OSX Sierra Installer App and select “SHOW PACKAGE CONTENTS". Mine is called Install 10.12 Developer Preview.

9. Browse to the folder /Contents/SharedSupport

10. Double-click to mount “InstallESD.dmg”

11. Within the InstallESD image, you’ll find in the root directory a file called “BaseSystem.dmg”. Double-click to mount “BaseSystem.dmg”

[NOTE] these next steps, in theory, can be replicated a different way using the restore method on disk utility - I tried that and it failed on me twice, so I did not use disk utility to do this, but rather the way I describe next - so I suggest you follow exactly what I did to get it working

12. Go back to terminal

13. Switch to root user by typing sudo su -

14. Enter your password when prompted from typing in sudo su -

15. Type this command into terminal and hit enter: cp -a /Volumes/"OS X Base System"/ /Volumes/BOOTIE/

16. Wait until copy is complete - you won’t get any sort of progress bar or verbose output - but it is working - just give it time. It took mine about 5 minutes.

17. Go back to your desktop

18. Using Finder, click on your BOOTIE partition

19. Go to the folder /System/Installation and delete the "Packages" alias file.

20. Now go back to the mounted InstallESD.dmg and drag the "Packages" folder into the BOOTIE partition folder of /System/Installation where the alias file called “Packages" used to be (i.e., the one you just deleted in step 19).

21. Still in InstallESD.dmg, copy the files “BaseSystem.dmg” and “BaseSystem.chunklist” to the root directory of the BOOTIE partition.

22. You can now unmount BaseSystem.dmg and InstallESD.dmg - you won’t be needing them again

23. Time to get that file you downloaded before you started called OSInstall.mpkg and copy it to the BOOTIE partition /System/Installation/Packages - select YES to replace the file that is already there

24. Now time to load the application IORegistryExplorer 3.0 which you downloaded before you started

25. In the left hand side of the application, you’ll see it says “Root" (which by default is selected) then a drop down to -> MacPro 3,1

26. Select MacPro 3,1 by clicking on it

27. On the right hand side you’ll see a value called “board-id”. Click on the VALUE field of the board ID and copy into the clipboard the part that looks like Mac-F42C88C8 (yours might be slightly different, so that’s fine if it is - copy your one) - do not copy the quotation marks

28. Close the IORegistryExplorer 3.0 application

29. Go back to BOOTIE in finder, and browse to the directory /System/Installation/Packages/

30. Using TextEdit, edit the file InstallableMachines.plist

31. Inside the file, go down to the last entry which will look something like this:

<string>Mac-942B5BF58194151B</string>

Replace the Mac-942B5BF58194151B text with your clipboard data which is your board ID that you copied in step 27. So it should now look something like

<string>Mac-F42C88C8</string>

32. Save the file and exit

33. Now in the BOOTIE in finder, browse to the directory /System/Library/CoreServices/

34. Using TextEdit, edit the file PlatformSupport.plist

35. Repeat step 31 inside this file - but do not exit the file at this stage.

36. Whilst remaining in the same file, scroll further down (it should only be a few lines down) to where you see:

<string>MacPro6,1</string>

change this to:

<string>MacPro3,1</string>

37. Save the file and exit

38. Now go back to terminal.

39. In terminal, type these commands and hit enter after each command

sudo bless --folder /Volumes/BOOTIE --file /Volumes/BOOTIE/System/Library/CoreServices/boot.efi

defaults write com.apple.finder AppleShowAllFiles FALSE

killall Finder

40. THIS STEP ONLY APPLIES TO PEOPLE RUNNING THE NVIDIA OPEN WEB DRIVER DUE TO HAVING A PC BASED NVIDIA CARD INSTALLED IN THEIR MAC PRO - go to step 41 if this does not apply to you

whilst still in terminal, type this command and hit enter:

sudo nvram boot-args="nv_disable=1”

41. Reboot (SHUTDOWN IF YOU HAVE A PC BASED CARD AS NOW IS THE TIME YOU NEED TO REMOVE YOUR PC CARD WITH THE EFI MAC CARD THAT DOESN’T REQUIRE A WEB DRIVER)

42. Hold down the ALT key when you hear the chime. Select the EFI drive (which will be BOOTIE) as your boot drive. Boot and install OSX as you normally would.

43. Once installed, your computer will automatically reboot. However, you are still not ready to boot using your new, normal boot drive.

44. Once again, hold down the ALT key and select the EFI BOOTIE drive.

45. Select TERMINAL

46. type this command and hit enter: rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist

*note* that MAIN DRIVE NAME is the name of your new boot drive - not BOOTIE

47. THIS STEP ONLY APPLIES TO PEOPLE RUNNING THE NVIDIA OPEN WEB DRIVER DUE TO HAVING A PC BASED NVIDIA CARD INSTALLED IN THEIR MAC PRO - go to step 49 if this does not apply to you

type this command and hit enter: csrutil disable

48. NVIDIA web driver people - go to step 51, everyone else, continue.

49. Reboot and this time you are free to boot with your new boot drive with Sierra installed.

50. Finished if you don’t have a PC based Nvidia card that requires the NVIDIA web driver.

**note** if you use a SSD, you'll need to re-enable TRIM

to do this, type the following in terminal:

sudo trimforce enable
------
51. Reboot and boot into your new, normal, Sierra boot drive (i.e. not BOOTIE)

52. Install the NVIDIA web driver that you downloaded before you started

53. Shutdown your computer (not reboot)

54. Pull out your EFI mac card, and put back in your NVIDIA PC card

55. Turn Mac Pro back on and boot with your normal drive which now has Sierra installed. Your card should now work

**note** if you use a SSD, you'll need to re-enable TRIM

to do this, type the following in terminal:

sudo trimforce enable

—————————————
MAINTAIN SIERRA

If you apply an update to Sierra via the App store, and you find that you are unable to boot post that update (we don’t know yet how often this boot issue will occur because there have been no updates yet), you’ll need to do the following:

1. Hold down the ALT key when you hear the chime on boot

2. Select BOOTIE EFI drive

3. Open TERMINAL

4.type this command and hit enter: rm /Volumes/[Main Drive Name]/System/Library/CoreServices/PlatformSupport.plist

*note* that MAIN DRIVE NAME is the name of your new boot drive - not BOOTIE

5. Reboot and you should be fixed

*note* if you have a PC based card, you are naturally going to have to swap cards back to perform these steps
How simple can this process be made ? I have a 3.0 that I need to have other than snow leopard on it. I'm not following some of the deeper instructions. So I wonder are there modified files or automation to accomplish this ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.