Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Bravo2zero

macrumors regular
Jun 1, 2013
125
42
Sheffield
MacBook Air 2017 also just bricked here. It's just turned on after about an hour of on/off playing about. The recovery mode wouldn't work too, all I could get is EFI boot and net selection but no further. I noticed also my MacBook sits idle about 90 degrees so I've had to install Mac fan control and run the fan at 100% which brings it down to 60 degrees idle.
 

eoblaed

macrumors 68040
Apr 21, 2010
3,087
3,202
Had the issue, I unplugged USB devices from mine and it loads fine. Plug them back in after I log in.

Does this seem to be a general workaround for people that are having problems with a beta 3 upgrade installing/booting?
 

markosb

macrumors 6502
Mar 19, 2010
384
55
Does this seem to be a general workaround for people that are having problems with a beta 3 upgrade installing/booting?
It worked for me. My iMac 2015 just sits on a black screen till I remove the three USB devices I have hooked up... one is a color munki display calibration device, Samsung SSD drive, and a powered USB hub.

Every time I reboot it sits on a black screen the first time I waited 10 min, before I forced shut the iMac down. Waited again, but this time noticed the USB devices were lit up. So I pulled them and the computer booted. On one occasion I connected the devices and the computer was super laggy on the login screen. I couldn't type as it took forever to get a character typed. I pulled the USB devices and it was fine. They work normally after I am logged in. I submitted a feedback report about it cause I had no issues with Beta 1 or 2.
 
  • Like
Reactions: Bravo2zero

richmond62

macrumors 6502
Mar 12, 2020
281
88
Well, at the risk of being accused of being cowardly, having managed to update to 10.15.6 stable after a lot of faffing around from the beta versions I've just deregistered from the Beta channel as I really don't want to wake up tomorrow and find my machine has been shafted by MacOS 11.0 beta 3.
 
Last edited:

Bravo2zero

macrumors regular
Jun 1, 2013
125
42
Sheffield
After all the issues of this afternoon shenanigans with laggy booting like others on here have had all now seems to be well except for 2 things.
The stupidly high temps remain leaving me to use a 3rd party app to run the MacBook at 100% speed to keep it bellow 100 degrees.
The Macbook seems to have lost boot animation or there’s a issue on that part as soon as it turns on loading bar is immediately full but the macbook takes about 30-45 seconds to load. This is an improvement over this afternoon as it took around 10mins to boot or crash on booting.
 

markosb

macrumors 6502
Mar 19, 2010
384
55
Well, at the risk of being accused of being cowardly, having managed to update to 10.15.6 stable after a lot of faffing around from the beta versions I've just deregistered from the Beta channel as I really don't want to wake up tomorrow and find my machine has been shafted by MacOS 11.0 beta 3.
Nothing cowardly about that. It is a beta for a reason. I’ve been testing Windows and Mac OS for a long time and nothing phases me when issues happen. Just report and share information till it gets fixed. It’s still a good beta for me.
 

bradley8795

macrumors regular
Original poster
Sep 19, 2013
163
68
So it is working again. My personal issue was the RAM. Odd that it worked perfectly for months, but the update seemed to kill it, IDK how or what happened, but I removed the OWC RAM, and used just the 8GB from Apple and it booted into recovery and allowed me to get back to Catalina. Hope that possibly helps anyone else with any issues.
 

xgman

macrumors 603
Aug 6, 2007
5,697
1,425
I know beta beta beta, but i find all this very discouraging, even for so early on.
 

iMacDragon

macrumors 68020
Oct 18, 2008
2,396
731
UK
It could be that the updated firmware changed default ram timings for some reason to something Incompatible? Ram needs to be verified somehow to try and diagnose
 

Mk2

macrumors member
Jul 9, 2009
51
73
I've just heard back from Apple and they've told me that the firmware was corrupted but they were able to fix it. The data was unfortunately unrecoverable, but I've had most of it backed up.
 

CheesePuff

macrumors 65816
Sep 3, 2008
1,454
1,574
Southwest Florida, USA
So it is working again. My personal issue was the RAM. Odd that it worked perfectly for months, but the update seemed to kill it, IDK how or what happened, but I removed the OWC RAM, and used just the 8GB from Apple and it booted into recovery and allowed me to get back to Catalina. Hope that possibly helps anyone else with any issues.

Did you put the RAM back in and see if it still works?
 

byke

macrumors 6502a
Mar 29, 2007
724
60
LDN. UK
Just curious if you figured anything out yet? With no Apple Stores open and no appointments available at any authorized repair shops looks like this won’t be resolved for quite a while for me anyways.

did you figure out a solutoon?
 

bradley8795

macrumors regular
Original poster
Sep 19, 2013
163
68
Did you put the RAM back in and see if it still works?

Yes I did, once I finally got it back to working on Catalina I reinstalled the 32GB of ram from OWC, and it would not boot. Contacted OWC and they are sending me some replacement RAM, will see if that fixes the issue. I'm considering going ahead and making another back up now, and updating to the public beta before I get the replacement RAM to make sure that everything is working right before I put it in and fry 2 more sticks.
 
  • Like
Reactions: CheesePuff
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.