Database Develop

My phone won't reboot after flashing a .tft file

Hello guys
First of all I wanna tell that I am a newbie
Let's start with the begining:
I have unlocked my bootloader yesterday , and I have installed CMW - using tutorials founded on google. my phone it's not rooted
the firmware version (android 4.3) that was intalled after I've unlocked the bootloader has an issue, it doesn't work the wi-fi
So I decided to update the version to the last available on Sony, but it won't let me update it because my phone has the bootloader unlocked
After that I tried to relock my bootloader using a tutorial founded on google
The problem is that after flashing Xperia_SP_Relock_Bootloader.tft file in Flashboot program, the phone didn't reboot automaticaly . So I tried to reboot it myself with the "Boot into system device" option. The phone was disconnected but it won't rebooted. I also tried to turn it on but no way.
Here is the entire log from Flashboot :
03/029/2014 17:29:41 - INFO - <- This level is successfully initialized
03/029/2014 17:29:41 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
03/029/2014 17:29:46 - INFO - Device disconnected
03/030/2014 17:30:06 - INFO - Device connected in fastboot mode
03/031/2014 17:31:21 - INFO - Selected kernel (boot.img or kernel.sin): C:\2 Flashtool\firmwares\Xperia_SP_Relock_Bootloader.ftf
03/031/2014 17:31:21 - INFO - Flashing selected kernel
03/031/2014 17:31:21 - INFO - sending 'boot' (62 KB)...
03/031/2014 17:31:21 - INFO - (bootloader) USB download speed was 15985kB/s
03/031/2014 17:31:21 - INFO - OKAY [ 0.020s]
03/031/2014 17:31:21 - INFO - writing 'boot'...
03/031/2014 17:31:21 - INFO - (bootloader) Flash of partition 'boot' requested
03/031/2014 17:31:21 - INFO - (bootloader) S1 partID 0x00000003, block 0x00003000-0x0000cfff
03/031/2014 17:31:21 - INFO - (bootloader) Erase operation complete, 0 bad blocks encountered
03/031/2014 17:31:21 - INFO - (bootloader) Flashing...
03/031/2014 17:31:21 - INFO - (bootloader) Flash operation complete
03/031/2014 17:31:21 - INFO - OKAY [ 0.333s]
03/031/2014 17:31:21 - INFO - finished. total time: 0.353s
03/031/2014 17:31:21 - INFO - FASTBOOT Output:
sending 'boot' (62 KB)...
(bootloader) USB download speed was 15985kB/s
OKAY [ 0.020s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00003000-0x0000cfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.333s]
finished. total time: 0.353s
03/031/2014 17:31:21 - INFO - Please check the log before rebooting into system
03/031/2014 17:31:48 - INFO - Device Status: FASTBOOT mode
03/032/2014 17:32:01 - INFO - Device will now exit fastboot mode and start booting into system
03/032/2014 17:32:01 - INFO - Device disconnected
Can you please help me to bring my phone back to life???

This should help you
http://forum.xda-developers.com/showthread.php?t=2354721
And oh it's clearly written there that you should not use ftf to relock your bootloader :-o.
Just follow the instructions there.
Sent from my C5303 using Tapatalk

Porblems Unlocking Bootloader

