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.
Hi do you think it is also possible to run an El Capitan in virtual machine to download Sierra, of course from unsupported mac?

Yes. I said before this can be done with a Sierra or El Capitan virtual machine. If you want to do it via El Capitan, make an El Capitan virtual machine. How to do this will differ depending on which virtualisation software you use. Whilst in the virtual machine go to mac app store, sign in.

Then there are 3 ways to download the Sierra full installer inside the virtual machine.

1. If you have previously redeemed a code for Sierra go to purchases tab and click Download. Ensure first there are no older Sierra installers in the virtual machine.

2. If you are a public beta tester, go to https://beta.apple.com/sp/betaprogram/ log in and redeem a code for Sierra.

3. If you are a developer, go to https://developer.apple.com/macos/ , click Download, login with developer account, find the GM and click Download again and a new redemption code will be generated and be redeemed in the mac app store.

Doing this inside the virtual machine means it won't matter if you are running it on a machine which is not directly supported.
 
  • Like
Reactions: brunsik
Thanks, will check that.

Confirm that it works.

1. Install osx el capitan in virtualbox
2. start MAS
3. create account in MAS through MAS app
4. Redeem sierra code
:)

FGhiyEc.png
 
Last edited:
Yes. That's right. It's an old trick I learnt a long time ago.

I use parallels but any such program should do.

Excellent! Beats running around to download from a supported system. I'm lucky enough to have an old iMac that's still supported , so would download from my developer account there. Funny, I've actually never virtualized a Mac on Mac before, mainly used it for Windows or other nix flavors (ubuntu, debian, linux etc...).

Now I'm intrigued about a virtualized system profile in that context. Could you share what the following commands return in your virtualized environment?

Code:
    var cpuFeatures = system.sysctl( 'machdep.cpu.features' );
    var currentModel = system.sysctl('hw.model');

This would explain alot.

btw, I would do so myself but don't have enough space left on my box to install another virtualzed OS for the moment :(

Thanks in advance, P.
 
Many (myself included) have successfully upgraded their pro 3,1 using the procedures here many times.
You don't provide much to go on...

Questions:

- describe your hardware a bit
- describe your current OS a bit (Yosemite, El Capitan, Sierra previews....what?)
- can you boot from that USB hard drive?
- if you have a spare USB stick, try this:
  • make sure you have enough free space on your system disk. Sierra installer needs space + recovery partition
  • run disk utility repair and permissions. make sure your system checks out.
  • backup your system. make sure its good.
  • reboot
  • download dosude's latest utility and record the version number
  • follow the instructions to prepare a usb boot stick
  • run the utility to prepare your usb boot disk
  • again follow the instructions and attempt another install

I have try again but with no success !

- when I try to make the installer on my USB Drive with my Mac Pro, I have an error message "An error occurred patching files. Please check your USB drive and macOS Sierra Installer App, then run the tool again."
- when I try to make the installer on a partition of the intern drive of my Mac Pro, it work, but when I reboot, my computer shut down after 1 min
- when I try to make the installer on my USB Drive with my MacBook Pro (Sierra compatible), it work. I can boot my MacBook Pro with that installer, but, if I try to use this installer with my Mac Pro, the computer shut down after 1 min...

Any idea ? I think I will have to buy a new computer to use Sierra !
 
I have try again but with no success !

- when I try to make the installer on my USB Drive with my Mac Pro, I have an error message "An error occurred patching files. Please check your USB drive and macOS Sierra Installer App, then run the tool again."
- when I try to make the installer on a partition of the intern drive of my Mac Pro, it work, but when I reboot, my computer shut down after 1 min
- when I try to make the installer on my USB Drive with my MacBook Pro (Sierra compatible), it work. I can boot my MacBook Pro with that installer, but, if I try to use this installer with my Mac Pro, the computer shut down after 1 min...

Any idea ? I think I will have to buy a new computer to use Sierra !
Ok - much to absorb here...

First of all, it seems like you are trying to create a "universal" installer on a usb stick. Personally, I've never tried that use case. I've also never attempted to "patch" an internal drive in place (assuming you can normally boot to it). So I won't comment on those variants.

At this point, the only thing I can suggest (assuming your system is "healthy" per my previous post), is to follow the patcher's recommendation:

- check your USB stick - switch to a new one if necessary
- check your macOS Sierra Installer App - you should be able to run it in-place and let it verify at least.
- what is your host OS?
- Do you option-boot when required (press the option/alt key when restarting and make sure you boot off of the right disk/partition)
- did you rule out any issues with your new video card (are there Sierra compatible drivers for it)

With a little persistence, you should be able to keep your old system...there is plenty to try when reading this thread. :)

Of course, if you have the resources to purchase a new system ...

P
 
Last edited:
Of course, if you have the resources to purchase a new system ...

The problem of buying a new computer is that I really don't know what to buy :
- the new mac pro est VERY expensive and a little out of date
- I don't the iMac-concept
- the mac mini seem's uncompetitive...
 
