Hey guys
Need some help as i got serius issues getting my old X10 Mini updated.
its currently running an old nAa kernel and im looking at getting the latest one and also Android 4x on it.
Im using the Kernel posted here:
http://forum.xda-developers.com/showpost.php?p=64910212&postcount=267
When trying to flash this kernel using Flashtool i get this error and the whole process is done in a few seconds.
Code:
07/005/2016 19:05:16 - INFO - Device disconnected
07/005/2016 19:05:18 - INFO - Device connected in flash mode
07/005/2016 19:05:18 - INFO - Opening device for R/W
07/005/2016 19:05:18 - INFO - Reading device information
07/005/2016 19:05:18 - INFO - Phone ready for flashmode operations.
07/005/2016 19:05:18 - INFO - Opening TA partition 2
07/005/2016 19:05:18 - INFO - Current device : E10i - CB511KABUT - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
07/005/2016 19:05:18 - INFO - Closing TA partition
07/005/2016 19:05:18 - INFO - Start Flashing
07/005/2016 19:05:18 - INFO - Using an unofficial loader
07/005/2016 19:05:18 - INFO - Processing loader_unlocked.sin
07/005/2016 19:05:18 - INFO - Checking header
07/005/2016 19:05:18 - ERROR - Processing of loader_unlocked.sin finished with errors.
07/005/2016 19:05:18 - INFO - Ending flash session
Dunno why it gives error on loader_unlocked.sin , but its getting quite frustrating.
Not that this is a daily phone or anything, i just want it up and running with the latest Android it can handle and use it as a spare phone or just to have fun with this oldie.
Apriciate any help to solve this issue as i googled for days trying to figure it out.
Adding:
Also using Win10 64Bit.
Did disable driver signature and added the driverpack.
Still the same issue
Flashtool running Degub mode
Code:
08/031/2016 12:31:45 - INFO - Device connected in flash mode
08/031/2016 12:31:45 - INFO - Opening device for R/W
08/031/2016 12:31:45 - INFO - Reading device information
08/031/2016 12:31:45 - DEBUG - Reading packet from phone
08/031/2016 12:31:45 - DEBUG - IN : CommandID : 1 / Flags : false,false,false / Data length : 46 / Data CRC32 : [B3, CC, 8A, 78]
08/031/2016 12:31:45 - DEBUG - VER="r8A029";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="4B629045635A7AE04A6E21BE32598A2E4FD5CF80";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01231200502147";MSN="CB511KABUT";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
08/031/2016 12:31:46 - DEBUG - First command reply (hook) : PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="4B629045635A7AE04A6E21BE32598A2E4FD5CF80";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01231200502147";MSN="CB511KABUT";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
08/031/2016 12:31:46 - INFO - Phone ready for flashmode operations.
08/031/2016 12:31:46 - INFO - Opening TA partition 2
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [F0, 01, 48, CC]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 4 / Data CRC32 : [62, 4B, C8, A7]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:46 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [5D, EC, A5, 43]
08/031/2016 12:31:46 - DEBUG - Reading packet from phone
08/031/2016 12:31:46 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : [5D, A9, 83, 87]
08/031/2016 12:31:46 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [46, 67, 65, F1]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 14 / Data CRC32 : [3F, 7E, 77, 5F]
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [D8, 03, F0, 52]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [6A, E6, 13, 8A]
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [DF, 6E, 34, 4B]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [3D, 5D, 5C, 6B]
08/031/2016 12:31:47 - INFO - Current device : E10i - CB511KABUT - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
08/031/2016 12:31:47 - INFO - Closing TA partition
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - DEBUG - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:47 - DEBUG - Reading packet from phone
08/031/2016 12:31:47 - DEBUG - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:47 - INFO - Start Flashing
08/031/2016 12:31:47 - INFO - Using an unofficial loader
08/031/2016 12:31:47 - INFO - Processing loader_unlocked.sin
08/031/2016 12:31:47 - INFO - Checking header
08/031/2016 12:31:47 - DEBUG - Writing packet to phone
08/031/2016 12:31:47 - ERROR - Processing of loader_unlocked.sin finished with errors.
08/031/2016 12:31:47 - INFO - Ending flash session
08/031/2016 12:31:48 - DEBUG - Writing packet to phone
08/031/2016 12:31:48 - DEBUG - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Reading packet from phone
08/031/2016 12:31:48 - DEBUG - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Writing packet to phone
08/031/2016 12:31:48 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
08/031/2016 12:31:48 - DEBUG - Reading packet from phone
i've now tried nAa's kernel for minicm7 ,9 and 10 also tried 2 diffrent phones and also a Win7 computer
same issue with loader_unlocked.sin on both computers and phones and on all 3 kernels.
Checked with s1tools and it says its unlocked as both phones has an identifier "r" and not "R"
Anyone have any idea what to try now ??
Myrmid0n said:
i've now tried nAa's kernel for minicm7 ,9 and 10 also tried 2 diffrent phones and also a Win7 computer
same issue with loader_unlocked.sin on both computers and phones and on all 3 kernels.
Checked with s1tools and it says its unlocked as both phones has an identifier "r" and not "R"
Anyone have any idea what to try now ??
Click to expand...
Click to collapse
You say in your first post that it's running an old nAa-kernel, but the output from flashtool suggests you're on the original stock firmware.
If you have flashed back to original firmware, it may have a 'locked' bootloader even though it was unlocked before (And the check says it is unlocked). Try the unlock procedure again and then try flashing a custom kernel.
SmG67 said:
You say in your first post that it's running an old nAa-kernel, but the output from flashtool suggests you're on the original stock firmware.
If you have flashed back to original firmware, it may have a 'locked' bootloader even though it was unlocked before (And the check says it is unlocked). Try the unlock procedure again and then try flashing a custom kernel.
Click to expand...
Click to collapse
Im running Minicm7 on both of them. Should be ok then or ?
Myrmid0n said:
Im running Minicm7 on both of them. Should be ok then or ?
Click to expand...
Click to collapse
The output from flashtool says you're on 2.1.1.A.0.6, which is stock firmware and not MiniCM7. Try the unlock procedure again and then try to flash a custom kernel.
SmG67 said:
The output from flashtool says you're on 2.1.1.A.0.6, which is stock firmware and not MiniCM7. Try the unlock procedure again and then try to flash a custom kernel.
Click to expand...
Click to collapse
Should i Flash stock first or just try to unlock it as is with Minicm7 on it ?
Been ages since i delt with this Phone, so i'd better find a guide again
Myrmid0n said:
Should i Flash stock first or just try to unlock it as is with Minicm7 on it ?
Been ages since i delt with this Phone, so i'd better find a guide again
Click to expand...
Click to collapse
According to flashtool it runs stock already... jus try the unlock procedure, I think flashtool can still do that for you without having to find the tutorial. See if that remedies your problems with flashing a kernel.
SmG67 said:
According to flashtool it runs stock already... jus try the unlock procedure, I think flashtool can still do that for you without having to find the tutorial. See if that remedies your problems with flashing a kernel.
Click to expand...
Click to collapse
no luck with flashtool.
dunno y its acting up. i mean,i did flash both phones ages ago with nAa kernel and MiniCM7.
So they should been unlocked allready back then or ?
Code:
11/026/2016 19:26:54 - INFO - (MainSWT.java:155) - Device connected in flash mode
11/026/2016 19:26:54 - INFO - (USBFlashWin32.java:24) - Opening device for R/W
11/026/2016 19:26:55 - INFO - (X10flash.java:1006) - Reading device information
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 1 / Flags : false,false,false / Data length : 46 / Data CRC32 : [B3, CC, 8A, 78]
11/026/2016 19:26:55 - DEBUG - (X10flash.java:1013) - VER="r8A029";DATE="20100601";TIME="12:17:00";
11/026/2016 19:26:55 - DEBUG - (X10flash.java:986) - PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="F4199098C2C4BF4E06936BBF9CF0DFF9429DA563";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01240300343741";MSN="CNBC003NUK";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
11/026/2016 19:26:55 - DEBUG - (X10flash.java:996) - First command reply (hook) : PROT_VER="01";DATE="20100601";TIME="12:17:00";VER="r8A029";UNIQUE_DEV_ID="F4199098C2C4BF4E06936BBF9CF0DFF9429DA563";CXC="1229-3593";TYPE="S1_EROM";SEC_LOCK_STATUS="LOCKED";MAN_ID="0020";DEV_ID="00BC";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";IMEI="01240300343741";MSN="CNBC003NUK";SIN_VER="0001";SIMLOCK_TAMP="TAMPERED";AID_TAMP="NOT_TAMPERED";LOADER_ROOT="S1_Loader_Root_8e35";EROM_ROOT="S1_EROM_Root_f54f";SW_ROOT="S1_SW_Root_3edc";CUST_ROOT="S1_Cust_Root_732f";SIM_LOCK_ROOT="S1_SL_Root_a640";HW_CONF_ROOT="S1_HWConf_Root_4b8c";
11/026/2016 19:26:55 - INFO - (X10flash.java:1022) - Phone ready for flashmode operations.
11/026/2016 19:26:55 - INFO - (X10flash.java:440) - Opening TA partition 2
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [F0, 01, 48, CC]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 4 / Data CRC32 : [62, 4B, C8, A7]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [5D, EC, A5, 43]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : [66, 85, B7, E5]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [46, 67, 65, F1]
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:55 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 14 / Data CRC32 : [3F, 7E, 77, 5F]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [D8, 03, F0, 52]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [6A, E6, 13, 8A]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : [DF, 6E, 34, 4B]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 12 / Flags : false,false,false / Data length : 21 / Data CRC32 : [3D, 5D, 5C, 6B]
11/026/2016 19:26:56 - INFO - (X10flash.java:589) - Current device : E10i - CNBC003NUK - 1238-0549_R10B - 1235-3408_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
11/026/2016 19:26:56 - INFO - (X10flash.java:449) - Closing TA partition
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
11/026/2016 19:26:56 - INFO - (X10flash.java:367) - Using an unofficial loader
11/026/2016 19:26:56 - INFO - (X10flash.java:323) - Processing loader_unlocked.sin
11/026/2016 19:26:56 - INFO - (X10flash.java:305) - Checking header
11/026/2016 19:26:56 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
11/026/2016 19:26:56 - ERROR - (X10flash.java:342) - Processing of loader_unlocked.sin finished with errors.
11/026/2016 19:26:56 - ERROR - (GetULCodeJob.java:136) -
11/026/2016 19:26:56 - INFO - (MainSWT.java:1313) - Your phone bootloader cannot be officially unlocked
11/026/2016 19:26:56 - INFO - (MainSWT.java:1314) - You can now unplug and restart your phone
Loaded old Emma. It says what you confirm: locked
So i'll try to get on it 2morrow and see if i can get it unlocked.
Only thing that puzzles med is: how did i manage to get nAa on it with cm7 in the first place if its locked?
Thanx a million for the help so far, will get back asap.
Btw. Should i try to get stock on it before unlocking or go ahead as is ?
Myrmid0n said:
Loaded old Emma. It says what you confirm: locked
So i'll try to get on it 2morrow and see if i can get it unlocked.
Only thing that puzzles med is: how did i manage to get nAa on it with cm7 in the first place if its locked?
Thanx a million for the help so far, will get back asap.
Btw. Should i try to get stock on it before unlocking or go ahead as is ?
Click to expand...
Click to collapse
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
SmG67 said:
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
Click to expand...
Click to collapse
Well.. im killing myself over this.
Started av fresh start today.
As SEUS is dead now i fired up PC Companion.
Restored the Phone to stock firmware again.
So now the old nAa is gone and its all official firmware and kernel.
I got superuser working as i can see it.
I run Semctools , it goes through with everything. No errors except for the standard
Protocol error when the Phone is rebooting.
Run Flashtool, choose the nAa kernel and press Flash.
Power up the Phone in flash flashmode and it gives the same error when flashing loader_unlocked.sin
I've tried running Semctools a couple more times but get the same issue with flashtool.
Also checked with s1tool which says "r" for unlocked and not "R" for locked ones
Also been looking in Sony's service menu which also says "r"
Dunno what to do anymore.
Thought Semc would unlock the bootloader, so i seriusly dunno what to try now.
Semc is this link btw
http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3
Funny, i found my brothers old X10 mini pro and i am playing around with it.
I updated the firmware using PC Companion, now i am on Firmware Version 2.1-update1, Kernel Version 2.6.29 [email protected] #1, Build Number 2.1.1.C.0.0
Then I unlocked the bootloader using msm7227_semc.cmd and it worked (checked for lowercase 'r' using S1Tool).
After that I tried to flash another kernel to install a custom rom, but i get the same error message.
I tried to flash another firmware, too. Again, the same error message.
I tried to unlock the bootloader agin, this time using FlashTool. It says it can't be done:
14/045/2016 15:45:31 - INFO - Device connected in flash mode
14/045/2016 15:45:31 - INFO - Opening device for R/W
14/045/2016 15:45:31 - INFO - Device ready for R/W.
14/045/2016 15:45:31 - INFO - Reading device information
14/045/2016 15:45:31 - INFO - Phone ready for flashmode operations.
14/045/2016 15:45:31 - INFO - Opening TA partition 2
14/045/2016 15:45:31 - INFO - Current device : U20i - CB511PC6HD - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
14/045/2016 15:45:31 - INFO - Closing TA partition
14/045/2016 15:45:31 - INFO - Using an unofficial loader
14/045/2016 15:45:31 - INFO - Processing loader_unlocked.sin
14/045/2016 15:45:31 - INFO - Checking header
14/045/2016 15:45:31 - ERROR - Processing of loader_unlocked.sin finished with errors.
14/045/2016 15:45:31 - ERROR - Error in processHeader : null
14/045/2016 15:45:31 - INFO - Your phone bootloader cannot be officially unlocked
14/045/2016 15:45:31 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
This error appers on both, windows and linux systems.
tOmAtE said:
Funny, i found my brothers old X10 mini pro and i am playing around with it.
I updated the firmware using PC Companion, now i am on Firmware Version 2.1-update1, Kernel Version 2.6.29 [email protected] #1, Build Number 2.1.1.C.0.0
Then I unlocked the bootloader using msm7227_semc.cmd and it worked (checked for lowercase 'r' using S1Tool).
After that I tried to flash another kernel to install a custom rom, but i get the same error message.
I tried to flash another firmware, too. Again, the same error message.
I tried to unlock the bootloader agin, this time using FlashTool. It says it can't be done:
This error appers on both, windows and linux systems.
Click to expand...
Click to collapse
Exactly the same issue i got... even tried to replace the loader_unlocked.sin file in flashtool with msm7227 one.
Same result...
I think i found a solution.
When i started Flashtool out of a Terminal, i noticed some Java-Error-Messages printed to the terminal.
So the problem seems to be in the program itself, not in the flashing-setup.
Using an older version of Flashtool everything worked out.
I used Version 0.9.14.0 (downloaded from here), installed the included drivers and everything worked out.
I was able to flash Firmware 2.1.1.A.0.6 and after that another Kernel and right now i am installing CM10
SmG67 said:
You may have unlocked it and put nAa-kernel and MiniCM7 on it, but you seem to have flashed stock firmware back, with the original bootloader, that's why it appears locked. Just do the unlock procedure and then flash a new kernel.
Click to expand...
Click to collapse
tOmAtE said:
I think i found a solution.
When i started Flashtool out of a Terminal, i noticed some Java-Error-Messages printed to the terminal.
So the problem seems to be in the program itself, not in the flashing-setup.
Using an older version of Flashtool everything worked out.
I used Version 0.9.14.0 (downloaded from here), installed the included drivers and everything worked out.
I was able to flash Firmware 2.1.1.A.0.6 and after that another Kernel and right now i am installing CM10
Click to expand...
Click to collapse
Superb ?
Away at work atm, but will download and try at wednesday.
Did download some old version as i suspected it could be the issue, but havent tried it yet.
Will grab the one u posted instead to make sure it works.
Got 2 x10 mini an 1 X10 to freshen up for the fun of it.
Thanx a bunch for getting back with your solution ??
Worked like a charm with the older version ?
Related
Hi.
I'm far from experienced when it comes to flashing, but I've flashed a handful of devices without any serious problems (one or two bootloops, but nothing serious). This time though my Xperia Tablet Z is in pretty bad shape and I REALLY need your help!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
Most firmware on xda are kernel only, search xda for xperia flashtool, its different from emma and should solve your problem seeing as you can still got flashmode
Run flashtool
menu devices
check update
double click relevant device
select device tab
select branding [vmo_us/ca/pr for north american]
double click version column
right click and download: will take a while to download the files, NOTE will fail on creating bundle (i think the '/' throws it off)
go to menu tools
bundle
create
source folder, navigate to where flashtool was installed, theres a folder called fimrware, sub folder downloads, sub folder sgp311_vmo_us
fill out fields (SGP311_vmo_us)
select everything and hit the > button, it will now create a firmware bundle that you can use to flash in flash mode (.ftf file should be almost 1GB in size)
press flash button in flashtool (looks like lightning)
flashmode, should default to where your bundle is, if not, source folder navigate to where bundle is
select firmware (make sure nothing is excluded, if you want to just flash kernel then excluded everything but kernel, ditto for system)
flash: WARNING THIS WILL PROBABLY WIPE YOUR DEVICE BACK TO FACTORY
Attach USB to computer, hold volume down while plugging USB into tablet, you now are in flash mode
n.b. place the tablet into flash mode last cause you only have 15 good sec before it drops out of flash mode and it takes some time for tge tool to prep the files for flashing
Try to flash a ftf that will relock your bootloader. Then flash desired firmware. It will wipe all the data present on your tablet. Your tablet will be resurrected after that..
SteelPicori said:
Most firmware on xda are kernel only, search xda for xperia flashtool, its different from emma and should solve your problem seeing as you can still got flashmode
Run flashtool
menu devices
check update
double click relevant device
select device tab
select branding [vmo_us/ca/pr for north american]
double click version column
right click and download: will take a while to download the files, NOTE will fail on creating bundle (i think the '/' throws it off)
go to menu tools
bundle
create
source folder, navigate to where flashtool was installed, theres a folder called fimrware, sub folder downloads, sub folder sgp311_vmo_us
fill out fields (SGP311_vmo_us)
select everything and hit the > button, it will now create a firmware bundle that you can use to flash in flash mode (.ftf file should be almost 1GB in size)
press flash button in flashtool (looks like lightning)
flashmode, should default to where your bundle is, if not, source folder navigate to where bundle is
select firmware (make sure nothing is excluded, if you want to just flash kernel then excluded everything but kernel, ditto for system)
flash: WARNING THIS WILL PROBABLY WIPE YOUR DEVICE BACK TO FACTORY
Attach USB to computer, hold volume down while plugging USB into tablet, you now are in flash mode
n.b. place the tablet into flash mode last cause you only have 15 good sec before it drops out of flash mode and it takes some time for tge tool to prep the files for flashing
Click to expand...
Click to collapse
Thanks for responding. Unfortunately I am getting the same kind of error with the firmware I downloaded through Flashtool according to your instructions above.
"14/016/2014 22:16:58 - ERROR - Processing of kernel.sin finished with errors.
14/016/2014 22:16:58 - INFO - Ending flash session
14/016/2014 22:16:58 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
Almost instantly after connecting my device.
jogen1980 said:
Try to flash a ftf that will relock your bootloader. Then flash desired firmware. It will wipe all the data present on your tablet. Your tablet will be resurrected after that..
Click to expand...
Click to collapse
Where do I get one of those?
tp_88 said:
Thanks for responding. Unfortunately I am getting the same kind of error with the firmware I downloaded through Flashtool according to your instructions above.
"14/016/2014 22:16:58 - ERROR - Processing of kernel.sin finished with errors.
14/016/2014 22:16:58 - INFO - Ending flash session
14/016/2014 22:16:58 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
Almost instantly after connecting my device.
Click to expand...
Click to collapse
What branding are you using, is this for SGP311, what is the size of the ftf file
its a problem with the kernel, try flashing the stock kernel you see posted in xda
did u install CM via
fastboot flash boot boot.img
fastboot flash system system.img
did you install dual recovery?
make sure bootloader is unlocked
EDIT: Tried to exclude one content after the other, and found out the following if it can help:
amss_fs_2.sin - works
amss_fs_1.sin - works
amss_fsg.sin - works
apps_log.sin - works
loader.in - works
partition-image.sin - works
b2b.sin - works (works most of the time, but fails once in a while)
cache.sin - FAILS (Has worked one time, but usually fails)
kernel.sin - FAILS
fotakernel.sin - FAILS
system.sin - FAILS
The log also says: "SGP311 - CB5A1RB3DX - 1272-8342_R2D - Unknown: Aug 14 2014/23:32:54 - GLOBAL-WIFI16G_10.5.1.A.0.283"
I'm trying to flash: "Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB"
SteelPicori said:
What branding are you using, is this for SGP311, what is the size of the ftf file
its a problem with the kernel, try flashing the stock kernel you see posted in xda
did u install CM via
fastboot flash boot boot.img
fastboot flash system system.img
did you install dual recovery?
make sure bootloader is unlocked
Click to expand...
Click to collapse
I'm guessing you're talking about the bundle, and it's: "FW release : Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB" (so yes, it's for the SGP311) | That was the only Nordic I saw in the list, so I picked that one. I now see that my device is listed as GLOBAL though, if that makes any difference?
I used this guide, but used the CM.zip för the Wifi model: http://forum.xda-developers.com/showpost.php?p=51850985&postcount=1
So I flashed the boot.img through fastboot if I remember correctly, which gave me CVM. I then wiped data/cache in CVM, and installed CM11.zip and GAPPS.zip (through CVM). No errors during installation, then dead upon reboot.
Not quite sure what you mean by dual recovery, I used CVM which I got through the boot.img in the CM11.zip.
I have tried to relock and unlock bootloader in Flashmode and it should be off. When I hit BLU it run-key say: "Relock" and the log say: "Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : ROOTED"
EDIT: The size of the tft is 0,97GB.
This is the debug-info for the part when kernel.sin fails, if that can be of any help:
14/053/2014 22:53:35 - DEBUG - Writing packet to phone
14/053/2014 22:53:35 - DEBUG - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
14/053/2014 22:53:35 - DEBUG - Reading packet from phone
14/053/2014 22:53:35 - DEBUG - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:35 - INFO - Processing kernel.sin
14/053/2014 22:53:35 - DEBUG - kernel.sin : header size : 1608
14/053/2014 22:53:35 - INFO - Checking header
14/053/2014 22:53:35 - DEBUG - Sending part 1 of 1
14/053/2014 22:53:35 - DEBUG - Writing packet to phone
14/053/2014 22:53:35 - DEBUG - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1608 / Data CRC32 : [B3, D9, 0A, 70]
14/053/2014 22:53:35 - DEBUG - Reading packet from phone
14/053/2014 22:53:35 - DEBUG - IN : CommandID : 5 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:35 - INFO - Flashing data
14/053/2014 22:53:35 - DEBUG - Number of parts to send : 16 / Part size : 524288
14/053/2014 22:53:35 - DEBUG - Sending part 1 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [BA, 13, 65, 3C]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Sending part 2 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [34, D2, 71, 38]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Sending part 3 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [F6, 5C, 35, 5A]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 7 / Flags : false,false,false / Data length : 64 / Data CRC32 : [41, 42, 40, 29]
14/053/2014 22:53:36 - ERROR - Processing of kernel.sin finished with errors.
14/053/2014 22:53:36 - INFO - Ending flash session
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
tp_88 said:
I'm guessing you're talking about the bundle, and it's: "FW release : Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB" (so yes, it's for the SGP311) | That was the only Nordic I saw in the list, so I picked that one. I now see that my device is listed as GLOBAL though, if that makes any difference?
I used this guide, but used the CM.zip för the Wifi model: http://forum.xda-developers.com/showpost.php?p=51850985&postcount=1
So I flashed the boot.img through fastboot if I remember correctly, which gave me CVM. I then wiped data/cache in CVM, and installed CM11.zip and GAPPS.zip (through CVM). No errors during installation, then dead upon reboot.
Not quite sure what you mean by dual recovery, I used CVM which I got through the boot.img in the CM11.zip.
I have tried to relock and unlock bootloader in Flashmode and it should be off. When I hit BLU it run-key say: "Relock" and the log say: "Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : ROOTED"
EDIT: The size of the tft is 0,97GB.
Click to expand...
Click to collapse
well your not going get anywhere if kernel, fotakernel and system fails
i would personally try vmo_eu4 or vmo_eu2 to see if that helps, i know NCB works on north american models cause ive flashed that on my one.
bootloader can only be unlocked via fastboot not flashmode
SteelPicori said:
bootloader can only be unlocked via fastboot not flashmode
Click to expand...
Click to collapse
My bad, I meant Flashtool. Don't remember if it was fastboot or flashmode, but you might be right. It seemed to work when I relocked it though, because SUS then recognized it (but said it couldn't fix it). After that I reverted the process with Flashtool again. And now the log says bootloader status: ROOTED and the BLU-funktion asks me if I want to Relock the device etc, so it should be unlocked.
I'm downloading the firmwares you recommended atm. Unfortunately I don't see it making any difference.
Tried VMO_EU4 now, same result (failed)
tp_88 said:
Tried VMO_EU4 now, same result (failed)
Click to expand...
Click to collapse
Same with EU2 I'm afraid. Any other suggestions?
tp_88 said:
Same with EU2 I'm afraid.
Click to expand...
Click to collapse
what operating system are you using, are you running flash or flash64, im a little stumped to be honest
try drop into fastboot mode
fastboot flash boot boot.img from AICP reboot and see if you can get into recovery
did you ever try to install twrp in the past using the adb shell?
SteelPicori said:
what operating system are you using, are you running flash or flash64, im a little stumped to be honest
try drop into fastboot mode
fastboot flash boot boot.img from AICP reboot and see if you can get into recovery
did you ever try to install twrp in the past using the adb shell?
Click to expand...
Click to collapse
Windows 8.1 Pro 64-bit. I'm running "Sony mobile flasher by Androxyde".
What's an AICP reboot?
I tried to flash the boot.img from the CM11.zip again yesterday and it said it was successful, but it didn't change anything. Still dead. Also tried to flash the CM11.zip through fastboot after that, same thing, no errors but didn't change anything. But I'll try it again in a second.
No, I haven't.
EDIT: Same thing, everything goes well in fastboot:
C:\Fastboot>fastboot flash boot boot.img
sending 'boot' (10030 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.816s
But nothing changes.
tp_88 said:
Windows 8.1 Pro 64-bit. I'm running "Sony mobile flasher by Androxyde".
What's an AICP reboot?
I tried to flash the boot.img from the CM11.zip again yesterday and it said it was successful, but it didn't change anything. Still dead. Also tried to flash the CM11.zip through fastboot after that, same thing, no errors but didn't change anything. But I'll try it again in a second.
No, I haven't.
Click to expand...
Click to collapse
if on win 8.1 64bit you need to use the flashtool64 not flashtool
aicp is android ice cream project, its a rom, uses twrp recovery rather than cwm
WELL I'LL BE DAMNED!
I turned flashed the boot.img again, turned it off and tried again and almost had a heart-attack when to screen lit up with the Sony-logo. I managed to get into recovery (CVM) aswell.
Now that I'm in recovery again, what should I do? Although I like CM11 alot I'm not too keen on trying to flash that again for obvious reasons. I have the OMNIROM-zip downloaded aswell, should I try that or what do you think?
Also, I just thought of something. I tried rooting the device with multiple different techniques, but don't think any of them actually worked, so my device might have been unrooted when I flashed CM (although with unlocked BL of course) could that have been the problem? I didn't think you needed root to flash, but like I said I'm pretty novice at this stuff.
tp_88 said:
WELL I'LL BE DAMNED!
I turned flashed the boot.img again, turned it off and tried again and almost had a heart-attack when to screen lit up with the Sony-logo. I managed to get into recovery (CVM) aswell.
Now that I'm in recovery again, what should I do? Although I like CM11 alot I'm not too keen on trying to flash that again for obvious reasons. I have the OMNIROM-zip downloaded aswell, should I try that or what do you think?
Click to expand...
Click to collapse
omni is good, aicp is based on omni, just remember to grab gapps and super user and wipe cache, dalvik and factory wipe before flashing
SteelPicori said:
omni is good, aicp is based on omni, just remember to grab gapps and super user and wipe cache, dalvik and factory wipe before flashing
Click to expand...
Click to collapse
Like I said I wasn't rooted before, can that be what caused all of this? Should I just flash SuperSU before that ROM this time?
Hi, All ... Is anyone here experienced in TA partition recovery on Xperia C4 (E5303)? Quick brief about situation:
I have rooted Xperia C4 (E5303) with locked bootloader (phone succefully rooted via Kingroot). Have backup of most important partitions, maked via dd command. But when i need to erase one of partitions from command line i make a big mistake and run somethig like this:
dd /if=/dev/zero /of=/dev/block/mmcblk0p1 (never do this with your device!) ... /dev/block/mmcblk0p1 - is a ta partition. After reboot, seems i have brick. Device won't boot in any mode. All i can do with it - it's turn it into flash mode by holding Volume Down key and insert USB cable in PC.
flashtool-0.9.19.6 and flashtool-0.9.19.10 won't flash it.
Code:
14/006/2016 08:06:41 - INFO - (X10flash.java:323) - Processing loader.sin
14/006/2016 08:06:41 - INFO - (X10flash.java:305) - Checking header
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1024 / Data CRC32 : [C9, A8, 96, 61]
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
14/006/2016 08:06:41 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 7 / Flags : false,false,false / Data length : 61 / Data CRC32 : [C1, 31, 8B, AC]
14/006/2016 08:06:41 - ERROR - (X10flash.java:342) - Processing of loader.sin finished with errors.
14/006/2016 08:06:41 - INFO - (X10flash.java:955) - Ending flash session
14/006/2016 08:06:42 - DEBUG - (USBFlashWin32.java:43) - Writing packet to phone
14/006/2016 08:06:42 - DEBUG - (USBFlashWin32.java:47) - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/006/2016 08:06:42 - DEBUG - (USBFlashWin32.java:58) - Reading packet from phone
14/006/2016 08:06:42 - DEBUG - (USBFlashWin32.java:64) - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/006/2016 08:06:42 - ERROR - (X10flash.java:780) -
14/006/2016 08:06:42 - ERROR - (X10flash.java:781) - Error flashing. Aborted
14/006/2016 08:06:42 - INFO - (MainSWT.java:155) - Device connected in flash mode
14/006/2016 08:06:42 - INFO - (MainSWT.java:151) - Device disconnected
Is any way to flash TA partition from flashmode? (i have a full backup of it) Is any way to get the phone in standart MTK preloader mode (as other MTK-based devices)?
p.s. Also i have disassembled the phone and was find a testpoint. When i short this testpoint - the new device appears in device manager with following VID & PID: USB\VID_0FCE&PID_D1D1. But there is no drivers for it. Is any info on this device? May be in this mode (after shorting testpoint) we can flash somehow any partition through VID_0FCE&PID_D1D1? Or there is no way to restore TA partition on this device and make it works?
I have the same problem with C5 (E5533), PC detects it as (VID_0FCE&PID_D1D1) and can't find any driver that matches it,
Tried to manually install Gordon's Gate, But that didn't work, It accepted the SEMC Flash Device, But still can't flash it with any tool (official or not),
I've also tried to externally charge the battery, and check for HW faults, but everything seems just fine,
FYI, Phone was working fine until it got disconnected in the middle of Flashing process with FT,
I wonder (hope) if you managed to fix yours !!
Where's the C5 test point?
Decker.Kaluga said:
p.s. Also i have disassembled the phone and was find a testpoint. When i short this testpoint -
Click to expand...
Click to collapse
Could you be more specific about how did you do the test point.
Thanks
I'm interested in this problem too. How to make the test point?
Hello friends I have a C4 model E5306 also dead with the red focus.
Can anybody help me
I was using PC companion to upgrade from 4.4.4 to the latest 5.1, but my computer crashed half way through (after reconnecting with volume up pressed). Now the phone is stuck in a boot loop, saying "the upgrade failed, please reconnect and try again'.
Pressing the reset button by the SIM tray has no effect. Connecting to PCC again just tells me to unplug and reconnect holding down volume, no change.
Connecting to Flashtool reports the device is connected in flash mode, but when I try and flash 5.1 (stock) file it says (after lots of other things which look fine):
Code:
04/014/2016 20:14:56 - INFO - (X10flash.java:533) - Start Flashing
04/014/2016 20:14:56 - INFO - (X10flash.java:275) - Processing loader.sin
04/014/2016 20:14:57 - DEBUG - (X10flash.java:276) - loader.sin : header size : 1024
04/014/2016 20:14:57 - INFO - (X10flash.java:254) - Checking header
04/014/2016 20:14:57 - DEBUG - (X10flash.java:258) - Sending part 1 of 1
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:27) - Writing packet to phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:32) - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1024 / Data CRC32 : [36, 03, 01, 69]
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:50) - Reading packet from phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:60) - IN : CommandID : 5 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:27) - Writing packet to phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:32) - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:50) - Reading packet from phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:60) - IN : CommandID : 7 / Flags : false,false,false / Data length : 64 / Data CRC32 : [D5, A2, BA, D7]
04/014/2016 20:14:57 - ERROR - (X10flash.java:290) - Processing of loader.sin finished with errors.
04/014/2016 20:14:57 - INFO - (X10flash.java:593) - Ending flash session
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:27) - Writing packet to phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:32) - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:50) - Reading packet from phone
04/014/2016 20:14:57 - DEBUG - (USBFlashLinux.java:60) - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
04/014/2016 20:14:57 - ERROR - (X10flash.java:566) -
04/014/2016 20:14:57 - ERROR - (X10flash.java:567) - Error flashing. Aborted
Is there any solution ?
update: I've made my own file using
https://www.youtube.com/watch?v=X_Y-BOWlQdw
and that is currently flashing fine..
Edit: worked fine. Flashed excluding TA, created without simlock.ta. I had to tick 'no final verification' or it gave every indication of hanging (even with debug logs on) after the large .sln is transferred.
Hi, I've been trying to flash the Customized UK 34.2.A.0.333 onto my US F5121 to get the fingerprint scanner. I'm new to all this flashing stuff so I imitated the steps from a guide on Xperiablog and got Flashtool to flash, but the entire process only took 3 minutes which seems a little too quick. I turnedo on the phone and it's still on 34.2.A.0.311 and no fingerprint scanner. I've tried different things (USB debugging and Unknown sources checked, drivers all installed, etc.) but it still doesn't seem to work. Have not unlocked bootloader or root yet. Can someone let me know what i'm doing wrong? Much appreciated!
25/046/2017 22:46:57 - INFO - (FlashJob.java:36) - Please connect your device into flashmode.
25/046/2017 22:46:58 - INFO - (USBFlashWin32.java:32) - Opening device for R/W
25/046/2017 22:46:58 - INFO - (X10flash.java:963) - Reading device information
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 1 / Flags : false,false,false / Data length : 1135 / Data CRC32 : FF 0D B9 34
25/046/2017 22:46:58 - DEBUG - (X10flash.java:970) - PROT_VER="04";VER="1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160";ID="1299-4841";FRP_PARTITION="config";TYPE="S1_LOADER";ACTIVE_COMP_AID="0004";MAX_PKT_SZ="00400000";IGNORE_CRC="HDR,DATA";DEF_SEC="ON";HWCONF_AID="0004";LOADER_AID="0004";BOOT_AID="0004";NO_SUB_SYSTEMS="0001";OTP_DATA_1="01000400";OTP_LOCK_STATUS_1="LOCKED";UNIQUE_DEV_ID_1="016B1BD5";IDCODE_1="109B00E1";SUID_1="01000000B0094130D51B6B0100000000";S1_ROOT="S1_Root_d553,S1_Root_Test_b316";MSN="CB512CX0CR";HW_CONFIG_VER="0006";HW_CONFIG_INFO="HWC_Loire_Com_009";SEC_STATE="HWC_Loire_Com_009";IMEI="35809807598345";PROD_ID="0001";GLOB_SEC="0000";PHONE_ID="0000:35809807598345";HW_CONFIG="S1_Boot:0004:0013,S1_Loader:0004:000B,S1_SW:0005:0013,S1_Cust:0004:0013,S1_ELabel:0004:0013,S1_SL:0004:0043,S1_ModemSW:0005:0013,S1_FOTA:0005:0023,S1_RIC:0005:0123,S1_ETS:0005:0013,S1_RAMETS:0005:000B,S1_RLock:0004:0223,S1_GCodes:0004:0423";AUTH_LEVEL="NONE";AUTH_MET="0001";MEMDEVS="03:00:0015:0100:000F:03A3E000:00080000:00000200";ROOTING_STATUS="ROOTABLE";PLF_ROOT_1="5D92A0231A651186849DE1939F1ADAE021D29890CDCAD71DB266CC1649B9B8DC";CARD_PRESENT="NO";S1SBL_VER="13";DEBUG_POLICY="NO";
25/046/2017 22:46:58 - DEBUG - (X10flash.java:953) - First command reply (hook) :
25/046/2017 22:46:58 - INFO - (X10flash.java:979) - Phone ready for flashmode operations.
25/046/2017 22:46:58 - INFO - (X10flash.java:424) - Opening TA partition 2
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : EE 0E 61 2C
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : F0 01 48 CC
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:58 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 12 / Flags : false,false,false / Data length : 5 / Data CRC32 : 89 41 7E 96
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : 5D EC A5 43
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : 64 D2 0E 21
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : 46 67 65 F1
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 12 / Flags : false,false,false / Data length : 13 / Data CRC32 : 9A B3 8E F3
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : D8 03 F0 52
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 12 / Flags : false,false,false / Data length : 22 / Data CRC32 : F7 23 AA 8A
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : DF 6E 34 4B
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 12 / Flags : false,false,false / Data length : 20 / Data CRC32 : 84 37 6C 85
25/046/2017 22:46:59 - INFO - (X10flash.java:575) - Current device : F5121 - CB512CX0CR - 1302-3278_R4C - 1303-0661_34.2.A.0.311 - GENERIC_34.2.A.0.311
25/046/2017 22:46:59 - INFO - (X10flash.java:433) - Closing TA partition
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/046/2017 22:46:59 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/046/2017 22:46:59 - INFO - (X10flash.java:707) - Start Flashing
25/046/2017 22:46:59 - INFO - (X10flash.java:359) - No loader in the bundle. Searching for one
25/046/2017 22:46:59 - INFO - (X10flash.java:364) - No matching loader found
25/046/2017 22:46:59 - WARN - (X10flash.java:377) - No loader found or set manually. Skipping loader
25/046/2017 22:46:59 - DEBUG - (X10flash.java:949) - After loader command reply (hook) :
25/046/2017 22:46:59 - INFO - (X10flash.java:950) - Loader : S1_Root_d553 - Version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Boot version : 1299-4841_S1_Boot_MSM8956_LA1.0.1_N_160 / Bootloader status : ROOTABLE
25/046/2017 22:46:59 - INFO - (X10flash.java:387) - Max packet size set to 4M
25/046/2017 22:46:59 - INFO - (X10flash.java:397) - USB buffer size set to 512K
25/047/2017 22:47:02 - INFO - (X10flash.java:442) - Parsing boot delivery
25/047/2017 22:47:03 - INFO - (X10flash.java:722) - No flash script found.
25/047/2017 22:47:03 - INFO - (X10flash.java:723) - Flash script is mandatory. Closing session
25/047/2017 22:47:03 - INFO - (X10flash.java:916) - Ending flash session
25/047/2017 22:47:03 - DEBUG - (USBFlashWin32.java:51) - Writing packet to phone
25/047/2017 22:47:03 - DEBUG - (USBFlashWin32.java:69) - OUT : CommandID : 4 / Flags : false,true,false / Data length : 1 / Data CRC32 : 77 07 30 96
25/047/2017 22:47:03 - DEBUG - (USBFlashWin32.java:80) - Reading packet from phone
25/047/2017 22:47:03 - DEBUG - (USBFlashWin32.java:86) - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/047/2017 22:47:03 - INFO - (X10flash.java:727) - Flashing finished.
25/047/2017 22:47:03 - INFO - (X10flash.java:728) - Please unplug and start your phone
25/047/2017 22:47:03 - INFO - (X10flash.java:729) - For flashtool, Unknown Sources and Debugging must be checked in phone settings
25/047/2017 22:47:03 - INFO - (MainSWT.java:158) - Device connected in flash mode
25/047/2017 22:47:09 - INFO - (MainSWT.java:154) - Device disconnected
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-x/help/unable-to-update-to-customized-34-2-0-t3580948
Please go through the above post, its seems like an error with flash script like I had!
You can also try this link from XperiaBlog. I just bought one from Amazon US and flashed the Russia Generic version. Everything works fine for me including fingerprint scanner
munjeni, good obvervation, the device I am trying to unbrick is indeed not a z1c but a Xperia Go ST27i. So here is the right place to try to unbrick it and not there: https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-t3657384/page115
munjeni said:
Hey wait. It might be that you using wrong firmware which is not for your device model. I see in your xflasher.bat prcmu.sin, never saw something like that for z1c, which is indication that you have an firmware not for z1c? Can you post more details about firmware you downloaded, and can you tell me your device model?
Click to expand...
Click to collapse
So the device is an Xperia Go ST27i and the firmware I am using is "ST27i_6.2.A.1.100_1264_7472.ftf"
Today I tried a different driver for flashing, one I found in an S1tool package. Now the device name is no longer "S1Boot Download" but "SEMC Flash Device". Now there seems to work more but still it is not flashing correctly. The results in flashtool:
Code:
25/031/2018 19:31:10 - DEBUG - Creating bundle from ftf file : H:\ST27i_6.2.A.1.100_1264_7472.ftf
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : loader.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : kernel.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : system.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : fotakernel.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : modemfs.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : partition-image.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : simlock.ta
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : prcmu.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : apps_log.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : modem.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : userdata.sin
25/031/2018 19:31:10 - DEBUG - Added this entry to the bundle list : cache.sin
25/031/2018 19:31:17 - INFO - Selected Bundle for Sony Xperia GO(ST27i). FW release : 6.2.A.1.100. Customization : 1264-7472
25/031/2018 19:31:17 - INFO - Preparing files for flashing
25/031/2018 19:31:17 - DEBUG - Created the prepared folder
25/031/2018 19:31:17 - DEBUG - Saving entry cache.sin to disk
25/031/2018 19:31:17 - DEBUG - Streaming from jar entry : cache.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\cache.sin
25/031/2018 19:31:18 - DEBUG - Saving entry fotakernel.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : fotakernel.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\fotakernel.sin
25/031/2018 19:31:18 - DEBUG - Saving entry kernel.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : kernel.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\kernel.sin
25/031/2018 19:31:18 - DEBUG - Saving entry modem.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : modem.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\modem.sin
25/031/2018 19:31:18 - DEBUG - Saving entry modemfs.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : modemfs.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\modemfs.sin
25/031/2018 19:31:18 - DEBUG - Saving entry partition-image.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : partition-image.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\partition-image.sin
25/031/2018 19:31:18 - DEBUG - Saving entry prcmu.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : prcmu.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\prcmu.sin
25/031/2018 19:31:18 - DEBUG - Saving entry system.sin to disk
25/031/2018 19:31:18 - DEBUG - Streaming from jar entry : system.sin
25/031/2018 19:31:18 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\system.sin
25/031/2018 19:31:30 - DEBUG - Saving entry loader.sin to disk
25/031/2018 19:31:30 - DEBUG - Streaming from jar entry : loader.sin
25/031/2018 19:31:30 - DEBUG - Writing Entry to C:\Users\Bernhard\.flashTool\firmwares\prepared\loader.sin
25/031/2018 19:31:30 - INFO - Please connect your device into flashmode.
25/036/2018 19:36:04 - INFO - Device connected in flash mode
25/036/2018 19:36:04 - INFO - Opening device for R/W
25/036/2018 19:36:04 - INFO - Reading device information
25/036/2018 19:36:04 - DEBUG - Reading packet from phone
25/036/2018 19:36:04 - DEBUG - IN : CommandID : 1 / Flags : false,false,false / Data length : 82 / Data CRC32 : 25 19 83 58
25/036/2018 19:36:04 - DEBUG - PROT_VER="04";ID="1240-4128";VER="R10E013";TYPE="S1_BOOT";ACTIVE_COMP_AID="0001";
25/036/2018 19:36:04 - DEBUG - First command reply (hook) :
25/036/2018 19:36:04 - INFO - Phone ready for flashmode operations.
25/036/2018 19:36:04 - INFO - Opening TA partition 2
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : EE 0E 61 2C
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : F0 01 48 CC
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 29 / Data CRC32 : F4 B2 2F 68
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : 5D EC A5 43
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 10 / Data CRC32 : 50 3C 3A 62
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : 46 67 65 F1
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 29 / Data CRC32 : F4 B2 2F 68
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : D8 03 F0 52
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 29 / Data CRC32 : F4 B2 2F 68
25/036/2018 19:36:05 - DEBUG - Writing packet to phone
25/036/2018 19:36:05 - DEBUG - OUT : CommandID : 12 / Flags : false,true,false / Data length : 4 / Data CRC32 : DF 6E 34 4B
25/036/2018 19:36:05 - DEBUG - Reading packet from phone
25/036/2018 19:36:05 - DEBUG - IN : CommandID : 12 / Flags : false,false,false / Data length : 29 / Data CRC32 : F4 B2 2F 68
25/036/2018 19:36:05 - INFO - Current device : Unknown: Mar 28 2013/20:01:29 - YT9105QUMF - Unknown: Mar 28 2013/20:01:29 - Unknown: Mar 28 2013/20:01:29 - Unknown: Mar 28 2013/20:01:29
25/036/2018 19:36:05 - INFO - Closing TA partition
25/036/2018 19:36:06 - DEBUG - Writing packet to phone
25/036/2018 19:36:06 - DEBUG - OUT : CommandID : 10 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:06 - DEBUG - Reading packet from phone
25/036/2018 19:36:06 - DEBUG - IN : CommandID : 10 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:06 - INFO - Start Flashing
25/036/2018 19:36:06 - INFO - Processing loader.sin
25/036/2018 19:36:06 - INFO - Checking header
25/036/2018 19:36:06 - DEBUG - Writing packet to phone
25/036/2018 19:36:06 - DEBUG - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1020 / Data CRC32 : 97 FE FC 54
25/036/2018 19:36:06 - DEBUG - Reading packet from phone
25/036/2018 19:36:06 - DEBUG - IN : CommandID : 5 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:06 - INFO - Flashing data
25/036/2018 19:36:06 - DEBUG - Number of parts to send : 2 / Part size : 65536
25/036/2018 19:36:06 - DEBUG - Sending part 1 of 2
25/036/2018 19:36:06 - DEBUG - Writing packet to phone
25/036/2018 19:36:06 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : CB 68 A2 19
25/036/2018 19:36:06 - DEBUG - Reading packet from phone
25/036/2018 19:36:06 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:06 - DEBUG - Sending part 2 of 2
25/036/2018 19:36:06 - DEBUG - Writing packet to phone
25/036/2018 19:36:06 - DEBUG - OUT : CommandID : 6 / Flags : false,true,false / Data length : 34284 / Data CRC32 : 5A 5C DC 51
25/036/2018 19:36:06 - DEBUG - Reading packet from phone
25/036/2018 19:36:06 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:06 - DEBUG - Reading packet from phone
25/036/2018 19:36:07 - DEBUG - IN : CommandID : 1 / Flags : false,false,false / Data length : 845 / Data CRC32 : 4D FF 8A F9
25/036/2018 19:36:07 - DEBUG - Writing packet to phone
25/036/2018 19:36:07 - DEBUG - OUT : CommandID : 1 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:07 - DEBUG - Reading packet from phone
25/036/2018 19:36:07 - DEBUG - IN : CommandID : 1 / Flags : false,false,false / Data length : 845 / Data CRC32 : 4D FF 8A F9
25/036/2018 19:36:07 - DEBUG - PROT_VER="04";VER="R5E006";ID="1240-4121";TYPE="S1_LOADER";NO_SUB_SYSTEMS="0001";UNIQUE_DEV_ID_1="C1FA2EFC539644687FDC6A8C48FF93C71C063491";OTP_DATA_1="030000000000000001000100010001002D48494444454E444154412D1DCC80D7";OTP_LOCK_STATUS_1="LOCKED";IDCODE_1="8500";BOOT_AID="0001";LOADER_AID="0001";HWCONF_AID="0001";ACTIVE_COMP_AID="0001";MEMDEVS="03:00:0045:0000:0090:00ECC000:00080000:00000200";RAM_INFO="FF000018";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";DEF_SEC="ON";CARD_PRESENT="NO";S1_ROOT="S1_Root_3065,S1_Root_Test_ddab";HW_CONFIG_VER="0005";HW_CONFIG_INFO="R5A";HW_CONFIG="S1_Boot:0001:0013,S1_Loader:0001:000B,S1_SW:0002:0013,S1_Cust:0001:0013,S1_SL:0001:0043,S1_ModemSW:0002:0013,S1_FOTA:0002:002B,S1_ETS:0002:0013,S1_RAMETS:0002:000B";IMEI="35511305333163";PHONE_ID="0000:35511305333163";PROD_ID="0000";GLOB_SEC="0000";
25/036/2018 19:36:07 - DEBUG - After loader command reply (hook) : PROT_VER="04";VER="R5E006";ID="1240-4121";TYPE="S1_LOADER";NO_SUB_SYSTEMS="0001";UNIQUE_DEV_ID_1="C1FA2EFC539644687FDC6A8C48FF93C71C063491";OTP_DATA_1="030000000000000001000100010001002D48494444454E444154412D1DCC80D7";OTP_LOCK_STATUS_1="LOCKED";IDCODE_1="8500";BOOT_AID="0001";LOADER_AID="0001";HWCONF_AID="0001";ACTIVE_COMP_AID="0001";MEMDEVS="03:00:0045:0000:0090:00ECC000:00080000:00000200";RAM_INFO="FF000018";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";DEF_SEC="ON";CARD_PRESENT="NO";S1_ROOT="S1_Root_3065,S1_Root_Test_ddab";HW_CONFIG_VER="0005";HW_CONFIG_INFO="R5A";HW_CONFIG="S1_Boot:0001:0013,S1_Loader:0001:000B,S1_SW:0002:0013,S1_Cust:0001:0013,S1_SL:0001:0043,S1_ModemSW:0002:0013,S1_FOTA:0002:002B,S1_ETS:0002:0013,S1_RAMETS:0002:000B";IMEI="35511305333163";PHONE_ID="0000:35511305333163";PROD_ID="0000";GLOB_SEC="0000";
25/036/2018 19:36:07 - INFO - Loader : S1_Root_3065 - Version : R5E006 / Boot version : R10E013 / Bootloader status : UNROOTABLE
25/036/2018 19:36:07 - INFO - Max packet size set to 64K
25/036/2018 19:36:07 - INFO - USB buffer size set to 512K
25/036/2018 19:36:08 - INFO - Ending flash session
25/036/2018 19:36:08 - DEBUG - Writing packet to phone
25/036/2018 19:36:08 - DEBUG - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:08 - DEBUG - Reading packet from phone
25/036/2018 19:36:08 - DEBUG - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : 00 00 00 00
25/036/2018 19:36:08 - ERROR - null
25/036/2018 19:36:08 - ERROR - Error flashing. Aborted
The log of xflasher:
Code:
-------------------------------------------------------
Xperia Command Line Flasher v23
by Munjeni @ 2014,2017
-------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_adde#5&345d8d38&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&345D8D38&0&6
- Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 00 00 00 01 00 00 00 01 00 00 00 52 59 ...........RY
- Successfully read 0x52 bytes from handle.
Raw input [0x52]:
00000000 50 52 4F 54 5F 56 45 52 3D 22 30 34 22 3B 49 44 PROT_VER="04";ID
00000010 3D 22 31 32 34 30 2D 34 31 32 38 22 3B 56 45 52 ="1240-4128";VER
00000020 3D 22 52 31 30 45 30 31 33 22 3B 54 59 50 45 3D ="R10E013";TYPE=
00000030 22 53 31 5F 42 4F 4F 54 22 3B 41 43 54 49 56 45 "S1_BOOT";ACTIVE
00000040 5F 43 4F 4D 50 5F 41 49 44 3D 22 30 30 30 31 22 _COMP_AID="0001"
00000050 3B 00 ;.
Can't get MAX_PKT_SZ!
-------------------------------------------------------
Xperia Command Line Flasher v23
by Munjeni @ 2014,2017
-------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_adde#5&345d8d38&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controller
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&345D8D38&0&6
Error: file is not a sin!?
Error uploading partition-image.sin!
S1tool says:
Code:
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_BOOT VER "R10E013"
SIMLOCK STATE: "TAMPERED"
LOADER AID: 0001
hash not supported []
Is there something I could try next? Thanks!
I'm out of ideas why this happening. And I have no idea what you have done before brick, you might write some more details. Did you done something to partitions? To trim area? I can see your device is locked and unrootable which mean you can use sony pc companion software to repair your phone. If that not help I realy have no idea what you might try next sorry. Your recovery is working? Android is working? Fastboot boot recovery.img booting recovery? Or your device is completely bricked?
Companion says, cannot fix device because bootloader is unlocked...
Unfortunately I do not remember everything I tried with the phone, because I last had it in my hands about a year ago...
Recovery is not working. The screen remains black in all modes. Only vibra and the LED is working...
I tried:
Code:
fastboot boot twrp-3.1.1-0-lotus.img
creating boot image...
creating boot image - 8765440 bytes
downloading 'boot.img'...
(bootloader) USB download speed was 16987kB/s
OKAY [ 0.626s]
booting...
FAILED (remote: Wrong range:0x10008000-0x1086303a. Ok:0x00000000-0x05efffff)
finished. total time: 0.628s
But this line from your log tells me that your bootloader is not unlocked:
25/036/2018 19:36:07 - INFO - Loader : S1_Root_3065 - Version : R5E006 / Boot version : R10E013 / Bootloader status : UNROOTABLE
How you unlocked your bootloader when it was with otp lock: locked? This unrootable status is also strange. Did you tried to flash recovery to the boot partition (fastboot flash boot recovery.img)? If you can't boot recovery after that, in that case I'm beliving that your trim area is broken, did you touched your trim area? Restored wrong trim area backup? Restored backup not from your phone? Thats just some questions to maybe remind about what maybe you done before brick.
---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------
You didn't used xflasher right! By your log I see you have skeep loader.sin file, loader sin file must be first! See readme file!
Today a miracle happened!! Suddenly I was able to flash recovery with "fastboot flash boot twrp-3.1.1-0-lotus.img"!! I don't know why, but suddenly it worked. And then I was able to flash this ROM via the zip file.
So I am having a working phone again now!! But... I cannot boot into recovery anymore now... I guess the reason is that I do not have a recovery partition but only boot partition and I had to flash recovery to boot partition. "fastboot flash recovery twrp-3.1.1-0-lotus.img" does not work, "(bootloader) Flash of partition 'recovery' requested" "FAILED (remote: partition not found)"...
Is there a solution to this?
And why do I not have root access in this ROM? I thought root access is automatic in every custom ROM?
swissly said:
Today a miracle happened!! Suddenly I was able to flash recovery with "fastboot flash boot twrp-3.1.1-0-lotus.img"!! I don't know why, but suddenly it worked. And then I was able to flash this ROM via the zip file.
So I am having a working phone again now!! But... I cannot boot into recovery anymore now... I guess the reason is that I do not have a recovery partition but only boot partition and I had to flash recovery to boot partition. "fastboot flash recovery twrp-3.1.1-0-lotus.img" does not work, "(bootloader) Flash of partition 'recovery' requested" "FAILED (remote: partition not found)"...
Is there a solution to this?
And why do I not have root access in this ROM? I thought root access is automatic in every custom ROM?
Click to expand...
Click to collapse
Don't know realy, I had xGo 3 years ago and forgot almost everything about that phone. About root on Lineage you need to install SuperSu