Некоторые производители не предоставляют EFI Shell сами. Бери отсюда
В том uefi, что установлен сейчас, нет uefi shell. vostrik уже посдказал, что можно взять full uefi у qlogic’а, но я пока не могу заставить hx5 с него загрузиться :\
через dd создал 128 мб файл, в нём партицию fat32, в неё распаковал full uefi от qlogic’a. Монтировал через remote drive корзины. В «/Boot Manager/Boot From File» ничего нового не появилось
Спасибо, попробую. Случайно не знаешь, как его готовить к загрузке?
Ложишь его в ESP или там в корень флешки какой-нибудь с FAT32 и впринципе должно работать. У меня в UEFI есть специально Launch efi shell from filesystem device.
Вот тут проблема. Корзина в другом конце города, есть только удалённая консоль корзины с возможностью монтирования. Образы cd точно принимает, насчёт образа флешки не уверен
У меня работало норм с флехи проброшенной через amm. У тебя какая корзина?
Чисто случайно под рукой не было не флэшки, ни компа с виндой
А теперь правильный ответ:
В результате в меню должен появиться пункт вроде
Другой вариант uefi shell. Не проверял.
Подробно про UEFI, см. секцию «References and Additional Information»
So I needed to do a factory reset now all I get is the following:- Restoration incomplete I click the retry button same thing happens. If I click details I get the following:- Sysprep not launched properly. The process will cause CTO panic because the image might not be normal.
Can anyone help please first time on the forum sorry if this is a repeat post.
How did you create the bootable drive?
Using the Media creation Tool should have set the drive up completely without this issue.
I would try booting with Legacy Mode enabled/Secure Boot off.
F10 to boot into Bios at startup.
Arrow over to System Configuration.
Arrow down to Boot Options and disable Secure Boot and enable Legacy (if is showing).
F10 to Save and Exit.
You will be prompted to enter a code. Do this, then reboot and try to boot into the USB again.
IF that does not work,
I would recommend you either try a different drive or try cleaning this drive and create the bootable again.
What is the full model number of your PC please?
Hi, Notebook model HO Pavilion 15 Notebook PC Product number F5c05ea#abu Serial number 5cd4103zvz
Performing recovery without disc as this is all pre installed.
The full error message is detailed in the original post does not include failed device.
I do have pictures of the error screen not sure how you attach them to this post.
For your own security, remove the Serial number in your post above.
That model came with Windows 8.1 originally and you upgraded to 10?
You are trying to do a recovery from the partition I assume.
When you install to the laptop, use Custom and delete the partitions first. Let Windows create new partitions itself when it installs.
IF it works, install the drivers for Win 10 from this page.
Let me know what happens or if you need more instructions.
I have downloaded the file to a usb stick plugged it into my laptop and nothing happens could you give me some more instructions please.
Use the Media Creation Tool to burn the bootable ISO file to an ( 8 to 32 GB ) usb flash stick on another computer that is working.
Не могу попасть из стандартного проводника в раздел EFI
BB-код ссылки (для форумов):
BB-код ссылки (для форумов):
NikROM, Вы ответьте сначала, зачем вам попадать в раздел EFI? Если вы испортите загрузочные файлы, система просто перестанет грузиться.
Попасть в него несложно, но в этом нет никакого смысла. Что бы в него попасть, надо хорошо владеть командой diskpart.
BB-код ссылки (для форумов):
Microsoft Windows [Version 10.0.18334.1] (c) 2018 Microsoft Corporation. All rights reserved.
Microsoft DiskPart version 10.0.18334.1
Copyright (C) Microsoft Corporation. On computer: P51FASTRING
DISKPART> select disk 0
Disk 0 is now the selected disk.
DISKPART> detail disk
NVMe Samsung SSD 960 SCSI Disk Device Disk ID: Type : NVMe Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1B00)#PCI(0000)#NVME(P00T00L00) Current Read-only State : No Read-only : No Boot Disk : Yes Pagefile Disk : Yes Hibernation File Disk : No Crashdump Disk : Yes Clustered Disk : No
DISKPART> list part
DISKPART> select part 1
Partition 1 is now the selected partition.
DISKPART> detail part
Partition 1 Type : e3c9e316-0b5c-4db8-817d-f92df00215ae Hidden : Yes Required: No Attrib : 0000000000000000 Offset in Bytes: 17408
There is no volume associated with this partition.
DISKPART> select part 2
Partition 2 is now the selected partition.
DISKPART> detail part
Partition 2 Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b Hidden : Yes Required: Yes Attrib : 0X8000000000000001 Offset in Bytes: 135266304
При развертывании Windows на компьютер с несколькими жесткими дисками убедитесь в том, что образы применяются к соответствующим дискам. Диски можно определить в средстве diskpart с помощью пути расположения (например, PCIROOT(0)#PCI(0100)#ATA(C00T00L00)), который зависит от физического подключения к компьютеру.
Для компьютеров на основе BIOS или компьютера со службой виртуальных дисков (VDS) для выбора соответствующих дисков можно использовать команды SELECT DISK=SYSTEM and SELECT DISK=NEXT. Дополнительные сведения см. в разделе Управление несколькими жесткими дисками на основе BIOS.
В этом разделе
Выбор системного диска
При настройке систем с несколькими дисками не используйте команду SELECT DISK=0 для указания системного диска. При перезагрузке компьютер может назначить дискам другие номера, а различные компьютеры с одной конфигурацией дисков также могут иметь различные номера дисков.
Определение пути расположения диска
Чтобы отобразить путь расположения для выбранного диска, используйте команду diskpart DETAIL DISK.
В этом примере путь расположения для выбранного диска равен PCIROOT(0)#PCI(0100)#ATA(C00T00L00).
Формат пути расположения
Для дисков с типом шины SCSI/SAS/RAID следует использовать следующий формат пути расположения:
Для дисков с типом шины ATA/SATA следует использовать следующий формат пути расположения:
В следующей таблице определяются элементы пути расположения.
Получите путь, вызвав SetupDiGetDeviceProperty с помощью свойства DEVPKEY_Device_LocationPaths.
Один из следующих типов: ATA, SCSI, SAS или RAID.
Поле PathId для SCSI_ADDRESS. Получите идентификатор PathID путем вызова IOCTL_SCSI_GET_ADDRESS.
Поле PathId для SCSI_ADDRESS. Получите идентификатор PathID путем вызова IOCTL_SCSI_GET_ADDRESS.
Примечание.
Для дисков с типом шины ATA/SATA идентификатор канала относится к тому же полю, что и PathID. Используется префикс C.
Поле TargetId для SCSI_ADDRESS. Получение путем вызова IOCTL_SCSI_GET_ADDRESS.
Поле Lun для SCSI_ADDRESS. Получение путем вызова IOCTL_SCSI_GET_ADDRESS.
В следующей таблице приведены примеры путей расположения для всех типов шин и дисков:
Issues revolving around macOS once properly installed.
# Broken iMessage and Siri
# No on-board audio
# BIOS reset or sent into Safemode after reboot/shutdown
# Synaptics PS2 based trackpad doesn’t work
(opens new window) By default, this uses PCI0.LPCB.PS2K for the pathing. you’ll want to rename accordingly.
Then compile with MaciASL, copy to your OC/ACPI folder, and add it to your config, and you should be good to go.
(opens new window) ). If you can live without the trackpad, this may be better:
Find the ACPI path of your mouse (see above), then grab SSDT-DisableTrackpadProbe.dsl
# Fix for Dell breakless PS2 keyboard keys
For those with issues surrounding key presses not releasing(ie. pressing infinitely), you’ll want to enable VoodooPS2’s Dell profile.
First of all, you need to find the path to your ACPI keyboard object in the Device Manager:
(opens new window) and change the ACPI path to the one found above as needed:
# macOS GPU acceleration missing on AMD X570
Verify the following:
# DRM Broken
# «Memory Modules Misconfigured» on MacPro7,1
Follow guide listed here:
For those who simply want to disable the notification(not the error itself) is more than enough. For these users, we recommend installing RestrictEvents
# Apps crashing on AMD
Easy fix, buy Intel
So with AMD, whenever Apple calls CPU specific functions the app will either not work or outright crash. Here are some apps and their «fixes»:
# Sleep crashing on AMD
This is generally seen on AMD who use the chipset’s USB controller, specifically for the Ryzen series and newer. The main way to tell if you’re having issues with this is checking logs after either sleeping or waking:
Should result in something like this:
You can double check which controller is XHC0 via IOReg and checking the Vendor ID(1022 for AMD chipset). The fix for this sleep issue is either:
# AssetCache Content Caching unavailable in virtual machine
arise due to VMM flag being exposed by sysctl.
(opens new window) kernel patch to disguise the flag and allow normal operation.
# Coffee Lake systems failing to wake
In macOS 10.15.4, there were some changes made to AGPM that can cause wake issues on Coffee Lake systems. Specifically displays hooked up to the iGPU would fail to wake. To resolve this:
# No brightness control on Dual GPU laptops
In macOS 11.3, there were some changes made to backlight controlling mechanisms that defaults the backlight to be controlled by the dGPU on Dual GPU laptops with MUX enabled. Optimus only laptops, however, are not affected, since you need to disable the dGPU anyways. Specifically, this problem only causes issues if you have a Dual GPU laptop with the internal screen from an iGPU output and external screens from dGPU outputs ( Hybrid Mode on some Mobile Workstations). To resolve this, you may disable either the iGPU or the dGPU, or do the following:
Add below to PciRoot(0x0)/Pci(0x2,0x0) :
@0,backlight-control | Data | 01000000
applbkl | Data | 01000000
AAPL,backlight-control | Data | 01000000
AAPL00,backlight-control | Data | 01000000
@0,backlight-control | Data | 00000000
applbkl | Data | 00000000
AAPL,backlight-control | Data | 00000000
# No temperature/fan sensor output
For iStat, you’ll have to wait for an update. For AMD users, you can use either:
Note for AMD with FakeSMC:
# «You can’t change the startup disk to the selected disk» error
This is commonly caused by irregular partition setup of the Windows drive, specifically that the EFI is not the first partition. To fix this, we need to enable this quirk:
# Selecting Startup Disk doesn’t apply correctly
Example of missing DevicePathsSupported :
# macOS waking up with the wrong time
An odd quirk some people may notice is that from wake, macOS will have the incorrect time for a bit before self-correcting with network time check. The root cause of this issue is most likely due to your RTC not ticking, and can be resolved with a new CMOS battery(note that Z270 and newer are quite picky with voltage so choose carefully).
To verify whether your RTC is working correctly:
This should provide you with a hexadecimal value, and once converted it should equal time elapsed from Midnight relative to Cupertino.
So for this example, we’ll grab our value( 00010D13 ) then convert it to decimal and finally divide it by 3600. This should result in the approximate time elapsed(in seconds) since midnight relative to Cupertino
Next you’ll want to put your hack to sleep for a bit and wake it, then check the CLKT value once more to see whether it deviated more or if it has a set difference. If you find it didn’t actually tick much of at all from the elapsed time, you’ll need to look into buying a new battery(with proper voltage)
# No Volume/Brightness control on external monitors
Oddly enough, macOS has locked down digital audio from having control. To bring back some functionality, the app MonitorControl
(opens new window) has done great work on improving support in macOS
# Time inconsistency between macOS and Windows
This is due to macOS using Universal Time while Windows relies on Greenwich time, so you’ll need to force one OS to a different way of measuring time. We highly recommend modifying Windows instead as it’s far less destructive and painful:
# Disabling SIP
SIP or more properly known as System Integrity Protection, is a security technology that attempts to prevent any malicious software and the end user from damaging the OS. First introduced with OS X El Capitan, SIP has grown over time to control more and more things in macOS, including limiting edits to restricted file locations and 3rd party kext loading with kextload (OpenCore is unaffected as kexts are injected at boot). To resolve this, Apple has provided numerous configuration options in the NVRAM variable csr-active-config which can either be set in the macOS recovery environment or with OpenCore’s NVRAM section(The latter will be discussed below).
You can choose different values to enable or disable certain flags of SIP. Some useful tools to help you with these are CsrDecode
Note: Disabling SIP with OpenCore is quite a bit different compared to Clover, specifically that NVRAM variables will not be overwritten unless explicitly told so under the Delete section. So if you’ve already set SIP once either via OpenCore or in macOS, you must override the variable:
# Writing to the macOS system partition
With macOS Catalina and newer, Apple split the OS and user data into 2 volumes where the system volume is read-only by default. To make these drives writable we’ll need to do a few things:
macOS Catalina
macOS Big Sur
Commands based off of Apple’s KDK documents:
# Rolling back APFS Snapshots
With macOS Big Sur, the system volume is now snapshotted allowing you to roll back in case of issues with system updates breaking due to a broken seal. Thanks to new snapshots being created with every OS update, we’ve got quite a bit to roll back too.
To roll back, you’ll first need to reboot into Recovery partition then select «Restore From Time Machine Backup»:
# Apple Watch Unlock issues
For those with Apple Watch Unlock issues, verify the following:
If the above are met, and you still have unlock issues we recommend running through the below guide:
# 4K iGPU output issues over HDMI
For machines with HDMI 2.0 capable ports with resolution issues, verify the following:
For all other troubleshooting, please reference WhateverGreen’s Intel docs
