macOS 11 Big Sur on Unsupported Macs Thread

[thatsmeonlyme]

Yes, after the kexts patch. I patched it from the Big Sur not from the USBoot, and after restart the grey screen happened... So I rebooted from the USB, got into terminal and just used the bless command. After that rebooted a bit longer but with no problem and all working, wifi, airdrop and handoff

the easier way is to patch without booting and directly apply the code. then boot and all is fine. Do it ditrectly from the usb drive after installing.

 

[IbrahimFmc]

I used beta 10 with micro-patcher 0.19 , but also I got same gray screen with mouse pointer only without any progress

 

[thatsmeonlyme]

I used beta 10 with micro-patcher 0.19 , but also I got same gray screen with mouse pointer only without any progress

you‘ve to change the system language to English first and then boot from the USB drive

 

[Joonyv]

Yes, after the kexts patch. I patched it from the Big Sur not from the USBoot, and after restart the grey screen happened... So I rebooted from the USB, got into terminal and just used the bless command. After that rebooted a bit longer but with no problem and all working, wifi, airdrop and handoff

Thanks.. MacBook Air 2012 working just fine on beta 10 with WiFI, Continuity working. Sip is disabled tough. Is it safe no enable? Will it mess anything?

 

[tnsbgs]

a wondering if there any way to make a folder writable on new Beta 10, as it was in all previous beta's versions by removing snapshot and executing sudo mount -uw / ?

 

[gosvamih]

Does anyone know how to set the download with the selected snapshot?
For example: there is a snapshot

diskutil apfs listSnapshots /
com.apple.bless.BD82C376-65C5-476A-9809-F4CFB9C27DA2

I can do

bless --folder /System/Library/CoreServices  --create-snapshot  --bootefi

And this will create a new snapshot
What should be written so that instead of

--create-snapshot

to boot from

BD82C376-65C5-476A-9809-F4CFB9C27DA2

?

 

[tnsbgs]

Is my issue to do with this? - with b10 I can't delete the remaining snapshot from Recovery. Even with the BS System volume mounted and R/W, I get 'Error -69863: Insufficient privileges'. I've managed to delete all snapshots manually up to/incl b9.

After I updated b9 to b10, the usual 'com.apple.update...' sort of snapshot was listed - but with 'Purgeable: No' this time around. I added a newer snapshot and zapped the Apple one with Barry's script. The remaining one I added stated 'Purgeable: Yes' but it still just won't delete.

Any thoughts anyone?

EDIT: I just reapplied the full Beta10 Installer over the injected-into-b9 delta b10 update and I 'can' now delete the initial update snapshot from recovery, leaving none (even though it was flagged as 'Purgeable: No').

Could you describe the removing process exactly how you did it? I still get Error: -69863: Insufficient privileges
Purgeable: No
Deleting APFS Snapshot 0FFE873F-86C8.....
Started APFS operation
Error: -69863: Insufficient privileges

 

[IbrahimFmc]

you‘ve to change the system language to English first and then boot from the USB drive

Yes it is working , Thank You @thatsmeonlyme For Your Support

 

[jackluke]

Hello, I've tried it three times today. I unpacked the InstallAssistand and created a USB stick with installmedia. Then I let the base system Legacy over it. Always the same. Bootet, mouse is visible and can be moved, nothing else. Download the installassistant again tomorrow and try again.

About grey screen on any patched BigSur Installer, the issue as many already reported, is due to the installer language, currently to avoid grey screen should be selected English as main installer recovery language, there are two ways to fix this enough easily:

- reset PRAM, then booting from any CMD+R or USB macOS Installer will show the language selector and pick English
- boot with CMD+R stock recovery (or a stock "USB supported macOS Installer" example El Capitan) then select from menu "File" and "Change Language" picking English

Another way, I also noticed these nvram values (not sure if without PRAM reset, just removing them also applies to reset the main installer language): nvram prev-lang:kbd ; nvram prev-lang-diags:kbd

those should work with: en:0 and en%00 or en-GB:2 and en-GB%00 (and probably other countries where English is the primary language).

 

[Alex-Microsmeta]

@Barry K. Nathan has added scripts to his patcher (and documented them) to modify the root volume without using the old mount -uw /. I have described the method before, too. And I use this method all the time after primary patching from the booted Big Sur when experimenting on the installed system.

The only unknown variable in this method used from the script is the mount point, which is /System/Volumes/Update/mnt1/ when using the patch-kext.sh from a booted Big Sur.

Hi @Ausdauersportler , can I use #3432 workaround alternative to mount -uw / directly from my installed BigSur EXT terminal? Could you specify step by step the instructions focused on Mac mini 2010 (Core 2 Duo Penryn) for enabling USB mouse and keyboard like it was with beta 4?
Thank you!

 

[Ausdauersportler]

Hi @Ausdauersportler , can I use #3432 workaround alternative to mount -uw / directly from my installed BigSur EXT terminal? Could you specify step by step the instructions focused on Mac mini 2010 (Core 2 Duo Penryn) for enabling USB mouse and keyboard like it was with beta 4?
Thank you!

