Ahh... there it goes. Trim enabled successfully. Thanks.
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
Ahh... there it goes. Trim enabled successfully. Thanks.
Dosdude actually helped me out on Discord,. I didn't have the lates firmware installed. Im now running Catalina on my MacBook pro 8,2!! Thanks @dosdude1
CloneToolX update: working on Disk to Image clones next, followed by Disk to Disk. GUI window is resizable. Dark and Light modes supported.
I know my card is not compatible with AirDrop and now I have a RAMDisk in the cloud to transfering files, I am using that in place of AirDrop and Thumb Drives. I’ll dig more into it later when I can afford a good card. I tried purchasing the 99 dollar one twice from the Chinese seller and my PayPal rejected the sale which also tells me the seller must be getting bad reviews and returns. So i’ll bother with this at a later time when I find a seller I can trust. OSXWIFi is a bit steep.
Last edited:
My first post on Catalina Forum (been posting mostly on Mojave forum)
I installed Catalina developer beta 2 on an external SSD hosted by a MacBook Air 13" Mid 2011 (MacbookAir4,2).
I used the excellent @dosdude1's macOS Catalina Patcher 1.0b2 (awesome as always and I like the new gui display).
It worked great - graphics acceleration accomplished, etc.
Several observations/issues:
Appreciate the excellent work of @dosdude1 and @ASentientBot. Apologies to those I failed to mention who should deserve it as well.
I installed Catalina developer beta 2 on an external SSD hosted by a MacBook Air 13" Mid 2011 (MacbookAir4,2).
I used the excellent @dosdude1's macOS Catalina Patcher 1.0b2 (awesome as always and I like the new gui display).
It worked great - graphics acceleration accomplished, etc.
Several observations/issues:
- System Preferences | Desktop | Appearance | Auto does not work or cannot be selected
- Night Shift does not work either.
- Light mode (same as in Mojave) still problematic (although I used @pkoume's latest hybrid patches). Not really an issue for me since Dark mode is my preference.
- Cannot disable or move files from the /usr/bin even if I logged in as root.
- If I use Time Machine backup, it states that I have 2 "host drive - data" so I have to exclude the " - data" folder.
- Related to the above, if I boot up to my Mojave host and attach the external Catalina SSD drive, I do see 2 " - data" folders.
Appreciate the excellent work of @dosdude1 and @ASentientBot. Apologies to those I failed to mention who should deserve it as well.
if you look at I believe post 2076 there is a fix for night shift what I did was renamed mine to bak then replaced core brightness folder from the post
Other than Photos (of which there's a fix), everything else seems to be in order on my MacBookPro5,5 with this beta, barring the known issues.
Thanks to @dosdude1 @ASentientBot and everyone else involved in making this work. I hope my testing and reporting bugs is helping at least a little bit...
Thanks to @dosdude1 @ASentientBot and everyone else involved in making this work. I hope my testing and reporting bugs is helping at least a little bit...
You really lucked out with the iPhone SE. It's the one Phone Apple has decided not to cutoff in ages and it's basically a 5s.
Last November Apple allowed the iPad Mini 2 to be upgraded to iOS 12. Previously it was cutoff at the knees with iOS 9. Then once again the Mini 2 got cutoff again. I'd get an iPad mini 4. I can't justify an iPad Pro and I saw a review on iPadOS and I'm really not impressed. Apple refuses to make a multi touch Mac. Which is disappointing. The iPad Pro could have been this and iPadOS could have done it, but it's still too weird. I hate to say MS Surface has done really good job.
Last edited:
I don't know what I did wrong. The panel for Night Shift appeared. No matter what setting I use, nothing happens.
Apple just needs to loosen up a make a touch screen Mac.
Just released an update to macOS Catalina Patcher (1.0 Beta 3)! Now, entering the "nvram boot-args" command in Terminal prior to installation is no longer necessary.
Does it automatically enter that command by itself, or does it modify internal settings that exclude vintage Mac models?
Currently it will do it by itself on the machine you install Catalina on, but I will be changing that soon.
I got sick of running mount -uw / all the time, so I made a tiny LaunchDaemon to do it for me at boot. For anyone else like me who dislikes Catalina's read-only-ness, just put this in /Library/LaunchDaemons/ on your Catalina volume.
No idea if this will continue to work in future versions, but it's working on DP2.
No idea if this will continue to work in future versions, but it's working on DP2.
I get same error with a MacBook Pro 2012 although it works "fine" with my iPad
Thank you everybody.
I am currently not brave enough to patch my MCP97 Chipset (in Mac mini 3,1). I did it tear down and got the number. It is LIKE MX25L3205D . Because there was one more letter or count after the "D" at the end, but I cannot remember now.
The Patcher tells me in this machine there are multiple chip definitions. I think the one that could fit and fit best in theory is that one, that is shown as "MX25L3205D/MX25L3208D" in the patcher.
I read a lot. So, to my conclusion people, who were successful in patching their machines are not Mac mini 3,1 users.
May I ask you, Dosdude1, are you going to add a APFS Patcher later in your final tool? Or are all machines with Nvidia chipset out of race?
Sorry for my bad English.
Thank you guys
I am currently not brave enough to patch my MCP97 Chipset (in Mac mini 3,1). I did it tear down and got the number. It is LIKE MX25L3205D . Because there was one more letter or count after the "D" at the end, but I cannot remember now.
The Patcher tells me in this machine there are multiple chip definitions. I think the one that could fit and fit best in theory is that one, that is shown as "MX25L3205D/MX25L3208D" in the patcher.
I read a lot. So, to my conclusion people, who were successful in patching their machines are not Mac mini 3,1 users.
May I ask you, Dosdude1, are you going to add a APFS Patcher later in your final tool? Or are all machines with Nvidia chipset out of race?
Sorry for my bad English.
Thank you guys
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
Any ideas
Installed successfully beta2 in MacBook 5,2. What can I do to enable backlighting control and fix keyboard trackpad? I could enable iSight with the Mojave Patcher but nothing more
I got Final Cut Pro X 10.4.6 to launch on macOS Catalina on a MBP 2011 17-Inch without removing the AMD kexts. All I did was I installed macOS Catalina with @dosdude1's tool. Then, I installed Lilu and Whatevergreen and bam it launched. It's really buggy probably because Lilu and Whatevergreen haven't been updated for macOS Catalina yet and neither has Final Cut Pro X. I am going to try Mojave and Lilu and Whatevergreen. Maybe there's hope for these old AMD Cards after all (by someone way smarter than me). I'm going to post a picture (if you don't believe me) and look up my serial number (if you don't believe me either):
