Hard bricked Xperia SP (QHSUSB_DLOAD) - Xperia SP Q&A, Help & Troubleshooting

Hard bricked Xperia SP (QHSUSB_DLOAD) - Xperia SP Q&A, Help & Troubleshooting

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

Related

[Q] ERR_DYNAMIC="SIN header verification failed" on xperia x8 flashtool

ok this is the log from flashtool v0.6.8.0
17/016/2013 20:16:47 - INFO - <- This level is successfully initialized
17/016/2013 20:16:47 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
17/016/2013 20:16:47 - INFO - You can drag and drop ftf files here to start flashing them
17/016/2013 20:16:52 - INFO - Device disconnected
17/016/2013 20:16:55 - INFO - Selected E15_nAa-13_2.6.29.6-nAa-13.ftf
17/016/2013 20:16:55 - INFO - Preparing files for flashing
17/016/2013 20:16:55 - INFO - Please connect your device into flashmode.
17/017/2013 20:17:06 - INFO - Device connected in flash mode
17/017/2013 20:17:06 - INFO - Opening device for R/W
17/017/2013 20:17:07 - INFO - Reading device information
17/017/2013 20:17:07 - INFO - Phone ready for flashmode operations.
17/017/2013 20:17:07 - INFO - Start Flashing
17/017/2013 20:17:07 - INFO - Flashing loader
17/017/2013 20:17:07 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
17/017/2013 20:17:07 - ERROR - Error flashing. Aborted
17/017/2013 20:17:07 - INFO - Device connected in flash mode
17/017/2013 20:17:08 - INFO - Device disconnected
17/017/2013 20:17:11 - INFO - Device connected in flash mode
17/017/2013 20:17:12 - INFO - Device disconnected
i get this from S1TOOL
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1242-6780_R5B
FILESYSTEM VERSION: WORLD-1-2-5_2.0.1.A.0.47
SERIAL NO: BX902AVHMC
SEMC SIMLOCK CERTIFICATE
Elapsed:10 secs.
why i cant flash my x8=?

andrescabana86 said:
ok this is the log from flashtool v0.6.8.0
17/016/2013 20:16:47 - INFO - <- This level is successfully initialized
17/016/2013 20:16:47 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
17/016/2013 20:16:47 - INFO - You can drag and drop ftf files here to start flashing them
17/016/2013 20:16:52 - INFO - Device disconnected
17/016/2013 20:16:55 - INFO - Selected E15_nAa-13_2.6.29.6-nAa-13.ftf
17/016/2013 20:16:55 - INFO - Preparing files for flashing
17/016/2013 20:16:55 - INFO - Please connect your device into flashmode.
17/017/2013 20:17:06 - INFO - Device connected in flash mode
17/017/2013 20:17:06 - INFO - Opening device for R/W
17/017/2013 20:17:07 - INFO - Reading device information
17/017/2013 20:17:07 - INFO - Phone ready for flashmode operations.
17/017/2013 20:17:07 - INFO - Start Flashing
17/017/2013 20:17:07 - INFO - Flashing loader
17/017/2013 20:17:07 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
17/017/2013 20:17:07 - ERROR - Error flashing. Aborted
17/017/2013 20:17:07 - INFO - Device connected in flash mode
17/017/2013 20:17:08 - INFO - Device disconnected
17/017/2013 20:17:11 - INFO - Device connected in flash mode
17/017/2013 20:17:12 - INFO - Device disconnected
i get this from S1TOOL
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1242-6780_R5B
FILESYSTEM VERSION: WORLD-1-2-5_2.0.1.A.0.47
SERIAL NO: BX902AVHMC
SEMC SIMLOCK CERTIFICATE
Elapsed:10 secs.
why i cant flash my x8=?
Click to expand...
Click to collapse
you should have used search button. this Q has been answered 3-4 times.
http://forum.xda-developers.com/showthread.php?t=1254225
this thread answers it too. you havent completed the unlock process

