FORUMS
Remove All Ads from XDA

Teclast X98 Air III & Air 3G debloated GoogleNow custom roms

227 posts
Thanks Meter: 151
 
By sikke1, Senior Member on 8th December 2015, 10:02 PM
Post Reply Email Thread
9th December 2015, 09:27 PM |#11  
Senior Member
Thanks Meter: 47
 
More
I just tried a different USB cable - shorter, heavier gauge... Same error: 12/09/15 16:18:51.532 DEBUG : Port 0/0/9 #0: XFSTK SN: Baytrail000003BA Attemp 58 times to scan devices ...

---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------

Quote:
Originally Posted by sikke1

Pickup the flash file before you plug in the tablet. Only plug in tablet after you have setup Flashtool waiting, it's manufacturing tool made to flash 100 tablets / hour. When tablet is in dnx mode its showing to windows PID 0A65 when flash tool commances tablet to go droidboot mode it will change to device id PID 0FFF. flash tool waits for these devices to appear, if Intel drivers are present it will work.


Ok, this is where my noob really shows. I tried the MFT in every order - flash file picked first, then connected while in Dnx mode, and vice versa. Same results. Where, other than settings, do I see PID change? I installed all the drivers that were in your MFT link. I did get a bunch of red warnings that the drivers were not validated - to which I clicked install anyway - at least 8-10 times.

---------- Post added at 09:27 PM ---------- Previous post was at 09:24 PM ----------

Ah, never mind on the PID - see that now in device manager. It's staying 0A65. It's showing under Samsung Android Device. There is also an Intel Soc USB Driver, but the only one that drops out when I disconnect the cable (while device is in DnX mode) is the Samsung one.
 
 
9th December 2015, 09:31 PM |#12  
OP Senior Member
Thanks Meter: 151
 
More
Proper flash process looks like this. When intel drivers are ok. Tablets steps 2 diffrent hardware modes.

9th December 2015, 09:39 PM |#13  
Senior Member
Thanks Meter: 47
 
More
Quote:
Originally Posted by sikke1

Proper flash process looks like this. When drivers are ok. Tablets steps 2 diffrent hardware modes, thats why 2 drivers.


I noticed your baytrail SN is 00000333, where mine is 000003BA.

Ok, here's my log:

