macOS 11 Big Sur on Unsupported Macs Thread

[Barry K. Nathan]

I ain’t lucky no more. When I succeeded to download the beta 9 with cURL command and Catalina usb , I’m not able now to patch

A while back, I mentioned the idea of running a memory test. Earlier today I had a chance to try running memtest86+ on my Early 2011. This is how to do it:
1. Download the memtest86+ ISO: https://www.memtest.org/download/5.01/memtest86+-5.01.iso.gz
2. Find it in your Downloads folder.
3. If it's called "memtest86+-5.0.1.iso.gz", double-click it so it decompresses and you get "memtest86+-5.0.1.iso". Once you have that file, right-click or Control-click it and choose to Burn it to disc. You will need a blank CD or DVD; it's small, so it will burn faster onto a blank CD, and you may as well burn it at the slowest speed that it will let you, just to be safe.
4. Once it's done burning onto CD, reboot while holding down Option. It should show up as a CD called "Windows". Start that up. (It's not really Windows, but it's not EFI-based and it's not macOS so the EFI firmware just calls it "Windows".)
5. Once you choose to start it up, the computer may look like it's frozen for several seconds. However, after that, it should switch to a screen with white text on a blue background. At that point, memtest86+ is now running but it won't respond to keyboard input. It will automatically do the right things on its own, so that's not a problem.

