All Activity

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.

Good. Can you make click on address -> move here? Like an address of jne instruction

Apple has released macOS Sequoia 15.7.8. The full installer can be downloaded from here: https://swcdn.apple.com/content/downloads/11/25/140-71763-A_J1EVMAEOWN/smk9mja1myiettgeafge6oha4levx39v2i/InstallAssistant.pkg EDIT: Very fast incremental update on my HackBookPro16,2. My system details: HP EliteBook 850 G7 (i7-10610u / 10th Gen Intel UHD Graphics) Open Core 1.0.7 SIP fully enabled: csr-active-config = <00000000> Wi-Fi: Intel itlwm / heliport No root patches EDIT2: It appears that the final release of macOS Sequoia 15.7.8 has resolved the Transparent Proxy issue that I was observing with Norton Firewall.

For example I installed Tahoe on my first computer all stages with Clover automatically. First time on HDD and second time on SSD as upgrade on Sequoia. If the EFI folder is good enough then all stages passed without a problem. I see no what is the possible error in your case. See my Quirk set config.plist

Small and fast sequential OTA update (894.5 MB) from macOS 26.6 RC (25G70) to macOS 26.6 (25G72). Apple has not yet released a matching Kernel Debug Kit for macOS 26.6 (25G72). OCLP therefore correctly selects Kernel Debug Kit 26.6 build 25G5065a, corresponding to macOS 26.6 beta 5, as the closest available match. My Broadcom/OCLP setup (BCM943602CDP) works under macOS 26.6 as expected. AppleHDA, Wi-Fi, native Bluetooth, AirDrop, AirPlay, Screen Mirroring, Continuity Camera, Personal Hotspot, and sleep/wake all appear to be working properly. The Tahoe Drive Icons Pack and all other customised icons continue to work as expected. Useful context information: a.) Universal-EFI-Folder distribution b.) Setup and troubleshooting guidelines for OCLP/OCLP-Mod/OCLP-Plus c.) OCLP 3.0.0 Nightly - amfipassbeta Edition d.) OCLP-Mod e.) OCLP-Plus f.) WiFiPatcherPro g.) HDAUniversal h.) X299 Guidelines i.) DownloadFullInstaller j.) About-This-Hack k.) Tahoe Drive Icons Pack l.) Stacks in Da Place

You may live without GPU acceleration like I do with my laptop #2. I am just not sure if you may launch Ventura somehow on Fermi. Forget about DSDT patching, it will not help.

I went ahead and tried this. Installing macos 15.7.7 from an installer USB on a mac mini to an external USB hard drive. It worked. This is what happened Booted mac mini into 15.7.7 installer USB. Formatted APFS partition as before with single volume MacHD to start. Ran 1st stage install. One thing I noticed is some messages reporting successful connections to Apple servers retrieving some update data that I did not see happen on a PC. This might be because of incomplete SMBIOS information or ACPI information that's used to identify the system. At completion of 1st stage install I turned off the mini, moved the disk to a PC to see what's on it. It appeared pretty much the same as after the 1st stage install on a PC, and the same size. There might have been some small changes in data files I didn't notice. Then moved disk back to mini to restart 2nd stage install. 2nd stage install completed. Again, I shut off the mini and moved the disk to PC to see what's on it. Again, it seemed in the same state as after the 2nd stage on a PC and the same sizes. The same nearly-empty Data volume. Again, Clover doesn't show an entry for it because it doesn't recognize it as anything bootable. Moved disk back to mini and voila - mini recognizes it as something bootable and knows how to boot it into 3rd stage install. 3rd stage install goes on for awhile with a bar moving at the bottom but no timer and completes. Then reboots. At this point I no longer had patience to move the disk to PC to see what's on it. I let it continue. Booted into 4th stage install. Again this went on for awhile with a bar advancing at the bottom and no timer. Eventually completed and rebooted. Again, didn't have patience to move the disk to a PC to see what's on it and let it continue. Booted into the 5th stage which is the final one. It took a long time to boot because of the slow magentic media but eventually arrived at the setup screen with "Select your region". I was able to safely shut it down by holding the power key and selecting shut down. So now there's a working system on the hard drive which can hopefully be replicated to SSD with asr command to be set up and used there. Conclusion Clover knows how to boot the installer USB. Clover knows how to boot the disk after first stage into 2nd stage. Clover doesn't know how to boot the disk into the 3rd stage. Needless to say I have no idea about the 4th stage. The 5th stage is final so Clover may be able to do that. It is very well possible that might work to boot into the 3rd stage with Clover, but it'll have to wait for another day...

@Zenith432 Try clear NVRAM before booting in the preboot Volume

@LuckyOldMan, Unfortunately, I don't have access to my Hackintosh at the moment because my NVMe drive failed (it burned out). In any case, please send me your EFI folder so I can check what might be causing the issue.

I used softwareupdate on Mac mini to download macos 15.7.7 and created a USB stick (which is new) with createinstallmedia. You think this can go bad? I can redo it. I just think if there were corrupted files there it would crash in a less subtle way. I could try to do the install on a mac mini to the external USB magnetic drive and see if that succeeds. 🤔

It could be a bad macOS Installer

