I don't remember the date it was released but someone should edit the first page dev beta 3 is 19A487m
I tried it no diceIn Mojave, there was a fix to recover the recovery OS. Is that doable in Catalina as well, yet?
Can I apply this to Mojave?
In Mojave, there was a fix to recover the recovery OS. Is that doable in Catalina as well, yet?
I tried it no dice![]()
Yes, or you can apply this: Mojave VolumeIcons for apple boot manager
[doublepost=1561962152][/doublepost]
The script just needed to integrate or to type before running in Catalina Terminal: sudo mount -uw /
However keep in mind that the "CMD+R" associated to your machine is only the latest macOS installed or re-installed or beta updated.
For example, if on internal disk I have two APFS containers with Mojave and Catalina, and I install/update Catalina, then "CMD+R" Recovery is Catalina, if instead I re-install or update Mojave to its next beta then APFS Recovery becomes the Mojave one.
I used your solution for the working APFS recovery from the page 415 of the Mojave thread. So right now I have Mojave/High Sierra installed. Pressing "CMD+R" will take me to the APFS recovery of the partition that I selected as a Startup Disk in a System Preferences. Do you think that something like that can work for Catalina partition as well?
Try re-downloading a new installer, and also try a different USB drive.
Oh right, I didn't noticed that also selecting from Startup Disk the Recovery was adjusted to the macOS installation, but I guess you have HighSierra in HFS+ , since for APFS container to setting the default Recovery I used typically this: diskutil apfs updatePreboot diskXs1
Just finished another update to Catalina Patcher, which now includes an all-new, fully-automated post-install tool! While it can still be applied manually just like older post-install tool versions, this new one will now be applied automatically for you once the Catalina installation completes, with all the optimal patches for your machine pre-determined.
View attachment 845834
Me helped it to retry the process on an second Mac not running the catalina Beta. Maybe try that. If you don't have a second mac just install the latest supported version for your mac and create a partition from it an the try it on there.I’m Unable to create a usb installer with dosdudes Catalina patcher as it crashes every time, I’ve tried five different usb sticks all 16g and every time it crashes ?????
Any ideas
is there , or will there be a patch to make pci m2 ssd drives to be recognised as internal.Just finished another update to Catalina Patcher, which now includes an all-new, fully-automated post-install tool! While it can still be applied manually just like older post-install tool versions, this new one will now be applied automatically for you once the Catalina installation completes, with all the optimal patches for your machine pre-determined.
View attachment 845834
Is there a new beta out? Your build number ends in "m" whereas mine is the same, but ending in "l". Or is that just public vs. developer beta?
Unfortunately I'm on HFS+ and it support APFS onlyAre any windows transparent? It seems like you achieved a semi acceleration/some sort of CPU based transparency.
[doublepost=1561886383][/doublepost]
You can install Catalina over it and it should work fine. But make sure to have a backup just in case.
As I said before, works very very well with that GPU disabled.Thanks @dosdude1 install on macbook pro 2011 work! I just can not turn off AMD.
The macOS Catalina Patcher 1.0b4 downloads the 15.0.16 19A487m.
This is the public beta.
After installation in Library/Preferences/com.apple.seeding.plist
SeedProgram = 3 (3 is beta / 2 is seed)
and Library/Preferences/com.apple.SoftwareUpdate.plist
https://swscan.apple.com/content/catalogs/others/index-10.15beta-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz
So change after installation:
com.apple.seeding.plist to 2
and in the terminal:
sudo softwareupdate --set-catalog https://swscan.apple.com/content/catalogs/others/index-10.15seed-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard. merged-1.sucatalog.gz
Now everything's alright.
Is there any problem if I leave the public beta numbers?
OK @******* thanks, but how to disable AMD?As I said before, works very very well with that GPU disabled.
Just make an Recovery USB with the latest supported macOS Version for your mac and use this as your recovery-partition. Thats how i a least was able to recover snapshots or backupsThat's a bummer.
Wait... what? On my machine, these used to crash with the earlier versions of my wrappers, but after making some modifications to my code, they no longer do. Are you sure your patcher includes the most recent versions?As of DP2/PB1, it seems that two processes are constantly crashing, causing poor system performance. To disable those processes, run the following commands in Terminal (ignore //AppleInternal... error), then reboot the system:
Code:sudo mount -uw / sudo rm /System/Library/LaunchAgents/com.apple.universalaccessd.plist sudo rm /System/Library/LaunchDaemons/com.apple.PerfPowerServices.plist
You can do it by software, just to try, but if you reset the ram , it will appear the AMD again.OK @******* thanks, but how to disable AMD?
Oh, really? I thought I was using your latest ones... Maybe not. I'll have to check and make sure.Wait... what? On my machine, these used to crash with the earlier versions of my wrappers, but after making some modifications to my code, they no longer do. Are you sure your patcher includes the most recent versions?
I'll attach them here for convenience.
If you are still getting crashes, please send me the logs. My DiagnosticReports folder doesn't have any new .crash files (other than Photoshop) since over a week ago. I didn't realize you guys were still seeing this level of instability with my fixes and I'd like to fix that if possible.
@DragenFi here is a script I wrote for easily applying the Mojave day/night Volume icon for apple startup manager, I also included the possibility to return to the default volume icon.
The script is totally safe and harmless for any machine.
While the apple stock "Mojave icns" didn't worked (previously uploaded), instead these icons that I manually modified/patched will work properly as VolumeIcons.
Wait... what? On my machine, these used to crash with the earlier versions of my wrappers, but after making some modifications to my code, they no longer do. Are you sure your patcher includes the most recent versions?
I'll attach them here for convenience.
If you are still getting crashes, please send me the logs. My DiagnosticReports folder doesn't have any new .crash files (other than Photoshop) since over a week ago. I didn't realize you guys were still seeing this level of instability with my fixes and I'd like to fix that if possible.
This got nothing to do with the patcher.is there , or will there be a patch to make pci m2 ssd drives to be recognised as internal.
as at the moment its external with the wrong icon ?