Hello there.
After beeing fed up with the sluggish performance of my Neo stock ICS over the last months I finally took the step
and tried to install a custom rom.
I went for the xperia Ultimate HD 3.0.2. And I messed it up!!
Root went fine with help of the Dessert Journey thread http://forum.xda-developers.com/showthread.php?p=42856914
Installed x-parts for CWM and here is where it started to go sideways.
I left the bootloader locked.
I took me 10 attempts to get into CWM but finally managed to start it.
I then installed ultimate HD with the help of a guide.
But then the phone stalled showing the sony logo. However I could still get into CWM so I repeated the process 4 times.
On the 4th attempt I was starting to get frustrated and here is where I messed up.
I had a brain freeze and ticked the last box in Aroma where its says reebot allthough the guide I used clearly says don't!
Result: The phone starts with the usual vibration but freezes on the sony logo.
I spent a few hours trying to find a thread how I could undo my mess but I just don't know where to start.I have now more or less given up and resigned to the fact that I killed it.
I'll probably drop the hammer on a second hand nexus 4 today.
It would however be fun to ressurrect the neo and to be able to play with it. (Perhaps bad choise of words) So any Idea where to start for me to untangle this mess?
Thanks in advance
VoidWiking said:
Hello there.
After beeing fed up with the sluggish performance of my Neo stock ICS over the last months I finally took the step
and tried to install a custom rom.
I went for the xperia Ultimate HD 3.0.2. And I messed it up!!
Root went fine with help of the Dessert Journey thread http://forum.xda-developers.com/showthread.php?p=42856914
Installed x-parts for CWM and here is where it started to go sideways.
I left the bootloader locked.
I took me 10 attempts to get into CWM but finally managed to start it.
I then installed ultimate HD with the help of a guide.
But then the phone stalled showing the sony logo. However I could still get into CWM so I repeated the process 4 times.
On the 4th attempt I was starting to get frustrated and here is where I messed up.
I had a brain freeze and ticked the last box in Aroma where its says reebot allthough the guide I used clearly says don't!
Result: The phone starts with the usual vibration but freezes on the sony logo.
I spent a few hours trying to find a thread how I could undo my mess but I just don't know where to start.I have now more or less given up and resigned to the fact that I killed it.
I'll probably drop the hammer on a second hand nexus 4 today.
It would however be fun to ressurrect the neo and to be able to play with it. (Perhaps bad choise of words) So any Idea where to start for me to untangle this mess?
Thanks in advance
Click to expand...
Click to collapse
Flash stock ftf with Flashtool...
Sent from my Xperia Neo V using xda app-developers app
Ok, I tried that but it' still the same.
Here is the log from flashtool:
Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
02/009/2013 14:09:50 - INFO - Device disconnected
02/010/2013 14:10:13 - INFO - Device connected in flash mode
02/010/2013 14:10:27 - INFO - Selected MT15I / 4.1.B.0.587 / 1247-0875 Nordic
02/010/2013 14:10:27 - INFO - Preparing files for flashing
02/010/2013 14:10:27 - INFO - Please connect your device into flashmode.
02/010/2013 14:10:28 - INFO - Opening device for R/W
02/010/2013 14:10:29 - INFO - Reading device information
02/010/2013 14:10:29 - INFO - Phone ready for flashmode operations.
02/010/2013 14:10:29 - INFO - Current device : Unknown: Jul 13 2012/20:41:33 - BX902E9079 - Unknown: Jul 13 2012/20:41:33 - 1242-4466_4.1.B.0.587 - Unknown: Jul 13 2012/20:41:33
02/010/2013 14:10:29 - INFO - Start Flashing
02/010/2013 14:10:29 - INFO - Processing loader
02/010/2013 14:10:29 - INFO - Checking header
02/010/2013 14:10:29 - INFO - Flashing data
02/010/2013 14:10:31 - INFO - Loader : S1_Loader_Root_773f - Version : R4A069 / Bootloader status : ROOTABLE
02/010/2013 14:10:31 - INFO - Disabling final data verification check
02/010/2013 14:10:31 - INFO - Processing kernel.sin
02/010/2013 14:10:31 - INFO - Checking header
02/010/2013 14:10:31 - INFO - Flashing data
02/010/2013 14:10:33 - INFO - Ending flash session
02/010/2013 14:10:33 - INFO - Flashing finished.
02/010/2013 14:10:33 - INFO - Please unplug and start your phone
02/010/2013 14:10:33 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/010/2013 14:10:33 - INFO - Device connected in flash mode
02/010/2013 14:10:48 - INFO - Device disconnected
just unlock u bootloader it is safety and quick
go to wotan server and make an account buy 8 dollars download xunlock tool from wotan server for youre pone install in pc make a test point start xunlock tool it tool one minute to unlock y bootloader and network for 8 buck it work for me great now i have a Brand new pone no problema with bootloop because every time i got bootloop i enter in recovery with press volumen down quickly hopr u served man .
Do I need Wotan when my phone has "bootloader unlock allowed"?
And does it say that flashtool doesn't recognize my device?
VoidWiking said:
Do I need Wotan when my phone has "bootloader unlock allowed"?
And does it say that flashtool doesn't recognize my device?
Click to expand...
Click to collapse
Dude just follow this:
You just have to flash the stock .ftf file into your phone and it will work like before
1. Download the .ftf stock file for your neo.
2. Now as your phone is stucked at sony logo take out your battery and connect the phone to pc.
3. Now presa the back button and while you keep on pressing it just insert the battery and you are in flashmode now install the stock firmware and your phone is back.
Hit "Thanks" if i helped.
Sent from my Xperia Neo V using xda premium
paras.arora said:
Dude just follow this:
You just have to flash the stock .ftf file into your phone and it will work like before
1. Download the .ftf stock file for your neo.
2. Now as your phone is stucked at sony logo take out your battery and connect the phone to pc.
3. Now presa the back button and while you keep on pressing it just insert the battery and you are in flashmode now install the stock firmware and your phone is back.
Hit "Thanks" if i helped.
Sent from my Xperia Neo V using xda premium
Click to expand...
Click to collapse
I wish it had helped! I have flashed the phone. But Im still stuck at sony logo.
Flashtoll says this: WARN - <- This level is successfully initialized.
Can it be that I have installed a corrupt rom that doesn't work and that because my bootloader is locked CWM has disappeared and that the phone has no way to start properly.
VoidWiking said:
I wish it had helped! I have flashed the phone. But Im still stuck at sony logo.
Flashtoll says this: WARN - <- This level is successfully initialized.
Can it be that I have installed a corrupt rom that doesn't work and that because my bootloader is locked CWM has disappeared and that the phone has no way to start properly.
Click to expand...
Click to collapse
Then try using sus and flash the stock rom with that and after your phone starts once then repeat all the steps for rooting and everything.
Sent from my Xperia Neo V using xda premium
If you flashed a rom with locked bootloader and after that you can still enter cwm, then you didn't follow the right steps.
When you install a rom you have to make all wipes in cwm, this will delete cwm after rom installation.
Same way with flashtool, when you flash a ftf firmware to restore corrupt phone make sure to check all wipes.
Sent from my MT15i using xda app-developers app
Bertellio said:
If you flashed a rom with locked bootloader and after that you can still enter cwm, then you didn't follow the right steps.
When you install a rom you have to make all wipes in cwm, this will delete cwm after rom installation.
Same way with flashtool, when you flash a ftf firmware to restore corrupt phone make sure to check all wipes.
Sent from my MT15i using xda app-developers app
Click to expand...
Click to collapse
Yeah....
So I removed the sd-card and checked what I ROM I had installed. I had installed xperia ultimate hd 3.0.2 following a guide for xperia ultimate hd 2.0.2. apparently they somewhat different. There is still a folder callad Clockwork Mod on the SD card.
Did I ever mess up.
Sus also say the latest updates are already istalled on the phone.
Question: The ftf firmware I flashed is the 4.1.0.587 Nordic and it does not give the option for any wipes. There is the 4.1.0.587 Global that does.
Should I flash that and wipe everything?
VoidWiking said:
Yeah....
So I removed the sd-card and checked what I ROM I had installed. I had installed xperia ultimate hd 3.0.2 following a guide for xperia ultimate hd 2.0.2. apparently they somewhat different. There is still a folder callad Clockwork Mod on the SD card.
Did I ever mess up.
Sus also say the latest updates are already istalled on the phone.
Question: The ftf firmware I flashed is the 4.1.0.587 Nordic and it does not give the option for any wipes. There is the 4.1.0.587 Global that does.
Should I flash that and wipe everything?
Click to expand...
Click to collapse
Do this.. Just go to recovery, do wipes as follows,
Wipe data/factory reset, wipe cache partition,
Go to advance, wipe dalvik cache,
Mounts and storage, format data, format system, format cache..
Flash rom once again properly by reading instructions,.. This should fix it without flashing stock ftf and stuff.. And while flashing please tick on locked bootloader in aroma.. Hope this helps you
Sent from my Xperia Neo V using xda premium
vishal_android freak said:
Do this.. Just go to recovery, do wipes as follows,
Wipe data/factory reset, wipe cache partition,
Go to advance, wipe dalvik cache,
Mounts and storage, format data, format system, format cache..
Flash rom once again properly by reading instructions,.. This should fix it without flashing stock ftf and stuff.. And while flashing please tick on locked bootloader in aroma.. Hope this helps you
Sent from my Xperia Neo V using xda premium
Click to expand...
Click to collapse
I'm unable to go to recovery. Led is green when I start the phone but Im still stuck on the sony logo. Tried the press down volume key and on/off button to get into recovery
VoidWiking said:
Ok, I tried that but it' still the same.
Here is the log from flashtool:
Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
02/009/2013 14:09:50 - INFO - Device disconnected
02/010/2013 14:10:13 - INFO - Device connected in flash mode
02/010/2013 14:10:27 - INFO - Selected MT15I / 4.1.B.0.587 / 1247-0875 Nordic
02/010/2013 14:10:27 - INFO - Preparing files for flashing
02/010/2013 14:10:27 - INFO - Please connect your device into flashmode.
02/010/2013 14:10:28 - INFO - Opening device for R/W
02/010/2013 14:10:29 - INFO - Reading device information
02/010/2013 14:10:29 - INFO - Phone ready for flashmode operations.
02/010/2013 14:10:29 - INFO - Current device : Unknown: Jul 13 2012/20:41:33 - BX902E9079 - Unknown: Jul 13 2012/20:41:33 - 1242-4466_4.1.B.0.587 - Unknown: Jul 13 2012/20:41:33
02/010/2013 14:10:29 - INFO - Start Flashing
02/010/2013 14:10:29 - INFO - Processing loader
02/010/2013 14:10:29 - INFO - Checking header
02/010/2013 14:10:29 - INFO - Flashing data
02/010/2013 14:10:31 - INFO - Loader : S1_Loader_Root_773f - Version : R4A069 / Bootloader status : ROOTABLE
02/010/2013 14:10:31 - INFO - Disabling final data verification check
02/010/2013 14:10:31 - INFO - Processing kernel.sin
02/010/2013 14:10:31 - INFO - Checking header
02/010/2013 14:10:31 - INFO - Flashing data
02/010/2013 14:10:33 - INFO - Ending flash session
02/010/2013 14:10:33 - INFO - Flashing finished.
02/010/2013 14:10:33 - INFO - Please unplug and start your phone
02/010/2013 14:10:33 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/010/2013 14:10:33 - INFO - Device connected in flash mode
02/010/2013 14:10:48 - INFO - Device disconnected
Click to expand...
Click to collapse
Seeing at your logs clearly tells that you're not flashing full firmware .ftf but just the kernel.
So to fix this do following:
1. Start Flashtool
2. Click on flash icon & select Flashmode.
3. Select the ftf file.
4. IMPORTANT: See the boxes on the right & CHECK all the 'Wipe boxes' (Apps log, User data, Cache, etc.) & UNCHECK all the 'Exclude boxes' (FOTA, System, Kernel, Baseband, etc.)
5. Click OK
6. Follow the instructions on screen.
7. Boot up your phone!
Then root your phone again > install CWM Recovery > follow the guide of ROM you want to install.
You're done! Cheers!
So when tried to flash the 4.1.0.587 Nordic ftf it did not give the option for any wipes. Could not check or uncheck anything because box was blank.
Then i flashed the 4.1.0.587 Global ftf and wiped cache and user data.
That worked!!
Thanks everyone that had the patience to try and help me.
Now I'm just gonna enjoythe fact that it works and in a day or so I'll root the slow and lagging thing and install a propher ROM
I have now been running Xperia Ultimate HD 2.0.2 for a week with no big issues and lot less lag.
Great! Cant wait to try another ROM.
Related
So you did the inevitable... you got a phone that's bricked.. fear not.. this happens to all of us.. consider it a "right of passage" when it comes to dealing with custom ROM's
Here at xda, help is never too far away (I was there once too)
I've tried to get you back to functioning latest Local 2.1 with recovery (xrecovery)
0) You'll lose all data with this method....
come to terms with that... not stuff on the sd card but data of your phone, sms'es, contacts, applications etc
1) Turn off your phone
Pull the battery and reinsert it if you have to...
2) Install Flashtool
go here and downlad flashtool
Install on your windows pc
Thank Androxyde and Bin4ry for this kickass tool
3) Download and flash stock 2.1
Go to this thread and download a 2.1 rom in your language of choice (Dont worry that it's not your local ROM)
4) Flash this rom using Flashtool
In the first link there is a how-to. follow it and flash the downloaded ROM from step 3
Once you have 2.1 on your phone,
5) Enable USB Debugging and Root
Use flashtool and root your phone using the simple button "Root" (I know!! what an awesome tool right!!?? )
Once rooted, disconnect the phone.
6) Get yourself a root file manager
Download a file manager capable of root access such as root explorer or solid explorer.
7) Access and edit the build.prop file
Open the file manager. U should get a superuser prompt to allow root access. Touch "Allow". Go to /system and mount the system as RW. there's a file there called build.prop. open it in a text editor. Find all instances of a number that looks like this 1238-9045 (this is my build number, yours will not be the same). Edit this number(all 3 instances) to look like your build number (Found on original box or behind the battery). Save the file and exit
8) Update via SEUS OR PC companion
Now connect your phone back. PC companion or SEUS will tell you there is a new update available. follow the instructions and you'll be running the latest 2.1 for your region and variant of the mini pro
9) [optional] Root and recovery
The new firmware installed by SEUS/PC companion is not rooted. If you need it, root again (same way as in step 5). once rooted, click "Ask root perms" on flashtool. Once root access is confirmed, install xrecovery from the menu.
Hope that helped!
Enjoy
Edit: if you get an error while opening flashtool saying "JVM could not be started because heap size bla bla bla..." Please try on another pc and maybe reinstall windows on urs
Bricked u20i
My phone keeps disconnecting nce the green light goes on. Please help
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
16/010/2012 19:10:31 - INFO - Device connected with USB debugging off
16/010/2012 19:10:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
Can someone help?
Immortalis said:
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
Can someone help?
Click to expand...
Click to collapse
Repair it with SEUS or PC Companion.
Step A: leave your phone disconnected from your PC
Step B: Run SEUS/PC Companion, and select update
Step C: It doesn't recognise your phone because it's disconnected and give you a repair option
Step D: Select it, choose your model, it will download the firmware
Step Ea: You get a popup, Press the back-button on your phone while it's off and plug in the USB-Cable
Step Eb: If you can't turn off your phone, plug in the USB-cable and press home- and power-buttons at the same time, it will do a hard reboot and enter flashmode.
Step F: Wait till it's done...
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
slvjpn said:
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
Click to expand...
Click to collapse
You don't need usb-debugging in order to flash your phone.
SmG67 said:
You don't need usb-debugging in order to flash your phone.
Click to expand...
Click to collapse
tell this to my sister's x10 pro mini ). I know your right but the phone is @&&&@%))+6)-)-))-=+( up so it doesn't know human comands
Help needed !!
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
(Damn I've been gone a while)
Not too sure of the greek firmware file bro.. can you put the link of the forum where you got it from? are you sure it is a stock firmware?
gixxerfan said:
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
Click to expand...
Click to collapse
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
jasonmiracle said:
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
Click to expand...
Click to collapse
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
SmG67 said:
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
Click to expand...
Click to collapse
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
and now that my bootloader is locked, and i cant root my phone without turning it on( the phone bricked cant turn on anymore) i cant unlock my bootloader to flash new kernels into it... please do provide stock firmware and rom for me... i can only flash stock kernel, but not the rom... after i flashed the stock u20i kernel, i dont know how to flash the original rom into my phone, since now my phone, didnt have the CWM or XRecover anymore, which can browse my SD card, and install the rom from .zip files....
flashing stock kernel no problem but did not know how to flash the stock rom
01/041/2012 15:41:58 - INFO - Device connected in flash mode
01/041/2012 15:41:59 - INFO - Opening device for R/W
01/041/2012 15:41:59 - INFO - Reading device information
01/042/2012 15:42:00 - INFO - Phone ready for flashmode operations.
01/042/2012 15:42:00 - INFO - Start Flashing
01/042/2012 15:42:00 - INFO - Processing loader
01/042/2012 15:42:00 - INFO - Checking header
01/042/2012 15:42:00 - INFO - Flashing data
01/042/2012 15:42:02 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
01/042/2012 15:42:02 - INFO - Processing kernel.sin
01/042/2012 15:42:02 - INFO - Checking header
01/042/2012 15:42:02 - INFO - Flashing data
01/042/2012 15:42:05 - INFO - Ending flash session
01/042/2012 15:42:05 - INFO - Flashing finished.
01/042/2012 15:42:05 - INFO - Please unplug and start your phone
01/042/2012 15:42:05 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
01/042/2012 15:42:06 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
unable to flash customised kernel probably because of the locked bootloader
01/052/2012 15:52:27 - INFO - Device connected in flash mode
01/052/2012 15:52:27 - INFO - Opening device for R/W
01/052/2012 15:52:28 - INFO - Reading device information
01/052/2012 15:52:28 - INFO - Phone ready for flashmode operations.
01/052/2012 15:52:28 - INFO - Start Flashing
01/052/2012 15:52:28 - INFO - Processing loader
01/052/2012 15:52:28 - INFO - Checking header
01/052/2012 15:52:28 - INFO - Ending flash session
01/052/2012 15:52:28 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
s1tool shows locked bootloader
i1109.photobucket.com/albums/h426/jasonforeverlove/11-2.jpg
problem- cant turn on the phone in order to choose usb debugging mode to root the phone
problem- SEUS cant detect update to my phone...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
jasonmiracle said:
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
Click to expand...
Click to collapse
Download this, It's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
SmG67 said:
ubuntuone.com/515oWr7b8j4PeeZfm8xZ1pIt's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
Click to expand...
Click to collapse
im trying this out... :victory:
tks for the thread, dude
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
itwasgood said:
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
Click to expand...
Click to collapse
Repair with Sony Update Service or PC Companion?
SmG67 said:
Repair with Sony Update Service or PC Companion?
Click to expand...
Click to collapse
already tried it. but still it won't turned on.
flashtool does not recognize my phone
flashtool does not recognize my x10 mini pro, screen still remains black, seus and pc companion does not recognize it either. what do i do?:crying:
itwasgood said:
already tried it. but still it won't turned on.
Click to expand...
Click to collapse
Your tried to unlock your booloader and now dont turn on?
If your phones was manufacturated after 11w29, you got a hard brick.
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
jaleelchennai said:
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
Click to expand...
Click to collapse
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
can i try other custom rom?
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
can i try other custom rom? like real ics 6?
jaleelchennai said:
can i try other custom rom? like real ics 6?
Click to expand...
Click to collapse
If your bootloader is unlocked, sure. Otherwise, can you enter cwm?
yes i can enter in cwm, i will try another rom, thanks..
jaleelchennai said:
yes i can enter in cwm, i will try another rom, thanks..
Click to expand...
Click to collapse
Is your bootloader locked or unlocked? Because if it's unlocked and you chose the right kernel and rom, maybe you forgot to do a factory reset or wipe cache?
it is unlocked 7 months ago, i tried some gb roms and this ics rom, but now only i had this type of problem, that why i little worried about.
May b just reflash the right kernel (kernel panic works fine with r6) then factory reset,wipe,dalvik cache and format system and flash the rom. I hope that should solve your problem. Otherwise you can always try stock kernel & rom suggested by mihahn
Try Pestanoid v3
Can you try this my ROM Pestanoid v3 ...http://forum.xda-developers.com/showthread.php?t=1905976
Just try another rom+kernel and remeber: You will have to do a factory reset and wipe cache/dalvik cache, but only format system if it's required in rom thread! Otherwise don't format it
Sent from my SK17i running Jelly Bean via CM10
Also turn usb debugging on when using flashtools!!
Thanks for all, now it is solved with another rom and Mesa kernel. But now i am think to re-flash new rom http://forum.xda-developers.com/showthread.php?t=1908269,
will download in this evening.
Stuck after SONY logo
I tried everything bt nothing is helpin me out to solve ths issue.
I flashed my cell again n again to stock ROM. bt, still my XMP is not able to boot or charge. I've repaired my cell through SUS, bt still same problem. what to do ?? I am on stock kernel n Stock ROM (ICS 4.1.B.0.587). My Bootloead is Locked.
Pls Reply ASAP.
First of all dont panic. you have NOT BRICKED ur phone.
Just flash any other kernel and any other ROM. your device should work fine...
Once I had the same problem.
The solution is flash your mobile with another kernel and wipe everything.
Use a custom rom.if nothing happen reunlock ur bootloder with testpoint method.
Sent from my WT19i using Tapatalk 2
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
CHETANN.5 said:
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
Click to expand...
Click to collapse
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
mihahn said:
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
Click to expand...
Click to collapse
No coz i dont know how to flash it ..n also i had a locked bootloader
CHETANN.5 said:
No coz i dont know how to flash it ..n also i had a locked bootloader
Click to expand...
Click to collapse
You can even flash on locked bootloader
So you download the stock firmware .ftf (for ics 4.1.B.0.587) for your device. (e.g. mini=st15=smultron, minipro=sk17=mango, active=st17=satsuma, livewithwalkman=wt19=coconut). Then you install flashtool and install all drivers for all devices/modes from flashtool installation folder - drivers
Now you place the downloaded .ftf in flashtool - firmwares and delete all other files in there. Afterwards you launch flashtool
Now click on the flash - flashmode - select the .ftf - click okay - now turn off phone, take out battery, wait 10 seconds, reinsert battery, hold volume down and while holding volume down simply connect phone via usb to your pc, the green led will light up and the flashing process starts. Now wait until it has finished, disconnect phone and boot it. Done :good:
Sent from my SK17i running stock ics (.587)
Thanxxxxx it worked
N also can i now install other roms on it as did before??
In the past i have once messed up the flashing of a rom and as a result my xperia neo v got stuck at boot loop at the "sony" logo
To fix it, all i did was to go into flashmode and flash the stock .ftf. After that, my phone would work again and i could flash my rom again.
However, now, my soft-bricked phone (same situation, bootloop at sony logo) is unable to go into flash mode and fastboot no matter which button it is i am holding. It just enters recovery mode no matter what i press.
When i hold volume down/menu/back button when i plug in, the phone vibrates and the sony logo appears, then the led light turns blue for a second then disappears, and enters recovery mode.
I am unsure whether my bootloader is unlocked as i may have relocked it in the past but i doubt it relocked it.
I did not find anything helpful after searching the forums for a solution for being unable to enter both flashmode and fastboot.
Re-flashing the rom, wiping cache partition, dalvik cache, factory reset, all of that did not work
Please help if you can :crying:
[EDIT]
Flashmode now works, but i get the header 6 error, so i am trying to use EMMA to fix my phone
[EDIT2]
EMMA worked! thanks guys for your suggestions.
credits to http://forum.xda-developers.com/showthread.php?t=2190272 for the suggestion
(in case anyone stumbles upon this thread and wants to try this solution)
on a side note my phone is now back to 2.3.4 haha
more problems incoming
Syntactic said:
In the past i have once messed up the flashing of a rom and as a result my xperia neo v got stuck at boot loop at the "sony" logo
To fix it, all i did was to go into flashmode and flash the stock .ftf. After that, my phone would work again and i could flash my rom again.
However, now, my soft-bricked phone (same situation, bootloop at sony logo) is unable to go into flash mode and fastboot no matter which button it is i am holding. It just enters recovery mode no matter what i press.
When i hold volume down/menu/back button when i plug in, the phone vibrates and the sony logo appears, then the led light turns blue for a second then disappears, and enters recovery mode.
I am unsure whether my bootloader is unlocked as i may have relocked it in the past but i doubt it relocked it.
I did not find anything helpful after searching the forums for a solution for being unable to enter both flashmode and fastboot.
Re-flashing the rom, wiping cache partition, dalvik cache, factory reset, all of that did not work
Please help if you can :crying:
Click to expand...
Click to collapse
How exactly did you brick it now?
Sent from my Xperia Neo V using xda app-developers app
use SUS ...((if bootloader is lock ))
or try to restore ur android backup from CWM
and if u think ur bootloader is unlock then try unlockbootloader flashtool
sagar.andro said:
use SUS ...((if bootloader is lock ))
or try to restore ur android backup from CWM
and if u think ur bootloader is unlock then try unlockbootloader flashtool
Click to expand...
Click to collapse
Im attempting SUS right now but it tells me my phone cant be identified
my android backup tells me MD5 checksum failed and i cant do anything about that because i cant get cmd to work..
[EDIT] SEUS gives me the 'your phone contains modified software' message and i relocked using flashtool but got the same message
sony service center last step ...........
or wait if any one give u some useful help
Attitude.SSJ said:
How exactly did you brick it now?
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
I simply did the standard procedure for flashing a new ROM.
1.kernel
2.factory reset, wipe cache partition, dalvik cache, format data , system, and cache, the likes
3. then i flashed a new rom. sjb5.5 and flashed the gapps zip
did i do anything wrong :/
Syntactic said:
I simply did the standard procedure for flashing a new ROM.
1.kernel
2.factory reset, wipe cache partition, dalvik cache, format data , system, and cache, the likes
3. then i flashed a new rom. sjb5.5 and flashed the gapps zip
did i do anything wrong :/
Click to expand...
Click to collapse
Which kernel?sjb needs a jb kernel...
Sent from my Xperia Neo V using xda app-developers app
Attitude.SSJ said:
Which kernel?sjb needs a jb kernel...
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
ahhh that must have been the problem.... i probably flashed a ICS kernel
i recovered phone using EMMA, and now i have a new problem :
06/038/2013 17:38:55 - INFO - Reading device information
06/039/2013 17:39:19 - INFO - Please connect your device into flashmode.
06/039/2013 17:39:20 - INFO - Opening device for R/W
06/039/2013 17:39:20 - INFO - Processing loader
06/039/2013 17:39:23 - INFO - Checking header
06/039/2013 17:39:23 - ERROR -
06/039/2013 17:39:23 - INFO - Your phone bootloader cannot be officially unlocked
06/039/2013 17:39:23 - INFO - You can now unplug and restart your phone
06/039/2013 17:39:30 - INFO - Selected MT11i / 4.1.B.0.431 / Customized Central Europe 3
06/039/2013 17:39:30 - INFO - Preparing files for flashing
06/039/2013 17:39:31 - INFO - Please connect your device into flashmode.
06/039/2013 17:39:32 - INFO - Opening device for R/W
06/039/2013 17:39:32 - INFO - Start Flashing
06/039/2013 17:39:32 - INFO - Processing loader
06/039/2013 17:39:32 - INFO - Checking header
06/039/2013 17:39:32 - INFO - Ending flash session
06/039/2013 17:39:32 - ERROR -
06/039/2013 17:39:32 - ERROR - Error flashing. Aborted
06/039/2013 17:39:32 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
the problem is that i see no error.
so im assuming its a header problem but i dont know how to fix it...
[EDIT] current phone :
using stock Xperia Neo V GB 2.3.4 (build 4.0.2.A.0.62 )
My Ray has a weird Brick like condition..
I can access CWM, got ot Flash and Fastboot mode, install zip ROMs and FTF ROMS, but all I get is the SE logo - never beyond that.
The PC Companion does not recognize the phone.. where it should show the cennected Device's model number, it shows "(null)"
It All started when I installed installed a new Kernel (was on Fusion for over a Year, but My Battery drained fast when I tried KitKat (Beanstalk) so I thought maybe changing Kernel would help. At first I lost ToutchScreen (even in CWM)
Than I tried several other ROM's and Kernels.. still no touchscreen.. until This happened.
I have tried: relocking BL, UnRooting, installing several Kernels and ROMS - custom and stock (GB, ICS, JB)
PC Companion has told me 2 things: I have custom software and there is no software available for My phone
Also tried with Emma - it did its thing, but as You guessed - Nothing.
Xperia Update Service tells Me the same as PC Companion: nothing to update - already latest version (even with GB)
Also I have read through countles post's and tutorials how to UnBrick.. so far nothing helped. Did not really find a similar case
Currently it is UnRooted and Bootloader is ReLocked.
Last FlashTool log:
13/000/2013 00:00:24 - INFO - <- This level is successfully initialized
13/000/2013 00:00:24 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
13/000/2013 00:00:30 - INFO - Device disconnected
13/000/2013 00:00:47 - INFO - Selected ST18 / 4.0.2.A.0.62 / Central Europe
13/000/2013 00:00:47 - INFO - Preparing files for flashing
13/001/2013 00:01:35 - INFO - Please connect your device into flashmode.
13/002/2013 00:02:47 - INFO - Device connected in flash mode
13/002/2013 00:02:47 - INFO - Opening device for R/W
13/002/2013 00:02:47 - INFO - Reading device information
13/002/2013 00:02:47 - INFO - Phone ready for flashmode operations.
13/002/2013 00:02:47 - INFO - Current device : ST18i - CB511V79AW - 1255-1753_R1I - Unknown: Jul 13 2012/21:04:14 - WORLD-i_4.1.B.0.587
13/002/2013 00:02:47 - INFO - Start Flashing
13/002/2013 00:02:47 - INFO - Processing loader.sin
13/002/2013 00:02:47 - INFO - Checking header
13/002/2013 00:02:48 - INFO - Flashing data
13/002/2013 00:02:50 - INFO - Loader : S1_Loader_Root_773f - Version : R4A069 / Boot version : R9A029 / Bootloader status : ROOTABLE
13/002/2013 00:02:50 - INFO - Disabling final data verification check
13/002/2013 00:02:51 - INFO - Processing kernel.sin
13/002/2013 00:02:51 - INFO - Checking header
13/002/2013 00:02:51 - INFO - Flashing data
13/002/2013 00:02:52 - INFO - Processing fota1.sin
13/002/2013 00:02:52 - INFO - Checking header
13/002/2013 00:02:52 - INFO - Flashing data
13/002/2013 00:02:53 - INFO - Processing fota0.sin
13/002/2013 00:02:53 - INFO - Checking header
13/002/2013 00:02:53 - INFO - Flashing data
13/002/2013 00:02:54 - INFO - Processing adsp.sin
13/002/2013 00:02:54 - INFO - Checking header
13/002/2013 00:02:54 - INFO - Flashing data
13/002/2013 00:02:56 - INFO - Processing amss_fs_urushi.sin
13/002/2013 00:02:56 - INFO - Checking header
13/002/2013 00:02:56 - INFO - Flashing data
13/002/2013 00:02:56 - INFO - Processing amss.sin
13/002/2013 00:02:56 - INFO - Checking header
13/002/2013 00:02:56 - INFO - Flashing data
13/003/2013 00:03:02 - INFO - Processing apps_log.sin
13/003/2013 00:03:02 - INFO - Checking header
13/003/2013 00:03:02 - INFO - Flashing data
13/003/2013 00:03:02 - INFO - Processing cache.sin
13/003/2013 00:03:02 - INFO - Checking header
13/003/2013 00:03:02 - INFO - Flashing data
13/003/2013 00:03:03 - INFO - Processing system.sin
13/003/2013 00:03:03 - INFO - Checking header
13/003/2013 00:03:04 - INFO - Flashing data
13/004/2013 00:04:26 - INFO - Processing userdata.sin
13/004/2013 00:04:26 - INFO - Checking header
13/004/2013 00:04:26 - INFO - Flashing data
13/004/2013 00:04:31 - INFO - Resetting customizations
13/004/2013 00:04:31 - INFO - Writing TA unit : [00, 00, 08, A4, 00, 00, 00, 0E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
13/004/2013 00:04:31 - INFO - Ending flash session
13/004/2013 00:04:31 - INFO - Flashing finished.
13/004/2013 00:04:31 - INFO - Please unplug and start your phone
13/004/2013 00:04:31 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
13/004/2013 00:04:32 - INFO - Device connected in flash mode
One more thing.. it is not charging.. It has been on the cable for the better part of a day,
but the Battery voltage is ~3,75V (about 5-10%)
Update: When I insert the USB Cable, it goes to Flash mode (without holding any buttons) and in 40 seconds Flashtool says Disconnected and the charging picture appears for a few seconds, and than starts charging.
Any Ideas ?!
Did you relock your bootloader with setool? I revived my totally dead phone (it wouldn't even power up, only green led blinks), I killed phone with OTA update on unlocked bootloader.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
Relocked it with Xperia_Relock_bootloader.ftf
ReLocking did not cause the problem. I relocked it to restore phone with PC Companion (which did not work)
Viljar70 said:
Relocked it with Xperia_Relock_bootloader.ftf
ReLocking did not cause the problem. I relocked it to restore phone with PC Companion (which did not work)
Click to expand...
Click to collapse
Did you try first to flash stock kernel or stock firmware then to relock bootloader?
Yes, after the crash, I flashed both Custom and Stock ROM's and Kernels.
Than restored Root and BootLoader and flashed ROM's and Kernels again.
the kernel seems to be working, otherwise it would not charge.
and the system should be on there, because the PC Companion tells Me I have the latest software installed.
Viljar70 said:
Yes, after the crash, I flashed both Custom and Stock ROM's and Kernels.
Than restored Root and BootLoader and flashed ROM's and Kernels again.
the kernel seems to be working, otherwise it would not charge.
and the system should be on there, because the PC Companion tells Me I have the latest software installed.
Click to expand...
Click to collapse
Unlock bootloader flash this firmware http://forum.xda-developers.com/showpost.php?p=46895025&postcount=40.
Also, if this didn't helped try fastboot clear commands (system, data... search in xda forums for this) then flash custom kernel.
I just recently ReLocked the bootloader. It was unlocked over a year before this happened..
I have cleared pretty much everything in CWM and Flashtool
I have tried GB, ICS and JB stock firmwares
So, as You can read from above, I have already tried what You suggested
Viljar70 said:
I just recently ReLocked the bootloader. It was unlocked over a year before this happened..
I have cleared pretty much everything in CWM and Flashtool
I have tried GB, ICS and JB stock firmwares
So, as You can read from above, I have already tried what You suggested
Click to expand...
Click to collapse
I am saying that your problem is in kernel. How on earth you flash kernel when your bootloader is locked?
You didn't try any of my suggestions - except you flashed firmware probably with locked bootloader.
btw your "above" post is changed
stock FTF firmwares should have Kernels with them..
at least the Kernel image (when starting the phone) changes each time I flash a new ROM
Emma says that the Phone is locked
But now, when I tried to flash the one You suggested, the Flashtool gives an Error while starting the flash.
So I'll unlock BL and try again...
After Unlocking the BL Still the same: Error flashing. Aborted
Same with other ftf files...
edit: cant flash anything in Flashmode.. always an error.
fastboot mode works well.. installed few Kernels - no change, installed few Custom ROM's in CWM - again nothing.
edit2: btw.. all of the kernels which support touchscreen, mine does not work (CTCaer Kernel looks awesome.. too bad its touch Only - so i cant use the CWM part at all)
Emma also show's I have a correct ROM on it
https://www.dropbox.com/s/qdj1by4xbw132zp/emma.jpg
So...
Kernel should be OK (currently on Fusion.. again)
ROM looks OK
theoretically all should work ?
What could cause this... Hardware ?
The phone will automatically go to charging process if you are not doing anything on your phone while it's in Flashmode.
Sent from my SK17i using XDA Premium 4 mobile app
---------- Post added at 03:54 PM ---------- Previous post was at 03:37 PM ----------
Try this
1. Install all necessary drivers like flashmode and fastboot drivers.
2. Re-download the FTF for your phone and make sure that the FTF that you download is for Xperia Ray. Maybe there is a problem with the file.
2. Exit PC Companion or Sony Update Service (don't let it run in the background because it will interfere with the Flashtool and make sure there is no logo of them on the bottom-right corner where you can see your PC time.) Unlock the bootloader of your phone. Flashtool can do the unlocking. Just search for the tutorial here on XDA.
3. Go to Flashtool and click the "thunder logo" for flashing FTFs and kernels.
4. Select Flashmode and select the FTF that you have re-downloaded.
5. Flashtool will load the FTF for flashing. A window pop-up will appear after the FTF is fully loaded and ready to be flash.
6. This is the time where you are going to connect the phone into the PC and make your phone go to Flash mode where the LED light becomes green.
7. When the PC successfully installed the drivers and the Flashtool detected your phone then the flashing of the FTF will automatically start.
8. Wait for the flashing to be finished. When the flashing finished, unplug the phone from the PC and USB cable and turn on your phone.
9. When the phone turned on and the software is fully loaded then relock the bootloader of your phone.
10. If you want, reinstall the firmware with PC Companion or Sony Update Service.
Sent from my SK17i using XDA Premium 4 mobile app
I have tried the same thing several times, but just in case, I tried it again.. with diffeent ROM, but same results
Viljar70 said:
I have tried the same thing several times, but just in case, I tried it again.. with diffeent ROM, but same results
Click to expand...
Click to collapse
why you want to relock bootloader? try dont relock bootloader...
1. unlock the bootloader
2. flash stock rom ftf
3. flash kernel ics based stock (dont turn on the phone after flash from stock rom ftf)
4. install the rom ics based.
5. turn on your phone..
if everythings is okay maybe you can relock the bootloader...
I relocked the Bootloader to use PC Companion (it wont touch a phone with Locked BL)
I unlocked it again, flashed stock ftf and kernel (tried several stock ftf's - GB, ICS, JB)
still the same: turn on - stuck on "Sony Ericsson" logo
is there anything I can do in ADB.. through Console ?!
Viljar70 said:
I relocked the Bootloader to use PC Companion (it wont touch a phone with Locked BL)
I unlocked it again, flashed stock ftf and kernel (tried several stock ftf's - GB, ICS, JB)
still the same: turn on - stuck on "Sony Ericsson" logo
is there anything I can do in ADB.. through Console ?!
Click to expand...
Click to collapse
can you enter into CWM? if you can enter into CWM.. juz check the soft key.. if not work.. so your screen need to be replace..
No, the soft key's are not working.
Broken Digitizer should not affect phones software functions.. or does it ?!
After I lost touchscreen, I installed 2-3 new ROMS's that booted up, but still no Touch.
and Than this happened - Stuck on kernel load image.
Before I buy another Digitizer I want to make sure, the phone is working...
I Just replaced it about a month ago...
Also tried the WotanServer - software crashes as soon as I plug in the phone
Viljar70 said:
No, the soft key's are not working.
Broken Digitizer should not affect phones software functions.. or does it ?!
After I lost touchscreen, I installed 2-3 new ROMS's that booted up, but still no Touch.
and Than this happened - Stuck on kernel load image.
Before I buy another Digitizer I want to make sure, the phone is working...
I Just replaced it about a month ago...
Also tried the WotanServer - software crashes as soon as I plug in the phone
Click to expand...
Click to collapse
I think your LCD is broken if the soft key not working...
---------- Post added at 10:24 AM ---------- Previous post was at 10:02 AM ----------
Viljar70 said:
No, the soft key's are not working.
Broken Digitizer should not affect phones software functions.. or does it ?!
After I lost touchscreen, I installed 2-3 new ROMS's that booted up, but still no Touch.
and Than this happened - Stuck on kernel load image.
Before I buy another Digitizer I want to make sure, the phone is working...
I Just replaced it about a month ago...
Also tried the WotanServer - software crashes as soon as I plug in the phone
Click to expand...
Click to collapse
I hope this one can help you..
http://forum.xda-developers.com/showthread.php?t=2068819
I'll try that when I get home.. Thank You.. I really appreciate the effort
edit: unfortunately I could'nt do it.. There's no Rage Kernel for Xperia Ray.. I tried the other phone kernels just in case, but no help.
So... still at the same situation
Hi!
Im trying to get a grip of how to get wolfbreaks UlBlDoom on my phone, but im so lost.
I dont know in which order to start, im trying these two guides but get an error in the first step.
http://forum.xda-developers.com/showthread.php?t=928343
http://forum.xda-developers.com/showthread.php?t=1568792
03/007/2014 17:07:10 - INFO - <- This level is successfully initialized
03/007/2014 17:07:10 - INFO - Flashtool Version 0.9.15.0 built on 15-03-2014 23:00:00
03/007/2014 17:07:16 - ERROR - Drivers need to be installed for connected device.
03/007/2014 17:07:16 - ERROR - You can find them in the drivers folder of Flashtool.
03/011/2014 17:11:23 - INFO - Device connected with USB debugging on
03/011/2014 17:11:24 - INFO - Connected device : SonyEricson X10
03/011/2014 17:11:24 - INFO - Installed version of busybox : N/A
03/011/2014 17:11:24 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537 / Build number : 3.0.1.G.0.75
03/019/2014 17:19:26 - INFO - Please connect your device into flashmode.
03/019/2014 17:19:32 - INFO - Device disconnected
03/020/2014 17:20:08 - INFO - Device connected in flash mode
03/020/2014 17:20:08 - INFO - Opening device for R/W
03/020/2014 17:20:30 - INFO - Processing loader.sin
03/020/2014 17:20:30 - INFO - Checking header
03/020/2014 17:20:30 - ERROR - Processing of loader.sin finished with errors.
03/020/2014 17:20:30 - ERROR -
03/020/2014 17:20:30 - INFO - Your phone bootloader cannot be officially unlocked
03/020/2014 17:20:30 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
What should i do and in which order?
What exactly you are trying to say?
Unlocking your bootloader or Flashing a rom's FTF??
unlocking bootloader.
I suggest you to start everything from the beginning,
Get all required tools, like latest flashtool, Stock 2.3.3 ftf etc.,
Flash FTF, then root your phone, install recovery. Use flashtool to install your phones drivers and flash mode drivers. Let your PC detects your phone, then try to unlock BL using BL unlock plugin in flashtool.
Post the results.
Hit THANKS, If I helped a bit
Sent from my DROID using XDA-Server!
tried to flash it but it seems like my phone never gets into flashmode. (nothing happens, the phone just restarts as normally) What can i do? I've tried to install recovery and rom manager manually, and then boot into recovery from rom manager but nothing happens.
Have you installed flash mode drivers bundled with flashtool in 'Drivers' folder of flashtool?
Are you holding back button while plugging USB to phone and saw a constant 'Green' LED on?
I am sure you are not doing it in correct way, As I suggest earlier, start every thing from beginning for a better result otherwise everything will be messed up!
Hit THANKS, If I helped a bit 
Sent from my highly customised DROID using XDA-Server!
made some progress but dont know what to do know.
updated with SEUS and got pass the loader.sin error.
but cant still get into flashmode or install recovery.
when i hit the recovery button it only says to be implemented and then nothing happens.
it was a constant green led light when i used SEUS but now when i try it only blinks for a second and then boots into mormal mode. also when im trying to boot into recovery with xrecovery or rom manager it doesnt work either.
10/018/2014 23:18:50 - INFO - Device connected in flash mode
10/018/2014 23:18:50 - INFO - Opening device for R/W
10/018/2014 23:18:50 - INFO - Device connected in flash mode
10/018/2014 23:18:51 - INFO - Reading device information
10/018/2014 23:18:51 - INFO - Phone ready for flashmode operations.
10/018/2014 23:18:51 - INFO - Current device : X10i - CB511H4S5T - 1232-9594_R3C - 1227-4612_3.0.1.G.0.75 - WORLD-1-4-8_3.0.1.G.0.75
10/018/2014 23:18:51 - INFO - Using an unofficial loader
10/018/2014 23:18:51 - INFO - Processing loader_unlocked.sin
10/018/2014 23:18:51 - INFO - Checking header
10/018/2014 23:18:51 - INFO - Flashing data
10/018/2014 23:18:51 - INFO - Processing of loader_unlocked.sin finished.
10/018/2014 23:18:53 - INFO - Loader : S1_Loader_Root_f851 - Version : r4A024 / Boot version : r8A033 / Bootloader status : ROOTED
10/018/2014 23:18:53 - INFO - Ending flash session
10/018/2014 23:18:53 - INFO - Phone already unlocked
10/018/2014 23:18:53 - INFO - You can safely reboot in normal mode
10/018/2014 23:18:53 - INFO - Your phone bootloader cannot be officially unlocked
10/018/2014 23:18:53 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
A good news for you is that your phones bootloader is now unlocked.:thumbup:
What exactly are you trying to flash ATM?
Try these steps and post the results:
*First select the kernel you want to flash (go for FeraLab GB v20 kernel) in flashtool. You need to download Feralab GB v38 ROM too. Dont forget to check final verification checkbox after selecting kernel.
*let flashtool process all pre-requisite, don't connect your phone untill flashtool asks you to. It will show an animation on how to get into flash mode.
*Connect your phone in flash mode by holding back button while pluggung USB in.
*Let flashtool to do its magic. It will take a couple of secs, then disconnect.
*Turn on and try entering CWM by continously hitting back button.
If u see CWM menu, congrates and flash ROM zip, you had downloaded!
Hit THANKS, If I helped a bit 
Sent from my highly customised DROID using XDA-Server!
Are u sure my bootloader is unlocked? It says:
10/018/2014 23:18:53 - INFO - Your phone bootloader cannot be officially unlocked
Click to expand...
Click to collapse
And then theres the next problem:
Unlocked bootloaders:
Download .ftf and .zip drivers package file
Copy your ROM .zip and downloaded driver package .zip to SDcard
Put downloaded .ftf file in FlashTool/firmwares folder
Boot into recovery and do:
Click to expand...
Click to collapse
I cant boot into recovery manually..
Ps: Thanks for all the help so far!
Look bro, I am damn sure your BL in now unlock, its showing 'Bootloader status: ROOTED'
Don't confuse everything with that recovery, you need to go ahead, step by steps :/
Have you tried flashing any custom kernel yet? if not! flash any of the custom kernel for Unlocked BL available on forum. I personally suggest FeraKernel v20.
Hit THANKS, If I helped a bit
Sent from my highly customised DROID using XDA-Server!
xanubhavx said:
Look bro, I am damn sure your BL in now unlock, its showing 'Bootloader status: ROOTED'
Don't confuse everything with that recovery, you need to go ahead, step by steps :/
Have you tried flashing any custom kernel yet? if not! flash any of the custom kernel for Unlocked BL available on forum. I personally suggest FeraKernel v20.
Hit THANKS, If I helped a bit
Sent from my highly customised DROID using XDA-Server!
Click to expand...
Click to collapse
I am using Sony Xperia S and I am getting the same error now and since i format my pc updated and install all the drivers still it is the same here i have mentioned everything about my problem along with error (screenshot) in the given link below.
http://forum.xda-developers.com/xperia-s/help/error-rooting-xperia-s-ub-t2924320/
devil.tiger said:
I am using Sony Xperia S and I am getting the same error now and since i format my pc updated and install all the drivers still it is the same here i have mentioned everything about my problem along with error (screenshot) in the given link below.
http://forum.xda-developers.com/xperia-s/help/error-rooting-xperia-s-ub-t2924320/
Click to expand...
Click to collapse
Bro, I really can't help you as now I don't have any SE or Sony device from a long time. But its seems you are having drivers problem. For that I suggest you to roll back to Windows 7, as of now Windows 8 have lots of compatibility issues with different USB devices.
CHERRY NOTE: Start everything from zero, if you are following any guide on here. My personal experience, I never failed flashing any kernel on my last two Sony devices.
GOOD LUCK FLASHING :thumbup:
Sent from my MI 3W using XDA Free mobile app
xanubhavx said:
Bro, I really can't help you as now I don't have any SE or Sony device from a long time. But its seems you are having drivers problem. For that I suggest you to roll back to Windows 7, as of now Windows 8 have lots of compatibility issues with different USB devices.
CHERRY NOTE: Start everything from zero, if you are following any guide on here. My personal experience, I never failed flashing any kernel on my last two Sony devices.
GOOD LUCK FLASHING :thumbup:
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
Thanks Bro I was thinking for the same to bounce back on W7.
devil.tiger said:
Thanks Bro I was thinking for the same to bounce back on W7.
Click to expand...
Click to collapse
Better choice. Hope all goes well.
Sent from my MI 3W using XDA Free mobile app
xanubhavx said:
Better choice. Hope all goes well.
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
Bro can u provide me loader.sin for XPERIA M?
vibhu0009 said:
Bro can u provide me loader.sin for XPERIA M?
Click to expand...
Click to collapse
So sorry buddy, No more Xperia stuff left with me since my last accidental PC format. I am sure there would be other peeps out here willing to help you with that.
Loder.sin error
I have got error flashing xperia l
To a letest firmwere
mrbambocha said:
Hi!
Im trying to get a grip of how to get wolfbreaks UlBlDoom on my phone, but im so lost.
I dont know in which order to start, im trying these two guides but get an error in the first step.
http://forum.xda-developers.com/showthread.php?t=928343
http://forum.xda-developers.com/showthread.php?t=1568792
What should i do and in which order?
Click to expand...
Click to collapse
I have this problem but for FIRST time
SECOND time I repeat the process and I succeed.
I dont know English well.if its not clear,Im sorry.
Same issue.
Trying to flash a Z3 to D6653 Customized Hong Kong and gives me that error (Processing of loader.sin finished with errors.).
Same here....
I want to flash my Z3 D6653 to latest 5.1.1 Customized Thailand firmware....But, the flash tool shows this error....
Please help....
26/003/2014 17:03:41 - INFO - Opening device for R/W
26/003/2014 17:03:41 - INFO - Start Flashing
26/003/2014 17:03:41 - INFO - Processing loader.sin
26/003/2014 17:03:41 - INFO - Checking header
26/003/2014 17:03:41 - ERROR - Processing of loader.sin finished with errors.
26/003/2014 17:03:41 - INFO - Ending flash session
26/003/2014 17:03:41 - ERROR -
26/003/2014 17:03:41 - ERROR - Error flashing. Aborted