Wow, thanks once again, brother! That's really comprehensive. I will have to read it over a few times to stitch it all together in my head. Just one initial Q: replacing the boot.efi's as you have outlined; that is what the PikeYoseFix patch was doing, ...correct? Thus I would not need to run that fix-patch once I perform the replacement of the boot.efi's as outlined…?
The 'Fix' is a script that checks whether the boot.efi in /Volumes/Yosemite/System/Library/CoreServices and /Volumes/Yosemite/usr/standalone/i386 are modded, or stock . . . if an Apple update decides to replace (e.g., "re-stock") said boot.efi's, the script notices the change, and re-copies the modded boot.efi back over the re-stocked boot.efi's
As the copy of Yosemite was “pre-patched” I'm just a little unclear what it was pre-patched with. And just what the pipe-line to getting this all going is. I'm assuming the pre-patch was the boot.efi's, and then the PikeYoseFix was to allow the upgrades to 10.10.5.
https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-yosemite.1740775/
More specifically (as noted--and written--by
@Hennesie2000):
https://www.icloud.com/pages/AwBUCA...ite_on_a_Mac_Pro_1,1_or_2,1_-_Boot.efi_Method
The | is to allow one to get an install running as effortlessly as one with a 'Supported' piece of hardware could.
pre-patch is more than just the boot'efi's (see "_Method", above), and 'The Fix' does not allow upgrades, but "fixes" what the upgrades do . . . .
I have a El Capitan installer flash I bought off eBay, could I just forget about Yosemite and move forward clean into 10.11.x?
You can, and it will probably work (God knows there are way, way too many variables involved in these types of things to safely say "Yah; this always wurks.").
I'm writing these words from within 10.10.5 (daily-driver), even though I've run-through four or five handfuls of clean 10.11.x installs.
This is my current Stable, baseline environment, and I would not replace this with anything I have not fully tested.
As for your eBay purchase (and any pre-patched installer d/l from teh interwebs): you are placing a great deal of trust in the veracity of another's works, and you need to accept that you know not what you are getting, or installing (much like a .dmg "...from an unknown developer").
My choice is that which I create by-mine-own-hand from legitimate Apple sourcing, that it provides the degree of Trust I need to conduct my Business.
On the flip-side . . .
I trust Pike--and Pike's creations--as I've sourced the code since Tiamo first psoted it, and have inspected every line of the code. I understand far less than I would like (most of it's as good as a Chinese manuscript, to me), but I can and have seen all the changes, throughout. What I do know is that Pike's mods only make it possible for those of us with un-supported" hardware to avail ourselves of the latest OS'es.
Pike's a real fsck'n bad-as coder . . . .
Give the
@Hennesie2000 guide a look-see, that it may educate on what you have in the pre-patch, and that you become confident in knowing further what these things are, and how they work.
Another note, my SSD totally crashed after I attempted a re-install with the pre-patched Yosemite. Can't even format it now, Can't see last blocks error msg. So I guess it really just gave up the ghost after just a month, grrr. Thus I have to send it back to RamJet and get an exchange, so I won't be able to get this all working until I get the new SSD. So if I go dark for a time, that's why. I will keep you informed once I get everything up and running again and moving forward with software.
And again, thanks sO much for the solid you are doing me with this. I really appreciate you taking the time and making the effort to go over all this with a noob like me. Really makes my day, TBT.
You're welcome. Glad these thoughts are of some help.
"Forward..."
Hit ya back soon as I get my new drive.
peace, brother | deg