2. Extract the installer from the archive and run it. If the installer reports that the drivers are already installed, allow it to uninstall the existing drivers before installing.
3. Congratulations. You have installed the Intel adb drivers ver 1.10.0
_________Change Log:9/11/2015 Updated Intel driver link to IntelAndroidDrvSetup1.10.0.zip7/21/2015 Created initial procedure.

Update the BIOS on your X98 Air II/3G to the latest dual boot version (2.02)

Frequently asked questions:What are the advantages/reasons for updating my BIOS to version 2.02
1. BIOS 2.02 fixes a major power drain issue in Windows sleep mode, slashing the power consumption by 80% when in sleep mode under Windows.
2. BIOS 2.02 enables Boot to other OS functionality from both Windows and Android. This allows you to simply click a Boot to Windows or Boot to Android icon to cause the device to immediately reboot and then launch the other OS.
3. Other minor fixes included in 2.02 update.

Which models of X98 Air II/3G is BIOS version 2.02 compatible with ?
BIOS 2.02 is designed to be compatible with all variants of the X98 Air II/3G.
At the time this instruction was published, 2.02 had been reported successfully flashed to virtually all Air models.
It is not known to be incompatible with any models.

What about other BIOS versions ? Can I use your script to flash them ?
Yes you can. I will keep the flash archive updated with what I consider the latest official Teclast BIOS that has proven to be safe to flash.
That is currently version 2.02.
If you wish to flash a different image, simply follow the instructions in Step 2.

Determine your current BIOS version (coming soon)

IMPORTANT !! READ FIRST !!Before you attempt this procedure:
1. There is ALWAYS a chance something might go wrong when flashing a BIOS image, even when the image is correct for your device.
When BIOS flashing goes awry, it can result in a "brick", meaning the tablet reponds like a brick. A bricked device will not power up or display anything. It is basically out of commission.
The only way to recover from a brick is to open your case and use a CH341A BIOS flasher like this one:http://www.ebay.com/itm/24-25-Series.../161436716985?
These instructions attempt to minimize your risk by using the update method with the highest success rate, which is using adb and android to flash the BIOS.
Indeed, reports of bricked tablets when using this flashing method are very rare.
Only you can decide if the benefits from updating to 2.02 are worth the risks. By continuing with this procedure, you are assuming all risk for what might happen to your tablet.
2. The BIOS image as shipped from the factory contains an embedded unique Windows 8.1 software license key.
It is highly recommended that you obtain your Windows 8.1 software license key before you flash BIOS 2.02, as the flashing process will remove your key from the BIOS image.New 8/25/2015
You can extract your embedded product key by pasting the following into a Windows CMD prompt, followed by Enter:

This will create a file called WProdKey.txt on your Desktop containing your embedded Windows product key.
Extract the key before you flash the new BIOS and store it somewhere that is NOT on the tablet.
Use the key if you need to reinstall Windows 8.1 on the tablet for some reason.

Procedure: Update BIOS to 2.02 Dual BootRequired:
1. Windows Host PC with adb drivers installed.
2. Teclast X98 Air device with any version of Android installed.
3. USB A to Micro USB cable
4. BIOS 2.02 adb FLASH202 archive (thanks to Mirek190 for creating this archive !! I have pretty much rewritten it at this point)

Step by Step instructions:
1. Extract FLASH202 archive to a folder on your Windows Host PC.
2. If you wish to flash a BIOS image other than 2.02, rename the BIOS image you want to flash to X98_Air_3G_Dual.bin and browse to the folder where you extracted the FLASH202 archive. Open the X98-Air-dual-boot-bios-and-FPT folder and place your renamed BIOS image there, overwriting the existing file.
3. Ensure that your tablet has at least 50% battery charge.
4. Boot your tablet into Android.
5. Enable USB debugging in Android if not already enabled.
6. Connect your tablet to your Windows Host PC using the USB A to Micro USB cable.
7. On Host PC, browse to the folder where you extracted the FLASH202 archive.
8. Double click on the file FLASH.BAT. It should have a GEAR icon next to it.
You should see:

If you do not see the line in red, and the script is not continuing to the message in Step 10 below, then adb is not detecting your X98 Air device. Check that your USB cable is connected properly and USB debugging is enabled in Android. If FLASH.BAT is still not detecting your tablet after these checks, press CTRL-C to abort. Then press y + ENTER to the Terminate BAT file (Y/N) prompt.
Now, perform the following procedure on your host PC:

Once you have completed the listed procedure, restart this procedure from Step 7.

10. If adb is able to detect your X98 Air device, you will see the following message:

You are about to flash the BIOS on your X98 Air device to ver 2.02 Dual Boot
If you do not wish to do this, press CTRL-C to abort.
By pressing ENTER you confirm your understanding that your embedded Windows key
will be wiped by this process and you agree to accept all responsibility
for what may happen to your device.

11. Press ENTER if you agree.
You will see:

NOTE: This process can take 2 minutes or more to complete.
DO NOT INTERRUPT THIS PROCESS or unpleasant results may occur.
Flash Process Commencing @ 12:30:30 on 7/17/2015

12. Wait for the script to finish. If you see this message:**BIOS flash FAILURE !! Check flashlog.txt. Post to XDA Developers if necessary
Press ENTER to view flashlog.txt.
Press ENTER and your flash log will be displayed. Troubleshoot your failed flash or post the log to XDA Developers..
13. If you see this message:**BIOS flash SUCCESS !! Press ENTER to power off X98 Air device immediately.
14. Press the ENTER key and your X98 Air device will be powered down.
15. Disconnect tablet from PC. Wait at least 15 seconds and power tablet back up while holding Vol+.
16. Select your OS and continue. Congratulations !!
_________Change Log:9/14/2015 Added Step 2 to allow users to replace the target BIOS image with an image of their choice. Added FAQ heading to this effect as well.8/10/2015FLASH.BAT ver 3.07. Changed confirmation wording to indicate Windows key will be destroyed and to have user assume all responsibility for what may happen.8/6/2015FLASH.BAT ver 3.06. Added code to change back to correct directory when run as administrator. Enhanced flash failure checking to indicate whether FPT was successfully executed and failed to flash vs when there was a problem launching FPT. Script now brings up flashlog.txt in NOTEPAD following failed flash.8/4/2015FLASH.BAT ver 3.05. Added automated power down of X98 Air device following successful flash. This is to attempt to minimize bricked devices due to users not following instructions. Thanks to Mirek190 for suggesting this. FYI: I tested this new FLASH.BAT on my X98 Air 3G twice. Each time the flash was successful and no bricks were made. Here is the flashlog.txt.7/27/2015FLASH.BAT ver 3.04. Removed Repartition option and option select menu. Clarified wording in a few places7/19/2015FLASH.BAT ver 3.03. Fixed error in call to FPT that was preventing FPT from launching. Thanks to Lysie for catching this. 7/17/2015FLASH.BAT ver 3.02. Added reliable FLASH success/failure detection to the script. Script now searches the output from the FPT command for the string "FPT Operation Passed". Thanks to ArcticSilverFox for providing a flashlog.txt from a successful flash. Also added a version # to FLASH.BAT and very specific do not disturb instructions as FPT is called.7/17/2015 Fixed a couple of errors in FLASH.BAT introduced while making the earlier mods. Thanks to ArcticSilverFox for his assistance above and beyond the call of duty !!7/16/2015 Improved FLASH.BAT script, adding detailed runtime logging to new log file flashlog.txt and added explicit warnings that display prior to flashing device. Added code to automatically kill any running adb processes before flashing. Removed instructions to user to kill adb processes. Updated tutorial to reflect changes in FLASH.BAT.

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.

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:

Step by Step instructions:
1. Extract archive to a folder on your target Windows PC.
2. Browse to the folder and launch:

1-InstallDrivers.bat

3. The batch file will install the iSoC USB drivers ver 1.2 and the Intel Android drivers, ver 1.10
If either installer reports you already have a version of the driver installed, allow it to uninstall the
old drivers and install the new ones.
4. Launch:

2-InstallMFT.bat

5. The installer will proceed to install the Flash Tool.
6. Right click on

3-RunAsAdmin-ApplyCustomConfig.bat

and select Run as Administrator.
This script copies the CUSTOM_CONFIG.INI to the MFT install folder and also copies Manufacturing Flash Tool.INI to the PROGRAMDATA folder. It needs admin rights to copy to the install folder.
7. Congratulations, your Flash Tool is now installed and configured.
If you have a ROM you need to flash, you can now proceed to:

_________Change Log:9/15/2015 Changed .BAT file 3-RunAsAdmin-ApplyCustomConfig.bat due to a coding error that could cause the Manufacturing Flash Tool.INI file to not be copied over correctly if the MFT installer failed to create the C:\ProgramData\Intel\ folder for some reason. Thanks to Spectator_0o for pointing this out and for providing appropriate code to use.9/14/2015 Had to restore iSoC drivers to install archive, batch file, and instructions, as MFT is getting a WDAPI1440.dll is missing error at launch time if the iSoC drivers were never installed on the system. Thanks to vanzan for catching this.9/13/2015 Removed iSoC drivers from install archive, batch file, and instructions, after reading a passage in MFT user guide that implied iSoC drivers were not needed on Baytrail devices. I then tested the theory and was pleased to be able to confirm that iSoC drivers are not needed,. The iSoC drivers may, in fact, be causing some of the USB enumeration issues we have been seeing. For more details, see this post.9/11/2015 Updated Intel adb driver to ver 1.10.07/19/2015 Added reference to 3rd .BAT file and the need to run as administrator.7/15/2015 Created initial procedure.