try diferent firmware

krzysiek1984 said:
try diferent firmware
Click to expand...
Click to collapse
you need to read the OP before answering...see the R in the post? unlock process was incomplete

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

Lumia 822 Stuck as QHSUSB_DLOAD device.

Hi guys so I had a problem with battery drain on the Lumia 822, so I decided to go back to 8.1 well it said it failed and then it rebooted to a black screen.
No logo or anything
So I plug the phone to the pc and it says QHSUSB_DLOAD then I open the recovery tool it asks me what phone I want to recover and it says Error: Emergency package was not found. Emergency flashing for your device is not supported.
So… how do I recover the device if you won’t provide the Emergency package…
All of this was created from the WDRT 3.8.19701
I got as far as:
thor2 -mode ffureader -ffufile C:\ProgramData\Microsoft\Packages\Products\RM-845\RM845_3051.50009.1446.0077_RETAIL_nam_usa_100_ 77_460421_prd_signed.ffu -dump_gpt -filedir C:\lumia\ and i got the 2 bin files and this RKH
RKH of SBL1: A0AE29AC24C843250D2DD0FFD409A649B4E4A09ED3B1A78413 FB2B94B7476AAB
RKH of UEFI: A0AE29AC24C843250D2DD0FFD409A649B4E4A09ED3B1A78413 FB2B94B7476AAB
Platform ID: Nokia.MSM8960.P5219
Hi. index sector 20967168
help?

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

[help] z1 hard brick?!!!?

Friends, hi. I´m having a big big big problem with my warrior z1. I had a problem with my display so i needed to replace it. But after that i tried to boot my Z1 and got a black screen. I thought it was a display problem, so, i talked to the seller and got another display (SAME PROBLEM) black screen ( but i could feel the power vibrate when i was pressing it) But suddenly it didnt work anymore, power botton didnt vibrate anymore, Power+vol up and power + vol down ... Nothing seems to work
( i didnt flashed anything, just changed the display ) and i didnt have problems to do it because for me its easy
( i have unlocked bootloader so PC COMPANION wont help me out)
When i plug the charger i got this red light
When i try to press power botton while charger connected it blinks red light
Tried to connect it on my PC but it keeps connecting and disconnecting with the red light blinking a lot.
One thing that i noticed is, when the phone is plugged into charger and i try to press power + vol up it give me this 3 times vibration but no response
I cant get into flash mode, fastboot mode.
I´ve searched a lot so i found about the HARD BRICK and needed to do the TEST POINT, so i tried too using S1 tool and i got this log
04/02/2018 11:53:02 Welcome to S1 tool.
04/02/2018 11:53:02 That is small and crippled subset of SETOOL2 service tool.
04/02/2018 11:53:05
04/02/2018 11:53:05 SELECT FIRMWARE PACKAGES
04/02/2018 11:53:05 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
04/02/2018 11:53:11 CHECKING PACKAGES ...
04/02/2018 11:53:11
04/02/2018 11:53:11 DETACH USB CABLE FROM PHONE
04/02/2018 11:53:11 REMOVE BATTERY FROM PHONE
04/02/2018 11:53:11 ATTACH TESTPOINT
04/02/2018 11:53:11 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
04/02/2018 11:53:11
04/02/2018 11:55:14 will use Sahara protocol ...
04/02/2018 11:55:14 REMOVE TESTPOINT NOW, THEN PRESS "READY"
04/02/2018 11:55:14
04/02/2018 11:55:21 PROCESSING ...
04/02/2018 11:55:21 SERIAL NUMBER : 8F0C4807
04/02/2018 11:55:21 HARDWARE ID : 04000100E1007B00
04/02/2018 11:55:21 HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
04/02/2018 11:55:21 Emergency loader uploaded ...
04/02/2018 11:55:22
04/02/2018 11:55:22 RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
04/02/2018 11:55:22 LOADER AID: 0004
04/02/2018 11:55:22 DEVICE ID: 07480C8F
04/02/2018 11:55:22 FLASH ID: "0011/01000010"
04/02/2018 11:55:22 LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
04/02/2018 11:55:22
04/02/2018 11:55:22 WRITING PACKAGES ...
04/02/2018 11:55:22 Processing package
04/02/2018 11:55:22 C:\Users\Rafael\Downloads\C6903\C6903\14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
04/02/2018 11:55:22
04/02/2018 11:55:23 WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.04_15
04/02/2018 11:55:23 PARSING: "DEVELOPMENT"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
04/02/2018 11:55:23 PARSING: "TEST_OEM0_007B00E1"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
04/02/2018 11:55:23 value OTP_DATA_1 : 00000100, not match 01000400
04/02/2018 11:55:23 value IDCODE_1 : 007B00E1, match 007B00E1
04/02/2018 11:55:23 PARSING: "PRECOMMERCIAL_007B00E1"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
04/02/2018 11:55:23 value OTP_DATA_1 : 01000400, match 01000400
04/02/2018 11:55:23 value IDCODE_1 : 007B00E1, match 007B00E1
04/02/2018 11:55:23 PROCESSING : dbi_S1_Boot_MSM8974_LA1_04_15_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:24 PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
04/02/2018 11:55:24 MINOR ERROR [ Open_TA_failed, err: 001D ]
04/02/2018 11:55:24 BOOT UPDATED
04/02/2018 11:55:24 Processing ACPU files
04/02/2018 11:55:24 PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:24 PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:25 PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:26 PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:27 SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
04/02/2018 11:55:27 PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:27 no update files in package
04/02/2018 11:55:27 FINISHED
04/02/2018 11:55:27 Elapsed:142 secs.
But after that im still in red lights....
How can we make the ressurrection of my z1... my heart is broken

