Database Develop

Help for not turning on after unlocking bootloader...

hi, i`ve tried to unlock bootloader , first i rooted it by clicking the icon of flashtool named "Root Device", and then when rooting is successfully done, i clicked the icon of flashtool named "BLU", but i didnt reboot at the end of unlocking, now i cant turn on the phone...
i really need your help, the phone is not mine, please help...

log
im using flashtool 0.9.13
Here`s the log:
31/019/2014 12:19:30 - INFO - <- This level is successfully initialized
31/019/2014 12:19:30 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
31/019/2014 12:19:35 - INFO - Device connected with USB debugging on
31/019/2014 12:19:37 - INFO - Connected device : SonyEricson X8
31/019/2014 12:19:37 - INFO - Installed version of busybox : N/A
31/019/2014 12:19:37 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/020/2014 12:20:47 - INFO - Decrypting C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue.enc to C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue
31/020/2014 12:20:58 - INFO - Pushing C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue to /data/local/tmp
31/020/2014 12:20:58 - INFO - Pushing C:\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
31/020/2014 12:20:59 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
31/021/2014 12:21:00 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
31/021/2014 12:21:02 - INFO - Running part1 of Root Exploit, please wait
31/021/2014 12:21:02 - INFO - Running rootit
31/021/2014 12:21:03 - INFO - Waiting for device. After 60secs, stop waiting will be forced
31/021/2014 12:21:04 - INFO - Device disconnected
31/021/2014 12:21:05 - INFO - Device connected with USB debugging on
31/021/2014 12:21:06 - INFO - Running part2 of Root Exploit
31/021/2014 12:21:06 - INFO - Running rootit2
31/021/2014 12:21:08 - INFO - Finished!.
31/021/2014 12:21:08 - INFO - Root should be available after reboot!
31/021/2014 12:21:08 - INFO - Device disconnected
31/021/2014 12:21:21 - INFO - Device connected with USB debugging off
31/021/2014 12:21:21 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/021/2014 12:21:24 - INFO - Device disconnected
31/021/2014 12:21:25 - INFO - Device connected with USB debugging on
31/021/2014 12:21:25 - INFO - Connected device : SonyEricson X8
31/021/2014 12:21:25 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
31/021/2014 12:21:25 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/021/2014 12:21:25 - INFO - Checking root access
31/021/2014 12:21:27 - INFO - Root Access Allowed
31/021/2014 12:21:27 - INFO - Installing toolbox to device...
31/021/2014 12:21:27 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
31/021/2014 12:21:27 - INFO - Running installftkit as root thru sysrun
31/022/2014 12:22:57 - INFO - Device disconnected
31/023/2014 12:23:01 - INFO - Device connected with USB debugging on
31/023/2014 12:23:01 - INFO - Connected device : SonyEricson X8
31/023/2014 12:23:02 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
31/023/2014 12:23:02 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/023/2014 12:23:02 - INFO - Checking root access
31/023/2014 12:23:04 - INFO - Root Access Allowed
31/023/2014 12:23:16 - INFO - Please connect your device into flashmode.
31/023/2014 12:23:20 - INFO - Device disconnected
31/024/2014 12:24:22 - INFO - Device connected in flash mode
31/024/2014 12:24:23 - INFO - Opening device for R/W
31/024/2014 12:24:23 - INFO - Reading device information
31/024/2014 12:24:23 - INFO - Phone ready for flashmode operations.
31/024/2014 12:24:23 - INFO - Current device : E15i - FYT0001R9J - 1241-2655_R4B - 1236-9291_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
31/024/2014 12:24:23 - INFO - Processing loader.sin
31/024/2014 12:24:23 - INFO - Checking header
31/024/2014 12:24:23 - INFO - Flashing data
31/024/2014 12:24:24 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
31/024/2014 12:24:24 - INFO - Start Reading unit 00000851
31/024/2014 12:24:24 - INFO - Reading TA finished.
31/024/2014 12:24:24 - INFO - Ending flash session
31/024/2014 12:24:24 - INFO - Waiting for device to reboot
31/024/2014 12:24:24 - INFO - Waiting for device
31/024/2014 12:24:25 - INFO - Device connected in flash mode
31/024/2014 12:24:26 - INFO - Device disconnected
31/024/2014 12:24:28 - INFO - Device connected in flash mode
31/024/2014 12:24:47 - INFO - Device connected with USB debugging off
31/024/2014 12:24:47 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/026/2014 12:26:17 - INFO - Device disconnected
31/027/2014 12:27:26 - INFO - Device connected with USB debugging on
31/027/2014 12:27:27 - INFO - Checking root access
31/027/2014 12:27:40 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\fixPart to /data/local/tmp
31/027/2014 12:27:40 - INFO - Running runfixPart as root thru sysrun
31/027/2014 12:27:41 - INFO - Successfully applied fixPart. Rebooting
31/027/2014 12:27:43 - INFO - Waiting for device
31/027/2014 12:27:43 - INFO - Device disconnected
31/027/2014 12:27:53 - INFO - Device connected with USB debugging off
31/027/2014 12:27:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/027/2014 12:27:59 - INFO - Device disconnected
31/028/2014 12:28:00 - INFO - Device connected with USB debugging on
31/028/2014 12:28:00 - INFO - Checking root access
31/028/2014 12:28:02 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\mapper_2.6.29.ko to /data/local/tmp
31/028/2014 12:28:02 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\bootwrite_semcSL to /data/local/tmp
31/028/2014 12:28:02 - INFO - Running runbootwrite as root thru sysrun
31/028/2014 12:28:03 - INFO - Successfully applied bootwrite. Bootloader should be unlocked. Rebooting
31/028/2014 12:28:05 - INFO - Device disconnected