btw, I would do so myself but don't have enough space left on my box to install another virtualzed OS for the moment

Actually there is yet another way to download the full installer of Sierra on an unsupported machine from a legitimate source - useful if you don't have space enough for a virtual machine.

Instead of a virtual machine you can install sierra or el capitan onto an external hard drive or ssd. Then boot up from the external drive, go to mac app store, login and then download sierra to the external drive in the manner I previously described for virtual machines.

This too will circumvent the machine check and will not take up any space on your computer.
 
The problem of buying a new computer is that I really don't know what to buy :
- the new mac pro est VERY expensive and a little out of date
- I don't the iMac-concept
- the mac mini seem's uncompetitive...
It's more than a little out of date, and there are rumors, that Apple is going to discontinue it outright this fall.
 
The problem of buying a new computer is that I really don't know what to buy :
- the new mac pro est VERY expensive and a little out of date
- I don't the iMac-concept
- the mac mini seem's uncompetitive...

I am happy with my late 2009 MacPro - (running Sierra) they made those towers through 2012 -
get one of them and you can finess it for a few years more!
I don't like the black Cylinder macPros ...
 
Installed in MB 5,2 mid 2009. Everything works fine, except for the trackpad, the button works and I can move the pointer just fine, but the clicking on the trackpad itself does not work anymore. The preference panel only shows a option for a bluetooth trackpad. Any way to fix this?

View attachment 650373
Has anyone else tried playing around with this problem? Or, were the results the same as with the PBs?
 
Actually there is yet another way to download the full installer of Sierra on an unsupported machine from a legitimate source - useful if you don't have space enough for a virtual machine.

Instead of a virtual machine you can install sierra or el capitan onto an external hard drive or ssd. Then boot up from the external drive, go to mac app store, login and then download sierra to the external drive in the manner I previously described for virtual machines.

This too will circumvent the machine check and will not take up any space on your computer.
I can comprehend how running a virtual OS can somehow spoof the machine check. But how booting from an external drive achieves that is still a mystery to me. I mean, you're still booting off the same physical machine - right? Guess I'll try that myself if time permits. Thanks again for the tips!
 
The problem of buying a new computer is that I really don't know what to buy :
- the new mac pro est VERY expensive and a little out of date
- I don't the iMac-concept
- the mac mini seem's uncompetitive...
Then you're in the same boat most of us here are...;)

We may have the same machine...Here are my specs:

Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3.2 GHz
Number of Processors: 2
Total Number of Cores: 8
L2 Cache (per Processor): 12 MB
Memory: 16 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4
Serial Number (system): XXXXXXXXXXX
Hardware UUID: XXXXXXXXXXXXXXXXX

System Version: macOS 10.12 (16A320)
Kernel Version: Darwin 16.0.0
Boot Volume: XXXX
Boot Mode: Normal
Computer Name: XXXXXX
User Name: XXXXXX
Secure Virtual Memory: Enabled
System Integrity Protection: Disabled
Time since boot: 5 days 22:18

What are yours? Go to :apple:->About This Mac-->System Report . Then click on Hardware and Software.

Try (again?) some of the suggestions above and post your system profile like I just did.

Good luck.
 
I can comprehend how running a virtual OS can somehow spoof the machine check. But how booting from an external drive achieves that is still a mystery to me. I mean, you're still booting off the same physical machine - right? Guess I'll try that myself if time permits. Thanks again for the tips!

Well in this case it isn't really the drive on the computer which is booting, but the external drive instead. And what can be downloaded on the external drive through the mac app store is not beholden to the machine check of your computer.
 
I am happy with my late 2009 MacPro - (running Sierra) they made those towers through 2012 -
get one of them and you can finess it for a few years more!
I don't like the black Cylinder macPros ...
Same here. I'm hoping to extend my "trash can" pro's life for at least another year.

However, the newer four core cpus have been running rings around our 8+ core Xeon setups for a while now. But, while Dell and HP are moving on to the seventh-generation Intel Kaby Lake processors this fall, Apple is still clinging to the fifth-generation Broadwell chips. Rumor has it, the new macbook pro's will only sport sixth-generation Skylake chips, so meeting in the middle. And of course, the new mind set at Infinite Loop is to offer less for more: probably a single USB-C forcing the additional purchase of docks and dongles where all of our external devices will hang. Intel's integration of Thunderbolt 3 in USB-C connections, USB, Thunderbolt, DisplayPort, PCI Express and power can be delivered over a single cable...blah blah blah

As for a new macPro? Even though Tim Cooke recently professed a long lasting commitment to the mac...I wouldn't hold my breath...They're making billions selling shiny black over-priced mobile devices. I'm afraid the bean counters aren't looking too kindly at the pro-line anymore...I may be wrong.

Yes, there are some really great bargains on older 2010+ pro towers, if you don't mind popping the hood and getting your hands a little dirty...One area where these older desktops still shine is graphics card expandability. Laptops still can't beat that.
 
