Jump to content
1699 posts in this topic

Recommended Posts

1 hour ago, SavageAUS said:


From what I’m reading the update should appear, download it, reboot with different smbios, next reboot revert back to proper smbios and continue update. The problem I have is not the downloading or installing but the update not showing up at all.


Sent from my iPhone using Tapatalk
From where?


Sent from my iPhone using Tapatalk

Yes WHERE ????

 

1 minute ago, eSaF said:

Ok let's cut to the basic and the obvious - Insure your Update Setting is as shown to start with.

  Reveal hidden contents

637287164_ScreenShot2021-09-22at13_11_32.png.a1edd1c18df8acc67bbbee4b2b6b38a5.png

 

Certainly is.

I'm going to reboot and clear nvram and try again.

Screen Shot 2021-09-22 at 9.47.18 pm.png

  • Sad 1

Hi @eSaF @ic005k and all users

 

Why SMBIOS Imac17,1 is necessary to update  Beta 7 from Beta 6. Via Clover, I can download it with Imac19,1, but can't install... (loop on macOS Install)

Any ideas ! Please.

I'm either confused or have a problem or both.....

 

based on what I read above, I changed my model to imac17,1 and set SecureBootModel to disable.

Once I rebooted I was able to DL the update.

 

However, once going through the install and rebooting the update never took and it looks to do it again....the loop.

 

So how do I get out of this loop? If I change everything back and rebook, I'm guessing the update won't be available to DL again....

1 hour ago, chris1111 said:

 Geforce 710 support is Gone

 

Ouch. I hope they haven't completely killed Kepler support as I have a 670 on my Monterey hack.

 

I tried the update yesterday but after I got back to the desktop (after what looked like a successful update) the update was still showing up in Software Update. Checking the build on my system I was still on B6.

 

Looking at the update partition the last_update_result.plist gives this as the reason for the update failing: MSU 1140 (EFI ROM does not support large BaseSystems).

 

I'm using MP6,1 SMBIOS here. Not going to change it for a beta update so I'll sit this one out and see if it's a bug or something more significant.

  • Like 1

Hi,

 

Update was not shown on my hack MacBookPro16,2.

I setup OC secure boot config.

ForceSecureBootScheme : YES

DmgLoading : Signed

SecureBootModel j214k

 

 After reboot, update is proposed.

 

SecureBoot, Tpm, Sgx disable in bios.

 

But still Loop reboot after update (see error post before.)

 

Fred

 

Edited by FredWst
53 minutes ago, Riley Freeman said:

 

Ouch. I hope they haven't completely killed Kepler support as I have a 670 on my Monterey hack.

 

I tried the update yesterday but after I got back to the desktop (after what looked like a successful update) the update was still showing up in Software Update. Checking the build on my system I was still on B6.

 

Looking at the update partition the last_update_result.plist gives this as the reason for the update failing: MSU 1140 (EFI ROM does not support large BaseSystems).

 

I'm using MP6,1 SMBIOS here. Not going to change it for a beta update so I'll sit this one out and see if it's a bug or something more significant.

Kepler is Killed

but some patch exist since yesterday

 

 

 

  • Like 1
  • Thanks 2
36 minutes ago, 5T33Z0 said:

 

Arghhhh, I have a GTX 760. How do I apply this patch?

I use my  Kext-Install.app with the patch Binaries files

Install done Reboot 

Test on DELL Optiplex 790 Sandy bridge system i5 2500K UEFI booting OpenCore 0.7.3  Works well :rofl:

1453711347_ScreenShot.png.18e05e94a5da4b38fd1e80a60ffaf7b4.png

  • Like 5
  • Thanks 2
4 hours ago, ic005k said:

Set "SystemProductName" to iMac17, 1, and change it back to your own model after the update is complete.

Wow this worked man! The only thing i changed was the "SystemProductName" to iMac17,1 and the update went thru. No messing with SecureBoot Model needed.

 

Anyone can explain why iMac17,1?

6 minutes ago, chris1111 said:

I use my  Kext-Install.app with the patch Binaries files

Install done Reboot 

