The link is not working. https://github.com/chris1111/ASR-Clone-SSD-macOS-Catalina-Big-Sur
There does not appear to be anything with a similar name on Chris's web page.
Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
There does not appear to be anything with a similar name on Chris's web page.
Encountering two apple logo with progress bar while booting any macOS graphical environment is completely normal, because the first progress bar is for kernel, binaries, frameworks and kext initialisation, the second progress bar is for graphics and AGC kext MUX switching, so showing a grey screen with cursor means that graphics kext are correctly loaded.
Your issue is only the "Choose Language", try reset PRAM and the retry to load the BigSurBaseSystemfix it should show the language selector screen.
Attachments
My MBP5,2 also has dosdude's APFS firmware patch since he provided it. Very good and useful.
Yet one can boot and use Catalina also without it: dosdude has also provided an alternative software fix (the one that shows textual output during booting).
Since there is no dosdude patcher for Big Sur, I guess the firmware APFS fix for these old machines is required though for Big Sur. That would mean, we benefit from @dosdude1 's coding work also in Big Sur.
Last edited:
All I can say is I've been using Big Sur on my 5,1 Mac Pro the last week and I love it. Extremely stable and no issues at all. Haven't used Catalina in almost a week. This partition is now my daily driver. Apple was smart shipping 11.0.1 before the final. Looking at the bug report prior to the first .1 release Big Sur would've been a mess.
Love it! Will try it out today and will let you know how it goes! I'm also working on a shell app with my friend for the post-install of BarryKN's patcher, so you don't need to run a single terminal command!I just uploaded a BigSurBaseSystemfix disk, updated for any generic BigSur 11.x beta (also non beta should work), simply restore through DiskUtility this DMG :
- minimum requirement 1 GB USB drive for an external modified recovery patcher (with BigSurFixes included)
to add an updated BigSur Installer app:
- an already downloaded InstallAssistant.pkg and unpacked to Applications folder
- 16 GB USB drive to add also the updated SharedSupport.dmg (typically size is 12.3 GB)
after restored the patched BigSurBaseSystemfix, you can use the same disk for any next beta releases, simply use this attached script I wrote for copying the updated SharedSupport.dmg to the target BigSurBaseSystemfix disk.
Yeah!! Resetting PRAM was the trick
Such a rookie move I didn't think of that before. I also appreciate the insight on the dual Apple logo/progress bars behavior.Thanks so much @jackluke!
So this is more of a generic question, and I've solved this before, but simply forgot how. And my detailed notes aren't help me
I need to modify the System Volume, so I can run the command to whitelist my iMac for Bluetooth Continuity support. I'm using the @jackluke patched installer. Reading the @Barry K. Nathan instructions, I know I need to
However, I can't figure out how to do this with my patched installer. From the installer recovery Terminal, I only get this:
I need to modify the System Volume, so I can run the command to whitelist my iMac for Bluetooth Continuity support. I'm using the @jackluke patched installer. Reading the @Barry K. Nathan instructions, I know I need to
remount-sysvol.sh and rebuild-kc.sh after I'm done.However, I can't figure out how to do this with my patched installer. From the installer recovery Terminal, I only get this:
Shouldn't that beSo this is more of a generic question, and I've solved this before, but simply forgot how. And my detailed notes aren't help me
I need to modify the System Volume, so I can run the command to whitelist my iMac for Bluetooth Continuity support. I'm using the @jackluke patched installer. Reading the @Barry K. Nathan instructions, I know I need toremount-sysvol.shandrebuild-kc.shafter I'm done.
However, I can't figure out how to do this with my patched installer. From the installer recovery Terminal, I only get this:
/Volumes/Install\ macOS\ Big\ Sur/remount-sysvol.sh.with the \ after Install and between macOS and Big and Sur?
So this is more of a generic question, and I've solved this before, but simply forgot how. And my detailed notes aren't help me
I need to modify the System Volume, so I can run the command to whitelist my iMac for Bluetooth Continuity support. I'm using the @jackluke patched installer. Reading the @Barry K. Nathan instructions, I know I need toremount-sysvol.shandrebuild-kc.shafter I'm done.
If you used my BigSurBaseSystemfix as booting environment, on the Utilities menu I also recently added a "BigSurFixes Continuity fix" that should whitelist continuity features on any Broadcom Wifi and Bluetooth 4.0 cards .
Maybe after applied the fix, you should sign out from BigSur System Preferences with your Apple ID and then sign in again.
And are also included "BigSurFixes disable snapshot" (or "delete snapshot") to use directly "sudo mount -uw /" ("csrutil disable" is required) from BigSur normal booting.
I can confirm, removing bluetooth card on my 3,1 fixed booting issue. Bigmac install now boots into Big Sur reliably.
Must have missed the software only fix. I'm pretty sure I'm using the firmware fix.
Interesting. I may have to try surgery in order to get past this problem. Normally I use a Bluetooth USB dongle anyway.
Cool. Although I think I'm erroring out in the attached screenshot?
From your pictures, seems you have Mojave (or HighSierra) and BigSur installed on the same APFS container (you can notice the Preboot size is 699 MB while normally for BigSur is around 300 MB), currently my BigSurFixes works only if BigSur is installed on a separated APFS container (with its own APFS Preboot volume).
If the same APFS container in particular the APFS Preboot is shared among multiple APFS macOS , then BigSurFixes currently can't work on that configuration where one APFS Preboot contains multiple UUID .
If your Mojave or HighSierra was installed on a separated HFS+ Volume (external to the APFS container), then those fixes worked.
Last edited:
Ah. Yes, I also have a High Sierra install on the same APFS container as Big Sur.
With that in mind, do you have any other fix recommendations for the Bluetooth Continuity whitelist? I have absolutely have had this working in the past, but the Big Sur re-install "breaks" it, due to volume sealing, I assume.
I just edited Mojave or HighSierra, because Mojave was also an APFS macOS without the APFS Data Volume (only added from Catalina so your picture showed only one APFS Data correctly), anyway currently I don't have a method to detect when the same APFS Preboot is shared with another APFS macOS, on purpose the command fails with "sudo command not found" to don't mismatch the other macOS Preboot.
So you should use the micropatcher remount sysvol and type from terminal that long string to whitelist the board id for continuity, after you should also run "patch kext" because you need a new snapshot with the Bluetooth framework modified for continuity.
Last edited:
Removing the BlueTooth card fixed the non booting issue on my 3,1. It boots fine now using bigmac. Trying to patch wifi and audio now.
Question....does the Bluetooth card have to come out permanently or just to get the install completed?
That did it! Thanks again
I have been taking copious notes regarding these steps, not only for my own sanity, but to help others going forward.
For me, BT card panics. I’d imagine a bt patch is needed or upgrade to a supported card.
I just removed the BT card. The installer just booted to the main MacOS Recovery screen without any weird problems. Installing BigSur now. Let's see what happens next...
Well, removed the card is a strong word. More like detached it from the motherboard and taped it to the drive above it since I was too lazy to disconnect the antenna cable.
Let me know how this goes! Removing the BT card didn’t help me much, and I still can’t seem to get the X minutes remaining black boot screenI just removed the BT card. The installer just booted to the main MacOS Recovery screen without any weird problems. Installing BigSur now. Let's see what happens next...
Well, removed the card is a strong word. More like detached it from the motherboard and taped it to the drive above it since I was too lazy to disconnect the antenna cable.