Jump to content
3741 posts in this topic

Recommended Posts

Let's see..

Everything went great,

I don't have any instability or reboots like in beta1

I don't have sound of course and I still don't have(fix) WiFi

The strange thing is that I can boot and see normally without the -lilubetaall and the WGreen kext.

"that's all folks" 😇

 

 

Item-0_and_Item-0_and_Sound_and_Item-0_and_com_bjango_istatmenus_sensors.jpg

  • Like 4
9 minutes ago, eSaF said:

Bro I don't know about you but It is because I have nothing better to do.

It beats boredom waiting for the next Beta to drop.

 

Plus I am going over the steps searching for the reasons why I found it so difficult installing the first Beta.

I don't want to go through that pain again even though the relief was fantastic in the end. :lol:

 

 I'll try on the Ventura partition (I think I'll remove it completely sooner or later)

just to try... I can restore it right after , I have the image saved 😜

 

I'm sanding that part of the disc well ... it's the sacrificial lamb , for my crazy experiments 😅 

  • Like 1
  • Haha 2
51 minutes ago, eSaF said:

Has anyone had any success clean installing Beta 2?

I am testing but keeps failing, I can only clean install Beta 1 then Update to Beta 2.

 

I am trying to understand why that is happening even though I am using the same EFI Folder I did for Beta 1.

 

I'm in the process of it. Will let you know.

Btw, I didn't get any updates for Beta 2 but a soon as I rebooted update started.

I didn't get any notification about Beta 2, or that is downloaded and ready for update. Weird.

  • Thanks 1

24 hours of debugging to find the recently added bastards suddenly preventing the boot of any of the Tahoe Beta installers with my EFI-folder: dmar.aml and the actual Whatevergreen.kext version 1.7.0 build 325196. The latter kext seems incompatible with the Radeon VII and SMBIOS macPro7.1 when running the Tahoe Beta installers. Important advice for all affected users: Just disable WEG during the Update or clean install of Tahoe Beta 1 or 2 and enable it again subsequently. With SMBIOS MacPro.7.1, WEG is in principle not deemed necessary. 

 

image.thumb.jpeg.b6fd23c2cbcb981ebc1ffe0beff4734f.jpeg

 

Now I tapped into the well known FileVault trap, which I could not uncheck at the last step of the installation, thus I cannot boot anymore my Tahoe partition, as the system does not recognise my password it is asking for at the very beginning. I still can access my files on the Tahoe partition from Sequoia, where the password works properly, when asked for the access of my Tahoe disk partition.

 

Too stupid that I tapped into this, despite all warnings and advises. Any solution??

 

    

Edited by KGP-iMacPro
  • Like 5

Hi all guys

 

Thanks to @Mirone for his Lilu.kext. Few minutes ago, I successfully clean install Tahoe Beta 2 on my Z390 machine. Directly using RX 580 card. 😊

 

Do you know if OCLP patches are working on Tahoe, because of my Fenvi T919 wireless card ! Let me know if.

Edited by Matgen84
  • Like 2
5 hours ago, Max.1974 said:

 

Of course  @mick3lson  with pleasure !! 

Im generate other SMBIOS you can use it normally or change by yours 

:guitar: We are here to help and enjoy it 

 

 

EFI-Raptor OC 105 DEV KEXTS-TAHOE B2 24.06.zip 23.99 MB · 54 downloads

 

 

 

I tried your EFI with same SMBios 7.1 to boot with pendrive but unfortunately stall at this point, I don't know if it's a issue with my wireless card, I have a Broadcom BCM4360, attach my pci device list. I hope it can be solved otherwise I should try to update through Sequoia without using pendrive. Thank's in advance for your support.

 

IMG-7375.avif

pcidevices.plist

  • Like 1

If you have having trouble with File Vault on a drive and you need to turn it off from the Internet Recovery Console, here are the steps to do it...

  1. Start up your Mac in Recovery Mode, like this on Intel Macs and this for Apple Silicone.

  2. Click Utilities > Terminal from the menu bar at the top.

  3. Enter...

diskutil apfs list
  1. Look for the volume with FileVault set to Yes that you want to decrypt, select its identifier, such as "disk4s1" and cmd-c to copy. Note that there may be more than one volume with FileVault enabled, if so, look for the "- Data" volume.

data-volume

  1. Run the command below to unlock the FileVault encrypted volume. Remember to replace the identifier with the number you copied to the clipboard.
