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.
BeatCrazy said:
I am mostly following along. Can I assume that the above analysis is responsible for my issue below?

Click to expand...

No, that is a BigSur InstallAssistant (or other installer framework) failing checks that you don't have a supported BigSur Mac, to fix this you simply could use this method:

sudo nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"

reboot and check "nvram boot-args", then apply the ASentientBot HaxLib patch for machines with non-APFS firmware: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28619108

launch the Hax3.app or if for some reason not work, copy the Hax.dylib file to your home folder /Users/yourusername/ then copy paste from terminal:
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

relaunch the BigSur installer from HighSierra desktop and it should work.
 
Last edited:
  • Like
Reactions: Bmju, TimothyR734, webg3 and 3 others
hi everyone. have a MacBook Pro 13 mid 2012 (9,2) and can't install Big Sur.
BS 11.0.1, createinstallmedia via terminal, patch usb stick with Micropatcher 0.5.0 (Micropatcher and install-setvars)
Reboot with efi, erase ssd w/disk utility, start install and have this.
Log
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Use NVRAM prev-lang:kbd value (252) as default ASCII input source: ABC
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Hardware: MacBookPro9,2 @ 2.50 GHz (x 4), 8192 MB RAM
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Running OS Build: macOS 11.0.1 (20B5012d)
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: SHELL=/bin/sh
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: TMPDIR=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: USER=root
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: __CF_USER_TEXT_ENCODING=0x0:0:0
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: PWD=/
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: XPC_FLAGS=0x0
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: XPC_SERVICE_NAME=com.apple.recoveryos_agent
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: SHLVL=0
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: HOME=/var/root
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: __OSINSTALL_ENVIRONMENT=1
Nov 4 19:04:54 MacBook-Pro InstallAssistant[218]: Env: LOGNAME=root
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: Failed to verify clock with apple.com, error: Error Domain=NSURLErrorDomain Code=-1009 "The internet connection appears to be offline." UserInfo={NSUnderlyingError=0x7fcaa3e08d60 {Error Domain=kCFErrorDomainCFNetwork Code=-1009 "The internet connection appears to be offline." UserInfo={NSErrorFailingURLStringKey=http://www.apple.com/library/test/success.html, NSErrorFailingURLKey=http://www.apple.com/library/test/success.html, _kCFStreamErrorCodeKey=50, _kCFStreamErrorDomainKey=1, NSLocalizedDescription=The internet connection appears to be offline.}}, NSErrorFailingURLStringKey=http://www.apple.com/library/test/success.html, NSErrorFailingURLKey=http://www.apple.com/library/test/success.html, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=50, NSLocalizedDescription=The internet connection appears to be offline.}
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: Seeding: ExtendedAttribute was not set on /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: seedingInfoDict ->
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: result : Fail
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: seedProgramSource : Default
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: seedProgram : PublicSeed
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: catalogURLString : https://swscan.apple.com/content/ca...n-lion-snowleopard-leopard.merged-1.sucatalog
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: fileName : /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: error : No xattr was set
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: OSISSoftwareUpdateController: No xattr was set on file /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app. Falling to default Seed.
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: OSISSoftwareUpdateController: Using catalog (source: Default): https://swscan.apple.com/content/ca...n-lion-snowleopard-leopard.merged-1.sucatalog
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: mountDiskImageWithPath: /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app/Contents/SharedSupport/SharedSupport.dmg
Nov 4 19:04:55 MacBook-Pro osinstallersetupd[234]: OSISSoftwareUpdateController: Failed to load catalog https://swscan.apple.com/content/ca...n-lion-snowleopard-leopard.merged-1.sucatalog: Error Domain=MSUProductManagerErrorDomain Code=51 "(null)" UserInfo={NSUnderlyingError=0x7fcaa3e0d7f0 {Error Domain=MSUDataDownloaderErrorDomain Code=2 "(null)"}}
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Mounting disk image complete, results dict = {
"system-entities" = (
{
"content-hint" = EFI;
"dev-entry" = "/dev/disk6s1";
"potentially-mountable" = 1;
"unmapped-content-hint" = "C12A7328-F81F-11D2-BA4B-00A0C93EC93B";
"volume-kind" = msdos;
},
{
"content-hint" = "Apple_HFS";
"dev-entry" = "/dev/disk6s2";
"mount-point" = "/Volumes/Shared Support";
"potentially-mountable" = 1;
"unmapped-content-hint" = "48465300-0000-11AA-AA11-00306543ECAC";
"volume-kind" = hfs;
},
{
"content-hint" = "GUID_partition_scheme";
"dev-entry" = "/dev/disk6";
"potentially-mountable" = 0;
"unmapped-content-hint" = "GUID_partition_scheme";
}
);
}
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Mount point /Volumes/Shared Support
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Extracting brain /Volumes/Shared Support/UpdateBrain.zip -> /tmp/UpdateBrain-rnzAj5I1
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Extracting /Volumes/Shared Support/UpdateBrain.zip -> /tmp/UpdateBrain-rnzAj5I1
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Finished extracting: succeeded
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Skipping starting the brain because we're not on a new enough macOS.
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Adding MobileSoftwareUpdate product: OSISMobileSoftwareUpdateProduct <brain: /Volumes/Shared Support/UpdateBrain.zip, bundle: /Volumes/Shared Support/com_apple_MobileAsset_MacSoftwareUpdate/88b17ec16b052905150871e4110f12785f6cad55.zip, SFR: /Volumes/Shared Support/SFR/com_apple_MobileAsset_SFRSoftwareUpdate/9803fe7b358740cf410230d42c5f7fe7e851a348.zip>
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Will extract Info.plist from: /Volumes/Shared Support/com_apple_MobileAsset_MacSoftwareUpdate/88b17ec16b052905150871e4110f12785f6cad55.zip toPath: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/416930F7-04BC-4E5D-8473-8C87AB549093
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Extracted Info.plist to path: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/416930F7-04BC-4E5D-8473-8C87AB549093/Info.plist
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Extracted BuildManifest,plist to path: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/416930F7-04BC-4E5D-8473-8C87AB549093/AssetData/boot/BuildManifest.plist
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: already using MSU springboard, skipping SUMAC
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: osinstallersetupd registered client
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Ignoring disk <DADisk 0x7fcaa631cf90 [0x7fffb7240f70]>{id = /Volumes?owner=0} because is has no device
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: Ignoring disk <DADisk 0x7fcaa631cf90 [0x7fffb7240f70]>{id = /System/Volumes/Data?owner=0} because is has no device
Nov 4 19:04:56 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:57 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:57 MacBook-Pro osinstallersetupd[234]: Disk disk3s1 already has an install user and must be erased.
Nov 4 19:04:57 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:57 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:57 MacBook-Pro osinstallersetupd[234]: ROM Features returned: 3238917495
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: diskAppeared: disk6s1
Nov 4 19:04:57 MacBook-Pro OSIESpringboard[187]: -[SpringboardController utilityDidAppear:]: NSConcreteNotification 0x7fd870e1df50 {name = com.apple.installdvdspringboard.utilityappear; object = <NSConcreteTask: 0x7fd870cd7f80>}
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: Ignoring non-user-visible disk IADisk_10_6: disk6s1 EFI as target
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: diskAppeared: disk6s2
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: Ignoring non-user-visible disk IADisk_10_6: disk6s2 Shared Support as target
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: diskAppeared: disk6
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: Ignoring non-user-visible disk IADisk_10_6: disk6 (null) as target
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: diskMounted: disk6s2
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: Ignoring non-user-visible disk IADisk_10_6: disk6s2 Shared Support as target
Nov 4 19:04:57 MacBook-Pro InstallAssistant[218]: diskChanged: disk6s2
Nov 4 19:04:58 MacBook-Pro InstallAssistant[218]: Use NVRAM prev-lang:kbd value (252) as default ASCII input source: ABC
Nov 4 19:04:58 MacBook-Pro osinstallersetupd[234]: Will need to use bundled in license doc
Nov 4 19:04:58 MacBook-Pro InstallAssistant[218]: localizedLicenseURL: file:///Volumes/Image%20Volume/Install%20macOS%20Big%20Sur%20Beta.app/Contents/MacOS/InstallAssistant.app/Contents/Resources/en_GB.lproj/License.html
Nov 4 19:05:04 MacBook-Pro InstallAssistant[218]: Failed to check if a disk is FDE.
Nov 4 19:05:05 MacBook-Pro InstallAssistant[218]: OSISClient: Using kAuthorizationFlagSheet
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: mountDiskImageWithPath: /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app/Contents/SharedSupport/SharedSupport.dmg
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Using product <OSISCollectionInstallProduct: 0x7fcaa3e66050> at distance 10
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Helper tool loaded
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Verify calculated time estimate: 385.958316 for /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app/Contents/SharedSupport/SharedSupport.dmg
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Required package references: (
)
Nov 4 19:05:06 MacBook-Pro osishelperd[254]: Privileged helper tool loaded.
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: OSISDownloadOperation: totalEstimate=0.000000, significantDownload=0
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Operation queue started
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Getting offset for dmg in pkg: /Volumes/Image Volume/Install macOS Big Sur Beta.app/Contents/MacOS/InstallAssistant.app/Contents/SharedSupport/SharedSupport.dmg
Nov 4 19:05:06 MacBook-Pro osinstallersetupd[234]: Verifying SharedSupport.dmg
Nov 4 19:05:53 MacBook-Pro osinstallersetupd[234]: pkgdmg checksum does not match, possible corruption.
Nov 4 19:05:53 MacBook-Pro osinstallersetupd[234]: pkgdmg validation has failed.
Nov 4 19:05:53 MacBook-Pro osinstallersetupd[234]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=255 "Installation cannot proceed because the installer is damaged." UserInfo={NSLocalizedDescription=Installation cannot proceed because the installer is damaged., NSLocalizedRecoverySuggestion=Redownload the installer and try again.}
Nov 4 19:05:53 MacBook-Pro InstallAssistant[218]: Stopped operation queue with Error Domain=com.apple.OSInstallerSetup.error Code=255 "Installation cannot proceed because the installer is damaged." UserInfo={NSLocalizedDescription=Installation cannot proceed because the installer is damaged., NSLocalizedRecoverySuggestion=Redownload the installer and try again.}
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] UID: 0, EUID: 0, GID: 0, EGID: 0, PID: 256, PROC: com.apple.appkit.xpc.openAndSav ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, Name: /Local/Default, Options: 0x0
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] node assigned UUID - 8EB8D4C8-A1B6-4859-836D-897DB7B2E681
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] ODNodeCreateWithNameAndOptions completed
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] UID: 0, EUID: 0, GID: 0, EGID: 0, PID: 256, PROC: com.apple.appkit.xpc.openAndSav ODQueryCreateWithNode request, NodeID: 8EB8D4C8-A1B6-4859-836D-897DB7B2E681, RecordType(s): dsRecTypeStandard:SharePoints, Attribute: dsAttrTypeStandard:RecordName, MatchType: Any, Equality: CaseExact, Value(s): dsRecordsAll, Requested Attributes: afp_use_parent_privs,dsAttrTypeStandard:GeneratedUID,afp_name,smb_inherit_permissions,dsAttrTypeStandard:AppleMetaNodeLocation,afp_shared,dsAttrTypeStandard:RecordType,sharepoint_version,smb_directorymask,smb_name,directory_path,dsAttrTypeStandard:RecordName,afp_use_parent_owner,ftp_shared,smb_shared,smb_guestaccess,smb_oplocks,afp_guestaccess,dsAttrTypeStandard:AppleMetaRecordName,com_apple_sharing_uuid,ftp_guestaccess,smb_strictlocking,ftp_name,sharepoint_account_uuid,smb_createmask,sharepoint_group_id, Max Results: 2147483647
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] queuing request to connection - 105343D9-6C69-4E03-8548-81BA431366F3 - CFBundle 0x7ffa09d551a0 </System/Library/OpenDirectory/Modules/PlistFile.bundle> (bundle, loaded)
Nov 4 19:06:15 MacBook-Pro opendirectoryd[59]: [session] ODQueryCreateWithNode completed
Nov 4 19:06:17 MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[256]: Use NVRAM prev-lang:kbd value (252) as default ASCII input source: ABC
Nov 4 19:06:17 MacBook-Pro com.apple.appkit.xpc.openAndSavePanelService[256]: Use NVRAM prev-lang:kbd value (252) as default ASCII input source: ABC
Click to expand...
Installation crash after Verifying SharedSupport.dmg

