Android device is not regognized

Unity Engine
,
1

After I updated to windows 10 I haven’t been able to deploy on Huawei Mediapad M1 8.0 with android 4.2.2
I’m using latest unity 5.2.1f1 and Java sdk 1.8.0_60 as well as adb 1.0.32

I have installed huawei mobile USB drivers 1.0 and device is shown as a external drive.

What i have tried so far, but with no luck:
Disabling avast premium
killing and starting adb server
rebooting both devices (laptop and pad)
USB debugging is enabled as well as unsafe sources

adb devices

List of devices attached



D:\Program Files (x86)\Android\android-sdk\platform-tools>adb nodaemon server
            main: 13928:13188 | Handling commandline()
bip_buffer_init: 13928:13188 | bit_buffer_init 00e22fe8
bip_buffer_init: 13928:13188 | bit_buffer_init 00e24028
  adb_socketpair: 13928:13188 | adb_socketpair: returns (100, 101)
init_transport_registration: 13928:13188 | socketpair: (100,101)  fdevent_update
: 13928:13188 | fdevent_update: add 1 to 101
event_looper_hook: 13928:13188 | event_looper_hook: call hook for 101 (new=0, ol
d=1)
      local_init: 13928:13188 | transport: local client init
device_poll_thread: 13928:13860 | Created device thread
   adb_auth_init: 13928:13188 | adb_auth_init
client_socket_thread: 13928: 5432 | transport: client_socket_thread() starting
get_user_keyfilepath: 13928:13188 | home 'C:\Users\Ville-Veikko'
    get_user_key: 13928:13188 | user key 'C:\Users\Ville-Veikko\.android\adbkey'

        read_key: 13928:13188 | read_key 'C:\Users\Ville-Veikko\.android\adbkey'

cannot bind 'tcp:5037': No error


D:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices -l
            main: 13332: 6440 | Handling commandline()
List of devices attached
       adb_query: 13332: 6440 | adb_query: host:devices-l
    _adb_connect: 13332: 6440 | _adb_connect: host:version
socket_loopback_client: 13332: 6440 | socket_loopback_client: port 5037 type tcp
=> fd 100
  WriteFdExactly: 13332: 6440 | writex: fd=100 len=4: 30303063 000c
  WriteFdExactly: 13332: 6440 | writex: fd=100 len=12: 686f73743a76657273696f6e
host:version
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4 got=4
4f4b4159 OKAY
    _adb_connect: 13332: 6440 | _adb_connect: return fd 100
     adb_connect: 13332: 6440 | adb_connect: service host:devices-l
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4 got=4
30303034 0004
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4
   ReadFdExactly: 13332: 6440 | readx: fd=100 wanted=4 got=4
30303230 0020
       adb_close: 13332: 6440 | adb_close: 100(lo-client:5037)
    _adb_connect: 13332: 6440 | _adb_connect: host:devices-l
socket_loopback_client: 13332: 6440 | socket_loopback_client: port 5037 type tcp
=> fd 101
  WriteFdExactly: 13332: 6440 | writex: fd=101 len=4: 30303065 000e
  WriteFdExactly: 13332: 6440 | writex: fd=101 len=14: 686f73743a646576696365732
d6c host:devices-l
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=4
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=4 got=4
4f4b4159 OKAY
    _adb_connect: 13332: 6440 | _adb_connect: return fd 101
     adb_connect: 13332: 6440 | adb_connect: return fd 101
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=4
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=4 got=4
30303030 0000
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=0
   ReadFdExactly: 13332: 6440 | readx: fd=101 wanted=0 got=0

D:\Program Files (x86)\Android\android-sdk\platform-tools>netstat -noa | findstr 5037
  TCP    127.0.0.1:5037         0.0.0.0:0              LISTENING       7640
  TCP    127.0.0.1:5037         127.0.0.1:55466        TIME_WAIT       0



D:\Program Files (x86)\Android\android-sdk\platform-tools>tasklist | findstr 7640
adb.exe                       7640 Console                    1      6 540 K
2

When you connect the device, does Windows trigger any sound? e.g: USB device connected ?

Does it get listed in Device manager ?