macOS 15 Sequoia on Unsupported Macs Thread

[TOM1211]

15.3 beta 1 revert patches to 15.3 beta 2 was 1.05gb on my mid 2014 MacBook Pro no issues on patching was abit slow after reverting patches but all went ok . Thought it had fixed the 1 second grey screen issue I get on third reboot it came back as before . (interestingly I am not getting the grey background for 0.1 second screen every reboot)
Update:
For those who have the grey screen ? Do you have iCloud plus ? Try turning off private relay then shutdown , switch back on Mac without iCloud relay on and see if grey screen returns (i also turned private relay off my iPhone ).

 

[olad]

Folks, I am curious. Why is the grey screen an issue? Seriously. It lasts 5-20 seconds depending on the machine, but I don't see anyone reporting adverse effects of the screen coming on for that duration. If the machine/laptop functions as it should, what's a few seconds' delay? I've had the grey screen for a while now (I don't remember when it started on my MBP11,4 on Sequoia 15.2 via OCLP 2.20, but I gave it little thought, until now that is).
I agree totally with @Frenchmen remark that the OCLP guys are not magicians (#2327). But for what they've achieved in coaxing ancient Macs to run the latest OSes, I would also call them magicians.

 

[TOM1211]

Exciting to see macOS 15 Sequoia running on unsupported Macs! It’s always cool when the community finds ways to push hardware beyond its limits.

Mine doesn’t feel like it’s beyond its limits still works perfectly only Apple thinks it’s being pushed and windows 11 think my cpu
Too old but a couple of codes for
Windows 11 and it runs fine. lol but yes I’m
Only messing.

 

[TOM1211]

Folks, I am curious. Why is the grey screen an issue? Seriously. It lasts 5-20 seconds depending on the machine, but I don't see anyone reporting adverse effects of the screen coming on for that duration. If the machine/laptop functions as it should, what's a few seconds' delay? I've had the grey screen for a while now (I don't remember when it started on my MBP11,4 on Sequoia 15.2 via OCLP 2.20, but I gave it little thought, until now that is).
I agree totally with @Frenchmen remark that the OCLP guys are not magicians (#2327). But for what they've achieved in coaxing ancient Macs to run the latest OSes, I would also call them magicians.

I don’t care about the grey screen also don’t care if it took 60 seconds to boot as long as it works . However have posted results where I’m not experiencing it anymore which is what this thread is about unsupported macs and “issues”they experience if it’s a grey screen or WhatsApp not working this is the place to post it.?. ( I originally installed the beta and wrote a comment on the grey screen as a joke but then it disappeared anyway. Also agree OCLP team are amazing without who this thread wouldn’t exist.

 

[amaze1499]

Folks, I am curious. Why is the grey screen an issue? Seriously. It lasts 5-20 seconds depending on the machine, but I don't see anyone reporting adverse effects of the screen coming on for that duration. If the machine/laptop functions as it should, what's a few seconds' delay? I've had the grey screen for a while now (I don't remember when it started on my MBP11,4 on Sequoia 15.2 via OCLP 2.20, but I gave it little thought, until now that is).
I agree totally with @Frenchmen remark that the OCLP guys are not magicians (#2327). But for what they've achieved in coaxing ancient Macs to run the latest OSes, I would also call them magicians.

I am curious as well. I also had a similar behaviour on my machine, which was fixed with a PRAM reset. Perhaps not the same thing after all?

 

[hvds]

15.3 beta 1 revert patches to 15.3 beta 2 was 1.05gb on my mid 2014 MacBook Pro no issues on patching was abit slow after reverting patches but all went ok . Thought it had fixed the 1 second grey screen issue I get on third reboot it came back as before . (interestingly I am not getting the grey background for 0.1 second screen every reboot)
Update:
For those who have the grey screen ? Do you have iCloud plus ? Try turning off private relay then shutdown , switch back on Mac without iCloud relay on and see if grey screen returns (i also turned private relay off my iPhone ).

MBP11,1: updated OTA from 15.3b1 to b2 (24D5040f) on external SSD. Using OCLP 2.2.0.
Smooth update, resulting system quite responsive. Thanks to the developers!

 

[luckyduke23]

15.3 beta 1 revert patches to 15.3 beta 2 was 1.05gb on my mid 2014 MacBook Pro no issues on patching was abit slow after reverting patches but all went ok . Thought it had fixed the 1 second grey screen issue I get on third reboot it came back as before . (interestingly I am not getting the grey background for 0.1 second screen every reboot)
Update:
For those who have the grey screen ? Do you have iCloud plus ? Try turning off private relay then shutdown , switch back on Mac without iCloud relay on and see if grey screen returns (i also turned private relay off my iPhone ).

Folks, I am curious. Why is the grey screen an issue? Seriously. It lasts 5-20 seconds depending on the machine, but I don't see anyone reporting adverse effects of the screen coming on for that duration. If the machine/laptop functions as it should, what's a few seconds' delay? I've had the grey screen for a while now (I don't remember when it started on my MBP11,4 on Sequoia 15.2 via OCLP 2.20, but I gave it little thought, until now that is).
I agree totally with @Frenchmen remark that the OCLP guys are not magicians (#2327). But for what they've achieved in coaxing ancient Macs to run the latest OSes, I would also call them magicians.

For me, the gray screen itself is not the problem, as it disappears after a few seconds. The problem for me is that it indicates a sluggish machine at startup. I don't use iCloud Plus. And so far I have always managed to get rid of the laggy behavior and the gray screen after a few days. I'm just curious what might be the reason for the gray screen issue, i.e. a laggy start. Once the machine restarts with normal behavior and speed, it's like a brand new Mac.

 

[TOM1211]

For me, the gray screen itself is not the problem, as it disappears after a few seconds. The problem for me is that it indicates a sluggish machine at startup. I don't use iCloud Plus. And so far I have always managed to get rid of the laggy behavior and the gray screen after a few days. I'm just curious what might be the reason for the gray screen issue, i.e. a laggy start. Once the machine restarts with normal behavior and speed, it's like a brand new Mac.

it’s interesting because I have one Mac mid 2014 with a broken monitor and damaged logic board I got for cheap as spare parts and ended up repairing doesn’t experience “grey screen” whatsoever only difference I thought is it’s not signed in to my iCloud but then it could also have a old .jpeg background which who knows might even make a difference but it experiences no grey screen both have widgets and same WiFi .

 

[luckyduke23]

It would be interesting to know if all users who have/had the gray screen issue are using File Vault encryption like me...if not, a connection to File Vault can be excluded...

 

[hvds]

It would be interesting to know if all users who have/had the gray screen issue are using File Vault encryption like me...if not, a connection to File Vault can be excluded...

I do see gray screen but don‘t use file fault (MBP11,1).

 

[MacinMan]

It would be interesting to know if all users who have/had the gray screen issue are using File Vault encryption like me...if not, a connection to File Vault can be excluded...

I don't use FileVault either, and have experienced the grey screen on both an iMac 17,1, and MBP 11,1, and macOS in a Virtual machine with Paravirtualization enabled. I mentioned the VM because it's an apple stock install without Open core. I remember reading people with supported macs also having it from time to time. So, I'm not sure if it's related to Open Core Legacy Patcher.

 

[houser]

It would be interesting to know if all users who have/had the gray screen issue are using File Vault encryption like me...if not, a connection to File Vault can be excluded...

If I understand you correctly, and that is what you mean, yes I see it for 5-10 secs on all my 2012-2015 metal Macs running Sonoma and Sequoia. Since it at least partially GPU-driven to use the Apple desktops I figure it is to be expected on legacy Macs and it never bothered me.
The one non-metal MBA 2010 that I still have takes ages to do anything, including several minutes loading the wallpaper. But it runs ubuntu and Win 11 ok and is an emergency Mac running Sequoia if I have to.

 

[ShyDrA]

I’m trying to install Sequoia from a USB drive on my Trashcan running macOS Monterey 12.7.6 (Quad-core, 16GB RAM, D300). I followed all the instructions for OCLP, however, as soon as I select EFI Boot and then “Install macOS”, the screen goes black, and nothing happens.

After installing OCLP on the hard drive, the Mac receives the 15.2 update through System Settings but fails to extract or verify the update due to “connection issues.” Has anyone else encountered this problem? What could I be doing wrong?

 

[houser]

I’m trying to install Sequoia from a USB drive on my Trashcan running macOS Monterey 12.7.6 (Quad-core, 16GB RAM, D300). I followed all the instructions for OCLP, however, as soon as I select EFI Boot and then “Install macOS”, the screen goes black, and nothing happens.

After installing OCLP on the hard drive, the Mac receives the 15.2 update through System Settings but fails to extract or verify the update due to “connection issues.” Has anyone else enco

1. Have you installed OCLP 2.2.0 on your internal drive and built the EFI to your local EFI partition?
If not, maybe do that.
2. If so, is that the EFI you then choose? And then selecting the USB installer makes the screen go black?

I would regardless maybe suggest Sonoma at this time if you need stability, but Sequoia might work too.
An alternative to try after point 1. is to download the correct installer from mrmacintosh and try to install from the
resulting "Install macOS Sonoma" / "Install macOS Sequoia" in your applications folder.

This has worked here but have never tried it on a MBP trashcan. Good luck.

 

[ShyDrA]

1. Have you installed OCLP 2.2.0 on your internal drive and bult the EFI to your local EFI partition?
If not, maybe do that.
2. If so, is that the EFI you then choose? And then selecting the USB installer makes the screen go black?

I would regardless maybe suggest Sonoma at this time if you need stability, but Sequoia might work too.
An alternative to try after point 1. is to download the correct installer from mrmacintosh and try to install from the
resulting "Install macOS Sonoma" / "Install macOS Sequoia" in your applications folder.

This has worked here but have never tried it on a MBP trashcan. Good luck.

1. Yes, I did. Same issue—black screen after booting the EFI. I also performed an NVRAM reset, but it didn’t help either.
2. Yes, I double-checked that and removed the USB drive.

I’m not sure if it’s worth mentioning, but I’ve connected the Trashcan Mac Pro to my Studio Display using a TB2-to-TB3 adapter. Maybe that’s causing some issues as well.

I’m reinstalling Monterey now and will try to install Sonoma next. Fingers crossed!

 

[houser]

1. Yes, I did. Same issue—black screen after booting the EFI. I also performed an NVRAM reset, but it didn’t help either.
2. Yes, I double-checked that and removed the USB drive.

I’m not sure if it’s worth mentioning, but I’ve connected the Trashcan Mac Pro to my Studio Display using a TB2-to-TB3 adapter. Maybe that’s causing some issues as well.

I’m reinstalling Monterey now and will try to install Sonoma next. Fingers crossed!

Ok. Yes, that tb thing does sound a bit like a potential culprit.
And I assume you have checked your Mac is supported here:

Supported Models | OpenCore Legacy Patcher

 

[ShyDrA]

Ok. Yes, that tb thing does sound a bit like a potential culprit.
And I assume you have checked your Mac is supported here:

Supported Models | OpenCore Legacy Patcher

Mac Pro 2013 is supported according to OCLP. Do I need to connect the mouse and keyboard via cable when booting the EFI?

 

[houser]

Mac Pro 2013 is supported according to OCLP. Do I need to connect the mouse and keyboard via cable when booting the EFI?

Never used that model so don't know but will not hurt if you have such devices available at install. Just try.

 

[joevt]

I’m not sure if it’s worth mentioning, but I’ve connected the Trashcan Mac Pro to my Studio Display using a TB2-to-TB3 adapter. Maybe that’s causing some issues as well.

I don't think MacPro6,1 can output > 4K width. 5K width will appear garbled. Not sure why it would show no image.
You are using a Thunderbolt 2 cable between the adapter and the Studio Display?
Maybe switch to a simpler display until your Mac Pro 2013 boots correctly.

 

[Pachnes]

The short grey screen after logging in seems to be usual, as it also appears on my iMac 2019 without any drivers from elsewhere ...

 

[Ready-for-Apple]

15.3 beta 1 revert patches to 15.3 beta 2 was 1.05gb on my mid 2014 MacBook Pro no issues on patching was abit slow after reverting patches but all went ok . Thought it had fixed the 1 second grey screen issue I get on third reboot it came back as before . (interestingly I am not getting the grey background for 0.1 second screen every reboot)
Update:
For those who have the grey screen ? Do you have iCloud plus ? Try turning off private relay then shutdown , switch back on Mac without iCloud relay on and see if grey screen returns (i also turned private relay off my iPhone ).

The short grey screen after logging in seems to be usual, as it also appears on my iMac 2019 without any drivers from elsewhere ...

Which "Grey screen"??🤔
Cloud you pls upload a video.

 

[TOM1211]

Which "Grey screen"??
Cloud you pls upload a video.

You might get this for 0.1 second for me (really is a none issue for some) then the actual wallpaper appears that’s set obviously some people are seeing this for 15 seconds then there set wallpaper appears ) this screenshot was borrowed from a M1 Mac so might just be a genuine Apple issue . I can’t confirm if anything doesn’t respond like I say it’s a none issue for me because 0.1 second my normal desktop appears but obviously annoying for those where it takes longer for the desktop to appear.

 

[MacinMan]

Hey all, I was wondering if someone could help here. I installed OCLP 2.2.0 and then in the app, I checked allow native models in the app settings. Then I built and installed Open core and booted into it. I noticed it still messed up the SSV and SIP settings according to Silent Knight. How can I use the open core boot loader with supported setups without it screwing up SIP? Isn't that what allow native models is supposed to do? Thanks

 

[Ready-for-Apple]

You might get this for 0.1 second for me (really is a none issue for some) then the actual wallpaper appears that’s set obviously some people are seeing this for 15 seconds then there set wallpaper appears ) this screenshot was borrowed from a M1 Mac so might just be a genuine Apple issue . I can’t confirm if anything doesn’t respond like I say it’s a none issue for me because 0.1 second my normal desktop appears but obviously annoying for those where it takes longer for the desktop to appear.

Ah, okay. Yes, for me it's about 1-2 seconds.

I guess why this is displayed for different lengths of time could be:

• Depending on whether it's legacy metal or non-metal Macs.
• Depending on the background image - static vs. dynamic

 

[StefanAM]

Hey guys! After update to the last Beta, my account became standard user. So I don't have anymore an admin in my MBP4.1. Any hints?