Related
===============================================================
Sony Ericsson Xperia X8
Model number: (e15i)
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404006
Kernel version 2.6.29 [email protected]#1
Build number 2.1.1.A.0.6
================================================================
This is log:
Code:
08/027/2012 13:27:15 - INFO - <- This level is successfully initialized
08/027/2012 13:27:15 - INFO - Flashtool Version 0.8.0.0 built on 2012-05-27 21:57:12
08/027/2012 13:27:15 - INFO - You can drag and drop ftf files here to start flashing them
08/027/2012 13:27:25 - INFO - Device connected with USB debugging off
08/027/2012 13:27:25 - INFO - For 2011 devices line, be sure you are not in MTP mode
08/027/2012 13:27:32 - INFO - Device connected with USB debugging on
08/027/2012 13:27:33 - INFO - Connected device : E15
08/027/2012 13:27:33 - INFO - Installed version of busybox : N/A
08/027/2012 13:27:33 - INFO - Android version : 4.0.3 / kernel version : 2.6.29.6-nAa-ics-01
08/027/2012 13:27:33 - INFO - Pushing C:\Flashtool\.\devices\E15\busybox\1.19.0\busybox to /data/local/tmp/busybox
08/027/2012 13:27:34 - INFO - Remounting system read-write
08/027/2012 13:27:34 - INFO - Installing toolbox to device...
08/027/2012 13:27:34 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
08/027/2012 13:27:34 - INFO - Running installftkit as root thru sysrun
08/027/2012 13:27:34 - INFO - Root Access Allowed
08/028/2012 13:28:14 - INFO - Selected X8_Shakira_E15i_2.1.1.A.0.6_generic.ftf
08/028/2012 13:28:14 - INFO - Preparing files for flashing
08/028/2012 13:28:24 - INFO - List of connected devices (Device Id) :
08/028/2012 13:28:24 - INFO - - USB\VID_0FCE&PID_612E\BX902GWA6D Driver installed : true
08/028/2012 13:28:24 - INFO - - USB\VID_0FCE&PID_612E&MI_01\7&8D93121&0&0001 Driver installed : true
08/028/2012 13:28:24 - INFO - - USB\VID_0FCE&PID_612E&MI_00\7&8D93121&0&0000 Driver installed : true
08/028/2012 13:28:24 - INFO - List of ADB devices :
08/028/2012 13:28:24 - INFO - - BX902GWA6D
08/028/2012 13:28:24 - INFO - List of fastboot devices :
08/028/2012 13:28:24 - INFO - - none
08/028/2012 13:28:27 - INFO - Please connect your device into flashmode.
08/028/2012 13:28:29 - INFO - Device disconnected
08/029/2012 13:29:20 - INFO - Device connected in flash mode
08/029/2012 13:29:20 - INFO - Opening device for R/W
08/029/2012 13:29:20 - INFO - Reading device information
08/029/2012 13:29:20 - INFO - Phone ready for flashmode operations.
08/029/2012 13:29:20 - INFO - Start Flashing
08/029/2012 13:29:20 - INFO - Flashing loader
08/029/2012 13:29:22 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
08/029/2012 13:29:22 - WARN - This file is ignored : simlock.ta
08/029/2012 13:29:22 - INFO - Flashing kernel.sin
08/029/2012 13:29:26 - INFO - Flashing fota1.sin
08/029/2012 13:29:26 - INFO - Flashing fota0.sin
08/029/2012 13:29:26 - INFO - Flashing amss_fs.sin
08/029/2012 13:29:27 - INFO - Flashing amss.sin
08/029/2012 13:29:37 - INFO - Flashing system.sin
08/031/2012 13:31:21 - INFO - Flashing userdata.sin
08/031/2012 13:31:23 - INFO - Flashing cache.sin
08/031/2012 13:31:23 - INFO - Ending flash session
08/031/2012 13:31:23 - INFO - Flashing finished.
Than I did flash and reboot I have message : "Please insert SIM card and reboot" I do it - nothing happens.
Tryed presh in phonebook "import contacts from your SIM card" have message: "No contacts on SIM card"
Then try choose network operator have message: "your sim card does not allow to register on this network"
tryed to check different SIM card's same error's
tryed switch on/off chip-radio - nothing
tryed install Custom's Rom - nothing
tryed install 06,24 basebands - nothing
I think problem is with BASEBAND or simlock.ta
I searched and found only 2 baseband supported to xperia X8 (06) and (24) .
How to test phone with different baseband's and where to find theys ?Can someone share links where to download basebands by e.g. .64 .66 .72 supported to X8 (E15i)
How to know what kind of version I'm using baseband ? I go to secret menu -> Service info -> Configuration and looking for IMEI software Version: now is 49 or this method is correct ?
I think I need .72 baseband and supported kernel to this Baseband .There to find it? Links ?
(I have bugs in english sorry for that and thanks for answers)
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
baseband
Sony Ericsson Xperia X8
Model number: (e15i)
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404006
Kernel version 2.6.29 [email protected]#1
Build number 2.1.1.A.0.6
remember!
for upgrading your phone baseband must -015
1. maybe you can flash your baseband into 015, i.e X8i_2.1.1.A.0.6_Baseband_015
try to find ond gingerDX media fire file
2. or flash into X8 E15i 2.1.1.C.0.0._un.. you can find on google or 4shared
klick Thanks if I help you
I think the problem is with unlocking the bootloader. I am not sure but did you unlock the bootloader. If so , maybe you did it the wrong way, try to use the s1tool and read carefully all the warnings and instructions..
question
Hi soft33!
Did you ever solved the problem? I am in the same trouble...
Hello and good day.
i hope i can find here some help.
SHORT FACTS AT THE END OF THE POST
my phone went to bootloop after i applyed a backup i made with titanium backup.
sadly, i also restored all system files and my phone went to bootloop when i restarted.
xperia v lt25i with fastboot installed and the bootloader is unlocked.
so as much as i know connecting it to the pc pressing the volume button down the green light goes on and it should be the fastboot mode.
pressing the volume button up and the light goes blue should be the bootloader.
the problem is the phone only stays for 2 secounds in this mode and then going into the battery load mode.
this leaves not much time to install the device drivers on the PC (windows vista)
i managed to install the fastboot driver and now the phone stays +30 secounds in fastboot mode and switches then into the battery mode.
if i try to install the bootloader drivers for the device, he tryes but aborts the install saying "wrong parameter".
during the install he switches from the bootloader into the battery mode.
i installed the android sdk, flashtool(sony mobile flasher), universal adb driver, sony update service,sony pc companion.
sony updateservice says the OS is modified and refuses to update.
the sony pc companion repair function only seems to work with a started phone.
also i somehow manage to get the update/repair function started but it suddenly closes when it downloads/prepares the operation.
connected with active bootloop to the pc he finds the LT25i and wants to install the drivers "sony sa0106 ADB driver interface" but aborts with the reason "wrong parameter"
I had this too before i puted my phone into bootloop.
seems normal coz sony pc companion needs to install the drivers on its own.
when i go into the fastboot mode and open the sony mobile flasher, select in the fastboot toolbox to check the current device status he isnt doing anything.
in the android sdk using the fasstboot tool over the console he shows nothing when giving the "fastboot devices" command.
with "fastboot update" or "fastboot continue" he says "waiting for device" but gets stuck in it.
please if you have any advice what i can do or try or even a solution on my problem let me know.
i would be very happy to solve this problem.
-----
iam a total noob when it comes to programing but 4 days ago i succesfully repaired the phone with a broken touch-lcd screen.
so if a possible solution requires a hardware mod-hack i have good experiance with even soldering smd components with a solder-needle.
LONG SHORT :
bootloop
Bootloader driver doesnt install on the PC.
Fastboot seems to give no response to commands.(in the windows device manager the device is installed as "SEMC flash device")
EDIT:Still trying to get the driver for the flashmode installed with the error "wrong parameter".
may seems to be a windows problem, maybe caused by old driver garbage but i have no solutuion.
How do i get the phone operational again?
Thank you for your time.
First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack
thanks for your reply
nlooooo said:
First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack
Click to expand...
Click to collapse
i deleted some drivers and reinstalled flashtool and the flashtool driverpack.
the s1bootloader or fastboot is now listed in the devicemanager as SEMC flashdevice.
flashtool recognizes the phone in flashmode but gets disconnected after +-40 secounds and then reconnects.
strangely....he now is performing the flash operation.
reading and writing data to the phone or at least trying to do the operation.
the phone is now connected without battery and is off.
no lights on and the screen is dark.
i will wait for the operation to complet.
is this normal??
is it flashing now? or can i abort the operation?
28/035/2014 20:35:22 - INFO - (MainSWT.java:130) - Device connected in flash mode
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\LT25i_9.2.A.1.210_1270-7096_R2J Customized SG.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : system.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : fotakernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_2.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cust-reset.ta
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_1.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : partition-image.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : apps_log.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : tzbsp.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fsg.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : userdata.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cache.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\X10_V1_BLRelock.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : s1boot.sin
28/035/2014 20:35:39 - INFO - (MainSWT.java:1020) - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/035/2014 20:35:39 - INFO - (Bundle.java:406) - Preparing files for flashing
28/035/2014 20:35:39 - DEBUG - (Bundle.java:416) - Created the prepared folder
28/035/2014 20:35:39 - DEBUG - (Bundle.java:325) - Saving entry system.sin to disk
28/035/2014 20:35:39 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : system.sin
28/035/2014 20:35:39 - DEBUG - (Bundle.java:329) - Writing Entry to .\firmwares\prepared\system.sin
28/036/2014 20:36:04 - INFO - (MainSWT.java:126) - Device disconnected
28/036/2014 20:36:08 - INFO - (MainSWT.java:130) - Device connected in flash mode
It broke the operation -.-
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [09, 58, 2F, 8D]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2777 of 16305
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [1F, A6, 11, 1C]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2778 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [C5, B5, C2, 78]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2779 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [08, 8D, FE, AE]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2780 of 16305
28/046/2014 20:46:39 - DEBUG - (MyLogger.java:100) - <- This level is successfully initialized
28/046/2014 20:46:39 - INFO - <- This level is successfully initialized
28/047/2014 20:47:27 - ERROR - Processing of system.sin finished with errors.
28/047/2014 20:47:27 - INFO - Ending flash session
28/047/2014 20:47:27 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
when connected clicking on BLU the bootloader unlock he manages to read some stats
28/052/2014 20:52:57 - INFO - Device connected in flash mode
28/053/2014 20:53:09 - INFO - Please connect your device into flashmode.
28/053/2014 20:53:10 - INFO - Opening device for R/W
28/053/2014 20:53:10 - INFO - Reading device information
28/053/2014 20:53:10 - INFO - Phone ready for flashmode operations.
28/053/2014 20:53:10 - INFO - Current device : LT25i - BX903HDWG2 - 1268-5967_R4I - 1264-2336_9.1.A.1.140 - GLOBAL-LTE_9.1.A.1.140
28/053/2014 20:53:10 - INFO - Processing loader.sin
28/053/2014 20:53:10 - INFO - Checking header
28/053/2014 20:53:10 - INFO - Flashing data
28/053/2014 20:53:10 - INFO - Processing of loader.sin finished.
28/053/2014 20:53:15 - INFO - Loader : S1_Root_7054 - Version : R5A058 / Boot version : R11A023 / Bootloader status : ROOTED
28/053/2014 20:53:15 - INFO - Start Reading unit 000008B2
28/053/2014 20:53:15 - INFO - Reading TA finished.
28/053/2014 20:53:15 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\BX903HDWG2\ulcode.txt
28/053/2014 20:53:17 - INFO - Ending flash session
28/053/2014 20:53:17 - INFO - You can now unplug and restart your device
28/053/2014 20:53:17 - INFO - Device connected in flash mode
28/053/2014 20:53:18 - INFO - Device disconnected
28/053/2014 20:53:20 - INFO - Device connected in flash mode
but then again disconnects.
...all the time.
is it maybe a windows problem?
what can i try or do?
I'm not sure what you have done but this is the correct procedure:
- First of all copy downloaded ftf file to folder c:\Program Files (x86)\Flashtool\firmwares\
- Start flashtool without phone connected to PC.
- Click on thunder icon.
- Choose Flashmode in given list.
- In next window (Firmware selector) choose ftf file you copied to firmware folder, tick to wipe all given options (APPSLOG, CACHE, DATA) and tick 'No final verification.
- Click on Flash and wait for files to be prepared.
- When dialog box appear connect your phone (powered off) to USB cable holding volume down.
- Green led with appear for moment and then it will go off.
- Wait for the process to be finished.
yes yes
he goes into flashmode and so on but after +- 40 secounds he automaticly exits the flashmode the sony sign appears on the screen and the green lamp goes off then starting again in flashmode.
so he periodicaly disconnects the phone and reconnects.
it doesnt matter if i touch the phone or not, so it isnt a broken cable problem.
28/047/2014 21:47:34 - INFO - Device disconnected
28/048/2014 21:48:19 - INFO - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/048/2014 21:48:19 - INFO - Preparing files for flashing
28/048/2014 21:48:28 - INFO - Device connected in flash mode
28/048/2014 21:48:53 - INFO - Please connect your device into flashmode.
28/048/2014 21:48:54 - INFO - Opening device for R/W
28/048/2014 21:48:54 - INFO - Reading device information
28/049/2014 21:49:10 - INFO - Unable to read from phone after having opened it.
28/049/2014 21:49:10 - INFO - trying to continue anyway
28/049/2014 21:49:10 - INFO - Start Flashing
28/049/2014 21:49:10 - INFO - Processing loader.sin
28/049/2014 21:49:10 - INFO - Checking header
28/049/2014 21:49:11 - ERROR - Processing of loader.sin finished with errors.
28/049/2014 21:49:11 - INFO - Ending flash session
28/049/2014 21:49:11 - ERROR - Error in processHeader : 995 : Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.
28/049/2014 21:49:11 - ERROR - Error flashing. Aborted
28/049/2014 21:49:11 - INFO - Device disconnected
Have you tried with Sony Update Service now when you have drivers installed?
28/004/2014 22:04:41 - INFO - Processing of apps_log.sin finished.
28/004/2014 22:04:41 - INFO - Processing cache.sin
28/004/2014 22:04:41 - INFO - Checking header
28/004/2014 22:04:41 - INFO - Flashing data
28/004/2014 22:04:42 - INFO - Processing of cache.sin finished.
28/004/2014 22:04:42 - INFO - Processing system.sin
28/004/2014 22:04:42 - INFO - Checking header
28/004/2014 22:04:42 - INFO - Flashing data
28/005/2014 22:05:09 - ERROR - Processing of system.sin finished with errors.
28/005/2014 22:05:09 - INFO - Ending flash session
28/005/2014 22:05:09 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
Sony update service says the device contains modified data for which no update is available.
is there a tool with which i can read the phone operations?
during the flash operation when the phone is off it suddenly switches back on, as i said showing the sony logo on the screen.
interessting after the last try to flash he now stays in the flashmode and now for over 5 mins.
i tried again but he stoped showing this :
28/015/2014 22:15:45 - INFO - (FlashJob.java:33) - Please connect your device into flashmode.
28/015/2014 22:15:46 - INFO - (USBFlashWin32.java:16) - Opening device for R/W
28/015/2014 22:15:46 - INFO - (X10flash.java:594) - Reading device information
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/015/2014 22:15:46 - INFO - (X10flash.java:606) - Unable to read from phone after having opened it.
28/015/2014 22:15:46 - INFO - (X10flash.java:607) - trying to continue anyway
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - INFO - (X10flash.java:484) - Start Flashing
28/015/2014 22:15:46 - INFO - (X10flash.java:237) - Processing loader.sin
28/015/2014 22:15:46 - DEBUG - (X10flash.java:238) - loader.sin : header size : 1020
28/015/2014 22:15:46 - INFO - (X10flash.java:216) - Checking header
28/015/2014 22:15:46 - DEBUG - (X10flash.java:220) - Sending part 1 of 1
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:252) - Processing of loader.sin finished with errors.
28/015/2014 22:15:46 - INFO - (X10flash.java:544) - Ending flash session
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:517) - Error in processHeader : 6 : Das Handle ist ungültig.
28/015/2014 22:15:46 - ERROR - (X10flash.java:518) - Error flashing. Aborted
28/015/2014 22:15:46 - INFO - (MainSWT.java:130) - Device connected in flash mode
Which version of flashtool do you use?
version 0.9.15.0
i dont think its the tool.
what could be the reason for the phone to continiusly bootloop in flashmode??
WHY?!?
WHAT THE HELL AM I DOING WRONG?!?
it was to 3/4 finished flashing and then....
what does the error mean?
block verification failed?
iam using now the latest flashtool and the Xperia V_9.1.A.1.140_1270-9887_R1I_CE.ftf
what could be the reason for it to just break the flashing???
my god it was almost finished!!
29/038/2014 13:38:46 - INFO - Processing of cache.sin finished.
29/038/2014 13:38:46 - INFO - Processing system.sin
29/038/2014 13:38:46 - INFO - Checking header
29/038/2014 13:38:46 - INFO - Flashing data
29/049/2014 13:49:29 - ERROR - Processing of system.sin finished with errors.
29/049/2014 13:49:29 - INFO - Ending flash session
29/049/2014 13:49:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
edit:
well at least the flashing seems to have a effect.
the phone gets stuck at the sony logo and doesnt permanently reboot.
Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running
You probably broke something from system files.
One more question, is your bootloader unlocked?
EDIT:
Ok, I red the first post again, it is unlocked, you have to relock it first for SUS and PCC to work.
okay? i suppose i can lock and unlock it as often as i want?
thanks a lot guys
you are the best
EDIT:
okay, locked it PCC doesnt work but SUS seems to work now
again thanks ))
Dr CAT said:
Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running
Click to expand...
Click to collapse
how did you solve it? can you please tell me? i have problems on xperia t.
-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys
Dr CAT said:
-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys
Click to expand...
Click to collapse
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin
isko95 said:
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin
Click to expand...
Click to collapse
flashtool brings its own drivers it needs.
in the flashtool folder is one called drivers, you can install them from there.
the new 4.3 ftf just aborted and even the 4.1 ftf which worked before.
so i think its trail and error and pray that it works the next time^^
-.- and again .....
There's one more thing, try to install INF file from Sony Unlock page.
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
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!
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