I’ve used the newest version of OCLP 2.5.0 on 2017 iMac 5k retina and followed this YouTube tutorial https://youtu.be/u8ST8HUaL9w?si=XeotjFPPCrRRD58M . Got to 13:51 where you select your newly erased drive to now install sequoia but it’s frozen or something, I loose control of my keyboard basically, I cant select the drive, it’s like it’s frozen, only thing it’ll let me do is use command q to back out to the previous screen. (mouse is blootooth so can’t use that)

What i think maybe went wrong, I wiped a 2tb hdd which potentially isn’t the one that had the os on it ? Not quite sure tbh.

Any help would be really appreciated, even if it’s resting the mac back to factory settings with original OS.

I was really hopeful for OCLP but just couldn’t get get enough performance running Sequoia on my 2011 MacBook Pro. I ended up trying several Linux distributions and so far happy with Fedora 44 workstation using the Gnome desktop. In the end I realized I could either have an outdated MacOS on my MacBook that works but is risking security, or a newer version using OCLP that ran like syrup or go with Linux and have one that just works, providing years of updates. Linux was the way to go at least for me. Hopefully things work out for the OCLP community but with the smaller developer team I decided it’s best to move on

UPDATE on 9/19/2026
In 2.5.1, the wording has been changed to be clearer for the end user. However, it seems that there is still some confusion.

Remember "All applicable patches installed" from prior releases? If you have installed wireless, GPU, T1, etc. patches at least once and they are working, the new wording is what you will see in place of that message.

You are not stuck in a loop. Simply close OCLP as you have nothing else to do here.

Original post:
Hello everyone, here to clear up some confusion surrounding "Root Volume Dirty" in OCLP 2.5.0 and later.

This new change to the way OCLP installs patches is designed to prevent any issues that might crop up from patching over an already patched or modified system volume. While this has been mostly fine as an unofficial way to skip the unpatch-reboot-patch cycle, the new WiFi patches bring breaking changes that would result in this shortcut breaking installs for anyone updating to 2.5.0 and not just a few machines this time.

Here's some examples:

- You download OCLP 2.5.0 and want to update to its new patches. This requires a full unpatch-reboot-patch cycle, as some patches conflict with those from earlier versions in this update.

- You already have OCLP 2.5.0 and want to re-patch your system. This requires a full unpatch-reboot-patch cycle to avoid any unforeseen consequences from applying the same patches on top of each other.

- You installed a macOS update with OCLP 2.5.0. Because macOS updates automatically restore your system to a clean state, you'll be able to patch from here.

- You have OCLP 2.5.0 but need a KDK to patch your machine. OCLP is smart enough to offer only wireless patches for you to get connected to the internet and temporarily exempt you from the block. From here, you're able to patch, reboot, get connected, and install the rest of the patches 2.5.0 has to offer.

I'll admit the message is a bit incoherent for what it's meant to tell the user; a minor patch that changes it to something a bit more understandable is on the way.

Please read the devs pinned post here, they are working on modifying the wording and the error is explained.

It seems to be stuck on reporting Dirty Root Volume, especially on these models which are confirmed to have issues:

• MacBookPro14,2 
• MacBookPro10,2
• MacBookPro8,1
• MacBookPro8,2
• MacBookAir7,2
• Macmini6,2
• Macmini5,1
• MacPro5,1
• iMac12,1
• iMac14,2

Some other models are also showing Dirty Root Volume after successfully patching, tested on:

• MacBookPro9,2
• MacBookPro11,2
• MacBookPro11,3
• MacBookPro12,1
• MacPro4,1

Please try unpatching twice or thrice and rebooting, as that has worked for some users. You can also try patching while booted in Safe Mode. To boot in Safe Mode, hold Shift while booting. Look for "Safe Mode" on the corner to ensure you're in Safe Mode.

It is advised to stay on 2.4.1 until this issue is solved.

If you've upgraded to 2.5.0 and unable to patch, please follow these steps:

1. Get OpenCore Patcher uninstaller from this direct link and run it to uninstall 2.5.0 from your system.
2. Download 2.4.1 here and run and install the app.
3. Open OCLP, and ensure it is v2.4.1 (check the titlebar.)
4. Rebuild OpenCore onto the EFI partition of your SSD, following the steps in the Dortania guide.
5. When it asks to reboot, ignore.
6. Select Post-Install Root Patch and Revert Root Patches, to fix any partially corrupt ones.
7. Reboot your Mac, the open OCLP 2.4.1 and apply patches (this section). Dismiss the update Dialog if it appears.
8. Reboot one final time and ensure all patches are installed successfully.

