MacBook Pro 13" 2013 garbled boot screen with Big Sur

[arsradu]

Hi guys,

I wasn't sure if this should be under MacBooks or...MacOS...since it kinda fits under both, but please, feel free to move it wherever you feel it's more appropriate.

So, I've got an issue with a MBP 13" Late 2013 (MacBookPro11,1). During boot, after the first boot stage (Apple logo + loading bar), when switching to second stage boot, I've got a glitched screen for a fraction of a second, then it continues like nothing happened. Everything else, once the OS is loaded works fine, but this is bugging me like crazy! I know it's a bug on Apple's side, since I had this before, with older OSes on the same machine. And it's been fixed. It's just that now, starting with Big Sur, it reoccurred.

Already reported this as a bug to Apple, but so far, no fix. And since most of the development is probably focused now on Monterey (where the bug still occurs), I don't have much hope that will be fixed anytime soon.

Has anyone else encountered the same issue? Is there a fix...? Aside from waiting for Apple, of course.

I've got the same issue with both the native bootloader and OpenCore (for Monterey support). So I know this is not an issue with OpenCore, since the same issue occurred a while ago with older OSes, when OpenCore was not even present. And it still occurs now, without OpenCore. But I'm thinking maybe there is a way around this until Apple fixes it on their side (if they ever do).

 

[Audit13]

I have a late 2013 13" too and mine does the same. No big deal for me since everything works properly when it boots to the desktop.

 

[arsradu]

I have a late 2013 13" too and mine does the same. No big deal for me since everything works properly when it boots to the desktop.

Yeah, it's a bug... Looks like it reappeared with Big Sur (still occurs under Monterey). So yeah...no surprise there. ) I was hoping there's a fix for it, something other than waiting for Apple to fix it.

It's not a big issue, that's for sure. But...with this model reaching its end of life (at least for what Apple's concerned), chances are it will stay with this bug for a very long time. ) That's why I was thinking to open a new thread here, in case there's someone who has the same issue and also managed to find a fix for it.

Anyway, thank you very much for the answer! At least now I know I'm not the only one with this issue. )

 

[Audit13]

I think our model will be supported for at least another year, then I'll try Monterey which I'm running on a mid-2014 13" Pro.

 

[arsradu]

I think our model will be supported for at least another year, then I'll try Monterey which I'm running on a mid-2014 13" Pro.

The Late-2013 MBP (MacBookPro11,1) is sadly not supported anymore starting with Monterey. The only way I know to get it to work is with something like OpenCore Legacy Patcher. I'm guessing the Mid-2014 models will probably follow pretty soon.

So....yeah... Looks like, with new M1 chips, Apple lost its interest on fixing issues on older MacBooks with Intel chips. And...to some extent, it's understandable. I mean, these are pretty old machines. Very capable machines. But still...old machines nonetheless. And that shows. There are a ton of bugs with Monterey, some of them starting with Big Sur (such as this particular one), some of them even older. And Apple doesn't seem to care too much about fixing them anytime soon. Which...as I said, to some extent, it's understandable. I mean, when you have a new CPU architecture, new hardware, and a lot of hype for it, a lot of people buying these products, of course you're gonna focus most of your energy (if not all), your time and development on that.

For us, that's unfortunate, but...it is what it is.

 

[Audit13]

The Late-2013 MBP (MacBookPro11,1) is sadly not supported anymore starting with Monterey. The only way I know to get it to work is with something like OpenCore Legacy Patcher. I'm guessing the Mid-2014 models will probably follow pretty soon.

So....yeah... Looks like, with new M1 chips, Apple lost its interest on fixing issues on older MacBooks with Intel chips. And...to some extent, it's understandable. I mean, these are pretty old machines. Very capable machines. But still...old machines nonetheless. And that shows. There are a ton of bugs with Monterey, some of them starting with Big Sur (such as this particular one), some of them even older. And Apple doesn't seem to care too much about fixing them anytime soon. Which...as I said, to some extent, it's understandable. I mean, when you have a new CPU architecture, new hardware, and a lot of hype for it, a lot of people buying these products, of course you're gonna focus most of your energy (if not all), your time and development on that.

For us, that's unfortunate, but...it is what it is.

The mid-2014 13" doesn't support Monterey either so I used Open Core Patcher to install Monterey beta and the MacBook gets OTA updates.