i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
this comes when flashing
20/044/2013 00:44:14 - INFO - <- This level is successfully initialized
20/044/2013 00:44:15 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
20/044/2013 00:44:15 - INFO - You can drag and drop ftf files here to start flashing them
20/044/2013 00:44:26 - INFO - Device connected with USB debugging on
20/044/2013 00:44:26 - INFO - Connected device : ST17
20/044/2013 00:44:27 - INFO - Installed version of busybox : BusyBox v1.20.2-cm9 bionic (2012-07-14 01:52 +0200) multi-call binary.
20/044/2013 00:44:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-FXP / Build number : IMM76L
20/044/2013 00:44:28 - INFO - Root Access Allowed
20/045/2013 00:45:19 - INFO - Selected WT19i_4.0.2.A.0.58_(1254-1868).ftf
20/045/2013 00:45:19 - INFO - Preparing files for flashing
20/045/2013 00:45:30 - INFO - Please connect your device into flashmode.
20/045/2013 00:45:35 - INFO - Device disconnected
20/046/2013 00:46:14 - INFO - Opening device for R/W
20/046/2013 00:46:15 - INFO - Device connected in flash mode
20/046/2013 00:46:15 - INFO - Start Flashing
20/046/2013 00:46:15 - INFO - Processing loader
20/046/2013 00:46:15 - INFO - Checking header
20/046/2013 00:46:15 - INFO - Ending flash session
20/046/2013 00:46:15 - ERROR -
20/046/2013 00:46:15 - ERROR - Error flashing. Aborted
20/046/2013 00:46:15 - INFO - Device connected in flash mode
Try checking "no final verification" before flashing. Should work
Siddharth121 said:
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
Click to expand...
Click to collapse
you have to tick your usb debugging... and then you must in MSC mode it can be on setting .
and dont connect your phone . you must flashing .ftf then after it wait until they say connect your HH with ~~~~.... after that in 10 seconds connect your usb and phone to pics/ laptop during press volume download
Sent from my WT19i using xda premium
hi,
I have pretty much the same symptoms, my ray is seen as ST17i by flashtool.
Is this a flashtool bug or is it really recognized as ST17i?
Thank you!
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Siddharth121 said:
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
nroberto13 said:
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
Click to expand...
Click to collapse
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Mysteryagr said:
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
yes, I saw the topic, but none of the fices worked for me .
I haven't found anybody on the forum who was successful on a ray with any of the fixes .
any advise?
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
tried that, also flashed system once again, then system and kernel, but phone doesn't boot.
what does cm9/10 different to stock so it boots?
is this issue coming from kernel or from rom?
where are the touch driver placed? in initrd or in rom?
thank you!
Please Help. Please.
I am having WT19i. I have installed Super Jelly Bean 8.0 and having nAa 2.6 kernel. I flashed this kernel through flashtool. That time my device was shown correctly (I guess that means all the drivers are installed correctly). And I havent changed anything on my PC (Windows 7) or in flashtool (0.9.13.0) after that. Now I want to install some KK Rom in my phone. So when I connected my LWW, it shows connected device as Xperia Active (ST17i) instead of WT19i. For that KK Rom, I need to flash .587 stock.ftf file. But I fear if I try to flash, it will brick my phone. I wont get a new mobile in near future. So I dont want to brick it. Anyone please help me through this. How can I get the job done without getting bricked. It will be a great if anyone could tell me.
If I continue with flashing ftf with the current situation (WT19i recognized as ST17i), will it brick my WT19i?? If yes, how to overcome this situation?? Help needed from members. Please, its urgent. I am a newbie actually. This is my first post in xda. Thanks in advance.
Related
[ROM] CyanogenMod 9 - V02 KANG -I can not install cwm recowery error, help please..
Error Current Recowery seems bad!
do you have nAa kernel ?
http://forum.xda-developers.com/showthread.php?t=1415012
faesh said:
do you have nAa kernel ?
http://forum.xda-developers.com/showthread.php?t=1415012
Click to expand...
Click to collapse
I aggre..if you don't have nAa kernel,you can't install cwm recowery.
Flash nAa kernel...and then check...
Flashtool log:
Code:
27/031/2012 16:31:11 - INFO - Device connected in flash mode
27/031/2012 16:31:11 - INFO - Opening device for R/W
27/031/2012 16:31:11 - INFO - Reading device information
27/031/2012 16:31:11 - INFO - Phone reading for flashing.
27/031/2012 16:31:11 - INFO - Phone already unlocked
27/031/2012 16:31:11 - INFO - You can safely reboot in normal mode
27/031/2012 16:31:11 - WARN - Cancelled
27/031/2012 16:31:11 - INFO - Device connected in flash mode
27/031/2012 16:31:16 - INFO - Device disconnected
27/032/2012 16:32:38 - INFO - Device connected in flash mode
27/032/2012 16:32:38 - INFO - Opening device for R/W
27/032/2012 16:32:38 - INFO - Reading device information
27/032/2012 16:32:38 - INFO - Phone reading for flashing.
27/032/2012 16:32:38 - INFO - Start Flashing
27/032/2012 16:32:38 - INFO - Flashing loader
27/032/2012 16:32:40 - INFO - Loader version : R4A045 / Bootloader status : ROOTED
27/032/2012 16:32:40 - INFO - Flashing finished.
27/032/2012 16:32:40 - INFO - Please wait. Phone will reboot
27/032/2012 16:32:40 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
27/032/2012 16:32:41 - INFO - Device connected in flash mode
27/032/2012 16:32:42 - INFO - Device disconnected
27/033/2012 16:33:34 - INFO - Connected device : U20
27/033/2012 16:33:35 - INFO - Installed version of busybox : BusyBox v1.19.1-cm71 bionic (2011-09-01 04:24 +0200) multi-call binary.
27/033/2012 16:33:35 - INFO - Android version : 2.3.7 / kernel version : 2.6.29
27/033/2012 16:33:35 - INFO - Root Access Allowed
Phone already unlocked, naa kernel could not load: (
Where is the error I'm doing?..
Sent from my U20i using xda premium
Try frm the start...go back to stock using SEUS...then try to flash nAa kernel...nd btw which flashtool version are u using?
Sent from my U20i using XDA App
flashtool version : 0.6.7.0 the same mistake again
Code:
27/050/2012 20:50:44 - INFO - Device connected in flash mode
27/050/2012 20:50:44 - INFO - Opening device for R/W
27/050/2012 20:50:45 - INFO - Reading device information
27/050/2012 20:50:45 - INFO - Phone reading for flashing.
27/050/2012 20:50:45 - INFO - Start Flashing
27/050/2012 20:50:45 - INFO - Flashing loader
27/050/2012 20:50:46 - INFO - Loader version : R4A045 / Bootloader status : ROOTED
27/050/2012 20:50:47 - INFO - Flashing finished.
27/050/2012 20:50:47 - INFO - Please wait. Phone will reboot
27/050/2012 20:50:47 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
27/050/2012 20:50:47 - INFO - Device connected in flash mode
27/050/2012 20:50:48 - INFO - Device disconnected
27/051/2012 20:51:15 - INFO - Device connected with USB debugging off
27/051/2012 20:51:15 - INFO - For 2011 devices line, be sure you are not in MTP mode
27/051/2012 20:51:16 - INFO - Device disconnected
27/051/2012 20:51:18 - INFO - Device connected with USB debugging on
27/051/2012 20:51:21 - INFO - Connected device : U20
27/051/2012 20:51:21 - INFO - Installed version of busybox : N/A
27/051/2012 20:51:21 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
Try using flashtool v0.5.3
Sent from my U20i using XDA App
flashtool v0.5.3 log not install nAa kernel 11.
Code:
28/034/2012 11:34:49 - INFO - Searching Xperia....
28/034/2012 11:34:50 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&8080175&0&3
28/034/2012 11:34:50 - INFO - VER="r8A029";DATE="20100601";TIME="12:17:00";
28/034/2012 11:34:50 - INFO - Phone already unlocked
28/034/2012 11:34:50 - WARN - Cancelled
28/031/2012 11:31:08 - INFO - Searching Xperia....
28/031/2012 11:31:08 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&8080175&0&3
28/031/2012 11:31:08 - INFO - Start Flashing
28/031/2012 11:31:08 - INFO - VER="r8A029";DATE="20100601";TIME="12:17:00";
28/031/2012 11:31:08 - INFO - Flashing loader
28/031/2012 11:31:10 - INFO -PROT_VER="02";DATE="20100615";TIME="17:28:00";VER="R4A045";CXC="1229-3641";TYPE="S1_LOADER";UNIQUE_DEV_ID="7B424E52BDC1343270711BC34B673DD42AC200F6";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4DFD7700470404000F080420DA9E4FBD";IMEI="*************";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_AID="0000";ACTIVE_LOADER_AID="0001";MAN_ID="00EC";DEV_ID="00BC";EXT_DEV_ID="0055";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="YES";CARD_SIZE="2GB";CARD_DATA="UHJvZE5vPTEyNDMtNTM0Mw1Qcm9kUmV2PVI2QQ1Db3BpZWRCeXRlcz0zMzkzMDUzNDYNQ29waWVkRmlsZXM9MTAxNjcNQ29waWVkRGlycz02OA1PcmRlcj05MDE4MDcxLTEwDQ==";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
28/031/2012 11:31:10 - INFO - Flashing finished.
28/031/2012 11:31:10 - INFO - Now unplug the device and power it on
28/031/2012 11:31:10 - INFO - Then go to application settings
28/031/2012 11:31:10 - INFO - turn on Unknown Sources and Debugging
8/032/2012 11:32:30 - INFO - Device connected with USB debugging on
28/032/2012 11:32:32 - INFO - Connected device : U20
28/032/2012 11:32:32 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
28/032/2012 11:32:32 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
28/032/2012 11:32:34 - INFO - Root Access Allowed
help me please
I looked at your flashtool log. There are 2 files to be flashed ie. Loader nd kernel.sin... Unfortunately flashtool is skipping the kernel.sin.. :-( wait sometime i will help you out... Til then use stock rom..
Sent from my U20i using XDA App
Waiting for your help. Thank you.
Sent from my U20i using xda premium
TrReCoN said:
Waiting for your help. Thank you.
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Have you read this thread?
http://forum.xda-developers.com/showthread.php?t=1462278
---------- Post added at 10:28 AM ---------- Previous post was at 10:14 AM ----------
TrReCoN said:
flashtool v0.5.3 log not install nAa kernel 11.
Code:
28/034/2012 11:34:49 - INFO - Searching Xperia....
28/034/2012 11:34:50 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&8080175&0&3
28/034/2012 11:34:50 - INFO - VER="r8A029";DATE="20100601";TIME="12:17:00";
28/034/2012 11:34:50 - INFO - Phone already unlocked
28/034/2012 11:34:50 - WARN - Cancelled
28/031/2012 11:31:08 - INFO - Searching Xperia....
28/031/2012 11:31:08 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&8080175&0&3
28/031/2012 11:31:08 - INFO - Start Flashing
28/031/2012 11:31:08 - INFO - VER="r8A029";DATE="20100601";TIME="12:17:00";
28/031/2012 11:31:08 - INFO - Flashing loader
28/031/2012 11:31:10 - INFO -PROT_VER="02";DATE="20100615";TIME="17:28:00";VER="R4A045";CXC="1229-3641";TYPE="S1_LOADER";UNIQUE_DEV_ID="7B424E52BDC1343270711BC34B673DD42AC200F6";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4DFD7700470404000F080420DA9E4FBD";IMEI="01234200392623";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_AID="0000";ACTIVE_LOADER_AID="0001";MAN_ID="00EC";DEV_ID="00BC";EXT_DEV_ID="0055";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="YES";CARD_SIZE="2GB";CARD_DATA="UHJvZE5vPTEyNDMtNTM0Mw1Qcm9kUmV2PVI2QQ1Db3BpZWRCeXRlcz0zMzkzMDUzNDYNQ29waWVkRmlsZXM9MTAxNjcNQ29waWVkRGlycz02OA1PcmRlcj05MDE4MDcxLTEwDQ==";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
28/031/2012 11:31:10 - INFO - Flashing finished.
28/031/2012 11:31:10 - INFO - Now unplug the device and power it on
28/031/2012 11:31:10 - INFO - Then go to application settings
28/031/2012 11:31:10 - INFO - turn on Unknown Sources and Debugging
8/032/2012 11:32:30 - INFO - Device connected with USB debugging on
28/032/2012 11:32:32 - INFO - Connected device : U20
28/032/2012 11:32:32 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
28/032/2012 11:32:32 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
28/032/2012 11:32:34 - INFO - Root Access Allowed
Click to expand...
Click to collapse
I think here you have a good tuturial to start and see if you are doing the right way, http://forum.xda-developers.com/showthread.php?p=10879507#post10879507
problem may be here? loader.sin and kernel.sin does not appear here.
Have to tried to install any other kernel????
Try installing any other
Sent from my U20i using XDA App
yes I've tried Fa kernel; loader.sin and kernel.sin does not appear.
and;
I do not understand why is this happening.
There is also one mre flashtool which I used to flash nAa kernel. See the nAa kernel page...if the link works then download it....if it dosent works then tell me i'll upload the flashtool
sent from my u20i using xda premium
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT
A server error
http://www.multiupload.com/GYL7A7XQBT your server responded too late. The server might be overloaded.
You can see some of the suggestions below:
Reload this web page later.
HTTP Error 504 (Gateway Timeout): one from the upstream server gateway or proxy server timed out waiting for a response.
Click to expand...
Click to collapse
multiupload.com error. Can you give a different link, please. Thank you.
What about the set of drivers for your mimmi required by FT? Did you try to use the "Check drivers" facility inside "Help" menu to check if you have' em installed? It's just a guess but may be the reason.
Also - can't see any "Connect your device in flash mode" command in log. Try not to start with your phone already connected in flash mode but instead start with connecting it while idle > click "Flash" command > pick nAa's kernel & click OK > do as FT tells you (power the phone off and connect it in flash mode) > let us know if anything's changed
Regards,
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
My phone was already rooted using flashtool using 0.2.9.1 GB-ready and had unlocked bootloader. However on updating flashtool, the app tells me that my phone isn't rooted and doesn't have an unlocked bl as well. So I tried flashing it but every time I boot the device into flash mode the process stops and I get this error :
15/022/2012 19:22:13 - INFO - Please connect your device into flashmode.
15/022/2012 19:22:19 - INFO - Device connected in flash mode
15/022/2012 19:22:19 - INFO - Opening device for R/W
15/022/2012 19:22:19 - INFO - Reading device information
15/022/2012 19:22:19 - INFO - Phone ready for flashmode operations.
15/022/2012 19:22:19 - INFO - Start Flashing
15/022/2012 19:22:19 - INFO - Processing loader
15/022/2012 19:22:19 - INFO - Checking header
15/022/2012 19:22:19 - INFO - Ending flash session
15/022/2012 19:22:19 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
Can anybody tell me the solution for this? I had xrecovery installed previously, I tried using SuperOneClick 2.3.3. Funny thing is that I can root my phone(shell root as well) and then start Flashtool 0.9.9 which will detect my phone as rooted(!).. but I can't install CWM recovery.. everytime I do so I get a process done message but if I go into Tools->Reboot->Recover->Specific Recovery all I get is a blank screen.
Now if I restart my phone after getting it rooted from superoneclick, it gets unrooted automatically! This is getting very confusing.. Can somebody help me please?
OP sorry, I have no answers, but I have the same/similar problem.
I figure if I add my information to the information you have provided we may collectively invite some comment to stair us in the direction to an answer.
OP, hope that's OK with you.
Just one thing OP, have you installed the Flashtool 0.9.9 Windows update/bug fix (assuming you're using windows)??
FlashTool-windows-0.9.9update1.zip
I am having all sorts of problems attempting to install a CM9/CM10 kernel with CWM recovery mode on my XPERIA X10i.
My end goal is to install [CM10] v4 (Torch) by: scritch007
I have an unlock??? bootloader and can root my phone. But I'm beginning to question that!!!
I have the following information provided from S1 Tool
Code:
Welcome to S1 tool.
RUNNING S1_EROM VER "R8A031"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB537QU1MN
SEMC SIMLOCK CERTIFICATE
Elapsed:55 secs.
Using the service information menu *#*#7378423#*#* I was able to see my SIM lock was unlocked [] SIM = 0
I have installed a fresh copy of GB 2.3.3 using Flashtool 0.9.9 with additional Windows update1.
I used a 'World' GB 2.3.3 ftf see above.
I have also installed GB using Sony Ericsson Update Service (SEUS) which provides the same base OS.
[Root XPERIA X10i using FlashTool 0.9.9]
I have rooted the device using ZergRush exploit from Flashtools 0.9.9 with update patch FlashTool-windows-0.9.9update1.zip
To do this, I started the phone and enabled debug and unknown source.
With the phone still up and running and Flashtool 0.9.9 also running, I plugged in the USB cable.
I select the "My X10" option -> root -> Force ZergRush and the process then rooted the phone and the phone rebooted with root access, no problems there.
Code:
19/042/2012 11:42:06 - INFO - <- This level is successfully initialized
19/042/2012 11:42:06 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-21 23:15:59
19/042/2012 11:42:06 - INFO - You can drag and drop ftf files here to start flashing them
19/042/2012 11:42:12 - INFO - Device connected with USB debugging on
19/042/2012 11:42:12 - INFO - Connected device : X10
19/042/2012 11:42:12 - INFO - Installed version of busybox : BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
19/042/2012 11:42:12 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-modFXP-DooMKernel-v06 / Build number : 3.0.1.G.0.75
19/042/2012 11:42:12 - INFO - Root Access Allowed
I can also install CWM recovery this way too.
After I have gained root access I have the phone up and running and again plug the USB cable in.
I select recovery mode option in Flashtool 0.9.9 and I'm requested to power down my phone and reconnect.
This then installs a recovery mode, either CWM or xRecovery depending on which one I select.
Again, this is all good and I can boot into either xRecovery or CWM recovery depending on which is installed.
I have installed and used other versions of Flashtool, however the outcomes always seems to be the same.
If I attempt to install a CM9/CM10 ftf I get the following error message:
Code:
19/016/2012 03:16:36 - INFO - <- This level is successfully initialized
19/016/2012 03:16:36 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-21 23:15:59
19/016/2012 03:16:36 - INFO - You can drag and drop ftf files here to start flashing them
19/016/2012 03:16:42 - INFO - Device disconnected
19/016/2012 03:16:55 - INFO - Selected X10_4.1.X_CMX10_bootmanager_v14.ftf
19/016/2012 03:16:55 - INFO - Preparing files for flashing
19/016/2012 03:16:56 - INFO - Please connect your device into flashmode.
19/017/2012 03:17:45 - INFO - Device connected in flash mode
19/017/2012 03:17:46 - INFO - Opening device for R/W
19/017/2012 03:17:46 - INFO - Reading device information
19/017/2012 03:17:46 - INFO - Phone ready for flashmode operations.
19/017/2012 03:17:46 - INFO - Start Flashing
19/017/2012 03:17:46 - INFO - Processing loader
19/017/2012 03:17:46 - INFO - Checking header
19/017/2012 03:17:46 - INFO - Ending flash session
19/017/2012 03:17:46 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
19/017/2012 03:17:46 - ERROR - Error flashing. Aborted
19/017/2012 03:17:46 - INFO - Device connected in flash mode
19/017/2012 03:17:47 - INFO - Device disconnected
19/017/2012 03:17:49 - INFO - Device connected in flash mode
19/018/2012 03:18:10 - INFO - Device disconnected
19/018/2012 03:18:13 - INFO - Device connected with USB debugging off
19/018/2012 03:18:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/018/2012 03:18:23 - INFO - Device disconnected
At the moment I have just given up until I have some good leads to renew my CM9/CM10 install efforts.
At the moment I have GB 2.3.3 rooted with ZergRush exploit.
xRecovery installed
DooMLoRD DooMkernel V6 install with overclocked CPU of 1152MHz
The phone is up and running, rooted and has a modified Kernel which I recovered via xRecovery backup restore.
So, I have a working GB 2.3.3 phone with root access....but I want more...
My phone seems to be a one trick pony and I don't seem to be able to install CM9/CM10 with the information I have to hand.
Any thoughts I why I'd be getting the "SIN header verification failed" message????
********* Update **************
[ANSWER]
I solved my problem by unlocking the bootloader on my XPERIA X10i using the following information.
Tutorial: Rooting, Bootloader unlocking&updating
Remember to have debugging and Unknown source ticked on your XPERIA X10i phone.
Code:
20/015/2012 16:15:44 - INFO - Device connected with USB debugging off
20/015/2012 16:15:44 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/015/2012 16:15:44 - INFO - Device connected with USB debugging on
20/015/2012 16:15:45 - INFO - Connected device : X10
20/015/2012 16:15:45 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
20/015/2012 16:15:45 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
20/015/2012 16:15:46 - INFO - Remounting system read-write
20/015/2012 16:15:46 - INFO - Installing toolbox to device...
20/015/2012 16:15:46 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\root\ftkit.tar to /data/local/tmp
20/015/2012 16:15:46 - INFO - Running installftkit as root thru sysrun
20/015/2012 16:15:47 - INFO - Root Access Allowed
20/016/2012 16:16:22 - INFO - Please connect your device into flashmode.
20/016/2012 16:16:27 - INFO - Device disconnected
20/017/2012 16:17:22 - INFO - Device connected in flash mode
20/017/2012 16:17:22 - INFO - Opening device for R/W
20/017/2012 16:17:22 - INFO - Reading device information
20/017/2012 16:17:22 - INFO - Phone ready for flashmode operations.
20/017/2012 16:17:22 - INFO - Flashing loader
[COLOR="Red"]20/017/2012 16:17:24 - INFO - Loader : S1_Loader_Root_f851 - Version : R4A024 / Bootloader status : UNROOTABLE[/COLOR]
20/017/2012 16:17:24 - INFO - Start Reading property
20/017/2012 16:17:24 - INFO - Reading TA finished.
20/017/2012 16:17:24 - INFO - Ending flash session
20/017/2012 16:17:24 - INFO - Found semcSL
20/017/2012 16:17:24 - INFO - You can now unplug and turn on device, then plug it again
20/017/2012 16:17:24 - INFO - Waiting for device
20/019/2012 16:19:39 - INFO - Device connected with USB debugging on
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\qsd8250bootwrite_semcSL to /data/local/tmp
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\mapper_2.6.29-00054-g5f01537.ko to /data/local/tmp
20/019/2012 16:19:40 - INFO - Pushing C:\Program Files\Flashtools 0.8.6\Flashtool\custom\features\UnlockBL\files\qsd8250\fixPart to /data/local/tmp
20/019/2012 16:19:40 - INFO - Running runfixPart as root thru sysrun
20/019/2012 16:19:41 - INFO - Successfully applied fixPart. Rebooting
20/019/2012 16:19:41 - INFO - Waiting for device
20/019/2012 16:19:42 - INFO - Device disconnected
20/019/2012 16:19:53 - INFO - Device connected with USB debugging off
20/019/2012 16:19:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/019/2012 16:19:57 - INFO - Device connected with USB debugging on
20/020/2012 16:20:10 - INFO - Running runbootwrite as root thru sysrun
20/020/2012 16:20:11 - INFO - Successfully applied unlock. Rebooting
20/020/2012 16:20:11 - INFO - Running runClean as root thru sysrun
20/020/2012 16:20:13 - INFO - Device disconnected
20/020/2012 16:20:24 - INFO - Device connected with USB debugging off
20/020/2012 16:20:24 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/020/2012 16:20:33 - INFO - Device disconnected
20/020/2012 16:20:36 - INFO - Device connected with USB debugging on
20/020/2012 16:20:36 - INFO - Connected device : X10
20/020/2012 16:20:36 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
20/020/2012 16:20:36 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
20/020/2012 16:20:48 - INFO - Root Access Allowed
20/023/2012 16:23:12 - INFO - Device disconnected
20/024/2012 16:24:10 - INFO - Log written to C:\Program Files\Flashtools 0.8.6\Flashtool\flashtool_2012-12-19_04-10-47.log
Don't 'freak out' when you see "Bootloader status : UNROOTABLE" scroll across the screen. My heart sunk when I saw that, but I let the first phase of the process complete and then connect the phone to the USB cable after the phone had re-booted with Flashtool 0.8.6 (in my case) still running and the process completed. In my case I got my phone back unlocked and still rooted. All good.
I'm pretty sure my bootloader was not locked when I started out a year or so ago, but I can't be absolutely sure; so somehow it's seems to have become locked during that time. Maybe because I was just recovering the same build each time I never installed anything else to check.
Like the OP, I originally rooted my phone by using 0.2.9.1 GB-ready using a convoluted process compared to todays one click root process.
Now when I flash a ftf file in Flashtool it runs through without any errors.
I was then able to go on and install [CM10] v4 (Torch) by: scritch007 without any problems.
Hope some of this information can help others.
My downloaded Flashtool has a virus. So I use the 0.9.0.0 version and it works ok.
I had the same issue too with v 0.9.9.0. for rooting I use v 0.6.8.0
Code:
02/018/2013 18:18:35 - INFO - <- This level is successfully initialized
02/018/2013 18:18:35 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
02/018/2013 18:18:35 - INFO - You can drag and drop ftf files here to start flashing them
02/018/2013 18:18:42 - INFO - Device connected with USB debugging on
02/018/2013 18:18:43 - INFO - Connected device : ST25
02/018/2013 18:18:43 - INFO - Installed version of busybox : N/A
02/018/2013 18:18:43 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
02/018/2013 18:18:50 - INFO - Pushing C:\Flashtool\.\devices\ST25\busybox\1.20.2\busybox to /data/local/tmp/busybox
02/018/2013 18:18:51 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
02/018/2013 18:18:51 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
02/018/2013 18:18:53 - INFO - Pushing C:\Flashtool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
02/018/2013 18:18:55 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
02/018/2013 18:18:55 - INFO - You have 60 seconds to follow the restore advice
02/018/2013 18:18:56 - INFO - Running adbrestoreexploit
02/018/2013 18:18:57 - INFO - Restore worked fine. Rebooting device. Please wait ...
02/019/2013 18:19:09 - INFO - Waiting for device
02/019/2013 18:19:10 - INFO - Device disconnected
02/019/2013 18:19:37 - INFO - Device connected with USB debugging on
02/019/2013 18:19:39 - INFO - Root hack did not work.
02/019/2013 18:19:39 - INFO - Cleaning hack files
02/019/2013 18:19:39 - INFO - Rebooting device. Please wait.
02/019/2013 18:19:43 - INFO - Device disconnected
02/020/2013 18:20:09 - INFO - Device connected with USB debugging on
02/020/2013 18:20:10 - INFO - Connected device : ST25
02/020/2013 18:20:10 - INFO - Installed version of busybox : N/A
02/020/2013 18:20:10 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
When I run the flash tool, Installing superuser does not work. Is there anything I can do?
Odp: [Q] Xperia U -"Root hack did not work"
http://forum.xda-developers.com/showthread.php?p=35015745
Post number 36 for me it worked i had same problem until i found that
And after flashing b.1.10 kernel u will have hard to see fonts , icons
Wysyłane z mojego ST25i za pomocą Tapatalk 2
First you need to flash the b.10 kernel and then root and then back to b.54 kernel
or just go here lot better firmware
http://forum.xda-developers.com/showpost.php?p=35339192&postcount=173
Hi There,
I'm just new here, and I try to change my Xperia U to JB, but still not have a stable version (i guess), I will use a clean ICS FW.
First I want to root the phone, but right now I have the same problem has RedMist.
I think I can't follow the method by Case87 because my XU is Branded. Am I right?
greats.
Hi,
I am new to Android operating systems, this is the first time i have ever had one. Always had iphones but i must say im impressed.
However i decided to unlock my bootloader which i have done, and root my device to remove the google apps them ram down the users throat and maybe try some custom roms.
The current issue i have is i tried flashtool to root my device and says no root exploit available, however is this the case for my phone or is it the app hasnt been updated?
Flashtool ver 0.9.10.1
Android Version 4.1.2
Build 9.1.A.1.140
LT30P
If this is the case is there anyway around the issue or am i stuck?
Again im new to android rooting and just trying to follow guides ive found but none have worked so far
Thanks in advance guys!
Any help at all?
Bump**
Bump**
26/032/2013 10:32:46 - INFO - <- This level is successfully initialized
26/032/2013 10:32:46 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
26/032/2013 10:32:46 - INFO - You can drag and drop ftf files here to start flashing them
26/032/2013 10:32:51 - INFO - Device connected with USB debugging on
26/032/2013 10:32:52 - INFO - Connected device : LT30
26/032/2013 10:32:52 - INFO - Installed version of busybox : N/A
26/032/2013 10:32:52 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00811-g8c0b35e / Build number : 9.1.A.1.140
26/034/2013 10:34:42 - INFO - Device disconnected
26/034/2013 10:34:44 - INFO - Device connected with USB debugging on
26/034/2013 10:34:44 - INFO - Connected device : LT30
26/034/2013 10:34:44 - INFO - Installed version of busybox : N/A
26/034/2013 10:34:44 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00811-g8c0b35e / Build number : 9.1.A.1.140
26/043/2013 10:43:03 - INFO - Flash canceled