Sorry, I do not own a system like you and never tested Big Sur on such a system. You will have to follow @jackluke.

And it would be great if you share your step by step instructions after succeeding.

 

[Alex-Microsmeta]

Sorry, I do not own a system like you and never tested Big Sur on such a system. You will have to follow @jackluke.

And it would be great if you share your step by step instructions after succeeding.

OK.. I try to apply #3242 inside BigSur Beta 10 terminal because bless xx works only from there to me. Just noticing that on Amazon a Bluetooth compatible mouse costs only 16€ instead of 69-89€ from Apple ?

 

[Franky1971]

About grey screen on any patched BigSur Installer, the issue as many already reported, is due to the installer language, currently to avoid grey screen should be selected English as main installer recovery language, there are two ways to fix this enough easily:

- reset PRAM, then booting from any CMD+R or USB macOS Installer will show the language selector and pick English
- boot with CMD+R stock recovery (or a stock "USB supported macOS Installer" example El Capitan) then select from menu "File" and "Change Language" picking English

Another way, I also noticed these nvram values (not sure if without PRAM reset, just removing them also applies to reset the main installer language): nvram prev-lang:kbd ; nvram prev-lang-diags:kbd

those should work with: en:0 and en%00 or en-GB:2 and en-GB%00 (and probably other countries where English is the primary language).

Hello, yes, that was the problem. NVRAM reset. Then I was shown the language selection, which I switched to English and then it worked. Thank you for your support.

 

[Ghostrider66]

I choose names like BSB10 for this disk in use...

I use this naming scheme as well.

I still have issues using tab for completion when running patch-kexts.sh in recovery mode, this part of of the upgrade keeps giving me grief. eventually i got it to run and am now on beta 10.

yes i have read the methods that are in Barry's micropatcher readme file and have tried all the suggestions mentioned in it

Once again thanks for all the support and help on here and the people involved in the programming to make this happen.

 

[Alex-Microsmeta]

Success updating BS beta 9 to 10 on Macmini 2010. The only difference from Beta 9 seems the wallpaper 😂
using hax3 to install it from Catalina to avoid gray screen, then applying 0.3.2 USB micropatcher to remove telemetry.
@jackluke @Barry K. Nathan I have managed to rebuild kexts doing that as suggested by @Ausdauersportler from inside BS B10: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28799574 If it could be used to inflate kexts on Core 2 Duo Penryn, but still no USB mouse and keyboard. Bluetooth, Wifi, internal audio, ethernet usb webcam and mic are OK.

1: APFS Volume ⁨BigSur EXT - Dati⁩ 15.2 GB disk7s1
2: APFS Volume ⁨Preboot⁩ 327.2 MB disk7s2
3: APFS Volume ⁨Recovery⁩ 655.1 MB disk7s3
4: APFS Volume ⁨VM⁩ 1.1 MB disk7s4
5: APFS Volume ⁨BigSur EXT⁩ 15.5 GB disk7s5
6: APFS Snapshot ⁨com.apple.bless.AB36...⁩ 15.5 GB disk7s5s1

alex@Mini-di-alex ~ % sudo mkdir /Volumes/ROOT
Password:
alex@Mini-di-alex ~ % sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/ROOT
alex@Mini-di-alex ~ % sudo chown -R 0:0 /Volumes/ROOT/System/Library/Extentions
alex@Mini-di-alex ~ % sudo chmod -R 755 /Volumes/ROOT/System/Library/Extensions
alex@Mini-di-alex ~ % sudo kmutil install --update-all --volume-root /Volumes/ROOT
checking collections...
Warning: com.apple.driver.KextExcludeList was not found!

updated extension 'com.promise.driver.stex' found on disk at '/Volumes/ROOT/System/Library/Extensions/PromiseSTEX.kext' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)

updated extension 'com.Areca.ArcMSR' found on disk at '/Volumes/ROOT/System/Library/Extensions/ArcMSR.kext' (mach-o UUID changed from <unknown> to 01FC5EBD-0A34-3E77-9216-53B89DDD8CE4)

updated extension 'com.apple.driver.usb.AppleUSBVHCICommonRSM' found on disk at '/Volumes/ROOT/System/Library/Extensions/AppleUSBCommon.kext/Contents/PlugIns/AppleUSBVHCICommonRSM.kext' (mach-o UUID changed from <unknown> to 983BD0E8-C3D2-3035-82FA-4791749754CB)

rebuilding release collections: boot, system

rebuilding release collections:

boot kernel collection

system kext collection

rebuilding local auxiliary collection

kmutil done

alex@Mini-di-alex ~ %

 

[borp99]

Could you describe the removing process exactly how you did it? I still get Error: -69863: Insufficient privileges
Purgeable: No
Deleting APFS Snapshot 0FFE873F-86C8.....
Started APFS operation
Error: -69863: Insufficient privileges

