Hello
Flashtool can be downloaded on the Flashtool Homepage
As Flashtool was originally developped for X10, you can find a lot of information on the Original X10 Flashtool thread
Major update for 0.6.8.0 : Ability to now install CWM from Flashtool on locked bootloader for LT15/LT18.
Fastboot now works fine under linux
Major feature for 0.6.5.0 is Linux and Windows editions, Drag&Drop for FTF files.
Major new feature : Fastboot toolbox for 2011 line devices.
Please post fastboot issues here in this thread
hey ppl we have added support for all new Xperia 2011 devices...
Code:
ST17 - coconut - ACTIVE
LT15 - anzu - ARC
LT18 - ayame - ARC S
WT19 - satsuma - LIVE WALKMAN
ST15 - smultron - MINI
SK17 - mango - MINI PRO
MT15 - hallon - NEO
MT11 - haida - NEO V
R800 - zeus,zeusc - PLAY
MK16 - iyokan - PRO
ST18 - urushi - RAY
this update will feature fastboot support!!!
check 1st post for more info and follow link to get latest files!!!
also any issue related to fastboot should be posted in the corresponding device threads...
will make stuff easier for us
hope u guys understand
P.S.: the fastboot toolbox is easy to use... in case some users are having issues using it i will create a small tutorial later...
regards,
DooMLoRD
Thanks for this but it always says that "Device connected with USB debugging off" and in fact USB debugging is ON !!
My device is xperia mini pro SK17i
Rami1987 said:
Thanks for this but it always says that "Device connected with USB debugging off" and in fact USB debugging is ON !!
My device is xperia mini pro SK17i
Click to expand...
Click to collapse
Can you try this :
1 - Exit Flashtool
2 - go to x10flasher_lib folder inside Flashtool install folder and edit driverid.properties
3 - remove all lines except this one : flash1=VID_0FCE&PID_ADDE
4 - Restart flashtool
So now we can flash costum kernels even if we dont have fastboot on device right?
Doomlord you should reall make a tut for this.
Thanks in advance
zousoum96 said:
So now we can flash costum kernels even if we dont have fastboot on device right?
Doomlord you should reall make a tut for this.
Thanks in advance
Click to expand...
Click to collapse
if ur bootloader isnt unlocked then u cant flash kernels...
ok i will make a tutorial for this over weekend...
DooMLoRD said:
if ur bootloader isnt unlocked then u cant flash kernels...
ok i will make a tutorial for this over weekend...
Click to expand...
Click to collapse
how come x10 mini pro can flash kernel with locked bootloader? is it not the same process? if not, would it be possible to flash the way they do?
batjon said:
how come x10 mini pro can flash kernel with locked bootloader? is it not the same process? if not, would it be possible to flash the way they do?
Click to expand...
Click to collapse
those devices have hacked bootloaders to support flashing custom kernels...
since new xperia 2011 device already support fastboot there is no need to hack their bootloaders... simply unlock them... the official or unofficial way
DooMLoRD said:
those devices have hacked bootloaders to support flashing custom kernels...
since new xperia 2011 device already support fastboot there is no need to hack their bootloaders... simply unlock them... the official or unofficial way
Click to expand...
Click to collapse
ah ok, thanks for clarifying.
I'm new to the new mini pro so please pardon my ignorance.. I've been reading through the forum and even though it is possible to unlock the bootloader on a branded phone (like i have), it is not possible to enable fastboot on the branded phone? For people who have this problem is it going to be forever impossible to flash custom kernels?
thanks
Thanks for the info i have unlocked my bootloader with the hardware trick
so now i can flash costum kernels and roms
Thank you Doom so much
Here is a small update that resolves the following issue :
Device not recognized correctly when plugged.
https://github.com/downloads/Androxyde/Flashtool/Flashtool-0.5.1.0-update.exe
Thank you so much for the update.. I will check it up..
Androxyde said:
Can you try this :
1 - Exit Flashtool
2 - go to x10flasher_lib folder inside Flashtool install folder and edit driverid.properties
3 - remove all lines except this one : flash1=VID_0FCE&PID_ADDE
4 - Restart flashtool
Click to expand...
Click to collapse
EDIT: for clarification, I have the same issue with the same phone.
I don't have the driverid.properties file in that folder.
shall I create one? EDIT - I tried that, didn't do ****. Something wrong with my install?
dryhte said:
I don't have the driverid.properties file in there.
shall I create one? EDIT - I tried that, didn't do ****. Something wrong with my install?
Click to expand...
Click to collapse
Install 0.5.0.0 then install 0.5.3 update and you shouldn't have anymore problems.
the driverid.properties file is removed with the 0.5.3 update. No more used.
Androxyde said:
Install 0.5.0.0 then install 0.5.3 update and you shouldn't have anymore problems.
the driverid.properties file is removed with the 0.5.3 update. No more used.
Click to expand...
Click to collapse
I just installed flashtool for the first time, (0.5.0.0 with 0.5.3.0 over it) and I had the same issue, that flashtool does not recognize my usb debugging settings.
dryhte said:
I just installed flashtool for the first time, (0.5.0.0 with 0.5.3.0 over it) and I had the same issue, that flashtool does not recognize my usb debugging settings.
Click to expand...
Click to collapse
once your device is plugged, go to Help -> Check drivers and give me the output please ?
Androxyde said:
once your device is plugged, go to Help -> Check drivers and give me the output please ?
Click to expand...
Click to collapse
Hi,
I changed from MTP to MSC which didn't seem to help at first, but now when I reconnect, more is recognized.
I'll still give you the output:
(with MSC)
Code:
24/006/2011 15:06:15 - INFO - <- This level is successfully initialized
24/006/2011 15:06:18 - INFO - Device connected with USB debugging on
24/006/2011 15:06:20 - INFO - Connected device : SK17
24/006/2011 15:06:21 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
24/006/2011 15:06:21 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf
24/007/2011 15:07:50 - INFO - List of connected devices (Device Id) :
24/007/2011 15:07:50 - INFO - - USB\VID_0FCE&PID_6166\42583930324B43415332: OK
24/007/2011 15:07:50 - INFO - List of ADB devices :
24/007/2011 15:07:50 - INFO - - 42583930324B43415332
24/007/2011 15:07:50 - INFO - List of fastboot devices :
(with MTP)
Code:
24/013/2011 15:13:28 - INFO - Device connected with USB debugging off
24/014/2011 15:14:16 - INFO - List of connected devices (Device Id) :
24/014/2011 15:14:17 - INFO - - USB\VID_0FCE&PID_5166\42583930324B43415332: OK
24/014/2011 15:14:17 - INFO - List of ADB devices :
24/014/2011 15:14:17 - INFO - List of fastboot devices :
I also think a short intro with what you can do with the program, and what types of files you need for that purpose, and what state your phone needs to be in in order to do it all, would help a lot...
EDIT: e.g. how to put the phone in flashmode (I know there's a picture, but it doesn't seem to work for me... probably since my 'back' button is a capacitative button in stead of a proper one)
thanks
dryhte said:
EDIT: e.g. how to put the phone in flashmode (I know there's a picture, but it doesn't seem to work for me... probably since my 'back' button is a capacitative button in stead of a proper one)
thanks
Click to expand...
Click to collapse
we will try n create a list for all devices (flashmode entry, fastboot entry)
dryhte said:
Hi,
I changed from MTP to MSC which didn't seem to help at first, but now when I reconnect, more is recognized.
I'll still give you the output:
(with MSC)
Code:
24/006/2011 15:06:15 - INFO - <- This level is successfully initialized
24/006/2011 15:06:18 - INFO - Device connected with USB debugging on
24/006/2011 15:06:20 - INFO - Connected device : SK17
24/006/2011 15:06:21 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
24/006/2011 15:06:21 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf
24/007/2011 15:07:50 - INFO - List of connected devices (Device Id) :
24/007/2011 15:07:50 - INFO - - USB\VID_0FCE&PID_6166\42583930324B43415332: OK
24/007/2011 15:07:50 - INFO - List of ADB devices :
24/007/2011 15:07:50 - INFO - - 42583930324B43415332
24/007/2011 15:07:50 - INFO - List of fastboot devices :
(with MTP)
Code:
24/013/2011 15:13:28 - INFO - Device connected with USB debugging off
24/014/2011 15:14:16 - INFO - List of connected devices (Device Id) :
24/014/2011 15:14:17 - INFO - - USB\VID_0FCE&PID_5166\42583930324B43415332: OK
24/014/2011 15:14:17 - INFO - List of ADB devices :
24/014/2011 15:14:17 - INFO - List of fastboot devices :
I also think a short intro with what you can do with the program, and what types of files you need for that purpose, and what state your phone needs to be in in order to do it all, would help a lot...
EDIT: e.g. how to put the phone in flashmode (I know there's a picture, but it doesn't seem to work for me... probably since my 'back' button is a capacitative button in stead of a proper one)
thanks
Click to expand...
Click to collapse
The problem is that all these case can be detected by program by I go on step by step and each time someone get stuck, I get some info and I go one step further
My goal is that flashtool will detect correctly how your device is connected and give the advice itself
OK thanks guys (by the way, my phone is not unlocked, maybe that's why I couldn't get to flash mode?)
Hi, I just did very, very bad thing. i wanted to try ICS alpha on my SE NEO, so I unlocked boot loader, followed all steps of manual and then, I realized it's for NEO V and for this it is not gonna work. But it was the time when I already flashed boot.img and userdata.img. So I wanted to heal it. The "best" idea what came was to erase "system" partition on my device... Sounds nice, noah? And now, problem (It's all big problem) I downloaded Xperia flasher, downloaded Stock firmware for NEO and I dont know how to get it there. In Flasher It looks like this, when I start and it stucks on it...
Code:
22/003/2012 01:03:09 - INFO - <- This level is successfully initialized
22/003/2012 01:03:09 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-15 22:00:21
22/003/2012 01:03:14 - INFO - Device disconnected
22/003/2012 01:03:22 - INFO - Selected MT15i.ftf
22/003/2012 01:03:22 - INFO - Preparing files for flashing
22/003/2012 01:03:24 - INFO - Please connect your device into flashmode.
22/003/2012 01:03:29 - INFO - Device connected in flash mode
22/003/2012 01:03:30 - INFO - Start Flashing
22/003/2012 01:03:30 - INFO - Flashing loader
22/003/2012 01:03:32 - INFO - PROT_VER="03";DATE="20110217";TIME="15:47:00";VER="R4A066";CXC="1234-5769";TYPE="S1_LOADER";UNIQUE_DEV_ID="3D1E4576377EE6976F2F33C0D70B67B8377BEF0B";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4B6D7100471404C815080428000B709BB001002000000000";IMEI="01270300658417";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_ID="0001";ACTIVE_LOADER_AID="0001";MEMDEVS="02:00:002C:00B3:0000:00002000:00020000:00000800:00000040,03:03:001B:534D:0010:0001DA60:00010000:00000200";MAN_ID="002C";DEV_ID="00B3";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="YES";CARD_SIZE="8GB";CARD_DATA="UHJvZE5vPTEyNDUtOTA4OQ1Qcm9kUmV2PVI5QQ1Db3BpZWRCeXRlcz0xMDEyNzUyMzM1DUNvcGllZEZpbGVzPTE2MTU1DUNvcGllZERpcnM9MTM0DU9yZGVyPTkwMjIxNDAtMTAN";LOADER_ROOT="S1_Loader_Root_773f";EROM_ROOT="S1_EROM_Root_d601";SW_ROOT="S1_SW_Root_883f";CUST_ROOT="S1_Cust_Root_9603";SIM_LOCK_ROOT="S1_SL_Root_c422";HW_CONF_ROOT="S1_HWConf_Root_08af";BIM_STATE="DISABLED"
22/003/2012 01:03:32 - INFO - Flashing adsp.sin
;
Please, tell me, what to do with it? It just stays on "Flashing adsp.sin"
1 Use flashtool
Will fix all your worries
Search for the .42 firmware and install that using flashtool
Search for a guide
Dear developers,
I would like to ask for your help, since I, like others, have messed up my X10i.
***Note, I am a newbie. Before trying anything, the X10i had latest Sony stock GB 2.3.3***
First, phone got rooted & bootloader unlocked, via flashtool.
Then,
I installed this: http://forum.xda-developers.com/showthread.php?t=1780398. It worked.
But, since I am in the process of testing & learning different things, decided I wanted to test that I could revert to the stock rom, which I had hoped it was backed up correctly with ClockWorkMod. Something must have gone wrong. Stuck at SE logo (sphere).
Later,
I figured I should try and flash the X10_V1_BLRelock_oemkernel.ftf ( i assumed that was the stock one, in the C:\Flashtool\firmwares folder).The ICS 4.0.4. rom I had flashed, previously, would require the kCernel-CM9-v03.ftf (however, since wi-fi would not work, I changed to: X10_CUSTOM_kernel.ftf).
Thus, after flashing to the X10_V1_BLRelock.ftf kernel, now stuck at the SE logo (letters: Sony Ericsson). Problem is that now in flashtool I get:
-------------------------------------------------------------------------------------------------------------------------------
19/048/2012 16:48:18 - INFO - <- This level is successfully initialized
19/048/2012 16:48:18 - INFO - Flashtool Version 0.8.6.0 built on 2012-06-13 08:08:54
19/048/2012 16:48:18 - INFO - You can drag and drop ftf files here to start flashing them
19/048/2012 16:48:23 - INFO - Device connected in flash mode
19/048/2012 16:48:33 - INFO - Device disconnected
19/048/2012 16:48:36 - INFO - Device connected with USB debugging off
19/048/2012 16:48:36 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/048/2012 16:48:49 - INFO - Device connected with USB debugging on
19/048/2012 16:48:49 - ERROR - Cannot identify your device.
19/048/2012 16:48:49 - INFO - Selecting from user input
19/048/2012 16:48:56 - INFO - Connected device : X10
19/048/2012 16:48:56 - INFO - Installed version of busybox : N/A
19/048/2012 16:48:56 - INFO - Android version : / kernel version : - exec '/system/bin/sh' failed: No such file or directory (2) -
--------------------------------------------------------------------------------------------------------------------------------
PC Companion also does not detect the phone anymore.
AND,obviously phone is not recognized anymore & cant do much. Could you provide some of your wisdom to a dummy?
Have you tried to flash Stock 2.3.3 ftf firmware with Flashtool?
For the info: BLrelock ftf is not a kernel, its to relock the bootloader again.
G-FACE said:
Have you tried to flash Stock 2.3.3 ftf firmware with Flashtool?
For the info: BLrelock ftf is not a kernel, its to relock the bootloader again.
Click to expand...
Click to collapse
Big Thanks to G-Face for his tip. Worked out pretty easily. It was all my fault, being dumm.
*Thanks for the clarification. That's what happens when some1 is stupid . Obviously "BL" stands for bootloader and "relock" ...well duh (lmao). I choose the wrong file, and I'm sure this messed things up even more*
Hello,
Currently i have some problems to root my xperia mini pro (SK17i). It works for me to flash ICS 4.0.4 official using flashtool and the xperia phone running fine. But if i try to follow the guide http://forum.xda-developers.com/showthread.php?t=1701357 from patembe i am unable to to transfer a ST18i rootable kernel on my smartphone.
13/048/2012 22:48:25 - INFO - Device connected with USB debugging on
13/048/2012 22:48:27 - INFO - Connected device : SK17
13/048/2012 22:48:27 - INFO - Installed version of busybox : N/A
13/048/2012 22:48:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
13/049/2012 22:49:13 - INFO - Selected ST18i_4.1.A.0.562_(1252-5332).ftf
13/049/2012 22:49:13 - INFO - Preparing files for flashing
13/049/2012 22:49:14 - INFO - Please connect your device into flashmode.
13/049/2012 22:49:21 - INFO - Device disconnected
13/050/2012 22:50:55 - INFO - Device connected in flash mode
13/050/2012 22:50:55 - INFO - Opening device for R/W
13/050/2012 22:50:55 - INFO - Reading device information
13/050/2012 22:50:55 - INFO - Phone ready for flashmode operations.
13/050/2012 22:50:56 - INFO - Start Flashing
13/050/2012 22:50:56 - INFO - Processing loader
13/050/2012 22:50:56 - INFO - Checking header
13/050/2012 22:50:56 - INFO - Flashing data
13/050/2012 22:50:58 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
13/050/2012 22:50:58 - INFO - Processing kernel.sin
13/050/2012 22:50:58 - INFO - Checking header
13/050/2012 22:50:58 - INFO - Flashing data
13/050/2012 22:50:58 - INFO - Ending flash session
13/050/2012 22:50:58 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
Click to expand...
Click to collapse
Without Windows i am maybe forced to replace the kernel over adb and to do the steps in DooMLoRD's batch file by hand. I dont know currently very much on android but it should i guess it be possible? Can somebody help a little bit?
Thanks
steavenX said:
Hello,
Currently i have some problems to root my xperia mini pro (SK17i). It works for me to flash ICS 4.0.4 official using flashtool and the xperia phone running fine. But if i try to follow the guide http://forum.xda-developers.com/showthread.php?t=1701357 from patembe i am unable to to transfer a ST18i rootable kernel on my smartphone.
Without Windows i am maybe forced to replace the kernel over adb and to do the steps in DooMLoRD's batch file by hand. I dont know currently very much on android but it should i guess it be possible? Can somebody help a little bit?
Thanks
Click to expand...
Click to collapse
Install windows 7 test edition on dualboot. I know, that's hard cause installing windows overrides grub, but that's better to root your phone.
And better root it with this method.
Afterwards you will have to install grub again, but that's the price...
Or you buy windows 7 (test version has a time limit) and then download easybcd and create a startup entrie for grub of linux...
Well it was a painfull job and a lot of wasted time, but its done.
The credits goes to DooMLoRD's and the guy(s) from Flashtool.
1. I did a mistake and tryed to flash a wrong .ftf file. Dont know why but i was sure that i had to take a rootable kernel from a ST18i Stock Image, but we need to use the kernel from MT11i_4.1.A.0.562_Nordic_1253-1755.ftf package. My fault
2. Because i have currently not the time to find out how i can replace a kernel by command line over the android device bridge (adb) i tryed work with windows xp in a virtualbox. Everything seams to be fine but DooMLoRD's rooting kit didnt work in a virtualbox on my linux workstion. Imho it was something between that stopped DooMLoRD's root kit to work (Hardware or USB issue).
3. With a normal native Windows 7 Installation it worked to root my xperia mini pro.
No clue what was wrong. We need a way to do this from linux too
Hi everybody...
I have a Xperia u (ST25i), rooted, bootloader unlocked.and it runs terrarom with build number 1.54...
but yesterday I wanted to roll back to the stock rom with build number 1.100 and I realized that there's an error in flash tools. so I decided to flash the old rom (1.54) but again it's all the same. I uninstalled flash tools and updated to the 9.11 version. I install the flash tools drivers. but again the same...FYI when i try to install the drivers, in the last part it says that something's not installed.but I check all the boxes in installation wizard here is the log I copied from flash tools...
10/034/2013 18:34:42 - INFO - <- This level is successfully initialized
10/034/2013 18:34:42 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
10/034/2013 18:34:47 - INFO - Device disconnected
10/034/2013 18:34:59 - INFO - Selected ST25i / 6.1.1.B.1.100 / Sony
10/034/2013 18:34:59 - INFO - Preparing files for flashing
10/035/2013 18:35:10 - INFO - Please connect your device into flashmode.
10/035/2013 18:35:14 - INFO - Device connected in flash mode
10/035/2013 18:35:14 - INFO - Opening device for R/W
10/035/2013 18:35:15 - INFO - Start Flashing
10/035/2013 18:35:15 - INFO - Processing loader
10/035/2013 18:35:15 - INFO - Checking header
10/035/2013 18:35:15 - INFO - Ending flash session
10/035/2013 18:35:15 - ERROR -
10/035/2013 18:35:15 - ERROR - Error flashing. Aborted
10/035/2013 18:35:15 - INFO - Device connected in flash mode
10/035/2013 18:35:24 - INFO - Device disconnected
plz help me... I have to flash a new rom...
justin9372 said:
plz help me... I have to flash a new rom...
Click to expand...
Click to collapse
Have you flashed this file before?
It could be a problem with the file itself, or driver problem, can you post exactly what is the message you get when installing the drivers ("something" is not very informative)
ChikeD said:
Have you flashed this file before?
It could be a problem with the file itself, or driver problem, can you post exactly what is the message you get when installing the drivers ("something" is not very informative)
Click to expand...
Click to collapse
yeah actually i did and the log is the exact thing that the flashtool shows to me...
justin9372 said:
yeah actually i did and the log is the exact thing that the flashtool shows to me...
Click to expand...
Click to collapse
No, I meant the driver installer not flashtool, you said it says "something" is not installed.
ChikeD said:
No, I meant the driver installer not flashtool, you said it says "something" is not installed.
Click to expand...
Click to collapse
I changed my windows and the drivers installed this time..at first i couldn't flash the 1.100, but after flashing 1.54, everything 's got right