[TOOL/MINIPRO] [UPDATE 07/01/2013] Flashtool version 0.9.10.0 - Windows / Linux / Mac - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

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?)