macOS High Sierra (10.13) Unsupported Macs Thread

[L Caputo]

Thanks for pointing that out.
I must have grabbed the wrong screen-shot, anyhow I corrected my original post.

So if you updated from PB2 to PB3, did you do it via the App Store, and if so how did you do it.
I have got the update in the App Store and can download it and when the restart happens I get the installation screen saying 17 minutes but almost immediately after it just reboots and I'm still on PB2.

 

[nekton1]

Ask Czo and he will send you a link

 

[nekton1]

I downloaded dosdude's High Sierra patcher as a zip file but it would not unarchive with macOS unarchiver. Pacifist was able to extract the file successfully and it works on a 10.13 beta 4 full install download from Apple (5.12 GB).

Use the Patcher Option menu to ignore the High Sierra version.

 

[RogueB]

I downloaded dosdude's High Sierra patcher as a zip file but it would not unarchive with macOS unarchiver. Pacifist was able to extract the file successfully a4nd it works on a 10.13 beta 4 full install download from Apple (5.12 GB).

Use the Patcher Option menu to ignore the High Sierra version.

How were you able to get full installer for developer beta 4 ? Getting it [full installer] seems to require an "oblique," mysterious, pathway (?)

Thanks
[doublepost=1501141949][/doublepost]

Well fortunatly my wife has a MacBook air that is suported, and thats how I downloaded HS beta 2...

Ah, a "familial" connection ... I have an iMac (late 2012) which can run High Sierra; that's my source.
Thanks for response
[doublepost=1501142127][/doublepost]

Are you using AFPS?

No, I am still on HFS+. If I followed foxlet's background information correctly, it is not possible to convert to AFSP when installing from a flash drive.

 

[nekton1]

How were you able to get full installer for developer beta 4 ? Getting it [full installer] seems to require an "oblique," mysterious, pathway (?)

Thanks
[doublepost=1501141949][/doublepost]

Ah, a "familial" connection ... I have an iMac (late 2012) which can run High Sierra; that's my source.
Thanks for response
[doublepost=1501142127][/doublepost]

No, I am still on HFS+. If I followed foxlet's background information correctly, it is not possible to convert to AFSP when installing from a flash drive.

[doublepost=1501145979][/doublepost]Developer

 

[roysterdoyster]

So if you updated from PB2 to PB3, did you do it via the App Store, and if so how did you do it.
I have got the update in the App Store and can download it and when the restart happens I get the installation screen saying 17 minutes but almost immediately after it just reboots and I'm still on PB2.

Since you are on an unsupported machine, the update shows, downloads, but suddenly stops installing midways. After restart, you are still stuck with your previous macOS.

Found two sources where to obtain working betas from:
1) French site Zoneactu: https://www.zoneactu.fr/category/apple/mac/os-x-beta
Beta installer is packed into a .zip archive. Unpack, select, hit cmd-I for a check of the installer version (hint: dev beta 3 installer is at version 13.0.40 , dev beta 4 is version 13.0.45). Proceed with dosdude1's patcher, which is easy as 1-2-3.

2) if you prefer torrent/magnet link: http://mac-torrent-download.net/?s=macos+10.13&x=25&y=12

Mods/admin please delete, if torrents are off limits. I checked FAQs for rules, couldn't find anything on torrents.

cheers

 

[L Caputo]

Since you are on an unsupported machine, the update shows, downloads, but suddenly stops installing midways. After restart, you are still stuck with your previous macOS.

Found two sources where to obtain working betas from:
1) French site Zoneactu: https://www.zoneactu.fr/category/apple/mac/os-x-beta
Beta installer is packed into a .zip archive. Unpack, select, hit cmd-I for a check of the installer version (hint: dev beta 3 installer is at version 13.0.40 , dev beta 4 is version 13.0.45). Proceed with dosdude1's patcher, which is easy as 1-2-3.

2) if you prefer torrent/magnet link: http://mac-torrent-download.net/?s=macos+10.13&x=25&y=12

Mods/admin please delete, if torrents are off limits. I checked FAQs for rules, couldn't find anything on torrents.

cheers

Hi thanks, I already used the French site to install PB1, and then install PB2, both were full installers.
So when the update to PB 3 announced itself in the App Store I downloaded from there but as I have found out it at the installation stage it detects this is an unsupported Mac and therefore boots back into PB2. So my question is how is it possible to get updates via the App Store and not have to download a full installer again.
After all I am running Sierra also and can do OS updates through the App Store.

 

[RogueB]

[doublepost=1501145979][/doublepost]Developer

I am a registered Apple developer. What one can download, at least in the US, are "split" packages, not a full installer. The only full installer that was available for download from apple developer site, was for the original 10.13.
Perhaps geographical location affects the type of download one can receive(?) Interesting ...
Thanks for responding.

 

[Tanith]

I also have a Mac mini 2009 with updated wifi card I'll give a try too when I get a chance!

Can you give a positive feedback here?

 

[roysterdoyster]

Hi thanks, I already used the French site to install PB1, and then install PB2, both were full installers.
So when the update to PB 3 announced itself in the App Store I downloaded from there but as I have found out it at the installation stage it detects this is an unsupported Mac and therefore boots back into PB2. So my question is how is it possible to get updates via the App Store and not have to download a full installer again.
After all I am running Sierra also and can do OS updates through the App Store.

In fact, the updates showing up in your App store/Updates section download to the root/Library/Updates/ folder on your unsupported machine as .pkg files. These however need be wrapped into an installer, which can be done, obviously, by the productbuild command. I lack in-depth expertise here. that being said, the experienced fellow member Czo posted details in post #367 on his working on solving the update via app Store issue. He actually said he was looking for members willing to test his solution on their respective unsupported machines.

cheers mate

 

[Luigi222]

Can you give a positive feedback here?

Hi there, I’ve been away from my mac’s due to medical issues, sorry haven’t had the chance to test it out...

 

[L Caputo]

In fact, the updates showing up in your App store/Updates section download to the root/Library/Updates/ folder on your unsupported machine as .pkg files. These however need be wrapped into an installer, which can be done, obviously, by the productbuild command. I lack in-depth expertise here. that being said, the experienced fellow member Czo posted details in post #367 on his working on solving the update via app Store issue. He actually said he was looking for members willing to test his solution on their respective unsupported machines.

cheers mate

Hi
Yes I'm aware that the files get downloaded to the Updates folder, and I have tried to follow the instructions on using productbuild but have had no success there either. I hav command line tools downloaded but not sure whether I need to have Xcode installed.

 

[nekton1]

Putting Czo SUVMMFaker.dylib in the correct place in your file system should enable trouble-free upgrades on MAS for unsupported Macs—that is its purpose I believe.

 

[L Caputo]

Putting Czo SUVMMFaker.dylib in the correct place in your file system should enable trouble-free upgrades on MAS for unsupported Macs—that is its purpose I believe.

Yes so I have heard but where can I get this file, I don't see any links here to download it.

 

[MacManMatt]

I would also like to try Czo's method.

If anyone has a link to the SUVMMFaker.dylib and its location would be good.

 

[nekton1]

I would also like to try Czo's method.

If anyone has a link to the SUVMMFaker.dylib and its location would be good.

[doublepost=1501230833][/doublepost]As I said in a previous post, ask Czo in a private conversation on this forum.
[doublepost=1501231286][/doublepost]

I am a registered Apple developer. What one can download, at least in the US, are "split" packages, not a full installer. The only full installer that was available for download from apple developer site, was for the original 10.13.
Perhaps geographical location affects the type of download one can receive(?) Interesting ...
Thanks for responding.

The full 10.13 beta 4 installer about 5 GB can be downloaded if you are a registered developer.
Mine was from macappstores://itunes.apple.com/app/id1209167288

Paste this URL into Safari—see the last two lines on the displayed page. You must either be enrolled in the beta program or must be an apple developer.

 

[Czo]

I would also like to try Czo's method.

If anyone has a link to the SUVMMFaker.dylib and its location would be good.

I have a working patch for App Store and i can send it to anyone, but for the installation some terminal expirience is required (currently it is in a beta testing phase, i want to wait one more beta release before i release it). Send me a PM and i can send back the file and the instruction.

Users must be enable beta updates to make the patch working!

 

[RogueB]

[doublepost=1501230833][/doublepost]As I said in a previous post, ask Czo in a private conversation on this forum.
[doublepost=1501231286][/doublepost]


The full 10.13 beta 4 installer about 5 GB can be downloaded if you are a registered developer.
Mine was from macappstores://itunes.apple.com/app/id1209167288

Paste this URL into Safari—see the last two lines on the displayed page. You must either be enrolled in the beta program or must be an apple developer.

Thanks for response, and the link.
Belatedly, I realized why I could not download the Beta4 full-installer from apple's developer site (to an eligible iMac).

The culprit was a copy of the original 10.13 installer, which I have left on the desktop of the iMac, after patching a copy of the 10.13 for installation on (ineligible) late 2009 MacBook Pro. Each time I tried to download Beta4, I was greeted with an auto-installer icon offering to instal the 10.13 copy (the one on my desktop). Deleting the full 10.13.0 installer from the desktop, allowed full Beta4 installer download, without triggering an automatic instal process.

Not sure if it is was a result of inadvertent bug on part of apple installer, or a pointed message to the "installer," not to mack with things unless attention to detail is exercised. In my defense, the iMac 27 " has a big screen, and that old installer icon looked really insignificant against the backdrop ... (?)

 

[nandor690]

Not really sure what changed in the latest beta builds but for some reason it messes with my clover install method. Now for some reason after the first reboot it boots to a black screen and stays there. I found that macOS High Sierra will put a firmware file in the EFI partition of the iMac I am using in smbios to spoof it. IE, if I'm using a 13,1 iMac smbios, there will be a 13,1 firmware file on the EFI partition. If I remove the hard drive and put it in my hackintosh and mount the EFI partition and then delete the Apple folder and then put it back in my unsupported iMac it will boot fine. But won't complete the install because of the same problem(macOS installer will put the firmware file back) once it reboots. BUT, if I finish the install on my hackintosh it will finish the complete install and then delete the Apple Folder again then put it back in my unsupported iMac and use a smbios with all my 7,1 info it will boot fine using AFPS file system. Which is weird because I am using the same smbios for the hack as I am using to spoof the 7,1.
So my hurdle right now is figuring out how to stop it from doing that.
any suggestions?

