SOLVED TOSHIBA Dynabook Cannot install any OS newer than Catalina.

[EliteMacx86]

Updating this thread because of newer developments. Removing the solved tag as well due to a new problem preventing completion of Mac installation.

The SN740 arrived just a few hrs earlier and I did a mirror copy of the Chinese drive's Catalina build on it. It's actually blazing fast, even faster than the Chinese drive. Everything runs perfectly, but I found the need to upgrade to a newer Mac OS as I can't install some of the apps that I need (Slack, to name one). The problem right now is that, I can't seem to upgrade to a newer version of Mac OS newer than Catalina as it always get stuck at 12 minutes remaining, with the errors that I saw after "Syncing disk data" being "unable to get data from (wherever the target drive is)" then it ends up with "prune orphaned unlock records failed with error: Error Domain=com.apple.OpenDirectory Code=10000 Operation is not supported by the directory node". No matter what version I try/use, it always end up like that. Be it Big Sur, Monterey, or Ventura, it's all the same.

Did you try a clean install instead of cloning the disk and then updating it?

I remade the whole config.plist from scratch and changed the SMBIOS to MacBookPro15,4, set the SecureBootModel to Default, and fixed my boot-args by removing the hyphen before the alcid argument. I also made sure to erase the drive in each attempts, reset NVRAM in each attempts, and tried force-restarting the laptop whenever it gets stuck at that error, and it always ends up not showing an installed OS despite data being written in there as seen in Disk Utility.

You must NOT reset NVRAM after the first phase or simply during the install stage. Only, before booting the installer.

What macOS version are you trying to install?

I've been dealing with this for the last 4 hours and I'm actually lost and unsure how to proceed with this. I need it running any of the newer MacOS so that I can use my needed apps with it, otherwise I really have no use for the OS and would rather go back to Windows.

Well, that's your choice! You need to decide.

Is there any information that I might've missed regarding installing/booting Big Sur and newer Mac OS?

Attach the complete EFI to check!

 

[takoriin]

Did you try a clean install instead of cloning the disk and then updating it?


You must NOT reset NVRAM after the first phase or simply during the install stage. Only, before booting the installer.

What macOS version are you trying to install?


Well, that's your choice! You need to decide.


Attach the complete EFI to check!

Yes, I did try to do a clean install of Big Sur first, then once it failed, I did try Monterey, Ventura, and Sonoma in hopes that trying each would change something.

As for resetting NVRAM, I had no idea to be honest. I only reset that whenever I do a clean install first but I don't do that after the first phase passes through. Thank you for clarifying.

Right now, I'm trying to get Sonoma working on this after I saw some users being able to run it with older chips, so I thought it'd be worth a shot. I've also noticed that there's not much of a difference between Ventura and that save for a few settings, and the video didn't have much specific changes indicated for Sonoma except for the SMBIOS.

I already sank weeks into this so just throwing the towel at this point isn't going to do it justice. However, at least I know that my laptop can run Catalina. That's a good start.

I just need to know what I'm missing out on running any macOS newer than that, especially Sonoma so that I can have it running the latest macOS and for me not to have issues with app compatibility unlike in Catalina.

Here's my complete EFI attached, thank you for being patient with me on this.

 

[EliteMacx86]

Yes, I did try to do a clean install of Big Sur first, then once it failed, I did try Monterey, Ventura, and Sonoma in hopes that trying each would change something.

As for resetting NVRAM, I had no idea to be honest. I only reset that whenever I do a clean install first but I don't do that after the first phase passes through. Thank you for clarifying.

Right now, I'm trying to get Sonoma working on this after I saw some users being able to run it with older chips, so I thought it'd be worth a shot. I've also noticed that there's not much of a difference between Ventura and that save for a few settings, and the video didn't have much specific changes indicated for Sonoma except for the SMBIOS.

I already sank weeks into this so just throwing the towel at this point isn't going to do it justice. However, at least I know that my laptop can run Catalina. That's a good start.

I just need to know what I'm missing out on running any macOS newer than that, especially Sonoma so that I can have it running the latest macOS and for me not to have issues with app compatibility unlike in Catalina.

Here's my complete EFI attached, thank you for being patient with me on this.

Remove SMCBatteryManager.kext

One should not use it before patching the ACPI.

Set SecureBootModel to Disabled. Its required for macOS Sonoma (14.5) and later.

Try MacBookPro15,1 and then check.

Also, post a picture where you exactly tend to have issue. Ensure that the OC is latest and the kexts as well.

 

[takoriin]

Remove SMCBatteryManager.kext

One should not use it before patching the ACPI.

Set SecureBootModel to Disabled. Its required for macOS Sonoma (14.5) and later.

Try MacBookPro15,1 and then check.

Also, post a picture where you exactly tend to have issue. Ensure that the OC is latest and the kexts as well.

Got it, will try all these now. Thank you!

Prior to these changes, this is what I’ve been getting from installing anything newer than Catalina, even in Sonoma. It’s the exact same error with the EFI that I just provided in the earlier post.

 

[takoriin]

Done with the trial and it’s just weird that this time my system just chose to hang when the setup’s on “Syncing extracted to disk”, making me unable to intercept any errors that came after it. Tried hitting Caps Lock and it’s definitely unresponsive. I’m actually scared of restarting it as it might brick my new drive.

Attaching the image showing where I’m currently stuck at.

 

[EliteMacx86]

Done with the trial and it’s just weird that this time my system just chose to hang when the setup’s on “Syncing extracted to disk”, making me unable to intercept any errors that came after it. Tried hitting Caps Lock and it’s definitely unresponsive. I’m actually scared of restarting it as it might brick my new drive.

Attaching the image showing where I’m currently stuck at.

This phase takes a while. Select Show all Logs and then provide a picture. If its not responding, wait for like 10mins and restart. When at OC, provide a picture.

 

[takoriin]

This phase takes a while. Select Show all Logs and then provide a picture. If its not responding, wait for like 10mins and restart. When at OC, provide a picture.

Got it, will try again. I already restarted 20 mins after my last reply above since the setup has been stuck in there for more than that already, and tried reinstalling it once more. I enabled Show All Logs just a while ago before it completely froze with no response from pressing Caps Lock. Here’s what I got.

 

[EliteMacx86]

Got it, will try again.

TIP: When you perform a clean install, always, select the main disk (not partition), fully erase it in APFS, GUID and then attempt to install on the target disk.

 

[takoriin]

Will do that right now. The setup has since then stalled on me. Might be worth the shot.

 

[takoriin]

I did exactly as you said and it did progress beyond that error. I think that it made a difference. However, I did observe something weird with the logs this time. It immediately crashed my system and froze the screen to this. Please advise.