As updated in my last post, I had to create a fresh USB installer from the B10 full download (http://swcdn.apple.com/content/down...ff81a690twrhri7k2vlmpkti/InstallAssistant.pkg), not the earlier delta update, then patched it with Barry K. Nathan's (0.4.1) micropatcher and then installed it over the top of the OS you're getting the -69863 error message on. Once done, boot into Recovery, mount your BS System volume with -uw / and use the 'diskutil apfs deleteSnapshot xxxxxxxetc --uuid xxxxxxetc' as you've tried before. Hopefully it will work this time.

 

[MacPeet]

Im there again, native without Micropatcher on the MacPro3,1 and everything works.

 

[Pinarek]

@MacPeet Such a nonsense .. can not work!

 

[tnsbgs]

...patched it with Barry K. Nathan's (0.4.1) micropatcher and then installed it over the top of the OS you're getting the -69863 error message on.

Thanks M8, I have already USB with latest B10 and I just dowloaded (0.4.1) micropatcher, but how to patch "usb installer"
is there step by step info?

 

[Ausdauersportler]

Thanks M8, I have already USB with latest B10 and I just dowloaded (0.4.1) micropatcher, but how to patch "usb installer"
is there step by step info?

Yes, the doc is on the github page you got the micro patcher from. Step by step!

 

[Ausdauersportler]

Success updating BS beta 9 to 10 on Macmini 2010. The only difference from Beta 9 seems the wallpaper 😂
using hax3 to install it from Catalina to avoid gray screen, then applying 0.3.2 USB micropatcher to remove telemetry.
@jackluke @Barry K. Nathan I have managed to rebuild kexts doing that as suggested by @Ausdauersportler from inside BS B10: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28799574 If it could be used to inflate kexts on Core 2 Duo Penryn, but still no USB mouse and keyboard. Bluetooth, Wifi, internal audio, ethernet usb webcam and mic are OK.

1: APFS Volume ⁨BigSur EXT - Dati⁩ 15.2 GB disk7s1
2: APFS Volume ⁨Preboot⁩ 327.2 MB disk7s2
3: APFS Volume ⁨Recovery⁩ 655.1 MB disk7s3
4: APFS Volume ⁨VM⁩ 1.1 MB disk7s4
5: APFS Volume ⁨BigSur EXT⁩ 15.5 GB disk7s5
6: APFS Snapshot ⁨com.apple.bless.AB36...⁩ 15.5 GB disk7s5s1

alex@Mini-di-alex ~ % sudo mkdir /Volumes/ROOT
Password:
alex@Mini-di-alex ~ % sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/ROOT
alex@Mini-di-alex ~ % sudo chown -R 0:0 /Volumes/ROOT/System/Library/Extentions
alex@Mini-di-alex ~ % sudo chmod -R 755 /Volumes/ROOT/System/Library/Extensions
alex@Mini-di-alex ~ % sudo kmutil install --update-all --volume-root /Volumes/ROOT
checking collections...
Warning: com.apple.driver.KextExcludeList was not found!

updated extension 'com.promise.driver.stex' found on disk at '/Volumes/ROOT/System/Library/Extensions/PromiseSTEX.kext' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)

updated extension 'com.Areca.ArcMSR' found on disk at '/Volumes/ROOT/System/Library/Extensions/ArcMSR.kext' (mach-o UUID changed from <unknown> to 01FC5EBD-0A34-3E77-9216-53B89DDD8CE4)

updated extension 'com.apple.driver.usb.AppleUSBVHCICommonRSM' found on disk at '/Volumes/ROOT/System/Library/Extensions/AppleUSBCommon.kext/Contents/PlugIns/AppleUSBVHCICommonRSM.kext' (mach-o UUID changed from <unknown> to 983BD0E8-C3D2-3035-82FA-4791749754CB)

rebuilding release collections: boot, system

rebuilding release collections:

boot kernel collection

system kext collection

rebuilding local auxiliary collection

kmutil done

alex@Mini-di-alex ~ %

@jackluke already wrote once in this post which kext to install. Unless you put the kext into the /Volumes/ROOT/System/Library/Extentions after the mount and before the chmod and chown you will not see any changes.
I guess this should fix your problem?

Edit:
And you need to create a new bootable snapshot after the kmutil call. I do not know if your command list is complete. But this changed surely nothing.

 

[MacPeet]

@MacPeet Such a nonsense .. can not work!

As always you have no idea, Pinarek !!! 👎

 

[tnsbgs]

Yes, the doc is on the github page you got the micro patcher from. Step by step!

I didn't understand if install-setvars.sh is also needed for this situation or is micropatcher.sh just enough, did you installed it too?

 

[Pinarek]

As always you have no idea

As always you have no idea @MacPeet 👎👎👎

 

[Alex-Microsmeta]

@jackluke already wrote once in this post which kext to install. Unless you put the kext into the /Volumes/ROOT/System/Library/Extentions after the mount and before the chmod and chown you will not see any changes.
I guess this should fix your problem?

Edit:
And you need to create a new bootable snapshot after the kmutil call. I do not know if your command list is complete. But this changed surely nothing.

I need help to do that. I don't know if there are different LegacyUSBInjector.kext, from where I can download them (I have searched on Catalina /System/Library/Extensions) and how to create a new snapshot...