Chuwi Vi10 CWI505 fresh Windows 10 Enterprise x86 driver issues

[Frosty]

Just noticed this thread:

http://techtablets.com/forums/topic/chuwi-vi10-pro-64gb-fix-restore-etc/

Perhaps I will try the approach of reinstalling Windows 8.1 first, then an in-place upgrade to Windows 10.

[Frosty]

Ahhhhh … PROGRESS!!!

I spent quite a while re-reading in this thread:

http://techtablets.com/forums/topic/vi10-s165c-drivers-available-from-chuwi/

Noticed this download, where someone helpfully made available the Broadcom drivers from their working install:

http://techtablets.com/wp-content/uploads/2015/10/S165-19-10-2015-19-30-57.zip

Downloaded those drivers.  Copied the Broadcom folder over to the tablet (via my USB-Ethernet dongle).  Navigated into the driver folders via Windows Explorer and found the setup file (OEM22.INF), right-click, Install, ignore the warning.  Reboot.  Loaded up Device Manager and AT LAST I can see a functional WiFi Adapter in the Networking section of Device Manager.

RESULT:  after connecting and entering my password, I now have working WiFi at last.

Now I just need to find the magic sauce to get Touch drivers to be recognised.

[Frosty]

Thanks to Phillip for his efforts!  I downloaded his S165 drivers:

https://drive.google.com/file/d/0B_WhOdPMvW1OdjVic1J2elVGc28/view?usp=sharing

Found the Touch driver (in the TP folder) he’d used, manually installed that using the supplied ‘dpinst32.exe’ driver installer package (right-click, Run As Administrator).  This replaced the existing KMDF driver with a new MY12C driver in the Human Interface Devices section.

RESULT:  Touch is now functioning … sort of … calibration is not-quite-right, but at least I am getting some response.

 

[Frosty]

Calibration done.  Not quite sure what the magic sauce was, but I did try manually copying the ‘icnfirmware.sys’ and ‘MY12C.sys’ files to C:\Windows\System32\drivers\ folder.  After mucking about with that a bit, I went into the Calibration screen of Windows and attempted to tap away on the X to get it calibrated.  Not much success.  Then (I think it was after a reboot) I went back into the Calibration screen, dumped all the previous calibration data, and then was able to very easily re-calibrate it successfully. Works really well now.

I still have two objects in Device Manager which don’t have correct drivers.  In their Properties I can see these details:

(1) is in Other Devices, named “Generic SDIO Device”, has two Hardware IDs starting with ‘SD\VID’ (so is this a video driver???)

(2) is in Other Devices, named “Unknown Device”, has Hardware ID starting with ‘ACPI\BCM2E74’ (Broadcom? bluetooth maybe???)

[Frosty]

Google is telling me that:

ACPI = Advanced Configuration and Power Interface

SD\VID might be Standard Definition video (?)

[Ilya Dyachenko]

Hi, where I can get J1D_S165C_206 bios?

[Frosty]

http://techtablets.com/2015/09/chuwi-vi10-windows-10-image-bios-update-and-drivers-released/

[Frosty]

I have not been able to solve the last remaining driver issue … still have two objects in Device Manager which don’t have correct drivers. In their Properties I can see these details:

(1) is in Other Devices, named “Generic SDIO Device”, has two Hardware IDs starting with ‘SD\VID’ (Standard Definition video driver?)
(2) is in Other Devices, named “Unknown Device”, has Hardware ID starting with ‘ACPI\BCM2E74’ (Advanced Configuration and Power Interface?)

The other odd thing: if I type in “camera” and open the standard Windows 10 Camera app, it works. There is a Camera object in Device Manager. But in Windows 10 “Scanners and Cameras” area there is no camera evident. I think Windows is using some kind of generic Intel camera driver. Any suggestions as to how I could find the right Camera driver? I’ve tried all the ones posted so far, without success.

[Jean-Baptiste Dupont]

Hi Frosty

(Sorry for my poor english, I’m french)

I’ve exactly the same issues with the same bios on mu vi10 pro (which have only 32GB on the eMMC (!) , I’ve adispute in progress with my seller).

serial: vi10PQ64G2215090****

But I’ve an other big problem: After reinstallation of Android, I don’ find a fonctional rom. No tactil, no wifi for me in Android.

I’v tried other bios but without success

Is it possible to have a save about your functiunnaly android rom please?

Thanks a lot!

 

 

[Frédéric Gub]

Frosty, was is the exact serial number of your tab (wrote on the aluminium) Q32G22151000XXX??

[Frosty]

For Jean-Baptiste: I’m not very good with Android and I did not attempt to replace mine. I just found a way to switch it from Chinese to English by clicking on the right icons (even though I could not read the text on the screen). So I just left it with the original Android install. I am sorry if this does not help!

For Frédéric: my serial number starts with Vi10PQ64G2215090**** (same as Jean-Baptiste above)

[Jean-Baptiste Dupont]

Ok Frosty, no problem.

 

 

[Author]

Posts