These are debloated factory stock roms with added GoogleNow launcher and Gapps. Clean as possible - non official.
Only for baytrail models
Teclast X98 Air 3G (C5J8) - flash with flash_nopartition.xml to keep Windows 10
https://mega.nz/#!y0wUyBKK!Qmu5mVHeIsd8RkAYce8cYw6iNJ5aXJCs7Qhh0NhOnBo
Teclast X98 Air III (M5C5) - 100 MB Android cache partition to release space. Stock partition is 1 GB
https://mega.nz/#!epBH1SLC!9bqJBevbnuuCIdYgnaYRa1fFCB3H_S1d13_XHe_Bdgg
Flash with Intel MFT 6.0.51
copy CUSTOM_CONFIG.ini to "C:\Program Files (x86)\Intel\Manufacturing Flash Tool"
https://mega.nz/#!rw4FwaQQ!tB7Bw307ktuOpaIaxkuC0W1Fcq7w3dSr-kFxoYuK6hY
Install and Configure the Intel Manufacturing Fash Tool on a Windows Host PC - This guide contains older MFT 6.0.43 use the installer from above link.
http://forum.xda-developers.com/showpost.php?p=62823535&postcount=55
Flash a custom Android image (ROM) to your X98 Air device
http://forum.xda-developers.com/showpost.php?p=62823546&postcount=6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Script to install root + xposed
1. enable USB debugging
2. Windows must have ADB driver
3. Copy xposed + root into tablet memory.
4. Run the script
--> choose 5. cwm and option T4
--> install zips from recovery
5. install XposedInstaller_3.0_alpha4.apk in Android
https://mega.nz/#!H0pSWCxD!I3FxmZHiI2Jg559mdBIaAkKG3JQC3zkkPb8vwi9SIjg
Result rooted + debloated Nexus like tablet.
**
Can install in a M5C6? It's the W10+Android5.0 64GB
W10 is affected?
corolev said:
Can install in a M5C6? It's the W10+Android5.0 64GB
W10 is affected?
Click to expand...
Click to collapse
The partition file will wipe your tablet. Its made for 32gb.
But you can install android only system with fastboot, all the rest of files are stock. With windows adb fastboot. Flash the 1,3gb android system file. It will fit in stock partition. You need to also factory reset and wipe data. Dont install kernel, only system.img its clean lean stock Intel + Google stuff.
"Fastboot flash system system.img"
Or
Download factory stock flash files and replace system.img + use nopartition.xml
You can use mireks flashing bat. Mireks roms are for z3736f and they work with z3735f but will overclock z3735f.
http://blog.syedgakbar.com/2013/02/android-installing-system-images-using-flashboot/
Complete noob, but what's the installation process for Air III? Is there already a how-to?
Ok, after playing with this a bit, I'm getting the following error in the MFT program:
12/09/15 15:51:12.055 DEBUG : Port 0/0/9 #0: XFSTK SN: Baytrail000003BA Attemp 119 times to scan devices
It repeats this until about 300 attempts, then ultimately fails. Any suggestions?
erkme73 said:
Complete noob, but what's the installation process for Air III? Is there already a how-to?
Ok, after playing with this a bit, I'm getting the following error in the MFT program:
12/09/15 15:51:12.055 DEBUG : Port 0/0/9 #0: XFSTK SN: Baytrail000003BA Attemp 119 times to scan devices
It repeats this until about 300 attempts, then ultimately fails. Any suggestions?
Click to expand...
Click to collapse
You need to correct the Flashing tool settings as in the photo provided 0FFF
http://forum.xda-developers.com/x98-air/general/tecknights-teclast-tutorials-t3201191
Install and Configure the Intel Manufacturing Flash Tool on a Windows Host PC
http://forum.xda-developers.com/showpost.php?p=62823535&postcount=5
sikke1 said:
You need to correct the Flashing tool settings as in the photo provided 0FFF
http://forum.xda-developers.com/x98-air/general/tecknights-teclast-tutorials-t3201191
Install and Configure the Intel Manufacturing Flash Tool on a Windows Host PC
http://forum.xda-developers.com/showpost.php?p=62823535&postcount=5
Click to expand...
Click to collapse
Thanks, I should have been more specific. I did get to the point where it appeared to start flashing... it showed 5%, but in the MFT log, it was repeating the "12/09/15 15:51:12.055 DEBUG : Port 0/0/9 #0: XFSTK SN: Baytrail000003BA Attemp 119 times to scan devices" error.
After reboot of both PC and tablet, now I can't get anything to show up under devices. At least before I had device 0/0/9 showing. I hate windows.
erkme73 said:
Thanks, I should have been more specific. I did get to the point where it appeared to start flashing... it showed 5%, but in the MFT log, it was repeating the "12/09/15 15:51:12.055 DEBUG : Port 0/0/9 #0: XFSTK SN: Baytrail000003BA Attemp 119 times to scan devices" error.
After reboot of both PC and tablet, now I can't get anything to show up under devices. At least before I had device 0/0/9 showing. I hate windows.
Click to expand...
Click to collapse
You cannot boot tablet to OS to start flash from there. Tablet must be put flash mode from buttons.
Flash a custom Android image (ROM) to your X98 Air device
http://forum.xda-developers.com/showpost.php?p=62823546&postcount=6
6. Power up your X98 Air device by holding down the power button, volume+ and volume- until your device enters DnX mode. Do not release any of the buttons until you see the message:
Entering DnX mode
Waiting for Fastboot command
sikke1 said:
Tablet goes to flash mode with all button pressed together. Tablet must be shut down completely before this procedure.
Click to expand...
Click to collapse
Correct. It's in DnX mode, and as soon as I plug in the USB, the MFT shows a device 0/0/9. It shows 0% until I choose "open" and select the "flash" file in the extracted directory from your zip. Then, the 0% goes to 5%, showing a blue prgress bar with "Flashing IFWI" - while in the log below it ramps up the errors. Eventually the tablet times out and powers off. I've configured the settings of the MFT according to your screenshot.
Is there anything in the error that would help indicate what the problem is?
erkme73 said:
Correct. It's in DnX mode, and as soon as I plug in the USB, the MFT shows a device 0/0/9. It shows 0% until I choose "open" and select the "flash" file in the extracted directory from your zip. Then, the 0% goes to 5%, showing a blue prgress bar with "Flashing IFWI" - while in the log below it ramps up the errors. Eventually the tablet times out and powers off. I've configured the settings of the MFT according to your screenshot.
Is there anything in the error that would help indicate what the problem is?
Click to expand...
Click to collapse
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.
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 ----------
sikke1 said:
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.
Click to expand...
Click to collapse
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.
Proper flash process looks like this. When intel drivers are ok. Tablets steps 2 diffrent hardware modes.
sikke1 said:
Proper flash process looks like this. When drivers are ok. Tablets steps 2 diffrent hardware modes, thats why 2 drivers.
Click to expand...
Click to collapse
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 ...
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.
sikke1 said:
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.
Click to expand...
Click to collapse
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.
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.
sikke1 said:
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.
Click to expand...
Click to collapse
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.
erkme73 said:
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.
Click to expand...
Click to collapse
Sorry - this is the error I get:
Device is in DnX mode, waiting for fastboot command, and device manager shows PID 0A65 is connected.
erkme73 said:
Sorry - this is the error I get:
Device is in DnX mode, waiting for fastboot command, and device manager shows PID 0A65 is connected.
Click to expand...
Click to collapse
*edit*
sikke1 said:
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:
Click to expand...
Click to collapse
Got it! Thanks for the push in the right direction. Got into adb mode from the OS. It's flashing now!
Related
Hello, I have a tablet sitting in front of me that I need to repair. The tablet will only boot to a screen that shows a usb logo and a white bar, which eventually changes to red. It appears that the device doesn't have a working bootloader and will only go into what seems like a download mode. Connecting the device to the computer shows "CLOVERVIEW" in device manager. Attempting button combinations doesn't provide any results. I do not know how to proceed from here. Any ideas?
This video seems like what I'd need to fix it, although I don't exactly know how to apply this to my device.
https://www.youtube.com/watch?v=jh89aiepcjQ
1 day later: I figured out how to use the Intel Phone flash tool, and this device is fairly easy to recover from a hardbrick. I was able to successfully get droidboot installed again. I wanted to repeat the process again, so I wiped the bootloader partition and tried to do it again. However, I can't seem to flash anything due to the dreaded "Windriver Error: 0x20000015, Timeout expired". Definitely seems to be a driver issue, but it doesn't work on the computer it originally worked on, nor does it work on 3 other computers I've tried (all Win 8.1).
EDIT: Fixed it and did a write-up: http://forum.xda-developers.com/memo-pad-7/general/howto-unbrick-hardbricked-memo-pad-t3105945
However, I managed to get myself stuck at the ASUS splashscreen. Does anyone know of a way to get past the screen or force download mode?
korockinout13 said:
1 day later: I figured out how to use the Intel Phone flash tool, and this device is fairly easy to recover from a hardbrick. I was able to successfully get droidboot installed again. I wanted to repeat the process again, so I wiped the bootloader partition and tried to do it again. However, I can't seem to flash anything due to the dreaded "Windriver Error: 0x20000015, Timeout expired". Definitely seems to be a driver issue, but it doesn't work on the computer it originally worked on, nor does it work on 3 other computers I've tried (all Win 8.1).
EDIT: Fixed it and did a write-up: http://forum.xda-developers.com/memo-pad-7/general/howto-unbrick-hardbricked-memo-pad-t3105945
However, I managed to get myself stuck at the ASUS splashscreen. Does anyone know of a way to get past the screen or force download mode?
Click to expand...
Click to collapse
If you have DROIDBOOT working, you can use a temp CWM session and flash the initial 182 ROM.
Nope, I don't have a working boot loader.
Hi, i destroy my ASUS Fonepad 7 fe170cg with this commands in droidboot:
fastboot flash boot boot.img
fastboot flash fastboot boot.img
fastboot flash splashscreen boot.img
splashscreen.img has 1.37mb but boot.img has 9mb. i flash 9mb and this could be overflow and destroy partition table?
At this time, i have intel inside logo at startup to infinity. If i connect usb to tablet and PC, detects cloverview device for 1 second and disconnect and intel inside show.
i try Manufacture Flashing Tool, change device scan period and this not work ( i mean this program didnt finish this process because it dont have time. Please tell me how to repair it. I have Windriver error device gone (
SORRY for my english
This is logs:
06/05/15 12:53:53.151 INFO : Manufacturing Flash Tool V 6.0.2 (build on Fri Feb 15 12:04:32 MST 2013)
06/05/15 12:53:53.166 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
06/05/15 12:53:53.198 INFO : LogLevel is set to DEBUG
06/05/15 12:53:53.198 DEBUG : FlashStats saves the logs into C:/Users/Grzechu/mfgft-stats.csv
06/05/15 12:53:53.198 INFO : Using Qt version: 4.8.1
06/05/15 12:53:53.198 INFO : Using XFSTK version: 1.3.6
06/05/15 12:53:53.213 WARNING: Please select a flash file...
06/05/15 12:54:00.125 INFO : FlashStats saves the logs into C:/Users/Grzechu/mfgft-stats.csv
06/05/15 12:54:00.252 INFO : FlashStats saves the logs into C:/Users/Grzechu/mfgft-stats.csv
06/05/15 12:54:00.673 DEBUG : Device manager period is set to 1000 ms
06/05/15 12:54:00.673 INFO : FlashStats saves the logs into C:/Users/Grzechu/mfgft-stats.csv
06/05/15 12:54:04.260 INFO : Loading Flash file (C:/Users/Grzechu/Desktop/rom/lol.xml)
06/05/15 12:54:04.260 WARNING: Fail to parse fastboot sequence xml file, now fastboot sequence is restored to default!
06/05/15 12:54:04.260 DEBUG : Flash image type: system
06/05/15 12:54:04.260 DEBUG : SOFTFUSE :
06/05/15 12:54:04.260 DEBUG : FW_DNX : C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_FWR_DnX_20.3E.bin
06/05/15 12:54:04.260 DEBUG : IFWI : C:/Users/Grzechu/Desktop/rom/IFWI_v64.25_CSAX_PROD.bin
06/05/15 12:54:04.260 DEBUG : OS_DNX : C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_OS_DnX_20.3E.bin
06/05/15 12:54:04.260 DEBUG : XXR_DNX :
06/05/15 12:54:04.260 DEBUG : KBOOT : C:/Users/Grzechu/Desktop/rom/fastboot.img
06/05/15 12:54:04.260 DEBUG : KERNEL :
06/05/15 12:54:04.260 DEBUG : RECOVERY :
06/05/15 12:54:04.260 DEBUG : SYSTEM :
06/05/15 12:54:04.260 DEBUG : MODEM :
06/05/15 12:54:04.260 DEBUG : OTA :
06/05/15 12:54:04.260 DEBUG : cmd[0] {timeout=10000, retry=2} : fastboot oem system /sbin/PartitionDisk.sh /dev/mmcblk0
06/05/15 12:54:04.260 DEBUG : cmd[1] {timeout=30000, retry=2} : fastboot flash /tmp/modem.fls $modem_file
06/05/15 12:54:04.260 DEBUG : cmd[2] {timeout=120000, retry=2} : fastboot oem system loadfw_modem.sh /tmp/modem.fls
06/05/15 12:54:04.260 DEBUG : cmd[3] {timeout=45000, retry=2} : fastboot erase factory
06/05/15 12:54:04.260 DEBUG : cmd[4] {timeout=45000, retry=2} : fastboot erase system
06/05/15 12:54:04.260 DEBUG : cmd[5] {timeout=45000, retry=2} : fastboot erase data
06/05/15 12:54:04.260 DEBUG : cmd[6] {timeout=45000, retry=2} : fastboot erase sdcard
06/05/15 12:54:04.260 DEBUG : cmd[7] {timeout=45000, retry=2} : fastboot erase cache
06/05/15 12:54:04.260 DEBUG : cmd[8] {timeout=45000, retry=2} : fastboot flash boot $kernel_file
06/05/15 12:54:04.260 DEBUG : cmd[9] {timeout=200000, retry=2} : fastboot flash system $system_file
06/05/15 12:54:04.260 DEBUG : cmd[10] {timeout=200000, retry=2} : fastboot flash data $userdata_file
06/05/15 12:54:04.260 DEBUG : Using GPFlag from flash file : 0x80000045
06/05/15 12:54:04.260 INFO : Ready to flash!
06/05/15 12:54:09.280 DEBUG : Port 0/0/3 #0: FlashManager::do_new_soc_device on port 3
06/05/15 12:54:09.280 DEBUG : Port 0/0/3 #0: Start XFSTK thread for device B8A5A46B0AADF79D with status 0
06/05/15 12:54:09.280 DEBUG : Port 0/0/3 #0: New device detected - SN : B8A5A46B0AADF79D
06/05/15 12:54:09.280 DEBUG : New SOC device -> serial: B8A5A46B0AADF79D port: 3
06/05/15 12:54:09.280 DEBUG : Flash ifwi with GPFlag 0x80000045
06/05/15 12:54:09.280 DEBUG : IFWI flash started for device B8A5A46B0AADF79D (Pt 5. cze 12:54:09 2015)
06/05/15 12:54:09.280 INFO : Port 0/0/3 #0: IFW flash started - SN : B8A5A46B0AADF79D
06/05/15 12:54:09.280 INFO : Disabling xFSTK wipe out ifwi option
06/05/15 12:54:09.280 INFO : Disabling xFSTK Misc DnX
06/05/15 12:54:09.280 DEBUG : XFSTK Downloader API 1.3.6
Copyright (c) 2012 Intel Corporation
06/05/15 12:54:09.280 DEBUG : fwdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_FWR_DnX_20.3E.bin
06/05/15 12:54:09.280 DEBUG : fwimage -- C:/Users/Grzechu/Desktop/rom/IFWI_v64.25_CSAX_PROD.bin
06/05/15 12:54:09.280 DEBUG : osdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_OS_DnX_20.3E.bin
06/05/15 12:54:09.280 DEBUG : osimage -- C:/Users/Grzechu/Desktop/rom/fastboot.img
06/05/15 12:54:09.280 DEBUG : gpflags -- 0x80000045
06/05/15 12:54:09.280 DEBUG : usbsn -- B8A5A46B0AADF79D
06/05/15 12:54:09.280 DEBUG : softfuse --
06/05/15 12:54:09.280 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Initiating download...
06/05/15 12:54:09.300 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Attemp 1 times to scan devices ...
06/05/15 12:54:09.500 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Attemp 1 times to start download ...
06/05/15 12:54:09.706 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Starting downloading thread...
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader::SetDevice
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader::UpdateTarget
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--FWDnxPath -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_FWR_DnX_20.3E.bin
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--FWImagePath -- C:/Users/Grzechu/Desktop/rom/IFWI_v64.25_CSAX_PROD.bin
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--SoftfusesPath --
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--OSDnxPath -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_OS_DnX_20.3E.bin
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--OSImagePath -- C:/Users/Grzechu/Desktop/rom/fastboot.img
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--MiscDnxPath --
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--Gpflags -- 80000045
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--DebugLevel -- ffffffff
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--UsbDelay ms -- 1
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--TransferType -- USB
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--WipeIFWI -- False
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--Idrq -- False
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--Verbose -- True
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusDownloader::Init
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusWdUsb20Device:pen
06/05/15 12:54:09.706 DEBUG : XFSTK-LOG--USBSN:--CloverviewPlusUtils::SetUsbsn
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D USB Device found - USBSN: B8A5A46B0AADF79D Address:3
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusDownloader::do_update
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D ClvpDldrState::Start
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Sending DnER...
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D ClvpDldrState::WriteOutPipe DnER
06/05/15 12:54:09.706 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D ClvpDldrState::WriteOutPipe 1
06/05/15 12:54:09.721 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusWdUsb20Device::Write --->DnER
06/05/15 12:54:10.189 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D ClvpDldrState::GetOpCode
06/05/15 12:54:10.189 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D ClvpDldrState::ReadInAck
06/05/15 12:54:10.205 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusWdUsb20Device::GetAck
06/05/15 12:54:10.205 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D usb_bulk_read() fails
06/05/15 12:54:10.205 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Windriver Error: 0xC0007000, USBD: Device gone
06/05/15 12:54:10.222 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D usb_bulk_read() fails
06/05/15 12:54:10.222 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Windriver Error: 0xC0007000, USBD: Device gone
06/05/15 12:54:10.238 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D usb_bulk_read() fails
06/05/15 12:54:10.238 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Windriver Error: 0xC0007000, USBD: Device gone
06/05/15 12:54:10.254 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D usb_bulk_read() fails
06/05/15 12:54:10.254 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Windriver Error: 0xC0007000, USBD: Device gone
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D usb_bulk_read() fails
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Windriver Error: 0xC0007000, USBD: Device gone
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D Device is not responding...
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusWdUsb20Device::GetAck - (0xBAADF00D)
06/05/15 12:54:10.269 INFO : Port 0/0/3 #0: XFSTK-STATUS SN: B8A5A46B0AADF79D Unknown Ack code:baadf00d, aborting ...
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusDownloader::do_abort
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusWdUsb20Device::Abort
06/05/15 12:54:10.269 INFO : Port 0/0/3 #0: XFSTK-STATUS SN: B8A5A46B0AADF79D FAIL
06/05/15 12:54:10.269 INFO : Port 0/0/3 #0: XFSTK-STATUS SN: B8A5A46B0AADF79D Errors encounter during download. Aborting...
06/05/15 12:54:10.269 DEBUG : Port 0/0/3 #0: XFSTK-LOG SN: B8A5A46B0AADF79D CloverviewPlusDownloader::GetStatus
06/05/15 12:54:10.269 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Download operation encountered errors.
06/05/15 12:54:10.269 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Please verify fw/os image integrity and reprovision target.
06/05/15 12:54:10.269 WARNING: Port 0/0/3 #0: Retry IFW Flashing - Serial: B8A5A46B0AADF79D
06/05/15 12:54:10.269 DEBUG : XFSTK Downloader API 1.3.6
Copyright (c) 2012 Intel Corporation
06/05/15 12:54:10.269 DEBUG : fwdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_FWR_DnX_20.3E.bin
06/05/15 12:54:10.269 DEBUG : fwimage -- C:/Users/Grzechu/Desktop/rom/IFWI_v64.25_CSAX_PROD.bin
06/05/15 12:54:10.269 DEBUG : osdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_OS_DnX_20.3E.bin
06/05/15 12:54:10.269 DEBUG : osimage -- C:/Users/Grzechu/Desktop/rom/fastboot.img
06/05/15 12:54:10.269 DEBUG : gpflags -- 0x80000045
06/05/15 12:54:10.269 DEBUG : usbsn -- B8A5A46B0AADF79D
06/05/15 12:54:10.269 DEBUG : softfuse --
06/05/15 12:54:10.269 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Interface is not available...
06/05/15 12:54:10.285 DEBUG : Port 0/0/3 #0: SOC Device is disconnected - state:1 - status - Flashing IFWI
06/05/15 12:54:10.285 DEBUG : SOC device lost on port 3
06/05/15 12:54:11.274 WARNING: Port 0/0/3 #0: Retry IFW Flashing - Serial: B8A5A46B0AADF79D
06/05/15 12:54:11.274 DEBUG : XFSTK Downloader API 1.3.6
Copyright (c) 2012 Intel Corporation
06/05/15 12:54:11.274 DEBUG : fwdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_FWR_DnX_20.3E.bin
06/05/15 12:54:11.274 DEBUG : fwimage -- C:/Users/Grzechu/Desktop/rom/IFWI_v64.25_CSAX_PROD.bin
06/05/15 12:54:11.274 DEBUG : osdnx -- C:/Users/Grzechu/Desktop/rom/CLVp_CSAX_OS_DnX_20.3E.bin
06/05/15 12:54:11.274 DEBUG : osimage -- C:/Users/Grzechu/Desktop/rom/fastboot.img
06/05/15 12:54:11.274 DEBUG : gpflags -- 0x80000045
06/05/15 12:54:11.274 DEBUG : usbsn -- B8A5A46B0AADF79D
06/05/15 12:54:11.274 DEBUG : softfuse --
06/05/15 12:54:11.274 DEBUG : XFSTK SN: B8A5A46B0AADF79 D -- Interface is not available...
06/05/15 12:54:12.274 ERROR : Port 0/0/3 #0: IFW flash failed - SN : B8A5A46B0AADF79D
flash problem Helpp !!
hi
after a flashing error with FLASHER V2 i cant reflash my X98 3G for reinstalling Mirek V4.2 after Mirek V6
MFT log :
11/24/15 00:07:44.037 INFO : Manufacturing Flash Tool V 6.0.43 (build on Sun May 18 12:29:29 PDT 2014)
11/24/15 00:07:44.037 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
11/24/15 00:07:44.037 INFO : Using Qt version: 4.8.1
11/24/15 00:07:44.037 INFO : Using XFSTK version: 1.5.5.
11/24/15 00:07:44.052 WARNING: Please select a flash file...
11/24/15 00:07:58.652 INFO : Loading Flash file (T:/Rom teclast/X98 Air 3G 4.4.4(C5Jx) mirek190_v4.2/ROM/flash-system_only_WIPE_DATA.xml)
11/24/15 00:07:58.652 INFO : GP_Flag is set to 0x80000045
11/24/15 00:07:58.652 INFO : Ready to flash!
11/24/15 00:08:03.402 INFO : do_new_medfield_device STARTING TO FLASH
11/24/15 00:08:03.402 INFO : Port 0/1/5 #0: IFW flash started - SN : Baytrail0D53DCBF
11/24/15 00:08:03.402 INFO : Disabling xFSTK wipe out ifwi option
11/24/15 00:08:03.402 INFO : Disabling xFSTK Misc DnX
11/24/15 00:08:11.773 INFO : Disabling xFSTK wipe out ifwi option
11/24/15 00:08:11.773 INFO : Disabling xFSTK Misc DnX
11/24/15 00:08:11.773 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: Baytrail0D53DCBF
11/24/15 00:08:21.126 INFO : Disabling xFSTK wipe out ifwi option
11/24/15 00:08:21.126 INFO : Disabling xFSTK Misc DnX
11/24/15 00:08:21.126 WARNING: Port 0/1/5 #0: Retry IFW Flashing - Serial: Baytrail0D53DCBF
11/24/15 00:08:30.507 ERROR : Port 0/1/5 #0: IFW flash failed - SN : Baytrail0D53DCBF
can you Help me
I have the same issue yesterday and for me it was a wrong entry in SoC/VID. The entry after installing MFT and copy the custom_config.ini was 8086 and that was wrong, it must be 8087. When you not sure, that this is right for you, look in Windows device manager under hardware id of the Android device.
take a look at the Screenshot in this POST
tasar said:
I have the same issue yesterday and for me it was a wrong entry in SoC/VID. The entry after installing MFT and copy the custom_config.ini was 8086 and that was wrong, it must be 8087. When you not sure, that this is right for you, look in Windows device manager under hardware id of the Android device.
take a look at the Screenshot in this POST
Click to expand...
Click to collapse
Thx a lot i think i have already change the value but not the good value (i don't remember)
I have resolved my problem, i have reinstall all the drivers and programs for flashing and reFlash android all is ok !!!!:laugh:
Hi xda-team,
in search for a new tablet, i became aware of this great forum.
I have decided to give the Teclast x98 Air iii a chance to convice me..
When the tablet arrives me, the first thing i do with android devices is, to root and flash a costum rom ?
But there is the point! My first try was, to flash a Mirek Rom V5 (from the Air ii/3G) with the flashing tool which were with in the folder..
Unfortunately, the flash process crushed in the meantime and now i cant boot the tablet anymore..(see pictures)
I can enter the “enx-mode” with the buttons combination (Volume + Power) and i guess i can enter the droidboot (my second try to flash was with the manufacturing flash tool and for that, the tablet boots in the droidboot i guess?)
Also, the power symbol appears when the tabelt is off and i connect it to the power supply.
I made two screenshots (at boot process and failure at flashin) and a logfile of the flashtool..
Code:
# Manufacturing Phone Flash Tool Logs generated on 2015-12-10T00:12:34
######################################
#### Flash tries 1 ####
#### Flash failure 1 ####
#### Flash success 0 ####
#### ####
#### Fail IFWI 0 ####
#### Fail ENUM 0 ####
#### Fail Modem 0 ####
#### Fail OS 1 ####
######################################
12/10/15 00:10:36.390 INFO : Manufacturing Flash Tool V 6.0.43 (build on Sun May 18 12:29:29 PDT 2014)
12/10/15 00:10:36.390 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
12/10/15 00:10:36.390 INFO : Using Qt version: 4.8.1
12/10/15 00:10:36.390 INFO : Using XFSTK version: 1.5.5.
12/10/15 00:10:36.405 WARNING: Please select a flash file...
12/10/15 00:10:41.770 INFO : Loading Flash file (C:/Mirek Rom/mirek V5 air ii/ROM/flash-full_with_REPARTITION.xml)
12/10/15 00:10:41.770 INFO : GP_Flag is set to 0x80000045
12/10/15 00:10:41.786 INFO : Ready to flash!
12/10/15 00:10:44.900 INFO : do_new_medfield_device STARTING TO FLASH
12/10/15 00:10:44.900 INFO : Port 0/0/2 #0: DNX/droidboot phase - SN : Baytrail09F47559
12/10/15 00:10:49.607 INFO : Port 0/0/2 #0: Booting to droidboot.img success - SN : Baytrail09F47559
12/10/15 00:11:01.477 INFO : Port 0/0/2 #0: Flashing OS
12/10/15 00:11:01.477 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M oem start_partitioning
12/10/15 00:11:04.790 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash /tmp/partition.tbl "C:\Mirek Rom\mirek V5 air ii\ROM\partition.tbl"
12/10/15 00:11:08.758 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M oem partition /tmp/partition.tbl
12/10/15 00:11:10.705 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase cache
12/10/15 00:11:13.400 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase system
12/10/15 00:11:16.127 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase data
12/10/15 00:11:24.994 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase factory
12/10/15 00:11:27.369 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase config
12/10/15 00:11:29.892 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M erase logs
12/10/15 00:11:31.947 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M oem stop_partitioning
12/10/15 00:11:33.831 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M oem wipe ESP
12/10/15 00:11:37.072 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash ESP "C:\Mirek Rom\mirek V5 air ii\ROM\esp.img"
12/10/15 00:11:45.466 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash fastboot "C:\Mirek Rom\mirek V5 air ii\ROM\droidboot.img"
12/10/15 00:11:50.252 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash boot "C:\Mirek Rom\mirek V5 air ii\ROM\boot.img"
12/10/15 00:11:55.007 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash recovery "C:\Mirek Rom\mirek V5 air ii\ROM\recovery.img"
12/10/15 00:11:59.738 INFO : Port 0/0/2 #0: fastboot -s Baytrail09F47559 -S 100M flash system "C:\Mirek Rom\mirek V5 air ii\ROM\system.img"
12/10/15 00:12:05.541 WARNING: Port 0/0/2 #0: Failed to execute "fastboot -s Baytrail09F47559 -S 100M flash system "C:\Mirek Rom\mirek V5 air ii\ROM\system.img"":
12/10/15 00:12:05.792 WARNING: Port 0/0/2 #0: Retry to execute fastboot -s Baytrail09F47559 -S 100M flash system "C:\Mirek Rom\mirek V5 air ii\ROM\system.img"
12/10/15 00:12:12.012 WARNING: Port 0/0/2 #0: Failed to execute "fastboot -s Baytrail09F47559 -S 100M flash system "C:\Mirek Rom\mirek V5 air ii\ROM\system.img"":
sending sparse 'system' (91840 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.042s
12/10/15 00:12:12.263 INFO : do_flash_finished END OF FLASH
12/10/15 00:12:12.263 ERROR : Port 0/0/2 #0: Flash failure
I hope some of you guys can maybe help me?
Greetings
-Tomatello
Maybe i have to flash the original .img?
I prefer not doing anything without an ok from you guys.. i dont want to make the situation worse :/
tomatello said:
Maybe i have to flash the original .img?
I prefer not doing anything without an ok from you guys.. i dont want to make the situation worse :/
Click to expand...
Click to collapse
Seems you are trying to flash bigger than 32GB. So it doesn't success.
Which partition table did you used ?
wassel said:
Seems you are trying to flash bigger than 32GB. So it doesn't success.
Which partition table did you used ?
Click to expand...
Click to collapse
Hi wassel,
i flashed with the original "partition.tbl" file from the Mirkek 190 V6 ultra light , which can be found in the folder with the .img files..didnt changed the partition with the data in the partition folders..
tomatello said:
Hi wassel,
i flashed with the original "partition.tbl" file from the Mirkek 190 V6 ultra light , which can be found in the folder with the .img files..didnt changed the partition with the data in the partition folders..
Click to expand...
Click to collapse
Well, by using another partition-table, the flash process finished at 100 % (green) so far...
The Alias (null) -> shell failure still appears .
Edit: Fixed my problem.
By typing "exit" in the shell comando line, android started after that normaly.
Edit2: i always have to typing this now in the commando line at every start.. can i solve this somehow?
Thanks
tomatello said:
Well, by using another partition-table, the flash process finished at 100 % (green) so far...
The Alias (null) -> shell failure still appears .
Edit: Fixed my problem.
By typing "exit" in the shell comando line, android started after that normaly.
Edit2: i always have to typing this now in the commando line at every start.. can i solve this somehow?
Thanks
Click to expand...
Click to collapse
Hi tomatello,
Exactly the same is hapening to me, but my tablet enters to BIOS when I type "exit" in the shell comando.
Which partition-table did you use?
Did you finally solve this problem?
PD: I own C5J6 version...
Gami_92 said:
Hi tomatello,
Exactly the same is hapening to me, but my tablet enters to BIOS when I type "exit" in the shell comando.
Which partition-table did you use?
Did you finally solve this problem?
PD: I own C5J6 version...
Click to expand...
Click to collapse
My problem was solved by flashing the ROM again changing ROM's directon to C:\ROM and using a different USB data cable.
Cheers,
Gami.
Hi guys.
I think I have bricked my one week ago purchased device. Screen stucks to Chinese logo and does not boot up.
That happenned after accidental stock UI freeze. I am only able to get into DNX mode.
I tried to fix using Manufacturing Flash Tool to reflash stock ROM, but flashing process stops at 5% and I get the message "IFW flash failed". I have read all similar threads but I do not know what the condition of device is to continue. Wouldn't be that nice to make it worse. Please help.
Thanks in advance.
P.S. I apologise for my bad English.
Matinaki said:
Hi guys.
I think I have bricked my one week ago purchased device. Screen stucks to Chinese logo and does not boot up.
That happenned after accidental stock UI freeze. I am only able to get into DNX mode.
I tried to fix using Manufacturing Flash Tool to reflash stock ROM, but flashing process stops at 5% and I get the message "IFW flash failed". I have read all similar threads but I do not know what the condition of device is to continue. Wouldn't be that nice to make it worse. Please help.
Thanks in advance.
P.S. I apologise for my bad English.
Click to expand...
Click to collapse
At last I resolved problem. After a copy-paste of the CUSTOM_CONFIG.INI file manually to C:\Program Files(x86)\Intel\MFT the problem resolved.
Now I can get into bootloader.
still not flashing ability
Well,
I resolved previous problem but still tablet does not boot. I try to flash rom through DNx mode, but bar stops at 10% and I get the message: timeout to enum adb (TIMEOUT = 180)
MTF SETTINGS
SOC devices VID 8087 PID 0A65
Android device VID 8087 PID 09EF
LOG:
# Manufacturing Phone Flash Tool Logs generated on 2016-02-09T20:58:08
######################################
#### Flash tries 1 ####
#### Flash failure 1 ####
#### Flash success 0 ####
#### ####
#### Fail IFWI 0 ####
#### Fail ENUM 1 ####
#### Fail Modem 0 ####
#### Fail OS 0 ####
######################################
02/09/16 20:52:36.131 INFO : Manufacturing Flash Tool V 6.0.43 (build on Sun May 18 12:29:29 PDT 2014)
02/09/16 20:52:36.131 INFO : Loading settings from C:/ProgramData/INTEL/Manufacturing Flash Tool.ini
02/09/16 20:52:36.162 INFO : Using Qt version: 4.8.1
02/09/16 20:52:36.162 INFO : Using XFSTK version: 1.5.5.
02/09/16 20:52:36.162 WARNING: Please select a flash file…
02/09/16 20:52:53.146 INFO : Loading Flash file (C:/Users/Γιώργος/Desktop/Teclast/rom debloaded/X98 Air III (M5C5) GoogleNow/flash.xml)
02/09/16 20:52:53.162 INFO : GP_Flag is set to 0x80000045
02/09/16 20:52:53.162 INFO : Ready to flash!
02/09/16 20:53:33.258 INFO : do_new_medfield_device STARTING TO FLASH
02/09/16 20:53:33.258 INFO : Port 0/0/1 #0: DNX/droidboot phase – SN : Baytrail00000832
02/09/16 20:53:38.268 INFO : Port 0/0/1 #0: Booting to droidboot.img success – SN : Baytrail00000832
02/09/16 20:56:36.484 ERROR : Port 0/0/1 #0: Device on port 0/0/1 #0 timeout to enum adb (TIMEOUT = 180)
Any idea what is going on?
Please help.
Thanks
hey guys..
anyone has DA for this MTK device..? device is totally dead.. only preloader recognized as Device Manager..
Phone found! [ 46 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 8127
BB_CPU_NME : [MediaTek] MT8127_S00
BB_CPU_EXT : 0xCA03 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
t-mobile_mda said:
hey guys..
anyone has DA for this MTK device..? device is totally dead.. only preloader recognized as Device Manager..
Phone found! [ 46 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 8127
BB_CPU_NME : [MediaTek] MT8127_S00
BB_CPU_EXT : 0xCA03 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
Click to expand...
Click to collapse
I don't think anyone has this. It would have made hacking the tablet tins easier if we did.
Might be only option is the unlock thread, with shorting the PIN to get direct brom access(or whatever mode it is called)