Archive for January 2025

Two-fingers swap left-right on trackpad doesn’t work

By Ufuk Durgun

Need some help, please.

I installed OCLP 2.2.0 with Sequoia 15.2, now updated to 15.3. Everything works perfectly, except for the two-fingers swap to go to previous page in Safari.

The corresponding setting is properly activated in Settings. I also tried to change it and re-set it with no effect.

By absurd, the three-fingers gesture works perfectly.

The same apply to the mbp trackpad and to the external Magic Trackpad.

Any idea how to fix this? Thanks!!!

submitted by /u/LukeDuke74
[link] [comments]
Share:

Error during install. What does it mean? How do I resolve? Need help.

By Ufuk Durgun

Multiple failed attempts to run the patcher. Below is the text dispayed in the error window. Attempting to update from Big Sur to Sonoma or Sequoia. Both end with the following error.

Failed to create macOS installer
Output: Started erase on disk2
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk2s2 as Mac OS Extended with name OCLP-Installer
Initialized /dev/rdisk2s2 as a 116 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk2
Copying essential files...

Error: Erasing disk: 0%... 10%... 20%... 30%... 100%
Failed to write .IAPhysicalMedia cookie to disk. Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “.IAPhysicalMedia” in the folder “Install macOS Sonoma”." UserInfo={NSFilePath=/Volumes/Install macOS Sonoma/.IAPhysicalMedia, NSUserStringVariant=Folder, NSUnderlyingError=0x7fe41ffc31e0 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}
The bless of the installer disk failed.

submitted by /u/Gpruitt54
[link] [comments]
Share:

How to Troubleshoot Post install Root Patch Failing 2012 RMBP - Error 31 on macOS

By Ufuk Durgun

How to Troubleshoot Post install Root Patch Failing 2012 RMBP - Error 31 on macOS

Graphics and media-app issues are normally caused by missing Metal acceleration, an unsupported GPU path, or a fragile patch combination. macOS needs a supported graphics stack; WhateverGreen, NootRX or NootedRed can help only when the underlying GPU path is viable.

Quick Checks

  • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
  • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
  • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Verify GPU support first: Confirm the exact GPU model and whether that macOS version supports Metal acceleration for it.
  3. Update graphics kexts: Refresh WhateverGreen, Lilu and any AMD-specific kexts together, not one at a time.
  4. Check boot arguments: Remove old experimental GPU boot args, then add back only the ones required for your hardware.
  5. Test acceleration: Open About This Mac, System Information and a Metal app before testing browsers, GarageBand or Pro Tools.
  6. Reduce app variables: Disable browser hardware acceleration or test another app build if only Chromium, Electron or CEF apps fail.

Do Not Continue If

  • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
  • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

  • The GPU reports Metal support in System Information.
  • Window animations are smooth and not CPU-bound.
  • The affected app opens after a clean reboot.
  • No repeated GPU restart messages appear in Console.

Rollback

  • Boot with a known-good EFI snapshot.
  • Temporarily remove experimental graphics patches.
  • Return to the last macOS version where acceleration was stable.

Next Action

  • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
  • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
  • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Related iATKOS Searches


Original Question: "Post install Root Patch Failing 2012 RMBP - Error 31"

Hello. I just installed Sequoia 10.3 onto my 2012 RMBP. It was running Monterrey that I installed years ago using OCLP.

Innstallation went fine except for the Post Install Root Patches. As I am getting an error 31. I have re-installed OCLP using both the host machine and MacbookPro 10,1 settings (should be the same) and it still fails with the following errors.

- Building new Auxiliary Kernel Collection

- Unable to build Auxiliary Kernel Collection

Subprocess failed.

Command: ['/Library/PrivilegedHelperTools/com.dortania.opencore-legacy-patcher.privileged-helper', '/usr/bin/kmutil', 'create', '--allow-missing-kdk', '--new', 'aux', '--boot-path', '/System/Volumes/Update/mnt1/System/Library/KernelCollections/BootKernelExtensions.kc', '--system-path', '/System/Volumes/Update/mnt1/System/Library/KernelCollections/SystemKernelExtensions.kc']

Return Code: 31

Standard Output:

No variant specified, falling back to release

No variant specified, falling back to release

Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:

1: One or more binaries has an error which prevented linking. See other errors.

2: Could not use 'com.nvidia.web.GeForceWeb' because: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN22IOAccelDisplayMachine210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN19IOAccelDisplayPipe210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN15IOAccelSurface210gMetaClassE' to be defined in another kext com.nvidia.web.GeForceWeb specific:

1: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN22IOAccelDisplayMachine210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN19IOAccelDisplayPipe210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN15IOAccelSurface210gMetaClassE' to be defined in another kext

" UserInfo={NSLocalizedDescription=Error occurred while building a collection:

1: One or more binaries has an error which prevented linking. See other errors.

2: Could not use 'com.nvidia.web.GeForceWeb' because: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN22IOAccelDisplayMachine210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN19IOAccelDisplayPipe210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN15IOAccelSurface210gMetaClassE' to be defined in another kext
com.nvidia.web.GeForceWeb specific:

