[Phillip]

Extract this

<li id=”d4p-bbp-attachment_13821″ class=”d4p-bbp-attachment d4p-bbp-attachment-zip bbp-atticon bbp-atticon-archive”>icnfirmware.zip

and copy the icnfirmware.sys to the following folder: C:\Windows\System32\Drivers and give admin rights when asked. Then reboot.

[Phillip]

@hachi

Hey buddy, in answer to the missing .dll I cannot find this .dll on the internet or in the folder that the flash tool runs from. I have searched my PC for it and have don’t have it. So that one is a mystery.

In response to the Windows 10 bootloops when installing the Insyde switcher to stop bootloops do this;

As the tablet is loading Windows 10 hold down the power button to force shut off, do this a couple of times and windows will start the auto-repair mode.  Once here navigate to the troubleshoot menu and choose the option that allows you to boot into safe mode. The tablet will restart and present you with several options. Choose safe-mode using the number at the front. (I think its number 4) Once in safe mode open windows explorer and navigate to the C:\Program Files\ and delete the Insyde folder. Now reboot and you will be able to boot fully. You can manually boot to either Android or Windows by holding Vol down and power then releasing power. You will get a windows icon and an Android one. Use volume rocker to select then power button to boot. The one that is flashing is the one that will boot.

Hope this helps

Phil

[Phillip]

@Steve the Android VID and PID need to be retrieved from Device manager after it’s in DNX mode. This is stopping you from booting temp into droidboot to start the flash!!

(An incorrect SOC VID & PID would not initiate the start(reboot to droidboot) as it wouldn’t recognise the device.  Then the Android VID & PID relate to once the device has rebooted and an incorrect one leaves you where you are. Check again change and save and retry)

[Phillip]

@Steve the Android VID and PID need to be retrieved from Device manager after it’s in DNX mode. This is stopping you from booting temp into droidboot to start the flash!!

(An incorrect SOC VID & PID would not initiate the start(reboot to droidboot) as it wouldn’t recognise the device.  Then the Android VID & PID relate to once the device has rebooted and an incorrect one leaves you where you are. Check again change and save and retry)

[Phillip]

Yes, mate. If you have not used diskclean to delete previous version of windows then you can go to the “All settings” then recovery and click revert to previous windows (8.1)

[Phillip]

Yes we have similar serials. Mine is: VI10PQ64G22150900*** I listed all bar the last three digits of my serial at the top of the guide. Please remember to use the USB 1.zip to create usb stick one and only use the usb2 folder (that contains the image folder)from the big file. hope you know what I mean.

[Phillip]

Did you switch the boot profile in bios to “windows” before you run the install procedure?

I have boot to Windows with the windows boot profile and lists the correct hardware. I managed to boot to windows using Android profile and device manager has loads more unknown devices. Change it back to Windows profile and device manager recognises the normal devices that it expects. Also after installing Android I left the Android profile whilst loading the USB 1 and  when running winpe it listed every partition it used for android and gave them drive letters. Put back to windows profile in bios and ran again, this time no problem. Must create USB 1 from the USB1.zip and just use the USB 2 that contains the windows .WIM files. When the script starts press control + c then y and enter. Type diskpart and press enter. Type list volume (or list volumes) This may give you an idea. You may need to manually assign the drive letters to the partitions from within diskpart. Then type exit and enter. Then change to USB drive letter say “e” so type e: and press enter. Then type startnet.cmd and press enter to continue. Shouldn’t need to do this though if using the correct USB folders and following the guide. (Saying that, the guide is what I did after a lot of mistakes, trail and errors, thats what worked for me. Will try to help you more if I can. Hope you get sorted)

Your friend Phil

[Phillip]

@ Mogan,

To be honest I’ve noticed a couple of times today when my tablet has had that problem when its come out of standby. I reboot though and Wifi is back. Does’t seem to affect bluetooth which I believe is on the same chip. It could be a power int failure. Try turning bluetooth off and rebooting. Maybe the power that doesn’t get distributed to bluetooth could provide a more stable wifi power init.

Glad it’s helped. I will keep an eye out for up to date drivers.

Also, has anyone else had phantom screens presses? Can get annoying sometimes, happens on both Windows and android but not all the time. Don’t know if its pressure on the screen, sensitivity or other. Will keep probing. 🙂

[Phillip]

@ Mogan in “Device Manager” are there any error codes etc?

[Phillip]

Please go here for the guide. Sorry it took so long, needed to wait for the uploads so I could create download links to include in the guide. I have put it in .docx and also .pdf as requested.

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

[Phillip]

Ok, so an update before I turn into bed. I have completed writing the guide. I’m just waiting on the second windows .zip file which has at this moment has uploaded 1.47GB out of 3GB then there are two small files I’m waiting on so I can get the links to include in the guide. I will start a new forum topic tomorrow once everything is in place. I am also uploading a video to youtube which I will link too. I’ve written the guide in Microsoft Word. But will probably make a .pdf also.

I’m gonna go to bed now. So I will update you in the morning.

Night guys and gals 🙂

[Phillip]

Worked perfect ladies and gents! I now have a fully functional Vi10 Pro 64gb emmc S165C Tablet with fully working Android (touch, Wifi, bluetooth) and everything works in windows! I mean everything. It is Windows 8 so you will need to upgrade but awesome!

I will write a guide in english as best as I can shortly. And will guide you through.

Phil

[Phillip]

So far this seems to be working. So when i publish part 1 and 2 of the Windows image, you will need to download both, extract all contents, set up usb 2 as ntfs and copy images folder to the root of that drive. Totally ignore usb1 folder. I will upload a working one separate. Along with Instruction/guide based on what I’ve done. Please be patient as part 1 of the windows .zip is nearly finished and part 2 is yet to upload and thats also 3gb.

[Phillip]

Yes, but it’s a bloody pest. They have messed up the windows install. I set up the fat 32 for USB 1 and NTFS for the images which are 5GB worth. during the winpe environment its formating my usb with the images on and setting up the usb as the windows drive, then complains because it can’t find the install.wim.

I’ve had to reflash Android again. Now gonna try setting up usb as normal and use the usb 1 folder to initiate the install. Wish me luck!!

[Phillip]

Hi Lucas,

Yeah, I’ve learn’t a hell of a lot about this tablet over the last week. The Windows image is in two files (a split .zip file if you know what I mean) The first part has finished and is currently uploading to my google drive account. The second part is has just five minutes left to download, then I can start uploading that part too. As it’s uploading I will be flashing. I’ll let you know once I’ve done it and post links once fully uploaded. Hope I can help you guys out. 🙂

Phil

[Author]

Posts