SecureBootModel does not affect OTA for their system, please don't modify OCLP manually this way. People can easily brick their configs, and we'll tell them off as we're not going to support those configurations.
# Enroll Developer Seed
sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll DeveloperSeed
# Force Software Update scan
softwareupdate -l
Adding to this: it happens on fully supported machines as well (including my Mac mini with Apple Silicon.)The actual solution to this is most likely just re-enrolling in the Developer Seed, an issue as old as Apple's had public betas
This is the terminal result:SecureBootModel does not affect OTA for their system, please don't modify OCLP manually this way. People can easily brick their configs, and we'll tell them off as we're not going to support those configurations.
SecureBootModel on a pre-T2 Mac will set Target Type to x86legacy, which it already defaults to... No change will be made. We already implement VMM spoofing for OTA updates regardless which Apple will always support for as long as they support Virtual Machines.
If there's an issue with our VMM patches, we need to fix it. Not throw it under the rug.
The actual solution to this is most likely just re-enrolling in the Developer Seed, an issue as old as Apple's had public betas:
Bash:# Enroll Developer Seed sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll DeveloperSeed # Force Software Update scan softwareupdate -l
I do not understand how to do this I m not a programmer can you explain how to do that please??@mortiis
Then I think you must change NVRAM >> Add >> 7C436110-AB2A-4BBB-A880-FE41995C9F82 >> csr-active-config to 6F020000 or 7F020000. Adding also (if it's not yet) csr-active-config in NVRAM >> Delete >> 7C436110-AB2A-4BBB-A880-FE41995C9F82.
I would wait longer for a software fix.
The alternative would be routing the USB connection on the wifi/bt card to a supported USB card in a PCIe slot. I previously tried this and it worked but you lose the ability to wake with bluetooth and I had to toggle bluetooth off/on after sleeping. You would also need a male USB to terminal adapter or similar. For MP3,1 you might have to cut traces on the adapter board.
You can circumvent it on cMP3,1 by using a simple (even non-powered) USB hub attached to any of the built-in USB2 ports, connect your kbd/mouse to it and you're fine...Thanks for your hints. Yes, I will first wait for new OCLP versions.
There are many new kexts, including new USB1.1 kexts with MinKernel 22 in the new OCLP-EFI for cMP3,1.
Correct, USB mapping is broken.
Monterey:
View attachment 2089470
View attachment 2089471
Ventura:
View attachment 2089472
View attachment 2089473
I have also tried all USB ports. No success. So I'm waiting.
You aren’t a developer but an OCLP user. You must check OCLP guides. Since OCLP is based on OpenCore, you must look for structure and edition of the config.plist file. Afterwards, open config.plist with a plain text editor (TextEdit is valid if you save the file as plain text). Look for the keys and change them.I do not understand how to do this I m not a programmer can you explain how to do that please??
I would also be interested in any experiences with a MBP4,1. So far I wasn’t even able to fully start up from the installer located on a bootable USB flash drive created via createinstallmedia, EFI patched with current 0.5.0alpha.Any success stories with MBP4,1 and older iMacs?
(I know that the MP6,1 is a special problem case, just wanted to share the observation that it stalls out at the same boot step).
I have not directly installed Ventura on the MBP4,1 but transferred the drive from another unsupported machine to the MBP4,1. I personally postpone such fresh installs to when things come out of beta phases... ;-)I would also be interested in any experiences with a MBP4,1. So far I wasn’t even able to fully load and run the installer located on a bootable USB flash drive created via createinstallmedia, EFI patched with current 0.5.0alpha.
The installer stops at a very early stage, empty progress bar under the apple logo appears then gets stuck. Also tried verbose mode, listed messages seem to be similar to the ones Larsvonhier received.
Edit: @Larsvonhier .. ah, right know while I was typing/asking. Must be reading my mind. ;-)
Possibly the installer has to be run from within an already booted OS like Monterey on that machine or as an OTA update over the current one?
add the cryxxx.kext from a fresh install, worked for me in ivy bridge, hd4000, p4000.. you need sip 803 instead of 802 and the amfigetoutofmyway=1. very nice.. need complie your own oclp 5a.. but need close and reopen terminal after install pyinstaller else complain of missing module, the file in in dist dir not in build dir as a site suggestedI would also be interested in any experiences with a MBP4,1. So far I wasn’t even able to fully start up from the installer located on a bootable USB flash drive created via createinstallmedia, EFI patched with current 0.5.0alpha.
The installer stops at a very early stage, empty progress bar under the apple logo appears then gets stuck. Also tried verbose mode, listed messages seem to be similar to the ones Larsvonhier received.
Edit: @Larsvonhier .. ah, right know while I was typing/asking. Must be reading my mind. ;-)
Possibly the installer has to be run from within an already booted OS like Monterey on that machine or as an OTA update over the current one?
you installed the in opencore lilu and crypt.kext and do a full reinstall of ventura?Hello everybody
just gave it a try and tried to install Ventura b9 with OCLP 0.5.0 on my 2011 IMAC.
specs:
View attachment 2091024
before it comes to the GUI the screen gets dark and nothing happens afterwards. I did it onto a second internal ssd , so I can always switch back to Monterey. Is there any possibility to read a log file or something where I can get to know what's the issue. Ive seen a couple of working installations with the same iMac.
I use a USB Installer . so its a blank installation.
great news indeed, can't wait OCLP 0.5.0 release, hopefully soon. Thanks for all the devs whose involved.Just updated to beta 1o on my MacBook Air 2012. Used the latest OCLP 0.5.O and everything works fine, now there are no longer issues with power management, so o now CPU runs at full speed. What an amazing team, even a week ago they were not sure how would the power management be fixed.
yes full reinstall and the EFI structure is complete. Though there isn't any crypt.kext but a cryptexfixup.kext 😁. Just what OCLP v0.5.0 installed to the efi partition on the Ventura ssd. but because I can't complete the setup I can't run the OCLP Tool in Ventura. I am wondering what I missed 🤔.you installed the in opencore lilu and crypt.kext and do a full reinstall of ventura?