I have the same problem as well I have been trying to install sense yesterday no go! So disappointedHas anyone with a Mac mini 2018 updated to beta 3 at all? The full update and incremental update just restarts my Mac with a 10 minute timer, and I don't have any spare drives to use an installer. Is there another workaround?
What computer do you have?I have the same problem as well I have been trying to install sense yesterday no go! So disappointed
Mac mini 2018 and its a no go...What computer do you have?
I'm disappointed as well.
Does the fresh install erase everything on the disk?I got it successfully installed! Boot into recovery mode and selected fresh install and from there it downloaded b3 and installed. It took around an hour but all works great and no need for me to make a usb boot installer. Why I don’t know 🤷🏻♂️
No it doesn’t you just choose to recover your Mac it went really slow between loading screens. Sorry just trying to remember off the top of my head ( have weekend on my 🧠)Does the fresh install erase everything on the disk?
It worked. Thanks so much!No it doesn’t you just choose to recover your Mac it went really slow between loading screens. Sorry just trying to remember off the top of my head ( have weekend on my 🧠)
[automerge]1595617015[/automerge]
Hold on boot up Command+r for a awhile until it gets into the recovery screen
I’m glad it worked one way or another have a great weekend ✌It worked. Thanks so much!
My Macintosh HD was locked, probably because of FileVault. Unlocking it in “Reinstall macOS” doesn’t work, I had to mount it in Disk Utility before I could reinstall.
This worked for me -- thanks!In my experience, you have to make the USB installer and boot from that device to successfully install the update. Make sure you boot to recovery mode using Command + R on boot to disable T2 chip security (allow booting from external drive and perhaps lower OS verification to medium or off temporarily). You should be able to find the instructions to make a USB installer on Apple’s website. Just replace the Catalina text with the name of the Big Sur Beta installer. When all of this is done and you’re ready to install boot the Mac mini while holding the Option key to select the boot device. Should be the one that looks like a drive icon and labeled macOS installer.
This is actually mentioned in the Developer Release Notes. I had to resort to a USB Stick.In my experience, you have to make the USB installer and boot from that device to successfully install the update. Make sure you boot to recovery mode using Command + R on boot to disable T2 chip security (allow booting from external drive and perhaps lower OS verification to medium or off temporarily). You should be able to find the instructions to make a USB installer on Apple’s website. Just replace the Catalina text with the name of the Big Sur Beta installer. When all of this is done and you’re ready to install boot the Mac mini while holding the Option key to select the boot device. Should be the one that looks like a drive icon and labeled macOS installer.
In my experience, you have to make the USB installer and boot from that device to successfully install the update. Make sure you boot to recovery mode using Command + R on boot to disable T2 chip security (allow booting from external drive and perhaps lower OS verification to medium or off temporarily). You should be able to find the instructions to make a USB installer on Apple’s website. Just replace the Catalina text with the name of the Big Sur Beta installer. When all of this is done and you’re ready to install boot the Mac mini while holding the Option key to select the boot device. Should be the one that looks like a drive icon and labeled macOS installer.
X The drive is fit and well according to Disk Utility's 'First Aid' and it begins to install Bug Sur on my MacBook Pro; but on my Mac Mini it gets stuck. I begin in System Preferences, and change Start Up Disk to the BS flash drive. Reboot. Installation looks good ( logo and progress bar). After a while I get "A software update is required to use this disk". I allow this update, then I get a new error message: "An error occurred installing the update".
Do you have any idea what this is or how to fix it? I assume that there's something about the T2 chip that's not allowing it but, as I say, I've given permission to boot from another drive.
I have the exact same problem with my 2018 Mac mini. The latest Public Beta 5 would not install.
That's my guess, too. But I don't know what to do about it.
Thank you for the suggestion.I had the same issue on my 13" 2018 MBP. The fix was to re-flash the bridge OS using a USB-C cable and another Mac.
Previous to this I had tried everything including a full reformat, clearing NVRAM, clearing SMC, re-downloading Big Sur, USB thumb drive install. Nothing worked until I used configurator and re-flashed the bridge OS.
Has anyone with a Mac mini 2018 updated to beta 3 at all? The full update and incremental update just restarts my Mac with a 10 minute timer, and I don't have any spare drives to use an installer. Is there another workaround?
it’s because mac mini 2018, as iMac 27 5K 2020, both have T2. the chip protect from install any beta software.
This is incorrect. Apple has not yet released a beta which supports the 2020 iMac, but every other computer Apple sells which has a T2 can install the Big Sur betas.it’s because mac mini 2018, as iMac 27 5K 2020, both have T2. the chip protect from install any beta software. I know cz I have both. luckily I avoid repeating same error on the brand new mac mini, but I have still the iMac 27, also brand new, blocked in a stupid loop. you need to take the mac mini to Apple and with Apple Configurator Beta 2, yes, beta, they will restore the os, witch, btw, will be reinstalled completely from scratch.
Update: Just tried to install and it took. Didn't do anything different (same installer as yesterday), I am guessing the error it was throwing about BridgeOS being out of date was Server Side and it was fixed between yesterday and today?Having this same issue on my 2018 Mac mini and the Big Sur RC 2. Any ideas? Should I just try and wait for the Public Release on Thursday to see if that resolves the issue?