macOS High Sierra (10.13) Unsupported Macs Thread

[EugW]

This will probably come across as yet another "me too" post, but I spent some time this weekend installing High Sierra on a freebie Mid-2009 Macbook. Mostly just to see if I could do it.

Not only was I impressed with how easy it was, I'm also blown away with how good the performance is. It lags a little while at startup, but it seems like the longer I use it, the faster it gets. Current versions of most apps seem to outperform their counterparts on my 5,2 iMac running older versions on Snow Leopard. And that's just with the stock hard drive and 2 gigs of RAM. It will be interesting to see how much of a boost it gets from an additional 2 gigs of ram and a nice new SSD.

So far, the only thing I can't get to work is the iSight. The keyboard function keys are all working fine. Brightnes, volumes, iTunes controls all work.

I sure wish I could get this kit running on my iMac. I always thought a 5,2 iMac and a 5,2 Macbook were virtually identical, but I guess not.

Cheers to all who expended efforts to make this work so well. (Donations forthcoming!)

View attachment 763382

I find it difficult to use any recent version of macOS with just 2 GB RAM. And basically impossible to use with 2 GB and hard drive.

4 GB with SSD is a HUGE improvement. HUGE! 8 GB with SSD is even better, but only incrementally so.

 

[macdos]

I find it difficult to use any recent version of macOS with just 2 GB RAM. And basically impossible to use with 2 GB and hard drive.

4 GB with SSD is a HUGE improvement. HUGE! 8 GB with SSD is even better, but only incrementally so.

Incrementally?? My 3,1 has 22 GB installed, and it is really, really tight. Just the loginwindow uses 600 MB. I constantly have to purge cached files so it doesn't start to swap to disk (that is how bad Mac OS memory management is; they should learn from Linux how to do it).

The comfort zone for a Mac lies at 32 GB minimum, better yet 64 or 128 of course.

 

[EugW]

Incrementally?? My 3,1 has 22 GB installed, and it is really, really tight. Just the loginwindow uses 600 MB. I constantly have to purge cached files so it doesn't start to swap to disk (that is how bad Mac OS memory management is; they should learn from Linux how to do it).

The comfort zone for a Mac lies at 32 GB minimum, better yet 64 or 128 of course.

Depends on what you do with it of course. I have 24 GB in my 2017 iMac, and really most of the time I only need 12 GB, with 16 GB sometimes being a bit better. Rarely do I really need 24 GB.

As for that 2/4 GB Mac in question, I was talking about using it as that poster was likely using it. For light usage, 4 GB High Sierra runs just fine. Very occasional beachballs if you only run maybe 2-3 basic applications at a time, like Word, email, and Safari with 2 tabs. 8 GB improves on this, but the improvement is only incremental. The occasional beachballs disappear, and you can add more Safari tabs, but 4 GB is more than usable otherwise if you have SSD.

I say this as someone who currently has 8 GB, 12 GB, 16 GB, and 24 GB Macs, and for many weeks ran High Sierra with just 4 GB. Overall, I'd say for the average relatively light user, 8 GB is actually the sweet spot.

 

[sgtaylor5]

me, too!!!!

Flawless upgrade to High Sierra (I forced cache rebuild just to be careful) from last week’s flawless upgrade to Sierra. [MacBook Pro 5,2 - 17” mid-2009] Most impressed. One observation - let the optimization happen for all of your apps with databases: Spotlight, Mail, Photos, Notes, iMessage.

Oh, SIP /was/ turned off when I installed Sierra last week.

 

[mnsiw]

I'm currently working on a firmware update utility to add native APFS support to unsupported machines, but in order to do so, I need a ROM dump from every unsupported machine. I have most of them, but I do not have the following and will need someone who owns one to dump its ROM:

- MacPro4,1 (NOT upgraded to 5,1 firmware)
- MacBookPro5,3
- MacBook5,1
- Xserve2,1
- Xserve3,1

(I will edit this list as ROMs are received.)

To dump your ROM, simply download and run this application, which is a program I wrote to dump a system's ROM in OS X. Once you've dumped your ROM, send it to me either by attaching it to a post here, or sending it to me via a PM.

-- Before dumping your ROM, please be sure you're running the latest firmware version for your machine. You can verify using the webpage found here.

-- Also note that SIP MUST be disabled in order to dump your ROM.

Thanks!

MacBook 5,1 ROM dump

 

[w1z]

I'm currently working on a firmware update utility to add native APFS support to unsupported machines, but in order to do so, I need a ROM dump from every unsupported machine. I have most of them, but I do not have the following and will need someone who owns one to dump its ROM:

- MacPro4,1 (NOT upgraded to 5,1 firmware)
- MacBookPro5,3
- MacBook5,1
- Xserve2,1
- Xserve3,1

(I will edit this list as ROMs are received.)

To dump your ROM, simply download and run this application, which is a program I wrote to dump a system's ROM in OS X. Once you've dumped your ROM, send it to me either by attaching it to a post here, or sending it to me via a PM.

