Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,550 posts in this topic

Recommended Posts

hmm. ok. well it seems to work for many of us on T420. if i use the built-in EDID i get lots of glitches and buffer hangs. as soon as i use/inject this EDID - zero glitch - zero hangs.  sorry it does not work for you.

Share this post


Link to post
Share on other sites
Advertisement

hmm. ok. well it seems to work for many of us on T420. if i use the built-in EDID i get lots of glitches and buffer hangs. as soon as i use/inject this EDID - zero glitch - zero hangs.  sorry it does not work for you.

can you send me your clover config plist for boot?

Share this post


Link to post
Share on other sites

@AJ 

 

1)  /.IAbootfiles  or something like this is created by the installer on the OS partition you were upgrading by the Install OSX.app ...  if you have HFSplus.efi vs Vboxhfs.efi in your clover drivers folder, then clover can boot from this installer bundle upon reboot. (just like a real mac)

 

since you aborted the install process by not restarting using this bundle, you can get rid of this folder now.

 

2) the installer will create (or update) the recovery partition - which is a 650MB partition on your OS HD. ( i would keep this.)

Thank you guys. I have deleted the .IABootfiles and the "Install Mavericks from..." is no longer there, good.

 

And for the recovery partition, it is actually there. The problem is that it doesn't boot, it complains about the AppleHDA kext. I'm trying to install the modified kexts to the BaseSystem.dmg that is in the recovery partition to see if I can boot from it. It would be useful in case of problems.

I used the following command from terminal to enable debug mode in Disk Utility and view/mount hidden partitions from the debug menu:

defaults write com.apple.DiskUtility advanced-image-options -bool true

 

Once mounted, I have converted the read-only .dmg into a read-write, applied the custom kexts using Kext Wizard, then converted .dmg into a compressed .dmg, and replaced the BaseSystem.dmg into the Recovery Partition. It almost boots now... still looking at it...

Share this post


Link to post
Share on other sites

@aj - there is a much easier way to boot recovery partition!!! it is essentially the same thing as the USB installer - which requires extra kexts.

 

so stop at clover GUI

use clover shell to rename OEM so it's not in play for this and boot recoveryHD using the top level config.plist which will inject (custom) kexts from 10.9 

 

shell commands
 

map fs0

fs0:

cd /EFI/CLOVER

mv OEM OEM.NU

exit

Share this post


Link to post
Share on other sites

@aj - there is a much easier way to boot recovery partition!!! it is essentially the same thing as the USB installer - which requires extra kexts.

 

so stop at clover GUI

use clover shell to rename OEM so it's not in play for this and boot recoveryHD using the top level config.plist which will inject (custom) kexts from 10.9 

 

shell commands

 

map fs0

fs0:

cd /EFI/CLOVER

mv OEM OEM.NU

exit

hehe, that seems easier... indeed... I will try it...

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

@tluck "EDID seems to be 309x173?" I don't know (don't understand in fact)

send me the new edid when it's created, i'll test and feed back. :)

Share this post


Link to post
Share on other sites

