macOS 11 Big Sur on Unsupported Macs Thread

[Tech Enthusiasm]

Redo the install-setvars part with install-setvars.sh -v. Then boot "EFI Boot" again. Then try to boot the installer again. See if there's any error message before the reboot happens -- or it's possible that the error message will go by too quickly to see, so see if it pauses for (more than) a few seconds at a particular line of text before the error happens.

Or, another thing to try: Boot back into a previous version of macOS (edit: of course you would need to do that anyway to run install-setvars.sh -v, but do this while you're at it), make sure the USB stick is inserted, then in Terminal run the command hdiutil verify /Volumes/Install\ macOS\ Big\ Sur\ Beta/BaseSystem/BaseSystem.dmg. The output should look something like this (the last line is the most important, especially the last word on that line):

Checksumming Protective Master Boot Record (MBR : 0)…
Protective Master Boot Record (MBR :: verified   CRC32 $89823BF5
Checksumming GPT Header (Primary GPT Header : 1)…
GPT Header (Primary GPT Header : 1): verified   CRC32 $A045269D
Checksumming GPT Partition Data (Primary GPT Table : 2)…
GPT Partition Data (Primary GPT Tabl: verified   CRC32 $C89838B6
Checksumming Untitled 1 (Apple_APFS : 3)…
..............................................................................
         Untitled 1 (Apple_APFS : 3): verified   CRC32 $C8F63833
Checksumming GPT Partition Data (Backup GPT Table : 4)…
..............................................................................
GPT Partition Data (Backup GPT Table: verified   CRC32 $C89838B6
Checksumming GPT Header (Backup GPT Header : 5)…
...............................................................................
  GPT Header (Backup GPT Header : 5): verified   CRC32 $14F74833
...............................................................................
verified   CRC32 $69037A38
hdiutil: verify: checksum of "/Volumes/Install macOS Big Sur Beta/BaseSystem/BaseSystem.dmg" is VALID

Many thanks @Barry K. Nathan for your swift response! I redid the install-setvars part with install-setvars.sh -v to use verbose mode and I booted from “EFI Boot”. However, when I tried booting from the installer, the machine rebooted before any error showed up. I also ran the command “hdiutil verify /Volumes/Install\ macOS\ Big\ Sur\ Beta/BaseSystem/BaseSystem.dmg”, as you advised, and the last line said “hdiutil: verify: checksum of "/Volumes/Install macOS Big Sur Beta/BaseSystem/BaseSystem.dmg" is VALID” — as you said it should. But, interestingly, after I redid install-setvars the installer showed up as “EFI Boot” instead of “Install macOS Big Sur Beta”. Am I missing something? Do you know any other way I can try to get Big Sur installed?





Thank you

 

[ChadTimothy]

Hey guys, I installed Big Sur on my upgraded iMac 2012 - CPU : 3770 - 32gbRam - OWC 248SSD - 1gb HDD (not fusioned) when the first public came out thanks to you guys here. The instructions where relatively easy to follow.
It fixed an issue that I had in Catalina where my Mac would keep resetting so that in itself was worth it....

I have just upgraded to the most recent Beta again thanks to BarryK and the people on the forum here.
I did an upgrade rather than a fresh install.

I'm pretty sure it worked but the version number 20A5343j is still showing in the settings, I can see some of the UI is different such as the way some icons are rendering (although I still have the glitch line through the background image) and am just wondering if this is normal?

 

[jackluke]

Hey guys, I installed Big Sur on my upgraded iMac 2012 - CPU : 3770 - 32gbRam - OWC 248SSD - 1gb HDD (not fusioned) when the first public came out thanks to you guys here. The instructions where relatively easy to follow.
It fixed an issue that I had in Catalina where my Mac would keep resetting so that in itself was worth it....

I have just upgraded to the most recent Beta again thanks to BarryK and the people on the forum here.
I did an upgrade rather than a fresh install.

I'm pretty sure it worked but the version number 20A5343j is still showing in the settings, I can see some of the UI is different such as the way some icons are rendering (although I still have the glitch line through the background image) and am just wondering if this is normal?

The correct version not showing maybe is a simply SystemVersion.plist or SystemVersionCompat.plist not overwritten by the stage2 installer, from your BigSur terminal type: ls -l /System/Library/Kernels/kernel or date -r /System/Library/Kernels/kernel

if the date and time showed is 25 September 9:19 (stock compiled by apple) then surely you are on the latest Big Sur beta 9 .

 

[Ungibbed]

Alright, a question here for when Big Sur finally releases, it seems I may have minimal issues running on my 2012 Mini. However, I have never done this before and not afraid to admit that I am am absolute noobsauce when it comes to the terminal and such. ?‍♂️

My last experience with a command line was with DOS 6.2.2 (and Win9x versions). I do back up my data of course but just wonder how far down the rabbit hole am I diving in here? ?

 

[justperry]

Alright, a question here for when Big Sur finally releases, it seems I may have minimal issues running on my 2012 Mini. However, I have never done this before and not afraid to admit that I am am absolute noobsauce when it comes to the terminal and such. ?‍♂️

My last experience with a command line was with DOS 6.2.2 (and Win9x versions). I do back up my data of course but just wonder how far down the rabbit hole am I diving in here? ?

The last micropatcher version made installing BS much easier, the easiest way is to have another computer at hand to read the instructions from the micropatcher page or just print them out, or read them on an iPad/iPhone.

 

[jackluke]

Redo the install-setvars part with install-setvars.sh -v. Then boot "EFI Boot" again. Then try to boot the installer again. See if there's any error message before the reboot happens -- or it's possible that the error message will go by too quickly to see, so see if it pauses for (more than) a few seconds at a particular line of text before the error happens.

When someone gets a quick kp at early BaseSystem booting, then I guess also MacPro with Nehalem and Westmere architecture have the same *ACPI* issues of iMac Clarkdale i3 and MacBookPro Arrandale i5 i7, so maybe it's not your Micropatcher the kp issue for these machines but it's the incompatible BigSur kernel 20.0.0 .

 

[vincenzo79]

please give a link to make bootable usb for mbp 13 2012 with this package

Hello, I downloaded the link you indicated but unfortunately the copy is made. I choose the item "Install Big Sur" but unfortunately the error symbol appears and I have no way of being able to install.

 

[vincenzo79]

Hello,
I read that the fix also works with Big Sur Beta 9, but I don't know where to download this version.
Can you help me ?
I am registered on the Apple developer program but it makes me download the profile file and I have no way to get the installation dmg.

 

[Pinarek]

@vincenzo79 Here download the Full Installer for DP9:

curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo /usr/bin/python installinstallmacos.py --raw --seedprogram DeveloperSeed

Show Number 10 !!

 

[Joonyv]

Hi, anyone know what is it in my disk utility (see pictures attached) and how to unmount it ?
Thanks.

I have exactly the same problem and have no idea what to do. This partition is taking 100 GN of disk space and can’t delete it or unmount it. Hope someone savvy can help us.

 

[vincenzo79]

I am very very happy ... I was able to install BigSur Beta 9 on my Macbook Pro.
I guess it is not possible to make updates through the App Store because these would block the computer ... correct?
In this moment no Wi-FI

 

[justperry]

I have exactly the same problem and have no idea what to do. This partition is taking 100 GN of disk space and can’t delete it or unmount it. Hope someone savvy can help us.

Your answer is on this page.

I am very very happy ... I was able to install BigSur Beta 9 on my Macbook Pro.
I guess it is not possible to make updates through the App Store because these would block the computer ... correct?
In this moment no Wi-FI

Regarding Wifi, read the "Read me" on Micropatchers page.

 

[buckrock]

@vincenzo79 Here download the Full Installer for DP9:

curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo /usr/bin/python installinstallmacos.py --raw --seedprogram DeveloperSeed

Show Number 10 !!

I'm confused! Here's #10??????:
10 041-90855 10.13.5 17F66a 2019-10-23 Install macOS High Sierra Beta

 

[vincenzo79]

Regarding Wifi, read the "Read me" on Micropatchers page.

Thanks a lot.
I ran the fix to fix the WiFi issue. Now I just have to figure out if when the final version comes out I can update without losing anything or if I have to do the installation again

 

[Ausdauersportler]

Thanks a lot.
I ran the fix to fix the WiFi issue. Now I just have to figure out if when the final version comes out I can update without losing anything or if I have to do the installation again

You will surely have to do a new installation, will do the patching again but most likely you will get all your user data untouched. But I would start with a backup right now and try a restore before you bet on this.

 

[justperry]

Thanks a lot.
I ran the fix to fix the WiFi issue. Now I just have to figure out if when the final version comes out I can update without losing anything or if I have to do the installation again

100% sure you have to that again, we've been doing this since beta 1, except for b7-b8, there's no Full Installer for these 2 beta's
You won't loose anything, I am on OS X/macOS since the very first beta, I always installed in place, never reinstalled...never.

 

[buckrock]

@vincenzo79 Here download the Full Installer for DP9:

curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo /usr/bin/python installinstallmacos.py --raw --seedprogram DeveloperSeed

Note that this curl command will write a table of several download choices. You need to be aware that the download will be put in your user Home folder and that it will not be a .pkg file, but will be saved as a .sparseimage.

See my post #4,615 .

 

[vincenzo79]

100% sure you have to that again, we've been doing this since beta 1, except for b7-b8, there's no Full Installer for these 2 beta's
You won't loose anything, I am on OS X/macOS since the very first beta, I always installed in place, never reinstalled...never.

I'm sorry I did not understand... Every time you update a new Beta before installing do you do a Backup, Install and then Restore? Or do you just upgrade your Mac?

 

[buckrock]

I'm sorry I did not understand... Every time you update a new Beta before installing do you do a Backup, Install and then Restore? Or do you just upgrade your Mac?

I'll chime in here; hope you don't mind.
Always follow "best practices". Backup, then install. Restore is not a step in the upgrade/update. And as justperry advises, until we have a final release, it is easiest and almost just as fast to do a complete install of the newer beta than to mess around with incremental (delta and/or combined) updates. Apple has released InstallAssistant.pkg files for all betas except 7 and 8.

 

[vincenzo79]

I'll chime in here; hope you don't mind.
Always follow "best practices". Backup, then install. Restore is not a step in the upgrade/update. And as justperry advises, until we have a final release, it is easiest and almost just as fast to do a complete install of the newer beta than to mess around with incremental (delta and/or combined) updates. Apple has released InstallAssistant.pkg files for all betas except 7 and 8.

Ok thanks
So the steps are:
1. Backup Time Machine
2. New complete installation
3. Restore from Time Machine ..

But shouldn't the final version of Big Sur be out these days?

 

[justperry]

Ok thanks
So the steps are:
1. Backup Time Machine
2. New complete installation
3. Restore from Time Machine ..

But shouldn't the final version of Big Sur be out these days?

Nope, the Time Machine is just for backup if something isn't working right.
So

Make a backup using TimeMachine.
Download the new full Installer, make a USB Installer with the help of Micropatch.

That's it, it's called "Install in Place" without erasing anything, your files will be safe.

It's rare for a macOS installer to mess up, especially on supported Macs, it's almost always possible to fix macOS without reinstalling.

 

[Mo Haya]

Kexts can be installed in Big Sur so I assume the same SSE 4.2 kext can be used in Big Sur. This won't work if the AMD drivers use more SSE 4.2 instructions. I don't know if anyone has tried.

I'm willing to check if this can be done in Big Sur, but don't know where to begin the kext editing.
I have an R9 Fury that works in Mojave in my Mac Pro 3,1 with the patch applied by Dosdude's patcher. Thanks

 

[buckrock]

Nope, the Time Machine is just for backup if something isn't working right.
So

Make a backup using TimeMachine.
Download the new full Installer, make a USB Installer with the help of Micropatch.

That's it, it's called "Install in Place" without erasing anything, your files will be safe.

It's rare for a macOS installer to mess up, especially on supported Macs, it's almost always possible to fix macOS without reinstalling.

...and as an added bonus, if at anytime after you install your new beta (let's say beta 9) your system starts acting up, simply use BarryKN's instructions (skipping Step 6: micropatcher.sh and Step 7: set-vars.sh) to reinstall (Step 9 may be required) that same beta (beta 9) using the same usb installer and instructions at Step 10. [version 0.3.3]

This is such a great way of correcting errors; always keep the most recent installer and its InstallAssistant.pkg for the chance to resurrect your system. I like it better than trying to restore from a TimeMachine file or even a SuperDuper clone.

 

[David dongfox]

Boot from an USB BigSur Installer recovery and use this ASentientBot method:

diskutil list

(locate your BigSur system diskXs5)

mount -uw /Volumes/YourBigSurLabel

(this makes writable your BigSur system diskXs5)

cd /S*/L*/File*/apfs*/C*/R*/

./apfs_systemsnapshot -v /Volumes/YourBigSurLabel -r ""

(this tags an empty string to disable snapshot booting diskXs5s1 on your BigSur system diskXs5)

If you get an output with "Attempting tagging Volume", at next reboot you should have snapshot booting disabled and so a root System with working "sudo mount -uw /" .

not working. maybe i not understand all the codes you give. but i’ll try again & again.
Thanks

 

[buckrock]

not working. maybe i not understand all the codes you give. but i’ll try again & again.
Thanks

I would suggest that you copy/paste us the output of your first command: diskutil list. That way someone here can make sure you are selecting the correct Big Sur system disk (there are a few now). As for the rest of the commands:
2. mount -uw blah blah
3. cd /S* blah blah ending /R*/
4. ./apfs_systemsnapshot blah blah ending in -r ""

Note A: #2 thru #4 are case-sensitive and depend on spaces/no spaces really a lot!
Note B: the entries like /S*/L*/File* are simply unix shorthand (wildcards) for System, Library, Filesystems, and apfs.fs. *C and *R are Contents and Resources.
Note C: ./apfs_systemsnapshot means in the current directory you navigated to in #3, you are running the executable apfs_systemsnapshot. The rest of that command tells Terminal what to do and what to do it to.

Hope this helps. First though, you need someone to tell you where to find that executable. So post your output. And by all means type very carefully. A small mistake can be catastrophic! I know -- I've done it!

[Edit] Oh yes, the most important thing -- I forgot to say. Use Terminal's tab completition, especially when entering lots of characters. The shell will help you know you are in the right place, since it will complete the phrase or offer choices only if those choices are in the rest of the current working directory or in a link to it. It will also space things correctly. I'd be lost without tab completion. So, as an example in #3 you can type cd /S then hit tab and System/ will suddenly appear!