Guest 5T33Z0 Posted August 31, 2021 Share Posted August 31, 2021 I also didn't get the update notification yet. But I also don't believe that this issue is SIP-related. Because no matter which csr-active-config you are using, you can override these settings from the Bootloader and re-enable SIP temporarily. I believe it's probably just a result of a stepped roll-out of macOS based on Location/Continent and/or mac model or whatever. Link to comment Share on other sites More sharing options...
AudioGod Posted August 31, 2021 Share Posted August 31, 2021 (edited) For anybody that’s not seeing the beta6 update using smbios 1,1 or 7,1 and probably anything else, What you need todo is go into the Config.plist and set the SecureBootModel to j160 restart and the update will show up and then disable the SecureBootModel while it’s downloading and let the system do its thing. This is the only method that seems to work so far. Edited August 31, 2021 by AudioGod 6 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 31, 2021 Share Posted August 31, 2021 7 hours ago, antuneddu said: Set according to Dortania csr-active-config>data>00000000 SIP completely enabled (0x0). https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/post-issues.html#disabling-sip Mine is permanent like this. I have nothing outside of EFI / OC so I don't need to disable it also do an NVRAM reset afterwards 🤞 I changed my csr-active-config>data>00000000, and enabled SIP, and no update... But @Hervé clarified the reason of the update no show... Thanks Link to comment Share on other sites More sharing options...
AudioGod Posted August 31, 2021 Share Posted August 31, 2021 @MorenoAv Try what I laid out in my last post brother. 1 Link to comment Share on other sites More sharing options...
Shaneee Posted August 31, 2021 Share Posted August 31, 2021 All is well on AMD Spoiler 3 1 Link to comment Share on other sites More sharing options...
Anto65 Posted August 31, 2021 Share Posted August 31, 2021 12 minutes ago, MorenoAv said: I changed my csr-active-config>data>00000000, and enabled SIP, and no update... But @Hervé clarified the reason of the update no show... Thanks Then try to set in securebootmodel a value that suits your smbios as mentioned by @AudioGod Link to comment Share on other sites More sharing options...
AudioGod Posted August 31, 2021 Share Posted August 31, 2021 Just now, antuneddu said: Then try to set in securebootmodel a value that suits your smbios as mentioned by @AudioGod Word of warning, if you're using j137 and 1,1 that won’t work. For some reason it needs to be j160 or bust. That could of just been on the two systems I tried it on but that’s what it looks like to me so far anyway. More people and more tests might expand on that though so it’s only via my bird eye and not set in stone.. 3 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 31, 2021 Share Posted August 31, 2021 I tried your suggestion @AudioGod, and it don't work I have SMBIOS 7,1 and j106... update no show... I forgot to mention if we change the value for secure boot it don't work with Any in DMGLoading, I had to boot with my usb installer and change that... Thanks anyway... Link to comment Share on other sites More sharing options...
AudioGod Posted August 31, 2021 Share Posted August 31, 2021 (edited) 1 minute ago, MorenoAv said: I tried your suggestion @AudioGod, and it don't work I have SMBIOS 7,1 and j106... update no show... I forgot to mention if we change the value for secure boot it don't work with Any in DMGLoading, I had to boot with my usb installer and change that... Thanks anyway... j160 not j106, Restart and reset your nvram. Edited August 31, 2021 by AudioGod 1 Link to comment Share on other sites More sharing options...
bisdak4920 Posted August 31, 2021 Share Posted August 31, 2021 @Audio God, thanks it works. 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 31, 2021 Share Posted August 31, 2021 (edited) Ups my bad I changed it im my config.plist to j160 and not j106, I write it wrong... Sorry... Be right back, reboot and rest NVRAM... Edited August 31, 2021 by MorenoAv Link to comment Share on other sites More sharing options...
eSaF Posted August 31, 2021 Share Posted August 31, 2021 @AudioGod - That is an interesting find B. This is my SecureBootModel setting (as shown in the attached) and the update showed up automatically, just to add, I am now using Mac Model 19.1 with both internal and dedicated GPU. Don't know how much or if that makes a difference to anything. Spoiler 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 31, 2021 Share Posted August 31, 2021 It works @AudioGod, Thanks 3 Link to comment Share on other sites More sharing options...
Anto65 Posted August 31, 2021 Share Posted August 31, 2021 Well solved this too thanks to @AudioGod Her the values that can be set as SecureBootModel https://dortania.github.io/OpenCore-Post-Install/universal/security/applesecureboot.html#securebootmodel 4 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 31, 2021 Share Posted August 31, 2021 I doubt that the issue is related to SecureBootModel. As you can see: SIP is enabled, SecureBootModel is enabled. Still no notification. And this installation is from yesterday, fresh on a brand new NVME. Link to comment Share on other sites More sharing options...
eSaF Posted August 31, 2021 Share Posted August 31, 2021 (edited) @5T33Z0 - I maybe mistaken but I understood the post as such - 'For anybody that’s not seeing the beta6 update using smbios 1,1 or 7,1 and probably anything else'. The tip by @AudioGod seems to be working for quite a few members. Edited August 31, 2021 by eSaF Link to comment Share on other sites More sharing options...
dehjomz Posted August 31, 2021 Share Posted August 31, 2021 (edited) Good find by @AudioGod to temporarily change the security model to j160 for Beta 6 to download. I wonder if this is a bug (or "feature") on the Macintosh side or on the Opencore side? Edited August 31, 2021 by dehjomz 1 Link to comment Share on other sites More sharing options...
Guest 5T33Z0 Posted August 31, 2021 Share Posted August 31, 2021 2 minutes ago, eSaF said: @5T33Z0 - I maybe mistaken but I understood the post as such - 'For anybody that’s not seeing the beta6 update using smbios 1,1 or 7,1 and probably anything else'. The reactions make it look like adding SecureBootModel (if it exists) to the corresponding SMBIOS would resolve thes issue – it doesn't. Link to comment Share on other sites More sharing options...
eSaF Posted August 31, 2021 Share Posted August 31, 2021 (edited) Ok Bro - So all those that tried the tip and got the desired result was just a fluke???!!! - Well ok then no worries. Not disregarding your statement but strange things happens with Betas (not following what we generally expect) on non Apple Machines. Edited August 31, 2021 by eSaF 1 Link to comment Share on other sites More sharing options...
AudioGod Posted August 31, 2021 Share Posted August 31, 2021 24 minutes ago, 5T33Z0 said: The reactions make it look like adding SecureBootModel (if it exists) to the corresponding SMBIOS would resolve thes issue – it doesn't. That’s why it works for everybody. 🤣 2 Link to comment Share on other sites More sharing options...
Shaneee Posted August 31, 2021 Share Posted August 31, 2021 1 hour ago, 5T33Z0 said: I doubt that the issue is related to SecureBootModel. As you can see: SIP is enabled, SecureBootModel is enabled. Still no notification. And this installation is from yesterday, fresh on a brand new NVME. Spoiler Your SecureBootModel is j185f. Set it to j160 and reboot and you'll get the update notification. While it's downloading set it back to j185f. Simple as that. 3 Link to comment Share on other sites More sharing options...
MorenoAv Posted August 31, 2021 Share Posted August 31, 2021 Well I have a situation that is a first for me... Right now I wanted to remove -v in my config.plist and I'm confronted with the EFI>APPLE>UPDATER>MULTIUPDATER> a bunch of files, and my OC is gone... anyone knows why this happened? Thanks 1 Link to comment Share on other sites More sharing options...
Partime Posted August 31, 2021 Share Posted August 31, 2021 2 hours ago, AudioGod said: Word of warning, if you're using j137 and 1,1 that won’t work. For some reason it needs to be j160 or bust. That could of just been on the two systems I tried it on but that’s what it looks like to me so far anyway. More people and more tests might expand on that though so it’s only via my bird eye and not set in stone.. j160 worked like a charm. thanks! 2 1 Link to comment Share on other sites More sharing options...
eSaF Posted August 31, 2021 Share Posted August 31, 2021 @5T33Z0 - After following @Shaneee advice please let us know if it worked out for you. Link to comment Share on other sites More sharing options...
SavageAUS Posted August 31, 2021 Share Posted August 31, 2021 Has the update been pulled? Link to comment Share on other sites More sharing options...
Recommended Posts