barrykn / big-sur-micropatcher Goto Github PK

Hey, booting beta 9 I get as far as a gray screen with "Language Chooser" in the menu bar. No mouse pointer although it does appear/disappear earlier.
Is there a log file somewhere that would help?

I am in exact same situation. Command in Step 6 fails with no file of directory.

ls /Volumes does not show Image Volume

Attached what I see in the USB booter file system

In the terminal run ls /Volumes (or cd /Volumes && ls).

It shows all the currently mounted volumes. Image Volume should be one of them.

If it's not then write all the drives listed into the comments, otherwise I have something else I would like you to do. (Both should help find the error.)

Originally posted by @bensova in #6 (comment)

Note: Still using patcher 0.0.19

In the tortuous road to accomplish this, i'm using a 2014 macbook pro and using the disk from the 2012 macbook pro as external disk. When booting the patched disk on the "new macbook" i get a kernel panic. Unpatching the disk didn't help. Then i read the comment about the snapshots, so i used the zap snapshots script and that solved the problem but introduced a new one. When running software update and trying to update to the new beta, i got the message ¨This system can't be updated because it is not snapshot booted", so we need a snapshot after all. Reinstalling beta 6 over the old beta6 installation fixed the issue. Then applied the beta updates via software update.
After updating the disk, it boots fine on the 2012 mac without any patches, of course with no wifi. Then applied the patch, everything's still fine and wifi enabled.

The real challenge is updating the release without using supported machines. Somebody has to know how to use the zip files downloaded in the update procedure. Here are the deltas from beta 8 to beta 9. You can find the deltas from beta 6 to beta 8 in issue #45
Link1
Link2

I had to reset my macs PRAM to fix an issue in bootcamp but now my big sur volume shows a prohibitory sign when attempting to boot. I don’t have any Catalina backups as I don’t have an external drive and I don’t really want to have to lose my installation

Hi, I have followed all the readme steps and this method is not working for me. After doing set-vars I tried to install the OS as if mac had official support and it shows me the following error "Installation of mac cloud not continue". Attached photo of the error and my mac model.

Last week I install Big Sur on iMac Late 2013 and the Mac shown the a circle with a prohibitory symbol (a circle with a line or slash through it). Did I do something wrong? TIA.

Has anyone tried installing with beta5?

There are some typos I noticed in the README (the numbers are what step they are under):

1. Step One says to obtain a copy of the Big Sur Developer Preview, but now that the public beta is out it should say something like Big Sur Beta Install.
2. It says that if you did not use Disk Utility in step 5, but that makes no since so you should replace the 5 with a 3...
3. Image Volume should have a \ after Image

Dear Barry,
I have my early 2011 Macbook Pro 13 inch 12GB ram
I want to install big sur
is it possible ?

I was able to install on late 2013 21” iMac and is working great. But when iMac is booting the boot log is in the screen. Is possible to make the log not appear when booting?

Dear Barry,

First of all, congratulate for your incredible work!

I'm trying to install Big Sur Public Beta 1 in my MBP8,1. Aside from the original, I've just replaced my network card with the following:
Card Type: AirPort Extreme (0x14E4, 0xF5)
Firmware Version: Broadcom BCM43xx 1.0 (7.21.190.33 AirPortDriverBrcm4360-1325.2)

Every time I try do patch the kexts following your readme steps, I get the following message:

Could please advise on how to proceed?

Thanks in advance!

regards!

Does iCloud work? On other patchers I would have everything working and the minute I would sign into iCloud it would always crash.

All seemed to go well apart from this resulting issue.

There’s a little typo in readme, recvoery doesn’t make any sense

Before I install this patch, I would like to know if you have any problems installing this on 2010 13" model.

Is graphics acceleration working on this model?

Basically everything works smoothly until i step 6 and i'm stuck there.. I'm using MBP Early 2013

Maybe a problem in general but my MacBook Pro Late 2012 13,3 runs very sluggish (graphic).
Is this Big Sur or the patcher?

Thanks!

Apple tweaked nvram in Beta 5 to silently fail when attempting to set boot-args.

This isn't a problem if you have it set from a previous beta, but set-vars.sh will produce an error and the install will not boot.

Tested by wiping NVRAM with Cmd-Opt-P-R. Booting the installer and trying 'nvram boot-args -no_compat_check' from terminal will produce no error but boot-args will not be set.

Workaround is to use any other bootable disk or Internet Recovery to set it.

This is just a finding:
I found that enabling Reduce Motion improves performance substantially

EDIT: Even better, I found this stack exchange that explains how to disable and enable most of the macOS animations. I will open a PR for this with two shell scripts for disabling and enable most animations in macOS

