[pre-release] macOS Tahoe

[Moviemakergr]

1 hour ago, fantomas said:

@Moviemakergr

Terminal command
 

 

 

Just fixit with enroll betas 

Thanks again.

 

 

 

Spoiler

 

Done

WG not needed for HDMI out

No neeed to reinstall AppleHDA

Runing cool

 

Spoiler

Edited August 6, 2025 by Moviemakergr

[miliuco]

@webipsum

New MA success. I think that it's the 5 try since Tahoe beta 1.

I do nothing special.

MacPro7,1 so no WhateverGreen, OC 1.0.5. Same EFI for Ventura to Tahoe (max and min kernel settings).

[Ludox]

InstallAssistant.pkg beta 5 Tahoe?

[webipsum]

27 minutes ago, miliuco said:

@webipsum

New MA success. I think that it's the 5 try since Tahoe beta 1.

I do nothing special.

MacPro7,1 so no WhateverGreen, OC 1.0.5. Same EFI for Ventura to Tahoe (max and min kernel settings).

You have superpowers!
As soon as I download Beta 5 directly, I'll test it.
Did you do a clean install of Beta 5 or was it an upgrade (from Beta 4)?

[fantomas]

53 minutes ago, Ludox said:

InstallAssistant.pkg beta 5 Tahoe?

 

You can check it from the Catalog URL
https://swscan.apple.com/content/catalogs/others/index-26seed-26-15-14-13-12-10.16-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

Touch Win+F to open researching and write macOS26

Actually, it shows the Beta 4 full installer (2025-07-22)

 

Spoiler

<key>URL</key>
                        <string>https://swcdn.apple.com/content/downloads/05/26/082-89906-A_7DP8EBEVZJ/g3p7sya93v36h1ri0h940xxuxutt23igcw/InstallAssistant.pkg</string>
                        <key>IntegrityDataSize</key>
                        <integer>59756</integer>
                    </dict>
                    <dict>
                        <key>Size</key>
                        <integer>1303377</integer>
                        <key>IntegrityDataURL</key>
                        <string>https://swcdn.apple.com/content/downloads/05/26/082-89906-A_7DP8EBEVZJ/g3p7sya93v36h1ri0h940xxuxutt23igcw/com_apple_MobileAsset_MacSoftwareUpdate.plist.integrityDataV1</string>
                        <key>URL</key>
                        <string>https://swcdn.apple.com/content/downloads/05/26/082-89906-A_7DP8EBEVZJ/g3p7sya93v36h1ri0h940xxuxutt23igcw/com_apple_MobileAsset_MacSoftwareUpdate.plist</string>
                        <key>IntegrityDataSize</key>
                        <integer>104</integer>
                    </dict>
                </array>
                <key>ExtendedMetaInfo</key>
                <dict>
                    <key>InstallAssistantPackageIdentifiers</key>
                    <dict>
                        <key>MobileAssetUpdateBundlePlist</key>
                        <string>com.apple.plist.MobileAsset.MacSoftwareUpdate</string>
                        <key>SharedSupport</key>
                        <string>com.apple.pkg.InstallAssistant.Seed.macOS26Seed</string>
                        <key>InstallInfo</key>
                        <string>com.apple.plist.InstallInfo</string>
                        <key>UpdateBrain</key>
                        <string>com.apple.zip.UpdateBrain</string>
                    </dict>
                </dict>
                <key>PostDate</key>
                <date>2025-07-22T17:29:12Z</date>
                <key>Distributions</key>
                <dict>

 

 

[miliuco]

2 hours ago, webipsum said:

Did you do a clean install of Beta 5 or was it an upgrade (from Beta 4)?

 

Clean install. Previous attempts were updates.

[AlfredoM]

Here fullVersion 26 Beta5:

https://swcdn.apple.com/conten…28oo/InstallAssistant.pkg

[deeveedee]

Beta 4 -> Beta 5 update completed without issues on my 2010 HackBookPro6,2.  I applied the update via OTA which downloaded the full 16.7GB installer.  After the upgrade, I needed to decrypt the TahoeBeta volume by following the steps here (because the upgrade was applied with the full installer).   Performance without OCLP post-install non-metal graphics patches is barely good enough to capture an "About This Mac" screenshot.

[fantomas]

Just a reminder for people that have a bluetooth hardware with BCM_4350C2 chip that this is still working fine on macOS 26 (beta 5 here) as well. 

[meg2014]

10 minutes ago, fantomas said:

Just a reminder for people that have a bluetooth hardware with BCM_4350C2 chip that this is still working fine on macOS 26 (beta 5 here) as well. 

 

I know, I have one in my Tahoe rig and it works great!

[bestal]

Friends, the ota update from beta 4 to beta 5 shows 3.22 gb it downloads but gives an error during the installation. There is no oclp mod, no kdk, I did a clean installation, why is it not installing?

Edited August 7, 2025 by bestal

[surenmunoo]

@Anto65 For some reason, I cannot enter my password to get this app going. Other apps allow me to enter my password but not this one. I can edit the username but password takes nothing. 

 

[Anto65]

Umm, it's strange, I don't know how much the app has to do with the system password.
I have Gatekeeper disabled... I haven't had any problems.

[Anto65]

In fact, there is no Beta 5 anywhere,
Full Downloader, OCLP, Gibmacos, Mr Macintosh...

 

Spoiler

 

Edited August 7, 2025 by Anto65

[arsradu]

6 hours ago, surenmunoo said:

@Anto65 For some reason, I cannot enter my password to get this app going. Other apps allow me to enter my password but not this one. I can edit the username but password takes nothing. 

 

It's a bug. Try to close some of the apps in the background, move the prompt over the desktop, not over other windows. This is an old bug. I'm surprised Apple hasn't fixed it yet. I had it too. It works, but again, you need to fiddle around with the windows. Weird enough, the username field doesn't have this issue. Only the password field.

Also, in case you have numbers in your password, try both the dedicated keypad (for full-size-keyboards) and the number row on top of the letters. For some reason, the dedicated keypad didn't work, but it could be just my setup.

Edited August 7, 2025 by arsradu

[arsradu]

9 hours ago, fantomas said:

Just a reminder for people that have a bluetooth hardware with BCM_4350C2 chip that this is still working fine on macOS 26 (beta 5 here) as well. 

 

Is this necessary to have Mic working on BT headphones? Does yours work...? The BT itself seems to be working, only the Mic is not working.

[arsradu]

15 hours ago, maly70 said:

Hi mates, any link for Tahoe Beta 5,  I am not getting any updates from beta4 even tho I have restrictEvent kext 1.6 and revpatch=sbvmm argument

You could also try to remove root-patches, in case you're using OCLP or OCLP-Mod. See if that helps.

[Gradou]

Did you have WEG permanently disabled for this ß5?

[nmano]

I try to Spoof Alder Lake to Raptor Lake.

DefinitionBlock ("", "SSDT", 2, "ACDT", "RPLGFX", 0x00000000)
{
    External (_SB_.PC00.GFX0, DeviceObj)  // Adjust path if different in your DSDT

    Scope (_SB.PC00.GFX0)  // Ensure this matches your ACPI path
    {
        Method (_DSM, 4, NotSerialized)
        {
            If (!Arg2) { Return (Buffer() { 0x03 } ) }
            Return (Package()
            {
                // Spoof Alder Lake (required for macOS)
                "device-id", Buffer() { 0x68, 0x9A, 0x00, 0x00 }, // 0x9A680000 (Alder Lake-S)
                
                // Platform ID (Desktop RPL)
                "AAPL,ig-platform-id", Buffer() { 0x07, 0x00, 0x9B, 0x3E }, // 07009B3E
                
                // Enable Metal & HDMI 2.0
                "enable-metal", Buffer() { 0x01, 0x00, 0x00, 0x00 },
                "enable-hdmi20", Buffer() { 0x01, 0x00, 0x00, 0x00 },
                
                // Framebuffer patches
                "framebuffer-patch-enable", Buffer() { 0x01, 0x00, 0x00, 0x00 },
                "framebuffer-stolenmem", Buffer() { 0x30, 0x01, 0x00, 0x00 }, // 19MB (0x130)
                "framebuffer-fbmem", Buffer() { 0x40, 0x00, 0x00, 0x00 },     // 4MB (0x40)
                
                // Optional: Model name (for cosmetic purposes)
                "model", Buffer() { "Intel UHD Graphics 770" },
            })
        }
    }
}

 

SSDT-IGPU.aml

[arsradu]

1 hour ago, Gradou said:

Did you have WEG permanently disabled for this ß5?

No. Just disabled for the installation, and for the last step, when it's booting again to black screen (or as in my case, bootlooping), re-enabled it and I was able to boot ok after that.

 

As I said before, this sounds like an issue with AGPM. Which is why I recommended AGPMInjector app, which creates an AGPMInjector.kext, tailored for your SMBIOS and Video card, to add to your OC folder, and config.

 

I already created mine, but I can't test it right now. So, I guess we'll see with the next update if it makes a difference or not.

 

