Jump to content
About Just Joined group Read more... ×
ErmaC

Clover General discussion

24,188 posts in this topic

Recommended Posts

F2 preboot log is written to "misc" folder in your Clover folder. 

 

bdmesg  :will show you clover boot log

 

sudo dmesg  :will show your kernel boot log

Is there anyway to get the log from the part of Clover that does the kext patching? This is the stuff that occurs after the clover boot log and before the kernel boot log.

 

Or is there a way to redirect the console output to the serial port instead of the screen? If the console output could be redirected, then couldn't it be redirected to a memory buffer, maybe the same buffer that holds the boot log or a new buffer for this log? It may be necessary to allocate extra space for this log before writing log information there if it is not possible to make a growing buffer.

Share this post


Link to post
Share on other sites
Advertisement

Hi, somehow clover has a problem with HFS+ volume modify dates. See:

 

 

18:288 0:063 - [02]: 'OSX'
18:321 0:033 AddLoaderEntry for Volume Name=OSX
18:335 0:013 Not match custom entry 0: Type: not match
18:387 0:052 Check if volume Is Hibernated:
18:404 0:016 Check sleep image 'by signature':
18:427 0:023 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success
18:443 0:015 using default sleep image name = \private\var\vm\sleepimage
18:463 0:020 Reading first 512 bytes of sleepimage ...
18:477 0:013 OurBlockIoRead: Lba=5DAC68, Offset=5DAC68000 (BlockSize=4096)
18:491 0:013 sig lion: 73696D65
18:504 0:012 sig snow: 0
18:516 0:011 got sleep image offset
18:529 0:012 Reading completed -> Success
18:543 0:013 sleepimage offset acquired successfully: 5DAC68000
18:557 0:014 gSleepTime: 1488973117
18:572 0:014 HFS+ volume modifyDate: -2082844801
18:585 0:012 image older then volume: 723149378 sec
18:597 0:011 image too old
18:610 0:012 hibernated: no - time

makes freshly created sleep images unloadable. Used Clover version: 4003. Clover files are available on: http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/

Edited by Micky1979
Please read the Rules

Share this post


Link to post
Share on other sites

Clover kext patching is being applied to kernel/kext cache and should be shown in bdmesg. 

 

As far as I know there is nothing to log between clovers end and the start of boot.efi 

Share this post


Link to post
Share on other sites

@joevt, idk if Clover supports that OOTB, but EDK2 supports serial output (DebugLib). Just change The DBG macros in the code if there isnt a serial one already.

I also have no clue why patching doesnt happen before, while the BS are still up.

 

@joe75 Clover does stuff during boot.efi execution

Share this post


Link to post
Share on other sites

@Slice

 

http://www.insanelymac.com/forum/index.php?/topic/284656-Clover-General-discussion&do=findComment&comment=2379057

 

This rc script is no problem about known failure case and other issue(entire code is same before, tluck have optimized in latest code).

 

I tested to find failure case and not work properly many times since find failure case.

 

No more see failure case now.

 

Hope update rc script in clover.

 

Thanks @tluck @syscl @testers

 

Thanks in advance.

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

 

Note:

the "LogoutHook method" needs more than just the rc.shutdown/80.save_nvram_plist.local updated in the Clover repo. 

CloverDaemon was split into 2 scripts and then the "Shutdown" part is the LogoutHook script.

I suspect this could be easily implemented in the Clover installer with Emuvariable or  new Rc script option

Share this post


Link to post
Share on other sites

Hi Guys!

 

First, the usual, thanks for all the great work. This project is pure goodness.

 

On to it: Wondering why we still proceed with a shutdown hook to capture and save nvram key-values to a file... especially since when we run an installer image, those hooks aren't present and thus the nvram modifications are lost.

 

My goal was to create a boot usb key which would not contain any OSes but simply contain clover and all that is needed to run a vanilla mac os install on a legacy BIOS board. Saving the nvram variables is pretty much what's left standing in the way of having this key complete.

 

I have changed the save_nvram_plist script to find the actual ESP where clover booted from (through ioreg analysis). It is attached to this post. It is a fork of the script from v2.3k_r3974. See attached.

 

Now it works well in that it doesn't care about the current OS disk running, but rather assumes that the clover EFI partition is the best spot. It allows me to have one single clover boot partition, from which I can boot any of my installs, test installs, clone backups, etc.

 

BUT, it nvram changes made into installer boots are still lost.

 

SO, is it not possible to have a fake UEFI handler/driver (I'm new at this) which would actually catch the expected firmware or SMC "functions" and save the nvram data to a file, or a fixed sector of a block device (USB or whatever). I know the legacy BIOS RTC memory won't fit the nvram data, but we should be able to spare a few sectors and do very raw, BIOS like, write operations no?

 

I am a professional linux embedded developer but have never actually developed on my macs. I started casually browsing clover source code but would need pointers to get started, if it's at all possible.

 

Really looking forward to contributing!

80.save_nvram_plist.local.zip

Share this post


Link to post
Share on other sites

Hi Guys,

 

I am having little problem here. i have installed Sierra on XEON E2683 V3 14Core machine successfully and is working fine except two issues. sleep won't working and about mac shows" 2.0Ghz unknown " I haven't added any fake id or enabled kernel patching, actually it is not necessary I believe. I have tried several values in clover "CPU type"  but none of them are working..still shows Unknow Cpu. but my XEON E5 12core CPU shows correctly in about mac section. 

Is anybody knows what may be the issue??

 

Thank you,

Share this post


Link to post
Share on other sites

Yes. There were 2 problems with edk2 commit dc4c77

  • Get error "global macro arch is not permitted' in refit.inf.  This is result of change in MetaFileParser.py.  Can fix this by either using reversion checked in by Slice, or as Fritz suggested - edit refit.inf and change CLOVER$(ARCH) to just CLOVER.
  • The change in WorkspaceDatabase.py caused unfixable breakdown - a regression in edk2 build process.  It was fixed by edk2 commit 1d8ceb.  So after 1d8ceb, it is possible to use WorkspaceDatabase.py from edk2 tree or the reversion checked in by Slice.

Hope this clarifies.

 

This is my fault, I was trying to get them to fix this problem with macro expansion and instead just emits an error now...

Share this post


Link to post
Share on other sites

@greatcornholio

 

"nvram save" has been a topic of discussion debate and progress over the last month or so. btw, Clover 3974 is a bit old by the way! :)

there is a new proposed script and method recently posted above (v.1.16.1) . but this new model is not yet incorporated into the Clover tree (or package installer).

 

Note:

1) saves NVRAM to ESP vs /

2) uses LogoutHook vs shutdown

3) needs some tools/scripts in /etc (rc.clover.lib, rc.shutdown.d) etc)

 

So either way to your point, the old (your script) or new method does not handle the OS installer scenario very well. 

So yes, If there is extra stuff on the Installer - and if that somehow gets run, then the USB could provide the nvram.plist file on next boot presuming that is boot disk. 

perhaps you can expand on your idea to maintain variables from the install session ( are these really needed?)

Share this post


Link to post
Share on other sites

@greatcornholio

 

"nvram save" has been a topic of discussion debate and progress over the last month or so. btw, Clover 3974 is a bit old by the way! :)

there is a new proposed script and method recently posted above (v.1.16.1) . but this new model is not yet incorporated into the Clover tree (or package installer).

 

Note:

1) saves NVRAM to ESP vs /

2) uses LogoutHook vs shutdown

3) needs some tools/scripts in /etc (rc.clover.lib, rc.shutdown.d) etc)

 

So either way to your point, the old (your script) or new method does not handle the OS installer scenario very well. 

So yes, If there is extra stuff on the Installer - and if that somehow gets run, then the USB could provide the nvram.plist file on next boot presuming that is boot disk. 

perhaps you can expand on your idea to maintain variables from the install session ( are these really needed?)

 

we have to add "CloverDaemon-stopservice" file?

 

 

 
trap StopService SIGTERM # SIGTERM @ shutdown
while true; do
    sleep 86400 &  # Start the sleep process in background
    wait $!        # and wait to finish
done

 

above code, you did disabled to prevent failure case when shutdown in CloverDaemon. Is not that enough?

 

actually CloverDaemon-stopservice file work? "CloverDaemon" file run with com.projectosx.clover.daemon.plist.

 

but i can't see something to run CloverDaemon-stopservice.

 

why you add CloverDaemon-stopservice this file?

 

add. if there is no CloverDaemon-stopservice file, nvram can't gernerate when shutdown or restart. need CloverDaemon-stopservice file.

 

anyways 1.16.1 is working without problem for 1 weeks. i checked log and location everyday

Share this post


Link to post
Share on other sites

@sherlocks 

 

if you installed nvram save script v1.16.1 by the installation script included the zip, then i believe you are launching the /etc/rc.shutdown.d/80*local script by LogoutHook - but not directly.

 

The LogoutHook script is /Library/A S/Clover/CloverDaemon-stopservice

- which runs then "shutdown scripts" in /etc/rc.shutdown.d

 

i will try to explain rationale again: 

 

I split the original CloverDaemon into 2 parts

- to avoid trying to running the "shutdown scripts" during shutdown which is not reliable.

- Changing the method to run these scripts by LogoutHook is reliable.

 

CloverDaemon

- runs all startup scripts /etc/rc.boot.d/

- run by launchd, set by /Library/LaunchDaemons/com.projectosx.clover.daemon.plist

 

CloverDaemon-stopservices 

- runs all shutdown scripts in /etc/rc.shutdown.d

- run by LogoutHook, set by installation script

Share this post


Link to post
Share on other sites

@sherlocks

 

if you installed nvram save script v1.16.1 by the installation script included the zip, then i believe you are launching the /etc/rc.shutdown.d/80*local script by LogoutHook - but not directly.

 

The LogoutHook script is /Library/A S/Clover/CloverDaemon-stopservice

- which runs then "shutdown scripts" in /etc/rc.shutdown.d

 

i will try to explain rationale again:

 

I split the original CloverDaemon into 2 parts

- to avoid trying to running the "shutdown scripts" during shutdown which is not reliable.

- Changing the method to run these scripts by LogoutHook is reliable.

 

CloverDaemon

- runs all startup scripts /etc/rc.boot.d/

- run by launchd, set by /Library/LaunchDaemons/com.projectosx.clover.daemon.plist

 

CloverDaemon-stopservices

- runs all shutdown scripts in /etc/rc.shutdown.d

- run by LogoutHook, set by installation script

Thank you. I understand it now.

 

 

나의 LG-F410S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

@Sherlocks

 

- on the Pkg for nvram save

- i think you need to add a post install command to define LogoutHook.

 

can i use uncomment this line in 20.mount_ESP.local? only have to add in postinstall?

you did comment this line blow

 

 

#gLogoutHookLog="${CLOVER_LOG_LOCATION}/rc.syscl.addlogoutHook.log"

#gLogoutHookf="/etc/rc.shutdown.d/80.save_nvram_plist.local"
#if [ -f "${gLogoutHookf}" ]; then
#    #
#    # file exist, need to logoutHook
#    #
#    echo "v${gScriptVersion} © 2017 syscl/lighting/Yating Zhou" >${gLogoutHookLog}
#    echo "Found ${gLogoutHookf}, register logoutHook"            >>${gLogoutHookLog}
#    defaults write com.apple.loginwindow LogoutHook ${gLogoutHookf}
#fi
 

Share this post


Link to post
Share on other sites

can i use uncomment this line in 20.mount_ESP.local? only have to add in postinstall?

you did comment this line blow

 

well one can either define the LogoutHook by the Clover pkg installer - or some other way

If you use this start up script it will need some better logic

1) this does not need happen everytime it is run. 

2) the LogoutHook script should be general - so i chose to use /Library/A S/Clover/CloverDaemon-stopservice - since it can run multiple scripts as needed.

Share this post


Link to post
Share on other sites

well one can either define the LogoutHook by the Clover pkg installer - or some other way

If you use this start up script it will need some better logic

1) this does not need happen everytime it is run. 

2) the LogoutHook script should be general - so i chose to use /Library/A S/Clover/CloverDaemon-stopservice - since it can run multiple scripts as needed.

 

1) this does not need happen everytime it is run. 

is it important? i want to know

 

2) how about this one?

 

gLogoutHookf="/Library/Application Support/Clover/CloverDaemon-stopservice"

if [ -f "${gLogoutHookf}" ]; then
    #
    # file exist, need to logoutHook
    #
    echo "v${gScriptVersion} © 2017 syscl/lighting/Yating Zhou" >${gLogoutHookLog}
    echo "Found ${gLogoutHookf}, register logoutHook"            >>${gLogoutHookLog}
    defaults write com.apple.loginwindow LogoutHook ${gLogoutHookf}
fi

 

 

add. it works

 

Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log

Password:

-------------------------------

DATE: 2017-03-11 TIME: 05:38:30

-------------------------------

>> Begin Script: /etc/rc.shutdown.d/80.save_nvram_plist.local

v1.16.1 © 2017 syscl/lighting/Yating Zhou/tluck/Sherlocks

2017-03-11-05:38:30  disk0: ESP -- Target  -- /Volumes/ESP-01/EFI/CLOVER

2017-03-11-05:38:30  NVRAM: No change since last update in /Volumes/ESP-01/nvram.plist

>> End Script: /etc/rc.shutdown.d/80.save_nvram_plist.local

 

Supreme-MBP:~ supreme$ 

 

and

 

v1.16.1 © 2017 syscl/lighting/Yating Zhou

Found /Library/Application Support/Clover/CloverDaemon-stopservice, register logoutHook
 

Share this post


Link to post
Share on other sites

@sherlocks - 

 

try this version for 20.mount_ESP.local

 

added some logic to make sure should even add the LogoutHook etc.

 

okay. i see good code. 

 

normal process

boot, clover-daemon load, when restart or shutdown, disable clover-daemon(by CloverDaemon-stopservice). it's no problem.

 

i want to know one case whether problem or not

case is 

if logout and login again or wakeup. clover-daemon never work again? no need sudo defaults write com.apple.loginwindow LoginHook?

like "defaults write com.apple.loginwindow LoginHook /Library/Application Support/Clover/CloverDaemon"

 

add. New ESP script no problem


>> Begin Script: /private/etc/rc.boot.d/10.save_and_rotate_boot_log.local
Clover boot messages saved in /Library/Logs/CloverEFI/boot.log
>> End Script: /private/etc/rc.boot.d/10.save_and_rotate_boot_log.local

>> Begin Script: /private/etc/rc.boot.d/20.mount_ESP.local
Not auto mounting EFI partition
v1.16.1 (c) 2017 syscl/lighting/Yating Zhou/tluck
Registering LogoutHook as /Library/Application Support/Clover/CloverDaemon-stopservice
>> End Script: /private/etc/rc.boot.d/20.mount_ESP.local

@Slice

i made new v3 pkg file. completed all

1.16.1 update pkg v3.zip

Share this post


Link to post
Share on other sites

Thanks for your answer.

 

"nvram save" has been a topic of discussion debate and progress over the last month or so. btw, Clover 3974 is a bit old by the way! :)

I know, this is why I was mentioning it. ;)

 

So either way to your point, the old (your script) or new method does not handle the OS installer scenario very well. 

So yes, If there is extra stuff on the Installer - and if that somehow gets run, then the USB could provide the nvram.plist file on next boot presuming that is boot disk. 

perhaps you can expand on your idea to maintain variables from the install session ( are these really needed?)

I know if I start the installer from my actual OS partition (which is setup to save nvram plist) some values are set to assist the reboot which completes the install. I assume the installer removes those. When emerging from the update in the real OS disk, these new key-values are still present. These are "install-product-url" and "rc_imgsrc_info". I had to manually remove them. Weather these are crucial or not I don't know.

 

Again, with the goal to keep the OS disk perfectly vanilla (rescue, install or real disk), since clover does kext injection, it would assume a kext could be written. This kext would grab all variables when asked to unload at shutdown and dump them in binary form to a storage device (maybe straight to device in a reserved area).

 

In fact, why is that not in FakeSMC.kext? Isn't the SMC responsible for saving nvram on real macs?

 

I'll keep digging.

Share this post


Link to post
Share on other sites

Hi. I think there's a typo in kext_inject.c:

UINT8   KBESieDebugSearchEXT[]   = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0xE9, 0x09, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };
UINT8   KBESieDebugReplaceEXT[]  = { 0xE8, 0x47, 0x00, 0x00, 0x00, 0x90, 0x90, 0x00, 0x00, 0x00, 0x48, 0x8B, 0x7D, 0xE8, 0xE8, 0xD9 };

Note that now we don't NOP out the jmpq fully. (E9 09 00 00 00 -> 90 90 00 00 00 , should be 5x NOP actually.)

 

And fixed here... (Also with a minor variable renaming, don't care about that. ;))

 

new_kext_inject.c.zip

Share this post


Link to post
Share on other sites

You all are going to think I'm nuts, but it would be wonderful if when the system boots to the Clover main load screen (the one that lists your drives and systems with icons), it would be great if there was a way to have some kind of screen saver turn on after some minutes.

 

I don't suppose there's any way to do that, but it would be a nice to have feature!

Share this post


Link to post
Share on other sites

Announcements

  • Similar Content

    • By BALDY_MAN
      Hi All.
      Im Happy to share my new EFI file that I put together  18/10/2020. which got me up and running 11.0  Beta(20A5395g) on my hack
      a thanks you to everyone who's work I have use to assemble this EFI File. and the help I have received from this site
      I have used openCore 0.6.3, sound work for me (HDMI) and onboard Ethernet. map the usb ports as you wish.
      the definition to iMac20,2
      hope it helps all who need it
      PS. Please leave a comment if the EFI File is helpful to you
      (No Kexts were Harmed in the making of this EFI)
                                                                                                                     regards
                                                                                                                                         Baldy_man
      GigabyteZ40Master.EFI.(20A539g) .zip
    • By le332313
      Can someone share the dell 5593/5493 EFI ? I try to fit the graphics driver, but it not working please help me thanks
       
    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/yxsw7d3t
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/yxsw7d3t
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
       
      Use these kexts, enable XHCI port limit patch
       
      USB INTEL SERIE 400.zip
       
      and follow this tutorial for remap USB ports
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By Nomade
      Hello All,
       
      It's been a while that I am trying to update my system to 10.15.16.
      The install seem to start, then at reboot time I only see the Normal boot and the Recovery option from the Clover boot menu.
      None of those 2 allow to complete the update.
       
      Is there any ways to force it to install and/or show the "Update" option on the Clover boot screen?
       
      PS: I'm using Z97-Gaming-3
    • By Damx
      The specs CPU: Intel® Core™ i3 Processor 8130U, 2.20 GHz (Kaby Lake Refresh) Chipset: Intel® 300 Series Graphics: Intel® UHD Graphics 620 Display: 21.5'' 1920x1200 RAM: DDR4 PC2400 4GB SSD1: M.2 PLEXTOR (with original Windows 10) SSD2: SATA SAMSUNG 850 EVO (for macOS) Sound: Realtek ALC269 WiFi / BT: Intel 3168 NGW Realtek Card-reader  
       
      Not working
      WiFi: Intel 3168 NGW Realtek Card-reader  
       
      Pre-Installation
       
      I will not go through the basics since it is explained in details here on this site. Briefly, the process is to:
      Get Clover Get Catalina macOS installer Create USB with 2 MBR partitions (FAT32 for Clover and HFS+J for the installer)  
       
      Required kexts
      AppleALC.kext Lilu.kext RealtekRTL8111.kext VirtualSMC.kext WhateverGreen.kext  
       
      Config.plist
      I used the one provided by RehabMan called config_HD615_620_630_640_650.plist. Download it from GitHub. It has almost everything you will need with only few edits for audio.
      Edits:
      [CPU] Make sure there is lilcpu=9 setting in boot arguments needed for Kaby Lake R CPU to be recognised correctly. [GPU] Make sure there is a patch GFX0 to IGPU under ACPI->DSDT [GPU] Under Devices->Properties->PciRoot(0)/Pci(0x02,0) make sure that the AAPL,ig-platform-id value is 00001B59, and the device-id value is 16590000 [AUDIO] Under Devices->Properties->PciRoot(0)/Pci(0x1f,3) set the layout-id to 40 and the device-id to 70A10000 [SMBIOS] Set Mac model ID is iMac19,2  

       

       
      Notes
      For some reason with latest version of Clover the install partition was not visible. If you run into the same issue you can downgrade Clover to r5103, which worked perfectly. WiFi / BT Intel 3168 NGW needs to be replaced if one needs WiFi. Someone mentioned that to get HDMI work properly you may need to change AAPL,ig-platform-id value to 00001659 for PciRoot(0)/Pci(0x02,0) - not my case but may be considered if you get this issue. Don't forget to generate your serial and other SMBUS values before signing in with iCloud services.  
       
×