Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I booted in verbose mode and after a while, the screen showed an Apple logo with an empty progress bar, which never progressed.
After around 30-60 seconds of the logo screen, the following text showed and remained for at least 15min, when I turned off the MBP.

View attachment 2484964
dude, what happened to that screen?
 
I'm not planning to update to 15.4 beta-anything on a rMBP10,1 2012 at all. I'm sticking with only public releases on that m/c, with enough delay to let Dortania address any issues, from now on.

I would like to keep it working as a fall back m/c. Currently everything else runs on a still supported Mac mini8,1 2018 while I figure out the next move. Most likely it will be a new Mac Mini M4 pro, slightly tweaked up from the base spec, and a 5K ASUS monitor and Thunderbolt 5 external SSD. Saving up my pennies here, no rush.
 
Check out Mr Mac's new video, I strongly recommend it.
It might fry a few brain cells if you're new to all this, but old hands will appreciate the insights.

Very useful, thanks for sharing. MrMacintosh is such a vital part of the OCLP experience!
The video also confirms some stuff many of us have seen (in my case keeping KDK and metallib updated) and my take away is that on legacy Macs, the time for doing MacOS updates as soon as they appear is now long gone, let alone betas, unless you are feeling adventurous and have time on your hands or have particular dev reasons.
If you can wait for a MrMacintosh video update, all the better.
 
That's weird. Maybe make another installer usb? Or stay on 15.3.1 for now? That's what I'd do actually.

I tried again with a diff style, 2.2/15.4, reverted patches, it did come up finally, OCLP asked to repatch, and it again froze halfway across. I will now wait for the next OCLP update. My suspicion is that increasing emphasis on AI may be causing problems.
 
Some testers with pukka Mx Macs are finding that 15.4 beta 1 causes unrecoverable bootloops that even an Apple Store Genius cannot recover or restore and therefore requires replacement of logic board by Apple, so it's not surprising that OCLP has problems too. Better to hang fire until the beta fix arrives.
 
Some testers with pukka Mx Macs are finding that 15.4 beta 1 causes unrecoverable bootloops that even an Apple Store Genius cannot recover or restore and therefore requires replacement of logic board by Apple, so it's not surprising that OCLP has problems too. Better to hang fire until the beta fix arrives.
Sometimes those geniuses have less experience than half the newbies in this forum.

However, obviously this beta is definitely something special in terms of testing.
 
Last edited:
After the 15.4 debug kit appeared I downloaded the latest nightly, and updated to 15.4, OCLP as ususal downloaded the kit during the process, it seems to be doing just fine, a couple of new things I think, the welcome to Mac opening window and before that a message that updates will be downloaded automatically, which you can change in settings, that window is different also. Things seem to be much better in general.

Thanks Devs for a very rapid response.
 

Attachments

  • IMG_1517.jpg
    IMG_1517.jpg
    165.5 KB · Views: 33
Last edited:
Last edited:
I created a new APFS volume to test Sequoia 15.4 Beta on my MBP6,2 and experienced the problems mentioned by others. After applying OCLP 2.2.0 post-install root patches (NVidia and Wi-Fi in my case), Sequoia 15.4 Beta would not boot. To restore 15.4 Beta to a bootable state (albeit without OCLP root-patches), the following still works:
  • Boot into Sequoia 15.4 Beta Recovery
  • mount -uw /Volumes/SequoiaBeta [where SequoiaBeta is the name of your Sequoia 15.4 Beta test volume]
  • bless --mount /Volumes/SequoiaBeta --bootefi --last-sealed-snapshot
  • Reboot Sequoia 15.4 Beta.

I'll leave my Sequoia 15.4 Beta test volume without OCLP root patches until the Devs release their fix.

EDIT: I also removed the following plists installed by OCLP
  • /Volumes/SequoiaBeta/System/Library/CoreServices/OpenCoreLegacyPatcher.plist
  • /Library/LaunchAgents/OpenCoreLegacyPatcher*.plist
  • /Library/LaunchDaemons/OpenCoreLegacyPatcher*.plist
 