In the meantime, my recommendation would be to disable WEG for the installation, and re-enable it on the last step (you'll know when that is, because you won't be able to boot, or you'll boot to black screen).

Edited August 7, 2025 by arsradu

[arsradu]

36 minutes ago, eSaF said:

With the created kext, do you run it with WEG.kext enabled or disabled?

Also when done if successful, do you then discard the kext and then use WEG.kext on it's own or continue with both?

 

I would try both with it enabled, and disabled, and compare the results. For our current setups, I think we would be able to boot no problem with only the AGPMInjector kext, and WEG disabled. But again, it needs to be tested.

Also, it is a permanent thing, as long as the SMBIOS we're using requires that AGPM patch. Not all of them do. Some older ones don't but with those, you can't boot Tahoe, since it's not supported. So...only with some param in the config, to skip this check, it might work. I haven't tried this scenario.

And with newer ones, they are supported, but you also get AGPM. But in general, as long as the SMBIOS is one of those in the list, and the card is one of those in the list, yeah, most likely you're gonna need the kext for both installation (which is what we're trying to confirm), and regular boots.

 

EDIT: have a backup at hand, or a way to re-enable WEG if needed. I tried to boot with only AGPMInjector and...I can't. So, either the kext needs an update to work on Tahoe, or...it's not the right fix for this issue.

Edited August 7, 2025 by arsradu

[webipsum]

8 hours ago, eSaF said:

Bro are you sure??!!

  Reveal hidden contents

 

It's Beta 4: Version 26.0 (25A5316i)

EDIT:
Anyway, I tried using Migration Assistant again. It didn't work!
Message to @miliuco:
Those born to be Robin (webipsum) never become Batman ( @miliuco ) 
OMG!

Edited August 7, 2025 by webipsum
Batman and Robin.

[arsradu]

26 minutes ago, eSaF said:

@arsradu Hi I only ask as doing Tahoe clean installs I have to start the install with the SmBIOS Mac Model 7,1 and then switch over which is a little tedious.

If this kext can allow me to use my normal iMac20,20 model then that would be a good thing for me.

 

I will test if/when Beta 5 is offered as a stand alone installation file or maybe the next update.

Thanks for the reply.

 

I tried it myself, with iMac20,1 SMBIOS, for regular boot, and...doesn't seem to work without WEG. It doesn't cause any issues if it's with it, but it doesn't seem to fix the issue of booting to black screen, if it's by itself. So...either it's not updated, or...not the right patch for this issue.

 

The idea here would be to be able to install Tahoe and boot it with the same SMBIOS. Now, of course, you can't have both SMBIOSes added to the same IGPMInjector kext (or at least I don't think it would work this way). So...if 20,2 is ok for you, then I think that's the one you should stick with. Although...I think I had better results, in terms of booting, with MacPro7,1. I'll have to test a little more.

 

By the way, here's the official topic for this app, in case you want to ask something.

 

EDIT: I think the confusion is on my side. So there are two problems. AGDP (Apple Graphics Device Policy) is handled by WEG and it's the problem that makes us boot to black screen. AGPM (Apple Graphics Power Management) is also related to graphics, but refers to power consumption and fans. So, not what we need for this case. I mean, it can be used together with WEG, but it's not what we need to fix the black screen. So, sorry, my bad.

Edited August 7, 2025 by arsradu

[Derty]

Ok, I had the FileVault problem. I left it enabled during the update to beta 5, and it wasn't recognizing my password. MaLdOn posted the solution here: filevault-problems-on-macos-tahoe-hackintosh, in his forum. Thanks, MaLdOn.

 

I leave the file in the EFI folder; just disable EnableJumpstart and enable apfs_aligned.efi.

 

Another thing, instead of fussing with WhateverGreen.kext, before starting the update, I disable it and leave NootRX.kext enabled, which works decently and simplifies the update.

 

EFI-Z690 Aorus.zip

[AlfredoM]

The update from beta 4 to beta 5 went smoothly on my late 2013 iMac, except for the unsupported Nvidia Kepler graphics.

 

Regarding Apple's now completely boring idea of changing the Mac OS drive logo, all I can say is,

who uses that original, ugly, silly icon? I've always created my own icon for each macOS,

just like Apple, using the amateurish tool "Image2Icon."

 

Here's my icon forTahoe:

 

Now I realize that ONLY the installation went well, but nothing more!!

I've always had a problem, even with beta 4 and beta 5, with a process called "iconserviceagent" (see photo).

After about 5 minutes, this process calms down, so you can then work with the beta again.

I can't restore the sound with the AppleHD.kext.
"SimpeLoader" no longer works, nor does "MyKextInstaller" (always the latest versions).

Apple has again broken everything that still works in beta 3 and Beta4. At least, it does on my late 2013 iMac.
I don't know how it works on your Hackintosh.

 

 

Edited August 7, 2025 by AlfredoM