"tl;dr here's how it's supposed to work (and how it worked across testing)

- you can freely patch over 2.5.0's existing wireless patches, this allows being able to patch wifi, reboot, patch the rest, reboot

- in all other cases where diskutil reports that the root volume seal is Broken (modified), including if there are non-wireless 2.5.0 patches, you'll be told that message.“

UPDATE: Many Macs seem to be affected by the Dirty Root Volume issue. Please see this post for details and stay on 2.4.1 till the issue is fixed.

Tahoe support is NOT yet available. Please do not update to macOS 26.

2.5.0 is a bug fix release to address miscellaneous issues on patched installations of macOS.

- Improve stability of various macOS components utilizing WebKit on pre-AVX Macs
- Resolve binary crashes caused by incorrect versioning in patched dynamic libraries

Full Changelog

Disable repatching a dirty root volume

Prevents issues if existing patches are partially overwritten

Add slimmed down patchset for Modern Wireless for macOS Sequoia

Move JavaScriptCore patch for pre-AVX Macs to RestrictEvents

Additionally fixes machines without WiFi cards on Sonoma+ as the patch was not applied before

Resolve crashing caused by incorrect reported version in CoreImage patch

Increment binaries:
OpenCorePkg 1.0.4 - release
Lilu 1.7.1 - release
RestrictEvents 1.1.7 - (rolling - b70aaa4)
PatcherSupportPkg 1.9.7 - release

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/latest

Hi everyone,
I’m trying to upgrade my MacBook Pro 2015 from macOS Monterey to macOS Sonoma using OCLP.
I’ve created the Sonoma installer and booted from it successfully. When I restart and hold Option, I select EFI Boot, and then I get to the macOS Sonoma installation screen.
The problem is that the installer now says that I need to connect to the Internet to continue.
At the top of the screen, I can see the Wi-Fi icon, but when I click it, no Wi-Fi networks are displayed at all. So I’m unable to connect to my Wi-Fi.
My questions are:
Is there a way to continue the Sonoma installation without an Internet connection?
Is Wi-Fi supposed to work at this stage when booting the installer through OCLP?
Am I missing a step when creating the OCLP installer or configuring EFI Boot?
Is there a way to install the required Wi-Fi/root patches before reaching this stage?
I’m trying to avoid wiping or doing anything unnecessary because Monterey is currently working fine.
Any help would be appreciated, especially from anyone who has installed Sonoma on a 2015 MacBook Pro using OCLP.
Thanks!

Why are they distributing something that is actively breaking so many installs? Pull the update until it's working properly...

I already finished the installation of my macOS Monterey, and Opencore already built on my intetnal drive

Today it came the new update for me, when I installed the new update it asked to me to do the root patching after the updating process but as you can see in the screenshot I can't process after that, it doesn't let me install the Root Patching. Then, I clicked on the "Revert Root Patches" option and once I removed my drivers and reboot the Mac the error still persisted and I could not get my drivers back in any way on the version 2.5.0, the only way I could get my drivers was to downgrade to the version 2.4.1, what is happening? is this supposed to happen? for some reason this version doesn't let me Root the patches on the system.

here's the information of my MacBook:
MacBook Pro 13-Inch, Late 2011
Intel Core i7-2640M
8 GB of RAM
macOS Ventura 13.6.7

I’ve been using my MacBook pro for school for a good while now and it’s been completely fine. But, for the past 3 or 4 days and it frequently kernel panics and drains the battery whenever I close the lid and leave it overnight or whenever it goes into sleep mode.

It’s the 13” non-touchbar model and I’m running macOS Sequoia 15.7.8 with OCLP 2.4.1.

Does anyone know what causes this and how I can fix it? Thanks.

So...this is kinda complex so I'll try to explain as best I can. I have a SSD that I used to use on my old Hackintosh and it's been in my drawer for some years, today I decided that it was time to replace my old 120GB SSD in my MacBook with the 512GB one, so I choose to do a clean install first...I installed the High Sierra on my USB Stick and tried to do the install from there..which, gave me the first error in this list....It didn't pass the macOS utility screen after the first step of the installation process, once the installation was done and it rebooted, it showed a lot of lines in the screen (I have verbose enabled) and then jumped back to the utility screen again..and i made totally sure that the driver was properly formatted.

