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
But there need to be special edit for x8
jit,xrecovery and other stuff for x10 will now work on x8
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
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,,,
cruizz said:
hmmm...i hope it works, cuz i ever try use the optimize and it isn't work
regards,,,
Click to expand...
Click to collapse
I hope too, I don't have any X8 so I can't test it ;-)
so... if we want to use flashtool, how and where to get the firmware?
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
work on any devices?
wow, that good news
thanks..
oisteink said:
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
Click to expand...
Click to collapse
glad to hear that...ready to download
@airyz :semarange endi gan?
menuju TKP gan... ama ijin sedotnya..
what does iptimize do? Does it autoinstall jit v2 for x8? does it work? Thanks
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Androxyde said:
A new version (0.5.0.0) of flashtool is here
What's new for X8 comunity : BL unlock for X8 added
Click to expand...
Click to collapse
Thanks!!!
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
After the 0.5.1 update there are still issues.
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.
@rav3n_pl
Wow, replaced the e15 properties without installing the 0.5.1 update and my e15 is
detectable by flashtool ....Thank you.
rav3n_pl said:
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.
Click to expand...
Click to collapse
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
Androxyde said:
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
Click to expand...
Click to collapse
In build.prop we have "shakira"
anyone has checked out if on E15 BL unlock works at all with the latest update??
Hi everyone, i just changed my pc so i had to install flashtool and all the rest again.
i installed the SDK, flashtool (and the drivers inside the folder for my arc S) but when my phone was connected it didnt recnoze him telling me i had to install drivers.
So i downloaded PC Companion and let it install my right drivers , infact after flashtool reconized my device.
the problem is that when i reboot it into fastboot mode to flash a new kernel it tells me that i need the driver :\
i tried to install them manualy from "device manager" in window's setup but they wont install.
i hard resetted device, and uninstalled flashtool many times but nothing change.
16/023/2012 18:23:03 - ERROR - Drivers need to be installed for connected device.
16/023/2012 18:23:03 - ERROR - You can find them in the drivers folder of Flashtool.
16/023/2012 18:23:17 - INFO - List of connected devices (Device Id) :
16/023/2012 18:23:17 - INFO - - USB\VID_0FCE&PID_0DDE\BX902VRA0X&ZLP Driver installed : false
16/023/2012 18:23:17 - INFO - List of ADB devices :
16/023/2012 18:23:17 - INFO - - none
16/023/2012 18:23:17 - INFO - List of fastboot devices :
16/023/2012 18:23:17 - INFO - - none
Unable to root Sony Xperia Pro MK16 with flashtool
Even i am getting following log while rooting my phone.
16/001/2012 12:01:19 - INFO - <- This level is successfully initialized
16/001/2012 12:01:19 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
16/001/2012 12:01:19 - INFO - You can drag and drop ftf files here to start flashing them
16/001/2012 12:01:21 - INFO - Device connected with USB debugging on
16/001/2012 12:01:21 - INFO - Connected device : MK16
16/001/2012 12:01:21 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
16/001/2012 12:01:21 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.587
16/002/2012 12:02:13 - INFO - Pushing C:\Flashtool\.\devices\MK16\busybox\1.19.0\busybox to /data/local/tmp/busybox
16/002/2012 12:02:14 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
16/002/2012 12:02:14 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
16/002/2012 12:02:16 - INFO - Please look at your device and click RESTORE!
16/002/2012 12:02:16 - INFO - You have 60 seconds to follow the restore advice
16/002/2012 12:02:16 - INFO - Running adbrestoreexploit
16/003/2012 12:03:17 - INFO - Root hack did not work. Cleaning hack files
16/007/2012 12:07:47 - INFO - Device disconnected
16/008/2012 12:08:41 - INFO - Device connected with USB debugging on
16/008/2012 12:08:42 - INFO - Connected device : MK16
16/008/2012 12:08:42 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary.
16/008/2012 12:08:42 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.587
The root hack is not working why?:crying:
No one knows what phone you are using or what you are trying to flash. May be better in your device forum.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Guys, I tried rooting my XU thru flashtool, but so far I havent had success.
OK, here's what I do, correct me if I'm wrong.
- First of all turn on debugging mode in phone and also tick non-market apps.
- flashtool recognises my phone after connecting. Select the Padlock icon and choose superuser.
- flashtool begins process of rooting, but I dont get the ROOTME in backup and restore.
P.S I'm on stock ICS.
Here's log file from flashtool.
This is the log file, I dont know whats wrong.
17/010/2012 17:10:53 - INFO - <- This level is successfully initialized
17/010/2012 17:10:53 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
17/010/2012 17:10:53 - INFO - You can drag and drop ftf files here to start flashing them
17/010/2012 17:10:58 - INFO - Device disconnected
17/011/2012 17:11:02 - INFO - Device connected with USB debugging off
17/011/2012 17:11:02 - INFO - For 2011 devices line, be sure you are not in MTP mode
17/011/2012 17:11:04 - INFO - Device connected with USB debugging on
17/011/2012 17:11:04 - INFO - Connected device : ST25
17/011/2012 17:11:04 - INFO - Installed version of busybox : N/A
17/011/2012 17:11:04 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.10
17/011/2012 17:11:11 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.20.0\busybox to /data/local/tmp/busybox
17/011/2012 17:11:11 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
17/011/2012 17:11:11 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
17/011/2012 17:11:13 - INFO - Pushing C:\Flashtool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
17/011/2012 17:11:13 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
17/011/2012 17:11:13 - INFO - You have 60 seconds to follow the restore advice
17/011/2012 17:11:13 - INFO - Running adbrestoreexploit
17/011/2012 17:11:14 - INFO - Root hack did not work. Cleaning hack files
If you want to root your phone by another method follow the instructions here :
http://forum.xda-developers.com/showthread.php?t=1886460
If the info helped you click the thanks button
Sent from my LT26i
I just recently got a new X10a so I flashed the new 2.3.3 global generic firmware so that I could root it via flashtool. However, everytime I try and root my phone I get this:
20/021/2012 20:21:29 - INFO - Device connected with USB debugging on
20/021/2012 20:21:29 - INFO - Connected device : X10
20/021/2012 20:21:29 - INFO - Installed version of busybox : N/A
20/021/2012 20:21:29 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537 / Build number : 3.0.1.G.0.75
20/021/2012 20:21:43 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.20.0\busybox to /data/local/tmp/busybox
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
20/021/2012 20:21:45 - INFO - Running part1 of Root Exploit, please wait
20/021/2012 20:21:45 - INFO - Waiting for device. After 60secs, stop waiting will be forced
20/022/2012 20:22:47 - INFO - Forced stop waiting.
20/022/2012 20:22:47 - ERROR - The part1 exploit did not work
20/022/2012 20:22:47 - INFO - Cleaning files
It should also be noted that I've tried to use the GB ready flashtool 0.2.9.1 to try and root my phone and when I use it the program says that it completed the root successfully. But when I open root checker it tells me I have no root access. Is there anything that can help this? Would manually rooting my phone help anything?
I am actually getting the same issue when attempting to root a x10a. Here's my post in the other thread
http://forum.xda-developers.com/showpost.php?p=34430771&postcount=1849
check out the response from the creator of the Flashtool
http://forum.xda-developers.com/showpost.php?p=34483707&postcount=1854
I've already applied the update and it works fine for me now
waldo98 said:
check out the response from the creator of the Flashtool
http://forum.xda-developers.com/showpost.php?p=34483707&postcount=1854
I've already applied the update and it works fine for me now
Click to expand...
Click to collapse
Thanks a lot man!
Hello,
i'm trying to root 6.1.B.0.544 on xperia p using a guide in developer section.
but i'm getting this.
28/039/2012 00:39:44 - INFO - <- This level is successfully initialized
28/039/2012 00:39:44 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
28/039/2012 00:39:44 - INFO - You can drag and drop ftf files here to start flashing them
28/039/2012 00:39:49 - INFO - Device connected with USB debugging on
28/039/2012 00:39:50 - INFO - Connected device : LT22
28/039/2012 00:39:50 - INFO - Installed version of busybox : N/A
28/039/2012 00:39:50 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.B.0.544
28/040/2012 00:40:23 - INFO - Pushing C:\Flashtool\.\devices\LT22\busybox\1.20.0\busybox to /data/local/tmp/busybox
28/040/2012 00:40:23 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
28/040/2012 00:40:23 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
28/040/2012 00:40:24 - INFO - Pushing C:\Flashtool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
28/040/2012 00:40:26 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
28/040/2012 00:40:26 - INFO - You have 60 seconds to follow the restore advice
28/040/2012 00:40:26 - INFO - Running adbrestoreexploit
28/040/2012 00:40:26 - INFO - Root hack did not work. Cleaning hack files
any ideas???
Did u selected root me on u phone screen during rooting??
Go to the development section and find the thread with kernels hosted on mediafire. Download the .54 and the .10 one.
Flash the .10 kernel via flashtool and run the root using bin4ry method (in dev section again). Once rooted, flash back .54 kernel via flashtool. Sorry for no links, on phone.