[Teclast X98 Air 3G] tecknight:
TTT-Fix X98 Air Device's Touchscreen functionality in Android

TTT TecKnight's Teclast Tutorials series

Fix X98 Air Device's Touchscreen functionality in Android.

The touchscreen is working in Windows and on the BIOS Boot Select screen, but is no longer being detected by Android.

Why did this happen ? What is causing this problem ?

The cause of this issue is still not clear, but it appears that it may be some sort of partial component failure.

Why ? Because almost all of the tablets now exhibiting this problem did at one time work perfectly using the standard Android images and touchscreen kernel modules, but at some point they "broke". Teclast probably has a good idea what is causing this, as they have released a special boot image that is able to fix the problem in a good majority of the cases.

Good News

If you have this problem, the good news is:

1. You are not alone. This is actually a pretty common problem.

2. The fix is fast and easier to apply than ever and it works in nearly every case.

I have just created an easy installer that automatically copies the new boot image to the boot partition and then reboots the tablet.

Detailed instructions follow.

Procedure: Replace boot.img to enable touchscreen functionality in Android

Required:

1. Windows Host PC with adb drivers installed.

2. Teclast X98 Air device running Android 4.4.

3. USB A to Micro USB cable

4. FixTSinAndroid.zip archive containing replacement script and modified boot.img

Download FixTSinAndroid.zip
​

Step by Step instructions:

1. Extract FixTSinAndroid.zip archive to a folder on your Windows Host PC.

2. Ensure that your tablet has at least 50% battery charge.

3. Boot your tablet into Android.

4. Enable USB debugging in Android if not already enabled.

5. Connect your tablet to your Windows Host PC using the USB A to Micro USB cable.

6. On Host PC, browse to the folder where you extracted the FixTSinAndroid.zip archive.

7. Double click on the file FixTSinAndroid.bat. It should have a GEAR icon next to it.

You should see:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

Baytrail00F0C770 device

Waiting for device... Please connect using USB cable if necessary.

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

restarting adbd as root

Press any key to apply Android Touchscreen fix or CTRL-C to Exit

Press any key to continue . . .

8. If you wish to proceed and replace the boot image, press any key. If not Press CTRL-C to abort the script.

If you pressed a key other than CTRL-C, you will see:

3272 KB/s (10596352 bytes in 3.161s)

20696+0 records in

20696+0 records out

10596352 bytes transferred in 0.962 secs (11014918 bytes/sec)

New Boot image written. Press key to reboot

Press any key to continue . . .

9. Press a key and your tablet will reboot. Hopefully it will boot back up with the touchscreen working !!

Note: The script creates a detailed log called scriptlog.txt.

Post your scriptlog.txt here if you are having any problems.

Example scriptlog.txt from successful run:

FixTSinAndroid Started from C:\fixandroidts - Date=Sat 07/11/2015 Time= 5:45:25.86 OS=Windows_NT Username=Randy
Contents of C:\fixandroidts:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
FixTSinAndroid.bat
How to Install.txt
IntelAndroidDrvSetup1.9.0.exe
log1.txt
running "adb devices" output=
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Baytrail00F0C770 device

Waiting for device on USB bus
running "adb root" output=
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root
Awaiting User Confirmation
User pressed key, continuing
running "adb push boot.img /data/local/tmp/" output=
3272 KB/s (10596352 bytes in 3.161s)
running "adb shell dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p3" output=
20696+0 records in

20696+0 records out

10596352 bytes transferred in 0.962 secs (11014918 bytes/sec)

Awaiting reboot confirmation
Rebooting device

_________

Change Log:

7/15/2015 Created initial procedure.