Sorry if this has been answered (I searched but my issue has a lot of generic / common terms in it so couldn't find the answer).
Patcher USB creation runs successfully (after formatting USB as Journaled with GUI Partition Map)
USB device shows in boot menu after holding alt/option during boot
When I select the USB device and press return it just reboots and goes into the old install of macOS.
So, it seems like the stick is bootable, but not? All I can gather is that there is something not right with the files on the USB after the patcher created it. No errors that I noticed in the process, says Completed! at the end.
Thoughts I where I can start? Log files, etc?
Edit:
More info... Previously did a successful install of HS on this same machine with a different USB stick but it machine suddenly slowed to a crawl at some point (after a macOS update, I think) so I decided to reinstall. Original USB stick was giving the "no" symbol and so I assumed it was corrupt or something. Only thing that changed with the machine after the original successful HS install was I addd more RAM (when from stock 2x 2GB to 2x 4GB), but that shouldn't have any effect(?), thought I'd mention it.
UPDATE (RESOLVED): Tried a different USB stick and it worked. No idea why that other stick would be succeed the creation process and show in the boot menu but not actually boot. Leaving this for others reference.
Have to inform you this is not news, did this a year ago and its well documented earlier in this very same thread. Please update your post to reflect that.
Have to inform you this is not news, did this a year ago and its well documented earlier in this very same thread. Please update your post to reflect that.
Thanks. At the moment, I'm leaning towards the Crucial but we'll see. With hard drives I know who the usual suspects are - so it's strange to see brands you'd normally associate with compact flash and that kind of thing.
For the first time since OS X Mountain Lion (10.8) in 2012, macOS Sierra (10.12) changed the official minimum requirements needed for installation, leaving many older (but still perfectly capable) Macs behind. Now macOS High Sierra (10.13) brings a new set of updates, and older Macs that can possibly run them.
MacBook (late 2009 or later)
iMac (late 2009 or later)
MacBook Air (2010 or later)
MacBook Pro (2010 or later)
Mac mini (2010 or later)
Mac Pro (2010 or later)
Note this space!
Preliminary Tested Models List:
MacBookPro5,5 (13-inch Mid 2009) - No issues
MacBookPro5,4 (15-inch Mid 2009) - No issues
MacBookPro5,3 (15-inch Mid 2009) - No issues
MacBookPro5,1 (15-inch Late 2008) - No issues
MacBook5,1 (13-inch Unibody Aluminum Late 2008) - No issues
MacPro3,1 (Early 2008) - No issues
iMac7,1 (Mid 2007 W/BCM94360CAX and SSE4 supported T9300) - Screen brightness is controllable (NightShift works with modified CoreBrightness.frameworks)
MacBook5,2 (Early [Mid] 2009 MacBook) - Screen brightness not controllable (buttons don't work either), volume buttons do not work, same trackpad detected as USB mouse issue
Xserve2,1 (Early 2008) - graphics are unaccelerated with the original ATI X1300 unless an upgraded graphics card e.g. Nvidia GT 120 (from a Mac Pro) is installed
Known Patching Methods:
Automatic tools that can be used to install macOS High Sierra onto an unsupported Mac.
Modifying the Security Updates or macOS Updates for Sierra or High Sierra.
Download the update.
Open the update.
Move the update.pkg to Desktop.
Open Terminal.
You will need to know your BoardID, In Terminal paste the following command
ioreg -lp IOService | grep board-id
hit Return
Enter pkgutil --expand now drag and drop the .pkg from the Desktop into the Terminal window andtype after a space ~/Desktop/Expanded hit Return and wait, this takes a little while.
Open Expanded folder and then open Distribution file in Text Wrangler or BBEdit
Change Distribution file, change Board iD select one and change it to <your Macs boardID> go to nonSupportedModels remove <your Mac model>
Save As .xml file to the Desktop
In Terminal chmod +x ~/Desktop/distribution.xml (or just drag it in to the Terminal window)
Remove the extension .xml
Move new Distribution file to Expanded replacing the original
In Terminal pkgutil --flatten ~/Desktop/Expanded ~/Desktop/Modified.pkg
Using the .pkg extension is crucial.
hello fm france ; my english is not good enough ..; with my imac 8.1 early 2008 , working with Elcapitan can I install High Sierra without problem, ? if there are paoblem, which one ? thank's for help
[...]with my imac 8.1 early 2008 , working with Elcapitan can I install High Sierra without problem, ? if there are paoblem, which one ? thank's for help
It looks like your iMac is supported by the patch since the main page says "Early-2008 or newer [...] iMac 8,1", however, the process is not what I would call "easy". You must make an installer USB key following the instructions and you must run the post-install patch tool after installing by booting the patched USB installer key again but this time 'exit' (or ignore) the installer dialog window and look for the post install patch tool in another window. It took me a few tries to figure it out. If you are not comfortable with this level of technical software installation, I wouldn't recommend upgrading to High Sierra. Even if the installation works, there are always concerns that future updates (although there may not be any more for High Sierra, but if there are) mess things up. It's difficult to predict what can go wrong but usually it's that people forget to run the post-install patch tool that generally makes things work. Many things can go wrong (loss of WiFi, graphics problems, etc) too many to practically list here for you but many of the limitations are posted on the patch page which Google Translate would do a good job on).
Using DosDude's package for patching Mojave on a MacBook Air 4,1 mid 2011.
I am running this in a second partition next to the main container with High Sierra.
The Patchtool does not see this container/partition, so for updates or installs I copy to an external drive, install & patch, and then CarbonCopyClone this back.
This used to work until now. On the latest update to the release I get a boot error (volume not permitted circle) after cloning. The external drive boots fine.
Does anybody have any ideas of what is going on?
Using DosDude's package for patching Mojave on a MacBook Air 4,1 mid 2011.
I am running this in a second partition next to the main container with High Sierra.
The Patchtool does not see this container/partition, so for updates or installs I copy to an external drive, install & patch, and then CarbonCopyClone this back.
This used to work until now. On the latest update to the release I get a boot error (volume not permitted circle) after cloning. The external drive boots fine.
Does anybody have any ideas of what is going on?
Rinse and repeat fixed it! I also had to apply the plist patch for Continuity to work properly - it was indicated to work but I could not get Watch Unlock to work or other continuity features to show. This 4,1 has a new WiFi/BLE module grafted on plus 1TB OWC. Apart from the horrible battery life of the earlier models it is serviceable as a third computer.
Just wondering if there might've been a security update to High Sierra that's incompatible with a Mac Pro 3,1?
I had a fully working Mac Pro with High Sierra. But the past couple of weeks I'd been using Win10 (which is on a different SSD from HS)... over the weekend I finally tried booting into MacOS again and I got the "no" sign. I can't recall changing any settings. BUT I might have goofed and did a software update through the App store, forgetting I was using it on an unsupported machine. Oops, maybe?
I got my trusty USB with the patcher and tried to repatch the drive. No go. I decided to re-download the v2.6.2 of the patcher along with a fresh copy of High Sierra. Tried to repatch again, but it was still a no go. So now I tried nuking the SSD (after backing up my files), reinstalling the OS, and then patching it. No go again. The result is always the same.
Luckily, I saved a copy of my original High Sierra installer from Nov 2017 that I can try. But I'm just wondering if there's a way I can run the latest security patches to "help me sleep better at night".
It doesn't look like I'll be able to upgrade to Mojave because I'm running an ATI Radeon 7970 (sounds like any ATI card won't work, even if only the 5xxx and 6xxx were specifically called out), so there goes that. I'll keep you posted if the old installer ends up working.
[...]tried nuking the SSD (after backing up my files), reinstalling the OS, and then patching it. No go again.[...]Luckily, I saved a copy of my original High Sierra installer from Nov 2017 that I can try. But I'm just wondering if there's a way I can run the latest security patches to "help me sleep better at night".
Did the reinstall finish without errors? Did you use Journaled HFS+? There's a special procedure to use APFS so I didn't bother even though I'm using an SSD.
Some people have reported here that troubles ended up being a bad HS download (although I think those are usual installer failures in general). Might be worth trying your original patched USB installer key. Beyond that, sounds to me like you're doing everything correctly and we'll need smarter people to chime in here.
Did the reinstall finish without errors? Did you use Journaled HFS+? There's a special procedure to use APFS so I didn't bother even though I'm using an SSD.
Some people have reported here that troubles ended up being a bad HS download (although I think those are usual installer failures in general). Might be worth trying your original patched USB installer key. Beyond that, sounds to me like you're doing everything correctly and we'll need smarter people to chime in here.
I've been using the same USB key, so I nuked that too and put the latest patcher with the Nov 2017 installer on it. It failed to boot (progress bar on boot screen took forever to get to "100%", and nothing). Repeated the whole process a few times, and then I gave up.
I'll heed your advice and re-make the USB key with the old patcher I used along with the Nov 2017 installer. The SSD is reformatted to APFS right now but I'll also change that to HFS+ too.
When it was working I had started with HFS+, then converted to APFS, and eventually encrypted it with file vault. Worked fine for months, so I thought I'd try starting with APFS. Hopefully everything works after this.
Side note: Also hoping the Win10 SSD has nothing to do with it. It still boots up, but it's been trying to update and keeps failing, then reverting updates, then normal boot. Thing is, I had created it on a Mac Pro 2,1 and stuck it in the 3,1 when I upgraded towers.
Got some good news: the short of it is that I've been able to get HS up and running again.
Long(er) version: Many more attempts later and a new, fresh dl of the installer (from within the patcher tool this time) finally did it. I reformatted the SSD to HFS+ Journaled, and now it's currently APFS unencrypted.
A few differences to note: the login screen is now red when it wasn't before (I've read this is a common bug on this setup, though), on the boot select screen there's a new 10.13.6 Recovery drive that I didn't have before (gives a "no" sign if you try to boot it), and File Vault doesn't want to encrypt the APFS drive anymore (it's complaining something about a boot partition/file missing, or something like that). The old setup was definitely encrypted before, and these are the differences I've noticed so far. At least I now know my machine isn't borked.
@tsialex After reading thru much of this thread (whew it's a long one!), you seem to be the guy who knows most about getting HS up and running on a Mac Pro 3,1 with as few tweaks as possible.
Questions:
Could dosdude's current patcher for HS work with a Quadro K5000? I know you recommend the GTX 680, but I see no mention of anyone trying this GPU in 3,1 on HS.
And does one need to use dosdude1's patcher to get HS working on a 3,1? I've seen some replies of yours explaining a more simple, less intrusive fix.
Currently running:
Mac Pro 3,1
Processor: 2 x 2.8 GHz Quad-Core
Graphics: ATI 5770
Memory: 14 GB
Storage: OWC 3G SSD system drive
@tsialex After reading thru much of this thread (whew it's a long one!), you seem to be the guy who knows most about getting HS up and running on a Mac Pro 3,1 with as few tweaks as possible.
Questions:
Could dosdude's current patcher for HS work with a Quadro K5000? I know you recommend the GTX 680, but I see no mention of anyone trying this GPU in 3,1 on HS.
And does one need to use dosdude1's patcher to get HS working on a 3,1? I've seen some replies of yours explaining a more simple, less intrusive fix.
Currently running:
Mac Pro 3,1
Processor: 2 x 2.8 GHz Quad-Core
Graphics: ATI 5770
Memory: 14 GB
Storage: OWC 3G SSD system drive
With 10.13 you can use almost any Nvidia card, 8800GT on wards. With 10.14, only Kepler cards - Maxwell and Pascal ones are not supported without web drivers. Quadro K5000 is a Kepler card, the professional version of GTX 680.
If you have another supported Mac to do the install, you just need to add "-no_compat_check" on the NVRAM boot-args, after that you can boot a standard install. I usually take my MP31 disk to my MP51 and do the install there.
First, add the APFS module to your BootROM, you can add it with UEFITool or with dosdude1 APFS Patcher. After that you don't need any hacks or patches beyond -no_compat_check.
Later if you want to have a fail proof install, add -no_compat_check to
/Library/Preferences/SystemConfiguration/com.apple.Boot.plist. After that I can zap-PRAM anytime.
With 10.13 you can use almost any Nvidia card, 8800GT on wards. With 10.14, only Kepler cards - Maxwell and Pascal ones are not supported without web drivers. Quadro K5000 is a Kepler card, the professional version of GTX 680.
If you have another supported Mac to do the install, you just need to add "-no_compat_check" on the NVRAM boot-args, after that you can boot a standard install. I usually take my MP31 disk to my MP51 and do the install there.
First, add the APFS module to your BootROM, you can add it with UEFITool or with dosdude1 APFS Patcher. After that you don't need any hacks or patches beyond -no_compat_check.
Later if you want to have a fail proof install, add -no_compat_check to the boot.ini. After that I can zap-PRAM anytime.
I got High Sierra up and running on my early 2009 Mac Pro 4,1 with no issues. It will not however run with my Nvidia GeForce GTX 980 graphics card as it's not supported under HS. Looking online showed a few sites and YouTube videos where it can apparently be made to run, but these tweeks or hacks seemed a bit beyond my level so I left them alone. Instead I opted for a Radeon Nitro+ RX 580 8Gb as it's natively supported by HS. Bought it on eBay. Should arrive next week. Till then I'm a slave to 512Mb graphics. (Yay for me!)
Before I even attempted to install HS using dosdude's Patcher, I did try to flash my 4,1 to 5,1 with no success. I spent the best part or a whole day trying it. I had csrutil disabled, and was using the latest Mac Pro 2009-2010 Firmware Tool and the MacProEFIUpdate.dmg, and following the instructions to the letter.
I would get to the very end of the procedure where I am looking at a message on my screen telling me to restart so as to complete the procedure. At this point my machine should restart and then flash itself to 5,1. Instead it would restart, then quickly shutdown again, only to then restart as per normal. A check in "About My Mac" would show it to still be 4,1. Anyhow, I guess that's not an issue for me anymore as HS works on the machine as a 4,1.
I got High Sierra up and running on my early 2009 Mac Pro 4,1 with no issues. It will not however run with my Nvidia GeForce GTX 980 graphics card as it's not supported under HS. Looking online showed a few sites and YouTube videos where it can apparently be made to run, but these tweeks or hacks seemed a bit beyond my level so I left them alone. Instead I opted for a Radeon Nitro+ RX 580 8Gb as it's natively supported by HS. Bought it on eBay. Should arrive next week. Till then I'm a slave to 512Mb graphics. (Yay for me!)
Before I even attempted to install HS using dosdude's Patcher, I did try to flash my 4,1 to 5,1 with no success. I spent the best part or a whole day trying it. I had csrutil disabled, and was using the latest Mac Pro 2009-2010 Firmware Tool and the MacProEFIUpdate.dmg, and following the instructions to the letter.
I would get to the very end of the procedure where I am looking at a message on my screen telling me to restart so as to complete the procedure. At this point my machine should restart and then flash itself to 5,1. Instead it would restart, then quickly shutdown again, only to then restart as per normal. A check in "About My Mac" would show it to still be 4,1. Anyhow, I guess that's not an issue for me anymore as HS works on the machine as a 4,1.
Ok. But I have managed to get HS on my machine as a 4,1. I have a new RX 580 in the mail that runs natively with HS. If I flash my system now, would I only create problems? My reason for asking is..... I'm not that tech-savy (though with detailed instructions I'm fine), and I run with the saying "If it ain't broke........".
I guess what I am asking is what advantage would i get if I flashed to 5,1?
[doublepost=1538194280][/doublepost]Also ended up with this message when I tried to instal from your link:
"Your firmware could not be updated, the hard drive partition scheme may not be supported. You must be booted from a GUID partition or RAID scheme"
I have no idea what that means. But as I have said... If everything is working, do I really need this?
