[REPAIR HARD BRICK] Test Point For Xperia Z1 Compact

[toanvd]

As I said, ta.emmc.win is from a TWRP backup.
I suppose you did yours with ta_gen?
In your screenshot, I guess it's the "TA" file that you can use (biggest file).
Because the icon represents an ISO file, the extension is hidden by your windows folder settings (may be TA.img : right click > properties and see file type if it's something ".img").
But compared to mine which is 2MB, yours is very tiny...
Try with it, but I can't assure you it would work...

 

[Edzus]

can someone send me thare ta partition which can i flash
my pphone is already dead so no trouble in trying

---------- Post added at 11:20 PM ---------- Previous post was at 11:17 PM ----------

can someone send me their ta partition so i can flash it ,my phone is dead so it doesnt hurt to try thx

Bad, I had beckups from is running the same phone...

---------- Post added at 12:49 PM ---------- Previous post was at 11:49 AM ----------

Edzus, can you tell me where you get the 2 files you talked about : "01.ta", "02.ta" ?

Edit : I tested your procedure, and it works (the 01.ta and 02.ta files are generated with the ta_gen tool and included directly in the generated TA_unbrick.SIN_FILE_SET file at the end, then select it in the s1tool.exe instead of amami_testpoint.SIN_FILE_SET) !! You saved me and my phone !! Thank you a lot !!

I'm glad that it helped you

---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------

i dont understand your post please write again

Sorry, but if you do not understand, you lack the knowledge to do this

---------- Post added at 01:00 PM ---------- Previous post was at 12:54 PM ----------

@toanvd i dont have ta.emmc.win file please help me

1) change the computer settings to show file types.
2) The first file is required, sold by zip and de-archive

 

[2net2]

pls help dont have bck up

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

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

WRITING PACKAGES ...
Processing package
C:\Users\nehj\Desktop\fw\amami_testpoint.SIN_FILE_SET

WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_RHINE1.2_LA1.04_19
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_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
PROCESSING : emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Amami_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_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:86 secs.

 

[munjeni]

@toanvd i dont have ta.emmc.win file please help me

On picture you posted I can see your TA is 256kb which is wrong and probably broken! Z1c have 2mb of the TA! Post your backup archive, I want to see what is wrong with your backup, maybe it is somehow archived!

 

[munjeni]

pls help dont have bck up

There is no magic that can help you without TA backup!!! Sugestion, next time read twice carefully everything before you go to play with any phone! Nobody can repair your phone now since every phone have unique trim area! You can't use it from any phone!

 

[munjeni]

New ta_gen is out http://forum.xda-developers.com/showpost.php?p=56571705&postcount=314

 

[Krisham0306]

Hi Mujeni,
i am getting logs and it says boot updated , but my phone is not powering on. can you pls help me. i am reachable on [email protected]

 

[munjeni]

Hi Mujeni,
i am getting logs and it says boot updated , but my phone is not powering on. can you pls help me. i am reachable on [email protected]

Now use flashtool and reflash whole rom, after that restore your full trim area

 

[Krisham0306]

Now use flashtool and reflash whole rom, after that restore your full trim area

Hi Mujeni, just for information, this is the first time, i am trying something like this, hence i am not aware of the whole stuff. My mobile had suddenly switched off by itself and not turning on. When i was searching for how to recover, i got this post. your posting help me to identify the TP, did the emergency loader process. But still post that the LED is still flashing when connected to power source or laptop.

I tried to connect to flash tool, but it just gives an error that debugging is not enabled. The device does not get detected.

Even after doing the bootloader process, the red led in the mobile still is flashing when connected for charging or laptop USB plug. Does it mean that the first step itself is still not successful?

 

[munjeni]

Hi Mujeni, just for information, this is the first time, i am trying something like this, hence i am not aware of the whole stuff. My mobile had suddenly switched off by itself and not turning on. When i was searching for how to recover, i got this post. your posting help me to identify the TP, did the emergency loader process. But still post that the LED is still flashing when connected to power source or laptop.

I tried to connect to flash tool, but it just gives an error that debugging is not enabled. The device does not get detected.

Even after doing the bootloader process, the red led in the mobile still is flashing when connected for charging or laptop USB plug. Does it mean that the first step itself is still not successful?

You must post more details here including log of the s1tool! Write every each step you done!

 

[Krisham0306]

You must post more details here including log of the s1tool! Write every each step you done!

Hi Munjeni,

Step 1: Identified test point and followed the steps as mentioned in (Z1C_hardbrick_repair.exe) and loaded the amami_testpoint.SIN_FILE_SET. Below logs: Even Post Step 1, the LED keep blinking when connected for charging or to laptop.
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 : 5473F008
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...

RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 08F07354
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"

WRITING PACKAGES ...
Processing package
C:\Users\LSLAKSH\Desktop\fw\amami_testpoint.SIN_FILE_SET

WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_RHINE1.2_LA1.04_19
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_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
PROCESSING : emmc_appsboot_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Amami_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_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:73 secs.

Step 2: Tried to connecting flashtool after Step 1, but device does not get detected.

 

[munjeni]

Well, you done one step but you not done more important step. You must use ta_gen.exe http://forum.xda-developers.com/showpost.php?p=56571705&postcount=314 to regenerate your broken trim area! For that you must have your phone trim area backup (TA.img), without that you can't repair your phone! You can't use that from any other phone since if you do that you will end with dead mainboard! If you have your phone trim area backup use that tool to make another syn file set to use with s1tool, post your log here...

 

[Krisham0306]

I don't have any file or backup like that. I just have only a general Xperia transfer backup file, which I used when changing from my z1 compact to z1. Does it mean that, now I cannot recover the phone unless the main board is changed, which can be done only at Sony service centres?

 

[munjeni]

I don't have any file or backup like that. I just have only a general Xperia transfer backup file, which I used when changing from my z1 compact to z1. Does it mean that, now I cannot recover the phone unless the main board is changed, which can be done only at Sony service centres?

You don't have TA backup? Oh oh bad, you can't do anything to your phone , only new mainboard. Making trim area backup is a first step you must do when you buy any Sony smartphone, you're learned leason like me with my first Sony phone

 

[Krisham0306]

You don't have TA backup? Oh oh bad, you can't do anything to your phone , only new mainboard. Making trim area backup is a first step you must do when you buy any Sony smartphone, you're learned leason like me with my first Sony phone

Thank you for the support Munjeni.. Appreciate..

 

[Krisham0306]

Hi Munjeni, just wanted to update this thread.
I replaced the battery in my handset and it's not alive and running too good.. battery was the issue. Now with the new battery, the standby time is excellent. Sony is always the best in the mobile standby time..
Thank you for your help.

 

[xTheDoctah]

Hi! Yesterday I done stupid thing to my phone which hard bricked my phone Played with GPT gdisk, restored wrong gpt backup which killed my device, phone was dead after reboot, had no fastboot, had no bootloader, only had led blinking red-green . But good news I have repaired my phone sucesfully ! Was a bit lucky since I saved my GPT backup so after unbricking I restored my GPT, than restored TA, rebooted and flashed everything normaly. Device finaly booted :highfive:

WARNING TO ALL:
1. DO NOT PLAY WITH FDISK OR GDISK IF YOU NOT KNOW WHAT YOU ARE DOING SINCE YOUR DEVICE WILL BE HARD BRICKED !!! If you mess your gpt table or change them your device can not be flashed using pc companion or flashtool!!! If you brick gpt table than you will notice hard brick, so my segestion is: do not be stupid like me!!! I was very stupid yesterday and done very bad thing to my new phone using these tools.
2. DO NOT PLAY WITH TRYING TO ENTER YOU PHONE INTO DIAG OR ENGINERING MODE IF YOU HAVE NO RIGHT QCOM USB DRIVERS, IT WILL HARD BRICK YOUR PHONE
3. NEVER TOUCH YOU TA PARTITION SINCE YOU WILL NOT BE ABBLE TO UNBRICK YOU PHONE IN ANY WAY!!!
If trim area is damaged you can try this tool -> http://forum.xda-developers.com/showpost.php?p=56571770&postcount=53 to repair your TA partition if possible

Searched for about an hour for pins on my phone and finaly found test point pins, hope picture will save your time, nerve and your device! Use my tool to unbrick you phone, enjoy!

Download Z1C_hard_brick_repair.exe :
- https://mega.co.nz/#!8FBQkbqK!GK2gQgq1li5Ez4lzijMMMUTkuOz0fowUHB1n1NItEaY

I've followed the instruction , but the computer give me an error 43 on the device manager , can u help me to fix this ?

 

[D_B_]

I know this tread is very old but I hope you answer me, Where did you get or how did you do your amami_testpoint.SIN_FILE_SET? I think this will work for other xperia models, but I need to know where I can find that file for my Xperia model

 

[munjeni]

I know this tread is very old but I hope you answer me, Where did you get or how did you do your amami_testpoint.SIN_FILE_SET? I think this will work for other xperia models, but I need to know where I can find that file for my Xperia model

Just open that file with 7z for idea

 

[panteryx_26]

i did all this. flashed successfully and i'm still getting the red light blinking. any other suggestions?