Won't boot to install. Few questions.

[AndrzejL-eu]

Hi @jtaczanowski,

I've followed your guide to a letter.

I have checked BIOS options - they are correct on both of my X201 machines.

I've generated and added the platform info for MacBookPro11,1 using GenSMBIOS and modified the config file using the 4 values as requested using ProperTree

Created USB installation media and made sure its in legacy boot mode

Mounted the EFI partition and copied the EFI folder (not just content of the folder) to it

This is what I am getting just before reboot.

Both machines - same info - and reboot right after this. Not getting to the "Apple Logo" stage.

Is this because BigSur 117 has issues with the XhciPortLimit being broken resulting in boot loop? That's possible BUT I've used another pendrive and created a Catalina installation media and used your files. Same result. Catalina is in 10.x version so I don't see how could the 11.3+ problem occur. Unless I misunderstand.

Is it possible that I have issues because I have i5 not i7 cpu?

What else could cause a behaviour like this?

Should I make more changes to the config file other than the 4 you listed?

Any other BIOS options I should be looking out for?

Do I need a specific version of OC? I downloaded everything fresh yesterday so I was using "latest / greatest" packages.

Kindest regards.

Andrzej

[AndrzejL-eu]

Few updates:

I have seen you @jtaczanowski asking another user for a boot video:

https://www.youtube.com/watch?v=Bt5hO20jP_g

Using different brand of pendrive OR different USB ports does nothing.

Enabling the Kernel > Quirks > XhciPortLimit entry in your config.plist does nothing.

Here are 2 boot time log files from the pendrive.

opencore-2022-10-04-104409.txt opencore-2022-10-04-104550.txt

Edit. Monterey pendrive created - same exact thing. Frustration is real ;-)...

Kindest regards.

Andrzej

[AndrzejL-eu]

Last login: Tue Oct  4 22:17:30 on ttys000
andrzejl@Andrzejs-Mac-mini ~ % /Users/andrzejl/Downloads/X201/OpenCore/Utilities/ocvalidate/ocvalidate /Users/andrzejl/Downloads/X201/ThinkPad-X201-Arrandale-macOS-OpenCore-main/EFI/OC/config.plist

NOTE: This version of ocvalidate is only compatible with OpenCore version 0.8.4!

OCS: No schema for Block at 0 index, context <Emulate>!
OCS: Missing key Block, context <Kernel>!
OCS: No schema for AllowNvramReset at 0 index, context <Security>!
OCS: No schema for AllowToggleSip at 2 index, context <Security>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: Missing key FullNvramAccess, context <Tools>!
OCS: No schema for LegacyEnable at 2 index, context <NVRAM>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
OCS: Missing key LoadEarly, context <Drivers>!
Serialisation returns 34 errors!

Kernel->Scheme->KernelArch is borked (Can only be Auto, i386, i386-user32, or x86_64)!
CheckKernel returns 1 error!

OpenCanopy.efi is loaded at UEFI->Drivers, but Misc->Boot->PickerMode is not set to External!
CheckMisc returns 1 error!

UEFI->Input->KeySupport should be enabled when Ps2KeyboardDxe.efi is in use!
OpenUsbKbDxe.efi at UEFI->Drivers[11], and Ps2KeyboardDxe.efi at UEFI->Drivers[12], should NEVER co-exist!
CheckUefi returns 2 errors!

Completed validating /Users/andrzejl/Downloads/X201/ThinkPad-X201-Arrandale-macOS-OpenCore-main/EFI/OC/config.plist in 2 ms. Found 38 issues requiring attention.
andrzejl@Andrzejs-Mac-mini ~ % 

[jtaczanowski]

Hi @AndrzejL-eu, Could you try to disable (set to false) loading patched DSDT.aml file and see if it will boot? https://github.com/jtaczanowski/ThinkPad-X201-Arrandale-macOS-OpenCore/blob/main/EFI/OC/config.plist#L21

This DSDT.aml is a whole file dumped and patched from x201 with i7 CPU. I suppose that maybe i5 version has different DSDT.

The correct way to patching the DSDT is to include only patches in OC directory -not the whole DSDT which maybe specified for one particular machine. I included whole DSDT file witch applied patches beacuse from what I remember I had problems to get it working with including only patches.

