asapreta

Hello Everyone. Last week I tested Tahoe installation in a spare SSD and decided to get it running in my actual setup, upgrading the Sequoia installation I had. The only difference I noticed was, after the final install reset I was asked for my password just after boot, not when the system was already loaded. And of course my password didn't work! Got the information about the File Vault, installed apfs_aligned.efi driver and unchecked the needed option in OC configurator. Could login in Tahoe with no issues except it is not possible to disable the File Vault. No matter how much I try to disable it, enter the password and select to turn it off, it always is on. Is there a way to turn it off? I have reached some information it can be disabled in Recovery Boot, but no so sure if it only for real macs. Checking the encryption, I get this: FileVault is On. Encryption in progress: Percent completed = 12 It is in 12 ever since. The other information I got it that File Vault is enabled always if you are connected to iCloud. Will it be even after forcing turning it off? Thank you!

The easiest way is Maldon's suggestion:

Solved, removed whatevergreen during install.

Where is this tutorial? The one with voodooHDA didn't work. Just found about MykextInstaller in insanelymac and it worked!

Hi guys. I finally solved the issue where the flash drive was not being recognized in BIOS. Now, using Olarila's coffeelake EFI folder, I got a KP after some loading. Changing the boot parameters string to the same I run sequoia, it boots, but hangs before installer starts: Using this same EFI folder, I created a Sequoia flash drive and It reaches the installer. Any clues?

Hi! I did that, got the coffeelake one but still no go. Tried several flashdrives redownloaded the image and still can't see the flashdrive as a boot option on PC's boot menu. Any other ideas? >>> EDIT >>> Problem solved!

Hello guys. I have created with Balena Etcher the flashdrive with Olarila's Tahoe RAW image and I can see it mounted in MacOS but it won't show as a bootable device in motherboard' boot menu. Is there any additional step this time as I am used to create it and never had problems before, downloading the image from here and creating the bootable flashdrive. <EDIT> I forgot to check but, do I need to add the EFI folder? Are these below updated to Tahoe? Thanks in advance,

Fiz o procedimento como sempre faço com as imagens daqui - obrigado por sinal por disponibilizá-las - e a única diferença que agora são com flashdrives de 32Gb e todas as tentativas dão esse erro. E hoje cedo até tentei com a imagem do mediafire, baixada no Windows 11 e "queimada" nele, com o mesmo erro no Balena Etcher. Mas vou continuar tentando.

Hello Guys! I have downloaded twice both Mediafire and Torrent Olarila Sequoia images but can't create the USB boot drive (I using a 32GB USB Flashdrive) as usual in Balena Etcher. Balena Etche reports an error while validating the image, about a compressed file to check the source. Tried to boot that image and really confirmed the installer can't proceed due to invalid files. Has anyone experienced that too? Thanks in advance,

Mald0n, bom dia. Já baixei duas vezes, tanto a versão do Mediafire como do Torrent e em ambas não é possivel criar com sucesso o USB bootável. Fiz o mesmo processo de sempre pelo Balena Etcher e no final, pós a verificação, reclama de uma imagem comprimida que pode estar com problemas. Tentei até dessa forma bootar com este USB para ver o que acontecia e realmente o installer detecta vários erros nos arquivos. Alguém mais já fez comentários sobre este problema? Tentei fazer post no fórum correspondente mas não há a opção de New Topic. Grato desde já.

Hi all! (sorry I couldn't find a Sonoma specific forum) I just noticed this weird error in my hack after using Sonoma for a while. In these two information windows I have mixed information. In the stock About this Mac window, the CPU model is wrong as I have a Core i5-9400F as listed on the About this Hack window. And, accordingly to my config.plist and SMBIOS section in the OpenCore configurator, the correct serial is the one on the About this Mac window. Where the hack the other on in the About this Hack came from? Also if I change back the iMac model to the iMac Pro (2017), in the stock About this Mac, no processor model is shown, just its speed. Can anyone please point me what can I do to fix this? Thanks in advance,

Hello Guys. Downloaded the image from here and tried on my rig where I have Ventura installed. Gigabyte Z390 Gaming X Radeon RX570 4gb Intel i5 9400 It end the first part of installation, reboots and I can't continue the install. In the menu doesn't appear the HD the installation was done to select and continue, I can only see the option to begin again the installation (and boot EFI, Reset NVRam and Toggle SIP). <EDIT> tried again and it showed up. Continuing.... <EDIT 2> Worked!

@MaLd0n Does an DSDT need to be update once it was created for a system, without changes on a new MacOS release? Since I have my new system, you created a DSDT I used on BigSur (thank you!). Can I use it in Ventura without updating? Thanks!

Desculpa se vai parecer uma pergunta idiota, mas pensei que o DSDT funcionasse para a máquina e não fosse tão dependente da versão do OS. Estou testando uma instalação do Ventura e tentei usar o meu USBMap.Kext do Big Sur nele (fazendo a colocação do kext no config.plist) e não deu certo. Aí lembrei que possivelmente as portas USB tem outro nome neste KEXT porque eu tenho o DSDT no Big Sur. Copiei esse DSDT pro Ventura, removi o SSDT da pasta ACPI, bootei e KP. Tenho que pedir um novo DSDT para o Ventura no mesmo computador? Se for o caso, fiz o dump: Agradeço @MaLd0nse puder, por favor, revisar para o Ventura então! https://www.transfernow.net/dl/20221217pvgbQYce Obrigado

I managed to get it installing by replacing the EFI folder with the correct one for my motherboard. thank you.

Oi pessoal. Estou com meu sistema rodando o BigSur com OC faz uns dois anos sem problemas Cheguei a instalar num disco secundário o Monterrey mas não fiz a troca de sistema. Hoje resolvi encarar o VEntura com a imagem disponibilizada aqui no Olarila. A instalação parece correr bem até depois do reboot da maça com a instalação. E, aparentemente fica nesse loop, como se nao finalizasse a instalação do recovery. Não importa quantos reboots der, vem até esse ponto, aparecem algumas mensagens e reinicia. Acho que devo precisar ajustar alguma coisa no bootargs, não? Usar os mesmos que uso no BigSur? Minha máquina: Gigabyte Z390 Gaming X - Intel i5 9400F - 16 GB DDR4 2666 - Radeon RX 570 4GB Agradeço qualquer ajuda. EDIT: Consegui instalar (até suave) colocando a pasta EFI correta (CoffeLake) no flashdrive de instalação. Agora é o ajuste fino. Obrigado.

Hello guys. For the first time I am trying to install Ventura in the same computer today I run Big Sur (I don't remember if the forum show in the signature the Rigs I have). I created the flashdrive with the raw image provided here in Olarila (thanks guys) with balena. The installation was going fine. it restarted about 2-3 times. Then I noticed it was in a loop, always installing the recovery folder, until this step, restart and again, again, see below: I didn't change anything in the image so, maybe it is time to adjust something, right? Like, use the same boot args I use for Big Sur? Copy the EFI folder, also provided here by Olarila, to the flashdrive to meet my chipset (Intel chipset for i5-9400F processor) ? EDIT> My specs: Gigabyte Z390 Gaming X - Intel i5 9400F - 16 GB DDR4 2666 - Radeon RX 570 4GB Please, advise me how I can proceed. Thanks in advance.

Just tried the new EFI folder with OC 0.7.1 for Monterey from Olarila and now I have sound.

Thanks, will run it. EDIT: Just a feedback. Still no sound from the ALC892. I have the new kexts, OC 0.7.0 and just ran the utility to rebuild the cache. I tried with the original flags and the beta ones and no sound with any of them. As I saw a lot of people complaining about the audio, I will wait a little bit, there is a long road until the final version. But, if someone wants me to try something, let me know. It is a test HD so no problem poking around.

How to rebuild cache in this case? Because, as the new kexts are in the KEXTS folder of OC in EFI, probably these commands won't do anything: sudo chown -R root:wheel /System/Library/Extensions/ sudo chmod -R 755 /System/Library/Extensions/ sudo kmutil install --update-all sudo kcditto Right?

I saw some report of these running fine. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/?do=findComment&comment=2760133

Acho que vale dar uma olhada nesta página: [pre-release] macOS Monterey - Page 5 - New Releases and Updates | InsanelyMac Eu tentei com os Kexts divulgados do dia 08/06 e com as flags sugeridas e não consegui sucesso no som da placa mãe. Apenas som pelo HDMI.

MalD0n, onde eu posso procurar os Kexts atualizados, como por exemplo do áudio (AppleALC.kext). É aqui GitHub - acidanthera/AppleALC: Native macOS HD audio for not officially supported codecs ? A princípio foi a única coisa que não funcionou aqui quando instalei o Monterrey vindo do BigSur 11.4 beta. O bootloader (OC) está atualizado. Obrigado.

Acho que a única coisa que não tinha visto que não fora instalado é o som porque estou usando via HDMI. Mas preciso checar uma coisa antes

Instalado sem mexer em nada sobre um Big Sur 11.4 Beta.