Database Develop

[Q] xperia v bootloop-problems with bootloader-fastboot

Hello and good day.
i hope i can find here some help.
SHORT FACTS AT THE END OF THE POST
my phone went to bootloop after i applyed a backup i made with titanium backup.
sadly, i also restored all system files and my phone went to bootloop when i restarted.
xperia v lt25i with fastboot installed and the bootloader is unlocked.
so as much as i know connecting it to the pc pressing the volume button down the green light goes on and it should be the fastboot mode.
pressing the volume button up and the light goes blue should be the bootloader.
the problem is the phone only stays for 2 secounds in this mode and then going into the battery load mode.
this leaves not much time to install the device drivers on the PC (windows vista)
i managed to install the fastboot driver and now the phone stays +30 secounds in fastboot mode and switches then into the battery mode.
if i try to install the bootloader drivers for the device, he tryes but aborts the install saying "wrong parameter".
during the install he switches from the bootloader into the battery mode.
i installed the android sdk, flashtool(sony mobile flasher), universal adb driver, sony update service,sony pc companion.
sony updateservice says the OS is modified and refuses to update.
the sony pc companion repair function only seems to work with a started phone.
also i somehow manage to get the update/repair function started but it suddenly closes when it downloads/prepares the operation.
connected with active bootloop to the pc he finds the LT25i and wants to install the drivers "sony sa0106 ADB driver interface" but aborts with the reason "wrong parameter"
I had this too before i puted my phone into bootloop.
seems normal coz sony pc companion needs to install the drivers on its own.
when i go into the fastboot mode and open the sony mobile flasher, select in the fastboot toolbox to check the current device status he isnt doing anything.
in the android sdk using the fasstboot tool over the console he shows nothing when giving the "fastboot devices" command.
with "fastboot update" or "fastboot continue" he says "waiting for device" but gets stuck in it.
please if you have any advice what i can do or try or even a solution on my problem let me know.
i would be very happy to solve this problem.
-----
iam a total noob when it comes to programing but 4 days ago i succesfully repaired the phone with a broken touch-lcd screen.
so if a possible solution requires a hardware mod-hack i have good experiance with even soldering smd components with a solder-needle.
LONG SHORT :
bootloop
Bootloader driver doesnt install on the PC.
Fastboot seems to give no response to commands.(in the windows device manager the device is installed as "SEMC flash device")
EDIT:Still trying to get the driver for the flashmode installed with the error "wrong parameter".
may seems to be a windows problem, maybe caused by old driver garbage but i have no solutuion.
How do i get the phone operational again?
Thank you for your time.

First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack

thanks for your reply
nlooooo said:
First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack
Click to expand...
Click to collapse
i deleted some drivers and reinstalled flashtool and the flashtool driverpack.
the s1bootloader or fastboot is now listed in the devicemanager as SEMC flashdevice.
flashtool recognizes the phone in flashmode but gets disconnected after +-40 secounds and then reconnects.
strangely....he now is performing the flash operation.
reading and writing data to the phone or at least trying to do the operation.
the phone is now connected without battery and is off.
no lights on and the screen is dark.
i will wait for the operation to complet.
is this normal??
is it flashing now? or can i abort the operation?
28/035/2014 20:35:22 - INFO - (MainSWT.java:130) - Device connected in flash mode
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\LT25i_9.2.A.1.210_1270-7096_R2J Customized SG.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : system.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : fotakernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_2.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cust-reset.ta
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_1.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : partition-image.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : apps_log.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : tzbsp.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fsg.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : userdata.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cache.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\X10_V1_BLRelock.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : s1boot.sin
28/035/2014 20:35:39 - INFO - (MainSWT.java:1020) - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/035/2014 20:35:39 - INFO - (Bundle.java:406) - Preparing files for flashing
28/035/2014 20:35:39 - DEBUG - (Bundle.java:416) - Created the prepared folder
28/035/2014 20:35:39 - DEBUG - (Bundle.java:325) - Saving entry system.sin to disk
28/035/2014 20:35:39 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : system.sin
28/035/2014 20:35:39 - DEBUG - (Bundle.java:329) - Writing Entry to .\firmwares\prepared\system.sin
28/036/2014 20:36:04 - INFO - (MainSWT.java:126) - Device disconnected
28/036/2014 20:36:08 - INFO - (MainSWT.java:130) - Device connected in flash mode
It broke the operation -.-
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [09, 58, 2F, 8D]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2777 of 16305
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [1F, A6, 11, 1C]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2778 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [C5, B5, C2, 78]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2779 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [08, 8D, FE, AE]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2780 of 16305
28/046/2014 20:46:39 - DEBUG - (MyLogger.java:100) - <- This level is successfully initialized
28/046/2014 20:46:39 - INFO - <- This level is successfully initialized
28/047/2014 20:47:27 - ERROR - Processing of system.sin finished with errors.
28/047/2014 20:47:27 - INFO - Ending flash session
28/047/2014 20:47:27 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
when connected clicking on BLU the bootloader unlock he manages to read some stats
28/052/2014 20:52:57 - INFO - Device connected in flash mode
28/053/2014 20:53:09 - INFO - Please connect your device into flashmode.
28/053/2014 20:53:10 - INFO - Opening device for R/W
28/053/2014 20:53:10 - INFO - Reading device information
28/053/2014 20:53:10 - INFO - Phone ready for flashmode operations.
28/053/2014 20:53:10 - INFO - Current device : LT25i - BX903HDWG2 - 1268-5967_R4I - 1264-2336_9.1.A.1.140 - GLOBAL-LTE_9.1.A.1.140
28/053/2014 20:53:10 - INFO - Processing loader.sin
28/053/2014 20:53:10 - INFO - Checking header
28/053/2014 20:53:10 - INFO - Flashing data
28/053/2014 20:53:10 - INFO - Processing of loader.sin finished.
28/053/2014 20:53:15 - INFO - Loader : S1_Root_7054 - Version : R5A058 / Boot version : R11A023 / Bootloader status : ROOTED
28/053/2014 20:53:15 - INFO - Start Reading unit 000008B2
28/053/2014 20:53:15 - INFO - Reading TA finished.
28/053/2014 20:53:15 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\BX903HDWG2\ulcode.txt
28/053/2014 20:53:17 - INFO - Ending flash session
28/053/2014 20:53:17 - INFO - You can now unplug and restart your device
28/053/2014 20:53:17 - INFO - Device connected in flash mode
28/053/2014 20:53:18 - INFO - Device disconnected
28/053/2014 20:53:20 - INFO - Device connected in flash mode
but then again disconnects.
...all the time.
is it maybe a windows problem?
what can i try or do?

I'm not sure what you have done but this is the correct procedure:
- First of all copy downloaded ftf file to folder c:\Program Files (x86)\Flashtool\firmwares\
- Start flashtool without phone connected to PC.
- Click on thunder icon.
- Choose Flashmode in given list.
- In next window (Firmware selector) choose ftf file you copied to firmware folder, tick to wipe all given options (APPSLOG, CACHE, DATA) and tick 'No final verification.
- Click on Flash and wait for files to be prepared.
- When dialog box appear connect your phone (powered off) to USB cable holding volume down.
- Green led with appear for moment and then it will go off.
- Wait for the process to be finished.

yes yes
he goes into flashmode and so on but after +- 40 secounds he automaticly exits the flashmode the sony sign appears on the screen and the green lamp goes off then starting again in flashmode.
so he periodicaly disconnects the phone and reconnects.
it doesnt matter if i touch the phone or not, so it isnt a broken cable problem.
28/047/2014 21:47:34 - INFO - Device disconnected
28/048/2014 21:48:19 - INFO - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/048/2014 21:48:19 - INFO - Preparing files for flashing
28/048/2014 21:48:28 - INFO - Device connected in flash mode
28/048/2014 21:48:53 - INFO - Please connect your device into flashmode.
28/048/2014 21:48:54 - INFO - Opening device for R/W
28/048/2014 21:48:54 - INFO - Reading device information
28/049/2014 21:49:10 - INFO - Unable to read from phone after having opened it.
28/049/2014 21:49:10 - INFO - trying to continue anyway
28/049/2014 21:49:10 - INFO - Start Flashing
28/049/2014 21:49:10 - INFO - Processing loader.sin
28/049/2014 21:49:10 - INFO - Checking header
28/049/2014 21:49:11 - ERROR - Processing of loader.sin finished with errors.
28/049/2014 21:49:11 - INFO - Ending flash session
28/049/2014 21:49:11 - ERROR - Error in processHeader : 995 : Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.
28/049/2014 21:49:11 - ERROR - Error flashing. Aborted
28/049/2014 21:49:11 - INFO - Device disconnected

Have you tried with Sony Update Service now when you have drivers installed?

28/004/2014 22:04:41 - INFO - Processing of apps_log.sin finished.
28/004/2014 22:04:41 - INFO - Processing cache.sin
28/004/2014 22:04:41 - INFO - Checking header
28/004/2014 22:04:41 - INFO - Flashing data
28/004/2014 22:04:42 - INFO - Processing of cache.sin finished.
28/004/2014 22:04:42 - INFO - Processing system.sin
28/004/2014 22:04:42 - INFO - Checking header
28/004/2014 22:04:42 - INFO - Flashing data
28/005/2014 22:05:09 - ERROR - Processing of system.sin finished with errors.
28/005/2014 22:05:09 - INFO - Ending flash session
28/005/2014 22:05:09 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
Sony update service says the device contains modified data for which no update is available.
is there a tool with which i can read the phone operations?
during the flash operation when the phone is off it suddenly switches back on, as i said showing the sony logo on the screen.
interessting after the last try to flash he now stays in the flashmode and now for over 5 mins.
i tried again but he stoped showing this :
28/015/2014 22:15:45 - INFO - (FlashJob.java:33) - Please connect your device into flashmode.
28/015/2014 22:15:46 - INFO - (USBFlashWin32.java:16) - Opening device for R/W
28/015/2014 22:15:46 - INFO - (X10flash.java:594) - Reading device information
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/015/2014 22:15:46 - INFO - (X10flash.java:606) - Unable to read from phone after having opened it.
28/015/2014 22:15:46 - INFO - (X10flash.java:607) - trying to continue anyway
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - INFO - (X10flash.java:484) - Start Flashing
28/015/2014 22:15:46 - INFO - (X10flash.java:237) - Processing loader.sin
28/015/2014 22:15:46 - DEBUG - (X10flash.java:238) - loader.sin : header size : 1020
28/015/2014 22:15:46 - INFO - (X10flash.java:216) - Checking header
28/015/2014 22:15:46 - DEBUG - (X10flash.java:220) - Sending part 1 of 1
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:252) - Processing of loader.sin finished with errors.
28/015/2014 22:15:46 - INFO - (X10flash.java:544) - Ending flash session
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:517) - Error in processHeader : 6 : Das Handle ist ungültig.
28/015/2014 22:15:46 - ERROR - (X10flash.java:518) - Error flashing. Aborted
28/015/2014 22:15:46 - INFO - (MainSWT.java:130) - Device connected in flash mode

