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.
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!
 
  • Like
Reactions: TimothyR734
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!
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
 
  • Like
Reactions: TimothyR734 and 16v
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
Thank you for the quick reply! :)

Does it matter if I run this using the "bash" shell or should I upgrade the shell to "zsh"?
 
  • Like
Reactions: TimothyR734
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
Ah!
Now i understand!

O.k. then good luck!
 
Im not sure why i'm having so much trouble with these betas.. i run all of the posted scripts (attached)
 

Attachments

  • Patch script-beta 5.txt
    1.7 KB · Views: 99
  • Like
Reactions: TimothyR734
yes... what i see is all ok. Where is the detail Problem ?
well, 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.
 

Attachments

  • Screen Shot 2020-03-12 at 10.06.33 AM.png
    Screen Shot 2020-03-12 at 10.06.33 AM.png
    48.8 KB · Views: 117
  • Screen Shot 2020-03-12 at 10.07.21 AM.png
    Screen Shot 2020-03-12 at 10.07.21 AM.png
    35 KB · Views: 108
  • Like
Reactions: TimothyR734
Im not sure why i'm having so much trouble with these betas.. i run all of the posted scripts (attached)
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 patch
[automerge]1584026759[/automerge]
well, 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.
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
 

Attachments

  • swupatch.sh.zip
    1.7 KB · Views: 77
  • catalinaswufix5amfi.command.zip
    1.7 KB · Views: 114
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 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
I have both scripts and have ran the both scripts several times, also did the terminal input you added
 

Attachments

  • Screen Shot 2020-03-12 at 11.01.59 AM.png
    Screen Shot 2020-03-12 at 11.01.59 AM.png
    35.7 KB · Views: 96
  • Screen Shot 2020-03-12 at 11.01.21 AM.png
    Screen Shot 2020-03-12 at 11.01.21 AM.png
    65.8 KB · Views: 119
  • Screen Shot 2020-03-12 at 11.03.53 AM.png
    Screen Shot 2020-03-12 at 11.03.53 AM.png
    44.7 KB · Views: 100
I have both scripts and have ran the both scripts several times, also did the terminal input you added
boot into your Catalina usb patcher in the terminal type csrutil status make sure you SIP is off
[automerge]1584030999[/automerge]
so 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
if you Mac is 2018-19 it should be able to run Mojave or Catalina and it might be because of the T-2 chip
 
  • Like
Reactions: Pinarek
boot into your Catalina usb patcher in the terminal type csrutil status make sure you SIP is off
[automerge]1584030999[/automerge]
terminal say :
-bash-3.2# csrutil status
System Integrity Protection status: disabled (Apple Internal).
-bash-3.2#
 
yes it is
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
 
OR if you have a Catalina Patcher, better if it's the same version as you are running, just boot from it and reinstall the OS over the existing one to "refresh" it. I do it all the time and have for years. It has worked wonders.

Ages ago I confirmed that it could be done, while waiting on hold with Tier 2 Apple Tech Support asking if it would and the guy had to go ask. I thought what the heck and did it while waiting for him to come back. It worked wonderfully and soon after I told him that it did, I saw Apple recommending it in the forums.
 
  • Like
Reactions: TimothyR734
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
will try it out
 
  • Like
Reactions: TimothyR734
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
as you asked I went back to 10.15.3 from the dosdude1 installer. zapped Pram (3 chimes), redid the scripts.
still having the same problem :(
im gonna try the args script one more time.
 
Has anybody been able to get Netflix to work on Safari? It works on the same beta on my MacBook Pro, but I get an unsupported browser error when loading a video page. I cleared the cache and there are no content blocks.
This is on a 5,1 with upgraded video and WiFI/BLE. No patches.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.