[WIP-Guide] HP ENVY x360 13-y013cl - i7-7500U Kaby Lake

[IcePiq]

There is no need to use emulated nvram on the 2017 X360 it has native NVRAM so i would ditch EmuVariableUefi-64 and remove the scripts that write nvram.plist to the efi partition on shutdown/reboot ... ensure that your clover config.plist is configured correctly for systemid .. suggest you read my imessage guide for tips and suggestions .. the guide you link to is a very basic one based on the info from my guide but gives no background information.

Cool. You are correct - your guide is the definitive volume on iMessage. I've found it very helpful in the past as well. The basic guide worked for me last time, but isn't working now that I've changed things up for legacy boot.

I've removed EmuVariableUefi-64 and the rc scripts from /etc/rc.boot.d/ . I also checked in IORegistryExplorer as suggested in Chapter 5 of your guide. It appears IODeviceTree:/efi/platform has no entry at all for system-id. My config.plist file definitely appears to be setting an SmUUID - but it's not working I guess. How can I check what's happening with the SmUUID?

 

[IcePiq]

JayMonkey (or others), I have the HP Envy x360 with the 1TB Hard Drive, otherwise identical to OPs. Did you encounter any end-of-installation crash issues which prevented a successful install? I think it may be linked to Sierra 12.5, as most of the attached clovers don't seem to have advanced beyond 12.3. Tried experimenting with Lilu & IntelFixGraphics, and making sure my NVMe kext was updated for 12.5, but to no avail. Maybe I need to revert to El Capitan?

When is it crashing? At the end of the OS X install process? If it's during install, run the installer with the console window open - does it tell you anything?

 

[Hhavoc]

So, I learned some more by trial and error: It was crashing always at the EXACT end of USB installation. Quick black screen with writing after the installtion finished counting down to Zero seconds. Then upon reboot to the new Apple OSx Hard Drive partition, it would switch to the installer, and then would give the error message, "OS cannot be installed". The earlier quick black-screen error message text always had to do with, "Assertion failed", which made me initially suspect IGFX, but that wasn't it.

It's something about the 1TB NVMe drive. I know this, because I tried installing instead using an external SSD connected via USB3. Perfect installation occurred. My HP Envy x360 has an internal 1TB Samsung PM961 (MZVLW1T0) M.2 NVMe, using the same ACPI SB.PCIO.RP05.PSXS BIOS address as the 256GB ones, so I naturally thought it would install as yours did. The internal drive Windows install originally had recovery partitions plus a small 16MB MSR, all of which I removed using DiskPart in attempts to solve this. Currently, the only partitions left are a 260MB FAT32-formatted EFI partition, 16MB of unallocated space (former MSR), 565GB NTFS Windows partition, then 388GB HFS-J partition for OSx.

I can't understand what about my 1TB internal drive with only a Fat32 EFI and Windows NTFS partition makes the OSx install process gag, but at this point, I'm wondering if my best bet is to CCC the successful partition from the OSx installed on my external SSD to the internal NVMe OSx partition. Anybody have experience doing something similar to this?

 

[IcePiq]

I'm wondering if my best bet is to CCC the successful partition from the OSx installed on my external SSD to the internal NVMe OSx partition. Anybody have experience doing something similar to this?

I've done exactly that, but used Apple Disk Utility instead of CCC. It worked fine. Back up before doing anything disk-related!

 

[jaymonkey]

I did not experience any of the end of install issues you report, my 2017 15" X360 (1TB Samsung SSD) runs 12.5 with no issues very stable .... However one thing to note to is that i did not install direct to the SSD but installed to a USB SSD (i used USB HUB in type A socket for install) once the OSX system was stable and debugged i used CCC to clone the OSX system to a partition on my SSD and then installed Clover as detailed in my post a few pages back ...

Cheers
Jay

 

[jaymonkey]

