Jump to content

[Pre Release] macOS Tahoe 26.1

Anto65

By Anto65,
in New Releases and Updates

 Share
246 posts in this topic

Recommended Posts

bluenote56
bluenote56
Posted
Posted

Success also this time. Unfortunately I must fix usb since I made a mess with the dedicated efi but this is related to my young age and I'll fix it with some cold beers. Doc doesn't agree but he's too young to understand (he drinks spritz and I said it all). Thanks as usual.

Untitled.jpg

  • Like 2
  • Haha 6
Zevgoli
Zevgoli
Posted
Posted
23 hours ago, strangeron said:

3.21 GB 😉

For me it tried to download this version and initially seemed to be progressing ok then I got an error at which point it downloaded the full installer.  This did install ok not sure why the short version died.

 

Cheers, Howard 

arsradu
arsradu
Posted
Posted (edited)

Hey guys,

 

I'm pretty sure I'm not the only one with this issue, but I'm hoping someone found a fix for it, cause it's driving me nuts!

 

So I'm trying to restore a Time Machine backup because I can't boot into the OS, so looks like the only solution here is a wipe and reinstall. At some point, with a very specific EFI configuration, I managed to boot into it, and did a Time Machine backup, but I can't remember what were the settings anymore. I've spent already waaaay too much time on this.

 

Anyway, I've installed Tahoe on a new partition, and was trying to restore the Time Machine backup I created earlier. All good with the restore, backup completes successfully. However, I can never finish the damn thing! It says Migration Complete. And then counts down to restart. After restart, it's showing the same thing again.

 

I tried to search for a solution online, but everyone says I should just undo root patches (I'm using OCLP-Mod by the way) and try again. Did that. Same result. I'm stuck in a loop. It does the same thing on new installations as well. What the hell is going on?

I tried to do a partial restore too (without "other files and folders"). Same thing. Could be that the backup is corrupted in some way. And I'm considering copy-pasting stuff manually from the backup. But I was thinking maybe you guys know of a way to fix this without having to do that.

 

Tahoe was a pain in the a** from the beginning. It still is after almost half a year after the initial release.

 

Anyway, looking forward to hearing your opinion on this.

Edited by arsradu
deeveedee
deeveedee
Posted
Posted (edited)

Easy OTA upgrade from Tahoe Beta 3 -> Beta 4 on my old HackBookPro6,2.  Still waiting for OCLP 3.0.0 in order to apply post-install patches, but the old hack is surprisingly responsive without the patches.

Screenshot2025-10-21at12_20_36PM.png.21c4c567f7c35253ab6a506da791a559.png

 

EDIT: ... and my HackMini8,1 with VoodooHDA.kext 3.0.2 for outstanding audio, SIP csr-active-config = <01000000> and no root patches.

Spoiler

Screenshot2025-10-21at11_46_07PM.png.69043daf80b181601e0c5309a0638427.png

 

Edited by deeveedee
  • Like 6
kaoskinkae
kaoskinkae
Posted
Posted

Only once on my two computers plus the USB-SSD adapter drives did the system fail to work after applying the AppleHDA.kext file, and the system never booted.

 

I had no choice but to reinstall the system from another drive with a Sequoia or Tahoe system. I believe there is a recovery method that allows you to recover the system.

 

I've tried this, and it requires booting the system with the WhateverGreen.kext disabled, just like we do with official and beta Tahoe installations.

 

Can anyone provide a link or a way to recover the system without having to reinstall it? I've seen many colleagues whose systems have stopped working.

  • Like 2
arsradu
arsradu
Posted
Posted (edited)
1 hour ago, kaoskinkae said:

Thanks, I remember this method and it is the same.

 

Try to boot into recovery, if you can, and do a First Aid on the Macintosh HD drive. It helped me a few times to boot back into the OS. For some reason, it doesn't work anymore. But it definitely helped before.

 

I think we might have the same issue as you're describing. Not sure what exactly happened but yeah, I remember having this issue after fiddling around with AppleHDA kext in an attempt to fix it. Apparently that was not the right way to fix it, but also, I couldn't boot into the OS anymore after that. Except for a couple of times, which a USB drive, to which I can't remember which settings did I make to make it work...

 

But anyway, try to do this, too. Maybe it works for you, too.

 

By the way, right now, my computer doesn't even boot into the boot picker. It goes into some sort of power loop. Turns on for a few seconds, then restarts. And keeps doing that until you force shut it down by pressing and holding the Power button. Can't even enter BIOS anymore... Last night everything was going fine. Now I can't boot at all. Not even to the same place I was yesterday.

Edited by arsradu
arsradu
arsradu
Posted
Posted (edited)
10 minutes ago, eSaF said:

Hiya, sorry to hear you're having a rough time with your rig.

If you can't get into the BIOS, you may need to reset it like this,

 

Power down, bridge the CMOS terminals on the motherboard to set the board to default settings (unless the board has a reset CMOS button that can be pressed).

On reboot you'll have setup the BIOS again for macOS as all the settings will be at default.

 

If that method fails, power down, remove the power cord and press the power button for at least 15 seconds, this removes any residue power from the capacitors that maybe still present.

Now remove the CMOS Battery for at least 1 minute then replace. This method will render the board in a default state, you'll have to set time date and replace settings for macOS to resume normal operation.

 

Hope you don't have to use these extreme methods and find a simpler way to normalcy.

Good luck Bro.

Thank you eSaF! Much appreciated!

 

Unfortunately, I've tried all of those... This is the second time this happens completely out of nowhere. Like, everything fine the day before, you shut down your computer normally, all good, the next day this happens...

 

Last time, the only thing that worked, and could be something related to this that's causing the issue, was removing some of the HDDs/SSDs attached to the computer via SATA, and trying to boot like this.... I need to take a closer look at those when I get some time, and make sure only one/two drives are actually bootable (having a boot file in the EFI folder). Theoretically, there should only be two SSDs that are bootable. One with Windows, with its own dedicated EFI boot, only for Windows, because you know how Microsoft loves to just re-write every other boot file and put their own, and one with OC (which can also boot Windows). But maybe I forgot to clean up some of the old EFIs... Will see...

 

Oh, by the way, all of the sudden, my RaspberryPi is acting up after a rather uneventful upgrade. :))) Looks like I'm gonna have a busy time trying to fix everything.

 

