Skip to content

← All issues

[Bug]: When tahoe finishes installing in recovery the partition created called install macos said that macos had an error installing and when i tried to go on it again the screen went blanck

· by @Pedroinsti

bug

Mac model / Mac-Modell

T2 — MacBook Pro 13-inch (2018, 4 Thunderbolt 3 ports)

Target macOS version (if it is about malicious forks, typosquatting sites or security vulnerabilities, write - instead) / macOS-Zielversion (falls es um Typpfehler-Webseiten, Typpfehler-Repository oder Sicherheitslücken handelt, schreiben Sie stattdessen ein - )

Macos tahoe 26.6

OpenCore Legacy Patcher T2 version (Please state the version clearly, not state as version new or something. / Bitte die exakte Version nennen, nicht nur etwas oder neu.)

4.0.0.190008.1 - 4.0.0 alpha 19.8.1

Issue type or recommendation / Typ Fehler oder Empfehlung

Installer error / Installationsfehler

Description / Beschreibung

Image here is after rebbotimg and trying to do it again

Steps to upload the logs of the kernel panic if any (if not, you can skip this step or write -) / Schritte zum Hochladen der Protokolle des Kernel-Panics, falls vorhanden (falls keiner, dann Sie können das überspringen oder einen - schreiben)

No response

Panic log (if any) / additional notes (if any) / Panikprotokoll (falls einer) / zusätzliche Notizen (falls einer)

Comments

@sonimcrinebru-art ·

@Pedroinsti

Was this after stage 1 where the Apple logo and progress Bar with a timer showed up? If so, this is an ongoing issue with the T2 and currently @zkennedy137 is solving it.

@Pedroinsti ·

@sonimcrinebru-art when the bar started loading after 3 min it said that

@sonimcrinebru-art ·

@Pedroinsti

Then that is a issue ongoing on T2 Macs that @zkennedy137 is working on.

@Pedroinsti ·

@sonimcrinebru-art okey thank you when its fixed could you tell me?

@sonimcrinebru-art ·

@Pedroinsti

You can see this issue's progress in #519.

@Pedroinsti ·

Image @sonimcrinebru-art does this update has anything to do

@Medelcartelinc ·

@Pedroinsti No, unfortunately this update (4.0.0.190008.2) does not fix your Stage 2 installation error yet.

Here is why:

  • What that release changed: Release 4.0.0.190008.2 updated PatcherSupportPkg, improved post-install kernel cache rebuilding, and fixed Wi-Fi Darwin version checks. It does not yet include a bypass for the Stage 2 installer failure.
  • Why your 2018 MacBook Pro 13" (MacBookPro15,2) fails in Stage 2:
    During Stage 2 (about 3 minutes into the installation bar), macOS runs OSIUpdateFirmwareElement to check and stage BridgeOS firmware for your T2 chip. Because Apple dropped 2018 Macs from Tahoe, the installer does not contain signed BridgeOS firmware payloads for your model, causing the installer to fail and abort with "macOS had an error installing".

This is the exact issue we are actively working on and solving right now in Discussion #519. We have already identified the exact selector (-[OSIUpdateFirmwareElement runReturningError:]) and successfully verified a working bypass in testing.

Keep an eye on #519 — once the Stage 2 bypass is packaged into an OCLP build, 2018 T2 Macs like yours will be able to complete the installation smoothly!

@Pedroinsti ·

@sonimcrinebru-art okay thank you so much if you need testing in something for thsi specific model tell me

@albert-mueller ·

@Pedroinsti No, unfortunately this update (4.0.0.190008.2) does not fix your Stage 2 installation error yet.

Here is why:

  • What that release changed: Release 4.0.0.190008.2 updated PatcherSupportPkg, improved post-install kernel cache rebuilding, and fixed Wi-Fi Darwin version checks. It does not yet include a bypass for the Stage 2 installer failure.
  • Why your 2018 MacBook Pro 13" (MacBookPro15,2) fails in Stage 2:
    During Stage 2 (about 3 minutes into the installation bar), macOS runs OSIUpdateFirmwareElement to check and stage BridgeOS firmware for your T2 chip. Because Apple dropped 2018 Macs from Tahoe, the installer does not contain signed BridgeOS firmware payloads for your model, causing the installer to fail and abort with "macOS had an error installing".

This is the exact issue we are actively working on and solving right now in Discussion #519. We have already identified the exact selector (-[OSIUpdateFirmwareElement runReturningError:]) and successfully verified a working bypass in testing.

Keep an eye on #519 — once the Stage 2 bypass is packaged into an OCLP build, 2018 T2 Macs like yours will be able to complete the installation smoothly!

https://github.com/albert-mueller/OpenCore-Legacy-Patcher-T2/discussions/519

@zkennedy137 ·

@albert-mueller @Medelcartelinc @gandolf243 @sonimcrinebru-art

I cannot guarantee this will work as I haven’t tested it. So I tried to get Claude to update the kext to Hooke the osinstallersetupd process and inject the value 1 for OSIUpdateFirmwareElement=1 it refused. So
I took the repo link to SpoofVMM.kext and asked Gemini it happily ablidged. Now that being said again do not treat this as a fix as I have not tested it. But here is a zip containing the new source code that one of you could try to test if you get the chance before I get home from work.

SpoofVMM_Plugin_Source.zip

@Pedroinsti ·

@albert-mueller the new updates fix that?

@zkennedy137 ·

@albert-mueller the new updates fix that?

It is an attempt to, like I said I haven’t actually compiled the kext and tried it etc. but if that @Medelcartelinc discovered is the issue it should help I think.