1: Cannot find symbol for metaclass pointed to by '__ZN16nvDisplayManager10superClassE'. Expected symbol '__ZN22IOAccelDisplayMachine210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN13nvDisplayPipe10superClassE'. Expected symbol '__ZN19IOAccelDisplayPipe210gMetaClassE' to be defined in another kextCannot find symbol for metaclass pointed to by '__ZN9nvSurface10superClassE'. Expected symbol '__ZN15IOAccelSurface210gMetaClassE' to be defined in another kext

}

Standard Error:

None

submitted by /u/clanggedin
[link] [comments]

Alternative / Duplicate Questions Resolved:

  • "How to Choose the Best macOS Version for Help! An error shows after I “post install root patch”":

    How to Choose the Best macOS Version for Help! An error shows after I “post install root patch”

    The best upgrade is not always the newest release; it is the newest release that keeps graphics, Wi-Fi, sleep, battery and daily apps reliable. Unsupported Macs depend on OpenCore Legacy Patcher root patches, and each macOS release changes drivers, security policy and graphics behaviour.

    Quick Checks

    • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
    • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
    • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

    Fix Steps

    1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
    2. Match macOS to hardware age: 2011-2012 Macs often behave better on Monterey or Ventura; 2013-2017 Macs can usually test Sonoma or Sequoia with an SSD and enough RAM.
    3. Avoid risky releases for production: Treat macOS Tahoe or any newly unsupported path as experimental until OCLP support is explicit.
    4. Update OCLP first: Install the latest OpenCore Legacy Patcher, build/install OpenCore, then run root patches after macOS boots.
    5. Test the real workload: Check browser tabs, Office/Adobe, printing, sleep, Wi-Fi, Bluetooth and battery before calling the upgrade successful.
    6. Keep a downgrade path: Have a USB installer for the previous stable macOS before upgrading.

    Do Not Continue If

    • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
    • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

    Verify It Worked

    • The machine boots twice without manual intervention.
    • Graphics acceleration and Wi-Fi work after root patches.
    • The user apps that motivated the upgrade actually launch.
    • Battery and thermals are acceptable for the intended workload.

    Rollback

    • Restore the previous macOS from Time Machine.
    • Reinstall the older stable release with OCLP.
    • Keep data on a separate backup before experimenting again.

    Next Action

    • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
    • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
    • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

    Related iATKOS Searches

Share:

To those thinking about installing it or not... Go fot it

By Ufuk Durgun

I have an iMac 2017 27" and wasn't confident about installing it because a stable system was really important to me.

But, for some weird reason Safari was running really slow and my Magic Trackpad broke and I needed one new and could only find the one with USB-C that's only compatible with Sonoma because Tim Cook is an asshole.

So, I've decided to install over my current Ventura installation just to test it and THE COMPUTER IS ACTUALLY RUNNING FASTER.

I don't know if it's the animations or the way the new OS handles things, but it seems faster and now the new Magic Trackpad works and Safari is much faster and it's not even a clean install.

Isn't Apple a piece of shit company? They deliberately make Safari worse on Ventura to force users to upgrade and don't even get me started on the Magic Trackpad 3.

But there's an important thing to say about my particular case. I'm not running that piece of shit Fusion Drive, but an SSD and I have 16gb of RAM. If you're running fusion, I'm willing to bet your result will be different.

The only error I've got so far was some blank prompt on the Apple TV app and the "Install MacOS icon" with an exclamation point on the Launchpad. Does anyone knows how can I get rid of that?

So, if you were thinking you should install it or not, like I did, I would say, go for it. It might surprise you.

And the funny thing is that my mom was asking me the other day if I upgraded her old laptop to Windows 11 wouldn't make things run faster and I've said that was impossible due to the fact she had an old laptop and a new system would demand more from it and lo and behold, I'm running a system that's two iterations from the last supported one and is actually running faster. Only Apple can provide you with that kind of experience and the good folks at the OpenCoreLegacyPatcher team that actually made the impossible happen. I don't know how they make it, but I can't thank you them enough for not only making MacOS run this smoothly, but empowering me to give the middle finger to Apple.

Just go for it.

submitted by /u/TheDigitalJockey
[link] [comments]
Share:

How to Fix Need some guidance please on macOS

By Ufuk Durgun

How to Fix Need some guidance please on macOS

Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption. On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

Quick Checks

  • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
  • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
  • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
  3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
  4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
  5. Check privacy permissions: Open System Settings and confirm Location Services, Maps, Weather and system services are enabled.
  6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.

Do Not Continue If

  • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
  • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

  • Maps can locate you without falling back to a stale location.
  • Wi-Fi reconnects after reboot and sleep.
  • Bluetooth remains available after a cold boot.
  • Console no longer shows repeated wireless or location daemon errors.

Rollback

  • Restore the previous EFI if Wi-Fi disappears completely.
  • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
  • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

Next Action

  • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
  • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
  • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Related iATKOS Searches


