Jump to content

[pre-release] macOS Tahoe

fantomas

By fantomas,
in New Releases and Updates

 Share
3741 posts in this topic

Recommended Posts

webipsum
webipsum
Posted
Posted (edited)
2 hours ago, crazybirdy said:

26.0 Beta 25A5346a, done.

 

26.png.fa14c4f4d3213adb69dc9000f783fbb4.png


@crazybirdy
Tip: Just click on the serial number and it will disappear, then you can take a screenshot and you won't have to delete it.

EDIT:
@surenmunoo already posted the link for you.
https://github.com/2009-Nissan-Cube/About-This-Hack

 

Edited by webipsum
  • Like 3
deeveedee
deeveedee
Posted
Posted

@Thebes Knossos I use Booter Patch "Skip Board ID Check" only because it's what the OCLP Developers use, but your response and @LockDown's previous suggestion to use -no_compat_check (which I always used before OCLP) inspired me to research this again.  According to ChatGPT, -no_compat_check boot-arg is the recommended approach.  I'll continue to use "Skip Board ID Check" because I'm too lazy to change, but I thought this was interesting:

 

From ChatGPT...

Both methods [-no_compat_check and Skip Board ID Check] achieve the same goal (bypassing Apple’s hardware checks), but they work differently:

1. Booter Patch → Skip Board ID Check

  • An OpenCore binary patch that disables the Board ID verification in the booter.

  • Works by modifying macOS internals directly.

  • Less future-proof since Apple updates can break patches.

  • Adds complexity to your OpenCore config.

2. boot-arg → -no_compat_check

  • An Apple-provided boot argument that tells macOS to skip compatibility checks.

  • Official, supported, and much cleaner.

  • Easier to maintain across updates.

  • Safer and more future-proof than using a booter patch.

✅ Recommendation:
Use -no_compat_check instead of the Booter Patch Skip Board ID check. It is cleaner, safer, and far more likely to continue working after macOS updates. Only use the booter patch if you encounter a rare case where -no_compat_check does not work.

  • Like 5
miliuco
miliuco
Posted
Posted (edited)

@webipsum

Sorry to say but yesterday night I did MA again and it worked again. 
Believe me I'm not doing anything different to follow on screen instructions. 
It was on a sealed disk. Did you read @deeveedee post about this?

 

Edited by miliuco
Typo
  • Like 3
webipsum
webipsum
Posted
Posted (edited)
3 hours ago, miliuco said:

@webipsum

Sorry to say but yesterday night I did MA again and it worked again. 
Believe me I'm not doing anything different to follow on screen instructions. 
It was on a sealed disk. Did you read @deeveedee post about this?

 

 

On 8/18/2025 at 11:00 PM, deeveedee said:

I haven't used migration assistant for a while (OTA works fine for me), but for those that are attempting to use MA, the destination volume (the volume to which you are migrating) should have a sealed snapshot.  That means no OCLP (or similar) patches on the destination volume.  Either use MA before applying patches or revert patches, MA and then restore patches.

 

Yes. And I did as deeveedee explained. I also had no success.
It's very strange.
1) Clean install - macOS Tahoe Beta ♾️,
2) Running Migration Assistant right at the beginning of setup or even after the installation is complete,
3) Time Machine backup or macOS Tahoe installed on an external SSD. Both unpatched.
4) It keeps looping.

Thanks for the information, @miliuco and @deeveedee!

Note: I'll only continue testing until Beta 999 before the Final Release! :thumbsup_anim:

 

Edited by webipsum
  • Like 2
  • Confused 1
webipsum
webipsum
Posted
Posted
On 8/19/2025 at 8:14 AM, webipsum said:


A problem that's been occurring here since Beta 5:
Sometimes when I turn on or restart my Hackintosh and try to boot into macOS Tahoe using OC 1.0.5, the boot process continues without opening macOS Tahoe (only those verbose lines are displayed), and then stops after a while.
If I restart it again, it normally loads into macOS Tahoe (currently Beta 7).
Any tips? Tks!

 

EDIT:
This happens very rarely. Most of the time it goes in normally.

 


Please, is this occurrence I quoted above happening with anyone's Hackintosh?

asdesoso
asdesoso
Posted
Posted
On 8/19/2025 at 2:05 PM, asdesoso said:

Hi,
I am be able to install Tahoe on a Haswell desktop rig, but MB/KB doesn´t work, I investigated a lot, and requires patch USB Map, at Sequoia from Big Sur with OC, I don´t need to to anything, just put my EFI, upgrade every year, from Big Sur to Sequoia, and all works, but Apple with Tahoe changed the using of USB ports.
Can anyone helps me?
If anyone has the patched kext for Haswell desktop I appreciated to post it.
Thanks in advance.

Cheers.

From other hand, I also be able to install it on my HP EliteBook 2570P, and it works USB MB and internal trackpad/keyboard, also BT and ACPI, but nothing more, no WiFi, no Ethernet, no HD 4000, no audio, can anyone help me with that?
Thank you.

