Jesus.
Oh come on. Macs do just work, you don't have to be sharp or smart to use them.
Jesus.
It is a problem cause I’m trying to build the patcher bootable drive on a Mac that has T2 chip. I’m getting an error doing it. Which is why he recommended I disable my T2 chip on my functioning Mac so I can create the drive and try to boot the non working Mac.No, i mean he wrote it is t2 cause of your wrong date. 2018/19 have t2, 2008/09 dont have.
So this is not the problem!
No, i mean he wrote it is t2 cause of your wrong date. 2018/19 have t2, 2008/09 dont have.
So this is not the problem!
Thank you for the quick reply!Hav the devs of macrumors made uploading a metal requirement as now I can't upload screenshots so frustrating it was work so good before this remake I bet the whole forum will be metal required
[automerge]1583968993[/automerge]
you might try this run it in your terminal
Ah!It is a problem cause I’m trying to build the patcher bootable drive on a Mac that has T2 chip. I’m getting an error doing it. Which is why he recommended I disable my T2 chip on my functioning Mac so I can create the drive and try to boot the non working Mac.
Make sense now ?
thanks
yes... what i see is all ok. Where is the detail Problem ?Im not sure why i'm having so much trouble with these betas.. i run all of the posted scripts (attached)
Yes I think you have to upgrade to zshThank you for the quick reply!
Does it matter if I run this using the "bash" shell or should I upgrade the shell to "zsh"?
well, I run the script.. MacBook restarts, goes into the install screen. that lasts about 30 sec, then it restarts back to the desktopyes... what i see is all ok. Where is the detail Problem ?
Do you have the swuswitcher app that will tell you which program you are in public or dev beta as the public beta is out as well then you run the swupatch in your terminal so the update appears in the software update in system preferences sometimes it checks twice once you start the download close and reopen your terminal at about 10% or so of the download process run the catalinaswufix5amfi patchIm not sure why i'm having so much trouble with these betas.. i run all of the posted scripts (attached)
before you restart to install the update run this script in the terminal as well sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool truewell, I run the script.. MacBook restarts, goes into the install screen. that lasts about 30 sec, then it restarts back to the desktop
P.S. I even deleted all of the updates in the update folder and started over again.
I have both scripts and have ran the both scripts several times, also did the terminal input you addedDo you have the swuswitcher app that will tell you which program you are in public or dev beta as the public beta is out as well then you run the swupatch in your terminal so the update appears in the software update in system preferences sometimes it checks twice once you start the download close and reopen your terminal at about 10% or so of the download process run the catalinaswufix5amfi patch
[automerge]1584026759[/automerge]
before you restart to install the update run this script in the terminal as well sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true
boot into your Catalina usb patcher in the terminal type csrutil status make sure you SIP is offI have both scripts and have ran the both scripts several times, also did the terminal input you added
if you Mac is 2018-19 it should be able to run Mojave or Catalina and it might be because of the T-2 chipso update cant do thr patcher on my current Mac becuase its a 2019 and I read that dosdude1 patcher has problems with 2018 and later Macs so somehow I will have to get a hold off an old one, or just try to take a to a Mac repair store in the City and see what they say
terminal say :boot into your Catalina usb patcher in the terminal type csrutil status make sure you SIP is off
[automerge]1584030999[/automerge]
is your terminal in macOS using zshterminal say :
-bash-3.2# csrutil status
System Integrity Protection status: disabled (Apple Internal).
-bash-3.2#
yes it isis your terminal in macOS using zsh
2 things you could try if you have tried any previous Beta's trying doing a PRAM reset then try again the other way is if you have a Catalina Patcher do a clean install of 10.15.3 final apply your post install patches and the night shift patch once in your desktop then try running the scripts again there could be something from previous attempts the preventing the update to installyes it is
will try it out2 things you could try if you have tried any previous Beta's trying doing a PRAM reset then try again the other way is if you have a Catalina Patcher do a clean install of 10.15.3 final apply your post install patches and the night shift patch once in your desktop then try running the scripts again there could be something from previous attempts the preventing the update to install
Yes I think you have to upgrade to zsh
This script works fixing safe mode as well both from jacklukeThank you ALL! you are GODS! The recovery fix worked I upgraded the shell and ran the script and tested the recovery and WOO HOO it is there!
as you asked I went back to 10.15.3 from the dosdude1 installer. zapped Pram (3 chimes), redid the scripts.2 things you could try if you have tried any previous Beta's trying doing a PRAM reset then try again the other way is if you have a Catalina Patcher do a clean install of 10.15.3 final apply your post install patches and the night shift patch once in your desktop then try running the scripts again there could be something from previous attempts the preventing the update to install
This script works fixing safe mode as well both from jackluke
Thank you! I have applied the safe mode script and I am typing this reply in safe mode.
[automerge]1584053220[/automerge]