moosethegoose2213 / automator-for-barrykn-micropatcher Goto Github PK

After booting in selection mode "Press Alt till boots"

1. If I press "EFI Boot icon" Mac boots in that mode. (whaaaa)
2. if I press "Install BigSur icon" it shows me O with line trough it. (nooooooo)

Am I missing something? Hmm...
If some can, please help.

I no longer see a stand alone volume named EFI and I no longer see a Post-Install Automator with my MacPro5,1 (Mid-2010). The readme still has the select EFI boot and do Post-Install. Is that now built-in or is my MacOS 112.1 Installer that was created by this MicroPatcher Automator have an issue? Since everything seems OK. I'm guessing with the latest version, it is doing this in the background

I downloaded the current version (2.0) and in the "Download Installer App" step, the password entry field does not accept a password. The entry field just re-appears every time I hit "authorize".

All I see is the Big Sur installer and my original hard disk. Please let us know how to overcome this issue.

After supplying the password, I get a message stating : "The requested URL was not found on this server".

I installed Big Sur using the Automator. Everything worked fine until I finally booted to USB and selected Post-Automator in Utilities. It failed with the following message:

Macintosh HD
running 11.2.3 detected
/System/Applications/PostAutomator.app/Contents/Resources/postautomator.sh: line 17: dirname: command not found
[Out] Recovery mode detected!
/Volumes/Image Volume
If you can read this, that means that I probably broke something ...

I am using a Late 2013 iMac where I replaced the 3 TB fusion drive by a 2 TB SSD drive.

Interestingly, when I am using the installed Big Sur 11.2.3 everything works fine and seamlessly. I did not experience any problems so far when playing around with the system.

But, to be honest, I am not sure what could be missing due to the failure of the Post-Automator.

(Yes, I'm using the patcher even though I said I never would)
I don't know if this is intended, but for some reason the app is downloading 11.1 instead of 11.2. If this is intended, then pardon me, but I just want to throw it out there that not the newest version is downloading for me. Is anyone else experiencing this?

Since a download of the micro patcher ends up normally in the ~/Downloads folder why you ask user to move the patcher folder to the ~/Desktop manually (it is an automator :-) )

BTW: Great work!!

I've been having issues manually patching my USB drive, mainly with install-setvars, so I resorted to using the Automator. (By the way, it's awesome, and I hope one day it is actually implemented in barrykn's.) I was pleasantly surprised when it informed me that the USB flash drive was successfully patched. However, when I restarted and held the Option button, I couldn't find EFI Boot, meaning there was an error setting up setvars. But Automator didn't mention this error.

Is there a way to have Automator spit out some kind of log or notify the user that an error has occurred? For example, it can detect if the log says "install-setvars cannot continue" so it spits out that error, or something like that.

One other feature suggestion is having a progress bar for createinstallmedia. I did see it working behind the scenes in Activity Monitor, but having some kind of indicator that it's ongoing would be a nice GUI touch.

I DEMAND MY CREDIT!!! I CO-CREATED THIS!!! I NEED ACCESS AND RIGHT TO UTILIZE!!!

Good afternoon from Argentina, I tell you that I used the wizard that I got from GitHub, I did the whole process in an excellent way, but when I wanted to start the pendrive it only told me Install macOS Big Sur, it never showed me EFI Boot as the tutorial of Git ... Outside of this, I decide to try to start from [Install macOS Big Sur] and it immediately gives me an error, why can it be? I have a MacBookPro8.1!

Hi, I would appreciate it if you could include in your patcher a means of resuming downloads. Where I live, the network is slow and patchy, and many breaks occur. It would make life easier for me, and many others, I think. Thank you very much

Hi, I have installed your Big Sur Micropatcher which works great but I am having boot issues when I start my computer from a cold start it sometimes does not find the hardrive and I so an SMC reset and it boots OK after that. Any suggestions or script I could download to fix? I have a Mac Pro 2012 6 core 3.33 GHz 6-Core Intel Xeon 32 gig ram thank you in advance cheers John

When trying to run the automator from 10.13, an empty password did not get accepted any time authorization was needed.
Only after setting the password, I was able to use the tool.

Possibly some input verification prevents this.

hello,
having performed successfully the installation of big sur 11.2.3 onto a cMP 5.1 with a metal capable nvidia geforce gtx 680.
what is now not possible anymore ist the boot into internal recovery partition (cmd + r). with each try it is performing an endless reboot until release. zap the pram did also not help out.

setup steps to big sure were the following:

1. installation of catalina with the most actual patcher from dosdude1 (-> internal boot to recovery worked)
2. installation of big sur 11.2.3 with the must actual patcher from micropatcher (automator), v2.0 (-> no internal boot to recovery possible, although partition ist present and visible via diskutil list, csrutil is disabled, nvram no compat check is in).

what is missing?
any targeting advices are welcome.
regards,
netshare

Hi!

Really cool development, I was just inspecting the instructions @JackLuKe made to make such an enhancement myself when I found your code and tool. Would it be possible that you link in the micro patcher source code like a fork instead of creating a complete copy.

Background: The micro patcher has more that 80 forks and some of them may step forward and it would be nice to use your tool with the upcoming versions.

Thanks in advance