Contribute
Register

Razer Blade 15 - High Sierra 10.13.6 - Success(-)

Status
Not open for further replies.
Is the 3 minute black screen fixed with whatevergreen patch / ssdt-pnfl patch on 17G2208 or 17G2307?
 
Last edited:
Then run the installinstallmacos.py script on another mac, let it download the file. It will download it as a .dmg, but once you open/mount it you will see the InstallMacOS.app in the mounted file and you can copy and paste it into the applications folder so you can make a bootable installer with Unibeast of that specific build.

Any reason why you went with Unibeast instead of the recommended method of creating a custom clover usb? I know unibeast removes a lot of the compatibility issues from the equation if that's the case.

I think I'm going to do a full install guide/write up soon to help people out. I just need the time to do so lol.

Yes, that would be great! I'm going to attempt mojave for the time being. Anything in particular I should be aware of? Thanks!
 
Is the 3 minute black screen fixed with whatevergreen patch / ssdt-pnfl patch on 17G2208 or 17G2307?

Almost! I'd say it's like 80% there. I actually just got back to this issue tonight. I'm using the patched version of WhateverGreen and the special version of the PNLF SSDT from the other thread that's dedicated to figuring out this issue, as you stated.

Right now I'm at 7 out of 9 reboots with full screen brightness and control, no black screen. The other 2 reboots have been to a black screen. So progress is being made for sure. Attached are the patched WhateverGreen, Lilu and PNLF incase any of you wanted to try it out.

If you're going to use the patched version you must use the bootflag: igfxcflbklt=opcode

For everyone else on this thread, more information can be found here: https://www.tonymacx86.com/threads/...ter-booting-coffeelake-uhd-630.261131/page-29
 

Attachments

  • Black Screen Patch.zip
    510.7 KB · Views: 69
Last edited:
Any reason why you went with Unibeast instead of the recommended method of creating a custom clover usb? I know unibeast removes a lot of the compatibility issues from the equation if that's the case.



Yes, that would be great! I'm going to attempt mojave for the time being. Anything in particular I should be aware of? Thanks!

I just used unibeast for the sake of ease, since it makes a bootable install with clover and it's never given me an issue. Couple of clicks and done.

As far as Mojave goes, you should be fine. Attached is my EFI folder, it should help you get to full functionality pretty quick. The EFI files I used for Mojave worked flawlessly for my 17G2307 build of High Sierra. You can use the config.plist for your USB installer to get the install to work without issue (you will probably need to do this), just don't use any other files in the EFI Clover folder, otherwise the installer will probably run into issues. Everything else gets added later after your install is complete and you're ready to boot off of your main drive.

Attached are the Kexts you need to install to L-E and the clover files you need to put in the EFI Drive.

Keep in mind you still need to patch your own DSDT to get the trackpad and battery indicator working and also OPT-10 SSDT needs to be patched if you want to disable the Nvidia card for battery life.

DSDT patching and the patches you need to apply are explained on this page, post #4: https://www.tonymacx86.com/threads/razer-blade-15-high-sierra-10-13-6-success.256954/page-13

OPT-10 SSDT patch is explained this page, post #5: https://www.tonymacx86.com/threads/razer-blade-15-high-sierra-10-13-6-success.256954/page-15



**There's a folder for Windows in the EFI folder, ignore it. Only use the files in the Clover folder. The Windows folder is from my Windows installation and I forgot to remove it before uploading. **
 

Attachments

  • EFI + Kexts.zip
    31.6 MB · Views: 88
Any reason why you went with Unibeast instead of the recommended method of creating a custom clover usb? I know unibeast removes a lot of the compatibility issues from the equation if that's the case.



Yes, that would be great! I'm going to attempt mojave for the time being. Anything in particular I should be aware of? Thanks!


Also incase you didn't see in previous posts, I forgot to mention this in the last comment to you, the one bug you will encounter is a 3 minute black screen at first boot. Currently working on a fix in a different thread and it's close to being resolved. There is a patch I posted 2 comments above that almost fixes it, some reboots will still boot to a black screen.

If you want to wait for the actual fully functional patch, the temporary fix so you don't have to wait 3 minutes for backlight is, once the laptop gets to the login screen, shut the lid and wait for the Razer logo to shut off and then open it back up and backlight will be working. It's more like a 1 minute issue that way instead of 3. This is only an issue at first boot from a shutdown or restart. You can put the laptop to sleep and you won't have this issue.
 
Also incase you didn't see in previous posts, I forgot to mention this in the last comment to you, the one bug you will encounter is a 3 minute black screen at first boot. Currently working on a fix in a different thread and it's close to being resolved. There is a patch I posted 2 comments above that almost fixes it, some reboots will still boot to a black screen.

If you want to wait for the actual fully functional patch, the temporary fix so you don't have to wait 3 minutes for backlight is, once the laptop gets to the login screen, shut the lid and wait for the Razer logo to shut off and then open it back up and backlight will be working. It's more like a 1 minute issue that way instead of 3. This is only an issue at first boot from a shutdown or restart. You can put the laptop to sleep and you won't have this issue.

Yes, I actually read through the entire thread :) Currently getting stuck in the middle of the mojave install (the one after rebooting from the usb installer). I have the mercury white blade which is on bios 1.06 which does not appear to have been released for download yet for the black models. It also does not have a lighted logo which is both good and bad I suppose.

Looks like I'll be forging slightly different path due to the different bios but at least it'll provide some insight into what's coming up for you guys ;) If I can't get mojave to install, I'll go back to high sierra.

FYI, I couldn't use an exact copy of your config.plist for the install because of certain post-install configs you had in there like the intel graphics ID. You also seem to be HFSPlus.efi instead of VboxHFS which unibeast uses now. Any reason for that?
 
Quick, concise update: did a fresh install using 17G2208, and got brightness control natively (what a relief). Correct screen resolution and profile instantly as well.
Got the WIFI/Bluetooth/Airport right effortlessly too.
It seems like (almost) everything's working but the trackpad (I'll succeed... eventually ;)). No matter what I do, I keep on failing...
Audio devices aren't recognized every now and then, but it might be quite different once I plug my external soundcard (electronic music producer / teacher here). I can't wait to finally install all my AUs and DAWs...

I'll have a look at your kext and EFI files vettz500, thank you so much! I'll probably do a fresh install once I get it all right and stable, and will document it / share it if anyone's then interested.
 
Yes, I actually read through the entire thread :) Currently getting stuck in the middle of the mojave install (the one after rebooting from the usb installer). I have the mercury white blade which is on bios 1.06 which does not appear to have been released for download yet for the black models. It also does not have a lighted logo which is both good and bad I suppose.

Looks like I'll be forging slightly different path due to the different bios but at least it'll provide some insight into what's coming up for you guys ;) If I can't get mojave to install, I'll go back to high sierra.

FYI, I couldn't use an exact copy of your config.plist for the install because of certain post-install configs you had in there like the intel graphics ID. You also seem to be HFSPlus.efi instead of VboxHFS which unibeast uses now. Any reason for that?

Have you tired booting back into the installer with Verbose to see what is hanging it up?

Honestly, the EFI folder had files in there from the very beginning of this thread that I got from someone else. They all always worked and I never had an issue, so I never changed them.
 
Quick, concise update: did a fresh install using 17G2208, and got brightness control natively (what a relief). Correct screen resolution and profile instantly as well.
Got the WIFI/Bluetooth/Airport right effortlessly too.
It seems like (almost) everything's working but the trackpad (I'll succeed... eventually ;)). No matter what I do, I keep on failing...
Audio devices aren't recognized every now and then, but it might be quite different once I plug my external soundcard (electronic music producer / teacher here). I can't wait to finally install all my AUs and DAWs...

I'll have a look at your kext and EFI files vettz500, thank you so much! I'll probably do a fresh install once I get it all right and stable, and will document it / share it if anyone's then interested.

Try using the Voodoo2IC, CHID and PS2 controller kexts in the folder I uploaded and see if the trackpad works then. As long as your DSDT is patched properly, it should work. You do have to add an IONameMatch to the Voodoo2IC Kext, I don't know if you saw that back on page 13 or not. If you use the kexts from my folder, that modification is already done and the kext is ready to read the trackpad for this laptop.

Can you post Problem Reporting Files? As well as your audio set up. I might be able to help you out with getting it all figured out.

Also I can confirm that if you're using an external audio interface, you won't have any issues with audio. Tested mine with an M32, Soundcraft Impact and a little Behringer 2 channel USB interface. All work natively, just plug and play.
 
Well, in my quest to get Audio over HDMI to work I have successfully enabled native audio on this laptop. VoodooHDA works, but it doesn't work all that well. Microphone didn't work, if the audio you're playing is too loud it would distort, speakers never got to full volume and it didn't automatically switch when you plugged in headphones.

All of those issues are solved with this, if anyone cares to use it.

Download the latest AppleALC Kext from here: https://github.com/acidanthera/AppleALC/releases
Install it to L-E. Rebuilt kextcache in terminal with sudo -i /

(If for some reason you're not using the Lilu kext, install it now, it's needed for this to work.)

Now either download my attached config.plist and use it (the easy way) to enable Audio or follow this to edit your own config.plist using XCode or PlistEditor.

First:
Check to make sure HDAS is renamed to HDEF (This should already be done, but double check)
Open your config.plist in Clover Configurator and in the Acpi section look in the patches and see if change HDAS to HDEF is there, if not click on List Of Patches and select HDAS to HDEF and add it.

From this point on use XCode or PlistEditor

Second:
Under Devices-Audio
Set Inject to Boolean and change it to NO

Third:
Under Devices-Properties add:
PciRoot(0x0)/Pci(0x1f,0x3)
layout-id Data <1d000000>

I attached a screenshot of what it should look like after you make both of the above changes.

Finally, reboot and enjoy 100% working audio!

Currently still working on HDMI audio, have not gotten it figured out yet.

If anyone would like to know:
Our specific Audio Codec is ALC298 and the Layout-id number is 29.
 

Attachments

  • Screen Shot 2018-10-25 at 10.51.09 PM.png
    Screen Shot 2018-10-25 at 10.51.09 PM.png
    99 KB · Views: 74
  • config.plist
    14.9 KB · Views: 139
Last edited:
Status
Not open for further replies.
Back
Top