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
Since Catalina beta 10, I have problems with macOS Catalina Patcher. Only version 1.1.1 worked with Mac mini5.2 (mid 2011). a problem to create a bootable USB drive, and another problem when installing (can't install because of damaged files)
@dosdude1 I am using an unpatched version of Catalina on a Mac Pro 5,1. SIP is normally enabled.
The Recovery boot on the Catalina disk does not work.
- Is there a way to patch it?
- How about installing the CatalinaInstaller partition as Recovery? I do not mind the extra space. It would be convenient.
The Recovery boot on the Catalina disk does not work.
- Is there a way to patch it?
- How about installing the CatalinaInstaller partition as Recovery? I do not mind the extra space. It would be convenient.
They are two bit different things from an APFS perspective, there are many roles, "B" is the Preboot (typically for storing the UUID and for a firmware password), "I" is the Installer, "S" is the System (Catalina) Volume, "D" is the Data (Catalina) Volume, "V" is the VM for virtual memory (swapped files and RAM sleep), "R" is recovery, to "R" is associated "CMD+R", while all the others are just bootable partition holding "alt-option" key after power-on.
For having a basic CMD+R APFS Recovery, this cheapish script will work:https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27842642
Hey everyone,
Something has gone whack with the installations. I seem to have 3 EFI Boots now.
One of them is my patched install Catalina partition, which I’m not worried about. However, the EFI Boot on the very left brings me straight into my Mojave partition (downgraded from Catalina after chrome wouldn’t work, couldn’t take care of work without chrome). The second EFI Boot partition brings me into what seems as the APFS patch, running the black and yellow code before booting into my Mojave partition.
My Boot ROM has been patched to natively boot APFS, so the patch is not necessary and thus the EFI Boot is not needed.
When I mount the EFI disk from terminal, there are three files in it:
apfs.efi
APPLE > EXTENSIONS > Firmware.scap
BOOT > BOOTX64.efi and startup.nsh
Which files do I delete to get rid of these EFI Boot options at startup? Thanks!
Something has gone whack with the installations. I seem to have 3 EFI Boots now.
One of them is my patched install Catalina partition, which I’m not worried about. However, the EFI Boot on the very left brings me straight into my Mojave partition (downgraded from Catalina after chrome wouldn’t work, couldn’t take care of work without chrome). The second EFI Boot partition brings me into what seems as the APFS patch, running the black and yellow code before booting into my Mojave partition.
My Boot ROM has been patched to natively boot APFS, so the patch is not necessary and thus the EFI Boot is not needed.
When I mount the EFI disk from terminal, there are three files in it:
apfs.efi
APPLE > EXTENSIONS > Firmware.scap
BOOT > BOOTX64.efi and startup.nsh
Which files do I delete to get rid of these EFI Boot options at startup? Thanks!
If you have the APFS ROM Patcher installed, you will see an "EFI Boot" partition for every APFS volume you have. This is just a side effect of the unofficial APFS support added to your BootROM. If you delete BOOTX64.efi from the ESP, that will get rid of one of them.
I have an EFI on my Macbook 4.2 and did not apply apfs patcher installed. It came when I installed Mojave. I just ignored it.
Not a great issue but in Catalina on a macbook 4.2 I have a problem selecting wifi. I have a hube and a plug in wifi extender. I can only connect to the extender. Signal and speed are fine. In Mojave I can choose and connect to either. I have tried reinstalling wifi patch but it make no differnce.
MAJOR ISSUE (for me) guys—the beta 11 DosDude version loses support for Japanese input. The Japanese keyboard can be selected but there is no Japanese character input!
This is a showstopper for me—seen it on two machines
There is no problem with the official GM candidate release on a supported mac.
This is a showstopper for me—seen it on two machines
There is no problem with the official GM candidate release on a supported mac.
Last edited:
I wanted to see if curiosisty would kill the cat Alina. I carboned copy cloned the internal hard disk of my iMac 10,1 (running macOS 10.4.6 supplemental 2 update) on an external USB hard drive. I then rebooted from this external hard disk and downloaded the installer for macOS 10.15 GM. I used this installer as source for dosdude1's Catalina patcher (version 1.1.5) and proceeded to the installation of macOS 10.15 over my current 10.4.6, directly from the patcher application. The upgrade was successful, my iMac rebooted and showed the Catalina background. As I noticed activity on the external hard drive, I let the system settle about one hour before login. When I eventually logged in I got a window for updating my account settings, and got a notification that the system was optimizing my account and then was prompted to update the Night shift patch. I let the system perform its task before applying the Night shift patch and restarting the machine. The reboot went alright. Have to check now with time if my machine is still working as I expect with my routine applications.
Update:
Update:
- Photos application is showing picture pixelized with weird colours in the viewer.
- Music did not recovered all the artwork cover of albums (cover manually added)
Last edited:
There was no such problem with Mojave.
I've seen this issue both on a format-and-clean install and an install-over-Mojave setup.
Not sure if it affects other languages.
The problem seems to be with so-called Romaji input which is where Japanese hiragana and katakana characters are input from a Roman alphabet keyboard. If the direct input is set then hiragana/katakana is OK. If Romaji input is set, then the Japanese character input fails and は appears as ha.
There is also a new setting (Apps) in the Language and Region Sys Pref tab that I wonder might be related to the issue.
I've seen this issue both on a format-and-clean install and an install-over-Mojave setup.
Not sure if it affects other languages.
The problem seems to be with so-called Romaji input which is where Japanese hiragana and katakana characters are input from a Roman alphabet keyboard. If the direct input is set then hiragana/katakana is OK. If Romaji input is set, then the Japanese character input fails and は appears as ha.
There is also a new setting (Apps) in the Language and Region Sys Pref tab that I wonder might be related to the issue.
Last edited:
My metal supported GFX card EVGA GT 740 is a PC based card and non Mac EFI supported one so I don’t see the apple logo during boot up or if I want verbose mode during the startup procedure. Is the only way to choose the startup disk is from within MacOS system preferences, startup?
Yes, but you can also use the Install to This Machine option of Catalina Patcher, which will be fully automated and does not require using the boot menu at all.
Rolled the OS back using Time Machine to Mojave with the dosdude1 patch and problem disappears.
Bit of a blow b/c I'd like to be using Cat on these machines (MP 3,1 and iMac 11,1) but if Japanese input is screwed it is a non-starter for me.
Bit of a blow b/c I'd like to be using Cat on these machines (MP 3,1 and iMac 11,1) but if Japanese input is screwed it is a non-starter for me.
Hi guys, anyone who has installed on macbook pro 2010 had any very serious problem can report?
I can read to page 100 of this forum ...
I can read to page 100 of this forum ...
I have had 0 problems with my MacBook Pro 2009, so I don't see why you would have any serious issues. That being said, I'm no expert
Also, I don't think this has been mentioned yet, but I found a workaround for the grayed-out menu bar and Finder Sidebar in light mode. If you go into System Preferences > Accessibility > Display, and check the box for 'Reduce Transparency'
After you do this, nothing in light mode should be weirdly grayed out.
Unfortunately, that makes the Dock no longer transparent, but that bothers me a lot less than either having to deal with a dark gray menu bar or stay in dark mode all the time.
I hope this helps!
After you do this, nothing in light mode should be weirdly grayed out.
Unfortunately, that makes the Dock no longer transparent, but that bothers me a lot less than either having to deal with a dark gray menu bar or stay in dark mode all the time.
I hope this helps!
I just realized, this affects dark mode too. A little downgrade on dark mode, but a huge improvement on the light mode in my opinion. I'm also curious if you could do something with the 'Color Filters' setting to get rid of this effect without reducing transparency. This at least proves that the transparency causes the incorrect grayness though.
Original Dark Mode:
Reduced Transparency Dark Mode:
Original (bugged) Light Mode:
Reduced Transparency Light Mode:
In both reduced transparency modes, the real downside to this solution is the dock. It makes it much worse. I usually have mine disappear automatically though, so this is a very viable solution.
Original Dark Mode:
Reduced Transparency Dark Mode:
Original (bugged) Light Mode:
Reduced Transparency Light Mode:
In both reduced transparency modes, the real downside to this solution is the dock. It makes it much worse. I usually have mine disappear automatically though, so this is a very viable solution.
For what it's worth, Chrome should be working again (it only broke due to an "improved" OpenGL patch that I suggested, which has now been reverted).
[automerge]1570333772[/automerge]
@pkouame, @testheit and @jackluke have created some patched versions of system frameworks which completely re-enable transparency in light mode on non-Metal systems. I believe @0403979 has an automated installer for these patches too.
[automerge]1570333876[/automerge]
Weird. Your screenshots look like they're from a Mac with a Metal-supported GPU, right? Were they taken on the machine with the issue?
Just trying to figure out if the legacy video patch has anything to do with this.
[automerge]1570337009[/automerge]
https://github.com/rmc-team/bluesky/releases/tag/1.4.3 if you follow the instructions here you don't have to reduce transparency
Thanks! This will fix my only complaint about running Catalina
The screenshots were taken on a Catalina-supported machine to show the relevant System Prefs settings locations.
I can take the same screenshots on the remaining affected machine if required but they add nothing and are in Japanese too!
It seems like the Romaji input setting is disabled in the patched Catalina—I think it is NOT related to the Legacy Video patch because one of the two affected machines is a MacPro 3,1 using a GTX680, so no Legacy Video patch. The other affected machine is the 2009 27" iMac 11,1, which I rolled back to Mojave and is now OK (and is using the Legacy Video patch).
I can take the same screenshots on the remaining affected machine if required but they add nothing and are in Japanese too!
It seems like the Romaji input setting is disabled in the patched Catalina—I think it is NOT related to the Legacy Video patch because one of the two affected machines is a MacPro 3,1 using a GTX680, so no Legacy Video patch. The other affected machine is the 2009 27" iMac 11,1, which I rolled back to Mojave and is now OK (and is using the Legacy Video patch).