Montelli Posted November 23, 2022 Author Share Posted November 23, 2022 (edited) 22 hours ago, antuneddu said: 🙈 https://drive.google.com/file/d/1f67-O0cb_hcTfrAZmLOSto8bKgTazsWT/view?usp=sharing after you edited the plist... double check with the validator I did, is everything correct? I attach the screens clover validator gives me out this: Edited November 23, 2022 by Montelli Link to comment Share on other sites More sharing options...
Antonuccio Posted November 23, 2022 Share Posted November 23, 2022 Link to comment Share on other sites More sharing options...
Montelli Posted November 24, 2022 Author Share Posted November 24, 2022 (edited) ok perfect: now I copied my CLOVER> ACPI> patched folder to the new Clover and included the one mentioned by Slice the kext I left only those present in the clover 5150 folder and I configured Booter and Kernel Quirks with updated cloverconfigurator I double checked the plist with clovervalidator and it's all Ok I chose my USB Uefi, I entered in clover, but when I start macos high sierra it hangs at the apple without a bar and without anything else: I wait your response, Thank you Edited November 24, 2022 by Montelli 1 Link to comment Share on other sites More sharing options...
Slice Posted November 24, 2022 Share Posted November 24, 2022 1 hour ago, Montelli said: ok perfect: now I copied my CLOVER> ACPI> patched folder to the new Clover and included the one mentioned by Slice the kext I left only those present in the clover 5150 folder and I configured Booter and Kernel Quirks with updated cloverconfigurator I double checked the plist with clovervalidator and it's all Ok I chose my USB Uefi, I entered in clover, but when I start macos high sierra it hangs at the apple without a bar and without anything else: I wait your response, Thank you Next step is to produce boot log. Set in config Boot->Debug=true and try to boot the system. It will be very slow, wait 10 minutes and then look into /EFI/CLOVER/misc. There should be new ***.log file. Upload it here for me to look. Link to comment Share on other sites More sharing options...
Montelli Posted November 26, 2022 Author Share Posted November 26, 2022 (edited) attached the log file thank you BOOTX64.EFI.log Edited November 26, 2022 by Montelli Link to comment Share on other sites More sharing options...
Slice Posted November 28, 2022 Share Posted November 28, 2022 On 11/26/2022 at 3:25 PM, Montelli said: attached the log file thank you BOOTX64.EFI.log 82.62 kB · 3 downloads I can propose that the hang at fix usb ownership because you have external ASMedia USB3 controller. Try to switch off USB handoff in BIOS if possible. Or switch off FixOwnership in config.plist but then you will encounter a stop at "waiting for root...". Try to insert your USB stick into USB2 port on motherboard not into ASMedia. The better way if your EFI folder will be in internal SATA drive then booting process will not depend on USB. If not help then wait until I will prepare a clover version doing no FixOwnership on ASmedia controller. Link to comment Share on other sites More sharing options...
Montelli Posted November 28, 2022 Author Share Posted November 28, 2022 as you can imagine I had inserted a 3.0 pendrive in a 3.0 usb port in front of the case... now I used a 2.0 pendrive directly in the 2.0 usb port of the motherboard and unfortunately it did not boot anyway ... I attach the .log file Thank you 2022-11-28_18-49_BOOTX64.EFI.log Link to comment Share on other sites More sharing options...
Slice Posted November 29, 2022 Share Posted November 29, 2022 10 hours ago, Montelli said: as you can imagine I had inserted a 3.0 pendrive in a 3.0 usb port in front of the case... now I used a 2.0 pendrive directly in the 2.0 usb port of the motherboard and unfortunately it did not boot anyway ... I attach the .log file Thank you 2022-11-28_18-49_BOOTX64.EFI.log 84.01 kB · 1 download Same. Be ready to test new Clover. Link to comment Share on other sites More sharing options...
Slice Posted November 29, 2022 Share Posted November 29, 2022 Test, please. Replace this file and make a copy cp /EFI/CLOVER/CLOVERX64.EFI /EFI/BOOT/BOOTX64.EFI on your EFI partition You should see ++++++++ on the screen and may be successful boot to system. CLOVERX64.efi.zip Link to comment Share on other sites More sharing options...
Montelli Posted November 30, 2022 Author Share Posted November 30, 2022 kind slice, I extracted this zip file, and replaced CLOVERX64 in EFI/CLOVER/CLOVERX64.EFI but in the zip there was only that and I didn't find a bootx64 file to replace in efi/boot/bootx64.efi... however I booted from usb 2.0 but unfortunately the system didn't boot I attach the .log file I wait your response thank you 2022-11-30_17-48_BOOTX64.EFI.log Link to comment Share on other sites More sharing options...
Slice Posted December 1, 2022 Share Posted December 1, 2022 12 hours ago, Montelli said: kind slice, I extracted this zip file, and replaced CLOVERX64 in EFI/CLOVER/CLOVERX64.EFI but in the zip there was only that and I didn't find a bootx64 file to replace in efi/boot/bootx64.efi... however I booted from usb 2.0 but unfortunately the system didn't boot I attach the .log file I wait your response thank you 2022-11-30_17-48_BOOTX64.EFI.log 84.21 kB · 1 download Expected... No, no, no.... Make a copy of the file CLOVERX64.efi. There will be second file. Rename it to BOOTX64.EFI. Copy it to your bootable EFI replacing existing BOOTX64.EFI. Link to comment Share on other sites More sharing options...
Montelli Posted December 1, 2022 Author Share Posted December 1, 2022 Ok sorry for delay, now I copied the same file you put above, into /EFI/CLOVER/CLOVERX64.EFI and the same into /EFI/BOOT/BOOTX64 but here renaming it to BOOTX64 but unfortunately the system didn't boot I attach the log file Thank you ps. the time day of pc is wrong but i just did it now 2022-11-30_19-07_BOOTX64.EFI.log Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2022 Share Posted December 2, 2022 11 hours ago, Montelli said: Ok sorry for delay, now I copied the same file you put above, into /EFI/CLOVER/CLOVERX64.EFI and the same into /EFI/BOOT/BOOTX64 but here renaming it to BOOTX64 but unfortunately the system didn't boot I attach the log file Thank you ps. the time day of pc is wrong but i just did it now 2022-11-30_19-07_BOOTX64.EFI.log 84.38 kB · 0 downloads But I see wrong commit 0:110 0:000 Starting Clover revision: 5150 (master, commit ee4d7a61b) on American Megatrends EFI It must be at least 4a3b16 or even ff1681ad It means you booted not same Clover as I upload for you. Link to comment Share on other sites More sharing options...
Montelli Posted December 2, 2022 Author Share Posted December 2, 2022 I did it again and attached there is video and log file video https://drive.google.com/file/d/1eFH0sNKnvG23CcH3t3LjgAPWrH-je4Jq/view?usp=sharing 2022-12-02_11-12_BOOTX64.EFI.log Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2022 Share Posted December 2, 2022 1 hour ago, Montelli said: I did it again and attached there is video and log file video https://drive.google.com/file/d/1eFH0sNKnvG23CcH3t3LjgAPWrH-je4Jq/view?usp=sharing 2022-12-02_11-12_BOOTX64.EFI.log 83.94 kB · 0 downloads Your video shows correct action but I see wrong revision again 0:107 0:000 Starting Clover revision: 5150 (master, commit ee4d7a61b) on American Megatrends EFI I will upload to you new version at the evening. Anyway try to switch off XHCI handoff (or something similar) in BIOS. Link to comment Share on other sites More sharing options...
Slice Posted December 2, 2022 Share Posted December 2, 2022 Try again CLOVERX64.efi.zip Link to comment Share on other sites More sharing options...
bronxteck Posted December 2, 2022 Share Posted December 2, 2022 sometimes in older bios if you boot from usb the bios still uses the internal efi path to boot. it will start from usb but then switch path during boot process. try only using internal efi. back up existing internal to usb in case. 1 Link to comment Share on other sites More sharing options...
deeveedee Posted December 2, 2022 Share Posted December 2, 2022 Definitely agree with @bronxteck . I had this problem with my Dell Latitude E6410. I ended up abandoning use of a bootable USB and had to do all of my EFI debugging by editing EFI on the SSD. Since my Dell Latitude E6410 has an aux bay, I was able to have a backup EFI on the SSD in the aux bay which saved me when I screwed up the EFI in my primary drive bay. Link to comment Share on other sites More sharing options...
Montelli Posted December 3, 2022 Author Share Posted December 3, 2022 (edited) it didn't boot and I attach log file, but in the meantime I looked in bios for XHCI handoff but I didn't find it, at least I think... I attach bios screen where can I disable XHCI? 2022-12-03_18-05_BOOTX64.EFI.log Edited December 3, 2022 by Montelli Link to comment Share on other sites More sharing options...
Montelli Posted December 3, 2022 Author Share Posted December 3, 2022 and I add that I have dualboot but windows is on ssd and macos is on nvme, so two separate Link to comment Share on other sites More sharing options...
Antonuccio Posted December 3, 2022 Share Posted December 3, 2022 Since you also have Windows installed Try copying the new EFI directly to the disk's EFI partition (nvme) (backup your working one... So as to restore it from Win if it doesn't boot from the disk either Link to comment Share on other sites More sharing options...
Montelli Posted December 3, 2022 Author Share Posted December 3, 2022 but efi folder and macos are in nvme and cloover boot in eufi from nvme... Anyway...but if it doesn't boot from internal efi how do I access the efi folder again? I would however try disabling the XHCI handoff first Link to comment Share on other sites More sharing options...
Antonuccio Posted December 3, 2022 Share Posted December 3, 2022 You can mount the EFI partition (in case of problems) from windows with MiniTool Partition Wizard... just assign a drive letter... and navigate with Explorer++ (as Admin) to navigate, replace the EFI folder 1 Link to comment Share on other sites More sharing options...
Slice Posted December 3, 2022 Share Posted December 3, 2022 25 minutes ago, Montelli said: but efi folder and macos are in nvme and cloover boot in eufi from nvme... Anyway...but if it doesn't boot from internal efi how do I access the efi folder again? I would however try disabling the XHCI handoff first Try to switch off "Legacy USB support". I see in your log good Clover version but you started HighSierra? 142:095 0:113 GetOSVersion: 10.13.5 (17F77) Is it too old for such hardware? Also try temporary disable some kexts except Lilu+VirtualSMC. I can also propose use one kext FakeSMC instead. Link to comment Share on other sites More sharing options...
Montelli Posted December 5, 2022 Author Share Posted December 5, 2022 (edited) the version I have is high sierra 10.13.5 and I thought I'd give it other try, I took the efi folder that I use for high sierra and put it in the usb and so it boot... at this point I think there is something wrong with the new cloover? because with the usb it actually starts if I use the high sierra efi... in all this I disabled the Legacy USB support and tried again with the new cloover but it didn't boot... I attach the log file 2022-12-05_11-22_BOOTX64.EFI.log to disable kexts, just leave VirtualSMC and Lilu in Other folder? Edited December 5, 2022 by Montelli Link to comment Share on other sites More sharing options...
Recommended Posts