FORUMS
Remove All Ads from XDA

[GUIDE] Z Ultra and Z1 HARD BRICK RECOVERY

509 posts
Thanks Meter: 995
 
By Doom Slayer, Senior Member on 13th February 2014, 12:15 AM
Post Reply Email Thread
23rd April 2014, 09:20 PM |#171  
Senior Member
Thanks Meter: 1,019
 
More
@bejibx:

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.

but if not, then using [ATTACH]3488018[/ATTACH( do NOT use s1tool from first post in topic ) flash your security units backup.

phone will connect in normal flash mode then, without testpoint.
you need to flash rootable firmware then and restore all your trim area backup using backup/restore script/tool/whatever.

i'm also implemented in this version of s1tool support of sony apq8064-based phones in emergency mode.
so people with xperia z,zl,zr and sgp3xx tablets could fix their phone, assuming that trim area partition not damaged and phone in qhusb_dload mode ( via testpoint or if boot partition damaged )

edit:
apq8064 recovery fixed ( not worked at all )
msm8960pro recovery added ( boot recovery included in archive )
msm8960 recovery added ( boot recovery included in archive )
Attached Files
File Type: zip s1tool.zip - [Click for QR Code] (4.27 MB, 3982 views)
The Following 11 Users Say Thank You to the_laser For This Useful Post: [ View ] Gift the_laser Ad-Free
 
 
24th April 2014, 02:29 AM |#172  
herogjan's Avatar
Senior Member
Flag Uitgeest
Thanks Meter: 66
 
More
Quote:
Originally Posted by the_laser


main loader not responding, this is abnormal for your situation.
you doing testpoint job with or without battery ? try to connect battery, when s1tool ask you to remove testpoint and try to change usb port.

@the_laser

I tried all the options, same result. When switching usb ports i get a fault.

Code:
24-4-2014 01:27:24 PROCESSING ...
24-4-2014 01:27:24 llbug: write error: "Toegang geweigerd"
24-4-2014 01:27:24 llbug: blk write fail.fatal
24-4-2014 01:27:24 Elapsed:152 secs.
"Toegang geweigerd" = "acces denied"
24th April 2014, 08:13 AM |#173  
Junior Member
Thanks Meter: 0
 
More
xperia C6902 dead after flash
Quote:
Originally Posted by vovanx500

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

------------------------------------------------------------------------------------------------------------
If I helped, you may want to buy me a beer or two.

I am facing This problem
PROCEDURE STOPPED BY USER
supported phone was not detected
Elapsed:183 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 : 1--------
HARDWARE ID 04000100E1207B00 NOT SUPPORTED
HARDWARE ID : 04000100E1207B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC 31852330BDDB177
CHIPSET NOT SUPPORTED
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 Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"

PROCESSING ...
SERIAL NUMBER : E-----------
HARDWARE ID 04000100E1207B00 NOT SUPPORTED
HARDWARE ID : 04000100E1207B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC 31852330BDDB177
Emergency loader uploaded ...

I am using windows XP service pack 3

Please help

Thanks
24th April 2014, 08:52 AM |#174  
Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by the_laser

@bejibx:

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.

but if not, then using Attachment 2704612 ( do NOT use s1tool from first post in topic ) flash your security units backup.

phone will connect in normal flash mode then, without testpoint.
you need to flash rootable firmware then and restore all your trim area backup using backup/restore script/tool/whatever.

i'm also implemented in this version of s1tool support of sony apq8064-based phones in emergency mode.
so people with xperia z,zl,zr and sgp3xx tablets could fix their phone, assuming that trim area partition not damaged and phone in qhusb_dload mode ( via testpoint or if boot partition damaged )

I did everything according to your instructions. Here is s1tool log:
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 : 388D4803
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
 
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 03488D38
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
 
WRITING PACKAGES ...
Processing package
D:\Downloads\xperia z1\s1tool_080414\35965205505263.SIN_FILE_SET
 
package not contains ACPU files.
Processing update files
PROCESSING: 35965205505263.gdfs
Writing TA var 0002/07D3/07C1
Writing TA var 0002/07DA/0287
Writing TA var 0002/0851/03CA
FINISHED
Elapsed:47 secs.
Now I'm trying to flash "C6903 14.1.G.1.518 Central Europe 1276-4314_R2A" firmware from this post but every time I'm getting this error:
Code:
24/039/2014 11:39:04 - INFO  - Selected Bundle for Sony Xperia Z1 (C6903). FW release : 14.3.A.0.757. Customization : Unbranded
24/039/2014 11:39:04 - INFO  - Preparing files for flashing
24/039/2014 11:39:05 - INFO  - Please connect your device into flashmode.
24/039/2014 11:39:56 - INFO  - Device connected in flash mode
24/039/2014 11:39:57 - INFO  - Opening device for R/W
24/039/2014 11:39:57 - INFO  - Reading device information
24/039/2014 11:39:57 - INFO  - Phone ready for flashmode operations.
24/039/2014 11:39:57 - INFO  - Start Flashing
24/039/2014 11:39:57 - INFO  - Processing loader.sin
24/039/2014 11:39:57 - INFO  -     Checking header
24/039/2014 11:39:57 - INFO  -     Flashing data
24/039/2014 11:39:57 - INFO  - Processing of loader.sin finished.
24/039/2014 11:39:57 - INFO  - Loader : S1_Root_6732 - Version : MSM8974_23 / Boot version : S1_Boot_MSM8974_Rhine1.2_LA1.04_12 / Bootloader status : ROOTABLE
24/039/2014 11:39:57 - INFO  - Ending flash session
24/039/2014 11:39:57 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0026";ERR_DYNAMIC="Write TA failed.";
I think I misunderstand you about "rootable firmware". Can you please tell me what kind of .tft I need to flash?
24th April 2014, 11:13 AM |#175  
Senior Member
Thanks Meter: 1,019
 
More
@bejibx:
flash this firmware using s1tool from last post, then root it and restore your trim area backup.
you can flash phone using normal S1 mode , not S1 recovery.

@herogjan:
install usbflash drivers from s1tool package,do not use usb 3.0 port, use short usb cable.
can't help you more, sorry.
The Following 2 Users Say Thank You to the_laser For This Useful Post: [ View ] Gift the_laser Ad-Free
24th April 2014, 02:56 PM |#176  
Junior Member
Thanks Meter: 4
 
More
Phone Restoring xperia z1 from brick state
I want to post full story about how I unbricked my xperia z1, just in case it can help someone.
So 2 days ago my xperia z1 c6903 was hard bricked (flash/fastboot mode not worked) after flashing firmware with flashtool.
  1. I tried instruction from this guide. Did not worked, I got this error in s1tools:
    Code:
    MINOR ERROR [ 0x80080021_, err: 0017 ]
    error while uploading final HDR block
  2. I asked here for help. User the_laser asked me for my trim area backup. I had one, so I post it to him via google docs.
  3. He sent me ".SIN_FILE_SET" file and post new version of s1tool in this post. I downloaded both.
  4. I exactly followed instruction from this guide with s1tool and ".SIN_FILE_SET" the_laser sent to me. Everything went fine. Here you can watch my s1tool log.
  5. I tried to flash some firmwares from here with flashtool. Did not worked, every time I got error:
    Code:
    24/039/2014 11:39:57 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0026";ERR_DYNAMIC="Write TA failed.";
  6. Then I downloaded firmware from this post, unzip it, and flash it (using "s1 flash mode" and then select all 3 files) with s1tool the_laser sent to me. Here is log from s1tool:
    Code:
    24.04.2014 15:34:19 Welcome to S1 tool.
    24.04.2014 15:34:19 That is small and crippled subset of SETOOL2 service tool.
    24.04.2014 15:34:29  
    24.04.2014 15:34:29 SELECT FIRMWARE PACKAGES
    24.04.2014 15:34:29 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
    24.04.2014 15:34:52 CHECKING PACKAGES ...
    24.04.2014 15:34:52  
    24.04.2014 15:34:52 TO CONNECT NEXT PHONES
    24.04.2014 15:34:52 X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
    24.04.2014 15:34:52 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
    24.04.2014 15:34:52 PRESS AND HOLD "BACK" BUTTON...
    24.04.2014 15:34:52  
    24.04.2014 15:34:52 ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
    24.04.2014 15:34:52 and Sony Xperia phone
    24.04.2014 15:34:52 PRESS AND HOLD "Volume Down" BUTTON...
    24.04.2014 15:34:52  
    24.04.2014 15:34:52 PLEASE ATTACH TURNED OFF PHONE NOW
    24.04.2014 15:34:52 Waiting for phone ...
    24.04.2014 15:34:59 PROCEDURE STOPPED BY USER
    24.04.2014 15:34:59 Elapsed:29 secs.
    24.04.2014 15:35:01  
    24.04.2014 15:35:01 SELECT FIRMWARE PACKAGES
    24.04.2014 15:35:01 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
    24.04.2014 15:35:04 CHECKING PACKAGES ...
    24.04.2014 15:35:04  
    24.04.2014 15:35:04 TO CONNECT NEXT PHONES
    24.04.2014 15:35:04 X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
    24.04.2014 15:35:04 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
    24.04.2014 15:35:04 PRESS AND HOLD "BACK" BUTTON...
    24.04.2014 15:35:04  
    24.04.2014 15:35:04 ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
    24.04.2014 15:35:04 and Sony Xperia phone
    24.04.2014 15:35:04 PRESS AND HOLD "Volume Down" BUTTON...
    24.04.2014 15:35:04  
    24.04.2014 15:35:04 PLEASE ATTACH TURNED OFF PHONE NOW
    24.04.2014 15:35:04 Waiting for phone ...
    24.04.2014 15:35:28  
    24.04.2014 15:35:28 RUNNING S1_BOOT VER "S1_Boot_MSM8974_Rhine1.2_LA1.04_12"
    24.04.2014 15:35:28 LOADER AID: 0004
    24.04.2014 15:35:29 DEVICE ID: 03488D38
    24.04.2014 15:35:29 FLASH ID: "0003/00000011"
    24.04.2014 15:35:29 LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
    24.04.2014 15:35:29  
    24.04.2014 15:35:29 WRITING PACKAGES ...
    24.04.2014 15:35:29 Processing package
    24.04.2014 15:35:29 D:\Downloads\xperia z1\s1tool_080414\14.1.G.1.534\14_1_G_1_534.APP_SW_Honami_EURO_1274_8313_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
    24.04.2014 15:35:29  
    24.04.2014 15:35:29 WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.0_56-A
    24.04.2014 15:35:29 PARSING: "DEVELOPMENT"
    24.04.2014 15:35:29 value OTP_LOCK_STATUS_1 :  UNLOCKED, not match LOCKED
    24.04.2014 15:35:29 PARSING: "TEST_OEM0_007B00E1"
    24.04.2014 15:35:29 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
    24.04.2014 15:35:29 value OTP_DATA_1 :  00000100, not match 01000400
    24.04.2014 15:35:29 value IDCODE_1 : 007B00E1, match 007B00E1
    24.04.2014 15:35:29 PARSING: "PRECOMMERCIAL_007B00E1"
    24.04.2014 15:35:29 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
    24.04.2014 15:35:29 value OTP_DATA_1 : 01000400, match 01000400
    24.04.2014 15:35:29 value IDCODE_1 : 007B00E1, match 007B00E1
    24.04.2014 15:35:29 PROCESSING : dbi_S1_Boot_MSM8974_LA1_0_56-A_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
    24.04.2014 15:35:29 PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_0_56-A_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
    24.04.2014 15:35:29 PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_0_56-A_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
    24.04.2014 15:35:29 PROCESSING : sbl1_S1_Boot_MSM8974_LA1_0_56-A_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
    24.04.2014 15:35:30 PROCESSING : tz_S1_Boot_MSM8974_LA1_0_56-A_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
    24.04.2014 15:35:30 PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
    24.04.2014 15:35:30 Writing TA var 0002/084F/0049
    24.04.2014 15:35:30 Writing TA var 0002/08FD/0001
    24.04.2014 15:35:30 BOOT UPDATED
    24.04.2014 15:35:30 Processing ACPU files
    24.04.2014 15:35:30 PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:31 PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:31 PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:32 PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:33 SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
    24.04.2014 15:35:33 PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:34 no update files in package
    24.04.2014 15:35:34 Processing package
    24.04.2014 15:35:34 D:\Downloads\xperia z1\s1tool_080414\14.1.G.1.534\14_1_G_1_534.ELABEL_Honami_elabel_c6903_row.201401221511_1.SIN_FILE_SET
    24.04.2014 15:35:34  
    24.04.2014 15:35:34 Processing ACPU files
    24.04.2014 15:35:34 PROCESSING: elabel-C6903-row_201401221511.1_14.1.G.1.534_S1-CUST-LIVE-6732-PID1-0004-MMC.sin
    24.04.2014 15:35:35 no update files in package
    24.04.2014 15:35:35 Processing package
    24.04.2014 15:35:35 D:\Downloads\xperia z1\s1tool_080414\14.1.G.1.534\14_1_G_1_534.FSP_Honami_EURO_LTE_1276_1193_S1_SW_LIVE_6732_PID1_0005_MMC.R7A.SIN_FILE_SET
    24.04.2014 15:35:35  
    24.04.2014 15:35:35 Processing ACPU files
    24.04.2014 15:35:36 PROCESSING: userdata_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:35:50 PROCESSING: system_S1-SW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:37:54 PROCESSING: amss_fs_1_S1-MODEMSW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:37:54 PROCESSING: amss_fs_2_S1-MODEMSW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:37:54 PROCESSING: amss_fsg_S1-MODEMSW-LIVE-6732-PID1-0005-MMC.sin
    24.04.2014 15:37:54 Processing update files
    24.04.2014 15:37:54 PROCESSING: cust-reset.ta
    24.04.2014 15:37:54 Writing TA var 0002/08A4/000E
    24.04.2014 15:37:54 SKIP: simlock.ta
    24.04.2014 15:37:54 FINISHED
    24.04.2014 15:37:54 Elapsed:172 secs.
  7. Phone succesfully loaded!

Great thanks to user the_laser for his help!
The Following 4 Users Say Thank You to bejibx For This Useful Post: [ View ] Gift bejibx Ad-Free
24th April 2014, 04:10 PM |#177  
herogjan's Avatar
Senior Member
Flag Uitgeest
Thanks Meter: 66
 
More
Quote:
Originally Posted by the_laser

@bejibx:
flash this firmware using s1tool from last post, then root it and restore your trim area backup.
you can flash phone using normal S1 mode , not S1 recovery.

@herogjan:
install usbflash drivers from s1tool package,do not use usb 3.0 port, use short usb cable.
can't help you more, sorry.

@the_laser Thanks, i know what to do. Also this post http://forum.xda-developers.com/show...1&postcount=13 by @Geoffxx gave me some insight in my battery. I assumed that battery was loading, but after i've let it a couple hours in the usb port after doing the failed settool procedure, the led also blinked when i removed the phone. This was new, so i'm no thinking that the battery is empty or almost empty. I'm now doing the loading procedure, let's see if that can make a difference.
24th April 2014, 07:17 PM |#178  
Senior Member
Thanks Meter: 1,019
 
More
@bejibx:
do not forget to restore your trim area backup.
28th April 2014, 01:25 AM |#179  
metal_god69's Avatar
Senior Member
Flag Regina
Thanks Meter: 12
 
More
Quote:
Originally Posted by Mighty_X

Maybe stupid question : Do you think with this testpoint mode there is a way of unlocking Bootlader although it is not permitted by the provider?

Did you ever try unlocking your boot loader with this method?
4th May 2014, 04:07 AM |#180  
Junior Member
Thanks Meter: 0
 
More
Xperia zl
It Works with an xperia zl?
10th May 2014, 07:53 PM |#181  
Junior Member
Thanks Meter: 1
 
More
ask for error while flashing with s1tool
hello all..

i have my Xperia z1 bricked and thanks god i made a search and find this threat

i've already do all necessary things to make my z1 wake up again but i got an error while flashing with s1 tools
Quote:

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 : B8D68F01
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC 31852330BDDB177
Emergency loader uploaded ...

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

WRITING PACKAGES ...
Processing package
K:\New Folder (2)\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_PLAT FORM-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:29 secs.

i realize maybe that errors appear because i've no Trim Area (TA) Backup.

is there any solution for this case??
thanks in advance and sorry for my poor english
The Following User Says Thank You to anchadict For This Useful Post: [ View ] Gift anchadict Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes