Have searched and searched regarding this problem.. i just cant figure it out.
No matter what i do i cant enter fastboot mode
I have the little r from s1tool: RUNNING S1_EROM VER "r9A021"
Have installed all possible drivers including ADB drivers.
Flashtool: 13/026/2012 07:26:33 - INFO - Device Status: ADB mode
Used the flashtool bootloader unlock, only to be told:
13/010/2012 07:10:15 - INFO - Flashing loader
13/010/2012 07:10:17 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
13/010/2012 07:10:17 - INFO - Start Reading property
13/010/2012 07:10:17 - INFO - Ending flash session
13/010/2012 07:10:17 - INFO - Your phone is already unlocked. Canceling task
13/021/2012 07:21:48 - INFO - Connected device : SK17
13/021/2012 07:21:48 - INFO - Installed version of busybox : BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
13/021/2012 07:21:48 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
13/022/2012 07:22:09 - INFO - Root Access Allowed
Click Fastboot mode --> Reboot into fastboot mode (via ADB)
Phone rebots into normal mode (sigh)
Take out battery - wait 30 sec - Hold Volum Up key and plug in the usb cable.
The bugger will not go into fastboot mode - light is still green.. no blue light for me
any help would be much appriciated.
You have sim-lock, right? Fastboot is disabled and the only way to enable it is via paid method.
Also, you have Bootloader Unlock Allowed: No, right?
Sent from my Xperia Live using xda premium
Yeah ut sats Bootloader unlock allowed: no
So only paid service then.. hmm too bad..
Thx for the help!
Related
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
Hi,
i tried to enter fastboot mode via flashtool.
I get this log when i enter the unlock mode:
22/055/2012 19:55:23 - INFO - Device connected with USB debugging on
22/055/2012 19:55:23 - INFO - Connected device : U20
22/055/2012 19:55:23 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/055/2012 19:55:23 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
22/055/2012 19:55:26 - INFO - Root Access Allowed
22/055/2012 19:55:33 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
22/055/2012 19:55:33 - INFO - Device Status: ADB mode
22/055/2012 19:55:35 - INFO - Device Status: ADB mode
22/055/2012 19:55:36 - ERROR - This action can be done only if the connected phone has fastboot mode
22/055/2012 19:55:38 - INFO - Finished Fastboot Toolbox
22/004/2012 20:04:44 - INFO - Please connect your device into flashmode.
22/004/2012 20:04:48 - INFO - Device disconnected
22/005/2012 20:05:11 - INFO - Device connected in flash mode
22/005/2012 20:05:11 - INFO - Opening device for R/W
22/005/2012 20:05:11 - INFO - Reading device information
22/005/2012 20:05:11 - INFO - Phone ready for flashmode operations.
22/005/2012 20:05:11 - INFO - Processing loader
22/005/2012 20:05:11 - INFO - Checking header
22/005/2012 20:05:11 - INFO - Flashing data
22/005/2012 20:05:13 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
22/005/2012 20:05:13 - INFO - Phone already unlocked
22/005/2012 20:05:13 - INFO - You can safely reboot in normal mode
22/005/2012 20:05:13 - INFO - Ending flash session
22/005/2012 20:05:13 - WARN - Cancelled
22/005/2012 20:05:13 - INFO - Device connected in flash mode
22/005/2012 20:05:15 - INFO - Device disconnected
22/005/2012 20:05:17 - INFO - Device connected in flash mode
So the phone is allready unlocked.
I have the Google Android ADB drivers installed.
But i can not kick the phone into fastboot via ADB.
Also i can not enter fastboot with any key while plugging the usb into the phone.
Any suggestions?
thx
A19183
are you sure you are entering fastboot mode in a proper way? power off the phone, hold vol down button and connect to pc, if the led turns blue you are in fastboot mode.
edit:
it seems you are trying this on x8 or similar phone, hold menu and connect the device
Think so......
n0b0dy666 said:
are you sure you are entering fastboot mode in a proper way? power off the phone, hold vol down button and connect to pc, if the led turns blue you are in fastboot mode.
Click to expand...
Click to collapse
Yes, i tried that several times.
The Blue light does not come on.
But i should be able to Kick it from ADB into fastboot via Flashtool, shouldn't i?
Greets
A19183
Edit:
Phone: xperia x10 Mini pro
System: Win xp in Parallels Desktop for Mac
a19183 said:
Yes, i tried that several times.
The Blue light does not come on.
But i should be able to Kick it from ADB into fastboot via Flashtool, shouldn't i?
Greets
A19183
Edit:
Phone: xperia x10 Mini pro
System: Win xp in Parallels Desktop for Mac
Click to expand...
Click to collapse
Okay, there are 2 things:
1. This is xperia mini pro sk17i forum and not x10 mini pro, so better ask there
2. On our phone it's volume up to enter fastboot and please install all drivers for all devices/modes from flashtool folder -> drivers, too...
Sent from my SK17i running Jelly Bean via CM10
Oooops
mihahn said:
Okay, there are 2 things:
1. This is xperia mini pro sk17i forum and not x10 mini pro, so better ask there
2. On our phone it's volume up to enter fastboot and please install all drivers for all devices/modes from flashtool folder -> drivers, too...
Sent from my SK17i running Jelly Bean via CM10
Click to expand...
Click to collapse
Sorry,
My Bad.
Could someone move the thread or close it?
As Far as i understand the x10 does Not have fastboot..
Shame on me..........
:silly:
hey guys,
ive got my phone rooted (with superoneclick) and ive installed the xrecovery.. thing is now i cant get into my flash thing at all - if i try and press the back button and plug it in - nothing, no light or anything - as soon as i let go of my back button it just boots.
i want a custom rom as ive had this android for over like 2years... should i just restore my phone using sonys pc campanion and follow an easy guild to do everything that i want, or am i missing something?
thanks
Edit: should i update from xrecovery to this?:
http://forum.xda-developers.com/showthread.php?t=1105745&highlight=cwm+installer
EVEN MORE EDITS:
11/010/2012 15:10:45 - INFO - <- This level is successfully initialized
11/010/2012 15:10:45 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
11/010/2012 15:10:45 - INFO - You can drag and drop ftf files here to start flashing them
11/010/2012 15:10:56 - INFO - Device connected with USB debugging on
11/010/2012 15:10:59 - INFO - Connected device : E10
11/010/2012 15:10:59 - INFO - Installed version of busybox : BusyBox v1.19.0.git.adrynalyne (2010-12-21 22:03:30 MST) multi-call binary.
11/010/2012 15:10:59 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
11/011/2012 15:11:09 - INFO - Root Access Allowed
11/011/2012 15:11:15 - INFO - Installing Recovery to device...
11/011/2012 15:11:15 - INFO - Remounting system read-write
11/011/2012 15:11:22 - INFO - Canceled
11/011/2012 15:11:26 - INFO - Please connect your device into flashmode.
11/011/2012 15:11:29 - INFO - Device disconnected
11/011/2012 15:11:46 - INFO - Device connected in flash mode
11/011/2012 15:11:46 - INFO - Opening device for R/W
11/011/2012 15:11:47 - INFO - Reading device information
11/011/2012 15:11:47 - INFO - Phone ready for flashmode operations.
11/011/2012 15:11:47 - INFO - Processing loader
11/011/2012 15:11:47 - INFO - Checking header
11/011/2012 15:11:47 - INFO - Flashing data
11/011/2012 15:11:50 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
11/011/2012 15:11:50 - INFO - Phone already unlocked
11/011/2012 15:11:50 - INFO - You can safely reboot in normal mode
11/011/2012 15:11:50 - INFO - Ending flash session
11/011/2012 15:11:50 - WARN - Cancelled
11/011/2012 15:11:50 - INFO - Device connected in flash mode
11/011/2012 15:11:51 - INFO - Device disconnected
11/011/2012 15:11:53 - INFO - Device connected in flash mode
11/012/2012 15:12:12 - INFO - Device disconnected
11/012/2012 15:12:15 - INFO - Device connected with USB debugging off
11/012/2012 15:12:15 - INFO - For 2011 devices line, be sure you are not in MTP mode
11/012/2012 15:12:19 - INFO - Device disconnected
11/012/2012 15:12:22 - INFO - Device connected with USB debugging on
11/012/2012 15:12:22 - INFO - Connected device : E10
11/012/2012 15:12:22 - INFO - Installed version of busybox : BusyBox v1.19.0.git.adrynalyne (2010-12-21 22:03:30 MST) multi-call binary.
11/012/2012 15:12:22 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
11/012/2012 15:12:23 - INFO - Root Access Allowed
Now what?! lol - flash a kernal?
You should change to CWM RECOVERY because it is more stable.
Sent from my E10i using Tapatalk 2
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
Did u unlock your bootloader?
Sent from my E10i using Tapatalk 2
pongnamu said:
You should change to CWM RECOVERY because it is more stable.
Sent from my E10i using Tapatalk 2
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
Did u unlock your bootloader?
Sent from my E10i using Tapatalk 2
Click to expand...
Click to collapse
i have just updated from xrecovery and yes my bootloader is unlocked now xD
Thank for the reply
InFam0us-1985 said:
i have just updated from xrecovery and yes my bootloader is unlocked now xD
Thank for the reply
Click to expand...
Click to collapse
Then move zip file of the Rom to sd and flash kernel!
Sent from my E10i using Tapatalk 2
pongnamu said:
Then move zip file of the Rom to sd and flash kernel!
Sent from my E10i using Tapatalk 2
Click to expand...
Click to collapse
but...
flashtool said this in the log:
11/011/2012 15:11:47 - INFO - Processing loader
11/011/2012 15:11:47 - INFO - Checking header
11/011/2012 15:11:47 - INFO - Flashing data
11/011/2012 15:11:50 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
11/011/2012 15:11:50 - INFO - Phone already unlocked
https://docs.google.com/document/pub?id=1VKfQ79qi6yPT8kZePoeDUWGTZXvUe7hjQREbMKSwHmM&pli=1 - says:
If you get r8A029 -> UNlocked.
If you get R8A029 -> Locked
InFam0us-1985 said:
but...
flashtool said this in the log:
11/011/2012 15:11:47 - INFO - Processing loader
11/011/2012 15:11:47 - INFO - Checking header
11/011/2012 15:11:47 - INFO - Flashing data
11/011/2012 15:11:50 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : ROOTED
11/011/2012 15:11:50 - INFO - Phone already unlocked
https://docs.google.com/document/pub?id=1VKfQ79qi6yPT8kZePoeDUWGTZXvUe7hjQREbMKSwHmM&pli=1 - says:
If you get r8A029 -> UNlocked.
If you get R8A029 -> Locked
Click to expand...
Click to collapse
You didnt unlocked it sucessfully.
Sent from my E10i using Tapatalk 2
pongnamu said:
You didnt unlocked it sucessfully.
Sent from my E10i using Tapatalk 2
Click to expand...
Click to collapse
Any other idea on how i can do this? - im running windows 8 :crying:
ok - i ran the s1tool and the log says its unlocked?:
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "00EC/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): E10i
SOFTWARE VERSION: 1235-3408_2.1.1.A.0.6
CUSTOM VERSION: 1236-0812_R7B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511KTG5G
SEMC SIMLOCK CERTIFICATE
Elapsed:9 secs.
PROCEDURE STOPPED BY USER
Update
Flashed nAa kernal - done
Flashed minicm7 2.2.1 - done
Phone currently booting for the first time - only thing i couldn't find was the gapps? :highfive:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
it is in the thread with minicm7
http://forum.xda-developers.com/showthread.php?t=1068553
INSTRUCTION xD
penthaler said:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
it is in the thread with minicm7
http://forum.xda-developers.com/showthread.php?t=1068553
INSTRUCTION xD
Click to expand...
Click to collapse
Thank you very much guys - problem now is my batt keeps dying so fast... i use to use crazyhome as my home screen - this comes with built in AWD? does it use that much power? i have turned everything off that is not important - like menu anim, desktops, changed cpu max to 320mhz, or should i just try a different rom? - Also do i need to relock my bootloader?
hey guys
recently i have got this jellybean rom
http://forum.xda-developers.com/showthread.php?t=2258058
i wanna to back again to ICS
what the kernel and rom should i flash it on flash tools
bec
no recovery and can't get it on jellybean
i wanna to back to ICS,unlock bootloader,root my phone then flash CM 10
and
yesterday i tried to unlock bootloader on jellybean
it was allowed in configuration
then i tried this method
http://www.androidauthority.com/xperia-s-unlock-bootloader-82532/
then it successfully unlocked
and the configuration
become
bootloader unlock : Yes
when i tried to root it with this method
http://forum.xda-developers.com/showthread.php?t=1886460
failed to root
and
become
bootloader unlock allow : no
nw what should i do ?
.
.
.
.
srry for my english
and flash tool INFO in bootloader unlock plugin
26/050/2013 07:50:04 - INFO - Current device : LT22i - CB511Z631Y - 1261-8592_R4H - 1254-4233_6.2.A.0.400 - WORLD_6.2.A.0.400
26/050/2013 07:50:04 - INFO - Processing loader
26/050/2013 07:50:04 - INFO - Checking header
26/050/2013 07:50:04 - INFO - Flashing data
26/050/2013 07:50:05 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTED
26/050/2013 07:50:05 - INFO - Start Reading property
26/050/2013 07:50:05 - INFO - Reading TA finished.
26/050/2013 07:50:05 - INFO - Ending flash session
26/050/2013 07:50:05 - INFO - Now unplug your device and restart it into fastbootmode
26/050/2013 07:50:05 - INFO - Device connected in flash mode
26/050/2013 07:50:06 - INFO - Device disconnected
26/050/2013 07:50:16 - INFO - Your phone is already unlocked. Canceling task
26/050/2013 07:50:17 - INFO - Device connected in fastboot mode
umm solved all thing
thx any way
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