Anyone yet have success after not being able to install 10.15.2 via Patcher 1.3 via either directly disk or USB stick? I try every other day or so with a different USB stick or starting the Patcher from scratch and having the exact same issues each time.
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
Hey Guys,
2 things:
1. GREAT!
Installed catalina on my 5.4.
I Think its better then mojave.
Alson the letters on the desktop are sharper.
2. Try to install on a mbp 15" 2011 demux flashed, running mojave already on apfs hdd. No ssd.
When booting from same sd card installed my 5.4 i get a forbidden sign.
Whats wrong?
2 things:
1. GREAT!
Installed catalina on my 5.4.
I Think its better then mojave.
Alson the letters on the desktop are sharper.
2. Try to install on a mbp 15" 2011 demux flashed, running mojave already on apfs hdd. No ssd.
When booting from same sd card installed my 5.4 i get a forbidden sign.
Whats wrong?
Jeff - See post 7449 on pg.298. took 6 attempts but it finally made a v1.3.0 USB installer. 10.15.2 runs as good if not better than Mojave.
Last edited:
Catalina Migration Assistant woes:
(any help greatly appreciated)
I´ve set up a MacBook Pro 8,2 successfully including eGPU on thunderbolt-1 (!) - but am now stuck
with transferring user setups and data with the Migration Assistant.
Scenario:
User data, configuration and programs an a working 10.15.2 installation on a MacBook 13", linked to the destination via firewire or ethernet cable.
Destination for migration: MacBook Pro 8,2, also on 10.15.2 (with various patches for the eGPU)
Whenever I start the Migration assistant, it closes down all other (running) apps and continues with the dialog box(es). Normal until then it either crashes or another daemon kicks in and the login window re-appears. Strange, never had this on Lion...Mojave. When password is entered, the screen returns to the Migration Assistant app, but it is crashed/frozen now.
This happens under all circumstances (source MB connected, not connected, AirPort on/off etc.) but time to crash to login screen varies: Sometimes it´s possible to reach the folder selection menu, sometimes it crashes immediately. It also crashes if left without user input after approx. 5-10 seconds.
As I suspected some eGPU or dGPU (disabler) activity to be the reason, I tried the Migration Assistant also on another "unsupported" MacBook Pro (4,1) without other than the suggested @dosdude1 patches for this machine. Same result, no migration with Apple´s tool possible.
I´d like to know if this is "widespread" (Apple support hotline has no clue of this happening on supported machines so far). Also: Any patch/remedy known or alternative tool (this feature a "must": Migrate user account and settings without i.e. cloning whole drive thus losing the OS installation and kext mix found for the eGPU operation*)
*more on that later, I´m still very happy to have found a viable HW/kext/patch combination to make this come true on our beloved old machines!
(any help greatly appreciated)
I´ve set up a MacBook Pro 8,2 successfully including eGPU on thunderbolt-1 (!) - but am now stuck
with transferring user setups and data with the Migration Assistant.
Scenario:
User data, configuration and programs an a working 10.15.2 installation on a MacBook 13", linked to the destination via firewire or ethernet cable.
Destination for migration: MacBook Pro 8,2, also on 10.15.2 (with various patches for the eGPU)
Whenever I start the Migration assistant, it closes down all other (running) apps and continues with the dialog box(es). Normal until then it either crashes or another daemon kicks in and the login window re-appears. Strange, never had this on Lion...Mojave. When password is entered, the screen returns to the Migration Assistant app, but it is crashed/frozen now.
This happens under all circumstances (source MB connected, not connected, AirPort on/off etc.) but time to crash to login screen varies: Sometimes it´s possible to reach the folder selection menu, sometimes it crashes immediately. It also crashes if left without user input after approx. 5-10 seconds.
As I suspected some eGPU or dGPU (disabler) activity to be the reason, I tried the Migration Assistant also on another "unsupported" MacBook Pro (4,1) without other than the suggested @dosdude1 patches for this machine. Same result, no migration with Apple´s tool possible.
I´d like to know if this is "widespread" (Apple support hotline has no clue of this happening on supported machines so far). Also: Any patch/remedy known or alternative tool (this feature a "must": Migrate user account and settings without i.e. cloning whole drive thus losing the OS installation and kext mix found for the eGPU operation*)
*more on that later, I´m still very happy to have found a viable HW/kext/patch combination to make this come true on our beloved old machines!
I saw that. Tried 5 times. So, ha!, ya, one more go at it.
Any thoughts on why so many times was needed? Gamma rays in the universe not lining up just right, maybe?
I'm running 10.15.1.
15.2.02 reinstallation success on MacBookPro5,5 using bootable USB2 Catalina Patcher 1.3.0 & Install Catalina 15.2.02 - about 2 hours - multiply estimated times by about 4X.
Then about 5 hours for a TimeMachine backup of the resulting /System via 100Mbit LAN.
Catalina Patcher 1.3.0 run from Catalina 15.1 system (patcher 1.2.3) created bootable USB2 SanDisk Cruzer Blade 16GB.
[progression ...ElCapitan native, High Sierra Patcher, Catalina Patcher 1.2.3]
Reason for this post - a data point for how slow a reinstall can be & a request for adding a known issue to the Catalina Patcher home page that "Software Update" will not show an available system update, just as the unpatched "softwareupdate --list" does not show available updates.
THIS thread told me that the Catalina 15.1 to 15.2 update is possible via:
Then about 5 hours for a TimeMachine backup of the resulting /System via 100Mbit LAN.
Catalina Patcher 1.3.0 run from Catalina 15.1 system (patcher 1.2.3) created bootable USB2 SanDisk Cruzer Blade 16GB.
[progression ...ElCapitan native, High Sierra Patcher, Catalina Patcher 1.2.3]
Reason for this post - a data point for how slow a reinstall can be & a request for adding a known issue to the Catalina Patcher home page that "Software Update" will not show an available system update, just as the unpatched "softwareupdate --list" does not show available updates.
THIS thread told me that the Catalina 15.1 to 15.2 update is possible via:
- dosdude1 reinstall from the latest bootable Catalina Patcher [I used USB2 flash]
- dosdude1 reinstall directly using latest Catalina Patcher [living without a safety net]
- softwareupdate tweaked command line methods posted in this thread
- off topic OpenCore routes
Last edited:
Migration Assistant never worked for me. Not in any Beta. Not in final release. Neither way I have tried.
Last edited:
O.k. got it to work but when trying to install it says not possible, hdd as S.m.a.r.t. Failures...
Aby chance to get it to work?
(Mojave did...)
Thx
Aby chance to get it to work?
(Mojave did...)
Thx
A niche display interface (Mini-DP) invented by APPLE !!!
They are unable to support their own interfaces ... congratulation !!
I use a Geforce 680, recommended and supported, but still no DP ...
It shouldn't be a shock. Catalina deprecated the support for the MacPro 5,1 which makes testing of Kepler driver support of DisplayPort a niche feature since iMacs already have a screen. Also, I believe we have some reports that running clover on MacPro's, while setting the machine type to a supported iMac, allows DisplayPort to work. So it may well be effectively disabled as a feature on unsupported hardware.
Last edited:
Thanks ASentientBot Legacy Video Patch works again 
10.15.3 Beta1
The Little GeForce 210 is not killable
10.15.3 Beta1The Little GeForce 210 is not killable
Could you be a bit more specific in "it never worked for me"?
Did it crash or did it not complete the job of migrating leading to unusable user account or what else?
Did it work for you under 10.14. (Mojave)? (I used it til Mojave very successfully).
I ask because I try to rule out certain patch effects that might render the Migration Assi unusable...
You try, seems to close session for start the procedure, and then returs to normal state. Not even start to search for files. In Mojave always worked like a charm.
On my 2011 15" its not possible to install any OS. It says smart errors.
Internet recovery dont work, catalina via dosdude patcher dont work smart error and mojave with latest dosdude patcher says no packages where found. Date is set...
Ideas?
Internet recovery dont work, catalina via dosdude patcher dont work smart error and mojave with latest dosdude patcher says no packages where found. Date is set...
Ideas?
This was the solution. files need to be in /Library/Extensions
also note this works with the latest beta
Thanks again for everyone's help and support
S. M. A. R. T. errors indicate a failing disk.
For those who might be interested, I've successfully and quite easily installed Catalina 10.15.2 on my venerable 2009 17" Macbook Pro. As in previous updates, I've installed from an external HDD partition (and not from an USB that would be either USB3 or smaller than 8 GB) and the installation was smooth (first 13 minutes wait on white background that switched to black background with 4 minutes still remaining, then further 13 minutes warning).
I (of course) bypassed Migration Assistant and again booted on the external partition for the post-install patches even though it was mentioned that the patches would be applied automatically after installation. First impressions were good, with the feeling that Catalina was smoother if not faster than Mojave. I tried Migration Assistant from Utilities only to have the same issues as others, i.e. being logged out after a few seconds timeout without being able to complete the process and being frozen when logging back in, like in an eternal loop nightmare.
So I manually imported the Users, Applications and Library/Application Support directories from my backup. The install started beachballing a lot, quite obviously for permissions issues as it would lag and suddenly be Ok. On top I noticed files and directories restored from my backup had mostly group ownership admin instead of wheel. I reinstalled the system and everything is now running sharply and apparently faster than Mojave (though Geekbench says the performance is near identical to the previous Mojave and High Sierra installs).
Hope this helps anyone.
I (of course) bypassed Migration Assistant and again booted on the external partition for the post-install patches even though it was mentioned that the patches would be applied automatically after installation. First impressions were good, with the feeling that Catalina was smoother if not faster than Mojave. I tried Migration Assistant from Utilities only to have the same issues as others, i.e. being logged out after a few seconds timeout without being able to complete the process and being frozen when logging back in, like in an eternal loop nightmare.
So I manually imported the Users, Applications and Library/Application Support directories from my backup. The install started beachballing a lot, quite obviously for permissions issues as it would lag and suddenly be Ok. On top I noticed files and directories restored from my backup had mostly group ownership admin instead of wheel. I reinstalled the system and everything is now running sharply and apparently faster than Mojave (though Geekbench says the performance is near identical to the previous Mojave and High Sierra installs).
Hope this helps anyone.
Disk Utility won't let you erase/partition a drive with SMART errors, which is a good thing. You don't want to install to a failing drive. Storage is cheap now. Just get a new HDD (or better yet, an SSD).
That said, you seem to be asking how to override this and install to a failing drive anyways? You could probably wipe it with
diskutil, but there is a high chance that the installation/subsequent use will end in disaster.
Like I told him before. What’s the point of trying to install Catalina on a 2011 laptop HDD anyway? Talk about unusable...