and here`s the log of s1tools before unlocking bootloader:
3/31/2014 10:56:54 AM Welcome to S1 identify tool
3/31/2014 10:57:02 AM
3/31/2014 10:57:02 AM TO CONNECT NEXT PHONES
3/31/2014 10:57:02 AM X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
3/31/2014 10:57:02 AM LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
3/31/2014 10:57:02 AM PRESS AND HOLD "BACK" BUTTON...
3/31/2014 10:57:02 AM
3/31/2014 10:57:02 AM PLEASE ATTACH TURNED OFF PHONE NOW
3/31/2014 10:57:02 AM
3/31/2014 10:57:49 AM
3/31/2014 10:57:49 AM RUNNING S1_EROM VER "R8A029"
3/31/2014 10:57:49 AM SOFTWARE AID: 0001
3/31/2014 10:57:49 AM LOADER AID: 0001
3/31/2014 10:57:51 AM FLASH ID: "002C/00BC"
3/31/2014 10:57:51 AM LOADER VERSION: "R4A045"
3/31/2014 10:57:51 AM
3/31/2014 10:57:51 AM MODEL (from GDFS): E15i
3/31/2014 10:57:51 AM SOFTWARE VERSION: 1236-9291_2.1.1.C.0.0
3/31/2014 10:57:51 AM CUSTOM VERSION: 1241-2655_R4B
3/31/2014 10:57:51 AM FILESYSTEM VERSION: WORLD-1-8_2.1.1.C.0.0
3/31/2014 10:57:51 AM SERIAL NO: FYT0001R9J
3/31/2014 10:57:51 AM
3/31/2014 10:57:51 AM SEMC SIMLOCK CERTIFICATE
3/31/2014 10:57:51 AM Elapsed:48 secs.

What is the manufacturing date of the x8?

cascabel said:
What is the manufacturing date of the x8?
Click to expand...
Click to collapse
i dont know, but the code is 11W44.

eefathi said:
i dont know, but the code is 11W44.
Click to expand...
Click to collapse
Does it show any sign of life at all? Try charging to a few minutes. I think it's a hard brick, but try anyway. If it doesn't work, send it to sony (serVice center).

hi
eefathi said:
i dont know, but the code is 11W44.
Click to expand...
Click to collapse
you may give a try to http://forum.xda-developers.com/showpost.php?p=27942435&postcount=206 ... if you can make it

cascabel said:
Does it show any sign of life at all? Try charging to a few minutes. I think it's a hard brick, but try anyway. If it doesn't work, send it to sony (serVice center).
Click to expand...
Click to collapse
i`ve tried to charge it with vivaz, (same battery),,, but no sign of living yet, is it the only way to fix this problem?

