186 replies to this topic

[led7]

2/24/2015 11:11:45 PM Welcome S1 Tool [06.02.2015].
2/24/2015 11:11:45 PM That is small and crippled subset of SETOOL2 service tool.
2/24/2015 11:11:49 PM  
2/24/2015 11:11:49 PM SELECT FIRMWARE PACKAGES
2/24/2015 11:11:49 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2/24/2015 11:11:53 PM CHECKING PACKAGES ...
2/24/2015 11:11:53 PM  
2/24/2015 11:11:53 PM DETACH USB CABLE FROM PHONE
2/24/2015 11:11:53 PM REMOVE BATTERY FROM PHONE
2/24/2015 11:11:53 PM ATTACH TESTPOINT
2/24/2015 11:11:53 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2/24/2015 11:11:53 PM  
2/24/2015 11:12:00 PM will use DLOAD protocol ... 
2/24/2015 11:12:00 PM 0808010600900000
2/24/2015 11:12:00 PM 0D0F50424C5F446C6F6164564552322E30
2/24/2015 11:12:00 PM 162001000100
2/24/2015 11:12:00 PM 17004001000100E1507E00
2/24/2015 11:12:00 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2/24/2015 11:12:00 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
2/24/2015 11:12:00 PM PROCESSING ...
2/24/2015 11:12:01 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
2/24/2015 11:12:01 PM  
2/24/2015 11:12:03 PM Emergency loader uploaded ...
2/24/2015 11:12:04 PM  
2/24/2015 11:12:04 PM RUNNING S1_PRELOADER VER "R5G008"
2/24/2015 11:12:04 PM LOADER AID: 0001
2/24/2015 11:12:04 PM DEVICE ID: 1A48B903
2/24/2015 11:12:04 PM FLASH ID: "0015/00000000"
2/24/2015 11:12:04 PM LOADER VERSION: "R5G008"
2/24/2015 11:12:04 PM  
2/24/2015 11:12:05 PM WRITING PACKAGES ...
2/24/2015 11:12:05 PM Elapsed:15 secs.
2/24/2015 11:13:27 PM PROCEDURE STOPPED BY USER

 

I flash all the 4 .sin by order and even i flash the s1boot.sin only is always the same.

 

 Untitled.png   201.62K   2 downloads

 

 

 

Please see this, "0000000000" any idea why it always zero?

 

 Untitled.png   144.33K   1 downloads

 

Edited by led7, 24 February 2015 - 16:49.

[Jurij]

I'm pretty sure that is some kind of flash driver problem. Maybe try to flash only APPSW, FSP and ELABEL files?

[led7]

Hmm.. What kind of flash driver problem? You think there's a missing driver not installed? But you said only Gordon's state flash driver will be installed and i followed it. Same as in SEMC flash device & s1 loader, but computer will be automatically installing that 2 driver i've said.

 

Later i'll try to flash APPSW, FSP and ELABEL only, because here at office again. Please suggest any more idea that will fixed that problem in s1tool. Thank you sir Jurij!

Edited by led7, 25 February 2015 - 00:43.

[led7]

2/25/2015 8:24:10 PM Welcome S1 Tool [06.02.2015].
2/25/2015 8:24:10 PM That is small and crippled subset of SETOOL2 service tool.
2/25/2015 8:24:19 PM  
2/25/2015 8:24:19 PM SELECT FIRMWARE PACKAGES
2/25/2015 8:24:19 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2/25/2015 8:24:33 PM CHECKING PACKAGES ...
2/25/2015 8:24:33 PM  
2/25/2015 8:24:33 PM DETACH USB CABLE FROM PHONE
2/25/2015 8:24:33 PM REMOVE BATTERY FROM PHONE
2/25/2015 8:24:33 PM ATTACH TESTPOINT
2/25/2015 8:24:33 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2/25/2015 8:24:33 PM  
2/25/2015 8:24:50 PM will use DLOAD protocol ... 
2/25/2015 8:24:50 PM llbug: write error: "The device does not recognize the command"
2/25/2015 8:24:50 PM llbug: blk write fail.fatal
2/25/2015 8:24:50 PM qcSendPacket: can't send packet.
2/25/2015 8:24:50 PM Elapsed:31 secs.

 

 

After flashing APPSW, FSP and ELABEL.sin_file_set 

[Jurij]

It looks like not enough power is supplied by usb cable. After removing testpoint but before pressing Testpoint READY button please attach to your phone battery. Also please make a screenshot of files you are flashing, i'm pretty sure that boot file is not unrared.

[led7]

Done fixing that error. Usb plug is loose.

 

After that i completely flash APPSW, FSP and ELABEL.sin_file_set, but same happens on flashing s1boot only.

 

"WRITING PACKAGES..

Elapsed: (secs)"

 

I research on internet why FLASH ID "0015/00000000" is always show "0". Some comments/post they lost drm keys. I think mine is the same, i lost my drm keys thats why it always show "0". Some other told that they not backup their TA partition after unlocking bootloader, thats why all the important on their phone is all wipe (ithink).

 

I really need your help. Please share any idea on how to fix that problem. No TA backup, lost drm keys on bricked phone

 

Copying TA backup on the same phone, same model Xperia SP C5303, it is possible to fix that problem? 

Edited by led7, 26 February 2015 - 00:50.

[Jurij]

Lost drm keys are normal symptom after unlocking bootloader using official Sony way. There is no way to fix that.

 

 

Copying TA backup on the same phone, same model Xperia SP C5303, it is possible to fix that problem? 

 

No, don't you even try to do that. It's an easy way to brick your phone forever.

 

 

Done fixing that error. Usb plug is loose.

 

After that i completely flash APPSW, FSP and ELABEL.sin_file_set, but same happens on flashing s1boot only.

 

I don't understand you. Setool2 should start flashing files if they are in correct sin_file_set / zip format. Maybe you are not doing testpoint properly? Tomorrow contact me on skype, i can assist you on TeamViewer if you want.

[led7]

I mean same happens when i flash "s1boot.sin_file_set" or APPSW, FSP, ELABEL.sin_file_set

2/25/2015 11:11:45 PM Welcome S1 Tool [06.02.2015].
2/25/2015 11:11:45 PM That is small and crippled subset of SETOOL2 service tool.
2/25/2015 11:11:49 PM 
2/25/2015 11:11:49 PM SELECT FIRMWARE PACKAGES
2/25/2015 11:11:49 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2/25/2015 11:11:53 PM CHECKING PACKAGES ...
2/24/2015 11:11:53 PM 
2/25/2015 11:11:53 PM DETACH USB CABLE FROM PHONE
2/25/2015 11:11:53 PM REMOVE BATTERY FROM PHONE
2/25/2015 11:11:53 PM ATTACH TESTPOINT
2/25/2015 11:11:53 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2/25/2015 11:11:53 PM 
2/25/2015 11:12:00 PM will use DLOAD protocol ... 
2/25/2015 11:12:00 PM 0808010600900000
2/25/2015 11:12:00 PM 0D0F50424C5F446C6F6164564552322E30
2/25/2015 11:12:00 PM 162001000100
2/25/2015 11:12:00 PM 17004001000100E1507E00
2/25/2015 11:12:00 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2/25/2015 11:12:00 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
2/25/2015 11:12:00 PM PROCESSING ...
2/25/2015 11:12:01 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
2/25/2015 11:12:01 PM 
2/25/2015 11:12:03 PM Emergency loader uploaded ...
2/25/2015 11:12:04 PM 
2/25/2015 11:12:04 PM RUNNING S1_PRELOADER VER "R5G008"
2/25/2015 11:12:04 PM LOADER AID: 0001
2/25/2015 11:12:04 PM DEVICE ID: 1A48B903
2/25/2015 11:12:04 PM FLASH ID: "0015/00000000"
2/25/2015 11:12:04 PM LOADER VERSION: "R5G008"
2/25/2015 11:12:04 PM 
2/25/2015 11:12:05 PM WRITING PACKAGES ...
2/25/2015 11:12:05 PM Elapsed:15 secs.
2/25/2015 11:13:27 PM PROCEDURE STOPPED BY USER

I'm doing testpoint properly sir, please see my other previous comments with attach pic of installing "qhsusb_dload" and it's completely installed "Qaualcomm HS-USB QDLoader 9008 (COM10)" then you said force windows update thru Gordon's Gate Flash Driver namely "Zeus Flash Device", right?

 

It's okay with me with TeamViewer.

 

Later you will be online on skype? Inform me.

Edited by faflak, 27 February 2015 - 08:51.

[Jurij]

So your initial problem is damaged partition system, not damaged boot. Mr the_laser made for you new version of S1Tool which allows to skip TA open attempt. Download and run this version:  s1tool 28II2015.exe   3.13MB   4798 downloads of s1tool and try to flash boot file in s1 emergency mode. Post output log here after flash.

[led7]

Using sir laser uploaded s1tool with "SKIP TA OPEN" with "USE EDL MODE"

After removing Testpoint and pressing READY.
 

