Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

RogueB

macrumors 6502
Sep 9, 2016
272
471
For non-Metal Nvidia Tesla on BigSur you should replace this package of kext, not only the patched ASentientBot NVDAResmanTesla, in the package is also included the patched ASentientBot GeForceTesla, but it is not included the GLDriver because too big to upload, anyway "brightness control" should work without it, only framebuffer video is required.
[automerge]1595919355[/automerge]


Having an unsealed system volume doesn't imply that you also won't have a snapshot booting (so after installation you still can't use "sudo mount -uw /"), but after using ASentientBot Hax3.app (or HaxLib.dylib) this should work: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28701959


Jackluke,

Understood; tremendous "thank you" for the pointers.

I mounted the Big Sur system folder in "writable" state, as per your post (# 1781 on page 72).
Navigated to Big Sur System/Library/Extension folder, and moved all NVDA-prefixed extensions out of Extension folder, into a desktop folder (for back-up).

Then, navigated to Catalina System/Library/Extensions folder and copied all NVDA-prefixed files into the Big Sur's System/Library/Extension location. I followed the rest of the "closing" commands in your #1781 post.
Rebooted, and all functions, thus far available for Penryn C2D machines on the Big Sur, were available
(The video acceleration is still work in progress, though (?))
 

Attachments

  • Screen Shot 2020-07-28 at 11.02.38.png
    Screen Shot 2020-07-28 at 11.02.38.png
    56.1 KB · Views: 212
  • Screen Shot 2020-07-27 at 14.11.20.png
    Screen Shot 2020-07-27 at 14.11.20.png
    71.3 KB · Views: 176
  • Like
Reactions: macinfo

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
With Big Sur installation after the stage1 installer apple scripts copy the BaseSystem.dmg to this path: /Volumes/BigSurLabel Data/macOS Install Data/ , so eventually should be replaced that path with the patched BaseSystem.dmg .

While stage2 copies some other packages to the Preboot BigSur UUID "com.apple.installer" folder.

I guessed that copied the same "Image Volume" to that path, anyway I don't tested directly this method, but eventually on next beta 4 .

Now that I finally got beta 3 installed without seals or snapshots so the 'sudo mount -uw /' works from a normal boot, I am wondering if you created any directories or symlinks for kextcache to work. My experiments with chroot under snapshots had suggested that the kextcache bundled with Big Sur expects to find /Library/Apple/System/Library/PrelinkedKernels and /Library/Apple/System/Library/Caches which no longer exist in Big Sur. My inclination has been to recreate them with symlink that point at /System/Library/PrelinkedKernels and /System/Library/Caches respectively.
 
  • Like
Reactions: TimothyR734

hvds

macrumors 6502a
Sep 1, 2017
848
2,019
Switzerland
Jackluke,

Understood; tremendous "thank you" for the pointers.

I mounted the Big Sur system folder in "writable" state, as per your post (# 1781 on page 72).
Navigated to Big Sur System/Library/Extension folder, and moved all NVDA-prefixed extensions out of Extension folder, into a desktop folder (for back-up).

Then, navigated to Catalina System/Library/Extensions folder and copied all NVDA-prefixed files into the Big Sur's System/Library/Extension location. I followed the rest of the "closing" commands in your #1781 post.
Rebooted, and all functions, thus far available for Penryn C2D machines on the Big Sur, were available
(The video acceleration is still work in progress, though (?))
Bravo!
That is getting our old MBPs quite close to Catalina functionality already.
Let us hope that video acceleration will be possible.
 

hvds

macrumors 6502a
Sep 1, 2017
848
2,019
Switzerland
It worked, keeping the stock BigSur "dyld_shared_cache_x86_64", I simply replaced the BigSur Privateframeworks CoreBrightness.framework (that essentially is only an alias) with the one from Catalina 10.15.6 and now Night Shift is working on an unsupported MacBook7,1 (@ASentientBot you could test this attached it should work).

Note: the non-metal videoframebuffer drivers are required, and to use any patched framework you need a disabled library validation, you could use nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
(this is already included in my prelinkedkernel fix and USBopencore so there is no need to add it on nvram)

otherwise if you use the stock BootKernelExtensions.kc you can use this ASentientBot method (before replace the framework):
Code:
sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true

while "sudo mount -uw /" is easier but not necessary, is possible to replace the patched framework from another macOS and then make a new snapshot with the replaced framework.

(@hvds you could test it should work also on your MacBookPro5,2 , just replace the framework in ~/Snapshot/System/Library/PrivateFrameworks/ with the same method you used for replacing AppleHDA.kext)

I attach two proof pictures and the CoreBrightness that I patched with pikeralpha method.

This attached should allow Night Shift on any BigSur unsupported mac, use it from BigSur beta 3 or later (because apple from this version changed the IOKit from 10.16 to 11.0 ).
Night Shift is working on MBP5,2.
I've put the 10.15.6 CoreBrightness.framework (from your attachment) into ~/Snapshot/System/Library/PrivateFrameworks/ .
Big thank you!

(BTW the output of mount doesn't show sealed for the previous and new snapshots?)
 

Attachments

  • Bildschirmfoto 2020-07-28 um 21.36.07.png
    Bildschirmfoto 2020-07-28 um 21.36.07.png
    147.6 KB · Views: 142
  • snapshot-bless-2.png
    snapshot-bless-2.png
    178 KB · Views: 173
  • Bildschirmfoto 2020-07-28 um 21.27.09.png
    Bildschirmfoto 2020-07-28 um 21.27.09.png
    156.9 KB · Views: 126

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
I hopefully can make a good patcher soon as I had to erase my ssd all 8gb of ram has gone to swap which leaves me about 600mb left can’t run Big Sur effectively so I reinstalled and installed the sandy bridge prelinked kernel fix no it just reboots so think Big Sur get adaptive to the patches
 

nandor690

macrumors 6502
Jun 25, 2011
374
221
Now that I finally got beta 3 installed without seals or snapshots so the 'sudo mount -uw /' works from a normal boot, I am wondering if you created any directories or symlinks for kextcache to work. My experiments with chroot under snapshots had suggested that the kextcache bundled with Big Sur expects to find /Library/Apple/System/Library/PrelinkedKernels and /Library/Apple/System/Library/Caches which no longer exist in Big Sur. My inclination has been to recreate them with symlink that point at /System/Library/PrelinkedKernels and /System/Library/Caches respectively.
which method have you been using? With ParrotGeek I can't get past the first reboot. And if I press option at boot and manually pick the Installer as it is named it still won't finish the install. Thanks for any help
 
  • Like
Reactions: TimothyR734

ASentientBot

macrumors 6502a
Jun 27, 2018
863
3,421
SkyLight.framework
I should have posted this ages ago, but my old ramdisk patch method to disable snapshots is still working on DP3, with slight changes:
  • The functions to be patched are now located in ramrod itself, not the plugin
  • ramrod's entitlements must be copied into a file and restored when re-signing it after patching, or it can't communicate with IOKit properly and the install fails
As before, there's no real reason to use this method, since easier options exist. But once BaseSystem-level signature checks are disabled, this may be useful in the creation of a fully automatic patcher.

Still working on other stuff, but nothing much to share yet.

Stay safe everybody.
 

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
I want add this Exact name (macOS BigSur HD) to my Installation Disk instead of BS Here

cd /Volumes/Image\ Volume/ && ./set-vars.sh && ./insert-hax.sh && bless -mount /Volumes/BS -setBoot.

Do I need to add "macOS BigSur HD" or Volumes/macOS\ BigSur\ HD -setBoot. ???
I haven't tried it yet because I think it instals on the internal disk just posted it as I found it
 
Last edited:

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
For booting a patched BigSur BaseSystem.dmg from BigSur beta 3 , I use this method, you should try this custom SIP value: w%09%00%00

but before doing this you need csrutil disable otherwise that value is not stored in nvram and the command is only emulated ("csrutil disable" is also required to write on APFS Preboot Volumes).

If SIP is correctly disabled from any macOS (or Recoveries) you should get this output: nvram csr-active-config
w%00%00%00 (with this output you surely can write a next nvram address).

Then after you could use my csrutil2 (copying it on the root) from a Catalina Recovery (or directly from recovery single user mode so without booting the environment) that produces csr-active-config=w%09%00%00 , or you can use your method from Mavericks Recovery nvram csr-active-config=w%09%00%00 (probably from Mavericks Recovery you already have a full nvram write access so you might not need a preset csrutil disable).

Using this should allow to boot any patched BigSur BaseSystem.dmg , I used that method since beta1 and it worked.
THIS WORKED!!! Thank you so much!!! I was able to decompress and recompress BaseSystem.dmg and it still booted. (It seems to boot off the installer USB a bit faster as well, which makes sense given that it doesn't have to authenticate the dmg first.) And I just tried deleting BaseSystem.chunklist and it still boots.

I should still see if I can get a patched boot.efi working, but at least that's no longer a showstopper for me.
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
THIS WORKED!!! Thank you so much!!! I was able to decompress and recompress BaseSystem.dmg and it still booted. (It seems to boot off the installer USB a bit faster as well, which makes sense given that it doesn't have to authenticate the dmg first.) And I just tried deleting BaseSystem.chunklist and it still boots.

I should still see if I can get a patched boot.efi working, but at least that's no longer a showstopper for me.

The challenge now is to make work LegacyUSBInjector.kext on BaseSystem's BootKernelExtensions.kc , because seems there is no way to boot the BaseSystem Recovery environment with prelinkedkernel.

I haven't tried yet the @testheit kmutil method for LegacyUSBInjector.kext , but this might require some additional modification to the "macOS Base System" or its "Preboot".

You could also manual point a BKE on the USB BigSur Installer example attached.
 

Attachments

  • recovery bigsur com.apple.Boot.plist.zip
    918 bytes · Views: 259

Barry K. Nathan

macrumors 6502
Jul 6, 2018
387
1,145
Irvine, CA, USA
I just figured out how to use a patched boot.efi on the installer USB:

sudo bless --folder /Volumes/Install\ macOS\ Big\ Sur\ Beta/System/Library/CoreServices --bootefi /Path/To/Patched/boot.efi

The patched boot.efi does not need to be on /Volumes/Install\ macOS\ Big\ Sur\ Beta -- it will be copied over by bless. Manually copying the patched boot.efi into /Volumes/Install \ macOS\ Big\ Sur\ Beta/System/Library/CoreServices (as opposed to letting bless do it) simply does not work (at least not for me).

Once you run this bless command, you don't need to copy the patched boot.efi anywhere else -- that's it.

Or, if you're doing this to the installer USB while booted from the installer USB (perhaps this is unusual, but it's how I ended up trying it the first time):

mount -uw /Volumes/Image\ Volume
bless --folder /Volumes/Image\ Volume/System/Library/CoreServices --bootefi /Path/To/Patched/boot.efi
 

MacHacJac

Suspended
Jun 28, 2020
214
354
Hey jackluke,
I'm trying very hard to get Big Sur (or even Mojave) on my 2011 MBP via your OpenCoreAPFSloader. When I install it and boot from EFI to the installer, I make it to recovery, but not any further. When I try to install the OS, the drives where I CAN install are grayed out saying "This version of macOS **.**.** cannot be installed on this computer". I tried with USBOpenCoreAPFSloader, no dice. Any suggestions?
 
  • Like
Reactions: TimothyR734

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
Hey jackluke,
I'm trying very hard to get Big Sur (or even Mojave) on my 2011 MBP via your OpenCoreAPFSloader. When I install it and boot from EFI to the installer, I make it to recovery, but not any further. When I try to install the OS, the drives where I CAN install are grayed out saying "This version of macOS **.**.** cannot be installed on this computer". I tried with USBOpenCoreAPFSloader, no dice. Any suggestions?

I don't included the spoof to a supported BigSur Mac enabled by default (it is present on config.plist but disabled), because even if for me worked also the OTA incremental update (tried on some machines), I encountered between stage2 and stage3 installer the big apple logo with loading bar (EFI SMC firmware update loading screen) that only emulated a firmware update, but can't advise it yet as reliable method, so you should instead use Hax3.app or parrotgeek1 BigSur installer or micropatcher.

The USBOpenCoreAPFSloader is intended to boot a BigSur already installed that applies some minimal patches to boot the desktop on non-metal, non-APFS and legacy USB Penryn Core2Duo Mac.
 

jhowarth

macrumors 65816
Jan 13, 2017
1,122
1,500
I don't included the spoof to a supported BigSur Mac enabled by default (it is present on config.plist but disabled), because even if for me worked also the OTA incremental update (tried on some machines), I encountered between stage2 and stage3 installer the big apple logo with loading bar (EFI SMC firmware update loading screen) that only emulated a firmware update, but can't advise it yet as reliable method, so you should instead use Hax3.app or parrotgeek1 BigSur installer or micropatcher.

The USBOpenCoreAPFSloader is intended to boot a BigSur already installed that applies some minimal patches to boot the desktop on non-metal, non-APFS and legacy USB Penryn Core2Duo Mac.

I am still struggling to create as usable prelinked kernel on an unsealed snapshotless installation of beta 3. Using...

sudo mount -uw /
sudo touch /Library/Extensions /System/Library/Extensions
sudo kextcache -i /

produces a prelinkedkernel which still results in the Bluetooth keyboard dialog on boot. I also tried...

sudo kextcache -prelinked-kernel /System/Library/PrelinkedKernels/prelinkedkernel -kernel /System/Library/Kernels/kernel -local-root -- /Library/Extensions/ /System/Library/Extensions/ /System/Library/Extensions/LegacyUSBInjector.kext

with no success. This is on a beta 3 installation performed on a supported machine after which the seal and then the snapshot was removed. Do you find that the available permutations that work for legacy usb is very restricted for building prelinked kernels? One other thing that I noticed on my Catalina machine was that the prelinked kernel doesn't show any obvious indications of LegacyUSBInjector.kext being embedded in it (ie grepping on parrot has no hits unlike with kc's). Do you have any tricks for checking on whether the LegacyUSBInjector.kext has made it into the prelinkedkernel. Oddly, I notice that your own legacy usb beta 1 prelinked kernel doesn't have any grep hits on 'parrot'.
 
Last edited:
  • Like
Reactions: TimothyR734

MacHacJac

Suspended
Jun 28, 2020
214
354
I don't included the spoof to a supported BigSur Mac enabled by default (it is present on config.plist but disabled), because even if for me worked also the OTA incremental update (tried on some machines), I encountered between stage2 and stage3 installer the big apple logo with loading bar (EFI SMC firmware update loading screen) that only emulated a firmware update, but can't advise it yet as reliable method, so you should instead use Hax3.app or parrotgeek1 BigSur installer or micropatcher.

The USBOpenCoreAPFSloader is intended to boot a BigSur already installed that applies some minimal patches to boot the desktop on non-metal, non-APFS and legacy USB Penryn Core2Duo Mac.
Ok. Thanks jackluke. I really appreciate your commitment to this purpose
 

jackluke

macrumors 68040
Jun 15, 2018
3,321
8,068
I am still struggling to create as usable prelinked kernel on an unsealed snapshotless installation of beta 3. Using...

sudo mount -uw /
sudo touch /Library/Extensions /System/Library/Extensions
sudo kextcache -i /

produces a prelinkedkernel which still results in the Bluetooth keyboard dialog on boot. I also tried...

sudo kextcache -prelinked-kernel /System/Library/PrelinkedKernels/prelinkedkernel -kernel /System/Library/Kernels/kernel -local-root -- /Library/Extensions/ /System/Library/Extensions/ /System/Library/Extensions/LegacyUSBInjector.kext

with no success. This is on a beta 3 installation performed on a supported machine after which the seal and then the snapshot was removed. Do you find that the available permutations that work for legacy usb is very restricted for building prelinked kernels? One other thing that I noticed on my Catalina machine was that the prelinked kernel doesn't show any obvious indications of LegacyUSBInjector.kext being embedded in it (ie grepping on parrot has no hits unlike with kc's). Do you have any tricks for checking on whether the LegacyUSBInjector.kext has made it into the prelinkedkernel. Oddly, I notice that your own legacy usb beta 1 prelinked kernel doesn't have any grep hits on 'parrot'.

I just used this:
Code:
sudo mount -uw /
sudo chown -R 0:0 /System/Library/Extensions/
sudo chmod -R 755 /System/Library/Extensions/
sudo kextcache -i /
sudo kmutil install --update-all
sudo kcditto
Now that you have "sudo mount -uw /" I'd advise to remove the telemetry.plugin .

LegacyUSBInjector doesn't show on kextstat, only on System Report loaded Extensions with unknown signature and notarised no.

this is the prelinkedkernel for beta3 to boot legacy USB without CMD+S: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28702758
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.