eefathi said:
i`ve tried to charge it with vivaz, (same battery),,, but no sign of living yet, is it the only way to fix this problem?
Click to expand...
Click to collapse
There are some shops that can fix it. You can also do it using jtag, but i haven't seen any tutorials about it. You can try google for that.

cascabel said:
There are some shops that can fix it. You can also do it using jtag, but i haven't seen any tutorials about it. You can try google for that.
Click to expand...
Click to collapse
thanx,,, looks like i gotta` kiss the friendship between me and my friend goodbye...
but i still dont understand why "S1 tool identify" software said its unlockable, because i`ve seen one site and it claimed if you see that sentence "SEMC SIMLOCK certificate", in s1tool identify`s log, you can unlock the bootloader,

eefathi said:
thanx,,, looks like i gotta` kiss the friendship between me and my friend goodbye...
but i still dont understand why "S1 tool identify" software said its unlockable, because i`ve seen one site and it claimed if you see that sentence "SEMC SIMLOCK certificate", in s1tool identify`s log, you can unlock the bootloader,
Click to expand...
Click to collapse
Well, you didn't want that to happen. Hopefully, you and you r friend can work things out. Yes s1tool will tell you that you can unlock it. Unfortunately, phones with manufacturing date above 11w28 is always a risk as far as unlocking the bootloader.

[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.

Bootloader. Proszę o pomoc. Help.

Welcome.
I wanted to unlock the bootloader on my Xperia with but encountered a problem when combined with flashtool'em .
Everything is done on windows 8.1 ( drivers are installed ), phone with network play , and can unlock it because the service menu says ... : YES.
system 4.4.4
I ask you to quick help .
Here you have the log:
12/025/2014 10:25:12 - INFO - < - This level is successfully initialized
12/025/2014 10:25:12 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 10:50:00 p.m.
12/025/2014 10:25:14 - INFO - Device disconnected
12/025/2014 10:25:16 - INFO - Please connect your device into flashmode .
12/026/2014 10:26:40 - INFO - Device connected in flash mode
12/026/2014 10:26:40 - INFO - Opening device for R / W
12/026/2014 10:26:41 - INFO - Processing loader
12/026/2014 10:26:54 - INFO - Checking header
12/026/2014 10:26:54 - ERROR -
12/026/2014 10:26:54 - INFO - Your phone bootloader can not be officially unlocked
12/026/2014 10:26:54 - INFO - You can now unplug and restart your phone

Try this way - How to unlock the bootloader.
Sent from my C6603 using Tapatalk

z
Czesc Krzysiek,
jak chcesz wiecej to na privie, a tak to po Angielsku
The best idea is to work it out with fastboot command, I never did this with flashtool.
Go to sony bootloader unlock site,
http://developer.sonymobile.com/unlockbootloader/
register, enter the IMEI no. you will get email with instructions - token - link with your code
power off the phone and go to folder where you have adb files - you will have to open the command line there ( shift + right click = otworz okno polecenia tutaj ),
there will a new window pop up with command line,
Take the phone, connect the usb cable to pc and phone and press power with volume down button. Blue notification led should light up - this means youre in fastboot mode,
I should mention you must have your adb drivers already installed at this stage.
When phone in fastboot, go to window with command line and type what you're got in email from sony - this should start with getvar or something,
type in exactly what is in the message,
Hit enter and wait,
You should be done in seconds.
Pzdr z iry
Filip
krzysiek0110 said:
Welcome.
I wanted to unlock the bootloader on my Xperia with but encountered a problem when combined with flashtool'em .
Everything is done on windows 8.1 ( drivers are installed ), phone with network play , and can unlock it because the service menu says ... : YES.
system 4.4.4
I ask you to quick help .
Here you have the log:
12/025/2014 10:25:12 - INFO - < - This level is successfully initialized
12/025/2014 10:25:12 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 10:50:00 p.m.
12/025/2014 10:25:14 - INFO - Device disconnected
12/025/2014 10:25:16 - INFO - Please connect your device into flashmode .
12/026/2014 10:26:40 - INFO - Device connected in flash mode
12/026/2014 10:26:40 - INFO - Opening device for R / W
12/026/2014 10:26:41 - INFO - Processing loader
12/026/2014 10:26:54 - INFO - Checking header
12/026/2014 10:26:54 - ERROR -
12/026/2014 10:26:54 - INFO - Your phone bootloader can not be officially unlocked
12/026/2014 10:26:54 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse

Hard bricked Xperia SP (QHSUSB_DLOAD)

The problem is: I accidentally restored wrong boot partition in TWRP(from another xperia sp). After that it was dead. I found this method to bring it back to life but i experience an error. I have backup of the original boot backup(the right one), but i don't know if it's possible to restore it with s1tool. If there is a method to do this, any help would be apriciated.

Tebex said:
The problem is: I accidentally restored wrong boot partition in TWRP(from another xperia sp). After that it was dead. I found this method to bring it back to life but i experience an error. I have backup of the original boot backup(the right one), but i don't know if it's possible to restore it with s1tool. If there is a method to do this, any help would be apriciated.
Click to expand...
Click to collapse
Ever been to a doctor and said: "Hi! My grandpa is sick, like dead. I found a list of drugs that could help, gave him some, but he didn't get better. Give me a prescription that'll heal him!"
As much as your doctor wouldn't have any idea what's going on with grandpa, we really have no idea what's going on with your phone...
Enough Sarcastaball, now seriously:
Tell us exactly what you did, each and every step!
Provide us with error codes, screenshots, everything you got.
Then we'll help you

Kaffeetrinker said:
Ever been to a doctor and said: "Hi! My grandpa is sick, like dead. I found a list of drugs that could help, gave him some, but he didn't get better. Give me a prescription that'll heal him!"
As much as your doctor wouldn't have any idea what's going on with grandpa, we really have no idea what's going on with your phone...
Enough Sarcastaball, now seriously:
Tell us exactly what you did, each and every step!
Provide us with error codes, screenshots, everything you got.
Then we'll help you
Click to expand...
Click to collapse
Yes, sorry that was just stupid.
So here is everything i did:
My friend wanted me to change stock Firmware to Cyanogenmod. I unlocked bootloader, and after that when I booted the touch wasn't working. I fastbooted TWRP and in TWRP everything was working. I cleaned /system, /data, /cache, and installed CM14.1/GAPPS. When phone booted i realised the touchscreen wasn't working. So I made backup of non system partitions(/boot and other but not /system /data /cache)
I took MY Xperia sp(the second one, my personal phone) , installed CM14.1 on it and made sure it was running correctly. After that i made backup of this install and restored it on the first phone(the one with "bad touch"). It didn't turn on. I realised I restored /boot partition from the other phone and now it's not booting at all. On my PC It was recognised as
I tried flashing emergency bootloader using this tutorial, but it gives me an error:
2016-12-14 22:05:37 Welcome S1 Tool [28.02.2015].
2016-12-14 22:05:37 That is small and crippled subset of SETOOL2 service tool.
2016-12-14 22:05:45
2016-12-14 22:05:45 SELECT FIRMWARE PACKAGES
2016-12-14 22:05:45 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2016-12-14 22:05:46 CHECKING PACKAGES ...
2016-12-14 22:05:46
2016-12-14 22:05:46 DETACH USB CABLE FROM PHONE
2016-12-14 22:05:46 REMOVE BATTERY FROM PHONE
2016-12-14 22:05:46 ATTACH TESTPOINT
2016-12-14 22:05:46 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2016-12-14 22:05:46
2016-12-14 22:06:07 will use DLOAD protocol ...
2016-12-14 22:06:07 0808010600900000
2016-12-14 22:06:07 0D0F50424C5F446C6F6164564552322E30
2016-12-14 22:06:07 162001000100
2016-12-14 22:06:07 17004001000100E1507E00
2016-12-14 22:06:07 PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2016-12-14 22:06:07 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
2016-12-14 22:06:07 PROCESSING ...
2016-12-14 22:06:10 REMOVE TESTPOINT NOW, THEN PRESS "READY"
2016-12-14 22:06:10
2016-12-14 22:06:14 Emergency loader uploaded ...
2016-12-14 22:06:15
2016-12-14 22:06:15 RUNNING S1_PRELOADER VER "R5G008"
2016-12-14 22:06:15 LOADER AID: 0001
2016-12-14 22:06:16 DEVICE ID: F67DAE05
2016-12-14 22:06:16 FLASH ID: "00FE/004E003F"
2016-12-14 22:06:16 LOADER VERSION: "R5G008"
2016-12-14 22:06:16
2016-12-14 22:06:16 WRITING PACKAGES ...
2016-12-14 22:06:16 Processing package
2016-12-14 22:06:16 C:\Documents and Settings\Pan Szef\Pulpit\genuinespboot\S1Boot_R11B023_HWID7E50E1.SIN_FILE_SET
2016-12-14 22:06:16
2016-12-14 22:06:16 Processing ACPU files
2016-12-14 22:06:16 PROCESSING: boot.sin
2016-12-14 22:06:16 FATAL ERROR [ 0x0508:_sin_header_verification, err: 000A ]
2016-12-14 22:06:16 error while uploading final HDR block
2016-12-14 22:06:16 Break.
2016-12-14 22:06:16 FINISHED
2016-12-14 22:06:16 Elapsed:31 secs.
I also tried mounting my phone as qualcomm emergency device but unlike tutorials my phone doesn't mount as storage device which i could easly restore my backup.
So i think the main problem is that i don't know how to restore my backup, or flash proper bootloader.

Tebex said:
Yes, sorry that was just stupid.
So here is everything i did:
My friend wanted me to change stock Firmware to Cyanogenmod. I unlocked bootloader, and after that when I booted the touch wasn't working. I fastbooted TWRP and in TWRP everything was working. I cleaned /system, /data, /cache, and installed CM14.1/GAPPS. When phone booted i realised the touchscreen wasn't working. So I made backup of non system partitions(/boot and other but not /system /data /cache)
I took MY Xperia sp(the second one, my personal phone) , installed CM14.1 on it and made sure it was running correctly. After that i made backup of this install and restored it on the first phone(the one with "bad touch"). It didn't turn on. I realised I restored /boot partition from the other phone and now it's not booting at all. On my PC It was recognised as
I tried flashing emergency bootloader using this tutorial, but it gives me an error:
2016-12-14 22:05:37 Welcome S1 Tool [28.02.2015].
2016-12-14 22:05:37 That is small and crippled subset of SETOOL2 service tool.
2016-12-14 22:05:45
2016-12-14 22:05:45 SELECT FIRMWARE PACKAGES
2016-12-14 22:05:45 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2016-12-14 22:05:46 CHECKING PACKAGES ...
2016-12-14 22:05:46
2016-12-14 22:05:46 DETACH USB CABLE FROM PHONE
2016-12-14 22:05:46 REMOVE BATTERY FROM PHONE
2016-12-14 22:05:46 ATTACH TESTPOINT
2016-12-14 22:05:46 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2016-12-14 22:05:46
2016-12-14 22:06:07 will use DLOAD protocol ...
2016-12-14 22:06:07 0808010600900000
2016-12-14 22:06:07 0D0F50424C5F446C6F6164564552322E30
2016-12-14 22:06:07 162001000100
2016-12-14 22:06:07 17004001000100E1507E00
2016-12-14 22:06:07 PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2016-12-14 22:06:07 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
2016-12-14 22:06:07 PROCESSING ...
2016-12-14 22:06:10 REMOVE TESTPOINT NOW, THEN PRESS "READY"
2016-12-14 22:06:10
2016-12-14 22:06:14 Emergency loader uploaded ...
2016-12-14 22:06:15
2016-12-14 22:06:15 RUNNING S1_PRELOADER VER "R5G008"
2016-12-14 22:06:15 LOADER AID: 0001
2016-12-14 22:06:16 DEVICE ID: F67DAE05
2016-12-14 22:06:16 FLASH ID: "00FE/004E003F"
2016-12-14 22:06:16 LOADER VERSION: "R5G008"
2016-12-14 22:06:16
2016-12-14 22:06:16 WRITING PACKAGES ...
2016-12-14 22:06:16 Processing package
2016-12-14 22:06:16 C:\Documents and Settings\Pan Szef\Pulpit\genuinespboot\S1Boot_R11B023_HWID7E50E1.SIN_FILE_SET
2016-12-14 22:06:16
2016-12-14 22:06:16 Processing ACPU files
2016-12-14 22:06:16 PROCESSING: boot.sin
2016-12-14 22:06:16 FATAL ERROR [ 0x0508:_sin_header_verification, err: 000A ]
2016-12-14 22:06:16 error while uploading final HDR block
2016-12-14 22:06:16 Break.
2016-12-14 22:06:16 FINISHED
2016-12-14 22:06:16 Elapsed:31 secs.
I also tried mounting my phone as qualcomm emergency device but unlike tutorials my phone doesn't mount as storage device which i could easly restore my backup.
So i think the main problem is that i don't know how to restore my backup, or flash proper bootloader.
Click to expand...
Click to collapse
OK, thanks.
Has the digitizer on the phone ever been replaced? Yes/No/Maybe?
Have you tried the tool "Emma" by Sony?
It's not that popular, but it has saved my phone twice.
After using Emma, you'll be back to Stock, but your BL will still be unlocked and you can start from scratch.
Emma is pretty much self explaining, Sony itself has information how to use it on the internet.
Try Emma and when you're done, check back! Then I'll tell you what to do next

Help! Xperia GX (SO-04D) hard brick

I'm following this topic: https://forum.xda-developers.com/xperia-t-v/general/xperia-hard-brick-recovery-t2915303
But I dont have any files, even TA backup. Can I unbrick my phone?
This is the S1Tool log when I try to use Xperia TX 's file:
Code:
Welcome S1 Tool [19.05.2015].
That is small and crippled subset of SETOOL2 service tool.
SELECT FIRMWARE PACKAGES
YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
CHECKING PACKAGES ...
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use DLOAD protocol ...
0808010600900000
0D0F50424C5F446C6F6164564552322E30
162001000100
17004001000100E1506B00
PRODUCT DETECTED: "SONY MSM8960-3 OEM1 Fused"
1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "R5F001"
LOADER AID: 0001
[ llcomm: 00010000,00080000 ]
DEVICE ID: A3A9AD01
FLASH ID: "0015/00000000"
LOADER VERSION: "R5F001"
WRITING PACKAGES ...
Processing package
C:\Users\Thanh Doi\Downloads\Compressed\9_2_A_1_205.APP_SW_Hayabusa_GENERIC_1253_6298_S1_SW_LIVE_7054_PID1_0002.SIN_FILE_SET
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
PROCESSING: apps_log_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
PROCESSING: kernel_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
PROCESSING: fotakernel_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
SKIP: partition-image_S1-SW-LIVE-7054-PID1-0002-MBR.sin
no update files in package
FINISHED
Elapsed:29 secs.
P/S: My English is not good. Please forgive my writing mistakes