Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Upgraded iMac 13,2 (27 inch, late 2012, HD- fusion drive)

Used Barry's K. Nathan's patcher 0.1.0 to create USB stick with patched Big Sur beta 6. Installation went smoothly; Airdrop , Handoff and Hostspot fully functional. It was a clean install on reformatted (empty) partition.

Had to reformat partition containing Beta 5 when message appeared, that there was not enough space to complete install. There was a note from B.K. Nathan, in previous posts, that implied "not enough disk space ... to install..." message, might be an issue with the patcher (?)

When installing, make sure to follow B.K. Nathan's instructions carefully, e.g., when instructions direct to quit "installer assistant", and shut down the Mac, do so.

Did not try to upgrade MacBook Pro 5,2 from beta 4, given lack of graphical acceleration.

Thank you to all developers, who have made the BIgSur viable on the "abandoned" Macs.
 

Attachments

  • Screen Shot 2020-09-04 at 1.54.51 PM.png
    Screen Shot 2020-09-04 at 1.54.51 PM.png
    115.2 KB · Views: 411
  • Screen Shot 2020-09-04 at 2.33.01 PM.png
    Screen Shot 2020-09-04 at 2.33.01 PM.png
    18.5 KB · Views: 308
  • Like
Reactions: TimothyR734 and Ausdauersportler
Successfully installed on Late 2013 27" iMac. Had to manually set args and csrutil disable a few times to get it accepted to run. I think with filevault turned on, it's best to go to disk utility and make sure the disks are mounted and unlocked first. Unlocking during install did not work. Then after making sure they were unlocked, that didn't work either. So, making sure they were unlocked, mounted, then running args and csrutil, I was able to get install to work.
 
  • Like
Reactions: TimothyR734 and Ausdauersportler
Ausdauersportler said:
Installation of the Beta 6 on my iMac 2011 / 780M / BCM94360CD with a modified @Barry K. Nathan micro patcher done....

After patching the USB installer put in the iMac2011Family-highvoltage12v.zip into the kexts folder on the patched USB installer and unzip the new patch-kexts-iMac-2011.sh.zip and put it at the same spot where you find the patch-kexts.sh provided by @Barry K. Nathan (version 0.1.0).

Follow exactly the guide @Barry K. Nathan created, just call the new patch-kexts-iMac-2011.sh instead of the stock patch-kexts.sh. Call the script while booted into Big Sur on your iMac. The new script needs a working OS to check the card type (NVIDIA Kepler or AMD Polaris).

Have fun! You may also check my first post about this mods...

