Semi Successful boot

hasrt1206

New member
AMD OS X Member
Aug 17, 2020
24
1
3
CPU:
Ryzen 5 3600
Hello everyone and thank you to those who helped me last time.

I installed Sequoia 15.3.1 from the latest Sonoma, it took me a while but finally got it working.
During my initial use of the system I was encountering glitches on my screen, because of it I decided to rollback with my previous EFI from Sonoma. The previous EFI I had from Sonoma was not booting my usb. Looking around I found oc simplify, which is what I use to boot into Sequoia. When I rolled back to my previous EFI, that would not boot either. So I decided to put pack the EFI from oc Simplify and now after it boots I get a blank screen.

All of these started because I have a native Apple airport card BCM94360CS that I want it to run natively but I have not had any success.

I have attached the two EFI's I have used.

Any help would be appreciated,
thanks.
 

Attachments

What's the working one? Because your Sonoma EFI has the CPUR SSDT for B550 and your Sequoia one doesn't. So I'd assume that's your main issue. Also your Sequoia SMBios, set that to the same as you had matching Serials etc to stop any iCloud sync errors.

For your BCM card to work you'll need extra setup to use OCLP to patch the system for Modern Wireless.
 
What's the working one? Because your Sonoma EFI has the CPUR SSDT for B550 and your Sequoia one doesn't. So I'd assume that's your main issue. Also your Sequoia SMBios, set that to the same as you had matching Serials etc to stop any iCloud sync errors.

For your BCM card to work you'll need extra setup to use OCLP to patch the system for Modern Wireless.
Do I still need CPUR SSDT even when I made my own SSDT from my windows?
I used the Sonoma one when I had Sonoma, then I created another one with OC Simplify which is the Sequoia one to use with Sequoia. But I had graphical issues to I switched back to Sonoma EFI and that did not work and going back to Sequoia EFI gets me a black screen.
 
Are you using the agdpmod=pikera boot argument to make your RX 5700 XT work correctly?
 
Are you using the agdpmod=pikera boot argument to make your RX 5700 XT work correctly?
Yes, I am.
I have tried booting with an usb and it boots without any issue (using the Sequoia EFI) but when adding the EFI into the main drive I get the black screen aforementioned.
 

Attachments

  • Screenshot 2025-03-15 at 4.21.27 PM.png
    Screenshot 2025-03-15 at 4.21.27 PM.png
    124.3 KB · Views: 12
I would double check you are copying the EFI folder on your USB installer to the EFI Partition on your macOS drive.

Do the following
  1. Download and copy the Hackintool App to your Applications folder, if you don't already have it installed.
    1. https://github.com/benbaker76/Hackintool/releases/tag/4.0.3
  2. Open Hackintool and navigate to the Disks tab,
  3. Click on the downward pointing arrow to the right of the name of your USB drive, to mount the USB EFI partition.
  4. Copy the EFI folder from the USB EFI Partition to your desktop.
  5. Eject the USB from the system.
  6. Click on the downward pointing arrow adjacent to your maCOS drive, this should mount the EFI partition on your desktop.
  7. Drag and drop the EFI folder you saved on your desktop to the EFI partition for your macOS drive.
This should fix any issues you have regarding booting to a black screen. As you will be using the exact same EFI you were previously using on your USB installation drive.

Screenshot 2025-03-15 at 23.50.23.png Example of Hackintool > Disks tab, with two drives present in the system (top drive macOS, bottom drive Windows 11)

The screenshot above shows the way the arrow changes when the EFI partition for the macOS drive appears on the desktop, i.e. when the volume is mounted. Arrow points upwards and the folder icon is not greyed out.
 
I would double check you are copying the EFI folder on your USB installer to the EFI Partition on your macOS drive.

Do the following
  1. Download and copy the Hackintool App to your Applications folder, if you don't already have it installed.
    1. https://github.com/benbaker76/Hackintool/releases/tag/4.0.3
  2. Open Hackintool and navigate to the Disks tab,
  3. Click on the downward pointing arrow to the right of the name of your USB drive, to mount the USB EFI partition.
  4. Copy the EFI folder from the USB EFI Partition to your desktop.
  5. Eject the USB from the system.
  6. Click on the downward pointing arrow adjacent to your maCOS drive, this should mount the EFI partition on your desktop.
  7. Drag and drop the EFI folder you saved on your desktop to the EFI partition for your macOS drive.
This should fix any issues you have regarding booting to a black screen. As you will be using the exact same EFI you were previously using on your USB installation drive.

View attachment 16589 Example of Hackintool > Disks tab, with two drives present in the system (top drive macOS, bottom drive Windows 11)

The screenshot above shows the way the arrow changes when the EFI partition for the macOS drive appears on the desktop, i.e. when the volume is mounted. Arrow points upwards and the folder icon is not greyed out.
I have but I still get a “blank” screen.
 

Attachments

  • IMG_5898.jpeg
    IMG_5898.jpeg
    1.8 MB · Views: 5
Did you change the boot order in the bios, so the UEFI Partition is first in the list of boot drives?
 
Yes.
I get into the boot picker and then I can choose my Mac drive but when it finishes booting I get that "blank" screen.
 
How are you connecting the Hack to the display, DisplayPort or HDMI?
Are you using any adapters or adapter cables, I.e. DP to HDMI?
 
It’s connected via display port, but I was able to fix it. It turns out I needed to reset nvram :ROFLMAO:.

I am dealing with other issues as well, my airport card still not working. Does anyone know the extra setup that @Shaneee mentioned?
I have a weird graphical bug. When using a web browser I get this weird red lines across the website. So far it only occurs on a web browser, Thorium to be more specific.
Lastly, I hope my Ethernet controller is not working my work around is a native Apple usb Ethernet adapter. I have an intel I225-v and currently using the AppleIntell210Ethernet.kext that use to work on Sonoma but not on Sequoia.

Thanks for everyone's help, much appreciated!
 

Attachments

  • Graphical Bug.png
    Graphical Bug.png
    751.4 KB · Views: 5
See this guide for the Ethernet controller fix.


Do you get the same graphics issues with any other browsers?
 
  • Like
Reactions: Edhawk
I tried both suggestions and was not successful. I kept getting a kernel panic.
So I decided to roll back to my previous config and EFI folder and now I am stuck again in the "black" screen. I reset the nvram twice before booting and same "black" screen. I've tried booting from usb and the same "black" screen.
I've reset nvram 5 times and still getting a black screen. Still have no idea of what is causing that.
 

Attachments

  • IMG_6EB8F430-5F06-45CD-9A20-47CE4223EFE9.jpeg
    IMG_6EB8F430-5F06-45CD-9A20-47CE4223EFE9.jpeg
    3 MB · Views: 7
See this guide for the Ethernet controller fix.


Do you get the same graphics issues with any other browsers?
I have tried adding both the boot arg and the kext but the ethernet still does not work.

I do not get the same graphical issues with other browsers.
 

Attachments

  • Screenshot 2025-03-17 at 7.50.14 PM.png
    Screenshot 2025-03-17 at 7.50.14 PM.png
    3.6 MB · Views: 5
I was able to fix Thorium web browser by using OpenGL as graphics backend.
Is there a way to get sidecar working? My airport wireless card is running fine, both airdrop and handoff function properly.
But sidecar "loads" and I can see it on my Display settings and add my iPad as a screen but it only a black screen.
 
For Sidecar you need the FeatureUnlock kext and an iMac SMBIOS (for example, iMac20,1) and some Terminal commands.
Is this still applicable for Sequoia?
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.