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

[Macschrauber]

Did someone full restart fron Scratch ?

Installing El Cap on a supported machine with all updates including darn latest security update, replaced both boot.efi and edited the platformsupport.plist ?

I cannot do that as I am away from my machines the next days, be hopefully next week back.
[doublepost=1516919086][/doublepost]

e update the boot.efi file in the:
- system —> Library —> Core services and
- usr—> standalone—> i386
- recovery partition.

Anybody have any t

Do you have the correct PlatformSupport.plist ? There must be an entry for 1.1 board ID in.

See http://www.caradimas.org/john/?p=193

 

[hwojtek]

I managed to restart thanks to the image ... the problem is Safari, back to version 9.1 and I can not update because it is included in the update 2018

http://swcdn.apple.com/content/down...5cnrlpdpys0xmdf51pw/Safari11.0.2ElCapitan.pkg

Surprisingly, the above link downloads 11.0.3 for El Capitan.

 

[SuperMatt]

http://swcdn.apple.com/content/down...5cnrlpdpys0xmdf51pw/Safari11.0.2ElCapitan.pkg

Surprisingly, the above link downloads 11.0.3 for El Capitan.

I was at 10.11.6, Safari 11.0.3 doesn't show up in App Store updates. But then I installed the Security update 2017-001 and rebooted. It now does show up and can be installed.

 

[AL1630]

So since it seems Sierra or higher is effectively impossible to install on a 1,1 or 2,1 because of the new instruction sets, and this new update seems to break every El Capitan install, could this be the true end of the road for these machines, or can we just skip over this update and keep going until support ends?

 

[Mystere65]

http://swcdn.apple.com/content/down...5cnrlpdpys0xmdf51pw/Safari11.0.2ElCapitan.pkg

Surprisingly, the above link downloads 11.0.3 for El Capitan.

[doublepost=1516947972][/doublepost]Unfortunately, the link does not go

 

[HugoMe]

You could use the pike installer application (page 56) running on ssd2 and then select ssd1 as the install target being careful not to at any point to delete the ssd1 drive. A fresh install will overwrite the system files but keep your other app/settings/data/icloud stuff unless you select fresh install in the installer options. Until we know what files are affected this maybe your only route to fix ssd1 unless you changeout your gpu to boot supported model and run a restore. Ive restored from pike USB stick re-installing the OS to my failed boot loop disk but not direct from another OS running the installer. Should work though.​

Thanks. This is very useful
I understand my path is to :

1. Retrieve a version of Installer Os X El Capitan.

I have a backup version dated 24/01/16 which according to https://en.wikipedia.org/wiki/OS_X_El_Capitan is 10.11.3​

2. Perform pike installer application (page 56)
3. Update El Capitan up to 10.11.6

Thanks to post #3847 (page 154), I've been able to retrieve the updater.
(I needed to install the mega application)​

4. Apply security updates without applying the last one

It's not clear to me how to get them. Post #3849 seems to say there online, but i don't see them sofar in safari. Or maybe they won't be necessary as they would have been preserved through previous steps.
​

I'll keep you posted

[UPDATE]
Actually you can get 10.11.6 directly from the app store through this page Get OS X El Capitan if you use a second Mac which is el-Capitan compatible. Apple is sneaky as you can't find it through the Apple Store search engine...
On second thought, I'll rather try that.

 

[Ant3000]

So since it seems Sierra or higher is effectively impossible to install on a 1,1 or 2,1 because of the new instruction sets, and this new update seems to break every El Capitan install, could this be the true end of the road for these machines, or can we just skip over this update and keep going until support ends?

As I understand it, support ended for the MacPro1.1/2.1 a long while ago. Without the help of the great people on this forum we would perhaps all have been forced to move on a long while ago. It has been made to work without any help from Apple. Whether or not there is a workaround for the recent security update won't be addressed by Apple I am sure and may not be necessary as the chips used appear to not be affected by the issues on other Intel chips according to some reports. We just have to learn to dodge these bullets.

 

[hwojtek]

Unfortunately, the link does not go

It does, 5 seconds ago:

Why does it download the .2 instead of .3 I downloaded yesterday I have no clue however. Perhaps something to do with the content delivery network, as I am in a very different location right now.

 

[Mystere65]

Downloaded from here
https://www.techspot.com/downloads/downloadnow/4185/?evp=e88fa7dde729eadd7478088bf9808c66&file=2

Thanks

 

[biglouie]

OK i managed to figure out how to recover if you have installed the Security 2018-001 by accident and you are stuck in the boot loop. The solution will require a El-capitan compatible machine.