@tluck, could you generate an EDID with that panel size for 1600x900? I tried all the EDIDs so far (except the one in post #629) and I'm still getting hangs and glitches (though rarely). I'm also on 1600x900.

Share this post


Link to post
Share on other sites

take 2 on EDID HD3000 fix.

 

OK this theory is working in practice!  Theory: bogus panel size was the culprit

 

I changed just the panel size from 309x174 to 310x174. I can't get a glitch/hang on 10.8.5 or 10.9.0 using this edited EDID info.

It was NOT sync sizes as i originally thought - that attempt eventually hung.

 

tetonne - your EDID seems to be 309x173? maybe if i gen one that has 310x174 for 1366x768 resolution? i will post a new one test EDID later.

i noticed these EDIDs (mine too) specify a max size to be 310x170 but the panel was set to be only 309mm... it stands to reason the max cannot be bigger than the panel!

 

more info from revised post             #629            

Can you generate a new edid for 1600x900? And explain which parts(number) to change?

Thanks i ll try

 

i have already tried your edid with 36AE10 but no luck, always glitch

Share this post


Link to post
Share on other sites

@honeywell - see post 629 ... and the clover bundle has this same working (for me ?!) EDID for 1600x900.  the OEM 1600.900 config.plist is set up to inject the EDID and i also put in the DSDT (for non-clover).

 

... i don't know why this particular EDID works for me (and others ) but not for all.  

 

if you are NOT injecting this EDID (with product 2e2) , then please run : ioreg -l |grep EDID and post the EDID - maybe we can make sense of it and get a working one. 

Share this post


Link to post
Share on other sites

@yum - i will look at this post.  but I already have LCD brightness (16 levels)

 

so i took at look at  your ioreg EDID dump. and the first thing i noticed is you have 1600x900 but its on a 17" vs 14" so here is an EDID that you could try that has the same info - but i tweaked the params slightly (changed) to match the values work for me but with proper sizing.

 

see 4 value changes on line 50

 

your EDID

post-954945-0-86085500-1383763286_thumb.png

 

new EDID to test - take string below and put in Clover config.plist

post-954945-0-81117500-1383763300_thumb.png

 

 

00FFFFFFFFFFFF000DAF19170000000005130103802716780A08059D58539729155054000000010101010101010101010101010101018025408060841A30302035007ED710000018000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C

 

                          DDCTest For: CMO 
______________________________________________________________________
______________________________________________________________________
EDID Block 0, Bytes 0-127
128 BYTES OF EDID CODE:
         0   1   2   3   4   5   6   7   8   9
      ________________________________________
  0  |  00  FF  FF  FF  FF  FF  FF  00  0D  AF
 10  |  19  17  00  00  00  00  05  13  01  03
 20  |  80  27  16  78  0A  08  05  9D  58  53
 30  |  97  29  15  50  54  00  00  00  01  01
 40  |  01  01  01  01  01  01  01  01  01  01
 50  |  01  01  01  01  80  25  40  80  60  84
 60  |  1A  30  30  20  35  00  7E  D7  10  00
 70  |  00  18  00  00  00  00  00  00  00  00
 80  |  00  00  00  00  00  00  00  00  00  00
 90  |  00  00  00  00  00  00  00  00  00  00
100  |  00  00  00  00  00  00  00  00  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  4C
______________________________________________________________________
(08-09)  ID Manufacturer Name ________________  = CMO
(11-10)  Product ID Code _____________________  = 1719
(12-15)  Last 5 Digits of Serial Number ______  = Not Used
(16)     Week of Manufacture _________________  = 05
(17)     Year of Manufacture _________________  = 2009
(10-17)  Complete Serial Number ______________  = See Descriptor Block
(18)     EDID Version Number _________________  = 1
(19)     EDID Revision Number ________________  = 3
(20)     VIDEO INPUT DEFINITION:
         Digital Signal
         Non - VESA DFP 1.x Compatible                        
                        
(21)     Maximum Horizontal Image Size ________________    =  390 mm
(22)     Maximum Vertical Image Size __________________    =  220 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         Preferred Timing Mode
         Display Type = R/G/B Color
(25-34)  CHROMA INFO:
         Red X - 0.613 Green X - 0.326 Blue X - 0.160 White X - 0.313
         Red Y - 0.344 Green Y - 0.590 Blue Y - 0.082 White Y - 0.329
(35)     ESTABLISHED TIMING I:
(36)     ESTABLISHED TIMING II:
(37)     Manufacturer's Reserved Timing:
           None Specified
(38-53)  Standard Timing Identification:
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
______________________________________________________________________
(54-71) Detailed Timing / Descriptor Block 1:
                   1600x900  Pixel Clock: 96.00 MHz
______________________________________________________________________
         Horizontal Image Size: 382 mm     Vertical Image Size: 215 mm
         Refreshed Mode: Non-Interlaced    Normal Display - No Stereo
 
Horizontal:
         Active Time: 1600 pixels          Blanking Time: 128 pixels
         Sync Offset: 48 pixels            Sync Pulse Width: 32 pixels
         Border: 0 pixels                  Frequency: 55.56 KHz
 
Vertical:
         Active Time: 900 lines            Blanking Time: 26 lines
         Sync Offset: 3 lines              Sync Pulse Width: 5 lines
         Border: 0 lines                   Frequency: 60.00 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
(126)    
(127)    
 

Share this post


Link to post
Share on other sites

 

00FFFFFFFFFFFF000DAF19170000000005130103802716780A08059D58539729155054000000010101010101010101010101010101018025408060841A30302035007ED710000018000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004C

 

i try it but with out surprise 1600 goes outside of my screen ;)

resolution is preferences/Screen are not as good as the one i have with 00FFFFFF FFFFFF00 06AF3C31 00000000 00140103 801F1178 0A10B697 58579226 1E505400 00000101 01010101 01010101 01010101 0101121B 56465000 23303020 360035AD 10000018 0000000F 00000000 00000000 00000000 00200000 00FE0041 554F0A20 20202020 20202000 000000FE 00585858 58585858 58585831 200A0023 

and /S/L/Display/Over.. config (see a previous post i send with my config (I use dualink 0)

@tluck could u please try your customize with the EDID i'm using ;)

DisplayVendorID-6af/DisplayProductID-313c

Share this post


Link to post
Share on other sites

@tetonne

- that EDID is only for YUM (or others) with 17" LCD 1600x900!

 

are you getting glitches or hangs with your default/built-in EDID? you have 1366x768 native LCD?

 

here one for you with just the panel size changed - for 14" 1366x768. from 309x173 to 310x174mm

 

00FFFFFFFFFFFF0006AF3C310000000000140103801F11780A10B597585792261E505400000001010101010101010101010101010101121B5646500023302616360036AE10000018000000000000000000000000000000000000000000FE0031333636783736380A2020202000000000000000000000000000000000000000A6  

 

 

                            Time:  13:33:08
                        Date:  Tue Nov 05, 2013
______________________________________________________________________
______________________________________________________________________
                        VIEWSONIC CORPORATION
                    EDID Version # 1,  Revision # 3
                          DDCTest For: AUO 
______________________________________________________________________
______________________________________________________________________
EDID Block 0, Bytes 0-127
128 BYTES OF EDID CODE:
         0   1   2   3   4   5   6   7   8   9
      ________________________________________
  0  |  00  FF  FF  FF  FF  FF  FF  00  06  AF
 10  |  3C  31  00  00  00  00  00  14  01  03
 20  |  80  1F  11  78  0A  10  B5  97  58  57
 30  |  92  26  1E  50  54  00  00  00  01  01
 40  |  01  01  01  01  01  01  01  01  01  01
 50  |  01  01  01  01  12  1B  56  46  50  00
 60  |  23  30  26  16  36  00  36  AE  10  00
 70  |  00  18  00  00  00  00  00  00  00  00
 80  |  00  00  00  00  00  00  00  00  00  00
 90  |  00  00  00  FE  00  31  33  36  36  78
100  |  37  36  38  0A  20  20  20  20  00  00
110  |  00  00  00  00  00  00  00  00  00  00
120  |  00  00  00  00  00  00  00  A6
______________________________________________________________________
(08-09)  ID Manufacturer Name ________________  = AUO
(11-10)  Product ID Code _____________________  = 313C(<1)
(12-15)  Last 5 Digits of Serial Number ______  = Not Used
(16)     Week of Manufacture _________________  = 00
(17)     Year of Manufacture _________________  = 2010
(10-17)  Complete Serial Number ______________  = See Descriptor Block
(18)     EDID Version Number _________________  = 1
(19)     EDID Revision Number ________________  = 3
(20)     VIDEO INPUT DEFINITION:
         Digital Signal
         Non - VESA DFP 1.x Compatible                        
                        
(21)     Maximum Horizontal Image Size ________________    =  310 mm
(22)     Maximum Vertical Image Size __________________    =  170 mm
(23)     Display Gamma ________________________________    =  2.20
(24)     Power Management and Supported Feature(s):
         Preferred Timing Mode
         Display Type = R/G/B Color
(25-34)  CHROMA INFO:
         Red X - 0.590 Green X - 0.340 Blue X - 0.150 White X - 0.313
         Red Y - 0.345 Green Y - 0.570 Blue Y - 0.120 White Y - 0.329
(35)     ESTABLISHED TIMING I:
(36)     ESTABLISHED TIMING II:
(37)     Manufacturer's Reserved Timing:
           None Specified
(38-53)  Standard Timing Identification:
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
         Not Used
______________________________________________________________________
(54-71) Detailed Timing / Descriptor Block 1:
                   1366x768  Pixel Clock: 69.30 MHz
______________________________________________________________________
         Horizontal Image Size: 310 mm     Vertical Image Size: 174 mm
         Refreshed Mode: Non-Interlaced    Normal Display - No Stereo
 
Horizontal:
         Active Time: 1366 pixels          Blanking Time: 70 pixels
         Sync Offset: 38 pixels            Sync Pulse Width: 22 pixels
         Border: 0 pixels                  Frequency: 48.26 KHz
 
Vertical:
         Active Time: 768 lines            Blanking Time: 35 lines
         Sync Offset: 3 lines              Sync Pulse Width: 6 lines
         Border: 0 lines                   Frequency: 60.10 Hz
 
Digital Separate, Horizontal Polarity (-) Vertical Polarity (-)
 
 
______________________________________________________________________
(72-89) Detailed Timing / Descriptor Block 2:
 
         
 
 
______________________________________________________________________
(90-107) Detailed Timing / Descriptor Block 3:
 
         ASCII Data:
         1366x768
 
 
______________________________________________________________________
(108-125) Detailed Timing / Descriptor Block 4:

Share this post


Link to post
Share on other sites

 

are you getting glitches or hangs with your default/built-in EDID? you have 1366x768 native LCD?

 

00FFFFFFFFFFFF0006AF3C310000000000140103801F11780A10B597585792261E505400000001010101010101010101010101010101121B5646500023302616360036AE10000018000000000000000000000000000000000000000000FE0031333636783736380A2020202000000000000000000000000000000000000000A6  

No glitches or hangs on my 1600x900 and 1376x768 with dualink 0 (dualink 1 doesn't work here)

but better customs are welcomed :)

 

I test the EDID provided 

my feed back here :

 

post-638501-0-90722100-1383768364_thumb.jpg

One more thing : Thanks tluck

Share this post


Link to post
Share on other sites

@tluck, thanks for your hard work on this, it's appreciated really.  I have the same edie like yum, i have controlled it by yum link in some previous post. I think that also laptop is probably same family with same screen 1600x900 on 17 inch. 

So i try your custom edie, i have past it directly in display/overrides and it is seen correctly but i have always artifacts, after 2-3 reboot or something of similar. Problem for me is still unsolved for now. I can try other if you have other ideas. I think that will be same for iim cause original edie is the same. 

But why all this is happen on clover instead on chameleon (and/or smcping daemon) there is not this artifacts problem?

Btw thanks 

Share this post


Link to post
Share on other sites

@Smith@@ - how are you injecting the EDID? i found that putting one in /S/L/Displays/Overrides does not actually override the built-in EDID! However, I found that if I put a new/different EDID in the DSDT or inject by clover then the system will use it. it seems that if the system can find one in the LCD hardware, it will use it versus use one in an Override file.

 

I have been trying to figure out what is special about the EDID that works for me versus the built-in. i don't know why my built-in EDID is glitchy but an alternative EDID is absolutely perfect. And i had glitches on Chameleon/MBR before i switched to Clover. 

Share this post


Link to post
Share on other sites

@tluck i think that your theory about override is right because with same edid in previous post, that for yum (my model is in fact exactly the same), if i override it in display/overrides and so in vanilla method, i see in profiler that name is correct (LCD HP in this case) but override is probably not complete, if instead use the same last edie in clover i have completely black screen after all loading verbose end screen begin always more bright, it throb, vibrates and then nothing.

 

So i think that i must try all from clover. Can you make a new edie for testing? ;)

 

Ed: i have another question, now i have injected original edid with clover. But The COMMENT in graphics setting, in this case i choose "GLITCHES?" is different from name in monitor profiler, i mean, name is taken always from original override in Display/Overrides. But i think that clover EDID is working cause with previous edid had black screen with original not. But about name is right? There should be also an override of COMMENT parameter from clover?

Share this post


Link to post
Share on other sites

@tluck i think that your theory about override is right because with same edid in previous post, that for yum (my model is in fact exactly the same), if i override it in display/overrides and so in vanilla method, i see in profiler that name is correct (LCD HP in this case) but override is probably not complete, if instead use the same last edie in clover i have completely black screen after all loading verbose end screen begin always more bright, it throb, vibrates and then nothing.

 

So i think that i must try all from clover. Can you make a new edie for testing? ;)

 

Ed: i have another question, now i have injected original edid with clover. But The COMMENT in graphics setting, in this case i choose "GLITCHES?" is different from name in monitor profiler, i mean, name is taken always from original override in Display/Overrides. But i think that clover EDID is working cause with previous edid had black screen with original not. But about name is right? There should be also an override of COMMENT parameter from clover?

Yup, it's same DV7 hp ;)  

 

@tluck, thanks so much for all help. I have done same smith@@ tries and result is the same. Now i'm starting to inject the edid directly from clover. I will test your other edid

Share this post


Link to post
Share on other sites

@Smith@@ and Yum

 

this is what you need to put in your config.plist - it this is a modified EDID (detailed timing section) but has the same product/vendor.

 

<key>Graphics</key>

<dict>

<key>Comment</key>

<string>HP 17" 1600x900</string>

<key>CustomEDID</key>

<data>

AP///////wANrxkXAAAAAAUTAQOAJxZ4CggFnVhTlykVUFQAAAABAQEBAQEB

AQEBAQEBAQEBgCVAgGCEGjAwIDUAftcQAAAYAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEw=

</data>

<key>DualLink</key>

<string>1</string>

<key>Inject</key>

<dict>

<key>Intel</key>

<true/>

</dict>

<key>InjectEDID</key>

<true/>

</dict>

Share this post


Link to post
Share on other sites

@Smith@@ and Yum

 

this is what you need to put in your config.plist - it this is a modified EDID (detailed timing section) but has the same product/vendor.

 

Graphics

Comment

HP 17" 1600x900

CustomEDID

AP///////wANrxkXAAAAAAUTAQOAJxZ4CggFnVhTlykVUFQAAAABAQEBAQEB

AQEBAQEBAQEBgCVAgGCEGjAwIDUAftcQAAAYAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEw=

DualLink

1

Inject

Intel

InjectEDID

 

In test, but i see already one artifact, but still in testing.  But before question, i should see this: HP 17" 1600x900 in System Preferences --> Monitor --> Colors ?

 

Or not, because seems that name is not override correctly..

 

Edit: artifacts again.. :(     but i don't understand about before question, if edie is override correctly

Share this post


Link to post
Share on other sites

Maybe chameleon and clover read something in different way. Common problem is artifacts on clover and more less (avoid totally with smcping daemon) on chameleon. If i can understand what is that "something", but honestly i have done practically every form of tries LOL

 

 

Can be also my 16 GB of ram, but i had the same problem also with 8. On mavericks then patch intel kext for "downgrade" gram is not work. It see for intel always 512 MB of ram

Share this post


Link to post
Share on other sites

No glitches or hangs on my 1600x900 and 1376x768 with dualink 0 (dualink 1 doesn't work here)

but better customs are welcomed :)

 

I test the EDID provided 

my feed back here :

 

attachicon.gifnull

One more thing : Thanks tluck

Can you post me your ML intel kext, frame buffer an hd3000? I am on mavericks but i want do a try..

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 Reel
      All work 10.10, 10.11, 10,12
      camera not work in 10.13, 10.14
      You need SwitchResX that the screen does not freeze
      Custom resolutions: Back porch - lines change to 2
      UEFI boot moded bios https://github.com/Thiblizz/l502x-modded-bios
       
      For 10.14 you need: HD3000 Fix for Mojave.zip
      Installed in S/L/E 
       
      SMBIOS: MacbookPro 8.3 or MacbookPro 9.1
       
       

       

       
       
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By SepehrM
      I'm trying to install High Sierra 10.13.3 on an ASUS N552VW laptop, and I get stuck after this message:
      "could not recover SATA HDD after 5 attempts, terminating" 
      And some other warnings afterwards.
      Specs:
      CPU: Intel Skylake 6700HQ 2.6GHz
      RAM: 16GB DDR4
      2TB HDD + 128GB SSD
      GPU: Intel HD Graphics 530 + Nvidia GTX960m
      I'm installing using a 16GB USB3 flash drive on one of HDD volumes (UEFI Mode)
       
      I uploaded the verbose log and clover config.plist
      config-new.plist

    • By Leinad12
      Olá a todos.
      Estou com o macOS Mojave instalado num Lenovo 305 (com um i3 5005 e uma HD 5500) porém tou com um problema.
      Sempre que o computador entra em pausa (Sleep) não consigo voltar a "acordar" (Wake).
      Alguém pode me ajudar pf?
×