sure APFS for the drive to install to and HFS,GUID for USB stick.I thought APFS is the preferred format for both Catalina and Big Sur. Am I missing something here?
sure APFS for the drive to install to and HFS,GUID for USB stick.I thought APFS is the preferred format for both Catalina and Big Sur. Am I missing something here?
thank you for the direct link to install assistant I used this image and its running great.Did you select public release? You could try downloading the install assistant directly from Apple, install it and then click View other versions in Patched Sur > Find an Installer and then select the Install MacOS Big Sur installer in your applications and see if that works.
Hope this helps.
Yep, that explains greatly. Thumbs up.sure APFS for the drive to install to and HFS,GUID for USB stick.
If you used the micropatcher, need to boot again on the USB EFI that will setup your nvram correctly. Then can boot BigSur back. I think you can't boot back into an older OS after the mod. Something in these lines.Hi I installed Big Sur final release on my Mac Pro flashed 5,1 using BigMac method. Everything works like a dream. I installed it on a nvme along side Mojave on another nvme. My problem it when I restart my Mac using startup disk back into Mojave I lose the option of restarting my Mac back into Big Sur (the startup disk is no longer there for Big Sur). any solutions?
Please, please add now your hardware to your signature and please check out the special MacPro threads. This is unlikely a Big Sur patcher issue at all.Hi I installed Big Sur final release on my Mac Pro flashed 5,1 using BigMac method. Everything works like a dream. I installed it on a nvme along side Mojave on another nvme. My problem it when I restart my Mac using startup disk back into Mojave I lose the option of restarting my Mac back into Big Sur (the startup disk is no longer there for Big Sur). any solutions?
This is not the stop sign issue, he lost the connection to his second NVME somehow. There are posts about not installing the OS to theses devices ...I do not know where and why.If you used the micropatcher, need to boot again on the USB EFI that will setup your nvram correctly. Then can boot BigSur back. I think you can't boot back into an older OS after the mod. Something in these lines.
This appears to be exactly the same symptoms which I got on my unsupported late 2012 13" MBP - which would make sense since, after upgrading the WiFi card, I understand it has exactly the same hardware as the supported machines which are also failing.
Having realised that this problem does not just affect people faking their machine id using @jackluke's extremely useful sideloader, but also affects completely normal installs on officially supported MBPs, I have just posted on the 'macOS Big Sur Update Bricking Some Older MacBook Pro Models' thread what (from my own experiences, already reported on this thread) seems very likely to be a genuine fix for the black screen problem, on both supported and unsupported MBPs.This appears to be exactly the same symptoms which I got on my unsupported late 2012 13" MBP - which would make sense since, after upgrading the WiFi card, I think it has essentially exactly the same hardware as the supported machines which are also failing.
@jackluke & @Barry K. Nathan (apologies if this has been discussed above, I've done some searches, but haven't read every single post on the 30-odd pages since I was last on here about a week ago!) and others who were interested, this sounds to me very much as if the issue I had *wasn't* cross-flashing after all, and more that it was the correct flash which was applied to my machine, but there is then some problem with how the flash is applied which makes machines of that era hang (until you remove the battery long enough to reset ... something!!).
It’s just wierd, when i boot back into Mojave the big sur disks are on my desktop just on in the startup disk option in system preferences but when I boot into recovery mode the big sur disk is in the start up disk option. I’m going to see if i can boot from it under recoveryThis is not the stop sign issue, he lost the connection to his second NVME somehow. There are posts about not installing the OS to theses devices ...I do not know where and why.
Yesterday I had problems with my external USB disk, so I will start over with a new one. Anyway I'm quite sure I erased the external disk using Catalina. I'll be back soon.Are you installing an internal SATA disk or external USB disk, and do you used as target installation an HFS+ disk or APFS container ?
If you could try a SATA internal installation (this doesn't required stage2 and stage3 installer fix) it should work on that machine, then from BigSur recovery environment you could easily clone that installation to external USB , the main required fix after bootloop is "BigSurFix Legacy USB patches".
I am enough sure that also I fixed thatapfs_get_firmlink_target_vnode
( @Ourkid and @telepati could confirm that ), but I need more testing on that stage3 installer when target is an external legacy USB host device.
You should use as target disk (for the stage1 installer) an already converted APFS container, possibly erasing it from Mojave or Catalina (that use their earlier apfs driver version), because the new BigSur apfs driver during conversion from HFS+ to APFS could made some incompatible modification to the Data Volume file system.
Yesterday I had problems with my external USB disk, so I will start over with a new one. Anyway I'm quite sure I erased the external disk using Catalina. I'll be back soon.
from Catalina:
diskutil list
(locate your BigSur diskXs2)
diskutil mount diskXs2
sudo bless --folder /Volumes/Preboot/*/System/Library/CoreServices --label "Big Sur"
sudo rm /Volumes/Preboot/*/System/Library/CoreServices/PlatformSupport.plist
Just out of curiosity: Did you use the micro patcher?I have successfully installed current Big Sur (20B29) on 2010 iMac 11,3 using OpenCore but still seeing two issues.
1. After cold power restart, Bluetooth mouse is not seen. I have to use USB mouse to open Bluetooth preferences and connect the Bluetooth mouse. After that it works fine until next power cycle.
2. Wifi works fine, but system does not see the Ethernet card. I have included the CatalinaBCM5701Ethernet kext as per instructions. System Info says there is no PCI Ethernet card installed.
I have tried searching this thread, but can only find info about wifi ethernet, which works fine for me, but nothing about wired ethernet. Have I missed something?
Thanks for your very welcome post!Having realised that this problem does not just affect people faking their machine id using @jackluke's extremely useful sideloader, but also affects completely normal installs on officially supported MBPs, I have just posted on the 'macOS Big Sur Update Bricking Some Older MacBook Pro Models' thread what (from my own experiences, already reported on this thread) seems very likely to be a genuine fix for the black screen problem, on both supported and unsupported MBPs.
Namely: completely remove power to the circuit board briefly, by disassembling, disconnecting the battery, and then holding the power button for 5 seconds (even though the batteries of these machines are not officially removable, this is simply the approach for Macbooks with removable batteries at https://support.apple.com/en-gb/HT201295).
I am currently pretty hopeful that this would fix the problem on supported MBPs just as well as it did on my unsupported MBP of basically the same era.
OK, I have a Mac Pro 3,1 that hasn't worked yet and I have a USB Bluetooth adapter that I can remove for this exercise. How are you using both BigMac patcher AND Micropatcher?Mac Pro 3.1 (Early 2008)
USB Keyboard and Mouse works with CMD+S, bootloop issue resolved by remove old BlueTooth adapter, BigMac patcher + Micropatcher (in big sur) + repeate BigMac's ./Postinstall.sh - and i get some stable system.
And i Still work on USB Key+Mouse issue.
Hi, I did the tips you suggested, but nothing changed. I installed BS on a new 250Gb external USB disk formatted as APFS by Catalina. Stage2 completed successfully (less than a minute lasted 55 minutes) and again stage3 failed bootlooping on "apfs_get_firmlink_target_vnode". Again when I applied the Legacy USB fix and the iSight fix no new snapshot was created with the same ARV error. The bless command didn't return any error, while removing PlatformSupport.plist returned that the file doesn't exist.I add other tips if you eventually after stage3 installer encounter that: "apfs_get_firmlink_target_vnode"
Code:from Catalina: diskutil list (locate your BigSur diskXs2) diskutil mount diskXs2 sudo bless --folder /Volumes/Preboot/*/System/Library/CoreServices --label "Big Sur" sudo rm /Volumes/Preboot/*/System/Library/CoreServices/PlatformSupport.plist
After stage3 (made of some auto reboot), only when encounter bootloop kernel panic, apply these fixes:
"Install OpenCoreAPFSloader3" , from its opencore text menu "Restart fix" to try booting without opencore, you need to apply "BigSurFixes Legacy USB patches" from Utilities.
Or using OpenCoreAPFSloader, select "BaseSystem fix installer", then from Utilities apply:
"BigSur stage3 installer fix"
"BigSurFixes Legacy USB patches" (that includes also Sound, wifi, telemetry and snapshot booting)
"BigSurFixes iSight camera fix" (that includes also Nvidia framebuffer)
then reboot again the "BaseSystem fix installer", from Utilities apply "BigSurFixes opencore Preboot".
Try booting BigSur through OpenCoreAPFSloader3 , if you have an APFS rom patch you can even skip using opencore through "Restart fix" button.