Contribute
Register

Catalina to BigSur upgrade - firmware issue

Status
Not open for further replies.
@Feartech

It was as I expected. I had to kinda "customize" my SMBIOS to get USB-C HDMI to work, I think I did that together with @vettz500. Now, that I disabled this custom SMBIOS and let OC fetch all values just from MacBookPro15,3 - I was able to select the disk.

I will change the SMBIOS back after updating. But this means: No, I don't need SIP (at least this far, let's see how reboot works out), and no, I don't need to run it from internal disk.
 
20201008_232617.jpg


Stuck on this screen after booting from the macOS installer partition. No matter if csr-active-config is at my custom value, or at 0x0. I will try to research this further and hopefully get past it, then I'll post my solution here.
 
When I was installing the beta, formatting as HFS greyed the disk out for me too. I re-formatted in APFS and it worked. I think it's a new version of APFS though. When I boot back into Catalina, it tells me that the BigSur drive is incompatible... (they are both inside the laptop..)
 
hello Feartech,

Today i wanted to modify the config.plist adding -v in the Boot args.
So i did it in NVRAM in 7C436110AB...
Next boot OK i got the verbose mode in order to watch any errors occuring...
But with this very slight mod the Boot process halted!
Maybe you may see some errors i need to fix also...
I already added again the missing kext itlw previously removed...
 

Attachments

  • Boot Error.jpg
    Boot Error.jpg
    3 MB · Views: 42
hello Feartech,

Today i wanted to modify the config.plist adding -v in the Boot args.
So i did it in NVRAM in 7C436110AB...
Next boot OK i got the verbose mode in order to watch any errors occuring...
But with this very slight mod the Boot process halted!
Maybe you may see some errors i need to fix also...
I already added again the missing kext itlw previously removed...
looks like it is missing your kext or the information of the kext in your config.plist
 
OK! but WHY simply adding -v in the NVRAM section was enough to STOP my Boot process?
 
OK! but WHY simply adding -v in the NVRAM section was enough to STOP my Boot process?
not sure, but you didn't upload your efi folder so can't really tell.....
 
OK! but WHY simply adding -v in the NVRAM section was enough to STOP my Boot process?
Perhaps you need to clear NVRAM after making config.plist changes.
 
OK so here is my EFI from Sakoula dedicated to my AIR13 Xiaomi laptop...
I just modified my serial to make it anonymous...
 

Attachments

  • AIR_EFI_Sakoula.zip
    26.2 MB · Views: 35
Status
Not open for further replies.
Back
Top