Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
@dosdude1

[.... other items, plus ....]
  • PLEASE add 10.11 trackpad pref pane for macbook5,2. I don't know why you don't want to do that

This reminds me that on my MacBookPro6,1 for a while I also saw the same trackpad issue (searching for a non-existent Bluetooth trackpad, disallowing tap-to-click, etc.) but resolved after some head-scratching.

What happened was that I started replacing prefpanes due to a suggestion from parrotgeek1 from the 10.12 (Low) Sierra Unsupported Macs thread, thinking it was a similar issue (although unreported by others). But re-installing High Sierra which officially works on my 2010 17" machine still exhibited the problem. So then I thought it must be an actual hardware problem with a bad trackpad, not a software patching issue.

Turns out that hardware wasn't the problem either! As it happened my machine had no battery installed after I removed it due to a charging problem, running on wall plug power only. I guess cognoscenti have noticed that taking away the battery affects the trackpad prefpane (!) for odd/unknown reasons: https://apple.stackexchange.com/que...system-preferences-after-instal/331198#331198

This is just a heads-up to others in a similar masquerade situation.

However, if owners of the MacBook5,2 really can conquer the trackpad quirk by using a 10.11 prefpane file, it should be SOP and the caveat removed from the 10.{12,13,14} instructions.
 
This reminds me that on my MacBookPro6,1 for a while I also saw the same trackpad issue (searching for a non-existent Bluetooth trackpad, disallowing tap-to-click, etc.) but resolved after some head-scratching.

What happened was that I started replacing prefpanes due to a suggestion from parrotgeek1 from the 10.12 (Low) Sierra Unsupported Macs thread, thinking it was a similar issue (although unreported by others). But re-installing High Sierra which officially works on my 2010 17" machine still exhibited the problem. So then I thought it must be an actual hardware problem with a bad trackpad, not a software patching issue.

Turns out that hardware wasn't the problem either! As it happened my machine had no battery installed after I removed it due to a charging problem, running on wall plug power only. I guess cognoscenti have noticed that taking away the battery affects the trackpad prefpane (!) for odd/unknown reasons: https://apple.stackexchange.com/que...system-preferences-after-instal/331198#331198

This is just a heads-up to others in a similar masquerade situation.

However, if owners of the MacBook5,2 really can conquer the trackpad quirk by using a 10.11 prefpane file, it should be SOP and the caveat removed from the 10.{12,13,14} instructions.
I'm pretty sure I had experimented with this in the past, with no results... I'll have to try it again, though, and see if that actually does fix the issue.
 
@dosdude1
  • PLEASE add 10.11 trackpad pref pane for macbook5,2. I don't know why you don't want to do that
P.S. we should update all kexts from 10.13.6

10.11's Trackpad.prefPane is even bigger than Patcher.app it self. Try using provided pref below for MB5,2 and make a backup of original first for sure. Thanks
/System/Library/PreferencePanes

#EDIT: New Pref, was wrong link.
 

Attachments

  • Screenshot 11.png
    Screenshot 11.png
    37.7 KB · Views: 158
Last edited:
Try re-installing using the Patch Updater application in your /Applications/Utilities folder, NOT the post-install utility.
Thanks! I got home and re-ran the patch updater and got my sound back!
[doublepost=1532239988][/doublepost]
S

Strange. I have exactly the same MBP and all goes well. Have you installed the post installation patches?
Reinstalled again and it works. Glad to know someone else on here that is testing with the same machine.
 
Oh yeah the latest patch renames the drive and then fails because it renames the drive. Unless you call it OS X Base Install.

It worked! The USB drive needs to be renamed to OS X Base System and not OS X Base Install.

It's funny that Apple even if from Sierra declared abandoning the name “OS X” in favor of “MacOS” still labels the BaseSystem.dmg ever "OS X Base System". Maybe if they change would fall onto installing issues too.
 