Test on DELL Optiplex 790 Sandy bridge system i5 2500K UEFI booting OpenCore 0.7.3  Works well :rofl:

1453711347_ScreenShot.png.18e05e94a5da4b38fd1e80a60ffaf7b4.png

 

So you do ths in post via screen sharing or how?

Or before the install?

Hi @all

Using Clover, I can download the new Beta. But SMBIOS Imac17,1 failed for my Z390, to update Beta 7. I don't know why 😪

So I want to remove "macOS Install Data" folder. I find 3 strange folder in System/Volumes/Monterey

  • macOS Install Data (11,7Go) --->2021-07-06
  • Previous Content (256,6Mo) ----> 2021-09-05 (Probably from previous   Beta !)
  • Boot folder. (283,2Mo) ---> 2021-09-15.   With  a lot of .im4m files and the X86_64SURamdisk.dmg
Spoiler

177341744_Capturedcran2021-09-2218_34_51.png.9db3c62cc24faabd5eab4c54238285bd.png

 

 

Spoiler

1718400754_Capturedcran2021-09-2218_44_12.png.44323c52df2d0b24011e15f2b38540de.png

 

 

 

macOS Install Data folder this normal, but the date is incorrect (the version too I suppose). Does anyone have an idea on these files/folders, it is the first time that I notice their presence except macOS Install Data folder of course.

Edited by Matgen84
  • Thanks 1
  • Sad 1
47 minutes ago, 5T33Z0 said:

 

So you do ths in post via screen sharing or how?

Or before the install?

After Update B7 I use my app 

I will make a  new page on github today

  • Like 4
  • Thanks 1
3 hours ago, Riley Freeman said:

 

Ouch. I hope they haven't completely killed Kepler support as I have a 670 on my Monterey hack.

 

I tried the update yesterday but after I got back to the desktop (after what looked like a successful update) the update was still showing up in Software Update. Checking the build on my system I was still on B6.

 

Looking at the update partition the last_update_result.plist gives this as the reason for the update failing: MSU 1140 (EFI ROM does not support large BaseSystems).

 

I'm using MP6,1 SMBIOS here. Not going to change it for a beta update so I'll sit this one out and see if it's a bug or something more significant.

 

 

With last OC build b7 update successfully hack iMac18,3.

 

Error -> "EFI ROM does not support large BaseSystems" as gone

 

Fred

  • Like 2
1 minute ago, FredWst said:

With last OC build b7 update successfully hack iMac18,3.

 

Error -> "EFI ROM does not support large BaseSystems" as gone

 

Fred

 

Thanks Fred! I only run the release builds so I'm still on 0.7.3.

 

The drop of Kepler support is a bigger issue now. I'll check out the Kepler patch along with the next official OC release but this might be where I call it quits with Monterey and go back to something earlier.

  • Like 1

@vit9696

 

Hack MacBookPro16,2 with Secure boot set in config.plist ApECID=0 and secureBootModel=j214k

I got update b7 proposed to update.

But got this error below. OC bug or bad config.plist ?

 

1516381872_Capturedcran2021-09-2219_41_52.png.83241618efcd2d91bf74a512b3e824e1.png 

 

Edit: update ok change -> secureBootModel to Disabled and back to j214k

 

Fred

 

 

Edited by FredWst
update ok change -> secureBootModel to Disabled and back to j214k
6 minutes ago, meaganmargaret said:

 

 

Well even after downloading the full installer as listed by @antuneddu, I got the same error.  Must be my old Z370.....

 

Have you launched the app or created the usb?
Because if I launch the app it seems to work

366196555_Schermata2021-09-22alle22_37_39.png.c6d8adc4e8c96e4ec732a8800ca5d31d.png 

 

but if I try to create the usb it says that the installer is not valid

674546193_Schermata2021-09-22alle22_34_39.png.3ad4f1dc91d6aaf1dbc071b99f8a7dda.png

 

TINU app 

365835601_Schermata2021-09-22alle22_35_59.png.b6d837e4b24d3c830364c9ad389748b6.png

 

I'm wrong, or the installer has some problem ... I downloaded it 2 times 🤔

  • Like 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...