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.
my macbook, macbookpro5.1late 2008, 256ssd, 8Gram.
I was installed high sierra by @dosdude1's tool.
but The Bluetooth mouse is not recognized and the trackpad tutorial settings can not be entered. When i try to enter the trackpad settings, the screen for finding the Bluetooth trackpad appears.

I ask you to help me solve it.
Can you run "/System/Library/PreferencePanes/Trackpad.prefPane/Contents/Resources/tplog" in Terminal, and send the output?
 
Apart from using Adobe's DNG Converter, that'll be challenging...
Yeah already got DNG converter. For example Canon 5D mkIV raw files can be opened in Preview and Photos but are prevented from doing so in Aperture and iPhoto. So it got me thinking that within that cameras specific file that is contained somewhere in the Macs raw engine there must be code that prevents it from being opened in Aperture and iPhoto.
This would be a bit like what we are doing here with Sierra where the patcher is modifying files in the installer to allow the installation to progress. So surely if we can get Sierra and High Sierra onto our excluded systems then we can find a way to get Aperture and iPhoto to see the raws from new cameras.
 
Can you run "/System/Library/PreferencePanes/Trackpad.prefPane/Contents/Resources/tplog" in Terminal, and send the output?
Hello. First of all, thank you for doing this voodoo magic to support our macs :D
I also have trackpad issues on MB alu 5,1 and it doesn't show the preference pane. It did once, on the first day of the install.
2017-10-21 11:03:18.682 tplog[503:8327] Looking for mouse:
2017-10-21 11:03:18.740 tplog[503:8327] - mouse type: 0x0
2017-10-21 11:03:18.787 tplog[503:8327] - one finger double tap : None
2017-10-21 11:03:18.787 tplog[503:8327] - two fingers swipe : Dock
2017-10-21 11:03:18.787 tplog[503:8327] - two fingers double tap : Dock
2017-10-21 11:03:18.787 tplog[503:8327] - button mode : One button
2017-10-21 11:03:18.788 tplog[503:8327] - scroll mode : Both axes
2017-10-21 11:03:18.789 tplog[503:8327] - momentum scroll : YES
2017-10-21 11:03:18.789 tplog[503:8327] ---------
2017-10-21 11:03:18.794 tplog[503:8327] Looking for trackpad(s), detected type 0x0:
2017-10-21 11:03:18.794 tplog[503:8327] ---------
2017-10-21 11:03:18.794 tplog[503:8327] scroll: YES
2017-10-21 11:03:18.794 tplog[503:8327] tapBehavior: 1 (TapBehaviorClick)
2017-10-21 11:03:18.794 tplog[503:8327] cornerClickBehavior: 0 (CornerClickBehaviorOff)
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerTapBehavior: 1 (TwoFingerTapBehaviorSecondaryClick)
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerDoubleTap: 1 (TapBehaviorZoom)
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerSecondaryClick: YES
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerRotate: YES
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerPinch: YES
2017-10-21 11:03:18.795 tplog[503:8327] twoFingerFromRightEdgeSwipe: 3 (SwipeTypeNotificationCenter)
2017-10-21 11:03:18.795 tplog[503:8327] threeFingerDrag: YES
2017-10-21 11:03:18.799 tplog[503:8327] threeFingerTap: 2 (TapBehaviorDefinition)
2017-10-21 11:03:18.799 tplog[503:8327] threeFingerActionClick: NO
2017-10-21 11:03:18.799 tplog[503:8327] threeFingerDoubleTap: 2
2017-10-21 11:03:18.799 tplog[503:8327] threeFingerHorizSwipe: 0 (SwipeTypeNone)
2017-10-21 11:03:18.799 tplog[503:8327] threeFingerVertSwipe: 0 (SwipeTypeNone)
2017-10-21 11:03:18.799 tplog[503:8327] fourFingerHorizSwipe: 2 (SwipeTypeDock)
2017-10-21 11:03:18.799 tplog[503:8327] fourFingerVertSwipe: 2 (SwipeTypeDock)
2017-10-21 11:03:18.799 tplog[503:8327] ignoreTrackpadIfMouseOnSystem: NO
2017-10-21 11:03:18.800 tplog[503:8327] multiFingerPinch: 2 (PinchTypeDock)
2017-10-21 11:03:18.800 tplog[503:8327] clickPressureLevel: 1
2017-10-21 11:03:18.800 tplog[503:8327] deepClickPressureLevel: 1
2017-10-21 11:03:18.800 tplog[503:8327] acutationStrength: 1
2017-10-21 11:03:18.800 tplog[503:8327] actuateDetents: 1
2017-10-21 11:03:18.800 tplog[503:8327] forceClick: YES
2017-10-21 11:03:18.800 tplog[503:8327] forceSuppressed: NO
2017-10-21 11:03:18.800 tplog[503:8327] ---------
2017-10-21 11:03:18.800 tplog[503:8327] other commands: [-mobileAssets [info | list]] [-mobileAssetPurge <name>] [-mobileAssetDownload <name>]
[-setMouseScrollMode Off | Vertical | Both | 360]
[-setMomentumScroll On | Off]
[-setIgnoreTrackpadIfMouseOnSystem On | Off]
 
To @dosdude1 and everyone who has contributed to making macOS HS possible on unsupported macs - Thank you so much for your contributions! I'll be making a round of donations beginning of next month.

@dosdude1 I took the plunge and upgraded my fully working Sierra installation to HS without converting any of my volumes (SSDs, Areca RAID10 etc.) to APFS. The upgrade went smooth, as expected from such stellar work, and my recently installed GTX 680 is running smooth except for one small issue - my recovery partition is no longer bootable as it displays a circle with a slash and I am not sure whether or not this has anything to do with leaving FileVault enabled on the boot drive when upgrading to HS.

Things I've tried:

- After upgrading to HS and rebooting into the patch installer, I unlocked/mounted my encrypted boot drive and selected the default options for MacPro 3,1 and also selected the recovery partition patch, applied them then rebooted - No bootable recovery!

- I examined the 'Recovery HD's partition contents and noticed timestamps of some files/directories have changed to todays date so it appears it has been updated. I then rebooted back into the patch installer and tried to apply the recovery patch again - No bootable recovery!
partition info - /dev/disk0s3 620Mi 549Mi 71Mi 89% 68 4294967211 0% /Volumes/Recovery HD

- Tried booting into the patch installer and ran Disk Utility/First Aid to check for/fix disk errors then reapplied the recovery patch again and rebooted - No bootable recovery!

I thought I would reach out to you before nuking the recovery partition.. Any clues?

Thanks again!
 
@dosdude1 I was able to track down the issue to an either incomplete recoverypatch.sh script or the patch installer v2.4.0 was corrupted during packing as I tried downloading the patch installer several times from your website with the same results every time.

Recovery Fix (for HFS volumes only)

Mount 'Recovery HD' and manually copy the following files, which weren't copied by recoverypatch.sh, from the patch installer /Applications/Utilities/macOS\ Post\ Install.app/Contents/Resources/ to /Volumes/Recovery\ HD/com.apple.recovery.boot/

- prelinkedkernel
- PlatformSupport.plist

Then execute -

Code:
# sudo chown root:admin /Volume/Recovery\ HD/com.apple.recovery.boot/BaseSystem.chunklist
# sudo chown root:wheel /Volume/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg
# sudo chown root:wheel /Volume/Recovery\ HD/com.apple.recovery.boot/prelinkedkernel
# sudo chown root:wheel /Volume/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist
# sudo xattr -c /Volume/Recovery\ HD/com.apple.recovery.boot/PlatformSupport.plist

That's it! We can now reboot into Recovery.
 
Can you run "/System/Library/PreferencePanes/Trackpad.prefPane/Contents/Resources/tplog" in Terminal, and send the output?

Also see this related post: #1922

I had same trackpad issue. Temporary fix was to copy over the Trackpad prefs panel from El Capitan. Now, after updating to 10.13.1 Beta 2 and applying the post install patches again the issue is gone, no problem using the Trackpad prefs panel from High Sierra with all features supported.

Very happy with my old ("new") Mac now! Even had some fun testing ExpressCard/34 connected eGPU.
 
Last edited:
  • Like
Reactions: dosdude1
Also see this related post: #1922

I had same trackpad issue. Temporary fix was to copy over the Trackpad prefs panel from El Capitan. Now, after updating to 10.13.1 Beta 2 and applying the post install patches again the issue is gone, no problem using the Trackpad prefs panel from High Sierra with all features supported.

Very happy with my old ("new") Mac now! Even had some fun testing ExpressCard/34 connected eGPU.
[doublepost=1508660461][/doublepost]I'm finding that CCC 5.03 does NOT produce a bootable clone. I have to run the post-install patch on the cloned disk before it will boot. Anyone else seen this?
 
  • Like
Reactions: 1theo0
To create a bootable clone w 5.03, I erased, formatted as HFS+, cloned, used the recovery partition option, and it is bootable.

I still can't make the recovery volume on my primary bootable. Drive is ok otherwise.
 
I have come across an issue when using Disk Utility and First Aid to check the APFS volume.

It completes very quickly, however does not do the job fully as it should, reporting error:
---
Checking the APFS volume superblock.
Checking the object map.
Checking the fsroot tree.
error: drec_key object (oid 0x91a3): invalid name (da.lprojS), given name_len (9)
fsroot tree is invalid.
The volume /dev/rdisk1s1 could not be verified completely.
Operation successful.
---

Any idea what this could be? Incompatibilities?
My APFS partition is residing on the drive next to my original HFS+ partition with El Capitan, which was originally shrunk down to make space for the APFS partition with High Sierra.
Thanks!
 
Hello,

Has anyone resolved the brightness issue? I think this is separate than the 'automatic brightness' feature not working. My use-case is that when I turn the display all the way down on my MacBook pro, I would expect the screen brightness to dim until the screen is completely black. This is NOT occurring and the screen brightness remains the same.

I have a 2009 MacBook Pro (MacBookPro5,3) where this is happening.

Does anyone have any ideas on how to resolve this please? TIA.


Anyone resolve this issue yet? Still trying to resolve it...

@dosdude1 - sent you a PM as well.


Thanks in advance everyone!
 
Hi, I know this is slightly off-topic.
Wanted to share with you my MacBook Pro 4,1 (early 2008 model) running High Sierra and eGPU via the ExpressCard/34 port using the EXP GDC adapter (total $50 !). I run a Nvidia Geforce 560Ti (Fermi-based) card I had lying around, with 2GB of graphics memory, on the port (using Nvidia's latest Web drivers, not required though), which is connected through PCIe 1x speed effectively. Getting quite good performance, and up to 10 times faster than the original Geforce 8600m built into the machine.

As it really is connected directly onto the internal PCIe bus (as opposed to Thunderbolt eGPU) no software modifications or hacks are needed, it just works.

Thanks to DosDude for making it possible to run High Sierra on this beloved machine! Outstanding work!

Enjoy!;)

 
Last edited:
Hi, I know this is slightly off-topic.
Wanted to share with you my MacBook Pro 4,1 (early 2008 model) running High Sierra and eGPU via the ExpressCard/34 port using the EXP GDC adapter (total $50 !). I run a Nvidia Geforce 560Ti (Fermi-based) card I had lying around, with 2GB of graphics memory, on the port (using Nvidia's latest Web drivers, not required though), which is connected through PCIe 1x speed effectively. Getting quite good performance, and up to 10 times faster than the original Geforce 8600m built into the machine.

As it really is connected directly onto the internal PCIe bus (as opposed to Thunderbolt eGPU) no software modifications or hacks are needed, it just works.

Thanks to DosDude for making it possible to run High Sierra on this beloved machine! Outstanding work!

Enjoy!;)


Hi, I've your same macbook. Can you give me the links of the eGPU and the adapter to install the card? Are the instruction to install it on fixit website?
 
Successfully installed High Sierra in my MacBook Pro 5,5 but, its now not recognizing SD cards. I tried inserting a few different cards, but nothing. The reader shows up under System Report->USB, but does not recognize when a card is inserted. Any help would be greatly appreciated!

EDIT: Nevermind, got it working. Did an SMC reset and it seems to have fixed it.
 
Last edited:
Can anyone post a direct d/l link to macOS 10.13.1 beta 4 [build number 17B45a], or let us know: did updating via App Store do the trick? Am on MBP 4.1 (Early 2008), and updates 10.13.1 beta1-3 produced Safari, App Store, etc. major bugs. Or would someone of the fellow experts here on the board instruct, how to wrap these into a full installer for use with dodsdude1's fantastic piece of software:

EmbeddedOSFirmware.pkg
FirmwareUpdate.pkg
FullBundleUpdate.pkg
macOSUpd10.13.1.RecoveryHDUpdate.pkg
macOSUpd10.13.1Patch.pkg
macOSUpd10.13.1.pkg

Thanks in advance, this board is great!
 
Can anyone post a direct d/l link to macOS 10.13.1 beta 4 [build number 17B45a], or let us know: did updating via App Store do the trick? Am on MBP 4.1 (Early 2008), and updates 10.13.1 beta1-3 produced Safari, App Store, etc. major bugs. Or would someone of the fellow experts here on the board instruct, how to wrap these into a full installer for use with dodsdude1's fantastic piece of software:

EmbeddedOSFirmware.pkg
FirmwareUpdate.pkg
FullBundleUpdate.pkg
macOSUpd10.13.1.RecoveryHDUpdate.pkg
macOSUpd10.13.1Patch.pkg
macOSUpd10.13.1.pkg

Thanks in advance, this board is great!

What did u want exactly? If you enable beta app installation, app store can be update fine to beta releases (thanks for my patch for App Store). If you found one or more bugs in beta on your unsupported mac, always check apple's own developer forum first for bugreports from anyone else (nearly 99% of bugs are already reported back to apple). Full installer with 10.13.1 beta are not exists.
 
What did u want exactly? If you enable beta app installation, app store can be update fine to beta releases (thanks for my patch for App Store). If you found one or more bugs in beta on your unsupported mac, always check apple's own developer forum first for bugreports from anyone else (nearly 99% of bugs are already reported back to apple). Full installer with 10.13.1 beta are not exists.

Czo, thanks for taking the time to answer my question.
That being said, a full installer for macOS 10.13.1 Developer Beta 3 DOES exist:
https://www.zoneactu.fr/2017/10/17/...sierra-10-13-1-developer-beta-3-liens-pkg-dmg

Install.macOS.High.Sierra.Beta.app.zip - MD5 : 9853a115f3b78b6a59bd7f5ff64b7bfb

Quite a number of fellow board members reported in this thread about the major bugs (Safari, App Store) and were not able to get a working system, hence had to revert to 10.13 release.

What I want to do exactly is: update from 10.13.1 dev beta 3 to 4 via full installer, in order to avoid the hassle of a possible broken system via App Store update.

(Nota bene: updates via App Store went smoothly whilst still in 10.13. beta range, thank you expressingly making it possible)

And as to the list of .dmg packages provided in my earlier post: am still looking for a way to wrap these into a full installer, is that at all possible, and how?)
 
Hi,

just updated my iMac 9,1 to High Sierra Beta 10.13. Im still on version 17A330h but i would like to update to the latest version.

The patch tool didn't find any update. Did i miss something ?

Any help will be highly appreciated!

Best from Germany.
 
Updated via App Store this morning and when I open safari the browser just sits there with a spinning beach ball not loading the webpage, I get notifications for emails but message content isn't showing, and opened App Store to check for updates but it's not able to connect. Running 10.13.1 beta (17B45a) on mid2009 5,3 MacBook Pro.

I've tried turning wifi off and restarting. Then enabling once I'm logged back but no luck. Anyone else have these issues? Anyone know of a fix?
 
Updated via App Store this morning and when I open safari the browser just sits there with a spinning beach ball not loading the webpage, I get notifications for emails but message content isn't showing, and opened App Store to check for updates but it's not able to connect. Running 10.13.1 beta (17B45a) on mid2009 5,3 MacBook Pro.

I've tried turning wifi off and restarting. Then enabling once I'm logged back but no luck. Anyone else have these issues? Anyone know of a fix?

Please guys, check apple's own forum first for bugreports. If a bug exists on supported mac, and peoples talking about it on Apple's forum(https://forums.developer.apple.com/thread/84560) it's will be fixed later because of it's a common bug.
 
  • Like
Reactions: dosdude1
Please guys, check apple's own forum first for bugreports. If a bug exists on supported mac, and peoples talking about it on Apple's forum(https://forums.developer.apple.com/thread/84560) it's will be fixed later because of it's a common bug.
Please guys, check apple's own forum first for bugreports. If a bug exists on supported mac, and peoples talking about it on Apple's forum(https://forums.developer.apple.com/thread/84560) it's will be fixed later because of it's a common bug.
I've tried that link and searched around. Still no luck with the issue. The post in that link is exactly what I'm experiencing. I guess the only thing is to standby for an update
 
Why did u installed the beta release? U need to enable beta app installation (https://beta.apple.com/sp/betaprogram/) and install updates via App Store, but i really recommend to install stable version and keep installing updates only from the stable tree.


I used the High Sierra patch tool and that was the version of High Sierra which was installed during the set up process. Any idea how to upgrade to the stable version of High Sierra?

Thanks in advance.
 
I've tried that link and searched around. Still no luck with the issue. The post in that link is exactly what I'm experiencing. I guess the only thing is to standby for an update

Hi Gill88. I had the same experience. I then reinstalled previous version 10.13.beta (17A362a) on my MacBook Pro 5,2. Converted the drive to AFPS and then from the App Store installed the latest 10.13.1 beta4 (17B45a). The installation completed OK and my laptop is working well. So it appears that installing the latest beta on a AFPS drive works.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.