[pre-release] macOS Sequoia

[Max.1974]

@jlrycm @eSaF 

 

Hi there! Here Drop-EFI from @chris1111  works very fine with Sequoia beta 5. 

 

Maybe you need check permissions to run app. 

 

Spoiler

 

[jlrycm]

1 hour ago, Max.1974 said:

@jlrycm @eSaF 

 

Hi there! Here Drop-EFI from @chris1111  works very fine with Sequoia beta 5. 

 

Maybe you need check permissions to run app. 

 

  Reveal hidden contents

 

I tried again, this time using the latest Drop-EFI release that @chris1111 posted this morning following his instructions found in the GitHub issue, but it didn’t mount the EFI  from the external drive where Sequoia is installed after loading macOS 15 latest dev beta. I don’t get any error. It runs the script and shows the window saying the EFI mounted but I don’t see it mounted in Finder. As I said earlier, the script that @Shaneee shared in this thread works in Sequoia mounting the EFI from the external drive.

Edited August 10, 2024 by jlrycm

[Max.1974]

Thats important to you getting works, @Shaneee and @chris1111 that all contributed with yours effort !! 

 

Nice that works to you! Congrats!! 

Edited August 10, 2024 by Max.1974

[Alpha22]

@chris1111 I confirm that Drop-Efi works with macOS Sequoia Beta 5 

Thanks

 

Spoiler

 

 

Edited August 10, 2024 by Alpha22

[meg2014]

Finally!

 

I got B5 to install and work, but it wasn't easy.

 

First the OTA (over the air) upgrade did not work.  I ended up with a broken Finder and many other problems. Scrambled bits, and a real mess of an attempted install.  A reinstall didn't work.   I was truly stuck. 

 

I decided to do a full install via USB.  But I had to wait for a link as I couldn't find it on my own.  Finally, someone posted the full download link, so I downloaded that, put it on a USB drive and tried that.  But I couldn't get it to work because it was spontaneously rebooting in the middle on the install.  Grrrr......🙁

 

In doing research, I found that @jlrycm had posted that disabling BlueToolFixup, which was causing rebooting in the middle of his attempted install, well, after disabling that, he was able to install.  I had to wipe my existing install and start from scratch, but then I disabled BlueToolFixup by using my Ventura install and EFI Agent on that install to disable BlueToolFixup.  After that, thank God, the install completed. 

 

Still, I needed to adjust the EFI in the Sequoia B5 install and rebooting into Ventura every time I needed to eidt the EFI on B5 was getting old.  So of course, like so many of you have noted, now I had to deal with the EFI issues that Sequoia B5 has caused, and that created some difficulty, and more delay but eventually
@chris1111 's new utility made it possible to adjust the EFI in B5 directly.

 

Once that was done, I had to use Migration Assistant to migrate my data from a Ventura install to the B5 install.  My Migration Assistant transfer was far from perfect, so lots of cleanup was needed to be done. But after many hours, it was finally over and I was done.  Whew.....

 

Some times installs go like this.  You just have to keep trying.

Edited August 10, 2024 by meg2014

[mek21]

Since  this msdos EFI mounting issue is still a topic for discussion, here, again, is an easy to use automator app that is configured for disk0s1.   See my previous post for additonal uses.

 

https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=410506&key=fe05c60485bc2760059fd6365c8264b2

[Max.1974]

Manually commands that works for EFI show and mount and USB mount is: 

 

Example:

 

 

UBS=$NAME

 

disk10s1 = DOS_FAT_32 TYPE

 

 

sudo diskutil unmount /dev/disk10s1; sudo mkdir /Volumes/USB; sudo mount -w -t msdos /dev/disk10s1 /Volumes/USB

 

 

 

EFI

 

Example 

 

 

 

 

 

EFI=disk2s1

 

sudo diskutil unmount /dev/disk2s1; sudo mkdir /Volumes/EFI; sudo mount_msdos /dev/disk2s1 /Volumes/EFi 

 

But I prefere use scripts from @chris1111 (Tks !!  )

 

 

 