Help me please.
 

Attachments

  • Screenshot 2020-11-04 at 22.56.42.png
    Screenshot 2020-11-04 at 22.56.42.png
    220.3 KB · Views: 344
  • Like
Reactions: TimothyR734
jackluke said:
No, that is a BigSur InstallAssistant (or other installer framework) failing checks that you don't have a supported BigSur Mac, to fix this you simply could use this method:

sudo nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"

reboot and check "nvram boot-args", then apply the ASentientBot HaxLib patch for machines with non-APFS firmware: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28619108

launch the Hax3.app or if for some reason not work, copy the Hax.dylib file to your home folder /Users/yourusername/ then copy paste from terminal:
launchctl setenv DYLD_INSERT_LIBRARIES $PWD/Hax.dylib

relaunch the BigSur installer from HighSierra desktop and it should work.
Click to expand...

Thanks. I did try these steps above, no change. I do have an APFS-capable Mac (iMac 11,1) if that matters at all.

Running "nvram -p" returns (among many other things): run-efi-updater No%00

I also tried all steps listed here.
 
Last edited:
  • Like
Reactions: TimothyR734 and macinfo
Alex-Microsmeta said:
@ASentientBot @jackluke @Barry K. Nathan could you search a fix to avoid CMD+S to enable USB mouse and keyboard on BigSur running on Mac mini 2010 Core 2 Duo Penryn (Macmini4,1) Thank you!
Click to expand...

If you replace in BigSur SLE the ASentientBot Catalina patched IOHIDFamily can skip CMD+S , @hvds also patched (through ASentientBot method) BigSur IOHIDFamily.kext , you could use his modified micropatcher script: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29159130

I also plan to add it for "BaseSystem Legacy USB fix" , I already made some patching bash apps for BigSur recovery, but at this point before releasing, I wait for the upcoming BigSur Release Candidate .
 
  • Like
Reactions: TimothyR734, webg3 and Alex-Microsmeta
jackluke said:
If you replace in BigSur SLE the ASentientBot Catalina patched IOHIDFamily can skip CMD+S , @hvds also patched (through ASentientBot method) BigSur IOHIDFamily.kext , you could use his modified micropatcher script: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29159130

I also plan to add it for "BaseSystem Legacy USB fix" , I already made some patching bash apps for BigSur recovery, but at this point before releasing, I wait for the upcoming BigSur Release Candidate .
Click to expand...
Thank you! Since I cannot still use mount -uw / to replace kekts, I'll wait your patches on RC :)
 
  • Like
Reactions: TimothyR734 and jackluke
BeatCrazy said:
Thanks. I did try these steps above, no change. I do have an APFS-capable Mac (iMac 11,1) if that matters at all.

Running "nvram -p" returns (among many other things): run-efi-updater No%00

