kaoskinkae Posted August 5 Share Posted August 5 39 minutes ago, eSaF said: Bro remove your personal data from the EFI Folder and upload here. We can take a look to see if there any errors. The Fenvi T-919 is ideal as proven by many. I feel something else is responsible for the failure on your machine. If your folder is proving too large to upload, remove the Resources Folder. SecureBoot should be set to Disabled if that is your query. the data is the sameconfig.plist on both computers, same error, look at the instructions on my computer Link to comment Share on other sites More sharing options...
eSaF Posted August 5 Share Posted August 5 2 hours ago, kaoskinkae said: the data is the sameconfig.plist on both computers, same error, look at the instructions on my computer To be honest I can't see much wrong within your config apart from if this config.plist is from the Z390 Board, why so many SSDT Files???!!! All I can say is, insure you have the very latest kext versions (I use OCAT to get me the Developers versions). The Z390 Board coupled with a Fenvi T-919 is a good combo, so I can only gather there is something else happening within your configuration. @miliuco has the same Platform board plus some very good EFI examples posted here on IM, have a search and do a comparison to your own. 2 Link to comment Share on other sites More sharing options...
mek21 Posted August 5 Share Posted August 5 4 hours ago, BarryBar said: Hello, I'm trying to upgrade install Sequoia from Ventura but am stuck in the booter as can see. Is this an error because secureboot or is it another problem? With my thanks in advance for any advice to solve this. Try turn off secure boot, ensure BIOS settings are correct, use minimum of kexts. unplug any peripherals not needed, boot args -igfxvesa -lilubetaall Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 11 1 Link to comment Share on other sites More sharing options...
Wayang-NT Posted August 5 Share Posted August 5 (edited) beta 5 ... no drama ... Edited August 5 by Wayang-NT 8 Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 Hi Guys, avoid update if you not have access to another EFI partition. Its have been denied access to open it. 6 Link to comment Share on other sites More sharing options...
taqieallah Posted August 5 Share Posted August 5 (edited) Beta 5 update Done - cpu temp is lower compared to beta 4 Edited August 5 by taqieallah 6 Link to comment Share on other sites More sharing options...
eSaF Posted August 5 Share Posted August 5 25 minutes including download and installation and it's done! Spoiler 6 Link to comment Share on other sites More sharing options...
jlrycm Posted August 5 Share Posted August 5 (edited) 7 hours ago, BarryBar said: Hello, I'm trying to upgrade install Sequoia from Ventura but am stuck in the booter as can see. Is this an error because secureboot or is it another problem? With my thanks in advance for any advice to solve this. @BarryBar If you use BlueToolfixup kext, consider disabling it if you are still getting update issues. In my case, in addition to disabling securebootmodel I need to disable this kext, otherwise the update will not progress and will remain in a restarting loop every time I resume it. Edited August 5 by jlrycm Link to comment Share on other sites More sharing options...
Craig Hazan Posted August 5 Share Posted August 5 From my M1 AIR I'm being shown two updates!, Beta 5 and Beta 15.1. 4 Link to comment Share on other sites More sharing options...
strangeron Posted August 5 Share Posted August 5 No problem🙂 7 Link to comment Share on other sites More sharing options...
eSaF Posted August 5 Share Posted August 5 (edited) 21 minutes ago, Craig Hazan said: From my M1 AIR I'm being shown two updates!, Beta 5 and Beta 15.1. I would hazard a guess, the 15.1 was geared for M1 Mac since hacks couldn't have it. Then I would try the Beta 5 after unless 15.1 is bundled with Beta 5 (for real Macs) which I doubt. Edited August 5 by eSaF 4 Link to comment Share on other sites More sharing options...
Craig Hazan Posted August 5 Share Posted August 5 3 minutes ago, eSaF said: I would hazard a guess, the 15.1 is geared for M1 Mac since hacks couldn't have it. Then I would try the Beta 5 after unless 15.1 is bundled with Beta 5 (for real Macs) which I doubt. I'm going to download 15.1 for the M1, I want to find out if any AI has been added. 3 Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 (edited) To Open EFI need run this commands sudo -i Type your password and then mkdir /Volumes/efi sudo mount -t msdos /dev/disk4s1 /Volumes/efi (need put diskXsY when your disk is X and your partition is Y) Maybe will be necessary Open your EFI from another macOs version, like Sonoma or Ventura Edited August 5 by Max.1974 6 Link to comment Share on other sites More sharing options...
Craig Hazan Posted August 5 Share Posted August 5 This must be M series only as Apple Intelligence has been added to System Settings, I obviously joined the wait list. 8 Link to comment Share on other sites More sharing options...
Craig Hazan Posted August 5 Share Posted August 5 I guess it was a short waiting list!. 6 Link to comment Share on other sites More sharing options...
kaoskinkae Posted August 5 Share Posted August 5 7 Link to comment Share on other sites More sharing options...
Craig Hazan Posted August 5 Share Posted August 5 The new Siri is pretty special in 15.1 6 Link to comment Share on other sites More sharing options...
Irish_Man Posted August 5 Share Posted August 5 No issues during the update. The issue after the update is that I can't see mounted EFI partition on my desktop. Anyone with the same issue? It's clearly mounted but it doesn't show up on desktop. I see all drives but EFI partitions. 3 Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 Yes @Irish_Man I gave alert above 2 Link to comment Share on other sites More sharing options...
Irish_Man Posted August 5 Share Posted August 5 1 hour ago, Max.1974 said: With this command and EFI folder deleted by another macOS Sonoma works this command sudo mount -t msdos /dev/disk4s1 /Volumes/efi When I use that command I get this: Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 (edited) @Irish_Man So sorry I fogott to said Need type this first sudo -i Type on root# your password and then mkdir /Volumes/efi sudo mount -t msdos /dev/disk4s1 /Volumes/efi (need put diskXsY when your disk is X and your partition is Y) Edited August 5 by Max.1974 Link to comment Share on other sites More sharing options...
jlrycm Posted August 5 Share Posted August 5 (edited) 21 minutes ago, Irish_Man said: No issues during the update. The issue after the update is that I can't see mounted EFI partition on my desktop. Anyone with the same issue? It's clearly mounted but it doesn't show up on desktop. I see all drives but EFI partitions. Does this mean that if I try to mount the EFI in Sequoia using OCAT, OpenCore Configurator or any other used to mount it, it will not mount and only the terminal command that @Max.1974 just shared would mount it? Edited August 5 by jlrycm 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted August 5 Share Posted August 5 (edited) My container disk was changes by Apple that put a lot of garbage on EFI partition, need delete all this "trashes". My real disk install is disk 4 but Apple "synthesized" to disk7 😆 yes @jlrycm Edited August 5 by Max.1974 2 1 Link to comment Share on other sites More sharing options...
jlrycm Posted August 5 Share Posted August 5 26 minutes ago, Max.1974 said: My container disk was changes by Apple that put a lot of garbage on EFI partition, need delete all this "trashes". My real disk install is disk 4 but Apple "synthesized" to disk7 😆 yes @jlrycm Thanks @Max.1974 fortunately I’m using the EFI that the macOS sonoma disk has and I’m not relying on the EFI that the Sequoia disk has. I hope this thing that was done to you guys it’s a bug or something that is not happening a lot / will be fixed by Apple in the near future. 2 Link to comment Share on other sites More sharing options...
Recommended Posts