My keyboard's backlight is not working on my 2012 MacBook Pro. The brightness controls just bring up a backlight icon with a prohibited icon underneath it (sort of like if you were trying to change the volume level with a custom sound setup).

Model: Mid-2012 MacBook Pro (9,2)
MacOS: v10.16 Beta 3/4
Patcher: v0.0.16/19

(Also thanks for making this patcher! It's really nice to still be able to use my old MacBook. 😄)

The MBP Retina 2012 has an Intel GPU (Intel HD4000) + a Discrete NVIDIA Geforce 650M.

In Mojave/Catalina the Mac boots by default with the Intel GPU as primary display and switch to NVIDIA on application demand.

On BS the Mac boots on NVIDIA by default and is stuck to it.

All the enegry preferences of BS seems very similar to the ones in Mojave/Catalina. The main difference is a process "displaypolicyd" that is "blocking" the automatic GPU switching. Once the process has been stoped the automatic switching between GPU works again and default back to the Intel GPU when no intensive GPU work is needed keeping the power consumption and the computer temperature lower.

Right now I do not found what is the role of displaypolicyd and what could be the impact of stoping it. More importantly, there is probably some settings or behavior of this process that prevents it from working as expected.

A possible temporary workaround is to stop this process (hoping that it will not have any other side effect on the system) :

• sudo launchctl stop com.apple.displaypolicyd -> restore macOS BS GPU switching capabilities
• sudo launchctl start com.apple.displaypolicyd -> NVIDIA GPU becomes the only one GPU used by system, no more switching possible
• sudo launchctl disable system/com.apple.displaypolicyd-> prevent it to restart on next reboot (thanks traviswparker)

On the internal SSD of my 2012 MacBook Air, I have macOS Mojave installed. I would like to keep that installation intact and only occasionally use Big Sur by booting off an external SSD.

Is it possible to install Big Sur on the external SSD using this method? Will my main Mojave installation be affected?

Ok, so I was able to use the patcher to create a fully functioning and bootable USB to begin installing Big Sur, but when I boot the USB, I can’t use my keyboard or mouse at all. They glow (gaming mouse and keyboard) like they are working, and they work as normal in the USB selector, and in Catalina, but the Big Sur Install Drive does not recognize them as being there. The animations I see on the screen is prompting me to turn on a Magic Mouse or a Magic Trackpad, and I just can’t escape it. I switched mouses, switched keyboards, and still no luck.

Delete

Hi,

I successfully installed the Big Sur public beta 1 on my late 2012 21.5' iMac, the OS works stable so far and I upgraded the radio chip some years ago, so WiFi worked too without the need of any further patching.

What doesn't seem to work is the full disk encryption with Filevault when trying to activate it under settings I get the following error message, it says something like "an internal error occurred":

I also tried to activate it via the terminal but also got an error messsage:

Error: A problem occurred while trying to enable FileVault. (-69596)

Is this a gererall issue with Big Sur or does this only happen on unsupported Macs? Did anyone else have this problem and found a fix?

I am not sure if these problems are related, but I also noticed that I seem not to have a recovery partition of Big Sur, when I reboot my Mac and hold CMD+R I end up in a recovery mode of Mountain Lion which for example doesn't give me an option to turn on SIP again, since it was introduced years after Mountain Lion.

Is there a way to recreate a recovery partion now after installation and would this maybe also fix the Filevault issue?

Thanks and have a great day :-)

Core i5 with ATI Radeon 4850.

Tried steps 1, 2, and 4. Booting to USB loads apple logo, screen goes black, and then just restarts boots my regular partition. And then, will restart again soon after booting my regular partition (just before I can type in my filevault password), before booting finally the 3rd time normally allowing me to type in my filevault password and boot into macOS (patched Mojave).

I can boot to USB in verbose mode, however the text scrolls by too quickly for me to be able to see anything meaningful. Perhaps I can try to capture the text output in slomo tomorrow to see what it says.

Can't recall EFI boot ----> MacOS Big Sur..
Turning on iMac holdin' OPTION key and see MacOS Mojave and EFI boot.......
But it's booting MacOS 11 beta 5.

I get this since MacOS Beta 2 & 3 & 4..
iMac 2013
Did anyone else have this problem and found a fix?

Thanks and have a great day! 👍

How do I enable Reduce Transparency?

Hi, I installed beta 3 on my Mac Pro 2009 (5,1 firmware upgraded) last time using your patch, everything worked except iMessages, FaceTime and TV app. I thought the issue was in the beta.

but today I formatted and freshly installed BigSur public beta using your patch and they are still not working. So I went back and installed Catalina using the dosdude's Catalina patcher and everything works again. Now I installed back the BigSur public beta with your patch and they don't work anymore, meaning iMessages and FaceTime don't let me login.