Thanks. I'll try this later. Here's an update. The problem is not a faulty SSD. I tried (with my initial config) on an external USB magnetic drive with a 120 GiB APFS partition and ended up with exactly the same result. The time countdown during the 2nd stage actually went to down to 1 minute before reboot. Here's a little more detail of what I see I start out with a formatted APFS partition (newfs_apfs -C) and add one volume MacHD on it. Owners are enabled. After 1st stage install, there is still only one volume MacHD with one folder on it 'macOS Install Data'. It appears to contain everything (about 17.48GB). I can find no log. The APFS partition also has the Preboot, Recovery and VM volumes. After 2nd stage install, there are now two volumes. MacHD and "MacHD - Data". The one named MacHD is 11GB+ big and appears to have pretty much everything on it, maybe even too much (see later). The Data volume is nearly empty (about 312MB), with only one non-empty folder on it com.apple.installer that has most of the boot files of a recovery boot partition. It has a prelinked kernel, but no file named boot.efi (although there are boot.efi with various extensions.) What should be the Data volume can be found on the MacHD volume under System/Library/Templates/Data. It's not really a deployed Data volume, but some kind of template to be made into a Data volume. So this is something that looks like it should have been copied to the Data volume and 'filled in' from a template, then removed from the MacHD volume. But none of this got done. It's as if the installer decided to quit midway for some reason. There's a boot.efi in /usr/standalone/i386 under MacHD, but no com.apple.Boot.plist except in the right place under System/Library/Templates/Data where it's just a template without entries filled in. I couldn't find anything which may be a log of what happened during the 2nd stage. 😳

Thanks for sharing your experience on the E6430! I totally get why you stayed on 10.11.6 — Fermi + Web Drivers on 10.13.6 is notoriously glitchy, and without OCLP back then there was no real fallback. But here's my actual goal: I'm not just considering 10.13.6 — I'm actually trying to push all the way to macOS Ventura 13.7.8. The reason is simple: even 10.13, 10.14, and other 10.x versions are now far too old. Many modern apps (browsers, dev tools, AI, Steam, etc.) have already dropped support for the entire 10.x line. Staying on any 10.x system means I'd still be stuck with outdated, insecure, or partially broken software. Ventura is the oldest macOS version that still gets relatively broader third-party app support compared to the 10.x era. I know Fermi (GT 555M) has zero native acceleration on Ventura and it'll be a framebuffer-only / basic display setup, but my priority is app compatibility rather than graphics performance. That's why I'm exploring DSDT patching, and OpenCore workarounds to make Ventura boot on this L702X 3D machine at all. Did you ever consider going beyond 10.13.6 toward something like Big Sur or Ventura just for the app ecosystem, despite the lack of GPU acceleration?

Last week I tried installing WiFi Patcher PRO – once on an iMac 18.3 @ Tahoe 26.5.2 @ OCLP3.0.0n and once on a Hackintosh MP7.1 @ Tahoe 26.5.2 @ OC 1.7. Unfortunately, without success. iMac 18.3: Hackintosh MP7.1 - Z170DL Both attempts ended with an "EFI folder validation error". What is going wrong?

@naquaada I get why you're using Yosemite on your old Mac. What's not clear is why you're using OCLP with Yosemite on a real Mac. It seems that we're not understanding each other. Sorry I'm making this harder than it should be. I hope you find the cause and the solution.

@lorys89 b10 version works fine on my M4. I think that all is as it should be. Good work.

Because it is the last version with the good Disk Utility. This one allows much better control, especcially if you are often using DIsk Images. And Yosemite is really fast. The boot process has none of the usual pauses in the loading bar, it boots right through in just 9 seconds. And because all software I use is available for Yosemite, it is for me a full operating system. I also have some 32-bit programs which I still use.

Hi @Zenith432 Happy to see you again 😀 Try this config attaching here, its yours but with the SMBIOS more completed You can clear the NVRAM first before booting to the USB install media config.plist.zip

This: MACOSX_DEPLOYMENT_TARGET = 10.13

IN 1.1.4 - Automatic updates — install & relaunch is now fully reliable: the app quits cleanly past the update dialog and relaunches itself into the new version. If it can't write to its own location it falls back to opening the download page instead. - Reliability fixes across the updater. Download: https://github.com/luminadevapps/KernelInspector/releases/download/v1.1.4/KernelInspector-1.1.4.dmg

@Max.1974 You can run the sensor check—which takes 6 minutes—and then send me the file generated on the desktop. I'm missing the one for your M4 Pro CPU, so I can check if it's okay or if I need to tweak anything. Thanks, buddy.

Google search shows "Memory try it!" is only on MSI motherboards and this is Gigabyte. There is no such feature in the BIOS. The "Above 4Gb encoding" is disabled and always has been. Nothing is overclocked. I took out a 2nd memory module that is slower and has dual rank, although I had the same install issue before putting it in. The module was causing delays during BIOS post for some reason anyway. I'll try install again when I have time and also try with an external magnetic hard drive. There's a problem with external drives that they have "Owners enabled" off by default and this sometimes casues security problems. For example I found that when doing TimeMachine restore of Catalina to an external drive, it restores the System Data volume with "Owners disabled" and the system won't boot unless the ownership is manually corrected with a script !!! I will try the OpenCore memory quirks although I don't know what they do. I will try looking for remnants of installation log files on the unworking system that ends up from install too. Thanks.