TTTTecKnight'sTeclastTutorials seriesFlash a custom Android image (ROM) to your X98 Air deviceSpecial Note: This procedure uses MFT to flash an android image to an X98 Air Device. MFT is the only software capable of imaging an X98 Air device that is missing some or all of its critical partitions,
such as the Android or Windows EFI boot partitions or the droidboot or recovery partitions.
The reason MFT is still able to image a device without a droidboot partition is a special provisioning mode called DnX mode that is built into the BIOS in Intel Bay Trail devices. MFT is able to send the X98 the droidboot image over USB using DnX protocol. Then the running droidboot process can restore the physical droidboot partition on the device.Procedure: Flash a custom Android image (ROM) to your X98 Air deviceRequired:
1. A Windows Host PC with the Manufacturing Flash Tool (MFT) installed and configured.
If you have a Windows PC, but need to install and configure the MFT, Try This Tutorial first.
2. Teclast X98 Air device with at least 50% battery charge
3. USB A to Micro USB cable
4. A downloaded Android ROM image that you intend to flash to your device. I would recommend downloading one of Mirek190's fine ROMs from here:

Step by Step instructions:
1. Extract the ROM you will be installing to a folder on your Windows Host PC. I have selected Mirek's V3 Lollipop image.
2. Launch the MFT using the desktop shortcut that looks like this:
The MFT Application looks like this:

3 Within the MFT, select the File menu, then Open. This brings up the XML selector dialog, which looks like this:

4. Using the MFT's XML selector dialog, browse to the folder containing your extracted ROM.
You should see the following options (wording will vary depending on the ROM):

If you select flash-full_with_partitioning, MFT will delete all existing partitions and then re-create all partitions from scratch before flashing the android partitions. This will destroy any existing Windows installation, so it is normally only used when converting from single OS to dual boot, resizing partitions, the X98 is missing critical partitions or the X98 is not booting properly.
The other 2 options load the requested android image into the existing partitions--the format or wipe data option wipes the user data partition, so it will remove all user downloaded applications and settings. This is usually advised when flashing a new android version (such as when flashing a Lollipop ROM to a device with KitKat installed). Keep data will preserve your existing user apps and settings.
Select the .xml file corresponding to the options desired.MFT is now ready to flash. The flash will be triggered by the detection of a Baytrail device in DnX mode on the Host PC's USB bus.

5. Connect the USB cable to the Host PC, but not to the tablet just yet.
6. Power up your X98 Air device by holding down the power button, volume+ and volume- until your device enters DnX mode. Do not release any of the buttons until you see the message:

Entering DnX mode
Waiting for Fastboot command

in small letters in the center of the display. DnX mode is a special provisioning mode, unique to Intel SoCs. The only software designed to communicate with a device in DnX mode is the Intel MFT.
7. Find a stable place to set down your X98 Air device, then connect the MicroUSB end of the USB cable to your device.
8. MFT should now detect your X98 Air device and immediately begin the flashing process. MFT will first send the tablet to droidboot mode, then it will flash the device using fastboot, displaying a progress bar indicating the percentage completed, like this:

The progress bar might seem to hang at about 80%, but give it some time and it will complete.
9. Once the MFT indicates flashing is complete:

disconnect the USB cable from the tablet and Host PC.
10. Power up your tablet and boot into your new Android ROM !!
_________Change Log:

8/17/2015Changed title of procedure to make it more generic (ie: include options that don't preserve Windows). Reworded XML selector dialog step to include partitioning options. Added special note detailing how MFT is able to flash a tablet with no droidboot or EFI partitions.7/21/2015 Added clarifications about DnX mode, reworded a few passages.7/14/2015 Created initial procedure.

The .ZIP files linked above will add Boot to Windows functionality in Mirek's V4 ROM to all Air II and Air 3G models.
Boot to Windows will function properly after applying this fix IF you have flashed BIOS version 2.02.This also installs the OsSwitcher App that gives you an icon that will boot you straight into Windows.

Code:

Extract archive to a Folder on your Host PC (with ADB drivers installed)
Connect X98 Air device to Host PC using USB cable.
Ensure USB debugging is enabled.
Browse to the Folder on Host PC and launch B2WinFix.bat
Once it detects your device it will let you continue by pressing a key
Your X98 Air device may display an SU dialog. If it does, you must GRANT SU privs.
Script is very fast. When complete press a key to reboot device.
When device reboots, OsSwitcher will be installed and functional

TTTTecKnight'sTeclastTutorials seriesFlash a custom Android image (ROM) to your X98 Air deviceSpecial Note: This procedure uses MFT to flash an android image to an X98 Air Device. MFT is the only software capable of imaging an X98 Air device that is missing some or all of its critical partitions,
such as the Android or Windows EFI boot partitions or the droidboot or recovery partitions.
The reason MFT is still able to image a device without a droidboot partition is a special provisioning mode called DnX mode that is built into the BIOS in Intel Bay Trail devices. MFT is able to send the X98 the droidboot image over USB using DnX protocol. Then the running droidboot process can restore the physical droidboot partition on the device.Procedure: Flash a custom Android image (ROM) to your X98 Air deviceRequired:
1. A Windows Host PC with the Manufacturing Flash Tool (MFT) installed and configured.
If you have a Windows PC, but need to install and configure the MFT, Try This Tutorial first.
2. Teclast X98 Air device with at least 50% battery charge
3. USB A to Micro USB cable
4. A downloaded Android ROM image that you intend to flash to your device. I would recommend downloading one of Mirek190's fine ROMs from here:

Step by Step instructions:
1. Extract the ROM you will be installing to a folder on your Windows Host PC. I have selected Mirek's V3 Lollipop image.
2. Launch the MFT using the desktop shortcut that looks like this:

The MFT Application looks like this:

3 Within the MFT, select the File menu, then Open. This brings up the XML selector dialog, which looks like this:

4. Using the MFT's XML selector dialog, browse to the folder containing your extracted ROM.
You should see the following options (wording will vary depending on the ROM):

If you select flash-full_with_partitioning, MFT will delete all existing partitions and then re-create all partitions from scratch before flashing the android partitions. This will destroy any existing Windows installation, so it is normally only used when converting from single OS to dual boot, resizing partitions, the X98 is missing critical partitions or the X98 is not booting properly.
The other 2 options load the requested android image into the existing partitions--the format or wipe data option wipes the user data partition, so it will remove all user downloaded applications and settings. This is usually advised when flashing a new android version (such as when flashing a Lollipop ROM to a device with KitKat installed). Keep data will preserve your existing user apps and settings.
Select the .xml file corresponding to the options desired.MFT is now ready to flash. The flash will be triggered by the detection of a Baytrail device in DnX mode on the Host PC's USB bus.

5. Connect the USB cable to the Host PC, but not to the tablet just yet.
6. Power up your X98 Air device by holding down the power button, volume+ and volume- until your device enters DnX mode. Do not release any of the buttons until you see the message:

Entering DnX mode
Waiting for Fastboot command

in small letters in the center of the display. DnX mode is a special provisioning mode, unique to Intel SoCs. The only software designed to communicate with a device in DnX mode is the Intel MFT.
7. Find a stable place to set down your X98 Air device, then connect the MicroUSB end of the USB cable to your device.
8. MFT should now detect your X98 Air device and immediately begin the flashing process. MFT will first send the tablet to droidboot mode, then it will flash the device using fastboot, displaying a progress bar indicating the percentage completed, like this:

The progress bar might seem to hang at about 80%, but give it some time and it will complete.
9. Once the MFT indicates flashing is complete:

disconnect the USB cable from the tablet and Host PC.
10. Power up your tablet and boot into your new Android ROM !!
_________Change Log:

8/17/2015Changed title of procedure to make it more generic (ie: include options that don't preserve Windows). Reworded XML selector dialog step to include partitioning options. Added special note detailing how MFT is able to flash a tablet with no droidboot or EFI partitions.7/21/2015 Added clarifications about DnX mode, reworded a few passages.7/14/2015 Created initial procedure.

Thank you for the detailed instructions for updating my Teclast X98 Air II with a new ROM. I followed the instructions and everything seemed to be going well until the process stopped at 14% and after about 5 minutes I received an error (Droid Boot I believe). Fortunately nothing was done to my tablet, so I get to try the process again. If you know what can cause this error and how resolve it I would be grateful. FYI, I am trying to install your "Android 5.0 V2 Debloated" ROM.

Thank you for the detailed instructions for updating my Teclast X98 Air II with a new ROM. I followed the instructions and everything seemed to be going well until the process stopped at 14% and after about 5 minutes I received an error (Droid Boot I believe). Fortunately nothing was done to my tablet, so I get to try the process again. If you know what can cause this error and how resolve it I would be grateful. FYI, I am trying to install your "Android 5.0 V2 Debloated" ROM.

probstc,
I need you to post your MFT log. Your description of the error (Droidboot, I believe) tells me nothing.
MFT logs are saved in the folder C:\MFLASH_LOGS

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service