Well in this case it isn't really the drive on the computer which is booting, but the external drive instead. And what can be downloaded on the external drive through the mac app store is not beholden to the machine check of your computer.

Intrigued, I just attempted an experiment booting my unsupported MacBookPro 5,3 off an external firewire drive with Yosemite. I logged into my developer account and, as usual, it led me to the MAS with a Redemption Code. I got the usual Redemption Code previously used message, but Sierra appeared in my MAS purchased tab. As expected. So I clicked and...

App Store.jpg


Sure looks like the MAS does NOT bypass the machine check when booting off an external drive.
Am I missing something here?

Whether I boot off an external drive or not, my physical system is still the same:

Code:
$ sysctl -n hw.model
MacBookPro5,3
$ sysctl -n machdep.cpu.features
FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 XSAVE
$ ioreg -lp IOService | grep board-id
"board-id" = <"Mac-F22587C8">

Right? All makes perfect sense to me. Maybe you have another scenario in mind?

Would still like to see what sysctl reports in your virtual box though...:)

P.
 
Intrigued, I just attempted an experiment booting my unsupported MacBookPro 5,3 off an external firewire drive with Yosemite. I logged into my developer account and, as usual, it led me to the MAS with a Redemption Code. I got the usual Redemption Code previously used message, but Sierra appeared in my MAS purchased tab. As expected. So I clicked and...

View attachment 652070

Sure looks like the MAS does NOT bypass the machine check when booting off an external drive.
Am I missing something here?

Whether I boot off an external drive or not, my physical system is still the same:

Code:
$ sysctl -n hw.model
MacBookPro5,3
$ sysctl -n machdep.cpu.features
FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 XSAVE
$ ioreg -lp IOService | grep board-id
"board-id" = <"Mac-F22587C8">

Right? All makes perfect sense to me. Maybe you have another scenario in mind?

Would still like to see what sysctl reports in your virtual box though...:)

P.
An El Capitan VMWare guest on MacPro3,1 gives me this sysctl reports and I can download Sierra without problems.

Code:
vmwares-Mac:~ vmware$ sysctl -n hw.model
VMware7,1
vmwares-Mac:~ vmware$ sysctl -n machdep.cpu.features
FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS MMX FXSR SSE SSE2 SS HTT SSE3 MON SSSE3 CX16 SSE4.1 VMM TSCTMR
vmwares-Mac:~ vmware$ ioreg -lp IOService | grep board-id
    |   "board-id" = <"Mac-F42C88C8">
 
An El Capitan VMWare guest on MacPro3,1 gives me this sysctl reports and I can download Sierra without problems.

Code:
vmwares-Mac:~ vmware$ sysctl -n hw.model
VMware7,1
vmwares-Mac:~ vmware$ sysctl -n machdep.cpu.features
FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS MMX FXSR SSE SSE2 SS HTT SSE3 MON SSSE3 CX16 SSE4.1 VMM TSCTMR
vmwares-Mac:~ vmware$ ioreg -lp IOService | grep board-id
    |   "board-id" = <"Mac-F42C88C8">
Cool! Both the hw.model and features are "changed". Makes sense. Nice to know....

Thanks alot.
 
Maybe you have another scenario in mind?

Well last time I did it it was with a USB hard drive, not firewire. Don't know why that should make a difference though.

Anyway, at least several people here have had more success with the virtual machine method.
 
Well last time I did it it was with a USB hard drive, not firewire. Don't know why that should make a difference though.

Anyway, at least several people here have had more success with the virtual machine method.
Yeah USB or FireWire shouldn't make a difference...

On the more curious front though, if your sysctl bits under Parallels are anything like @chromafile under VMWare , you should be able to at least install a virtual Sierra. Have you tried? Even though I can foresee some hardware and kext issues cause they inject their own drivers (especially graphics )

Obviously stepping into Hackintosh world here...;)
 
For anyone looking for a Liteicon fix, i experimented around a little bit and in Liteicon > contents > resources I changed icondata_ 10.11 to icondata_ 10.12 and it works pretty stable now, albeit you get a "This system is not supported" banner across the top. Happy Customizing.

Hmmm... I'm on the GM and this isn't working for me. Did you also go into the plist and change all 10.11 to 10.12? Thanks.

EDIT: I get a dialogue that says, "LiteIcon.app”is damaged and can’t be opened. You should move it to the Trash."
 
Last edited:
Hmmm... I'm on the GM and this isn't working for me. Did you also go into the plist and change all 10.11 to 10.12? Thanks.

EDIT: I get a dialogue that says, "LiteIcon.app”is damaged and can’t be opened. You should move it to the Trash."
If you're going to bring up a tip someone posted two months ago, you really need to fix your quote so they get a notification. :)
 
Just in case you are not aware, there is a new build now. 16A323.

So rather than wait for it to go up on some unauthorised source (if it ever does) maybe you should use the virtual machine method to get it the legitimate way if you want to download it on an unsupported machine.
 
  • Like
Reactions: fischersd
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.