[Bug]:2012 MacBook Pro stuck at boot on macOS 26 Tahoe at apfs_extract_root_manifest
bug
Mac model / Mac-Modell
non-T chip: 2012 MacBook Pro
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 - )
26.5.1
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.18003.2
Issue type / Typ Fehler
Boot failure / Startfehler
Description / Beschreibung
I was trying to install macOS Tahoe 26.5.1 on MacBook Pro 2012 retina 13 inches but somehow can't reach the graphical set up and still stuck at the log view. I tried the smbios spoof to advanced and manually configure to boot-args but it did not work. still the same. Please guide me to boot Tahoe
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)
Panic log (if any) / additional notes (if any) / Panikprotokoll (falls einer) / zusätzliche Notizen (falls einer)
Dieses Issue auf GitHub diskutieren9 Kommentare
Kommentare
@Medelcartelinc ·
Hi @Htet-2aung! 👋
Thanks for sharing the verbose boot log screenshot! Looking at the log, there are two fundamental hardware barriers blocking the macOS 26 Tahoe installer on your 2012 13" Retina MacBook Pro (
MacBookPro10,2):AVX1 vs AVX2 CPU Instructions:
fletcher64_init: Selecting AVX1. The 2012 MacBook Pro uses a 3rd Gen Intel Ivy Bridge processor which only supports AVX1.Root Hash & Manifest Validation (Error 22):
authenticate_efi_forwarded_roothash: populate_value_from_memory_descriptor for root hash failed: 22apfs_extract_root_hash_and_manifest failed with error: Invalid argument (22)Repository Scope:
For a 2012 Ivy Bridge MacBook Pro, the highest stable macOS releases with full graphics acceleration and hardware support are macOS 14 Sonoma and macOS 15 Sequoia using mainline OpenCore Legacy Patcher (Dortania). macOS 26 Tahoe cannot currently boot to GUI on Ivy Bridge hardware.
Hope this clarifies things! 😊
@albert-mueller ·
@Medelcartelinc Which means to make 2012 MacBook Pros into Tahoe it requires some kexts/further development?
@Medelcartelinc ·
@albert-mueller
Exactly. Technically, getting Ivy Bridge (2012 MacBook Pros) to boot and run macOS 26 Tahoe would require extensive reverse engineering and low-level development:
On top of that, performance and usability would be a major concern:
Even if bootability were achieved through software emulation, these 14-year-old dual/quad-core machines would lag significantly. Tahoe's background services, UI rendering, and memory footprint are tuned for modern architectures; running heavy software emulations on an Ivy Bridge CPU would result in severe UI stuttering, thermal throttling, and an overall sluggish experience that wouldn't be practical for daily use.
So while theoretically anything is possible with enough development time, the effort-to-reward ratio is extremely low compared to focusing our resources on 2016–2020 Macs.
@albert-mueller ·
@Medelcartelinc I think running macOS 26 on a Sandy Bridge would be pain, because Spotlight uses AI features even on Intel Macs. That will make those Macs practically unusuable if you add software emulation to the equation. So at least at the moment anything prior to 2013-2014 Macs would be off limits until we make T2 Macs to boot?
@Medelcartelinc ·
@albert-mueller
100% agreed. Spotlight's background neural/vector indexing and Tahoe's unified system daemons would cause constant thermal throttling and 100% CPU usage on those dual-core Sandy/Ivy Bridge chips.
Focusing our efforts strictly on Haswell+ (2013-2014+) and prioritizing getting T2 Macs, 2016–2020 Intel machines, and modern legacy GPUs fully booted and rock-solid is definitely the right strategic roadmap. Once T2 and modern Intel platforms are mature and stable, we can always revisit older hardware boundaries if there's ever demand, but right now T2 bootability, stability, and modern patch sets give users the best real-world experience.
@albert-mueller ·
@Htet-2aung Currently, for now until this is fixed (it will take a very very long time, unless you start researching together with us and try fixing this problem), for now the most practical thing is to stay on Sequoia, install Windows 11 or using some Linux distro.
@albert-mueller ·
@Medelcartelinc Also updated the readme to state that anything prior 2013-2014 Macs can't boot into Tahoe yet.
@Medelcartelinc ·
Awesome, thanks for updating the README @albert-mueller!
That will definitely save a lot of users with pre-Haswell hardware from running into boot stalls and keep the issue tracker focused on T1/T2 and supported 2013+ machines. Appreciate you getting that in! 👍
@albert-mueller ·
@Htet-2aung Can you try the latest release?