yes I have the same problem .. but nobody believed me here. It is definitely on the side of dosdude1 and not on the Google Chrome cache or anything else.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
To anyone who is having issues downloading latest patcher, clear safari history and it should work, it worked for me
[automerge]1585577983[/automerge]
[U]jackluke[/U] sorry for another question, I have successfully gotten the update fix and ota update fixer working. The issue is when the mac restarts to install the update, it reboots into the OS instead of the update progress screen. I think this issue is with the MacBook pro 5,5 as the same thing happens when trying to install thee update uing Dosdude's patcher when the install to this machine is used.
[automerge]1585577983[/automerge]
[U]jackluke[/U] sorry for another question, I have successfully gotten the update fix and ota update fixer working. The issue is when the mac restarts to install the update, it reboots into the OS instead of the update progress screen. I think this issue is with the MacBook pro 5,5 as the same thing happens when trying to install thee update uing Dosdude's patcher when the install to this machine is used.
Hi just had the idea of downloading with Firefox and in fact DID download 1.35. Seems the Safari & Safari tech preview I was using was linking because of cache??? to the previous link of 1.30. In process of creating USB patcher With 1.35 install and will report once done.
UPDATE: I can confirm that Dosdude patcher 1.35 works. As mentioned above I believe it had to do with a cache "issue" in Safari connecting to 1.30 (should have checked ver. before starting; lesson learned). Everything installed without a hitch. One thing however certain apps on first launch after install of 10.15.4 would crash. After several tries to relaunch and same crash result (3-4x) the apps would then open normally (ex. Office 2019 apps, Boom 3D, while others such as Adobe Acrobat PS would open on first launch after install) I am a newbie perhaps it has something to do with the programs plist??). In any case on my MBP 8,2 the install went smoothly. I will have to reinstall airdrop (AirDropInfoView.nip etc.) but should not be problematic.
Last edited:
Yes, currently the OTA update installer correctly proceed only on APFS firmware machines or APFS ROM patched, because from a certain Catalina release the "macOS Installer" is an APFS volume (previously was an HFS installer), anyway I guess I found a way to force booting from "macOS Installer" temporary volume, using nvram or another boot loader (different from the apfs loader script) but I'd want to test this after 10.15.5 beta 1 .
Meanwhile from catalina terminal if you type: diskutil list (or diskutil apfs list)
can you notice a "macOS Install Data" Volume ?
Maybe if in System Preferences APFS Startup Disk you could select the macOS Installer as bootable volume.
I have already updated using dosdude's patched version from USB stick. I will try the other suggestions once the beta comes out.
Thanks as always.
Has anyone had any issues with booting a usb installer or to Catalina after a successful upgrade? I was able to upgrade to 10.15.4 however the Apple logo progress bar will not move at at all following a reboot.
I can't seem to get a USB installer to boot either (tried the usb drive on another machine and it works fine).
I can't seem to get a USB installer to boot either (tried the usb drive on another machine and it works fine).
Other than a browser issue, I don't know what the problem is. It works perfectly and downloads the newest patcher every single time I try it out.
Just let you know jackluke your CatalinaOTAswufix does enable SIP on mu iMac 9,1 I tested it again rebooted and could not get into the desktop rebooted in the Catalina Patcher entered csrutil disable in the terminal back into the desktopThank you jackluke I deleted the libraryvalidation script.plist from the Launchdaemons folder everything is running smooth again
All that is req. is fan speed, CPU die temp, CPU, Memory and network activity. What is really missed is the iStatPro widget from Mojave and back. Basic but great for comparing various OS. Snow Leopard, El Capitan, High Sierra, Mojave and two versions of Catalina reside on this Mini3,1 which came with Snow Leopard but I digress. Still have a few more installs to go on iStatMenus licence, again, much thanks for the observations.😎
Just let you know jackluke your CatalinaOTAswufix does enable SIP on mu iMac 9,1 I tested it again rebooted and could not get into the desktop rebooted in the Catalina Patcher entered csrutil disable in the terminal back into the desktop
My app doesn't enable SIP, rather it's the new OTA update installer that refreshing system files re-enabled SIP itself for known apple security reasons, but if you use the latest 1.3.5 post-install patches , even with SIP enabled Catalina will boot to desktop because the ASentientBot patched boot.efi disables automatically SIP.
Last edited:
Premise: my CatalinaOTAswufix will work without issues on any APFS native firmware and APFS ROM patched machine.
Some "OTA update debugging" for non-APFS firmware machine (those who use the apfs efi shell loader script):
After downloaded, the automatic OTA preparing puts its APFS OTA installer in this path:
/YourCatalinaLabel/System/Volumes/YourCatalinaLabel/macOS Install Data/
During the first apple logo the OTA process copies the content of /Library/Updates/yourOTAnumber/ to this path:
/YourCatalinaLabel/System/Volumes/YourCatalinaLabel/macOS Install Data/Locked Files/Product Files/yourOTAnumber/
The automatic OTA phase sets also some kind of nvram about this: -rootdmg-ramdisk auth-root-dmg=file:///macOS%20Install%20Data/Locked%20Files/BaseSystem.dmg
and of course sets the boot.efi to this: macOS Install Data/Locked Files/Boot Files/boot.efi
(I intercepted these informations using single user mode during the OTA update)
Regardless of that, I got unhidden and bootable the macOS Install Data that from an apple startup manager has the label "macOS Installer", but it involves to use OpenCore boot loader instead of apfs loader script, it worked but I need further tests on OpenCore before release any package for non-APFS machines.
Some "OTA update debugging" for non-APFS firmware machine (those who use the apfs efi shell loader script):
After downloaded, the automatic OTA preparing puts its APFS OTA installer in this path:
/YourCatalinaLabel/System/Volumes/YourCatalinaLabel/macOS Install Data/
During the first apple logo the OTA process copies the content of /Library/Updates/yourOTAnumber/ to this path:
/YourCatalinaLabel/System/Volumes/YourCatalinaLabel/macOS Install Data/Locked Files/Product Files/yourOTAnumber/
The automatic OTA phase sets also some kind of nvram about this: -rootdmg-ramdisk auth-root-dmg=file:///macOS%20Install%20Data/Locked%20Files/BaseSystem.dmg
and of course sets the boot.efi to this: macOS Install Data/Locked Files/Boot Files/boot.efi
(I intercepted these informations using single user mode during the OTA update)
Regardless of that, I got unhidden and bootable the macOS Install Data that from an apple startup manager has the label "macOS Installer", but it involves to use OpenCore boot loader instead of apfs loader script, it worked but I need further tests on OpenCore before release any package for non-APFS machines.
Last edited:
Thanks!
MBP5,2 17" mid 2009.
NightShift patch version 4 installed with Patch Updater.
After your proposed replacements from 10.15.3, NightShift now appears on Monitor Panel and works fine.
(I've tried only with the internal display I don't use an external one)
trying to update my iMac 7,1 from catalina 10.15.3 to 10.15.4. is there an easier way to do it rather than downloading the whole O/S also while trying to recrated my patched bootable media with the updated O/S I get an error message saying:
"An error occurred while attempting to save the BaseSystem image. Ensure that there is at least 10GB of free space on your Startup Disk, then try again."
when I check the log this is what I get:
------------------------------------------------------------------------------------------
Mounting BaseSystem.dmg...
/dev/disk3 GUID_partition_scheme
/dev/disk3s1 Apple_HFS /private/tmp/basesystem
Patching BaseSystem.dmg...
hdiutil: couldn't unmount "disk3" - Resource busy
-------------------------------------------------------------------------------------------
The thing is I have 80gb of free space left so it can't possibly be lack of space. Has anyone else experienced this issue? If so how do you get around it?
"An error occurred while attempting to save the BaseSystem image. Ensure that there is at least 10GB of free space on your Startup Disk, then try again."
when I check the log this is what I get:
------------------------------------------------------------------------------------------
Mounting BaseSystem.dmg...
/dev/disk3 GUID_partition_scheme
/dev/disk3s1 Apple_HFS /private/tmp/basesystem
Patching BaseSystem.dmg...
hdiutil: couldn't unmount "disk3" - Resource busy
-------------------------------------------------------------------------------------------
The thing is I have 80gb of free space left so it can't possibly be lack of space. Has anyone else experienced this issue? If so how do you get around it?
Booting from USB Catalina Patcher, open terminal and type "csrutil disable", close terminal and reapply the post-install patches.
Last edited:
Boot holding CMD+V in verbose mode, if you notice many AMFI strings, means that you need to disable SIP from a recovery environment, if your CMD+R doesn't work, then you should make from another mac an external USB Recovery using for example this tool: https://github.com/chris1111/Catalina-Recovery-HD-Partition
Once you boot from a recovery environment, open terminal type:
csrutil disable ; reboot
Are you using a 16 USB that is formatted HFS-Extended-Journaled before you make the patcher
Hi guys,
just installed 15.4 with patcher 1.3.5 and got a wird behavior, the same I already had with 1.3.1 When I install it every restart ends in a black screen But when I hit the option key I come to the boot screen and can 1. finish the installation 2. finish the post install and 3. boot the finished 15.4. But every reboot without holding down the option key ends in a black screen. I use a iMac 11,3 (late 2010) and upgraded the GPU to a metal compatible one NVIDIA GTX 765M. With 15.3 everything was fine. Any recommendations how I can boot without holding down the option key? Everything else seems to run fine.
Best
just installed 15.4 with patcher 1.3.5 and got a wird behavior, the same I already had with 1.3.1 When I install it every restart ends in a black screen But when I hit the option key I come to the boot screen and can 1. finish the installation 2. finish the post install and 3. boot the finished 15.4. But every reboot without holding down the option key ends in a black screen. I use a iMac 11,3 (late 2010) and upgraded the GPU to a metal compatible one NVIDIA GTX 765M. With 15.3 everything was fine. Any recommendations how I can boot without holding down the option key? Everything else seems to run fine.
Best
Bonsoir,
I have a problem !
I made a very clean install of 10.15.4 with @dosdude1 patcher (1.3.5.) on a freshly "nuked" and repartitioned SSD (MP 3,1 with a GTX 680 2Go full metal compatible).
Everything OK but after each standby, I have this screen :
In my csrutil status :
Configuration:
Apple Internal: enabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
Any idea ?
Many thanks in advance,
Serviteur,
I have a problem !
I made a very clean install of 10.15.4 with @dosdude1 patcher (1.3.5.) on a freshly "nuked" and repartitioned SSD (MP 3,1 with a GTX 680 2Go full metal compatible).
Everything OK but after each standby, I have this screen :
In my csrutil status :
Configuration:
Apple Internal: enabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
Any idea ?
Many thanks in advance,
Serviteur,
Last edited:
sleep is broken in Catalina. Look here: https://forums.macrumors.com/threads/2011-imac-graphics-card-upgrade.1596614/