Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After Security Update 2018-001, MacPro 1,1 no longer boot #32

Open
r2d3 opened this issue Jan 25, 2018 · 2 comments
Open

After Security Update 2018-001, MacPro 1,1 no longer boot #32

r2d3 opened this issue Jan 25, 2018 · 2 comments

Comments

@r2d3
Copy link

r2d3 commented Jan 25, 2018

My MacPro 1,1 using Piker boot.efi worked fine until the last "Security Update 2018-001".

Now, the machine starts booting then loop back to chime ...

In verbose mode, no "interesting" (for debug) message seems to be shown.

Any idea ?

@ghost
Copy link

ghost commented Jan 25, 2018

I had the same problem (see this thread) and was able to recover by restoring my last full backup.

Alternately, some people on that thread have been able to simply re-install their 'pikified' USB install image to the broken target disk to recover, preserving user data and settings.

Going forward, I logged in as 'admin' and set that Security Update 2018-001 to be 'hidden' and will be sure to check that macrumors.com thread before applying any other kernel updates in future.

@b23prodtm
Copy link

b23prodtm commented Nov 18, 2024

Get another Mac and plug in the HD in it (external is) we need to copy boot.efi into /System/Library/CoreServices/. and /usr/standalone/i386 because it was overwritten by the security update. That’s it !
Source:https://www.lecafeduretro.fr/2019/09/installer-mac-os-x-el-capitan-sur-un.html?m=1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants