[pre-release] macOS Sonoma

[pico joe]

2 hours ago, Henry2010 said:

I can confirm that no OTA with just revpatch=sbvmm and SIP partly disabled when using iMac Pro 2017 SMBIOS.

Will change it to iMac 19,1 later.

 

EDIT

iMac19,1 now. But, oh my bad. Didn't switch the update channel from Public to Dev.

Will try again next time (or next week?) with the old iMac Pro 2017 SMBIOS.

no problem here with iMac Pro .. still get OTA (1.2 gb), 1. revert patch 2. boot-args: amfi 0x80 revpatch=sbvmm 3. secure boot: Disabled

[deeveedee]

As I mentioned before, I need to add these VMM kernel patches to my OC 0.9.4 config.plist in order to perform macOS installs (and now I discover I also need them for upgrades) on my hack (MBP6,2).  

• Reroute kern.hv_vmm_present patch (1)
• Reroute kern.hv_vmm_present patch (2) Legacy
• Reroute kern.hv_vmm_present patch (2) Ventura

These kernel patches are supposed to be replaced by RestrictEvents.kext 1.1.2 with NVRAM value revpatch=sbvmm.  

 

I am finding that even with RestrictEvents.kext 1.1.2 and revpatch=sbvmm, I still need the VMM kernel patches to install and upgrade macOS.  Without the kernel patches, my hack detects the OTA update and I can download the update, but the update's macOS Installer gets stuck in a boot-loop.  If I enable the kernel patches, the macOS installer isn't stuck in a boot-loop.

 

Is anyone else seeing this by any chance?

 

I have confirmed that RestrictEvents.kext 1.1.2 is loaded:
 

Spoiler

 

and NVRAM contains revpatch=sbvmm

Spoiler

 

Thanks in advance for any tips / advice.  My config.plist is attached.  I'm not sure that RestrictEvents.kext ever worked for me after I removed the VMM kernel patches.  Thank you.

config.plist.zip

Edited August 9, 2023 by deeveedee

[SavageAUS]

No problem on Dell laptop.
Downloaded full installer, installed, reapplied OCLP wifi and all good.


Sent from my iPhone using Tapatalk

[surenmunoo]

Beta 5 done and dusted but my Outlook is crashing, worked fine up until Beta 4, can anyone else confirm they are having issues with Microsoft Outlook?

 

[surenmunoo]

8 minutes ago, eSaF said:

It's working Ok for me Bro.

Strange that I am getting random crashes form it, maybe I will do a re-install. 

[Max.1974]

Hi guys, how are you doing? Hope fine!!!

 

im pass a few hours compiled my kexts, with Xcode 15 beta 6 (compatible with Xcode 14 on Sonoma). 

 

Im noticed that im using another revpatch on Nvram like print 

 

And follow my kexts if help somenone

 

New update without errors. 

 

iMacPro 1,1 SMBIOS not need change

 

I have important to said that come kexts im using with code signature folder included. 

 

 

Spoiler

 

 

 

.

 

 

For exemple

RestrictEvents 1.1.3  

 

 

 

Kexts zip 

 

Don't forget use your USB kext

 

 

Best Regards 

 

Kexts XCODE 15 Beta.zip

Edited August 9, 2023 by Max.1974

[Wayang-NT]

8 hours ago, cankiulascmnfye said:

For Intel Wifi users: I had to disable AirportItlwm-Sonoma-Preview04 kext in order to update to Sonoma beta 5. I've reverted to itlwm.kext + Heliport for the time being.

 

Beta 5 feels snappier to me overall than previous builds

AX210 work in beta5 with Airport-Sonoma-Preview05 ...

[cankiulascmnfye]

18 minutes ago, Wayang-NT said:

AX210 work in beta5 with Airport-Sonoma-Preview05 ...

 

Okay, cool. Yesterday Preview05 didnt exist… this kext has been up for half an hour only

[Stefanalmare]

5 hours ago, deeveedee said:

Without the kernel patches, my hack detects the OTA update and I can download the update, but the update's macOS Installer gets stuck in a boot-loop.  If I enable the kernel patches, the macOS installer isn't stuck in a boot-loop.

 

Is anyone else seeing this by any chance?

 

Me. On Ivy Bridge and lower.

 

2 hours ago, Max.1974 said:

Hi guys, how are you doing? Hope fine!!!

 

im pass a few hours compiled my kexts, with Xcode 15 beta 6 (compatible with Xcode 14 on Sonoma). 

 

Im noticed that im using another revpatch on Nvram like print 

 

And follow my kexts if help somenone

 

New update without errors. 

 

iMacPro 1,1 SMBIOS not need change

 

I have important to said that come kexts im using with code signature folder included. 

 

 

 

 

.

 

 

For exemple

RestrictEvents 1.1.3  

 

 

 

Kexts zip 

 

Don't forget use your USB kext

 

Best Regards 

 

 

 

 

 

 

 

 

 

Kexts XCODE 15 Beta.zip 4.36 MB · 4 downloads

 

It will be nice if you'll use "spoiler".

Edited August 9, 2023 by Stefanalmare

[Matgen84]

35 minutes ago, eSaF said:

I don't want to disrespect or upset my Bro but that post as helpful and informative as it is does take up a lot of real estate. 

 

In the window message, there is a spoiler function useful for pictures or long text as @Stefanalmare suggests. Then have a look to Reveal hiden content

Spoiler

 

Edited August 9, 2023 by Matgen84

[Meerkat]

Well, I had Sonoma working great on beta 4 even WiFi, one thing that wouldn't work was iMessage.. Then silly me decided to update to beta 5, got to my sign in page started loading then crashed and went back to the beginning. Tried everything but nada. So now back on Ventura.

[Stefanalmare]

18 minutes ago, Meerkat said:

Well, I had Sonoma working great on beta 4 even WiFi, one thing that wouldn't work was iMessage.. Then silly me decided to update to beta 5, got to my sign in page started loading then crashed and went back to the beginning. Tried everything but nada. So now back on Ventura.

 

I have running Ventura from about a year on z690 Aorus Master beautifully. Take a look at this config, maybe it can help you.

config.plist

[Matgen84]

12 hours ago, cankiulascmnfye said:

For Intel Wifi users: I had to disable AirportItlwm-Sonoma-Preview04 kext in order to update to Sonoma beta 5. I've reverted to itlwm.kext + Heliport for the time being.

 

Beta 5 feels snappier to me overall than previous builds

 

