Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Will Dos Dude be able to get the 2010 imac with upgrades supported. I have added more ram and a SSD.
This posting by Dosdude1 might help you to understand.


Hopefully the terrific Nathan and the wonderful others here might help you.
 
From the past ones why were older imacs supported. Why is the card that bad?
Also what about an external gpu would that be posable?
 
I have this problem if someone could help please I install Big Sur from here version 3. https://github.com/BenSova/Patched-Su... the problem I have is I can't unlock the info plist to change in there so I can have full brightness in iMac mid 2011 27 quadro k3100m.in Catalina from dos dude patcher everything was unlocked so I could change things and have full brightness.how do I get access read and write in files.ive tried everything with no luck.
Patched Sur ≠ Catalina Patcher. I don't control what kexts you get with an Info.plist. Right now it's still using the micropatcher's patch-kexts.sh command, but that will change soon so I can better integrate it with the GUI. The script is on the USB installer.
 
I removed the BT card ages ago, tried doing that just now - still getting a prohibited sign.
I don't know why, but if you patch install media by usb fix 1 and 2, under Mac Pro 2008 - it's 100% be unusable and you got bootloop. Both of my USB sticks, that i compilled and it 100% worked on Mac Pro 2008, i patch at Mac Mini Late 2009.

And i recomended to patch you EFI Bootrom by DosDude1 APFS Rom Patcher - it's do your installation less painfull.
 
  • Like
Reactions: AlexSakha67
Hi, I have Mac Pro 3.1 AMD Radeon HD 5770 for several days could not install Big Sur. It turns out I did not flash APFS ROM Patcher. After the firmware, everything was installed immediately.

По английски через переводчик google,может я не правильно написал😋
Спасибо "Макс Твой ЗнакомыйАйтишник»👍
Many thanks to all programmers DosDude1👍🙂
StarPlayrX Super 🍔 bigmac👍
Jacklukem BigSurfixes BigSurBaseSystemfix Super👍
 

Attachments

  • Снимок экрана 2020-11-30 в 02.03.05.png
    Снимок экрана 2020-11-30 в 02.03.05.png
    48.1 KB · Views: 125
  • Снимок экрана 2020-11-30 в 16.07.26.png
    Снимок экрана 2020-11-30 в 16.07.26.png
    82.2 KB · Views: 167
  • 20201130_162523.jpg
    20201130_162523.jpg
    105.4 KB · Views: 117
Last edited:
  • Like
Reactions: yezza and Pri-est
I have this problem if someone could help please I install Big Sur from here version 3. https://github.com/BenSova/Patched-Su... the problem I have is I can't unlock the info plist to change in there so I can have full brightness in iMac mid 2011 27 quadro k3100m.in Catalina from dos dude patcher everything was unlocked so I could change things and have full brightness.how do I get access read and write in files.ive tried everything with no luck.
Got to the first page and read about the micro patcher and how to make changes to your root partition/slice/container. The other pay is to use the patch-kext.sh I published on the GPU thread. It will automatically select the fitting extensions based on your GPU and there will be no need to manually change things, including the backlight fix. It is compatible with micro patcher 0.5.1.
 
Hi, I have Mac Pro 3.1 AMD Radeon HD 5770 for several days could not install Big Sur. It turns out I did not flash APFS ROM Patcher. After the firmware, everything was installed immediately.

По английски через переводчик google,может я не правильно написал😋
Спасибо "Макс Твой ЗнакомыйАйтишник»👍
Many thanks to all programmers DosDude1👍🙂
StarPlayrX Super 🍔 bigmac👍
Jacklukem BigSurfixes BigSurBaseSystemfix Super👍

I can guarantee that installing BigSur also without an APFS ROM is doable, only require some additional efforts using OpenCore (to show hidden APFS "macOS Installer"), from your pictures you combined bigmac patches with BigSurFixes on MacPro3,1 with DDR2 RAM and a non Metal AMD GPU that provides a bootscreen for apple startup manager and don't require SSE4.2 instruction , I guess instead as discussed with @Syncretic that many that encountered issue in installing BigSur on those MacPro3,1 are using a Metal AMD GPU without a bootscreen, apart also that Bluetooth 2 hardware kp issue that needs to unplug, I mean MacPro3,1 has enough different configurations.

