Database Develop

Has anyone tried this free sofware SIM unlock?

http://forum.gsmhosting.com/vbb/f606/acer-liquide-unlock-solution-100-working-1092894/
I am confused because the OS update from the global Acer site doesn't create a folder called "qcn" or "01" or "03."
If anyone knows how to get this free unlock working, please educate us. I'd rather not pay for an unlock.

I did not try, but I downloaded the file, and translated the french, not sure what to make of it, I think it could be dangerous if it's for liquid and not liquid e, although, writing nv items on most similar devices should be the same
French to English translation
Flasher / unlocked his Liquid AMSS in Fashion
Render unto Caesar what belong to Caesar:
I would like to thank DNA without him if he was not mistaken in the keys that I have given him, I'd still be looking!
Right now the heart of the matter ...
The Acer software to reverse mode AMSS Tools uses to flash the baseband before flashing the rest of the liquid, you could just put up this system, those with Maleza recovery or at worst by fastboot.
But in any case we could touch the baseband, much less dream of désimlockage its Liquid!
The method I'll suggest is as dangerous as a flash! In fact it is one! So be very careful, no hurry, because even if it is recovered through this method, about 10 minutes of flash is a long time anyway!
With this, any liquid is recovered even those whose method fastboot can not walk alone are not such that the light at all, unfortunately, more vibration and hopelessly lost!
If you still have access to your phone, do a backup!
Otherwise:
0 Download this-> http://www.mcboydesign.fr/media/acer_liquid/amss_mode/amss_mode.zip and unzip it!
1 Turn off your phone if it is not already the case!
IMPORTANT: The drive must be disconnected!
Volume 2 Make (and not-as Volume Recovery!) Picture Power, all at the same time, the liquid will vibrate twice, but nothing appears on the screen!
3 Plug the USB into Liquid on your phone, I do not explain here how to ask the drivers, there is enough explanation on the Forum!
If you're curious, you'll see in your device manager in "port COM & LTP" a port whose name appeared is quite explicit!
4 Open Acer Tool!
IMPORTANT: If you're running Vista and Seven, do not forget to right click on the icon of acer tools and do "Run as administrator", if not crash!
5 You will see that you are logged in AMMS (connected (AMSS)), with "Browse" go get your bin, select "Select QCN File Manually" and START!
6 A window appeared, press "Yes"
7 And there does not touch anything, the flash is short, about 10 minutes or more depending on the PC!
...
8 A window is opened again, select the file I give you (desimlock.xml) And be open,,,
9 Do not worry your Flash will be a long shot, as if he walked over, wait (almost a minute!)
10 Do not touch anything now as you do not "Process Finished, You Can remove USB" Acer Tools!
11 Enjoy! Finished!
This method replaces fastboot and serves also unlocked
Small Tip: In another flash, Acer Tools has detected a former NAQ, and my re-simlocker Liquid, Think A1_QCN delete the directory at the root of C: (or save it elsewhere if you prefer!)
I hope this will help everyone!!
Remains for me to figure out how to manually send files to other AMSS and not having to use Acer Tools!

dan-htc-touch said:
I did not try, but I downloaded the file, and translated the french, not sure what to make of it, I think it could be dangerous if it's for liquid and not liquid e, although, writing nv items on most similar devices should be the same
French to English translation
Flasher / unlocked his Liquid AMSS in Fashion
Render unto Caesar what belong to Caesar:
I would like to thank DNA without him if he was not mistaken in the keys that I have given him, I'd still be looking!
Right now the heart of the matter ...
The Acer software to reverse mode AMSS Tools uses to flash the baseband before flashing the rest of the liquid, you could just put up this system, those with Maleza recovery or at worst by fastboot.
But in any case we could touch the baseband, much less dream of désimlockage its Liquid!
The method I'll suggest is as dangerous as a flash! In fact it is one! So be very careful, no hurry, because even if it is recovered through this method, about 10 minutes of flash is a long time anyway!
With this, any liquid is recovered even those whose method fastboot can not walk alone are not such that the light at all, unfortunately, more vibration and hopelessly lost!
If you still have access to your phone, do a backup!
Otherwise:
0 Download this-> http://www.mcboydesign.fr/media/acer_liquid/amss_mode/amss_mode.zip and unzip it!
1 Turn off your phone if it is not already the case!
IMPORTANT: The drive must be disconnected!
Volume 2 Make (and not-as Volume Recovery!) Picture Power, all at the same time, the liquid will vibrate twice, but nothing appears on the screen!
3 Plug the USB into Liquid on your phone, I do not explain here how to ask the drivers, there is enough explanation on the Forum!
If you're curious, you'll see in your device manager in "port COM & LTP" a port whose name appeared is quite explicit!
4 Open Acer Tool!
IMPORTANT: If you're running Vista and Seven, do not forget to right click on the icon of acer tools and do "Run as administrator", if not crash!
5 You will see that you are logged in AMMS (connected (AMSS)), with "Browse" go get your bin, select "Select QCN File Manually" and START!
6 A window appeared, press "Yes"
7 And there does not touch anything, the flash is short, about 10 minutes or more depending on the PC!
...
8 A window is opened again, select the file I give you (desimlock.xml) And be open,,,
9 Do not worry your Flash will be a long shot, as if he walked over, wait (almost a minute!)
10 Do not touch anything now as you do not "Process Finished, You Can remove USB" Acer Tools!
11 Enjoy! Finished!
This method replaces fastboot and serves also unlocked
Small Tip: In another flash, Acer Tools has detected a former NAQ, and my re-simlocker Liquid, Think A1_QCN delete the directory at the root of C: (or save it elsewhere if you prefer!)
I hope this will help everyone!!
Remains for me to figure out how to manually send files to other AMSS and not having to use Acer Tools!
Click to expand...
Click to collapse
i tried ur method bro, but when i choice desimlock.xml file, Acer tool show Sever connection fail, and phone stuck at recovery mode...plz help bro

[Workshop] Unbrick fully bricked I9070

