What should happen to my z1c? - Xperia Z1 Compact Q&A, Help & Troubleshooting

Hello guys I am a new member here but I have been followed this forum for years and at the end I decided to became a member to get your help.
I have used my device for 5 years and after a while the power button was broken. I needed to press it hard to make it work. At the end my z1c suddenly turned off and I couldn't turn on it anymore. These are things i did:
- I tried to turn on it by pressing the small button near the sim slot. It doesn't give any response on battery but when it is on plug it vibrates three times but it doesn't boot and starts to charge the phone again. By the way I am able to charge the device.
-To flash a firmware I used Software Repair option on Xperia Companion but unfortunately I broke power flex cable while disassembling so
the device couldn't enter download mode. It also sometimes gives an error like this: "Your device is locked".
- I also tried munjeni's testpoint solution .Here is the log:
Code:
12.07.2019 18:54:09 Welcome to S1 tool.
12.07.2019 18:54:09 That is small and crippled subset of SETOOL2 service tool.
12.07.2019 18:54:13
12.07.2019 18:54:13 SELECT FIRMWARE PACKAGES
12.07.2019 18:54:13 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
12.07.2019 18:54:18 CHECKING PACKAGES ...
12.07.2019 18:54:18
12.07.2019 18:54:18 DETACH USB CABLE FROM PHONE
12.07.2019 18:54:18 REMOVE BATTERY FROM PHONE
12.07.2019 18:54:18 ATTACH TESTPOINT
12.07.2019 18:54:18 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
12.07.2019 18:54:18
12.07.2019 19:08:01 will use Sahara protocol ...
12.07.2019 19:08:01 REMOVE TESTPOINT NOW, THEN PRESS "READY"
12.07.2019 19:08:01
12.07.2019 19:08:46 PROCESSING ...
12.07.2019 19:08:47 llbug: write error: "Aygıt komutu algılayamıyor"
12.07.2019 19:08:47 llbug: blk write fail.fatal
12.07.2019 19:08:47 Elapsed:873 secs.
12.07.2019 19:09:10
12.07.2019 19:09:10 SELECT FIRMWARE PACKAGES
12.07.2019 19:09:10 YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
12.07.2019 19:09:14 CHECKING PACKAGES ...
12.07.2019 19:09:14
12.07.2019 19:09:14 DETACH USB CABLE FROM PHONE
12.07.2019 19:09:14 REMOVE BATTERY FROM PHONE
12.07.2019 19:09:14 ATTACH TESTPOINT
12.07.2019 19:09:14 PRESS "READY", THEN ATTACH USB CABLE TO PHONE
12.07.2019 19:09:14
12.07.2019 19:09:42 will use Sahara protocol ...
12.07.2019 19:09:42 REMOVE TESTPOINT NOW, THEN PRESS "READY"
12.07.2019 19:09:42
12.07.2019 19:09:56 PROCESSING ...
12.07.2019 19:09:56 SERIAL NUMBER : 08194506
12.07.2019 19:09:56 HARDWARE ID : 04000100E1007B00
12.07.2019 19:09:56 HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
12.07.2019 19:09:57 Emergency loader uploaded ...
12.07.2019 19:10:01
12.07.2019 19:10:01 RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
12.07.2019 19:10:01 LOADER AID: 0004
12.07.2019 19:10:01 DEVICE ID: 06451908
12.07.2019 19:10:01 FLASH ID: "0015/01000001"
12.07.2019 19:10:01 LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
12.07.2019 19:10:01
12.07.2019 19:10:02 WRITING PACKAGES ...
12.07.2019 19:10:02 Processing package
12.07.2019 19:10:02 C:\Users\BARIN\Desktop\fw\amami_testpoint.SIN_FILE_SET
12.07.2019 19:10:02
12.07.2019 19:10:02 WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_RHINE1.2_LA1.04_19
12.07.2019 19:10:02 PARSING: "DEVELOPMENT"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
12.07.2019 19:10:02 PARSING: "TEST_OEM0_007B00E1"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
12.07.2019 19:10:02 value OTP_DATA_1 : 00000100, not match 01000400
12.07.2019 19:10:02 value IDCODE_1 : 007B00E1, match 007B00E1
12.07.2019 19:10:02 PARSING: "PRECOMMERCIAL_007B00E1"
12.07.2019 19:10:02 value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
12.07.2019 19:10:02 value OTP_DATA_1 : 01000400, match 01000400
12.07.2019 19:10:02 value IDCODE_1 : 007B00E1, match 007B00E1
12.07.2019 19:10:02 PROCESSING : dbi_S1_Boot_MSM8974_Rhine1.2_19_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:02 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
12.07.2019 19:10:02 PROCESSING : s1sbl_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : sbl1_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : tz_S1_Boot_MSM8974_Rhine1.2_19_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
12.07.2019 19:10:03 PROCESSING : Amami_S1BootConfig_MiscTA_130115_1430.ta
12.07.2019 19:10:03 MINOR ERROR [ Open_TA_failed, err: 001D ]
12.07.2019 19:10:03 BOOT UPDATED
12.07.2019 19:10:03 Processing ACPU files
12.07.2019 19:10:03 PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:04 PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:05 PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:06 PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:07 SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
12.07.2019 19:10:07 PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
12.07.2019 19:10:07 no update files in package
12.07.2019 19:10:07 FINISHED
12.07.2019 19:10:08 Elapsed:57 secs.
I wanted to know what should happen to my device. Possible scenarios on my mind are those:
- Power ic on the mainboard broken,
- Somebody copied its imei and device was locked (It is nearly impossible as it has qualcomm chip),
- Battery completely discharged
I would be really happy if you give your opinions and solutions other than mine. Thanks for your help.