Last edited:
@dosdude1 @ASentientBot @pkouame @TimothyR734 Good news! Macmini 2010 (Macmini4,1) works perfectly on FullHD without glitches using patcher beta12 with an HDMI cable instead of a VGA Adapter!! I have no money to upgrade my Mac and you are geniuses (not like @ Apple store always refusing to help customers on obsolete machines :( )
 

Attachments

  • IMG_20180722_095041.jpg
    IMG_20180722_095041.jpg
    350.8 KB · Views: 189
Last edited:
Probably sounds stupid, but is my macbook early 2008 able to run mojave?And is it even safe to just try it out?Mine has added 6gb ram by the way.
 
  • Like
Reactions: TimothyR734
Probably sounds stupid, but is my macbook early 2008 able to run mojave?And is it even safe to just try it out?Mine has added 6gb ram by the way.

It’s not. The requirements are as follows and can also be found here. They are also listed om the wiki post.

Code:
Requirements:

- Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
- MacPro3,1
- MacPro4,1
- iMac8,1
- iMac9,1
- iMac10,x
- iMac11,x
- iMac12,x
- MacBookPro4,1
- MacBookPro5,x
- MacBookPro6,x
- MacBookPro7,1
- MacBookPro8,x

- Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
- MacBookAir2,1
- MacBookAir3,x
- MacBookAir4,x
- MacBook5,1

- Early-2009 or newer Mac Mini or white MacBook:
- Macmini3,1
- Macmini4,1
- Macmini5,x
- MacBook5,2
- MacBook6,1
- MacBook7,1

- Early-2008 or newer Xserve:
- Xserve2,1
- Xserve3,1


Machines that ARE NOT supported:

- 2006-2007 Mac Pros, iMacs, MacBook Pros, and Mac Minis:
- MacPro1,1
- MacPro2,1
- iMac4,1
- iMac5,x
- iMac6,1
- iMac7,1
- MacBookPro1,1
- MacBookPro2,1
- MacBookPro3,1
- Macmini1,1
- Macmini2,1

-- The 2007 iMac 7,1 is compatible if the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.

- 2006-2008 MacBooks:
- MacBook1,1
- MacBook2,1
- MacBook3,1
- MacBook4,1

- 2008 MacBook Air (MacBookAir 1,1)
 
I have tried installing the latest beta 4 on my iMac (late 2009); The iMac boots from the USB, the install process starts. About 75% into the install it crashes with error:

Code:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SMMigrationRequest addUserToTransfer:excludedPaths:overwriteTargetName:]: unrecognized selector sent to instance

Any idea what might be the cause? I have tried recreating the USB installer/different USB sticks, same error
 
Good morning everyone. I’m currently experiencing an issue which is preventing me from finishing the installation on my MacBook Pro 5,5 (Mid 2009).
Preparing USB drive and booting from it went just fine, until the installation reached around 15 minutes to go, then I’m getting the error described in the image attached. I have a partitioned SSD, regarding OS in one partition and personal files on the other one.
Does anyone know what is this about? And perhaps could I a get a workaround this issue? Any help would be highly appreciated.
 

Attachments

  • FC7CF5E2-7F92-4E2A-9E73-130CAC0204CF.jpeg
    FC7CF5E2-7F92-4E2A-9E73-130CAC0204CF.jpeg
    4.7 MB · Views: 202
Good morning everyone. I’m currently experiencing an issue which is preventing me from finishing the installation on my MacBook Pro 5,5 (Mid 2009).
Preparing USB drive and booting from it went just fine, until the installation reached around 15 minutes to go, then I’m getting the error described in the image attached. I have a partitioned SSD, regarding OS in one partition and personal files on the other one.
Does anyone know what is this about? And perhaps could I a get a workaround this issue? Any help would be highly appreciated.

It seems like you and @martin__j have the same issue. Could you take a photo of the right side of the screen so I can confirm this?
 
  • Like
Reactions: TimothyR734
Good morning everyone. I’m currently experiencing an issue which is preventing me from finishing the installation on my MacBook Pro 5,5 (Mid 2009).
Preparing USB drive and booting from it went just fine, until the installation reached around 15 minutes to go, then I’m getting the error described in the image attached. I have a partitioned SSD, regarding OS in one partition and personal files on the other one.
Does anyone know what is this about? And perhaps could I a get a workaround this issue? Any help would be highly appreciated.

I have the same Mojave unsupported mac model and got the same experience in upgrading to Dev Preview 4. Inorder for me to complete the install/upgrade successfully, I booted from my USB install drive containing @dosdude1's Mojave Patcher App and ran Post Install Utility. Selected MBP5,5 and rebuilt the cache and rebooted.

upload_2018-7-22_2-59-24.png


Good Luck.
 
I have the same Mojave unsupported mac model and got the same experience in upgrading to Dev Preview 4. Inorder for me to complete the install/upgrade successfully, I booted from my USB install drive containing @dosdude1's Mojave Patcher App and ran Post Install Utility. Selected MBP5,5 and rebuilt the cache and rebooted.

View attachment 772108

Good Luck.
So Mojave is actually installed, just not patched? Is that correct? Or am I gonna have to start over the whole process?
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.