Anyway, thank you so much for the ideas! :) Much appreciated!

Edited by arsradu
Anto65
Anto65
Posted
  • Author
Posted (edited)
6 minutes ago, Oyecomova said:

In 26.1 beta 4 (25B5072a) USB port mapping no longer works.. so I disabled USBPorts.kext.. the system boots with keyboard and mouse enabled.. and Hackintool v4.1.3 does not detect the ports.. has anyone else experienced this?

 

 

Edited by Anto65
  • Like 3
deeveedee
deeveedee
Posted
Posted
25 minutes ago, Oyecomova said:

In 26.1 beta 4 (25B5072a) USB port mapping no longer works.. so I disabled USBPorts.kext.. the system boots with keyboard and mouse enabled.. and Hackintool v4.1.3 does not detect the ports.. has anyone else experienced this?

USB mapping that worked for Tahoe 26.0 works for Tahoe 26.1 Beta.  If you'd like help, please post your EFI (at least your config.plist and your USB port mapping kext(s)).

  • Like 2
kgp
kgp
Posted
Posted (edited)
17 hours ago, arsradu said:

Hey guys,

 

I'm pretty sure I'm not the only one with this issue, but I'm hoping someone found a fix for it, cause it's driving me nuts!

 

So I'm trying to restore a Time Machine backup because I can't boot into the OS, so looks like the only solution here is a wipe and reinstall. At some point, with a very specific EFI configuration, I managed to boot into it, and did a Time Machine backup, but I can't remember what were the settings anymore. I've spent already waaaay too much time on this.

 

Anyway, I've installed Tahoe on a new partition, and was trying to restore the Time Machine backup I created earlier. All good with the restore, backup completes successfully. However, I can never finish the damn thing! It says Migration Complete. And then counts down to restart. After restart, it's showing the same thing again.

 

I tried to search for a solution online, but everyone says I should just undo root patches (I'm using OCLP-Mod by the way) and try again. Did that. Same result. I'm stuck in a loop. It does the same thing on new installations as well. What the hell is going on?

I tried to do a partial restore too (without "other files and folders"). Same thing. Could be that the backup is corrupted in some way. And I'm considering copy-pasting stuff manually from the backup. But I was thinking maybe you guys know of a way to fix this without having to do that.

 

Tahoe was a pain in the a** from the beginning. It still is after almost half a year after the initial release.

 

Anyway, looking forward to hearing your opinion on this.

 

@arsradu, as far I remember you recently opted for BCMC. Be very careful with macOS updates with the kext enabled! Some people even reported that it was necessary to remove also the hardware to complete the recent macOS updates! Hope this helps somehow.  

Edited by KGP-iMacPro
  • Like 2
arsradu
arsradu
Posted
Posted
1 minute ago, KGP-iMacPro said:

 

@arsradu, as far I remember you recently opted for BCMC. Be very careful with macOS updates with the kext enabled! Some people even reported that it was necessary to remove also the hardware to complete the recent macOS updates! Hope this helps somehow.  

Well, the updates were ok so far.... Just can't understand why I can't boot into the system (sometimes I get an error that says something like "different KC UUID than expected"). What bothers me the most is the fact that I don't understand why/how did it work before? Weird things happening.

 

But yeah, good to know. Thank you very much for the info and the advice! :)

  • Like 1