diskutil apfs unlockVolume /dev/<paste identifier>
e.g.
diskutil apfs unlockVolume /dev/disk4s1
  1. Enter the FileVault password requested and hit return. You should see the message, "Unlocked and mounted APFS volume."

  2. Execute the diskutil command below to get the UUID (Universal Unique Identifier) of enabled accounts (paste the disk identifier again). It will ask for your password, enter it.

diskutil apfs listcryptousers /dev/<paste identifier>

bash2

  1. Type the command below and paste in the volume identifier you still have in the clipboard. Next, look for the UUID for the Local Open Directory User entry from the command above, select and copy it, then paste it to the end of the command, and run it to start the decryption process.
diskutil apfs decryptVolume /dev/<paste identifier> -user <paste uuid>

recovery3

  1. My computer kept going to sleep when I did this and did nothing overnight, so you can use the Caffinate command to keep it working in the background.
Caffinate

Caffinate

  1. If you want to check the status, you can use ctrl-c to stop the Caffinate command and execute the command below to monitor the decryption status of the APFS volume.
diskutil apfs list

Now in macOS Tahoe Beta 2 running without FileVault that almost driving me mad...

 

Thanks to a colleague that make this possible with those commands via Recovery partition. => Jac Tim is the Colleague from https://www.ichi.co.uk/blog/removing-file-vault-from-internet-recovery-console

Thats all folks!

Edited by fernando.c.neves
  • Like 4
  • Thanks 6

DP2 for my X299 platform

@chris1111Hello,could u pls update this theme Flavours-ShadowSquare for macOS 26??Thanks in advance~~

Screenshot 2025-06-24 at 11.43.04 PM 拷贝.jpg

  • Like 2
8 hours ago, KGP-iMacPro said:

 

How did you pass this issue, @kaoskinkae ? 

Same kernel panic,For my X299 platform,just disable the SSDT-UIAC.aml,use USBInjectAll.kext or USBMap.kext/USBPort.kext instead,this panic will be solved perfectly

Screenshot 2025-06-24 at 11.29.28 PM.png

  • Like 2
5 hours ago, eSaF said:

Bro happy to hear your Daughter is not seriously hurt.

As we get a lot of pleasure messing about with Hacks, there are more important things than this.

 

Life is more important and sometimes we lose sight of that it self and get too wrapped up with trivial things.

We are here to help with your Hack queries although I confess you are more than capable than I solving the glitches.

I have a 5 month old, my wife has to do everything now because I'm glued to this thread especially with the return of @KGP-iMacPro! Just kidding! I just refresh the thread every time I put him to sleep.
Welcome back @KGP-iMacPro your IMacPro guide set me up in 2018, and it's been a wild ride ever since keeping it up to date with each OS. 

Finally transitioned into MacPro7,1 but still not testing Tahoe BETA until there is a new OC release to remedy some of the issues.

  • Like 1

So strange — I did a clean install, and everything goes fine until the first reboot. After that, everything just vanishes, lol.

 

When I get back to the boot menu after the first reboot, there’s no USB installer and no SSD Tahoe option to boot from. The only thing showing up is the Sequoia NVMe drive.

.

 

Spoiler

IMG_0451.thumb.jpeg.ba2e45994ca2f08160904b28fbd70465.jpeg


Update: 2nd attempt i got this:

Spoiler

IMG_0454.thumb.jpeg.dde368d36cfa9c7d873abb6687a571ca.jpeg

 

Edited by Irish_Man
3 hours ago, eSaF said:

Has anyone had any success clean installing Beta 2?

I am testing but keeps failing, I can only clean install Beta 1 then Update to Beta 2.

 

I am trying to understand why that is happening even though I am using the same EFI Folder I did for Beta 1.

 

I did a clean installation, install went well 

  • Like 1
1 hour ago, fernando.c.neves said:

 

If you have having trouble with File Vault on a drive and you need to turn it off from the Internet Recovery Console, here are the steps to do it...

  1. Start up your Mac in Recovery Mode, like this on Intel Macs and this for Apple Silicone.

  2. Click Utilities > Terminal from the menu bar at the top.

  3. Enter...

diskutil apfs list
  1. Look for the volume with FileVault set to Yes that you want to decrypt, select its identifier, such as "disk4s1" and cmd-c to copy. Note that there may be more than one volume with FileVault enabled, if so, look for the "- Data" volume.

