macOS 10.14 Mojave on Unsupported Macs Thread

[Infografix]

So here’s a question...

If I wanted to do an unsupported upgrade en masse — a client office with a mixed bag of 2010-11 Macs — and wanted to do it with a master disk and super duper (because I always do a major OS upgrade clean and restore backups onto the fresh install anyhow), could I build a “universal” system volume by just checking everything down the line in the post install app, rather than selecting a single Mac system? Or does a given option in post install put in different patches for a given option (graphics for instance) based on the Mac model chosen?

 

[avz]

BUMPING AS I'VE HAD ZERO REPLIES AFTER SEVERAL DAYS:



And some further questions, if I may :

-Is there some reason why booting to recovery mode might be disallowed? Have also tried from an APFS volume, and similarly get the no entry symbol. No reason to think the recovery partitions are damaged.

-Just discovered that Mojave via the patcher apparently needs to run with SIP disabled ("SIP Disabler Patch") Wondering why? Would think that if some SIP protected files need to be modified, that at least SIP would be restored afterwards. Do not want to run with SIP constantly disabled. In that regard, ran sudo csrutil clear, which showed "successfully enabled SIP + now restart." After restarting, saw from csrutil status that SIP was still disabled. If SIP can't be enabled, this would be a real deal breaker. Would think that if this is so, that the documentation would clearly state this.

(Have written directly to dosdude several days ago, to address offered for further suppport, also with zero response -- very disheartening)

Like Psych Majors would say "our own reflection in other people annoys us the most". I ask my fair share of noob questions and have to admit that noob questions of others annoy me.
Your questions are beyond noob. You need to educate yourself on SIP and how people survived without it before 2015. Recovery environment is a mini OS that requires a supported Mac to run OOB or needs patching to work on unsupported. Mojave is never meant to be run on HFS+ so you are on your own here(lots of people had success doing so).

 

[joevt]

I have an old Mojave 10.14.3 installer that I downloaded months ago (I can't download a newer one? - I'll use the 10.14.4 updater and the 10.4.5 combo updater on another partition). I used macOS Mojave Patcher 1.3.3 to create a USB installer. I started the installer and got an error "No packages were eligible for install". The patcher documentation says I should change the date using Terminal.app. I checked the date in the installer using Terminal.app and it appears to be correct (Oct 26, 2019). Then I remembered reading something about Apple certificates expiring Oct 24 so I tried setting the date to Oct 23. Now the installer appears to work. Is this a real problem or would it have worked if I set the date to Oct 26 (even though it was already set to Oct 26)? I'll try again on another partition.

