Jump to content
1176 posts in this topic

Recommended Posts

3 minutes ago, eSaF said:

@ hellojuliomoreira - Although the description of your install is sketchy at best, it is good news if you was abled to install without the aid of a pre-built image, VM, or the aid of a real Mac. If that is indeed the case, I think it is only a matter of time before the Devs get a grip of what is needed for  a straight up installer. Well done on your install. :thumbsup_anim:

 

Sorry man, I feel you. Hahaha

 

Although the post won't paint a clear picture, I think I can add that this was on the course of the previous 24h or more at least, so, it was not as easy as it sounds, but I understand you being skeptical.

 

Appreciate your thoughts still.

  • Like 1
2 minutes ago, hellojuliomoreira said:

 

Sorry man, I feel you. Hahaha

 

Although the post won't paint a clear picture, I think I can add that this was on the course of the previous 24h or more at least, so, it was not as easy as it sounds, but I understand you being skeptical.

 

Appreciate your thoughts still.

 

Another thing to note is that I've installed ON TOP of an existing Catalina fully functional system, so we can say that it was an upgrade not an "vanilla" install per se. I don't know exactly how things change from a technical point of view, but I think it could be helpful in some way...

  • Like 1
11 hours ago, rianosx said:

Hey brothers, i am having some problems to boot macOS Big Sur. i am having a "prohibited symbol" problem. Could you help me?

My hardware: i3 7020U, 8GB RAM DDR4, SSD, OpenCore Bootloader, MacBookPro 14,1 SMBIOS

 

Sorry for the bad English. I'm Brazilian. :)

EFI.zip

 

Please, specific your all important hardware. (Fala irmão, precisa postar todo seu hardware importante, processador, placa mãe, modelo, ssd, placa de vídeo, com detalhes, para o pessoal te ajudar!)

Hi to all,

I'm back and and I installed again macOS Big Sur... restore dmg method, but I have problems my bluetooth is finicky and I don't have sound... anyone knows how to solve this?

My codec is ALC1220-VB and in Catalina I use 7, it is possible that the kext AirportBrcmFixup is useful to solve my bluetooth problems?

Thanks

 

PS: All is solved, I have bluetooth and sound... apparently all works as it should... yesssss...

 

Captura de ecrã 2020-06-29, às 22.55.40.png

Edited by MorenoAv
21 minutes ago, Max.1974 said:

 

Please, specific your all important hardware. (Fala irmão, precisa postar todo seu hardware importante, processador, placa mãe, modelo, ssd, placa de vídeo, com detalhes, para o pessoal te ajudar!)

Thanks :)

My hardware is i3-7020U, 4GB RAM DDR4, OPENCORE, HD GRAPHICS 620, SAMSUNG ESSENTIALS E30, HDD ORIGINAL TOSHIBA, 

I'm having trouble booting big sur, I'm having the problem of still waiting for root device and then the lock symbol.

he also can't find the chip via virtualSMC, which I have no idea what it is. I have a photo here.

basically after these messages, i get the still waiting for root device and the symbol.

 

as far as i know, everything is correct in my efi, including nvram, kexts and plist.

(E obrigado max.1974, sou brasileiro também. Abraços de Salvador!)

 

photo5172779391086864491.jpg

EFI.zip

4 hours ago, mvitanov said:

 

I tried both 5102 and 5119 and I can't see the BigSur volume. Can you share your apfs.efi from the 5102 Clover? Thanks!

For sure! I’ll send it tomorrow night, I’m not home currently.

  • Thanks 1
1 hour ago, Djlild7hina said:

 

You might have to do a DSDT dump and compare the SSDT-Range but yeah most likely different on C422 VS X299.  Talked to slav and found out that the SSDT will not work with AWAC due to already having STA.

So, only find-replace patch ? Or also impossible together with AWAC?

Because probably must be (my OEM DSDT.aml attached).

 

 

DSDT.aml.zip

Edited by yapan4
6 hours ago, tunglamvghy1210 said:

I've got loop boot with many lines "Service exited due to SIGABRT" how to fix it??

 

 

Which step are you at? Have you got the system fully extracted to disk? And can I have context of that log? There might be other useful information several lines above.

 

Loop of lines seems related to apfs_get_firmlink errors near it. Do you install over a existing (fresh installed) Catalina? The stage 2 ramdisk cannot be booted which makes firmlink, so we need existing links made in Catalina.

 

So far, I think you won't have more issues. After this one is solved, you will get the welcome screen at this stage.

 

Edited by Zhen-zen
1 hour ago, rianosx said:

Thanks :)

My hardware is i3-7020U, 4GB RAM DDR4, OPENCORE, HD GRAPHICS 620, SAMSUNG ESSENTIALS E30, HDD ORIGINAL TOSHIBA

I'm having trouble booting big sur, I'm having the problem of still waiting for root device and then the lock symbol.

he also can't find the chip via virtualSMC, which I have no idea what it is. I have a photo here.

basically after these messages, i get the still waiting for root device and the symbol.

 

as far as i know, everything is correct in my efi, including nvram, kexts and plist.

(E obrigado max.1974, sou brasileiro também. Abraços de Salvador!)

 

 

 

Hi @rianosx try this EFI folder, and don't forget reset Nvram. Im not advanced user, so backup your files, and save your OC that was useful in a pendrive.

 

Change for this, and im suppose that you make restore image on your SSD or HD external. Internal not work.

 

God bless you!!!

"Óh meu rei!!" :thumbsup_anim:

EFI-HWH-BA.zip

30 minutes ago, Max.1974 said:

 

Hi @rianosx try this EFI folder, and don't forget reset Nvram. Im not advanced user, so backup your files, and save your OC that was useful in a pendrive.

 

Change for this, and im suppose that you make restore image on your SSD or HD external. Internal not work.

 

God bless you!!!

"Óh meu rei!!" :thumbsup_anim:

EFI-HWH-BA.zip

It even went up a little more, but then it ended up in the same symbol.

  • Sad 1

Big Sur on HP 800 G1 mini

 

Installed  Big Sur from a real Mac (Mac mini) using a USB SSD, mounted the EFI partition and copied my EFI folder. (after many hours of trial and error), install the SSD into my HP 800 G1 mini and the system boots into the desktop, finished user settings. Sleep is working but fans seem to be running fast. all in all seems to be good. I using VooDooHDA for sound. 

 

Thanks to all with the great posts that helped figure out, this is not ready for prime time but its cool to play with...

 

 

Screen Shot 2020-06-28 at 7.21.04 PM.png

Edited by Donw35
  • Like 2
  • Thanks 1
6 hours ago, yapan4 said:

So, only find-replace patch ? Or also impossible together with AWAC?

Because probably must be (my OEM DSDT.aml attached).

 

 

DSDT.aml.zip

 

Do you currently need SSDT-AWAC to boot?  It looks like you're on a patched BIOS but not sure the version numbers on C422.  If you do need SSDT-AWAC, you can just use the find-replace patch. Or, disable SSDT-AWAC and use the SSDT-RTC0-Range.aml (Remove the RTC scope).  

Scope (RTC)
        {
            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                If (_OSI ("Darwin"))
                {
                    Return (Zero)
                }
                Else
                {
                    Return (0x0F)
                }
            }
        }

You don't need the find-replace patch with this.

Edited by Djlild7hina
  • Like 1
11 hours ago, Ivan999 said:

Can anyone help me to make my efi bootable with Big Sur?

I have i5-5200U with Intel HD Graphics 5500

 

 

 

 

EFI.7z

Is this a laptop or a desktop.
Provide more details like if it is a Desktop like MoBo, Wifi Card Model, Network Card model, Processor Speed etc etc. Add those details to your signature it will make things easier for yourself as this gives more insight about your hardware to people trying to help you.

Edited by manmo71
10 hours ago, luki1979 said:

From my understanding OS now boots from snapshot of the system. Making any patches to kexts and replacing system kexts on the fly impossible hence Clover failing immediately. OpenCore is somehow injecting essential third party kexts but when I’ve tried load IO80211Family.kext from Catalina with OC it won’t boot. Instant KP.

What card do you have and did you make it work. I’m interested in this stuff.;)

Broadcomm BCM94352Z on Laptop.

As for WiFi Apple did a brutal thing and removed 3 plugins from IO80211Family.kext that is BCM4360.kext, BCM4331.kext and Atheros one too. AirportBRCMFixup was simply a pointer/patcher kext and its not going to work as there isn’t support inside the BigSur for those cards at all. Maybe they do some workaround in new version. Update Lilu and AirportBrcmFixup and try. But I fear that the only solution is to inject or replace IO80211Family.kext from Catalina.

  • Confused 1
2 minutes ago, luki1979 said:

As for WiFi Apple did a brutal thing and removed 3 plugins from IO80211Family.kext that is BCM4360.kext, BCM4331.kext and Atheros one too. AirportBRCMFixup was simply a pointer/patcher kext and its not going to work as there isn’t support inside the BigSur for those cards at all. Maybe they do some workaround in new version. Update Lilu and AirportBrcmFixup and try. But I fear that the only solution is to inject or replace IO80211Family.kext from Catalina.

Much of the early line of Mac products that are supported by BS have one of those cards. Apple won't drop support for them.

I believe I'm using an BCM4360, Vendor 0x14E4 Device: 0x43A0.

Booting as a MacPro6,1,  wifi and Bluetooth was working. Did not test it, but I saw my bluetooth devices and wifi networks listed.
Booting as an iMac13,2, wifi was working, but bluetooth doesn't show up on system preferences.

I do see AirPortBrcmNIC.kext loaded in Catalina

@Taruga In that case patching should work, I simply observed lack of plugins in the kext. Now only AirPortBrcmNIC.kext is left do do the job. You can check in Hackintool what plugin/kext is loaded in Catalina. If AirPortBrcmNIC.kext is loaded your card should work OTB in Big Sur.

×
×
  • Create New...