All Activity

I didn't find anything significant in your configuration file that could prevent it from loading. But I didn't check for any quirks. Some of them do not match the recommended default values (It needs to be selected individually).

After a second or third attempt, it worked with OCPL PLUS on NEW:

👍

Regular to regular delta updates on PC Laptop , PC Desktop and Mac Laptop :

From macOS 26.6 RC (25G70) to macOS 26.6 (25G72) (894.5MB) Beta Updates/off The Safari language issue has been resolved with Seed2.

Thank you – that's very kind. Attached is the config.plist of the Z170DL Hackintosh – due to the attachment size limit. But the config.plist should provide sufficient information. If not, please ask or tell me how I can send you the complete EFI folder. If there's anything redundant that I'm still carrying over from previous OpenCore versions, feel free to delete it. I'd also like to use the WiFi Patcher for the unsupported iMac 18.3 @OCLP3.0.0n. OCLP3.0.0n is currently unchanged from how I downloaded it. What would need to be changed for your patcher to be accepted there as well? config.plist

Error updating new audio in AppleALC using OCPL-Plus or MyKextInstaller on this same computer; this error did not occur in the beta version.

Hi all users I want to update from 15.7.7 to 15.7.8, my old Ivybridge (OCLP 2.4.1). Actually, MetallibSupportPKG release is 24G809 on Dortania repo. Does it work for macOS 15.7.8 (24G824) ?

Regular delta update, only on desktop PC :

I think latest regular update for Sonoma, From regular to regular delta update, Deskto and Laptop PC:

@Max.1974 You might have misunderstood; you need to start the sensor check and send the file generated on the desktop once the check is complete. And after this process, which takes about 6 minutes, you will have the file on your desktop. You need to send me that file.

No. I said I was using 5173 in my first post. Downloaded binary from github. Please clarify how you booted into the 3rd stage of the install - did Clover show you an icon or did you need to show hidden options (F3) and use the Preboot volume? I don't get an icon for booting the 3rd stage. I can expose the Preboot with F3 and use that. I also said this in my first post 'Clover does show an option to boot the APFS partition from the "Preboot" volume, but this starts and hangs midway eventually rebooting.' I think I misinterpreted this. In the 3rd stage, with no icon, I tried booting the Preboot instead. There is a progress bar without a timer. It went through about midway, then got stuck there for some minutes and finally rebooted. After the reboot there was again no icon. So I interpreted this to mean that it's stuck in some kind of loop and not succeeding and didn't try to boot the Preboot again. But it may have completed the 3rd stage and now I was supposed to start the 4th stage the same way. On the Mac mini, during the 3rd stage the progress bar moved through until the end before rebooting so it looked like a successful completion. Also, when booting the Mac mini before the 3rd stage into the boot selection menu by holding the Alt key - it shows an option for booting the newly installing disk. There is an icon for it. PS I see in the config.plist you uploaded that DefaultVolume is set to LastBootedVolume which is taken from nvram. Before the 3rd stage, it would be set to the system volume 'MacHD' which was used to boot the 2nd stage, and as I said in a previous post there is a /usr/standalone/i386/boot.efi there. There is no com.apple.Boot.plist in any of the usual locations. So set to LastBootedVolume it may boot automatically to something that works. I have DefaultVolume set to Windows, so have to manually select what to boot - and there is no icon for the installing disk. It's not detected. It's detected before the 2nd stage (when boot.efi is under the 'macos Install Data' tree), but not before the 3rd stage. The MacHD APFS volume was formatted with the default case-insensitive, although system files always have the same case so I don't see why it would matter. Update: The plot thickens. I connected the external HDD with the macos 15.7.7 that was successfully installed and is bootable on mac mini to PC. Booted to Clover to scan it. Guess what? Clover does not detect the system. I then press F3 to show the hidden entries and it shows Preboot and Recovery on this APFS partition. It doesn't show the main system volume. Here are photos showing it detects the Preboot and Recovery volumes but not the main system volume https://drive.google.com/file/d/1YdHPn3tfvkEHnvqOR6GVwP5O9oZI79Oe https://drive.google.com/file/d/1_D6ARKax9S33LUD_SiU-jKM4k6XAQszV I boot into the Preboot, which actually goes suspiciously quickly and it arrives at the hello screen https://drive.google.com/file/d/1m5idVdO_a3a6CBWZfixy6GaopLX8AHcL From this I can proceed to language selection and region selection. I checked the system volumes (main+data) with the installer USB and they seem fine. There's boot.efi in /usr/standalone/i386 and /System/Library/CoreServices on the main system volume and com.apple.Boot.plist on the Data volume at /Library/Preferences/SystemConfiguration. So what's going on? The quirks, ACPI, SMBIOS settings have nothing to do with the detection. They're runtime options. My config.plist is in my first post. Why is the system undetected? The APFS partition was formatted with newfs_apfs from 15.7.7. The binaries are from Clover github 5173, including CloverX64.efi and ApfsDriverLoader.efi. The APFS driver itself is on the APFS container. Edit: I tried resetting nvram (F11) several times. Doesn't make any difference.