Hi @cankiulascmnfye Can you share the last itwlm 2.3.0 (version 2.2.0 don't work) + Heliport because I don't find them to update from Sonoma Beta 4 to Beta 5. Please

 

AirportItlwm-Sonomoma-Preview 05 is published but the kext works only on Beta5+

Edited August 9, 2023 by Matgen84

[Cyberdevs]

4 minutes ago, eSaF said:

@Cyberdevs Or anyone in the know - Hi I have a query, After getting the incremental update with the RE kext and the boot-arg Entry, do you remove the kext and boot-arg or do you leave them there? I tend to remove them. Just wondering if ok to leave them as is. Cheers.

I just leave them be for the next update. No need to remove them afiak

[cankiulascmnfye]

55 minutes ago, Matgen84 said:

 

Hi @cankiulascmnfye Can you share the last itwlm 2.3.0 (version 2.2.0 don't work) + Heliport because I don't find them to update from Sonoma Beta 4 to Beta 5. Please

 

AirportItlwm-Sonomoma-Preview 05 is published but the kext works only on Beta5+

 

I can't share my itlwn.kext because I build it from source  and it only contains the firmware for Intel AC-9560 (Firmware: iwm-9000-46)

 

Heliport can be downloaded from openintelwirelss: https://github.com/OpenIntelWireless/HeliPort

 

This issue contains all betas of AirportItlwm for Sonoma: https://github.com/OpenIntelWireless/itlwm/issues/883

Edited August 9, 2023 by cankiulascmnfye

[Matgen84]

20 minutes ago, cankiulascmnfye said:

 

I can't share my itlwn.kext because I build it from source  and it only contains the firmware for Intel AC-9560 (Firmware: iwm-9000-46)

 

Heliport can be downloaded from openintelwirelss: https://github.com/OpenIntelWireless/HeliPort

 

This issue contains all betas of AirportItlwm for Sonoma: https://github.com/OpenIntelWireless/itlwm/issues/883

 

I have also an Intel AC-9560 on my Gigabyte Aorus Master Z390. So can share itlwm.kext if you want.

[CloverLeaf]

I confirm Wi-Fi is working again with Airportitlwm-Sonoma-Preview05. Thank you so much!

 

@Matgen84 - If you want to use itlwm.kext you can just go with itlwm 2.20 stable. On my side it works fine with Beta 5 and Intel 9560NGW.

[Cyberdevs]

14 hours ago, cankiulascmnfye said:

I never revert root patches prior to updating. And I've been applying root patches on my Laptop eversince Monterey. Simply because the full installer is downloaded everytime on a system with applied root patches because this breaks the security seal of the volume. So updating/upgraiding  in this case completely reinstalls macOS as a whole anyway.

 

On a real Mac reverting the root patches makes the volume inside the container sealed again and as the results the incremental updates being presented instead of the full installer download.

you can check the the status of the volume before root patching which is sealed which changes to Sealed: Broken or No after applying the root patches and once again to Sealed: Yes after reverting the patches.

diskutil apfs list

will show you the changes as I described above. Once again his is on a genuine Mac, on hacks it might be a bit different because the seal is either set to Broken or No even after reverting the root patches which brings the RestrictEvents and the boot-arg in play.

 

P.S.

On my iMac15,1 (Late 2014) iMac the RestrictEvenets.kext is present but there's no need for revpatch=sbvmm

[deeveedee]

8 hours ago, Stefanalmare said:

Me. On Ivy Bridge and lower.

Thank you for confirming.  Do you know if this boot-loop problem is specific to hacks, or does it also happen on real Macs?  If it only happens on your hacks, would you mind posting a config.plist from one of your affected hacks?  Thanks!

 

I have started my own diagnosis of this issue here.

Edited August 9, 2023 by deeveedee

[Max.1974]

4 hours ago, eSaF said:

Eu não quero desrespeitar ou chatear meu irmão, mas esse post, tão útil e informativo quanto é, convém muito imobiliário.

 

@eSaF Thanks my friend!!!

 

Thanks too @Cyberdevs for ajust my post. I will learn how use spoiler  

 

5 hours ago, Stefanalmare said:

 

Eu. Na Ivy Bridge e abaixo.

 

 

Será bom se você usar "spoiler".

 

I have no idea how use them. But will try next post. Sorry  

Edited August 9, 2023 by Max.1974

[Max.1974]

4 hours ago, Meerkat said:

Well, I had Sonoma working great on beta 4 even WiFi, one thing that wouldn't work was iMessage.. Then silly me decided to update to beta 5, got to my sign in page started loading then crashed and went back to the beginning. Tried everything but nada. So now back on Ventura.

 

My iMessage works fine since 1th Sonoma beta. Probably is some config or kext. It works with intel wifi and Broadcom. Im not use OCLP. 

 

Maybe you need some help from @MaLd0n that is an expert in this tread. 

 

Spoiler

 

 

Spoiler

 

Edited August 9, 2023 by Max.1974

[cankiulascmnfye]

@Cyberdevs Interesting. I will test this on my hack before the next update and see if incremental updates will be available then. This would reduuce the update time a lot.

Edited August 9, 2023 by cankiulascmnfye

[cankiulascmnfye]

@Matgen84

 

itlwm.kext.zip

[mnfesq]

On 8/2/2023 at 7:41 AM, deeveedee said:

@mnfesq I'm glad there was one other person (besides me) who found value in my ACPI patching technique. 😂   I have found that the PXSX->ARPT rename is not necessary and only the device parameter spoofing is required for OCLP to detect BCM 94352 as a patchable Wi-Fi.

 

My update to beta 5 went very smoothly and without incident until I had to reapply the OLCP patches.  Every change I needed to make to patch wifi originally needed to be restored including (1) restoring the spoof in my DSDT to make my 4352 wifi card appear as a 4360 card; (2) the PSXS->ARPT SSDT, (3) the spoof patch to ACPI to make my wifi card appear to OLCP as 4353 in config.plist; and (4) change csr-active-config to 03080000.  

 

Given the frequency that I update Sonoma, I will just keep those changes on a permanent basis except the csr-active-config, because I need SIP disabled to run some of the software I like.

[deeveedee]

@mnfesq If you post your EFI, I'd be happy to take a look.  Once the Wi-FI patch is properly applied, it should never need to be removed and should not interfere with normal Wi-Fi operation. Happy to help if you want the help.

 

EDIT: the Wi-Fi ACPI patch shouldn't need to rename WiFi to ARPT and shouldn't interfere with the true identity of your Wi-Fi as recognized by macOS (e.g., no need for macOS to think your 4352 is a 4360).

Edited August 9, 2023 by deeveedee