So I have unlocked my bootloader with the Flashtool
At least thats what Flashtool tells me, everytime I am trying to flash the Recovery i am getting an error, all instructions tell me to use "boot.img" but i am always pointed to some DooMxxxxxxxx.img I tried renaming that one to boot.img biut no luck. (am I just using the wrong image?)
Also when trying to use Sonys Method (command line) to unlock the bootloader(after relocking with Flashtool) I get an error message:
Code:
>fastboot -i 0x0FCE oem unlock 0xXXXXX
FAILED (remote: Command did not succeed)
finished. total time: 0.030s
This is my Log from Flashtool from unlocking to trying to flash the image
Code:
10/054/2014 16:54:48 - INFO - Unlock finished
10/054/2014 16:54:51 - INFO - Ending flash session
10/054/2014 16:54:51 - INFO - You can now unplug and restart your device
10/055/2014 16:55:19 - INFO - Device connected in fastboot mode
10/056/2014 16:56:22 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\gcjb\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\kernel.img
10/056/2014 16:56:22 - INFO - Flashing selected kernel
10/056/2014 16:56:22 - INFO - sending 'boot' (13014 KB)...
10/056/2014 16:56:22 - INFO - OKAY [ 0.461s]
10/056/2014 16:56:22 - INFO - writing 'boot'...
10/056/2014 16:56:22 - INFO - FAILED (remote: Command not allowed)
10/056/2014 16:56:22 - INFO - finished. total time: 0.464s
10/056/2014 16:56:22 - INFO - FASTBOOT Output:
sending 'boot' (13014 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.464s
10/056/2014 16:56:22 - INFO - Please check the log before rebooting into system
10/056/2014 16:56:27 - INFO - Fetching connected device info
10/056/2014 16:56:27 - INFO - Connected device info: [****h ]
Windows 8.1 , Thinkpad W530 (usb 2.0 and 3.0 both do the same) , Unlock allowed: YES , carrier free Z3c
Maybe someone can help me out here? Is there anyway to test if the phone is Unlocked or not? Because after Unlocking with flashtool I still see "Unlock allowed yes" in the service menu!
thank you in advance!

finnschi said:
So I have unlocked my bootloader with the Flashtool
At least thats what Flashtool tells me, everytime I am trying to flash the Recovery i am getting an error, all instructions tell me to use "boot.img" but i am always pointed to some DooMxxxxxxxx.img I tried renaming that one to boot.img biut no luck. (am I just using the wrong image?)
Also when trying to use Sonys Method (command line) to unlock the bootloader(after relocking with Flashtool) I get an error message:
Code:
>fastboot -i 0x0FCE oem unlock 0xXXXXX
FAILED (remote: Command did not succeed)
finished. total time: 0.030s
This is my Log from Flashtool from unlocking to trying to flash the image
Code:
10/054/2014 16:54:48 - INFO - Unlock finished
10/054/2014 16:54:51 - INFO - Ending flash session
10/054/2014 16:54:51 - INFO - You can now unplug and restart your device
10/055/2014 16:55:19 - INFO - Device connected in fastboot mode
10/056/2014 16:56:22 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\gcjb\Downloads\adt-bundle-windows-x86_64-20140702\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\kernel.img
10/056/2014 16:56:22 - INFO - Flashing selected kernel
10/056/2014 16:56:22 - INFO - sending 'boot' (13014 KB)...
10/056/2014 16:56:22 - INFO - OKAY [ 0.461s]
10/056/2014 16:56:22 - INFO - writing 'boot'...
10/056/2014 16:56:22 - INFO - FAILED (remote: Command not allowed)
10/056/2014 16:56:22 - INFO - finished. total time: 0.464s
10/056/2014 16:56:22 - INFO - FASTBOOT Output:
sending 'boot' (13014 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.464s
10/056/2014 16:56:22 - INFO - Please check the log before rebooting into system
10/056/2014 16:56:27 - INFO - Fetching connected device info
10/056/2014 16:56:27 - INFO - Connected device info: [****h ]
Windows 8.1 , Thinkpad W530 (usb 2.0 and 3.0 both do the same) , Unlock allowed: YES , carrier free Z3c
Maybe someone can help me out here? Is there anyway to test if the phone is Unlocked or not? Because after Unlocking with flashtool I still see "Unlock allowed yes" in the service menu!
thank you in advance!
Click to expand...
Click to collapse
i think your device is already unlock

[Q] Z3C D5833 Bricked but with some hope

Hello guys
I sold a Z3C to a customer but 1 week after the phone died (January V4.4.4). He don't make nothing (root, unlock bootloader, flash rom, etc). Just a sudden death.
The issues were:
-By pressing the power button, the sony logo turned on but suddenly it shuts down just after that (once time).
-When I putted it on chage in the wall it appears the battery level ans it charges as well.
-When I was pressed vol up (or down, i can't remember well) + power it gave 3 vibrations.
- The LED light apperently was working.
What I've tried:
-Recover through the official softaware but I can't because it don't apear in USB and It asked to turn on the phone (the phone don't boot).
-Using flashtool. Same trouble, the usb don't recongnize.
After that, I gave up and sent it to sony repair. So it takes long SIX months. In the first, they said that was the battery. Next was the mainboard and that's it, no way to repair and them return the phone to me.
New issues (after the "sony repair"):
- The back glass was badly adjusted. No glue at all.
-No Sony logo anymore when press power button neither the LED lights.
-Good bye the 3 vibrations when press the 2 buttons.
-No charging battery icon when I puted in the wall charge (thank you sony).
-When I put it in the wall charge (or USB cable PC) the LED bright red and the logo sony appears over and over again in an eternal loop. Turns on, turns off.
(...)
I got new experience/knowledge with an asus zenfone 5 bricked and "ADB and Fastboot". I follow this tutorial:
a little update on my mini guide should be more clear now
- Download ADB and Fastboot (install at c:\adb for easy access )
- Download and install the Windows zenfone 5 driver
- Download firmware from Asus site for WW ( extract this zip file to get fastboot.img, boot.img and copy these to your ADB Fastboot folder )
- Rename the WWzip into "rom.zip" and move it to your ADB Fastboot folder (for easy typing in cmd)
- Turn Off your phone - connect to pc with usb cable
- Hold vol up and then press power On button of your phone - Keep holding both buttons, it should went into Droidboot screen.
- Open command prompt (cmd) and go to your ADB Fastboot folder (e.g. cd C:\adb)
- Type the following 2 lines: "fastboot flash fastboot fastboot.img" and "fastboot flash boot boot.img" (look phone screen, should say successfully done for both)
- Scroll down(use volume keys) to recovery and select it(use power key) and your phone will reboot
- now that you are in recovery(you can see a droid symbol lying down with red triangle over its stomach)
- Hold Vol Down and press Vol up (menu should appear)
- Choose "Apply update from adb"
- From cmd above type "adb sideload rom.zip"
- Wipe cache/dat and reboot
But in "fastboot flash fastboot fastboot.img" it appear "device not found". I installed PDANet Desktop and some ajusts I could fix the USB problem.
(...)
What I've tried (Today):
- If I press vol up button and plug it on PC the LED light is blue and show the USB icon next the clock.
-When I open ADB terminal and type "fastboot devices" it returns YT910YCRMG
-When i tried to flash the new room through the Flashtool the follow message appear:
24/016/2015 21:16:47 - INFO - Device connected with USB debugging off
24/016/2015 21:16:47 - INFO - For 2011 devices line, be sure you are not in MTP mode
I'm sure that the customer doesn't turned the debugging on (he don't know what is this). There is a way to turn debugging on the device in the current situation?
I can't apply the same tutorial from asus because there's no fastboot.img and boot.img files inside the Sony rom .TFT.
Some suggestions? I really appreciate some suggestions.
Thank you

Updates:
I've tried via Flashtool > fastboot mode (by holding vol UP button) install the kernel.sin (extracted from the rom) but it leads to the follows errors:
By "Version 1.0" > (Select Kernel to Hotboot)
03/059/2015 22:59:21 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\nada\.flashTool\firmwares\kernel.sin
03/059/2015 22:59:21 - INFO - Flashing selected kernel
03/059/2015 22:59:22 - INFO - sending 'boot' (9261 KB)...
03/059/2015 22:59:22 - INFO - OKAY [ 0.313s]
03/059/2015 22:59:22 - INFO - writing 'boot'...
03/059/2015 22:59:22 - INFO - FAILED (remote: Command not allowed)
03/059/2015 22:59:22 - INFO - finished. total time: 0.316s
03/059/2015 22:59:22 - INFO - FASTBOOT Output:
sending 'boot' (9261 KB)...
OKAY [ 0.313s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.316s
Pelo By DooMLoRD > (Select Kernel to Flash)
03/059/2015 22:59:31 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\nada\.flashTool\firmwares\kernel.sin
03/059/2015 22:59:31 - INFO - HotBooting selected kernel
03/059/2015 22:59:32 - INFO - FASTBOOT Output:
creating boot image...
creating boot image - 9486336 bytes
downloading 'boot.img'...
OKAY [ 0.309s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.366s
After both ways the message continues over and over again...
3/059/2015 22:59:32 - INFO - Device disconnected
03/059/2015 22:59:34 - INFO - Device connected with USB debugging off
03/059/2015 22:59:34 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:41 - INFO - Device disconnected
03/059/2015 22:59:43 - INFO - Device connected with USB debugging off
03/059/2015 22:59:43 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:51 - INFO - Device disconnected
03/059/2015 22:59:52 - INFO - Device connected with USB debugging off
03/059/2015 22:59:52 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:53 - INFO - Device disconnected
There's some mode to apply USB debugging with device bricked? The phone don't passes from the sony logo. It is stuck on bootloop.

hey there!just so happen to see your post.so,why not try to help you out..& i hope i'm not too late for this!hehe..anyways,here's what i could suggest by checking this link out("the rubber band trick"):
http://forum.xda-developers.com/showthread.php?p=33032165
big thanx to @Toledo_JAB!(way to go,man!thanx again a lot!)

Thank you for the reply. I will try this and post the results soon.

sure thing! that link i just shared with you should possitively resolve your issue! and remember,patience is a virtue..good luck! :good:

Arturiuz! said:
sure thing! that link i just shared with you should possitively resolve your issue! and remember,patience is a virtue..good luck! :good:
Click to expand...
Click to collapse
Thank you very much for the support. I really appreciate it.
I've tried the rubber suggestion: 2 days in wall charger plus 1 day plugged in PC with rubber and no answer.
I think is probably a hardware damage. Too sad.

Xperia SP- Bricked After Trying To Flash CM12.1?

Did I brick it?
So my sweet old SP seems kinda in between the kinds of bricks I find on this forum, so before giving elaborate background stories, this is the condition my phone is in after attempting to flash CM12.1 (first time doing such things which was probably what went wrong):
Without power cable, turning device on gives one short buzz, volume up + power button the same and a blue flash volume down a green flash. Thats all they do, black screen and no signs of life afterwards.
Now with power cable connected to my PC and powering up while holding one of the volume buttons it is recognised on the PC (unknown device in the device manager). I downloaded FlashTool, which whined about drivers but those couldn't install for some reason, so I unpacked the installer and manually installed what I thought were the correct drivers.
Now FlashTool sees the device connected in FlashMode (curiously disconects and reconnects every minute) or Fast Bootmode (whatever those mean, I'm a noob and yeah I hate myself) but I cant actually flash anything.
Is there hope? Or did I screw up?
Thank you very much for even reading my pathetic plea.

Have you tried using PC Companion to restore your phone? Maybe your phone doesn't have enough charge, that might be what's preventing Flashtool from working properly.

Plum Crazy said:
Have you tried using PC Companion to restore your phone? Maybe your phone doesn't have enough charge, that might be what's preventing Flashtool from working properly.
Click to expand...
Click to collapse
I'll try it, but when I started flashing I had 100% and last time I (could) check it was still around 90%.
UPDATE: Charging makes green led burn, also I find it strange that PC companion didn't recognise the phone as being a phone either

28/007/2015 10:07:30 - INFO - Device connected in flash mode
28/007/2015 10:07:37 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.207. Customization : T-Mobile NL
28/007/2015 10:07:37 - INFO - Preparing files for flashing
28/008/2015 10:08:02 - INFO - Please connect your device into flashmode.
28/008/2015 10:08:04 - INFO - Opening device for R/W
28/008/2015 10:08:04 - INFO - Reading device information
28/008/2015 10:08:04 - INFO - Unable to read from phone after having opened it.
28/008/2015 10:08:04 - INFO - trying to continue anyway
28/008/2015 10:08:05 - INFO - Start Flashing
28/008/2015 10:08:05 - INFO - Processing loader.sin
28/008/2015 10:08:05 - INFO - Checking header
28/008/2015 10:08:05 - ERROR - Processing of loader.sin finished with errors.
28/008/2015 10:08:05 - INFO - Ending flash session
28/008/2015 10:08:05 - ERROR - Error in processHeader : 1 : Onjuiste functie.
28/008/2015 10:08:05 - ERROR - Error flashing. Aborted

Hmm, I just tried to flash it using the fastboot mode since that connection seems much more stable. Now I get this:
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:186) - Selected kernel (boot.img or kernel.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:187) - Flashing selected kernel
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (1147743 KB)...
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:190) - FASTBOOT Output:
sending 'boot' (1147743 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:191) - Please check the log before rebooting into system
28/031/2015 10:31:48 - INFO - (FastbootToolbox.java:136) - Now plug your device in Fastboot Mode
28/031/2015 10:31:49 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:209) - Selected system (system.img or system.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:210) - Flashing selected system
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - sending 'system' (1147743 KB)...
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - FAILED (remote: The Device must be rooted first)
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - finished. total time: 0.007s
28/032/2015 10:32:02 - INFO - (FastBootToolBoxJob.java:213) - Please check the log before rebooting into system
My phone unrooted itself? :crying: Can I even root it again without a functioning OS on it?

Raven5887 said:
Hmm, I just tried to flash it using the fastboot mode since that connection seems much more stable. Now I get this:
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:186) - Selected kernel (boot.img or kernel.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:187) - Flashing selected kernel
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (1147743 KB)...
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:190) - FASTBOOT Output:
sending 'boot' (1147743 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:191) - Please check the log before rebooting into system
28/031/2015 10:31:48 - INFO - (FastbootToolbox.java:136) - Now plug your device in Fastboot Mode
28/031/2015 10:31:49 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:209) - Selected system (system.img or system.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:210) - Flashing selected system
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - sending 'system' (1147743 KB)...
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - FAILED (remote: The Device must be rooted first)
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - finished. total time: 0.007s
28/032/2015 10:32:02 - INFO - (FastBootToolBoxJob.java:213) - Please check the log before rebooting into system
My phone unrooted itself? :crying: Can I even root it again without a functioning OS on it?
Click to expand...
Click to collapse
Try on another PC with another cable. Preferably on Windows 7.

Phoenix854 said:
Try on another PC with another cable. Preferably on Windows 7.
Click to expand...
Click to collapse
Somehow this did the trick... I could update the drivers directly and everything just worked.
Many thanks!

zr bricked

My phone don't open to system or show anything on screen .. just a red led and open flash mode and fast boot but can't flash any thing there are a problem in boot loader
message when flash anything from flash mode
12/039/2017 00:39:11 - INFO - Processing loader.sin
12/039/2017 00:39:11 - INFO - Checking header
12/039/2017 00:39:11 - INFO - Flashing data
12/039/2017 00:39:11 - INFO - Processing of loader.sin finished.
12/039/2017 00:39:13 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_39 / Boot version : / Bootloader status : NOT_ROOTABLE
12/039/2017 00:39:13 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0016";ERR_DYNAMIC="Invalid TA";
message when flash recovery or any thing from fastboot
12/037/2017 00:37:39 - INFO - Selected kernel (boot.img or kernel.sin): G:\sony\twrp-3.0.2-1-dogo.img
12/037/2017 00:37:39 - INFO - Flashing selected kernel
12/037/2017 00:37:40 - INFO - sending 'boot' (13064 KB)...
12/037/2017 00:37:40 - INFO - OKAY [ 0.451s]
12/037/2017 00:37:40 - INFO - writing 'boot'...
12/037/2017 00:37:40 - INFO - FAILED (remote: flash write failure)
12/037/2017 00:37:40 - INFO - finished. total time: 0.463s
12/037/2017 00:37:40 - INFO - FASTBOOT Output:
sending 'boot' (13064 KB)...
OKAY [ 0.451s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.463s
12/037/2017 00:37:40 - INFO - Please check the log before rebooting into system
my phone C5502 opened bootloader and official firmware 5.1.1 rooted by king root

Your bootloader unlocked or not?! Post ur questions in question forum!

sandeepxperia said:
Your bootloader unlocked or not?! Post ur questions in question forum!
Click to expand...
Click to collapse
unlocked

elzawy said:
unlocked
Click to expand...
Click to collapse
Did u unlocked the bootloader successfully and installed twrp recovery before bricking?

sandeepxperia said:
Did u unlocked the bootloader successfully and installed twrp recovery before bricking?
Click to expand...
Click to collapse
yes