-- Before dumping your ROM, please be sure you're running the latest firmware version for your machine. You can verify using the webpage found here.

-- Also note that SIP MUST be disabled in order to dump your ROM.

Thanks!

Hi @dosdude1,

I downloaded and executed your APFS ROM patcher tool located here but was not able to boot off the converted APFS volume. I made sure the recently converted volume had the correct default APFS partitions by reinstalling macOS HS 10.13.4 using your HS Patcher but without enabling the APFS boot patch. I also followed the instructions provided by the ROM patcher tool.

I am only able to boot with your APFS HS boot patch - am I missing something? This is on a MacPro3,1

Thank you.

 

[vmirmow]

I'm currently working on a firmware update utility to add native APFS support to unsupported machines, but in order to do so, I need a ROM dump from every unsupported machine. I have most of them, but I do not have the following and will need someone who owns one to dump its ROM:

- MacPro4,1 (NOT upgraded to 5,1 firmware)
- MacBookPro5,3
- MacBook5,1
- Xserve2,1
- Xserve3,1

(I will edit this list as ROMs are received.)

To dump your ROM, simply download and run this application, which is a program I wrote to dump a system's ROM in OS X. Once you've dumped your ROM, send it to me either by attaching it to a post here, or sending it to me via a PM.

-- Before dumping your ROM, please be sure you're running the latest firmware version for your machine. You can verify using the webpage found here.

-- Also note that SIP MUST be disabled in order to dump your ROM.

Thanks!

I'm glad that I can contribute in some little way to this great project, thanks for all you do. MBP 5,3 attached.

Edit: removed ROM dump file after implementation change

 

[dosdude1]

Hi @dosdude1,

I downloaded and executed your APFS ROM patcher tool located here but was not able to boot off the converted APFS volume. I made sure the recently converted volume had the correct default APFS partitions by reinstalling macOS HS 10.13.4 using your HS Patcher but without enabling the APFS boot patch. I also followed the instructions provided by the ROM patcher tool.

I am only able to boot with your APFS HS boot patch - am I missing something? This is on a MacPro3,1

Thank you.

It's not done yet... Can you please use the tool found here to flash your original ROM back on? (it's located in your home folder). Sorry for the inconvenience... I put it in that directory for quick access for testing.

 

[w1z]

It's not done yet... Can you please use the tool found here to flash your original ROM back on? (it's located in your home folder). Sorry for the inconvenience... I put it in that directory for quick access for testing.

No worries mate.. I was just about to say the same after reading your other post on the subject - the patch will be released via patch updater.. Cool!

Will the rom patch remove the APFS boot batch/screen?

Cheers

 

[dosdude1]

No worries mate.. I was just about to say the same after reading your other post on the subject - the patch will be released via patch updater.. Cool!

Will the rom patch remove the APFS boot batch/screen?

Cheers

Yes, it will once I've finished implementing everything.

 

[Stratus Fear]

Hey @dosdude1 just wanted to give you a heads up...was poking around ROM dumps and noticed in GUID FFF12B8D-7696-4C8B-A985-2747075B4F50 (one of the unknown entries at the root of the UEFI tree in UEFITool) there seems to be some level of machine-specific (i.e. private/personal) information stored, like preferred networks, paired BT devices, possibly iCloud data...not sure how you sanitize that, but I thought it would be good to point it out.

 

[dosdude1]

Hey @dosdude1 just wanted to give you a heads up...was poking around ROM dumps and noticed in GUID FFF12B8D-7696-4C8B-A985-2747075B4F50 (one of the unknown entries at the root of the UEFI tree in UEFITool) there seems to be some level of machine-specific (i.e. private/personal) information stored, like preferred networks, paired BT devices, possibly iCloud data...not sure how you sanitize that, but I thought it would be good to point it out.

Yes, I noticed this. I've actually had to completely change the implementation, no longer requiring the ROM dumps (it patches on-the-fly now).

 

[Stratus Fear]

Yes, I noticed this. I've actually had to completely change the implementation, no longer requiring the ROM dumps (it patches on-the-fly now).

This is why you are awesome

 

[dosdude1]

At long last, it is FINISHED! I have just finished writing my tool, which will patch your system firmware to allow native APFS booting. Just download the tool, select "Patch Firmware", and it will do the rest. It will dump your system ROM (and back it up for you), modify it on-the-fly with the APFS components, and flash it back onto your system. Download the tool here.

Disclaimer: As with any firmware flash, there is a slim chance your system could become bricked afterwards if something doesn't go correctly. This application has many safeguards against this, and has been tested thoroughly, but the possibility is still there. With that said, I take no responsibility for a bricked machine as a result of running this tool.

 

[mnsiw]

At long last, it is FINISHED! I have just finished writing my tool, which will patch your system firmware to allow native APFS booting. Just download the tool, select "Patch Firmware", and it will do the rest. It will dump your system ROM (and back it up for you), modify it on-the-fly with the APFS components, and flash it back onto your system. Download the tool here.

Thanks Just patched my MacBook 5,1, now what I have to do to remove EFI script? That script screen still popup on boot/reboot. Will it work if I just delete EFI contents?

 

