[Sony Xperia XZ Premium Guides, News, & Discussion] smiley.raver:
so this is not my first time rooting Xperia phones - but this new method - I have followed the steps but keep getting the following error:

on xperifix it installs recovery, then it gets stuck on open booting the recovery to which i follow the new instructions - unplug cable , hold vol + until device vibrates 3 times hold vol down boot recovery

plug in and click ok

xpfix to continue

but then i get the following errors:

Log File"

10-4-2018_09-30-25 ===> Flash TWRP

target reported max download size of 536870912 bytes

sending 'recovery' (21692 KB)...

OKAY [ 0.679s]

writing 'recovery'...

OKAY [ 0.003s]

finished. total time: 0.682s

10-4-2018_09-30-31 ===> Boot TWRP

downloading 'boot.img'...

OKAY [ 0.822s]

booting...

OKAY [ 5.793s]

finished. total time: 6.615s

10-4-2018_09-34-36 ===> Mount /system

error: no devices/emulators found

10-4-2018_09-34-39 ===> List /system

error: no devices/emulators found

10-4-2018_09-34-42 ===> List credmgr files

error: no devices/emulators found

10-4-2018_09-34-43 ===> Remove credmgr files

error: no devices/emulators found

10-4-2018_09-34-44 ===> List credmgr files

error: no devices/emulators found

10-4-2018_09-34-46 ===> Pull system file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-47 ===> Push system file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-48 ===> Push lib file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-49 ===> Push lib file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-50 ===> Push lib file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-51 ===> Push lib file

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-34-52 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-53 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-54 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-55 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-56 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-57 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-58 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-34-59 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-01 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-02 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-03 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-04 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-05 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-06 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-07 ===> Change file attributes

error: no devices/emulators found

10-4-2018_09-35-08 ===> Push XperiFIX Flasher

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-35-09 ===> Push Magisk

adb: error: failed to get feature set: no devices/emulators found

10-4-2018_09-35-10 ===> Run Xperifix Flasher

error: no devices/emulators found

10-4-2018_09-35-11 ===> Flash Magisk

error: no devices/emulators found

10-4-2018_09-35-12 ===> Wipe Cache

error: no devices/emulators found

10-4-2018_09-35-13 ===> Wipe Dalvik

error: no devices/emulators found

10-4-2018_09-35-15 ===> Reboot

error: no devices/emulators found

"

Phone is booting as per normal - DMR Fix not installed - nor magisk

I do have USB debugging on etc, so I'm not sure what I'm missing???

is there away to flash these manually (which I'm assuming is what the app is basically doing except on an automated script)

EDIT - I have just checked fastboot devices & adb devices and my device is not showing - so why would this not happen?

EDIT EDIT - It helps if i had the correct ADB drivers installed - this has now worked perfectly - [MENTION=8363210]sToRm//[/MENTION] Brialliant job