arsradu
arsradu
Posted
Posted (edited)
2 hours ago, eSaF said:

To be honest, I removed that Apple Card and all it entails to regain wifi in Tahoe and replace the Fenvi Card.

The cons of using that Card outweighed the pros compared to the Fenvi.

 

For the time being I will leave the rig as it is until a more viable solution is found with either OCLP or the BCMC route.

It is good to have the machine not freezing when going into or coming out of Sleep/Wake mode.

 

 

You know, this is a common issue.... I've noticed this when setting up my Lenovo L450 laptop for Sequoia. Kexts like firewolf's Realtek Card Reader have this exact issue. At least after sleep. Before sleep...might be something else. Apparently the problem is resuming kexts functionality after sleep. It's caused by the system waiting 180s (hope I remember it well) for the kext to respond. If it doesn't, it panics. That's the issue with that kext, I'm guessing it's the same issue with this one, as well.

 

Not sure if this is something that can be fixed on driver's side... When it comes to Realtek Card Reader kext, looks like it's not being developed/updated anymore. I hope it's not gonna happen the same thing with BCMC as well. But...it could happen.

 

Anyway, looks like my power loops before BIOS screen were caused by....RAM. How do I know that? Well, let's say I removed everything, one by one, until the only things left were my mouse and keyboard, and the CPU and RAM on my motherboard. :)) Why it happened now, why only sometimes, I have no idea. But that's how I fixed it for now. I can work fine with only 8GB of RAM. Generally speaking, when weird things are happening, and you can't explain it with anything software-side, it's probably the RAM.

 

Now let's hope I can also fix the boot to system issue I was having before.

 

Update: fixed that, too.

 

How?

 

With some of your guys' help (Mirone's suggestion brought here by Anto's post above) and two little commands in Terminal, from Recovery: 

mount -uw /Volumes/Tahoe
bless --mount /Volumes/Tahoe --bootefi --last-sealed-snapshot

If the boot drive's name is not "Tahoe", the command above needs to be changed accordingly.

That fixed it. Simple as that.

 

This is why I love this forum. You guys are awesome! Better than Google, better than ChatGPT. Absolutely amazing.

 

Thank you!

Edited by arsradu
  • Like 5
jlrycm
jlrycm
Posted
Posted (edited)
8 hours ago, KGP-iMacPro said:

 

@arsradu, as far I remember you recently opted for BCMC. Be very careful with macOS updates with the kext enabled! Some people even reported that it was necessary to remove also the hardware to complete the recent macOS updates! Hope this helps somehow.  

I need to disabled the kext in the config file before triggering the OTA update; otherwise the update process would stall. After the update is done I re-enable Firewolf wifi kext. No need to remove the wifi card at my end.

Edited by jlrycm
  • Like 4
ameenjuz
ameenjuz
Posted
Posted (edited)
51 minutes ago, Anto65 said:

:thumbsup_anim:

 

Screenshot2025-10-26alle22_04_11.png.7d80b2857a0089c01861d7be8f1d9e69.png

( Notebook HP EliteBook 840 G4 )

 

  Hide contents

 

Screenshot2025-10-26alle21_26_09.png.b4e72ca9f45bced780e95b3fa4622a5a.png

 

Screenshot2025-10-26alle21_27_23.png.8c5be388209f1df448ac0391e18dab69.png

 

Screenshot2025-10-26alle22_33_53.png.e004fdc3dde86b9865f9bb77078ffd3e.png

 

 

Do you have external display is working in this smbois MacBook Pro 2019

i have not working 

please share your efi folder

Edited by ameenjuz
Edited
AlfredoM
AlfredoM
Posted
Posted (edited)

I had a bit of time again and wanted to try reinstalling the Tahoe 26.1 beta.

 

I stopped at the RC1 version of Tahoe.

Now I've noticed that after installing the 26.1 beta, nothing works: no USB, no Ethernet. What's going on? Everything worked with the RC1.

It seems that the Tahoe no longer works on a late 2013 iMac, or does anyone know what's going on?

 

Could it be due to OC 1.0.4, or does it have to be OC 1.0.6?
Or is it related to KDK? There are two builds available on Apple Developer:
25B5057f and 25B5062e
Thanks for any tips.

KDK's

Edited by AlfredoM
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...