(help)z1 hard brick
LinkRaf said:
Friends, hi. I´m having a big big big problem with my warrior z1. I had a problem with my display so i needed to replace it. But after that i tried to boot my Z1 and got a black screen. I thought it was a display problem, so, i talked to the seller and got another display (SAME PROBLEM) black screen ( but i could feel the power vibrate when i was pressing it) But suddenly it didnt work anymore, power botton didnt vibrate anymore, Power+vol up and power + vol down ... Nothing seems to work
( i didnt flashed anything, just changed the display ) and i didnt have problems to do it because for me its easy
( i have unlocked bootloader so PC COMPANION wont help me out)
When i plug the charger i got this red light
When i try to press power botton while charger connected it blinks red light
Tried to connect it on my PC but it keeps connecting and disconnecting with the red light blinking a lot.
One thing that i noticed is, when the phone is plugged into charger and i try to press power + vol up it give me this 3 times vibration but no response
I cant get into flash mode, fastboot mode.
I´ve searched a lot so i found about the HARD BRICK and needed to do the TEST POINT, so i tried too using S1 tool and i got this log
04/02/2018 11:53:02 Welcome to S1 tool.
04/02/2018 11:53:02 That is small and crippled subset of SETOOL2 service tool.
04/02/2018 11:53:05
04/02/2018 11:53:05 SELECT FIRMWARE PACKAGES
04/02/2018 11:53:05 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
04/02/2018 11:53:11 CHECKING PACKAGES ...
04/02/2018 11:53:11
04/02/2018 11:53:11 DETACH USB CABLE FROM PHONE
04/02/2018 11:53:11 REMOVE BATTERY FROM PHONE
04/02/2018 11:53:11 ATTACH TESTPOINT
04/02/2018 11:53:11 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
04/02/2018 11:53:11
04/02/2018 11:55:14 will use Sahara protocol ...
04/02/2018 11:55:14 REMOVE TESTPOINT NOW, THEN PRESS "READY"
04/02/2018 11:55:14
04/02/2018 11:55:21 PROCESSING ...
04/02/2018 11:55:21 SERIAL NUMBER : 8F0C4807
04/02/2018 11:55:21 HARDWARE ID : 04000100E1007B00
04/02/2018 11:55:21 HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
04/02/2018 11:55:21 Emergency loader uploaded ...
04/02/2018 11:55:22
04/02/2018 11:55:22 RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
04/02/2018 11:55:22 LOADER AID: 0004
04/02/2018 11:55:22 DEVICE ID: 07480C8F
04/02/2018 11:55:22 FLASH ID: "0011/01000010"
04/02/2018 11:55:22 LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
04/02/2018 11:55:22
04/02/2018 11:55:22 WRITING PACKAGES ...
04/02/2018 11:55:22 Processing package
04/02/2018 11:55:22 C:\Users\Rafael\Downloads\C6903\C6903\14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
04/02/2018 11:55:22
04/02/2018 11:55:23 WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.04_15
04/02/2018 11:55:23 PARSING: "DEVELOPMENT"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
04/02/2018 11:55:23 PARSING: "TEST_OEM0_007B00E1"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
04/02/2018 11:55:23 value OTP_DATA_1 : 00000100, not match 01000400
04/02/2018 11:55:23 value IDCODE_1 : 007B00E1, match 007B00E1
04/02/2018 11:55:23 PARSING: "PRECOMMERCIAL_007B00E1"
04/02/2018 11:55:23 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
04/02/2018 11:55:23 value OTP_DATA_1 : 01000400, match 01000400
04/02/2018 11:55:23 value IDCODE_1 : 007B00E1, match 007B00E1
04/02/2018 11:55:23 PROCESSING : dbi_S1_Boot_MSM8974_LA1_04_15_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:23 PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
04/02/2018 11:55:24 PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
04/02/2018 11:55:24 MINOR ERROR [ Open_TA_failed, err: 001D ]
04/02/2018 11:55:24 BOOT UPDATED
04/02/2018 11:55:24 Processing ACPU files
04/02/2018 11:55:24 PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:24 PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:25 PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:26 PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:27 SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
04/02/2018 11:55:27 PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
04/02/2018 11:55:27 no update files in package
04/02/2018 11:55:27 FINISHED
04/02/2018 11:55:27 Elapsed:142 secs.
But after that im still in red lights....
How can we make the ressurrection of my z1... my heart is broken
Click to expand...
Click to collapse
Hello friend,I have the same problem with my z1 c6903,here is my log:
Welcome S1 Tool [06.02.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 Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : 6BEFE502
HARDWARE ID : 04000100E1007B00
PRODUCT DETECTED: "MSM8974 OEM1 fused"
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 02E5EF6B
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
WRITING PACKAGES ...
Processing package
C:\Users\\Downloads\+++++Sony Folder+++++\+++Xperia Z1 C6902 & C6903 Dead Boot Repair File(1)\Xperia Z1 C6902 & C6903 Dead Boot Repair File\C6903\C6903\14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.04_15
PARSING: "DEVELOPMENT"
value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
PARSING: "TEST_OEM0_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 00000100, not match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PARSING: "PRECOMMERCIAL_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 01000400, match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PROCESSING : dbi_S1_Boot_MSM8974_LA1_04_15_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
can't get S1 command header
error while uploading final DATA block
Break.
llbug: write timeout [Overlapped I/O operation is in progress]
llbug: blk write fail.fatal
llbug: write timeout [Overlapped I/O operation is in progress]
llbug: blk write fail.fatal
can't send S1 command data [0000000A/00000003]
FINISHED
llbug: write timeout [Overlapped I/O operation is in progress]
llbug: blk write fail.fatal
llbug: write timeout [Overlapped I/O operation is in progress]
llbug: blk write fail.fatal
can't send S1 command data [00000004/00000003]
Elapsed:388 secs.
So,I'm at a total loss here.I must be doing something right to get to the flshing stage.Can someone help me to decipher the errors please.
Thanks.

Database Develop

welcome