Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Altavek312 said:
I have a MacBook Air 3,1 that was on High Sierra (so I did the firmware updates) that won’t finish the install. Did a complete wipe of the drive/container before. APFS/extended journaled partition. I’ve tried several times, redone the install USB drive. Just can’t figure why it hangs?
Click to expand...
if you still have a partition with a Recovery partition. Shut down the Mac, wait 10 secs, turn on the Mac holding down <command-R> until macOS Recovery appears, go to Terminal under Tools and enter csrutil disable RETURN, then immediately restart, hold <option> to boot the USB. The install should finish.
 
MBP4,1 17" (Early 2008) Successfully updated to 19H1304.
(no more unwanted files like default.profraw)
Safari still showing old iCloud tabs on each fresh startup (when history has been deleted)
 
Last edited:
  • Like
Reactions: K two
MBP4,1 17" (Early 2008)
When booting with alt/option-key Macintosh HD shows up as "EFI boot" and showing wrong icon.
Is there a sure way to restore to its correct icon and name?

(I successfully installed Big Sur 11.2.1 via OCLP and had to modify the EFI of my Macintosh HD in the process.
I could remove the injected OC parts, but the EFI boot-OC-icon stuck during boot with alt-key.
I reverted back to Catalina, the MBP4,1 is clearly not made for Big Sur.)
 
Last edited:
Altavek312 said:
I have a MacBook Air 3,1 that was on High Sierra (so I did the firmware updates) that won’t finish the install. Did a complete wipe of the drive/container before. APFS/extended journaled partition. I’ve tried several times, redone the install USB drive. Just can’t figure why it hangs?
Click to expand...
deleted for now
 
Last edited:
Has anyone successfully updated to Security Update 2021-003? The OTA Software fix button on @jackluke CatalinaOTASwufix isn’t working, so my machine just restarts and never installs the update
 
tejljr said:
Has anyone successfully updated to Security Update 2021-003? The OTA Software fix button on @jackluke CatalinaOTASwufix isn’t working, so my machine just restarts and never installs the update
Click to expand...
Yes. But with OpenCore is an straight proccess. Works like a charm.
Later I will try in my Macbook 17" 2011 dosdude1 patched.


1.jpg
 
@K two Just one question. Previously applied the CatalinasOTA… Now I can see the 2021-003 Update. Must I rerun the whole proccess?

Thanks
 
  • Like
Reactions: K two
MBP4,1 17" (Early 2008) 19H1304

Q: How do I restore a full Time Machine backup?

After trying out Big Sur, I decided to revert to Catalina. Did a fresh install, which delivered 19H15.
I rebooted into the dosdude1-patched macOS Base System. From there I was not able to restore my Time Machine backup from the external TM drive (USB, MacOS Extended (Journaled) formatted). The restore was denied, mentioned some APFS reason.

My successful solution was to boot from an OCLP EFI boot, from there call Big Sur Installer, which there gave me the option to restore from Time Machine. That was successful.

Can the full Time Machine restore be done easier and without the hassle of the mentioned workaround?
 
  • Like
Reactions: K two
Hello, since a few days ago, for some reason the post install app has been crashing, I already tried different Catalina Installer.app, different USB and I still can't get it to work (I think the crashing started when I installed the security update 2021-003 for Catalina)

System Info
MacBookPro 8,1
macOS Catalina 10.15.7 (19H1217)
dosdude1 - Catalina Patcher Version 1.1.4

(EDIT: After trying various things I realized that the app only crashes when trying to patch the Mac's Boot Volume, I tried to patch another Catalina partition on another Mac (without the 2021-003 Update) and it worked, just reinstalled Catalina, and now the patch works again, I wonder what causes the error, and how to prevent it from happening again, but well it works and Reinstalling Catalina is not a problem for me)

Here is the output of the app


2021-05-26 17:36:48.910 macOS Post Install[705:3392] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSDictionaryM setObject:forKey:]: object cannot be nil (key: Kernel Flags)' *** First throw call stack: ( 0 CoreFoundation 0x00000001113ff727 __exceptionPreprocess + 250 1 libobjc.A.dylib 0x000000010fa20a9e objc_exception_throw + 48 2 CoreFoundation 0x00000001114ae796 _CFThrowFormattedException + 194 3 CoreFoundation 0x00000001114b92cd -[__NSDictionaryM setObject:forKey:].cold.3 + 0 4 CoreFoundation 0x000000011133cb52 -[__NSDictionaryM setObject:forKey:] + 969 5 macOS Post Install 0x000000010f2dc7d5 macOS Post Install + 10197 6 macOS Post Install 0x000000010f2e27b8 macOS Post Install + 34744 7 macOS Post Install 0x000000010f2dff98 macOS Post Install + 24472 8 Foundation 0x000000010f3547a2 __NSThread__start__ + 1064 9 libsystem_pthread.dylib 0x0000000116e7f109 _pthread_start + 148 10 libsystem_pthread.dylib 0x0000000116e7ab8b thread_start + 15 ) libc++abi.dylib: terminating with uncaught exception of type NSException Abort trap: 6
 