Sounds like you should replace the battery.

Related

How do I flash a UK ROM on an R800X with flashtool?

I recently tried to flash 2 different UK roms on my R800X with flashtool and get the following log in the flashtool window
12/040/2012 14:40:34 - INFO - Device connected in flash mode
12/040/2012 14:40:36 - INFO - Selected R800i_4.0.2.A.0.58_Enhanced.ftf
12/040/2012 14:40:36 - INFO - Preparing files for flashing
12/040/2012 14:40:37 - INFO - Please connect your device into flashmode.
12/040/2012 14:40:38 - INFO - Opening device for R/W
12/040/2012 14:40:38 - INFO - Reading device information
12/040/2012 14:40:38 - INFO - Phone ready for flashmode operations.
12/040/2012 14:40:38 - INFO - Start Flashing
12/040/2012 14:40:38 - INFO - Flashing loader
12/040/2012 14:40:40 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
12/040/2012 14:40:40 - INFO - Flashing fota1.sin
12/040/2012 14:40:40 - INFO - Ending flash session
12/040/2012 14:40:40 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";
12/040/2012 14:40:40 - ERROR - Error flashing. Aborted
Is there a reason or a fix to make this rom flash? I just want the UK UI, Game Pads and WiFi to work and that's it.

need E9+ flashtools firmware full for unbreack totualy is dead