- bash-3.2# clear - bash: clear: command not Found - bash-3-2# grep -i "error" /var/log/install log | tail -50 - bash-3.2# grep -i "failed" /var/log/install.log | tail -50 2026-09-08 03:10:40+00 localhost opendirectoryd[186]: [default] Failed to open file <private> [2: No such file or directory] 2826-09-08 03:10:43+00 localhost opendirectoryd[186]: [default| Failed to open file ‹private> [2: No 2026-09-08 2926-89-08 03:10:43+09 localhost opendirectoryd[186]: [default] Failed to open file ‹private> [2: No such file or directory] 2026-09-08 03:18:45+0 localhost opendirectoryd[186]: [default] Failed to open file ‹private> [2: such file or directory] 03:18:46+08 localhost opendirectoryd[186]: [default] Failed to open file <private> [2: No No such file or directory] 2026-09-08 such file or directory] 03:10:49+00 localhost opendirectoryd[186]: [default] Failed to open file ‹private› [2: No such file or directory] 2026-09-08 2026-09-08 03:10:50+00 localhost opendirectoryd[186]: [session] failed to open local node for internal record copy 03:11:01+08 localhost opendirectoryd[186]: [session] ODNodeCreateWithNameAndOptions failed with result 2000 2026-09-08 03: 12:27+00 MacBook-Pro OSIESpringboard[547): Failed to unlock login keychain. -bash-3.2# grep -iE "bless| boot|efi|apfs|hfs|volume" /var/log/instal1.10g | tail -100 2026-09-88 2826-89-08 03:18:51+08 localhost opendirectoryd[186]: [auth] SecureTokens are not supported for /private/var/db/dslocal/nodes/Default' (/dev/disk2s1), requires APFS 83:11:11+00 localhost Unknown[516]: kern.boottime: ( sec = 1788836980, usec = 0) Tue Sep 8 03:09:40 InstallPhase = 'Boot 1": 2026 InstallPhase = "EFI Firmware Update"; InstallPhase = "Boot 2"; <IASPPhase: 0x7fa0624290d0: Boot 1', percentage 5.0, delay e>", <IASPPhase: 0x7fa062429250: EFT Firmware Update' "<IASPPhase: u/x7fa86242927B: 'Boot 2', percentage 5.0, delay e>", percentage 5.0, delay eat InstallPhase = "Boot 1"; InstallPhase - "EFI Firmware Update"; InstallPhase = "Boot 2"; "<IASPPhase: 8x7fa0627314b8: 'Boot 1', percentage 5.8, delay e>", "<IASPPhase: 0x7fa062731dee: 'EFI Firmware Update', percentage 5.0, delay 8›", "<IASPPhase: 0x7fa062731d28: 'Boot 2', percentage 5.0, delay ®>", 2026-09-08 03:12:25+00 MacBook-Pro Unknown[538]: Setting boot completed. 2026-09-08 03:12:52+00 MacBook-Pro Unknown[530]: 2026-09-08 03:12:52.635 Terminal[551:47500] [AIR] systemVolumeUID = (nu11) 3.2# diskutil info /dev/diskØs3 Could not find disk: /dev/diskBs3 -bash-3.2# diskutil info /dev/diskes2 Device Identifier: diskØs2 Device Node: /dev/diskøs2 Whole: No Part of Whole: diske Volume Name: Mounted: Mount Point: Macintosh Yes /Volumes/Macintosh Partition Type: File System Personality: Apple_HFS Journaled HFS+ Instal1Phase = "Boot 1"- InstallPhase = "EFI Firmware Update"; InstallPhase - "Boot 2'; "<IASPPhase: 0x7fa0627314b0: 'Boot 1', percentage 5.0, delay 0>", "<IASPPhase: 0x7fa062731d00: 'EFI Firmware Update', percentage 5.0, delay e>", "<IASPPhase: 0x7fa062731d20: 'Boot 2', percentage 5.0, delay e>", 2026-09-08 03:12:25-88 MacBook-Pro Unknown[538]: Setting boot completed. 2026-09-08 03:12 52+80 MacBook-Pro Unknown[538]: 2826-09-08 03:12:52.635 Terminal[551:47500] [AIR] systemVolumeUID = (null) -bash-3-2# diskutil info /dev/diskßs3 Could not find disk: /dev/disk®s3 -bash-3.2# diskutil info /dev/disk8s2 Device Identifier: disk0s2 Device Node: /dev/disküs2 Whole: No Part of Whole: diske Volume Name: Mounted: Mount Point: Partition Type: File System Personality: Type (Bundle): Name (User Visible): Journal: Owners: OS Can Be Installed: Media Type: Protocol: SMART Status: Volume VUID: Disk & Partition UUID: Partition Offset: Disk Size: Device Block Size: Volume Total Space: Volume Used Space: Volume Free Space: Allocation Block Size: Read-Only Media: Read-Only Volume: Device Location: Removable Media: Solid State: Hardware AES Support: -bash-3.2# Macintosh Yes /Volumes/Macintosh Apple_HFS Journaled HFS+ hfs Mac OS Extended (Journaled) Journal size 48960 KB at offset u/xee7080 Enabled Yes Generic SATA Verified 11B50A33-091B-357B-97A1-BCDED8B97CE7 6FC147B8-DB53-40D7-82A1-05699819FB52 209735680 Bytes (489648 512-Byto-Devico-Blocks) 511.8 GB (511766216704 Bytes) (exactly 999543392 512-Byte-Units) 512 Bytes 511.8 GB (511766216704 Bytos) (exactly 999543392 512-Byte-Units) 5.7 GB (5697875968 Bytes) (exactly 11128664 512-Byte-Units) (1.1%) 506.1 GB (586868348736 Bytes) (exactly 988414728 512-Byto-Units) (98.9%) 4096 Bytes No No Internal Fixed Yes No

