[XDA Assist] mmsn:
hello all members of this community. A few days ago my xperia z phone suddenly stopped working and had these symptoms.

- No battery loaded.

- He did not react when pressed any buttons conbinacion to enter boot flash and fast.

- He not started, or vibrated

- It not recognized the phone, sony program.

practically did nothing.

I Given this situation, I look in different forums such cases to find a solution. I found many comments saying that this terminal suffered from a condition called '' sudden death ''. Comparing my situation with that of those other people come to conclucion that this was my problem.

I decided to open the terminal and remove the battery, I happened without battery and connect the phone was detected by the computer in s1 fastboot mode.

when I saw the phone was detected in this way by the computer, because they did not have the bootloader activated, it decided activated via a reset point. In this way you could flash the rom again by flash tool.

I did the reset point this way.

2. Download and install the latest Gordon's Gate Flash Driver from this post: Attached File ggsetup-3.0.0.7.exe

3. Download and run this s1tool: Attached File s1tool.exe

4. Download proper APPSW firmware for your Sony Xperia Z

5. In S1tool choose S1 EMERGENCY MODE, press Flash button, select correct APPSW .sin_file_set file (or you can select whole firmware if you have it in order APPSW, FSP, Elabel - but you can't use .ftf flashtool files),

6. Press Testpoint READY button:

Follow the steps and as a result I got this in the software tool s1: WWelcome to S1 tool.

That is small and crippled subset of SETOOL2 service tool.

and if your phone is detected as qhusb_dload device, just attach usb cable. If not, perform all steps from point 1 (connect testpoint to GND and attach USB cable).

7. When drivers will be installed and phone will be detected, program will ask you to disconnect testpoint. Disconnect testpoint from GND and press Testpoint READY button.

8. After that phone will load emergency s1 loader, re-enumerate usb, load s1 loader, update boot in your phone and flash selected firmware.

9. Now you have to flash (if not done yet) your phone with all firmware parts (APPSW, FSP, ELABEL) using S1 FLASH MODE, phone will be fixed. Also you can flash your phone using Sony Update Service, Sony PC Companion or any other flasher like current Flashtool.

10. Time to reassembly your phone using service manual: Sony Xperia Z C66XX Service Manuals

Credits: Big thanks to mr the_laser for creating this fantastic software and solution and thanks to anwar726 from Sony.yt for finding Xperia Z testpoint :piwo:

after I did the previous guide, This is what he showed me the s1flashtool:

--------------------------------------------------------------------------------------------------------------------------------------

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

17004001000100E1907100

PRODUCT DETECTED: "SONY APQ8064-3 ES1 OEM1 Fused"

1801001EA8B0C1B209C88CBB3E220F0AC00F6E6520A273D516B40E7F2EAEB0E5B3DB8B

PROCESSING ...

REMOVE TESTPOINT NOW, THEN PRESS "READY"

Emergency loader uploaded ...

RUNNING S1_PRELOADER VER "APQ8064_39"

LOADER AID: 0001

DEVICE ID: 01AB8624

FLASH ID: "0015/01000004"

LOADER VERSION: "APQ8064_39"

WRITING PACKAGES ...

Processing package

C:\Users\Mateo\Desktop\xperia z\Xperia Z series Dead Boot repair\C6602\10_5_A_0_230.APP_SW_Yuga_GENERIC_1269_5309_S1_SW_LIVE_5CA3_PID1_0002_MMC.SIN_FILE_SET

WILL UPDATE BOOT TO : 1264-2309 S1_BOOT_LAGAN_1.1.1_1

PARSING: "DEVELOPMENT"

value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED

PARSING: "TEST_OEM0_007190E1"

value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED

value OTP_DATA_1 : 00000100, not match 01000100

value IDCODE_1 : 007190E1, match 007190E1

PARSING: "PRECOMMERCIAL_007190E1"

value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED

value OTP_DATA_1 : 01000100, match 01000100

value IDCODE_1 : 007190E1, match 007190E1

PROCESSING : emmc_appsboot_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : s1sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : sbl1_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : sbl2_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : sbl3_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : tz_signed_1.1.1_1_S1-BOOT-5CA3-0001-MMC.sin

PROCESSING : Yuga_S1BootConfig_MiscTA_121203_1222.ta

Writing TA var 0002/084F/0060

Writing TA var 0002/08FD/0001

BOOT UPDATED

Processing ACPU files

PROCESSING: cache_S1-SW-LIVE-5CA3-PID1-0002-MMC.sin

llbug: blk write fail.fatal

can't send S1 command data [00000006/00000007]

Break.

llbug: blk write fail.fatal

llbug: blk write fail.fatal

can't send S1 command data [0000000A/00000003]

FINISHED

llbug: write error: "El dispositivo no reconoce el comando"

llbug: blk write fail.fatal

llbug: write error: "El dispositivo no reconoce el comando"

llbug: blk write fail.fatal

can't send S1 command data [00000004/00000003]

Elapsed:45 secs.

PROCEDURE STOPPED BY USER

-----------------------------------------------------------------------------------------------------------------------------

I do not understand very well what is written there, but I think think it's important ... haha

I have to mention that after the restpoint has not been started in s1 fastmood only recognizes Zeus flash mode or something similar.

I Made my phone at a brick? Does this have solution?

Thank you for your attention.!!!