Let it run for at least 1 pass, ideally 2 (or more) passes. This may take several hours. (There's no harm in letting it run longer than 2 passes, so if you can deal with the screen light and fan noise, you can just run it overnight.) Once it has finished at least 2 passes, or once it's showing errors (if that happens earlier), take a photo of the screen, then get out of memtest86+ by holding down the Power button to turn the Mac off.

I figured out what happened with kmutil -- the error messages got a lot less informative in beta 9, but running beta 8's kmutil still shows detailed error messages. Eventually I think I'll add an option to patch-kexts.sh to use beta 8's kmutil, to make troubleshooting easier.

 

[Barry K. Nathan]

I have released Big Sur Micropatcher v0.3.3. Release notes:

This is a very minor release. I considered calling it v0.3.2a. If you have already installed and patched Big Sur beta 9 successfully, there is no need to update to this patcher release.

The biggest change in this release is actually the improvements to the README; thanks in particular to thatsmeonlyme and treee111 for their feedback. Also, a bug has been fixed in error handling code in install-setvars.sh thanks to Ben Sova. In addition, if micropatcher.sh is run on a USB that already has some version of this patch, it will automatically use unpatch.sh before continuing, as opposed to the previous behavior of asking the user to run unpatch.sh. Finally, there are some more code cleanups and preparations for future patcher improvements.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

 

[Barry K. Nathan]

Hi, installing DB9 using latest micro patcher I am getting com.apple.disk management.dissenter error 49168.. on first reboot. I followed every instruction mentioned by Berry. Please help.

I've only had this happen once, and I just tried rebooting and the installation continued and finished successfully. If that doesn't work, just try starting the installation over. (For what it's worth, this is an error that has also happened on supported Macs, at least with earlier Big Sur betas.)

 

[elise_s1]

If you are talking about the iMac in your signature give this thread a try, both the BCM94360CD and the BCM943602CDP
...
Both cards work perfectly with High Sierra, Mojave and Catalina, but your 2010 iMac will probably not run Big Sur...

thanks. I asked because I already have a spare AX200 here (it also looks dimensionally identical to the old Broadcom).

 

[ykokosh]

http://swcdn.apple.com/content/down...2h830qlq8eiiokbzccrxlacl/InstallAssistant.pkg

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

 

[Tech Enthusiasm]

Hi,


I have been trying to install macOS Big Sur on my 2010 Mac Pro using the barrykn big sur micropatcher. I successfully patched the USB stick by running "micropatcher.sh" and “install-setvars.sh”. Booting from "EFI Boot"on the mac startup selector makes the machine shut down which is normal when the setvars EFI utility makes the necessary changes to the Mac's NVRAM settings. After I started up from "EFI Boot" the computer shut down. I then started up from "Install macOS Big Sur Beta”, but the machine just restarts when I try to boot from that. Also, I am using the stock ATI Radeon 5770 graphics card (I do have a metal supported graphics card, but I am using the 5770 to get a boot screen temporarily), but I don’t know if that is the problem. Any help will be much appropriated.


Thank you

 

[telepati]

Guys I am trying to open Preboot Volumes with this code and Preboot Volumes looks mounted but when I try to open it, it says 'No such file or directory'. WHY is that?

sudo -s
diskutil mount disk2s2
cd /Volumes/Preboot
open .

 

[jackluke]

Guys I am trying to open Preboot Volumes with this code and Preboot Volumes looks mounted but when I try to open it, it says 'No such file or directory'. WHY is that?

sudo -s
diskutil mount disk2s2
cd /Volumes/Preboot
open .

View attachment 962629

From BigSur the default mount point for Preboot is : /System/Volumes/Preboot/

at least csrutil disable is required to access Preboot folder with read and write permissions also from Catalina or Mojave.

 

[justperry]

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

Go to Micropatcher, that's all.

 

[telepati]

From BigSur the default mount point for Preboot is : /System/Volumes/Preboot/

at least csrutil disable is required to access Preboot folder with read and write permissions also from Catalina or Mojave.

Thank you @jackluke you are a savior as always ?

 

[Ghostrider66]

Hi i came accross a problem. After running set-vars on the usb key in recovery mode in terminal and reboot and holding option key the usb installer does not show in the list. I have to boot in to catalina and restart and the usb installer shows up then. Once again thanks to everyone here i now have beta 9 on my macbook pro mid 2012. It was also great to see wifi working automatically showing list of wifi in the area in MacOS setup assistant

 

[justperry]

Hi i came accross a problem. After running set-vars on the usb key in recovery mode in terminal and reboot and holding option key the usb installer does not show in the list. I have to boot in to catalina and restart and the usb installer shows up then. Once again thanks to everyone here i now have beta 9 on my macbook pro mid 2012. It was also great to see wifi working automatically showing list of wifi in the area in MacOS setup assistant

Why you ask if you already have b9 running on your mac.

 

[Barry K. Nathan]

Why you ask if you already have b9 running on your mac.

No, it's a good question for them to ask!!

Sometimes the Startup Selector will fail to show a USB stick for whatever reason. In my experience, unplugging and replugging the USB stick makes it show up. For v0.3.4 I've updated the README to note this in step 10.

 

[Barry K. Nathan]

Hi,


I have been trying to install macOS Big Sur on my 2010 Mac Pro using the barrykn big sur micropatcher. I successfully patched the USB stick by running "micropatcher.sh" and “install-setvars.sh”. Booting from "EFI Boot"on the mac startup selector makes the machine shut down which is normal when the setvars EFI utility makes the necessary changes to the Mac's NVRAM settings. After I started up from "EFI Boot" the computer shut down. I then started up from "Install macOS Big Sur Beta”, but the machine just restarts when I try to boot from that. Also, I am using the stock ATI Radeon 5770 graphics card (I do have a metal supported graphics card, but I am using the 5770 to get a boot screen temporarily), but I don’t know if that is the problem. Any help will be much appropriated.


Thank you

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

 

[air.man]

Hi, I applied the Barry's micropatcher 0.3.3 on my MBP 8,2 15' 2011 successfully. Then I would like to enable the system modification. I tried to run the script provided by Barry and I got

Install macOS Big Sur Beta % /Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh
csr-active-config appears to be set incorrectly:
csr-active-config    %7f%08%00%00

To fix this, please boot the setvars EFI utility, then boot back into macOS
and try again.

Of course I did the EFI boot again, but I got the same.
Any suggestion?

Update
I booted by USB stick and did both the csrutil disable commands by terminal successfully. But the script failed again.

 

[Ghostrider66]

Why you ask if you already have b9 running on your mac.

I was only letting people know the issue i was having. I tried the removing and reinserting the USB trick but it did not work for me. The biggest issue i had was running the the patch-kexts command in terminal in recovery mode.

/Volumes/Image\ Volume/patch-kexts.sh /Volumes/BSB9

Tab wasnt working for me. It kept failing to find my big sur volume. I dont know what i did to get it to work eventually.

 

[Caeed]

No, this will not be solved in the final Big Sur release. Right now, this is inherent to running Big Sur on a 2011 MacBook Pro (it's actually much much worse on 2010 MacBooks, in my experience). When people say there's "no graphics acceleration" on non-Metal GPUs with Big Sur, this is what they're warning about.

For the foreseeable future, this is as good as Big Sur is going to be on 2011 MacBook Pros. (Edit: Go to System Preferences->Accessibility->Display and try turning on Reduce Transparency, Reduce Motion, maybe Increase Contrast as well. Also try running the disable-animations.sh script that comes in the misc-scripts folder of the patcher. Those steps will improve performance a little bit, but you will probably still find it to be unacceptable.)

To the best of my knowledge, there is still work being done by some other patch developers to try to fix this, to try to bring graphics acceleration to non-Metal GPUs on Big Sur, but it's very difficult work, it could turn out to be infeasible in the end, and if it is feasible it could take a while. I personally believe it would be prudent to assume it won't happen and make decisions accordingly -- that way, if it actually happens, it will be a very happy surprise, and if it doesn't, at least you'll still be prepared. (If anyone involved in this work believes that I am mischaracterizing the situation, please speak up and correct me!)

Thanks for your kind reply

 

[Barry K. Nathan]

Hi, I applied the Barry's micropatcher 0.3.3 on my MBP 8,2 15' 2011 successfully. Then I would like to enable the system modification. I tried to run the script provided by Barry and I got

Install macOS Big Sur Beta % /Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh
csr-active-config appears to be set incorrectly:
csr-active-config    %7f%08%00%00

To fix this, please boot the setvars EFI utility, then boot back into macOS
and try again.

Of course I did the EFI boot again, but I got the same.
Any suggestion?

Update
I booted by USB stick and did both the csrutil disable commands by terminal successfully. But the script failed again.

Oops, bugs in the scripts, sorry. I'll see if I can fix them later this weekend.

 

[Barry K. Nathan]

I tried the removing and reinserting the USB trick but it did not work for me.

Whenever I've seen that (removing and reinserting the USB stick doesn't work at the Startup Selector), it has usually been a USB stick that's on its way out.

 

[David dongfox]

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

 

[Ghostrider66]

Thanks Barry. FYI it was micropatcher 0.3.2 i used. 0.3.3 and 0.3.4 came out after i was finished working on my Macbook. I have read the Readme file in 0.3.4 with the newly added section on how to run the patch-kext script. Hopefully it will help me in beta 10. Its a pity you cant copy and paste from the readme file while in terminal in recovery mode the path /Volumes/Image\ Volume/patch-kexts.sh /Volumes/ and just type the big sur volume at the end

 

[Ausdauersportler]

Thanks Barry. FYI it was micropatcher 0.3.2 i used. 0.3.3 and 0.3.4 came out after i was finished working on my Macbook. I have read the Readme file in 0.3.4 with the newly added section on how to run the patch-kext script. Hopefully it will help me in beta 10. Its a pity you cant copy and paste from the readme file while in terminal in recovery mode the path /Volumes/Image\ Volume/patch-kexts.sh /Volumes/ and just type the big sur volume at the end

The magic solution is tab completion within terminal...one should get used to terminal in the future, we are on our way to own more a Hackintosh than a supported Mac. It helps!

 

[justperry]

Thanks Barry. FYI it was micropatcher 0.3.2 i used. 0.3.3 and 0.3.4 came out after i was finished working on my Macbook. I have read the Readme file in 0.3.4 with the newly added section on how to run the patch-kext script. Hopefully it will help me in beta 10. Its a pity you cant copy and paste from the readme file while in terminal in recovery mode the path /Volumes/Image\ Volume/patch-kexts.sh /Volumes/ and just type the big sur volume at the end

It is possible but would be considerably typing.

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

It tells you right there on the picture, it's a System Snapshot.

 

[David dongfox]

It is possible but would be considerably typing.



It tells you right there on the picture, it's a System Snapshot.

so why got is System Snapshot came up ? how to get back to my original system disk like picture 2 ?

 

[jackluke]

so why got is System Snapshot came up ? how to get back to my original system disk like picture 2 ?

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 /" .