Vídeo: 

 

Spoiler

 

 

 

Edited August 11, 2024 by Max.1974

[cankiulascmnfye]

I %&/() hate Apple for how they crippled filesystem support.

 

You even have to mount USB flash drives now! I wanted to copy my EFI folder and copy it over to my FAT32 formatted usb drive. But mounting USB flash drive with chriss' script unounted the internal EFI partition… I had to copy the EFI folder to the desktop temporarily… aaaarggh

[chris1111]

@cankiulascmnfye @miliuco @eSaF @Max.1974

Ok all is Fix for DROP EFI 

Make sur Uninstalling Drop EFI with the `Previous V2` or 'Previous PRE Release V3' FOR @Alpha22 with DropEFI Installer.app

Or Uninstalling manually if you know how to do it

 

 

After uninstalling use the command

tccutil reset AppleEvents
tccutil reset SystemPolicyAllFiles

Reboot macOS

Download release V3

 

Follow every step in  new Video

 

Edited August 11, 2024 by chris1111

[Max.1974]

Thanks @chris1111 my brother, always Big thanks!!  Mercy! 

 

🇨🇦 🇧🇷 

[ANTIKO]

11 hours ago, chris1111 said:

 

Пожалуйста, попробуйте следовать моим инструкциям. 

https://github.com/chris1111/Drop-EFI/issues/2#issuecomment-2281840398

Thank you, your advice helped

[chris1111]

1 hour ago, ANTIKO said:

Thank you, your advice helped

latest and final advise is here 

 

[Alpha22]

7 hours ago, chris1111 said:

@cankiulascmnfye @miliuco @eSaF @Max.1974

Ok all is Fix for DROP EFI 

Make sur Uninstalling Drop EFI with the `Previous V2` or 'Previous PRE Release V3' FOR @Alpha22 with DropEFI Installer.app

Or Uninstalling manually if you know how to do it

 

 

After uninstalling use the command

tccutil reset AppleEvents
tccutil reset SystemPolicyAllFiles

Reboot macOS

Download release V3

 

Follow every step in  new Video

 

followed the instructions for version 3 all ok
Thank you @chris1111

[BALDY_MAN]

I have installed Sequoia. but I can't see any usb stick I plug in on the desktop. how do I fix it please

[Alpha22]

15 minutes ago, BALDY_MAN said:

I have installed Sequoia. but I can't see any usb stick I plug in on the desktop. how do I fix it please

https://github.com/chris1111/Mount-MS-DOS-Partition

 

Spoiler

Here the command

USB is the name of my Volume  - FAT 32 / Master Boot Record

diskutil list
diskutil unmount /dev/disk9s1
mkdir -p /Private/tmp/USB
sudo mount -t msdos /dev/disk9s1 /Private/tmp/USB

 

Mount-MS-DOS-Partition.tool

 

Attaching Automate Script

Mount-MS-DOS-Partition.zip1.87 kB · 36 downloads

 

 

 

Thanks to @chris1111

Edited August 11, 2024 by Alpha22

[BALDY_MAN]

15 minutes ago, Alpha22 said:

https://github.com/chris1111/Mount-MS-DOS-Partition

Thanks to @chris1111

@Alpha22  its any usb I plug in. I can't see them to open. the link above seems to be for ms-dos partition. I have some fat32 drives i can't view 

[Alpha22]

22 minutes ago, BALDY_MAN said:

@Alpha22  its any usb I plug in. I can't see them to open. the link above seems to be for ms-dos partition. I have some fat32 drives i can't view 

 

from the link download Mount-MS-DOS-Partition, drag it into Terminal you will see your usb enter the number and matti your password

 

[BALDY_MAN]

35 minutes ago, Alpha22 said:

 

from the link download Mount-MS-DOS-Partition, drag it into Terminal you will see your usb enter the number and matti your password

 

thanks for your help. I'm just going back to Sonoma. thanks again

[chris1111]

@Alpha22 I create an App for the Mount MSDOS Partition tool Same thing, type the disk number 