Original Question: "Need some guidance please"

Hi. I would like to know step by step what should I do in order to install mac os.

I'm an experienced user in Windows only.

I really don't know should I do first , secondly and more.

I have Intel nuc 8.

WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406

WindowsCurrentVersion : 6.3

WindowsEditionId : CoreSingleLanguage

WindowsInstallationType : Client

WindowsInstallDateFromRegistry : 04-Nov-24 13:27:53

WindowsProductName : Windows 10 Home Single Language

WindowsRegisteredOrganization :

WindowsRegisteredOwner : Ronik

WindowsSystemRoot : C:\Windows

WindowsVersion : 2009

BiosCharacteristics : {7, 11, 12, 15...}

BiosBIOSVersion : {INTEL - 61, BECFL357.86A.0097.2024.0221.1015, American Megatrends - 5000D}

BiosBuildNumber :

BiosCaption : BECFL357.86A.0097.2024.0221.1015

BiosCodeSet :

BiosCurrentLanguage : en|US|iso8859-1

BiosDescription : BECFL357.86A.0097.2024.0221.1015

BiosEmbeddedControllerMajorVersion : 3

BiosEmbeddedControllerMinorVersion : 26

BiosFirmwareType : Uefi

BiosIdentificationCode :

BiosInstallableLanguages : 2

BiosInstallDate :

BiosLanguageEdition :

BiosListOfLanguages : {en|US|iso8859-1, }

BiosManufacturer : Intel Corp.

BiosName : BECFL357.86A.0097.2024.0221.1015

BiosOtherTargetOS :

BiosPrimaryBIOS : True

BiosReleaseDate : 21-Feb-24 02:00:00

BiosSeralNumber : G6BE919005Q7

BiosSMBIOSBIOSVersion : BECFL357.86A.0097.2024.0221.1015

BiosSMBIOSMajorVersion : 3

BiosSMBIOSMinorVersion : 2

BiosSMBIOSPresent : True

BiosSoftwareElementState : Running

BiosStatus : OK

BiosSystemBiosMajorVersion : 5

BiosSystemBiosMinorVersion : 6

BiosTargetOperatingSystem : 0

BiosVersion : INTEL - 61

CsAdminPasswordStatus : Unknown

CsAutomaticManagedPagefile : False

CsAutomaticResetBootOption : True

CsAutomaticResetCapability : True

CsBootOptionOnLimit :

CsBootOptionOnWatchDog :

CsBootROMSupported : True

CsBootStatus : {0, 0, 0, 0...}

CsBootupState : Normal boot

CsCaption : MYINTELNUC

CsChassisBootupState : Safe

CsChassisSKUNumber :

CsCurrentTimeZone : 120

CsDaylightInEffect : False

CsDescription : AT/AT COMPATIBLE

CsDNSHostName : MyIntelNUC

CsDomain : WORKGROUP

CsDomainRole : StandaloneWorkstation

CsEnableDaylightSavingsTime : True

CsFrontPanelResetStatus : Unknown

CsHypervisorPresent : False

CsInfraredSupported : False

CsInitialLoadInfo :

CsInstallDate :

CsKeyboardPasswordStatus : Unknown

CsLastLoadInfo :

CsManufacturer : Intel(R) Client Systems

CsModel : NUC8i3BEH

CsName : MYINTELNUC

CsNetworkAdapters : {Wi-Fi, Ethernet}

CsNetworkServerModeEnabled : True

CsNumberOfLogicalProcessors : 4

CsNumberOfProcessors : 1

CsProcessors : {Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz}

CsOEMStringArray : {Default string}

CsPartOfDomain : False

CsPauseAfterReset : -1

CsPCSystemType : Desktop

CsPCSystemTypeEx : Desktop

CsPowerManagementCapabilities :

CsPowerManagementSupported :

CsPowerOnPasswordStatus : Unknown

CsPowerState : Unknown

CsPowerSupplyState : Safe

CsPrimaryOwnerContact :

CsPrimaryOwnerName : Ronik

CsResetCapability : Other

CsResetCount : -1

CsResetLimit : -1

CsRoles : {LM_Workstation, LM_Server, NT}

CsStatus : OK

CsSupportContactDescription :

CsSystemFamily : Intel NUC

CsSystemSKUNumber : BOXNUC8i3BEH

CsSystemType : x64-based PC

CsThermalState : Safe

CsTotalPhysicalMemory : 17052598272

CsPhyicallyInstalledMemory : 16777216

CsUserName : MYINTELNUC\Ronik

CsWakeUpType : PCIPME

CsWorkgroup : WORKGROUP

OsName : Microsoft Windows 10 Home Single Language

OsType : WINNT

OsOperatingSystemSKU : 100

OsVersion : 10.0.19045

OsCSDVersion :

OsBuildNumber : 19045

OsHotFixes : {KB5049621, KB5045936, KB5011048, KB5015684...}

OsBootDevice : \Device\HarddiskVolume1

OsSystemDevice : \Device\HarddiskVolume3