smooth update to 15.7.8 here as well.

smooth update from 14.8.5 to 14.8.8 with clover 5166

https://swdist.apple.com/content/downloads/56/57/140-71750-A_ZJ1ETGFD03/dnnk12px38rclkv5ettt24crfqd9w244ua/140-71750.English.dist https://swdist.apple.com/content/downloads/56/57/140-71750-A_ZJ1ETGFD03/dnnk12px38rclkv5ettt24crfqd9w244ua/InstallAssistant.pkg [ 40 ] 2026-07-27 18:01:08 .. 140-71750 .. 26.6.0.25G72 macOS Tahoe

Hi there, I came across your post from 2023 about the Dell XPS 17 L702X 3D — interesting to see someone else working on the same rare 3D variant! I wanted to follow up because I've recently picked up my own L702X 3D again after it sat in storage for years. Back then I was running macOS 10.9 Mavericks + Clover, and I'm now in the process of upgrading it all the way to macOS Ventura 13.7.8 + OpenCore. The machine is going to be a programming learning laptop for my son, so I need reasonably modern app support — that's why I'm skipping the entire 10.x line and pushing straight to Ventura. I actually have some positive progress to share since I last checked: on Ventura 13.7.8, I've managed to get the display running at 1600×900 resolution, up from the default 800×600 @ 1MB VRAM right after installation. It's now showing 5MB VRAM with basic framebuffer output — no acceleration of course (Fermi has zero Metal/QE-CI on Ventura), but the desktop is usable for coding, SSH, and light tasks. I read that you couldn't enable the Intel HD 3000 on your 3D unit, which matches what I understand about the hardware — the 3D variant has the display hard-wired directly to the GT 555M with no Optimus, so the iGPU is disabled at the BIOS/mux level. That part hasn't changed. Since you were working on this in 2023, I'd love to compare notes. Could you please clarify a few things when you have a moment? GT 555M status on Ventura: Were you able to get the GT 555M recognized with the correct VRAM size (e.g. 3 GB), or was it stuck at a small value like 5 MB / 256 MB with no acceleration? Which Ventura build?: Which exact macOS Ventura version were you running back then? (e.g. 13.4, 13.5, or something else?) EFI & ACPI sharing: If you still have it, would you be willing to share your EFI folder and any ACPI patches (DSDT/SSDT) you used? Even if HD 3000 couldn't be enabled, your GT 555M configuration from 2023 might give me useful pointers for my current OpenCore setup. Thanks in advance for any info you can share — and good luck with whatever you're running on your L702X these days!

Thanks for the honest feedback! I actually have some positive progress to share — I managed to boot macOS Ventura 13.7.8 on this L702X 3D machine, and it's now running at 1600x900 resolution. Compared to the default 800x600 @ 1MB VRAM right after installation, this is already a huge improvement in usability — text is crisp, the UI is scaled properly, and basic desktop navigation is smooth enough for non‑graphic tasks. As you correctly pointed out, the VRAM is still showing only 5MB and there is zero GPU acceleration (no Metal, no Quartz Extreme). Regarding DSDT: I understand your point that patching alone won't magically enable acceleration. My current DSDT work is purely aimed at cleaning up ACPI errors, fixing embedded controller queries. It's a complementary step, not a miracle fix. So yes — it boots, it renders at 1600x900, but it's a software‑rendered desktop. For my use case (SSH, text editing, legacy app testing), even this limited state is valuable. Thanks again for the reality check — it helps me set the right expectations while I keep tweaking the EFI and OpenCore quirks!

Oh nice my friend, thanks for your work! Good App Here report: sensor-dump-Mac16,11-20260727-220247.txt.zip

I installed macOS 26.6 (25G72) and everything is working as expected.

Why don't you download Clover from here first and do everything as described in the manuals many times? I can assume that you are using an incomplete Clover installation package. 1. I installed MacOS 15.7.7 from an installer USB on a rented Mac mini to an external USB hard drive. 2. I installed Clover then I put the necessary kexts and the correct config into the EFI and moved the hard drive to my main RIG. It worked fine.

Creedence bug gone at last.

Apple has released macOS Sonoma 14.8.8. Note that Beta Updates must be Off to receive this update. The full installer is here: https://swcdn.apple.com/content/downloads/40/12/140-75436-A_GB8UWVHS9N/5xfegq6xrfx5iewmc26aruzvv4ykpubijg/InstallAssistant.pkg ======================================== Very fast and easy incremental update.

Easy incremental update to macOS Tahoe 26.6 (25G72). Note that Beta updates must be Off to receive this update. My system details are as follows: HP EliteBook 850 G7 Laptop (i7-10610u, 10th Gen UHD Graphics) Open Core 1.0.7 SIP csr-active-config = <01000000> (allow untrusted kexts) Wi-Fi: Intel itlwm / heliport Audio: VoodooHDA.kext 3.6.4 No root patches

@Zenith432, Did you compiled Clover by yourself? By what compiler? You may have a problem with file names so why Clover will not see file "boot.efi". Just a glitch of Xcode clang compiler.