[chris1111]

9 minutes ago, eSaF said:

Nice work Maestro!!!. 

Thank you 😆

[cankiulascmnfye]

For those using AdvancedMap.kext: v4.0.0 works in Sequoia but not in Sonoma. But v3.0.0 works in Sonomo, so…

 

I did this to workaround the problem:

 

 

And yes, you can rename kexts, since they are nothing more than containers! You just have to ensure to control which one is loaded by utilizing MinKernel and MaxKernel Settings

Edited August 11, 2024 by cankiulascmnfye

[BarryBar]

Recently I posted a screenshot of Opencore start problem in the case of a upgrade install to macOS Sequoia. I find it strange since my EFI is working under Ventura. Did all the necessary changes to config file still no success.

 

In the reddit Hackintosh forum the user called  doggodoesaflipinabox 😀 posted this:

"Updating to Sequoia

As Apple now polls for more T2-specific information from its Macs, you can't update to Sequoia without either of these fixes:

• Use iMac19,1 SMBIOS to update, then revert to your old SMBIOS if needed

• Download the latest release of RestrictEvents.kext, and use it with the boot argument revpatch=sbvmm."

Could it be that you all upgraded using the mentioned iMac SMBIOS? My SMBIOS is macPro 7,1 and that would explain it.

[Slice]

29 minutes ago, BarryBar said:

Recently I posted a screenshot of Opencore start problem in the case of a upgrade install to macOS Sequoia. I find it strange since my EFI is working under Ventura. Did all the necessary changes to config file still no success.

 

In the reddit Hackintosh forum the user called  doggodoesaflipinabox 😀 posted this:

"Updating to Sequoia

As Apple now polls for more T2-specific information from its Macs, you can't update to Sequoia without either of these fixes:

• Use iMac19,1 SMBIOS to update, then revert to your old SMBIOS if needed

• Download the latest release of RestrictEvents.kext, and use it with the boot argument revpatch=sbvmm."

Could it be that you all upgraded using the mentioned iMac SMBIOS? My SMBIOS is macPro 7,1 and that would explain it.

In Sonoma using SMBIOS iMac19,1 allows you to get update. In Sequoia not.

To get updates in Sequoia you need RestrictEvents.kext or use Clover as I do.

[cankiulascmnfye]

42 minutes ago, BarryBar said:

Recently I posted a screenshot of Opencore start problem in the case of a upgrade install to macOS Sequoia. I find it strange since my EFI is working under Ventura. Did all the necessary changes to config file still no success.

 

In the reddit Hackintosh forum the user called  doggodoesaflipinabox 😀 posted this:

"Updating to Sequoia

As Apple now polls for more T2-specific information from its Macs, you can't update to Sequoia without either of these fixes:

• Use iMac19,1 SMBIOS to update, then revert to your old SMBIOS if needed

• Download the latest release of RestrictEvents.kext, and use it with the boot argument revpatch=sbvmm."

Could it be that you all upgraded using the mentioned iMac SMBIOS? My SMBIOS is macPro 7,1 and that would explain it.

 

Well, the important part is a) registering the sytstem for beta update and b) using  RestrictEvents + boot-arg/NVRAM entry.

 

RestrictEvents is mandatory when:

- Using anything else than 00000000 for csr-active-config

- SecureBootModel is set to Disabled (which you must do in order to be able to update to anything newer than macOS 14.3 – otherwise the installer will crash early!)

 

Changing SMBIOS is not a necessity. See, I have a Cometlake CPU so iMac20,2 works. And I have a Lenovo Notebook which uses MBP15,2 SMBIOS and I can install 15.0 beta 5 on both machines.

Edited August 11, 2024 by cankiulascmnfye

[Max.1974]

10 hours ago, BALDY_MAN said:

thanks for your help. I'm just going back to Sonoma. thanks again

 

Try Manually my friend, if you can't run programs 

 

Follow this video: 

 

Spoiler

 

 

 

To Watch this video  in 4k resolution, don't use Safari on Sequoia.