Code:
12/09/15 16:32:25.713  INFO   : FlashStats saves the logs into C:/Users/EC-i7/mfgft-stats.csv
12/09/15 16:32:44.829  INFO   : Loading Flash file (D:/X98 Air III (M5C5) GoogleNow/X98 Air III (M5C5) GoogleNow/flash.xml)
12/09/15 16:32:44.830  INFO   : GP_Flag is set to 0x80000045
12/09/15 16:32:44.830  DEBUG  : Fastboot sequence in flash file is used.
12/09/15 16:32:44.831  DEBUG  : Flash image type: system
12/09/15 16:32:44.831  DEBUG  : droidboot : D:/X98 Air III (M5C5) GoogleNow/X98 Air III (M5C5) GoogleNow/droidboot.img
12/09/15 16:32:44.831  DEBUG  : esp : D:/X98 Air III (M5C5) GoogleNow/X98 Air III (M5C5) GoogleNow/esp.img
12/09/15 16:32:44.831  DEBUG  : osloader : D:/X98 Air III (M5C5) GoogleNow/X98 Air III (M5C5) GoogleNow/efilinux-userdebug.efi
12/09/15 16:32:44.831  DEBUG  : stage2_BAYTRAIL_EDK2_BYT_CRV2_IA32 : 
12/09/15 16:32:44.831  DEBUG  : stage2_BAYTRAIL_EDK2_BYT_CRV2_X64 : 
12/09/15 16:32:44.831  DEBUG  : FASTBOOT : 
12/09/15 16:32:44.831  DEBUG  : SOFTFUSE : 
12/09/15 16:32:44.831  DEBUG  : FW_DNX : 
12/09/15 16:32:44.831  DEBUG  : IFWI : 
12/09/15 16:32:44.831  DEBUG  : OS_DNX : 
12/09/15 16:32:44.831  DEBUG  : XXR_DNX : 
12/09/15 16:32:44.831  DEBUG  : KBOOT : 
12/09/15 16:32:44.831  DEBUG  : KERNEL : 
12/09/15 16:32:44.831  DEBUG  : RECOVERY : 
12/09/15 16:32:44.831  DEBUG  : SYSTEM : 
12/09/15 16:32:44.831  DEBUG  : MODEM : 
12/09/15 16:32:44.831  DEBUG  : OTA : 
12/09/15 16:32:44.831  DEBUG  : cmd[0] {timeout=120000, retry=2} : fastboot oem start_partitioning
12/09/15 16:32:44.831  DEBUG  : cmd[1] {timeout=120000, retry=2} : fastboot flash /tmp/partition.tbl "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\partition.tbl"
12/09/15 16:32:44.831  DEBUG  : cmd[2] {timeout=120000, retry=2} : fastboot oem partition /tmp/partition.tbl
12/09/15 16:32:44.831  DEBUG  : cmd[3] {timeout=120000, retry=2} : fastboot format factory
12/09/15 16:32:44.831  DEBUG  : cmd[4] {timeout=120000, retry=2} : fastboot format system
12/09/15 16:32:44.831  DEBUG  : cmd[5] {timeout=120000, retry=2} : fastboot format cache
12/09/15 16:32:44.831  DEBUG  : cmd[6] {timeout=120000, retry=2} : fastboot format config
12/09/15 16:32:44.831  DEBUG  : cmd[7] {timeout=120000, retry=2} : fastboot format logs
12/09/15 16:32:44.831  DEBUG  : cmd[8] {timeout=120000, retry=2} : fastboot format data
12/09/15 16:32:44.831  DEBUG  : cmd[9] {timeout=120000, retry=2} : fastboot oem stop_partitioning
12/09/15 16:32:44.831  DEBUG  : cmd[10] {timeout=120000, retry=2} : fastboot oem wipe ESP
12/09/15 16:32:44.831  DEBUG  : cmd[11] {timeout=120000, retry=2} : fastboot oem wipe reserved
12/09/15 16:32:44.831  DEBUG  : cmd[12] {timeout=120000, retry=2} : fastboot flash ESP "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\esp.img"
12/09/15 16:32:44.831  DEBUG  : cmd[13] {timeout=120000, retry=2} : fastboot flash fastboot "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\droidboot.img"
12/09/15 16:32:44.831  DEBUG  : cmd[14] {timeout=120000, retry=2} : fastboot flash boot "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\boot.img"
12/09/15 16:32:44.831  DEBUG  : cmd[15] {timeout=120000, retry=2} : fastboot flash recovery "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\recovery.img"
12/09/15 16:32:44.831  DEBUG  : cmd[16] {timeout=180000, retry=2} : fastboot flash system "D:\X98 Air III (M5C5) GoogleNow\X98 Air III (M5C5) GoogleNow\system.img"
12/09/15 16:32:44.831  DEBUG  : cmd[17] {timeout=120000, retry=2} : fastboot continue
12/09/15 16:32:44.831  DEBUG  : Using GPFlag from flash file : 0x80000045
12/09/15 16:32:44.831  INFO   : Ready to flash!
12/09/15 16:33:02.630  DEBUG  : New SOC device connected, removing the existing device connected on the same port
12/09/15 16:33:02.630  DEBUG  : Port 0/0/9   #0: FlashManager::do_new_soc_device on port 9
12/09/15 16:33:02.630  INFO   : do_new_medfield_device STARTING TO FLASH
12/09/15 16:33:02.630  DEBUG  : Port 0/0/9   #0: Start XFSTK thread for device Baytrail000003BA with status 0
12/09/15 16:33:02.630  DEBUG  : Port 0/0/9   #0: New device detected - SN : Baytrail000003BA
12/09/15 16:33:02.630  DEBUG  : New SOC device -> serial: Baytrail000003BA port: 9 
12/09/15 16:33:02.630  DEBUG  : Flash ifwi with GPFlag 0x80000045
12/09/15 16:33:02.630  DEBUG  : IFWI flash started for device Baytrail000003BA (Wed Dec 9 16:33:02 2015)
12/09/15 16:33:02.630  INFO   : Port 0/0/9   #0: IFW flash started - SN : Baytrail000003BA
12/09/15 16:33:02.631  INFO   : Disabling xFSTK wipe out ifwi option
12/09/15 16:33:02.631  INFO   : Disabling xFSTK Misc DnX
12/09/15 16:33:02.631  DEBUG  :  XFSTK Downloader API 0.0.0 
Copyright (c) 2014 Intel Corporation
12/09/15 16:33:02.631  DEBUG  :  fwdnx --
12/09/15 16:33:02.631  DEBUG  :  fwimage --
12/09/15 16:33:02.631  DEBUG  :  osdnx --
12/09/15 16:33:02.631  DEBUG  :  osimage --
12/09/15 16:33:02.631  DEBUG  :  gpflags -- 0x80000045
12/09/15 16:33:02.631  DEBUG  :  usbsn -- Baytrail000003BA
12/09/15 16:33:02.631  DEBUG  :  softfuse --
12/09/15 16:33:02.631  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Initiating download...
12/09/15 16:33:02.641  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 1 times to scan devices ...
12/09/15 16:33:02.841  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 2 times to scan devices ...
12/09/15 16:33:03.041  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 3 times to scan devices ...
12/09/15 16:33:03.241  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 4 times to scan devices ...
12/09/15 16:33:03.441  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 5 times to scan devices ...
12/09/15 16:33:03.641  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 6 times to scan devices ...
12/09/15 16:33:03.841  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 7 times to scan devices ...
12/09/15 16:33:04.041  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 8 times to scan devices ...
12/09/15 16:33:04.241  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 9 times to scan devices ...
12/09/15 16:33:04.441  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 10 times to scan devices ...
12/09/15 16:33:04.641  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 11 times to scan devices ...
12/09/15 16:33:04.841  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 12 times to scan devices ...
12/09/15 16:33:05.041  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 13 times to scan devices ...
12/09/15 16:33:05.241  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 14 times to scan devices ...
12/09/15 16:33:05.441  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 15 times to scan devices ...
12/09/15 16:33:05.641  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 16 times to scan devices ...
12/09/15 16:33:05.841  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 17 times to scan devices ...
12/09/15 16:33:06.041  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 18 times to scan devices ...
12/09/15 16:33:06.241  DEBUG  : Port 0/0/9   #0: XFSTK SN: Baytrail000003BA Attemp 19 times to scan devices ...
9th December 2015, 09:42 PM |#14  
OP Senior Member
Thanks Meter: 151
 
