[TOOL/E15] [UPDATE 07/01/2013] Flashtool version 0.9.10.0 - Windows / Linux / Mac

Search This thread

Androxyde

Recognized Developer
Aug 3, 2010
1,099
2,836
50
Paris
www.flashtool.net
Hello

Flashtool can be downloaded on the Flashtool Homepage (on Installation tab)

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 new feature :
- Fastboot toolbox for 2011 line devices.
- BL Unlock for X10 Mini/PRo and X8

Please post device related issues here in this thread
 
Last edited:

Asdoos

Senior Member
Nov 27, 2010
298
49
Stuttgart
Changelog:

0.2.8:

[New] The device is autodetected by the flashtool at plug / unplug
[New] If you install xRecovery from flashtool, you can reboot into recovery from flashtool too (Advanced menu)
[New] You can now backup all /system/app content (Advanced menu)
[New] You can translate all parts of the Graphical Interface (look in x10flasher_lib/langs for samples)
[Upd] Firmware screen selection offers the ability to change the folder source containing ftf files.
[Upd] Clean task now has a notion of profile that can be imported/exported for sharing
[Upd] Customize is now APK Installer. This screen has the ability to choose the folder where apk files are
[Upd] Optimize should work for any device (X10, X10mini/pro, X8)
[Upd] xRecovery should work for any device (X10, X10mini/pro, X8)
[Bug] Flashing should not anymore hang if flash goes wrong. An error should be thrown and flash aborted


Watch this
 

cruizz

Senior Member
Dec 17, 2010
317
20
undefined
hmmm...i hope it works, cuz i ever try use the optimize/xrecovery and it isn't work also stuck on boot...but if only for flashing it's work smoothly. i'm sure bin4ry will fixed it :)

regards,,,
 
Last edited:

oisteink

Senior Member
Jan 19, 2011
123
16
Oslo
I've tried it on latest SEMC rom. My phone was already rooted though and I had xrecovery installed. After you check for root you can optimize (will put on jit) and I also installed the new xrecovery.

works for x8

Edit: Install script don't work for xRecovery. It picks the right files, but the script fails.
Code:
09/054/2011 23:54:55 - INFO  - <- This level is successfully initialized
09/055/2011 23:55:02 - INFO  - Connected device : E15
09/055/2011 23:55:02 - INFO  - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
09/055/2011 23:55:14 - DEBUG - <- This level is successfully initialized
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:18 - DEBUG - stderr :7 KB/s (101 bytes in 0.014s)
09/055/2011 23:55:18 - DEBUG - Pushing .\custom\root\checkperms to /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\checkperms /data/local/tmp/runscript
09/055/2011 23:55:18 - DEBUG - stderr :0 KB/s (11 bytes in 0.011s)
09/055/2011 23:55:18 - WARN  - Please check your Phone and 'ALLOW' Superuseraccess!
09/055/2011 23:55:18 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:19 - DEBUG - stdout :uid=0(root) gid=0(root)
09/055/2011 23:55:19 - INFO  - Root Access Allowed
09/055/2011 23:55:25 - INFO  - Installing xRecovery to device...
09/055/2011 23:55:25 - INFO  - Remounting system read-write
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:25 - DEBUG - stderr :10 KB/s (101 bytes in 0.009s)
09/055/2011 23:55:25 - DEBUG - Pushing .\custom\root\remount to /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\remount /data/local/tmp/runscript
09/055/2011 23:55:25 - DEBUG - stderr :15 KB/s (156 bytes in 0.010s)
09/055/2011 23:55:25 - DEBUG - Running remount  as root thru sysrun
09/055/2011 23:55:25 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:26 - INFO  - Pushing .\custom\xRecovery\xrecoveryE15.tar.gz to /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\xrecoveryE15.tar.gz /data/local/tmp/xrecovery.tar.gz
09/055/2011 23:55:26 - DEBUG - stderr :1611 KB/s (1270848 bytes in 0.770s)
09/055/2011 23:55:27 - INFO  - Pushing .\custom\xRecovery\chargemonnew to /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargemonnew /data/local/tmp/chargemon
09/055/2011 23:55:27 - DEBUG - stderr :120 KB/s (741 bytes in 0.006s)
09/055/2011 23:55:27 - INFO  - Pushing .\custom\xRecovery\chargerE15 to /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\chargerE15 /data/local/tmp/charger
09/055/2011 23:55:27 - DEBUG - stderr :350 KB/s (14364 bytes in 0.040s)
09/055/2011 23:55:27 - INFO  - Pushing .\custom\xRecovery\sh to /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\xRecovery\sh /data/local/tmp/sh
09/055/2011 23:55:27 - DEBUG - stderr :1012 KB/s (735308 bytes in 0.709s)
09/055/2011 23:55:27 - DEBUG - Pushing .\custom\root\sysrun to /data/local/tmp/sysrun
09/055/2011 23:55:27 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\sysrun /data/local/tmp/sysrun
09/055/2011 23:55:28 - DEBUG - stderr :14 KB/s (101 bytes in 0.007s)
09/055/2011 23:55:28 - DEBUG - Pushing .\custom\root\installrecovery to /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb push .\custom\root\installrecovery /data/local/tmp/runscript
09/055/2011 23:55:28 - DEBUG - stderr :56 KB/s (583 bytes in 0.010s)
09/055/2011 23:55:28 - INFO  - Running installrecovery  as root thru sysrun
09/055/2011 23:55:28 - DEBUG - Running .\x10flasher_lib\adb shell su -c 'sh /data/local/tmp/sysrun'
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - DEBUG - stdout :rm failed for -f, Read-only file system
09/055/2011 23:55:29 - INFO  - xRecovery successfully installed

