Jump to content
1699 posts in this topic

Recommended Posts

50 minutes ago, Matgen84 said:

 

Few month ago, users noticed that the value assigned to csr-active-config had an influence on the appearance of updates. I don't know if it is the same for Monterey.

The same. It is the bit 4. The difference between EF0F and FF0F.

  • Thanks 1

Hi @all

I found a spare hard disk. What is the correct way for this HDD drive: format macOS journaled and Monterey will convert it to APFS. Or format it directly to APFS.

Let me know. Please.

On 6/28/2021 at 7:04 PM, Middleman said:

I have. Try to boot with SecureBoot disabled and use -lilubetaall -wegbeta -no_compat_check. Use EC060800 as the CPUID1Data and use USBInjectAll.kext with XHCIPortLimit enabled. Add the SMC plugins for processor and superio. Vit9696’s Intel I-225V kernel patch and also the FakePCIID Intel I225V needs to be disabled also because it is now natively supported. That could be the cause.

I have made those changes but cannot boot into the OS, not even into Big Sur. 

16 minutes ago, Matgen84 said:

 

For Clover, I use 0x285 as you told me few month ago for Big Sur. Is it correct !

Yes, the bit4==0 so this is correct. I also use this value.

11 minutes ago, Matgen84 said:

Hi @all

I found a spare hard disk. What is the correct way for this HDD drive: format macOS journaled and Monterey will convert it to APFS. Or format it directly to APFS.

Let me know. Please.

No matter. But I prefered macOS journaled. Let Monterey choose right format by itself.

11 minutes ago, hiphopboy said:

my hack checking to software update but have no any update for new beta 2, already install Betaultility, please help me

What is your csr-active-config?

3 minutes ago, miliuco said:

Nothing. Tried OC 0.7.0 and 0.7.1. Csrutil enabled (00000000). Gatekeeper enabled. SecureBootModel=Disabled. No luck.

SMBIOS Model?

  • Like 1
  • Thanks 1
3 minutes ago, Slice said:

Yes, the bit4==0 so this is correct. I also use this value.

No matter. But I prefered macOS journaled. Let Monterey choose right format by itself.

What is your csr-active-config?

SMBIOS Model?

 

My csr-active : 85020000 SMBIOS iMacPro 1.1 2017

8 minutes ago, Hervé said:

Re: SIP, it's the same story as with Big Sur: Apple Internal flag must be left unchanged (i.e. disabled); it's the 5th bit out of the 12 (at time of writing), hence csr-active-config values such as 0xFEF, not 0xFFF.


nible:               #3        |         #2        |         #1     
nibble bits:   4   3   2   1   |   4   3   2   1   |   4   3   2   1
bits:         12  11  10   9   |   8   7   6   5   |   4   3   2   1
               -   -   -   -       -   -   -   -       -   -   -   -
               |   |   |   |       |   |   |   |       |   |   |   |
               |   |   |   |       |   |   |   |       |   |   |   |
               /   |   |   |       |   |   |   |       |   |   |   |
   Unauth. Root    /   |   |       |   |   |   |       |   |   |   |
       Policy Over.    /   |       |   |   |   |       |   |   |   |
              Kext app.    /       |   |   |   |       |   |   |   |
                  Recov. OS        /   |   |   |       |   |   |   \
                     Device Config.    /   |   |       |   |   \    Kext Sig.
                            NVRAM Prot.    /   |       |    \   FS Prot.
                               DTrace Rest.    /       \     Task for PID
                                     Apple Int.         Kernel Debug.

If the flag is set, i.e. Apple Internal enabled, no updates are offered.

 

So what must i do ?

 

37 minutes ago, miliuco said:

Nothing. Tried OC 0.7.0 and 0.7.1. Csrutil enabled (00000000). Gatekeeper enabled. SecureBootModel=Disabled. No luck.

@Slice

SMBIOS MacPro7,1.

 

@eSaF

Added TPM disabled in BIOS and 👍

 

So you know. in my case:

  • TPM disabled in BIOS.
  • Csrutil enabled (00000000).
  • Gatekeeper enabled.
  • SecureBootModel=Disabled in config.plist.

 

Edited by miliuco
  • Like 1
27 minutes ago, miliuco said:

@Slice

SMBIOS MacPro7,1.

 

@eSaF

Added TPM disabled in BIOS and 👍

 

So you know. in my case:

  • TPM disabled in BIOS.
  • Csrutil enabled (00000000).
  • Gatekeeper enabled.
  • SecureBootModel=Disabled in config.plist.

 

 

Thanks :) TPM disabled, do you disable SecureBoot too in BIOS !

Hi all,

like @Hervé

I have that problem with bluetooth since the first beta of Monterey, and I have it still with the new beta, but mine with a Fenvi T-919 card is always disabled, from the boot trough the reboot.

But even in my Big Sur after 11.2.3 bluetooth with the same card is awful, I stopped updating it or I loose bluetooth, even if I remap my USB ports, sometimes it works others it didn't work ...

 

  • Like 1
12 hours ago, miliuco said:

Me too. It seems to be installing beta 2, rebooting, etc., but at the end I stay in beta 1. Tried 2 times.

 

Same for me. I have newest Clover and SIP 0x285. 

 

I have tried to install macOS beta1 again to repair the previous installation, and then run the Beta2 update again, but no luck.

 

Anyone have any ideas how to fix this issue?

11 minutes ago, eSaF said:

That is the reason why a few of us are here trying to find a solution. As a matter of interest what is the chipset platform of your board? You have not populated your profile as per the rules, the reason I ask I see a pattern of success among Laptops and Dell desktops but Z390 boards are proving difficult. Don't know why I am just trying to dissimulate the difference.

 

I have an Intel Z87 motherboard + 4770K CPU and I am using iMac18,3. SMBIOS has been generated using GenSMBIOS (https://github.com/corpnewt/GenSMBIOS).

 

Maybe I should generate another SMBIOS with maybe some Mac Mini or earlier iMac, just to try installing the update?

 

Or maybe I need a clean installation of macOS, I guess could be some problem with an APFS partition, I know there is one partition used for updates. But I want to avoid re-installing if I can.

 
I have an Intel Z87 motherboard + 4770K CPU and I am using iMac18,3. SMBIOS has been generated using GenSMBIOS (https://github.com/corpnewt/GenSMBIOS).
 
Maybe I should generate another SMBIOS with maybe some Mac Mini or earlier iMac, just to try installing the update?
 
Or maybe I need a clean installation of macOS, I guess could be some problem with an APFS partition, I know there is one partition used for updates. But I want to avoid re-installing if I can.

Can you make a separate partition to try a clean install? Then you can see if you can run it before updating your main system. That’s what I’ve done. Monterey is on a separate partition to Big Sur to test and when it’s stable / released I’ll update my main.


Sent from my iPhone using Tapatalk
Guest
This topic is now closed to further replies.
×
×
  • Create New...