[Tom]

Hi, how do you have opened it?

I would like to take a look but I don’t want to break anything…

thank you

T0m

[Tom]

Hi,

wifi problem is strange, since the x98 pro chipset (RTL8723BS) appears to be on the supported modules of  android-x86

source:

https://sourceforge.net/p/android-x86/kernel/ci/android-x86-6.0-r2/tree/drivers/staging/

for the inverted digitizer try to open /system/build.prop with any root explorer and try adding the following line:
ro.sf.hwrotation=180
Save it and be sure to check permission are set to rw-r–r–
Reboot

source: https://forum.xda-developers.com/general/help/how-to-fix-inverted-upside-touchscreen-t2866130

as soon as I have some time I will give it a try myself.

BTW: thanks of the info provided

[Tom]

Probably they mishandled something while they flashed english version of windows.

I can assure the tablet fully works and dual boots.

Whatever way you want to handle it you need a working PC with windows (7 or up on it).

Tablet needs to be put in “fastboot mode” (like android phones and tablets, but since it’s intel and not arm based it’s “dnx” mode) to reupload system image.

Try to follow these instructions:HOW TO: dualboot Android/Windows on K9C3

Since you have K9C6 and not the old K9C3 you just need to follow from point 4 onwards.

Otherwise you could try to get hold of an updated windows version, create a usb drive, boot to bios (press f7 when black screen with teclast logo appears) with keyboard and usb key attached to powered micro usb hub and install fresh pointing to old windows partition, and format it (second last partition of the internal disk) otherwise, you risk to hose android partitions.

If you are going for a fresh install just remember to download all the drivers in advance (use doubledriver to install) you can find them in download section of the techtablets site.

All the best

 

[Tom]

Many thanks for the info.

I know it’s unrelated but I think that install.wim + wimboot was a much safe way to manage a resilient system.

I have taken a look at the disk structure and it seems we have 2 efi partition,

I assume boot menu is in bios and it points directly to 1 of the 2 uefi partition ignoring the other.

Probably a boot loader like clover could be a more clean solution but this way you are not messing with os installs…

anyway I am still curious about the disk structure,  -BTW android partitioning looks like a real mess!

 

[Author]

Posts