Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
I'm thinking about updating my Mojave to BS on my 1tb name drive as it is far quicker than the ssd I have BS installed on.
Only macOS Big Sur 11.1 (beta)
MacBook Air 11' 2012 i5 1.7GHz 4GB RAM SSD 1TB WD Blue m2 (with adapter)
You may start reading in the first post!
I did that, but it’s still not working. I formatted the destination drive as APFS, JHFS+ and tried both clean install and updates. Neither works.
One strange thing is that the installer tells me the installation is complete even though the progress bar is only about 20-25% full, and then it reboots. The destination drive is now labelled “macOS Installer” and keeps causing reboot loops even after I apply post-install patches.
So close to giving up at this point lol
Edit your post please, the command is missing the disk to install to.
It should be:
Code:
/Volumes/Image\ Volume/patch-kexts.sh /Volumes/****** is the disk label
My Disk label is SSD so you get:
Code:
/Volumes/Image\ Volume/patch-kexts.sh /Volumes/SSDI already have Big Sur since it was made possible by the great folkes here, probably around a few weeks after the first BS beta, it runs fine on my 2012 Mac Mini, I think Macs before 2012 don't run that well, MacPro's with hardware upgrades excluded.
As the other one already said, start off by reading first, a good place would be this place...Micropatcher
Bootlooping after a BigSur installation occurs after one or more of these situations:
- clean installing BigSur with a non-APFS Mac (legacy USB devices) on external USB host root device target (installing on internal SATA should work easier)
- Legacy USB fixes not properly applied or telemetry plugin not properly deleted through a valid snapshot UUID
- incompatible CPU (some Intel Xeon and many Nehalem or similar) architecture (try OpenCore with khronokernel SSDT ACPI patch) with BigSur kernel
- incompatible non apple GPU with BigSur kernel (try an advanced OpenCore setup)
- stage3 installer hasn't completed properly (installing on internal SATA disk should fix this, then you can clone to external)
- incompatible Wifi Bluetooth combo card (or any other PCI express card) with BigSur kernelcollections
There is a circumstance where you can avoid the stage3 installer, when there is already an external USB BigSur installation (or upgrading a previous Catalina install), so updating that installation will work also skipping the stage3 installer, this because there is an apple setup done with a root account for the APFS Data Volume.
Anyway regardless of those hints, you should first check that your machine is capable to boot a BigSur recovery installer graphical environment, note that many that installed BigSur through a Catalina or Mojave desktop with Hax3 app, haven't encountered any BigSur graphical environment because the stage1 installer is made directly from Catalina or Mojave desktop, and even the stage2 installer is not a graphical environment it's simply an apple logo with loading bar showing "29 minutes remaining" this is NOT a BigSur graphical environment (also stage3 installer is not a graphical environment).
So my advise try first to boot any BigSur installer graphical environment, then you can establish what's the issue of bootlooping on MacPro3,1 (Intel Xeon or similar cpu) for example this : https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29315114
Today complite another case of Big Sur on Mac Pro 3.1.
1. Install started under Catalina by BigMac-Master with -no_compat_check bootarg (./preinstall.sh - and start install.app)
2. After reboot about 5 times, and finish install - comin to error screen
3. After complite install - do postinstall.sh under Catalina
4. boot in BIg Sur Installer at USB Stick patched by JackLuke's USB fix's and do USB fix
5. ShutDown Mac and remove USB Stick (otherwise you got bootloop )
6. Start Mac and boot in Big Sur
Last edited:
Ahhh got it, you have not completed the installation!
When you execute the macOS Big Sur Installation after the preinstall.sh script execution, reboot the Mac Pro and hit Option.
Choose the macOS Installer disk and the installation start (it require near 60 min and 5 reboots).
Only after that you can apply the postinstall.sh script from Catalina.
Thank you all for your suggestions!
I will try those and update on how it goes
Hey guys,
I love the Big Sur Patchers, so I put together a how to video using Ben's Patched Sur. The installation went very smoothly.
I was thinking of doing my next video on the micro-patcher or BigMac next. Any interest?
Again a huge shout out to DosDude1, Ben, Barry and everyone else who has contributed to these amazing patchers.
I love the Big Sur Patchers, so I put together a how to video using Ben's Patched Sur. The installation went very smoothly.
I was thinking of doing my next video on the micro-patcher or BigMac next. Any interest?
Again a huge shout out to DosDude1, Ben, Barry and everyone else who has contributed to these amazing patchers.
I did a clean install on a 2012 MBA and then replicated the container to a 2012 MBP via TB1. On the Air it appears to be booting from a locked snapshot but on the MBP it looks like its booting from a normal container like previous macOS. Does this really matter? It works fine I am just wondering about updates in the future.
Really interesting!
Made a similar observation when using this tool to replicate Big Sur installations....
OTA upgrades are a completely different Story.
I'm back to giving this thing another try again. There must be something specific to these machines that has some people successful and some not. I have TWO different Mac 3,1s. The one I've been trying is my 2.8 Ghz 8 Core one which has been my primary desktop for years and is currently running Catalina via the Dosdude1 patch. The other one is a 3.0 Ghz 8 Core also upgraded through Dosdude1's work. That later machine is the household media server and I am hoping to find budget to upgrade to an M1 Mac Mini sometime early next year. But I've been hesitant in screwing with that machine since the family actually uses that machine for media.
So far on the 2.8 Ghz machine, I've tried various versions of the StarPlayrX Github script code. I noticed that my NewerTech external USB drive caddy didn't like being hooked up via Firewire for this exercise so I had to change it to USB. That got me farther but not a complete installation. Here's what does seem to work:
1. Running ./bigmac.sh to create a boot disk.
2. Booting the BigSur install disk *sometimes* works. Sometimes it just freezes.
3. If I get the installer boot going and run Terminal, wired USB keyboards are a problem. My old standby iMac G3 keyboard I use for installs isn't recognized and neither is my wired Magic Keyboard. What does work is the Magic Keyboard 2 hooked up via a USB/Lightning cable. Not sure why. Wired mice work without fail regardless of age.
4. Once I finish running ./preinstall.sh, I can now run the BigSur installer. I have a spare 500 GB SSD (from OWC) that I retired for a 1 GB SSD on this machine. The older SSD is near the end of its life and I don't trust it with data, but it useful for tests like this.
5. During the install, at some point there is a reboot.
6. At this point, the install sometimes fails since it can't seem to proceed to the next level. But sometimes it boots to a new screen where it seems to freeze while trying another progress bar. I decided to let it complete and not just give in to my impatience. At some point in 30 minutes or so, there is another reboot.
7. if I've gotten this far, I'm just rebooting to a gray screen and finally the rebooting stops frozen like this. Again, it doesn't seem like anything is happening and at this point I usually give up and reboot back to the option key. My own two choices are Catalina and the USB Boot HD. I don't have an intermediate installer to come back to.
8. If I boot back to Catalina and examine the BigSur SSD, I see that is has properly formatted for APFS with both regular and "Data" volumes. But the install seems incomplete. Specifically, there are no applications in the Applications folder and I'm certain there are lots of other things missing.
What I might try next is to have the ./bigmac.sh script to use the aging SSD instead, and then use Disk Utility to partition the disk further to see if it makes any difference (it shouldn't).
Maybe you Mac Pro not supported APFS nativly?
Try to use Jackluke's fix BigSur BaseSystem stage2 installer fix, that maybe work for you.
And maybe you should be use DosDude1's APFS_ROM_Patcher to get native APFS Support.
No. If I boot directly from BigSurBaseSystemfix I just get the Apple logo, no progress bar. From CatalinaLoader into the BigSurBaseSystemfix USB, I get the same Apple logo + loading bar, then stalled out on full gray screen. Not even a Language Chooser option.
Still no luck I booted from you OpenCore4b1, then used the picker for your patched BigSurBaseSystemfix installer. I get the full gray screen after a couple of black screens with Apple logo w/progress bar.
Same story if I try to boot from OpenCore4b1, then pick the 11.0.1 Recovery partition.
I'm not sure if the gray screen is related to Beta, as I've only been using 11.0.1 (20B50).
This Mac Pro 3,1 has already been running Catalina for some time via Dosdude1 patcher. Which means I'm using his APFS patch since it wouldn't work otherwise.
APFS patch in DosDude Catalina patcher and FirmWare BootRom patcher - its a different things i mean.
Yes, I patched my firmware to be able to boot APFS last year. Otherwise it’s impossible to boot Catalina since it’s expecting to run from an APFS volume.
Ok. So I am using the latest version of Patched Sur on my late 2013 27" iMac. Every time i hit EFI at start up and restart the computer holding down the option key, it just sits on a black screen. The only way to recover it is to power off the computer and unplug anything from USB then restart. I'm not sure what's going on. Any advice would be appreciated.