2/28/2015 6:14:21 PM Welcome S1 Tool [26.02.2015].
2/28/2015 6:14:21 PM That is small and crippled subset of SETOOL2 service tool.
2/28/2015 6:15:20 PM 
2/28/2015 6:15:20 PM SELECT FIRMWARE PACKAGES
2/28/2015 6:15:20 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2/28/2015 6:15:30 PM CHECKING PACKAGES ...
2/28/2015 6:15:30 PM 
2/28/2015 6:15:30 PM DETACH USB CABLE FROM PHONE
2/28/2015 6:15:30 PM REMOVE BATTERY FROM PHONE
2/28/2015 6:15:30 PM ATTACH TESTPOINT
2/28/2015 6:15:30 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2/28/2015 6:15:30 PM 
2/28/2015 6:15:51 PM will use DLOAD protocol ... 
2/28/2015 6:15:51 PM 0808010600900000
2/28/2015 6:15:51 PM 0D0F50424C5F446C6F6164564552322E30
2/28/2015 6:15:51 PM 162001000100
2/28/2015 6:15:51 PM 17004001000100E1507E00
2/28/2015 6:15:51 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2/28/2015 6:15:51 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9 EC7074DDAE8B05CDC8E1
2/28/2015 6:15:51 PM PROCESSING ...
2/28/2015 6:15:52 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
2/28/2015 6:15:52 PM 
2/28/2015 6:16:01 PM llbug: write error: "The device does not recognize the command"
2/28/2015 6:16:01 PM llbug: blk write fail.fatal
2/28/2015 6:16:01 PM qcSendPacket: can't send packet.
2/28/2015 6:16:01 PM Elapsed:40 secs.
2/28/2015 6:16:08 PM 

After not removing Testpoint and pressing READY.

2/28/2015 6:16:08 PM SELECT FIRMWARE PACKAGES
2/28/2015 6:16:08 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
2/28/2015 6:16:09 PM CHECKING PACKAGES ...
2/28/2015 6:16:09 PM 
2/28/2015 6:16:09 PM DETACH USB CABLE FROM PHONE
2/28/2015 6:16:09 PM REMOVE BATTERY FROM PHONE
2/28/2015 6:16:09 PM ATTACH TESTPOINT
2/28/2015 6:16:09 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
2/28/2015 6:16:09 PM 
2/28/2015 6:16:15 PM will use DLOAD protocol ... 
2/28/2015 6:16:15 PM 0808010600900000
2/28/2015 6:16:15 PM 0D0F50424C5F446C6F6164564552322E30
2/28/2015 6:16:15 PM 162001000100
2/28/2015 6:16:15 PM 17004001000100E1507E00
2/28/2015 6:16:15 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
2/28/2015 6:16:15 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9 EC7074DDAE8B05CDC8E1
2/28/2015 6:16:15 PM PROCESSING ...
2/28/2015 6:16:16 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
2/28/2015 6:16:16 PM 
2/28/2015 6:16:17 PM Emergency loader uploaded ...
2/28/2015 6:16:27 PM 
2/28/2015 6:16:27 PM RUNNING S1_PRELOADER VER "R5G008"
2/28/2015 6:16:27 PM LOADER AID: 0001
2/28/2015 6:16:28 PM DEVICE ID: 1A48B903
2/28/2015 6:16:28 PM FLASH ID: "0015/00000000"
2/28/2015 6:16:28 PM LOADER VERSION: "R5G008"
2/28/2015 6:16:28 PM 
2/28/2015 6:16:28 PM WRITING PACKAGES ...
2/28/2015 6:16:28 PM Elapsed:20 secs.
2/28/2015 6:16:36 PM PROCEDURE STOPPED BY USER

But after i click "SKIP TA OPEN" and click FLASH the "check" on SKIP TA OPEN will disappear.

Edited by faflak, 02 March 2015 - 13:36.

[Jurij]

It was a bug in s1tool. Try this version:  s1tool 28II2015.exe   3.13MB   4798 downloads

[led7]

Using updated s1tool created by sir laser.

S1 EMERGENCY MODE, [?] SKIP TA OPEN

 

Removing Testpoint, and Pressing "READY"

 