Last edited:
I am a bit out of the loop. So I installed on my MP 5,1 Catalina 10.15.5 some time ago using @dosdude1 patcher (thanks). What is the easiest way now to bump it to the latest Catalina version 10.15.7 ? Is it via dosdude1 patcher again or via OTA by installing CatalinaOTAswufix.app (if that is even possible this way) ?
 
  • Like
Reactions: K two
I'm on a 13-inch MacBook Pro from 2011 (MBP 8,1). I've made it to build 19H1217, but I had a little bit of drama on the way with the Catalina Patcher, CatalinaOTAswufix, and Security Update 2021-003.

After applying post-install patches and booting back into Catalina, I lost Wifi, and there was nothing I could do inside the OS to bring it back online. I thought it might be something that was needed through the patch updater, so I put an ethernet cable in her and linked up to the patch updater that way.

The patch updater re-downloaded and re-installed the Library Validation Disabler patch, then I rebooted her, and now the wifi is back.

Other people who have the same MBP as me may run into this issue while updating, so I'm posting about this.
 
  • Like
Reactions: K two
Also, for users that are using an SSD with the Catalina Patcher, one can observe that with every security update via CatalinaOTAswufix, one will need to re-enable trim support. Every time I update, I lose trim support for my SSD. I go to the terminal and type "sudo trimforce enable" after the update to re-enable trim on her. You can check the status of your trim support in [About this Mac]-->[system report] -->SATA/SATA Express
 
Last edited:
  • Like
  • Wow
Reactions: ghost82, roysterdoyster and K two
TimmuJapan said:
Also, for users that are using an SSD with the Catalina Patcher, one can observe that with every security update via CatalinaOTAswufix, one will need to re-enable trim support. Every time I update, I lose trim support for my SSD. I go to the terminal and type "sudo trimforce enable" after the update to re-enable trim on her. You can check the status of your trim support in [About this Mac]-->[system report] -->SATA/SATA Express
Click to expand...

With 2 SSDs in this Mini3,1, never seen a MacOS update disable TRIM. Both now have Catalina Build 19H1304 via CatalinaOTAswufix.app. 🧐
 
Last edited:
TimmuJapan said:
Also, for users that are using an SSD with the Catalina Patcher, one can observe that with every security update via CatalinaOTAswufix, one will need to re-enable trim support. Every time I update, I lose trim support for my SSD. I go to the terminal and type "sudo trimforce enable" after the update to re-enable trim on her. You can check the status of your trim support in [About this Mac]-->[system report] -->SATA/SATA Express
Click to expand...
I noticed the same issue with my MBP4,1 after the various Security Updates ending with #003
 
  • Like
Reactions: ghost82 and TimmuJapan
roysterdoyster said:
I noticed the same issue with my MBP4,1 after the various Security Updates ending with #003
Click to expand...
This comment sent me to check each @dosdude1 and @jackluke updated Mac - iMac11,2, MB5,1 and three other Mini3,1s. ALL had TRIM enabled just fine. After running unsupported Macs for years, NEVER seen this issue at any time. Not disputing but perhaps SOME but not ALL SSD Macs see this problem. FWIW
 
Last edited:
  • Like
Reactions: ghost82
macbook pro 4,1 I'm experiencing the same "trim issue" with a CT500MX500SSD1 500 Gb ssd from Crucial (catalina latest stable+dosdude).
Slight off topic but I saw the same happens sometimes with emulated ssd (QEMU disk+emulated sata controller+rotational flag set to ssd), no patch at all applied.
Sometimes the trim setting has to be checked after updates (better to check after each update).
 
Last edited:
K two said:
This comment sent me to check each @dosdude1 and @jackluke updated Mac - iMac11,2, MB5,1 and three other Mini3,1s. ALL had TRIM enabled just fine. After running unsupported Macs for years, NEVER seen this issue at any time. Not disputing but perhaps SOME but not ALL SSD Macs see this problem. FWIW
Click to expand...
I've experienced that once before - as far as I recollect on my 8,1.
 
K two said:
Welcome - From the unzipped gibMacOS-master ƒ in your Downloads ƒ, run the gibMacOS.command shell, go to the Security Pref Pane and OK it, enter the #5 in the prompt below. Then make certain the D/L has fully completed, progress is shown, it can take awhile. Inside the new Downloads ƒ is a ƒ with a Product I.D. #, drop that ƒ into the BuildmacOSInstallApp.command shell, after another visit to the Security Pane and OK, a brand new full macOS Catalina installer v.15.7.03 aka (19H15) will appear in the gibMacOS-master ƒ. It can be selected from there when building the new v.1.4.4 USB patcher. BTW - ƒ is for the word - folder - because I'm lazy. 😎
Click to expand...

Thanks, just upgraded to 19H15 from 19H2. Everything went well, btw I don't create USB installer, just do the update directly from my SSD.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back