I have XperiaZ1(SO-01F for Japan)
I had mistake to install Z1f's rom.
It didn't light but I could hear touch sound.
But, I can't do enable adb.
I want to recover by this way.
So, I want to do this way.
However S1 tool says "Waiting for Phone".
PC show me "SEMC Flash Devices".
Why I can't those....?
Please tell me solution.
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.
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
------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.
I am getting error
17-11-2016 21:36:52 Welcome to S1 tool.
17-11-2016 21:36:52 That is small and crippled subset of SETOOL2 service tool.
17-11-2016 21:37:26
17-11-2016 21:37:26 SELECT FIRMWARE PACKAGES
17-11-2016 21:37:26 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
17-11-2016 21:37:35 CHECKING PACKAGES ...
17-11-2016 21:37:35
17-11-2016 21:37:35 DETACH USB CABLE FROM PHONE
17-11-2016 21:37:35 REMOVE BATTERY FROM PHONE
17-11-2016 21:37:35 ATTACH TESTPOINT
17-11-2016 21:37:35 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
17-11-2016 21:37:35
17-11-2016 21:38:50 will use Sahara protocol ...
17-11-2016 21:38:50 REMOVE TESTPOINT NOW, THEN PRESS "READY"
17-11-2016 21:38:50
17-11-2016 21:39:02 PROCESSING ...
17-11-2016 21:39:02 SERIAL NUMBER : A4F31802
17-11-2016 21:39:02 HARDWARE ID 00000000E1007B00 NOT SUPPORTED
17-11-2016 21:39:02 HARDWARE ID : 00000000E1007B00
17-11-2016 21:39:02 NOT SUPPORTED HASH :CC3153A80293939B90D02D3BF8B23E0292E452FEF662C74998421ADAD42A380F
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET
Since I bricked my TA I was not able to repair TA by using gdfs, do not know why, but I created tool for unbricking TA partition, TA backup is required to get tool working! Here is tool for all who have TA.img and bricked TA partition inside phone, tool will convert your TA.img to TA_unbrick.SIN_FILE_SET so you can easily repair your TA partition and flash the rest of firmware, enjoy! Windows machine is required!
How to use:
- put TA.img to the same folder
- run ta_gen.exe
1st of all i dont know if my phone is hardbrick, even i charge it for hours it wont turn on. And when i try to repair it via Xperia Companion and Flashtool, the phone cant be recognize (there is this sound from laptop when a device is connected, then another sound because of disconnection,and so on..)so the process wont continue. Then i try this method,and i am seeing "SOMC" instead of "SEMC",also, When i connect my phone to my laptop (win 8 64-bit), as for this instruction " 5. Disconnect a battery, connect a usb cable. LED RED will start to blink. " , there's no red led blinking on my phone (z1 c6903). And also i've got this log from s1tool please any help? THANKS!
Hello, Mr.Doom slayer pls send me the procedures as a videos. My sony z1 is also has the same pblm red light blinking.pls help me to recover the phone.I'm unable to understand the procedures.so pls send me a video about working on the above procedures..pls pls pls....
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 : 7FA0D105
HARDWARE ID 00000000E1107B00 NOT SUPPORTED
HARDWARE ID : 00000000E1107B00
NOT SUPPORTED HASH :CC3153A80293939B90D02D3BF8B23E0292E452FEF662C74998421ADAD42A380F
Elapsed:13 secs.
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.
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
------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.
flash TA_unbrick.SIN_FILE_SET and after that flash amami_testpoint.SIN_FILE_SET
and all was fix
when you can't flash 14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET or amami_testpoint.SIN_FILE_SET
You must to flash TA_unbrick.SIN_FILE_SET at first . and then you'll found the 14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET or amami_testpoint.SIN_FILE_SETc
can flash in !!!!!
hello everybody,
jumping in here to join the Z1 brick club
I've got one too and its a long story but i want to mention all the details and everything i have tried already.
History of what led to this problem (infamous sony battery drain of death)
about roughly 2 weeks ago, the battery died, only red LED when connected to charger and 3 times blinking red LED when trying to power on. no fastboot either
after trying to charge through different chargers (ranging from 5V 500mA to 5V 2.1A) and failing to revive the battery , i finally disassembled the device and used a multi-meter to check the battery which showed it at 2.2V, so i hooked up its +ve and -Ve pins to a 5V 2A usb charger and let it charge to a full 3.8V and then plugged in the battery and tried powering on again.
but again multiple attempts to get my phone power up/charge the Z1 failed.
then i tried this one method that said plug in battery, hold power button and it will show 3 times red LED blink, and without releasing the power button plug in the charger and leave it to charge and it will power on.
that failed too.
and after charging it for a while, when i tried to power it on by holding power button, i felt a small duration vibrations and then no response from the phone, the LED, screen everything was blank.
tried connecting it to charger again same thing happened and upon my 4th attempt my phone totally stoped responding, even the small vibration was gone and there is no LED when i connect to charger
after leaving it for a day like that, i connected it to my laptop and it appeared as a Qualcomm HS-USB Qdloader 9008 device under PORTS in device manager. after some googling i found out i have a bricked Z1 with most probably a damaged bootloader.
so i looked for a couple guides and followed them for a fix
so following is the summary of what i have tried so far my phone is NOT ROOTED, LOCKED BOOTLOADER and STOCK ANDROID 5.1.1
SOFTWARE ENVIRONMENT (Phone and PC)
PHONE
Stock Android 5.1.1 (German Firmware C6903_14.6.A.1.236_DE.ftf)
NO OTA updates after flashing firmware
NOT rooted
LOCKED BOOTLOADER
only apps that were installed at the time of battery darin and then all that followed were MX Player, UC Browser and ES File Explorer; so overall an untouched stock android phone.
LAPTOP
win 10 64 bit build 1511
all required drivers installed and removed any conflicting software like xperia companion, used disable driver sign enforcement to ensure proper install of drivers.
tried using multiple USB ports and USB cables
and for reference i am following these two guides along with XDA to fix http://sony.yt/topic/7295-english-tutorial-how-to-unbrick-and-update-boot-in-sony-xperia-z1-c6903/ http://saki-sss.blogspot.com/2015/09/s1toolhard-brickxperia-z.html(use google translate please)
the required drivers, software were obtained from above links.
WHAT HAPPENS WHEN I TRY IT 1) if i connect my phone normally into the USB port, it shows as Qualcomm HS-USB Qdloader 9008 under ports in device manager. 2) after i enable emergency mode using the test point (open back cover >> remove plastic frame screwed to the main body >> unplug battery >> connect test point >> plug in battery >> hold power button and release test point)
it now shows as a ZUES FLASH DEVICE under USB controllers in device manager; which i believe is what's supposed to happen. 3) i fire up S1 tools and use S1 emergency mode, click flash choose SIN file and then it asks me to "remove usb cable, remove battery and connect test point, click test point ready and then connect usb cable"
i follow and then phone shows us as SOMC FLASH DEVICE under USB controller (not SEMC flash device as i read somewhere) then process fails.
tried different versions of S1 tool too, one of them shows LOADER AID: DEAD and other one shows LOADER AID: FFFF, rest is same.
NOTE: there is a frame around the battery which needs to be removed in order to take the battery out, and it's got two small connecting pincs on lower right corner, and i understand that frame needs to be put back on in order to power up a normally functioning Z1 and those two pins need to connect.
but for above process, in order to access the test point i have to remove that frame.
am i doing this right?? or the frame needs to be on in order to perform above mentioned steps??
i do not have any form of backup for my phone as i never tried to root it or unlock the bootloader, my main phone is a Droid Razr m and i was getting around to doing a Titanium backup from there and migrate to my Z1 but this happened before i could do that Following is the log from S1 tool.
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 ...
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
and Sony Xperia phone
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
Waiting for phone ...
PROCEDURE STOPPED BY USER
Elapsed:4 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 : 346FA206
HARDWARE ID : 00000000E1007B00
PRODUCT DETECTED: "MSM8974 Unfused"
HASH :CC3153A80293939B90D02D3BF8B23E0292E452FEF662C74998421ADAD42A380F
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "MSM8974_23_4"
LOADER AID: DEAD
can't get S1 command header
LOADER NOT RESPONDING
Elapsed:54 secs.
PS: i tried this on another laptop with Win 7 64 bit, but it only detects the phone as HS USB QDLoader under PORTS all the time, even after installing Gordon's Gate Drivers.
thank you for being patient and reading through my long post
if anybody can point me in the righ direction, or tell me what i might be doing wrong here or help me fix my phone i would be very grateful
the prolem was becuase of wrong TA data (i flashed another TA on my phone )
therefore i got this error : [ 0x0508:_sin_header_verification, err: 000A ]
but How?
this is the story:
i just have TA backup in " .ta (text)" format (using FlashTool S1 Dump in Advance menu -> Trim Area)
but how use it in S1Tool??
after some study in this thread (on posts #201 to #211 of this thread)
and download the script that user @the_laser made for another user @NiM72NiK
i Extracted (zip) that script an found 7D3.gdfs , 7DA.gdfs and 851.gdfs ,,,, then opened them with notepad
and compared with 2.ta from S1 dump of my Device.
i find 7d3 ,7da,851 lines in 2.ta too
Code:
from script file of Sony SP:
tawrite:00020[B][U]7d3[/U][/B][COLOR="Red"]0353494E000004000000002 . . . . .[/COLOR]
tawrite:00020[B][U]7da[/U][/B][COLOR="red"]F648C1307F7E05891D3FE03 . . . . . .[/COLOR]
tawrite:00020[B][U]851[/U][/B][COLOR="red"]02000907DA270F0015024E0 . . . . .[/COLOR]
from 2.ta file of Sony V:
02
000007D2 0001 01
00000[B][U]7D3[/U][/B] [COLOR="Lime"]05CE[/COLOR] [COLOR="Red"]02 00 00 00 03 FC 04 00 00 00 00 00 00 00 29 . . . . .[/COLOR]
00000[B][U]7DA[/U][/B] [COLOR="Lime"]0287[/COLOR] [COLOR="Red"]9E 2B 0C FB 72 37 68 54 76 E7 15 D4 BA 9C 8E . . . . . .[/COLOR]
.
.
.
00000[B][U]851[/U][/B] [COLOR="Lime"]03CA[/COLOR] [COLOR="Red"]02 00 09 07 DA 27 0F 00 15 02 4E 00 03 BC 00 . . . . .[/COLOR]
. . .
.
.
but the number (count) of data after 7d3 and 7da in gdfs script was different from 2.ta file (i think because they are different phone type)
, 851 data was not same in data but same in number
now what u think ? a little risk? again?
ok i made another script with my own TA data
first use c# and wrote simple app to remove spaces of data(red area) in each field(under lined)
then open each script and replace new data, i mean this:
now it's time to repack it.
i putted all file to zip archive and changed zip to sin_file_set
OK connect test point and flow the instruction in first post ,, but now use the file that recently created
after that i could write Boot on my phone
All Done .
Thanks to all member of xda Specially @the_laser for his Sofware and script and helps
here is S1Tool Log:
Code:
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
llbug: blk write fail.fatal
can't send S1 command data [00000006/00000007]
error while uploading DATA block [000001/000001]
LOADER NOT STARTED
Elapsed:99 secs.
SELECT FIRMWARE PACKAGES
YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
CHECKING PACKAGES ...
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
and Sony Xperia phone
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
Waiting for phone ...
PROCEDURE STOPPED BY USER
supported phone was not detected
Elapsed:260 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 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
DEVICE ID: F9E5CF03
FLASH ID: "0015/00000000"
LOADER VERSION: "R5F001"
WRITING PACKAGES ...
Processing package
C:\Users\AbdoRahman_Amani\Desktop\R11AB029.S1_MSM8960_R3_S1Boot_1264_2289_Live_HWID6B50E1.SOFTWARE.SIN_FILE_SET
Processing ACPU files
PROCESSING: R11AB029.S1_MSM8960_R3_S1Boot_1264_2289_Live_HWID6B50E1.SOFTWARE.SIN
ERROR [ 0x0508:_sin_header_verification, err: 000A ]
HDR block not accepted
Break.
ERROR [ S1_TA_Close,limited, err: 0010 ]
FINISHED
Elapsed:29 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 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
DEVICE ID: F9E5CF03
FLASH ID: "0015/00000000"
LOADER VERSION: "R5F001"
WRITING PACKAGES ...
Processing package
C:\Users\AbdoRahman_Amani\Desktop\TA-backup-20140301.101415.sin_file_set
package not contains ACPU files.
Processing update files
PROCESSING: 7d3.gdfs
Writing TA var 0002/07D3/05CE
PROCESSING: 7da.gdfs
Writing TA var 0002/07DA/0287
PROCESSING: 851.gdfs
Writing TA var 0002/0851/03CA
FINISHED
Elapsed:155 secs.
/*
* ^^^^^^^
* |||||||
* writeing TA fields
*----------------------
* writeing boot
* ||||||||
* ˅˅˅˅˅˅˅˅
*/
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
DEVICE ID: F9E5CF03
FLASH ID: "0015/00000000"
LOADER VERSION: "R5F001"
WRITING PACKAGES ...
Processing package
C:\Users\AbdoRahman_Amani\Desktop\R11AB029.S1_MSM8960_R3_S1Boot_1264_2289_Live_HWID6B50E1.SOFTWARE.SIN_FILE_SET
Processing ACPU files
PROCESSING: R11AB029.S1_MSM8960_R3_S1Boot_1264_2289_Live_HWID6B50E1.SOFTWARE.SIN
no update files in package
FINISHED
Elapsed:55 secs.
Hi, I hope somebody can help me.
I didn't understand how you get text file from your TA.img backup.
I have the TA backup of my phone lt25, I would kindly ask if every lt25 have the same TA or are different because I don't know what is it, i'm a noob about this.
Anyway I used the Tool for converting TA.img founded the link to another thread, and i have obtained the sin unbricked file to flash with s1tool.
Than I lunch s1tool 2015 with EDL MODE and i flashed that file.
This is what i get.
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
DEVICE ID: 96887E09
FLASH ID: "0015/00000000"
LOADER VERSION: "R5F001"
WRITING PACKAGES ...
Processing package
C:\Users\rikic\Desktop\Unbrick Xperia V\MSM8960\TA_unbrick.SIN_FILE_SET
package not contains ACPU files.
Processing update files
PROCESSING: 02.ta
Writing TA var 0002/07D3/05CE
ERROR [ S1_TA_WriteUnit,06_:_TA_write_unit_failed, err: 0026 ]
Fail
Writing TA var 0002/0851/03CA
ERROR [ S1_TA_WriteUnit,limited, err: 0010 ]
Fail
Writing TA var 0002/07DA/0287
ERROR [ S1_TA_WriteUnit,limited, err: 0010 ]
Fail
ERROR [ S1_TA_Close,limited, err: 0010 ]
FINISHED
Elapsed:126 secs.
hello everybody,
jumping in here to join the Z1 brick club
I've got one too and its a long story but i want to mention all the details and everything i have tried already.
History of what led to this problem (infamous sony battery drain of death)
about roughly 2 weeks ago, the battery died, only red LED when connected to charger and 3 times blinking red LED when trying to power on. no fastboot either
after trying to charge through different chargers (ranging from 5V 500mA to 5V 2.1A) and failing to revive the battery , i finally disassembled the device and used a multi-meter to check the battery which showed it at 2.2V, so i hooked up its +ve and -Ve pins to a 5V 2A usb charger and let it charge to a full 3.8V and then plugged in the battery and tried powering on again.
but again multiple attempts to get my phone power up/charge the Z1 failed.
then i tried this one method that said plug in battery, hold power button and it will show 3 times red LED blink, and without releasing the power button plug in the charger and leave it to charge and it will power on.
that failed too.
and after charging it for a while, when i tried to power it on by holding power button, i felt a small duration vibrations and then no response from the phone, the LED, screen everything was blank.
tried connecting it to charger again same thing happened and upon my 4th attempt my phone totally stoped responding, even the small vibration was gone and there is no LED when i connect to charger
after leaving it for a day like that, i connected it to my laptop and it appeared as a Qualcomm HS-USB Qdloader 9008 device under PORTS in device manager. after some googling i found out i have a bricked Z1 with most probably a damaged bootloader.
so i looked for a couple guides and followed them for a fix
so following is the summary of what i have tried so far my phone is NOT ROOTED, LOCKED BOOTLOADER and STOCK ANDROID 5.1.1
SOFTWARE ENVIRONMENT (Phone and PC)
PHONE
Stock Android 5.1.1 (German Firmware C6903_14.6.A.1.236_DE.ftf)
NO OTA updates after flashing firmware
NOT rooted
LOCKED BOOTLOADER
only apps that were installed at the time of battery darin and then all that followed were MX Player, UC Browser and ES File Explorer; so overall an untouched stock android phone.
LAPTOP
win 10 64 bit build 1511
all required drivers installed and removed any conflicting software like xperia companion, used disable driver sign enforcement to ensure proper install of drivers.
tried using multiple USB ports and USB cables
and for reference i am following these two guides along with XDA to fix http://sony.yt/topic/7295-english-tutorial-how-to-unbrick-and-update-boot-in-sony-xperia-z1-c6903/ http://saki-sss.blogspot.com/2015/09/s1toolhard-brickxperia-z.html(use google translate please)
the required drivers, software were obtained from above links.
WHAT HAPPENS WHEN I TRY IT 1) if i connect my phone normally into the USB port, it shows as Qualcomm HS-USB Qdloader 9008 under ports in device manager. 2) after i enable emergency mode using the test point (open back cover >> remove plastic frame screwed to the main body >> unplug battery >> connect test point >> plug in battery >> hold power button and release test point)
it now shows as a ZUES FLASH DEVICE under USB controllers in device manager; which i believe is what's supposed to happen. 3) i fire up S1 tools and use S1 emergency mode, click flash choose SIN file and then it asks me to "remove usb cable, remove battery and connect test point, click test point ready and then connect usb cable"
i follow and then phone shows us as SOMC FLASH DEVICE under USB controller (not SEMC flash device as i read somewhere) then process fails.
tried different versions of S1 tool too, one of them shows LOADER AID: DEAD and other one shows LOADER AID: FFFF, rest is same.
NOTE: there is a frame around the battery which needs to be removed in order to take the battery out, and it's got two small connecting pincs on lower right corner, and i understand that frame needs to be put back on in order to power up a normally functioning Z1 and those two pins need to connect.
but for above process, in order to access the test point i have to remove that frame.
am i doing this right?? or the frame needs to be on in order to perform above mentioned steps??
i do not have any form of backup for my phone as i never tried to root it or unlock the bootloader, my main phone is a Droid Razr m and i was getting around to doing a Titanium backup from there and migrate to my Z1 but this happened before i could do that Following is the log from S1 tool.
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 ...
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
and Sony Xperia phone
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
Waiting for phone ...
PROCEDURE STOPPED BY USER
Elapsed:4 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 : 346FA206
HARDWARE ID : 00000000E1007B00
PRODUCT DETECTED: "MSM8974 Unfused"
HASH :CC3153A80293939B90D02D3BF8B23E0292E452FEF662C74998421ADAD42A380F
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "MSM8974_23_4"
LOADER AID: DEAD
can't get S1 command header
LOADER NOT RESPONDING
Elapsed:54 secs.
PS: i tried this on another laptop with Win 7 64 bit, but it only detects the phone as HS USB QDLoader under PORTS all the time, even after installing Gordon's Gate Drivers.
thank you for being patient and reading through my long post
if anybody can point me in the righ direction, or tell me what i might be doing wrong here or help me fix my phone i would be very grateful
okay guys, i have some progress and i hope this will be a step towards unbricking my Z1
so here is the update on my situation,
Battery has been charged externally to 3.8V and then put into the phone,
If i press the power button, there is a short vibration and then nothing, blank display and no LEDs, i then have to force shutdown using PWR + Vol Up because nothing else works.
If i
Connect Charger >> Red LED, Remove charger >> Still Red LED until i force shutdown using PWR + Vol Up
Connect to PC >> Red LED, Remove from PC >> Still Red LED and same response as above (also can't see anything new connected in Device Manager too)
and if i Fire Up S1 tool of Sony FlashTool
PWR Up + Vol Up and connect to PC >> Red LED for a split Second and then Constant Blue LED!!!!!!! which i believe is the Fastboot Mode (my BL is locked, so falshing any images don't work, and Reboot to Bootloader command shows as successfully finished in ADB Window, but phone is still in the same condition that is constant Blue LED)
OR
Vol Down and connect to PC >> Red LED for a split Second and then Constant Green LED!!!!!!! (although S1tool or Sony Flashtool still wont recognize the device and Device Manager Shows Unknown Device )
and in both of the above cases, removing the USB cable doesn't turn off the Green/Blue LED, i have to force shutdown using PWR + Vol Up
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.
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
------------------------------------------------------------------------------------------------------------
If I helped you to save money, you can buy me a beer or two, which is cheaper than a new motherboard.
Tool for converting TA.img to TA_unbrick.SYN_FILE_SET
Since I bricked my TA I was not able to repair TA by using gdfs, do not know why, but I created tool for unbricking TA partition, TA backup is required to get tool working! Here is tool for all who have TA.img and bricked TA partition inside phone, tool will convert your TA.img to TA_unbrick.SIN_FILE_SET so you can easily repair your TA partition and flash the rest of firmware, enjoy! Windows machine is required!
How to use:
- put TA.img to the same folder
- run ta_gen.exe
i'm assuming that your problem is because you wrote foreign trim area into your phone. if your phone have damaged trim area ( format/rewrite trim area partition ) - phone is brick.
So who else thinks this thread should be featued on the portal?
Ive already submitted via the news tip button and pmed @SammiSaysHello since she writes alot of xperia articles.
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
