macOS 11 Big Sur on Unsupported Macs Thread

[thatsmeonlyme]

Please help my friend
I have installed 11.0 beta 20A5364e on my MacBook Pro late 2011 13’
i applied patches but no network , lan or even WiFi no brightness f1 f2 buttons , the MacBook is also so slow with 100% cpu (secd process)
i tried every method , really I need your help, tired of searching every post

first to the first question: did you patch --2011?
the second: BS will not work on this macBook in a usable way because of no acceleration

 

[eminemmm]

first to the first question: did you patch --2011?
the second: BS will not work on this macBook in a usable way because of no acceleration

yes I used —2011 but I get an error message about kmutil failed

 

[thatsmeonlyme]

yes I used —2011 but I get an error message about kmutil failed

boot back into the installer/terminal/csrutil status /csrutil authentic-..... status

if both are disabled start the patching process again. if that not works you got a corrupted installer?

installation on this machine works without probs.

 

[eminemmm]

boot back into the installer/terminal/csrutil status /csrutil authentic-..... status

if both are disabled start the patching process again. if that not works you got a corrupted installer?

installation on this machine works without probs.

Yes they are all disabled
(Dunno what to do)
Now I tried to reinstall the Big Sur from startup it gives me strange error (the operation couldn’t be completed . BIErrorDomain error 2)

 

[thatsmeonlyme]

Yes they are all disabled
(Dunno what to do)
Now I tried to reinstall the Big Sur from startup it gives me strange error (the operation couldn’t be completed . BIErrorDomain error 2)

if both are disabled start the patching process again. did I tell you you should install new? think you got it installed?If kmutil did not work you have to patch new via terminal and get it working.

 

[eminemmm]

if both are disabled start the patching process again. did I tell you you should install new? think you got it installed?If kmutil did not work you have to patch new via terminal and get it working.

now I did the ( /volumes/image\ volume/set-vars.sh ) again
And started to reinstall big sur

(the strange thing first time when I installed it (I didn’t get the language and region settings they talked about. It took me to log in page at the end ?!?

 

[thatsmeonlyme]

now I did the ( /volumes/image\ volume/set-vars.sh ) again
And started to reinstall big sur

(the strange thing first time when I installed it (I didn’t get the language and region settings they talked about. It took me to log in page at the end ?!?

please for my understanding explain why you are doing a new install while having an installation with the described issues.

the login screen means the first point of installation you are able to quit without harms. It doesn't matter if you get it or not. Before getting a working system you'll have to do what @dosdude1 called the post install patches.
You'll have to reboot into the installer again and apply the patches again. That is the step you missed. There's no need of new installation.

 

[eminemmm]

please for my understanding explain why you are doing a new install while having an installation with the described issues.

the login screen means the first point of installation you are able to quit without harms. It doesn't matter if you get it or not. Before getting a working system you'll have to do what @dosdude1 called the post install patches.
You'll have to reboot into the installer again and apply the patches again. That is the step you missed. There's no need of new installation.

i already now started installing it again
I will reboot after that and try to apply the patches (patch-kexts.sh) thing

I hope really it works because I can’t even use my MacBook now and there is no even internet , I’m using my iPhone 11 pro Max and my iPad Pro now

really I want to thank you for your help and patience , I will tell you what happened after 30 min

 

[Ghostrider66]

hi All. as always thanks to all who contributed here to make this happen. I have managed to get all betas from 3 to 6 working great on my MacBook Pro. I have been following the discussion in relation to getting beta 7 installation possible. I have tried BigSurOTAswufix.app.zip and get the following screen

this is the screenshot of beta 6 on my MacBook Pro. Any help would be appreciated

Thanks

 

[Ghostrider66]

Here are my results from softwarewareupdate

 

[eminemmm]

please for my understanding explain why you are doing a new install while having an installation with the described issues.

the login screen means the first point of installation you are able to quit without harms. It doesn't matter if you get it or not. Before getting a working system you'll have to do what @dosdude1 called the post install patches.
You'll have to reboot into the installer again and apply the patches again. That is the step you missed. There's no need of new installation.

After all I got the same message
Kmutil failed
Patch-kexts.sh cannot continue

 

[Fangio]

I'll attempt but I guess can't update it much, because BigSur to detect OTA updates requires mainly a supported Mac ID spoofing (on Catalina the spoofing was to a generic Virtual Machine that on BigSur doesn't work), moreover BigSur incremental update requires a valid APFS container with snapshot booting , because as also @Barry K. Nathan explained the update is temporary mounted on the new Update APFS volume starting from this zip package naming "com_apple_MobileAsset_MacSoftwareUpdate" , while before the macOS update was downloaded in separated packages on this path /Library/Updates/ .

So to detect and install an OTA update an enough working method is through opencore to spoof a supported Mac.

Thanks a lot. I'll give it a try.

BTW, I'd wish @dosdude1 would be more responsive here these days. With all due respect, at least a statement would be nice if he's working on it, at all... and sorry Discord is not the way to go, imo its just a chat platform for kids. Not comparable to contributions from adults here.

 

[thatsmeonlyme]

After all I got the same message
Kmutil failed
Patch-kexts.sh cannot continue

try another patcher with other usb

 

[thatsmeonlyme]

try another patcher with other usb

37 minutes for installation seems to be to fast. do you break the installation?

 

[eminemmm]

37 minutes for installation seems to be to fast. do you break the installation?

No it finished automatically

what do you mean another patcher

no internet and I have only on usb patches with micropatcher

 

[Alex-Microsmeta]

Thanks a lot. I'll give it a try.

BTW, I'd wish @dosdude1 would be more responsive here these days. With all due respect, at least a statement would be nice if he's working on it, at all... and sorry Discord is not the way to go, imo its just a chat platform for kids. Not comparable to contributions from adults here.

Yes, I'd also like to know if it's everything fine with him and I wish all the best for @dosdude1 !

 

[thatsmeonlyme]

No it finished automatically

what do you mean another patcher

no internet and I have only on usb patches with micropatcher

how far does your machine boot?

 

[Ausdauersportler]

I just made the download of the beta7 updater.

(this is just an updater, not a full installer, download link some pages back, but it does not work alone)

Has anybody tried to put it into /Library/Updates and let the system decide to install the updates?

(Normally I do this with the High Sierra updates (2.6 GB) - faster than downloading.)

 

[justperry]

I just made the download of the beta7 updater.

(this is just an updater, not a full installer, download link some pages back, but it does not work alone)

Has anybody tried to put it into /Library/Updates and let the system decide to install the updates?

(Normally I do this with the High Sierra updates (2.6 GB) - faster than downloading.)

I, before used Pacifist to Install, but I am pretty sure that won't work anymore, same goes for your method, it used to be so much easier than nowadays.

 

[justperry]

I just made the download of the beta7 updater.

(this is just an updater, not a full installer, download link some pages back, but it does not work alone)

Has anybody tried to put it into /Library/Updates and let the system decide to install the updates?

(Normally I do this with the High Sierra updates (2.6 GB) - faster than downloading.)

I put the files in Updates, then use Software Update, nothing happens.
I don't know how to invoke the Updating process, before it was possible to just click on the .pkg installer, now there are .Boms, as I said, don't know how to invoke the install process.

 

[Ausdauersportler]

I put the files in Updates, then use Software Update, nothing happens.
I don't know how to invoke the Updating process, before it was possible to just click on the .pkg installer, now there are .Boms, as I said, don't know how to invoke the install process.

Normally I just reboot the system once or twice. There must be a daemon checking contents of this folder and initialising the update process once correct data has been found. For sure one can observe the download, unpacking and reboot process on a supported machine closely.

And of course one must spoof a supported BoardID or edit the PlatformSupportList.plist somehow. I am new to the deep details of the patcher business. Spent just some time on the open source code of the @dosdude1 patcher and the scripts @Barry K. Nathan published.

In the long run I will buy a supported system, again

 

[justperry]

Normally I just reboot the system once or twice. There must be a daemon checking contents of this folder and initialising the update process once correct data has been found. For sure one can observe the download, unpacking and reboot process on a supported machine closely.

In the long run I will buy one, again

I won't buy a new mac until Apple silicon has arrived, I have 2 Macs, both from 2012, a Mac Mini and a 23" MBP, they both work fairly well, except for the Graphic cards.

I' ll try restarting a few times.

 

[justperry]

Normally I just reboot the system once or twice. There must be a daemon checking contents of this folder and initialising the update process once correct data has been found. For sure one can observe the download, unpacking and reboot process on a supported machine closely.

And of course one must spoof a supported BoardID or edit the PlatformSupportList.plist somehow. I am new to the deep details of the patcher business. Spent just some time on the open source code of the @dosdude1 patcher and the scripts @Barry K. Nathan published.

In the long run I will buy a supported system, again

As I suspected a restart (Actually 2) doesn't work, it does not work that way, the installer has to be invoked first, upon restart it will startup from that installer, might be investigating if blessing the boot folder in *Updates might work.

*Hmm, don't think that'll work either.

 

[abelpinate]

I won't buy a new mac until Apple silicon has arrived, I have 2 Macs, both from 2012, a Mac Mini and a 23" MBP, they both work fairly well, except for the Graphic cards.

I' ll try restarting a few times.

I'm on this one too. I have the mbp9,2 and a mini 5,2 (selling it) and I'm waiting for the Apple Silicon and from here to there, I plan to use this... but as I read somewhere, a good point it's buy one of the last intel machine the could work pretty well for 10 years more?

Anyway... due to work since it's my main machine, I've read ALL this threat since beta 1 but haven't try yet... I can go without machine...

Get a project in lockdown it's a miracle and noooo way.

 

[eminemmm]

Okay I got Big Sur downloaded I’m on step after I hold cmd q for the reboot and it keeps not letting me put mount -uw I was not able to do the kext someone help and thank you for all those who got me to this point and it says mount: unknown special file or files system /volumes\bigsur

What did you do to fix this ?