OsSystemDirectory : C:\Windows\system32

OsSystemDrive : C:

OsWindowsDirectory : C:\Windows

OsCountryCode : 1

OsCurrentTimeZone : 120

OsLocaleID : 0409

OsLocale : en-US

OsLocalDateTime : 31-Jan-25 12:20:43

OsLastBootUpTime : 29-Jan-25 13:41:34

OsUptime : 1.22:39:09.0320466

OsBuildType : Multiprocessor Free

OsCodeSet : 1252

OsDataExecutionPreventionAvailable : True

OsDataExecutionPrevention32BitApplications : True

OsDataExecutionPreventionDrivers : True

OsDataExecutionPreventionSupportPolicy : OptIn

OsDebug : False

OsDistributed : False

OsEncryptionLevel : 256

OsForegroundApplicationBoost : Maximum

OsTotalVisibleMemorySize : 16652928

OsFreePhysicalMemory : 11309300

OsTotalVirtualMemorySize : 16669312

OsFreeVirtualMemory : 11521536

OsInUseVirtualMemory : 5147776

OsTotalSwapSpaceSize :

OsSizeStoredInPagingFiles : 16384

OsFreeSpaceInPagingFiles : 8

OsPagingFiles : {C:\pagefile.sys}

OsHardwareAbstractionLayer : 10.0.19041.3636

OsInstallDate : 04-Nov-24 15:27:53

OsManufacturer : Microsoft Corporation

OsMaxNumberOfProcesses : 4294967295

OsMaxProcessMemorySize : 137438953344

OsMuiLanguages : {en-US}

OsNumberOfLicensedUsers : 0

OsNumberOfProcesses : 148

OsNumberOfUsers : 2

OsOrganization :

OsArchitecture : 64-bit

OsLanguage : en-US

OsProductSuites : {TerminalServicesSingleSession, HomeEdition}

OsOtherTypeDescription :

OsPAEEnabled :

OsPortableOperatingSystem : False

OsPrimary : True

OsProductType : WorkStation

OsRegisteredUser : Ronik

OsServicePackMajorVersion : 0

OsServicePackMinorVersion : 0

OsStatus : OK

OsSuites : {TerminalServices, TerminalServicesSingleSession, HomeEdition}

OsServerLevel :

KeyboardLayout : en-US

TimeZone : (UTC+02:00) Jerusalem

LogonServer : \\MYINTELNUC

PowerPlatformRole : Desktop

HyperVisorPresent : False

HyperVRequirementDataExecutionPreventionAvailable : True

HyperVRequirementSecondLevelAddressTranslation : True

HyperVRequirementVirtualizationFirmwareEnabled : True

HyperVRequirementVMMonitorModeExtensions : True

DeviceGuardSmartStatus : Off

DeviceGuardRequiredSecurityProperties :

DeviceGuardAvailableSecurityProperties :

DeviceGuardSecurityServicesConfigured :

DeviceGuardSecurityServicesRunning :

DeviceGuardCodeIntegrityPolicyEnforcementStatus :

DeviceGuardUserModeCodeIntegrityPolicyEnforcementStatus :

submitted by /u/Sea_Propellorr
[link] [comments]

Alternative / Duplicate Questions Resolved:

Share:

Having issues with my MBP MID 2012 installing Sequoia. Might have broken it?

By Ufuk Durgun
Having issues with my MBP MID 2012 installing Sequoia. Might have broken it?

I have a MBP 9,1 mid 2012, 15", 16GB ram with 250GB SSD where I installed Sequoia 15.3 using OpenCore. It wasn't recognizing my WiFi or able to connect to an external monitor (2nd picture) so I tried to install a fresh 15.1 Sequoia on it.

So I erased my SSD (which means no 15.3 anymore is installed) as part of trying a fresh install of 15.1 and I got this error. I currently do not have a bootable 15.3, but I do have a bootable 15.1 giving me this error.

I'm lost and I don't know what to do or what options I have. Can anyone please help me?

submitted by /u/pengouin85
[link] [comments]

Share:

Which version of macOS do I need to rollback to in order to regain use of external monitors via Thunderbolt port?

By Ufuk Durgun

MacBook Pro 8,1 w/ Intel HD Graphics 3000 512 MB. I've lost the use of Thunderbolt Ports after upgrading to Ventura 13.7.2.

This totally defeats the purpose of restoring my old MacBook. Is there a workaround to regain use of the monitor? How far back do I need to downgrade until I can connect external monitors again?

Thanks!

submitted by /u/DavyJonesRocker
[link] [comments]
Share:

My Sequoia 15.3 & OCLP 2.2.0 Testing & Deep Dive Video + AMA!

By Ufuk Durgun

I just posted my macOS Sequoia 15.3 & OpenCore Legacy Patcher testing/update video!

Usually I go over the 15.3 update and what's included. Then I test the latest update against multiple Macs (11 in this video) to make sure it installs and works properly. In this video, I went into a deep dive on how the KDK (Kernel Debug Kit) and MetalLibSupport.pkg works.