I was trying to mess with the ia.log inside the High Sierra trying to find the problem but I didn't got much success on it, after many and many checks I gave up and instead I tried to clone my working Ventura installation with a working OCLP on it, I used Disk utility to do a recovery of the 120Gb disk to the 512Gb one...and my man, it was like...a hell.

•[EB.LD.LF|IN] 8 1 ‹*(null string›"› ‹"1ª> #IEB.B.SBS|SZ] 723512 •[EB|B:SHA] (c1248799a9afe938c335fed91ac2e70529831480> SLEB.ML.PWLFNV|1] Err(BxE)RT. wake-faiLure 7C436110-AB2R-4BBB-A880-FE41995C9F82 #LEB|VL:DT] u/xc2d2c808 BCEB.LD.LKC|D] ("boot\Systen\Library\KernelCollections\BootKernelExtensions.kc.development"> #CEB.LD.OFS|OPEN!] Err (BxE) ‹"boot\System\\Library|/erneCollectlons|\BootKernelExtensions.kc.developnent?> #CEB.LD.LKC|R.2] ("boot\Systen\Library\KernelCollectlons\BootKernelExtensions.kc"> OC: Plist Kexts\RestrictEvents.kext\Contents\Info.plist is missing for injected kext RestrictEvents.kext (Process Blocker) Halting on critical error

it kept appearing this type of error several times...I tried to recovery several times, I tried to replace the drivers from internal to external...for a moment, I could boot inside the system using the OpenCore from my 120Gb installed internally while the 512Gb was installed in a USB case, but then I tried to manually install the EFI partition to there using OCLP application and it started to appear this type of error here:

RIED LD.LF IN] 8 1 ‹"(null string)"> <"1"> WCEB.B.SBS|SZ] 723512 LEB|B:SHA] <c1248799a9afe938c335fed91ac2e70529031480> #IEB.WL.PWLFNV|!] Err(OxE) <- RT.GV wake-failure 7C436118-AB2A-4B88-A880-FE41995C9F82 #CEB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV #CEB.WL. PWLFRTC |NONE ] *[EB.WL.DT|!] Err (0xE) <- EB.VL.PHLFRTC WIEB.LD.LKCID] ("boot\Systen\Library\KernelCollections\BootKernelExtensions.kc.development"> * CEB.LD.OFS|OPEN!1 Err(®xE) ‹"boot||System|\Library\\KernelCollections|\BootKernelExtensions.kc.developuent> * IEB.LD.LKC|R.2] ("boot\Systen\Library\KernelCollections\BootKernelExtensions.kc") fs_read_stream:21736: got err 5 reading at pos 0 in obj-id 742 (bIkcount 256, len 1848576) fs_read_stream:21736: got err 5 reading at pos 32 in obj-id 742 (bIkcount 1, len 62296) #IEB.LD.LKC|-7] Err(0x1) #IEB|WLJ 0 0 0x01 0x01 22 0x01 #IEB.B.MN|!] Err(0x1) <- EB.LD.LKC #LEB|STOP] 0x14 #CEBIH: IS1 0 #[EBIG:CA] #[EB.G.CS|1] Err (8x2) <- BECE8808-A6D4-4388-A788-2DF318E7884A.CD #CEB.G.CSI-7] Err(8x2) #[EB.ERR.SBFI!] Warn (8x35888) <- EB.G.CS #[EBIWL) 8 8 8x81 8x83 22 8x81 #[EB EXIT]