Which version of flashtool do you use?

version 0.9.15.0
i dont think its the tool.
what could be the reason for the phone to continiusly bootloop in flashmode??

WHY?!?
WHAT THE HELL AM I DOING WRONG?!?
it was to 3/4 finished flashing and then....
what does the error mean?
block verification failed?
iam using now the latest flashtool and the Xperia V_9.1.A.1.140_1270-9887_R1I_CE.ftf
what could be the reason for it to just break the flashing???
my god it was almost finished!!
29/038/2014 13:38:46 - INFO - Processing of cache.sin finished.
29/038/2014 13:38:46 - INFO - Processing system.sin
29/038/2014 13:38:46 - INFO - Checking header
29/038/2014 13:38:46 - INFO - Flashing data
29/049/2014 13:49:29 - ERROR - Processing of system.sin finished with errors.
29/049/2014 13:49:29 - INFO - Ending flash session
29/049/2014 13:49:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
edit:
well at least the flashing seems to have a effect.
the phone gets stuck at the sony logo and doesnt permanently reboot.

Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running

You probably broke something from system files.
One more question, is your bootloader unlocked?
EDIT:
Ok, I red the first post again, it is unlocked, you have to relock it first for SUS and PCC to work.

okay? i suppose i can lock and unlock it as often as i want?
thanks a lot guys
you are the best
EDIT:
okay, locked it PCC doesnt work but SUS seems to work now
again thanks ))

Dr CAT said:
Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running
Click to expand...
Click to collapse
how did you solve it? can you please tell me? i have problems on xperia t.

-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys

Dr CAT said:
-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys
Click to expand...
Click to collapse
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin

isko95 said:
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin
Click to expand...
Click to collapse
flashtool brings its own drivers it needs.
in the flashtool folder is one called drivers, you can install them from there.
the new 4.3 ftf just aborted and even the 4.1 ftf which worked before.
so i think its trail and error and pray that it works the next time^^
-.- and again .....

There's one more thing, try to install INF file from Sony Unlock page.

HELP issue when try to flash and relock (C5303 ULB)