EDIT: What if I add the firmware files for a 7,1 iMac to the EFIPayloads folder inside the FirmwareUpdate.pkg? But how do I get full read/write access to the installer. Iv tried a bunch of different ways to get access but I can't.

EDIT2: Or could I simply remove them from the installer?

 

[robert1998]

Guys, I'm sorry I gonna ask but if you have unsupported macs why are you trying to run all the betas and facing all the struggle?
Why you don't wait for the final release/ GM and try to install that on your macs?

 

[nandor690]

Guys, I'm sorry I gonna ask but if you have unsupported macs why are you trying to run all the betas and facing all the struggle?
Why you don't wait for the final release/ GM and try to install that on your macs?

Whats the fun in that hahahahahahahaha

 

[retiarius]

Greetings from one who earlier reported on the infamous trackpad problem for my 2.0GHz MacBook5,1 and also wondering how another contributor could report success for a 2.4GHz version, when the basic difference is only the CPU speed and a backlit keyboard.

Only now, after running the dosdude1 patcher on 10.13 Public Beta #3, the problem is resolved (see attached screenshot). Except, since more than one thing changed, I'm not sure what fixed this, i.e. PB3 itself with new drivers perhaps, or the way I ran the patcher, or the effect of the presence/non-presence of "parrotgeek's" USB kext injection.

What I did was to regenerate a new USB stick w/17A315i, thence apply to a previous install of PB2/dosdude1 patcher (i.e. not "clean"), but I neglected *this time* to run 'postinstall' which I usually do by habit. The patched PB3 ran full course without seeing the "flashing folder" and it restarted fine, so I didn't run postinstall at all. The screenshot also shows System > Software > Extensions > LegacyUSBInjector "Not Loaded" so maybe it was just getting in the way earlier instead of helping. Happy for now.

 

[Czo]

The LegacyUSBInjector.kext is not a real kext. It's a kext without a binary part (because of it, it's status never could be "loaded"). It's only a description file that informs OS X about the available USB ports, thier power limits, etc. Without this, all of the ports are unpowered and you can't use any built-in usb device (iSight, Keyboard, Trackpad, Bluetooth, IR Receiver).

 

[RogueB]

Greetings from one who earlier reported on the infamous trackpad problem for my 2.0GHz MacBook5,1 and also wondering how another contributor could report success for a 2.4GHz version, when the basic difference is only the CPU speed and a backlit keyboard.

Only now, after running the dosdude1 patcher on 10.13 Public Beta #3, the problem is resolved (see attached screenshot). Except, since more than one thing changed, I'm not sure what fixed this, i.e. PB3 itself with new drivers perhaps, or the way I ran the patcher, or the effect of the presence/non-presence of "parrotgeek's" USB kext injection.

What I did was to regenerate a new USB stick w/17A315i, thence apply to a previous install of PB2/dosdude1 patcher (i.e. not "clean"), but I neglected *this time* to run 'postinstall' which I usually do by habit. The patched PB3 ran full course without seeing the "flashing folder" and it restarted fine, so I didn't run postinstall at all. The screenshot also shows System > Software > Extensions > LegacyUSBInjector "Not Loaded" so maybe it was just getting in the way earlier instead of helping. Happy for now.

I just installed the High Sierra beta4 on a MacBookPro 5,2 using dosdude1's patcher. I did run the post install patcher as a matter of routine, and my trackpad control panel is also fully operational. Since I did not try to boot straight into beta4 updated system, the way you did, I am not sure what would have happened had I not run the post install patcher.

Given the same result, whether post patcher was used or not, it is possible, that some subtle changes in Beta4 resulted in restoring the preferences for track pad (?) It does not eliminate probability, that once used, dosdude1's patcher persist in the library despite upgrades. Only a clean install, one with dosdued's patch, and one without its use, could provide the answer.
[doublepost=1501392028][/doublepost]

Greetings from one who earlier reported on the infamous trackpad problem for my 2.0GHz MacBook5,1 and also wondering how another contributor could report success for a 2.4GHz version, when the basic difference is only the CPU speed and a backlit keyboard.

[doublepost=1501392871][/doublepost]

The LegacyUSBInjector.kext is not a real kext. It's a kext without a binary part (because of it, it's status never could be "loaded"). It's only a description file that informs OS X about the available USB ports, thier power limits, etc. Without this, all of the ports are unpowered and you can't use any built-in usb device (iSight, Keyboard, Trackpad, Bluetooth, IR Receiver).

I posted a reply to retiarius, just missing your entry. Your explanation seems to point to apple-generated changes in beta4 (?)

 

[dendkmac]

Fun battle tonight considering the disk utility is broken in High Sierra...had to go back to a older vm to create...