I also checked in IORegistryExplorer as suggested in Chapter 5 of your guide. It appears IODeviceTree:/efi/platform has no entry at all for system-id. My config.plist file definitely appears to be setting an SmUUID - but it's not working I guess. How can I check what's happening with the SmUUID?

I wrote the iMessage guide several years ago ... it was started well before Clover existed as such the sections on Clover really need updating as it's now the preferred method ... one thing to note is back then clovers magic wand function to generate smuuid ... etc was very unreliable hence the recommendation to use uuidgen. However Clovers ID/system def generator is pretty good these days .... i used it for my X360 ... i'm using MacBookAir7,2 as my system def .. just remember to use the shake buttons to randomize the build dates.

Ensure Inject System ID in System Parameters section is unchecked and leave custom UUID empty.

No issues with iM or FT for me ...

Looking forward to native Kaby Lake support soon which should extract more performance from the X360

Cheers
Jay

 

[jaymonkey]

It's something about the 1TB NVMe drive. I know this, because I tried installing instead using an external SSD connected via USB3. Perfect installation occurred. My HP Envy x360 has an internal 1TB Samsung PM961 (MZVLW1T0) M.2 NVMe, using the same ACPI SB.PCIO.RP05.PSXS BIOS address as the 256GB ones, so I naturally thought it would install as yours did. The internal drive Windows install originally had recovery partitions plus a small 16MB MSR, all of which I removed using DiskPart in attempts to solve this. Currently, the only partitions left are a 260MB FAT32-formatted EFI partition, 16MB of unallocated space (former MSR), 565GB NTFS Windows partition, then 388GB HFS-J partition for OSx.

As i explained in some of my earlier investigations in this thread i don't think its the m.2 drive but the way HP deals with UEFI/EFI booting, i did not remove any of the factory recovery or diagnostic partitions .. i used AOMEI Partition Assistant 6.1.0 to resize the windows partition and then created a OSX partition from the installer.

Then cloned my working OSX partition from my USB SSD to the internal m.2 SSD.

I also created several partitions to install linux ... a NTFS partition that is shared across all the OS's and also have a OSX Recovery Partition ..... this is what my 1TB SSD looks like :-

Cheers
Jay

 

[Hhavoc]

Thanks for the feedback, JayMonkey. Attempts to clone using CCC failed. Finally I tried using Gparted to physically move the Windows partition to the end, and shifted the EFI partition to eliminate the 1MB starting unallocated space. Formatting this as exFAT allowed successful installation. I'm a little fuzzy on what to keep in Clover Driver64UEFI & Kexts, vs what to load to L/E using KextBeast. Followed the iMessage Guide, and now have all things iCloud working great. I'm also on the latest BIOS. Anyone have a 12.5 Clover folder they can share, so I can compare? Also does it seem that the DSDT changed in the latest BIOS update?

 

[jaymonkey]

Glad you got iMessage back up and running ...

Not sure why you had such a hard time with the disk partitions .... i think exFAT is really only meant for large capacity USB memory sticks ...

I have not installed the latest BIOS update yet as i think its only needed to support the next release of windows which comes out later this year ... but i will get around to it at some point, might help with the UEFI wideness that seems to plague the latest HP Specter's and Envy Laptops ...

You should always re-dump and re-patch your DSDT and SSDT's after a BIOS update or changing any significant BIOS settings, use a compare utility to check for changes between the old and new native DSDT.

Cheers
Jay

 

[Hhavoc]

Ok, will do. (BTW, the exFat was only for temporarily making partition visible to installer. I of course formatted HFS+ for Install). Anyone willing to share their patch workflow? Seems most of you ignore the SSDTs, creating one for NVMe and CPU only. On the DSDT, I was removing the second BNUM, following Rehabman's suggested patches, but I'd like to crowdsource the best practices for patching this laptop, as well as preferred L/E kext lists, as I'm periodically having the sound fail (grey speaker menu bar icon), and only multiple reboots seem to get it back.

Also, am I right that only the Spectre supports Windows Hello? My Envy x360 shows not eligible in the settings.