I'll be around for a bit and will answer any questions you may have about macOS or OCLP!

https://youtu.be/4Rd3V12Irb0

submitted by /u/MrMacintoshBlog
[link] [comments]
Share:

Unable to get OpenCore Boot picker with PC GPU Mac Pro 3,1

By Ufuk Durgun

Hi, I have a mac pro 3,1 that I put a Nvidia GeForce GTX 1060 into and I can't seem to get the OpenCore boot picker to show up even though I have the option selected for Nvidia GOP Injection in the patcher. I currently have Ubuntu installed on it so can anyone help?

submitted by /u/Switch_modder
[link] [comments]
Share:

HELP PE TO FIND MACOS FOR MY SYSTEM!!!!

By Ufuk Durgun

CPU

Intel Core i3 2100 @ 3.10GHz 45 °C

Sandy Bridge 32nm Technology

RAM

4.00GB Single-Channel DDR3 @ 665MHz (9-9-9-24)

Motherboard

Intel Corporation DH61HO (CPU 1) 29 °C

Graphics

LCD-MONITOR (1366x768@60Hz)

512MB NVIDIA GeForce 210 (ASUStek Computer Inc) 51 °C

Storage

465GB TOSHIBA DT01ACA050 (SATA )

This is my system 😊

submitted by /u/Logical-Newt6787
[link] [comments]
Share:

Mac Pro 5,1 - upgrade from OEM Mojave straight to Sequoia? Possible? Advisable?

By Ufuk Durgun

Hello all,

Had some (self-inflicted) hiccups with my Mac Pro 5,1 & finally got it up and running again on the Mojave. I had previously been trying to get Sequoia to install from Monterey, but the Mac would just sit on the Apple logo after selecting “Install macOS Sequoia.” I was able to create the Sequoia installer fine on three different USB drives but got the same behavior every time.

I guess my direct question is: are there any obvious concerns, hangups, issues, or errors I should be aware of/anticipate trying to upgrade from Mojave?

Mac Pro 5,1, 12-core, 96GB OWC RAM, PowerColor Vega 56, 256GB SATA SSD (Samsung).

Thank you in advance!

submitted by /u/Kindly_Action_8388
[link] [comments]
Share:

MacPro5,1 W6600 & WX7100 egpu?

By Ufuk Durgun

Wondering if anyone has tried this two boot macOS Sequoia from the egpu and leave the W6600 in the system for booting to Monterey when I have to do real work? Or vice versa. Don't want to waste money on a egpu if it won't work. Currently swapping cards back and forth and it's a bit annoying. Also if it works for you what enclosure are you using? Thanks in advance for the feedback.

submitted by /u/According_Ad1271
[link] [comments]
Share:

Mid-2012 MBP 9.2 Scrolling code

By Ufuk Durgun

Thanks in advance for any help and replies.

In the past, I have successfully updated a few MBPs using OCLP.

For some reason, operator error is more than likely. This one is giving me problems.

I purchased based a new Pony USB to create an installer. I followed the instructions on OLCP and was watching a video of MacIntosh pausing between steps as I have before.

However, I get confused when more than one EFI comes up after reboot, and it's starts the pages and pages of code scrolling.

The OS on this MBP is Catalina, and I am attempting to update to Sequoia. On a couple of these models/years, which I updated, this never happened, but I am getting older and may have forgotten some things.

I believe starting over with a fresh install may be the way to go, but I am not sure about erasing the SSD hardrive totally. There is nothing on the MBP I need to keep. It will only be used with my other ones for torrenting, storing media, etc.

Should I have tried to update the older version OS and then proceed to Sequoia or Sonoma? I get confused at the point of rebooting when there are two choices for EFI one has a black card like on it, and the other does not.

I realize it is an old computer, but these are still workhorses as far as my needs on certain things.

I always upgrade ram to real-life specs for these models/years to 16g and install new SSD.

Is it possible the USB was not in the right format, or should I totally delete everything on the USB, which now contains Sequoia Installer along with the SDD harddrive.

I have never had one of the older Macs give me the huge amounts of scrolling code, then not upgrade.

Anyone who has successfully updated unsupported MBP of this time from Catalina or similar OS or has answers to what I may possibly be doing wrong or step skipping, please help if you can.

I will attempt watching the Mr. MacIntosh videos again until anyone has an answer.

Also, chime is not an option to turn off by regular actions in Catalina. So, is there a code to turn off the startup chime in the terminal? The other persons in the house are kinda getting tired of hearing it all day long while I'm working on this upgrade.

The version of OCLP I downloaded for Sequoia installers was, I believe, the newest one available on their website.

Thanks.

submitted by /u/Inevitable-Fix-3212
[link] [comments]
Share:

How to Fix Hackintosh guide on macOS

Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption. On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

Quick Checks

  • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
  • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
  • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
  3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
  4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
  5. Check privacy permissions: Open System Settings and confirm Location Services, Maps, Weather and system services are enabled.
  6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.