I also tried all steps listed here.
Click to expand...

If your iMac11,1 has a Lynnfield/Nehalem cpu, you should use OpenCore boot loader with @khronokernel SSDT patch for ACPI kp to boot the BigSur installer.

Moreover some late 2009 Mac even if with APFS firmware they still embed Legacy USB devices (requiring an additional LegacyUSBInjector patch) so I made a preconfigured opencore setup with khronokernel SSDT patch and Legacy USB (to encounter few issues with "Legacy USB BKE" install BigSur on internal SATA disk).

Make a stock BigSur createinstallmedia installer, then try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-29138842

The OpenCore4b1 setup is totally safe because doesn't contain any spoofing for OTA BigSur updates so no risk of firmware update during stage2 installer.
 
  • Like
Reactions: ASentientBot, TimothyR734, webg3 and 1 other person
Today I successfully installed DP 11.01 on my cMP 5.1 with @Barry K. Nathan ´s latest patcher. The installation went through without problems but one abnormality after phase 1. During reboot the machine connected all drives ( could hear it by DVD an BD drives ) but then booted into the USB Installer again. Here a window (no mouse or keyboard support ) with the language chooser and Mac update assistent opened. The update assistent did not do anything so I removed the USB drive and did a hard reset. Then the machine finished the setup without any problem.

Both mBP Mid 2012 are also working without any problems after using identic USB drive
 

Attachments

  • Bildschirmfoto 2020-11-05 um 09.44.52.png
    Bildschirmfoto 2020-11-05 um 09.44.52.png
    137.7 KB · Views: 293