Please anyone can help me?

naiclub
naiclub
Posted
Posted (edited)

Hello.

I've identified the cause of the inexplicable restart issue.
From beta 2 to beta 7, it's been happening consistently. It's caused by a crash in AppleIGC.kext, which then causes a panic. It restarts before the crash is noticed.

I've already notified the manufacturer of AppleIGC.kext.

I'm currently using Intel(R) Wi-Fi 6E AX211 160MHz instead.

.2025-08-21-040101.kernel.core.log

Edited by naiclub
  • Like 2
  • Thanks 1
Renard45
Renard45
Posted
Posted (edited)

someone has mac os slow startup with kexts intel wifi/Bluetooth?

now just finished install Tahoe public beta 3 but after boot i have a black screen with mouse cursor and stuck at this step.

my graphic card is a nvidia GT 720 (i know i need to replace with a AMD soon) but can i have tahoe working yet?

Edited by Renard45
surenmunoo
surenmunoo
Posted
Posted
1 hour ago, Renard45 said:

someone has mac os slow startup with kexts intel wifi/Bluetooth?

now just finished install Tahoe public beta 3 but after boot i have a black screen with mouse cursor and stuck at this step.

my graphic card is a nvidia GT 720 (i know i need to replace with a AMD soon) but can i have tahoe working yet?

If i am correct, there is no drivers for the GT720 in Tahoe at all. 

  • Like 1
deeveedee
deeveedee
Posted
Posted (edited)

@Renard45 The only way to use an NVidia GT 720 (or any NVidia card that was once supported by macOS) is to patch newer versions of macOS with Open Core Legacy Patcher (OCLP).  OCLP is not yet available for macOS Tahoe at the time of this post.  Have you tested your video card in macOS Sequoia with OCLP 2.4.0?  If you have questions about OCLP, post them in this thread.

Edited by deeveedee
  • Like 3
Renard45
Renard45
Posted
Posted (edited)
25 minutes ago, deeveedee said:

@Renard45 The only way to use an NVidia GT 720 (or any NVidia card that was once supported by macOS) is to patch newer versions of macOS with Open Core Legacy Patcher (OCLP).  OCLP is not yet available for macOS Tahoe at the time of this post.  Have you tested your video card in macOS Sequoia with OCLP 2.4.0?  If you have questions about OCLP, post them in this thread.

yes i have another SSD with sequoia 15.6 and works very well with OCLP patch but on Tahoe beta i can not have the finish setup install (install was ok but finish setup not)

43 minutes ago, surenmunoo said:

If i am correct, there is no drivers for the GT720 in Tahoe at all. 

ok thank you

Edited by Renard45
Renard45
Renard45
Posted
Posted (edited)
19 hours ago, deeveedee said:

@Thebes Knossos I use Booter Patch "Skip Board ID Check" only because it's what the OCLP Developers use, but your response and @LockDown's previous suggestion to use -no_compat_check (which I always used before OCLP) inspired me to research this again.  According to ChatGPT, -no_compat_check boot-arg is the recommended approach.  I'll continue to use "Skip Board ID Check" because I'm too lazy to change, but I thought this was interesting:

 

From ChatGPT...

 

Both methods [-no_compat_check and Skip Board ID Check] achieve the same goal (bypassing Apple’s hardware checks), but they work differently:

1. Booter Patch → Skip Board ID Check

  • An OpenCore binary patch that disables the Board ID verification in the booter.

  • Works by modifying macOS internals directly.

  • Less future-proof since Apple updates can break patches.

  • Adds complexity to your OpenCore config.

2. boot-arg → -no_compat_check

  • An Apple-provided boot argument that tells macOS to skip compatibility checks.

  • Official, supported, and much cleaner.

  • Easier to maintain across updates.

  • Safer and more future-proof than using a booter patch.

✅ Recommendation:
Use -no_compat_check instead of the Booter Patch Skip Board ID check. It is cleaner, safer, and far more likely to continue working after macOS updates. Only use the booter patch if you encounter a rare case where -no_compat_check does not work.

Sequoia 15.6.1  has been released with the two methods I still have to download the full installer and not only the 15.6.1 update I really don't understand my issue....

For Tahoe beta boot normaly now but still have black screen with mouse cursor and stuck there.. I have usb ports working now but still have black screen with mouse cursor...

for Nvidia support on Tahoe there is this patch for some Nvidia cards: https://github.com/skyscope-sentinel/Skyscope-macOS-Patcher-main

 

Can someone check my EFI folder please

EFI.zip

Edited by Renard45
kaoskinkae
kaoskinkae
Posted
Posted

Perfect. OLD: AppleHDA + MykexInstaller + Disk.Icon-macOSTahoe - WhateverGreen.kext +  VideoProc Converter Grafic Radeon RX560 Working and representing the graph well, it didn't do it before. thanks to chris1111 and Mirone

 

 

image.thumb.png.8e4c0f8d90b5894cd64c8baf4b667790.png

  • Like 2
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...