More
if tablet stays in DNX mode it wont find correct driver.
The samsung adb driver is ok... maybe, if you also see the PID 0A65 there. It works, any adb driver works. But you need the dnx driver from Intel to proceed after that.

Intel SoC USB driver needs to be present too, it wont drop out. Just the ADB driver will change PID from 0A65 to 0FFF when droidboot starts fastboot flash mode.

Reinstall drivers anyway.
10th December 2015, 01:29 AM |#15  
Senior Member
Thanks Meter: 47
 
More
Quote:
Originally Posted by sikke1

if tablet stays in DNX mode it wont find correct driver.
The samsung adb driver is ok... maybe, if you also see the PID 0A65 there. It works, any adb driver works. But you need the dnx driver from Intel to proceed after that.

Intel SoC USB driver needs to be present too, it wont drop out. Just the ADB driver will change PID from 0A65 to 0FFF when droidboot starts fastboot flash mode.

Reinstall drivers anyway.

Sorry for delayed reply...

Yup, the screen on the tablet never changes out of DnX mode - well, at least not until it times out and powers off. The PC also never ding-dongs like it's changing USB devices.

I'll try uninstalling and reinstalling the driver packages. Is it normal to get countless windows warnings about drivers not being verified?

Updated: After uninstalling and reinstalling, I once again got the same 'can't verify driver' prompt. I clicked "install anyway". The log for the installer shows:

Code:
x64 os
x64 os
Windows version: 7
CertMgr.exe MFLD_USB_driver_cert.cer returned 0
Installing drivers, please wait
drvinstall.exe intc_usbcomp.inf returned 0
drvinstall.exe intc_cdcserial.inf returned 0
drvinstall.exe intc_rndis.inf returned 0
drvinstall.exe intc_mtp.inf returned 0
drvinstall.exe intc_adb.inf returned 0
drvinstall.exe intc_dvctrace.inf returned 0
And at the conclusion, the installer says it installed successfully. I did this for both the IntelAndroidDrvSetup and iSoCUSBDriver files. Both run as administrator.

Final result: same as before. bummer. Getting really tired of all the Chinese crap that keeps popping up.
10th December 2015, 07:40 AM |#16  
OP Senior Member
Thanks Meter: 151
 
More
MFT cant find correct unit if its stuck in dnx mode.

You can also use adb fastboot to push the system.img in place. Least you have working adb

Fastboot should be in intel adb folder.

*****

Haha.
Cant blame Chinese for Microsoft Windows + Intel software and drivers those are not made in Shenzen.
11th December 2015, 02:46 AM |#17  
Senior Member
Thanks Meter: 47
 
More
Quote:
Originally Posted by sikke1

MFT cant find correct unit if its stuck in dnx mode.

You can also use adb fastboot to push the system.img in place. Least you have working adb

Fastboot should be in intel adb folder.

*****

Haha.
Cant blame Chinese for Microsoft Windows + Intel software and drivers those are not made in Shenzen.

I appreciate all your help @sikke1... I just tried using fastboot flash system system.img. It failed after 112 seconds, saying no device found... Looks like my M5C5 is stuck w/stock junk.
11th December 2015, 02:55 AM |#18  
Senior Member
Thanks Meter: 47
 
More
Quote:
Originally Posted by erkme73

I appreciate all your help @sikke1... I just tried using fastboot flash system system.img. It failed after 112 seconds, saying no device found... Looks like my M5C5 is stuck w/stock junk.

Sorry - this is the error I get:

Device is in DnX mode, waiting for fastboot command, and device manager shows PID 0A65 is connected.
Attached Thumbnails
Click image for larger version

Name:	2015-12-10_21-53-47.jpg
Views:	440
Size:	29.8 KB
ID:	3572290  
11th December 2015, 03:11 AM |#19  
OP Senior Member
Thanks Meter: 151
 
More
Quote:
Originally Posted by erkme73

Sorry - this is the error I get:

Device is in DnX mode, waiting for fastboot command, and device manager shows PID 0A65 is connected.

*edit*
11th December 2015, 03:13 AM |#20  
Senior Member
Thanks Meter: 47
 
More
Quote:
Originally Posted by sikke1

DnX is wrong mode.
Start tablet in Android and enable USB debugging. Settings --> developer options --> USB debugging.
(if your ADB driver is OK tablet reboots)

system.img must be in same folder with fastboot and adb

Then do this:

Got it! Thanks for the push in the right direction. Got into adb mode from the OS. It's flashing now!
11th December 2015, 03:17 AM |#21  
OP Senior Member
Thanks Meter: 151
 
More
Quote:
Originally Posted by erkme73

Got it! Thanks for the push in the right direction. Got into adb mode from the OS. It's flashing now!

*edit*
The Following User Says Thank You to sikke1 For This Useful Post: [ View ] Gift sikke1 Ad-Free
Post Reply Subscribe to Thread

Tags
air 3g, air iii, teclast x98

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes