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.
Ausdauersportler said:
You missed my first point: This particular OTA update had the same size of the complete installer package. We are going round in circles.

There is a single patcher offering OTA upgrades right now - revisit the first post.
Click to expand...
Mmmmm so even for the supported hardware, its the same thing about downloading big images for update? Wow... So maybe that was my misconception.... that even supported machines have to do it!

Well, since my project went off right now, maybe I will try it tomorrow.

Thanks to everyone... All this months reading this threat has been so curious!
 
A lot of chatter about "Patched Sur" and not sure what that is.

I have 11.0.1 installed via the Barry K Nathan micro-patcher for a long while now. For 11.1, is that still the recommended method if it worked for 11.0.1?

Do I have to to a full erase/wipe and fresh install or can 11.1 be installed over the top of 11.0.1 and re-patched?
 
  • Like
Reactions: Dilli
Bobpeace said:
Hello. I have a Macbook Pro 15" Early 2013.

  • I am trying to update my Patched Sur install over Catalina of 11.01 to 11.1 using the Patched Sur method.
  • I have created the "Install Big Sur" usb drive and can boot into it just fine.
  • When I am in recovery and attempting to select the user account to begin the install, my password that I used to log onto Big Sure does not work to unlock the volume.
  • Alternatively, I have tried to log in using my Apple ID but was not provided authentication on my account.
  • The password works fine logging into Big Sur normally though.
  • I tried to reset my SMC and that did not work.
  • I tried to boot using Command + R but I am getting an error and unable to do so.
  • Any recommendations on how to resolve this "password" issue?
  • Thanks in advance for the help!
Click to expand...
Check to see if FileVault is enabled. Thats where I'd start
 
Allistah said:
A lot of chatter about "Patched Sur" and not sure what that is.

I have 11.0.1 installed via the Barry K Nathan micro-patcher for a long while now. For 11.1, is that still the recommended method if it worked for 11.0.1?

Do I have to to a full erase/wipe and fresh install or can 11.1 be installed over the top of 11.0.1 and re-patched?
Click to expand...
Patched Sur basically added a GUI, and some user friendly prompts for the Micropatcher. Both will work. But if you are comfortable with the micropatcher, 11.1 can be installed overtop of your current install. No need to wipe the drive. Just create the installer as you did before, install, and you're good to go
 
  • Love
Reactions: Allistah
Bobpeace said:
FileVault is enabled. Should I disable it and retry?
Click to expand...
Yes. BigSur has had some issues with it, and the Micropatcher doesn't fully support it. Option 1: disable it if possible, and proceed with the install. Or option 2 : do a time machine backup. Then wipe the drive, and do a fresh install of 11.1, and restore from the backup. (that's probably your best option)
 
naylom11 said:
Patched Sur basically added a GUI, and some user friendly prompts for the Micropatcher. Both will work. But if you are comfortable with the micropatcher, 11.1 can be installed overtop of your current install. No need to wipe the drive. Just create the installer as you did before, install, and you're good to go
Click to expand...
Ok, cool. Since someone went and took the time to make Patched Sur, I'll take a look at it.

I've been searching for the URL to the direct download of the final 11.1, does anyone have that handy at all? I found this one but not sure if this is it or not: http://swcdn.apple.com/content/down...gypwunjfl96dza0upa854qgg/InstallAssistant.pkg
 
buckrock said:
Whenever you run a shell script (Barry has/instructs this one):
/Volumes/Install\ macOS\ Big\ Sur\ Beta/remount-sysvol.sh
it creates a new process called subshell and your script will get executed using a subshell.

A Subshell can be used to do parallel processing. If you start another shell on top of your current shell, it can be referred to as a subshell.

An aside: If you are asking what is a subshell, then you really need to Google zsh, Terminal, shell, subshell, etc to get good explanations. Be very careful typing commands; spaces, capitals, \ versus /, all are critically important. And lastly, the word 'Beta' in the command above is probably wrong since you installed BS 11.1 and your USB installer isn't named that. I'd recommend using drag and drop, and Tab-competition as much as possible. Barry describes these in his excellent ReadMe.
Click to expand...
ok understand, but where to run first remount-sysvol.sh, on BS or in recovery mod?

and if I understood correctly I don't need to run: remount-sysvol.sh if I wanna just use zap-snapshots.sh for delete APFS system snapshot, right? then please explain where to run zap-snapshots.sh by Recovery?

If I run this in BS system I get:
/Volumes/Install\ macOS\ Big\ Sur/zap-snapshots.sh
zsh: no such file or directory: /Volumes/Install macOS Big Sur/zap-snapshots.sh
or
/Volumes/Install\ macOS\ Big\ Sur\ zap-snapshots.sh
zsh: permission denied: /Volumes/Install macOS Big Sur
 
Last edited:
  • Like
Reactions: Dilli
tnsbgs said:
ok understand, but where to run first remount-sysvol.sh, on BS or in recovery mod?

and if I understood correctly I don't need to run: remount-sysvol.sh if I wanna just use zap-snapshots.sh for delete APFS system snapshot, right? then please explain where to run zap-snapshots.sh by Recovery?
Click to expand...
"For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation)."

If you read the docs carefully enough .... :)
 
  • Like
Reactions: Dilli
  • Like
Reactions: Allistah
Awesome, looks like I got the right one.

For this .pkg file, if I install that, it will just install the Big Sur 11.1 Installer.app and not actually install Big Sur, is that right? I was about to do it, but didn't want to kick off an actual install and not be able to stop it.

Answered my own question: Running and installing the .pkg file results in the file "Install macOS Big Sur.app" being installed in the /Applications folder.
 
Last edited:
Ausdauersportler said:
"For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation)."

If you read the docs carefully enough .... :)
Click to expand...
yes I got it, but what about zap-snapshots.sh I just tried run it in recovery mode:
/Volumes/Install\ macOS\ Big\ Sur/ zap-snapshots.sh and I get "no such file or directory":(
 
[solved]
[how]
CH341A programmer with SOP8 clip to flash EFI chip MX25L6406E with modified EFI file from clean one with my own serieal number, hash code and checksum valid.
[cost]
US$5.0

I bricked my iMac 27 late 2013 when OTA updating Big Sur 11.01 to 11.1 using "Opencore Legacy Patcher" 0.0.7 release.

I might use "Opencore Legacy Patcher" in a wrong way, during update after download finishing, system rebooted then got permanent black screen from that. Did the update crossflash the boot rom/firmware for different board ID/model?

PRAM & SMC many times did not work. It still chimes and it will shutdown less than one minute after power on, and with black screen. It can enter recovery mode and keep on but cannot see any thing.

I am wondering if anyone here has the same experience and know how to fix it.

Any possible solutions:
  1. change motherboard/logic board?
  2. flash the boot rom chip (downgrade to correct version) and how?
Thanks
 

Attachments

  • IMG_0816.JPG
    IMG_0816.JPG
    54.6 KB · Views: 62
Last edited:
paul.zhu said:
I bricked my iMac 27 late 2013 when OTA updating Big Sur 11.01 to 11.1 using "Opencore Legacy Patcher" 0.0.7 release.

I might use "Opencore Legacy Patcher" in a wrong way, during update after download finishing, system rebooted then got permanent black screen from that. Did the update crossflash the boot rom/firmware for different board ID/model?

PRAM & SMC many times did not work. It still chimes and it will shutdown less than one minute after power on, and with black screen. It can enter recovery mode and keep on but cannot see any thing.

I am wondering if anyone here has the same experience and know how to fix it.

Any possible solutions:
  1. change motherboard/logic board?
  2. flash the boot rom (downgrade to correct version) but how?
Thanks
Click to expand...
This is the major problem with OC and spoofing. I haven't heard of a viable solution other than re-flashing the boot ROM. I'd first try to run an apple hardware/diagnostic test, and check the ROM version. Then see what the latest supported version is for your machine. I believe you can download the EFI firmware directly from apple, but I haven't tried to do it. And I know Dosdude has a tool http://dosdude1.com/apps/ to re-flash the older firmware... I'm not an expert on this exact issue, but that's where I'd start

Edit: If you have another thunderbolt Mac available, it may be worth trying to use Target Disk Mode to mount the OC EFI partition. Doing some extended troubleshooting could reveal its as simple as re-installing Opencore. Just thought I'd add that, rather than assuming it is the ROM
 
Last edited:
  • Like
Reactions: paul.zhu
Dilli said:
Exactly. So how to go about it. I need to get airdrop and hands off running so kexts need to be replaced
Click to expand...
I had the same problem. With opencore legacy patcher 0.0.7 I had Airdrop working. If it helps give a try, I have MBP late 2011
 
  • Like
Reactions: Dilli
naylom11 said:
This is the major problem with OC and spoofing. I haven't heard of a viable solution other than re-flashing the boot ROM. I'd first try to run an apple hardware/diagnostic test, and check the ROM version. Then see what the latest supported version is for your machine. I believe you can download the EFI firmware directly from apple, but I haven't tried to do it. And I know Dosdude has a tool http://dosdude1.com/apps/ to re-flash the older firmware... I'm not an expert on this exact issue, but that's where I'd start
Click to expand...
cheers naylom11,
I do have an identical iMac that I can get correct ROM version from. But the trouble is black screen so cannot see anything if using online flash plus I might not be able to boot into any system at all at the moment. Or offline flash, save a correct one from identical iMac and flash it to the rom chip on logic board by using USB flash tool/clip?
 
Last edited:
paul.zhu said:
I bricked my iMac 27 late 2013 when OTA updating Big Sur 11.01 to 11.1 using "Opencore Legacy Patcher" 0.0.7 release.

I might use "Opencore Legacy Patcher" in a wrong way, during update after download finishing, system rebooted then got permanent black screen from that. Did the update crossflash the boot rom/firmware for different board ID/model?

PRAM & SMC many times did not work. It still chimes and it will shutdown less than one minute after power on, and with black screen. It can enter recovery mode and keep on but cannot see any thing.

I am wondering if anyone here has the same experience and know how to fix it.

Any possible solutions:
  1. change motherboard/logic board?
  2. flash the boot rom chip (downgrade to correct version) and how?
Thanks
Click to expand...
Did you hold Option when booting? If you did, you should report this on GitHub.
 
  • Like
Reactions: paul.zhu
Ausdauersportler said:
"For now, remount-sysvol.sh should be run from the patched installer USB (but after booting from your Big Sur installation)."

If you read the docs carefully enough .... :)
Click to expand...
Ok done!!! It's fantastic:) I don't need to delete snapshot, everything worked smoothly inside the BS system using only remount-sysvol.sh.
but I have a question, I just see under Disc Utility the name of snapshot is: com.apple.bless.05473884-872F-xxxx etc... it's normal that in the snapshot name it present word: BLESS? Leaving this as it is or do I need to do something else?
 
  • Like
Reactions: Dilli
tnsbgs said:
Ok done!!! It's fantastic:) I don't need to delete snapshot, everything worked smoothly inside the BS system using only remount-sysvol.sh.
but I have a question, I just see under Disc Utility the name of snapshot is: com.apple.bless.05473884-872F-xxxx etc... it's normal that in the snapshot name it present word: BLESS? Leaving this as it is or do I need to do something else?
Click to expand...
Yes. If it's not blessed it won't boot from the snapshot.
It's fine :)
 
  • Like
Reactions: hvds and Ausdauersportler
Hi,

I just updated from Big Sur 11.0.1 to 11.1 using BenSovs/Patched-Sur v0.0.0.4 Beta after restarting I ran Patched Sur app to Patch Kexts and I get this error message this is the text from the red box:

Error 1x1
Message: "Password:nvram: Error getting variable - 'csr-active-config': (iokit/common) data was not found
nvram: Error getting variable - 'csr-active-config': (iokit/common) data was not found"
"csr-active-config appears to be set incorrectly:

To fix this, please boot the setvars EFI utility, then boot back into macOS
and try again. Or if you believe you are seeing this message in error, try the
`--force` command line option."
Patch Kexts error.png

Everything seems to be working fine, WiFi works but was wondering what is this error?

Thanks
 
telepati said:
@jackluke finally I booted it. After Install OC and OC fix. Wifi works I didn't test other things cause no acceleration and everything extremely slow.

Now we can see, we can install BigSur to non AFPS Mac without an APFS rom patch.

Here is my spec for who want to try install;

View attachment 1659707
View attachment 1659712View attachment 1659708
Click to expand...
Hello Telepati,
How are you.
I was read all your and jacluke post,for the installation of core 2 duo penryn intel structure base systems.
Well
I have mac mini 3,1 Early 2009
Core 2 duo 2ghz 8gb ran
Nvida 9400 256.
Can i use jackluke base system installer for big sur installation.
You guide me in this if you dont mind
Thank you.
 
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