Jump to content
1699 posts in this topic

Recommended Posts

@SavageAUS

I've downloaded the beta 7 by ANYMacOS app. Select macOS version >> download (it downloads files into Desktop).

Then, with @chris1111 script you are able to create Install macOS Monterey.app getting the InstallAssitant.pkg file from the downloaded files. 

3 hours ago, Naki said:

I meant this one! You need NO USB media of any kind.

Just download, install and you should get Beta 7. :) 

But some people has had troubles with this file. @chris1111 intends to fix this.

Edited by miliuco
  • Like 2
6 minutes ago, eSaF said:

Hi @chris1111 released create_app-V3.Zip, are you talking about that one being a problem? I was about to test it.

i already try this PKG then without script methode this never work for me

  • Like 1

Went straight from Big Sur to Monterey Beta 7...

 

So far it seems like Monterey is a very minor release... Literally just new wallpapers... (including the beautiful M1 iMac ones which now come by default with the OS...)

And only a few new features...

 

Looks like a Leopard > Snow Leopard / Lion > Mountain Lion / Sierra > High Sierra type of update...

 

I presume we're not getting any more changes on Monterey since we're inching closer to RC, right?

  • Like 1
I just tried a clean install on my Notebook. Here are my experiences so far:
 
1. If SharedSupport.dmg is present in /Volumes/Install macOS Monterey beta/Install macOS Monterey beta.app/Contents/SharedSupport, then the installation fails ("Installer Damaged").
2. If SharedSupport.dmg is instead extracted to Volumes/Install macOS Monterey beta/Install macOS Monterey beta.app/Contents/SharedSupport, then the installer works.
 
But now I have an error, which i have never seen before (couldn't check Firmware Version):
20210924_145346_HDR_(1).thumb.jpg.0cc4edbbbb95c6016d3872efc4eb219c.jpg

I was just testing the USB installer I made and I came across this same error. Switching to iMac17,1 allowed me to move past.


Sent from my iPhone using Tapatalk
  • Like 2
  • Thanks 1

@SavageAUS The issue was that I was using Bootloader Chooser on the Installer stick to easily switch between OpenCore and Clover. But I think it uses an outdated firmware, since it is kinda old. After I put the latest "BOOTx64.efi" back in, installation worked fine. No Securebootmodel, no SMBIOS switching needed.

Edited by 5T33Z0
Just now, antuneddu said:

You can focus on themes again , instead of scripts 😆

Wait full Installer not sure apple FIX it :rofl:

4 minutes ago, miliuco said:

As in beta 8, I had to change SMBIOS from MacPro7,1 to iMac17,1 and revert after update.

Yes for me

  • Like 1
  • Haha 1

All of these “update with no issues” did you have to change smbios? Secure boot settings? Intel or AMD? Clover or OpenCore?
This sort of information really goes a long way.


Sent from my iPhone using Tapatalk

  • Like 1
1 hour ago, eSaF said:

Now that's strange, I didn't have to change from 19.1 to 17.1 for the update as in B7, nothing at all was changed and the update was flawless.

I have the theory that, in many of our hackintosh (which do not really have an Apple T2 chip), these Monterey updates are only shown on Mac models without T2, for example iMac19,1 and older, that's why they are shown also on iMac17,1.
What I do not understand is that this change is only necessary to update because, after updating, the system accepts Mac models that do have T2 (such as MacPro7,1 which is the one I use).
Anyway, it's just an idea.

EDIT: @eSaF I've tried iMac19,1 in other disk and it has worked also.

Edited by miliuco
  • Like 2
Guest
This topic is now closed to further replies.
×
×
  • Create New...