Hi,
I'm new to this forum and want to say that I have searched my issue/tried a bunch of things that don't seem to work, and I can't find a thread where someone had the exact same issue.
I finally got around to rooting my phone (it is unlocked as well), because I decided it's worth giving this phone a refresh before buying something else. Really I might have but I just don't find that any of the newer "compact" phones are really even small anymore so might as well stick with my trusty Xperia if I can free up some internal memory/try a new ROM etc etc.
I'll give my device/info here first, then explain my issue. Really hoping it's just something stupid/simple that I am missing and that someone may be able to help
My Device:
Sony Ericsson Xperia Ray ST18a
Details as per Flashtool64 when I connect it now:
06/056/2016 16:56:21 - INFO - Starting phone detection
06/056/2016 16:56:26 - INFO - Device connected with USB debugging on
06/056/2016 16:56:27 - INFO - Connected device : SonyEricson Xperia Ray
06/056/2016 16:56:27 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
06/056/2016 16:56:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.431
06/056/2016 16:56:27 - INFO - Checking root access
06/056/2016 16:56:29 - INFO - Root Access Allowed
Details from Service Menu (launched using Flashtool64):
Phone Software Version:
1248-9545_4.1.B.0.587
File System Version:
TELUS_4.1.B.0.431
S1 Boot Version:
1241-3566 r9A021
ETS Software Version:
1247-1301_7
Customization Version:
1252-5788_R1l
Active Customization:
1252-5788_R1l
Memory Card:
No file found
Content Version :
PA5
Type Number:
AAD-3880118-BV
Touch Firmware Version:
7
Fuel Guage Firmware Version:
0x0507 0x0507 0x01121
(I rooted my phone the other day using the following tools:
Android-Root_v1_Xperia-2012-ICS-ROOT-emu-busybox-su, which gave me the runme.bat etc, and Flashtool64 to flash the kernels ST18i_4.0.4_4.1.A.0.562_kernel.ftf and ST18i_4.0.4_4.1.B.0.587_T.ftf
Took awhile to sort that all out, but got it done and installed root checker which verified it was installed properly on my device.
I have since installed and used the App "Uninstall" which worked fine showing I now have Root Access as I could remove some unwanted bloatware to free up a little space)
Anyway.. here is the problem:
I can't seem to run recovery mode (which, from what I gather, I need to run before loading customs ROMs). I Have downloaded both TWRP and CWM from the Play store, but found they don't list support for Xperia Ray... Then I found through searching here that X-Parts should do the trick for my phone.. So I've downloaded that fine, it says that it installed CWM, but when I try to use the tool "Reboot to Recovery" my phone just reboots normally... I've also tried rebooting while combinations of tapping and/or holding the volume down key as I've read to do. Still nothing.
Any help at this point would be greatly appreciated!!!
This site seems great, and love the idea of being able to customize everything and have community support! (ie not a fan of iAnything..lol)
Thanks!
Ryan
3kgtang said:
Hi,
I'm new to this forum and want to say that I have searched my issue/tried a bunch of things that don't seem to work, and I can't find a thread where someone had the exact same issue.
I finally got around to rooting my phone (it is unlocked as well), because I decided it's worth giving this phone a refresh before buying something else. Really I might have but I just don't find that any of the newer "compact" phones are really even small anymore so might as well stick with my trusty Xperia if I can free up some internal memory/try a new ROM etc etc.
I'll give my device/info here first, then explain my issue. Really hoping it's just something stupid/simple that I am missing and that someone may be able to help
My Device:
Sony Ericsson Xperia Ray ST18a
Details as per Flashtool64 when I connect it now:
06/056/2016 16:56:21 - INFO - Starting phone detection
06/056/2016 16:56:26 - INFO - Device connected with USB debugging on
06/056/2016 16:56:27 - INFO - Connected device : SonyEricson Xperia Ray
06/056/2016 16:56:27 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
06/056/2016 16:56:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.431
06/056/2016 16:56:27 - INFO - Checking root access
06/056/2016 16:56:29 - INFO - Root Access Allowed
Details from Service Menu (launched using Flashtool64):
Phone Software Version:
1248-9545_4.1.B.0.587
File System Version:
TELUS_4.1.B.0.431
S1 Boot Version:
1241-3566 r9A021
ETS Software Version:
1247-1301_7
Customization Version:
1252-5788_R1l
Active Customization:
1252-5788_R1l
Memory Card:
No file found
Content Version :
PA5
Type Number:
AAD-3880118-BV
Touch Firmware Version:
7
Fuel Guage Firmware Version:
0x0507 0x0507 0x01121
(I rooted my phone the other day using the following tools:
Android-Root_v1_Xperia-2012-ICS-ROOT-emu-busybox-su, which gave me the runme.bat etc, and Flashtool64 to flash the kernels ST18i_4.0.4_4.1.A.0.562_kernel.ftf and ST18i_4.0.4_4.1.B.0.587_T.ftf
Took awhile to sort that all out, but got it done and installed root checker which verified it was installed properly on my device.
I have since installed and used the App "Uninstall" which worked fine showing I now have Root Access as I could remove some unwanted bloatware to free up a little space)
Anyway.. here is the problem:
I can't seem to run recovery mode (which, from what I gather, I need to run before loading customs ROMs). I Have downloaded both TWRP and CWM from the Play store, but found they don't list support for Xperia Ray... Then I found through searching here that X-Parts should do the trick for my phone.. So I've downloaded that fine, it says that it installed CWM, but when I try to use the tool "Reboot to Recovery" my phone just reboots normally... I've also tried rebooting while combinations of tapping and/or holding the volume down key as I've read to do. Still nothing.
Any help at this point would be greatly appreciated!!!
This site seems great, and love the idea of being able to customize everything and have community support! (ie not a fan of iAnything..lol)
Thanks!
Ryan
Click to expand...
Click to collapse
Hello,
Do you have an unlocked bootloader? If yes, you may flash a custom kernel based on your current firmware. The custom kernels have built in CWM so you can flash the kernel and can directly enter recovery with help of combination of volume down and power key.
-Vatsal
Vatsal said:
Hello,
Do you have an unlocked bootloader? If yes, you may flash a custom kernel based on your current firmware. The custom kernels have built in CWM so you can flash the kernel and can directly enter recovery with help of combination of volume down and power key.
-Vatsal
Click to expand...
Click to collapse
Thanks for the reply!
I guess it isn't and maybe that's where I'm stuck?
I tried the "Bootloader Unlock" feature (from the Flashtool64)
06/042/2016 22:42:21 - INFO - Device connected with USB debugging on
06/042/2016 22:42:21 - INFO - Connected device : SonyEricson Xperia Ray
06/042/2016 22:42:21 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
06/042/2016 22:42:21 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.431
06/042/2016 22:42:21 - INFO - Checking root access
06/042/2016 22:42:23 - INFO - Root Access Allowed
06/042/2016 22:42:58 - INFO - Launching Service Menu. Plese check on your phone.
06/044/2016 22:44:24 - INFO - Please connect your device into flashmode.
06/044/2016 22:44:33 - INFO - Device disconnected
06/045/2016 22:45:17 - INFO - Device connected in flash mode
06/045/2016 22:45:18 - INFO - Opening device for R/W
06/045/2016 22:45:18 - INFO - Reading device information
06/045/2016 22:45:18 - INFO - Phone ready for flashmode operations.
06/045/2016 22:45:18 - INFO - Opening TA partition 2
06/045/2016 22:45:18 - INFO - Current device : ST18a - CB511VDUWL - 1252-5788_R1I - 1248-9545_4.1.B.0.587 - TELUS_4.1.B.0.431
06/045/2016 22:45:18 - INFO - Closing TA partition
06/045/2016 22:45:18 - INFO - Loading devices database
06/045/2016 22:45:18 - INFO - Loaded 86 devices
06/045/2016 22:45:18 - INFO - Using an unofficial loader
06/045/2016 22:45:55 - INFO - Processing loader.sin
06/045/2016 22:45:55 - INFO - Checking header
06/045/2016 22:45:55 - INFO - Flashing data
06/045/2016 22:45:59 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Boot version : r9A021 / Bootloader status : ROOTED
06/045/2016 22:45:59 - INFO - Max packet size set to 65536K
06/045/2016 22:45:59 - INFO - USB buffer size set to 65536K
06/045/2016 22:45:59 - INFO - Opening TA partition 2
06/045/2016 22:45:59 - INFO - Start Reading unit 00 00 08 B2
06/045/2016 22:45:59 - INFO - Reading TA finished.
06/045/2016 22:45:59 - INFO - Closing TA partition
06/045/2016 22:45:59 - INFO - Ending flash session
06/045/2016 22:45:59 - INFO - Your phone bootloader cannot be officially unlocked
06/045/2016 22:45:59 - INFO - You can now unplug and restart your phone
06/045/2016 22:45:59 - INFO - Device connected in flash mode
06/046/2016 22:46:00 - INFO - Device disconnected
When I check the Rooting Status from Service Menu (launched using Flashtool64) though I find this:
Bootloader unlock allowed: Yes
Any ideas?
Really appreciate it
Ryan
3kgtang said:
Thanks for the reply!
I guess it isn't and maybe that's where I'm stuck?
I tried the "Bootloader Unlock" feature (from the Flashtool64)
06/042/2016 22:42:21 - INFO - Device connected with USB debugging on
06/042/2016 22:42:21 - INFO - Connected device : SonyEricson Xperia Ray
06/042/2016 22:42:21 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
06/042/2016 22:42:21 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf / Build number : 4.1.B.0.431
06/042/2016 22:42:21 - INFO - Checking root access
06/042/2016 22:42:23 - INFO - Root Access Allowed
06/042/2016 22:42:58 - INFO - Launching Service Menu. Plese check on your phone.
06/044/2016 22:44:24 - INFO - Please connect your device into flashmode.
06/044/2016 22:44:33 - INFO - Device disconnected
06/045/2016 22:45:17 - INFO - Device connected in flash mode
06/045/2016 22:45:18 - INFO - Opening device for R/W
06/045/2016 22:45:18 - INFO - Reading device information
06/045/2016 22:45:18 - INFO - Phone ready for flashmode operations.
06/045/2016 22:45:18 - INFO - Opening TA partition 2
06/045/2016 22:45:18 - INFO - Current device : ST18a - CB511VDUWL - 1252-5788_R1I - 1248-9545_4.1.B.0.587 - TELUS_4.1.B.0.431
06/045/2016 22:45:18 - INFO - Closing TA partition
06/045/2016 22:45:18 - INFO - Loading devices database
06/045/2016 22:45:18 - INFO - Loaded 86 devices
06/045/2016 22:45:18 - INFO - Using an unofficial loader
06/045/2016 22:45:55 - INFO - Processing loader.sin
06/045/2016 22:45:55 - INFO - Checking header
06/045/2016 22:45:55 - INFO - Flashing data
06/045/2016 22:45:59 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Boot version : r9A021 / Bootloader status : ROOTED
06/045/2016 22:45:59 - INFO - Max packet size set to 65536K
06/045/2016 22:45:59 - INFO - USB buffer size set to 65536K
06/045/2016 22:45:59 - INFO - Opening TA partition 2
06/045/2016 22:45:59 - INFO - Start Reading unit 00 00 08 B2
06/045/2016 22:45:59 - INFO - Reading TA finished.
06/045/2016 22:45:59 - INFO - Closing TA partition
06/045/2016 22:45:59 - INFO - Ending flash session
06/045/2016 22:45:59 - INFO - Your phone bootloader cannot be officially unlocked
06/045/2016 22:45:59 - INFO - You can now unplug and restart your phone
06/045/2016 22:45:59 - INFO - Device connected in flash mode
06/046/2016 22:46:00 - INFO - Device disconnected
When I check the Rooting Status from Service Menu (launched using Flashtool64) though I find this:
Bootloader unlock allowed: Yes
Any ideas?
Really appreciate it
Ryan
Click to expand...
Click to collapse
Hello,
I guess root allowed : yes states that your bootloader is unlocked.
You may try flashing a custom kernel via fastboot.
-Vatsal
Vatsal said:
Hello,
I guess root allowed : yes states that your bootloader is unlocked.
You may try flashing a custom kernel via fastboot.
-Vatsal
Click to expand...
Click to collapse
I thought because of this line:
"06/045/2016 22:45:59 - INFO - Your phone bootloader cannot be officially unlocked", that my bootloader is NOT unlocked... but since Rooting Status from Service Menu says: "Bootloader unlock allowed: Yes:" it's only telling me I'm ABLE to unlock it some other way>?
that was throwing me off.. but I'll try and see if I can flash a custom kernel (think so since I had to flash kernels to root the phone...).
Is there any particular kernel you would recommend? at least just to make sure I have a CWM that works so I can then load whichever ROM I'd like after?
Thanks again,
Ryan
3kgtang said:
I thought because of this line:
"06/045/2016 22:45:59 - INFO - Your phone bootloader cannot be officially unlocked", that my bootloader is NOT unlocked... but since Rooting Status from Service Menu says: "Bootloader unlock allowed: Yes:" it's only telling me I'm ABLE to unlock it some other way>?
that was throwing me off.. but I'll try and see if I can flash a custom kernel (think so since I had to flash kernels to root the phone...).
Is there any particular kernel you would recommend? at least just to make sure I have a CWM that works so I can then load whichever ROM I'd like after?
Thanks again,
Ryan
Click to expand...
Click to collapse
I've read this this thread on flashing custom kernels and ROMS, and I've tried the X-parts way etc but like I said it won't run CWM when I reboot so am stuck from there... unless my phone bootloader actually IS unlocked already?? then I just try the first method with the fastboot procedure... I just haven't tried that yet since I;ve seen warnigns NOT to do that if you;re not sure that your phone bootloader is unlocked.
http://forum.xda-developers.com/showthread.php?p=31381594#post31381594
Sorry just not sure what I'm missing here!
3kgtang said:
I've read this this thread on flashing custom kernels and ROMS, and I've tried the X-parts way etc but like I said it won't run CWM when I reboot so am stuck from there... unless my phone bootloader actually IS unlocked already?? then I just try the first method with the fastboot procedure... I just haven't tried that yet since I;ve seen warnigns NOT to do that if you;re not sure that your phone bootloader is unlocked.
http://forum.xda-developers.com/showthread.php?p=31381594#post31381594
Sorry just not sure what I'm missing here!
Click to expand...
Click to collapse
Hello,
Your bootloader seems already unlocked.
You just need to fastboot a kernel based on your current firmware.
The kernel has inbuilt CWM so you don't need x-parts for your recovery.
-Vatsal
Vatsal said:
Hello,
Your bootloader seems already unlocked.
You just need to fastboot a kernel based on your current firmware.
The kernel has inbuilt CWM so you don't need x-parts for your recovery.
-Vatsal
Click to expand...
Click to collapse
This is what I get:
08/002/2016 18:02:01 - INFO - Loaded 86 devices
08/002/2016 18:02:01 - INFO - Starting phone detection
08/002/2016 18:02:06 - ERROR - Drivers need to be installed for connected device.
08/002/2016 18:02:06 - ERROR - You can find them in the drivers folder of Flashtool.
I've tried to update the drivers from:
C:\Flashtool\drivers
but it keeps saying install failed... any ideas?
I read: http://forum.xda-developers.com/showthread.php?t=1578577
do I need to download/install Android SDK now first??
3kgtang said:
This is what I get:
08/002/2016 18:02:01 - INFO - Loaded 86 devices
08/002/2016 18:02:01 - INFO - Starting phone detection
08/002/2016 18:02:06 - ERROR - Drivers need to be installed for connected device.
08/002/2016 18:02:06 - ERROR - You can find them in the drivers folder of Flashtool.
I've tried to update the drivers from:
C:\Flashtool\drivers
but it keeps saying install failed... any ideas?
I read: http://forum.xda-developers.com/showthread.php?t=1578577
do I need to download/install Android SDK now first??
Click to expand...
Click to collapse
I found the file: android_winusb.inf and opened it to try adding in lines for sony ericsson but I guess that's not the right file to change (it won't allow me to save any changes)
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_bd75d06c56998078C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_bd75d06c56998078
FOUND A WORKING SOLUTION
Thank you Vatsal for all of the replies up until this point
Fixed my main issue by following "milowke" 's post in the following thread!:
http://forum.xda-developers.com/showthread.php?t=1913245&page=3
and for anyone else that may read this that had similar issues I used the following thread as a good guide to the flashing process:
http://forum.xda-developers.com/showthread.php?p=31381594#post31381594
Still have to make sure evrything works from here on out... will update!
3kgtang said:
FOUND A WORKING SOLUTION
Thank you Vatsal for all of the replies up until this point
Fixed my main issue by following "milowke" 's post in the following thread!:
http://forum.xda-developers.com/showthread.php?t=1913245&page=3
and for anyone else that may read this that had similar issues I used the following thread as a good guide to the flashing process:
http://forum.xda-developers.com/showthread.php?p=31381594#post31381594
Still have to make sure evrything works from here on out... will update!
Click to expand...
Click to collapse
After a bit of playing around, I'm happy to say that everything worked! Installed Xperia Ultimate HD ROM and we're up and running
I got version 3.0.2 for some reason so I'll probably update it to the newest version but so far looks good! I'll check it out fully and give props for sure where it's due!
Cheers,
Ryan
Related
Well, here it goes... I have a qouple of questions that I would like straighten out before I proceed.
I just got hold of a unused unbranded X10i for hardly any money at all. I managed to root it with the instructions here on XDA and it went fine... really easy, acually. Now I want to move a bit further to se the potential of the X10.
Here´s my questions:
As I understand I have to unlock the bootloader to be able to flash other kernels. If I use the descriptions here on XDA will my current setup disapear? Will I have to flash another ROM as I unlock the bootloader? Or will the current ROM be intact and give me the oppertunity to flash another ROM at a later time?
Witch ROM is the most bugfree? I want it for day to day use and I want everything to work, including WIFI-teahering. It would be nice to have the camera fully working aswell, with all 8 megapixels usable...
How about MIUI? Any in Swedish with the criterias I want? And CM7? Is that bug free?
I would love your input...
Manneman, Sweden
U don't need to flash another ROM after u have unlocked bootloader. When u have a unlocked bootloader u can flash any ROM u want. If your on stock 2.3.3 & unlock ur bootloader u won't miss anything. About the stability of the ROMs.. Stock or stock based ROMs are the most stable ones.. MiUI or CM7 are never "totally" bug-free. All ROMs 'should' have the criterias u want
I love MIUI and Cyanogenmod, but in all honesty probably the best rom on x10 is Erick Wills Ewjet. It has stock camera fully working, great themes and options available. Right now even his 2.1 rom would beat many for reliability and function. Im using Oodies MIUI prime 9, its fantastic and so is his cm7 but theres many I havent tried so start reading the developement threads to see what fits your needs, be sure to have a good backup program from the market like titanium or ultimate backup.
Than you!
I used the latest Flashtool to unlock the bootloader... Everything seems to have gone allright... here´s my log:
2/013/2012 11:13:24 - INFO - <- This level is successfully initialized
22/013/2012 11:13:24 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-21 17:31:40
22/013/2012 11:13:24 - INFO - You can drag and drop ftf files here to start flashing them
22/013/2012 11:13:30 - INFO - Device disconnected
22/013/2012 11:13:46 - INFO - Device connected with USB debugging on
22/013/2012 11:13:46 - INFO - Connected device : X10
22/013/2012 11:13:46 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
22/013/2012 11:13:46 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
22/013/2012 11:13:47 - INFO - Root Access Allowed
22/013/2012 11:13:55 - INFO - Please connect your device into flashmode.
22/014/2012 11:14:00 - INFO - Device disconnected
22/014/2012 11:14:28 - INFO - Device connected in flash mode
22/014/2012 11:14:28 - INFO - Opening device for R/W
22/014/2012 11:14:28 - INFO - Reading device information
22/014/2012 11:14:28 - INFO - Phone reading for flashing.
22/014/2012 11:14:28 - INFO - Start Reading property
22/014/2012 11:14:28 - INFO - Reading property finished.
22/014/2012 11:14:28 - INFO - Found semcSL
22/014/2012 11:14:28 - INFO - You can now unplug and turn on device, then plug it again
22/014/2012 11:14:28 - INFO - Waiting for device
22/014/2012 11:14:28 - INFO - Device connected in flash mode
22/015/2012 11:15:16 - INFO - Device disconnected
22/015/2012 11:15:32 - INFO - Device connected with USB debugging off
22/015/2012 11:15:32 - INFO - For 2011 devices line, be sure you are not in MTP mode
22/015/2012 11:15:36 - INFO - Device connected with USB debugging on
22/015/2012 11:15:59 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\qsd8250bootwrite_semcSL to /data/local/tmp
22/016/2012 11:16:02 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\mapper_2.6.29-00054-g5f01537.ko to /data/local/tmp
22/016/2012 11:16:02 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\fixPart to /data/local/tmp
22/016/2012 11:16:02 - INFO - Running runfixPart as root thru sysrun
22/016/2012 11:16:04 - INFO - Successfully applied fixPart. Rebooting
22/016/2012 11:16:04 - INFO - Waiting for device
22/016/2012 11:16:05 - INFO - Device disconnected
22/016/2012 11:16:16 - INFO - Device connected with USB debugging off
22/016/2012 11:16:16 - INFO - For 2011 devices line, be sure you are not in MTP mode
22/016/2012 11:16:23 - INFO - Device connected with USB debugging on
22/016/2012 11:16:46 - INFO - Running runbootwrite as root thru sysrun
22/016/2012 11:16:48 - INFO - Successfully applied unlock. Rebooting
22/016/2012 11:16:48 - INFO - Running runClean as root thru sysrun
22/016/2012 11:16:50 - INFO - Device disconnected
22/017/2012 11:17:02 - INFO - Device connected with USB debugging off
22/017/2012 11:17:02 - INFO - For 2011 devices line, be sure you are not in MTP mode
22/017/2012 11:17:25 - INFO - Device disconnected
22/017/2012 11:17:27 - INFO - Device connected with USB debugging on
22/017/2012 11:17:27 - INFO - Connected device : X10
22/017/2012 11:17:27 - INFO - Installed version of busybox : BusyBox v1.18.4 (2011-04-04 18:40:20 CDT) multi-call binary.
22/017/2012 11:17:27 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
22/017/2012 11:17:49 - INFO - Root Access Allowed
Am I really unlocked?
Thanx for the input!
hi..what you just did is only the rooting part..next would be ask permission for xrecovery..to unlock bootloader, follow this tread http://forum.xda-developers.com/showthread.php?t=1254087.. the simplest way to know if you are on the unlockBL (Bootloader)..when you turn on your X10..the 'Sony Ericsson' logo is forever gone...
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?
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
[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,
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