3/2/2015 8:09:08 PM Welcome S1 Tool [28.02.2015].
3/2/2015 8:09:08 PM That is small and crippled subset of SETOOL2 service tool.
3/2/2015 8:09:20 PM  
3/2/2015 8:09:20 PM SELECT FIRMWARE PACKAGES
3/2/2015 8:09:20 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
3/2/2015 8:09:25 PM CHECKING PACKAGES ...
3/2/2015 8:09:25 PM  
3/2/2015 8:09:25 PM DETACH USB CABLE FROM PHONE
3/2/2015 8:09:25 PM REMOVE BATTERY FROM PHONE
3/2/2015 8:09:25 PM ATTACH TESTPOINT
3/2/2015 8:09:25 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
3/2/2015 8:09:25 PM  
3/2/2015 8:09:32 PM will use DLOAD protocol ... 
3/2/2015 8:09:32 PM 0808010600900000
3/2/2015 8:09:32 PM 0D0F50424C5F446C6F6164564552322E30
3/2/2015 8:09:32 PM 162001000100
3/2/2015 8:09:32 PM 17004001000100E1507E00
3/2/2015 8:09:32 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
3/2/2015 8:09:32 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
3/2/2015 8:09:32 PM PROCESSING ...
3/2/2015 8:09:33 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
3/2/2015 8:09:33 PM  
3/2/2015 8:09:39 PM llbug: write error: "The device does not recognize the command"
3/2/2015 8:09:39 PM llbug: blk write fail.fatal
3/2/2015 8:09:39 PM qcSendPacket: can't send packet.
3/2/2015 8:09:39 PM Elapsed:18 secs.
3/2/2015 8:09:49 PM  

 

 

 

Using updated s1tool created by sir laser.

S1 EMERGENCY MODE, [?] SKIP TA OPEN

 

Not Removing Testpoint, and Pressing "READY"

 

3/2/2015 8:09:49 PM SELECT FIRMWARE PACKAGES
3/2/2015 8:09:49 PM YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
3/2/2015 8:09:51 PM CHECKING PACKAGES ...
3/2/2015 8:09:51 PM  
3/2/2015 8:09:51 PM DETACH USB CABLE FROM PHONE
3/2/2015 8:09:51 PM REMOVE BATTERY FROM PHONE
3/2/2015 8:09:51 PM ATTACH TESTPOINT
3/2/2015 8:09:51 PM PRESS "READY", THEN ATTACH USB CABLE TO PHONE
3/2/2015 8:09:51 PM  
3/2/2015 8:09:59 PM will use DLOAD protocol ... 
3/2/2015 8:09:59 PM 0808010600900000
3/2/2015 8:09:59 PM 0D0F50424C5F446C6F6164564552322E30
3/2/2015 8:09:59 PM 162001000100
3/2/2015 8:09:59 PM 17004001000100E1507E00
3/2/2015 8:09:59 PM PRODUCT DETECTED: "SONY MSM8960-3 Pro OEM1 Fused"
3/2/2015 8:09:59 PM 1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9EC7074DDAE8B05CDC8E1
3/2/2015 8:09:59 PM PROCESSING ...
3/2/2015 8:10:01 PM REMOVE TESTPOINT NOW, THEN PRESS "READY"
3/2/2015 8:10:01 PM  
3/2/2015 8:10:02 PM Emergency loader uploaded ...
3/2/2015 8:10:09 PM  
3/2/2015 8:10:09 PM RUNNING S1_PRELOADER VER "R5G008"
3/2/2015 8:10:09 PM LOADER AID: 0001
3/2/2015 8:10:10 PM DEVICE ID: 1A48B903
3/2/2015 8:10:10 PM FLASH ID: "0015/00000000"
3/2/2015 8:10:10 PM LOADER VERSION: "R5G008"
3/2/2015 8:10:10 PM  
3/2/2015 8:10:10 PM WRITING PACKAGES ...
3/2/2015 8:10:10 PM Processing package
3/2/2015 8:10:10 PM C:\Users\PC-8\Desktop\s1tool\S1Boot_R11B023_HWID7E50E1.SIN_FILE_SET
3/2/2015 8:10:10 PM  
3/2/2015 8:10:10 PM Processing ACPU files
3/2/2015 8:10:10 PM PROCESSING: boot.sin
3/2/2015 8:10:10 PM FATAL ERROR [ 0x0508:_sin_header_verification, err: 000A ]
3/2/2015 8:10:10 PM error while uploading final HDR block
3/2/2015 8:10:10 PM Break.
3/2/2015 8:10:10 PM FINISHED
3/2/2015 8:10:10 PM Elapsed:20 secs.

 

Edited by faflak, 02 March 2015 - 13:37.

[Jurij]

Did you tried to flash only appsw, fsp and elabel?

[led7]

Yup! Flashing s1boot only and appsw only and appsw, fsp, elabel tried it too.

 

I've read on previous post/comments, in same problem/error from sir seli1987

