[Bug]: weird issues with installers
bug
Mac model / Mac-Modell
T2 — MacBook Pro 13-inch (2020, 2 thunderbolt 3 ports, Intel)
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 - )
Mac OS tahoe 26
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.)
update when avalaible
Issue type or recommendation / Typ Fehler oder Empfehlung
Installer error / Installationsfehler
Description / Beschreibung
obviously the installers have been having issues recently. but I found something strange. the installer may be failing because of apfs failure. for some reason I can boot my native supported os which is sequoia and use its recovery to install it to a partition. weird part is I'm currently booted to sequoia through oclp t2 on the newest version and it booted with no issues. @albert-mueller @Medelcartelinc
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)
Dieses Issue auf GitHub diskutieren5 Kommentare
Kommentare
@zkennedy137 ·
How did you install it from recovery? Mind sharing? I have an idea based on this. To be clear you mean you were able to install Tahoe from recovery?
@jakecaley · · bearbeitet
@zkennedy137 well my MacBook has support for sequoia so I used the official recovery and installed it and booted into the sequoia install through the opencore menu. Also no I used sequoia. But still even after allat it didn’t work and I still got the Mac OS isn’t compatible with this Mac when I tried upgrading to Tahoe
@zkennedy137 ·
I did discover last night I got through the language selection screen not because it was booting from the main drive but because it was by default not using restrictevents.kext. When I disable that kext in opencore I can get to installer and format the drive etc. The only problem is of course that gives the not supported screen when attempting.
I went so far as to create a second BaseImage.dmg. I edited the PlatformSupport.plist and resealed it as read only. That should bypass the check. Then I got into the installer environment(recovery) and opened terminal, manually mounted the edited dmg, ran the “startosinstaller” from terminal and it wanted internet connection. I gave it that with type-c Ethernet and reran the command only to get told “important content can’t be downloaded”. I tried spoofing MacBookPro16,1 that didn’t fix the compatibility check. Even though I told opencore to spoof when I checked info from ioreg it said it was my real Mac info not the spoof. The installer did attempt to start though in this method. I did try disabling dmg signing on opencore to boot the custom image. It fails to boot and hangs around DSMOS arrived.
@zkennedy137 ·
@albert-mueller @Medelcartelinc possible entry point to run the installer? I’m not sure if there is a way to. Like at this point if we could bypass the check for compatibility in the installer we might get it. Also I think the reason apfs.kext fails to load is restric events loading before it.
@zkennedy137 ·
Did you try this method since SpooVMM was added to your efi? @jakecaley