Do Not Continue If

  • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
  • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

  • Maps can locate you without falling back to a stale location.
  • Wi-Fi reconnects after reboot and sleep.
  • Bluetooth remains available after a cold boot.
  • Console no longer shows repeated wireless or location daemon errors.

Rollback

  • Restore the previous EFI if Wi-Fi disappears completely.
  • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
  • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

Next Action

  • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
  • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
  • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Related iATKOS Searches


Original Question: "Hackintosh guide"

Can i hackintosh this computer and how?

Please help me.

Does anyone know how to hackintosh a I7-12700 or I3-4130 the simplest way possible? i only have one M2 slot on my motherboard but i have sata ssds if that works (128GB). Please help me.

Hardware:

Asrock H610M-ITX/ac

Crucical Pro DDR4 32GB 3200MHz

I7-12700

GPU: Asus 6650 XT or Powercolor HD7970

Storage:Crucial P3 Plus 2TB

Sata SSD:120GB and 240GB

Crucial:120GB

Kingston:240GB

Wireless LAN- 802.11ac WiFi Module - Supports IEEE 802.11a/b/g/n/ac - Supports Dual-Band (2.4/5 GHz) - Supports high speed wireless connections up to 433Mbps - Supports Bluetooth + High speed class II

Does anyone know how to setup the config.plist file properly and what kexts i need? i would like to dual boot with Windows 10 i want MacOS 14-15.2> and i want to be able to use Apple Account for app store etc.

Please note:I want to keep Windows 10 and dualboot i am not going to erase my current os.

Target version:15.0 and up

Minimum version:14

submitted by /u/Mr_Z12
[link] [comments]

Alternative / Duplicate Questions Resolved:

  • "How to Fix Lenovo T430 Hackintosh Guide on macOS":

    How to Fix Lenovo T430 Hackintosh Guide on macOS

    Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption. On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

    Quick Checks

    • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
    • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
    • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

    Fix Steps

    1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
    2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
    3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
    4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
    5. Check privacy permissions: Open System Settings and confirm Location Services, Maps, Weather and system services are enabled.
    6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.

    Do Not Continue If

    • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
    • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

    Verify It Worked

    • Maps can locate you without falling back to a stale location.
    • Wi-Fi reconnects after reboot and sleep.
    • Bluetooth remains available after a cold boot.
    • Console no longer shows repeated wireless or location daemon errors.

    Rollback

    • Restore the previous EFI if Wi-Fi disappears completely.
    • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
    • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

    Next Action

    • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
    • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
    • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

    Related iATKOS Searches

  • "How to Fix Guide During macOS Boot or Installation":

    How to Fix Guide During macOS Boot or Installation

    Boot failures need a predictable pass through firmware, USB, storage, EFI and verbose logs before reinstalling macOS. Most installer stalls come from firmware settings, an invalid config.plist, wrong SSDTs, bad USB mapping or unsupported storage/controller settings.

    Quick Checks

    • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
    • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
    • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

    Fix Steps

    1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
    2. Boot verbose: Add -v keepsyms=1 debug=0x100 so the final visible line gives a real clue.
    3. Check firmware settings: Disable Secure Boot and Fast Boot, set SATA to AHCI, disable CFG Lock if possible, and use UEFI mode.
    4. Validate OpenCore: Update OpenCore, Lilu and core kexts, then run ocvalidate or ProperTree clean snapshot.
    5. Recreate the installer: Use a fresh USB installer and try another USB port; older Macs may need a USB 2.0 hub for input during setup.
    6. Reset NVRAM: Reset NVRAM from the OpenCore picker before retrying the installer.

    Do Not Continue If

    • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
    • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

    Verify It Worked

    • Verbose boot moves past the previous stopping line.
    • The installer reaches Disk Utility and sees the target disk.
    • Keyboard, mouse and USB remain active during recovery.
    • OpenCore picker still loads after a cold boot.

    Rollback

    • Restore the last booting EFI folder.
    • Use the officially supported macOS installer to recover the machine.
    • Do not erase the internal disk until the installer can boot twice consistently.

    Next Action

    • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
    • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
    • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

    Related iATKOS Searches

  • "Need Hackintosh Build guide!":

    I have already owned

    Processor: AMD 5600x Mobo: Msi B550 Steal legend GPU: GT710 Ram: Adata 3600x 2

    I want to upgrade my GPU. Can u suggested me which GPU should i buy for completely supported Hackintosh

    submitted by /u/psg18
    [link] [comments]
  • "Where can i get a complete guide for hackintosh ?":

    I have Ryzen 5 5500U and Vega 7 gpu.

    submitted by /u/AioliAccomplished684
    [link] [comments]
  • "Looking for hackintosh guide for i7 920 (Bloomfield)":

    Parts

    - i7 920

    - Asus rampage ii motherboard

    - RX 580 4gb

    - 16gb ddr3 ram

    This will be my first even hackintosh, so I have no idea what I am doing. Any help will be appreciated. Thank you.

    submitted by /u/Charming-Language-10
    [link] [comments]
  • "Hackintosh Guide Needed":

    Can anyone suggest a good guide for hackintosh my pc specs are :

    CPU: Intel(R) Core(TM) i5-10400F CPU
    GPU: Nvidia GeForce GT 710
    RAM: 8 GB
    Motherboard/Laptop Make and Model: Gigabyte H410M H
    BIOS version: American mega trends

    Is it even Hacintoshable.

    submitted by /u/HeadCorpse-
    [link] [comments]