I ask if you can test on your MacPro3,1 this version of OpenCoreAPFSloader: OpenCore4b1.zip (if this doesn't show any additional graphics menu then try this text menu OpenCore3b1.zip )
simply unzip and copy the EFI folder to any USB FAT32 device, then try booting alt-option that EFI Boot with custom icon and select BigSur.

To boot BigSur again from apple startup manager without OpenCore simply from opencore select "Restart fix".
 
After weeks of trying and days with the help of @jackluke going back and forth and most importantly patience my Macbook Pro 17” early 2008 is running Big Sur. Wifi and sound works. Will update more later. Super excited!
Are you able to help me get it running on mine?
 
Hey. Yesterday I managed to install macOS Big Sur 11.0.1, the Patched Sur doesn't work for me either, I can't install kexts. What to do in this case?
 

Attachments

  • Снимок экрана 2020-11-30 в 13.43.01.png
    Снимок экрана 2020-11-30 в 13.43.01.png
    4.2 MB · Views: 170
Yeah a lot of people are having issues with his post-install app. That's why I'm trying at a post-install in recovery, which will work almost guaranteed. I can't just paste his app to recovery, as recovery doesn't allow for Swift.
 
My post-install will be in shell, so it won't be as pretty, but it will WORK without terminal knowledge.
 
I can't just paste his app to recovery, as recovery doesn't allow for Swift.

Correct, booting from BigSur recovery any developed based macOS Aqua, Cocoa or Carbon app is not so easily, because in general the recovery Frameworks are forked (a bit different from those in a full macOS installation) and mainly since BigSur release their exec are just an alias for those embedded in dyld_shared_cache_x86_64 .

I am not skilled in build nice GUI apps (also my shell script are not so clever), anyway I don't exclude that patching the BaseSystem.dmg adding SwiftUI.framework (unless it has other "otool" frameworks dependencies) could allow even to boot a swift developed app from 11.x recovery, but there is another little issue that is BigSur recovery is themed in dark mode, that means it uses probably only dark assets CAR files , I tried for fun to force using the light mode theme, but many context menu are unreadable, so who develop an app for recovery should use dark mode .
 
  • Like
Reactions: hvds and MacHacJac
I can guarantee that installing BigSur also without an APFS ROM is doable, only require some additional efforts using OpenCore (to show hidden APFS "macOS Installer"), from your pictures you combined bigmac patches with BigSurFixes on MacPro3,1 with DDR2 RAM and a non Metal AMD GPU that provides a bootscreen for apple startup manager and don't require SSE4.2 instruction , I guess instead as discussed with @Syncretic that many that encountered issue in installing BigSur on those MacPro3,1 are using a Metal AMD GPU without a bootscreen, apart also that Bluetooth 2 hardware kp issue that needs to unplug, I mean MacPro3,1 has enough different configurations.

I ask if you can test on your MacPro3,1 this version of OpenCoreAPFSloader: OpenCore4b1.zip (if this doesn't show any additional graphics menu then try this text menu OpenCore3b1.zip )
simply unzip and copy the EFI folder to any USB FAT32 device, then try booting alt-option that EFI Boot with custom icon and select BigSur.

To boot BigSur again from apple startup manager without OpenCore simply from opencore select "Restart fix".
OpenCore3b1 Yes there is a download mac OS Big Sur.👍
OpenCore4b1.zip No 😞
 

Attachments

  • A)20201130_211609.jpg
    A)20201130_211609.jpg
    176.5 KB · Views: 122
  • B)20201130_214942.jpg
    B)20201130_214942.jpg
    161.9 KB · Views: 106
  • C)20201130_214359.jpg
    C)20201130_214359.jpg
    180.1 KB · Views: 102
  • D)20201130_214505.jpg
    D)20201130_214505.jpg
    195.5 KB · Views: 101
Correct, booting from BigSur recovery any developed based macOS Aqua, Cocoa or Carbon app is not so easily, because in general the recovery Frameworks are forked (a bit different from those in a full macOS installation) and mainly since BigSur release their exec are just an alias for those embedded in dyld_shared_cache_x86_64 .

I am not skilled in build nice GUI apps (also my shell script are not so clever), anyway I don't exclude that patching the BaseSystem.dmg adding SwiftUI.framework (unless it has other "otool" frameworks dependencies) could allow even to boot a swift developed app from 11.x recovery, but there is another little issue that is BigSur recovery is themed in dark mode, that means it uses probably only dark assets CAR files , I tried for fun to force using the light mode theme, but many context menu are unreadable, so who develop an app for recovery should use dark mode .
I wasn't aware that you can patch a SwiftUI framework. In my past experiences, it would crash or glitch the recovery a lot. How might patching the SwiftUI framework be possible in the most stable manner?

I'd love to do SwiftUI as I know the language well and it looks nice with a proper GUI, unlike shell.
 
OpenCore3b1 Yes there is a download mac OS Big Sur.👍
OpenCore4b1.zip No 😞

I suspect that those who encountered issues in booting OpenCore4b1 , I guessed it was the non apple GPU (but you are using non Metal ATI so I exclude it), instead probably is due to DDR2 RAM maybe incompatible with newer OpenCore.efi version, but not sure yet, could you try from OpenCore3b1 open in this folder /EFI/OC/Drivers/

rename OpenCanopy.efi to OpenCanopy2.efi and then retry to boot with alt-option key the EFI Boot (that contains OpenCore3b1 with renamed file) from external FAT32 USB , it should show a graphics menu instead of text menu, if works this doesn't add any additional functionality but let me to debug why newer OpenCore version stuck on apple logo loading bar with DDR2 RAM Mac.
 
I suspect that those who encountered issues in booting OpenCore4b1 , I guessed it was the non apple GPU (but you are using non Metal ATI so I exclude it), instead probably is due to DDR2 RAM maybe incompatible with newer OpenCore.efi version, but not sure yet, could you try from OpenCore3b1 open in this folder /EFI/OC/Drivers/

rename OpenCanopy.efi to OpenCanopy2.efi and then retry to boot with alt-option key the EFI Boot (that contains OpenCore3b1 with renamed file) from external FAT32 USB , it should show a graphics menu instead of text menu, if works this doesn't add any additional functionality but let me to debug why newer OpenCore version stuck on apple logo loading bar with DDR2 RAM Mac.
Okay I will try :)
 
Hey. Yesterday I managed to install macOS Big Sur 11.0.1, the Patched Sur doesn't work for me either, I can't install kexts. What to do in this case?
In this case you go back to the first post of this thread and read or you go directly to the micro patcher page and study the last section if the docs provided there....

Possible you follow my posts on the GPU thread, I published there the iMac aware patch-kext.sh. Unfortunately @Barry K. Nathan seems to by busy and development stuck there right now.
 
I suspect that those who encountered issues in booting OpenCore4b1 , I guessed it was the non apple GPU (but you are using non Metal ATI so I exclude it), instead probably is due to DDR2 RAM maybe incompatible with newer OpenCore.efi version, but not sure yet, could you try from OpenCore3b1 open in this folder /EFI/OC/Drivers/

rename OpenCanopy.efi to OpenCanopy2.efi and then retry to boot with alt-option key the EFI Boot (that contains OpenCore3b1 with renamed file) from external FAT32 USB , it should show a graphics menu instead of text menu, if works this doesn't add any additional functionality but let me to debug why newer OpenCore version stuck on apple logo loading bar with DDR2 RAM Mac.
Direct download to Catalina:rolleyes:
 

Attachments

  • 20201201_013809.jpg
    20201201_013809.jpg
    330 KB · Views: 109
  • 20201201_013925.jpg
    20201201_013925.jpg
    324.5 KB · Views: 102
  • 20201201_013941.jpg
    20201201_013941.jpg
    274.1 KB · Views: 87
  • Like
Reactions: jackluke
Direct download to Catalina:rolleyes:

At this point I guess OpenCanopy.efi is incompatible with DDR2 RAM (or something else) , try just this from the OpenCore4b1 folder open in this folder /EFI/OC/Drivers/ and rename OpenCanopy.efi to OpenCanopy2.efi and select as external USB FAT32 the EFI Boot (that is OpenCore4b1 with that renamed file) and it should show a text menu (without some additional features) from where you could try booting BigSur that means newer OpenCore.efi is compatible with DDR2 RAM.
 
  • Like
Reactions: AlexSakha67
Hi, I have Mac Pro 3.1 AMD Radeon HD 5770 for several days could not install Big Sur. It turns out I did not flash APFS ROM Patcher. After the firmware, everything was installed immediately.

По английски через переводчик google,может я не правильно написал😋
Спасибо "Макс Твой ЗнакомыйАйтишник»👍
Many thanks to all programmers DosDude1👍🙂
StarPlayrX Super 🍔 bigmac👍
Jacklukem BigSurfixes BigSurBaseSystemfix Super👍
Amazing how you got your Mac Pro 3,1 to work so easy. My Mac Pro 3,1 have the flash APFS as you can see in the attached screen shot. My Mac Pro still repeat the boot cycle when it starts the install. I tried the following and all results to the repeated boot cycle;;
video cards used: ATI 5870 Mac Edition, Sapphire Radeon HD 7950 Mac Edition, Sapphire Radeon RX 580, Nvidia GTX 680,
OpenCore used: OpenCore3b1, OpenCore4b1, USBOpenCoreAPFSloader4b, OpenCore 0.6.1 and 0.6.3
StarPlayrX/bigmac-master
 

Attachments

  • Screen Shot 2020-11-30 at 8.47.23 AM.png
    Screen Shot 2020-11-30 at 8.47.23 AM.png
    189.6 KB · Views: 125
Amazing how you got your Mac Pro 3,1 to work so easy. My Mac Pro 3,1 have the flash APFS as you can see in the attached screen shot. My Mac Pro still repeat the boot cycle when it starts the install. I tried the following and all results to the repeated boot cycle;;
video cards used: ATI 5870 Mac Edition, Sapphire Radeon HD 7950 Mac Edition, Sapphire Radeon RX 580, Nvidia GTX 680,
OpenCore used: OpenCore3b1, OpenCore4b1, USBOpenCoreAPFSloader4b, OpenCore 0.6.1 and 0.6.3
StarPlayrX/bigmac-master
Let's try this image to "clean" install
Google

It contains patched by USB fix1 and fix2 installer, and BigMac's Folder , for performing postinstall after installation complited.
And you should be shut down Mac, and remove USB stick after postinstall patching.
 
Last edited:
Amazing how you got your Mac Pro 3,1 to work so easy. My Mac Pro 3,1 have the flash APFS as you can see in the attached screen shot. My Mac Pro still repeat the boot cycle when it starts the install. I tried the following and all results to the repeated boot cycle;;
video cards used: ATI 5870 Mac Edition, Sapphire Radeon HD 7950 Mac Edition, Sapphire Radeon RX 580, Nvidia GTX 680,
OpenCore used: OpenCore3b1, OpenCore4b1, USBOpenCoreAPFSloader4b, OpenCore 0.6.1 and 0.6.3
StarPlayrX/bigmac-master

You have many useful different non Metal and Metal GPUs for testing, currently any of my OpenCore4 (based on 0.6.x binaries) setup are incompatible with MacPro3,1 (due to OpenCanopy that is the graphical menu), OpenCore3b1 (based on 0.5.9 binaries) at least should show the text menu, but the BigSur staged installer on that machine is problematic, recently some reported that unplugging the Bluetooth 2 internal device avoid some kp .

Anyway I still guess that a bit of incompatibility with BigSur kernel is due to Intel Xeon cpus based on Nehalem or similar architecture or maybe DDR2 RAM quantity installed or its layout , then for those machines especially with non EFI apple Metal GPU is required a more advanced OC config.
 
In this case you go back to the first post of this thread and read or you go directly to the micro patcher page and study the last section if the docs provided there....

Possible you follow my posts on the GPU thread, I published there the iMac aware patch-kext.sh. Unfortunately @Barry K. Nathan seems to by busy and development stuck there right now.
Yes, I read your posts. But the patch patch-kext.sh unfortunately did not help me either, maybe I did something wrong. I wonder why @dosdude1 didn't develop his patch this time?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.