Code: 
install@WolfsiMac27 ~ % /Volumes/Install\ macOS\ Big\ Sur\ Beta/patch-kexts-iMac-2011.sh --2011-iMac-no-wifi
Password:
Installing iMac-2011, AppleHDA, HD3000, and LegacyUSBInjector to:
/
Volume appears to have a Big Sur installation (build 20A5364e). Continuing.
Volume is mounted from device:  /dev/disk5s1s1
Mounted device is a snapshot. Will now mount underlying volume
from device /dev/disk5s1 at temporary mountpoint:
/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ
Installing High Sierra AppleHDA.kext
Installing High Sierra Intel HD 3000 kexts
Installing LegacyUSBInjector.kext
Installing Catalina AppleBCM5701Ethernet.kext
Installing highvoltage12v patched iMac-2011-family.kext
NVIDIA Kepler based graphics adapter found
Using stock NVIDIA compatible version of AppleIntelSNBGraphicsFB.kext
Using kmutil to rebuild boot collection...
Using kmutil to rebuild system collection...
Copying deferred prelinked kernels in /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.3/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7fe82450a990 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-692.40.3/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
    Folder
), NSUnderlyingError=0x7fe824610cb0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ...
System Volume UUID: 9697E05A-6962-447B-92AE-D551BB842748
Volume Group UUID: 04B26AE3-BE22-4DDD-95F9-DD96527E06BC
Preboot disk: /dev/disk5s2
Preboot volume: /System/Volumes/Preboot
Copying: /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/04B26AE3-BE22-4DDD-95F9-DD96527E06BC/boot/System/Library/KernelCollections
Copying:
/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/04B26AE3-BE22-4DDD-95F9-DD96527E06BC/boot/System/Library/KernelCollections
Copying: /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/System/Library/PrelinkedKernels/immutablekernel -> /System/Volumes/Preboot/04B26AE3-BE22-4DDD-95F9-DD96527E06BC/System/Library/PrelinkedKernels
Copying: /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ/System/Library/PrelinkedKernels/prelinkedkernel -> /System/Volumes/Preboot/04B26AE3-BE22-4DDD-95F9-DD96527E06BC/System/Library/PrelinkedKernels
Creating new root snapshot.
Attempting to unmount underlying volume (don't worry if this fails).
This may take a minute or two.
umount(/private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/tmp.qYEeldqJ): Resource busy -- try 'diskutil unmount'
Volume BSAMD on disk5s1 failed to unmount: dissented by PID 0 (kernel_task)
Installed patch kexts successfully.
install@WolfsiMac27 ~ %
Click to expand...

Would this approach work on a MacPro 2008 with GTX680 and BCM94360CD as well?
 
  • Like
Reactions: TimothyR734 and thatsmeonlyme
amaze1499 said:
Had the same (expected) issue on MBP 13" mid2012. You need to run the installation from a micropatched USB installer. Follow Barry K's instructions.
Click to expand...
I did that but it keeps saying the usb installer which is a brand new Samsung evo internal ssd disk is locked after I patch the micro installer can u help please
 
  • Like
Reactions: TimothyR734
lowercaseman said:
Successfully installed on Late 2013 27" iMac. Had to manually set args and csrutil disable a few times to get it accepted to run. I think with filevault turned on, it's best to go to disk utility and make sure the disks are mounted and unlocked first. Unlocking during install did not work. Then after making sure they were unlocked, that didn't work either. So, making sure they were unlocked, mounted, then running args and csrutil, I was able to get install to work.
Click to expand...
 
  • Like
Reactions: TimothyR734
Will350 said:
I did at first and posted here the picture came out the data was not found and I ignore that trying to installed the big sure patch and always got stuck at 12 minutes with forbidden sign and shutdown by itself and here's the picture attached and thanks to you and Perry was trying to help me solve this issue
Click to expand...

You may have to erase the USB and start from fresh, just follow Barry's micro patchers instructions step by step you will get it.
 
  • Like
Reactions: TimothyR734
maxsp97 said:
You may have to erase the USB and start from fresh, just follow Barry's micro patchers instructions step by step you will get it.
Click to expand...

I did erase it start fresh still same same issue and i did on my brother macbook pro they don’t have those nvram error boot arg data not found and it works smooth.
 
  • Like
Reactions: TimothyR734
TQ for All
MBP 2012 BS B6 Work Ok
Use Micropatcher 0.0.19
 

Attachments

  • Screen Shot 2020-09-05 at 08.37.45.png
    Screen Shot 2020-09-05 at 08.37.45.png
    835.6 KB · Views: 255
  • Like
Reactions: TimothyR734
Updated from beta 4 to beta 6. I have an annoying issue in Recovery that my volume is "unknown special file or system". I also see the volume is no longer writable which probably means it has sealed itself. I ran the proper set-vars.sh at the beginning before the install. Anyway to unseal the volume again?
 

Attachments

  • IMG_20200904_225605__01__01.jpg
    IMG_20200904_225605__01__01.jpg
    714.6 KB · Views: 294
  • IMG_20200904_225825.jpg
    IMG_20200904_225825.jpg
    876 KB · Views: 259
  • IMG_20200904_230641.jpg
    IMG_20200904_230641.jpg
    952.4 KB · Views: 225
  • Like
Reactions: TimothyR734
highvoltage12v said:
Updated from beta 4 to beta 6. I have an annoying issue in Recovery that my volume is "unknown special file or system". I also see the volume is no longer writable which probably means it has sealed itself. I ran the proper set-vars.sh at the beginning before the install. Anyway to unseal the volume again?
Click to expand...


The "unknown special file or system" message has been addressed in one of the previous posts in this thread.
Attached is a copy of the response which solved this message problem.
Please note, that credit for this workaround belongs to the original author of the excerpt I included in the post.

You do have to identify the disk ID on your drive and substitute for the "disk2s5" entry. Hope this may be of help.

From USB BS Installer Recovery Terminal:
diskutil mount disk2s5
Volume Big Sur on disk2s5 mounted

terminal command ==> mount -uw /Volumes/Big\ Sur/.
system response ==> mount: unknown special file or file system /Volumes/Big Sur/.

Workaround (message):

Regarding the "unknown special file or file system" issue,
I had the same issue. However it did work for me when I put the path within quotation marks.
mount -uw "/Volumes/Big Sur"
 
  • Like
Reactions: highvoltage12v, TimothyR734 and macinfo
reset nvram will make already exist Mac os big sur fail to start
 

Attachments

  • macos-startup-screen-prohibitory.jpg
    macos-startup-screen-prohibitory.jpg
    64.2 KB · Views: 206
  • Like
Reactions: TimothyR734
amaze1499 said:
Same hardware here. However Airdrop does not even show up in Finder. I used micro patcher 0.1.0. iCloud Desktop/Documents syncing enabled.
Click to expand...

Hey! you should download the patcher 0.0.19, use the unpatch on the USB boot and repatch it with 0.0.19. After reboot from the USB and run kexts.sh comand (the one with \Volumes\ Image...). It will give you handoff and airdrop ;)
 
  • Like
Reactions: IbrahimFmc, TimothyR734, thatsmeonlyme and 1 other person
justperry said:
Because it is wrong, it is

/Volumes/Image\ volume/set-vars.sh -v

Not

/Volumes/Image/ volume/set-vars.sh -v

You see the difference...?
Click to expand...

forward slash is the wrong one, i did installled beta 4 and 5 before for some reason can’t install it now ,i was using beta 5 and reset the nvram then i lost it trying to re-install using usb but “nvram error boot arg not found”
 
  • Like
Reactions: TimothyR734
Will350 said:
forward slash is the wrong one, i did installled beta 4 and 5 before for some reason can’t install it now ,i was using beta 5 and reset the nvram then i lost it trying to re-install using usb but “nvram error boot arg not found”
Click to expand...

Huh
it's this one "/Volumes/Image\ volume/set-vars.sh", that's it, not going to argue.
If you use the other one it's not going to work, period.
 
  • Like
Reactions: TimothyR734 and webg3
justperry said:
Huh
it's this one "/Volumes/Image\ volume/set-vars.sh", that's it, not going to argue.
If you use the other one it's not going to work, period.
Click to expand...

i did use the correct one man cause i use yesterday with my brother 2012 macbook pro lol it just happened won’t work anymore on my imac
 
  • Like
Reactions: TimothyR734
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back