[Mark1966]

patching mac mini 3,1 lasts in no start any more. after button blinking of hd led and fann starts up. than after some seconds on one shine on hd led and that was it.

Do not knoe why but mac mini is dead for the moment.


KawaZ650b1

 

[mnsiw]

patching mac mini 3,1 lasts in no start any more. after button blinking of hd led and fann starts up. than after some seconds on one shine on hd led and that was it.

Do not knoe why but mac mini is dead for the moment.


KawaZ650b1

After patching I restarted, it freeze on black screen, then I long pressed power button to force shutdown, started gain and it booted, have you tried that?

 

[lostmyshoe123]

Thanks Just patched my MacBook 5,1, now what I have to do to remove EFI script? That script screen still popup on boot/reboot. Will it work if I just delete EFI contents?

Same here on iMac 7.1.

 

[w1z]

At long last, it is FINISHED! I have just finished writing my tool, which will patch your system firmware to allow native APFS booting. Just download the tool, select "Patch Firmware", and it will do the rest. It will dump your system ROM (and back it up for you), modify it on-the-fly with the APFS components, and flash it back onto your system. Download the tool here.

Disclaimer: As with any firmware flash, there is a slim chance your system could become bricked afterwards if something doesn't go correctly. This application has many safeguards against this, and has been tested thoroughly, but the possibility is still there. With that said, I take no responsibility for a bricked machine as a result of running this tool.

View attachment 763810

Flashed with no issues. Just had to mount the EFI boot volume and deleted the folders under /Volume/EFI/EFI then rebooted.

Thanks mate and great work!!

 

[honglong1976]

Using a Macbook Pro Mid 2009
- videos are always playing corrupted
- slow all the time (8GB and SSD)

Thanks for all your hard work but I will go back to Sierra which was great on this laptop

 

[mnsiw]

Same here on iMac 7.1.

Mounted and deleted EFI as @W1SS confirmed it, now it's perfect thanks @dosdude1

 

[Mark1966]

I can not find a firmware restoration cd for mini 3,1 can anybody help me with that.

thanks

 

[w1z]

Hi @dosdude1,

I have some feedback regarding the APFS ROM patch.

I just tried a clean install of HS 10.13.4 with the APFS ROM patch previously applied and verified to boot the old installation with the APFS boot patch applied then deleted, however, I am unable to boot into the clean OS install after the second restart without applying the APFS boot patch - I get a grey screen with a 'slash in a circle' sign.

Does this mean the APFS ROM patch is limited to booting partitions that have had the APFS boot patch applied to previously?

I had to reinstall the OS as the Security/Supplemental 2018-0001 update was failing towards the end of its installation.

Cheers

Edit: I won't proceed with the time machine restoration until I hear back from you just in case you need me to debug something.

Update: Yup, just as I suspected. Without adding the board ID and model to PlatformSupport.plist and no-compat-check kernal flag in the com.apple.boot.plist under /Volumes/Preboot/xxxxxxxxxxxxxxxxxxxxx/..., the OS won't boot. So basically, the APFS boot patch must be applied to boot the OS then deleted afterwards from /Volumes/EFI/EFI unless you implement new logic in your Patch installer based on whether the APFS ROM patch was applied or not (not saying that you should bother with it just pointing it out).

 

[Stratus Fear]

Same here on iMac 7.1.

Just tested, deleted the APFS boot patch from the EFI partition. Boots up seamlessly. Thanks dosdude!

 

[dosdude1]

Hi @dosdude1,

I have some feedback regarding the APFS ROM patch.

I just tried a clean install of HS 10.13.4 with the APFS ROM patch previously applied and verified to boot the old installation with the APFS boot patch applied then deleted, however, I am unable to boot into the clean OS install after the second restart without applying the APFS boot patch - I get a grey screen with a 'slash in a circle' sign.

Does this mean the APFS ROM patch is limited to booting partitions that have had the APFS boot patch applied to previously?

I had to reinstall the OS as the Security/Supplemental 2018-0001 update was failing towards the end of its installation.

Cheers

Edit: I won't proceed with the time machine restoration until I hear back from you just in case you need me to debug something.

Update: Yup, just as I suspected. Without adding the board ID and model to PlatformSupport.plist and no-compat-check kernal flag in the com.apple.boot.plist under /Volumes/Preboot/xxxxxxxxxxxxxxxxxxxxx/..., the OS won't boot. So basically, the APFS boot patch must be applied to boot the OS then deleted afterwards from /Volumes/EFI/EFI unless you implement new logic in your Patch installer based on whether the APFS ROM patch was applied or not (not saying that you should bother with it just pointing it out).

Yes, currently the APFS patch must be applied, as it removes the system compatibility check from the APFS preboot volume. I will be releasing a full patch soon that will perform all the modifications necessary. But for now, just do what others have done: Apply APFS patch even after the FW update, then just delete the EFI boot files in your EFI System Partition to get rid of the old boot method. Or, you can just set your startup disk to the APFS volume in System Preferences.