I did a clean install of CM 12.1 and after y tried to flash a Stock Rom (ftf) but i couldn't do that.
Show this log.
I only want relock bootloader (that i can't. With adb i give an error and with Flashtool the progress stop when y click on relock)
CM12.1 and kernel of the Rom
1- First try
13/003/2015 04:03:07 - INFO - Device connected in flash mode
13/003/2015 04:03:22 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.0.A.2.254. Customization : Customized CE4
13/003/2015 04:03:22 - INFO - Preparing files for flashing
13/003/2015 04:03:36 - INFO - Please connect your device into flashmode.
13/003/2015 04:03:37 - INFO - Opening device for R/W
13/003/2015 04:03:37 - INFO - Reading device information
13/003/2015 04:03:48 - INFO - Unable to read from phone after having opened it.
13/003/2015 04:03:48 - INFO - trying to continue anyway
13/003/2015 04:03:48 - INFO - Start Flashing
13/003/2015 04:03:51 - INFO - Processing loader.sin
13/003/2015 04:03:51 - INFO - Checking header
13/003/2015 04:03:51 - ERROR - Processing of loader.sin finished with errors.
13/003/2015 04:03:51 - INFO - Ending flash session
13/003/2015 04:03:51 - ERROR - Error in processHeader : 22 : El dispositivo no reconoce el comando.
13/003/2015 04:03:51 - ERROR - Error flashing. Aborted
13/003/2015 04:03:51 - INFO - Device disconnected
Click to expand...
Click to collapse
2- Second try
13/018/2015 04:18:39 - INFO - Preparing files for flashing
13/018/2015 04:18:47 - INFO - Device connected in flash mode
13/018/2015 04:18:49 - INFO - Please connect your device into flashmode.
13/018/2015 04:18:50 - INFO - Opening device for R/W
13/018/2015 04:18:50 - INFO - Reading device information
13/018/2015 04:18:50 - INFO - Phone ready for flashmode operations.
13/018/2015 04:18:50 - INFO - Opening TA partition 2
13/018/2015 04:18:50 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT910M945P - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
13/018/2015 04:18:50 - INFO - Closing TA partition
13/018/2015 04:18:50 - INFO - Start Flashing
13/018/2015 04:18:52 - INFO - Processing loader.sin
13/018/2015 04:18:52 - INFO - Checking header
13/018/2015 04:18:53 - INFO - Flashing data
13/018/2015 04:18:58 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B023 / Bootloader status : ROOTED
13/018/2015 04:18:58 - INFO - Transfer buffer size : 32768
13/018/2015 04:18:58 - INFO - You must have the according fsc script to flash this device.
13/018/2015 04:18:58 - INFO - Flashing finished.
13/018/2015 04:18:58 - INFO - Please unplug and start your phone
13/018/2015 04:18:58 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Click to expand...
Click to collapse
I can't flash anything and cant relock bootloader for use PC Companion.
¿What can i do?
Depending of the rom that i install, i can do it or not.
If i flash a kernel via fastboot with recovery i can install a diferent rom, but i continue without can relock bootloader or flash a .ftf
Always gime me the same error, the "fsc script"
Also, i say that when Flashtool "start" to flash, my C5303 power off the green light, and when Flashtool stop of trying flash, the light power on again.
PD: Can't flash the file for relock bootloader and can't relock bootloader with adb.
This happend when try to relock. (Relock button clicked and green bar stopped)
oi57. tinypic. com/wb9tnd .jpg
(link with spaces)

Try the 0.9.18.5 version, I faced some issues on the latest version of Flashtool a month ago. But this one worked.
So give it a try.

BD.Zenith said:
Try the 0.9.18.5 version, I faced some issues on the latest version of Flashtool a month ago. But this one worked.
So give it a try.
Click to expand...
Click to collapse
Thanks, that was the problem :/

Welcome,
Glad I could help

Z3C stucked in flashtool

Hi, I tried to flash Z3C to Marshmallow. I did it exactly as here: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
Everything went perfect, but it stucked here:
10/029/2016 14:29:31 - INFO - Flashtool Version 0.9.21.0 built on 28-04-2016 22:00:00
10/029/2016 14:29:31 - INFO - Executing search strategies to find proxy selector
10/029/2016 14:29:31 - INFO - No proxy found for IE. Trying next one
10/029/2016 14:29:31 - INFO - Strategy firefox failed trying next one : No Firefox installation found
10/029/2016 14:29:31 - INFO - No proxy found for java. Trying next one
10/029/2016 14:29:31 - INFO - Syncing devices from github
10/029/2016 14:29:32 - INFO - Opening devices repository.
10/029/2016 14:29:32 - INFO - Scanning devices folder for changes.
10/029/2016 14:29:46 - INFO - Pulling changes from github.
10/029/2016 14:29:46 - INFO - Quietly closing devices repository.
10/029/2016 14:29:46 - INFO - Devices sync finished.
10/029/2016 14:29:47 - INFO - Loading devices database
10/029/2016 14:29:47 - INFO - Loaded 88 devices
10/029/2016 14:29:47 - INFO - Starting phone detection
10/029/2016 14:29:51 - INFO - Device disconnected
10/030/2016 14:30:11 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.5.A.0.570. Customization : RU
10/030/2016 14:30:11 - INFO - Preparing files for flashing
10/032/2016 14:32:15 - INFO - Please connect your device into flashmode.
10/032/2016 14:32:40 - INFO - Device connected in flash mode
10/032/2016 14:32:40 - INFO - Opening device for R/W
10/032/2016 14:32:41 - INFO - Reading device information
10/032/2016 14:32:41 - INFO - Phone ready for flashmode operations.
10/032/2016 14:32:41 - INFO - Opening TA partition 2
10/032/2016 14:32:41 - INFO - Current device : D5803 - YT910Y4UXB - 1289-4463_R7C - 1285-6521_23.4.A.1.264 - GLOBAL-LTE_23.4.A.1.264
10/032/2016 14:32:41 - INFO - Closing TA partition
10/032/2016 14:32:41 - INFO - Start Flashing
10/032/2016 14:32:41 - INFO - Processing loader.sin
10/032/2016 14:32:41 - INFO - Checking header
10/032/2016 14:32:41 - INFO - Flashing data
10/032/2016 14:32:41 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_L_37 / Bootloader status : ROOTABLE
10/032/2016 14:32:41 - INFO - Max packet size set to 512K
10/032/2016 14:32:41 - INFO - USB buffer size set to 256K
10/032/2016 14:32:51 - INFO - Parsing boot delivery
10/033/2016 14:33:12 - INFO - No flash script found. Using 0.9.18 flash engine
10/033/2016 14:33:12 - INFO - Opening TA partition 2
10/033/2016 14:33:12 - INFO - Writing TA unit 00002774. Value : 01
10/033/2016 14:33:13 - INFO - Closing TA partition
10/033/2016 14:33:13 - INFO - Processing partition.sin
10/033/2016 14:33:13 - INFO - Checking header
10/033/2016 14:33:13 - INFO - Flashing data
10/033/2016 14:33:13 - INFO - Phone boot version : S1_Boot_MSM8974AC_LA3.0_L_37. Boot delivery version : S1_Boot_MSM8974AC_LA3.0_M_2
10/033/2016 14:33:13 - INFO - Going to flash boot delivery
10/033/2016 14:33:13 - INFO - Opening TA partition 2
10/033/2016 14:33:13 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:13 - INFO - Checking header
10/033/2016 14:33:13 - INFO - Flashing data
10/033/2016 14:33:13 - INFO - Closing TA partition
10/033/2016 14:33:13 - INFO - Opening TA partition 2
10/033/2016 14:33:13 - INFO - Flashing Aries_S1BootConfig_MiscTA.ta to partition 2
10/033/2016 14:33:13 - INFO - Writing TA unit 0000084F. Value : 1A CE 28 00 01 00 06 05 00 02 02 08 00 10 03 00 02 04 02 05 00 01 03 02 00 10 05 00 03 03 05 00 10 05 00 05 83 02 00 10 02 00 05 85 12 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
10/033/2016 14:33:13 - INFO - Writing TA unit 000008FD. Value : 00
10/033/2016 14:33:13 - INFO - Closing TA partition
10/033/2016 14:33:13 - INFO - Opening TA partition 2
10/033/2016 14:33:13 - INFO - Processing sbl1_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:13 - INFO - Checking header
10/033/2016 14:33:13 - INFO - Flashing data
10/033/2016 14:33:13 - INFO - Processing rpm_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:13 - INFO - Checking header
10/033/2016 14:33:13 - INFO - Flashing data
10/033/2016 14:33:13 - INFO - Processing tz_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:13 - INFO - Checking header
10/033/2016 14:33:13 - INFO - Flashing data
10/033/2016 14:33:14 - INFO - Processing s1sbl_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:14 - INFO - Checking header
10/033/2016 14:33:14 - INFO - Flashing data
10/033/2016 14:33:14 - INFO - Processing dbi_S1_Boot_MSM8974AC_LA3_0_M_2_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID12-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
10/033/2016 14:33:14 - INFO - Checking header
10/033/2016 14:33:14 - INFO - Flashing data
10/033/2016 14:33:14 - INFO - Closing TA partition
10/033/2016 14:33:14 - INFO - Opening TA partition 2
10/033/2016 14:33:16 - INFO - Closing TA partition
10/033/2016 14:33:16 - INFO - Opening TA partition 2
10/033/2016 14:33:16 - INFO - Processing amss_fsg.sin
10/033/2016 14:33:16 - INFO - Checking header
10/033/2016 14:33:16 - INFO - Flashing data
10/033/2016 14:33:16 - INFO - Processing amss_fs_1.sin
10/033/2016 14:33:16 - INFO - Checking header
10/033/2016 14:33:16 - INFO - Flashing data
10/033/2016 14:33:16 - INFO - Processing amss_fs_2.sin
10/033/2016 14:33:16 - INFO - Checking header
10/033/2016 14:33:16 - INFO - Flashing data
10/033/2016 14:33:16 - INFO - Processing apps_log.sin
10/033/2016 14:33:16 - INFO - Checking header
10/033/2016 14:33:16 - INFO - Flashing data
10/033/2016 14:33:16 - INFO - Processing cache.sin
10/033/2016 14:33:16 - INFO - Checking header
10/033/2016 14:33:16 - INFO - Flashing data
10/033/2016 14:33:18 - INFO - Processing fotakernel.sin
10/033/2016 14:33:18 - INFO - Checking header
10/033/2016 14:33:18 - INFO - Flashing data
10/033/2016 14:33:20 - INFO - Processing kernel.sin
10/033/2016 14:33:20 - INFO - Checking header
10/033/2016 14:33:20 - INFO - Flashing data
10/033/2016 14:33:22 - INFO - Closing TA partition
10/033/2016 14:33:22 - INFO - Opening TA partition 2
10/033/2016 14:33:24 - INFO - Processing system.sin
10/033/2016 14:33:24 - INFO - Checking header
10/033/2016 14:33:24 - INFO - Flashing data
Its beed 40 minutes like here and now I dont know what to do. Can I disconnect it? Or what can I do? Thanks

Ne_X_uS said:
Hi, I tried to flash Z3C to Marshmallow. what can I do? Thanks
Click to expand...
Click to collapse
As it doesn't give any errors then it should have worked, unless you unplugged it before it finished?
The flash takes quite a long time.
Did you make sure you got the right firmware for the right model D5803 or D5833?
Download a different firmware and try again, perhaps that TFT has a problem?
Hold the power button + volume up until it vibrates three times to turn it off.

Didgesteve said:
As it doesn't give any errors then it should have worked, unless you unplugged it before it finished?
The flash takes quite a long time.
Did you make sure you got the right firmware for the right model D5803 or D5833?
Download a different firmware and try again, perhaps that TFT has a problem?
Hold the power button + volume up until it vibrates three times to turn it off.
Click to expand...
Click to collapse
But flash takes like 20 minutes, this was stucked on same thing for 50 minutes, so I suppose it is stucked. Well, thats what I thought - Im downloading 5.1.1. and I will try flash it.
Yes, and I turned it off by clicking power button +volume up (just random clicking took me here ^^).
So, I will let you know if stock 5.1.1. is working or not

I see where can be the problem. In tutorial from xda is not mentioned, that u have to enable USB debugging and unknown sources..I think I do not have enabled it. I just read it from another tutorial. Well, I cant boot phone, so what can I do now?

Ne_X_uS said:
I see where can be the problem. In tutorial from xda is not mentioned, that u have to enable USB debugging and unknown sources..I think I do not have enabled it. I just read it from another tutorial. Well, I cant boot phone, so what can I do now?
Click to expand...
Click to collapse
Try with PC Companion.
Don't click upgrade as it will give 'unknown device' error, follow the instructions here

Didgesteve said:
Try with PC Companion.
Don't click upgrade as it will give 'unknown device' error, follow the instructions here
Click to expand...
Click to collapse
I will try it. It downloading softwere in PC companion , so it tooks another hour to download and still not sure if it can works. But I hope so

Ne_X_uS said:
I will try it. It downloading softwere in PC companion , so it tooks another hour to download and still not sure if it can works. But I hope so
Click to expand...
Click to collapse
PC Companion saved my phone once.
Just follow the instructions.

Didgesteve said:
PC Companion saved my phone once.
Just follow the instructions.
Click to expand...
Click to collapse
Ya, PC companion worked and phone booted, THANKS! But I tried flash it again, and its again stucked..So, I give it up and going to flash via PC Companion and wait for OTA update

Ne_X_uS said:
Ya, PC companion worked and phone booted, THANKS! But I tried flash it again, and its again stucked..So, I give it up and going to flash via PC Companion and wait for OTA update
Click to expand...
Click to collapse
You could follow this guide on how to root.
Downgrade your build, root it, add recovery, then flash a pre-rooted MM build.
That way you'll get the MM build and not have to unlock your bootloader.
It seems like a lot of trouble to get the latest bug ridden and problematic OS. Once you have it installed you can join the big line of complaints on the threads at the moment about how it's broken.
TBH I think MM is more trouble than it's worth right now. Sony are about to release 'fix it' patch for MM, wait a couple of weeks for the developers to incorporate it into their roms, then it'll be worth switching.

Set USB buffer to Device Max. It's much faster

If me, I set usb buffer speed to 256. slow but no error
Sent from my D5833 using XDA-Developers mobile app

<Solved> Bricked Xperia T

I use my Xperia T for handling the verification codes sent by some websites, mainly so I don't encounter issues if the phone was lost.
The Xperia keyboard app stopped working and I was getting by using a different app, but it was annoying me so I decided to re-flash the 'LT30p_9.2.A.0.295_CE_Skyfall' stock rom I was already using back onto the phone.
For some reason the FlashTool v0.0.23.1 does not recognise the FTF file ??
So I thought I would flash the Lineage Mint Rom , however something went wrong and the phone will now only get to the Sony logo and stay there. Controls would not respond so I took the back off and disconnected battery for 20 minutes.
I then downloaded a generic version 'LT30p_9.2.A.0.295_Generic IT' which I managed to start to flash on to the phone except it failed on "Processing of system.sin failed with errors".
Downloaded a number of other LT30p roms, some were not recognized by Flashtool two were but failed with same error.
I managed to flash the generic rom by excluding system.sin but phone remains the same. I tried flashing just the system.sin which fails with same error.
Any suggestions or ideas would be greatly appreciated.
<Solved>
Un-installed current FlashTool and re-installed older v0.9.18.3.
All FTFs recognised by older version
disconnected battery and successfully Flashed my preferred FTF.
Reconnected battery Phone boots and works fine.
Error log
- INFO - (X10flash.java:306) - Processing system.sin
- INFO - (X10flash.java:288) - Checking header
- DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
- DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 5 / Flags : false,true,false / Data length : 88850 / Data CRC32 : E5 C4 58 CD
- DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
- DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
- (USBFlashWin32.java:51) - Writing packet to phone
- DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
- DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
- DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 7 / Flags : false,false,false / Data length : 70 / Data CRC32 : 6D 26 B5 E9
- ERROR - (X10flash.java:326) - Processing of system.sin finished with errors.
- INFO - (X10flash.java:910) - Ending flash session
- DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
- DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
- DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
- DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
- ERROR - (X10flash.java:883) -
- ERROR - (X10flash.java:884) - Error flashing. Aborted
- INFO - (X10flash.java:727) - Flashing finished.

Hi,
I am still not making any progress with problem.
I have tried to hard brick reset method of disconnecting the battery and grounding the third test point pad - the phone responds but gives an undefined error.
Sony PC Companion just laughs and says "Unlocked Phone".
FlashTool can lock and unlock the phone as many times as I like.
I still get an error flashing System.sin
Does no one have any idea what the problem is ?

One thought is...
Would protecting the phone with Avast anti-theft be preventing the system.sin flashing ?
If so does any one have any idea of how to get around it ?

What state is my phone in right now?

I'm at a bit of a loss on what to do right now. I had an Xperia XP (F8132) which died on me, so I got a new one with warranty replacement. I had a TWRP backup of my entire old phone, so I did an official bootloader unlock of the new F8132, and then flashed the TWRP recovery. I then tried to restore the backup of my old phone and had everything selected, though it appeared to fail, saying something about the data partition not being flashed. Anyway, I decided to reboot the phone, only to find that it would not boot.
I can not get the phone into flashboot or recovery at all. As soon as I plug the phone into a computer, it will go into flashmode (green LED), regardless of what buttons are pressed. I've tried holding down the power and volume buttons for a soft/hard reset though neither seem to do anything. The screen doesn't power on either, so I can't tell what the power level is or whether the phone is on or off. Now, when I attempt to reset the phone, there are no vibrations or any indicators.
Nothing appears to happen when I plug the phone in to charge. I think it warms up a bit, but there are no LEDs. For the past few days, the phone has simply sat on my desk doing nothing.
In short, my phone appears to be bricked, and all I get is a green LED when I plug it into the computer. I've attempted to flash a stock FTF, but it fails every time with "Processing of partition.sin finished with errors". So...any advice?

Method1 : Maybe ftf error, try another one.
Method2: relock bootloader and use Xperia™ Companion to repair.
P.S. TWRP backup cannot cross drvice to recovery the data and system.

bkk99213 said:
Method1 : Maybe ftf error, try another one.
Method2: relock bootloader and use Xperia™ Companion to repair.
P.S. TWRP backup cannot cross drvice to recovery the data and system.
Click to expand...
Click to collapse
I've tried a few things, though none have worked so far.
I've tried using two different FTF files I've downloaded, and one that I bundled using Xperifirm and Flashtool but all give the same error. It appears that flashing will fail regardless of what I exclude, and even trying kernel.sin on its own doesn't work.
I am able to unlock and relock the bootloader using Flashtool, but I get a "getphoneinfofailure" UE_302 from Xperia companion, so that doesn't seem to work either.
I think this may have happened because I renamed my old TWRP backup to match the serial of my new device to try to restore it. I probably shouldn't have done that. I'm looking at the guide to "Recover 2012 and newer XPERIAs from SOFT-brick" by Toledo_JAB, but I can't quite tell what my battery level is at the moment. The phone has no reaction whatsoever normally, and no LEDs when plugged into a charger, but will enter flashmode whenever plugged into a computer.

Can you enter fastboot mode(blue LED) or TWRP?

bkk99213 said:
Can you enter fastboot mode(blue LED) or TWRP?
Click to expand...
Click to collapse
No, I'm unable to get the screen to power on in any way, so unable to get into recovery. Strangely, fastboot does not work either. Regardless of whether the volume up, volume down, or no button is held when I plug it into the computer, I get a green LED and it is recognised as being in flash mode by Flashtool.

Unlock/Relock bootloader need fastboot mode.
So, how can you relock bootloader and use Xperia™ Companion before？
If you can relock bootloader, that mean you can enter fastboot mode.

bkk99213 said:
Unlock/Relock bootloader need fastboot mode.
So, how can you relock bootloader and use Xperia™ Companion before？
If you can relock bootloader, that mean you can enter fastboot mode.
Click to expand...
Click to collapse
I originally unlocked the bootloader in fastboot, but that was when the phone was still functional.
I relocked the bootloader using Flashtool, while my phone was in flash mode.

Relock using flashtool....
For flashtool, when you relock, you also need enter fastboot mode. So, I think, your phone can enter fastboot mode.
Or ... Have you got the log when relock using flashtool?
Maybe relock is unsuccessful.

bkk99213 said:
Relock using flashtool....
For flashtool, when you relock, you also need enter fastboot mode. So, I think, your phone can enter fastboot mode.
Or ... Have you got the log when relock using flashtool?
Maybe relock is unsuccessful.
Click to expand...
Click to collapse
The LED on my phone remains green the whole time, and it appears to be successful in relocking and unlocking.
Code:
29/018/2017 17:18:08 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
29/018/2017 17:18:08 - INFO - Executing search strategies to find proxy selector
29/018/2017 17:18:08 - INFO - No proxy found for IE. Trying next one
29/018/2017 17:18:08 - INFO - Strategy firefox failed trying next one : No Firefox installation found
29/018/2017 17:18:09 - INFO - No proxy found for java. Trying next one
29/018/2017 17:18:09 - INFO - Syncing devices from github
29/018/2017 17:18:09 - INFO - Opening devices repository.
29/018/2017 17:18:09 - INFO - Scanning devices folder for changes.
29/018/2017 17:18:38 - INFO - Pulling changes from github.
29/018/2017 17:18:41 - INFO - Quietly closing devices repository.
29/018/2017 17:18:41 - INFO - Quietly closing devices repository.
29/018/2017 17:18:41 - WARN - close() called when useCnt is already zero
29/018/2017 17:18:41 - INFO - Devices sync finished.
29/018/2017 17:18:41 - INFO - Loading devices database
29/018/2017 17:18:41 - INFO - Loaded 98 devices
29/018/2017 17:18:41 - INFO - Starting phone detection
29/018/2017 17:18:46 - INFO - Device disconnected
29/018/2017 17:18:52 - INFO - Please connect your device into flashmode.
29/019/2017 17:19:04 - INFO - Device connected in flash mode
29/019/2017 17:19:05 - INFO - Opening device for R/W
29/019/2017 17:19:05 - INFO - Reading device information
29/019/2017 17:19:05 - INFO - Phone ready for flashmode operations.
29/019/2017 17:19:05 - INFO - Opening TA partition 2
29/019/2017 17:19:05 - INFO - Current device : F8131 - CB512B2JLN - 1302-6562_R2D - 1300-5317_41.2.A.2.223 - GENERIC_41.2.A.7.8
29/019/2017 17:19:05 - INFO - Closing TA partition
29/019/2017 17:19:05 - INFO - No loader in the bundle. Searching for one
29/019/2017 17:19:05 - INFO - No matching loader found
29/019/2017 17:19:05 - WARN - No loader found or set manually. Skipping loader
29/019/2017 17:19:05 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : NOT_ROOTABLE
29/019/2017 17:19:05 - INFO - Max packet size set to 4M
29/019/2017 17:19:05 - INFO - Opening TA partition 2
29/019/2017 17:19:05 - INFO - Start Reading unit 00 00 08 B2
29/019/2017 17:19:05 - INFO - Reading TA finished.
29/019/2017 17:19:05 - INFO - Closing TA partition
29/019/2017 17:19:06 - INFO - Unlock code saved to C:\Users\_____\.flashTool\registeredDevices\CB512B2JLN\ulcode.txt
29/019/2017 17:19:12 - INFO - Relocking device
29/019/2017 17:19:12 - INFO - Opening TA partition 2
29/019/2017 17:19:12 - INFO - Writing TA unit 000008B2. Value :
29/019/2017 17:19:12 - INFO - Closing TA partition
29/019/2017 17:19:12 - INFO - Relock finished
29/019/2017 17:19:16 - INFO - Ending flash session
29/019/2017 17:19:16 - INFO - You can now unplug and restart your device
29/019/2017 17:19:16 - INFO - Device connected in flash mode
29/019/2017 17:19:17 - INFO - Device disconnected
29/019/2017 17:19:22 - INFO - Device connected in flash mode
29/019/2017 17:19:22 - INFO - Please connect your device into flashmode.
29/019/2017 17:19:23 - INFO - Opening device for R/W
29/019/2017 17:19:23 - INFO - Reading device information
29/019/2017 17:19:23 - INFO - Phone ready for flashmode operations.
29/019/2017 17:19:23 - INFO - Opening TA partition 2
29/019/2017 17:19:23 - INFO - Current device : F8131 - CB512B2JLN - 1302-6562_R2D - 1300-5317_41.2.A.2.223 - GENERIC_41.2.A.7.8
29/019/2017 17:19:23 - INFO - Closing TA partition
29/019/2017 17:19:23 - INFO - No loader in the bundle. Searching for one
29/019/2017 17:19:23 - INFO - No matching loader found
29/019/2017 17:19:23 - WARN - No loader found or set manually. Skipping loader
29/019/2017 17:19:23 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : NOT_ROOTABLE
29/019/2017 17:19:23 - INFO - Max packet size set to 4M
29/019/2017 17:19:23 - INFO - Opening TA partition 2
29/019/2017 17:19:23 - INFO - Start Reading unit 00 00 08 B2
29/019/2017 17:19:23 - INFO - Reading TA finished.
29/019/2017 17:19:23 - INFO - Closing TA partition
29/019/2017 17:19:26 - INFO - Unlocking device
29/019/2017 17:19:26 - INFO - Opening TA partition 2
29/019/2017 17:19:26 - INFO - Writing TA unit 000008B2. Value : 45 42 35 38 39 33 42 42 31 44 45 43 39 39 41 32
29/019/2017 17:19:26 - INFO - Closing TA partition
29/019/2017 17:19:27 - INFO - Unlock finished
29/019/2017 17:19:29 - INFO - Ending flash session
29/019/2017 17:19:29 - INFO - You can now unplug and restart your device
29/019/2017 17:19:29 - INFO - Device connected in flash mode
29/019/2017 17:19:30 - INFO - Device disconnected
29/019/2017 17:19:35 - INFO - Device connected in flash mode

Bootloader status : NOT_ROOTABLE???
By Google, it say NOT_ROOTABLE cannot get unlock code
Any I got mistake, I also can unlock by flashmode.

It seems this might actually be a hard brick, or close to one. It doesn't appear to be recognised by Emma, the official Sony flash tool. And it seems to come up as some sort of "SOMC Flash Device" for drivers. The s1tool and test point emergency flash for older Xperia devices would be incredibly helpful now, but it doesn't seem to support any of the newer Xperia devices. Is there anything similar for the 2016 line to recover from a hard brick?