Last edited:
  • Like
Reactions: TimothyR734
Hi there,

I've just installed BigSur 11.0.1 on my cMP 5.1 with @Starplayr "bigmac" solution, directly from Catalina, to a brand new APFS volume just next to Catalina's. https://github.com/StarPlayrX/bigmac
It was so easy, and without USB stick! :D Thanks StarPlayerX!!!

The only thing that doesn't work is Wifi. Has he say "Currently this patch tool does not install Apple's WiFi drivers. I have you a Broadcom BCM43xx 1.0 device. Native AirPort drivers should work.".

I have a Broadcom BCM43xx 1.0 device too. But the device is not seen.

Is there a way to force install Broadcom BCM43xx 1.0 drivers?

:)
 
Last edited:
  • Like
Reactions: TimothyR734, macinfo and webg3
alfon_sico said:
I have one issues in Big Sur, I don't know if they could be for new macOS version or because my is an "unsupported Mac"

- TP_link adapter T4U installation. the driver is not updated for Big Sur however when I install it works, however the problem is the installation process. Just in the end show a message that doesn't complete the installation process. Anyway it works, load the manager and connect to wifi

The problem is that every time I reboot I need to re-install the driver and configure the wifi connection

Can I force the installation process in any way?
Click to expand...

Manually add the TP Link utility in Login Items under users and in Accessibility under privacy. Check the screenshots.
Screenshot 2020-11-05 at 16.49.58.png
Screenshot 2020-11-05 at 16.51.53.png
 
  • Like
Reactions: alfon_sico, pyedog, TimothyR734 and 1 other person
Just to chime in and say that after testing everything I could in a MacBook Air 2019 loaned from the office (since Big Sur beta 1), I found 11.0.1 to be good enough to take the plunge and make an in-place upgrade of my main driver, an 9,2 MBP Mid-2012 Unibody.

I used @Barry K. Nathan 's 0.5.0 patcher and it was, as I expected, flawless.Everything is working perfectly with the sole exception of having to reconnect manually 2 or 3 times the Wi-Fi after the Mac goes to sleep (it gives the "network not found" error on the first attempt). It's no big deal, and certainly not a showstopper.

Being an in-place upgrade also meant that I didn't have to reinstall the whole mess of my tools/apps, which was a definite plus.

Kudos to @Barry K. Nathan , @ASentientBot and everyone who worked (and still are working) hard to make this possible. From a Macintosh 128K veteran to all of you, hats off (man, do I feel old xD).

Thanks for giving me at least another year with this machine. I think this will be the last and I will be sorry to see it go, since it has served my daily needs since 2012 (and admirably well, given its age), but I think I'm getting overdue for an upgrade. Anyway, for now. I'm happy to have it for one last year.

Thanks again.
 

Attachments

  • MBP.png
    MBP.png
    115.7 KB · Views: 285
  • Like
Reactions: Ausdauersportler, ASentientBot, TimothyR734 and 1 other person
i'm more than happy to have support by all you master ethic hackers (or RC hackers if you prefer :) ) and I hope that this forum will never be closed if Mac Silicon will spread worldwide since November, 10 ...But maybe it will be possible to "open" A14x & A14T too, to free up all new macs potentials.
 
  • Like
Reactions: TimothyR734 and macinfo
Alex-Microsmeta said:
i'm more than happy to have support by all you master ethic hackers (or RC hackers if you prefer :) ) and I hope that this forum will never be closed if Mac Silicon will spread worldwide since November, 10 ...But maybe it will be possible to "open" A14x & A14T too, to free up all new macs potentials.
Click to expand...
Apple should support latest Intel Macs for a few years from now, so we can bet on maybe a 4, 5 years window before the end of Intel machines support.
 
  • Like
Reactions: TimothyR734, macinfo and iMac-iPad
djr004 said:
Not sure what's going on. I haven't been able to install Beta 10 or the latest beta. I haven't had any issues on my Late 2013 iMac up through Beta 9 and now all of sudden I keep getting "The update cannot be installed on this computer."

I have been using the same install method as rumormiller #579 with all the beta updates. I've been running this on the main SSD of the iMac for a while now. Now I get the error mentioned. Any help?
Click to expand...
Unfortunately that method is now out of date. I've successfully updated to 11.0.1 Beta on my iMac 2013.

