Jump to content

17 posts in this topic

Recommended Posts

Hello guys,

Today i installed the beta on my external SSD ( cause i don't have more space in the case)

i tried in this way:

post-1050154-0-28111700-1506603651_thumb.jpg

and also using this:

41AhFQ8M6GL.jpg.40f4eb1cb2466662f9ed0f9d1a32f182.jpg

All goes right but, when i 1st boot the hdd it appears as this:

(the photo was just old , i'm using the new clover)

post-1050154-0-11995900-1506603655_thumb.jpg

and he stuck at apple logo.

This are the setting i use to make the usb boot:

1528520686-284133-customize-clover.thumb.png.a0752611e9259b67f731193d0048819d.png

what can i do ?

 

thx :D

 

 

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
1 hour ago, Si Vis Pacem said:

Try with Clover 4533 - latest

 

Some people were having no luck with 4522.

 

There is now ApfsDriverLoader to be used instead of apfs.efi.

 

Loads the apfs from the container itself. So no more updating / patching required.

i try and let u know ;)

thank u :D

EDIT: Nope alwayse stuck at the apple logo

the installation go fine ,it's alwayse the 1st boot the problem :(

Edited by Mario1964

Share this post


Link to post
Share on other sites
Posted (edited)
53 minutes ago, Gigamaxx said:

It could be the USB port is shutting down.    Hit the space bar and choose verbose boot and see where it stops and post a pic.

If i boot verbose he stuck here :/

i also tried with single user or safe, but same stuck here too

Screen.jpeg

Edited by Mario1964

Share this post


Link to post
Share on other sites
Posted (edited)
44 minutes ago, Si Vis Pacem said:

Did you select the plugins for upgrade as well?

 

ehm, what i need to do ?

i just use your Apfsdriverloader and put it in uefifolder64

59 minutes ago, Gigamaxx said:

Have you tried USB ports on back of machine try different ports.

i try and let u know ;)

EDIT: Nope , alwayse same :(

Edited by Mario1964

Share this post


Link to post
Share on other sites
Posted (edited)

Mario1964,

If this is the first boot then the install process shouldn't have completed since it usually takes a few reboots to complete the full install? Can you clarify when this reboot took place? How far along the progress bar when it rebooted? If that is the case then when you're at the clover boot screen you should be selecting the one that says something to the effect Boot OSX Install from Install..... if memory serves me correctly.

Edited by In-N-Out

Share this post


Link to post
Share on other sites
Posted (edited)
15 hours ago, In-N-Out said:

Mario1964,

If this is the first boot then the install process shouldn't have completed since it usually takes a few reboots to complete the full install? Can you clarify when this reboot took place? How far along the progress bar when it rebooted? If that is the case then when you're at the clover boot screen you should be selecting the one that says something to the effect Boot OSX Install from Install..... if memory serves me correctly.

it's the REAL 1st boot after the installation progress , the installation go fine.

 

EDIT: Just to try , i put it inside the pc (sata) and it worked without doing nothing , i made the language selection , account etc.

i tried again external (cause i need it external) and again freeze here:

Screen.thumb.jpeg.7d5098740edaeb07f1a2cb6115e74915.jpeg

so i don't know what can be :(

 

if it could be useful with the HFS+ OS it work as external , only as APFS i got this problem

 

Hope this can help

Edited by Mario1964

Share this post


Link to post
Share on other sites
Posted (edited)

I've got some news
i tried to boot using the flag: boot without injected kexts
and after 30min of apple logo with the loading (very slow)
finally something appear : a grey screen with the mouse .
that's all , can this be useful ?

Edited by Mario1964

Share this post


Link to post
Share on other sites
On 6/22/2018 at 3:41 AM, Mario1964 said:

I've got some news
i tried to boot using the flag: boot without injected kexts
and after 30min of apple logo with the loading (very slow)
finally something appear : a grey screen with the mouse .
that's all , can this be useful ?

 

 I had this with my RX 480 and RX 460 cards, I picked up a Displayport adapter to HDMI and it works.     My cards don't work with HDMi connection or at least they didn't in beta 1.

 

 

Are you using HDMi cable?

Share this post


Link to post
Share on other sites
6 hours ago, Gigamaxx said:

 

 I had this with my RX 480 and RX 460 cards, I picked up a Displayport adapter to HDMI and it works.     My cards don't work with HDMi connection or at least they didn't in beta 1.

 

 

Are you using HDMi cable?

yep , i'm using an hdmi cable .

su u suggest to try another video cable , i will try when i can ;)