data-volume

  1. Run the command below to unlock the FileVault encrypted volume. Remember to replace the identifier with the number you copied to the clipboard.
diskutil apfs unlockVolume /dev/<paste identifier>
e.g.
diskutil apfs unlockVolume /dev/disk4s1
  1. Enter the FileVault password requested and hit return. You should see the message, "Unlocked and mounted APFS volume."

  2. Execute the diskutil command below to get the UUID (Universal Unique Identifier) of enabled accounts (paste the disk identifier again). It will ask for your password, enter it.

diskutil apfs listcryptousers /dev/<paste identifier>

bash2

  1. Type the command below and paste in the volume identifier you still have in the clipboard. Next, look for the UUID for the Local Open Directory User entry from the command above, select and copy it, then paste it to the end of the command, and run it to start the decryption process.
diskutil apfs decryptVolume /dev/<paste identifier> -user <paste uuid>

recovery3

  1. My computer kept going to sleep when I did this and did nothing overnight, so you can use the Caffinate command to keep it working in the background.
Caffinate

Caffinate

  1. If you want to check the status, you can use ctrl-c to stop the Caffinate command and execute the command below to monitor the decryption status of the APFS volume.
diskutil apfs list

Now in macOS Tahoe Beta 2 running without FileVault that almost driving me mad...

 

Thanks to a colleague that make this possible with those commands via Recovery partition.

 

Thats all folks!

 

Successful FileVault unlock of my Tahoe Beta 2 System Disk performed from Sequoia via terminal commands provided by @fernando.c.neves above. 

 

Back on Tahoe Beta 2. Many thanks, man! 🤩 👍

 

image.thumb.jpeg.05527357b7b6706027f368a2a160d902.jpeg
 

Everything worked as described, although I had to use Local Open Directory User UUID instead of Disk User UUID, which was not available. 

 

 

image.png.a772e3ff15774957f837438c5229fda0.png

 

Just 15 minutes and the disk was unlocked. You saved my life and much work and time!!!! 🤗

 

image.png.abf5199cd778e883b6c5d41b7eebb513.png

  • Like 7
14 minutes ago, eSaF said:

Well the mystery deepens. At the moment I have an EFI Folder that boots Sonoma, Sequoia and Tahoe from this single EFI.

To me logic dictates that this same EFI should be able to assist in the creation of a USB installation drive.

 

The machine is back to the RX580 configuration booting and running all 3 Mac versions trouble free.

So why in the name of all things hackable, does it fail at 'KeyLog: Loading Pageable KC From File S/L/Kernel Collecting/BaseSystemkernelExtensions.KC'

 

I tried the lilu.kext uploaded with no difference apart from decorating my monitor screen with fancy purple lines that was last seen in Big Sur.

Please don't post suggestions to try this or that I'm done trying until the next Beta. I have aged 10 fold since the introduction of Tahoe.

 

Before Tahoe I was 99% certain of building a USB Installation drive without the drama.

This one has taken the wind out of my sails and confidence.

Mate, Not sure if this helps but for me, I cannot do a clean installation with the full EFI. I have to use the EFI with minimum kexts to get it installed. I have this EFI on a usb. 

1 minute ago, eSaF said:

What Graphics Card were you connected to for the installation?

At one point I got black screen and I couldn't be bothered to go into the BIOS to change settings and swopping around the Cable.

 

Far too much hassle considering it was only a test.

Maybe on a calmer day I will try again but without changing settings back and forth.

I am using the RX6800XT

  • Like 1
7 minutes ago, KGP-iMacPro said:

 

Successful FileVault unlock of my Tahoe Beta 2 System Disk performed from Sequoia via terminal commands provided by @fernando.c.neves above. 

 

Back on Tahoe Beta 2. Many thanks, man! 🤩 👍

 

image.thumb.jpeg.05527357b7b6706027f368a2a160d902.jpeg
 

Everything worked as described, although I had to use Local Open Directory User UUID instead of Disk User UUID, which was not available. 

 

 

image.png.a772e3ff15774957f837438c5229fda0.png

 

Just 15 minutes and the disk was unlocked. You saved my life and much work and time!!!! 🤗

 

image.png.abf5199cd778e883b6c5d41b7eebb513.png

This FileVault issue from Beta 2 it's given me pain in the head.. Till I found a solution.

 

Regards,

Fernando.

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