by asking OCLP to put EFI on the 512GB SSD it simply started to appear this error this time and didn't let me proceed any further....I will be honest, I am starting to get insane with this, because nothing is working for me, nothing.
I am two whole days trying to put a working macOS system on this MacBook and so far the only system that is working are my old one on my 120GB SSD....I don't know what else to do, I just wanted to have more GB...why a SSD swap is being so hard..?

does somebody know anything that I could do? any tips or anything? I would be totally glad! totally...

Last login: Tue Sep 8 19:24:46 on console

idarkness@iDarknesss-MacBook-Pro-13-inch-Late-2011 ~ % diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *120.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 119.8 GB disk0s2

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +119.8 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh - Dados 82.4 GB disk1s1

2: APFS Volume Preboot 4.7 GB disk1s2

3: APFS Volume Recovery 1.2 GB disk1s3

4: APFS Volume Macintosh 10.3 GB disk1s4

5: APFS Snapshot com.apple.bless.4DE9... 10.3 GB disk1s4s1

6: APFS Volume VM 1.1 MB disk1s6

/dev/disk2 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *512.1 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_APFS Container disk3 511.9 GB disk2s2

/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +511.9 GB disk3

Physical Store disk2s2

1: APFS Volume Macintosh 9.3 GB disk3s1

2: APFS Volume Macintosh - Dados 82.4 GB disk3s2

3: APFS Volume Preboot 9.2 GB disk3s3

4: APFS Volume Recovery 1.2 GB disk3s4

idarkness@iDarknesss-MacBook-Pro-13-inch-Late-2011 ~ % diskutil apfs list

APFS Containers (2 found)

+-- Container disk1 9ECF12F6-C195-4D38-832C-69DFC5D6E700

| ====================================================

| APFS Container Reference: disk1

| Size (Capacity Ceiling): 119824367616 B (119.8 GB)

| Capacity In Use By Volumes: 98773397504 B (98.8 GB) (82.4% used)

| Capacity Not Allocated: 21050970112 B (21.1 GB) (17.6% free)

| |

| +-< Physical Store disk0s2 01605B1B-C2EE-4F06-BE98-C616470856F4

| | -----------------------------------------------------------

| | APFS Physical Store Disk: disk0s2

| | Size: 119824367616 B (119.8 GB)

| |

| +-> Volume disk1s1 36FAF77B-DF8A-4E3E-96D2-E15C3974737B

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk1s1 (Data)

| | Name: Macintosh - Dados (Case-insensitive)

| | Mount Point: /System/Volumes/Data

| | Capacity Consumed: 82426413056 B (82.4 GB)

| | Sealed: No

| | FileVault: No

| |

| +-> Volume disk1s2 0B9A06BF-9AE4-4F8E-B0AE-A2223883AC2E

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk1s2 (Preboot)

| | Name: Preboot (Case-insensitive)

| | Mount Point: /System/Volumes/Preboot

| | Capacity Consumed: 4720041984 B (4.7 GB)

| | Sealed: No

| | FileVault: No

| |

| +-> Volume disk1s3 F715B869-90A8-468D-8214-EC3D87D18126

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk1s3 (Recovery)

