Develop Bugs

[Q] what does exclamation mark and phone logo means?

the title says it all. what does it mean? my phone crashed yesterday and was going to flash from .368 to the latest one. the thing is I get error while flashing so it's aborted. tried reflashing the .368 and some other f/w. it was successful but when I boot my phone up. after SE logo I see a exclamtion mark w/ a traingle around it and a phone below. what does it mean?
after a while my phone boots up then I get FC everywhere. stuck on setup wizard then low on space??!!!! I need help please (((
22/043/2011 08:43:39 - INFO - <- This level is successfully initialized
22/043/2011 08:43:50 - INFO - Preparing files for flashing
22/044/2011 08:44:02 - INFO - Searching Xperia....
22/044/2011 08:44:03 - ERROR - Please plug you device in flash mode
22/044/2011 08:44:04 - INFO - Searching Xperia....
22/044/2011 08:44:04 - ERROR - Please plug you device in flash mode
22/044/2011 08:44:05 - INFO - Searching Xperia....
22/044/2011 08:44:05 - ERROR - Please plug you device in flash mode
22/044/2011 08:44:06 - INFO - Searching Xperia....
22/044/2011 08:44:06 - ERROR - Please plug you device in flash mode
22/044/2011 08:44:07 - INFO - Searching Xperia....
22/044/2011 08:44:07 - ERROR - Please plug you device in flash mode
22/044/2011 08:44:08 - INFO - Searching Xperia....
22/044/2011 08:44:08 - ERROR - USB\VID_0FCE&PID_ADDE\6&147D268&0&1
22/044/2011 08:44:09 - INFO - Searching Xperia....
22/044/2011 08:44:09 - INFO - Found at USB\VID_0FCE&PID_ADDE\6&147D268&0&1
22/044/2011 08:44:09 - INFO - Start Flashing
22/044/2011 08:44:09 - INFO - VER="R9A021";DATE="20110128";TIME="11:49:00";
22/044/2011 08:44:10 - INFO - Flashing loader
22/044/2011 08:44:11 - INFO - PROT_VER="03";DATE="20110217";TIME="15:47:00";VER="R4A066";CXC="1234-5769";TYPE="S1_LOADER";UNIQUE_DEV_ID="F69C97E268F3A2963A8C564287843968E79B8729";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4B6D7100471404C8150404288863725BB001002000000000";IMEI="35730204270287";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_ID="0001";ACTIVE_LOADER_AID="0001";MEMDEVS="02:00:002C:00B3:0000:00002000:00020000:00000800:00000040,03:03:001B:534D:0010:0001DA60:00010000:00000200";MAN_ID="002C";DEV_ID="00B3";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="YES";CARD_SIZE="8GB";CARD_DATA="";LOADER_ROOT="S1_Loader_Root_773f";EROM_ROOT="S1_EROM_Root_d601";SW_ROOT="S1_SW_Root_883f";CUST_ROOT="S1_Cust_Root_9603";SIM_LOCK_ROOT="S1_SL_Root_c422";HW_CONF_ROOT="S1_HWConf_Root_08af";BIM_STATE="DISABLED";
22/044/2011 08:44:12 - INFO - Flashing adsp.sin
22/044/2011 08:44:15 - INFO - Flashing kernel.sin
22/044/2011 08:44:17 - INFO - Flashing amss_fs.sin
22/044/2011 08:44:17 - INFO - Flashing fota1.sin
22/044/2011 08:44:18 - INFO - Flashing fota0.sin
22/044/2011 08:44:19 - INFO - Flashing amss.sin
22/044/2011 08:44:30 - INFO - Flashing cache.sin
22/045/2011 08:45:14 - INFO - Flashing system.sin
22/047/2011 08:47:21 - INFO - Flashing userdata.sin
22/055/2011 08:55:00 - INFO - Flashing finished.
22/055/2011 08:55:00 - INFO - Now unplug the device and power it on
22/055/2011 08:55:00 - INFO - Then go to application settings
22/055/2011 08:55:00 - INFO - turn on Unknown Sources and Debugging
Click to expand...
Click to collapse

anyone? PLEASE

On my old HTC that icon meant that you were accessing the built in recovery...it's odd that your phone continues to boot after that..
All I can suggest is reinstalling the firmware.

it is odd. yeah experienced it too on my old desire.
I was shocked why it won't boot. sometimes it boots on a specific f/w without wipe. but the phone memory is messed up. used space is 380mb. and FC everytime

gonemad02 said:
it is odd. yeah experienced it too on my old desire.
I was shocked why it won't boot. sometimes it boots on a specific f/w without wipe. but the phone memory is messed up. used space is 380mb. and FC everytime
Click to expand...
Click to collapse
Read about some others having that problem with spaced got filled up. One got it resolved by flashing and the other i'm not sure what he did or if he got it solved?
There might be some command in fastboot to erease that partition where it fails to clean up when flashing. It might be the boot section/bootloader that's screewed up somehow?
Regards Dousan...

that's what I thought too. bu I don't know those commands in fastboot. this is driving me crazy! haha been up for 41hours now trying to figure it ourt :S
EDIT: and oh. could you please point me to those posts you were talking about. couldn't seem to find it. sorry and many thanks for the idea )
tried fastboot -w commande and got this msg
C:\Users\user\Desktop\ANDROID\fastboot>fastboot -w
< waiting for device >
erasing 'userdata'...
(bootloader) Erase of partition 'userdata' requested
(bootloader) S1 partID 0x00000009, block 0x00000ca8-0x00001887
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
(bootloader) Erase operation complete, 2184 bad blocks encountered
OKAY [ 1.513s]
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
finished. total time: 1.517s
Click to expand...
Click to collapse
is it normal for the wipe cache to fail? pls have a look

and btw. CWM says
Can't open /cache/recovery/log etc2.

41 hours You need to get some sleep mate
It looks like a corupted bootloader, taken that amount of bad blocks you've encountered, and a simple flash won't fix that. Take a look at this thread as I think it will help you to get a booting and working phone again:
http://forum.xda-developers.com/showthread.php?t=1252038
Regards Dousan...

thankyou. will try that later on.
EDIT: my phone now boots up. the problem is "low on space' then FC FC and FC
i believe the real culprit is this
(bootloader) Erase operation complete, 2184 bad blocks encountered
OKAY [ 1.513s]
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
Click to expand...
Click to collapse

2184 bad blocks? dayum @[email protected]
low on space? new firmware and maybe a new SDCard might help..

I have every firmware for play
yeah alot huh
wonder how it became that high :| tried two of my sdcards.
some blocks on the bootloader is the problem :S
I need help fixing it asap thanks for all your response

Unable to boot Custom Kernels

My unlocked R800i doesn't seem to be able to boot custom kernels! After flashing a kernel it will go to the splash screen before the screen turns black and the phone reboots. I have tried relocking and unlocking again but it doesn't seem to make a difference. The only kernels I can use are DoomLords, with any others such as FXP, Mjolnir and KeICS not booting.Can't figure out whats wrong, any ideas?
Unlocking
Code:
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
OKAY [ 2.974s]
finished. total time: 2.974s
Flashing a Kernel:
Code:
C:\Android>fastboot flash boot KeICSv2.img
sending 'boot' (6202 KB)...
(bootloader) USB download speed was 30829kB/s
OKAY [ 0.747s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.230s]
finished. total time: 1.978s

i think you need to get the most recent, the newest version of the kernel
and i suggest you to do a full wipe, also with the dalvik cache

yukarundeng said:
i think you need to get the most recent, the newest version of the kernel
and i suggest you to do a full wipe, also with the dalvik cache
Click to expand...
Click to collapse
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.

mcharga3000 said:
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.
Click to expand...
Click to collapse
doomlord/keiren = tap back button
cm7/cm9/ICX/MIUI/mjolnir/lupus = tap the vol down button
to enter the recovery mode when the kernel logo shows up

mcharga3000 said:
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.
Click to expand...
Click to collapse
Re-read the instructions for the kernel your using you probably have to use a different button to get into recovery, like volume button or something. Doomkernel is back button
Sent from my R800a using XDA App

can't flash custom kernel

I'm facing an major problem I have a arc s with unlocked bootloader and it's rooted I'm on 4.0.4 FW 41.B.0.587
And when i try to flash a custom kernel ex. vengeance v1.32 it goes good and it doesn't give me any error
Code:
01/020/2013 21:20:24 - INFO - <- This level is successfully initialized
01/020/2013 21:20:24 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
01/020/2013 21:20:24 - INFO - You can drag and drop ftf files here to start flashing them
01/020/2013 21:20:32 - INFO - Device disconnected
01/020/2013 21:20:33 - INFO - Flash canceled
01/020/2013 21:20:37 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/020/2013 21:20:37 - INFO - Device Status: NOT FOUND
01/020/2013 21:20:39 - ERROR - This action can only be done in fastboot mode
01/020/2013 21:20:58 - INFO - Device connected in fastboot mode
01/021/2013 21:21:13 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Compaq\Desktop\android\fastboot\boot.img
01/021/2013 21:21:13 - INFO - Flashing selected kernel
01/021/2013 21:21:15 - INFO - Finished Fastboot Toolbox
01/021/2013 21:21:15 - INFO - sending 'boot' (5632 KB)...
01/021/2013 21:21:15 - INFO - (bootloader) USB download speed was 14239kB/s
01/021/2013 21:21:15 - INFO - OKAY [ 0.787s]
01/021/2013 21:21:15 - INFO - writing 'boot'...
01/021/2013 21:21:15 - INFO - (bootloader) Download buffer format: boot IMG
01/021/2013 21:21:15 - INFO - (bootloader) Flash of partition 'boot' requested
01/021/2013 21:21:15 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
01/021/2013 21:21:15 - INFO - (bootloader) Erase operation complete, 1 bad blocks encountered
01/021/2013 21:21:15 - INFO - (bootloader) Flashing...
01/021/2013 21:21:15 - INFO - (bootloader) Flash operation complete
01/021/2013 21:21:15 - INFO - OKAY [ 1.140s]
01/021/2013 21:21:15 - INFO - finished. total time: 1.927s
01/021/2013 21:21:15 - INFO - FASTBOOT Output:
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 14239kB/s
OKAY [ 0.787s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 1 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.140s]
finished. total time: 1.927s
01/021/2013 21:21:15 - INFO - Please check the log before rebooting into system
Now after I unplug the USB and try to go into CMW by pressing power+volume down
it does vibrate but forever black screen and I'm able to go into flashmode and fastboot mode so I flashed back to stock
plz help me out :crying:

Sv: can't flash custom kernel
android-turk said:
I'm facing an major problem I have a arc s with unlocked bootloader and it's rooted I'm on 4.0.4 FW 41.B.0.587
And when i try to flash a custom kernel ex. vengeance v1.32 it goes good and it doesn't give me any error
Code:
01/020/2013 21:20:24 - INFO - <- This level is successfully initialized
01/020/2013 21:20:24 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
01/020/2013 21:20:24 - INFO - You can drag and drop ftf files here to start flashing them
01/020/2013 21:20:32 - INFO - Device disconnected
01/020/2013 21:20:33 - INFO - Flash canceled
01/020/2013 21:20:37 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/020/2013 21:20:37 - INFO - Device Status: NOT FOUND
01/020/2013 21:20:39 - ERROR - This action can only be done in fastboot mode
01/020/2013 21:20:58 - INFO - Device connected in fastboot mode
01/021/2013 21:21:13 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Compaq\Desktop\android\fastboot\boot.img
01/021/2013 21:21:13 - INFO - Flashing selected kernel
01/021/2013 21:21:15 - INFO - Finished Fastboot Toolbox
01/021/2013 21:21:15 - INFO - sending 'boot' (5632 KB)...
01/021/2013 21:21:15 - INFO - (bootloader) USB download speed was 14239kB/s
01/021/2013 21:21:15 - INFO - OKAY [ 0.787s]
01/021/2013 21:21:15 - INFO - writing 'boot'...
01/021/2013 21:21:15 - INFO - (bootloader) Download buffer format: boot IMG
01/021/2013 21:21:15 - INFO - (bootloader) Flash of partition 'boot' requested
01/021/2013 21:21:15 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
01/021/2013 21:21:15 - INFO - (bootloader) Erase operation complete, 1 bad blocks encountered
01/021/2013 21:21:15 - INFO - (bootloader) Flashing...
01/021/2013 21:21:15 - INFO - (bootloader) Flash operation complete
01/021/2013 21:21:15 - INFO - OKAY [ 1.140s]
01/021/2013 21:21:15 - INFO - finished. total time: 1.927s
01/021/2013 21:21:15 - INFO - FASTBOOT Output:
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 14239kB/s
OKAY [ 0.787s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 1 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.140s]
finished. total time: 1.927s
01/021/2013 21:21:15 - INFO - Please check the log before rebooting into system
Now after I unplug the USB and try to go into CMW by pressing power+volume down
it does vibrate but forever black screen and I'm able to go into flashmode and fastboot mode so I flashed back to stock
plz help me out :crying:
Click to expand...
Click to collapse
Are you using latest Flashtool? And which kernel are u going to flash?
Sent from my GT-I9300 using xda app-developers app

android-turk said:
I'm facing an major problem I have a arc s with unlocked bootloader and it's rooted I'm on 4.0.4 FW 41.B.0.587
it does vibrate but forever black screen and I'm able to go into flashmode and fastboot mode so I flashed back to stock
plz help me out :crying:
Click to expand...
Click to collapse
flash stock kernel and test

Yes it is the lastest flashtools and I tried different kernels like vengeance, fusion 4.5, cm10.1 kernel, fxp cm10 kernel and all same result.
Sent from my LT18i using xda app-developers app

Stock, no custom kernel

You didn't understood me i was going to flash a custom rom but before I can do that I need to flash a custom kernel and boot into recovery and there I get stuck I can't boot in to recovery logo doesn't appear the only thing I can do is go into flashmode and fastboot mode
EDIT: I looked into logs of other people and there is something different in my log the mine says 1 badblock encounterd... Does somebody know what this mean ???
Sent from my LT18i using xda app-developers app

Read Recovery thread

Plz give link to thread
Sent from my LT18i using xda app-developers app

Hi Buddy,
If I read your post correctly , you are trying with Power On + Volume Down right?
Do this
1> Power on and leave power button.
2> Wait for logo to appear and keep pressing volume down button , you should be able to see CMW recovery ..
If you still face the same issue use Flashtool to flash stock rom with kernel.
Steps:
1> Copy stock ROM to "Flashtool\firmwares" and select flash with kernel selected in Flashtool
2> Press , back button and connect phone to PC when the Flashtool asks you to connect the phone
3> Once flashed boot the phone normally.
Thanks,
mastfun

I alrready found my prob. It was that I had a bad block in my boot so thats why the kernels didn't bootup and solution is to lock bootloader and flash only roms for locked bootloader now everything is fine
Sent from my LT18i powered by REVELUTION ICS HD ROM using xda app-developers app

Error in Custum Karnel install [lupus]

17/025/2013 15:25:22 - INFO - Please check the log before rebooting into system
17/025/2013 15:25:34 - INFO - Finished Fastboot Toolbox
17/026/2013 15:26:06 - INFO - Device disconnected
17/038/2013 15:38:18 - INFO - Device connected with USB debugging off
17/038/2013 15:38:18 - INFO - For 2011 devices line, be sure you are not in MTP mode
17/038/2013 15:38:19 - INFO - Device disconnected
17/038/2013 15:38:20 - INFO - Device connected with USB debugging off
17/038/2013 15:38:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
17/038/2013 15:38:28 - INFO - Device disconnected
17/038/2013 15:38:30 - INFO - Device connected in fastboot mode
17/038/2013 15:38:40 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
17/038/2013 15:38:41 - INFO - Device Status: FASTBOOT mode
17/038/2013 15:38:44 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\5.4fusion.img
17/038/2013 15:38:44 - INFO - Flashing selected kernel
17/038/2013 15:38:46 - INFO - sending 'boot' (5760 KB)...
17/038/2013 15:38:46 - INFO - (bootloader) USB download speed was 2949120kB/s
17/038/2013 15:38:46 - INFO - OKAY [ 0.650s]
17/038/2013 15:38:46 - INFO - writing 'boot'...
17/038/2013 15:38:46 - INFO - (bootloader) Download buffer format: boot IMG
17/038/2013 15:38:46 - INFO - (bootloader) Flash of partition 'boot' requested
17/038/2013 15:38:46 - INFO - (bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
17/038/2013 15:38:46 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
17/038/2013 15:38:46 - INFO - (bootloader) Flashing...
17/038/2013 15:38:46 - INFO - (bootloader) Flash operation complete
17/038/2013 15:38:46 - INFO - OKAY [ 1.186s]
17/038/2013 15:38:46 - INFO - finished. total time: 1.836s
17/038/2013 15:38:46 - INFO - FASTBOOT Output:
sending 'boot' (5760 KB)...
(bootloader) USB download speed was 2949120kB/s
OKAY [ 0.650s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.186s]
finished. total time: 1.836s
17/038/2013 15:38:46 - INFO - Please check the log before rebooting into system
And now? =S

What's the error?seems fine...
Sent from my Neo V using xda-developers app

(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3 (bootloader) Erase operation complete, 0 bad blocks encountered
After the lupus screen the screen stay black

Punk44 said:
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3 (bootloader) Erase operation complete, 0 bad blocks encountered
After the lupus screen the screen stay black
Click to expand...
Click to collapse
that is normal, just boot up the phone now and get into the recovery to flash the rom you want.

How i recovery to flash the rom in lupus?
I install with zip and nothing, black screen

Punk44 said:
How i recovery to flash the rom in lupus?
I install with zip and nothing, black screen
Click to expand...
Click to collapse
after you flash the kernel, if your phone is arc s just keep pressing the vol down button after you boot up your phone to enter the cwm recovery

But i install the zip (ultimate HD 3.0.2) and after lupus logo the screen are black =/

Punk44 said:
But i install the zip (ultimate HD 3.0.2) and after lupus logo the screen are black =/
Click to expand...
Click to collapse
did you wipe all, before flashing the rom?

Punk44 said:
But i install the zip (ultimate HD 3.0.2) and after lupus logo the screen are black =/
Click to expand...
Click to collapse
Which lupus kernel you installed? There are two of them...
Sent from my Xperia Neo V using xda app-developers app

Are you flashing lupus or fusion?
Sent from my X10i using xda premium

Did you follow the instructions for installing the Rom correctly? If you unknowingly missed something, then you might need to reflash the Sony stock Rom using flashtool.
Sent from my LT18i using xda premium

[Q] Dead XPERIA S - vibrates only

Hello,
I was preparing my Xperia S to change ROM to new official JB:
Firstly, after wiping SD Card it dissapeared and couldn't be mounted, I tried to get it back wiping caches and formating system (it was the newest PAC installed there with another recovery - not CWM, which allows me to copy files to SD Card using PC in recovery mode - I wanted it back).
Secondly, I installed this stock kernel: http://forum.xda-developers.com/showthread.php?t=2250287 using flashtool on fastboot mode LOG:
01/027/2013 11:27:00 - INFO - Device Status: FASTBOOT mode
01/027/2013 11:27:30 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Domin\Desktop\boot.elf
01/027/2013 11:27:30 - INFO - Flashing selected kernel
01/027/2013 11:27:31 - INFO - sending 'boot' (7565 KB)...
01/027/2013 11:27:31 - INFO - (bootloader) USB download speed was 33980kB/s
01/027/2013 11:27:31 - INFO - OKAY [ 0.244s]
01/027/2013 11:27:31 - INFO - writing 'boot'...
01/027/2013 11:27:31 - INFO - (bootloader) Flash of partition 'boot' requested
01/027/2013 11:27:31 - INFO - (bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
01/027/2013 11:27:31 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
01/027/2013 11:27:31 - INFO - (bootloader) Flashing...
01/027/2013 11:27:31 - INFO - (bootloader) Flash operation complete
01/027/2013 11:27:31 - INFO - OKAY [ 1.183s]
01/027/2013 11:27:31 - INFO - finished. total time: 1.427s
01/027/2013 11:27:31 - INFO - FASTBOOT Output:
sending 'boot' (7565 KB)...
(bootloader) USB download speed was 33980kB/s
OKAY [ 0.244s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.183s]
finished. total time: 1.427s
01/027/2013 11:27:31 - INFO - Please check the log before rebooting into system
01/027/2013 11:27:39 - INFO - Device will now exit fastboot mode and start booting into system
01/027/2013 11:27:39 - INFO - Device disconnected
01/030/2013 11:30:28 - INFO - Finished Fastboot Toolbox
, then rebooting device to system and after that my phone is totaly dead.
Before these operations Xperia was charged to ~90%, was unlocked and rooted.
Diodes are dead too, even when I charge the phone with loader.
When I hold power and vol+ for ~10s i feel three vibrations and nothing happens...
Probably this kernel (Advanced Stock Kernel v1.0) provoked this problem, I've installed so many another kernels on my device and it was always fine.
What to do?

U have xperia S kernel is for xperia P
Brick

adiif1 said:
U have xperia S kernel is for xperia P
Brick
Click to expand...
Click to collapse
Damn xD
What now? poop

I think,if it vibrates u still got chance.Just try to flash stock ftf in flashmode.Do tell the result
Press Thanks if it worked
Sent from my Xperia SL using xda premium