[GUIDE] Z Ultra and Z1 HARD BRICK RECOVERY

osum101 · Apr 21, 2017

hi guys,
well i've got a bricked C6903 as explained in my earlier posts,
here >> https://forum.xda-developers.com/showpost.php?p=71808603&postcount=696
and here >> https://forum.xda-developers.com/showpost.php?p=71885258&postcount=698

and long story short, i can get into fastboot now if i charge my battery externally to 3.5V+ (blue LED and Flashtool says "phone connected in fastboot mode")
but when i try to flash the stock kernel (as i believe my phone's kernel is damaged) i get this error "FAILED (remote: Command not allowed)"
Stock kernel was extracted from this FTF "C6903_14.6.A.1.236_DE.ftf" (as this is the firmware that was on my phone when it got bricked) using Flashtool >> Tools
tried Kernel in .Sin , .elf and .img formats and failed
>>My phone is Not Rooted, Stock Rom, Locked Bootloader<<

also i can get into flashmode too apparently as i can see a solid Green LED if i connect it while holding down Vol- key (again if battery is charged externally to 3.5V+ capacity), but it's not detected in Flashtool or S1Tool , i can't flash any FTF and my PC says "USB Device not recognized" (tried on different laptops, same results)

someone please help me unbrick my Z1 or guide me about anything i might be doing wrong
thanks in advance

22229999 · Apr 21, 2017

help me for unbrick C6802 please

help me please

i cant unbrick a C6802 by this process
after that process phone,
can not detect by setool and red blinking and 3vibration & after power too

this log:

Welcome S1 Tool [28.02.2015].

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 : 18588C02
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: 028C5818
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"

WRITING PACKAGES ...
Processing package
F:\SETOOL\SE FLASH FILES\C6802_xpria_z_ultra\C6802___Z Ultra_UNBRICK\tools\14_2_A_0_290.APP_SW_Togari_GENERIC_1271_5715_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
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Togari_S1BootConfig_MiscTA_130115_1430.ta
Writing TA var 0002/084F/0049
Writing TA var 0002/08FD/0001
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:27 secs.

help me plz

osum101 · Apr 25, 2017

A bit more progress, any help is really appreciated guys

well my whole story is above in case full details are required, but this is the current situation of the phone now,
following is what i can currently do with my phone (which i was able to do previously too, but tried a couple new things this time)

here is the new progress i mentioned in my title though
IF I put the battery back into the phone and hold the Hard Reset Key (Near the SIM card tray in the SIM slot) for at least 120 seconds (tried 10/15/20 seconds but failed so went for a full 2 mins as mentioned in a post in Sony.yt forums)
and then repeat the S1 tool stuff, this time it doesn't give me the old "can't get S1 command header - LOADER NOT RESPONDING" error, instead it show's a bit more progress, but surprisingly the results are a bit different with two different versions of S1 tool
here are the logs from S1 tool
Log from S1 tool version 6/2/2015

Log from S1 tool version 19/5/2015

.
Also if i interrupt the process while S1 tool re-enumerates the USB so that phone is now detected as SOMC flash device and open Flashtool, it will see that the phone is connected in Flash mode
so taking advantage of that, if i try to flash any FTF the flash tool gets stuck on Reding Device information line.
only once it behaved differently, following is the log from Flashtool

Machiavellian · May 16, 2017

One last problem

Hi guys,
I did this procedure on my bricked Sony Xperia Z1 C6903, it has been dead and it has had only a red blinking LED when connected on the USB cable, but it is still dead. Here's the log of the program:

Code:

Welcome to S1 tool.
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 : E9A38801
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: 0188A3E9
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
 
WRITING PACKAGES ...
Processing package
C:\Users\Cosmo\Downloads\ta_gen\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
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
Writing TA var 0002/084F/0049
Writing TA var 0002/08FD/0001
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:132 secs.

I put the power button but no reply from the phone, so I connected it to the electric socket and the red LED is still blinking, what can I do?

Thanks in advance

Hoxen · May 19, 2017

Hello Guys ,
Plz Help
I ve done everything alright , but it still doesn't start , only the usual red light blinking ???
what's the solution plz :'(

Welcome to S1 tool.
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 : 21248603
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...

RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 03862421
FLASH ID: "0015/01000001"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"

WRITING PACKAGES ...
Processing package
C:\Users\Home\Desktop\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
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:36 secs.
PROCEDURE STOPPED BY USER

peymanpeyman · May 19, 2017

xperia m

hello every body,
this is my first post in this site,and i just wonder if this work for xperia m as well? (total dead xperia m)
thank you all in advanced

esssa · Jun 5, 2017

how to unbrick hard bricked SONY V

Hello guys , im hard bricking my SONY V ?

And i cant decrypt file downloaded from xperifirm
(File type is .sin)

Plaese help me ?

goldmobile · Jul 12, 2017

Xperia Z3 D6603 TestPoint find

Doom Slayer said:
THIS TUTORIAL IS ONLY FOR HARD BRICKED DEVICES.
HARD BRICK MEANS NO FLASHMODE AND NO FASTBOOT.
IN ORDER TO PROCEED DISASSEMBLY OF YOUR DEVICE IS REQUIRED.
IF YOU HAVE WARRANTY,STOP READING THIS, GO THE SONY SERVICE AND PLAY STUPID.
AS AFTER OPENING YOUR DEVICE, YOUR WARRANTY IS 100% VOID.
I AM NOT RESPONSIBLE FOR ANY DAMAGE.
YOU'VE BEEN WARNED.

Let's get started.
1. Download tools.7z from attachments and pack for your device.
2. Install ggsetup-3.0.0.7.exe
3. Open the back cover of your device.
4. Find the test point (See attachments).
5. Disconnect a battery, connect a usb cable. LED RED will start to blink.
6. Using the paper clip connect your test point with the GND. I used the metal shield in the middle of the motherboard.
7. Open the device manager, you should see SEMC Flash Device. If no, you did something wrong.
8. Disconnect your phone from computer.
9, Repeat the step 5.
10.Run the s1tool and select S1 MSM8974 EMERGENCY for the phone type.
11. Press the flash button, and choice the APP file for your device.
12. Press testpoint ready and repeat the step 6.
13. Remove the testpoint and press READY, when program will ask you to do so.
14. If flash was successful, you may disconnect your phone from usb, connect your battery and try to boot.You may have to charge your battery.
15. Now you can flash your device normally using software.

P.S.
I was not be able to flash on windows 8 64bit, but I flashed without problems on XP.

I would like to thank:

the_laser for making the software.

myevilface from support.setool.net for finding testpoint for c69xx.

and my poor Z Ultra which I sacrificed trying to find the test point
Actually I finished him when I wanted to fix audio jack.
Was to happy that my device is fixed and damaged the screen connector

UPDATE:
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET

------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.

hi please help me for find test point D6603

lostpaladin · Aug 9, 2017

z1 its gone forever or we can fix?

Doom Slayer said:
THIS TUTORIAL IS ONLY FOR HARD BRICKED DEVICES.
HARD BRICK MEANS NO FLASHMODE AND NO FASTBOOT.
IN ORDER TO PROCEED DISASSEMBLY OF YOUR DEVICE IS REQUIRED.
IF YOU HAVE WARRANTY,STOP READING THIS, GO THE SONY SERVICE AND PLAY STUPID.
AS AFTER OPENING YOUR DEVICE, YOUR WARRANTY IS 100% VOID.
I AM NOT RESPONSIBLE FOR ANY DAMAGE.
YOU'VE BEEN WARNED.

Let's get started.
1. Download tools.7z from attachments and pack for your device.
2. Install ggsetup-3.0.0.7.exe
3. Open the back cover of your device.
4. Find the test point (See attachments).
5. Disconnect a battery, connect a usb cable. LED RED will start to blink.
6. Using the paper clip connect your test point with the GND. I used the metal shield in the middle of the motherboard.
7. Open the device manager, you should see SEMC Flash Device. If no, you did something wrong.
8. Disconnect your phone from computer.
9, Repeat the step 5.
10.Run the s1tool and select S1 MSM8974 EMERGENCY for the phone type.
11. Press the flash button, and choice the APP file for your device.
12. Press testpoint ready and repeat the step 6.
13. Remove the testpoint and press READY, when program will ask you to do so.
14. If flash was successful, you may disconnect your phone from usb, connect your battery and try to boot.You may have to charge your battery.
15. Now you can flash your device normally using software.

P.S.
I was not be able to flash on windows 8 64bit, but I flashed without problems on XP.

I would like to thank:

the_laser for making the software.

myevilface from support.setool.net for finding testpoint for c69xx.

and my poor Z Ultra which I sacrificed trying to find the test point
Actually I finished him when I wanted to fix audio jack.
Was to happy that my device is fixed and damaged the screen connector

UPDATE:
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET

------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.

hi friends, i am new in forum but i am almost 3 year folowing this pages. i have a problem. my xperia z1 harder brick. (all gone no response anythink. i forget adb on. adb off, only black screen , i tried s1 tool but giving error code invalit ta err:0016 how i can fix this phone , i belive phone is live but how can i fix. my problems phone no open, no flashmode,flashtool not working, ofical sony comp. not detect, windows nothing detect, only working red light blink and power+ wol up 3 times vibrating, pelease help me . sory for my bad english.

karoliens · Aug 10, 2017

Could you please tell me where is the test point for Sony Xperia M4 Aqua located?

Red00fox · Sep 6, 2017

Help please. My phone xperia z1 is not detected by any flashtool or in the device manager. My phone was left uncharged for several months, when i tried to charge it, it just show a solid red led, not blinking so i thought maybe the battery is dead so i bought a new battery and replaced the old one, but still the same, cannot be on, cannot be detected by pc, when I connect to the charger it just show a solid red led. I tried all the button combination.

哈喇客 · Dec 10, 2017

Do you have sin set file for sol24?(z ultra Japan AU KDDI version)

recently I bought a second hand sony sol24,which was unable to turn on or entre the flash mode because the previous user turn off the power while flashing.
now the indicator light goes red blink when plug in the charger or connected to computer with the data cable.
I wanna try to fix it with S1tool.
but it seems the phone never had trim aera backup.
thanks a lot.

serkansınan · Mar 10, 2018

sa z5 hard brick s1 boot help me

Welcome to S1 tool.
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 : 13484502
HARDWARE ID : 04000100E1009400
HASH :F421B16FFDD52124A7107C2156B6C478355991BC9D88F0F8682CD08F127A0FA5
HARDWARE ID 04000100E1009400 NOT SUPPORTED
Elapsed:27 secs.

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

PROCEDURE STOPPED BY USER
Elapsed:19 secs.

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 ...
llbug: write error: "Aygıt komutu algılayamıyor"
llbug: blk write fail.fatal
Elapsed:24 secs.

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 : 13484502
HARDWARE ID : 04000100E1009400
HASH :F421B16FFDD52124A7107C2156B6C478355991BC9D88F0F8682CD08F127A0FA5
HARDWARE ID 04000100E1009400 NOT SUPPORTED
Elapsed:147 secs.

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 ...
llbug: write error: "Aygıt komutu algılayamıyor"
llbug: blk write fail.fatal
Elapsed:77 secs.

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 : 13484502
HARDWARE ID : 04000100E1009400
HASH :F421B16FFDD52124A7107C2156B6C478355991BC9D88F0F8682CD08F127A0FA5
HARDWARE ID 04000100E1009400 NOT SUPPORTED
Elapsed:18 secs.

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 : 13484502
HARDWARE ID : 04000100E1009400
HASH :F421B16FFDD52124A7107C2156B6C478355991BC9D88F0F8682CD08F127A0FA5
HARDWARE ID 04000100E1009400 NOT SUPPORTED
Elapsed:22 secs.

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

PROCEDURE STOPPED BY USER
Elapsed:99 secs.

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 : 13484502
HARDWARE ID : 04000100E1009400
HASH :F421B16FFDD52124A7107C2156B6C478355991BC9D88F0F8682CD08F127A0FA5
HARDWARE ID 04000100E1009400 NOT SUPPORTED
Elapsed:91 secs.

_3F · May 13, 2018

Loader not responding

Hi, can anyone clarify what does this code mean ? LOADER AID: 0004 or why this loader may not responding ?

Code:

RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
can't get S1 command header
LOADER NOT RESPONDING
Elapsed:57 secs.

well...

What commands will be pushed for initializing after sending ? Does available any source code for s1tools ?

Does exist any way to execute custom bootloader like u-boot etc. ?
Mainly what's the problem and what to do for this case. I mean from what to start o_o

By the way, initially I used GND from usb connector on board, but now [ SOMC Flash Device ] always is activated after connecting without test-point and without battery of course. Any idea ?

munjeni said:
If you have ta backup (TA.img) from your phone than you can try with this http://forum.xda-developers.com/showpost.php?p=56571705&postcount=314 it is for z1c but I am sure it will work too for your model (but please open syn file set archive after tool generate them for you, to be sure custom-reset.ta is not blank or probably with some stupid data!)

I have TA but I can't get S1 command header as you can see above. Do you know what's problem may be for this ? Thanks.

-----
upd: hmm, just noticed postfix - '...MSM8974_23_4_AID_4' but, what's wrong with loader

where are you

p.s: z ultra C6833 is not mine, however will be good to fix this anyway

arminalvand · May 17, 2018

My phone is xa1 plus please help to me my phone is just red light when connect to usb but not reset with power + up volume

prashanth12 · Jun 27, 2018

i havesame problem somc flash mode in e1 dual plz help me

daaabs · Jul 1, 2018

Hi everybody. My Z Ultra was bricked after I accidentally connected a cheap OEM magnetic charger the wrong way round ("reverse charging" - I'm not the first person to do it)

https://forum.xda-developers.com/xperia-z-ultra/help/damage-to-z-ultra-magnetic-charger-t2806392

Power button produced a vibration. Power and volume down produced an Xperia splash screen and nothing else. I removed the battery and charged it for about 45 minutes directly at the terminals. I followed the steps in the OP and it didn't work. The readout says:

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 : 6ED79402
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...

RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 0294D76E
FLASH ID: "0015/01000001"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"

WRITING PACKAGES ...
Processing package
C:\Users\Daniel\Desktop\C6806\14_2_A_0_290.APP_SW_Togari_GENERIC_1271_5715_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
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Togari_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:130 secs.

What's the problem? Is it just a hardware problem?

AdmiralKitteh · Jul 24, 2018

So, from what i've understood;
If my TA is damaged, theres no way im gonna get my Z1 to work again?

krasavinn · Aug 29, 2018

I can't download tools.7z, help pls

XxKing · Sep 13, 2018

Doom Slayer said:
THIS TUTORIAL IS ONLY FOR HARD BRICKED DEVICES.
HARD BRICK MEANS NO FLASHMODE AND NO FASTBOOT.
IN ORDER TO PROCEED DISASSEMBLY OF YOUR DEVICE IS REQUIRED.
IF YOU HAVE WARRANTY,STOP READING THIS, GO THE SONY SERVICE AND PLAY STUPID.
AS AFTER OPENING YOUR DEVICE, YOUR WARRANTY IS 100% VOID.
I AM NOT RESPONSIBLE FOR ANY DAMAGE.
YOU'VE BEEN WARNED.

Let's get started.
1. Download tools.7z from attachments and pack for your device.
2. Install ggsetup-3.0.0.7.exe
3. Open the back cover of your device.
4. Find the test point (See attachments).
5. Disconnect a battery, connect a usb cable. LED RED will start to blink.
6. Using the paper clip connect your test point with the GND. I used the metal shield in the middle of the motherboard.
7. Open the device manager, you should see SEMC Flash Device. If no, you did something wrong.
8. Disconnect your phone from computer.
9, Repeat the step 5.
10.Run the s1tool and select S1 MSM8974 EMERGENCY for the phone type.
11. Press the flash button, and choice the APP file for your device.
12. Press testpoint ready and repeat the step 6.
13. Remove the testpoint and press READY, when program will ask you to do so.
14. If flash was successful, you may disconnect your phone from usb, connect your battery and try to boot.You may have to charge your battery.
15. Now you can flash your device normally using software.

P.S.
I was not be able to flash on windows 8 64bit, but I flashed without problems on XP.

I would like to thank:

the_laser for making the software.

myevilface from support.setool.net for finding testpoint for c69xx.

and my poor Z Ultra which I sacrificed trying to find the test point
Actually I finished him when I wanted to fix audio jack.
Was to happy that my device is fixed and damaged the screen connector

UPDATE:
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET

------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.

can we do this with xperia z2 if so where to find the syn file set file

[GUIDE] Z Ultra and Z1 HARD BRICK RECOVERY

Member

New member

Member

New member

New member

New member

New member

Senior Member

New member

Member

Member

New member

New member

New member

Senior Member

New member

Senior Member

New member

New member

New member

Similar threads

Top Liked Posts