I've the same issue: https://www.zoneactu.fr/2017/07/10/...h-sierra-10-13-developer-beta-3-liens-pkg-zip is wrong. It's Beta 2 Update. Beta 3 is 17A306f. You can use Foxlet's utility in this thread to download a good version.
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 High Sierra (10.13) Unsupported Macs Thread
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I've the same issue: https://www.zoneactu.fr/2017/07/10/...h-sierra-10-13-developer-beta-3-liens-pkg-zip is wrong. It's Beta 2 Update. Beta 3 is 17A306f. You can use Foxlet's utility in this thread to download a good version.
So for the people messaging me and asking how I am using APFS on unsupported Mac. I am using the latest Clover boot loader with apfs.efi in /EFI/Clover/drivers64UEFI. I use clover config app to edit everything and uncheck everything that is checked by default....EVERYTHING. I change the smbios to a iMac that is compatible with APFS and High Sierra ONLY in order to install with APFS. So I use a smbios for a 2013 iMac. Then run the macOSDeveloperBetaAccess. Then download the latest High Sierra from App Store. Run it. Then when it restarts you boot into clover again but instead of choosing your macOS hard drive you choose the macOS Install option. (It will NOT install if you are not using clover because without clover it is still an unsupported Mac). I have found that if you make it to when it shows you the 'Installing: About 34 minutes remaining' you should be good without any errors.
Once this is done I change the smbios back to exactly what my iMac really is, a 2007 20" iMac. Except for the Bios Release Date, that has to be to the date used in this thread. You can use Terminal to find your product name, board-id and serial. then use about this Mac to find your serial number and uuid. That why everything will work on your Mac like it is suppose to. When I have a 2013 smbios only one of my usb works. Unless I added kext and other things like on a hackintosh. But for this purpose you just need your Mac to work just enough to get High Sierra downloaded and installed.
After I was all done I added clover to the EFI partition of Apple_APFS Container disk2 and it boots up automatically without me having to do anything. Ironically enough my processor is recognized correctly now.
I suspect that if some other people used clover they could fix some of their problems.
The last thing I did was edit the coreBrightness.framework so night shift would work. Im next going to work on fixing the brightness slider using clover. Other than that everything works like it should and is now identified like it should be
Side Note: from the time I hit the power button it will sit on a white screen for 40 seconds until it loads apfs.efi. Total time to login screen 1:22:85(with a 1 second clover loading screen) Total time to working desktop is 1:45:49(taking into account the time it takes to click on my profile and type in my 6 character password)
Once this is done I change the smbios back to exactly what my iMac really is, a 2007 20" iMac. Except for the Bios Release Date, that has to be to the date used in this thread. You can use Terminal to find your product name, board-id and serial. then use about this Mac to find your serial number and uuid. That why everything will work on your Mac like it is suppose to. When I have a 2013 smbios only one of my usb works. Unless I added kext and other things like on a hackintosh. But for this purpose you just need your Mac to work just enough to get High Sierra downloaded and installed.
After I was all done I added clover to the EFI partition of Apple_APFS Container disk2 and it boots up automatically without me having to do anything. Ironically enough my processor is recognized correctly now.
I suspect that if some other people used clover they could fix some of their problems.
The last thing I did was edit the coreBrightness.framework so night shift would work. Im next going to work on fixing the brightness slider using clover. Other than that everything works like it should and is now identified like it should be
Side Note: from the time I hit the power button it will sit on a white screen for 40 seconds until it loads apfs.efi. Total time to login screen 1:22:85(with a 1 second clover loading screen) Total time to working desktop is 1:45:49(taking into account the time it takes to click on my profile and type in my 6 character password)
Last edited:
Glad to read it's not me then. Have tried Foxlet's utility but been getting some "rsync" errors when it attempts to create the flash drive so never got far with that.
I have this model, does this mean i just won't be able to control screen brightness but other than that no other issues?
Also I had custom ordered my iMac with the ATI Radeon HD 4850 512 MB, might this have an impact?
Is it possible you can make a detailed tutorial for newbies? Or maybe even a video?
After it boots, in the OS it self in terms of usability, do you find the system faster or smoother in APFS compared to HFS?
I could make a write up but it will be during the week. I won’t have time on the weekend. Monday maybe Tuesday.
As far as being quicker, I think it’s hard to make that comparison while it is still in beta. It definitely isn’t any slower tho
[doublepost=1500151519][/doublepost]
I think it could be possible. You will have to do some research tho. I would start by looking at what rehabman does. And talk to him. I will warn you tho. Do some homework. He can be kind of an ass if you ask stupid questions. He does do some great work tho. He may already have a fix in all the kext he has built
[doublepost=1500152755][/doublepost]I was wrong about one thing tho. There must be a new way to enable night shift for macOS High Sierra because the old way gives me a Preferences Error could not load Displays preference pane when I either A) edit CoreBrightness manually or B) use the night shift on unsupported Macs GitHub script. booooooo
If anyone is interested in getting NightShift to work in macOS High Sierra, this is the new offset
00000000000200a0 S _ModelMinVersion
and data dump
000200a0: 0900 0000 0d00 0000 0600 0000 0500 0000
000200b0: 0600 0000 0800 0000
and make sure you resign CoreBrightness or Display Preferences will crash
00000000000200a0 S _ModelMinVersion
and data dump
000200a0: 0900 0000 0d00 0000 0600 0000 0500 0000
000200b0: 0600 0000 0800 0000
and make sure you resign CoreBrightness or Display Preferences will crash
That would be pretty cool, when you get a chance right those instrutions as detailed as possible so we can test it out.
Thanks!
Interesting, i have two versions of Hi Sierra and both run Night Shift via the NightEnabler app.
Sorry to ask did you relaunch System Preferences and or reboot.
Hi foxlet,
i'd like to test your FetchMacOS application.
Can you please send me a copy of it?
Thanks
Flawless. Amazingly fast, too. Great share, foxlet, thanks.
Could you point me to your NewCore tool v.0.2/0.3, went through the thread all the way back to your post #87, couldn't find a download link.
Else, would you be so kind to shoot us some quick-and-dirty Terminal command, how to convert the .pkg files into an Installer for use with dosdude1's patcher?
Your great work, time and effort is highly appreciated
step-by-step instructions (understandable for an informed layman) would be nice.
Thanks![/QUOTE]
also, Im kind of hoping the better minds in here come up with a better method before Im done. Because this is gonna be a lot to write up hahahaha
I am working on this now. It is going to take a little while because I want to write some disclaimers of problems I ran into and also make the instructions as detailed as possible.
also, Im kind of hoping the better minds in here come up with a better method before Im done. Because this is gonna be a lot to write up hahahaha
I am working on this now. It is going to take a little while because I want to write some disclaimers of problems I ran into and also make the instructions as detailed as possible.
also, Im kind of hoping the better minds in here come up with a better method before Im done. Because this is gonna be a lot to write up hahahaha[/QUOTE]
That's ok, take your time and write it as main stream for newbies as possible
I've read some stuff online on how to work with clover and it is kind of a mess out there
I (and others) ran into problems installing the 10.13 betas onto an unsupported MP in which the stock GPU had been replaced with an AMD Sapphire RX460 (that runs fine on Sierra). Rominator also found that the Sapphire RX460 does not work on 10.13 but the Sapphire RX480 does work OOTB, which it does not do on 10.12.6. Something has changed. 10.13 beta does install on a late 2016 MBP with the RX460 option GPU so the drivers are present in the OS and a quick look through through the AMD kexts shows the presence of the correct GPU board ID. What has changed? I can't spot it from looking at kexts but does anyone here have an educated guess? A safe boot also gets to a desktop so the problem does seem related to a kext.
The unsupported MP runs the 10.13 betas fine when the stock Apple GPU is returned to the machine BUT having both the stock Apple GPU and the RX460 in the same machine causes the same problem of "booting" to a black screen with white rectangle at top right. I've seen someone mention a Windowserver crash but can't pin it down.
That's ok, take your time and write it as main stream for newbies as possible
I've read some stuff online on how to work with clover and it is kind of a mess out there[/QUOTE]
The unsupported MP runs the 10.13 betas fine when the stock Apple GPU is returned to the machine BUT having both the stock Apple GPU and the RX460 in the same machine causes the same problem of "booting" to a black screen with white rectangle at top right. I've seen someone mention a Windowserver crash but can't pin it down.
That's ok, take your time and write it as main stream for newbies as possible
I've read some stuff online on how to work with clover and it is kind of a mess out there
[/QUOTE]
Last edited:
[/QUOTE]I (and others) ran into problems installing the 10.13 betas onto an unsupported MP in which the stock GPU had been replaced with an AMD Sapphire RX460 (that runs fine on Sierra). Rominator also found that the Sapphire RX460 does not work on 10.13 but the Sapphire RX480 does work OOTB, which it does not do on 10.12.6. Some something has changed. 10.13 beta does install on a late 2016 MBP with the RX460 option GPU so the drivers are present in the OS and a quick look through through the AMD kexts shows the presence of the correct GPU board ID. What has changed? I can't spot it from looking at kexts but does anyone here have an educated guess? A safe boot also gets to a desktop so the problem does seem related to a kext.
The unsupported MP runs the 10.13 betas fine when the stock Apple GPU is returned to the machine BUT having both the stock Apple GPU and the RX460 in the same machine causes the same problem of "booting" to a black screen with white rectangle at top right. I've seen someone mention a Windowserver crash but can't pin it down.
That's ok, take your time and write it as main stream for newbies as possible
I've read some stuff online on how to work with clover and it is kind of a mess out there
I AM ACTIVELY COMMUNICATING WITH OTHERS AND WAITING FOR A FIX FOR THIS AS WELL!
cMP 3,1 with Flashed AMD RADEON HD7950 with zero issues, until trying to install these HS betas. Running latest Sierra flawlessly. Last dosdude1 patcher went without a hitch. I want to know, too, was has changed?
I have tried all Developer and Public Betas, dosdude1's new patcher as well as newCore's. It all leads to the same freeze point at boot once the Install macOS HS drive is created and you are booting from it. I also tried copying the Extensions from "known-good" kexts in Sierra and "transplant" those into the respective installers (tried both). No go.
I don't have the tech at level of detail to understand behind the scenes what is going on and why this would have changed (see nekton1's dialogue further on process of elimination). Can anyone articulate this more clearly so we can follow what we know and what we need to focus on?
I would like to ask if we can we have some more discussion on this particular area from our experts out there? Given my naive approach to the "transplant" of known-good kexts working fine in Sierra into the HS Installer(s), could this be something that could be integrated in a future release?
This will impact so many users who have multiple/various video cards. I await a response from The Oracles in The Matrix.
Successfully installed High Sierra developer Beta 3 on 2009, 17 Inch, MacBook Pro 5,2
Words of caution: my writeup worked on my machine, but it may have unforeseen effect on other users' computers. Please back-up your data to assure it is not lost in experimentation. In addition, if you use Little Snitch, make sure that you have the latest *nightly* Little Snitch installed; failure to do so will result in a runaway CPU usage by Little Snitch.app upon boot to High Sierra Beta 3.
Process did require additional steps to those described in Foxlet’s and Dosdude’s instructions. This method also required both: Foxlet’s NewCore Installer an Dosdude’s post-install patcher.
I re-used a flash drive (USB), which was previously used to install original 10.13 on my computer, (via dosdude's method). Hence, that flash drive still contained original installation files for High Sierra 10.13. (Note, that I used both foxlet’s and dosdue’s methods to test their installation capability, and both worked for *original* 10.13)
It also meant, that dosdude’s post-install patch was present on that original 10.13 install setup (USB drive); it becomes important in latter part of installation. If your flash drive dose not contain dosdude’s post-install patcher file, then manually copy it to that drive, AFTER installing Foxlet’s NewCore installer (my flash drive was not erased, so it was there by serendipity - see below).
I used Foxlet’s FetchMacOS utility to download the Beta3 files. Keep in mind that Python needs to be installed on your machine (at least it was in my case).
Unzip FetchMacOS zipfile —> open folder—>double click on file titled “RunMe.command” to start the process. It will launch Terminal and present you with request for password; enter your administrator password and press return. If all works, a terminal window will open, and let you follow download progress. In the end, there should be a folder on your drive with High Sierra Beta3 installation components.
While download proceeded without problems, the downloaded components were still in “Stab” format i.e. there was no OSXinstall.app, just packages.
Since dosdude’s patcher works with actual installer.app, I could not use that method.
I used Foxlet’s NewCore-installer application to initiate the process. Check his instructions as to which files (packages) need to be copied into “what” folders in the NewCore-installer.
While following Foxlet’s instructions, I noticed that a “file” titled InstallESD.dmg needed to be copied to NewCore-Installer, but it was not visible in folder containing the FetchMacOS-downloaded packages, dmgs, and files. I used ==> *Pacifist*<== to open each package (.pkg) and check whether it contained the “InstallESD.dmg.” I found it in one of the packages, but at this point in time (a while after) I don’t recall in which .pkg it was “hidden.”
I copied that file, installESD.dmg, into appropriate folder in CoreInstall (see folxlet’s instructions)
To initiate process of flash drive installer formation, launch the script in CoreInstall folder named “createdisk.sh.” ==>Click to highlight that script file, than drag-and-drop its icon onto the open terminal window. A direct path to the createdisk.sh file will be displayed in the terminal, just press return to execute the file and follow further instructions. It is assumed that you have a flash drive already in your USB port.
I did run into problems in this process. The CoreInstall script was supposed to erase the flash drive, before installing the new Beta3 files, but it did not erase the drive (I had original High Sierra 10.13 installed on that flash drive - this may be important.) While the script executed to completion, the terminal window displayed several run-time errors.
When I checked contents of the flash drive, I realized that it [flash drive] was not totally erased prior to Beta3 files transfer, but the Beta3 files were actually transferred into proper folders. I checked “Info” on those files and it displayed “today” under date of formation, and size of files matched the new Beta3 installation files.
Next, boot into the flash drive, by rebooting computer while holding option key; you will be presented with choices of drives capable of booting your machine; choose the flash drive.
If all went well, you should see standard OS X installer window. Follow instructions on screen.
Once installation is completed, computer has to be rebooted back into flash drive; again use option key while rebooting to be able to select the flash drive.
Here I run into problems: I tried to run Foxlet's necessary post install “system-patcher-sh” script, and while it did run, the terminal window showed multiple run-time errors, with message: “sudo command not found,.” I tired to boot into main operating system, but it failed with “Do-Not-Enter” sign - circle with line across it.
I tried to run “sudo” command directly in terminal to test terminal response, and also was greeted with “no sudo command found.” That was first time I have seen this error message.
I booted back into the Flash Drive (using option key method), which greeted me with OSX installer screen. I clicked randomly on the window (not installer icon window) to change focus, then accessed dropdown menu in menubar, clicking on utilities. There I found Dosudue’s post-install patcher listed in menubar’s drop down menu. [Note that I suggested to make sure dosdude’s post-install patcher is copied onto flash drive manually (see above.)]
I launched Dosdue’s post-install patch, by double clicking on its icon, and followed the instructions, choosing appropriate modification for my machine. Rebooted again, with option key on to get boot choices, selected main drive with High Sierra Beta3 installed and ... I was greeted with standard installation messages and process completed without a hitch.
I have a fully operational Beta3, other than no track-pad configuration (a known issue).
Many, many thanks to everyone involved in this project.
Hope this is of help.
Attachments
Last edited:
Hi there, I think all that installation mixing has your mac going nuts, because I have your model, a Macbook pro 17 mid 2009, 2.8 C2D, ergo Macbookpro5,2 and my trackpad is working fine as well as the its configuration, I used public beta 2 ( Developer beta 3) with @dosdude1 patcher and everything works fine...
The only odd thing is on about this mac is shows as an early 2009, but other than that it runs like butter.