hmm - 2nd time i ran the script it installed. it's the removal of the temp files that fails.

I'm happy anyways
 
Last edited:

rav3n_pl

Senior Member
Sep 16, 2011
481
129
Wojcieszyce
bit.ly
not detecting properly

v291
Code:
19/002/2011 01:02:08 - INFO  - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO  - Connected device : E15
19/002/2011 01:02:12 - INFO  - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary

v051:
Code:
19/001/2011 01:01:03 - INFO  - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO  - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO  - Selecting from user input
19/001/2011 01:01:13 - INFO  - Connected device : E15
19/001/2011 01:01:13 - INFO  - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO  - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO  - Root Access Allowed

It is not see my phone automagically, need choose it.

edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15

v291 was looking for
ro.product.model as far I remember

We need update build.prop or change e15.properites :)
Edited file attached.
 

Attachments

  • E15.zip
    340 bytes · Views: 384
Last edited:
  • Like
Reactions: al5911

al5911

Senior Member
Jul 27, 2011
347
35
@rav3n_pl

Wow, replaced the e15 properties without installing the 0.5.1 update and my e15 is

detectable by flashtool ....Thank you.
 
Last edited:

Androxyde

Recognized Developer
Aug 3, 2010
1,099
2,836
50
Paris
www.flashtool.net
v291
Code:
19/002/2011 01:02:08 - INFO  - <- This level is successfully initialized
19/002/2011 01:02:12 - INFO  - Connected device : E15
19/002/2011 01:02:12 - INFO  - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary

v051:
Code:
19/001/2011 01:01:03 - INFO  - <- This level is successfully initialized
19/001/2011 01:01:06 - INFO  - Device connected with USB debugging on
19/001/2011 01:01:08 - ERROR - Cannot identify your device.
19/001/2011 01:01:08 - INFO  - Selecting from user input
19/001/2011 01:01:13 - INFO  - Connected device : E15
19/001/2011 01:01:13 - INFO  - Installed version of busybox : BusyBox v1.19.2-cm71 bionic (2011-10-06 22:08 +0200) multi-call binary.
19/001/2011 01:01:13 - INFO  - Android version : 2.3.7 / kernel version : 2.6.29-Alfs
19/001/2011 01:01:13 - INFO  - Root Access Allowed

It is not see my phone automagically, need choose it.

edit:
v5 is looking for
buildprop=ro.product.device
recognition=E15

v291 was looking for
ro.product.model as far I remember

We need update build.prop or change e15.properites :)
Edited file attached.

what is the value you have for ro.product.device ?

the recognition property can be a coma separated list of values.

for example on X10 I have :
recognition=X10,SO-01B,es209ra

the latest one (es209ra) is the value set by FXP team for CM7 on X10
 

Top Liked Posts

  • There are no posts matching your filters.
  • 57
    Hello

    Flashtool can be downloaded on the Flashtool Homepage (on Installation tab)

    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 new feature :
    - Fastboot toolbox for 2011 line devices.
    - BL Unlock for X10 Mini/PRo and X8

    Please post device related issues here in this thread
    5
    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
    4
    A new version (0.5.0.0) of flashtool is here :)

    What's new for X8 comunity : BL unlock for X8 added :)
    2
    But there need to be special edit for x8
    jit,xrecovery and other stuff for x10 will now work on x8
    2
    Changelog:

    0.2.8:

    [New] The device is autodetected by the flashtool at plug / unplug
    [New] If you install xRecovery from flashtool, you can reboot into recovery from flashtool too (Advanced menu)
    [New] You can now backup all /system/app content (Advanced menu)
    [New] You can translate all parts of the Graphical Interface (look in x10flasher_lib/langs for samples)
    [Upd] Firmware screen selection offers the ability to change the folder source containing ftf files.
    [Upd] Clean task now has a notion of profile that can be imported/exported for sharing
    [Upd] Customize is now APK Installer. This screen has the ability to choose the folder where apk files are
    [Upd] Optimize should work for any device (X10, X10mini/pro, X8)
    [Upd] xRecovery should work for any device (X10, X10mini/pro, X8)
    [Bug] Flashing should not anymore hang if flash goes wrong. An error should be thrown and flash aborted


    Watch this