Jump to content
376 posts in this topic

Recommended Posts

OCLP Devs have produced working non-metal post-install patches for Sequoia in OCLP 2.0.0 (Beta at the time of this writing).  I am now booting Big Sur, Monterey, Ventura, Sonoma and Sequoia on this HackBookPro6,2 (now just for a fun hobby and bragging rights since I don't trust OCLP-patched hacks and Macs for any production use).  My uses for OCLP are my preference.  If you are certain that you have use cases that can't be compromised by a broken APFS seal, disabled SIP and disabled SecureBootModel (or you just don't care), keep using your OCLP patched hack / Mac.

 

I am multibooting multiple versions of macOS with a single Open Core 1.0.1 EFI and am applying OCLP post-install patches to each version of macOS as follows:

  • Big Sur: OCLP 0.6.8
  • Monterey: OCLP 0.6.8
  • Ventura: OCLP 0.6.8
  • Sonoma: OCLP 1.4.3
  • Sequoia: OCLP 2.0.0

I don't upgrade OCLP post-install patches for the sake of upgrading, so this strategy (patching each macOS version with its own fully tested OCLP version) works well for me.  Others may find it more convenient to patch all versions of macOS with the same version of OCLP.  There is no technical reason to keep all OCLP post-install patch versions the same - it's just a personal preference.  

 

I don't expect this old hack to be supported in macOS 16, but I do hope I'm wrong.  This has been a fun journey, which started when, in 2019, someone over at LatitudeOSX told me that "If no one has found a solution for the Dell Latitude E6410 by now, no one is going to find one" (referring to the fact that no one had ever gotten sleep/wake to work properly with the Dell Latitude E6410).  I hope they know how much I appreciated their encouragement ;)

 

There's nothing that motivates me more than being told that it can't be done.  I'm glad the OCLP Devs are motivated to do what others said couldn't be done.

Edited by deeveedee
  • Like 1
  • Thanks 1

Upgrade from Ventura 13.6 -> 13.7 proceeded without issues via OTA.  Still applying Ventura Nvidia Tesla post-install patches with OCLP 0.6.8.

Spoiler

Screenshot2024-09-18at10_16_22AM.png.ffcff43c5d1281f0a45999400ac49d48.png

 

EDIT: ... and Sonoma 14.6 -> 14.7.  Still applying Sonoma post-install patches with OCLP 1.4.3.

Spoiler

Screenshot2024-09-18at11_56_16AM.png.286554c40ecf8a2e77eebe05522a399f.png

 

Edited by deeveedee
  • Like 1
  • 4 weeks later...

Easy upgrade of this HackBookPro6,2 from Sequoia 15.1 Beta 5 -> Beta 6.  Booting with Open Core 1.0.2.  Post-install patches applied with OCLP 2.0.2.

 

Screenshot2024-10-13at4_43_44PM.png.1bbb63af24b22946777fbddb54f2c7fc.png

  • Like 1
  • 1 month later...

FYI - I upgraded Safari to 18.1.1 on this HackBookPro running Sonoma 14.7.1 and re-applied post-install patches with OCLP 1.4.3.  The patched Sonoma volume is no longer bootable.  I can still boot Sonoma 14.7.1 Recovery.

 

EDIT: I was able to boot the corrupted Sonoma volume by doing the following (not sure if all steps were necessary):

  • Boot Sonoma 14.7.1 Recovery
  • In terminal
    • mount -uw /Volumes/Sonoma

    • delete /Volumes/Sonoma/System/Library/CoreServices/OpenCoreLegacyPatcher.plist (not sure if this was necessary)

    • bless --mount /Volumes/Sonoma --bootefi --last-sealed-snapshot

  • Shutdown and then boot the formerly corrupted Sonoma

 

*** When I first attempted this, 'bless --mount...' failed because of missing /Volumes/Sonoma/System/Library/CoreServices/SystemVersion.plist.'  I restored the missing SystemVersion.plist from another Sonoma 14.7.1 installation and then repeated 'bless --mount..'

 

EDIT2: I have been able to duplicate the corrupted Sonoma volume after upgrading to Safari 18.1.1.  It does appear that there is a bug in OCLP 1.4.3 that results in a corrupted Sonoma 15.1.1 Volume when Safari 18.1.1 is installed.  I may need to upgrade the OCLP version that I use to patch Sonoma.

 

EDIT3: Applying OCLP 2.1.2 post-install patches to Sonoma 14.7.1 with Safari 18.1.1 has resolved the patching problem.  My OCLP patching baseline for Sonoma has changed from version 1.4.3 to version 2.1.2.

Edited by deeveedee

Upgraded my EFI from OC 1.0.2 -> OC 1.03.  Upgrade was flawless.  Booting Big Sur through Sequoia.

 

Changes are listed below.  I'm hoping that others can make their own EFI changes, because I'm extremely busy with other things and don't have time to sanitize and post my latest EFI.  This old hack is a lower priority for me than maintaining my newer hacks.

 

EFI Changes from OC 1.0.2 -> OC 1.0.3

  • Upgrade EFI/BOOT/BOOTx64.efi
  • Upgrade EFI/OC/Drivers/*.* (all except for HfsPlusLegacy.efi which did not require an upgrade)
  • Upgrade EFI/OC/OpenCore.efi
  • Upgrade EFI/OC/Tools/*.*
  • Upgrade the following EFI/OC/Kexts
    • Upgrade AppleALC.kext 1.9.2 -> 1.9.3
    • Upgrade IntelMausi.kext 1.0.8 Beta -> 1.0.8 Release
    • Upgrade Lilu.kext 1.6.9 -> 1.7.0
    • Upgrade VoodooPS2Controller.kext 2.3.6 -> 2.3.7
  • Update EFI/OC/config.plist
    • NVRAM > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > OCLP-Version 2.0.2 -> 2.1.2

 

  • Using OC 1.0.3 LegacyBoot
  • Applied OC 1.0.3 LogoutHook
Edited by deeveedee
  • Like 2

Smooth upgrade to Sequoia 15.2 (24C101) patched with OCLP 2.2.0, booting with OC 1.0.3.

 

Screenshot2024-12-11at9_18_53PM.png.9ba97e918f1f38794afd757f617c5be0.png

 

EDIT: After reading reports by some in MacRumors, I expected Sequoia to be slower than previous versions of macOS.  It seems to me that Sequoia 15.2 is more responsive than Sonoma on this 2010 laptop.

Edited by deeveedee
  • Like 2

Upgraded from Ventura 13.7.1 -> 13.7.2 and also Safari 18.1.1 -> 18.2.  The upgrade was flawless via OTA, but patching with OCLP 2.2.0 (which has fixes for Safari 18.2) did not go well.  Safari 18.2 crashed when visiting websites.  My attempt to revert root patches with OCLP 2.2.0 borked my Ventura volume, such that I can no longer apply root patches (even after attempting manual mount and bless).

 

Fortunately, I experimented with a test volume, so I'm going to trash the test volume and remain on Ventura 13.7.1 patched with OCLP 0.6.8 for now.

 

EDIT: Before I had trashed the test volume, user RK78 here suggested using the Safari 18.1.1 installer to downgrade Safari 18.2 to 18.1.1.  This worked!  After downgrading Safari from 18.2 -> 18.1.1, I was able to apply OCLP post-install patches with OCLP 2.2.0.  I am now running Ventura 13.7.2 with Safari 18.1.1, booting with OC 1.0.3 and patched with OCLP 2.2.0.

 

Screenshot2024-12-13at10_45_19PM.png.89cfa84df3461388d511c114b38a935f.png

Edited by deeveedee
  • Like 1
  • 1 month later...

I have uploaded my fully working OC 1.0.3 EFI here for macOS Big Sur through Sequoia.  This is my latest EFI that captures all of my changes documented in this thread.  I have no issues, other than the limitations documented by OCLP Developers.

 

In order to use my posted EFI for Big Sur through Sequoia, add the attached IO80211FamilyLegacy.kext to the OC/Kexts folder.  I needed to remove this kext so that I could upload my EFI without exceeding my 10 MB upload limit.

 

This new EFI represents a ton of work.  Credit to the OCLP Devs for their clever solutions that keep macOS running on this legacy hardware and to the Open Core Devs who have done an amazing job with their bootloader.  I maintain this hack for pride and bragging rights, but I don't trust it for any secure computing because of the way OCLP needs to break fundamental macOS security protections.

 

Important: At the time of this post, do not upgrade Safari beyond version 18.1.1.  If you accidentally upgrade Safari beyond 18.1.1 and have problems, see my previous post here.

 

IO80211FamilyLegacy.kext.zip

Edited by deeveedee
  • Like 2

I just noticed that I have Safari 18.2 running in Sequoia 15.2 on this hack without any observed problems.  It may be that the Safari 18.2 problem (and thus the need to stay on Safari 18.1.1) is just a Ventura issue.

  • Like 2

Smooth upgrade to Sonoma 14.7.3 and Sequoia 15.3.  Running  Safari 18.3 without issues in both OSes.  Both OSes patched with OCLP 2.2.0.

  • Like 1

Smooth upgrade of this hack from Ventura 13.7.2 -> 13.7.3.  Applied post-install patches (Nvidia Tesla) with OCLP 2.2.0.  Booting with OC 1.0.3.

 

Must remain on Safari 18.1.1.  Safari 18.2 and Safari 18.3 crash when running in Ventura 13.7.3.  

 

*** It appears that the Safari 18.1.1 install package for Ventura is no longer available for download from Apple. Recovery from an accidental upgrade to Safari 18.2+ may not be possible with a direct download from Apple. ***

 

Screenshot2025-01-29at11_54_58AM.png.7bce065ee1df951e2bb96eeb424c1c91.png

Edited by deeveedee
  • Like 1

Hello. I recently turned on my old E6420 that I had set aside for a long period. It boots Sierra with a Clover install from Olarila. A time ago, I had put it aside believing that it was as far as I could go with this laptop. I see that you have gone quite further with your E6410. If I could get at least Ventura running on this laptop then that would be great. It would also be nice if no OCLP patches were needed. Do you think an EFI used on your laptop would work? The hardware is close. The graphics is a different model Nvidia. I can try it myself but I would appreciate your opinion before investing the time. I also need a new battery.

E6420.jpg

10 hours ago, Mac Hosehead said:

 Do you think an EFI used on your laptop would work?

I admire your desire to resurrect your E6420.  If you inspect my EFI and look closely at my ACPI patches, you'll note that my ACPI patches are heavily customized for the E6410.  I don't believe my solution will work for the E6420 and am certain that some of the ACPI patches that I created for the E6410 will break and/or conflict with native E6420 ACPI.

 

I did a quick search and see posted Hackintosh solutions for the E6420.  I would recommend that you start with those posted E6420 solutions.  If you don't find what you're looking for, start a new thread asking for help with your E6420.

 

Good luck!

  • Like 1
  • 3 weeks later...

I couldn't resist the temptation, so I created a new APFS volume to test Sequoia 15.4 Beta 1.  Not surprised that Sequoia 15.4 Beta 1 does not boot after applying OCLP 2.2.0 post install patches.  Fortunately, I was able to revert the OCLP root patches by booting into Sequoia 15.4 Recovery and executing "bless --mount /Volumes/SequoiaBeta --bootefi --last-sealed-snapshot" to restore Sequoia 15.4 boot (albeit without OCLP root patches).

 

I also removed OpenCoreLegacyPatcher plists in /Volumes/SequoiaBeta/System/Library/CoreServices, /Library/LaunchAgents and /Library/LaunchDaemons (where SequoiaBeta is my test volume for SequoiaBeta 15.4).

 

EDIT: Here are the specific steps I followed to revert OCLP root patches after not being able to boot Sequoia 15.4 Beta 1:

  • 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.
Edited by deeveedee
  • Like 5
  • Thanks 1

I have the same problem with my iMac late 2013 (27 inch) after the OCLP patch 2.3.0, it no

longer boots Beta1 macOS 15.4

 

I'll try it like @deeveedee wrote here.

 

Is there a new OCLP patch in the pipeline that will hopefully fix the problem?
Has Apple sabotaged the OCLP patch again or?

Edited by AlfredoM

@AlfredoM I haven't seen any OCLP Developer activity, but I'm sure they will be working on the fix.  You can monitor commits to OCLP's GitHub repository here.  Watch for new commits after February 15.

  • Thanks 1

Sequoia 15.4 Beta 2 boots to blackscreen when patched with OCLP 2.2.0 and OCLP 2.3.0 Nightly (not surprised, since I see no commits that improve 2.3.0 over 2.2.0 for NVidia Tesla graphics).  Reverted to bootable state by following steps here.  It appears to me that Sequoia 15.4 Beta needs updated OCLP patches for NVidia Tesla.

  • 4 weeks later...

OCLP 2.3.0 Release has successfully patched this HackBookPro6,2 running Sequoia 15.4 RC1. Posting this with Safari 18.4. Still booting with OC 1.0.3 EFI. For my purposes, all appears ok. Will be upgrading to 15.4 Release and maybe OC 1.0.4 soon. Well done, OCLP Devs!

 

Screenshot2025-03-31at3_44_38PM.png.1eee131c184c4449be160af118507d98.png

 

EDIT: After upgrading to Sequoia 15.4 (Release) and upgrading my EFI to OC 1.0.4, all still appears to be good for my limited use cases.

Edited by deeveedee
  • Like 1

@Flynn Huang I perform my macOS and OCLP updates with a wired Ethernet connection.  I keep the wired Ethernet connected during the entire macOS upgrade and OCLP patching process.

 

EDIT: I'm not planning to post my Open Core 1.0.4 EFI any time soon, since it's not a necessary upgrade for this hack.  For those who want to upgrade my posted EFI from OC 1.0.3 -> 1.0.4, here are the changes:

 

  • EFI/BOOT/BOOTx64.efi
  • EFI/OC/Drivers/*.* (all except for HfsPlusLegacy.efi which did not require an upgrade)
  • EFI/OC/OpenCore.efi
  • EFI/OC/Tools/*.*
  • EFI/OC/Kexts
    • Upgrade AppleALC.kext 1.9.3 -> 1.9.4
    • Upgrade VirtualSMC.kext 1.3.4 -> 1.3.5 1.3.6 (When it is available from Acidanthera)
      •  Upgrade SMCBatteryManager.kext 1.3.4 -> 1.3.5 1.3.6 (When it is available from Acidanthera)
  • EFI/OC/config.plist
    • Add Booter > Quirks > ClearTaskSwitchBit (Boolean, False)

 

  • Apply OC 1.0.4 LegacyBoot
  • Apply OC 1.0.4 LogoutHook
Edited by deeveedee
Changed VirtualSMC.kext version from 1.3.5 -> 1.3.6
  • Like 2

@deeveedeeUpgrade successful.After using it, I have the following feelings:

  • Compared to the high Sierra, Ventura runs slower and generates more heat.
  • The graphics card support can be used, but it is not perfect.
  • WiFi and Bluetooth are slow to reconnect after being covered or sleeping, and sometimes I have to manually connect them.

I think all of these are normal and acceptable. Additionally, my E6410 is no longer able to save BIOS settings information, it's not a battery issue. I feel like my old buddy hasn't been with me for long. It has been idle for a long time before, You let him continue to shine. Thank you very much!

Edited by Flynn Huang
  • Like 1

@Flynn Huang I agree that High Sierra is the most responsive macOS (and am not surprised, since that's the last macOS version that is "natively" supported without patches).  I am not experiencing the Wi-Fi / Bluetooth "slowness" that you describe, so I don't know how to explain them.  Is it possible that your antenna connections are faulty?  I haven't touched the BIOS settings for a long time, but I remember experiencing some BIOS issues that I resolved by resetting BIOS to factory settings and re-configuring.  In my opinion, Dell did not do a very good job with this laptop's BIOS.

 

I currently have Big Sur, Monterey, Ventura, Sonoma and Sequoia installed on separate APFS volumes.  All booting with the same EFI (my posted EFI upgraded to OC 1.0.4).  On a separate SSD (not currently installed, I have High Sierra). I rarely have the High Sierra volume installed at the same time that I have Big Sur and newer volumes (because the older and newer macOS versions don't coexist well).  When I want to boot High Sierra, I install my High Sierra SSD and remove my Big Sur+ SSD (and vice versa).

 

Since I don't use this laptop for any "production" use (just for tinkering and the fun of keeping it alive), I have very low expectations that are easily exceeded by this hack.

 

EDIT: @Flynn Huang Are you applying the PowerManagement settings listed in the attached file?  If not, these may help your sleep/wake observations.  You can copy the attached file to your Desktop, change it to executable (chmod +x) and run it.

 

EDIT2: I just tested sleep / wake a few times (by closing the lid, waiting for the laptop to sleep and then opening the lid).  When running Ventura 13.7.5, this laptop wakes immediately and Wi-Fi / Bluetooth is available almost immediately after waking from sleep.

 

pmset-fix.zip

Edited by deeveedee
  • Like 1
On 4/3/2025 at 10:52 PM, deeveedee said:

@Flynn Huang I agree that High Sierra is the most responsive macOS (and am not surprised, since that's the last macOS version that is "natively" supported without patches).  I am not experiencing the Wi-Fi / Bluetooth "slowness" that you describe, so I don't know how to explain them.  Is it possible that your antenna connections are faulty?  I haven't touched the BIOS settings for a long time, but I remember experiencing some BIOS issues that I resolved by resetting BIOS to factory settings and re-configuring.  In my opinion, Dell did not do a very good job with this laptop's BIOS.

 

I currently have Big Sur, Monterey, Ventura, Sonoma and Sequoia installed on separate APFS volumes.  All booting with the same EFI (my posted EFI upgraded to OC 1.0.4).  On a separate SSD (not currently installed, I have High Sierra). I rarely have the High Sierra volume installed at the same time that I have Big Sur and newer volumes (because the older and newer macOS versions don't coexist well).  When I want to boot High Sierra, I install my High Sierra SSD and remove my Big Sur+ SSD (and vice versa).

 

Since I don't use this laptop for any "production" use (just for tinkering and the fun of keeping it alive), I have very low expectations that are easily exceeded by this hack.

 

EDIT: @Flynn Huang Are you applying the PowerManagement settings listed in the attached file?  If not, these may help your sleep/wake observations.  You can copy the attached file to your Desktop, change it to executable (chmod +x) and run it.

 

EDIT2: I just tested sleep / wake a few times (by closing the lid, waiting for the laptop to sleep and then opening the lid).  When running Ventura 13.7.5, this laptop wakes immediately and Wi-Fi / Bluetooth is available almost immediately after waking from sleep.

 

pmset-fix.zip 682 B · 1 download

Thank you for your continued support. I have been using it with high proficiency this weekend. My E6410 is mainly used for entertainment. Watching news and online videos, listening to music, the effect is very good, and even some pictures can be processed with Photoshop. Based on my feelings for him, I will continue to use him as long as he is willing.:lol:

  • Like 1

I have upgraded a few kexts in my Open Core EFI.  I haven't yet uploaded my latest EFI, but the changes are easy if you want to make the changes yourself.

  • Upgrade VirtualSMC.kext to 1.3.6 from here
    • VirtualSMC.kext
    • SMCBatteryManager.kext
  • Upgrade BrcmPatchRAM to 2.7.0 from here
    • BlueToolFixup.kext
    • BrcmBluetoothInjector.kext
    • BrcmFirmwareData.kext
    • BrcmPatchRAM3.kext
  • Like 2
  • 2 weeks later...

Sequoia 15.5 Beta 3 (24F5053j) breaks Safari page loading (same problem that Safari 18.2+ has in Ventura).  If you are testing Sequoia 15.5 Beta versions on this old hack, you may want to stop at Beta 2 if you need working Safari.  If you don't need Safari, Firefox is a suitable/working replacement (my opinion).

 

Reverting to older versions of Safari (I tested as far back as August 2024) does not fix the non-metal Safari issues in Sequoia 15.5 Beta 3 on this hack.

Edited by deeveedee
Fixed typo
  • Like 1
×
×
  • Create New...