hi pls share htc e9+ flashtools firmware
phone is soft breack
Operation : Check / Read Info [ v1.58 ]
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey
Wait for phone...
Phone found! [ 7 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6795
BB_CPU_NME : [MediaTek] Helio[X10]|MT6795_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
[DA_ERROR] : SECURITYBOOT_BOOT_NOT_ACCEPTED
Boot Error!
Operation Failed
Elapsed: 00:00:28
Reconnect Power/Cable!

[Help Please] Stucked in bootloop and cant flash rom using twrp.

Hey guys last night I factory reset my phone using inbulit clock work mod but it was unsuccessful as my phone was only 2% charged and it switched off ( I was using RR 7.1 ROM ) then after charging when I try to switch it on it sucked in boot loop. Now the problem is when I try to flash the same ROM or any other ROM using twrp it shows failed message but when i try to flash gapps it easily get flashed. Even when I try to wipe Dalvik chace and data it shows failed message. How can I fix it , I remember I haven't switched on the usb debugging so how can I flash the ROM using flash tool please help.
And When I try to on the in-built clockwork mod ( using vol down button) it shows only black screen.
I Can provide screenshot if someone helps sorry for my bad english.
I would suggest you to flash the stock firmware file on your xperia. To do this follow me:
-charge your phone to at least 80%
-install the fastboot and adb drivers onto your pc if not installed previously
-open xperia flashtool by androxyde
-click on xpirifirm from the flashtool window and download the firmware for your specific region(if your region is not listed then any relevant region would do)
-after the download has finished, exit xpirifirm
-then connect your xperia device to the pc in the flashmode(connecting the power cable while pressing down the volume(-) button)
-now click the flash button in flashtool and select flashmode
-locate the firmware file from the browse button
-select wipe userdata.sin (or something similar in the wipe tab)
-leave all the other options and checkboxes blank or unchanged
-click on flash and the process will begin
-be patient as the time taken for 'preparing files for flashing' is between 5-15 minutes so don't abort the process
-after the flash is complete the device will be disconnect from the pc and will restart
-if not then restart manually
Hope this solves your problem. Good Luck :good:
19/042/2017 05:42:36 - INFO - Preparing files for flashing
19/043/2017 05:43:13 - INFO - Please connect your device into flashmode.
19/043/2017 05:43:35 - INFO - Device connected in flash mode
19/043/2017 05:43:36 - INFO - Opening device for R/W
19/043/2017 05:43:36 - INFO - Reading device information
19/043/2017 05:43:36 - INFO - Phone ready for flashmode operations.
19/043/2017 05:43:36 - INFO - Opening TA partition 2
19/043/2017 05:43:36 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910MFH6Y - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
19/043/2017 05:43:36 - INFO - Closing TA partition
19/043/2017 05:43:36 - INFO - Start Flashing
19/043/2017 05:43:36 - INFO - Processing loader.sin
19/043/2017 05:43:36 - INFO - Checking header
19/043/2017 05:43:36 - INFO - Flashing data
19/043/2017 05:43:36 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/043/2017 05:43:36 - INFO - Max packet size set to 512K
19/043/2017 05:43:36 - INFO - USB buffer size set to 512K
19/043/2017 05:43:39 - INFO - Parsing boot delivery
19/043/2017 05:43:39 - INFO - Ending flash session
19/043/2017 05:43:39 - ERROR - null
19/043/2017 05:43:39 - ERROR - Error flashing. Aborted
19/043/2017 05:43:39 - INFO - Device connected in flash mode
19/043/2017 05:43:40 - INFO - Device disconnected
19/043/2017 05:43:43 - INFO - Device connected in flash mode
19/044/2017 05:44:43 - INFO - Device disconnected
19/045/2017 05:45:05 - INFO - Device connected with USB debugging off
19/045/2017 05:45:05 - INFO - For 2011 devices line, be sure you are not in MTP mode
Hey try again with flashtool version 0.9.22.3. Try, this could fix your problem. If not then go to flashtool fastboot section and then flash twrp recovery in the boot section and then try the usual method .

i think i wiped something through twrp and now its soft brick.please help

i think i wiped something through twrp and now its soft brick.please help
i cant flash through flash tools gives me error.:
11/048/2017 23:48:37 - INFO - Selected Bundle for Sony Xperia M Dual(C2005). FW release : 15.5.A.1.5. Customization : DE
11/048/2017 23:48:37 - INFO - Preparing files for flashing
11/048/2017 23:48:46 - INFO - Please connect your device into flashmode.
11/048/2017 23:48:53 - INFO - Device connected in flash mode
11/048/2017 23:48:53 - INFO - Opening device for R/W
11/048/2017 23:48:53 - INFO - Reading device information
11/048/2017 23:48:53 - INFO - Phone ready for flashmode operations.
11/048/2017 23:48:53 - INFO - Opening TA partition 2
11/048/2017 23:48:53 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910S8XGK - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
11/048/2017 23:48:53 - INFO - Closing TA partition
11/048/2017 23:48:53 - INFO - Start Flashing
11/048/2017 23:48:53 - INFO - Processing loader.sin
11/048/2017 23:48:53 - INFO - Checking header
11/048/2017 23:48:53 - INFO - Flashing data
11/048/2017 23:48:54 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
11/048/2017 23:48:54 - INFO - Max packet size set to 512K
11/048/2017 23:48:54 - INFO - USB buffer size set to 512K
11/048/2017 23:48:54 - INFO - Parsing boot delivery
11/048/2017 23:48:54 - INFO - Ending flash session
11/048/2017 23:48:54 - ERROR - null
11/048/2017 23:48:54 - ERROR - Error flashing. Aborted
11/048/2017 23:48:54 - INFO - Device connected in flash mode
i cant remember if i wiped partition,system, data, dalvik or cache.
i can access twrp and install a custom rom but noting works(wifi..etc)since there is no firmware installed any more.just only a custom rom.
please help
thank you.
hussian said:
i think i wiped something through twrp and now its soft brick.please help
i cant flash through flash tools gives me error.:
11/048/2017 23:48:37 - INFO - Selected Bundle for Sony Xperia M Dual(C2005). FW release : 15.5.A.1.5. Customization : DE
11/048/2017 23:48:37 - INFO - Preparing files for flashing
11/048/2017 23:48:46 - INFO - Please connect your device into flashmode.
11/048/2017 23:48:53 - INFO - Device connected in flash mode
11/048/2017 23:48:53 - INFO - Opening device for R/W
11/048/2017 23:48:53 - INFO - Reading device information
11/048/2017 23:48:53 - INFO - Phone ready for flashmode operations.
11/048/2017 23:48:53 - INFO - Opening TA partition 2
11/048/2017 23:48:53 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910S8XGK - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
11/048/2017 23:48:53 - INFO - Closing TA partition
11/048/2017 23:48:53 - INFO - Start Flashing
11/048/2017 23:48:53 - INFO - Processing loader.sin
11/048/2017 23:48:53 - INFO - Checking header
11/048/2017 23:48:53 - INFO - Flashing data
11/048/2017 23:48:54 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
11/048/2017 23:48:54 - INFO - Max packet size set to 512K
11/048/2017 23:48:54 - INFO - USB buffer size set to 512K
11/048/2017 23:48:54 - INFO - Parsing boot delivery
11/048/2017 23:48:54 - INFO - Ending flash session
11/048/2017 23:48:54 - ERROR - null
11/048/2017 23:48:54 - ERROR - Error flashing. Aborted
11/048/2017 23:48:54 - INFO - Device connected in flash mode
i cant remember if i wiped partition,system, data, dalvik or cache.
i can access twrp and install a custom rom but noting works(wifi..etc)since there is no firmware installed any more.just only a custom rom.
please help
thank you.
Click to expand...
Click to collapse
try to download other firmware from xperiafirm on flashtool, and try to reflash your rom using your new firmware. maybe that error from loader.sin like my old problem
Nicklas Van Dam said:
try to download other firmware from xperiafirm on flashtool, and try to reflash your rom using your new firmware. maybe that error from loader.sin like my old problem
Click to expand...
Click to collapse
i used 2 different roms ... C2005_15.5.A.1.5_XMD.ftf and C2005_15.5.A.1.5_DE.ftf..both give me the same error. 11/048/2017 23:48:54 - INFO - Parsing boot delivery
11/048/2017 23:48:54 - INFO - Ending flash session
11/048/2017 23:48:54 - ERROR - null
11/048/2017 23:48:54 - ERROR - Error flashing. Aborted
any ideas??:crying:
hussian said:
i used 2 different roms ... C2005_15.5.A.1.5_XMD.ftf and C2005_15.5.A.1.5_DE.ftf..both give me the same error. 11/048/2017 23:48:54 - INFO - Parsing boot delivery
11/048/2017 23:48:54 - INFO - Ending flash session
11/048/2017 23:48:54 - ERROR - null
11/048/2017 23:48:54 - ERROR - Error flashing. Aborted
any ideas??:crying:
Click to expand...
Click to collapse
can you enable debugging for flashtool? go to help tab and choose log level and choose error, after that try to reflash your firmware again and tell us what error that show up from your flashtool.
Are your device is unlocked bootloader?
Nicklas Van Dam said:
can you enable debugging for flashtool? go to help tab and choose log level and choose error, after that try to reflash your firmware again and tell us what error that show up from your flashtool.
Are your device is unlocked bootloader?
Click to expand...
Click to collapse
12/052/2017 15:52:09 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
12/052/2017 15:52:09 - INFO - Executing search strategies to find proxy selector
12/052/2017 15:52:09 - INFO - No proxy found for IE. Trying next one
12/052/2017 15:52:09 - INFO - Strategy firefox failed trying next one : No Firefox installation found
12/052/2017 15:52:09 - INFO - No proxy found for java. Trying next one
12/052/2017 15:52:09 - INFO - Syncing devices from github
12/052/2017 15:52:09 - INFO - Opening devices repository.
12/052/2017 15:52:09 - INFO - Scanning devices folder for changes.
12/052/2017 15:52:13 - INFO - Pulling changes from github.
12/052/2017 15:52:14 - INFO - Quietly closing devices repository.
12/052/2017 15:52:14 - INFO - Devices sync finished.
12/052/2017 15:52:14 - INFO - Loading devices database
12/052/2017 15:52:14 - INFO - Loaded 98 devices
12/052/2017 15:52:14 - INFO - Starting phone detection
12/052/2017 15:52:19 - INFO - Device disconnected
12/052/2017 15:52:33 - INFO - Device connected in flash mode
12/053/2017 15:53:06 - ERROR - <- This level is successfully initialized
12/053/2017 15:53:54 - ERROR - null
12/053/2017 15:53:54 - ERROR - Error flashing. Aborted
this is what i got.. yes im sure its unlocked.
oo one more thing
Nicklas Van Dam said:
can you enable debugging for flashtool? go to help tab and choose log level and choose error, after that try to reflash your firmware again and tell us what error that show up from your flashtool.
Are your device is unlocked bootloader?
Click to expand...
Click to collapse
while i was waitiing for an answer from you.i downloaded a .zip flash able rom(since i cant for some reason flash from flashtools)so it said to clear everything ..as i was formating it said e:unknown volume for path (/sd-ext).
i think maybe some thing wrong with some partition table.thats why it gives error in flashtools.
:silly::silly:
still need your help and experience.
hussian said:
12/052/2017 15:52:09 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
12/052/2017 15:52:09 - INFO - Executing search strategies to find proxy selector
12/052/2017 15:52:09 - INFO - No proxy found for IE. Trying next one
12/052/2017 15:52:09 - INFO - Strategy firefox failed trying next one : No Firefox installation found
12/052/2017 15:52:09 - INFO - No proxy found for java. Trying next one
12/052/2017 15:52:09 - INFO - Syncing devices from github
12/052/2017 15:52:09 - INFO - Opening devices repository.
12/052/2017 15:52:09 - INFO - Scanning devices folder for changes.
12/052/2017 15:52:13 - INFO - Pulling changes from github.
12/052/2017 15:52:14 - INFO - Quietly closing devices repository.
12/052/2017 15:52:14 - INFO - Devices sync finished.
12/052/2017 15:52:14 - INFO - Loading devices database
12/052/2017 15:52:14 - INFO - Loaded 98 devices
12/052/2017 15:52:14 - INFO - Starting phone detection
12/052/2017 15:52:19 - INFO - Device disconnected
12/052/2017 15:52:33 - INFO - Device connected in flash mode
12/053/2017 15:53:06 - ERROR - <- This level is successfully initialized
12/053/2017 15:53:54 - ERROR - null
12/053/2017 15:53:54 - ERROR - Error flashing. Aborted
this is what i got.. yes im sure its unlocked.
Click to expand...
Click to collapse
Nicklas Van Dam said:
can you enable debugging for flashtool? go to help tab and choose log level and choose error, after that try to reflash your firmware again and tell us what error that show up from your flashtool.
Are your device is unlocked bootloader?
Click to expand...
Click to collapse
while i was waiting for an answer from you.i downloaded a .zip flash able rom(since i cant for some reason flash from flashtools)so it said to clear everything ..as i was formating it said e:unknown volume for path (/sd-ext).
i think maybe some thing wrong with some partition table.thats why it gives error in flashtools.
:silly::silly:
still need your help and experience.
hussian said:
while i was waiting for an answer from you.i downloaded a .zip flash able rom(since i cant for some reason flash from flashtools)so it said to clear everything ..as i was formating it said e:unknown volume for path (/sd-ext).
i think maybe some thing wrong with some partition table.thats why it gives error in flashtools.
:silly::silly:
still need your help and experience.
Click to expand...
Click to collapse
what kind of recovery did you use it for format all partition? if only problem from wiped sdcard, then i think it's safe for your device to flash another custom rom. why you want to flash stock rom?, you still can access your recovery right?
anyway, your flashtool log seems not completed. can you give me your stderr.log from your flashtool installation directory? i think that log is more provide about error or warning from your flashtool when flashing is on progress.
Nicklas Van Dam said:
what kind of recovery did you use it for format all partition? if only problem from wiped sdcard, then i think it's safe for your device to flash another custom rom. why you want to flash stock rom?, you still can access your recovery right?
anyway, your flashtool log seems not completed. can you give me your stderr.log from your flashtool installation directory? i think that log is more provide about error or warning from your flashtool when flashing is on progress.
Click to expand...
Click to collapse
here is my flashtools log:
13/052/2017 17:52:50 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
13/052/2017 17:52:50 - INFO - Executing search strategies to find proxy selector
13/052/2017 17:52:50 - INFO - No proxy found for IE. Trying next one
13/052/2017 17:52:50 - INFO - Strategy firefox failed trying next one : No Firefox installation found
13/052/2017 17:52:50 - INFO - No proxy found for java. Trying next one
13/052/2017 17:52:50 - INFO - Syncing devices from github
13/052/2017 17:52:50 - INFO - Opening devices repository.
13/052/2017 17:52:50 - INFO - Scanning devices folder for changes.
13/052/2017 17:52:55 - INFO - Pulling changes from github.
13/052/2017 17:52:56 - INFO - Quietly closing devices repository.
13/052/2017 17:52:56 - INFO - Devices sync finished.
13/052/2017 17:52:56 - INFO - Loading devices database
13/052/2017 17:52:56 - INFO - Loaded 98 devices
13/052/2017 17:52:56 - INFO - Starting phone detection
13/053/2017 17:53:00 - INFO - Device disconnected
13/054/2017 17:54:08 - INFO - Selected Bundle for Sony Xperia M Dual(C2005). FW release : 15.5.A.1.5. Customization : XMD
13/054/2017 17:54:08 - INFO - Preparing files for flashing
13/054/2017 17:54:17 - INFO - Please connect your device into flashmode.
13/054/2017 17:54:23 - INFO - Device connected in flash mode
13/054/2017 17:54:23 - INFO - Opening device for R/W
13/054/2017 17:54:24 - INFO - Reading device information
13/054/2017 17:54:24 - INFO - Phone ready for flashmode operations.
13/054/2017 17:54:24 - INFO - Opening TA partition 2
13/054/2017 17:54:24 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910S8XGK - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
13/054/2017 17:54:24 - INFO - Closing TA partition
13/054/2017 17:54:24 - INFO - Start Flashing
13/054/2017 17:54:24 - INFO - Processing loader.sin
13/054/2017 17:54:24 - INFO - Checking header
13/054/2017 17:54:24 - INFO - Flashing data
13/054/2017 17:54:24 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
13/054/2017 17:54:24 - INFO - Max packet size set to 512K
13/054/2017 17:54:24 - INFO - USB buffer size set to 512K
13/054/2017 17:54:25 - INFO - Parsing boot delivery
13/054/2017 17:54:25 - INFO - Ending flash session
13/054/2017 17:54:25 - ERROR - null
13/054/2017 17:54:25 - ERROR - Error flashing. Aborted
13/054/2017 17:54:25 - INFO - Device connected in flash mode
13/054/2017 17:54:25 - INFO - Device disconnected
13/054/2017 17:54:28 - INFO - Device connected in flash mode
here is the stderr.log:
java.lang.NullPointerException
at flashsystem.X10flash.flashDevice(X10flash.java:717)
at gui.tools.FlashJob.run(FlashJob.java:44)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
i used twrp to wipe.cant remember what i wiped...
Nicklas Van Dam said:
what kind of recovery did you use it for format all partition? if only problem from wiped sdcard, then i think it's safe for your device to flash another custom rom. why you want to flash stock rom?, you still can access your recovery right?
anyway, your flashtool log seems not completed. can you give me your stderr.log from your flashtool installation directory? i think that log is more provide about error or warning from your flashtool when flashing is on progress.
Click to expand...
Click to collapse
hello sir i am waiting for a responses from you.
thank you.:good:

Repairing a corrupted boot on GT-P5210

Recently, I discovered that I had this old device in my drawers so I decided to take it out to see if I could get it running. It wasn't charging or turning on at all, so I took the back off and replaced battery and connector, nothing. So, after plugging it in to my computer, I noticed a weird device named "CLOVERVIEW", which searching that up, is usually associated with ASUS devices, which is really weird. I followed a guide to repair a dead boot, using a zip file provided here.
I put the files into the correct spots in Phone Flash Tool 4.4.4, yet I only receive an error when flashing. It appears the IFW file flashes fine, but the DnX FW does not. Log provided below.
----
06/20/23 23:13:48.280 INFO : Loading Flash file ...
06/20/23 23:13:48.280 INFO : Ready to flash!
06/20/23 23:13:49.317 INFO : Port 0/4: Start flashing BLANKPHONE flash file for
06/20/23 23:13:49.317 INFO : Port 0/4: IFW flash started - SN : CDC36BFD990D9446
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 0
06/20/23 23:13:49.361 INFO : XFSTK-STATUS Detecting Intel Device - Attempt #0
06/20/23 23:13:49.361 INFO : XFSTK-PROGRESS 5
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FW download is in progress ...
06/20/23 23:13:50.490 INFO : Port 0/4: XFSTK-PROGRESS SN: CDC36BFD990D9446 3
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Softfuses Binary absent. Please provide binary.
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 FAIL
06/20/23 23:13:50.491 INFO : Port 0/4: XFSTK-STATUS SN: CDC36BFD990D9446 Errors encounter during FW download. Aborting ...
06/20/23 23:13:50.491 INFO : Port 0/4: IFW flash success - SN : CDC36BFD990D9446
06/20/23 23:16:51.438 ERROR : Port 0/4: Device on port 0/4 timeout to enum adb (TIMEOUT = 180)
----
I'm not exactly sure what to do from here, the device still appears in Device Manager and I can't do anything about it from this point.

Categories

Resources