Jump to content
58 posts in this topic

Recommended Posts

@eSaF https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/CHANGELOG.md

 

I think you're a few commits behind They had continued until 1.5 went back... latest commit bbc8902 now 1.3 🤷

 

https://github.com/dortania/OpenCore-Legacy-Patcher/actions/runs/8326849351

 

But you made me doubt...I'll check 😂

Edited by Antonuccio
  • Like 4

 

image.png.30df887144e7d3003b21fbd0528150ff.png

OTA Update works but tested with Restrict Events compiled by Lorys and Compiled normally, both kexts not works, until im disable IntelBTpatcher and IntelBluetoothFixup  WI-FI 6 Card AX 210 on Lenovo 

 

 

Thanks my friends!! 

 

 

Edited by Max.1974
  • Like 4

Last login: Tue Mar 26 07:18:14 on ttys001
(base) pico@Picos-iMac-Pro ~ % sw_vers
ProductName:        macOS
ProductVersion:        14.4.1
BuildVersion:        23E224
(base) pico@Picos-iMac-Pro ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-100-2024-03-12
(base) pico@Picos-iMac-Pro ~ %

  • Like 3

Well, thanks to @Antonuccio, I was able to install 14.4.1.  Until I read his post, it was not working (failed at the "preparing to install" stage several times).  I disabled wifi and bluetooth and then it installed.  SBM is currently disabled.

 

However, I can say that this version of macOS is not very good.  Deleting and copying files via the GUI is a nightmare - they just don't complete.  I've had to resort to cp -R.  And even on my M1 Macbook, one time, shortly after the final reboot, the login screen came up in a foreign language (my native tongue is english).  Then on that machine, all my photos were all screwed up.

 

I've become more and more familiar with Activity Monitor as tasks seem to hang often.

 

And, just now, I've had a Finder hang (only recourse is a finder restart, but even then that doesn't always work and this time, I had to cold reboot).

 

 

Edited by meg2014
  • Like 3
  • Sad 1

Posted my 14.4.1 status here.  Not using OCLP or itlwm.  Needed to set SecureBootModel = Disabled for the 14.4 -> 14.4.1 upgrade.  Restored SecureBootModel=Default after upgrade complete.  Upgrade with no issues.

5 hours ago, deeveedee said:

Posted my 14.4.1 status here.  Not using OCLP or itlwm.  Needed to set SecureBootModel = Disabled for the 14.4 -> 14.4.1 upgrade.  Restored SecureBootModel=Default after upgrade complete.  Upgrade with no issues.

Why do you set Default? Because Acidanthera said the nonsense two years ago?

  • Like 2
4 hours ago, Slice said:

Why do you set Default? Because Acidanthera said the nonsense two years ago?

Please enlighten me.

 

1 hour ago, eSaF said:

I agree

Ok.  Maybe you can enlighten me, too.

@eSaF My car still starts if I don't use my seatbelts.  I don't get why people use their seatbelts.

 

EDIT: Ok, that was a snarky reply.  Sorry.  macOS incremental updates are only broken if you have OCLP post-install patches applied.  You should have seen over at MacRumors that users are keeping SecureBootModel=Disabled and SIP partially disabled just like you.  If you revert OCLP post-install patches while keeping SIP partially disabled and SBM=Disabled, incremental updates still work on many Macs (and hacks).  That is well known.

 

I'm trying to encourage the conversation away from "it works, so it must be ok" to "what are the security implications of setting SecureBootModel=Disabled vs. Default"?

Edited by deeveedee
7 minutes ago, eSaF said:

Yes so does mine apart from the annoying beep that gets louder and louder until it is remedied (Lexus eh!!!)

But I will leave it there with your analogy of satisfaction.

Cheers. :angel:

We were typing at the same time. Please see my previous post.

  • Like 1

Hi @deeveedee let me ask you, im not use OCLP, and now both RE works, normal kext and Lorys89 kext. 

 

So im use SIP 0xA87 (is recommend by Slice) and in Clover im not find  SBM (SecureBootModel) (sorry if I miss something). 

 

So SIP need activated to receive Updates? Im disable my Intel BT kext and works fine. After that im just enable again. Works with SIP partially 

 

Thanks. 

@Max.1974 I set SIP and SecureBootModel based on my security preferences, not because they are needed or not needed for macOS updates.  If you are satisfied with your partially disabled SIP, then you don't need to change anything.

 

As far as I know, CLOVER does not offer a way to configure SecureBootModel.  SecureBootModel is an OpenCore attribute.  Someone please correct me if I am wrong.

 

EDIT:  For more information about SIP, read this.  For more information about SecureBootModel, read this.

Edited by deeveedee
  • Like 3
  • Thanks 1
×
×
  • Create New...