What you need is:

1. Mac OS Install Package 11.0.1

2. Latest version of Barry's Big Sur Micropatcher (v.0.5.0 as of writing this)
https://github.com/barrykn/big-sur-micropatcher/releases/tag/v0.5.0

Follow the instructions big-sur-micropatcher carefully.

Especially use Disk Utility to erase the USB stick using "Mac OS Extended (Journaled)" format and "GUID Partition Map" scheme.

Install the InstallAssistant.pkg.

Use the 'createinstallmedia' command in Terminal

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/UNTITLED

To see the names of your volumes in terminal type:

ls /Volumes

Run Micropatcher.sh to patch the usb stick
Replace <big-sur-micropatcher-main> with actual folder name

sudo ~/Downloads/<big-sur-micropatcher-main>/micropatcher.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Run install-setvars.sh to patch the usb stick

sudo ~/Downloads/<big-sur-micropatcher-main>/install-setvars.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Start up from "EFI Boot"

Boot from "Install macOS Big Sur Beta"

Start the installer and you're done.
 
  • Like
Reactions: abelpinate, vincenzo79, macinfo and 5 others
rumormiller said:
Unfortunately that method is now out of date. I've successfully updated to 11.0.1 Beta on my iMac 2013.

What you need is:

1. Mac OS Install Package 11.0.1

2. Latest version of Barry's Big Sur Micropatcher (v.0.5.0 as of writing this)
https://github.com/barrykn/big-sur-micropatcher/releases/tag/v0.5.0

Follow the instructions big-sur-micropatcher carefully.

Especially use Disk Utility to erase the USB stick using "Mac OS Extended (Journaled)" format and "GUID Partition Map" scheme.

Install the InstallAssistant.pkg.

Use the 'createinstallmedia' command in Terminal

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/UNTITLED

To see the names of your volumes in terminal type:

ls /Volumes

Run Micropatcher.sh to patch the usb stick
Replace <big-sur-micropatcher-main> with actual folder name

sudo ~/Downloads/<big-sur-micropatcher-main>/micropatcher.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Run install-setvars.sh to patch the usb stick

sudo ~/Downloads/<big-sur-micropatcher-main>/install-setvars.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Start up from "EFI Boot"

Boot from "Install macOS Big Sur Beta"

Start the installer and you're done.
Click to expand...


Just a note, instead of "The path to a file" use drag and drop.

So, just drag the "micropatcher.sh" and the "install-setvars.sh" file into the terminal, it autofills the path.

Also, You need sudo for install-setvars.sh but not for micropatcher.sh
 
  • Like
Reactions: TimothyR734, rumormiller and djr004
rumormiller said:
Unfortunately that method is now out of date. I've successfully updated to 11.0.1 Beta on my iMac 2013.

What you need is:

1. Mac OS Install Package 11.0.1

2. Latest version of Barry's Big Sur Micropatcher (v.0.5.0 as of writing this)
https://github.com/barrykn/big-sur-micropatcher/releases/tag/v0.5.0

Follow the instructions big-sur-micropatcher carefully.

Especially use Disk Utility to erase the USB stick using "Mac OS Extended (Journaled)" format and "GUID Partition Map" scheme.

Install the InstallAssistant.pkg.

Use the 'createinstallmedia' command in Terminal

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/UNTITLED

To see the names of your volumes in terminal type:

ls /Volumes

Run Micropatcher.sh to patch the usb stick
Replace <big-sur-micropatcher-main> with actual folder name

sudo ~/Downloads/<big-sur-micropatcher-main>/micropatcher.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Run install-setvars.sh to patch the usb stick

sudo ~/Downloads/<big-sur-micropatcher-main>/install-setvars.sh /Volumes/Install\ macOS\ Big\ Sur\ Beta

Start up from "EFI Boot"

Boot from "Install macOS Big Sur Beta"

Start the installer and you're done.
Click to expand...
Thank you so much. I figured I would use this method once the release candidate comes out. Really appreciate the step by step directions. Looks like I'll be using this soon now.
 
  • Like
Reactions: TimothyR734, rumormiller, Mystere65 and 1 other person
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