Patched DSDT is needed for working battery indicator and working cpu power management.

[jamesfawcett]

Hi @jtaczanowski

I've done some digging!

I went right back through every EFI version I have on bitbucket, right back to early versions of Clover - I always seem to have that DSDT. I keep copies on dropbox too, and found in my very very old notes a link to this guide: https://osxlatitude.com/forums/topic/10136-short-guide-install-high-sierra-on-lenovo-x201-i5-520m/?_fromLogin=1

Looking at the files though, it DOES include a patched DSDT in his files:

Looking at the original DSDT patcher's X201 specs, he built this for an i5 X201 - so it rules out this being an i5/l7 issue I think?

[AndrzejL-eu]

Hi @AndrzejL-eu, Could you try to disable (set to false) loading patched DSDT.aml file and see if it will boot? https://github.com/jtaczanowski/ThinkPad-X201-Arrandale-macOS-OpenCore/blob/main/EFI/OC/config.plist#L21

This DSDT.aml is a whole file dumped and patched from x201 with i7 CPU. I suppose that maybe i5 version has different DSDT.

The correct way to patching the DSDT is to include only patches in OC directory -not the whole DSDT which maybe specified for one particular machine. I included whole DSDT file witch applied patches beacuse from what I remember I had problems to get it working with including only patches.

Patched DSDT is needed for working battery indicator and working cpu power management.

Hi @jtaczanowski I did as suggested. I went to proppertree and set the DDST.aml to false

<key>ACPI</key>
<dict>
    <key>Add</key>
    <array>
        <dict>
            <key>Comment</key>
            <string>DSDT.aml</string>
            <key>Enabled</key>
            <False/>
            <key>Path</key>
            <string>DSDT.aml</string>
        </dict>

That's the only .aml file that I am to disable right?

Unfortunately that did not help.

I believe that since your machine is running i7 there must be a different board (newer) involved. Maybe this is the difference...

I believe one of mine is running 520M the other is running 560M.

Kindest regards.

Andrzej

[jamesfawcett]

@AndrzejL-eu how did you find the 560M/520M? I have three different i7 X201's here, I had trouble getting one of them to with a working booting Big Sur SSD from another - I can check the CPU on that?

[AndrzejL-eu]

Hi @jtaczanowski

I've done some digging!

I went right back through every EFI version I have on bitbucket, right back to early versions of Clover - I always seem to have that DSDT. I keep copies on dropbox too, and found in my very very old notes a link to this guide: https://osxlatitude.com/forums/topic/10136-short-guide-install-high-sierra-on-lenovo-x201-i5-520m/?_fromLogin=1

Looking at the files though, it DOES include a patched DSDT in his files:

Looking at the original DSDT patcher's X201 specs, he built this for an i5 X201 - so it rules out this being an i5/l7 issue I think?

I believe you might be right @jamesfawcett as disabling the .aml file from loading does not fix the issue on the Monterey installing pendrive.

Kindest regards.

Andrzej

[jamesfawcett]

Hi @AndrzejL-eu

I just checked the bios on two of my machines, both are 620. I will compare the bios settings on both to see if there are any differences.

[AndrzejL-eu]

@AndrzejL-eu how did you find the 560M/520M? I have three different i7 X201's here, I had trouble getting one of them to with a working booting Big Sur SSD from another - I can check the CPU on that?

I have a friend who used to work for this company in county Limerick - the company was upgrading the hardware so he was told he can liberate few machines. I bought 5 of them. Gave away 3 to family kept 2 for wifey and myself.

Please do check and I will check the fix on the other X201.

Ooops - I was mistaken. Both of my i5s are 560M

Both do exactly the same thing.

Kindest regards.

Andrzej

[AndrzejL-eu]

Hi @AndrzejL-eu

I just checked the bios on two of my machines, both are 620. I will compare the bios settings on both to see if there are any differences.

Thanking you @jamesfawcett 😃

Andrzej

[jtaczanowski]

Hi @jamesfawcett, Thank you for your findings :) You mentioned that you have three x201 machines and one of them has problems with booting. What CPU model has this problematic machine? I think that i7 version has the same board as the i5 version.

I attaching my bootlog - I can see some differences between our logs @AndrzejL-eu. opencore-2022-10-05-183111.txt

I'll think about where the problem may be.

Regards, Jan

[AndrzejL-eu]

Hi @jamesfawcett, Thank you for your findings :) You mentioned that you have three x201 machines and one of them has problems with booting. What CPU model has this problematic machine? I think that i7 version has the same board as the i5 version.

I attaching my bootlog - I can see some differences between our logs @AndrzejL-eu. opencore-2022-10-05-183111.txt

I'll think about where the problem may be.

Regards, Jan

@jtaczanowski @jamesfawcett Thanks guys - I really appreciate your help. I've tried Hackintoshing these 2 in the past. No joy. I only recently returned to the subject because your GH projects gave me hope so... I HOPE this will take us on a journey to somewhere interesting 😃

Kindest regards.

Andrzej

[AndrzejL-eu]

Hi @jamesfawcett, Thank you for your findings :) You mentioned that you have three x201 machines and one of them has problems with booting. What CPU model has this problematic machine? I think that i7 version has the same board as the i5 version.

I attaching my bootlog - I can see some differences between our logs @AndrzejL-eu. opencore-2022-10-05-183111.txt

I'll think about where the problem may be.

Regards, Jan

@jtaczanowski

You 11:678 00:005 AAPL: #[EB|VERSION] <"boot.efi 540.120.3~19 (Official), built 2022-06-17T21:09:01-0700">

Me: 18:541 00:069 AAPL: #[EB|VERSION] <"bootbase.efi 495.140.2~49 (Official), built 2022-08-29T05:08:23-0700">

Also this -btlfxallowanyaddr does not show up on mine...

Interesting...

Andrzej

[jtaczanowski]

btlfxallowanyaddr showing up because i am trying get bluetooth working on Monterey.

I zipped my whole EFI partition with new spoofless approach via vmm (https://github.com/dortania/OpenCore-Legacy-Patcher/issues/543). Using this approach allows to run OTA updates without changing model and run macOS installer or install updates with working CPU power management. In free time I will commit this changes to this repo.

@AndrzejL-eu You can extract this zip on your EFI partition and try with Monterey or Bigsur (currently I'm on Monterey) - maybe somehow it will work :) I left the serial numbers and everything other written in the config.plist - so don't need to generate them.

https://taczanowski.net/download/backup_8_0_with_spoofless_via_vmm.zip

[AndrzejL-eu]

btlfxallowanyaddr showing up because i am trying get bluetooth working on Monterey.

I zipped my whole EFI partition with new spoofless approach via vmm (dortania/OpenCore-Legacy-Patcher#543). Using this approach allows to run OTA updates without changing model and run macOS installer or install updates with working CPU power management. In free time I will commit this changes to this repo.

@AndrzejL-eu You can extract this zip on your EFI partition and try with Monterey or Bigsur (currently I'm on Monterey) - maybe somehow it will work :) I left the serial numbers and everything other written in the config.plist - so don't need to generate them.

https://taczanowski.net/download/backup_8_0_with_spoofless_via_vmm.zip

Hi @jtaczanowski

I grabbed my Monterey pendrive, plugged it in, mounted EFI partition, removed the boot file and the EFI folder, opened your zip file and copied the content to the EFI partition, unmounted EFI partition unplugged pendrive and plugged it in the X201. Booted. Same behaviour as before on both.

opencore-2022-10-06-083614.txt

opencore-2022-10-06-093822.txt

There's the boot.efi and bootbase.efi difference again - not sure why and also just at the end:

You: 14:894 00:007 AAPL: #[EB|RH:MF] <"usr\\standalone\\OS.dmg.root_hash.x86legacyap.im4m">
14:903 00:009 AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash"> <"0">
>>>>> 14:912 00:008 AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash.x86legacyap.im4m"> <"0">
14:921 00:009 AAPL: #[EB.BST.FBS|RHPSZ] 229
14:927 00:005 AAPL: #[EB.BST.FBS|RHMSZ] 3627
14:936 00:009 AAPL: #[EB|LOG:DT] 2022-10-05T18:31:26
14:947 00:010 AAPL: #[EB|LOG:EXITBS:START] 2022-10-05T18:31:26

Me: 44:579 00:086 AAPL: #[EB|RH:MF] <"usr\\standalone\\OS.dmg.root_hash.x86legacyap.im4m">
44:664 00:085 AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash"> <"0">
>>>>> 44:751 00:086 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"usr\\standalone\\OS.dmg.root_hash">
44:838 00:087 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
44:923 00:085 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
45:325 00:401 AAPL: #[EB|LOG:DT] 2022-10-06T08:37:00
45:412 00:086 AAPL: #[EB|LOG:EXITBS:START] 2022-10-06T08:37:00

Something must be different between our machines...

Which USB port are you using? The one on the left just below the fan grill?

Kindest regards.

Andrzej

[AndrzejL-eu]

I am wondering if the i5 has a different graphics then i7... I mean yeah I am pretty sure its a cpu / apu difference that's messing me up...

Kindest regards.

Andrzej

[jtaczanowski]

Installer is working for me on all USB ports and even on SD card reader.

i5-560m and i7-620m are very similar processors. i7 version only have slightly higher turbo boost clock and more L3 cache. I'm pretty sure that the processors has the same graphics cards. What's more - even original Macbooks Pro came with i5-520M, i5-540M, i5-560M, i7-620m CPUs

Regards, Jan

[AndrzejL-eu]

Installer is working for me on all USB ports and even on SD card reader.

i5-560m and i7-620m are very similar processors. i7 version only have slightly higher turbo boost clock and more L3 cache. I'm pretty sure that the processors has the same graphics cards. What's more - even original Macbooks Pro came with i5-520M, i5-540M, i5-560M, i7-620m CPUs

Regards, Jan

I am at a loss then… What am I doing wrong? Bios setting? @jtaczanowski

Kindest regards

Andrzej

[AndrzejL-eu]

Ok, so I've tried using earlier version of opencore mentioned here:

https://github.com/jtaczanowski/ThinkPad-X201-Arrandale-macOS-OpenCore/issues/1

Did not help.

I also tried this method of creating a bootable pendrive with MacOS installer:

https://youtu.be/l_QPLl81GrY?t=430

I created Catalina USB - no go.

So I've decided to bring in a bigger crowd and started a post on reddit.

Maybe some of these guys will have an idea... I don't know. I am grasping at straws here...

Nevermind. /r/Hackintosh mod removed my post because they do not allow premade EFIs...

Before he removed it someone replied with "invalidflexratio" I need to research it.

Cheers.

Andrzej

[jamesfawcett]

@AndrzejL-eu sorry I've not been much help this week, I work freelance and have been overbooked.

If you have a Catalina USB set up, you can try my old Clover EFI from here: https://github.com/jamesfawcett/Thinkpad-X201-Hackintosh-Catalina

I was actually using that machine daily with that config, then @jtaczanowski contributed to that repo and got graphic acceleration working too.

Later in the week I'm going to start from scratch and see how far I can get with mine starting again with @jtaczanowski 's opencore - which OS are you trying to install? I have bootable USB for Big Sur, Ventura and Monterey

[AndrzejL-eu]

@AndrzejL-eu sorry I've not been much help this week, I work freelance and have been overbooked.

If you have a Catalina USB set up, you can try my old Clover EFI from here: https://github.com/jamesfawcett/Thinkpad-X201-Hackintosh-Catalina

I was actually using that machine daily with that config, then @jtaczanowski contributed to that repo and got graphic acceleration working too.

Later in the week I'm going to start from scratch and see how far I can get with mine starting again with @jtaczanowski 's opencore - which OS are you trying to install? I have bootable USB for Big Sur, Ventura and Monterey

No stress @jamesfawcett. I will have a look.

Before they shutdown my reddit post someone replied with "invalidflexratio" I will have to research it.

Thanks Bud.

Andrzej

[AndrzejL-eu]

OK... Here are my findings.

The last time I was trying to Hackintosh this lappy I ran into an issue. Laptop would reboot after End RandomSeed and a lot of +++++++++++.

Now that I have searched for the "invalidflexratio" I did not get a lot of results BUT:

https://github.com/chris1111/OpenCore-Desktop-Guide/blob/master/troubleshooting/troubleshooting.md#stuck-on-endrandomseed

One of the listed items is:

IgnoreInvalidFlexRatio missing, this is needed for Broadwell and older. Not for AMD and Skylake or newer

BUT when I looked into the config.plist - its there. Toggled True? So I am guessing that's not it...

Cheers.

Andrzej

[AndrzejL-eu]

Disabling IgnoreInvalidFlexRatio changes nothing. Adding UEFI > Quirks > InvalidFlexRatio as boolean set to true give me Unknown Schema information. I am starting to think that my boot pendrives are somehow messed up and that the boot partition cannot reach the "installer" partition or file...

Cheers.

Andrzej

[AndrzejL-eu]

If you have a Catalina USB set up, you can try my old Clover EFI from here: https://github.com/jamesfawcett/Thinkpad-X201-Hackintosh-Catalina

I was actually using that machine daily with that config, then @jtaczanowski contributed to that repo and got graphic acceleration working too.

Just a side note I might be cursed @jamesfawcett - your method fails too...

https://www.youtube.com/watch?v=3sIweca8Aj4

Yes I know its unrelated to @jtaczanowski project... but IT may throw more light on my no boot issue...

Cheers.

Andrzej

[jamesfawcett]

That's interesting @AndrzejL-eu ! Video is still processing so I can't view it yet. Are you making your USB stick with createinstallmedia?

[AndrzejL-eu]

That's interesting @AndrzejL-eu ! Video is still processing so I can't view it yet. Are you making your USB stick with createinstallmedia?

The video is up now but still in 360p so wait a bit @jamesfawcett.

I created it like you said using DosDude1 patcher. Today.

Cheers.

Andrzej

[jamesfawcett]

Hi @AndrzejL-eu

I've come to a conclusion, I think it's the installer.

From my testing:

Installing Ventura @jtaczanowski 's EFI - NO My working EFI - NO Your EFI - NO

Installing Monterey @jtaczanowski 's EFI - NO (I get exact same error as you) My working EFI - NO (I get exact same error as you) Your EFI - NO (I get exact same error as you)

Installing Big Sur I wasn't able to test this, when making the bootable USB I kept getting "Library not loaded: @executable_path/../Frameworks/IAESD.framework/" - apparently its common when trying to make older USB's on a later OS

Installing Catalina @jtaczanowski 's EFI - YES My working EFI - YES Your EFI - YES

Do you have access to Catalina USB? Once you install Catalina, you should then be able to upgrade within the OS (I did and I think @jtaczanowski did this too)

[AndrzejL-eu]

Hi @AndrzejL-eu

I've come to a conclusion, I think it's the installer.

From my testing:

Installing Ventura @jtaczanowski 's EFI - NO My working EFI - NO Your EFI - NO

Installing Monterey @jtaczanowski 's EFI - NO (I get exact same error as you) My working EFI - NO (I get exact same error as you) Your EFI - NO (I get exact same error as you)

Installing Big Sur I wasn't able to test this, when making the bootable USB I kept getting "Library not loaded: @executable_path/../Frameworks/IAESD.framework/" - apparently its common when trying to make older USB's on a later OS

Installing Catalina @jtaczanowski 's EFI - YES My working EFI - YES Your EFI - YES

Do you have access to Catalina USB? Once you install Catalina, you should then be able to upgrade within the OS (I did and I think @jtaczanowski did this too)

Which method did you use when creating Catalina usb? DosDude1 patcher + clover or the official opencore way @jamesfawcett?

Cheers Bud

[jamesfawcett]

@AndrzejL-eu I used the following command on my desktop Hackintosh to create the bootable USB:

sudo /Volumes/BACKUP2TB/Downloads/SOFTWARE\ -\ OS\ no-backup/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Catalina

Then I put the EFI folders into a separate USB stick I already ran the Opencore legacy trick on to make them bootable, except for your Clover EFI I downloaded, for this I used a different USB stick and ran the clover installer with "EFI files in the ESP" checked, then I copied over your EFI.

If it helps I can create a disk image of the USB stick? Sorry I know this isn't the best solution either, I've not actually fixed installing Monterey directly.

[AndrzejL-eu]

@AndrzejL-eu I used the following command on my desktop Hackintosh to create the bootable USB:

sudo /Volumes/BACKUP2TB/Downloads/SOFTWARE\ -\ OS\ no-backup/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Catalina

Then I put the EFI folders into a separate USB stick I already ran the Opencore legacy trick on to make them bootable, except for your Clover EFI I downloaded, for this I used a different USB stick and ran the clover installer with "EFI files in the ESP" checked, then I copied over your EFI.

If it helps I can create a disk image of the USB stick? Sorry I know this isn't the best solution either, I've not actually fixed installing Monterey directly.

Nah Dude you did great. I will try it myself first and yes when you have time get the image file ready I might need it 😜.

Cheers.

Andrzej

[jtaczanowski]

Hi @jamesfawcett Thank you for your tests with different installers :)

I'm very surprised that only Catalina installer is working which, by the way, I have never used with my opencore. I used Catalina only with your Clover bootloader.

Once you install Catalina, you should then be able to upgrade within the OS (I did and I think @jtaczanowski did this too)

I did not update in this way.

I used successfully in the past my opencore with Big Sur and Monterey installers - although the last time with an older version Monterey installer - maybe 12.3, after that I was only installing upgrades without full installation with installer. I'll try to prepare Monterey 12.6 installer and check if I can boot it as older installers. I will check and let you know :)

[AndrzejL-eu]

Hey @jamesfawcett @jtaczanowski thank you for your help.

I am cursed. Nothing works for me.

I have formatted a pendrive. 2GB of Fat partition and used:

sudo ~/Downloads/OpenCore/Utilities/legacyBoot/BootInstall_X64.tool

To get it legacy booted.

I copied Jan’s EFI folder onto that pendrive. The one shared above. The one that worked for James.

I then created a pendrive using the Catalina image downloaded by the DosDude1 patcher (I had that one on hand) using this command:

sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

So now I have 2 pendrives.

Plugged them into the Thinkpad and booted from the 2gb one. Used external keyboard to get the Installer started.

Just like previously - it reboots.

Then I tried:

mkdir -p ~/macOS-installer && cd ~/macOS-installer && curl https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py > installinstallmacos.py && sudo python installinstallmacos.py

To download this file:

17 001-68446 10.15.7 19H15 2020-11-11 macOS Catalina

Created boot USB using this image.

sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

Plugged them into the Thinkpad and booted from the 2gb one. Used external keyboard to get the Installer started.

Just like previously - it reboots.

Anyway. The fight continues but not today. Need to step away because frustration is real and I will blow the gasket...

Kindest regards.

Andrzej

[AndrzejL-eu]

Hi @jamesfawcett Thank you for your tests with different installers :)

I'm very surprised that only Catalina installer is working which, by the way, I have never used with my opencore. I used Catalina only with your Clover bootloader.

Once you install Catalina, you should then be able to upgrade within the OS (I did and I think @jtaczanowski did this too)

I did not update in this way.

I used successfully in the past my opencore with Big Sur and Monterey installers - although the last time with an older version Monterey installer - maybe 12.3, after that I was only installing upgrades without full installation with installer. I'll try to prepare Monterey 12.6 installer and check if I can boot it as older installers. I will check and let you know :)

You both are a stars guys. Thank you for your help. I appreciate both of you.

Kindest regards.

Andrzej

Edit... OH Damn... I confused my X201 with the Dell lappy that had a socket with removable CPU... On X201 its soldered on so no replacing it unless I will replace the whole motherboard... Ah well. At least its now running nice and cool with clean fan and Noctua re-greased CPU...

[AndrzejL-eu]

Trying again with

2 061-86291 10.15.3 19D2064 2020-03-23 macOS Catalina

Maybe old version will work...

[AndrzejL-eu]

Trying again with

2 061-86291 10.15.3 19D2064 2020-03-23 macOS Catalina

Maybe old version will work...

opencore-2022-10-12-223128.txt

And reboot.

[jtaczanowski]

I have checked if I can boot latest Monterey installer with my opencore - it is working without problem. Weird :| I have no idea why on my computer it is working and on other not.

I have disabled trackpoint in Bios - but I don't think it matters.

I created fresh Monterey installer with opencore legacy patcher (option "Create macOS installer") on my pendrive. I did not install opencore and create mbr on that pendrive - I just boot my laptop from internal SSD drive (with opencore and mbr installed) and select macOS Installer form opencore picker. But it also doesn't matter - in the past I was able to create pendrive with macOS installer and opencore on EFI partition and mbr on that pendrive - it was also boot without problem...

[AndrzejL-eu]

I have checked if I can boot latest Monterey installer with my opencore - it is working without problem. Weird :| I have no idea why on my computer it is working and on other not.

I have disabled trackpoint in Bios - but I don't think it matters.

I created fresh Monterey installer with opencore legacy patcher (option "Create macOS installer") on my pendrive. I did not install opencore and create mbr on that pendrive - I just boot my laptop from internal SSD drive (with opencore and mbr installed) and select macOS Installer form opencore picker. But it also doesn't matter - in the past I was able to create pendrive with macOS installer and opencore on EFI partition and mbr on that pendrive - it was also boot without problem...

You're making me saddo :-P @jtaczanowski

[AndrzejL-eu]

Hey guys,

Could it be a one stupid BIOS setting? I mean I don't know which one but..

[AndrzejL-eu]

BIOS defaults reset. Nothing changed... I even disabled trackpoint lik @jtaczanowski mentioned. I am cursed.

[AndrzejL-eu]

Is there a way to enable more debug info in logs?

[jtaczanowski]

Hi @AndrzejL-eu currently I have no new ideas what could be the problem. It seems that it is possible to get more logs - https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html

[AndrzejL-eu]

Hi @AndrzejL-eu currently I have no new ideas what could be the problem. It seems that it is possible to get more logs - https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/debug.html

I've been looking at this yes.

Its very frustrating. I will probably make a video of the entire process that I use to get into the point of failure. Maybe I do something wrong. Wouldn't be the first time. I would LOVE to get it going but at the moment I am stepping away for a while because this thing has raised my already high blood pressure ;-).

[AndrzejL-eu]

https://www.youtube.com/watch?v=Lj3lI9SWV4g

opencore-2022-10-21-180642.txt

OC Validator.pdf

Latest update.

Cheers.

Andrzej

[Scorpionchiques]

@AndrzejL-eu Hi, did you fix your boot problem. I have t510i with i7-640m and nvidia quardo, and rebooing on boot too with same logs :(

[AndrzejL-eu]

@AndrzejL-eu Hi, did you fix your boot problem. I have t510i with i7-640m and nvidia quardo, and rebooing on boot too with same logs :(

Sadly no...

[Scorpionchiques]

@AndrzejL-eu Hi, did you fix your boot problem. I have t510i with i7-640m and nvidia quardo, and rebooing on boot too with same logs :(

Sadly no...

Do your x201 have nvidia gpus? I thought my problem was nvidia until i read your post..

[AndrzejL-eu]

@AndrzejL-eu Hi, did you fix your boot problem. I have t510i with i7-640m and nvidia quardo, and rebooing on boot too with same logs :(

Sadly no...

Do your x201 have nvidia gpus? I thought my problem was nvidia until i read your post..

Early intel GPU. Sorry bud. I wish I could help more.

[Scorpionchiques]

@AndrzejL-eu I think we are somehow preparing the legacy bootloader incorrectly

[AndrzejL-eu]

@AndrzejL-eu I think we are somehow preparing the legacy bootloader incorrectly

https://www.youtube.com/watch?v=eLSzLESxOfo

See if you can spot the issue... 2 Js and myself couldn't...

[Scorpionchiques]

@AndrzejL-eu I think we are somehow preparing the legacy bootloader incorrectly

https://www.youtube.com/watch?v=eLSzLESxOfo

See if you can spot the issue... 2 Js and myself couldn't...

Do your x201 have optical drive? I swapped that to hdd, maybe this produce issues?