I have found that the 10.14.4 Update has the certificate issue, but Installer.app gives you the choice to Show Certificate, Cancel, or Continue (Certificate expires Oct 24, 2019 at 10:29:17 AM Pacific Daylight Time). If I click Continue, I get an error "This software is not supported on your system." How can I update to 10.14.4 (I want to do some testing of the Parallels Desktop slowdown problem that doesn't exist in 10.14.3)? I see there is a "Distribution" file in the pkg that has checks for the board-id and model which I can remove, but how do I make the change in the pkg? Are there other changes that will need to be made?

 

[TimothyR734]

I have found that the 10.14.4 Update has the certificate issue, but Installer.app gives you the choice to Show Certificate, Cancel, or Continue (Certificate expires Oct 24, 2019 at 10:29:17 AM Pacific Daylight Time). If I click Continue, I get an error "This software is not supported on your system." How can I update to 10.14.4 (I want to do some testing of the Parallels Desktop slowdown problem that doesn't exist in 10.14.3)? I see there is a "Distribution" file in the pkg that has checks for the board-id and model which I can remove, but how do I make the change in the pkg? Are there other changes that will need to be made?

I don't know if you can still find 10.14.4 as Mojave is 10.14.6 maybe someone on discord like Julian might have a copy

 

[tzmmtz]

As you have found, migration is far from foolproof and does tend to copy unwanted remains of apps to the new Mac. I always do a manual restore when starting afresh with new system especially on a supported device. This does take time though! I just had a look on my cMP3.1 running a patched Mojave (not Sierra) and these are some of the patcher files etc:

Library/LaunchAgents/com.dd1.SIPLD.plist. Library/LaunchAgents/dosdude1.patchUpdater.plist
Library/Extensions/LegacyUSBInjector.kext. Library/Extensions/LegacyUSBVideoSupport.kext
Library/Extensions/SIPManager.kext

You may find using EtreCheckPro useful as it will give you a list of all the unsigned kexts and files in your new system and paths so you can remove them. A free demo, but limited version, is available in the Apple App Store.

Thanks Flacko. This is very helpful.

 

[Flacko]

I have found that the 10.14.4 Update has the certificate issue, but Installer.app gives you the choice to Show Certificate, Cancel, or Continue (Certificate expires Oct 24, 2019 at 10:29:17 AM Pacific Daylight Time). If I click Continue, I get an error "This software is not supported on your system." How can I update to 10.14.4 (I want to do some testing of the Parallels Desktop slowdown problem that doesn't exist in 10.14.3)? I see there is a "Distribution" file in the pkg that has checks for the board-id and model which I can remove, but how do I make the change in the pkg? Are there other changes that will need to be made?

Can you just change the date to before 24 October 2019? A temporary fix until Apple update the certificates.

 

[joevt]

Can you just change the date to before 24 October 2019? A temporary fix until Apple update the certificates.

Unnecessary because it is just a 10.14.4 Update (not a full install) so Installer.app gives the option to ignore the expired certificate. To get past the "This software is not supported on your system" error, I used the following commands (from https://snippets.aktagon.com/snippets/669-how-to-open-and-repackage-osx-pkg-files )

pkgutil --expand /Volumes/xxx.pkg ~/Desktop/xxx.unpkg
...edit file(s)...
pkgutil --flatten ~/Desktop/xxx.unpkg ~/Desktop/xxx.pkg

I edited the Distribution file (modified version attached), did the --flatten command, and ran the installer. After the installer runs, boot into the patched 10.14.3 or earlier installer USB stick and do the post install patches. Now I can boot into 10.14.4. I retested my Parallels Desktop VM. 10.14.4 (APFS) does have the slow down problem, but an old 10.14.3 (HFS+) and a new (from yesterday) clean install of 10.14.3 (APFS) do not have the problem. Next I'll reproduce the VM slow down problem in 10.14.5 (that will be a combo updater instead of a single version updater).

 

[shirsch]

Hi, all. I apologize if these are FAQs, but after reading through > 100 pages of this list I cannot find clear answers.

Question the first:

I have successfully installed Mojave 10.14.6 on my 2008 Mac Pro 3,1. It is currently booting an APFS install from the UEFI "stub". Does applying the firmware patch provide any functional advantage over the present arrangement? If there's no benefit, I'd rather not take the risk of bricking the machine. I think the entire subject of firmware patching could benefit from more in-depth discussion on the patcher web site.

Question the second:

Is Time Machine function on my computer limited in any manner as compared to a fully supported system? The patcher USB setup has an option for bare metal restore, but I saw one earlier posting that implied this wouldn't work on unsupported systems. Is this correct? If so, what's the workaround for recovery from a full disk loss?

Thanks again to Collin for all the great work (which I have reinforced via donation).
[automerge]1572192878[/automerge]
Wanted to separate this into its own post. I tried installing the bluesky packages to fix rendering issues on my unsupported GeForce 8800 GT video adapter. While they did fix the desktop appearance, I started experiencing markedly slower desktop startup from login (8-10x longer). Also, XQuartz was utterly broken. It took a minute (!) to start and all windows lacked borders and could not be moved or resized. Emacs editor took at least that long to start (typically < 5 seconds) and entire desktop became non-responsive during that period.

Even after removing both packages, XQuartz was still broken and required a re-installation to get things back to normal.

I opened a ticket on the GitHub page to report the issues.

 

[seyyed]

Don't confuse MacBook 4,1 with MacBook Pro 4,1. The Pro has a fully supported multi-touch trackpad whereas the MB4,1 and MB5,2 lack suitable kexts to enable most features. If the top case of a MacBook Pro 4,1 has been replaced with one from a MBPro3,1 though, you might end up with the same lack of features...

mine is MBP 4,1 but still Mojave doesn't recognize my trackpad so I'm stuck with clicking ctrl+click for right clicking 🤦‍♂️

on dosdude's website the bug is acknowledged but it says only MBP 5,2 is affected🤔

 

[RK78]

Like Psych Majors would say "our own reflection in other people annoys us the most". I ask my fair share of noob questions and have to admit that noob questions of others annoy me.
Your questions are beyond noob. You need to educate yourself on SIP and how people survived without it before 2015. Recovery environment is a mini OS that requires a supported Mac to run OOB or needs patching to work on unsupported. Mojave is never meant to be run on HFS+ so you are on your own here(lots of people had success doing so).

-Re. "Noob-Beyond Noob": Sorry, but I won't venture much further into a conversation with someone who needs to resort to putdowns at this adolescent level. I've been around computer forums long enough to take the measure of someone like yourself: Big fish in small pond. Actually, you haven't been around here that long --just over a year, maybe not such a big fish. (Couldn't you have offered the information you wanted to present without the putdown and snarky tone?)

That done with:

-And sorry, but I am very well educated about SIP. Like many others I survived very well for years without it, by staying away from dodgy sites and downloads, but given the choice I prefer to keep it enabled, and will have to give some consideration to whether I want to run with SIP disabled by default, with Mojave (including very ugly black, almost unreadable Dark Mode on non-metal GPU) or continue with 10.13 unsupported next year at EOL. Perhaps unlikely, as malware can install on the non-SIP files, but there's always the chance that, even with employing the most caution, one might run into something that does want to modify/install in those locations. Even with SIP enabled, I run BlockBlock, as well as a few other defensive programs.

->>"Mojave never meant to run on HFS+": Quite likely so, but not everyone is running an SSD, to which APFS was tailored. With an HDD, which I employ, it is pretty well known by now that APFS has major drawbacks on platter drives. Maybe you should do some reading from Mike Bombich's excellent analysis:

And I do have Mojave on an APFS formatted partition, in order to be able to get security or supplemental updates, then clone back to the HFS+ volume -- the APFS volume mostly for updating, but nothing I would want to stay with for daily use.

 

[LuisN]

mine is MBP 4,1 but still Mojave doesn't recognize my trackpad so I'm stuck with clicking ctrl+click for right clicking 🤦‍♂️

on dosdude's website the bug is acknowledged but it says only MBP 5,2 is affected🤔

Try to reapply the patches

 

[avz]

mine is MBP 4,1 but still Mojave doesn't recognize my trackpad so I'm stuck with clicking ctrl+click for right clicking 🤦‍♂️

on dosdude's website the bug is acknowledged but it says only MBP 5,2 is affected🤔

Do you have battery installed in your MBP4,1?

 

[MTBnBeer]

mine is MBP 4,1 but still Mojave doesn't recognize my trackpad so I'm stuck with clicking ctrl+click for right clicking 🤦‍♂️

on dosdude's website the bug is acknowledged but it says only MBP 5,2 is affected🤔

My 17" Early 2008 MBP trackpad works fine with DosDude1's Mojave Patcher 10.14.6 including these Trackpad settings:

1. Tap to Click (Tap with one finger)

2. Secondary Click a.k.a. RIGHT CLICK (Click with two fingers)

3. Look up & data detectors (Tap with three fingers)

As others have said, try reapplying the macOS Mojave Patcher again

 

[joevt]

I have successfully installed Mojave 10.14.6 on my 2008 Mac Pro 3,1. It is currently booting an APFS install from the UEFI "stub". Does applying the firmware patch provide any functional advantage over the present arrangement? If there's no benefit, I'd rather not take the risk of bricking the machine. I think the entire subject of firmware patching could benefit from more in-depth discussion on the patcher web site.

The firmware patch may have less spam during boot (from the efi Shell and startup.nsh script). The firmware patch allows using the Startup Disk preferences panel to select APFS partitions for booting, otherwise you can use the bless command or the APFS Boot preferences panel. The firmware patch allows APFS volumes to appear in the Startup Manager (hold option during boot). I'm not sure about all of those since I haven't tried the firmware patch yet.

I remove the stuff in the EFI partition because "EFI Boot" is not a very descriptive name in the Startup Manager (hold option during boot). Plus, I have multiple APFS bootable OSs and "EFI Boot" can only load one of them (unless it's replaced with rEFInd).

For each APFS bootable OS, I create a 20 MB HFS+ partition with a specifically named folder containing the efi files. startup.nsh has two modifications: the targetUUID is modified to point to the APFS bootable OS (use "diskutil info" to find the UUID), and the path of apfs.efi includes the named folder. The partition has a volume icon (pasted into the info window of the boot volume in the Finder) which can appear in the Startup Manager (but I only see one for Catalina - maybe the icns files of the other partitions is missing a specific size of icon). The partition has a disk_label generated by the bless command (the label appears in the Startup Manager - the partition has a Boot suffix which I don't include in the label).

This spoiler includes all the info:

Spoiler

joevt@Joes-Mac-Pro ~ % ls -l /Volumes | grep Boot                
drwxrwxr-x@  9 root   admin    374 17 Oct 00:21 Catalina Boot
drwxr-xr-x   9 joevt  staff    374 26 Oct 16:44 Mojave4 Boot
drwxr-xr-x   9 joevt  staff    374 26 Oct 16:47 Mojave5 Boot
drwxr-xr-x@ 11 joevt  staff    442 26 Oct 16:49 Mojave6 Boot

joevt@Joes-Mac-Pro ~ % dump_label () { local contents=$(xxd -p -c99999 $1); echo ${contents:10} | perl -pe "s/(..)/\1 /g;s/00/../g;s/ //g;s/(.{$((0x${contents:2:4}*2))})/\1\n/g" ; }

joevt@Joes-Mac-Pro ~ % cd /Volumes/Mojave4\ Boot/*Patcher         

joevt@Joes-Mac-Pro Mojave4 Boot % sudo find . -not \( -name '.DS_Store' -or -path '*/.*/*' \)
.
./.fseventsd
./.TemporaryItems
./.Trashes
./.VolumeIcon.icns
./macOSMojave4Patcher
./macOSMojave4Patcher/.disk_label
./macOSMojave4Patcher/.disk_label_2x
./macOSMojave4Patcher/apfs.efi
./macOSMojave4Patcher/Mojave4_Boot.worksheet
./macOSMojave4Patcher/ShellX64.efi
./macOSMojave4Patcher/startup.nsh

joevt@Joes-Mac-Pro macOSMojave4Patcher % /usr/libexec/PlistBuddy -c 'print :WorksheetContents' Mojave4_Boot.worksheet
sudo bless --folder /Volumes/Mojave4\ Boot/macOSMojavePatcher --file /Volumes/Mojave4\ Boot/macOSMojavePatcher/ShellX64.efi --label Mojave4 --setBoot

joevt@Joes-Mac-Pro macOSMojave4Patcher % dump_label .disk_label
................................................................................
................................................................................
....2afaf7......faf9............f92a......................................f8f6..
....55d6fc....f8d6ab............fbf8....................................f9d6f9..
....55d6d6....80d6ab..fbfffffb..80f9..fcffabf9fafd....fd552aabfffc....f7ffd6f9..
....55fefff8..ffababf7d6fbfbd6f7ab5555fff880fe2ad6f7f7d62afefcfafffb..abfbfef9..
....55fe80fcf8d6faabfaab....abfaab55f6fafbfeff..fffafafef7d680fbfefdfbfe..fef9..
....55fef8d6fcfcfaabfbfd....abfaab55fbd680fdff..fbababfa2ad680fb8055ffd6ffd6d6f9
....55fe..ffd6f9faabf8d62af8d62aab55fdfd..abff..2ad6d6f6..fffaf6ab80f72a2afffbf6
....55ab..80d6..faab..fcd6d6fd..ab55f9d6d6fed6fa..feab....55ffd6fff7......fef9..
........................f6f6....fe55....f6....................f7................
..............................80ff2a............................................

joevt@Joes-Mac-Pro macOSMojave4Patcher % dump_label .disk_label_2x
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..................................................................................................................................................................
..........fdd6d6fc..............ffd6d6fa........................fad6ab..............................................................................558055........
..........fed6d6d6f6..........f9d6d6d6fb........................fbd6fe............................................................................2ad6d6fd........
..........fed6d6d655..........fcd6d6d6fb........................f8fcfb............................................................................fed6d6fd........
..........fed6d6d6fd..........d6d6d6d6fb........f7f8f8f7........................f7f8f6....................................f72af7................fcd6d6d6fd........
..........fed6d6d6d6f6......f9d6d6d6d6fb....f7abd6d6d6d6abf7....fad6ab......80ffd6d6d6ff80..f6d6d6fc........fcd6d6....f8ffd6d6d6ff55..........f9d6d6d6d6fd........
..........fed6abd6d655......fcd6feffd6fb..f6d6d6d6d6d6d6d6d6f6..fbd6fe....fad6d6d6ffd6d6d6fb..fed6ff........d6d6fd..f9d6d6d6d6d6d6d6fb......f7d6d6fcfdd6fd........
..........fed6fcabd6fd......d6d6fbffd6fb..80d6d6fa....fad6d6fc..fbd6fe....fed6ab....f6ffd6ab..fad6d6f8....f9d6d6f9..ffd6ff2a..f7fed6d6f6....abd6ff..fdd6fd........
..........fed6fcfad6d6f6..f9d6d6f7ffd6fb..d6d6ab........fdd6ff..fbd6fe....80fdf8......abd6fe..f6d6d680....fcd6ff..f9d6d6fa......2ad6d655..fbd6d62a..fdd6fd........
..........fed6fcf6d6d655..fcd6fe..ffd6fbf6d6d6fb........fbd6d6..fbd6fe......2afbfcabd6d6d6fe....fdd6ff....d6d680..fad6d6abfcfcfcfcd6d6fbf8d6d6fb....fdd6fd........
..........fed6fc..abd6ab..d6d6fa..ffd6fb2ad6d6f9........fad6d6f6fbd6fe....fbd6d6d6d6d6d6d6fe....f9d6d6f8f9d6d62a..80d6d6d6d6d6d6d6d6d6fbabd6d680fbfbffd6fffbf9....
..........fed6fc..55d6d6fad6d6f7..ffd6fbf7d6d6fa........fcd6d6..fbd6fe..f6d6d6fffbf9f780d6fe......d6d680fdd6fe....fbd6d6faf9f9f9f9f9f9f6abd6d6d6d6d6d6d6d6d6ab....
..........fed6fc..f6d6d6d6d6ab....ffd6fb..d6d6fd........fed6fe..fbd6fe..fad6d6f7......abd6fe......fcd6d6d6d6fa....f9d6d655......f7fffff8558080808080ffd6ff8055....
..........fed6fc....fdd6d6d6fa....ffd6fb..fdd6d6f9....fad6d6fa..fbd6fe..fad6d655....80d6d6fe......f8d6d6d6d6f6....f6d6d6fef6..f6abd6d6f7............fcd6fd........
..........fed6fc....55d6d6d6f7....ffd6fb..2ad6d6d6d6d6d6d6fff6..fbd6fe..2ad6d6d6ffd6d6d6d6d6fe......ffd6d6fd........fbd6d6d6fed6d6d680..............fcd6fd........
..........abd680....f6d6d6ab......ffd6fa....f8ffd6d6d6d6abf6....fbd6fe....fad6d6d6d6fef9fed6d6......fbd6d6f9..........fad6d6d6d6d680................80d6fc........
................................................2af9f8f6........fbd6fe......f6f8f8f6......2af7..........................f6f8f9f8f6................................
................................................................fdd6fe............................................................................................
............................................................f7d6d6d6fc............................................................................................
............................................................f7d6d6ff2a............................................................................................

joevt@Joes-Mac-Pro macOSMojave4Patcher % cat startup.nsh
echo -off
mode 320 84
set StartupDelay 1
set -v efishellmode 1.1.2
set macOSBootFile "System\Library\CoreServices\boot.efi"
set targetUUID "7CC0F8C1-B913-464B-8CE7-92638F74179E"

for %i in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
  if exist fs%i:\macOSMojave4Patcher\apfs.efi then
    load fs%i:\macOSMojave4Patcher\apfs.efi
    connect -r
    map -u
  endif
endfor

echo "Searching for macOS Boot File..."
for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
  if exist "fs%m:\%targetUUID%\%macOSBootFile%" then
    echo "Starting macOS..."
    fs%m:\%targetUUID%\%macOSBootFile%
    exit
  endif
endfor

for %m in 0 1 2 3 4 5 6 7 8 9 A B C D E F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
  if exist "fs%m:\%macOSBootFile%" then
    echo "Starting macOS..."
    fs%m:\%macOSBootFile%
    exit
  endif
endfor
echo "Boot file not found, exiting..."
exit

 

[shirsch]

The firmware patch may have less spam during boot (from the efi Shell and startup.nsh script). The firmware patch allows using the Startup Disk preferences panel to select APFS partitions for booting, otherwise you can use the bless command or the APFS Boot preferences panel. The firmware patch allows APFS volumes to appear in the Startup Manager (hold option during boot). I'm not sure about all of those since I haven't tried the firmware patch yet.

I remove the stuff in the EFI partition because "EFI Boot" is not a very descriptive name in the Startup Manager (hold option during boot). Plus, I have multiple APFS bootable OSs and "EFI Boot" can only load one of them (unless it's replaced with rEFInd).

For each APFS bootable OS, I create a 20 MB HFS+ partition with a specifically named folder containing the efi files. startup.nsh has two modifications: the targetUUID is modified to point to the APFS bootable OS (use "diskutil info" to find the UUID), and the path of apfs.efi includes the named folder. The partition has a volume icon (pasted into the info window of the boot volume in the Finder) which can appear in the Startup Manager (but I only see one for Catalina - maybe the icns files of the other partitions is missing a specific size of icon). The partition has a disk_label generated by the bless command (the label appears in the Startup Manager - the partition has a Boot suffix which I don't include in the label).

This spoiler includes all the info:

(snip)

Ah, thanks so much for that thorough rundown! I need only a single volume so it looks safe for me to just stay with the EFI shell based startup. But, I'll certainly make note of this information in case my needs change in the future.

 

[joevt]

Next I'll reproduce the VM slow down problem in 10.14.5 (that will be a combo updater instead of a single version updater).

The 10.14.5 Combo Updater does not update from 10.14.3 (18D109 is not one of the supported build numbers - actually the combo updater includes build numbers only from 10.14.4 and 10.14.5?) so I had to update to 10.14.4 before using the 10.14.5 Combo Updater (modified with a similarly patched Distribution file as the 10.14.4 updater). 10.14.5 also has the VM slow down problem as expected. The kernel source code for 10.14.4 hasn't been released yet so I can't see what has changed since 10.14.3.

 

[seyyed]

Do you have battery installed in your MBP4,1?

wow! no i dont! does it actually have anything to do with this?
[automerge]1572250559[/automerge]

My 17" Early 2008 MBP trackpad works fine with DosDude1's Mojave Patcher 10.14.6 including these Trackpad settings:

1. Tap to Click (Tap with one finger)

2. Secondary Click a.k.a. RIGHT CLICK (Click with two fingers)

3. Look up & data detectors (Tap with three fingers)

As others have said, try reapplying the macOS Mojave Patcher again

sorry but i hadn't tested all functions. my trackpad has some gestures like swipe three fingers upwards or swipe two fingers from right edge of trackpad to center but:
1- in trackpad setting in preferences it says no trackpad found
2- touch to click doesn't work
3- two finger touch or touch_click to right click doesn't work
[automerge]1572250666[/automerge]

Try to reapply the patches

by reapplying patches do you mean the "post install" option in the menu after booting from patcher ?

 

[avz]

wow! no i dont! does it actually have anything to do with this?
[automerge]1572250559[/automerge]


sorry but i hadn't tested all functions. my trackpad has some gestures like swipe three fingers upwards or swipe two fingers from right edge of trackpad to center but:
1- in trackpad setting in preferences it says no trackpad found
2- touch to click doesn't work
3- two finger touch or touch_click to right click doesn't work
[automerge]1572250666[/automerge]

by reapplying patches do you mean the "post install" option in the menu after booting from patcher ?

Yes, you must have a battery installed for a trackpad to be recognised by the system. All the machines that support High Sierra and up have a non-removable batteries. The system is smart and knows that when there is no battery, something fishy is going on.

 

[Larsvonhier]

Yes, you must have a battery installed for a trackpad to be recognised by the system. All the machines that support High Sierra and up have a non-removable batteries. The system is smart and knows that when there is no battery, something fishy is going on.

In addition, try the swipe-from-right two finger gesture to see if message sidebar comes up.
If this (and your three-finger and other gestures) works, then it might also be that some settings are wrong (and you cannot change them as you do not get the trackpad settings panel in system settings - perhaps due to no-battery behaviour). Should be still possible to enable secondary two-finger click by terminal then.
There are lots of entries if you google for that, one being i.e.
defaults -currentHost write -g com.apple.trackpad.enableSecondaryClick -bool YES

 

[seyyed]

Yes, you must have a battery installed for a trackpad to be recognised by the system. All the machines that support High Sierra and up have a non-removable batteries. The system is smart and knows that when there is no battery, something fishy is going on.

thx for the heads up . btw does this battery thing affect performance too? cuz my MBP seems sluggish after my battery broke and I removed it .(sorry for the unrelated question)
[automerge]1572281806[/automerge]

In addition, try the swipe-from-right two finger gesture to see if message sidebar comes up.
If this (and your three-finger and other gestures) works, then it might also be that some settings are wrong (and you cannot change them as you do not get the trackpad settings panel in system settings - perhaps due to no-battery behaviour). Should be still possible to enable secondary two-finger click by terminal then.
There are lots of entries if you google for that, one being i.e.
defaults -currentHost write -g com.apple.trackpad.enableSecondaryClick -bool YES

thx but the code didn't work. I think I will buy a replacement battery ASAP

 

[LuisN]

wow! no i dont! does it actually have anything to do with this?
[automerge]1572250559[/automerge]


sorry but i hadn't tested all functions. my trackpad has some gestures like swipe three fingers upwards or swipe two fingers from right edge of trackpad to center but:
1- in trackpad setting in preferences it says no trackpad found
2- touch to click doesn't work
3- two finger touch or touch_click to right click doesn't work
[automerge]1572250666[/automerge]

by reapplying patches do you mean the "post install" option in the menu after booting from patcher ?

or using the patcher updater in utilities folder. Open it, select the patch you want, right click on it and click the reinstall button that appears

 

[Macschrauber]

Have a MacBook Air 3.1 with removed swollen battery and can second that it does not show its trackpad in trackpad preference pane.

I can edit the plist in ~/library/preferences tho to configure it.

In supported High Sierra btw, so nothing to do with the patches for unsupported.

 

[avz]

thx for the heads up . btw does this battery thing affect performance too? cuz my MBP seems sluggish after my battery broke and I removed it .(sorry for the unrelated question)
[automerge]1572281806[/automerge]


thx but the code didn't work. I think I will buy a replacement battery ASAP

Yes, good battery is essential for the top performance, without it your CPU is downclocked by the system. I found the unsupported threads to be a great place to get your general Mac knowledge.

 

[olad]

0-700 (almost) pages in 512 days! Not bad

 

[MTBnBeer]

Is this Security Update 2019-001 and Safari 13.0.3 safe to install on my MacBookPro4,1 (17" Early 2008 MacBook Pro 2.6 GHZ Core 2 Duo, 6GB RAM, 500GB SSD) that's currently running Mojave 10.14.6 perfectly with macOS Mojave Patcher and bkltpatch10.14.2 ? It just showed up in Software Update