Anyone having trouble installing Xcode 9 on a machine with the patch installed (Sierra or High Sierra)? Seems to be stuck for me at the ‘install additional components’ phase.
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'm going to make another patcher... There are some major changes within the macOS Installer, it seems... When creating the installer drive using the standard restore BaseSystem to volume and copy Packages method, it doesn't work... It boots, but the installer just says "/System/Installation/Packages/OSInstall.mpkg is missing or damaged", even though the file is there and is unmodified. Still trying to figure this out, as it's quite strange.@dosdude1 are you going to push out a small update for the Sierra or just make another patcher for this OS?
Also All the Night Shift patches work perfectly.
@dosdude1 are you going to push out a small update for the Sierra or just make another patcher for this OS?
Also All the Night Shift patches work perfectly.
I wonder if pushing out an update right from Sierra 10.12.5 to High Sierra would even be possible with the patcher, but it would be really useful.
I can confirm this doesn’t work on the MacBook 5,2. With that being said, my MacBook is history and this is such a small update I don’t think it’s worth doing a video. I think I’m done with the unsupported Mac game. Good luck though y’all!
instead of it, you could just change launchagent plist for the installer to insert SUVMMFaker.dylib? because vmm check also bypasses unsupported model check i think
In terms of upgrades, we might be able to skip the flash drive completely...
This was on a supported machine, with a completely unmodified installer.
For the working SUVMMPatcher we need to wait for the first update. But now, i am thinking its working now and nothing is changed in the upgrade process/requirements check.
Ok! You've piqued my interest...Seems like you have an installer running ... Pray tell ...In terms of upgrades, we might be able to skip the flash drive completely...
The "pre-alpha" version of HSierra patcher currently panics on boot...
Ok! You've piqued my interest...Seems like you have an installer running ... Pray tell ...
Alternative Installer works indeed (this on top of APFS MacBookPro5,3).
Note that it doesn't rely on @dosdude1's Sierra patcher, it's a new implementation that has a new set of legacy kexts and support files.
Last edited:
Alternative Installer works indeed (this on top of APFS MacBookPro5,3).
So are you saying you've got it to boot from an APFS partition?
And was that a re-format and clean install? Or an upgrade?
Yes.
So everything works perfect on it?
I have a similar model, Macbook pro 17 mid 2009
macOS High Sierra on unsupported Macs
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,3 (Mid 2009 MacBook Pro)
MacBookPro5,1 (Late 2008 MacBook Pro)
MacPro3,1 (Early 2008 Mac Pro)
Gonna test it out on my 2007 iMac today when I get home
Yes, all the hardware on it works just fine out of the box as in Sierra (with the necessary legacy USB support, of course). Wi-Fi, Ethernet, Sound, Backlight, keyboard illumination, Bluetooth, were some of the things tested.
Alternative Installer works indeed (this on top of APFS MacBookPro5,3).
Where can I find that Alternative Installer? Is it the one in the Sierra Unsupported Macs Thread
http://swdist.furcode.co/bin/AUSEnabler.zip
Or is that only for getting the 10.12.x updates?
That's really awesome news
I'm glad we are able to maintain 2 and 3 year old hardware running the latest macOS for at least one more year ;-)
Hope you guys can put together a tool, or a guide, that enables people like me (regular users) to install the macOS High Sierra on these still very awesome macs, I still love my Macbook pro 17
Thanks for the reply
[doublepost=1496755565][/doublepost]
To my knowledge that link is for the first tool that enabled updates in macOS Sierra.
The " alternative " installer that is mentioned I believe it's still " cooking ", at least that's what it looks like
that would just be for clean install right? Upgrading to High Sierra and then running the post install should be good right?
[doublepost=1496755721][/doublepost]
Thats what I was going to try and doIn terms of upgrades, we might be able to skip the flash drive completely...
[doublepost=1496755931][/doublepost]
That's really awesome news
I'm glad we are able to maintain 2 and 3 year old hardware running the latest macOS for at least one more year ;-)
Hope you guys can put together a tool, or a guide, that enables people like me (regular users) to install the macOS High Sierra on these still very awesome macs, I still love my Macbook pro 17
Thanks for the reply
[doublepost=1496755565][/doublepost]
Im still maintaining 10 year old hardware. Minus the updated bluetooth/wifi card for 802.11ac and bluetooth 4.0. Although I might switch out the one in my iMac and put it in my 2012 MacBook Pro. The MacBook Pro natively supports latest macOS and continuity but not unlock from Apple Watch. So switching it out it will and the iMac, that doesn't need that feature will still have continuity
To my knowledge that link is for the first tool that enabled updates in macOS Sierra.
The " alternative " installer that is mentioned I believe it's still " cooking ", at least that's what it looks like
Cheers. Been a while since I looked at this.
Hi all! nice to see a lot of you again!
I just tried to make a usb installer (same usb I used for Sierra) but this year it kernel panics while booting from it.
I wil try to redo the usb patcher, some other ideas or should I wait..
Thanks alot
P.S. im on a macbook pro mid 2009
I just tried to make a usb installer (same usb I used for Sierra) but this year it kernel panics while booting from it.
I wil try to redo the usb patcher, some other ideas or should I wait..
Thanks alot
P.S. im on a macbook pro mid 2009
Code:
*** Panic Report ***
panic(cpu 1 caller 0xffffff801b76ccdf): initproc exited -- exit reason namespace 2 subcode 0x4 description: none
uuid info:
0x10f819000 uuid = <c3a32dff-b9a9-3510-b840-efcdef4d58a0>
0x10f295000 uuid = <b4539d66-a422-3674-8b72-018e85ac628a>
0x10f2f0000 uuid = <223f6863-e84e-31a6-9776-46dfc3f03fdf>
0x10f8b2000 uuid = <d986accf-2373-3f3c-8aad-f478b136843e>
0x10f2f8000 uuid = <7e91feb4-cb74-350c-92cb-ae338ad363fb>
0x10f300000 uuid = <92d1e484-0029-3d02-8672-bd078693c778>
0x10f319000 uuid = <843b5c31-21f9-310d-9131-05ebef648f01>
0x10f321000 uuid = <f06a78b4-6bdb-3693-8492-8b591052e0c3>
0x10f32b000 uuid = <b317e3b6-501d-324d-bbdc-ea396354d234>
0x10f343000 uuid = <f803a070-f8b7-37fb-bfd6-f076e82f419d>
0x10f358000 uuid = <0ee3526f-f742-3982-ad4d-de86e6a029ea>
0x10f367000 uuid = <dd6d824f-e18e-3716-9962-07d6bfbece24>
0x10f408000 uuid = <7095fe46-2ff7-3b80-b160-95366adf47f7>
0x10f47c000 uuid = <787fe571-03ac-334c-b984-606f7f0fd61b>
0x10f2ea000 uuid = <c90f99dd-ba5b-3735-aeb3-fab4afedd90e>
0x10f4af000 uuid = <6a9fb63d-90b8-3da0-a7d8-adbdd0d59b7e>
0x10f4b6000 uuid = <9c28065c-2c49-3b4f-8e1c-0b921c4ea8af>
0x10f4c1000 uuid = <14f326d2-1d8b-33ae-bd0b-38fb0129e5b7>
0x10f4ca000 uuid = <a3ac2c66-e4d2-36bf-9580-b4da1bac985c>
0x10f4d1000 uuid = <51c384c0-ab40-3615-bd6d-11f309f05f73>
0x10f4f6000 uuid = <47f78294-38b9-368b-b635-29735c367b9e>
0x10f4fb000 uuid = <cb25e8cc-40e2-3726-9c04-7144727d125e>
0x10f5ad000 uuid = <8c73c6b8-552d-313b-bca2-63565c037198>
0x10f5b7000 uuid = <d1f8ceaf-2001-392a-855e-2e5fd56aeb70>
0x10f5c0000 uuid = <0f83b182-c942-37f1-a660-6ff3f310823d>
0x10f5c7000 uuid = <4426f07d-4322-38b7-b74f-c6b5f363acee>
0x10f5d4000 uuid = <4d57621e-a78e-3da9-8d0c-67e8cf62a766>
0x10f635000 uuid = <3c3e7519-e77e-3785-9ffe-7ce817c4fcd8>
0x10f68f000 uuid = <06b9d140-7c31-362c-b86c-fe3d33773bdb>
0x10f6bb000 uuid = <eeb7e56a-c642-3b74-aa0d-daea7a043e65>
0x10f77e000 uuid = <a5d576aa-a2a0-38b5-a3b4-e839ae733b3e>
0x10f795000 uuid = <2903c20e-58f7-3e3f-a080-5ebcaaa102f8>
0x10f7a6000 uuid = <b74c9f33-64e4-31ef-b422-37d35c50ac25>
0x10f7b0000 uuid = <af9b1017-8c31-38f3-ae23-0b87fdc9f2dd>
0x10f7b7000 uuid = <4a459d48-998c-3e09-b411-abccc54409d1>
0x10f7f6000 uuid = <6c0e6cd5-d07b-3ebf-a7ab-c48b3ed75f98>
0x10fe54000 uuid = <54a9f95b-0320-364d-9826-bbe1db6624a6>
0x10f806000 uuid = <e9b666f8-73df-3225-ad91-e783b3552c62>
0x10fe6c000 uuid = <23ac12e6-99f3-30ac-98f5-578e66d3cf45>
0x10fe8e000 uuid = <849d1325-5f9b-34de-9d76-1f27828e8e59>
0x10fe9b000 uuid = <64ae8381-f096-3184-a85c-c50db8d979e6>
0x10fee7000 uuid = <eaf93b13-1432-3ce2-9b58-132858b81fdf>
0x10ff1b000 uuid = <3cffaded-75c9-3dc6-aa97-82bb2e46efe9>
Thread 0 crashed
RAX: 0x0000000000000016, RBX: 0x001ffe2500000001, RCX: 0x000000010f43aeec, RDX: 0x0000000000000000
RSP: 0x00007fff5096ad10, RBP: 0x00007fff5096add0, RSI: 0x00007fff5096ad10, RDI: 0x00000000ffffffff
R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0x00007fff5096ad10, R11: 0x0000000000000202
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x00007f8668c02740, R15: 0x0000000000000005
RFL: 0x0000000000010293, RIP: 0x000000010f4289fa, CS: 0x000000000000002b, SS: 0x0000000000000023
Thread 0: 0xffffff802cf9c4e8
0x000000010f4289fa
0x000000010f2a1534
0x000000010f482515
0x0000000000000001
Thread 1: 0xffffff802cde3288
0x000000010f552bd4
0x000000010f2c45fc
0x000000010f2c3ef8
0x000000010f41c03a
0x000000010f4092e5
0x000000010f41d831
0x000000010f4109e3
0x000000010f40aed1
0x000000010f41f3fe
0x000000010fe57315
0x000000010fe56da9
0x0000000000000000
Thread 2: 0xffffff802c7502b0
0x000000010f7d377a
0x000000010fe56da9
0x0000000000000000
Thread 3: 0xffffff802ce49078
0x000000010f7d377a
0x000000010fe56da9
0x0000000000000000
Thread 4: 0xffffff802ce45df0
0x000000010f7d377a
0x000000010fe56da9
0x0000000000000000
Mac OS version:
17A264c
Kernel version:
Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64
Kernel UUID: 06F94FD7-451F-34A1-B13C-D68FF7EDE0A0
System model name: MacBookPro5,3 (Mac-F22587C8)
Model: MacBookPro5,3, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2,66 GHz, 8 GB, SMC 1.48f2
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 5.0.4f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 PRO 512GB, 512,11 GB
Serial ATA Device: MATSHITADVD-R UJ-868
USB Device: USB 2.0 Bus
USB Device: Card Reader
USB Device: USB 2.0 Bus
USB Device: Built-in iSight
USB Device: UDisk
USB Device: USB Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus:
Last edited:
Here's the issue I'm currently having with the installer... To get to this point, all I've done is restored BaseSystem.dmg to a drive, and copied the Packages folder from InstallESD.dmg into the /System/Installation directory on the drive... OSInstall.mpkg is, of course, there, and it is completely unmodified (this is booted on a supported machine). Anybody have some sort of idea as to what's going on here? An installer log file is attached as well, if that helps.
The latest High Sierra version (linked above) panick'ed on my mbpro 5,3 also...
All Installers are still cooking...
It is quite strange message and the attached log did not give much information too. Maybe the root (/) is not the root of the media. Have you tried creating usb install using createinstallmedia?
sudo /Applications/Install\ macOS\ 10.13\ beta.app/Contents/Resources/createinstallmedia --volume /Volumes/your_volume --applicationpath /Applications/Install\ macOS\ 10.13\ beta.app
I have, and that works just fine, however it results in a read-only root filesystem (it mounts BaseSystem.dmg and InstallESD.dmg at boot), preventing the necessary modifications to get the installer to boot on an unsupported Mac.