Hi,
I've been trying to flash my Xperia SP to 12.0.A.1.257 as per the thread "How-to for rooting newest firmware 12.0.A.2.245".
I currently have 12.0.A.2.254 installed, and I understand that I need to flash my kernel to 12.0.A.1.257 to be able to root. Flashing to 257 seems to be successful, please see the log below.
<- This level is successfully initialized
Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
Device connected with USB debugging on
Connected device : Sony Xperia SP
Installed version of busybox : N/A
Android version : 4.1.2 / kernel version : 3.4.0-perf-g1285c6c-01110-g8395f64 / Build number : 12.0.A.2.254
Selected XperiaSP_C530X / 12.0.A.1.257 / KernelOnly
Preparing files for flashing
Please connect your device into flashmode.
Device disconnected
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Current device : C5302 - CB5123ZDXT - 1272-1094_R8A - 1269-3538_12.0.A.1.257 - INDIA-HSPA_12.0.A.2.254
Start Flashing
Processing loader.sin
Checking header
Flashing data
Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTABLE
Processing kernel.sin
Checking header
Flashing data
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
Later when I use the Rooting toolkit v17 to get root access I get the following.
Device detected: C5302 (12.0.A.2.254)
C5302 (12.0.A.2.254) is not supported.
Am I missing something here?
Thanks in advance.
Unable to flash Kernel on Xperia SP
isvicbhasme said:
Hi,
I've been trying to flash my Xperia SP to 12.0.A.1.257 as per the thread "How-to for rooting newest firmware 12.0.A.2.245".
I currently have 12.0.A.2.254 installed, and I understand that I need to flash my kernel to 12.0.A.1.257 to be able to root. Flashing to 257 seems to be successful, please see the log below.
<- This level is successfully initialized
Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
Device connected with USB debugging on
Connected device : Sony Xperia SP
Installed version of busybox : N/A
Android version : 4.1.2 / kernel version : 3.4.0-perf-g1285c6c-01110-g8395f64 / Build number : 12.0.A.2.254
Selected XperiaSP_C530X / 12.0.A.1.257 / KernelOnly
Preparing files for flashing
Please connect your device into flashmode.
Device disconnected
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Current device : C5302 - CB5123ZDXT - 1272-1094_R8A - 1269-3538_12.0.A.1.257 - INDIA-HSPA_12.0.A.2.254
Start Flashing
Processing loader.sin
Checking header
Flashing data
Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTABLE
Processing kernel.sin
Checking header
Flashing data
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
Later when I use the Rooting toolkit v17 to get root access I get the following.
Device detected: C5302 (12.0.A.2.254)
C5302 (12.0.A.2.254) is not supported.
Am I missing something here?
Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my C5303
Related
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
this comes when flashing
20/044/2013 00:44:14 - INFO - <- This level is successfully initialized
20/044/2013 00:44:15 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
20/044/2013 00:44:15 - INFO - You can drag and drop ftf files here to start flashing them
20/044/2013 00:44:26 - INFO - Device connected with USB debugging on
20/044/2013 00:44:26 - INFO - Connected device : ST17
20/044/2013 00:44:27 - INFO - Installed version of busybox : BusyBox v1.20.2-cm9 bionic (2012-07-14 01:52 +0200) multi-call binary.
20/044/2013 00:44:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-FXP / Build number : IMM76L
20/044/2013 00:44:28 - INFO - Root Access Allowed
20/045/2013 00:45:19 - INFO - Selected WT19i_4.0.2.A.0.58_(1254-1868).ftf
20/045/2013 00:45:19 - INFO - Preparing files for flashing
20/045/2013 00:45:30 - INFO - Please connect your device into flashmode.
20/045/2013 00:45:35 - INFO - Device disconnected
20/046/2013 00:46:14 - INFO - Opening device for R/W
20/046/2013 00:46:15 - INFO - Device connected in flash mode
20/046/2013 00:46:15 - INFO - Start Flashing
20/046/2013 00:46:15 - INFO - Processing loader
20/046/2013 00:46:15 - INFO - Checking header
20/046/2013 00:46:15 - INFO - Ending flash session
20/046/2013 00:46:15 - ERROR -
20/046/2013 00:46:15 - ERROR - Error flashing. Aborted
20/046/2013 00:46:15 - INFO - Device connected in flash mode
Try checking "no final verification" before flashing. Should work
Siddharth121 said:
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
Click to expand...
Click to collapse
you have to tick your usb debugging... and then you must in MSC mode it can be on setting .
and dont connect your phone . you must flashing .ftf then after it wait until they say connect your HH with ~~~~.... after that in 10 seconds connect your usb and phone to pics/ laptop during press volume download
Sent from my WT19i using xda premium
hi,
I have pretty much the same symptoms, my ray is seen as ST17i by flashtool.
Is this a flashtool bug or is it really recognized as ST17i?
Thank you!
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Siddharth121 said:
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
nroberto13 said:
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
Click to expand...
Click to collapse
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Mysteryagr said:
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
yes, I saw the topic, but none of the fices worked for me .
I haven't found anybody on the forum who was successful on a ray with any of the fixes .
any advise?
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
tried that, also flashed system once again, then system and kernel, but phone doesn't boot.
what does cm9/10 different to stock so it boots?
is this issue coming from kernel or from rom?
where are the touch driver placed? in initrd or in rom?
thank you!
Please Help. Please.
I am having WT19i. I have installed Super Jelly Bean 8.0 and having nAa 2.6 kernel. I flashed this kernel through flashtool. That time my device was shown correctly (I guess that means all the drivers are installed correctly). And I havent changed anything on my PC (Windows 7) or in flashtool (0.9.13.0) after that. Now I want to install some KK Rom in my phone. So when I connected my LWW, it shows connected device as Xperia Active (ST17i) instead of WT19i. For that KK Rom, I need to flash .587 stock.ftf file. But I fear if I try to flash, it will brick my phone. I wont get a new mobile in near future. So I dont want to brick it. Anyone please help me through this. How can I get the job done without getting bricked. It will be a great if anyone could tell me.
If I continue with flashing ftf with the current situation (WT19i recognized as ST17i), will it brick my WT19i?? If yes, how to overcome this situation?? Help needed from members. Please, its urgent. I am a newbie actually. This is my first post in xda. Thanks in advance.
Hello,
I was trying to root my sola so to solve the wifi bug.
I found i need to flash it back from .54 to .10 using flashtool
Although, i am not being able to do it as I get a error message regarding drivers
What I do is I install flashtool on c:
I go to the drivers folder and execute Flashtool-drivers.exe and I install the Sola Drivers as well as the Flashboot and Fastboot drivers.
I open flashboot, select the .10 kernel, press flash, it tells me to turn off my sola and run it at flash mode (Volume down + USB) and then it gives me Drivers error message...
Can anyone help me?
08/041/2013 16:41:58 - INFO - <- This level is successfully initialized
08/041/2013 16:41:59 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
08/042/2013 16:42:05 - INFO - Device connected with USB debugging on
08/042/2013 16:42:07 - INFO - Connected device : Sony Xperia Sola
08/042/2013 16:42:07 - INFO - Installed version of busybox : N/A
08/042/2013 16:42:07 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
08/042/2013 16:42:13 - INFO - List of connected devices (Device Id) :
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_01\7&37E26950&0&0001 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_00\7&37E26950&0&0000 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173\BX9033RP3D Driver installed : true
08/042/2013 16:42:13 - INFO - List of ADB devices :
08/042/2013 16:42:13 - INFO - - BX9033RP3D
08/042/2013 16:42:13 - INFO - List of fastboot devices :
08/042/2013 16:42:13 - INFO - - none
This not flash mode, you device must be powered off to connect in flash mode.
ChikeD said:
This not flash mode, you device must be powered off to connect in flash mode.
Click to expand...
Click to collapse
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected
haloboyscp said:
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected
Click to expand...
Click to collapse
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?
ChikeD said:
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?
Click to expand...
Click to collapse
I already got that.
that was just because i was running on flashloader 64, i switched for normal flashloader and it ran.
I think now i have done the whole thing for rooting the phone, though... Using Es File Explorer, I go to root there and it's still nothing there.
When i flashed back from the .10 to .54 it was written 08/011/2013 19:11:27 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTABLE
so everything should have been ok?
:S
Thanks guys
Now I flash the phone, everything works.
I flash back to .10.
I try to root and get an error message like.
Could not restore. reconnect external memory and try again
I read it would be because the phone wasnt flashed on .10 but i do that...
What can it be?
Thanks
m trying to root my Xperia U but when I do that using Flashtool, it gives me an error. The log is below.
03/03/2014 08:30:02 - INFO - <- This level is successfully initialized
03/03/2014 08:30:03 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
03/03/2014 08:30:03 - INFO - Device connected with USB debugging on
03/03/2014 08:30:04 - INFO - Connected device : ST25
03/03/2014 08:30:05- INFO - Installed version of busybox : N/A
03/03/2014 08:30:07- INFO - Android version :4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.10
03/03/2014 08:30:10- INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/03/2014 08:30:15- INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\chattr : Not found
first i unlock boot loader of xperia u by using official method on sony website
then i try root xperia u by using flash tool and it give me above error
so plz help me to root my xperia u
and whan i select supersu mode then the process started normally
That's how the log ends?
U could 1st try this One
Good luck
[LB][JB] same problem
I just want to root my xperia P to remove some sony and google apps that I don't like,
but I've tried with a win8.1 and win7 pc and I have the same problem. Any solution?
Thanks in advance.
Superuser root package is broken, known bug
i follow guide by LoOpy!:
here his thread
LoOpy! said:
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE, or anything for that matter.
Tested 2x R800a. Please let me know if it doesn't work on your device!
THIS WILL WIPE YOUR DEVICE!
So you have a R800 that can't be unlocked officially i.e:
Code:
Bootloader unlock Status: [B]No[/B]
:crying:
What this means is that while we can get the device's bootloader unlocked(TP method), it will not enable fastboot access.
So we lack the ability to flash kernels, in .img formats...but why not just make a FTF packed kernel, which we can flash through flashmode?
I'm actually not sure to tell you the truth(*insert conspiracies*), but that was the solution this whole time...
Note: I have only made FTF versions of Turbo Kernel v3.1 by CosmicDan (R800x/R800a/i/at) I have vouch for the R800a to be working, others will need testing....(just have stock FTF ready to go:fingers-crossed
Requirements
Flashtool
GSM ONLY: Vendor-Unlocked Partition layout
Dev-Host link by fma965
Google Doc's link from [URL="forum.xda-developers.com/showthread.php?t=1817548"]CosmicDan Turbo Kernel [/URL]
Ability to use Flashtool... Read Flashing A FTF by fma965
Paperclip or pin + wire for Testpoint (if BL not unlocked)
S1tool for Testpoint (if BL not unlocked)
STEP 1: BL Unlock Via Test Point method (Locked BL Only)
If your bootloader is currently LOCKED:
Read TP Guide by DragonClawsAreSharp...If you don't feel comfortable doing this...stop reading.
If you are comfortable with unlocking the bootloader then go ahead and do it.
Here is R800 TP location(quick google search): Here, and with red dot...you can use a paperclip and hold it to the (-) battery terminal to achieve the same results as the TP cable the guide shows.
In Flashtool (if you ever noticed):
Code:
S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE ([I]lies[/I])
will now become:
Code:
S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED ([I]huehue[/I])
STEP 2: Prepare for Kernel
For GSM Only: Flash R800i_4.0.2.A.0.62_phoenixvendor.ftf with Flashtool. Let device fully boot to language selection page.
Read through Turbo Kernel (or what ever kernel.ftf you plan to use)
Grab a rom, look at the compatibility section on the kernel page.
Copy rom over to root directory of phone memory card.
Prepare your body?
STEP 3: Kernel Time + Rom
R800a/at/i Turbo Kernel 3.1 Download
R800x Turbo Kernel 3.1 Download
More Kernels!! Thanks denisfgn
Flash via Flashtool in flashmode.
Unplug usb....press and hold power button until 1 vibration....wait...wait...:victory:
Wait for the blue LED + vibration?, then press Volume Up. You should enter a sexy recovery...
Select: "Slot 1" > "TWRP Recovery" > "Wipe" > Wipe Cache, Dalvik Cache, System, then Factory Reset.
Go back to main page (hit back button), then select "Install", scroll down to the Rom you copied to the device, select and install it.
If you forgot rom: plug phone into computer, then in TWRP Select "Mount"> "Mount USB Storage" copy rom over to phone then install it
Reboot. Done.
This method should work for all Xperia 2011 devices that lack fastboot, but can be/are unlock via testpoint (anyone that can test let me know). Just need kernel to be in packed as a .ftf...
HAS THIS BEEN DONE BEFORE?? Maybe I can't search properly...
References
DragonClawsAreSharp for TP Guide
CosmicDan for Kernel
fma965 for FTF Guide
Flashtool Dev's
wedgess for Kernels
DooMLoRD for Kernel
Yay!! 1st post ever on XDA...
Click to expand...
Click to collapse
but I did these steps:
imauri1990 said:
I'm happy ! it succeeds in my xperia mini pro ( SK17 [ 12w19 ] Unlock Bootloader allowed : no) now have pacman 4.4.2
the steps were followed :
1.First , I unlocked my bootloader with testpoint .
2 . Then , I converted to boot.img That Loopy ftf with tools provided . tools: http://www.mediafire.com/download/u3ez1ud7sfcdcqd/img-to-ftf+%27Axel%27.rar
and a tutorial: https://www.youtube.com/watch?v=ykeRIEaqK8o
if u get error , remember when u install cygwin select "cpio" and "perl".
3 This is VERY IMPORTANT - I copied loader_unlocked.sin from Flashtool/devices/R800 to Flashtool/devices/SK17
4 . Kernel.ftf I flashed I made the
(Note you need to have copied from Flashtool/devices/R800 to Flashtool/devices/SK17 loader_unlocked.sin otherwise you will get the following error ! :
09/004/2013 18:04:12 - INFO - Selected Xperia MiniPro ( SK17i ) / 4.0.2.A.0.42 / HU
09/004/2013 18:04:12 - INFO - Preparing files for flashing
09/004/2013 18:04:15 - INFO - Please connect your device into Flashmode .
09/004/2013 18:04:17 - INFO - Device disconnected
09/004/2013 18:04:26 - INFO - Device connected in flash mode
09/004/2013 18:04:26 - INFO - Opening device for R / W
09/004/2013 18:04:26 - INFO - Reading device information
09/004/2013 18:04:26 - INFO - Phone Flashmode ready for operations .
09/004/2013 18:04:26 - INFO - Current device: SK17a - BX902SQQ7Q - 1250- 1736_R9D - 1244- 7088_4.0.2.A.0.58 - WORLD- a_4.0.2.A.0.58
09/004/2013 18:04:27 - INFO - Start Flashing
09/004/2013 18:04:27 - INFO - Using an unofficial loader
09/004/2013 18:04:27 - INFO - Device loader has not Been identified. Using the one from the bundle
09/004/2013 18:04:27 - INFO - Processing loader.sin
09/004/2013 18:04:27 - INFO - Checking header
09/004/2013 18:04:27 - INFO - Flashing data
09/004/2013 18:04:28 - INFO - Loader : S1_Loader_Root_773f - Version: R4A066 / Boot version: r9A029 / Bootloader status : ROOTED
09/004/2013 18:04:29 - INFO - Processing kernel.sin
09/004/2013 18:04:29 - INFO - Checking header
09/004/2013 18:04:29 - INFO - Ending flash session
09/004/2013 18:04:29 - ERROR - ERR_SEVERITY = " MAJOR " ; ERR_CLASS = " SECURITY_CLASS " ; ERR_STATIC = " SIN_HEAD_VER " ; ERR_DYNAMIC = "Failed to Verify without header" ;
09/004/2013 18:04:29 - ERROR - Error flashing . Aborted
09/004/2013 18:04:29 - INFO - Device connected in flash mode
09/004/2013 18:04:30 - INFO - Device disconnected
09/004/2013 18:04:32 - INFO - Device connected in flash mode)
5 . The next thing I did was start in recovery mode. I flashed the ROM and Gapps .
6 .And after 2 days of intense work and break my head finally enjoying kit kat
:good::good::fingers-crossed::highfive:
Click to expand...
Click to collapse
Do you think there's a chance for my WT19a 12w31 with "bootloader unlock allowed: no"?
Could you share the resulting .ftf? I tried to, but it fails everytime. I don't know, maybe I'm missing something or it only works with the mini pro sk17.
I´ve been trying with my girlfriends mini st15 (already unlocked bootloader via test point) and just can´t make it work.
Does someone have a jellybean ftf kernel for the ST15?? Thank you...
ciran said:
Could you share the resulting .ftf? I tried to, but it fails everytime. I don't know, maybe I'm missing something or it only works with the mini pro sk17.
I´ve been trying with my girlfriends mini st15 (already unlocked bootloader via test point) and just can´t make it work.
Does someone have a jellybean ftf kernel for the ST15?? Thank you...
Click to expand...
Click to collapse
Cada archivo ftf es unico, cada vez que intentes instalar una nueva rom deberas extraer el archivo boot.img de la rom y convertirlo en ftf , luego ingresar al recovery y instalar la rom.
Each ftf file is unique, every time you try to install a new ROM will have to extract the boot.img file in the ROM and turn it into ftf, then enter the recovery and install the rom.
Snake1405 said:
Do you think there's a chance for my WT19a 12w31 with "bootloader unlock allowed: no"?
Click to expand...
Click to collapse
yup, maybe it works
imauri1990 said:
yup, maybe it works
Click to expand...
Click to collapse
cannot get cygwin to work .........extractboot ....
---------- Post added at 01:17 AM ---------- Previous post was at 12:58 AM ----------
got this error on flashtools
09/014/2015 22:14:01 - INFO - Device connected in flash mode
09/014/2015 22:14:23 - INFO - Selected Bundle for sk17i . FW release : kernel cm9. Customization : FTF For Xperia mini pro
09/014/2015 22:14:23 - INFO - Preparing files for flashing
09/014/2015 22:14:23 - INFO - Please connect your device into flashmode.
09/014/2015 22:14:24 - INFO - Opening device for R/W
09/014/2015 22:14:24 - INFO - Reading device information
09/014/2015 22:14:41 - INFO - Unable to read from phone after having opened it.
09/014/2015 22:14:41 - INFO - trying to continue anyway
09/014/2015 22:14:41 - INFO - Start Flashing
09/014/2015 22:14:41 - INFO - Processing loader.sin
09/014/2015 22:14:41 - INFO - Checking header
09/014/2015 22:14:41 - ERROR - Processing of loader.sin finished with errors.
09/014/2015 22:14:41 - INFO - Ending flash session
09/014/2015 22:14:41 - ERROR - Error in processHeader : 22 : El dispositivo no reconoce el comando.
09/014/2015 22:14:41 - ERROR - Error flashing. Aborted
09/014/2015 22:14:41 - INFO - Device disconnected
error proces header..... i have no idea........
contame bien que pasos hiciste y capaz te puedo ayudar.
Did you unlock using the official Sony page?
Or you unlock it using the "TP Guide by DragonClawsAreSharp"?
Edit: already did it. Unlocked successfully. Thanks for the tutorial.
It doesn't work for me. When I'm trying to flash the kernel, it gives me this error:
Code:
26/007/2015 07:07:19 - INFO - Processing loader_unlocked.sin
26/007/2015 07:07:19 - INFO - Checking header
26/007/2015 07:07:19 - INFO - Flashing data
26/007/2015 07:07:19 - INFO - Processing of loader_unlocked.sin finished.
26/007/2015 07:07:20 - INFO - Loader : S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Boot version : r9A021 / Bootloader status : ROOTED
26/007/2015 07:07:21 - INFO - No bootdelivery to send
26/007/2015 07:07:21 - INFO - Processing kernel.sin
26/007/2015 07:07:21 - INFO - Checking header
26/007/2015 07:07:21 - INFO - Flashing data
26/007/2015 07:07:21 - ERROR - Processing of kernel.sin finished with errors.
26/007/2015 07:07:21 - INFO - Ending flash session
26/007/2015 07:07:21 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
I've tried to convert a kernel boot.img to ftf like 10 times, I've even tried another kernels, but I get the same error everytime I try to flash. I've followed everything in the tutorials.
I have ST15i by the way.
Could you send me the ftf you've created? So I can test if the ftf was the problem.
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