1. Put the borked mac in 'target disk' mode.
2. Connect the borked mac to the El-Capitan Mac via Firewire.
3. Make sure the boot disk of the Borked mac shows up on the desktop of the El-Cap Mac.
4. On the El-Cap Mac, go to System preferences -> Startup Disk and select the Borked Mac boot disk.
5. Reboot the El-Cap Mac with the Borked Mac boot disk.
6. If all goes well, it will reboot and go into an El-Cap OS installer. Agree on the terms and conditions and Ciick install.
7. The installer will start installing. Be patient, it will take a while (it took 25mins on mine). When it is done it will reboot.
8. After rebooting, go to System preferences -> Startup Disk and select the El-Cap boot disk. Reboot.
9. Once booted, replace the Borked Mac's boot.efi in system/Library/Core services and usr/standalone/i386 and the recovery partition with Piker's version.
10. Eject the Borked mac's boot disk from the El-Cap Mac.
11. If you have done it correctly, your Borked Mac should boot. You can breathe a sigh of relief now.

 

[F1Mac]

So since it seems Sierra or higher is effectively impossible to install on a 1,1 or 2,1 because of the new instruction sets, and this new update seems to break every El Capitan install, could this be the true end of the road for these machines, or can we just skip over this update and keep going until support ends?

Support ended long ago, we just tried to build a longer road ourselves. Ever since someone came with the idea (and possibility) to install Mountain Lion on these Macs, we were on uncharted and 100% unsupported territory. The fact is we *shouldn’t* install 10.8, 10.9, 10.10 and 10.11 on these machines. But we do and it works fine, until it breaks... Apple supports the OS, not the incompatible machine we’re running it on.

El Capitan on these Mac Pros works absolutely fine without this security update. I would be very cautious with future security updates however. Apple will stop supporting 10.11 at the end of this year anyway (or is it next year?). But the Mac Pros will still continue to work

 

[Macschrauber]

@biglouie
DID I got you right:
You ran the Recovery on a supported machine via target mode.
So the recovery boot.efi was 64bit

Should not work when one patched the recovery as well. Afaik the 32bit efi will not boot a 64 bit Mac Pro.

 

[sOwL]

Meh, My Mac Pro now feels like a Hackintosh. I also installed the update and was stuck in bootloop (which is even more annoying for me because it's a headless computer nowadays) and I thought to check on here. Thankfully I clone the drive daily so I can boot directly to yesterday's backup.

So, are we royally screwed with this? We can't install this update in any way? Seems like a sever security concern. Does it only applies to the playback of audio files? Is it safe if audio files are never executed?

 

[we6drucks]

So not sure if I just lucked out or my machine was as broken as the rest. But I was stuck in a boot loop and the only option I could get to work at all was booting into recovery. I tried rebooting from both of my drives with an OS on it, one with the hacked El Captain and the other with Lion. So I thought I was going to have to take the long way. But I figured let's try the recover from Time Machine back up and see what happens, can't hurt right..... so then about 40 minutes later I am up and running. So far so good, fingers crossed....I will verify that the pinkers boot files are still there and update if I have any issues. Thank goodness for back ups

 

[Mystere65]

https://eclecticlight.co/2018/01/24/what-is-in-the-el-capitan-security-update-2018-001/

it will be rather difficult

 

[sOwL]

https://eclecticlight.co/2018/01/24/what-is-in-the-el-capitan-security-update-2018-001/

it will be rather difficult

Wow, this is much more serious than it seemed. This whole meltdown/spectre thing is a huge annoyance. My machine was serving its purpose perfectly fine and now it can't be trusted. This is really really sad

 

[HugoMe]

Thanks. This is very useful
I understand my path is to :

1. Retrieve a version of Installer Os X El Capitan.

I have a backup version dated 24/01/16 which according to https://en.wikipedia.org/wiki/OS_X_El_Capitan is 10.11.3​

2. Perform pike installer application (page 56)
3. Update El Capitan up to 10.11.6

Thanks to post #3847 (page 154), I've been able to retrieve the updater.
(I needed to install the mega application)​

4. Apply security updates without applying the last one

It's not clear to me how to get them. Post #3849 seems to say there online, but i don't see them sofar in safari. Or maybe they won't be necessary as they would have been preserved through previous steps.
​

I'll keep you posted

[UPDATE]
Actually you can get 10.11.6 directly from the app store through this page Get OS X El Capitan if you use a second Mac which is el-Capitan compatible. Apple is sneaky as you can't find it through the Apple Store search engine...
On second thought, I'll rather try that.

Finally succeeded. I was a little cautious of pikify video who suggest to create a new account, which I did not want, so I went another way : I used another el-capitan enabled Mac to install el capitan 10.11.6 back to my bricked mac (SSD1) using #3860 procedure, hoping (falsely) that i would get the 2018 security update.
It did not work so I adapted it a little, and it worked :

1. Put the borked mac in 'target disk' mode.
2. Connect the borked mac to the El-Capitan Mac via Firewire.
3. Launch El-Cap OS installer and choose target: the borked Mac.
4. The installer will start installing. Be patient, it will take a while (it took 60 mins on mine). When it is done it will reboot.
5. On the El-Cap Mac, go to System preferences -> Startup Disk and select the Borked Mac boot disk.
6. Reboot the El-Cap Mac with the Borked Mac boot disk.
7. Once booted, replace the Borked Mac's boot.efi in system/Library/Core services and usr/standalone/i386 and the recovery partition with Piker's version. Change privileges accordingly

$ sudo chflags nouchg boot.efi # déverrouille le fichier boot.efi
$ sudo mv boot.efi boot.efi.orig # renomme le fichier boot.efi en boot.efi.orig
$ sudo cp ~/Desktop/boot.efi . # copie le nouveau fichier boot.efi
$ sudo chflags nouchg boot.efi # le déverrouille
$ sudo chown root:wheel boot.efi # attribue les droits corrects au fichier
$ sudo chmod 644 boot.efi # attribue les permissions correctes au fichier
$ sudo chflags uchg boot.efi boot.efi.orig # reverrouille les fichiers (par sécurité)​

8. Eject the Borked mac's boot disk from the El-Cap Mac.
9. If you have done it correctly, your Borked Mac should boot. You can breathe a sigh of relief now.

Now I have to figure which security updates (prior to 2018) I should install.

 

[judino28]

Wow, I'm so glad I caught this thread before I updated. It's a little sad that this is really the end of the line for us, as it was still nice to know that we thought we would still get all the El Capitan Security Updates working, but the machine and OS still works great and I'm not too worried about attacks. The Safari & iTunes updates worked fine.

 

[Iron Bridge]

Did someone full restart fron Scratch ?

Installing El Cap on a supported machine with all updates including darn latest security update, replaced both boot.efi and edited the platformsupport.plist ?

This is an important question from macschrauber before we should think about end of the road on current pikify version. Does an El Capitan disk prepared installed and updated on an officially supported EC mac upto and including the latest security 2018-001, then manually boot piked and moved to 1.1/2.1, does that configuration work? anyone?. If I had a El Capitan supported mac we would have the answer already but my other mac is a proud G3

Or indeed has anyone got SU 2018-001 working on a 1.1/2.1 or is it 100% bootloop failure or possibly graphics driver related?

SU2018-001 overwrites required piked boot files that we know for sure. I also think it tries to update NVram/SMC but to no ill effect on my 2x machines when restored pre 2018-001. The other previous 5 security updates installed through app store did not to my recollection overwrite boot files. The security updates installed as apps through app store not OS updates like 10.11.0 to 10.11.6....again to my recollection. Fingers crossed on macschrauber question which would reopen certain install methods to latest version.

 

[HugoMe]

This is an important question from macschrauber before we should think about end of the road on current pikify version. Does an El Capitan disk prepared installed and updated on an officially supported EC mac upto and including the latest security 2018-001, then manually boot piked and moved to 1.1/2.1, does that configuration work? anyone?. If I had a El Capitan supported mac we would have the answer already but my other mac is a proud G3

Or indeed has anyone got SU 2018-001 working on a 1.1/2.1 or is it 100% bootloop failure?

I had book64 installed (which automatically reinstalls pikefy boot.efi) so I can confirm that post 2018-001 i was stuck in boot loop lockup while having nevertheless the pikefy boot.efi. (and i did check it)
On top of that #3865 insists that there were significant changes on 2018 new boot.efi ( I believe one is 600+Kb while the pikefy is only 300+Kb)
So I don't think there is much hope from that direction.

 

[hwojtek]

My machine was serving its purpose perfectly fine and now it can't be trusted.

Why? The CPUs that are compatible with the 1,1/2,1 are not affected by this bug.

Does an El Capitan disk prepared installed and updated on an officially supported EC mac upto and including the latest security 2018-001, then manually boot piked and moved to 1.1/2.1, does that configuration work?

No.

Or indeed has anyone got SU 2018-001 working on a 1.1/2.1 or is it 100% bootloop failure or possibly graphics driver related?

100% bootloop failure due to massive changes in kernel, that are not supported by processors available for the 1,1/2,1. They are also not affected by Meltdown.

Fingers crossed on macschrauber question which would reopen certain install methods to latest version.

A 1,1/2,1 will never work with the 2018-001 for reasons stated above. Also the Meltdown patch is not needed for these computers.

 

[Iron Bridge]

thanks wojtek. lets see if 2018-002 needs 001. perhaps we have parked security package wise.

 

[sOwL]

Why? The CPUs that are compatible with the 1,1/2,1 are not affected by this bug.

Can you give me a source to read more on that? I thought these chips are fully exploitable by meltdown/spectre.

 

[F1Mac]

Can you give me a source to read more on that? I thought these chips are fully exploitable by meltdown/spectre.

5100s and 5300s are not affected.

https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr

 

[AL1630]

Support ended long ago, we just tried to build a longer road ourselves. Ever since someone came with the idea (and possibility) to install Mountain Lion on these Macs, we were on uncharted and 100% unsupported territory.

I guess I was a bit unclear. I meant support for El Capitan, not the Macs themselves. Hopefully apple doesn't put something else in a future El Capitan update that stops us from getting the last few updates.