Jump to content

Sherlocks

Coders
  • Content count

    1,998
  • Joined

  • Last visited

  • Days Won

    30

Sherlocks last won the day on October 20

Sherlocks had the most liked content!

3 Followers

About Sherlocks

  • Rank
    InsanelyMac Deity

Profile Information

  • Gender
    Male
  • Location
    Seoul

Recent Profile Visitors

7,369 profile views
  1. Sherlocks

    Clover problems report & features request

    try this test1.zip
  2. Sherlocks

    Clover problems report & features request

    your nvram was clean. try this test file for freeze problem. little freeze happen when removing nvram values. but after freezing, your system have to reboot. if hold on freezing option long time, it's problem. test.zip
  3. Sherlocks

    Clover problems report & features request

    okay. seems logic is not univeral for all bios. i will check it tommorow. and i will upload test file here. 나의 LG-F800S 의 Tapatalk에서 보냄
  4. Sherlocks

    Clover problems report & features request

    great. we can't see nvram boot order variables in macos. it's normal.your system shown good result. thanks for report. 나의 LG-F800S 의 Tapatalk에서 보냄
  5. Sherlocks

    Clover problems report & features request

    okay did you try cleanvram.efi? 나의 LG-F800S 의 Tapatalk에서 보냄
  6. Sherlocks

    Clover problems report & features request

    my peonix bios laptop, i did lost clover boot option(initialized) if BootOrder was removed. only boot windows. so i added boot entry again in bios. your bios is good. anyways removing the nvram value associated with the boot is not currently the best option. thanks
  7. Sherlocks

    Clover problems report & features request

    you can't see BootOrder nnvram in macos. cleannvram.efi remove BootOrder nvram value and other from filter that has Boot####. it affects our clover boot option entry in BIOS. after press f11, my nvram result(aptiomemoryfix, vitrualsmc). it's very clean status. Last login: Sat Oct 20 21:15:07 on ttys000 SherloccBookPro:~ sherlocks$ nvram -p fmm-computer-name Sherlocks%ec%9d%98 MacBook%c2%a0Pro security-mode none bluetoothActiveControllerInfo z%e0%89%04%00%00%00%000%14%ac%d1%b8%e2%a4%d0 EFILoginHiDPI %00%00%00%00 specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00%00H%06%00%00%00%00%00%00(*%08%00%00%00%00%8f%0a5%8c%c6P%e6C%ad%a6^%16p%d2e%d9%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ba%afc~%ff%1e%a9M%b0%d2$%86%1e%e2HD%7f%ff%04%00 SystemAudioVolume # SystemAudioVolumeDB %d9 csr-active-config w%00%00%00 backlight-level i%05 flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 SherloccBookPro:~ sherlocks$
  8. Sherlocks

    Clover problems report & features request

    try latest version r4717. cleannvram.efi has deleting the boot menu option. i added that disabled this option. i tested again. there is no problem. 나의 LG-F800S 의 Tapatalk에서 보냄
  9. Sherlocks

    Clover problems report & features request

    right. if you want, press f11 in gui in r4717. it's fixed. some users use virtualsmc. but there is previous fakesmc values in NVRAM. in mojave, it's hard to remove it. because nvram -c command is not working. so you usually use CleanNvram.efi. now in GUI, press f11, you easily remove NVRAM values. 나의 LG-F800S 의 Tapatalk에서 보냄
  10. Sherlocks

    Clover problems report & features request

    froze up -> processing -> reboot okay? i know vit9696 nvram clear has bootorder remove. i think he want all nvram value initialized. i will add that avoid to remove boot option. 나의 LG-F800S 의 Tapatalk에서 보냄
  11. Sherlocks

    Clover problems report & features request

    @Pavo. i worked NVRAM cleaner and tested all. its same that CleanNvram.efi of vit9696. try latest clover. 나의 LG-F800S 의 Tapatalk에서 보냄
  12. Sherlocks

    Clover Change Explanations

    Rev 4716 new way for reset native NVRAM in GUI by Sherlocks. thanks to vit9696. - it's perfectly same process by vit9696's CleanNvram.efi. now we can't properly delete NVRAM variables in Mojave. so if you want to clean NVRAM, press F11 in GUI. - caution! your bootorder also will be deleted(it means that bootorder initialized) if you have a dual boot(macos and windows). it's different according to user system Rev 4717 prevent clover boot options from being deleted when NVRAM is reset
  13. Sherlocks

    Clover problems report & features request

    @Pavo. i traced NVRAM values and i checked vit9696 cleanvram efi file. i saw many nvram values for system. if ease all option, maybe we can lost our system. therefore specific nvram values were removed. 2:259 0:000 DIAGSPLSHSCRN 2:259 0:000 SetupMode 2:259 0:000 SignatureSupport 2:259 0:000 SecureBoot 2:260 0:000 VendorKeys 2:260 0:000 XVar 2:260 0:000 TxeUnlockBootCount 2:260 0:000 BootOptionSupport 2:260 0:000 PlatformLangCodes 2:261 0:000 SctCapResvMemAddr 2:261 0:000 SctCapResvMemSize 2:261 0:000 SetupVolatileData 2:261 0:000 CpuSetupVolatileData 2:262 0:000 ColdReset 2:262 0:000 SaColdReset 2:262 0:000 MeColdReset 2:262 0:000 CpuColdReset 2:262 0:000 PchColdReset 2:262 0:000 IccMbpData 2:263 0:000 ConOutDev 2:263 0:000 ErrOutDev 2:263 0:000 ConInDev 2:263 0:000 MeInfoSetup 2:264 0:000 OsIndicationsSupported 2:264 0:000 BootCurrent 2:264 0:000 AuthVarKeyDatabase 2:264 0:000 VendorKeysNv 2:264 0:000 SaDataBase 2:264 0:000 PbaStatusVar 2:265 0:000 XnoteFpVar 2:265 0:000 SecureBootEnable 2:265 0:000 PciBusSetup 2:265 0:000 MeBiosExtensionSetup 2:265 0:000 SelectView 2:265 0:000 UCR 2:266 0:000 CustomMode 2:266 0:000 MemoryOverwriteRequestControlLock 2:266 0:000 TcgSetup 2:266 0:000 RTC 2:267 0:000 MemoryConfig 2:267 0:000 AcpiGlobalVariable 2:267 0:000 PlatformLang 2:267 0:000 SctLoadDefaultCreateFlag 2:267 0:000 ExFPDT 2:267 0:000 SetupCpuFeatures 2:268 0:000 HDDPWD 2:268 0:000 SinitSvnSetup 2:268 0:000 InitSetupVariable 2:268 0:000 OsProfile 2:268 0:000 TREE_CONFIGURATION 2:268 0:000 Boot0010 2:269 0:000 Boot0011 2:269 0:000 Boot0012 2:269 0:000 Boot0013 2:269 0:000 BootMenu 2:269 0:000 Boot0014 2:270 0:000 Boot0015 2:270 0:000 Boot0016 2:270 0:000 Boot0017 2:270 0:000 Boot0018 2:270 0:000 BootAllPciLan 2:270 0:000 Boot0019 2:271 0:000 BootOrderDefault 2:271 0:000 ProtectedBootOptions 2:271 0:000 Key0000 2:271 0:000 Key0001 2:271 0:000 Key0002 2:272 0:000 Key0003 2:272 0:000 Key0004 2:272 0:000 Key0005 2:272 0:000 Key0006 2:272 0:000 ConOut 2:272 0:000 TrEEPhysicalPresenceFlags 2:273 0:000 TrEEPhysicalPresence 2:273 0:000 BootState 2:273 0:000 S3MemoryVariable 2:273 0:000 CapsuleLongModeBuffer 2:273 0:000 FirmwarePerformance 2:273 0:000 HSTI_RESULTS 2:274 0:000 PlatformConfigurationChange 2:274 0:000 MemoryTypeInformation 2:274 0:000 MeSetupStorage 2:274 0:000 SystemAccess 2:274 0:000 CpuSmm 2:275 0:000 PNP0604_1_VV 2:275 0:000 PNP0604_1_NV 2:275 0:000 PNP0501_0_VV 2:275 0:000 PNP0501_0_NV 2:275 0:000 PNP0510_1_VV 2:275 0:000 PNP0510_1_NV 2:276 0:000 PNP0400_0_VV 2:276 0:000 PNP0400_0_NV 2:276 0:000 PNP0604_0_VV 2:276 0:000 PNP0604_0_NV 2:276 0:000 PNP0501_2_VV 2:277 0:000 PNP0501_2_NV 2:277 0:000 PNP0400_1_VV 2:277 0:000 PNP0400_1_NV 2:277 0:000 PNP0604_2_VV 2:277 0:000 PNP0604_2_NV 2:277 0:000 PNP0501_3_VV 2:278 0:000 PNP0501_3_NV 2:278 0:000 PNP0501_4_VV 2:278 0:000 PNP0501_4_NV 2:278 0:000 PNP0400_2_VV 2:278 0:000 PNP0400_2_NV 2:278 0:000 UserManagerVar 2:279 0:000 Timeout 2:279 0:000 CurrentActivePolicy 2:279 0:000 certdb 2:279 0:000 CurrentPolicy 2:279 0:000 BootDebugPolicyApplied 2:280 0:000 Kernel_SiStatus 2:280 0:000 Kernel_RvkSiStatus 2:280 0:000 Kernel_SkuSiStatus 2:280 0:000 Kernel_WinSiStatus 2:280 0:000 Kernel_ATPSiStatus 2:280 0:000 Kernel_EntRevokeSiStatus 2:281 0:000 WindowsBootChainSvn 2:281 0:000 BootingDeviceTypeInfo 2:281 0:000 UnlockID 2:281 0:000 UnlockIDCopy 2:281 0:000 OfflineUniqueIDEKPub 2:282 0:000 OfflineUniqueIDEKPubCRC 2:282 0:000 dbx 2:282 0:000 MemoryOverwriteRequestControl 2:282 0:000 Boot0001 2:282 0:000 Boot0000 2:282 0:000 UIScale 2:283 0:000 current-network 2:283 0:000 XnoteStat 2:283 0:000 System 2:283 0:000 HDD_Password_Status 2:283 0:000 boot-feature-usage 2:284 0:000 Boot0081 2:284 0:000 Boot0080 2:284 0:000 LastBootOrder 2:284 0:000 LastBootCurrent 2:284 0:000 BiosSetup 2:284 0:000 XnoteBootFailCounts 2:285 0:000 Setup 2:285 0:000 SaSetup 2:285 0:000 PchSetup 2:285 0:000 CpuSetup 2:285 0:000 MeSetup 2:286 0:000 PlatformInfo 2:286 0:000 BootOrder 2:286 0:000 fakesmc-key-$Num-ui8 2:286 0:000 csr-active-config 2:286 0:000 specialbootdevice 2:286 0:000 backlight-level 2:287 0:000 preferred-networks 2:287 0:000 preferred-count 2:287 0:000 bluetoothActiveControllerInfo 2:287 0:000 fakesmc-key-$Adr-ui32 2:287 0:000 fakesmc-key-RMde-char 2:288 0:000 security-mode 2:288 0:000 EFILoginHiDPI 2:288 0:000 flagstate 2:288 0:000 fakesmc-key-RPlt-ch8* 2:288 0:000 fakesmc-key-RBr -ch8* 2:288 0:000 fakesmc-key-EPCI-ui32 2:289 0:000 fakesmc-key-REV -ch8* 2:289 0:000 fakesmc-key-BEMB-flag 2:289 0:000 fakesmc-key-BATP-flag 2:289 0:000 fakesmc-key-BNum-ui8 2:289 0:000 fakesmc-key-BBIN-ui8 2:290 0:000 fakesmc-key-MSTc-ui8 2:290 0:000 fakesmc-key-MSAc-ui16 2:290 0:000 fakesmc-key-MSWr-ui8 2:290 0:000 fakesmc-key-MSFW-ui8 2:290 0:000 fakesmc-key-MSPS-ui16 2:290 0:000 SystemAudioVolumeDB 2:291 0:000 fmm-computer-name 2:291 0:000 fakesmc-key-#KEY-ui32 2:291 0:000 AAPL,PanicInfoLog 2:291 0:000 SystemAudioVolume 2:291 0:000 security-mode 2:292 0:000 backlight-level 2:292 0:000 EFILoginHiDPI 2:292 0:000 flagstate 2:292 0:000 csr-active-config 2:292 0:000 specialbootdevice 2:292 0:000 AAPL,PathProperties0000 2:293 0:000 PVar 2:293 0:000 OpromDevicePath 2:293 0:000 ConIn 2:293 0:000 MTC Now the macOS nvram value is mixed with the nvram values of my laptop. what is your left nvram values?
  14. Sherlocks

    Clover problems report & features request

    case1 no intel injection, Device/Properties, inject EDID case2 no intel injection, no inject EDID, Device/Properties(AAPL00,override-no-connect) case3 intel injection, Device/AddProperties(IntelGFX), inject EDID i'm using case3
  15. Sherlocks

    AnV is back

    Welcome back[emoji3] 나의 LG-F800S 의 Tapatalk에서 보냄
×