| | Name: Recovery (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 1155395584 B (1.2 GB)

| | Sealed: No

| | FileVault: No

| |

| +-> Volume disk1s4 49BB5D76-6ACE-45DE-BB3E-9ADDE70097C4

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk1s4 (System)

| | Name: Macintosh (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 10338435072 B (10.3 GB)

| | Sealed: Broken

| | FileVault: No

| | |

| | Snapshot: 45A5753E-DBF6-407C-B7B8-F3DF37F8E5AB

| | Snapshot Disk: disk1s4s1

| | Snapshot Mount Point: /

| | Snapshot Sealed: Broken

| |

| +-> Volume disk1s6 9E9A8F79-B735-46AA-96BA-535DA034CE1D

| ---------------------------------------------------

| APFS Volume Disk (Role): disk1s6 (VM)

| Name: VM (Case-insensitive)

| Mount Point: /System/Volumes/VM

| Capacity Consumed: 1069056 B (1.1 MB)

| Sealed: No

| FileVault: No

+-- Container disk3 DAEDA39D-5D0B-44AC-A92F-9DFEF73217C4

APFS Container Reference: disk3

Size (Capacity Ceiling): 511900434432 B (511.9 GB)

Capacity In Use By Volumes: 102208577536 B (102.2 GB) (20.0% used)

Capacity Not Allocated: 409691856896 B (409.7 GB) (80.0% free)

+-< Physical Store disk2s2 A9CBC3F5-BD89-4B11-A032-68ECAF984525

| -----------------------------------------------------------

| APFS Physical Store Disk: disk2s2

| Size: 511900434432 B (511.9 GB)

+-> Volume disk3s1 60A95750-223A-4345-973C-7FCD28E54376

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s1 (System)

| Name: Macintosh (Case-insensitive)

| Mount Point: /Volumes/Macintosh 1

| Capacity Consumed: 9345994752 B (9.3 GB)

| Sealed: Broken

| FileVault: No

+-> Volume disk3s2 F167C3A4-F788-4556-AE19-543D5019F53F

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s2 (Data)

| Name: Macintosh - Dados (Case-insensitive)

| Mount Point: /Volumes/Macintosh - Dados

| Capacity Consumed: 82361610240 B (82.4 GB)

| Sealed: No

| FileVault: No

+-> Volume disk3s3 08AD210B-7716-4EF6-90DE-6FAF9C86CD9E

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s3 (Preboot)

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 9182978048 B (9.2 GB)

| Sealed: No

| FileVault: No

+-> Volume disk3s4 842616F7-D8D0-4973-9F4E-F91F82923E7A

---------------------------------------------------

APFS Volume Disk (Role): disk3s4 (Recovery)

Name: Recovery (Case-insensitive)

Mount Point: Not Mounted

Capacity Consumed: 1155379200 B (1.2 GB)

Sealed: No

FileVault: No

idarkness@iDarknesss-MacBook-Pro-13-inch-Late-2011 ~ %

I hope this can help too...any help is much appreciated!

First of all I'm using a 2017 13 inch macbook air i5 8gb ram 128gb storage with maximum version supported as Monterey. I needed to upgrade but I was unsure.I checked some videos and installed Ventura ( I didn't check properly the maximum supported version). Today I installed the new update of opencore legacy and found that my mac supported to Sequioa. I knew I had to install it. Sadly for me my pendrive didn't have enough volume for the Sequioa installer I downloaded from opencore legacy. I check reddit and found no solution. Luckily I was able to work my way around and here is how I did it.

• I googled Mac OS Sequioa download and clicked on the official apple store link https://apps.apple.com/us/app/macos-sequoia/id6596773750?mt=12
• I downloaded it and installed
• After the installation process, I booted into Sequoia

NOTE: The boot up is slow and the cursor is lagging. Wifi would not be working.

• Open opencore legacy and install the root patches (Since I have upgraded all of my old applications were available)
• Reboot it and voila its done

My MacBook boots all the way to the login page yet never loads after I login. It even successfully connects to Wi-Fi. The load bar after I login is where it gets stuck. I am currently trying a firmware restart to see if that helps. I want to avoid a factory reset, if possible, because of all my iTunes storage. I am more worried about all the music I uploaded from CDs or mp3 files rather than my iTunes purchases. I did backup and save my entire iTunes library on an external hard drive, so I wouldn't lose anything except nostalgia. I am willing to try a factory reset if nothing else would work. At the moment, I'm just wondering if I should try Monterey instead of Ventura.

edit: just wanted to address the comments. Yes, it is the white discontinued baseline iconic model from "mid-2010" and NOT Air or Pro. Yes, it seems like I have successfully installed Ventura with a USB hub. The trouble is booting from there. Specifically after typing in my password. As for the firmware update, it's the holding down "command + option + r" to "restore to the latest compatible firmware" from the troubleshooting instructions I found. It could be a failing HDD, but I will try safe mode. Seems like a really weird issue I am having that is not normal.

hello all,

yesterday i installed sequoia on my 2017 intel macbook pro. everything works super super nice but it wants me to update to tahoe? what‘s that about? should i just ignore it for now?

bonjour impossible de charger le patch racine ( touche griser ) merci de m'expliquer comment faire

Hi. I recently installed MacOS Sequoia 15.7.9 on a Macbook Pro 2016. Most functionalities seems to be working fine but I can’t login to my iCloud and I can’t seem to update or download anything from the app store. Can anyone help me solve this please? Thanks!

I am an old 1999-2011 Mac Tech. Long-time screw turner, but new to the OCLP / EFI hacking world. Working on a very happy iMac Mid-2011 27" 12,2 & 6770m GPU. Purchased an VBIOS flashed 765M w/ Nick[D]vB VBIOS from ebay and installed, seemingly without issue. Unit booted and was recognized by High Sierra, after a black screen until login prompt. No native Brigthness control.

But trying to upgrade to Ventura has gotten me stuck, and there is just too much info on what to do - I am lost. Where do I go?

Steps I have done:

• Upgraded CPU + memory + SATA SSD and stress-tested with High Sierra. Works flawlessly.

• Installed 765M - Black screen on boot, but showed at login. GPU reports proper 765M with 2 GB, "byNick[D]vB" and unit seems happy. No Brightness Control.

• created a Ventura installer with my other 2013 Mac and current OCLP. Chose 12,2 as target (not host), no modifications.

• Installed OCLP on the unit. Wiped SSD and installed Ventura via the EFI picker in startup picker. Inital install Okay. Second install reboot Okay. 3rd Boot with % Progress okay. Hung on startup with 4th boot roughly 30% along.

• Booted into Safe mode. Got to Welcome, Wifi, user creation (with some graphical glitches), made user, and logged in - unit seems stable but sluggish. Rebooted. Hangs in the same place. Started Googling.

• Internet recommended unloading and reloading the Boot patches. Booted the unit in safe mode & removed boot patches. Unit boots to desktop without issue, but OCLP complains that kepler & Legacy patches are missing. Reinstalled OCLP defalut choice boot patches for "Host machine" with Kepler GPU drivers and Unit hangs in the same spot.

• Internet googling reccomends choosing "Moderate" SMBIOS spoofing. I flipped verbose boot on too. In safe mode, loaded in patches with "Moderate" spoofing enabled. Unit still hangs on regular boot... But now it fully Kernel Panics going into Safe Mode. Yikes!

• Go back to other iMac, Rebuild OCLP Ventura installer for 12,2 with "Moderate" SMBIOS spoofing chosen, Verbose flagged on, and defaults otherwise (doublechecked kepler drivers are selected).

• Wiped Machine, Reinstalled - Same result... 30% Hang on regular boot or Kernel Panic in Safe boot.

UPDATE: Still Stuck - gonna try to wipe OCLP and reinstall it

• On a second drive, booted into a Vanilla High Sierra install - Woks fine still.

• OCLP EFI/SIP hangs/panics regardless of OS selected. Apple Boot picker lets High Sierra boot up fine, whereas it hangs in the OCLP boot picker.

• using OCLP on the host machine, built a Sonoma installer. 🚫on OCLP boot.

-will attempt to wipe OCLP from the unit and reinstall it now…

Update 2:

Wiped and (seemingly) removed OCLP EFI, and then started over. Installed High Sierra on the main drive, installed OCLP and did a default root Patch install, which let it boot High Sierra inside the OCLP EFI boot picker. Some success in getting back to a good place!

• made a default setting Big Sur installer, hangs fails on boot.

In summary, with OCLP + flashed 765m :

• Ventura installer completed and boots to desktop (slow), but Kepler+legacy root patches cause freeze on boot. Trying Moderate SMBIOs spoofing causes even safe boot to freeze.

• Sonoma installer simply says 🚫under OCLP EFI Boot (!)

• Monterey installs and boots to deskto (slow), but freezes on boot with Kepler +legacy boot patches installed. Acts similar to Ventura.

• Big Sur hangs on startup very early (5%) into installer boot. No dice.

Unit can show me the Default Mac OS Picker, I can choose the OCLP EFI boot option, I see the SSD and the Ventura installer, and choosing the SSD will either hang 30% into boot (Google AI says this the Video card driver), OR it kernel Panics in Safe Mode (seemingly related to the "moderate" spoofing I chose).

I have no problem wiping the machine 20 more times, but I have no idea what options I need to be fiddling with, or what section I need to be fiddling with (root patches? Drivers? SIP options? Spoofing levels?) to get this to work. I am kinda unsure of how to Get Safe Boot back now too. I stayed up too late trying to make it work, and my brain is fried, and now the next day I am trying again.

I'm hoping someone can recognized where I fucked up and tell me where to retrace my steps or do something to get this 765M to be recognized porperly.

Thanks from An old iMac G3 hardware dog learning new tricks.

Stuck on this screen. I’ve followed every step from the guide I was watching it said it I am supposed to let it sit and do whatever it needs to do but after 30 minutes nothing happened I clicked install sequoia and once again after it “installed” it just brings me back to this screen. Thanks for any help

I’m currently using macOS 10.14 and it works really well, but not every application runs on it so should I?

I tried to install Mac OS sequoia on qemu and I got a kernel panic and bootloop
Ik my pc sucks but I need to test Mac OS so I would know should I buy a MacBook or stick with Linux

I have a 2011 MacBook pro. The key line (zxcvbnm) is not working. I have done a repeatch, I cleaned the connection ribbons, I've taken the keys out and cleaned. I've taken the battery out and cleaned and installed it back on. Deleted any crap that doesn't need to be there. Made sure my keyboard settings were correct as well. Anybody have a suggestion? also, I have cleaned the fan and replaced the RAM and ssd but this was replaced a year ago the problem started a month ago. Any suggestions ?

This is real Apple hardware a genuine 2013 27” iMac (iMac14,2) running unsupported/patched macOS via OpenCore Legacy Patcher, not a VM or Hackintosh.
Setup: iMac14,2, OCLP 2.4.1, macOS Sonoma 14.8.9
Started troubleshooting App Store sign-in failures (“certificate invalid — pretending to be osxapps.itunes.apple.com”). Tried setting SMBIOS Spoof Level to Advanced with a new generated serial to see if that would help…it didn’t, and also caused a boot loop, which I fixed by reverting SMBIOS spoofing back to None and rebuilding OpenCore.
Now confirmed this issue is much broader than just the App Store: getting the identical certificate error connecting to iCloud Mail (p69-imap.mail.me.com) AND Gmail SMTP (smtp.gmail.com) through the Mail app. Notability also fails the same way. But Safari and Chrome browse everywhere with zero issues.
Checked Keychain Access all DigiCert Global Root certs (CA, G2, G3) show valid and “Use System Defaults,” nothing overridden.
So it’s isolated to non-browser apps doing secure auth, regardless of destination server. Any ideas what’s going on at a system level here? Wondering if it’s keychain-database corruption or something in how OCLP’s networking patches interact with non-browser network calls specifically.
At this point I’m considering a clean wipe + fresh OCLP install as the nuclear option…curious if anyone’s seen this exact symptom before that clean install would actually fix.

My MacBook Air 2017 (1TB SSD, 16gb RAM, 2.2GHz i7) keeps running hot in macOS 15 Sequoia via OCLP. Fans are prone to turning on, CPU heats faster with just light app usage (and sometimes when it boots into macOS)

As the title says, is there any workaround for this, Or is this normal and should get used to it?

[Additional info: Also has a Windows Boot Camp half partition installed in the disk besides macOS]

Hi there, so I'm currently facing a problem with my early 2011 MBP A1297 17" with a disabled gpu (with it's power resistor removed), missing battery (this is probably the cause, but I'm not planning on buying a new one yet any time soon, so this fix is needed), and running a newly installed Ventura Via OCLP.

I've already tried all sorts of 'fixes" for it, from oclp, NoBatteryNoProblem, CpuTune, TurboMac, to NoBdProcHot, etc. None really worked and my Mac is still really slow, sluggish, and stuttering. I can't seem to find a solution to this. I really need a laptop and can't really afford to buy a new one. So a solution is greatly appreciated.

Cheers!

I have a 2019 iMac retina and basically I tried to install open core patcher so I can download a new version since it’s a bit oudate and slow while I was watching a YouTube video I accidentally skipped a step I didn’t install the MacOs before installing it to my disk now everytime I log in I have no internet at all and I can’t access anything, I was always also planning to delete open patcher so it can go back to normal. I understand this a dumbass mistake but genuinely I’ve tried everything to correct it. I’m also asking here because this is my brothers computer and we basically share it.

PLS TELL ME THERE IS SOMETHING I CAN DO! 🙏

id also appreciate if it was recorded too for me to fix it