Share this post


Link to post
Share on other sites
6 hours ago, Mario1964 said:

yep , i'm using an hdmi cable .

su u suggest to try another video cable , i will try when i can ;)

 

I picked up a DisplayPort to HDMI adapter for $10 US and it solved it.

Share this post


Link to post
Share on other sites

from the sound of the issue, it sounds like FakSMC injection is not working, because the install does not use FakeSMC it will run and allow you to get through the install, but when you do the (first real boot) it triggers the FakeSMC(modules) but they are not loaded and causing a lag and only gray screen.

 

 

HBP

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By jackluke
      Those who use Mojave with an OpenGL (non-Metal) Video Card in "dark mode" have noticed that global transparencies are working fine, while in "light mode" encountered the "grey" Finder menu bar and sidebars issues, this patch is intended for those who want to use Mojave mainly in "light mode" saving some transparencies around, so here is my "hybrid reduce transparency" patch.
       
      It is totally safe, harmless and reversible, it has been deeply tested and will 100% work until restart or logout, even after sleep lock screen it will still work.
      To return with normal "transparency" you can also do that from Accessibility prefpane disabling the "reduce transparency" checkbox.
      To use this patch just double click on this attached shell "mojavehld.command" and it will launch through Terminal.

      [METHOD 1: Enable hybrid transparency]
      After launch the mojavehld.command just follow these steps:
      type 1
      type 4
      close Terminal (CMD+Q) and any other app previously opened.

      (The choice number 3 is not mandatory)

      [METHOD 2: Force hybrid transparency]
      If for some reason after that you will still get Dock and Notification Center without "transparencies" then relaunch the mojavehld.command:
      type 2
      type 1
      type 4
      close Terminal (CMD+Q) and any other app previously opened.
       
      Download attached here: mojavehld.zip
       





    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Beta Warning
      Please note that it is currently in a "beta" state so use it at your own risk. I am just documenting this here for those of you who want to get framebuffer patching now.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can wait for the official binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - Desktop: 0x00030010 (default)
      - Laptop: 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - Support started with OS X 10.8.x
      - Desktop: 0x0166000A (default), 0x01620005
      - Laptop: 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - Support started with OS X 10.9.x
      - Desktop: 0x0D220003 (default)
      - Laptop: 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - Support started with OS X 10.10.2
      - Desktop: 0x16220007 (default)
      - Laptop: 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - Support started with OS X 10.11.4
      - Desktop: 0x19120000 (default)
      - Laptop: 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - Support started with macOS 10.12.6
      - Desktop: 0x59160000 (default)
      - Laptop: 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - Desktop: 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - Laptop: 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Debugging
      If you need a dump of your framebuffers in binary use the boot flag -igfxdump. The output will be in /AppleIntelFramebuffer_GEN_KERNX_Y on your boot drive (Eg. AppleIntelFramebuffer_10_17.7). Intel FB-Patcher can File->Open this and generate a config.plist/Devices/Properties patch for Clover. 010 Editor can also parse this file using the IntelFramebuffer.bt template.
      To get debug output from Lilu use the -liludbgall flag and for WhateverGreen use the -wegdbg boot flag. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt
      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for All Data patching method
       


    • By chebkhaled1960
      Hello everyone 
      i noticed that when you install MacOS Mojave the format of HDD is converted to APFS automatically even if you formatted the HDD with HFS ! 
       
      My question is: i read that APFS is especially for SSD and not HDD, is APFS will damage my HDD or it’s Ok if I used it ?
       
      i need your helps and thank you .
    • By onlyJRevenge
      Ciao ragazzi, 
      volevo anticipatamente nuovamente ringraziare gengik84 per avermi realizzato il medesimo portatile su High Sierra perfettamente funzionante, che fino ad oggi non mi ha mai dato nessun problema.
       
      Ho deciso di installare la developer 11 o se meglio vogliamo chiamarla "DG" che dovrebbe essere l'anticipazione della stabile, tutto funziona correttamente tranne le seguenti cose:
       
      - WiFi non funzionante (prima andava senza problemi, addirittura la 5Ghz)
      - Bug grafici (che ad es. disattivato l'accelerazione hardware da Chrome, non da più problemi)
      - Se non avvio Clover in -v, non parte
       
      Avreste modo di aiutarmi?
      Per il resto, touchpad, tastiera, audio, batteria, ethernet e quant'altro vanno senza problemi.
       
      Grazie anticipatamente e allego la EFI
      EFI.zip
×