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??
Related
I have done everything(phone rooted,recovery installed and unlocked boot loader)There is option to install kernel through flashtool and i have installed Doomkernel V6 successfully as the log says.But how do i know it.
Easiest way to check it... go to Settings > about phone ... there it should show which kernel you have.
HAve Fun
DIP
No sign of doom kernel in settings.Still showing the stock kernel.
if you have terminal emulator or..
or adb shell.
type ----> cat /proc/version
it will tell you for sure which kernel is running
Through flashtool log
Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
Best way to do it is using S1tool, just run the prog,click identify, connect in flash mode and read the output, if "S1 ERROM VER" starts with a small letter "r8A033" it is unlocked, if starts with a capital letter "R8A033" it is not
One last thing, if you SIM.unlocked your phone using Omnius, then the bootloader it's unlocked, but the flashing process is different, I can tell you because that is my case (and it will appear as not "R8A033")
Can you try reflashing and make sure the Flashtool didn't report any errors?
Here's the log
22/023/2012 15:23:05 - INFO - Installing kernel to device...
22/023/2012 15:23:05 - INFO - Remounting system read-write
22/023/2012 15:23:23 - INFO - Installing chargemon feature / kernel bootkit to device...
22/023/2012 15:23:23 - INFO - Remounting system read-write
22/023/2012 15:23:24 - INFO - Pushing C:\Flashtool\.\devices\X10\bootkit\bootkit.tar to /data/local/tmp
22/023/2012 15:23:24 - INFO - Running installbootkit as root thru sysrun
22/023/2012 15:23:24 - INFO - bootkit successfully installed
22/023/2012 15:23:24 - INFO - Pushing C:\Flashtool\.\devices\X10\kernel\2.6.29-modFXP-DooMKernel-v06-1113\kernel.tar to /data/local/tmp
22/023/2012 15:23:28 - INFO - Running installkernel as root thru sysrun
22/023/2012 15:23:30 - INFO - kernel successfully installed
22/023/2012 15:23:45 - INFO - Device disconnected
22/023/2012 15:23:50 - INFO - Device connected with USB debugging on
22/023/2012 15:23:50 - INFO - Connected device : X10
22/023/2012 15:23:50 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/023/2012 15:23:50 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
Did you install the kernel via flashmode or some kind of other method? I don't recall the process to be that long when flashing a kernel.
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
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>cd android-sdk
C:\android-sdk>cd tools
C:\android-sdk\tools>fastboot.exe -i 0x0fce oem unlock 0xFF6C0B6CABAA77A3
... INFOUnlock phone requested
FAILED (remote: Phone is already unlocked!)
C:\android-sdk\tools>
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
@x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
1869 KB/s (119636 bytes in 0.062s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
2338 KB/s (1085140 bytes in 0.453s)
Pushing su binary ....
2874 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
2491 KB/s (996704 bytes in 0.390s)
Making busybox runable ...
.
Pushing fake Backup
2304 KB/s (73728 bytes in 0.031s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.VIEW dat=com.sonyericsson.vendor.ba
ckuprestore/.ui.BackupActivity }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity flg=0x100000
00 }
If all is successful i will tell you, if not this shell will run forever.
Running ......
05/040/2012 07:40:56 - INFO - <- This level is successfully initialized
05/040/2012 07:40:56 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
05/040/2012 07:40:56 - INFO - You can drag and drop ftf files here to start flashing them
05/040/2012 07:40:58 - INFO - Device connected with USB debugging on
05/040/2012 07:40:59 - INFO - Connected device : ST25
05/040/2012 07:40:59 - INFO - Installed version of busybox : N/A
05/040/2012 07:40:59 - INFO - Android version : 2.3.7 / kernel version : 2.6.35.7+ / Build number : 6.0.B.3.184
05/041/2012 07:41:02 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.19.0\busybox to /data/local/tmp/busybox
05/041/2012 07:41:06 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
05/041/2012 07:41:07 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
05/041/2012 07:41:07 - INFO - Running part1 of Root Exploit, please wait
05/041/2012 07:41:26 - INFO - Waiting for device. After 60secs, stop waiting will be forced
05/042/2012 07:42:30 - INFO - Forced stop waiting.
05/042/2012 07:42:30 - ERROR - The part1 exploit did not work
05/042/2012 07:42:30 - INFO - Cleaning files
I want to root my phone mainly to clean **** like facebook and other which eat ram in stock rom. After that all i dont have any icons from supersu/superuser in list. In bin4ry script nothing happen but its supposed to show backup and restore window i think.
The method works only on ICS
Tapatalked !
Ok problem solved i uploaded rooted kernel for gb. And now all works fine. Topic can be closed or go to trash, thanks for reply.
Hello,
I have xperia X10 mini (Not pro): E10.
I've used "Flashtool" to root the phone and then to install "xRecovery" (with the cross button).
I manage to use Flashtool V0.7.1.0 because I didn't succeed rooting with the new version 0.9.9.0.
Flashtool recognised my phone OK (E10) and installed recovery with no errors (Log attached).
Now my phone is rooted and has recovery that I can get into while booting.
My question is- The recovey screen headline says "FreeXperia X8 Recovery v001"
. Is it OK even though my model is X10 mini? or I wiil have troubles when flashing ROMs or Kernels?
22/030/2012 14:30:12 - INFO - <- This level is successfully initialized
22/030/2012 14:30:12 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:23
22/030/2012 14:30:12 - INFO - You can drag and drop ftf files here to start flashing them
22/030/2012 14:30:18 - INFO - Device connected with USB debugging on
22/030/2012 14:30:18 - INFO - Connected device : E10
22/030/2012 14:30:18 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/030/2012 14:30:18 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
22/030/2012 14:30:19 - INFO - Remounting system read-write
22/030/2012 14:30:19 - INFO - Installing toolbox to device...
22/030/2012 14:30:19 - INFO - Pushing D:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
22/030/2012 14:30:20 - INFO - Running installftkit as root thru sysrun
22/030/2012 14:30:20 - INFO - Root Access Allowed
22/030/2012 14:30:58 - INFO - Installing Recovery to device...
22/030/2012 14:30:58 - INFO - Remounting system read-write
22/031/2012 14:31:03 - INFO - Installing chargemon feature / kernel bootkit to device...
22/031/2012 14:31:03 - INFO - Remounting system read-write
22/031/2012 14:31:03 - INFO - Pushing D:\Flashtool\.\devices\E10\bootkit\bootkit.tar to /data/local/tmp
22/031/2012 14:31:03 - INFO - Running installbootkit as root thru sysrun
22/031/2012 14:31:04 - INFO - bootkit successfully installed
22/031/2012 14:31:04 - INFO - Pushing D:\Flashtool\.\devices\E10\recovery\xRec\recovery.tar to /data/local/tmp/recovery.tar
22/031/2012 14:31:05 - INFO - Running installrecovery as root thru sysrun
22/031/2012 14:31:05 - INFO - Recovery successfully installed
Did some trys..
I rerooted the phone with SEUS, and repeated the proccess with v0.8.6.0 of FT: Succeed rooting and recovery install.
But the recovery headline is the same- X8.
Is it OK?
well It say the same on my phone and it works perfect and in t he worst case u can flash a new recovery like cwm or new virson of xrecovery :b
Sent from my E10i using xda app-developers app
aharonzu said:
well It say the same on my phone and it works perfect and in t he worst case u can flash a new recovery like cwm or new virson of xrecovery :b
Sent from my E10i using xda app-developers app
Click to expand...
Click to collapse
Nice to hear that, thx!
When I am going to root my Xperia X10i following error appears. Why is that how to fix this error. Please help me.
Thanks
18/023/2013 09:23:01 - INFO - <- This level is successfully initialized
18/023/2013 09:23:02 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
18/023/2013 09:23:02 - INFO - You can drag and drop ftf files here to start flashing them
18/023/2013 09:23:13 - INFO - Device connected with USB debugging off
18/023/2013 09:23:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/023/2013 09:23:27 - INFO - Device connected with USB debugging on
18/023/2013 09:23:27 - INFO - Connected device : X10
18/023/2013 09:23:27 - INFO - Installed version of busybox : BusyBox v1.16.2androidfull (2011-06-09 17:40:07 CST) multi-call binary.
18/023/2013 09:23:27 - INFO - Android version : 2.3.4 / kernel version : 2.6.38-android-x86+ / Build number : GRJ22
18/023/2013 09:23:38 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.20.0\busybox to /data/local/tmp/busybox
18/023/2013 09:23:41 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
18/023/2013 09:23:42 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
18/023/2013 09:23:44 - INFO - Running part1 of Root Exploit, please wait
18/023/2013 09:23:44 - INFO - Waiting for device. After 60secs, stop waiting will be forced
18/024/2013 09:24:45 - INFO - Forced stop waiting.
18/024/2013 09:24:46 - ERROR - The part1 exploit did not work
18/024/2013 09:24:46 - INFO - Cleaning files
First Root Your Divice With
First Root Your Divice With
http://forum.xda-developers.com/showthread.php?t=1321582
Download Here
After Rooting Your Divice Reboot Once And Install XRecovery Using Flash Tool
BloombergSL said:
When I am going to root my Xperia X10i following error appears. Why is that how to fix this error. Please help me.
Thanks
18/023/2013 09:23:01 - INFO - <- This level is successfully initialized
18/023/2013 09:23:02 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
18/023/2013 09:23:02 - INFO - You can drag and drop ftf files here to start flashing them
18/023/2013 09:23:13 - INFO - Device connected with USB debugging off
18/023/2013 09:23:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/023/2013 09:23:27 - INFO - Device connected with USB debugging on
18/023/2013 09:23:27 - INFO - Connected device : X10
18/023/2013 09:23:27 - INFO - Installed version of busybox : BusyBox v1.16.2androidfull (2011-06-09 17:40:07 CST) multi-call binary.
18/023/2013 09:23:27 - INFO - Android version : 2.3.4 / kernel version : 2.6.38-android-x86+ / Build number : GRJ22
18/023/2013 09:23:38 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.20.0\busybox to /data/local/tmp/busybox
18/023/2013 09:23:41 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
18/023/2013 09:23:42 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
18/023/2013 09:23:44 - INFO - Running part1 of Root Exploit, please wait
18/023/2013 09:23:44 - INFO - Waiting for device. After 60secs, stop waiting will be forced
18/024/2013 09:24:45 - INFO - Forced stop waiting.
18/024/2013 09:24:46 - ERROR - The part1 exploit did not work
18/024/2013 09:24:46 - INFO - Cleaning files
Click to expand...
Click to collapse
BloombergSL said:
When I am going to root my Xperia X10i following error appears. Why is that how to fix this error. Please help me.
Thanks
18/023/2013 09:23:01 - INFO - <- This level is successfully initialized
18/023/2013 09:23:02 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
18/023/2013 09:23:02 - INFO - You can drag and drop ftf files here to start flashing them
18/023/2013 09:23:13 - INFO - Device connected with USB debugging off
18/023/2013 09:23:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/023/2013 09:23:27 - INFO - Device connected with USB debugging on
18/023/2013 09:23:27 - INFO - Connected device : X10
18/023/2013 09:23:27 - INFO - Installed version of busybox : BusyBox v1.16.2androidfull (2011-06-09 17:40:07 CST) multi-call binary.
18/023/2013 09:23:27 - INFO - Android version : 2.3.4 / kernel version : 2.6.38-android-x86+ / Build number : GRJ22
18/023/2013 09:23:38 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
18/023/2013 09:23:40 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.20.0\busybox to /data/local/tmp/busybox
18/023/2013 09:23:41 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
18/023/2013 09:23:42 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
18/023/2013 09:23:44 - INFO - Running part1 of Root Exploit, please wait
18/023/2013 09:23:44 - INFO - Waiting for device. After 60secs, stop waiting will be forced
18/024/2013 09:24:45 - INFO - Forced stop waiting.
18/024/2013 09:24:46 - ERROR - The part1 exploit did not work
18/024/2013 09:24:46 - INFO - Cleaning files
Click to expand...
Click to collapse
You can even Download " Superoneclick " If thats not what your using. Make sure your phone is in "USB Debugging" And is set in charge mode. Not Mass storage device/Connect to computer. and now that i read over the prompt. You were definately not using Superoneclick, Download that. It'll make your life easier.