I created a new APFS volume to test Sequoia 15.4 Beta on my MBP6,2 and experienced the problems mentioned by others. After applying OCLP 2.2.0 post-install root patches (NVidia and Wi-Fi in my case), Sequoia 15.4 Beta would not boot. To restore 15.4 Beta to a bootable state (albeit without OCLP root-patches), the following still works:
  • Boot into Sequoia 15.4 Beta Recovery
  • mount -uw /Volumes/SequoiaBeta [where SequoiaBeta is the name of your Sequoia 15.4 Beta test volume]
  • bless --mount /Volumes/SequoiaBeta --bootefi --last-sealed-snapshot
  • Reboot Sequoia 15.4 Beta.

I'll leave my Sequoia 15.4 Beta test volume without OCLP root patches until the Devs release their fix.

EDIT: I also removed the following plists installed by OCLP
  • /Volumes/SequoiaBeta/System/Library/CoreServices/OpenCoreLegacyPatcher.plist
  • /Library/LaunchAgents/OpenCoreLegacyPatcher*.plist
  • /Library/LaunchDaemons/OpenCoreLegacyPatcher*.plist
I commend your bravery testing Sequoia 15.4 Beta on an OCLP'd Mac. I was able to upgrade my last running OCLP Mac a 2014 Mac mini 7,1 to 15.3.1 but had to do a clean install (reformatting the drive) from an OCLP USB stick. Seems to run pretty well for a 10+ yr old mini. I am awed with amazement at what the developers have accomplished with OCLP. Cheers to them and all the helpful folks here on MR.
 

Attachments

  • Mac mini 7,1.png
    Mac mini 7,1.png
    240.9 KB · Views: 23
I created a new APFS volume to test Sequoia 15.4 Beta on my MBP6,2 and experienced the problems mentioned by others. After applying OCLP 2.2.0 post-install root patches (NVidia and Wi-Fi in my case), Sequoia 15.4 Beta would not boot. To restore 15.4 Beta to a bootable state (albeit without OCLP root-patches), the following still works:
  • Boot into Sequoia 15.4 Beta Recovery
  • mount -uw /Volumes/SequoiaBeta [where SequoiaBeta is the name of your Sequoia 15.4 Beta test volume]
  • bless --mount /Volumes/SequoiaBeta --bootefi --last-sealed-snapshot
  • Reboot Sequoia 15.4 Beta.

I'll leave my Sequoia 15.4 Beta test volume without OCLP root patches until the Devs release their fix.

EDIT: I also removed the following plists installed by OCLP
  • /Volumes/SequoiaBeta/System/Library/CoreServices/OpenCoreLegacyPatcher.plist
  • /Library/LaunchAgents/OpenCoreLegacyPatcher*.plist
  • /Library/LaunchDaemons/OpenCoreLegacyPatcher*.plist
 
OCLP has updated:

The latest OCLP nightly downloads this when 15.4 is being downloaded OTA, I have used it successfully on an internalHD and an external SSD both are now 15.4, and doing well.

The info on the KDK 15.4 link is extensive, including 14 printable pages, very interesting.

Sorry about he double post, I do not know how that happened.
 
Helo to all,

I was going to post about installation of Sequoia 15.3.1, but then Sequoia 15.4 beta1 arrived.
Installation of 15.3.1 was a bit arduous for MacBook Pro 5,2, but in the end the final effort produced functionality equivalent to 15.2 in performance and functionality

Sequoia 15,4 beta 1 report

iMac 13,2. (27’ , late 2012).

Installed 15.4 b1 over 15.3.1 using software update mechanism.
Everything seemed to proceed well until second reboot in the process, where progress bar stalled third of the way to completion, and cursor (arrow) appeared and disappeared at regular intervals, action suggestive of a boot loop. Shut down via power button; neither PRAM or SMAC resets were effective.

Booted into fully functional Sonoma volume (14.7.4) and launched OCLP to revert patches. Used terminal to mount EFI volume and erase OC contents from its folder. Reinstalled OCLP 2.2, booted into 15.4 B1 volume in “safe” mode and was able to reach logon screen, but Bluetooth keyboard and track were unresponsive. Attached wired keyboard and mouse to USB port of iMac and was able to type the passphrase. iMac booted into desktop (white screen - no graphic acceleration).
Message box appeared advising that “Window Server ‘crashed’” on previous boot attempt; this message and repetitive cursor on-off cycle (described above) are suggestive of a boot-loop triggered by Window Server failures (without fatal event), and system’s “attempt” to restart the boot process.

Reinstalling patches while booted in 15.4 beta 1 resulted in same boot-loop with cursor on-off cycle ( as also reported by others)

While booted without patches iMac 13,2 had no Bluetooth functionality and no WIFI (latter not surprising), and required wired keyboard and track (or mouse). Ethernet was fully functional.

MacBook pr 5,2 (2009)

The installation events matched the experience with iMac 13,2; same results and same procedure to boot to desktop. No Bluetooth, WiFI, and no graphic acceleration. Wired keyboard and track required. Installing OCLP patches causes boot failure.

Hope this data may be of help.
 
Helo to all,

I was going to post about installation of Sequoia 15.3.1, but then Sequoia 15.4 beta1 arrived.
Installation of 15.3.1 was a bit arduous for MacBook Pro 5,2, but in the end the final effort produced functionality equivalent to 15.2 in performance and functionality

Sequoia 15,4 beta 1 report

iMac 13,2. (27’ , late 2012).

Installed 15.4 b1 over 15.3.1 using software update mechanism.
Everything seemed to proceed well until second reboot in the process, where progress bar stalled third of the way to completion, and cursor (arrow) appeared and disappeared at regular intervals, action suggestive of a boot loop. Shut down via power button; neither PRAM or SMAC resets were effective.

Booted into fully functional Sonoma volume (14.7.4) and launched OCLP to revert patches. Used terminal to mount EFI volume and erase OC contents from its folder. Reinstalled OCLP 2.2, booted into 15.4 B1 volume in “safe” mode and was able to reach logon screen, but Bluetooth keyboard and track were unresponsive. Attached wired keyboard and mouse to USB port of iMac and was able to type the passphrase. iMac booted into desktop (white screen - no graphic acceleration).
Message box appeared advising that “Window Server ‘crashed’” on previous boot attempt; this message and repetitive cursor on-off cycle (described above) are suggestive of a boot-loop triggered by Window Server failures (without fatal event), and system’s “attempt” to restart the boot process.

Reinstalling patches while booted in 15.4 beta 1 resulted in same boot-loop with cursor on-off cycle ( as also reported by others)

While booted without patches iMac 13,2 had no Bluetooth functionality and no WIFI (latter not surprising), and required wired keyboard and track (or mouse). Ethernet was fully functional.

MacBook pr 5,2 (2009)

The installation events matched the experience with iMac 13,2; same results and same procedure to boot to desktop. No Bluetooth, WiFI, and no graphic acceleration. Wired keyboard and track required. Installing OCLP patches causes boot failure.

Hope this data may be of help.

I had the same bootloop problem until I installed yesterdays OCLP 2.3n with the new KDK 15.4, and updated to 15.4 OTA.
Works great now. I used recovery to reinstall 15.3 first.
 
Unfortunately there are more and more apps that require AVX2... such as Whatsapp Desktop.
@Mystere65 That's interesting, because here WhatsApp Desktop is crashing at startup, too.

Unfortunately, you cannot use older versions of WhatsApp Desktop, the program expires and can no longer be used afterwards. You are therefore forced to update. In our case, this means that you can no longer use the program.

Is there perhaps some kind of add-on that simulates AVX2?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.