Share:

I need a developer or someone responsible for OCLP. My 2015 iMac is having nothing but issues with OCLP a New Problem for OCLP? Sorry for my Bad english!

By Ufuk Durgun

Hello everyone, I’m new here and at my wit’s end.

I collect and restore Apple computers. I upgrade them as much as possible and install the appropriate macOS using OpenCore to keep them usable today.

Specifically, I’m working on an iMac Late 2015 (Model 16,2) with 16 GB RAM. I have two SSDs installed: a standard SATA SSD and another one in the M.2 slot via an adapter. The M.2 SSD is recognized, and everything seems normal so far. Since the iMac natively supports macOS Monterey, I wanted to install Sequoia 15.3 or 15.2. I’ve successfully installed 15.2 on multiple older Macs without any issues.

The Problem:

The installation does not work reliably on this iMac. Normally, my process is:

  1. Download macOS through the app,
  2. prepare a USB stick,
  3. boot from the USB stick,
  4. format the target drive in the Recovery menu, and
  5. start the installation.

This has always worked flawlessly – except on this iMac. Either the installation does not start automatically, or it gets stuck. By forcing multiple restarts, I can eventually get macOS 15.2 installed, but if I unplug the iMac for an extended period, it refuses to boot from the M.2 SSD or freezes.

If I install macOS on the SATA SSD, it runs fine, but this whole behavior still seems odd.