I think it has to do with resetting NVRAM. I tried by resetting NVRAM (which caused system to show this sign- ø) then I used the bootable USB and repeated the step 6 alone. Now it boots again into the OS. But then when I tried to log back into the FaceTime and iMessages, it let's me in into a nonfunctional iMessages app: no sync, send and receive messages. As soon as I log out and log back in, its doesn't log me in anymore, same problem repeats.

And as for the TV app, the content plays for only 5-8seconds then the content window automatically closes.

Can you please look into this issue or guide me if I am missing something in the setup process?

Thank you so much!

Best
PSZ

Boot macos installer, see apple logo at about 10% then windowserver? crashes and system shutdowns and reboots. Anyone else have this problem? Can’t find any logs on disk.. Thanks

Currently, remount-sysvol.sh creates a temporary directory with a rather random filename and mounts the underlying system volume there. However, another option to consider would be to mount it at /System/Volumes/Update/mnt1. That's where Apple's own updaters mount the underlying system volume.

I'm filing an issue instead of just changing the code, because I need to think this over first before I go ahead and do it, but I also want to put it in writing and make sure I don't forget about it.

Even if I enroll my MacBook Air 2012 in the public beta, Software Update in System Preferences doesn't find the Big Sur update, and I suspect this might be because my Mac is unsupported?

How can I download Big Sur in order to then use this micropatcher?

Does anyone have an idea about how Xcode 12 performance will be?

I'm getting this screen after following all the steps but instead of getting the setup screen this is what I get,

I'm trying this on my MacBook Pro Mid 2012 13 inch

Hey, I just found a issue with the patcher

It on uses nvram boot-args='-no_compat_check'

When it should use
nvram boot-args='-no_compat_check amfi_get_out_of_my_way=1`

How I can update to new beta? I have to download and make new usb installer?

Hello!
I have a Late 2012 retina macbook pro. When trying to install Big Sur using the patcher, the installer closes and my computer goes off after "13 min left". After rebooting screen shows a folder with a question mark on it.
Any help is appericiated!

I'm trying to install big sur on a 21.5-inch iMac late 2009, model 10.1. I made the USB bootable and inserted the patch on the USB sticker, but when I get to the installation screen (I attached the image), the Bluetooth keyboard and mouse, both from Apple, do not work, I also tried to connect USB mouse and keyboard, and I also did not get success.
I can't go through the installation process

I have late 2009 27 in iMac. Start iMac pressing option key and choose usb installation but the iMac just reboot and start to the main Mojave partition. I need to replace any hardware to this work?

On MacBook Pro 17" 2011
Cant boot on patched Installation if nvram is not modified :
nvram boot-args="-no_compat_check" is required

Best Regards

When trying to run set-vars.sh from the Terminal, the first two lines say:

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found

When trying the installation, once it reaches 12 minutes left it reboots into the prohibitory sign.

What should I do?

Hello! I'm gonna try it ASAP! Hope y'all doing great!

Regards!

Hello!
Installation was successful done without any issue. But now (probably after using bootcamp to mount windows drive) my Big Sur drive becomes unmountable.

I have mac mini 2012 late & Big Sur beta 4 installation.

Unusual behaviour: Big Sur drive become writable.
I'm trying to make it bootable by using "Modifying the System volume yourself" part of instruction but with no luck.

I still can boot in Catalina and Windows drive as normal. But then i try boot Big Sure i got error "The bless tool was unable to set the current boot disk".

Thanks in advance for help.

This was suggested by iPixelGalaxy on Discord several days ago.

I'm not completely sold on the idea, but I'm probably being cautious to a fault. I'll revisit this idea soon.

The install went well, to start, and after the first 24 minutes it rebooted ... and turned itself off.
I rebooted and had the no HD icon on screen.

I can reboot into the USB fine and redo the stage above,b ut again the same reboot issue then power off happens.

This MacBook works perfectly on MOJAVE FYI so I do not see it as a hardware issue.

I have reformatted/partitioned the SSD but the same issue happens.

All BETA v3? and big-sur-micropatcher, as dated with this post.

Beta 4 bootable media created, patched (0.19) and on the way to install (no VM, iMac27' 2012 late, beta2 already installed via parrot geek). But facing above mentioned issue on the main hard disk after booting from stick and selecting device to install. Any suggestions?

The display brightness control is missing, Night Shift is disabled and it's not possible to Sleep the computer. Is there a way around these issues? It might have to do with the graphics driver? This Macbook Pro has the AMD Radeon HD 6770M 1GB as well as the Intel HD 3000 512MB graphics cards installed.

I know this is a work in progress, but just wanted to report that I was able to get wifi to connect to my network. However when opening up safari, no urls would load.