Contribute
Register

Asus Vivobook Pro 17 N705U - Cloned SSD problem

Status
Not open for further replies.
Joined
Mar 31, 2014
Messages
62
Motherboard
ASUS VivoBook Pro 17 N705UD (Clover)
CPU
i7-8550U
Graphics
UHD620/GTX1050, 1920x1080

With a lot of help I managed to have a working computer 4 years without any problem.

Since I needed more space I've cloned my 256GB SSD to a 2TB SSD, the result is Clover is broken.

Neither MacOS or Windows 10 work, tried many hours to fix Clover but ended trying with OpenCore, after following the long install process now MacOS HighSierra is booting but except the display and the usb ports nothing else is working.

Not working :
- Asus Keyboard
- Fn Keys
- Brightness control
- ELAN 1300 (touchpad)

- ACL3251 (soundcard)

I can post my old clover if it helps and the new opencore folder, but I don't know where to start with this...

Some advice will be very welcomed.
 
Last edited:

With a lot of help I managed to have a working computer 4 years without any problem.

Since I needed more space I've managed to clone my 256GB SSD to a 2TB SSD, the result is Clover is broken.

Neither MacOS or Windows 10 work, tried many hours to fix Clover but ended trying with OpenCore, after following the long install process now MacOS HighSierra is booting but except the display and the usb ports nothing else is working.

Not working :
- Asus Keyboard
- Fn Keys
- Brightness control
- ELAN 1300 (touchpad)

- ACL3251 (soundcard)

I can post my old clover if it helps and the new opencore folder, but I don't know where to start with this...

Some advice will be very welcomed.
did you use a DSDT.aml with clover?
 
you have some very old kexts that needs to be updated...

AsusNBFnKeys.kext has been replaced with AsusSMC.kext

IntelGraphicsFixup.kext can be deleted, use latest version of whatevergreen.kext and lilu.kext

replace FakeSMC.kext with VirtualSMC.kext

replace ACPIBatteryManager.kext with SMCBatteryManager.kext

replace VoodooHDA.kext with AppleALC.kext


may be worth checking over:
 
I'm planning to update High Sierra, that's why I'm switching to OpenCore.
Tried so many things but no luck, it's booting but nothing works.
 

Attachments

  • OC.zip
    4.2 MB · Views: 38
I'm planning to update High Sierra, that's why I'm switching to OpenCore.
Tried so many things but no luck, it's booting but nothing works.
remove boot argument:
alcid=1

change your audio layout in:
PciRoot(0x0)/Pci(0x1b,0x0)
as per:
reset nvram on each try
 

With a lot of help I managed to have a working computer 4 years without any problem.

Since I needed more space I've managed to clone my 256GB SSD to a 2TB SSD, the result is Clover is broken.

Neither MacOS or Windows 10 work, tried many hours to fix Clover but ended trying with OpenCore, after following the long install process now MacOS HighSierra is booting but except the display and the usb ports nothing else is working.

Not working :
- Asus Keyboard
- Fn Keys
- Brightness control
- ELAN 1300 (touchpad)

- ACL3251 (soundcard)

I can post my old clover if it helps and the new opencore folder, but I don't know where to start with this...

Some advice will be very welcomed.
Yeah @Feartech's advice is great.

If it helps this video on YT helped me with my Windows rebuild >

For the touchpad you will need these files:

SSDT-GPIO.aml in /OC/ACPI
VoodooI2C.kext
VoodooI2CElan.kext
VoodooInput.kext
VoodooPS2Controller.kext
 
remove boot argument:
alcid=1

change your audio layout in:
PciRoot(0x0)/Pci(0x1b,0x0)
as per:
reset nvram on each try
Little progress today.

removing alcid=1 and setting layout-id=22 is not working even after clearing nvram.

but alcid=22 makes sound work???
 
Little progress today.

removing alcid=1 and setting layout-id=22 is not working even after clearing nvram.

but alcid=22 makes sound work???
the boot argument will over ride what you have in PciRoot(0x0)/Pci(0x1b,0x0) (assuming that is the correct path to your audio)

and always reset nvram when making any config.plist changes
 
the boot argument will over ride what you have in PciRoot(0x0)/Pci(0x1b,0x0) (assuming that is the correct path to your audio)

and always reset nvram when making any config.plist changes
Thank you, path was wrong, found the correct one with gfxutil.
 
Status
Not open for further replies.
Back
Top