Possible Causes?

  • Is this a bug?
  • Are additional OpenCore settings required?
  • OpenCore is set up correctly, and NVMe support is enabled.
  • After a crash, I only get the standard error message ("Your computer restarted because of a problem"), but no crash logs appear in the macOS Console. but a Panic? (https://pastebin.com/raw/zHVth22g)

Interestingly, Monterey runs without issues, both during installation and in daily use. I’ve thoroughly checked the hardware:
Apple diagnostics show no issues
Both SSDs are new
Thermal paste and PRAM battery have been replaced and tested
PRAM reset performed

A hardware defect is therefore highly unlikely. The issue seems to be related to OpenCore or Sequoia.

Additional Observations:

  • When booting Sequoia from the USB stick, the progress bar freezes, and all USB ports seem to turn off (mouse lighting goes dark).
  • I have to press the power button three times before the installer finally loads into Recovery Mode.
  • During installation (when about 10 minutes remain), the iMac should restart multiple times to continue setup but freezes instead.
  • I have to manually intervene to get the installation to complete.

Has anyone experienced similar issues or found a solution? 🤔

submitted by /u/Outside_Window_5061
[link] [comments]
Share:

**SOME** wifi networks not detected - MacbookAir7,1

By Ufuk Durgun

This is NOT a new post of "OCLP broke my wifi", in the sense that some networks are seen but others are not.

MacbookAir7,1 (last 11" model). A number of wifi networks (in particular one of my home networks, with WPA2 personal) are not visible at all if I install Ventura/Sonoma/Sequoia using OCLP. Trying to manually add the network doesn't work either.

With a regular (non-OCLP) installation of Monterey, I can correctly see the network and join it. They are also visible if I boot into internet recovery mode.

My network is in 2.4 GHz channel 12 which is a permitted channel in Europe (where I am), but apparently not in the USA. Could that be it?

Thanks for reading and for any potential tip.

submitted by /u/pope_es
[link] [comments]
Share:

Software upgrade

By Ufuk Durgun

Hi is anyone having difficulties with software updates? I'm running Sonoma on a 27" 2012 iMac. Nothing seems to happen when I try to update software via system settings. I'm having to upgrade via OCPL.

OK something did just happen after trying and trying and waiting and waiting. It appears to be downloading something although it not telling me what. I'm assuming it's Sequoia but its way easier via OCPL.

submitted by /u/Sure_Method9206
[link] [comments]
Share:

OpenCore-Patchererror error, need help

By Ufuk Durgun

I am trying to install OCLP 2.2.0 onto a 2014 Macbook Pro Retina. During the install process, I get the message "Failed to Create MacOS installer...". I've tried to install Seruoia, and again with Sonoma. I have tryed a few times, all with the same error result. Any solution would help. Thanks.

submitted by /u/Gpruitt54
[link] [comments]
Share:

How do I prevent OpenCore from messing up the EFI boot order?

By Ufuk Durgun

I used OCLP to put Catalina on a 2009 MacBook Pro. Works great! I also saved 60GB of disk space for Linux. Works great!

My issue is — I want the system default boot to be Linux/Grub2. Which it does fine, until I eventually boot into MacOS using OpenCore… at which point OpenCore resets the boot order to OpenCore first. Is there a setting in OpenCore that prevents it from altering the EFI boot order? I keep having to use the Linux efibootmgr command to set the boot order back to Linux as the default

submitted by /u/ksandbergfl
[link] [comments]
Share:

"EFI Boot" waiting at startup or reboot

By Ufuk Durgun

I have successfully installed Sonoma 14.7.2 on Late 2012 Mac Mini.

Model: Late 2012 Mac mini 6,2

MacOS: Sonoma 14.7.2

OCLP Version: 2.2.0

When I reboot or startup, the system waits for me to click on "EFI Boot" to proceed.

After that, it waits for 5 seconds for the boot picker and proceeds automatically without any intervention.

How can I change settings so that the system does not wait for me to click on "EFI Boot"?

submitted by /u/RockCloud9
[link] [comments]
Share:

How to Fix Stuck on boot after macOS Big Sur root patches in 2011 Macbook Air on macOS

By Ufuk Durgun

How to Fix Stuck on boot after macOS Big Sur root patches in 2011 Macbook Air on macOS

Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption. On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

Quick Checks

  • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
  • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
  • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
  3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
  4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
  5. Check privacy permissions: Open System Settings and confirm Location Services, Maps, Weather and system services are enabled.
  6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.

Do Not Continue If

  • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
  • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

  • Maps can locate you without falling back to a stale location.
  • Wi-Fi reconnects after reboot and sleep.
  • Bluetooth remains available after a cold boot.
  • Console no longer shows repeated wireless or location daemon errors.

Rollback

  • Restore the previous EFI if Wi-Fi disappears completely.
  • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
  • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

Next Action

  • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
  • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
  • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Related iATKOS Searches


Original Question: "Stuck on boot after macOS Big Sur root patches in 2011 Macbook Air"

I installed macOS Big Sur on my aunt's old MacBook. but when I installed the root patches and rebooted the progress bar got stuck around a quarter, and this Mac doesen't have Wi-FI. How can I fix it?

submitted by /u/GabrielKLBr
[link] [comments]

Alternative / Duplicate Questions Resolved:

  • "How to Fix Boot up always stuck after Root Patches During macOS Boot or Installation":

    How to Fix Boot up always stuck after Root Patches During macOS Boot or Installation

    Boot failures need a predictable pass through firmware, USB, storage, EFI and verbose logs before reinstalling macOS. Most installer stalls come from firmware settings, an invalid config.plist, wrong SSDTs, bad USB mapping or unsupported storage/controller settings.

    Quick Checks

    • Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
    • Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
    • Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

    Fix Steps

    1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
    2. Boot verbose: Add -v keepsyms=1 debug=0x100 so the final visible line gives a real clue.
    3. Check firmware settings: Disable Secure Boot and Fast Boot, set SATA to AHCI, disable CFG Lock if possible, and use UEFI mode.
    4. Validate OpenCore: Update OpenCore, Lilu and core kexts, then run ocvalidate or ProperTree clean snapshot.
    5. Recreate the installer: Use a fresh USB installer and try another USB port; older Macs may need a USB 2.0 hub for input during setup.
    6. Reset NVRAM: Reset NVRAM from the OpenCore picker before retrying the installer.

    Do Not Continue If

    • Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
    • Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

    Verify It Worked

    • Verbose boot moves past the previous stopping line.
    • The installer reaches Disk Utility and sees the target disk.
    • Keyboard, mouse and USB remain active during recovery.
    • OpenCore picker still loads after a cold boot.

    Rollback

    • Restore the last booting EFI folder.
    • Use the officially supported macOS installer to recover the machine.
    • Do not erase the internal disk until the installer can boot twice consistently.

    Next Action

    • Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
    • If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
    • Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

    Related iATKOS Searches

Share:

I think I broke my MacBook part 3

By Ufuk Durgun
I think I broke my MacBook part 3

It's fix and running the lastest OCLP. I gave up for a while as I just needed a break from it. But since I am on a med leave from work thought I would try again. I did some Google and find a solution I hope would work and it did. I live in a small town which means small library and only two computers open for the public for adults to use (the children have their own computer area).

The problem is that the computersbare always in used by other people that don't have their own computer and hog it for hours watching YouTube and whatnot (yes library staff try but no one gets paid enough to piss someone off and risk getting hurt). Anyway I find was able to get access to a computer download Linux Mint onto a USB key.

I have downloaded Linux Mint before on a few old computers its pretty simple. So I wipe the hard drive, installed Linux Mint, download and install the lasted version of MacOS that I originally had on the MacBook updated everything and then install OCLP.

This round went better obviously, I install the lasted version of Sequoia and did it as a software update instead of a clean wipe install since there wasn't anything on the MacBook. I literally went from mint, to Monterey to Sequoia and everything now works as it should. Thank goodness cause I was driving myself made trying to pin point where I went wrong.

Anyway any suggestions on what I should do now that I finally have this on Sequoia?

Thanks for all of your help reddit

submitted by /u/seleneangel
[link] [comments]

Share: