[Android General] charlestek:
[MENTION=7184758]charlestek[/MENTION] What exactly happens when you connect the tablet to the PC (tablet being turned off)?

Do you get the "USB device connected" sound effect in Windows, followed shortly by the "USB device disconnected" sound effect?

In your screenshot, the COM devices are translucent (=disconnected). Does one of them turn briefly solid when you connect the tablet?

On my machines, I don't have this "MTK USB Port" entry, by the way. Only "MediaTek PreLoader USB VCOM Port".

Just recently I installed "my" driver on my Win 8.1 notebook, and had zero problems. Well, first it didn't work, because I forgot to disable driver signature enforcement. So, I disabled it, installed the driver again, rebooted, and it worked.[/QUOTE]

[MENTION=5919159]Tzul[/MENTION]

Yes, when I initially plug the usb connector in, I get the funny connect noise and the device manager rolls up and down and then the device is disconnected. I get a balloon saying that the driver installed correctly as well. Just that after the process, the port in the device manager stays ghosted in grey (Am using show_non_present_devices), saying the device is not now connected. I am in test mode on the Win 7 64 bit OS system.

The very first time, the driver shows up as MT65xx preloader for which driver can't be found and then I updated the driver using the inf for the drivers from the link you gave me. In addition, from googling, I have found at least a half dozen other drivers from Mediatek, even one package that installs the Google usb drivers as well plus some other Microsoft drivers. I have been able to get none of these to work, save one single time on my Win 7 32 bit system when I momentarily got SPFT to readback the first row in the scatter file. That happened under some strange circumstance where I had in frustration installed multiple versions of drivers in succession. Then it never worked again.

It is interesting that the download you gave me, it contains another ? alternative usbser.sys, which I compared the hash for what the inf file itself relies on, which is the built in Microsoft system32\DRIVERS\usbser.sys "Usb Serial emulation modem driver" The hashes are not the same, so the original Microsoft system32\DRIVERS\usbser.sys does not get replaced by the file included in your preloader driver folder.

Contrary to the picture I showed, subsequent uninstalls (via deleting the oem*.inf files in c:\windows\inf and reinstalls, have not detected the plain Vcom usb driver, only the vcom preloader.

[IMG="Altered Usbser.sys file for Vcom Preloader"]https://db.tt/8xGJIQLl[/IMG]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0E8D&PID_2000\6&a59b994&0&4]

"DeviceDesc"="@oem73.inf,%mtk_preloader%;MediaTek PreLoader USB VCOM Port"

"Capabilities"=dword:00000084

"HardwareID"=hex(7):55,00,53,00,42,00,5c,00,56,00,49,00,44,00,5f,00,30,00,45,\

00,38,00,44,00,26,00,50,00,49,00,44,00,5f,00,32,00,30,00,30,00,30,00,26,00,\

52,00,45,00,56,00,5f,00,30,00,31,00,30,00,30,00,00,00,55,00,53,00,42,00,5c,\

00,56,00,49,00,44,00,5f,00,30,00,45,00,38,00,44,00,26,00,50,00,49,00,44,00,\

5f,00,32,00,30,00,30,00,30,00,00,00,00,00

"CompatibleIDs"=hex(7):55,00,53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,\

5f,00,30,00,41,00,26,00,53,00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,\

00,30,00,30,00,26,00,50,00,72,00,6f,00,74,00,5f,00,30,00,30,00,00,00,55,00,\

53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,41,00,26,00,53,\

00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,30,00,00,00,55,00,\

53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,41,00,00,00,00,\

00

"ContainerID"="{94c116a0-e5f8-11e5-a74f-001fc6488cf1}"

"ConfigFlags"=dword:00000000

"LocationInformation"="Port_#0004.Hub_#0009"

"ClassGUID"="{4d36e978-e325-11ce-bfc1-08002be10318}"

"Driver"="{4d36e978-e325-11ce-bfc1-08002be10318}\\0002"

"Class"="Ports"

"Mfg"="@oem73.inf,%mtk%;MediaTek Inc."

"Service"="usbser"

"FriendlyName"="MediaTek PreLoader USB VCOM Port (COM8)"