First android. Also first post so I can't use the proper thread...
My android is rooted and sim-unlocked by Omnius.
I manually installed ClockworkMod Recovery. (to do this I had to remount the /system folder as rw, don't know if this is important, but wasn't in the installation instructions).
PC companion says my firmware is the lastest
I want flash this kernel.
I think I can't unlock my bootloader...
I followed this guide to unlock the bootloader, using FlashTool or msm7227_omniusSL.cmd.
Both processes complete without errors... But when I check with s1tool, the erom version has an uppercase "R".
When I try to flash, FlashTool throws the error:
Code:
06/056/2012 20:56:22 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Here are my s1tool and FlashTool logs:
s1tool:
Code:
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E10a
SOFTWARE VERSION: 1235-3408_2.0.A.0.504
CUSTOM VERSION: 1237-0397_R8B
FILESYSTEM VERSION: WORLD-1-2-5_2.0.A.0.504
SERIAL NO: CB511QQTMH
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:6 secs.
Flashtool - unlocking BL log
Code:
06/044/2012 20:44:25 - INFO - Device connected in flash mode
06/047/2012 20:47:23 - INFO - Device disconnected
06/048/2012 20:48:01 - INFO - Device connected with USB debugging on
06/048/2012 20:48:02 - INFO - Connected device : E10
06/048/2012 20:48:03 - INFO - Installed version of busybox : BusyBox v1.19.3-Stericson (2011-12-20 21:07:32 CST) multi-call binary.
06/048/2012 20:48:03 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
06/048/2012 20:48:06 - INFO - Root Access Allowed
06/048/2012 20:48:19 - INFO - Remounting system read-write
06/048/2012 20:48:21 - INFO - Pulling system/build.prop to C:\Flashtool\custom\features\Optimize\files\E10\build.prop.orig
06/049/2012 20:49:04 - INFO - Please connect your device into flashmode.
06/049/2012 20:49:32 - INFO - Please connect your device into flashmode.
06/049/2012 20:49:35 - INFO - Device disconnected
06/049/2012 20:49:46 - INFO - Device connected in flash mode
06/049/2012 20:49:46 - INFO - Opening device for R/W
06/049/2012 20:49:46 - INFO - Reading device information
06/049/2012 20:49:46 - INFO - Phone reading for flashing.
06/049/2012 20:49:46 - INFO - Start Reading property
06/049/2012 20:49:46 - INFO - Reading property finished.
06/049/2012 20:49:46 - INFO - Found omniusSL
06/049/2012 20:49:46 - INFO - You can now unplug and turn on device, then plug it again
06/049/2012 20:49:46 - INFO - Waiting for device
06/049/2012 20:49:47 - INFO - Device connected in flash mode
06/050/2012 20:50:12 - INFO - Device disconnected
06/051/2012 20:51:18 - INFO - Device connected with USB debugging on
06/051/2012 20:51:20 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\my7227bootwrite_omniusSL to /data/local/tmp
06/051/2012 20:51:21 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\mapper_2.6.29.ko to /data/local/tmp
06/051/2012 20:51:21 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\my7227\fixPart to /data/local/tmp
06/051/2012 20:51:21 - INFO - Running runfixPart as root thru sysrun
06/051/2012 20:51:21 - INFO - Successfully applied fixPart. Rebooting
06/051/2012 20:51:22 - INFO - Waiting for device
06/051/2012 20:51:23 - INFO - Device disconnected
06/051/2012 20:51:40 - INFO - Device connected with USB debugging off
06/051/2012 20:51:40 - INFO - For 2011 devices line, be sure you are not in MTP mode
06/051/2012 20:51:42 - INFO - Device connected with USB debugging on
06/052/2012 20:52:08 - INFO - Running runbootwrite as root thru sysrun
06/052/2012 20:52:10 - INFO - Successfully applied unlock. Rebooting
06/052/2012 20:52:11 - INFO - Running runClean as root thru sysrun
06/052/2012 20:52:15 - INFO - Device disconnected
Flashtool - upgrading kernel log
Code:
06/056/2012 20:56:21 - INFO - Selected E10_nAa-10_2.6.29.6-nAa-10.ftf
06/056/2012 20:56:21 - INFO - Preparing files for flashing
06/056/2012 20:56:21 - INFO - Please connect your device into flashmode.
06/056/2012 20:56:21 - INFO - Opening device for R/W
06/056/2012 20:56:21 - INFO - Reading device information
06/056/2012 20:56:21 - INFO - Phone reading for flashing.
06/056/2012 20:56:22 - INFO - Start Flashing
06/056/2012 20:56:22 - INFO - Flashing loader
[COLOR="Red"]06/056/2012 20:56:22 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"[/COLOR]
Both BL unlocking methods were repeted several times, with equal logs...
Any help with this?
I am having the same problem too - if you find a solution i would like to hear from you - i am looking too and will post here if i finde something
I have u20 (the pro, but it seems like the same problem and maybe same solution)
I unlocked my Xperia Play using the SE website. Isn't that accessible for X10 users?
ridder215215 said:
I unlocked my Xperia Play using the SE website. Isn't that accessible for X10 users?
Click to expand...
Click to collapse
this site???: http://unlockbootloader.sonyericsson.com/instructions
same problem, coudn't install ICS on my X10. can someone help me?>
Hi folks, i have the xperia mini pro SK17 a and have the same problem with the exactly log that the first post of the tread. Waht is interesting is that the phone was enabled to unblock the bootloader with the use of S1 tool. But when i get the code from the site of SE and used the flashtool to complete the process.
When i tried to flash a kernel have the same error: ERR_SEVERITY="MAJOR"ERR_CLASS="SECURITY_CLASS"ERR_DYNAMIC="SIN header verification failed". All refers that this error is because of the block of bootloader, but how if all here have the used the process to unblock...??????????????????????????????????????
Anyone knows any solution? What roms can i install with the stock kernel?
No solutions yet? Having the same problem :/
Try using the flash tool for Xperia......
Sent from my Xperia U using xda app-developers app
Related
Hi everybody,
I tried to flash my SK17i using flashtool the way it is described here:
http://forum.xda-developers.com/showthread.php?t=1455216
http://forum.xda-developers.com/showthread.php?t=928343
But it didnt work.
2/030/2012 21:30:51 - INFO - Selected SK17i_4.0.2.A.0.58_kernel only.ftf
22/030/2012 21:30:51 - INFO - Preparing files for flashing
22/030/2012 21:30:51 - INFO - Please connect your device into flashmode.
22/031/2012 21:31:07 - INFO - Device connected in flash mode
22/031/2012 21:31:07 - INFO - Opening device for R/W
22/031/2012 21:31:07 - INFO - Reading device information
22/031/2012 21:31:07 - INFO - Phone reading for flashing.
22/031/2012 21:31:07 - INFO - Start Flashing
22/031/2012 21:31:07 - INFO - Flashing loader
22/031/2012 21:31:08 - INFO - Loader version : R4A069 / Bootloader status : ROOTABLE
22/031/2012 21:31:08 - INFO - Flashing kernel.sin
22/031/2012 21:31:11 - INFO - Flashing finished.
22/031/2012 21:31:11 - INFO - Please wait. Phone will reboot
22/031/2012 21:31:11 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
22/031/2012 21:31:11 - INFO - Device connected in flash mode
22/031/2012 21:31:13 - INFO - Device disconnected
22/031/2012 21:31:14 - INFO - Device connected in flash mode
22/031/2012 21:31:36 - DEBUG - (MyLogger.java:86) - <- This level is successfully initialized
22/031/2012 21:31:46 - INFO - <- This level is successfully initialized
22/031/2012 21:31:54 - INFO - Device disconnected
22/032/2012 21:32:11 - INFO - Device connected with USB debugging off
22/032/2012 21:32:11 - INFO - For 2011 devices line, be sure you are not in MTP mode
what do you mean?
i dont see any message to seems to be an error
actually, i just tried the same as you and also it didnt work on mine =(
and mine is a sk17a, maybe that is the reason? is yours really a sk17i?
my debug is on, so it should have worked.. =\
yes, i didnt see any error...
you're gona flash kernel only right?
Shall I it trie again with debug message activated.
The message I posted before contained the FlashTool Log.
My phone is still running FW 0.62.
I tried to flash multiple times, but after each time i was still running 0.62.
No Error message nothing. I tried to flash this file:
http://www.mediafire.com/?qnehf31lf5s1eai
found it in this thread:
http://forum.xda-developers.com/showthread.php?t=1455216
I did already post the FlashTool Log that appeared at the beginning of this thread.
Can some help me out?
Is it possible that my phone took damage from the procedure?
Less words - Device: Sony Ericcson x10 Mini Pro. I'm using: CM7Pro, stock kernel. -> i want pass to CM72.2.0 using nAa, kernel. I've got a wrong when i was trying install kernel. (see code)
Hi all and sry for my bad english, it should be much bad as i remember correct.
At this moment i've mount on my device CM7Pro using stock Kernel. I've installed CWM and by means of it, now i'm using CM7Pro. I want something use less battery, so i want change it. I've choice CM7 2.2.0.
But every time i try to flash nAa kernel i got this answer:
Code:
21/009/2012 04:09:08 - INFO - <- This level is successfully initialized
21/009/2012 04:09:08 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
21/009/2012 04:09:08 - INFO - You can drag and drop ftf files here to start flashing them
21/009/2012 04:09:13 - INFO - Device connected with USB debugging on
21/009/2012 04:09:14 - INFO - Connected device : U20
21/009/2012 04:09:14 - INFO - Installed version of busybox : BusyBox v1.19.1-cm71 bionic (2011-09-01 04:24 +0200) multi-call binary.
21/009/2012 04:09:14 - INFO - Android version : 2.3.7 / kernel version : 2.6.29
21/009/2012 04:09:14 - INFO - Root Access Allowed
21/009/2012 04:09:18 - INFO - Flash canceled
21/010/2012 04:10:33 - INFO - Selected X10_V1_BLRelock.ftf
21/010/2012 04:10:33 - INFO - Preparing files for flashing
21/010/2012 04:10:34 - INFO - Please connect your device into flashmode.
21/011/2012 04:11:07 - INFO - Device disconnected
21/011/2012 04:11:10 - INFO - Device connected in flash mode
21/011/2012 04:11:10 - INFO - Opening device for R/W
21/011/2012 04:11:10 - INFO - Reading device information
21/011/2012 04:11:10 - INFO - Phone ready for flashmode operations.
21/011/2012 04:11:10 - INFO - Start Flashing
21/011/2012 04:11:10 - INFO - Flashing loader
21/011/2012 04:11:10 - INFO - Ending flash session
21/011/2012 04:11:10 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
21/011/2012 04:11:10 - ERROR - Error flashing. Aborted
21/011/2012 04:11:10 - INFO - Device connected in flash mode
21/011/2012 04:11:23 - INFO - Device disconnected
21/015/2012 04:15:33 - INFO - Device connected with USB debugging on
21/015/2012 04:15:33 - INFO - Connected device : U20
21/015/2012 04:15:34 - INFO - Installed version of busybox : BusyBox v1.19.1-cm71 bionic (2011-09-01 04:24 +0200) multi-call binary.
21/015/2012 04:15:34 - INFO - Android version : 2.3.7 / kernel version : 2.6.29
21/015/2012 04:15:34 - INFO - Root Access Allowed
21/015/2012 04:15:51 - INFO - Device disconnected
21/016/2012 04:16:01 - INFO - Device connected with USB debugging off
21/016/2012 04:16:01 - INFO - For 2011 devices line, be sure you are not in MTP mode
21/016/2012 04:16:43 - INFO - Device disconnected
21/016/2012 04:16:49 - INFO - Device connected with USB debugging off
21/016/2012 04:16:49 - INFO - For 2011 devices line, be sure you are not in MTP mode
21/017/2012 04:17:09 - INFO - Device disconnected
21/017/2012 04:17:16 - INFO - Device connected with USB debugging on
21/017/2012 04:17:16 - INFO - Connected device : U20
21/017/2012 04:17:16 - INFO - Installed version of busybox : BusyBox v1.19.1-cm71 bionic (2011-09-01 04:24 +0200) multi-call binary.
21/017/2012 04:17:16 - INFO - Android version : 2.3.7 / kernel version : 2.6.29
21/017/2012 04:17:17 - INFO - Root Access Allowed
21/022/2012 04:22:06 - INFO - Selected X10_V1_BLRelock.ftf
21/022/2012 04:22:06 - INFO - Preparing files for flashing
21/022/2012 04:22:06 - INFO - Please connect your device into flashmode.
21/022/2012 04:22:12 - INFO - Device disconnected
21/022/2012 04:22:39 - INFO - Device connected in flash mode
21/022/2012 04:22:40 - INFO - Opening device for R/W
21/022/2012 04:22:40 - INFO - Reading device information
21/022/2012 04:22:40 - INFO - Phone ready for flashmode operations.
21/022/2012 04:22:40 - INFO - Start Flashing
21/022/2012 04:22:40 - INFO - Flashing loader
21/022/2012 04:22:40 - INFO - Ending flash session
21/022/2012 04:22:40 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
21/022/2012 04:22:40 - ERROR - Error flashing. Aborted
21/022/2012 04:22:40 - INFO - Device connected in flash mode
21/022/2012 04:22:41 - INFO - Device disconnected
21/022/2012 04:22:44 - INFO - Device connected in flash mode
I've read much times the guide of FlashTool but i've not found answers.
Please help me about that.
Thank you all, see you.
Do you have an open Bootloader?
Unlock your bootloader and install the kernel whit the last flash tool
Sent from my E10i using xda premium
You must unlock bootloader!
Go and pass to the link below. It's a link about unlocking your bootloader.
Link: http://forum.xda-developers.com/showthread.php?t=1254225&highlight=bootloader
Click the thanks button for me and SpyderX!
like every body said, Unlock your boot loader.
Do u have any applications installed in your computer that associate with the flash tools? for example, bluestack. If u have this, this will make your flash tools recognize the bluestack application that installed in the computer as a device that connected to the pc.
xurrec 1793
atm i'm using flashtool for unlock my bootloader and it say is unlocked. I'll try some other app for do that, ty all answers.
I'll write again if that's not solved.
It looks to me like youŕe trying to flash the bootloader-relock, and not nAa 11 kernel.
It says: Selected X10-V1-BLrelock.ftf
It should say something like: Selected; nAa-11_2.6.29.6-nAa.11.ftf.
If you can not select this kernel properly, go to the installation folder of flashtool, browse to firmwares, make a subfolder and put the other ftf files in there so you only have the nAa kernel ftf file left when you get to choose which file to flash.
Try to flash again
I hope this helps
[EDIT] You may have to unlock your bootloader again, if you've accidentally relocked the bootloader this way before [/EDIT]
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
Flashtools will not unlock the bootloader. The log is below.
20/037/2012 17:37:06 - INFO - <- This level is successfully initialized
20/037/2012 17:37:06 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-21 23:15:59
20/037/2012 17:37:06 - INFO - You can drag and drop ftf files here to start flashing them
20/037/2012 17:37:19 - INFO - Device connected with USB debugging off
20/037/2012 17:37:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
20/038/2012 17:38:01 - INFO - Device connected with USB debugging on
20/038/2012 17:38:02 - INFO - Connected device : X10
20/038/2012 17:38:02 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
20/038/2012 17:38:02 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537 / Build number : 3.0.1.G.0.75
20/038/2012 17:38:05 - INFO - Root Access Allowed
20/038/2012 17:38:16 - INFO - Please connect your device into flashmode.
20/038/2012 17:38:21 - INFO - Device disconnected
20/038/2012 17:38:42 - INFO - Device connected in flash mode
20/038/2012 17:38:42 - INFO - Opening device for R/W
20/038/2012 17:38:42 - INFO - Reading device information
20/038/2012 17:38:42 - INFO - Phone ready for flashmode operations.
20/038/2012 17:38:42 - INFO - Processing loader
20/038/2012 17:38:43 - INFO - Ending flash session
20/038/2012 17:38:43 - WARN - Cancelled
20/038/2012 17:38:43 - INFO - Device connected in flash mode
20/038/2012 17:38:45 - INFO - Device disconnected
20/038/2012 17:38:46 - INFO - Device connected in flash mode
Check if ur bootloader is unlockable. Use s1tool.. search for a guide abt bootloader unlocking..
Sent from my Xperia X10 using xda app-developers app
Make sure you installed your drivers from the drivers folder.
Sent from my X10i using xda app-developers app
AdX9170 said:
Check if ur bootloader is unlockable. Use s1tool.. search for a guide abt bootloader unlocking..
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
does X10 has the un-unlockable bootloader version?
honestly I'm lucky on order to I haven't look my X10 bootloader version before unlock it via flashtool, and it was success
Yes some seem to be permanently locked. As far as I remember if s1tool says semc simlock certificate then it can be unlocked. Dunno what its gotta do with bootloader lock.. I'm not a dev.. check out the guide on the flash tool thread..
Sent from my Xperia X10 using xda app-developers app
I'm currently on locked bootloader x10. Cause I've problems with unlocking. Now I want to upgrade to ICS/JB. Is it possible to do with locked bootloader?
Sent from my X10S using xda app-developers app
No ICS/JB request UBL but is easy to unlock it
I'd trying to unlock. But I've lost phone signal and have relock it again. And when try to unlock using flash tool it abort the process.
Sent from my X10S using xda app-developers app
Do you try with doomlord method?
aimarstaru said:
Do you try with doomlord method?
Click to expand...
Click to collapse
His method? Which method?
Sent from my X10S using xda app-developers app
epulrevo said:
His method? Which method?
Sent from my X10S using xda app-developers app
Click to expand...
Click to collapse
Is your phone rooted
Sent from my Xperia X10 using xda app-developers app
here is the doomlord method
Extract -> RUN ME -> and folow the intructions
good luck
EzzyLupe said:
Is your phone rooted
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I've rooted my phone.
Sent from my X10S using xda app-developers app
aimarstaru said:
here is the doomlord method
Extract -> RUN ME -> and folow the intructions
good luck
Click to expand...
Click to collapse
It's for rooted or unlock? Because I've rooted my phone.
Sent from my X10S using xda app-developers app
epulrevo said:
It's for rooted or unlock? Because I've rooted my phone.
Sent from my X10S using xda app-developers app
Click to expand...
Click to collapse
if you flashtool 0.9.x.x you csn unlock your bootlooder with it
Send by Xperia X10i
EzzyLupe said:
if you flashtool 0.9.x.x you csn unlock your bootlooder with it
Send by Xperia X10i
Click to expand...
Click to collapse
Yeah, I have the latest flash tool. But unlocking process aborted when I trying to unlock.
Sent from my X10S using xda app-developers app
ICS/JB on x10i
Well I have a rooted,unlocked x10i. Every time I try to install a custom ROM I get a Sony logo after every reboot. I wait for >15mins for no good. I reset it again using SEUS and have been going in a cycle from the past two days. Can someone help me. I have tried Feralab's ROM(http://forum.xda-developers.com/showpost.php?p=25331067&postcount=2452) with Ferakernel and also MM team CM 7.2(http://forum.xda-developers.com/showthread.php?t=1609399) with their kernel, everything installs fine without an error, so I guess I am making some very basic nooby mistake here.Totally frustrated, any help is appreciated.
epulrevo said:
Yeah, I have the latest flash tool. But unlocking process aborted when I trying to unlock.
Sent from my X10S using xda app-developers app
Click to expand...
Click to collapse
Show me the error ?!!
Send by Xperia X10i
EzzyLupe said:
Show me the error ?!!
Send by Xperia X10i
Click to expand...
Click to collapse
After i connect switched off phone with back button pressed, the flashtool do its job, no log just the % bar below is loading something and stop after reach 100%. Just like that. And I check with s1tools l, its still locked. No log, no error to show u.
Sent from my X10S using xda app-developers app
epulrevo said:
After i connect switched off phone with back button pressed, the flashtool do its job, no log just the % bar below is loading something and stop after reach 100%. Just like that. And I check with s1tools l, its still locked. No log, no error to show u.
Sent from my X10S using xda app-developers app
Click to expand...
Click to collapse
Does S1 Tool look like the following with an uppercase 'R' in R4A024 on the line LOADER VERSION: "R4A024"
If the the 'r' is lower case the bootloader is unlocked.
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: CB53KEEPUMUM
SEMC SIMLOCK CERTIFICATE
Elapsed:55 secs.
When using FlashTool to unlock the boot loader you should see something like the following logged output as it unlocks the boot loader.
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
The line highlighted in red in my example of Flashtool unlocking the boot loader scared me, but unlocked the bootloader anyway.
Tutorial: Rooting, Bootloader unlocking & updating
Dr Goodvibes said:
Does S1 Tool look like the following with an uppercase 'R' in R4A024 on the line LOADER VERSION: "R4A024"
If the the 'r' is lower case the bootloader is unlocked.
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: CB53KEEPUMUM
SEMC SIMLOCK CERTIFICATE
Elapsed:55 secs.
When using FlashTool to unlock the boot loader you should see something like the following logged output as it unlocks the boot loader.
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
The line highlighted in red in my example of Flashtool unlocking the boot loader scared me, but unlocked the bootloader anyway.
Tutorial: Rooting, Bootloader unlocking & updating
Click to expand...
Click to collapse
Hmm, yeahh. I've check it using s1tools I got a big R. -_-"
Sent from my X10S using xda app-developers app