Hi,
I'm launching this thread to work on an unbrick procedure for fully bricked I9070/P without JTAG or Riffbox (same as Adam Outler, TheBeano, Odia etc... 's project "let's save some bricks")
Reminder : fully bricked = no download/recovery mode, no display, not charging, not going to recovery with a 301k Ohm jig.
I have a fully bricked I9070P and a fully functionnal I8090 (same processor).
Based on the sources and tools for the U8500 that were disclosed in january, I've managed to make my dead phone and my PC talk "a bit" together (under Windows with the VSIW tool, and under linux with recompiling the "flashkit" tools): when plugged in and inserting the battery, the tool sees the terminal, gets its serial number and various data and fails while trying to send and execute a boot file because the terminal closes the USB port.
I've managed to get a certain degree of communication with the "riff" tool (open source) of the Snowball project too (the dev board based on a U9500).
Based on this half successes, I'm pretty sure we are close to a clean solution to revive a fully bricked terminal without soldering JTAG.
Here are the main docs I've read so far :
* most posts from the threads "let's save some bricks" and "fun with resistors"
* the reference documents of the I9070 (Samsung_GT-I9070_Galaxy_S_Advance_Galaxy_S_II_Lite_service_manual.rar)
* the reference manual of the U9500 (http://www.calao-systems.com/reposi...X/DATASHEETS/AP9500_reference_manual_rev1.pdf)
* TSU6111 datasheet from TI (the USB/UART switch the 9070 is using, cf the service manual -> Lite Schematics -> u-USB SW IC part)
* lots of docs from the "flashkit" sources
My setup :
* a fully bricked I9070P
* a fully working I8190P
* an 8GB SDCard
* a Windows/Linux workstation (Ubuntu 12.04LTS + Android compiling environment + disclosed sources)
* terminal emulators
* a Prolific cable (PL2303) (any USB to TTL adapter would do it, you can buy one for 3$ as Arduino accessory, or reuse a Nokia DKU 5 -see hackaday website for a link). Take care with Prolifics : they don't work under Windows 8 with the last driver, you have to use the version before, Google is your friend)
* a set of resistors
* a multimeter
* libusb win32 drivers setup, see sourceforge (use the tool included in the drivers package to generate the right .inf file for the U8500 (or use 04CC and 8500)
Here are my conclusions so far :
* based on the Snowball docs and the U9500 spec, we don't seem to have any need to modify anything (resistors) on the mainboard to change boot sequence. The dev board does not have any switch for that and my dead I9070 and working I8190 exibit the same behaviour at bootup : the appear as a "U8500 USB ROM" for a seconds and disconnect when going on farther in the boot sequence.
Moreover, the fact that I managed to have my dead phone talk with the flashtool confort me in the fact that we are almost done.
* I have *not* managed to get any output on my terminal with my Prolific cable plugged in with a 630kOhm resistor on the pins 4 and 5. My resistor setup might be good because it make my working I8190 boot when I plug it in.
But I'm not sure of my RX/TX setup, I have crossed the RX/TX of the phone and the ones of the Prolific but I might have been wrong identifying the pins of my modified USB plug (D+ and D-).
But I'm sure the RX and TX wires of my Prolific are the right ones : when I connect them together (nullmodem configuration), the characters typed on my terminal are displayed.
So the main issue is : how can we have the dead phone keep the USB port open and not close it after 2 seconds?
My assumption is that it is always probing different boot methods (UART, USB, MMC etc) and then attempts to boot normaly from eMMC.
I don't know which part of the bootchain sequence I've garbaged on my I9070: IBL, PBL, SBL, PARAM? Managing to get any debug output on my console would greatly help me.
Has any of you tried to achieve something similar? If yes, could you post your setup and results?
Let's save some bricks another time!

any progress
flentus said:
Hi,
I'm launching this thread to work on an unbrick procedure for fully bricked I9070/P without JTAG or Riffbox (same as Adam Outler, TheBeano, Odia etc... 's project "let's save some bricks")
Reminder : fully bricked = no download/recovery mode, no display, not charging, not going to recovery with a 301k Ohm jig.
I have a fully bricked I9070P and a fully functionnal I8090 (same processor).
Based on the sources and tools for the U8500 that were disclosed in january, I've managed to make my dead phone and my PC talk "a bit" together (under Windows with the VSIW tool, and under linux with recompiling the "flashkit" tools): when plugged in and inserting the battery, the tool sees the terminal, gets its serial number and various data and fails while trying to send and execute a boot file because the terminal closes the USB port.
I've managed to get a certain degree of communication with the "riff" tool (open source) of the Snowball project too (the dev board based on a U9500).
Based on this half successes, I'm pretty sure we are close to a clean solution to revive a fully bricked terminal without soldering JTAG.
Here are the main docs I've read so far :
* most posts from the threads "let's save some bricks" and "fun with resistors"
* the reference documents of the I9070 (Samsung_GT-I9070_Galaxy_S_Advance_Galaxy_S_II_Lite_service_manual.rar)
* the reference manual of the U9500 (http://www.calao-systems.com/reposi...X/DATASHEETS/AP9500_reference_manual_rev1.pdf)
* TSU6111 datasheet from TI (the USB/UART switch the 9070 is using, cf the service manual -> Lite Schematics -> u-USB SW IC part)
* lots of docs from the "flashkit" sources
My setup :
* a fully bricked I9070P
* a fully working I8190P
* an 8GB SDCard
* a Windows/Linux workstation (Ubuntu 12.04LTS + Android compiling environment + disclosed sources)
* terminal emulators
* a Prolific cable (PL2303) (any USB to TTL adapter would do it, you can buy one for 3$ as Arduino accessory, or reuse a Nokia DKU 5 -see hackaday website for a link). Take care with Prolifics : they don't work under Windows 8 with the last driver, you have to use the version before, Google is your friend)
* a set of resistors
* a multimeter
* libusb win32 drivers setup, see sourceforge (use the tool included in the drivers package to generate the right .inf file for the U8500 (or use 04CC and 8500)
Here are my conclusions so far :
* based on the Snowball docs and the U9500 spec, we don't seem to have any need to modify anything (resistors) on the mainboard to change boot sequence. The dev board does not have any switch for that and my dead I9070 and working I8190 exibit the same behaviour at bootup : the appear as a "U8500 USB ROM" for a seconds and disconnect when going on farther in the boot sequence.
Moreover, the fact that I managed to have my dead phone talk with the flashtool confort me in the fact that we are almost done.
* I have *not* managed to get any output on my terminal with my Prolific cable plugged in with a 630kOhm resistor on the pins 4 and 5. My resistor setup might be good because it make my working I8190 boot when I plug it in.
But I'm not sure of my RX/TX setup, I have crossed the RX/TX of the phone and the ones of the Prolific but I might have been wrong identifying the pins of my modified USB plug (D+ and D-).
But I'm sure the RX and TX wires of my Prolific are the right ones : when I connect them together (nullmodem configuration), the characters typed on my terminal are displayed.
So the main issue is : how can we have the dead phone keep the USB port open and not close it after 2 seconds?
My assumption is that it is always probing different boot methods (UART, USB, MMC etc) and then attempts to boot normaly from eMMC.
I don't know which part of the bootchain sequence I've garbaged on my I9070: IBL, PBL, SBL, PARAM? Managing to get any debug output on my console would greatly help me.
Has any of you tried to achieve something similar? If yes, could you post your setup and results?
Let's save some bricks another time!
Click to expand...
Click to collapse
dude did you find any solution??same problem here

up up this thread.... i'm also experiencing with my s3 mini i8190 continuously disconnecting libusb-win32 driver... my phone is at deadboot and unable to resurrect with RIFFBOX...

neilPD_07 said:
up up this thread.... i'm also experiencing with my s3 mini i8190 continuously disconnecting libusb-win32 driver... my phone is at deadboot and unable to resurrect with RIFFBOX...
Click to expand...
Click to collapse
Mebay u have dead mini USB port in SIII mini ?
Sent from my GT-I9070 using Tapatalk

Hi guys,
I had a little time playing with this, but I have good news :
I modified the default profile used for the flashtool backend to "ADL boot" : my "dead" phone now stays connected to the USB and is reported as "started" by the flashtool CLI ("flash-tool get_connected_equipments") however, when I try some "active" flash-tool CLI commands, the backend crashes.
As I was running it either in windows 8.1 64 bits or Linux in a VM, their might have some bad interactions with the OS on the one hand and the USB port forwarding on the other hand (there was issues with the LCD and LCM drivers in Windows, I grabbed the 64 bits ones from VSIW...).
-> I have to test on a 32 bit Windows.
Good to read to understand further (extracted from flash-tool-backend.html file) :
Note : ME stands for mobile equipment, "boot indication" can take the following values : ADL, ALT, Normal, Production, Programming : set into the config files pointed by the .mesp file)
Boot process description
When the peripheral boot sequence starts, the ME sends an asic id to the connected PC tool. The PC tool then answers with a boot indication. If normal, "ADL" or "production" is sent as boot indication; this means that the x-loader will start the binary software stored at the corresponding location in the boot image (based on the location stated by the TOC). If programming is used as boot indication, the PC will send a completely new set of boot code to the ME. This is used when a loader is downloaded during service mode startup via the Flash Tool Backend. When the normal boot indication is sent, Flash Tool backend sends no more data and the ME is booted with the binary software stored in the place where the normal software is stored according to the TOC.
The ADL boot scenario works like this:
1. Flash Tool Backend receives asic id
2. Boot indication ADL is sent
3. Flash tool backend starts LCD and LCM and waits for a loader startup message.
The loader is stored at the ADL location of the boot image (this is supported by the assemble tool).
I think I'd have to assemble the correct bootloader to enable "profile-STE_DBX500_flashloader.prfl" profile to work (we are missing corresponding loader.ldr loader). It would enable the use of the "LoaderCommunication"
I think I have all the pieces and the docs (we even have the certificates to sign it !): just need time and a better GFAF (Girlfriend acceptance factor).
The guys who managed to unbrick some Qualcomm based devices might be of a huge help, they would be much more efficient than I can be... I any of you have time to drive them around here, do not hesitate!
Enjoy!

flentus said:
Hi guys,
I had a little time playing with this, but I have good news :
I modified the default profile used for the flashtool backend to "ADL boot" : my "dead" phone now stays connected to the USB and is reported as "started" by the flashtool CLI ("flash-tool get_connected_equipments") however, when I try some "active" flash-tool CLI commands, the backend crashes.
As I was running it either in windows 8.1 64 bits or Linux in a VM, their might have some bad interactions with the OS on the one hand and the USB port forwarding on the other hand (there was issues with the LCD and LCM drivers in Windows, I grabbed the 64 bits ones from VSIW...).
-> I have to test on a 32 bit Windows.
Good to read to understand further (extracted from flash-tool-backend.html file) :
Note : ME stands for mobile equipment, "boot indication" can take the following values : ADL, ALT, Normal, Production, Programming : set into the config files pointed by the .mesp file)
Boot process description
When the peripheral boot sequence starts, the ME sends an asic id to the connected PC tool. The PC tool then answers with a boot indication. If normal, "ADL" or "production" is sent as boot indication; this means that the x-loader will start the binary software stored at the corresponding location in the boot image (based on the location stated by the TOC). If programming is used as boot indication, the PC will send a completely new set of boot code to the ME. This is used when a loader is downloaded during service mode startup via the Flash Tool Backend. When the normal boot indication is sent, Flash Tool backend sends no more data and the ME is booted with the binary software stored in the place where the normal software is stored according to the TOC.
The ADL boot scenario works like this:
1. Flash Tool Backend receives asic id
2. Boot indication ADL is sent
3. Flash tool backend starts LCD and LCM and waits for a loader startup message.
The loader is stored at the ADL location of the boot image (this is supported by the assemble tool).
I think I'd have to assemble the correct bootloader to enable "profile-STE_DBX500_flashloader.prfl" profile to work (we are missing corresponding loader.ldr loader). It would enable the use of the "LoaderCommunication"
I think I have all the pieces and the docs (we even have the certificates to sign it !): just need time and a better GFAF (Girlfriend acceptance factor).
The guys who managed to unbrick some Qualcomm based devices might be of a huge help, they would be much more efficient than I can be... I any of you have time to drive them around here, do not hesitate!
Enjoy!
Click to expand...
Click to collapse
Any good updates & tested solution sir? I'm still waiting for a big solution for this kind of problem... TIA

Hi !
well, I'm almost done with the bootloaders: I have a loader.ldr compiled + 2 bin.
I've reset my dev. env. to an Ubuntu 10.04 according to a .doc I found in the sources (search for "*.doc", you will find "getting_Started_with_Android_and_Linux.doc"): I now have far less compilation errors, but I'm still struggling to get the full compilation process just right. For eg. I had to remove the "alsactrl" component due to dependency issues I've not been able to solve.
As already stated, I'm far from being a dev. expert so it takes me a lot of time to acheive the right compilation.
I would highly need the help of s/b who is fluent with Android compilation/dev env.: first it would be necessary to establish how to merge correctly the disclosed sources with Google's sources + the open sources from Samsung (kernel + system) (we have duplicates here as the kernel is also available in the disclosed sources, but both are different releases).
As already stated, given the few spare tile I have and without the help of the right people this will take me ~4 months+ to have this unbrick done (if I face no deadlock).
So, if you want this faster: get the right guys on the forum (from the "dev" branches) and drag them here so we can go forward much faste!

Hi!
So, I think I'm getting close: I now have the boot files build procedure working (+kernel and sytem, but I don't need those).
When I try to boot my phone with those boot files using the "flasher -tXXXX -X0,normal.bin" command, it seems that they are rejected as the phone connects and disconnects (boot loop on the iRom startup, I believe).
So, now I really need to have some kind of debug console setup to understand what's going on (cause of rejection, like signature problem etc...):
I've been working blindly up to now hopping that the software would work "off the shelves"... it never does
I'll have to try to understand how the "trigger UART" parameter of flashkit backend works and what is it intended to (I'll have to read the code for that as I've never seen any explanation about it anywhere in the docs). I don't figure out how this could work as on the backend GUI it lists the host PC's serial ports...
Another option would be to have my FTDI debug setup working. Maybe it's not "another option" but is required if the "trigger UART" is just enabling UART debug on the phone and requires a debug cable to read these debug data. My problem in that case would be how to have USB *and* UART on the same port... unless all this is designed for dev targets that have 2 USB ports as the Calao's u8500 targets. In that case, i'd have to find something smarter
As usual, if someone with knownledge on all this is willing to help: wave your hand, I'd happy to share my researches and go forward much faster. But I really feel I'm alone on this (even if I know that there will be tons of leechers when/if I manage to have this work
That's life on XDA!

Nice nice
flentus said:
Hi!
So, I think I'm getting close: I now have the boot files build procedure working (+kernel and sytem, but I don't need those).
When I try to boot my phone with those boot files using the "flasher -tXXXX -X0,normal.bin" command, it seems that they are rejected as the phone connects and disconnects (boot loop on the iRom startup, I believe).
So, now I really need to have some kind of debug console setup to understand what's going on (cause of rejection, like signature problem etc...):
I've been working blindly up to now hopping that the software would work "off the shelves"... it never does
I'll have to try to understand how the "trigger UART" parameter of flashkit backend works and what is it intended to (I'll have to read the code for that as I've never seen any explanation about it anywhere in the docs). I don't figure out how this could work as on the backend GUI it lists the host PC's serial ports...
Another option would be to have my FTDI debug setup working. Maybe it's not "another option" but is required if the "trigger UART" is just enabling UART debug on the phone and requires a debug cable to read these debug data. My problem in that case would be how to have USB *and* UART on the same port... unless all this is designed for dev targets that have 2 USB ports as the Calao's u8500 targets. In that case, i'd have to find something smarter
As usual, if someone with knownledge on all this is willing to help: wave your hand, I'd happy to share my researches and go forward much faster. But I really feel I'm alone on this (even if I know that there will be tons of leechers when/if I manage to have this work
That's life on XDA!
Click to expand...
Click to collapse
U R great man..UP UP UP :good::good::good:

use UART debug on USB
This will help me, I'll test it on my working S3 mini (same proc and very similar HW)... when I have time...
-> this will validate my UART debug setup : http://forum.xda-developers.com/showthread.php?t=2100809

ok, UART debug up and partially running on my SIII mini: debug messages displayed on terminal but keystrokes do not reach the phone, this is secondary for me at the moment, I may have a bad contact somewhere.
Tested on my dead I9070: no display, so the Xloader on my eMMC is garbaged (or Xloader UART debug is disabled, but this is less likely).
As expected, I now have to figure out how to have flashloader boot files upload *and* debug working together to understand what's wrong with my compiled boot files. I think the "trigger UART" thing is a good track, but I'm really puzzled by how to have the USB *and* the UART setup at the same time.
I fear to fry something by having phone D+/D- connected to USB port of the PC and connected at the same time to my Prolific TxD/RxD + 5V VCC connected to PC USB... sounds like a bad thing.
Another track would be USB debug I see in some parts of the code, but I don't know how to read the debug from there, more code to inspect...

got it~
---------- Post added at 02:03 PM ---------- Previous post was at 01:22 PM ----------
I also have a fully bricked I9070( not I9070P).I`m waiting for your good news.Thanks first.

I received this PM, I believe it can be useful for others experimenting with it
flentus said:
Ola Paul,
I contact you on an advise from Cocafe.
I launched a while ago the thread "[Workshop] Unbrick fully bricked I9070" (http://forum.xda-developers.com/showthread.php?t=2701363)
I'm looking for help to acheive the task as I don't have very much time to spend on it due to huge work I have this year.
Would you be ok to participate if you have a little spare time and interest in it?
I think I'm very close to the solution, and this would help a lot of 9070 owners (and maybe SIII mini and Sony too).
As explained in my thread, I have difficulties getting the disclosed sources to build correctly up to the end when integrated with Google SDK. As a result the "finalizing" scripts (that gather the binaries and tidy the "out" directory) don't execute: I end up with a large mess and STE tools don't work out of the box. I have to gather the pieces one by one to have them run which is very time consuming and error prone.
I can say that the recovery process won't need any kind of soldering, wiring or whatever: just a regular USB cable and the right sofware.
The disclosed sources contain everything we need: PBL/SBL sources, signing tool+certificates, the software to talk to the iROM + various documentation.
The problem is just a question of assembling the pieces...
My idea is to assemble an Xloader (PBL) + Uboot (SBL) + recovery and boot from that to execute recovery.
The "flashkit" tool enables this process, I quote the docs: "If 'programming' boot indication is used as boot indication, the PC will send a completely new set of boot code to the ME. This is used when a loader is downloaded during service mode startup via the Flash Tool Backend.".
Tell me if you wish to help me, or if you know someone who has competencies and would wish to!
I speek average spanish if you prefer to exchange in this language.
Regards
Click to expand...
Click to collapse
I am sorry for pointing this out, STE tools wont work ever on i9070, the reason being that we do not have a STE bootloader, heck, most of the low level stuff do not resemble the ST-Ericsson Montblanc development board. You can't even change the bootloader arguments, you can only add to them (the way I first enabled SELinux), the Samsung Bootloader version that we have may be not as restrictive as others, but Sonys bootloader resembles more to STE's than ours.
The only way you may found how to restore it is accessing the JTAG mode (something that is determined only if JTAG is connected and recognized) and depends solely on the emergency bootloader (if that exists, because I am not sure how the device powers on without PBL), the "seconds" of power you get on the USB is the device looking for JTAG.
The "disclosed" sources are for ST-Ericsson devices
Something you should do, is analyze the structures of /dev/block/mmcblk0p10, which contains our partition table (GUID Partition Table - GPT).
Simple way of doing it, you have to do dd if=/dev/block/mmcblk0p10 of=/sdcard/janice.pit on terminal emulator, this is ROM agnostic, because the structures are the same on both stock and any custom ROM. Of course, that is from a working device, I'll do that and drop it here later since I am working on something else right now, and thanks diegoch for discovering this.
Anyway, as diego pointed to me, our partition table is like this.
PIT, CSPSA, EFS, MODEM fs, SBL, SBL2, PARAM, IPL modem, MODEM, Kernel, Kernel2, system, data, cache, preload, fota, sdcard
This is the correct order I believe, since basically, when you use ODIN and use a PIT file, the partition table gets rewritten according to whatever is on that .pit file. So PIT is basically the GPT partition table; obviously SBL is the Samsung bootloader, and SBL2 I believe it's either stage 2.5 or a backup of the first.
So, no clue by going the STE way, something familiar here.
So, I may say something good at the end, see if the i9100 guys ever did it, and go from there, since our device is largely based around i9100 (Galaxy S II)

Hi Paul,
thanks for your contribution.
A few replies/questions :
* you state that Montblanc dev board and I9070 are completly different: isn't the aim of dev dev board to be close to ME while adding extra connectors to ease debug and interfacing for prototyping? Calao dev board looks very close to I9070: I have compared the schematics and component list: they look very very much alike. For me, NovaThor U8500 plateform consists of a DB8500 SoC, a Mali 400, a built-in modem + chips for USB, audio and SIM operations.
So, to me, I may be wrong, at least the processor (u8500), PLL, eMMC, SDRAM, UART + several low level controlers should be the same. As we are trying to work at such level (just trying to get the basic system to boot to just enable eMMC write), don't we have a chance to manage to have those work (maybe with adressing adaptation, those might be tough)?
* I can't agree with you that "the "seconds" of power you get on the USB is the device looking for JTAG.": on boot time, even without trashed PBL, the ME connects to USB properly with vendor/ID=04cc/8500, and sends its ASIC ID (displayed on PC screen). As stated earlier in the thread, I manage to send some commands and receive response from the ME in this state using STE tools (flashkit_cli, sending commands threw flashkit_backend).
It's definetly not any JTAG stuffs. JTAG on the I9070 is accessible on the mainboard via dedicated pads, you can locate using the light schematics provided in the "Service manual" package.
This early boot behaviour is documented in the "flash-tool-backend.html" document (available in s-4.1_vendor_st-ericsson.tar in ./s-4.1_vendor_st-ericsson/vendor/st-ericsson/tools/platform/flash_kit/flash_tool_backend/com.stericsson.sdk.backend.build/doc):
Boot process description
When the peripheral boot sequence starts, the ME sends an asic id to the connected PC tool.
The PC tool then answers with a boot indication.
- If normal, ADL or production is sent as boot indication; this means that the x-loader will start the binary software stored at the corresponding location in the boot image (based on the location stated by the TOC).
- If programming is used as boot indication, the PC will send a completely new set of boot code to the ME. This is used when a loader is downloaded during service mode startup via the Flash Tool Backend.
- When the normal boot indication is sent, Flash Tool backend sends no more data and the ME is booted with the binary software stored in the place where the normal software is stored according to the TOC.
The ADL boot scenario works like this:
1. Flash Tool Backend receives asic id
2. Boot indication ADL is sent
3. Flash tool backend starts LCD and LCM and waits for a loader startup message.
The loader is stored at the ADL location of the boot image (this is supported by the assemble tool).
* If I understand well, as we don't have the sources for the bootloader, your proposal is to grab one from a working device.
That sounds a really good idea!
Here is the complete partition table/PIT of the I9070 (recovered by someone with a Riff box from a GB archive, if I remember well):
(copy/paste it in a traditional editor and add padding to recover the table).
Partition number Filename in archive Name in PIT starting offset HEX Size in bytes HEX
MBR, GPT 0 20000
STE_boot.bin TOC ISSW XLOADER 20000 60000
mmcblk0p10 GT-I9070P_EUR_XX_8G.pit PIT 80000 100000
mmcblk0p6 cspsa.img CSPSA FS 180000 180000
EMPTY 300000 100000
mmcblk0p7 EFS.img EFS 400000 A00000
mmcblk0p2 modemfs.img MODEM FS E00000 100000
mem_init.bin STE MEM INIT 1E00000 80000
power_management.bin PWR MGT 1E80000 80000
mmcblk0p14 normal.bin SBL 1F00000 200000
mmcblk0p16 normal2.bin SBL_2 2100000 200000
mmcblk0p1 param.lfs PARAM 2300000 1000000
mmcblk0p12 ipl.bin IPL MODEM 3300000 200000
mmcblk0p13 modem.bin MODEM 3500000 1000000
mmcblk0p15 kernel.bin KERNEL 4500000 1000000
mmcblk0p17 kernel2.bin KERNEL2 5500000 1000000
mmcblk0p3 system.img SYSTEM 6500000 26400000
mmcblk0p5 userdata.img DATAFS 2C900000 80000000
mmcblk0p4 cache.img CACHEFS AC900000 13200000
mmcblk0p9 hidden.img HIDDEN BFB00000 14000000
mmcblk0p11 ssgtest.img FOTA D3B00000 3200000
mmcblk0p8 ums.rfs UMS D6D00000 FAA00000
--> PBL corresponds to "TOC ISSW XLOADER" (STE_boot.bin in the flash archive) and SLB to normal.bin. So basically we have our boot files. We can extract them from the GB flash archive or from a ROM dump (I have dd'ed every partitions from 2 different I9070P + a full recovery dump from a 9070 provided by Riff box support files I found once I don't remember where).
So, if I have time one of theses days, I'll try to build a flash archive based on these files and try to boot from STE tools on it using "programming" as boot indication.
* Using the knowledge of the I9100 (Galaxy S II): I'm afraid this is a very different hardware, I9100 uses an Exynos 4210, so I hardly see what we could use from there... Could you give us some more advise on that idea?
Regards

Hi!
I had no time working on this for a while: extremely busy at work.
Maybe this weekend...
@cocafe: I've read you know how to extract the initramfs from the kernel, modify, repack, and reflash it. I'll need to do that to modify the "on boot" section of the init.rc to launch the recovery from standard boot. Could you drop me here the command lines to do that? Thanks in advance!

This looks by far the most advanced research into bringing back a hard bricked i9070.
@flentus Did you manage to upload a new bootloader?

Hi,
had to time at all to play with this for a loooong time.
I have grabed a few new phones so me 9070 is now burried deep into a drawer but I really wish to finish this one day because I feel I'm very close to something.
If anybody would like to take over this, feel free, I can provide support for the stuff I have understood (and remember of...)
Regards

Teclast X98 Air 3G Tablet: 9.7" 2048x1536 px - Z3736F - 3G - Android/Windows 8.1

Teclast X98 Air 3G Tablet: 9.7" 2048x1536 px - Z3736F - 3G - Android/Windows 8.1
Hi to everyone,
I would like to apologize because my english is not so good.
This thread could be usefull for to get informations and modding istructions about the tablet Teclast X98 Air 3G.
I'm waiting for delivery via dhl and i guess some of the user here could think that the air 3G is an interesting tablet considering dimensions, cpu, display and the dual OS support .
I would like to point out that given the architecture and hardware of this tablet since the Teclast has released firmware for Android (standard) and Windows 8.1 (still in beta), even though I opened the thread in the Android tablet could be open also a thread in the Windows 8 section.
It was necessary to open a new thread because following the thread on the x98 Air teclast someone has mistakenly flashed a firmware dell'X98 air thinking it would go well on the X98 air 3G.
These are the hardware specifications:
Brand Name: Teclast
Teclast Model: X98 Air 3G
Processor Model: Intel Bay Trail-T Z3736F
Processor Main Frequency: Quad Core, 64-bit, 2.16GHz
GPU: Intel HD Graphics GEN7
Memory Capacity: 2Gb DDR3L
Tablet Data Capacity: 32GB
Screen Size: 9.7"
Display resolution: 2048X1536
Screen Technology : IPS Retina 10 Point touch Capacitive Screen
Dimensions : 240mmx169mmx7.4mm
Camera (Front): 2MP
Second Camera (Back): 5MP
Net Weight: 498g
Network Communiction: Built-in 3G,Bluetooth,Wifi
Extend Port: 3G External,Earphone Jack,OTG,TF card,Mini HDMI
Supporting Language: English,Russian,Spanish,Swedish,Portuguese,Turkish,Italian,German,Chinese,French,Japanese,Polish,Ukrainian,Greek,Hebrew
Other Feature: GPS, G Sensor,Phone Call
Operating System: Android 4.4
Cell Capacity: 8500mAh
OFFICIAL LINK
http://www.teclast.com/zhuanti/X98Air3GWin8/
SOME REVIEWS
http://mikecanex.wordpress.com/2014/09/18/teclast-x98-air-3g-gets-a-review/
http://translate.google.com/transla...s.imp3.net/thread-11183835-1-1.html&sandbox=1
http://bbs.teclast.com/thread-253051-1-1.html (you must be registered)
VIDEOS
Dual boot: www.youtube.com/watch?v=29dtAF39R9c
Dual boot conversion (with some usefull files): https://www.youtube.com/watch?v=qxpU_hFup64
Win 8.1: http://www.youtube.com/watch?v=Q3e_KTfbSK0
Win 8.1 - Multitasking and desktop mode: http://www.youtube.com/watch?feature=player_embedded&v=YHNki9ZBRgQ
Win 8.1 Gaming - Team Fortress 2:http://www.youtube.com/watch?feature=player_embedded&v=V8SpGjc3H4Y
Win 8.1 Gaming - Counter Strike Global Offensive: http://www.youtube.com/watch?v=rvwIxm2mCZw
Win 8.1 Gaming - Asphalt 8 (1366 x 768): http://www.youtube.com/watch?feature=player_embedded&v=qrJAGQ9iEYE
USEFUL TOOLS
VRoot : http://www.mgyun.com/vroot
VRoot chinese version (recommended) : http://d-h.st/lWu (Thanks to SUMMERBREEZE)
SRSroot: http://j.gs/4cyJ
Create ISO with driver : http://www.wincert.net/forum/files/file/5-win-toolkit/
Create bootable USB pen drive : http://rufus.akeo.ie/?locale=it_IT
REPOSITORIES WITH MANY THINGS (thanks to Frontiers and Hendrickson)
http://d-h.st/users/Frontier?fld_id=40727&s=file_size&d=DESC
http://techtablets.com/teclast-x98-air-3g/downloads/
BENCHMARKS
http://www.futuremark.com/hardware/mobile/Teclast+X98+Air+3G/review
OPEN A TECLAST TABLET (thanks to supercowz)
https://www.youtube.com/watch?v=841pMJC_QOk
ENGLISH REVIEW (thanks to Hendrickson)
techtablets.com review
ITALIANS REVIEW AND TUTORIALS (thanks to topdigamma.it)
Topdigamma.it Review
POSSIBILITIES FOR RECHARGE (thanks to cvfancypants)
Included Chinese Charger (TP-U25)- 5.0V/2.5A + Included USB cable
Belkin Boost Up (F8J040kr)- 5.0V/2.4A + Included USB cable
Samsung Charger (EP-TA11KWK)- 5.3V/2.0A (attached USB cable)

ANDROID DEVELOPMENT​
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested for the model C6J6
ROOT INSTRUCTIONS WITH VROOT (thanks to zackman)
http://androidxda.com/download-vroot
VIDEOTUTORIAL VROOT USE
https://www.youtube.com/watch?v=cRgHZSnLmus
Note: someone has done the root through Vroot (english version) only after using Kingroot http://www.kingroot.net/
VIDEOTUTORIAL SRSROOT USE
https://www.youtube.com/watch?v=cRgHZSnLmus
FIRMWARE ANDROID
Teclast: http://dl.vmall.com/c0jpmqz7r5 (passw:C6J6)
Intel: https://01.org/android-ia/downloads
ADB DRIVER
https://mega.co.nz/#!3JshGCLB!6ldn4tPJZlZtDvlR17pmxhqxkrDs4OxxyCJhIHyhZ-4
http://www.koushikdutta.com/post/universal-adb-driver
FRONTIERS X98 TOOLBOX (for easy rooting)
https://www.oboom.com/MCY35B1Z
Just extract it and run "1_Toolbox.bat".
The rest is self explanatory.
If you have some difficulties you can follow these istructions: 25gee's tutorial
TOOLBOX WITH SU - updated to 2.43 - now root works without any problem if someone needs it
https://mega.co.nz/#!Mp50gIoD!ErMC5F...f9Qff_FQY0apcw
ALL THE APKS COMES IN /system/app STOCK ROM (thanks to migui88)
https://mega.co.nz/#!wYBixJaR!U6hO52KW0Wg_hy8OC8OBXP7ATmdpXmMWZNq9mHP2hMQ
ANDROID ROMS ​
CHINESE LITE 4.4.4 ROM (without bloatware and with lollipop keyboards)
https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
SUPERCOWZ X98 Air 3G (C8J7)-Android4.4.4-V2.00-1CF3.rar 556.1 Mb
https://mega.co.nz/#!zVdgWJyS!Vh7zGqX6NcYgXrCf-5v_qmEReZXuicvGzw6h1u5OnGo
jcespi2005 LIte ROM
v2.0 - C6J6 (Based on 2.01 Stock)
https://mega.co.nz/#!oQFU1CbR!NgwcEag4D1fuiVyS5qklyGq2wvMuPfwAwvHmFYzS4r4
v1.0 - C8J7 (Based on 2.02 Stock)
https://mega.co.nz/#!QY9kUQCI!hsPc8259qi0TmJhRmnc42inPEhFmpw-75fYxqrons6k
Description:
Fully rooted (Just launch SuperSU and update binary)
Deodexed
Zipaligned
Chinese Apps deleted (system should boot EN locale)
Nova Launcher as default Launcher (and the only one)
Google Play Fixed (integrated on System partition)
Audio fix by Frontier
Viper4Android
TeclastAutoUpdate (Just in case)
ES File Explorer
Three XML, one stock, one for 1Gb System, 128Mb Cache and 5Gb Data (for Dual Boot) and the other one to flash SYSTEM partition
mirek190 rom v3.1
v3.0 - C6J6
https://mega.co.nz/#!41IQHCDZ!g09l4U...A-30nY3DybSl2g
https://drive.google.com/file/d/0B8B...ew?usp=sharing
v3.1 - C8J7
https://mega.co.nz/#!8s4j0DZS!G6d9Ft...PI6fojDtwprLnM
https://drive.google.com/file/d/0B8B...ew?usp=sharing
v3.1 - C9J7
https://mega.co.nz/#!Yo4i0KJD!dnSXlt...jSH13iHvoHyc0o
https://drive.google.com/file/d/0B8B...ew?usp=sharing
Description:
ability to flash only system ( data and partitions are not touched ) or full flash.
system partition 1 GB instead of 1.5 GB -default but you can change it.
cache 100 MB instead of 1000 MB - is completely enough I tested but you can change it.
data partition 27 GB instead of 25 GB - I added other partition tables for data like 1 , 2, 3, 4, 5 ,6 ,7 ,8 ,9 , 10 GB , only android ( 27 GB ) , only windows 27 GB as well ) or default.
fully rooted
removed all Chinese programs
busy box
init.t
zip alignment
deodexed
changed navigation buttons to Android L looks
resided navigation bar
removed vol buttons and screenshot button from navigation bar - screenshot you can make pressing vol - and power at the same time.
battery with percent
bold fonts on system bar - fonts looks better
lower min brightens
microphone gain fix
clock on the middle of the status bar
4 way power menu - ability boot to droidboot, CWM, Hotboot
some changes in Buildprop for performance.
some optimizations in Framework but still very simple.
added. Google services, Google play, YouTube
google keyboard
adblock ( need root )
resolution changer ( need root )
ViPER4Android FX - need root now sound is really good and noisy
Apex launcher
and other things he don't remember
WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier)​
Required materials:
- A Teclast X98 Air 3G (obviously), battery sufficiently charged (recommended to be fully charged the battery before starting the process). The tablet will be running Windows 8.1 or in FastBoot mode
- The Android DnX BIOS (or Android BIOS) from here
- Tin last available (this season) Android ROM for the X98 Air 3G: X98_Air3G_(C6J6)-Android4.4.2-V1.10.7z
-The tools of the platform upgrade Intel (Intel Manufacturing Tools). These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
Upgrade Preparation tool (Intel Manufacturing Tools)
- Unzip the computer you use to convert (not tablet), the Android ROM given above.
- Unzip one of the two available sets of tools Intel Manufacturing Tools. Inside the folder, you will find some executables that run in the following order and always with administrator privileges:
iSocUSB-Driver-Setup-xxxexe: At some point during the installation, you will know that you have to connect the X98 with USB cable to the computer to install the NAND drivers. H connection is necessary otherwise you can install to see and shape the NAND memory of tablet.
IntelAndroidDrvSetupx.xxexe: We run this installer as an administrator with the tablet plugged in USB. This will install the ADB driver Intel, which appears in the Device Manager (Device Manager) for Windows. (See the picture Figure_1)
ManufacturingFlashTool_Setup_x.xxexe: This tool is used in the final planning "name" (branding) of the tablet and install the fastboot kernel. Install with administrator rights on the proposed application folder (hold down the name of the file for the next step).
- Upon completion of the installation of the Intel Manufacturing Tool, copy the file "CUSTOM_CONFIG.INI" into the folder that the tool was installed (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
The function is said to be installed and functional guest running on X98 Air 3G, host.
Once the installation of the guest operating, it becomes host to the tablet and just run it.
Not supported - for now - the simultaneous execution of Android & Windows.
Remove the microSD card that you probably have the tablet, before initiation.
From Windows host -> Android guest (conversion to Android tablet)
- Unzip the Android DnX BIOS directly into the Windows installation on X98 Air 3G.
- Run with administrative rights (from command line) flash.bat file inside the folder BIOS_X98_Air_3G_android. H process starts with the completion of the installation DnX BIOS displays the message "FPT Operation Passed".
- Turn off the tablet holding the POWER button for 10 seconds.
- Run Intel Manufacturing Tool as administrator.
- On the tablet, hold the VOL +, VOL- and POWER until you see the logo of the Teclast. The tablet will be "stuck" there, is perfectly normal. Connect the tablet to the USB port on your computer, so you will receive the following message: "Entering DnX mode. Waiting for fastboot command..."
- In the Device Manager of Windows (Device Manager), find the Android ADB Interface and right-click -> Properties (Properties). In the window that appears, go to the Details (Details) and there in the drop-down menu choose the Hardware ID (Hardware IDs). Our interest rates VID and PID, as shown in the picture Figure_2.
Transfer the VID and PID values ​​in the respective fields of Manufacturing Tool, section SoC Devices.
- Disables the tablet holding the POWER button for 10 seconds and disconnect the USB.
- We keep the tablet down the VOL- and POWER to enter the mode droidboot. Once this happens, connect the USB cable again, go to the Device Manager Windows (Device Manager) and - as before - we find the values ​​of the PID & VID Android ADB Interface (values ​​are different from the previous Figure_3
Transfer prices PID & VID Manufacturing Tool in their respective fields of unity "Android devices", so o Dialogue Manufacturing Tool will be something like shown in the picture. Press "Apply" and "OK" to save the parameters. Close the application.
- Disconnect the USB cable from the tablet and disable.
- Xanatrechoume the Intel Manufacturing Tool as managers and go to the menu File -> Open. There, choose the folder of ROM (X98_Air_3G_ (C6J6)), find the file "flash.xml" and open it.
- We keep the tablet down the VOL +, VOL- and POWER in order to display the logo of running Teclast DnX, connect the USB cable and Intel Manufacturing Tool begins the process of flashing Android ROM. Wait until the process is complete, disconnect the tablet from the USB and disable the X98 Air 3G.
The conversion process in Android tablet has been completed.
3D GAMES FREEZES FIX (thanks to Akitoyo and acc007)​You can download the patch from here: patch for 3D games freezes
Then follow these steps:
1. Copy the update.zip to the root path of internal storage
2. Click OTA icon, then choose local update
3. Choose update.zip file then apply it, system will reboot automatically
4. There will be a new icon "Fastmode" on the desktop, choose it before launching large 3D games.
You must click it again if you reboot the tablet then play 3D games
If you haven't Teclast OTA app you can download it from here: Teclast update tool
If you want can find the apk attached to this post (fastmode.apk).
If you don't want use apk, use adb shell and then su to become root.Then launch these commands:
Code:
echo 400 >/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
echo 400 >/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
If you want a persistent fix, also after reboot you can create new file install-recovery-2.sh file and put it in ./etc folder with these istructions:
Code:
#!/system/bin/sh
echo 400 >/sys/class/drm/card0/gt_min_freq_mhz
echo 400 >/sys/class/drm/card0/gt_max_freq_mhz
Remember remount /system as rw and chmod this neely created file to 755. You can then execute it or restart to have it automatically started.
For more detailed tutorial look here : jcespi2005's tutorial
GOOGLE PLAY STORE FIX (thanks to Frontier and Hendrickson)​Anyone having issues with Google Play Store - this applies to both Air 3G with the latest 2.0.1 update (will post more information later) and Air II - please apply this fix.
Your OS should be rooted in order for this to work.
- Download the files from here.
- Follow this Hendrickson's Videotutorial
TECLAST X98 AIR 3G ANDROID KITKAT 4.4.4 ROM(OFFICIAL) v2.0.0 (thanks to Frontier)​Download the upgrade from here.
You also need the Intel Manufacturing Tools (get them from here).
After installing this ROM upgrade, you need to apply the Google Play store fix (links and instructions just above).
The procedure to install this ROM is described above in this post. Just ignore the part that describes how to flash the Android BIOS to the tablet, as it is not needed in this case.
This upgrade will erase all data in the internal flash storage (32GB), so make sure you have a recent backup for your applications.
This ROM is OTA safe, after installation the Teclast Software Updater will notify you for an updated ROM; install the update (it's quite small) so the final ROM version would be v2.0.1_20141505 (see Teclast_X98_Air_3G_Android_4_4_4.png).
Visible changes:
- Intel Firmware Updater Tool inside the Android system; you can use it to flash .bin files directly to the tablet within Android (dual-boot system).
- Google Play Store enhancements; I can install applications now that I couldn't with 4.4.2 release (e.g Google+, Paypal and various e-Banking apps).
- A (little) faster boot.
MICROPHONE GAIN FIX FOR ANDROID 4.4.4 (thanks to Frontier)​Here is the final version of the microphone gain fix.
Tests done:
- Voice recognition using Google Now and Google voice typing (even in Greek) works as good as on my OnePlus One with CM11s 44R
- GSM/3G voice calls are clear (I am using Wind GSM network) both with the built-in microphone and via Bluetooth headset (Samsung WEP210).
- Skype voice/video calls are clear, both with internal microphone and the Bluetooth headset.
Connect the tablet with USB cable to a PC with android debug bridge installed.
The tablet needs to have USB debugging enabled.
Open shell and cd to the location of new audio configuration file.
On a PC shell write:
adb root
adb remount
adb push AudioConfigurableDomains.xml /system/etc/parameter-framework/Settings/Audio
adb shell
In the adb shell write:
cd /system/etc/parameter-framework/Settings/Audio
chmod 644 AudioConfigurableDomains.xml
reboot
Done !
XPOSED ON 4.4.4 (thanks to majkel_94)​Ok guys, thanks to @jcespi2005 for Xposed ASUS mod which steer me to the correct solution in xda topic for Xposed
So here it is:
Downolad Xposed Installer (2.6.1 has been tested, modules working ok), install it but don't launch the app or install framework.
Download Root Browser, install and open it.
In root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Profit! You have working the latest Xposed and working KK Gravitybox!
Remember: You can disable xposed at boot by repeatedly pushing a hardware button as the tablet begins to boot. For example you can use Vol + button.
HOW TO UNPACK AND PACK framework-res.apk CORRECTLY (thanks to mirek190)​Follow these instructions. mirek190's tutorial
ITALIAN TUTORIAL FOR UPDATE TO STOCK ROM FROM CUSTOM SELLER ROM (thanks to topdigamma.it)​topdigamma.it Tutorial

DUAL BOOT FAQ + HARDWARE AND LOW LEVEL FIXING​
FAQ
1)Q: While in Intel Manufacturing Tools and trying to flash, the progress bar is stuck at X%
The flash tool does not like funny characters ,should clear up some confusion as to why things aren't working.So before to flash please try removing the chinese characters from the file name. It screwed you up on something else having chinese in the name.
At 0%: Well, reconnect your device again, check your VID and PID values in settings, check if your drivers are properly installed, replace a cable if it is faulty, check that you're in DNX mode, basically, the flashing didn't even start.
If you have the right pid/vid from the device manager,unplug the device, close the app and restart it, select the flash.xml (should say ready to flash) then plug the device in while in DnX mode and it should begin.
At 5%: Mostly due to the fact that "Custom_config.ini" was not copied to the IMT directory, or there are some other programs that is blocking the progress, try changing a computer and flash again.
At 10 or 11%: Mostly due to wrong settings or parameters, check Device Manager in Windows for any missing drivers, check that the downloaded ROM is not damaged, or that the tablet is not already bricked. Also, this software is very sensitive to the USB port that it was first installed on, so try plugging it back to the same USB port that you plugged it during the install process. (Yes, you have to plug the device in during the install process, if you missed this out, uninstall all the drivers and redo the installation properly).Sometime help to try a different ROM, just to clarify you have copied the "custom_config" file to the Intel Manufacturer Tool folder right. It should get to 10% for about 5-10 seconds then make a disconnection sound and suddenly jump to 15% and continue.
At 89 or 90%: The files written at this stage are larger, so it might take a while longer, but if it is really stuck here, probably the USB cable is faulty. Replacing a cable and flashing again should solve the problem, or just simply leave the tablet and cables still (do not move them around) and try again.
If the flash freezes at 90% a solution could to be increase the timeout values in the program facturing flash tool.
At any other points: Might be due to faulty cables, or simply just try again!
2) Q: I flashed android bios, now I can not get in to droidboot mode by pressing Vol + and POWER. The tablet always gets into EFI shell command interface. I can only get to DnX mode by pressing VOL+ , VOL- and POWER. Any solutions?
A: Follow this steps valid for C6J6 and C8J7 model :
Open Intel manufacturing tools,then open file menu and go to the settings.
Put this value to SoC Devices: VID: 8087 PID:0A65
Put this value to Androird Device: VID: 8087 PID: 09EF
Click on apply and then on ok.
Disconnect the USB cable from the tablet and turn off your tablet (important)
Download the Android 4.4.4 ROM for C6J6 and C8J7 by supercows (link above)
Then in Intel Manufacturing Tool and go to the menu File -> Open. There, choose the folder of X98 Air 3G (C8J7.C6J6) lite 4Gb or 8GB and choice "flash.xml" for your device 4Gb or 8GB and open it.
Keep pressed VOL +, VOL- and POWER button until the tablet go to the dnx mode
Connect the USB cable and Intel Manufacturing Tool begins the process of flashing Android ROM.
Wait until the process is complete.
Disconnect the tablet from the USB and and turn off your tablet .
Connect the usb keyboard to the tablet and turn on your tablet, you could get shell command error again
Just type exit and you see the tablet go to the android version
When go to the android you must change your bios with ifwiupdate and you can flash dualboot bios or new android bios from first post
3) Q: I have problems getting into Android from the dual boot menu! Windows is okay.
A: If there are any problems getting into Android from the dual boot menu, change this option in the BIOS. Change "Boot Architecture" to "OS Boot Menu Only".
View attachment 3048901
4) Q: After shutting down the table in Windows, it takes very long before I can power it on again.
A: Turn off "Fast Startup" option in Windows Power Options. Another way is to navigate to "C:\Windows\System32", find "SlidetoShutDown.exe" and use that to shut down.
5) Q: The time in Android and Windows is not synchronised!
A: Go to "Run", type in "regedit", then navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Add in a new REG_DWORD, "RealTimeIsUniversal" and set its value to 1
6) Q: I plugged the tablet into the charger and it shows as charging but after a while I noticed that the battery percentage dropped!
A: Check the cable, it should be of good quality and as short as possible. Original teclast cable is good, not too long and thick enough. Best to use short cable of 5cm. This is due to high current and low voltage of the tablet.
7) Q: I'm on Android 4.4.2 and this tutorial needs me to upgrade to 4.4.4. How
A: Go to post #2, download the 4.4.4 ROM from there, start by following the tutorial from the line "WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier)" onwards all the way until you reach GOOGLE PLAY STORE FIX (thanks to Frontier). If you see the line "From Windows host -> Android guest (conversion to Android tablet)" in the tutorial, do not worry, because this process is used for both purposes, from Android to Android or Windows to Android, both are applicable.
8) Q: I flashed my tablet to dual boot OS already, but now I want to reinstall only one OS! How can I do it without having to reinstall everything?
A: If you want to reinstall Android only (leaving Windows unharmed):
One way is to flash just "system.img" through the Intel Manufacturing Tools (try this way first).
Download from here the zip named "ONLY FLASH system.img": http://1drv.ms/1s8dci8
Replace the "flash.xml" in your ROM folder with the one in this version.
Then flash as per normal using IMT.
This "flash.xml" will instruct the IMT to flash only the "system.img" file which is Android OS.
If that doesn't work, we will try flashing all components of the ROM without re-partitioning the whole eMMC,
Download from here the zip named "ONLY FLASH ANDROID PARTITIONS": http://1drv.ms/1s8dci8
Replace the "flash.xml" in your ROM folder with the one in this version.
Then flash as per normal using IMT.
If you want to reinstall Windows only (leaving Android unharmed):
Prepare your USB Drive with the Windows image.
Boot into Windows first, then restart and plug in the OTG cable, USB HUB, keyboard, and USB Drive.
Enter BIOS by pressing "ESC" key during boot and under the "Save and Exit" menu, scroll down to the "Boot Override" option, find the USB drive and select it to boot from it. The BIOS restart the tablet and will boot into the USB Drive so Windows install should start.
Remember the USB bootable stick must be created with Fat32 file system and GPT table partitioning.
9) Q: Help! My touchscreen is inverted!
A: (Thanks to @krisbliz):
Download the files from @krisbliz post here, and copy the files into C:\Windows
now run gpedit.msc
computer configuration
scripts (startup/shutdown)
startup
add
browse for reset driver.bat
10) Q: How to reinstall windows without reinstall android ? I cannot change the language and even updates from winddows update,every time when I put usb prepared and trying to install windows it working installation and after 65% shows installation error 0xc1440137 0x2000c and going back to previous instal (chinese) to windows
A: (Thanks to @mohamad_skiller):
Connect usb keyboard and usb windows instalition to your hub then
Enter BIOS by pressing "ESC" key during boot and under the "Save and Exit" menu, scroll down to the "Boot Override" option, find the USB drive and select it to boot from it.
The BIOS will boot into the USB Drive and Windows install should start.
11) Q: I have installed dualboot bios with a success. When I plug in usb to install the IntelAndroidDrvSetup1.5.0.exe, in the boot menu I can see a Windows in the right center of screen and in the right top corner two small icons of android and windows which I can check. I dont see Android logo in the center of screen?
A: (Thanks to @jcespi2005):
Sounds you install windows on top of android partitions.So check what partitions do you have in windows partition manager...If you deleted the android ones, you'll need to start over starting installing android again.
In any case, make sure you've followed these steps correctly:
blackman818's tutorial
12) Q: Why Microsoft Store doesnt work?
A: (Thanks to @Hendrickson ):
Run the troubleshooter (Search and type trouble shooter) And run it for the Store, this should re-install the drivers
13) Q: Why camera doesnt shows anything (the screen turns black and i have to exit to desktop)?
A: (Thanks to @Hendrickson ):
Reinstall the camera.inf and OV and GS camera drivers from the Air 3G drivers
14) Q: I can't use touchsceen and also screen rotation is not working. During installation , Windows stopped at language selection ,i had to connect usb moude and keyboard to make selection, is this normal?
A: (Thanks to @25gee ):
Yes,continue the installation and use drivers zip on the first page.Install the driver under gyroscope and run the registry file.Go into device manager,find the unknown device,install drivers and point manually to the drivers folder (it will install but fail to enable,this is normal) from here simply right click on the display,disable it and reenable, you can do the same with the 2 I/O devices for the orientation and accelerometer to fix the inverted screen rotation
15) Q: I partitioned my 32 GB SD card and formatted the smaller partition EXT4. Link2SD recognized the partition but it "fails to create MOUNT SCRIPT.
A: (Thanks to @kinhvanhoa ):
Probably you forgot to format your EXT4 partition on the SD CARD as "PRIMARY PARTITION."
Please make sure the EXT4 Partition which should be smaller than FAT32 partition, must be set as "PRIMARY" (FAT 32 as well).
Then, use LINK2SD on the Rooted Android, it works fine and allows apps to be moved to the EXT4 partition on the SD card.
16) Q: How can i change the intel turbo mode on to off? How can i enter in the bios mode? Only few games works, others freeze!.
A: (Thanks to @SUMMERBREEZE ):
Find an USB keyboard first and plug OTG cable to the tablet and turn it off. Turn the tablet on and immediately press ESC button. And follow the images (bios_1 and bios_2) i attached and do the settings carefuly. f4 save & exit
17) Q: I have problem with the dual boot bios, now I don't arrive any more to the page where there are the icons of the Android and Window (that I never saw it). Please could anybody known what happens, I am stacked on the installation of windows?
A: (Thanks to @grigoris_a ):
From switched off press power button once to boot and keep holding vol up key pressed
18) Q: I have installed dualboot bios with a success. The icon of windows is not showed,why?
A: (Thanks to @grigoris_a):
If you don't see windows icon it means the USB is not bootable.Try getting into bios and see if the USB drive is detected and check the file system on your windows usb drive it should be FAT32. Often the problem is inside the bios, maybe is enabled the options the EFI format on the boot option, disabled it the icon of windows appears and then you can started the installation.
18) Q: I start from Windows 8.1 then I installed the Dual Boot Bios (No problem).
I restart to the bios, power down the tablet and power up again and use the Windows 8.1 again (without reinstall anything) with 60hz. Everything perfect but... right now I cant install android because my tablet is not recognize by the PC I power off by pressing 10 seconds the power button. Then while its connected I power it up and shows the battery meter but the PC dont do anything so I cant use any program to flash android, any idea? I tried different cables and nothing
A: (Thanks to @Petepe10):
This is the normal way, do not know about dualboot though: Power up (vol up down power press) until screen shows dnx mode, and then connect cable. Flash starts automatically (provided pc is ready to flash of course)
19) Q: How to switch from an OS to another?
A: (Thanks to @BPM):
Power off the device and then press and hold vol+ and power until you see the bootmenu
20) Q: On the lockscreen in Windows the text in the lower right corner is chinese.
Sometimes there pops up chinese messages in the infobar (lower right corner in windows - left to the clock).How can i remove this?
A: (Thanks to @smartchip):
On Control panel : Clock, Language and Region : Language : Change date, time or number formats. On Formats tab - Match Windows display language (should be default). On Location tab - change "Home location" to get your Start Menu tiles to load news, recipes, etc from your country (open the apps when you're done and refresh). On Administrative tab - "Welcome screen and new user accounts" click "Copy settings", apply to all.
21) Q: I have teclast x98 air 3g dualboot version but accidentaly i touch in corner to swich off choosing the system, now i have only android.How ca I return to dual boot menu?
A: (Thanks to @smartchip):
Hold power + volume up to power on. You'll get the menu back
22) Q: On Windows is there any way to hibernate the tablet? I try to hibernate but doesnt works well,the tablets power off but you have to press power button for 10s to power it up again, and you start windows normally?
A: (Thanks to @seba2000):
Make a shortcut on your desktop to C:\Windows\System32\rundll32.exe PowrProf.dll, SetSuspendState Hibernate
and save it as "Hibernate" for instance.You can pin it to start as well.When you will run this shurtcut tablet will hibernate. Remember that after you will run this command (shortcut) you need to wait a bit before you will be able to switch on again (10-15 sec) . Do not try to switch on immediately - Windows needs time to dump all data from RAM to hard disk (need time to hibernate). In this tablet there is missing any led which show disk activity so you just need be patient.
After 10-15 sec you will be able to switch on by single power button press.
If you want add hibernate and sleep option in Windows, follow the vpx tutorial
23) Q:Why there is one hour difference between android and windows ?
A: (Thanks to @G3n3R4L):
Hit Start and type regedit.exe in the search box. Hit Enter and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\TimeZoneInformation. Right click anywhere in the right pane and hit New > DWORD (32-bit) Value. Name it RealTimeIsUniversal, then double click on it and give it a value of 1.
and done, time in windows is exactly the same as android under the correct time zone.
If you want to do these steps automatically you can use this reg file: abanglek's X98DualClockFix.zip
25) Q:Windows only reporting 1 battery cell, battery gets stuck at 7% for a few hours as mentioned previously here. Did anyone manage to fix the issue in Windows?
A: (Thanks to @grigoris_a):
1.Fully charge the tablet
2 Run cmd as admin and paste this command
powercfg-setdcvalueindex SCHEME_CURRENT SUB_BATTERY BATACTIONCRIT 0
3 Use the tablet until it shuts down
4 Charge the tablet without pushing power button until it charges fully.(let it overnight)
24) Q:Why I can't enter in fastboot mode?
A: (Thanks to @jcespi2005):
Just power off (press power off for 10 seconds), wait some time, 5 minutes, and press VOL+ VOL- and then power on until fastmode shows on the tablet. When you connect the tablet on fastmode, the Manufacturing tool just boot a droidmode image like this:
01/14/15 00:14:29.870 INFO : Port 0/0/4 #0: Booting droidboot image - SN : Baytrail00005B06
01/14/15 00:14:32.914 INFO : Port 0/0/4 #0: Booting to droidboot.img success - SN : Baytrail00005B06
25) Q: The brightness auto dimming up and down by itself. But This tablet no light sensor and cannot enable/disabled auto brightness.
A: (Thanks to @melvincz):
Go to the Intel Graphics settings utility (find it in the tray), choose Power section and disable all energy savings functionality. That will fix the auto-dimming issue.
That's all! ENJOY! If there are any questions feel free to post in the forum. Thanks!
HARDWARE AND LOW LEVEL FIXING
FLASH BIOS WITH THE USB PROGRAMMER AND CLIP (thanks to Hendrickson)
You can follow the tutorial here:
Russian Tutorial
The clip took a few goes to connect and it finally do when you hear the windows beep beep that new hardware is detected. Flashed and verified and boots fine. Windows 8.1 installed the drivers itself. You don't need to install them.
Some tips, I did it with the battery connected and fully charged. I used the 25xx slot on the usb programmer and the clip #1 is the colored cable of the 8. #1 on the clip to the . connector on the winbond chip itself.
Flashing took around a minute its quick.
DISPLAY BRIGHTNESS THROTTLING (thanks to Petepe10)
I think I found a way to prevent that the display is heavily dimmed due to a thermal event. It is in thermal_throttle_config.xml in system/etc. My interpretation is that by the mod below the brightness reduction is not immediately to 40 percent but goes down in steps to 80 60 40. Wouldn't you agree? I have not found the trigger settings yet though. The xml is editable (I use total commander), reboot afterwards. I will test some more. Of course such thermal mods are not without risk, so be warned..
Code:
<!--Cooling Devices-->
<ContributingDeviceInfo>
<CDeviceName>Display</CDeviceName>
<CDeviceID>1</CDeviceID>
<CDeviceClassPath>com.android.server.thermal.Brigh tnessControl</CDeviceClassPath>
<CDeviceThrottlePath>none</CDeviceThrottlePath>
<ThrottleValues>
<!--ThrottleNormal>100</ThrottleNormal-->
<!--ThrottleWarning>40</ThrottleWarning-->
<!--ThrottleAlert>40</ThrottleAlert-->
<!--ThrottleCritical>40</ThrottleCritical-->
<ThrottleNormal>100</ThrottleNormal>
<ThrottleWarning>80</ThrottleWarning>
<ThrottleAlert>60</ThrottleAlert>
<ThrottleCritical>40</ThrottleCritical>
</ThrottleValues>
</ContributingDeviceInfo>
FIX EMMC (thanks to stachoo777)
You can follow the tutorial here:
stachoo777 Tutorial
Be aware of broken droidboot mode when updating to newest ifwi bios for c6j6. One hint for this is that efi shell is like dos so if you want to go to USB just type "fs1:"
FIX PROBLEMS OF HEAT DISSIPATION (thanks to acc007)
acc007 Tutorial
FIX HEADSET PROBLEM(thanks to Hendrickson )
If with music, it sounds like it's being played through a tunnel, or been compressed down to something like 8kbps. The main instrument tracks usually sound fine, but the vocal track is heavily muted and in some tracks practically inaudible; it's also tinny and a bit distorted.
It's not defective, it's a Iphone style jack, if you don't fully insert your 3.5 plug it will sound normal. Or use a headphone without a mic or a converter like this one: http://www.ebay.com/itm/301385140519?_trksid=p2060778.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT

WINDOWS DEVELOPMENT​
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested for the model C6J6
WINDOWS 8.1 PRO ISO
http://getintopc.com/softwares/operating-systems/windows-8-1-download/
WINDOWS 8.1 WITH BING (Teclast beta version - no driver nedeed)
https://drive.google.com/folderview...&usp=sharing&tid=0BzgIeN_XB6mlUmFieDdxa3JkUHc
WINDOWS 8.1 LANGUAGE PACK
https://social.technet.microsoft.co...uage-pack-for-windows-81?forum=w8itprogeneral
WINDOWS 8/8.1 TECLAST COMPONENTS DRIVER
https://mega.co.nz/#!tJdHCIAT!agSun8Wa1tOx_3tL8YMuS19j1i5wWG2WUJPprmTbTCs
ADB DRIVER
https://mega.co.nz/#!3JshGCLB!6ldn4tPJZlZtDvlR17pmxhqxkrDs4OxxyCJhIHyhZ-4
Note: The camera driver not work correctlly on Windows 8.1, after OS installation it's necessary to install ManyCam Pro to get a satisfactory use of the camera
ANDROID => WINDOWS 8.1 PROCEDURE (thanks to Frontier)​
Required materials:
- A USB stick of 256MB (generally small), FAT32 configuration with label (label) WINPE (uppercase).
- A USB stick capacity of at least 8GB, formatted system NTFS. This will pass the installation files Windows 8.1.
- A USB hub to connect these two sticks in OTG cable X98 Air 3G. The hub would be good to have its own power supply.
- A Teclast X98 Air 3G (obviously), battery sufficiently charged (recommended to be fully charged the battery before you start the process).
Preparing USB sticks:
- Unzip the file WinPE_User_20140814.7z and copy all files directly on the root directory of the USB stick WINPE. See the picture Figure_1.
- Unzip the installation files for Windows 8.1 DVD into a folder named "images", which should be on the root directory of the USB stick of 8GB (with NTFS configuration). The Windows 8.1 version with Bing for X98 Air 3G is here (5 files total): Part1 , Part2 , Part3 , Part4 , Part5 . Inside the folder images, you need to have the files install.txt, install.wim, UnattendAudit.xml, UnattendUser.xml, WIMPART.TXT, Winre.wim. If you want to use your own image and make the USB stick with a tool (Rufus, etc), drivers for the Windows X98 Air 3G is here . If you use Rufus remember to use MBR for UEFI, not GPT!.
See the picture Figure_2
Preparation of material:
- X98 Air 3G enabled USB debugging in the settings.
- On the PC, will be available the tool adb (part of the platform SDK) and have installed the ADB drivers (adbdriver.com). The PC should recognize the X98 Air 3G before starting the procedure.
- It is recommended to install Intel Manufacturing Tools before turning the tablet on Windows tablet, in order to be able to restore it to operating condition if the procedure fails. These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
Upgrade Preparation tool (Intel Manufacturing Tools)
- Unzip the computer you use to convert (not tablet), the Android ROM given above.
- Unzip one of the two available sets of tools Intel Manufacturing Tools. Inside the folder, you will find some executables that run in the following order and always with administrator privileges:
iSocUSB-Driver-Setup-xxxexe: At some point during the installation, you will know that you have to connect the X98 with USB cable to the computer to install the NAND drivers. H connection is necessary otherwise you can install to see and shape the NAND memory of tablet.
IntelAndroidDrvSetupx.xxexe: We run this installer as an administrator with the tablet plugged in USB. This will install the ADB driver Intel, which appears in the Device Manager (Device Manager) for Windows.
ManufacturingFlashTool_Setup_x.xxexe: This tool is used in the final planning "name" (branding) of the tablet and install the fastboot kernel. Install with administrator rights on the proposed application folder (hold down the name of the file for the next step).
- Upon completion of the installation of the Intel Manufacturing Tool, copy the file "CUSTOM_CONFIG.INI" into the folder that the tool was installed (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
The function is said to be installed and the guest OS you are running on X98 Air 3G, host.
Once the installation of the guest operating, it is now host to the tablet and just run it.
Not supported - for now - the simultaneous execution of Android & Windows.
Remove the microSD card that you probably have the tablet, before initiation.
From Android host -> Windows guest (conversion to Windows tablet)
- Uncompress file BIOS_X98_Air_3G_android_to_windows.7z folder without spaces in the name (eg C: \ Temp). We should be inside the unzipped folder, a subfolder 'fpt-tools-package'.
- Connect the tablet to the PC and wait (in Windows) to recognize.
- If you have rooted your device,from a command prompt (with administrator rights), we give the following commands:
adb push c:\temp\fpt-tools-package data/local/tmp/
adb shell
cd data/local/tmp
chmod 0777 FPT
su
./FPT -F X98Air3G.bin
- If you have not rooted your device,from a command prompt (with administrator rights), we give the following commands:
adb push c:\temp\fpt-tools-package data/local/tmp/
adb root
adb shell
cd data/local/tmp
chmod 0777 FPT
./FPT -F X98Air3G.bin
- Once the execution of the last command and display the message "FPT Operation Passed", disable the tablet holding and hold POWER. See the picture Figure_3.
- Connect the two USB sticks in USB hub and the hub of the OTG port X98 Air 3G. Activating the X98 Air 3G with the POWER button, and automatically starts the installation process of Windows 8.1. The whole process takes a long time - and for this reason it is recommended that you fully charged the battery - and requires no user intervention. See the picture Figure_4.
If you do not automatically start the process, connect a USB keyboard to the hub, then reset the tablet (CTRL-ALT-DEL or off) and after doing reset, enter the UEFI BIOS by pressing DEL. At the boot menu, go to the Boot Override option and press ENTER on the USB stick (small in size) to do boot from there. See the picture Figure_5.
- When the message "WIMboot image deployment COMPLETE. Type EXIT from command prompt to restart or turn off the device." You can disconnect the USB hub and terminate the tablet. See the picture Figure_6.
The process of converting the X98 Air 3G in Windows tablet, complete!
After the Android to Windows conversion is it recommended first install the Gsensor, run the kxaccel-win8-x86-dbg-intel.exe that comes in the folder GSENSOR in the attached zip in and then execute the reg file.
Finally copy the TouchSetting.gt to C:\Windows\inf folder and reboot.
Everything should go smoothly now.
For the Italian friends I have prepared a simplified guide in Italian pdf.
CHINESE TOOL FOR CLEAN WINDOWS FOLDER AND FREE MORE SPACE (thanks to BoORDeL and keepfishes)​
The zipped file is attached to this post (Windows_Cleaner.zip).
Execute the exe and click on button showed in Figure_7.
You will see a list of folder that can be cleaned (if this doesn't happen change permissions on your windows folder : http://tipsandtricksforum.com/thread-223.html )
Than select the checkbox near folders name and let the program clean them by pressing button as shown in the Figure_8
INVERTED CAMERA FIX (thanks to ro11er and Hendrickson)​
You can downlad the fix from this url:
Inverted Camera FIX
You need to uninstall these three devices and reboot:
Kionix KXCJ9 Accelerometer SPB
Goodix Touch HID
Intel Graphics
Then after reboot install in this order from the attachment download in above link.
Intel Graphics
Goodix Touch
kxaccel-win8-x86-dbg-intel.exe and registry
Once registry entry is done and reboot monitor will be reversed. You must change registry to this value: 01 00 00 01 01 00 02
Very important: Do not do video drivers update or u will loose all your configuration!
UPDATED WIRELESS AND BLUETOOTH DRIVERS (thanks to Hendrickson)​If you have problems with wireless when using bluetooth at the same time it was so damn slow, you can use updated bluetooth and Wireless drivers attached to this post ( Air_3G_Updated_WLAN_and_BT_drivers.zip).
These drivers were discovered November 4th from Dell site and seems to have fixed the issue.
TUTORIAL FOR DOWNLOAD WINDOWS METRO APP WITH IDM (thanks to mohamad_skiller)​For read tutorial click here: Mohamad_skiller's tutorial
BATTERY PROBLEM FIX (thanks to puzdar )​For read tutorial click here: puzdar's tutorial
HOW TO CHANGE LANGUAGE FROM CHINESE (thanks to Hendrickson )​For see the tutorial click here: Hendrickson's tutorial

DUAL BOOT DEVELOPMENT​
TUTORIAL VIDEOS
Hendrickson's complete Tutorial
This tutorial cover:
intel mfg tools installation
drivers
flashing
partitions
making a bootable usb drive
windows installation
windows drivers + fixes installation
DEMO VIDEOS
supercowz's Teclast X98 air 3G dual boot
UPGRADE FLOW PROCESS SCHEME(thanks to Petepe10)
upgrade flow process scheme
LAST BIOS
Be very carefull, you could brick your tablet if you use a version of bios not in conformity with your tablet model.I take absolutely no responsibility for damage caused by the flash of the following bios.
C9J8 ( Warning, the tablet could became instable with random rebooting and even if you turned it off you have to wait 2 min to power it again)
mirek190 modified C9J8 bios
AIR II DUAL (compatible with C6J6)
grigoris_a AIR II DUAL bios
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested on C6J6 only. For C8J7, there are some additional pointers along the way, do look out. All files in this tutorial are by default for C6J6, unless otherwise stated. Is highly recommend reading through the whole post first before touching your tablet to prevent errors, or worse, bricking the whole thing
Install dual boot(C6J6) - KEEPFISHES TUTORIAL (thanks to supercowz, mohamad_skiller, ro11er and Frontier)​
Please before you begin to read this tutorial is better to watch the Hendrickson's complete Tutorial video that show and explain all the needed steps for dual boot implementation.
The original post of keepfishes is here. in case he make some updates and it is not shown in this post
I found that the tutorial on the first page lacked detail and some steps were not shown clearly, so I made a new one that I think is easier to follow for newcomers! Will add screenshots soon.
Dual boot BIOS benefits:
Fixes 60Hz refresh rate for Windows 32 bit system
Probably on old bios there are low voltage settings for GPU that makes some problems with 3D games,after updated to dual bios no problems at all for many users
Drawbacks:
BIOS settings very little
No boot menu (so no easy way to reinstall Windows with a USB drive)
Time in Windows will mess up when using dual OS
The flashing process is roughly as such:
Click image for larger version
View attachment 3050134
Many of us have different start points, some are coming from Android, some from Windows, but it does not matter. First thing is to flash with dual boot BIOS, which is most important.
WARNING: (Be very careful, this part may brick your device. After you get past here, you can practically do anything you want and there is almost no risk of bricking your device, so pay attention here!)
Get dual boot BIOS files here (both C6J6 and C8J7): http://pan.baidu.com/s/1sjK4Zbn
View attachment 3048864
Extract the BIOS "完美双系统BIOS.7z" and copy the contents to the tablet.
Note the filepath on the tablet, you will need it later.
1a) Flash BIOS from existing Android system
NOTE:
If your existing Android version is 4.4.4, you can use the "UpdateIFWI.apk" that was installed on the system to flash the BIOS.
If Android version is 4.4.2 on C6J6 and there is an "UpdateIFWI.apk" on it, there have been reports that it does not flash properly. (as reported by @ambrosio5)
Current advice is to update to 4.4.4 before proceeding. .For instructions on how to upgrade to 4.4.4 from other previous Android versions, see FAQ 7 below.
From the tablet itself, run “UpdateIFWI.apk”, select "Browser" and point it to the filepath of the BIOS named "X98Air3GDuala.bin''.
STOP: Make sure you have at least 50% battery and chose the correct file! If this fails, it might BRICK!
Now flash the BIOS.
1b) Flash BIOS from existing Windows system
From the tablet itself, RUN AS ADMIN the .bat file in the folder (the one with chinese words) provided.
View attachment 3048853
After you see the Green line “FPT Operation passed”, it’s good news.
Now reboot the system and you will be taken to the BIOS screen. Just igonore it and press power button for 10 seconds to turn it off.
2) Installing ANDROID first (must be done before Windows)
Now we need to FIRST install ANDROID. This step will wipe out your whole tablet (INCLUDING ALL PREVIOUS WINDOWS AND ANDROID PARTITIONS AND DATA)
ON ANOTHER PC (not tablet), download the Android 4.4.4 Lite ROM here: https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
OR
SUPERCOWZ ANDROID 4.4.4 C6J6 AND C7J8 ROM For Both: https://mega.co.nz/#!zVdgWJyS!Vh7zGqX6NcYgXrCf-5v_qmEReZXuicvGzw6h1u5OnGo
OR
USE ANY OTHER ROM YOU WISH
Download this modified "partition.tbl" file from the Chinese: http://pan.baidu.com/s/1qWnxc4G
Inside are two folders, the 5000 one is 5GB Android space, the 8000 one is 8GB Android space. I personally used 5GB, because I want to leave more space for Windows.
View attachment 3048857
Download and install Notepad++, we need to edit "partition.tbl" file below, the Notepad.exe and Wordpad.exe built in on Windows DOES NOT SAVE THE FILE CORRECTLY AND WILL NOT WORK!
Extract the contents of the ROM to a folder. You should see a "partition.tbl" file inside.
This file controls how the 32GB eMMC in the tablet will be partitioned in this step.
View attachment 3048867
Copy the "partition.tbl" file FROM the Chinese download (either 5000 or 8000) TO the Android ROM folder that you extracted. Replace the original "partition.tbl" file that came with the ROM.
Edit the "partition.tbl" file in the Android ROM folder, find the second last line, which is "add -b 5931048 -s 10240000 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0"
and change the highlighted number to the value of user space you want in Android. The number is a multiple of 2048, so let's say if I want 500MB user space, I would have to multiply 500MB x 2048 = 1024000 and input "1024000".
View attachment 3048872
I tried 300MB but it was too small, I think 500MB would be good if you're planning to use more Windows. Save the file!
Credits to FRONTIER for Android ROM flashing instructions (I made a number of changes):
The tools of the platform upgrade Intel (Intel Manufacturing Tools). These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
- Unzip the downloaded Intel Manufacturing Tools. Inside the folder, you will find some executables. RUN THEM IN THE FOLLOWING ORDER WITH ADMIN RIGHTS:
iSocUSB-Driver-Setup-xxxexe: During the installation, DO NOT PLUG IN YOUR TABLET. Near the end of the install, there will be a text asking saying that you need to plug in tablet and power cycle to complete installation. ONLY PLUG IN YOUR TABLET THEN, and do as the instruction says. After you're done, click Finish. After install, you should see Intel SOC device in your device manager.
IntelAndroidDrvSetupx.xxexe: Plug in your tablet, and MAKE SURE that your computer RECOGNISES your tablet. You will see unknown ADB device if you plug in the tablet. Now run this program as ADMIN, this will install the ADB driver for the unknown device. In device manager, if it still shows unknown device after install, manually update the driver in device manager and browse to the install directory of the driver, it will then install the driver from there.
ManufacturingFlashTool_Setup_x.xxexe: Install with ADMIN rights, this will install the Flash tool with the Lightning icon, which is the GUI interface we use to flash our tablet.
Copy the file "CUSTOM_CONFIG.INI" from the downloaded folder into the install folder of IMT (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
Remove the microSD card from tablet.
Run Intel Manufacturing Tools (the one with Lightning icon), In the Settings menu, change the VID and PID values to this, then click apply and OK:
If you're using Windows XP, your VID and PID values may be different to the ones shown. Check the instructions on Post #2 on how to get the values.
View attachment 3051023
Close the IMT application and launch it again. Go to the menu File -> Open. There, choose the folder of ROM you want to flash, find the file "flash.xml" and open it. The "flash.xml" file which tells IMT how to flash the tablet's eMMC.
(IF YOU ARE USING SUPERCOWZ Android 4.4.4 C6J6 and C7J8 ROM, here are his instructions, :
flash with ManufacturingFlashTool
for C6J6 open in ManufacturingFlashTool :
flashC6J6-4GB.xml or flashC6J6-8GB.xml
for C8J7 open in ManufacturingFlashTool :
flashC8J7-4GB.xml or flashC8J7-8GB.xml
this last action dedicate 4 or 8 gb of rom space for Android and you can install windows in 18.5 or22.5 gb free rom space.
Then reinstall Android rom as before (open manufacture flash tools and select flash.xml)
After install android rom you can install windows as before (using bootable windows usb disk and select 18.5 or 22.5gb rom free))
-----------------------------------------------------------------------------------------------------------------
8) Turn off the tablet holding the POWER button for 10 seconds.
- Run Intel Manufacturing Tool as administrator.
- On the tablet, hold the VOL +, VOL- and POWER until you see the "Entering DnX mode. Waiting for fastboot command..."
Click image for larger version
View attachment 3048873
- Connect the USB cable to the computer and flashing will start.
- After progress bar is green and 100%, hold down power button for 10 seconds to turn off tablet.
If the progress bar turns red, take note of the percentage that it stopped at, and refer to FAQ 1 below.
Click image for larger version
View attachment 3048876
After finishing these steps, Android is now installed on the tablet, and if you power it up, you can see the dual boot menu with the Android logo.
Click image for larger version
View attachment 3048880
If you're happy with ANDROID only without Windows, you can stop here and just boot into Android! You can go on to do the Google play store fix and others...
3) Installing Windows
If you plug in your USB drive via the OTG cable and boot up, you will see the boot menu with an Android icon and a small Windows icon. (If you don't see the boot menu at all, shut down the tablet and press Vol + and Power button until the boot menu appears).
This small Windows icon is the only way to get the BIOS to boot into your USB drive to install Windows. This dual boot BIOS has no boot menu, and in the BIOS there is no option to select to boot from USB, so this is the only way to boot to a USB drive that I know of so far...
(If you already have a USB stick prepared, skip this section in BLUE)
Preparing your Windows USB Stick:
You can install Windows via the traditional method which involves the GUI (in which case you will need an OTG HUB to plug in the USB Drive and mouse together) OR you can use a downloaded wimboot image (no need for HUB and mouse, just a thumbdrive will do).
Whatever the case, make sure your USB Drive is formatted as FAT32! Very important!
I used this wimboot image that automatically uses WinPE to get through the whole install process automatically without needing a single mouse click, which also has all the drivers and everything installed and working properly:
Waiting for repost on mega...
Link: http://pan.baidu.com/s/1hqIfAle
password: zhec
Extract the downloaded files and then copy all the contents into the root of the USB Drive. NO NEED FOR RUFUS!
If you are not using the above images, and use other Windows ISO or images as found in Page 1 or if you want to make your own images, you will need this software RUFUS:https://rufus.akeo.ie/
Follow tutorial here on creating the USB Drive: http://www.techverse.net/how-to-create-bootable-usb-flash-drive-install-windows-8-1/
Remember to use MBR for UEFI, not GPT!
If your Windows doesn't come with drivers, you can download them from here and install them:
https://mega.co.nz/#!tJdHCIAT!agSun8Wa1tOx_3tL8YMuS19j1i5wWG2WUJPprmTbTCs
Here also a Windows 8.1 PRO version with drivers and English/French language pack (thanks to supercowz):
Win 8.1 PRO with driver and eng/fr language pack
Plug in the USB drive via OTG cable or HUB, and choose the small Windows icon until it turns blue, then hit the grey button below and Windows installation should start.
If it asks you for which partition to install to, you will see a great many partitions there (due to Android), don't worry, it is normal. Typically you will install Windows to the largest available partition. (Unless you set the Android user space partition in the "partition.tbl" file previously to be huge)
DO NOT TOUCH ANY OF THE ANDROID PARTITIONS, IT WILL DESTROY THE ANDROID SYSTEM!
Everything should go smoothly from here and you can remove your OTG cable and USB drive once Windows starts asking for your User Name.
4) Final Steps
One last step. Thanks to Android, we have to hide the Android partitions from Windows, because when we open "This PC", Windows will attempt to mount all the partitions and cause the whole thing to hang.
So, go to control panel, administrative tools, computer management, then Storage, then for each of the RAW partitions that belong to Android, right click and choose "change drive letters" and choose "remove", then OK. Repeat for the rest of the partitions, leaving the C: drive alone. DO NOT DELETE ANY PARTITIONS OR ANDROID WILL NOT WORK!
Note: For people who only want to install Windows and don't want Android but still want the dual boot BIOS (due to the 60Hz refresh rate), I have tried it and it works. What you need to do is to follow this tutorial exactly, but REPLACE STEP 2 WITH THE ONE BELOW:
STEP 2) This step will wipe out your whole tablet (INCLUDING ALL PREVIOUS WINDOWS AND ANDROID PARTITIONS AND DATA)
Yes, even though we are not installing Android, we need this step still:
ON ANOTHER PC (not tablet), download the Android 4.4.4 Lite ROM here: https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
OR
USE ANY OTHER DOWNLOADED ROM AS YOU WISH
Download this modified "partition.tbl" file from the Chinese: http://pan.baidu.com/s/1qWnxc4G
Download and install Notepad++, we need to edit "partition.tbl" file below, the Notepad.exe and Wordpad.exe built in on Windows DOES NOT SAVE THE FILE CORRECTLY AND WILL NOT WORK!
Extract the contents of the ROM to a folder. You should see a "partition.tbl" file inside.
This file controls how the 32GB eMMC in the tablet will be partitioned in this step.
Copy the "partition.tbl" file FROM the Chinese download from the 5000M folder TO the Android ROM folder that you extracted. Replace the original "partition.tbl" file that came with the ROM. Edit the "partition.tbl" file in the Android ROM folder, find the second last line, which is "add -b 5931048 -s 10240000 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0"
and change the highlighted number to 2048. Save the file!
Open "flash.xml" with Notepad++.
DELETE this chunk:
<code_group name="system">
<file TYPE="system">
<name>system.img</name>
<version>eng.yankendi</version>
</file>
</code_group>
AND THIS CHUNK BELOW:
<command>
<string>fastboot flash system $system_file</string>
<timeout>420000</timeout>
<retry>2</retry>
<description>Flashing 'system' image.</description>
<mandatory>1</mandatory>
</command>
Then save the file.
Follow the post on the FIRST PAGE HERE, scroll down and start from this part onwards “WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier))” until the end (stop at "GOOGLE PLAY STORE FIX (thanks to Frontier)"). READ BELOW FIRST:
Because we have already done certain steps, we can ignore some parts:
PARTS TO IGNORE:
Under the "Required materials" section
IGNORE: “- The Android DnX BIOS (or Android BIOS) from here “
If you wish, you can use Android 4.4.4 lite ROM in place of the 4.4.2 ROM as proposed here.
Under the "From Windows host -> Android guest (conversion to Android tablet)" section
IGNORE all these: (because we have already flashed BIOS)
- Unzip the Android DnX BIOS directly into the Windows installation on X98 Air 3G.
- Run with administrative rights (from command line) flash.bat file inside the folder BIOS_X98_Air_3G_android. H process starts with the completion of the installation DnX BIOS displays the message "FPT Operation Passed".
After finishing the steps, you can power it up, you can see the dual boot menu option with the Android logo and a very small Windows icon. Continue and follow STEP 3 in the guide. You can partition your 32GB eMMC in the Windows setup to remove all previously created Android partitions and make it into one large Windows partition to install Windows.
For dual boot FAQ click here
INVERTED TOUCH FIX UNDER WINDOWS (thanks to krisbliz)​
You can use the DevManView to restart the "Goodix Touch HID" before the windows logon screen and everything working perfect again.
Here are the steps:
Download the file "disable enable touch driver.rar" attached to this post
So first copy the extracted files in Windows dir
Now run gpedit.msc
Computer configuration
Scripts (startup/shutdown)
Startup
Add
browse for reset driver.bat
Then reboot to test.
SPACE PROBLEMS IN WINDOWS 8.1 AFTER WINDOWS UPDATE (thanks to jcespi2005)​
Follow these istructions to clean WinSxS folder:
http://www.eightforums.com/tutorials/44351-winsxs-folder-component-store-clean-up-windows-8-1-a.html
SLEEP PROBLEM IN WINDOWS 8.1 (thanks to sasort)​
Follow these istructions:
First open cmd as admin and check status with this command:
powercfg /sleepstudy
It should give you this reply:
No connected standby traces available. Report not generated.
Now start regedit an go here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power
Change the value of the key CsEnabled from 1 to 0 and reboot.
(1 means connected standby enabled and 0 disabled.)
After reboot.
Now go to the control panel and select Energy, under Advanced there will be many new settings.
Don´t change anything, just select save settings.
Then with regedit change the CsEnabled key back to 1 and reboot again.
Open cmd as admin and again check status with the command:
powercfg /sleepstudy
It should now work and create a sleepstudy-report.html and the sleep function now works as expected.
MANAGE APP UNDER ANDROID (thanks to jcespi2005)​
You can use link2sd to move app, libs and data, and FolderMount to link and move OBB and SD data to microSD
BATTERY DRAIN FIX UNDER WINDOWS (thanks to vpx)​
The main problem is very old (year 2006) driver of "Intel SD Host Controller", they are 3 in Device manager. Only thing what you need is update driver.
start Computer Management (hold My Computer and select Manage)
select Device management
find SD Controllers, if you click on it, there are 3 "Intel SD Host Controller"s
hold on every one controller, select "Update Driver", select driver from computer, and there is another option "SDA Standard Compliant SD Host Controller", install driver, confirm restart of computer after last update install
reboot
WIFI FIX UNDER WINDOWS (thanks to Hendrickson)​
If you see that ping on windows is very strange,sometimes i have lost packets and ping time is not stable try this fix: techtablets repository
BATTERY CALIBRATION FIX UNDER ANDROID (thanks to Hendrickson)​
Try this, download and run advanced battery calibrator from Play and Battery Life repair:
Blackmart Studios - Battery riparator
Blackmart Studios - Advanced Battery Calibrator
This seems to have fixed the issue.

Maybe you should copy some post about Air 3G from X98 Air thread?

Nice english instructions for rooting, Win->Android, Android->Win, removal of bloatware etc. would be nice. Everyone can use google translate to navigate official chinese forums but you will get funny translations like "Brush Wizard software". If instructions are unclear and they leave space for interpretation mistakes can happen. Worst case scenario is bricked device.

After using windows and Android I still have the same gpu issues. I also looked in the log and at the end of every crashlog (in android) I see a dev_prive->gpu_error, which is a call from the kernel. (I saw some code on the internet about this) So, my intel Atom chip is bad. Going to return it and ask for a replacement.
The error seems to only happen when I use an app that uses opengl 3.0 (and a LOT of games use that!).
Also about the touchscreen, there seems to be a major problem with the driver in linux. Since I guess they cross-compiled the driver, I am guessing they made the same mistake in both android(linux) and windows.
How did I verify this? Well I used a goodix android application which had some demo app and I saw that the moments the touchscreen gets refreshed are not constant. Let me explain.
When I slide my finger over the touchscreen with a constant speed this happens to my tablets:
This is what my "old and smooth" tablet does(every dot is a touchscreen refresh): .---------.---------.---------.---------.---------.---------.---------.---------. (this is a constant refresh)
This is what my X98 Air 3G does: .--------.--.---------.-.-------.------.-------.-.-----.-----.-.-----.------.----.----.---------.-------.----. (not constant at all)
So the times the touchscreen gets refreshed is not constant. The result is that especially scrolling doesn't work that smooth.
And on top of that, the response time is extremely slow. I am guessing that the driver puts the touchscreen into sleep mode after every single touch, which is stupid. The response (as stated in the goodix GT9271 datasheet) is <200ms. Lets say it's about 100ms, do you know how slow that is??? If your mouse would only refresh every 10th of a second, it would be extremely slow!!!
If I didn't have gpu issues and the touchscreen issue would be corrected, this tablet would be superb, but that is not the case of course.
I am going to contact Teclast if they want my help in enhancing the touchscreen driver. (I am an embedded software engineer specialized in C/C++/C# code)
Also, I might be able to make simple C# app that does most of the work when you want to flash your tablet from android to windows. (this could also be done with a very simple windows batch script)

Jote said:
Everyone can use google translate to navigate official chinese forums but you will get funny translations like "Brush Wizard software". If instructions are unclear and they leave space for interpretation mistakes can happen. Worst case scenario is bricked device.
Click to expand...
Click to collapse
Hi Jote, sorry again for my bad english.
The biggest problem is that most of the information and instructions on how to root, how to change OS,etc.. come from the Chinese manufacturer's forum.
As written before your help in any way will be really appreciated! This is true also about the translation from chinese to the english language.
I ordered this tablet because I think it has enormous potential enclosed in a shell of very small dimensions, if we combine our knowledge to bridge the gap of the Chinese language I think we have great satisfaction with it.
I will try to add link to files for rooting, for change the OS and get other resources asap.

My tablet hasn't arrived yet but I tried to prepare everything.
I'm unable to browse the official forum. I've tried on several days but forums are just working extremely slow. When i try to browse directly through Google Translate I get "Proxy server to access restrictions ". I'll try again someday to find proper threads but right now i'm useless.

So the touch screen is going into sleep states very quickly? I noticed compared to the Onda v975w that it was much slower. I have the X98 3G air now and I have gotten use to it. But it would be nicer if it was how you pointed out.
I have disabled Allow the computer to turn off this device to save power, under power management on the Goodix Touch HID in device manager.

Jote said:
My tablet hasn't arrived yet but I tried to prepare everything.
I'm unable to browse the official forum. I've tried on several days but forums are just working extremely slow. When i try to browse directly through Google Translate I get "Proxy server to access restrictions ". I'll try again someday to find proper threads but right now i'm useless.
Click to expand...
Click to collapse
You have to use translator from bing/microsoft to translate threads from teclast forum at www .bing.com/translator/ (sorry, I'm not allowed to post links yet)

Hendrickson said:
So the touch screen is going into sleep states very quickly? I noticed compared to the Onda v975w that it was much slower. I have the X98 3G air now and I have gotten use to it. But it would be nicer if it was how you pointed out.
I have disabled Allow the computer to turn off this device to save power, under power management on the Goodix Touch HID in device manager.
Click to expand...
Click to collapse
Yes, that it what I am claiming right now based on the information I know and what I have experienced at this point.
I attached the zip containing the datasheet of the goodix GT9271 touchscreen controller. (it's the touchscreen controller inside our tablet if I can believe the log)
The zip also contains an android app from goodix. You can select demo in the menu and then test the touchscreen in various ways. Give it a try
Disabling the "Allow the computer to turn off this device to save power" isn't going to work I think. It can only be done in the driver and I am not sure if it's even supported. It's standard USB stuff, but the GT9271 is connected via I2C. This is a Inter-IC Connection to other chips (IC's) of smartphones/tablets like touchscreen controllers, temperature sensors, accelerometers, gyroscopes etc.
I use it a lot in embedded software engineering and I2C is a very common connection in embedded applications. USB is very heavy for small systems, but I2C does require "special code" to get it up and running.
This will give you a better idea of what an I2C connection is capable of(example of RK3288):
http://www.arctablet.com/blog/wp-content/uploads/2014/02/RK3288-2-nowrmk.jpg
Sorry for all the information
Edit: I contacted Teclast and said I'd like to offer them help for free. Let's hope they accept my free help. (if they are smart...)

Someone can check if is it true?
https://twitter.com/srsroot/status/522464839294550017

petruccig said:
Useful Tools
Root : http://www.mgyun.com/vroot
Click to expand...
Click to collapse
This link doesn't work ...

malojk said:
This link doesn't work ...
Click to expand...
Click to collapse
i uploaded the latest chinese version of vROOT for you and the others :good:
vRoot
http://d-h.st/lWu

With the help of a member of another forum, probably very soon we will have a detailed explanation of the steps for change the Operating System in a better english than mine .
Stay tuned.

petruccig said:
With the help of a member of another forum, probably very soon we will have a detailed explanation of the steps for change the Operating System in a better english than mine .
Stay tuned.
Click to expand...
Click to collapse
Which forum if I may ask?

LVL91 said:
Which forum if I may ask?
Click to expand...
Click to collapse
I've set-up an easy to follow guide (in Greek) for Android -> Windows flashing.
The link is here and the translated (in English) link is here.
The procedure of flashing from Windows -> Android is here (English translation is here).
Feel free to copy it and post it here in order to help others.

I have a question about the screen, namely, whether at you vertically (then best seen) is the difference between the left and right sides of the LCD to the distance from the frame (the black space)? In my left is approximately 2 mm and 1 mm from the right. Such a little thing but unobtrusive I hope you understand what I mean.
Next case. Has anyone tried to install on Android Xposed? For me, after the installation of almost every application resets the tablet .
How can I boost speaker volume in this tablet?

Stuck at "Press the Windows key" in recovery mode Windows

After installing the dual boot bios on my teclast air III (M5C5) I tried to install Windows. Unfortunately, just before completion the installation was cancelled because of the following error: "Windows could not update the computer's boot configuration. Installation cannot proceed."
If I start my tablet and choose Windows, I get the following Recovery page:
The boot configuration data file is missing some required information.
File:\BCD
Error code: 0x0c0000034
You'll need to use recovery tools, if you don't have them...
Press the WIndows key for UEFI Firmware Settings
Click to expand...
Click to collapse
Of course I've tried to press the Windows key, but nothing happens. I've tried all keys and several common combinations, but none of them did anything, except spamming Ctrl-Alt-Delete, which forced a shutdown.
I can enter the BIOS, but for some reason there's no option to select Boot from USB stick (only UEFI OS and Windows Boot Manager). The strange thing is that I've used this usb stick to install Windows on the tablet in the first place and I've tried both GPT and MBR and used a usb 2.0 stick in a 2.0 hub, so the usb stick shouldn't be the problem I guess.
But probably even worse is that I cannot get into DNX mode anymore, so I can't install Android either. If I try I get the following message (instead of " Waiting for fastboot commands" ):
BOM Selection Switch (SW1B1) has been changed, but cannot take action. system will reset in 3 seconds
Click to expand...
Click to collapse
For some reason there is not much information about this error message and I could not find solutions to a similar problem ("BOM selection switch SW1B1 has changed Force_Windows"). In a desperate attempt I've tried to enable fastboot in BIOS to see if that would make a difference, but it doesn't.
Any help is welcome, thanks in advance!

Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.

Mikha777 said:
Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.
Click to expand...
Click to collapse
It was a 2.0 drive in a 2.0 hub. But I've tried with a usb 3.0 stick in a 3.0 hub as well and that doesn't work either.
I've had some problems flashing the BIOS. Initially I tried the simple method using the UpdateIFWI app (using the Mirek V7 rom and downloaded the UpdateIFWI app seperately) with the bios "Dualboot Bios Tested C6J6 And C8J7" from here, but that didn't work. Then I used the Mirek's flash tool to update the BIOS and unfortunately selected the latest version, which apparently is not compatible. Luckily DNX mode worked and I could use the tool in this thread to flash the correct BIOS. I used the dualboot bios from techtablets. It finished with FPT operation passed, but did not automatically reboot. After manually rebooting, it launched the screen with the options Android and a small Windows logo. I selected Windows and it started the Windows installer from the USB stick and the rest I've described above. If I start my tablet now, the Android and Windows logo are equally large (so it did install a part of Windows?). Unfortunately I haven't checked if DNX mode worked between flashing Dual boot and installing Windows.
I've ordered an USB programmer already

Teclast X80 Pro (E3E6) Dual OS (Win10/Android 5.0): Remove Windows

Hey guys. Sorry to bother you in the X98 section, but since there's no section for the X80 yet and maybe the devices have some similarities, I hope it's ok.
The tablet worked fine, but to remove any possible bloatware under Windows or Android, I reset Windows. Somehow the device must have crashed (low battery?) and now I can't boot to Windows anymore (black screen and / or boot loop). Of course I made no backup / recovery disk. Android still works fine and I still get into BIOS / UEFI.
I tried reinstalling Windows via OTG with USB stick. I got to the point where I can choose a partition. Problem is, there are lots of partitions (Android, recovery, System and so on). I located the Windows partition, formatted / deleted it and tried to reinstall Windows on this partition. Just the exact way I would do it on a PC. Somehow it won't install on this partition. The error message says something about "the partitions are not in the recommended order. Further information for installation on GPT-volumes..." (I don't know the exact English phrasing because everything is in German). I chose "continue anyway". Then I get the message that "the EFI-system is not formatted in NTFS. Format the partition to FAT32 and start install procedure again". I press ok and get back to Windows Setup (Install now).
I also tried different repair and recovery options. One time I got error code 0xC0000034. Funny thing is, Windows still seems to be there because while trying to repair / recover I tried to load some drivers and could see the hard drives and folders under Windows.
I tried downloading the original roms here: http://pan.baidu.com/s/1qYEa8gc
You need a Baidu account for the larger files and after days and days I gave up to create such an account as it seems to work only with a mainland China number. There's an option for oversea mobiles but that's not working. I tried a QQ-account, but Baidu wants to link with it and you need that telephone number again. So apparently there's no way to get the original files that way.
I found some stuff here: http://www.needrom.com/download/teclast-x80-pro-dualboot/ but that's only a tutorial file in Chinese and some flash programms / drivers (also got them from Baidu - smaller files are possible to download without an account).
Long story short: I guess recovering Windows 10 is too much effort, so I want to make the tablet Android only and of course want to use the whole capacity for Android. I found a thread on reddit about removing Windows on the X98: https://www.reddit.com/r/teclast/comments/479eua/teclast_x89_how_to_remove_windows_10/
But I have no idea which partitions are definitely needed for Android and which ones I can safely delete. I found a partition map here: http://wheresmykeyboard.com/2015/08/teclast-x98-air-64gb-dual-boot-default-partition-map/ but that doesn't help me that much because they look different.
Attached you will find a photo of all the partitions on my device. I guess there are some which were created during the failed Windows installation because I had about 20 GB free space and now only 17.7 GB.
So is there anybody out there who knows if it's possible to remove Windows completely and which partitions I have to delete?

Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.

Deathgazer said:
Did you ever figure this out? I just bought an X80 Pro and was thinking of doing something similar since I plan on making it an android-only tablet.
Click to expand...
Click to collapse
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Please do describe how you achieved Android-only with 32 GB memory
Cheers

metalaxi said:
Hi. Sorry for the late replay. Yes, I figured it out and my X80 Pro is now running Android-only with 32 GB. In the end, it wasn't that hard but a long way to success.
Click to expand...
Click to collapse
Yes please tell us how metalaxi , it'll be much appreciated.:good:

Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!

metalaxi said:
Ok, guys. Since some of you are asking how I did it, I'm going to try to explain it. It's kinda embarrassing that I don't remember the exact way but I hope it helps somehow. I used the tutorial from this site: http://techtablets.com/forum/topic/x80-plus-android-os-only/#login
Even though it's supposed to be for the Plus model, it also worked on the Pro. Btw, the guy Alex in that thread is me .
You can download all the files from my Google Drive here: https://drive.google.com/open?id=0BxEFqy4Rt9w_cnh3VG9ySk5sOHM
You need
- Android5.1 Upgrade Tool.rar
- X80 Pro (E3E6)- Dual OS - Android5.1-V1.04 Firmware.rar
- gpt.rar (Credit goes to Allember @techtablets-forum; hope it's ok to spread the file)
First you have to install the flash tool. Unrar the firmware and replace the gpt.bin. Then flash the firmware by checking BLANK.
Problem is that when I did all that, my Windows was already crushed and wasn't working anymore. I can't remember anymore if I erased the Windows partitions or any others beforehand. If you're not interested in Windows anymore, just flash it without changing or erasing any of the partitions. I guess by replacing the gpt-file, you do all that automatically.
I hope this somehow helps you. Feel free to ask for more help.
Have a good night!
Click to expand...
Click to collapse
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!

Do we have to change the gpt before doing what you said in your PDF? Or I have just to follow your PDF?

Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.

reycharlesconrad said:
Hi @metalaxi. Do you think its possible to like "reverse" and use the same files to remove Android instead and maintain the Windows 10? Appreciate to hear from you. Thanks!
Click to expand...
Click to collapse
Sorry, I can't answer that sufficent enough. As far as I know, you can just delete all partitions except the ones from Windows. Then format the unallocated space and merge it with the one from Windows. No guarantee!

dirkzelf said:
Hi guys, got mine a few months and want to get rid of the Windows part, but the instructions are insufficient for a joker like me.....
1. Download the firmware, its 4 parts of rar being zipped together
2. flash the firmware HOW?!?!?! I have no Idea...... please give us some closer instructions.
Click to expand...
Click to collapse
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32

metalaxi said:
1. Which 4 parts do you mean?
2. To flash any firmware, you need to install all the upgrade tools:
IntelAndroidDrvSetup1.5.0
iSocUSB-Driver-Setup-1.2.0
PhoneFlashTool_5.3.4.0_internal_win32
Click to expand...
Click to collapse
it's too long ago, so I don't know what I exactly did there, but since there was no reply for a long time, I just took a shot and worked out well, now I have an Android only tablet.
I just got lucky I guess....

partition help
Hi, please help.
I have x80pro e3e8
I managed to erase a complete disk partition.
You are trying to revive again, fail.
installed here:
iSocUSB-Driver-Setup-1.2.0
IntelAndroidDrvSetup1.5.0
PhoneFlashTool_5.3.4.0_internal_win32
downloaded here:
Firmware (20161020_SZ)
Tablet joined and tried to flash.
* failed - failed loadet.efi
Please help. I can not download from Baidu
* If I use phoneFlasTool and flash a blank disc - Create Flash partition and dual boot and replace recovery?
What to do with an empty disc?
Thanks for any advice

It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.

theone0987654321 said:
It is not so hard. By mine it was only trial and error. Installiert all drivers an go in the bootloader with three Finger method. Go two levels up and go into bootloader. Then connect to PC and look in Intel flashing tool if connection is reconiced correctly. Select the downloaded file and select flash. Thats it. Device will reboot and you are ready to go.
Click to expand...
Click to collapse
Thank you for the advice. That's right, I did it was marked. I found a reason. rom file was saved on desktop, and had a long name (as I downloaded it) It must copy the file to C've renamed the firmware. Everything went alright. I downloaded and used the GPT files for resizing disk and now goes all right. Thank you for responding to my question.

hi, I have problem while flashing.
Phone flash tool always gives ERROR
Automatic reboot is not supported on this device, please reboot the device manually
ERROR : [Port 0/1/4] Failed to reboot the device
Click to expand...
Click to collapse
Any idea what to do? I followed all the steps, tried many times, still same problem. And it's not possible to reboot device manually, because then it lose connection with PC

Restock OS Without Android
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
affe2000 said:
Hi there.
I have to restock my Device, but the Intel Flash Tool does not recognize my Device.
I cannot boot into Android to turn on USB-Debugging or go into fastboot mode
How do i flash my device without any OS installed?
Click to expand...
Click to collapse
Ok, got it working... dnx fastboot mode is there

....

hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon

mike mike baby said:
hello guys by accident i deleted windows 10, how can i reinstall them? i dont have the windows 10 icon in the dual boot select i only see the android icon
Click to expand...
Click to collapse
Straightforward if you can obtain a USB stick capable of storing over 7GB (some 8GB sticks may not); USB hub (ideally a powered hub); USB keyboard; OTG cable.
1) Obtain the Windows files of the correct firmware. The procedure outlined here is for E6E9 firmware, but other firmware will be similar. Download the circa 6.5GB E6E9 firmware Windows files from https://yadi.sk/d/XEvRsoiD3Q4vKX or https://mega.nz/#F!I0AXGR5C!YiNFkZL9DIvzepH28qAjEQ (or from appropriate source for your firmware version).
Decompress the downloads as required to obtain six folders and two files.
2) Format the stick to FAT32.
3) Name the stick WINPE (five uppercase characters).
4) Copy the previously mentioned folders and files to the USB stick.
5) Plug USB stick and USB keyboard into hub; plug hub into OTG cable; plug OTG cable into tablet whilst the tablet is off.
6) Turn on tablet and immediately start tapping << Delete >> key on USB keyboard. This should open the UEFI config section prior to Android boot option. If the tablet displays the Android boot option, turn off the tablet, wait a few seconds, then turn on and start tapping << Delete >> key on USB keyboard again.
7) When in UEFI, touch the title menu option of << Save and Exit >> and look in the << Boot Override >> section for the name of your USB stick, then touch the name of your USB stick. The screen will immediately go blank as the tablet starts to boot from the USB stick.
8) After a few minutes, a numerically display of progress will be displayed in a CMD window.
9) After reaching 100% and nearing completion of the overall installation, the tablet will prompt for acceptance, so accept that prompt.
10) The setup will run a few final operations for a few seconds, then automatically reboot.
11) Done.
You will be prompted to complete the OOBE on each Windows boot until you complete OOBE.