12/22/2014 01:01:12 ?.? Processing ACPU files
12/22/2014 01:01:12 ?.? PROCESSING: loader.sin
12/22/2014 01:01:12 ?.? FATAL ERROR [ 0x0508:_sin_header_verification, err: 000A ]
12/22/2014 01:01:12 ?.? error while uploading final HDR block
12/22/2014 01:01:12 ?.? Break.
12/22/2014 01:01:12 ?.? FATAL ERROR [ limited, err: 0010 ]
12/22/2014 01:01:12 ?.? FINISHED
12/22/2014 01:01:12 ?.? Elapsed:17 secs.

"FATAL ERROR [ limited, err: 0010 ]"

 

This one is not the same error i got, you said on your reply "No. Your phone is a brick. Nothing more to do." There's a chance my phone will be fix?

Edited by faflak, 03 March 2015 - 08:07.

[Jurij]

Ask the_laser and show him those logs but i hardly think so. If it's not a bug in s1tool, your phone has serious problem and only main board swap can help... but it's just my humble opinion.

Well, we know the answer from the_laser. Trim area damaged, this babe is a brick. Buy working Xperia SP with broken lcd and swap main board.

[JE0]

I confirm that the testpoint pictured for the SP is correct.

 

However, I think I've accidently used a Russian(?) firmware (the text looked cyrillic), and I can only make emergency phonecalls.

It doesn't complain that the sim card is not present as it does when I remove the simcard.

I presume this means that the phone is now simlocked to some foreign provider?

 

If I continue ahead to install cyanogenmod over the top of the current install, will it fix this issue, or will I need to fix this first?

 

Thanks very much for posting this tutorial!

[Jurij]

 

However, I think I've accidently used a Russian(?) firmware (the text looked cyrillic), and I can only make emergency phonecalls.

 

So change language. All android firmwares has all languages in it.

 

 

It doesn't complain that the sim card is not present as it does when I remove the simcard.

 

Insert sim card with enabled PIN. If it will not ask for PIN, maybe sim card reader is damaged... It's hard to say.

 

 

I presume this means that the phone is now simlocked to some foreign provider?

 

If phone was unlocked before flash it will be unlocked after flash. Flashing has nothing in common with simlock state.

 

 

If I continue ahead to install cyanogenmod over the top of the current install, will it fix this issue, or will I need to fix this first?

 

Try and see. But be careful, it's easy to brick phone permanently when playing with CyanogenMod.

[JE0]

Thanks for the quick reply.

 

It doesn't look like I can unlock the bootloader due to it not being allowed (Bootloader unlock allowed: No).

 

However, I could install cyanogenmod 12 (lollipop) using

Please Login or Register to see this Hidden Content

method (warning, it most likely played a part in me needing this tutorial!).

It mostly worked, except for cellular data - which may be fixed at some point.

 

In case it helps anyone else, the cause of my bricking was:

• Rooting the device (step 1 of

  Please Login or Register to see this Hidden Content

  )
• Install Clockwork Recovery (step 2)
• Wiping to factory using Clockwork Recovery
• Installing cyanogenmod 12 (step 3)
• Install Google Apps (step 4)
• (normally use the device for a while)
• Wiping to factory again
• Attempting to install cyanogenmod 11 (using step 3, but substituting with a download from the main cyanogenmod website). The install failed.

I have a backup of the original system using clockwork, so I'll reset back to that.

Unfortunately, I don't make a backup of the TA partition, so I'll make do without the special features.

 

Thanks again!

Edited by JE0, 06 March 2015 - 20:04.

[Jurij]

Flash your phone with stock Sony firmware and check if all is working. If yes - you are lucky.

 

 

It doesn't look like I can unlock the bootloader due to it not being allowed (Bootloader unlock allowed: No).

 

No you can't and probably that will never be possible.

[bigboy85]

hello can you help me i flashed this c5303 cause some system errors after flashed phone brick I did ta backup with setool box before flashing

the phone can be detected by the pc in zeus and driver can be changed to QHSUSB drivers of medusa box or whatever I want 

 

the s1tool 28II2015 program only detec it when driver is in zeus driver installed but the s1tool 28II2015 program says:

 

PHONE NOT SUPPORTED IN THIS MODE

 

 

 

will use DLOAD protocol ... 
0808010600900000
0D0F50424C5F446C6F6164564552322E30
162001000100
17004001000100E1108800
1801000F43240892D02F0DC96313C81351B40FD5029ED98FF9 EC7074DDAE8B05CDC8E1
PHONE NOT SUPPORTED IN THIS MODE
Elapsed:26 secs.

 

 

now if  I change driver to QHSUSB  anything happens

 

make test point just don´t work either

 

plz I added ta backup in case it can help       ta_35581005418943.zip   97.11K   45 downloads