G3311 can't boot after attempting to flash new firmware with flashtool - Sony Xperia L1 Questions & Answers

Hello There,
I was attempting to put new firmware on my G3311 using flashtool (first time i'm doing it) and it got some error on the log and now the phone can't be power up. Pushing the power button for a long time but only got black screen. tough the phone can be put into flashmode.
Here is the eror on flashtool:
16/020/2020 02:20:02 - INFO - (SearchJob.java:48) - Using Gordon gate drivers version 3.2.0.0
16/020/2020 02:20:02 - INFO - (USBFlashWin32.java:15) - Opening device for R/W
16/020/2020 02:20:03 - INFO - (USBFlashWin32.java:17) - Device ready for R/W.
16/020/2020 02:20:03 - INFO - (S1Flasher.java:970) - Reading device information
16/020/2020 02:20:03 - DEBUG - (S1Flasher.java:977) - PROT_VER="04";VER="S1_Boot_MT6737_N0.MP1_2";ID="1306-5028";FRP_PARTITION="frp";TYPE="S1_LOADER";ACTIVE_COMP_AID="0004";MAX_PKT_SZ="00080000";IGNORE_CRC="HDR,DATA";DEF_SEC="OFF";HWCONF_AID="FFFF";LOADER_AID="0001";BOOT_AID="0001";NO_SUB_SYSTEMS="0001";OTP_DATA_1="0000";OTP_LOCK_STATUS_1="UNLOCKED";UNIQUE_DEV_ID_1="2C6A06D8E849C06F";IDCODE_1="2103000000000000";SUID_1="0900000021030000B9514F7EA693139E";S1_ROOT="S1_Root_a4cd,S1_Root_Test_b316";MSN="WUJ01KXNXK";HW_CONFIG_VER="0006";HW_CONFIG_INFO="HWC_Chambal_Dev_007";SEC_STATE="HWC_Chambal_Dev_007";IMEI="35419407057839";PROD_ID="0000";GLOB_SEC="0000";PHONE_ID="0000:35419407057839";HW_CONFIG="S1_Boot:0001:0017,S1_Loader:0001:000F,S1_SW:0001:0017,S1_Cust:0001:0017,S1_ELabel:0001:0017,S1_SL:0001:0047,S1_FOTA:0001:0027,S1_RLock:0001:0227";AUTH_LEVEL="NONE";AUTH_MET="0001";MEMDEVS="03:00:0015:0100:000D:01D1F000:00000400:00000200";ROOTING_STATUS="ROOTABLE";PLF_ROOT_1="0000000000000000000000000000000000000000000000000000000000000000";RAM_INFO="0105001F:0105001F";S1SBL_VER="MT6737_8";
16/020/2020 02:20:03 - DEBUG - (S1Flasher.java:940) - First command reply (hook) :
16/020/2020 02:20:03 - INFO - (S1Flasher.java:986) - Phone ready for flashmode operations.
16/020/2020 02:20:03 - INFO - (S1Flasher.java:410) - Opening TA partition 2
16/020/2020 02:20:05 - INFO - (S1Flasher.java:561) - Current device : G3311 - WUJ01KXNXK - 1307-3090_R1A - 1306-9490_43.0.A.0.53 - GENERIC_43.0.A.0.53
16/020/2020 02:20:05 - INFO - (S1Flasher.java:419) - Closing TA partition
16/020/2020 02:20:05 - INFO - (S1Flasher.java:696) - Start Flashing
16/020/2020 02:20:05 - INFO - (S1Flasher.java:337) - No loader in the bundle. Searching for one
16/020/2020 02:20:05 - INFO - (S1Flasher.java:342) - No matching loader found
16/020/2020 02:20:05 - WARN - (S1Flasher.java:355) - No loader found or set manually. Skipping loader
16/020/2020 02:20:05 - DEBUG - (S1Flasher.java:936) - After loader command reply (hook) :
16/020/2020 02:20:05 - INFO - (S1Flasher.java:937) - Loader : S1_Root_a4cd - Version : S1_Boot_MT6737_N0.MP1_2 / Boot version : S1_Boot_MT6737_N0.MP1_2 / Bootloader status : ROOTABLE
16/020/2020 02:20:05 - INFO - (S1Flasher.java:363) - Max packet size set to 512K
16/020/2020 02:20:05 - INFO - (S1Flasher.java:383) - USB buffer size set to 512K
16/020/2020 02:20:09 - INFO - (S1Flasher.java:428) - Parsing boot delivery
16/020/2020 02:20:09 - INFO - (S1Flasher.java:610) - Found a template session. Using it : C:\Users\Unknown\.flashTool\firmwares\prepared\43.0.fsc
16/020/2020 02:20:09 - INFO - (S1Flasher.java:108) - Set loader configuration : [00 01 00 00 00 0C]
16/020/2020 02:20:09 - INFO - (S1Flasher.java:410) - Opening TA partition 2
16/020/2020 02:20:10 - INFO - (S1Flasher.java:160) - Writing TA unit 00002774. Value : 01
16/020/2020 02:20:10 - INFO - (S1Flasher.java:419) - Closing TA partition
16/020/2020 02:20:10 - INFO - (S1Flasher.java:286) - Processing partitions.sin
16/020/2020 02:20:10 - INFO - (S1Flasher.java:274) - Checking header
16/020/2020 02:20:10 - INFO - (S1Flasher.java:288) - Flashing data
16/020/2020 02:20:10 - DEBUG - (S1Flasher.java:289) - Number of parts to send : 1 / Part size : 524288
16/020/2020 02:20:10 - DEBUG - (S1Flasher.java:293) - Sending part 1 of 1
16/020/2020 02:20:10 - INFO - (S1Flasher.java:108) - Set loader configuration : [00 01 00 00 00 0D]
16/020/2020 02:20:10 - INFO - (S1Flasher.java:108) - Set loader configuration : [00 01 00 00 00 0F]
16/020/2020 02:20:10 - INFO - (S1Flasher.java:286) - Processing preloader_s1sbl_S1-BOOT-LIVE-A4CD-0004-MMC.sin
16/020/2020 02:20:10 - INFO - (S1Flasher.java:274) - Checking header
16/020/2020 02:20:11 - INFO - (S1Flasher.java:288) - Flashing data
16/020/2020 02:20:11 - DEBUG - (S1Flasher.java:289) - Number of parts to send : 1 / Part size : 524288
16/020/2020 02:20:11 - DEBUG - (S1Flasher.java:293) - Sending part 1 of 1
16/020/2020 02:20:11 - INFO - (S1Flasher.java:108) - Set loader configuration : [00 01 00 00 00 0D]
16/020/2020 02:20:11 - INFO - (S1Flasher.java:286) - Processing secro_S1-BOOT-LIVE-A4CD-0004-MMC.sin
16/020/2020 02:20:11 - INFO - (S1Flasher.java:274) - Checking header
16/020/2020 02:20:11 - INFO - (S1Flasher.java:288) - Flashing data
16/020/2020 02:20:11 - DEBUG - (S1Flasher.java:289) - Number of parts to send : 1 / Part size : 524288
16/020/2020 02:20:11 - DEBUG - (S1Flasher.java:293) - Sending part 1 of 1
16/020/2020 02:20:12 - ERROR - (S1Flasher.java:304) - Processing of secro_S1-BOOT-LIVE-A4CD-0004-MMC.sin finished with errors.
16/020/2020 02:20:12 - INFO - (S1Flasher.java:716) - Flashing finished.
16/020/2020 02:20:12 - INFO - (S1Flasher.java:717) - Please unplug and start your phone
Thanks in advance for you help

Noob need of help
@bigrammy Hello i've seen some good post of yours and i just wanted to ask if you can please put your "god hand" on my issue. Thanks in advance for your precious time

evanjrrys said:
@bigrammy Hello i've seen some good post of yours and i just wanted to ask if you can please put your "god hand" on my issue. Thanks in advance for your precious time
Click to expand...
Click to collapse
Thanks for your confidence but I am no god in these matters :laugh:
I have not used FlashTool for ages now as it's broke on my Linux distro and is missing some of the .png's.
I mostly use the command line xflasher tool. :good:
From the log it seems like you only flashed the boot area (Preloader, LK, etc) you should really choose to flash ALSO the boot/kernel, fotakernel, system, userdata and cache if it exists from the same package.
Make sure you select them for flashing, you have to choose them manually using the "exclude" option box. (Exclude SECRO if its giving you problems)
For userdata just ticking wipe userdata will add the userdata for you.
I found this old screenshot example so everything in "Under "Content"" would get flashed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things May look or of changed slightly since this version screenshot but the principal will probably be the same.
If yours looks drastically different point me to a image that looks like yours.
.

bigrammy said:
Thanks for your confidence but I am no god in these matters :laugh:
I have not used FlashTool for ages now as it's broke on my Linux distro and is missing some of the .png's.
I mostly use the command line xflasher tool. :good:
From the log it seems like you only flashed the boot area (Preloader, LK, etc) you should really choose to flash ALSO the boot/kernel, fotakernel, system, userdata and cache if it exists from the same package.
Make sure you select them for flashing, you have to choose them manually using the "exclude" option box. (Exclude SECRO if its giving you problems)
For userdata just ticking wipe userdata will add the userdata for you.
I found this old screenshot example so everything in "Under "Content"" would get flashed
Things May look or of changed slightly since this version screenshot but the principal will probably be the same.
If yours looks drastically different point me to a image that looks like yours.
.
Click to expand...
Click to collapse
@bigrammy thank you for your prompt response since i'm on windows i'm going to find the most recent version of xflasher and i'll let you know

evanjrrys said:
@bigrammy thank you for your prompt response since i'm on windows i'm going to find the most recent version of xflasher and i'll let you know
Click to expand...
Click to collapse
You could just try another firmware package using FlashTool. Sometimes the Packages can be corrupted during download or extraction.

Related

[FTF] HK_Xperia Z2 Tablet SGP521 - LTE [23.4.A.0.546]

5.1.1 LOLLIPOP
I was looking all over for this one and since No one has uploaded one I thought of uploading one.
Click here
17.1.2.A.0.314 Uploaded
Lollipop FTF is added. 23.1.A.0.690 VMo HK-SA-AE-KW_1281-8152
17.1.1.A.2.402/17.1.2.A.0.314/23.1.A.0.690/23.4.A.0.546
Thanks bro, wait this a long time,
Sent from my SGP521 using XDA Premium 4 mobile app
Glad to help
Sorry man
I have the one problem, why i put this ftf to the flashtool folder, but can't found this 402 ftf for choose? There is empty......what's matter???
sent form my xperia z2 or z2 tablet or z or z tablet??? im dont think so ~~
eric1214 said:
Sorry man
I have the one problem, why i put this ftf to the flashtool folder, but can't found this 402 ftf for choose? There is empty......what's matter???
sent form my xperia z2 or z2 tablet or z or z tablet??? im dont think so ~~
Click to expand...
Click to collapse
Did you put it to flashtool/firmware folder?
chesterr said:
Did you put it to flashtool/firmware folder?
Click to expand...
Click to collapse
Sure , im not first time to do it,
eric1214 said:
Sure , im not first time to do it,
Click to expand...
Click to collapse
Here I tried it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
16/029/2014 14:29:00 - INFO - Selected Bundle for Sony Xperia Z2 Tablet (SGP521). FW release : 1278-8152. Customization : Unbranded
16/029/2014 14:29:00 - INFO - Preparing files for flashing
16/029/2014 14:29:16 - INFO - Please connect your device into flashmode.
16/032/2014 14:32:25 - INFO - Device connected in flash mode
16/032/2014 14:32:25 - INFO - Opening device for R/W
16/032/2014 14:32:25 - INFO - Reading device information
16/032/2014 14:32:25 - INFO - Phone ready for flashmode operations.
16/032/2014 14:32:25 - INFO - Current device : SGP521 - CB5126ZQ0H - 1281-8152_R6A - 1278-4804_17.1.1.A.0.402 - GLOBAL-LTE_17.1.1.A.0.402
16/032/2014 14:32:25 - INFO - Start Flashing
16/032/2014 14:32:25 - INFO - Processing loader.sin
16/032/2014 14:32:25 - INFO - Checking header
16/032/2014 14:32:25 - INFO - Flashing data
16/032/2014 14:32:25 - INFO - Processing of loader.sin finished.
16/032/2014 14:32:25 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_12 / Boot version : S1_Boot_MSM8974AB_LA2.0.1_37-B / Bootloader status : ROOTABLE
16/032/2014 14:32:26 - INFO - Processing partition-image.sin
16/032/2014 14:32:26 - INFO - Checking header
16/032/2014 14:32:26 - INFO - Flashing data
16/032/2014 14:32:26 - INFO - Processing of partition-image.sin finished.
16/032/2014 14:32:26 - INFO - Parsing boot delivery
16/032/2014 14:32:26 - INFO - Phone boot version : S1_Boot_MSM8974AB_LA2.0.1_37-B. Boot delivery version : S1_Boot_MSM8974AB_LA2.0.1_37-B
16/032/2014 14:32:26 - INFO - Boot delivery up to date. Nothing to do
16/032/2014 14:32:26 - INFO - Processing kernel.sin
16/032/2014 14:32:26 - INFO - Checking header
16/032/2014 14:32:26 - INFO - Flashing data
16/032/2014 14:32:27 - INFO - Processing of kernel.sin finished.
16/032/2014 14:32:27 - INFO - Processing fotakernel.sin
16/032/2014 14:32:27 - INFO - Checking header
16/032/2014 14:32:27 - INFO - Flashing data
16/032/2014 14:32:29 - INFO - Processing of fotakernel.sin finished.
16/032/2014 14:32:29 - INFO - Processing amss_fs_2.sin
16/032/2014 14:32:29 - INFO - Checking header
16/032/2014 14:32:29 - INFO - Flashing data
16/032/2014 14:32:29 - INFO - Processing of amss_fs_2.sin finished.
16/032/2014 14:32:29 - INFO - Processing amss_fs_1.sin
16/032/2014 14:32:29 - INFO - Checking header
16/032/2014 14:32:29 - INFO - Flashing data
16/032/2014 14:32:29 - INFO - Processing of amss_fs_1.sin finished.
16/032/2014 14:32:29 - INFO - Processing amss_fsg.sin
16/032/2014 14:32:29 - INFO - Checking header
16/032/2014 14:32:29 - INFO - Flashing data
16/032/2014 14:32:29 - INFO - Processing of amss_fsg.sin finished.
16/032/2014 14:32:29 - INFO - Processing b2b.sin
16/032/2014 14:32:29 - INFO - Checking header
16/032/2014 14:32:29 - INFO - Flashing data
16/032/2014 14:32:31 - INFO - Processing of b2b.sin finished.
16/032/2014 14:32:31 - INFO - Processing apps_log.sin
16/032/2014 14:32:31 - INFO - Checking header
16/032/2014 14:32:31 - INFO - Flashing data
16/032/2014 14:32:31 - INFO - Processing of apps_log.sin finished.
16/032/2014 14:32:31 - INFO - Processing cache.sin
16/032/2014 14:32:31 - INFO - Checking header
16/032/2014 14:32:31 - INFO - Flashing data
16/032/2014 14:32:32 - INFO - Processing of cache.sin finished.
16/032/2014 14:32:32 - INFO - Processing system.sin
16/032/2014 14:32:32 - INFO - Checking header
16/032/2014 14:32:32 - INFO - Flashing data
16/037/2014 14:37:16 - INFO - Processing of system.sin finished.
16/037/2014 14:37:16 - INFO - Processing userdata.sin
16/037/2014 14:37:16 - INFO - Checking header
16/037/2014 14:37:17 - INFO - Flashing data
16/037/2014 14:37:57 - INFO - Processing of userdata.sin finished.
16/037/2014 14:37:57 - INFO - Processing elabel-SGP521-row_201404081709.1_17.1.1.A.0.402.sin
16/037/2014 14:37:57 - INFO - Checking header
16/037/2014 14:37:57 - INFO - Flashing data
16/038/2014 14:38:00 - INFO - Processing of elabel-SGP521-row_201404081709.1_17.1.1.A.0.402.sin finished.
16/038/2014 14:38:00 - INFO - Flashing fota-reset.ta
16/038/2014 14:38:00 - INFO - Writing TA unit : [00, 00, 09, 64, 00, 00, 00, 01, 00]
16/038/2014 14:38:00 - INFO - Flashing cust-reset.ta
16/038/2014 14:38:00 - INFO - Custumization reset is now based on UI choice
16/038/2014 14:38:00 - INFO - Ending flash session
16/038/2014 14:38:00 - INFO - Flashing finished.
16/038/2014 14:38:00 - INFO - Please unplug and start your phone
16/038/2014 14:38:00 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
16/038/2014 14:38:00 - INFO - Device connected in flash mode
Is this fresh off the press or rooted ROM?
fribriz said:
Is this fresh off the press or rooted ROM?
Click to expand...
Click to collapse
Downloaded this file twice but it did not open with 7zip which mean it is probably corrupted.
Then never bothered tried to flash it
can u upload again , cuz this file corrupted
need hk plz
I will re-upload everything today.
Edit: It's been re-uploaded. Please give me a feed back.
chesterr said:
I will re-upload everything today.
Edit: It's been re-uploaded. Please give me a feed back.
Click to expand...
Click to collapse
ty for uploading , working fine now :good:
SPooT24 said:
ty for uploading , working fine now :good:
Click to expand...
Click to collapse
Glad to hear that. I was little worried about that. I think something must've gone wrong when I uploaded it in the first time
Lollipop FTF is added
Lollipop FTF is added. 23.1.A.0.690 VMo HK-SA-AE-KW_1281-8152
LOLLIPOP 5.1.1 added

My Xperia E4 Dual E2115 is having problems bootloop

My device is original type :
Model : E2115
Application Software : 1290-6611 24.0.B.5.14
CDF : 1293-2718 R5A
File System : WORLD-i 24.0.B.5.14
SIM Lock : Open
Activated : Yes
Boot : 1286-4499 S1_boot_MT6582_TC9SP_11
DRM : CKB
Security State : HWC_Amur_Com_004
Currently is having problems bootloop , after I flash boot to CWM .
Cause it failed then I flash my device with the firmware download from "XperiFirm Downloader" as shown below .
Screenshoot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when in flash result were "ERROR - Error dumping TA. Aborted".
Code:
07/032/2016 19:32:55 - INFO - Selected Bundle for Sony Xperia E4 (E2115). FW release : 24.B.5.14_R5A. Customization : Sony Xperia
07/032/2016 19:32:55 - INFO - Preparing files for flashing
07/033/2016 19:33:24 - INFO - Please connect your device into flashmode.
07/033/2016 19:33:32 - INFO - Device connected in flash mode
07/033/2016 19:33:33 - INFO - Opening device for R/W
07/033/2016 19:33:33 - INFO - Reading device information
07/033/2016 19:33:33 - INFO - Phone ready for flashmode operations.
07/033/2016 19:33:33 - INFO - Opening TA partition 2
07/033/2016 19:33:33 - INFO - Current device : E2115 - WUJ01H77QV - 1293-2718_R5A - 1290-6611_24.0.B.5.14 - WORLD-i_24.0.B.5.14
07/033/2016 19:33:33 - INFO - Closing TA partition
07/033/2016 19:33:33 - INFO - Start Flashing
07/033/2016 19:33:33 - INFO - Processing loader.sin
07/033/2016 19:33:33 - INFO - Checking header
07/033/2016 19:33:33 - INFO - Flashing data
07/033/2016 19:33:33 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : S1_Boot_MT6582_TC9SP_11 / Bootloader status : ROOTED
07/033/2016 19:33:33 - INFO - Max packet size forced to 512K
07/033/2016 19:33:33 - INFO - Making a TA backup
07/033/2016 19:33:33 - INFO - Opening TA partition 1
07/033/2016 19:33:33 - INFO - Start Dumping TA partition 1
07/033/2016 19:33:33 - INFO - Finished Dumping TA partition 1
07/033/2016 19:33:33 - INFO - Closing TA partition
[COLOR="Red"]07/033/2016 19:33:33 - ERROR -
07/033/2016 19:33:33 - ERROR - Error dumping TA. Aborted[/COLOR]
07/033/2016 19:33:33 - INFO - Opening TA partition 2
07/033/2016 19:33:33 - INFO - Start Dumping TA partition 2
07/033/2016 19:33:33 - INFO - Finished Dumping TA partition 2
07/033/2016 19:33:34 - INFO - TA partition 2 saved to C:\Users\Astra Efandri\.flashTool\registeredDevices\WUJ01H77QV\s1ta\2016-03-07_07-33-33\2.ta
07/033/2016 19:33:34 - INFO - Closing TA partition
07/033/2016 19:33:45 - INFO - Found a template session. Using it : C:\Users\Astra Efandri\.flashTool\devices\E21XX\default.fsc
07/033/2016 19:33:45 - INFO - Opening TA partition 2
07/033/2016 19:33:45 - INFO - Writing TA unit 00002774. Value : [01]
07/033/2016 19:33:45 - INFO - Closing TA partition
07/033/2016 19:33:45 - INFO - Processing partition.sin
07/033/2016 19:33:45 - INFO - Checking header
07/033/2016 19:33:45 - INFO - Flashing data
07/033/2016 19:33:45 - INFO - Set loader configuration : [00, 01, 00, 00, 00, 01]
07/033/2016 19:33:45 - INFO - Set loader configuration : [00, 01, 00, 00, 00, 03]
07/033/2016 19:33:45 - INFO - Flashing finished.
07/033/2016 19:33:45 - INFO - Please unplug and start your phone
07/033/2016 19:33:45 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
After the flash device is still bootloop and then I try using Emma Software , the result is also failed .
Emma's info like this "No available services matched the connected device."
Screenshoot :
Please help, so my device back to normal .
I've tried googling of any reference is not solved my problem .
thanks for your help . Sorry if my english is not good .
Thx before....
Just install Sony pc companion, then repair. Don't forget to relock bootloader first on flashtool
astraefandri said:
My device is original type :
Model : E2115
Application Software : 1290-6611 24.0.B.5.14
CDF : 1293-2718 R5A
File System : WORLD-i 24.0.B.5.14
SIM Lock : Open
Activated : Yes
Boot : 1286-4499 S1_boot_MT6582_TC9SP_11
DRM : CKB
Security State : HWC_Amur_Com_004
Currently is having problems bootloop , after I flash boot to CWM .
Cause it failed then I flash my device with the firmware download from "XperiFirm Downloader" as shown below .
Screenshoot :
when in flash result were "ERROR - Error dumping TA. Aborted".
Code:
07/032/2016 19:32:55 - INFO - Selected Bundle for Sony Xperia E4 (E2115). FW release : 24.B.5.14_R5A. Customization : Sony Xperia
07/032/2016 19:32:55 - INFO - Preparing files for flashing
07/033/2016 19:33:24 - INFO - Please connect your device into flashmode.
07/033/2016 19:33:32 - INFO - Device connected in flash mode
07/033/2016 19:33:33 - INFO - Opening device for R/W
07/033/2016 19:33:33 - INFO - Reading device information
07/033/2016 19:33:33 - INFO - Phone ready for flashmode operations.
07/033/2016 19:33:33 - INFO - Opening TA partition 2
07/033/2016 19:33:33 - INFO - Current device : E2115 - WUJ01H77QV - 1293-2718_R5A - 1290-6611_24.0.B.5.14 - WORLD-i_24.0.B.5.14
07/033/2016 19:33:33 - INFO - Closing TA partition
07/033/2016 19:33:33 - INFO - Start Flashing
07/033/2016 19:33:33 - INFO - Processing loader.sin
07/033/2016 19:33:33 - INFO - Checking header
07/033/2016 19:33:33 - INFO - Flashing data
07/033/2016 19:33:33 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : S1_Boot_MT6582_TC9SP_11 / Bootloader status : ROOTED
07/033/2016 19:33:33 - INFO - Max packet size forced to 512K
07/033/2016 19:33:33 - INFO - Making a TA backup
07/033/2016 19:33:33 - INFO - Opening TA partition 1
07/033/2016 19:33:33 - INFO - Start Dumping TA partition 1
07/033/2016 19:33:33 - INFO - Finished Dumping TA partition 1
07/033/2016 19:33:33 - INFO - Closing TA partition
[COLOR="Red"]07/033/2016 19:33:33 - ERROR -
07/033/2016 19:33:33 - ERROR - Error dumping TA. Aborted[/COLOR]
07/033/2016 19:33:33 - INFO - Opening TA partition 2
07/033/2016 19:33:33 - INFO - Start Dumping TA partition 2
07/033/2016 19:33:33 - INFO - Finished Dumping TA partition 2
07/033/2016 19:33:34 - INFO - TA partition 2 saved to C:\Users\Astra Efandri\.flashTool\registeredDevices\WUJ01H77QV\s1ta\2016-03-07_07-33-33\2.ta
07/033/2016 19:33:34 - INFO - Closing TA partition
07/033/2016 19:33:45 - INFO - Found a template session. Using it : C:\Users\Astra Efandri\.flashTool\devices\E21XX\default.fsc
07/033/2016 19:33:45 - INFO - Opening TA partition 2
07/033/2016 19:33:45 - INFO - Writing TA unit 00002774. Value : [01]
07/033/2016 19:33:45 - INFO - Closing TA partition
07/033/2016 19:33:45 - INFO - Processing partition.sin
07/033/2016 19:33:45 - INFO - Checking header
07/033/2016 19:33:45 - INFO - Flashing data
07/033/2016 19:33:45 - INFO - Set loader configuration : [00, 01, 00, 00, 00, 01]
07/033/2016 19:33:45 - INFO - Set loader configuration : [00, 01, 00, 00, 00, 03]
07/033/2016 19:33:45 - INFO - Flashing finished.
07/033/2016 19:33:45 - INFO - Please unplug and start your phone
07/033/2016 19:33:45 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
After the flash device is still bootloop and then I try using Emma Software , the result is also failed .
Emma's info like this "No available services matched the connected device."
Screenshoot :
Please help, so my device back to normal .
I've tried googling of any reference is not solved my problem .
thanks for your help . Sorry if my english is not good .
Thx before....
Click to expand...
Click to collapse
Please use flashtool and ftf file of Xperia E4 dual.
Watch YouTube.
How to flash the ftf by flashtool.

[Tutorial][Oreo][2.24] Step-by-step guide to gain root access properly

Please see note section before doing anything.
Though all the instructions are updated, you may want
to read through all comments.
For Oreo (both models), patch this after flashing custom kernel
View attachment drmfix.zip
in the recovery BEFORE booting into system.
Before start you need to install USB driver (for Windows). If it's not working, try using Androxyde's driver instead.
To flash stock image (not required, just for newer firmware or fingerprint support)
1. Download latest Flashtool. *make sure you patch x10flasher.jar to latest version by replacing it in your installation directory (mine was 0.9.23.2).
2. Download G82XX support for Flashtool from this thread (thanks IcemanSu)
3. Extract the file to "C:\Users\<username>\.flashTool\devices\G82XX".
4. Launch Flashtool, select Devices > Manage > Import. It should say "Loaded 95 devices" (before is 94).
2. Thanks to Androxyde, device list now includes G82XX on github so skip those steps.
3. Click Xperifirm icon (XF rightmost icon below toolbar), find and download firmware.
4. Tools > Bundle > Create. Select your firmware, choose all content then Create . If it says "a fsc script is found..." click Yes. (I tried choosing no and I cannot flash system partition (system.sin finished with errors).
5. Start devices in flash mode (hold vol. down and connect USB until LED blinking green).
6. Click Flash icon (first one) in Flashmode, select all content from bundle you created then Flash. Again, if it ask to use .fsc script, click Yes. It should finish without error.
*Device list from Github hasn't updated yet. So if you flash 41.3 (Oreo), make sure you duplicate 41.2.fsc to 41.3.fsc in C:\Users\%HOMEPATH%\.flashTool\devices\G82XX
7. Done, you can try booting to test if it works.
Starting from locked bootloader
1. Check "OEM unlocking" under developer options.
2. Unlock bootloader - follow instruction from this link. *Select Xperia XZ, it requires same unlock code as XZs. ** Data including internal storage will be wiped like typical Sony unlocking. Make sure you do some backup copy your important files out before proceed.
3. Enter fastboot - press vol. up the moment you connect USB. LED should be blue light.
4.1 Flash kernel with DRM patch *the kernel is specific to firmware version (not customizations) , so it will bootloop if you flash the wrong version.
41.3.A.2.24
41.3.A.0.401
41.2.A.7.76
41.2.A.7.65
41.2.A.7.53
41.2.A.4.35 dual sim
41.2.A.7.8 -.235
4.2 Flash TWRP (XZ still work perfectly) as recovery.
For new people, you can use Minimal ADB and Fastboot. Do "fastboot flash recovery <twrp_name>.img" and "fastboot flash boot <kernel_name>.img".
5. Once you installed recovery, give it a try. Enter recovery by holding power and vol. down when the phone is off (no LED).
6. Root your phone - Transfer SU flashable zip (only systemless for now, either Magisk with sony fix or SuperSU) to anywhere in the phone (MTP in recovery, OTG, external, or just boot up and download)
7. Install zip in recovery. If you can't mount internal and install SU, doing factory reset (format data) will remove encryption and do the trick. Magisk might work with encrypted data*see note below about magisk installation
8. Enjoy!
Note
(September 15 2017) To install Xposed
Don't install it with TWRP. Just install the module in Magisk Manager and you'll be fine.
(August 20, 2017) To disable force data encryption
I think I passed safety net by install magisk inside /data (with patched kernel).
Take a look at my thread. I also wrote how to modify it, so you can just download .img or do it yourself.
(July 31, 2017) To fix the green camera & other rooting problems on any firmware version ie. To use rootkernel tool (thanks tobias.waldvogel) to patch drm/ric fix.
Follow instruction from his thread.
TL;DR
- Download zip in the attactments and extract.
- Extract kernel.sin (using any archive manager eg. 7zip winrar) from your .ftf firmware.
- In Flashtool, use tool -> sin editor and extract your kernel.sin into .elf.
- Move your kernel image.elf in the same directory you just extracted.
- (Windows) Shift + right click -> open command windows here in the extracted directory and run "rootkernel <extracted elf> boot.img" (Linux) Just use terminal, cd to that directory and do the same.
- Select Y for everything except busybox.
- Done! you got patched kernel image.
(July 11, 2017) To make it compatible with magisk 13+
- Use the kernel with both DRM and RIC Protection patches so that it works well with magisk 13.1 and gets working camera.
Make sure you uninstall old version using uninstaller through TWRP or flash fresh kernel, wipe cache, install new one, then install latest magisk manager because it was made only for newer version.
If you have question or something goes wrong, feel free to ask me or other nice guys on XDA!
Thanks for everyone who contributes these contents.
Nicely written tutorial!
The kernel isn't required. You could just unlock bootloader and flash magiskv12sonyfix directly and get root + pass in safetypass but causes the pictures you take to become green images.
The kernel from arjun.arora has DRM-fix embedded which solves the camera problem but then it doesn't pass in safetypass in magisk. Rather a working camera than a pass I guess.
Personally I flashed TWRP-3.0.2-4 because it mounts internal+external while the newest version only mounts external.
WOW! It works perfectly. Thank you so much!
CIVMC said:
WOW! It works perfectly. Thank you so much!
Click to expand...
Click to collapse
Congrats!
If you use magisk, let me know if it passes safetynet test or not. Thanks.
zlRampageSlz said:
Congrats!
If you use magisk, let me know if it passes safetynet test or not. Thanks.
Click to expand...
Click to collapse
In fact, I don't know what magisk is . :laugh:
zlRampageSlz said:
Congrats!
If you use magisk, let me know if it passes safetynet test or not. Thanks.
Click to expand...
Click to collapse
It does if you skip the kernel but once you flash the kernel it doesn't pass anymore.
FartyParty said:
It does if you skip the kernel but once you flash the kernel it doesn't pass anymore.
Click to expand...
Click to collapse
Before I flashed this kernel, it didn't pass and got green screen too lol.
zlRampageSlz said:
Before I flashed this kernel, it didn't pass and got green screen too lol.
Click to expand...
Click to collapse
I tried a bunch of combination but everytime I flashed magisk directly after fresh new fw flash it passed, as soon as I flashed the kernel and then magick it stopped passing.
So for me, if I flashed magisk first it passes but then I get green image so I have to flash kernel and then magisk but then I lose safetypass, oh well .
Obviously not worth losing camera over safetypass.
Is X-Reality working with arjunarora DRM kernel? and where is the link to that kernel?
FartyParty said:
Nicely written tutorial!
The kernel isn't required. You could just unlock bootloader and flash magiskv12sonyfix directly and get root + pass in safetypass but causes the pictures you take to become green images.
The kernel from arjun.arora has DRM-fix embedded which solves the camera problem but then it doesn't pass in safetypass in magisk. Rather a working camera than a pass I guess.
Personally I flashed TWRP-3.0.2-4 because it mounts internal+external while the newest version only mounts external.
Click to expand...
Click to collapse
inteltecra1700 said:
Is X-Reality working with arjunarora DRM kernel? and where is the link to that kernel?
Click to expand...
Click to collapse
It's working great. Here is the link: https://forum.xda-developers.com/xzs/development/kernel-7-1-1-xperia-xzs-t3607488
this morning i unlocked bootloader, flash modified kernel and flash twrp kagura
then my phone wont boot, after sony logo directly enter twrp mode
tried flash stock rom, but failed
can someone tell whats wrong? below the log from flashtool
thanks
02/037/2017 16:37:46 - INFO - <- This level is successfully initialized
02/037/2017 16:37:47 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
02/037/2017 16:37:47 - INFO - Executing search strategies to find proxy selector
02/037/2017 16:37:48 - INFO - No proxy found for IE. Trying next one
02/037/2017 16:37:48 - INFO - Strategy firefox failed trying next one : No Firefox installation found
02/037/2017 16:37:48 - INFO - No proxy found for java. Trying next one
02/037/2017 16:37:48 - INFO - Syncing devices from github
02/037/2017 16:37:48 - INFO - Opening devices repository.
02/037/2017 16:37:48 - INFO - Scanning devices folder for changes.
02/038/2017 16:38:04 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
02/038/2017 16:38:04 - INFO - Pulling changes from github.
02/038/2017 16:38:05 - INFO - Quietly closing devices repository.
02/038/2017 16:38:05 - INFO - Devices sync finished.
02/038/2017 16:38:05 - INFO - Loading devices database
02/038/2017 16:38:05 - INFO - Loaded 94 devices
02/038/2017 16:38:05 - INFO - Starting phone detection
02/038/2017 16:38:10 - INFO - Device connected in flash mode
02/038/2017 16:38:29 - INFO - Loading devices database
02/038/2017 16:38:29 - INFO - Loaded 95 devices
02/039/2017 16:39:23 - INFO - Selected Bundle for Sony Xperia XZs(G8232). FW release : 41.2.A.0.235. Customization : Customized SG
02/039/2017 16:39:23 - INFO - Preparing files for flashing
02/041/2017 16:41:11 - INFO - Please connect your device into flashmode.
02/041/2017 16:41:12 - INFO - Opening device for R/W
02/041/2017 16:41:13 - INFO - Reading device information
02/041/2017 16:41:13 - INFO - Phone ready for flashmode operations.
02/041/2017 16:41:13 - INFO - Opening TA partition 2
02/041/2017 16:41:13 - INFO - Current device : G8232 - BH902M7972 - 1307-9001_R4D - 1306-8087_41.2.A.0.219 - GENERIC_41.2.A.0.219
02/041/2017 16:41:13 - INFO - Closing TA partition
02/041/2017 16:41:13 - INFO - Start Flashing
02/041/2017 16:41:13 - INFO - No loader in the bundle. Searching for one
02/041/2017 16:41:13 - INFO - No matching loader found
02/041/2017 16:41:13 - WARN - No loader found or set manually. Skipping loader
02/041/2017 16:41:13 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Bootloader status : ROOTED
02/041/2017 16:41:13 - INFO - Max packet size set to 4M
02/041/2017 16:41:13 - INFO - USB buffer size set to 512K
02/041/2017 16:41:25 - INFO - Parsing boot delivery
02/041/2017 16:41:25 - INFO - No flash script found.
02/041/2017 16:41:25 - INFO - Flash script is mandatory. Closing session
02/041/2017 16:41:25 - INFO - Ending flash session
02/041/2017 16:41:25 - INFO - Flashing finished.
02/041/2017 16:41:25 - INFO - Please unplug and start your phone
02/041/2017 16:41:25 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/041/2017 16:41:25 - INFO - Device connected in flash mode
nino_valerino said:
02/037/2017 16:37:47 - INFO - Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
Click to expand...
Click to collapse
Did you patch Flashtool to latest version? I didn't try 0.9.23.1 but using 0.9.23.2 did work. Simply replace x10flasher.jar in the directory you installed with new one.
It flashed nothing and there might be a problem reading that bundle.
Hope this helps!
This one will work https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634 as you can see v20 comfirmed working https://forum.xda-developers.com/showpost.php?p=72484790&postcount=152 . If any question go to my thread and ask :good:
finally done flashing firmware.
but after i flash kernel and twrp, i get 0mb internal
6. Boot into system. *When it ask to require PIN/Pattern at boot, SELECT NO. Otherwise, your device will be encryped and unable to install Magisk because TWRP won't let you mount internal. Download SU flashable zip (either Magisk with sony fix or SuperSU).
i don't have NO to select, only CANCEL and change language
and now im stuck at twrp
Flashing firmware wipes almost everything, including internal. So it's normal to have 0 mb.
You will see this prompt only If you set PIN or Pattern. It should be fine not to set passcode. You can flash magisk right after flashing recovery through MTP or external.
If magisk fail to install just do factory reset. This will remove data encryption.
zlRampageSlz said:
Flashing firmware wipes almost everything, including internal. So it's normal to have 0 mb.
You will see this prompt only If you set PIN or Pattern. It should be fine not to set passcode. You can flash magisk right after flashing recovery through MTP or external.
If magisk fail to install just do factory reset. This will remove data encryption.
Click to expand...
Click to collapse
get stuck on sony logo, after flashing recovery and magisk
nino_valerino said:
get stuck on sony logo, after flashing recovery and magisk
Click to expand...
Click to collapse
Try again after factory reset and wait a bit longer.
If not, looks like system is missing. Did you flash system correctly? Try booting into recovery. In mount, check your system partition size and tell me if its 0 mb or not.
Can you also send me flashtool log?
zlRampageSlz said:
Try again after factory reset and wait a bit longer.
If not, looks like system is missing. Did you flash system correctly? Try booting into recovery. In mount, check your system partition size and tell me if its 0 mb or not.
Can you also send me flashtool log?
Click to expand...
Click to collapse
i think my problem is recovery and root.
after flash firmware booting was normal but after flash recovery and root, it wont boot and always back to recovery
this my flashtool log
02/025/2017 21:25:40 - INFO - <- This level is successfully initialized
02/025/2017 21:25:43 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
02/025/2017 21:25:43 - INFO - Executing search strategies to find proxy selector
02/025/2017 21:25:43 - INFO - No proxy found for IE. Trying next one
02/025/2017 21:25:43 - INFO - Strategy firefox failed trying next one : No Firefox installation found
02/025/2017 21:25:43 - INFO - No proxy found for java. Trying next one
02/025/2017 21:25:44 - INFO - Syncing devices from github
02/025/2017 21:25:44 - INFO - Opening devices repository.
02/025/2017 21:25:44 - INFO - Scanning devices folder for changes.
02/026/2017 21:26:01 - INFO - Pulling changes from github.
02/026/2017 21:26:02 - INFO - Quietly closing devices repository.
02/026/2017 21:26:02 - INFO - Devices sync finished.
02/026/2017 21:26:02 - INFO - Loading devices database
02/026/2017 21:26:02 - INFO - Loaded 94 devices
02/026/2017 21:26:02 - INFO - Starting phone detection
02/026/2017 21:26:07 - INFO - Device disconnected
02/027/2017 21:27:12 - INFO - Loading devices database
02/027/2017 21:27:12 - INFO - Loaded 95 devices
02/027/2017 21:27:26 - INFO - Selected Bundle for Sony Xperia XZs(G8232). FW release : 41.2.A.0.235. Customization : Customized TH
02/027/2017 21:27:26 - INFO - Preparing files for flashing
02/029/2017 21:29:57 - INFO - Please connect your device into flashmode.
02/030/2017 21:30:21 - INFO - Device connected in flash mode
02/030/2017 21:30:21 - INFO - Opening device for R/W
02/030/2017 21:30:22 - INFO - Reading device information
02/030/2017 21:30:22 - INFO - Phone ready for flashmode operations.
02/030/2017 21:30:22 - INFO - Opening TA partition 2
02/030/2017 21:30:22 - INFO - Current device : G8232 - BH902M7972 - 1307-9001_R4D - 1306-8087_41.2.A.0.219 - GENERIC_41.2.A.0.219
02/030/2017 21:30:22 - INFO - Closing TA partition
02/030/2017 21:30:22 - INFO - Start Flashing
02/030/2017 21:30:22 - INFO - No loader in the bundle. Searching for one
02/030/2017 21:30:22 - INFO - No matching loader found
02/030/2017 21:30:22 - WARN - No loader found or set manually. Skipping loader
02/030/2017 21:30:22 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_115 / Bootloader status : ROOTED
02/030/2017 21:30:22 - INFO - Max packet size set to 4M
02/030/2017 21:30:22 - INFO - USB buffer size set to 512K
02/030/2017 21:30:35 - INFO - Parsing boot delivery
02/030/2017 21:30:59 - INFO - Found a template session. Using it : C:\Users\XPS\.flashTool\devices\G82XX\41.fsc
02/030/2017 21:30:59 - INFO - Set loader configuration : [00 01 00 00 00 0C]
02/030/2017 21:30:59 - INFO - Opening TA partition 2
02/030/2017 21:30:59 - INFO - Writing TA unit 00002774. Value : 01
02/030/2017 21:30:59 - INFO - Closing TA partition
02/031/2017 21:31:00 - INFO - Processing partition.sin
02/031/2017 21:31:00 - INFO - Checking header
02/031/2017 21:31:00 - INFO - Flashing data
02/031/2017 21:31:00 - INFO - Opening TA partition 2
02/031/2017 21:31:00 - INFO - Processing cmnlib_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:00 - INFO - Checking header
02/031/2017 21:31:00 - INFO - Flashing data
02/031/2017 21:31:00 - INFO - Processing devcfg_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:00 - INFO - Checking header
02/031/2017 21:31:00 - INFO - Flashing data
02/031/2017 21:31:01 - INFO - Processing emmc_appsboot_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:01 - INFO - Checking header
02/031/2017 21:31:01 - INFO - Flashing data
02/031/2017 21:31:01 - INFO - Processing hyp_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:01 - INFO - Checking header
02/031/2017 21:31:01 - INFO - Flashing data
02/031/2017 21:31:02 - INFO - Closing TA partition
02/031/2017 21:31:02 - INFO - Opening TA partition 2
02/031/2017 21:31:02 - INFO - Writing TA unit 0000084F. Value : 1A CE 33 00 01 00 08 03 00 02 04 02 05 00 02 02 10 00 10 05 00 01 03 02 00 10 05 00 04 83 03 00 10 02 00 04 85 05 00 03 03 03 00 10 05 00 05 83 02 00 10 02 00 05 85 1A 00 02 00 A9 09 BE BA A9 09 00 00 B3 08 BE BA B3 08 00 00 7E 13 BE BA 7E 13 00 00 04 00 03 00 02 00 04 00 04 00 B0 04 0E 00 06 00 B8 0B 01 4B 00 00 00 03 96 00 2C 01 03 00 09 00 01
02/031/2017 21:31:02 - INFO - Writing TA unit 000008FD. Value : 00
02/031/2017 21:31:02 - INFO - Closing TA partition
02/031/2017 21:31:02 - INFO - Opening TA partition 2
02/031/2017 21:31:03 - INFO - Processing keymaster_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:03 - INFO - Checking header
02/031/2017 21:31:03 - INFO - Flashing data
02/031/2017 21:31:03 - INFO - Processing pmic_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:03 - INFO - Checking header
02/031/2017 21:31:03 - INFO - Flashing data
02/031/2017 21:31:03 - INFO - Processing rpm_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:03 - INFO - Checking header
02/031/2017 21:31:03 - INFO - Flashing data
02/031/2017 21:31:05 - INFO - Processing s1sbl_S1_Boot_MSM8996_LA2_0_N_115_AID_4_S1-BOOT-LIVE-DE8D-0004-ELF_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:05 - INFO - Checking header
02/031/2017 21:31:05 - INFO - Flashing data
02/031/2017 21:31:06 - INFO - Processing tzs1attest_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:06 - INFO - Checking header
02/031/2017 21:31:06 - INFO - Flashing data
02/031/2017 21:31:06 - INFO - Processing tz_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:06 - INFO - Checking header
02/031/2017 21:31:06 - INFO - Flashing data
02/031/2017 21:31:07 - INFO - Processing tzs1sbl_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:07 - INFO - Checking header
02/031/2017 21:31:07 - INFO - Flashing data
02/031/2017 21:31:07 - INFO - Processing xbl_S1_Boot_MSM8996_LA2_0_N_115_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
02/031/2017 21:31:07 - INFO - Checking header
02/031/2017 21:31:07 - INFO - Flashing data
02/031/2017 21:31:08 - INFO - Closing TA partition
02/031/2017 21:31:08 - INFO - Opening TA partition 2
02/031/2017 21:31:08 - WARN - apps_log is excluded from bundle
02/031/2017 21:31:08 - WARN - diag is excluded from bundle
02/031/2017 21:31:09 - WARN - ssd is excluded from bundle
02/031/2017 21:31:09 - INFO - Processing adspso.sin
02/031/2017 21:31:09 - INFO - Checking header
02/031/2017 21:31:09 - INFO - Flashing data
02/031/2017 21:31:10 - INFO - Processing cache.sin
02/031/2017 21:31:10 - INFO - Checking header
02/031/2017 21:31:10 - INFO - Flashing data
02/031/2017 21:31:10 - INFO - Processing modem.sin
02/031/2017 21:31:10 - INFO - Checking header
02/031/2017 21:31:10 - INFO - Flashing data
02/031/2017 21:31:13 - WARN - Qnovo is excluded from bundle
02/031/2017 21:31:14 - INFO - Processing amss_fs_1.sin
02/031/2017 21:31:14 - INFO - Checking header
02/031/2017 21:31:14 - INFO - Flashing data
02/031/2017 21:31:14 - INFO - Processing amss_fs_2.sin
02/031/2017 21:31:14 - INFO - Checking header
02/031/2017 21:31:14 - INFO - Flashing data
02/031/2017 21:31:14 - INFO - Processing amss_fsg.sin
02/031/2017 21:31:14 - INFO - Checking header
02/031/2017 21:31:14 - INFO - Flashing data
02/031/2017 21:31:15 - WARN - persist is excluded from bundle
02/031/2017 21:31:15 - INFO - Processing kernel.sin
02/031/2017 21:31:15 - INFO - Checking header
02/031/2017 21:31:15 - INFO - Flashing data
02/031/2017 21:31:17 - INFO - Processing fotakernel.sin
02/031/2017 21:31:17 - INFO - Checking header
02/031/2017 21:31:18 - INFO - Flashing data
02/031/2017 21:31:19 - INFO - Processing ramdump.sin
02/031/2017 21:31:19 - INFO - Checking header
02/031/2017 21:31:19 - INFO - Flashing data
02/031/2017 21:31:29 - INFO - Processing system.sin
02/031/2017 21:31:29 - INFO - Checking header
02/031/2017 21:31:29 - INFO - Flashing data
02/034/2017 21:34:45 - INFO - Closing TA partition
02/034/2017 21:34:45 - INFO - Opening TA partition 2
02/034/2017 21:34:45 - INFO - Processing oem.sin
02/034/2017 21:34:45 - INFO - Checking header
02/034/2017 21:34:45 - INFO - Flashing data
02/034/2017 21:34:47 - WARN - userdata is excluded from bundle
02/034/2017 21:34:47 - INFO - Closing TA partition
02/034/2017 21:34:48 - INFO - Opening TA partition 2
02/034/2017 21:34:48 - WARN - Unit 2212 not found in bundle
02/034/2017 21:34:48 - INFO - Closing TA partition
02/034/2017 21:34:48 - INFO - Opening TA partition 2
02/034/2017 21:34:48 - INFO - Writing TA unit 00000964. Value : 00
02/034/2017 21:34:48 - INFO - Closing TA partition
02/034/2017 21:34:48 - INFO - Opening TA partition 2
02/034/2017 21:34:48 - INFO - Writing TA unit 000009B6. Value :
02/034/2017 21:34:48 - INFO - Closing TA partition
02/034/2017 21:34:49 - INFO - Opening TA partition 2
02/034/2017 21:34:49 - INFO - Writing TA unit 00000907. Value : 00
02/034/2017 21:34:49 - INFO - Closing TA partition
02/034/2017 21:34:50 - INFO - Opening TA partition 2
02/034/2017 21:34:50 - INFO - Writing TA unit 0000091A. Value : 00
02/034/2017 21:34:50 - INFO - Closing TA partition
02/034/2017 21:34:51 - INFO - Opening TA partition 2
02/034/2017 21:34:51 - WARN - Unit 2550 not found in bundle
02/034/2017 21:34:51 - INFO - Closing TA partition
02/034/2017 21:34:51 - INFO - Opening TA partition 2
02/034/2017 21:34:51 - WARN - Unit 2553 not found in bundle
02/034/2017 21:34:51 - INFO - Closing TA partition
02/034/2017 21:34:51 - INFO - Opening TA partition 2
02/034/2017 21:34:51 - INFO - Writing TA unit 000009A9. Value : 00
02/034/2017 21:34:51 - INFO - Closing TA partition
02/034/2017 21:34:52 - INFO - Opening TA partition 2
02/034/2017 21:34:52 - INFO - Processing elabel.sin
02/034/2017 21:34:52 - INFO - Checking header
02/034/2017 21:34:52 - INFO - Flashing data
02/034/2017 21:34:53 - INFO - Closing TA partition
02/034/2017 21:34:53 - INFO - Opening TA partition 2
02/034/2017 21:34:53 - INFO - Writing TA unit 00002725. Value : 32 30 31 37 2D 30 36 2D 30 32 20 32 31 3A 33 34 3A 35 33 00
02/034/2017 21:34:53 - INFO - Writing TA unit 00002774. Value : 00
02/034/2017 21:34:53 - INFO - Closing TA partition
02/034/2017 21:34:54 - INFO - Ending flash session
02/034/2017 21:34:54 - INFO - Flashing finished.
02/034/2017 21:34:54 - INFO - Please unplug and start your phone
02/034/2017 21:34:54 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Did you flash TWRP as recovery, not system?
Recovery should be launched when you hold power and vol. down. System is launched when you hold power like normal boot. Sorry, I will be on board very soon. Coming back around 6-7 hours. You can leave any message here.
problem solved
the problem was everytime i flash recovery, my phone wont boot
so i hotboot recovery, flash supersu with twrp. done. root success

Cannot enter fastboot. Is there a chance?

Today I received my second X Compact after the first one stopped recognizing SIM card. And I really didn't want to set it up.
So I made a backup using TWRP from my old phone and restored it on the new one. The partitions that I foolishly tried restored were: Boot, System, Vendor, Data, OEM, and Trim-Area.
I don't know which of them did it (Trim-Area?), but the phone does not boot anymore. I cannot enter fastboot, no blue LED. And the only reason to think that there is still life somewhere in there is because the phone is recognized by PC when connected. However an attempt to flash a firmware using Sony Mobile Flasher fails:
Code:
13/030/2020 20:30:12 - INFO - Selected Bundle for Sony Xperia X Compact(F5321). FW release : 34.4.A.2.118. Customization : Customized DE
13/030/2020 20:30:12 - INFO - Preparing files for flashing
13/030/2020 20:30:36 - INFO - Please connect your device into flashmode.
13/030/2020 20:30:50 - INFO - Using Gordon gate drivers version 3.1.0.0
13/030/2020 20:30:50 - INFO - Opening device for R/W
13/030/2020 20:30:50 - INFO - Device ready for R/W.
13/030/2020 20:30:50 - INFO - Reading device information
13/030/2020 20:30:50 - INFO - Phone ready for flashmode operations.
13/030/2020 20:30:50 - INFO - Opening TA partition 2
13/030/2020 20:30:50 - INFO - Current device : F5321 - BH90037B5Z - Unknown: Sep 6 2018/05:16:07 - 1302-7793_34.4.A.2.118 - GENERIC_34.4.A.2.118
13/030/2020 20:30:50 - INFO - Closing TA partition
13/030/2020 20:30:50 - INFO - Start Flashing
13/030/2020 20:30:50 - INFO - No loader in the bundle. Searching for one
13/030/2020 20:30:50 - INFO - No matching loader found
13/030/2020 20:30:50 - WARN - No loader found or set manually. Skipping loader
13/030/2020 20:30:50 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_O_168 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_O_168 / Bootloader status : NOT_ROOTABLE
13/030/2020 20:30:50 - INFO - Max packet size set to 4M
13/030/2020 20:30:50 - INFO - USB buffer size set to 512K
13/030/2020 20:30:50 - INFO - Parsing boot delivery
13/030/2020 20:30:50 - INFO - Found a template session. Using it : C:\Users\Eugene Strizhok\.flashTool\firmwares\prepared\34.fsc
13/030/2020 20:30:50 - INFO - Set loader configuration : [00 01 00 00 00 0C]
13/030/2020 20:30:50 - INFO - Opening TA partition 2
13/030/2020 20:30:50 - INFO - Writing TA unit 00002774. Value : 01
13/030/2020 20:30:50 - INFO - Closing TA partition
13/030/2020 20:30:50 - INFO - Processing partition-image.sin
13/030/2020 20:30:50 - INFO - Checking header
13/030/2020 20:30:50 - ERROR - Processing of partition-image.sin finished with errors.
13/030/2020 20:30:50 - INFO - Flashing finished.
I have a full TWRP backup of the new phone from before my restore attempt. But is there a way to restore it?
estrizhok said:
Today I received my second X Compact after the first one stopped recognizing SIM card. And I really didn't want to set it up.
So I made a backup using TWRP from my old phone and restored it on the new one. The partitions that I foolishly tried restored were: Boot, System, Vendor, Data, OEM, and Trim-Area.
I don't know which of them did it (Trim-Area?), but the phone does not boot anymore. I cannot enter fastboot, no blue LED. And the only reason to think that there is still life somewhere in there is because the phone is recognized by PC when connected. However an attempt to flash a firmware using Sony Mobile Flasher fails:
Code:
13/030/2020 20:30:12 - INFO - Selected Bundle for Sony Xperia X Compact(F5321). FW release : 34.4.A.2.118. Customization : Customized DE
13/030/2020 20:30:12 - INFO - Preparing files for flashing
13/030/2020 20:30:36 - INFO - Please connect your device into flashmode.
13/030/2020 20:30:50 - INFO - Using Gordon gate drivers version 3.1.0.0
13/030/2020 20:30:50 - INFO - Opening device for R/W
13/030/2020 20:30:50 - INFO - Device ready for R/W.
13/030/2020 20:30:50 - INFO - Reading device information
13/030/2020 20:30:50 - INFO - Phone ready for flashmode operations.
13/030/2020 20:30:50 - INFO - Opening TA partition 2
13/030/2020 20:30:50 - INFO - Current device : F5321 - BH90037B5Z - Unknown: Sep 6 2018/05:16:07 - 1302-7793_34.4.A.2.118 - GENERIC_34.4.A.2.118
13/030/2020 20:30:50 - INFO - Closing TA partition
13/030/2020 20:30:50 - INFO - Start Flashing
13/030/2020 20:30:50 - INFO - No loader in the bundle. Searching for one
13/030/2020 20:30:50 - INFO - No matching loader found
13/030/2020 20:30:50 - WARN - No loader found or set manually. Skipping loader
13/030/2020 20:30:50 - INFO - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_O_168 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_O_168 / Bootloader status : NOT_ROOTABLE
13/030/2020 20:30:50 - INFO - Max packet size set to 4M
13/030/2020 20:30:50 - INFO - USB buffer size set to 512K
13/030/2020 20:30:50 - INFO - Parsing boot delivery
13/030/2020 20:30:50 - INFO - Found a template session. Using it : C:\Users\Eugene Strizhok\.flashTool\firmwares\prepared\34.fsc
13/030/2020 20:30:50 - INFO - Set loader configuration : [00 01 00 00 00 0C]
13/030/2020 20:30:50 - INFO - Opening TA partition 2
13/030/2020 20:30:50 - INFO - Writing TA unit 00002774. Value : 01
13/030/2020 20:30:50 - INFO - Closing TA partition
13/030/2020 20:30:50 - INFO - Processing partition-image.sin
13/030/2020 20:30:50 - INFO - Checking header
13/030/2020 20:30:50 - ERROR - Processing of partition-image.sin finished with errors.
13/030/2020 20:30:50 - INFO - Flashing finished.
I have a full TWRP backup of the new phone from before my restore attempt. But is there a way to restore it?
Click to expand...
Click to collapse
Definitely TA, and probably System - don't try to use from one phone to another. I think the phone is probably saveable, but I guess you lost your TA forever... I'm surprised that there's no fastboot, but you have flash mode. I would try with Androxyde Flashtool, try connecting in different ways and try flashing with that. Fastboot won't help much at this point, unless you want to try to flash AOSP or something. If you can get Flashtool to recognize, you can try "reboot to bootloader" option.
levone1 said:
Definitely TA, and probably System - don't try to use from one phone to another. I think the phone is probably saveable, but I guess you lost your TA forever... I'm surprised that there's no fastboot, but you have flash mode. I would try with Androxyde Flashtool, try connecting in different ways and try flashing with that. Fastboot won't help much at this point, unless you want to try to flash AOSP or something. If you can get Flashtool to recognize, you can try "reboot to bootloader" option.
Click to expand...
Click to collapse
Thank you! Androxyde Flashtool was exactly the tool I tried to flash the phone with. And flashmode is the only mode that works (but flashing fails).
Anyway, I have given up on that phone and ordered one more

Somebody helps me please...

I bought a Sony Z3 (SOL26 AU) from my friends 3 days ago.
After that, I started to flash the lastest stock for the phone. But the weird thing is no matter I use which version of Flashtool, I can not flash the 23.5.A.1.291 ftf to my phone.
If I use the flashtool-0.9.15.0, flash 23.5.A.1.291, it will show - ERROR - - INFO - Cannot open bundle. Flash operation canceled.
If I use the Flashtool 0.9.18.6, flash 23.5.A.1.291, it will show - ERROR - root : this bundle is not valid.
If I use the Flashtool 0.9.34.0, flash 23.5.A.1.291, it shows
25/026/2022 22:26:41 - INFO - Using Gordon gate drivers version 3.1.0.0
25/026/2022 22:26:42 - INFO - Opening device for R/W
25/026/2022 22:26:42 - INFO - Device ready for R/W.
25/026/2022 22:26:42 - INFO - Reading device information
25/026/2022 22:26:42 - INFO - Phone ready for flashmode operations.
25/026/2022 22:26:42 - INFO - Opening TA partition 2
25/026/2022 22:26:42 - INFO - Current device : D6603 - CB5A270HY4 - 1286-2777_R9B - 1282-2729_23.0.A.2.93 - GLOBAL-LTE_23.0.A.2.93
25/026/2022 22:26:42 - INFO - Closing TA partition
25/026/2022 22:26:42 - INFO - Start Flashing
25/026/2022 22:26:42 - INFO - Processing loader.sin
25/026/2022 22:26:42 - INFO - Checking header
25/026/2022 22:26:42 - INFO - Flashing data
25/026/2022 22:26:42 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8974AC_LA3.0_52-2 / Bootloader status : ROOTED
25/026/2022 22:26:42 - INFO - Max packet size set to 512K
25/026/2022 22:26:42 - INFO - USB buffer size set to 512K
25/026/2022 22:26:42 - INFO - Parsing boot delivery
25/026/2022 22:26:42 - INFO - No flash script found. Using 0.9.18 flash engine
25/026/2022 22:26:42 - INFO - Opening TA partition 2
25/026/2022 22:26:43 - INFO - Writing TA unit 00002774. Value : 01
25/026/2022 22:26:43 - INFO - Closing TA partition
25/026/2022 22:26:43 - INFO - Phone boot version : S1_Boot_MSM8974AC_LA3.0_52-2. Boot delivery version : S1_Boot_MSM8974AC_LA3.0-M-3
25/026/2022 22:26:43 - INFO - Going to flash boot delivery
25/026/2022 22:26:43 - INFO - Opening TA partition 2
25/026/2022 22:26:43 - INFO - Processing emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin
25/026/2022 22:26:43 - INFO - Checking header
25/026/2022 22:26:43 - ERROR - Processing of emmc_appsboot_S1_Boot_MSM8974AC_LA3_0_M_3_AID_4_PLATFORM-MSM8974AC-LIVE-HWID007B40E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-9C84-0004-MMC.sin finished with errors.
25/026/2022 22:26:43 - INFO - Ending flash session
25/026/2022 22:26:43 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080021";
25/026/2022 22:26:43 - ERROR - Error flashing. Aborted
Does anybody help me with this situation??? I had tried it for 3 days which made me mad....
Btw, I can use any version of Flashtool to flash the KK stock ftf successfully... I don't understand why...The stock ftf I had change 3 version, but lead to the same error.....
hey, i dont very good with english, but you verify before the model of the FTF? in the log your phone is identified with the number D6603 ( idont know is the ftf model info or the actual device), the FTF must match the same model number. hope this helps...

Categories

Resources