Welcome.
I wanted to unlock the bootloader on my Xperia with but encountered a problem when combined with flashtool'em .
Everything is done on windows 8.1 ( drivers are installed ), phone with network play , and can unlock it because the service menu says ... : YES.
system 4.4.4
I ask you to quick help .
Here you have the log:
12/025/2014 10:25:12 - INFO - < - This level is successfully initialized
12/025/2014 10:25:12 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 10:50:00 p.m.
12/025/2014 10:25:14 - INFO - Device disconnected
12/025/2014 10:25:16 - INFO - Please connect your device into flashmode .
12/026/2014 10:26:40 - INFO - Device connected in flash mode
12/026/2014 10:26:40 - INFO - Opening device for R / W
12/026/2014 10:26:41 - INFO - Processing loader
12/026/2014 10:26:54 - INFO - Checking header
12/026/2014 10:26:54 - ERROR -
12/026/2014 10:26:54 - INFO - Your phone bootloader can not be officially unlocked
12/026/2014 10:26:54 - INFO - You can now unplug and restart your phone
Try this way - How to unlock the bootloader.
Sent from my C6603 using Tapatalk
z
Czesc Krzysiek,
jak chcesz wiecej to na privie, a tak to po Angielsku
The best idea is to work it out with fastboot command, I never did this with flashtool.
Go to sony bootloader unlock site,
http://developer.sonymobile.com/unlockbootloader/
register, enter the IMEI no. you will get email with instructions - token - link with your code
power off the phone and go to folder where you have adb files - you will have to open the command line there ( shift + right click = otworz okno polecenia tutaj ),
there will a new window pop up with command line,
Take the phone, connect the usb cable to pc and phone and press power with volume down button. Blue notification led should light up - this means youre in fastboot mode,
I should mention you must have your adb drivers already installed at this stage.
When phone in fastboot, go to window with command line and type what you're got in email from sony - this should start with getvar or something,
type in exactly what is in the message,
Hit enter and wait,
You should be done in seconds.
Pzdr z iry
Filip
krzysiek0110 said:
Welcome.
I wanted to unlock the bootloader on my Xperia with but encountered a problem when combined with flashtool'em .
Everything is done on windows 8.1 ( drivers are installed ), phone with network play , and can unlock it because the service menu says ... : YES.
system 4.4.4
I ask you to quick help .
Here you have the log:
12/025/2014 10:25:12 - INFO - < - This level is successfully initialized
12/025/2014 10:25:12 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 10:50:00 p.m.
12/025/2014 10:25:14 - INFO - Device disconnected
12/025/2014 10:25:16 - INFO - Please connect your device into flashmode .
12/026/2014 10:26:40 - INFO - Device connected in flash mode
12/026/2014 10:26:40 - INFO - Opening device for R / W
12/026/2014 10:26:41 - INFO - Processing loader
12/026/2014 10:26:54 - INFO - Checking header
12/026/2014 10:26:54 - ERROR -
12/026/2014 10:26:54 - INFO - Your phone bootloader can not be officially unlocked
12/026/2014 10:26:54 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
Related
03/020/2013 21:20:22 - INFO - <- This level is successfully initialized
03/020/2013 21:20:22 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
03/020/2013 21:20:22 - INFO - libusb version 1.0.15
03/020/2013 21:20:23 - INFO - Device disconnected
03/020/2013 21:20:32 - INFO - Device connected with USB debugging off
03/020/2013 21:20:32 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/020/2013 21:20:34 - INFO - Device connected with USB debugging on
03/020/2013 21:20:34 - INFO - Connected device : Sony Xperia SP
03/020/2013 21:20:34 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
03/020/2013 21:20:34 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-perf-g1285c6c-01110-g8395f64 / Build number : 12.0.A.1.257
03/020/2013 21:20:34 - INFO - Checking root access
03/020/2013 21:20:36 - INFO - Root Access Allowed
03/021/2013 21:21:09 - INFO - Please connect your device into flashmode.
03/021/2013 21:21:15 - INFO - Device disconnected
03/021/2013 21:21:38 - INFO - Device connected in flash mode
03/021/2013 21:21:38 - INFO - Opening device for R/W
03/021/2013 21:21:40 - INFO - Device ready for R/W.
03/021/2013 21:21:40 - INFO - Reading device information
03/021/2013 21:21:40 - INFO - Unable to read from phone after having opened it.
03/021/2013 21:21:40 - INFO - trying to continue anyway
03/021/2013 21:21:40 - INFO - Processing loader
03/021/2013 21:21:47 - INFO - Checking header
03/021/2013 21:21:47 - ERROR - S1 Header checksum Error
03/021/2013 21:21:47 - INFO - Your phone bootloader cannot be officially unlocked
03/021/2013 21:21:47 - INFO - You can now unplug and restart your phone
I have successfully root my device using Doomlord easy rooting tool kit now i have installed ROM manager also.I cannot access the recovery, i think this is because i am on locked boot loader, My problem is i cant unlock my boot loader using flash tool.I cant follow windows CMD method becoz im on ubuntu. Why i cannot unlock my boot loader
Can someone help me on this issue please.
Hello everyone,
Looks like i killed my Xperia Z today.
Ive just backed up my TA and tried to Root this worked for me
but my TA must have been corrupted after reapplying TA to Device and restart the screen keeps off
What i Tried is:
Using EMMA --> Phone not recognized
Using SUS --> Phone not recognized
using Flashtool:
15/044/2013 22:44:14 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
15/044/2013 22:44:19 - INFO - Device connected with USB debugging on
15/044/2013 22:44:19 - ERROR - Cannot identify your device.
15/044/2013 22:44:19 - INFO - Selecting from user input
15/044/2013 22:44:30 - INFO - Connected device : C660X
15/044/2013 22:44:31 - INFO - Installed version of busybox : BusyBox v1.21.1-Stericson (2013-07-08 15:58:11 BST) multi-call binary.
15/044/2013 22:44:31 - INFO - Android version : 4.0.4 / kernel version : 3.1.10-cyanogenmod+ / Build number : IMM76L
15/044/2013 22:44:31 - INFO - Checking root access
15/044/2013 22:44:33 - INFO - Root access denied
15/044/2013 22:44:33 - INFO - Device connected in flash mode
when i try to Flash the Xperia i get This
15/045/2013 22:45:34 - INFO - Device connected in flash mode
15/045/2013 22:45:56 - INFO - Selected C6603 / 10.3.1.A.2.67 / CE
15/045/2013 22:45:56 - INFO - Preparing files for flashing
15/045/2013 22:45:56 - INFO - Please connect your device into flashmode.
15/045/2013 22:45:57 - INFO - Opening device for R/W
15/045/2013 22:45:57 - INFO - Reading device information
15/046/2013 22:46:17 - INFO - Unable to read from phone after having opened it.
15/046/2013 22:46:17 - INFO - trying to continue anyway
15/046/2013 22:46:17 - INFO - Start Flashing
15/046/2013 22:46:17 - INFO - Processing loader.sin
15/046/2013 22:46:17 - INFO - Checking header
15/046/2013 22:46:17 - INFO - Ending flash session
15/046/2013 22:46:17 - ERROR - Error in processHeader : 2 : Das System kann die angegebene Datei nicht finden.
15/046/2013 22:46:17 - ERROR - Error flashing. Aborted
15/046/2013 22:46:18 - INFO - Device disconnected
15/046/2013 22:46:20 - INFO - Device connected in flash mode
The problem is the flashmode reboots any 1 min no LEDs lit
under windows the xperia is shown as SEMC Flash Device
did anybody have a solution ?
thx
Doesn't seem serious, from reading the logs, try another cable, another port, one directly connected to the motherboard, not from a hub or a front shortcut.
Try reinstalling the drivers, a clean install.
Although there is the posibility of you bricking your device, since the TA part of the phone is the most sensible part of it. Give it another shot.
Hi,
always after 1 minute the phone reconnects
15/020/2013 23:20:41 - INFO - Device disconnected
15/020/2013 23:20:43 - INFO - Device connected in flash mode
15/021/2013 23:21:44 - INFO - Device disconnected
15/021/2013 23:21:47 - INFO - Device connected in flash mode
15/022/2013 23:22:47 - INFO - Device disconnected
15/022/2013 23:22:50 - INFO - Device connected in flash mode
15/023/2013 23:23:50 - INFO - Device disconnected
15/023/2013 23:23:53 - INFO - Device connected in flash mode
15/024/2013 23:24:53 - INFO - Device disconnected
15/024/2013 23:24:56 - INFO - Device connected in flash mode
Its plugged directly on my Laptop tried USB2 & 3
I was using my device unlocked for a long time, but I decided to relock, since I was not planning to install custom rom after the official 4.3 release.
But yesterday I was bored and I tried to unlock again, but I did not succeed.
Flashtool gives me the following error:
08/006/2014 17:06:13 - INFO - Please connect your device into flashmode.
08/006/2014 17:06:13 - INFO - Opening device for R/W
08/006/2014 17:06:13 - INFO - Reading device information
08/006/2014 17:06:13 - INFO - Phone ready for flashmode operations.
08/006/2014 17:06:13 - INFO - Current device : C6603 - CB5A1PVYH9 - 1270-7689_R4C - 1269-5309_10.4.B.0.569 - GLOBAL-LTE_10.4.B.0.569
08/006/2014 17:06:13 - INFO - Processing loader.sin
08/006/2014 17:06:13 - INFO - Checking header
08/006/2014 17:06:13 - INFO - Flashing data
08/006/2014 17:06:14 - INFO - Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : ROOTABLE
08/006/2014 17:06:14 - INFO - Start Reading unit 000008B2
08/006/2014 17:06:14 - INFO - Reading TA finished.
08/006/2014 17:06:14 - INFO - Ending flash session
08/006/2014 17:06:14 - INFO - Now unplug your device and restart it into fastbootmode
08/006/2014 17:06:14 - INFO - Device connected in flash mode
08/006/2014 17:06:15 - INFO - Device disconnected
08/006/2014 17:06:18 - INFO - Device connected in fastboot mode
08/006/2014 17:06:21 - INFO - Unlocking phone using key **************
08/006/2014 17:06:21 - INFO - ...
08/006/2014 17:06:21 - INFO - FAILED (remote: Command did not succeed)
08/006/2014 17:06:21 - INFO - finished. total time: 0.037s
Click to expand...
Click to collapse
But then I tried to unlock manually with fastboot.exe doing this command:
fastboot.exe -i 0x0fce oem unlock 0x**************
Click to expand...
Click to collapse
And apparently worked, I was able to flash a custom kernel
But when I restarted the phone my device was entering on flash mode automatically. Not even the sony logo was appearing.
So I re-flashed the stock rom, and now it's ok. But I want to know why I am having this problem.
Anyone knows?
__________________
About the drivers: Everything is installed ok. I am using a Windows 8 Pro and I have a Windows 7 on VMWare Player. On both I have the same problems.
I found the solution on this thread!
It's really simple actually
For those who have the same problem
Go to the folder: \Flashtool\custom\mydevices\<YOURDEVICESERIALNUMBER>\ulcode.txt
IF there's no folder inside mydevices, create one with the S/N of your XZ.
and IF there's no ulcode.txt inside <YOURDEVICESERIALNUMBER> folder, just create this file.
Now, inside the ulcode.txt, put your unlock bootloader key and save.
That's it! Go to flashtool again and try to unlock your device. It will work!
hi, i`ve tried to unlock bootloader , first i rooted it by clicking the icon of flashtool named "Root Device", and then when rooting is successfully done, i clicked the icon of flashtool named "BLU", but i didnt reboot at the end of unlocking, now i cant turn on the phone...
i really need your help, the phone is not mine, please help...
log
im using flashtool 0.9.13
Here`s the log:
31/019/2014 12:19:30 - INFO - <- This level is successfully initialized
31/019/2014 12:19:30 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
31/019/2014 12:19:35 - INFO - Device connected with USB debugging on
31/019/2014 12:19:37 - INFO - Connected device : SonyEricson X8
31/019/2014 12:19:37 - INFO - Installed version of busybox : N/A
31/019/2014 12:19:37 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/020/2014 12:20:47 - INFO - Decrypting C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue.enc to C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue
31/020/2014 12:20:58 - INFO - Pushing C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue to /data/local/tmp
31/020/2014 12:20:58 - INFO - Pushing C:\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
31/020/2014 12:20:59 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
31/021/2014 12:21:00 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
31/021/2014 12:21:02 - INFO - Running part1 of Root Exploit, please wait
31/021/2014 12:21:02 - INFO - Running rootit
31/021/2014 12:21:03 - INFO - Waiting for device. After 60secs, stop waiting will be forced
31/021/2014 12:21:04 - INFO - Device disconnected
31/021/2014 12:21:05 - INFO - Device connected with USB debugging on
31/021/2014 12:21:06 - INFO - Running part2 of Root Exploit
31/021/2014 12:21:06 - INFO - Running rootit2
31/021/2014 12:21:08 - INFO - Finished!.
31/021/2014 12:21:08 - INFO - Root should be available after reboot!
31/021/2014 12:21:08 - INFO - Device disconnected
31/021/2014 12:21:21 - INFO - Device connected with USB debugging off
31/021/2014 12:21:21 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/021/2014 12:21:24 - INFO - Device disconnected
31/021/2014 12:21:25 - INFO - Device connected with USB debugging on
31/021/2014 12:21:25 - INFO - Connected device : SonyEricson X8
31/021/2014 12:21:25 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
31/021/2014 12:21:25 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/021/2014 12:21:25 - INFO - Checking root access
31/021/2014 12:21:27 - INFO - Root Access Allowed
31/021/2014 12:21:27 - INFO - Installing toolbox to device...
31/021/2014 12:21:27 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
31/021/2014 12:21:27 - INFO - Running installftkit as root thru sysrun
31/022/2014 12:22:57 - INFO - Device disconnected
31/023/2014 12:23:01 - INFO - Device connected with USB debugging on
31/023/2014 12:23:01 - INFO - Connected device : SonyEricson X8
31/023/2014 12:23:02 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
31/023/2014 12:23:02 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
31/023/2014 12:23:02 - INFO - Checking root access
31/023/2014 12:23:04 - INFO - Root Access Allowed
31/023/2014 12:23:16 - INFO - Please connect your device into flashmode.
31/023/2014 12:23:20 - INFO - Device disconnected
31/024/2014 12:24:22 - INFO - Device connected in flash mode
31/024/2014 12:24:23 - INFO - Opening device for R/W
31/024/2014 12:24:23 - INFO - Reading device information
31/024/2014 12:24:23 - INFO - Phone ready for flashmode operations.
31/024/2014 12:24:23 - INFO - Current device : E15i - FYT0001R9J - 1241-2655_R4B - 1236-9291_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
31/024/2014 12:24:23 - INFO - Processing loader.sin
31/024/2014 12:24:23 - INFO - Checking header
31/024/2014 12:24:23 - INFO - Flashing data
31/024/2014 12:24:24 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
31/024/2014 12:24:24 - INFO - Start Reading unit 00000851
31/024/2014 12:24:24 - INFO - Reading TA finished.
31/024/2014 12:24:24 - INFO - Ending flash session
31/024/2014 12:24:24 - INFO - Waiting for device to reboot
31/024/2014 12:24:24 - INFO - Waiting for device
31/024/2014 12:24:25 - INFO - Device connected in flash mode
31/024/2014 12:24:26 - INFO - Device disconnected
31/024/2014 12:24:28 - INFO - Device connected in flash mode
31/024/2014 12:24:47 - INFO - Device connected with USB debugging off
31/024/2014 12:24:47 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/026/2014 12:26:17 - INFO - Device disconnected
31/027/2014 12:27:26 - INFO - Device connected with USB debugging on
31/027/2014 12:27:27 - INFO - Checking root access
31/027/2014 12:27:40 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\fixPart to /data/local/tmp
31/027/2014 12:27:40 - INFO - Running runfixPart as root thru sysrun
31/027/2014 12:27:41 - INFO - Successfully applied fixPart. Rebooting
31/027/2014 12:27:43 - INFO - Waiting for device
31/027/2014 12:27:43 - INFO - Device disconnected
31/027/2014 12:27:53 - INFO - Device connected with USB debugging off
31/027/2014 12:27:53 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/027/2014 12:27:59 - INFO - Device disconnected
31/028/2014 12:28:00 - INFO - Device connected with USB debugging on
31/028/2014 12:28:00 - INFO - Checking root access
31/028/2014 12:28:02 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\mapper_2.6.29.ko to /data/local/tmp
31/028/2014 12:28:02 - INFO - Pushing C:\Flashtool\devices\E15\blu\files\bootwrite_semcSL to /data/local/tmp
31/028/2014 12:28:02 - INFO - Running runbootwrite as root thru sysrun
31/028/2014 12:28:03 - INFO - Successfully applied bootwrite. Bootloader should be unlocked. Rebooting
31/028/2014 12:28:05 - INFO - Device disconnected
and here`s the log of s1tools before unlocking bootloader:
3/31/2014 10:56:54 AM Welcome to S1 identify tool
3/31/2014 10:57:02 AM
3/31/2014 10:57:02 AM TO CONNECT NEXT PHONES
3/31/2014 10:57:02 AM X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
3/31/2014 10:57:02 AM LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
3/31/2014 10:57:02 AM PRESS AND HOLD "BACK" BUTTON...
3/31/2014 10:57:02 AM
3/31/2014 10:57:02 AM PLEASE ATTACH TURNED OFF PHONE NOW
3/31/2014 10:57:02 AM
3/31/2014 10:57:49 AM
3/31/2014 10:57:49 AM RUNNING S1_EROM VER "R8A029"
3/31/2014 10:57:49 AM SOFTWARE AID: 0001
3/31/2014 10:57:49 AM LOADER AID: 0001
3/31/2014 10:57:51 AM FLASH ID: "002C/00BC"
3/31/2014 10:57:51 AM LOADER VERSION: "R4A045"
3/31/2014 10:57:51 AM
3/31/2014 10:57:51 AM MODEL (from GDFS): E15i
3/31/2014 10:57:51 AM SOFTWARE VERSION: 1236-9291_2.1.1.C.0.0
3/31/2014 10:57:51 AM CUSTOM VERSION: 1241-2655_R4B
3/31/2014 10:57:51 AM FILESYSTEM VERSION: WORLD-1-8_2.1.1.C.0.0
3/31/2014 10:57:51 AM SERIAL NO: FYT0001R9J
3/31/2014 10:57:51 AM
3/31/2014 10:57:51 AM SEMC SIMLOCK CERTIFICATE
3/31/2014 10:57:51 AM Elapsed:48 secs.
What is the manufacturing date of the x8?
cascabel said:
What is the manufacturing date of the x8?
Click to expand...
Click to collapse
i dont know, but the code is 11W44.
eefathi said:
i dont know, but the code is 11W44.
Click to expand...
Click to collapse
Does it show any sign of life at all? Try charging to a few minutes. I think it's a hard brick, but try anyway. If it doesn't work, send it to sony (serVice center).
hi
eefathi said:
i dont know, but the code is 11W44.
Click to expand...
Click to collapse
you may give a try to http://forum.xda-developers.com/showpost.php?p=27942435&postcount=206 ... if you can make it
cascabel said:
Does it show any sign of life at all? Try charging to a few minutes. I think it's a hard brick, but try anyway. If it doesn't work, send it to sony (serVice center).
Click to expand...
Click to collapse
i`ve tried to charge it with vivaz, (same battery),,, but no sign of living yet, is it the only way to fix this problem?
eefathi said:
i`ve tried to charge it with vivaz, (same battery),,, but no sign of living yet, is it the only way to fix this problem?
Click to expand...
Click to collapse
There are some shops that can fix it. You can also do it using jtag, but i haven't seen any tutorials about it. You can try google for that.
cascabel said:
There are some shops that can fix it. You can also do it using jtag, but i haven't seen any tutorials about it. You can try google for that.
Click to expand...
Click to collapse
thanx,,, looks like i gotta` kiss the friendship between me and my friend goodbye...
but i still dont understand why "S1 tool identify" software said its unlockable, because i`ve seen one site and it claimed if you see that sentence "SEMC SIMLOCK certificate", in s1tool identify`s log, you can unlock the bootloader,
eefathi said:
thanx,,, looks like i gotta` kiss the friendship between me and my friend goodbye...
but i still dont understand why "S1 tool identify" software said its unlockable, because i`ve seen one site and it claimed if you see that sentence "SEMC SIMLOCK certificate", in s1tool identify`s log, you can unlock the bootloader,
Click to expand...
Click to collapse
Well, you didn't want that to happen. Hopefully, you and you r friend can work things out. Yes s1tool will tell you that you can unlock it. Unfortunately, phones with manufacturing date above 11w28 is always a risk as far as unlocking the bootloader.
I'm at a bit of a loss on what to do right now. I had an Xperia XP (F8132) which died on me, so I got a new one with warranty replacement. I had a TWRP backup of my entire old phone, so I did an official bootloader unlock of the new F8132, and then flashed the TWRP recovery. I then tried to restore the backup of my old phone and had everything selected, though it appeared to fail, saying something about the data partition not being flashed. Anyway, I decided to reboot the phone, only to find that it would not boot.
I can not get the phone into flashboot or recovery at all. As soon as I plug the phone into a computer, it will go into flashmode (green LED), regardless of what buttons are pressed. I've tried holding down the power and volume buttons for a soft/hard reset though neither seem to do anything. The screen doesn't power on either, so I can't tell what the power level is or whether the phone is on or off. Now, when I attempt to reset the phone, there are no vibrations or any indicators.
Nothing appears to happen when I plug the phone in to charge. I think it warms up a bit, but there are no LEDs. For the past few days, the phone has simply sat on my desk doing nothing.
In short, my phone appears to be bricked, and all I get is a green LED when I plug it into the computer. I've attempted to flash a stock FTF, but it fails every time with "Processing of partition.sin finished with errors". So...any advice?
Method1 : Maybe ftf error, try another one.
Method2: relock bootloader and use Xperia™ Companion to repair.
P.S. TWRP backup cannot cross drvice to recovery the data and system.
bkk99213 said:
Method1 : Maybe ftf error, try another one.
Method2: relock bootloader and use Xperia™ Companion to repair.
P.S. TWRP backup cannot cross drvice to recovery the data and system.
Click to expand...
Click to collapse
I've tried a few things, though none have worked so far.
I've tried using two different FTF files I've downloaded, and one that I bundled using Xperifirm and Flashtool but all give the same error. It appears that flashing will fail regardless of what I exclude, and even trying kernel.sin on its own doesn't work.
I am able to unlock and relock the bootloader using Flashtool, but I get a "getphoneinfofailure" UE_302 from Xperia companion, so that doesn't seem to work either.
I think this may have happened because I renamed my old TWRP backup to match the serial of my new device to try to restore it. I probably shouldn't have done that. I'm looking at the guide to "Recover 2012 and newer XPERIAs from SOFT-brick" by Toledo_JAB, but I can't quite tell what my battery level is at the moment. The phone has no reaction whatsoever normally, and no LEDs when plugged into a charger, but will enter flashmode whenever plugged into a computer.
Can you enter fastboot mode(blue LED) or TWRP?
bkk99213 said:
Can you enter fastboot mode(blue LED) or TWRP?
Click to expand...
Click to collapse
No, I'm unable to get the screen to power on in any way, so unable to get into recovery. Strangely, fastboot does not work either. Regardless of whether the volume up, volume down, or no button is held when I plug it into the computer, I get a green LED and it is recognised as being in flash mode by Flashtool.
Unlock/Relock bootloader need fastboot mode.
So, how can you relock bootloader and use Xperia™ Companion before?
If you can relock bootloader, that mean you can enter fastboot mode.
bkk99213 said:
Unlock/Relock bootloader need fastboot mode.
So, how can you relock bootloader and use Xperia™ Companion before?
If you can relock bootloader, that mean you can enter fastboot mode.
Click to expand...
Click to collapse
I originally unlocked the bootloader in fastboot, but that was when the phone was still functional.
I relocked the bootloader using Flashtool, while my phone was in flash mode.
Relock using flashtool....
For flashtool, when you relock, you also need enter fastboot mode. So, I think, your phone can enter fastboot mode.
Or ... Have you got the log when relock using flashtool?
Maybe relock is unsuccessful.
bkk99213 said:
Relock using flashtool....
For flashtool, when you relock, you also need enter fastboot mode. So, I think, your phone can enter fastboot mode.
Or ... Have you got the log when relock using flashtool?
Maybe relock is unsuccessful.
Click to expand...
Click to collapse
The LED on my phone remains green the whole time, and it appears to be successful in relocking and unlocking.
Code:
29/018/2017 17:18:08 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
29/018/2017 17:18:08 - INFO - Executing search strategies to find proxy selector
29/018/2017 17:18:08 - INFO - No proxy found for IE. Trying next one
29/018/2017 17:18:08 - INFO - Strategy firefox failed trying next one : No Firefox installation found
29/018/2017 17:18:09 - INFO - No proxy found for java. Trying next one
29/018/2017 17:18:09 - INFO - Syncing devices from github
29/018/2017 17:18:09 - INFO - Opening devices repository.
29/018/2017 17:18:09 - INFO - Scanning devices folder for changes.
29/018/2017 17:18:38 - INFO - Pulling changes from github.
29/018/2017 17:18:41 - INFO - Quietly closing devices repository.
29/018/2017 17:18:41 - INFO - Quietly closing devices repository.
29/018/2017 17:18:41 - WARN - close() called when useCnt is already zero
29/018/2017 17:18:41 - INFO - Devices sync finished.
29/018/2017 17:18:41 - INFO - Loading devices database
29/018/2017 17:18:41 - INFO - Loaded 98 devices
29/018/2017 17:18:41 - INFO - Starting phone detection
29/018/2017 17:18:46 - INFO - Device disconnected
29/018/2017 17:18:52 - INFO - Please connect your device into flashmode.
29/019/2017 17:19:04 - INFO - Device connected in flash mode
29/019/2017 17:19:05 - INFO - Opening device for R/W
29/019/2017 17:19:05 - INFO - Reading device information
29/019/2017 17:19:05 - INFO - Phone ready for flashmode operations.
29/019/2017 17:19:05 - INFO - Opening TA partition 2
29/019/2017 17:19:05 - INFO - Current device : F8131 - CB512B2JLN - 1302-6562_R2D - 1300-5317_41.2.A.2.223 - GENERIC_41.2.A.7.8
29/019/2017 17:19:05 - INFO - Closing TA partition
29/019/2017 17:19:05 - INFO - No loader in the bundle. Searching for one
29/019/2017 17:19:05 - INFO - No matching loader found
29/019/2017 17:19:05 - WARN - No loader found or set manually. Skipping loader
29/019/2017 17:19:05 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : NOT_ROOTABLE
29/019/2017 17:19:05 - INFO - Max packet size set to 4M
29/019/2017 17:19:05 - INFO - Opening TA partition 2
29/019/2017 17:19:05 - INFO - Start Reading unit 00 00 08 B2
29/019/2017 17:19:05 - INFO - Reading TA finished.
29/019/2017 17:19:05 - INFO - Closing TA partition
29/019/2017 17:19:06 - INFO - Unlock code saved to C:\Users\_____\.flashTool\registeredDevices\CB512B2JLN\ulcode.txt
29/019/2017 17:19:12 - INFO - Relocking device
29/019/2017 17:19:12 - INFO - Opening TA partition 2
29/019/2017 17:19:12 - INFO - Writing TA unit 000008B2. Value :
29/019/2017 17:19:12 - INFO - Closing TA partition
29/019/2017 17:19:12 - INFO - Relock finished
29/019/2017 17:19:16 - INFO - Ending flash session
29/019/2017 17:19:16 - INFO - You can now unplug and restart your device
29/019/2017 17:19:16 - INFO - Device connected in flash mode
29/019/2017 17:19:17 - INFO - Device disconnected
29/019/2017 17:19:22 - INFO - Device connected in flash mode
29/019/2017 17:19:22 - INFO - Please connect your device into flashmode.
29/019/2017 17:19:23 - INFO - Opening device for R/W
29/019/2017 17:19:23 - INFO - Reading device information
29/019/2017 17:19:23 - INFO - Phone ready for flashmode operations.
29/019/2017 17:19:23 - INFO - Opening TA partition 2
29/019/2017 17:19:23 - INFO - Current device : F8131 - CB512B2JLN - 1302-6562_R2D - 1300-5317_41.2.A.2.223 - GENERIC_41.2.A.7.8
29/019/2017 17:19:23 - INFO - Closing TA partition
29/019/2017 17:19:23 - INFO - No loader in the bundle. Searching for one
29/019/2017 17:19:23 - INFO - No matching loader found
29/019/2017 17:19:23 - WARN - No loader found or set manually. Skipping loader
29/019/2017 17:19:23 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : NOT_ROOTABLE
29/019/2017 17:19:23 - INFO - Max packet size set to 4M
29/019/2017 17:19:23 - INFO - Opening TA partition 2
29/019/2017 17:19:23 - INFO - Start Reading unit 00 00 08 B2
29/019/2017 17:19:23 - INFO - Reading TA finished.
29/019/2017 17:19:23 - INFO - Closing TA partition
29/019/2017 17:19:26 - INFO - Unlocking device
29/019/2017 17:19:26 - INFO - Opening TA partition 2
29/019/2017 17:19:26 - INFO - Writing TA unit 000008B2. Value : 45 42 35 38 39 33 42 42 31 44 45 43 39 39 41 32
29/019/2017 17:19:26 - INFO - Closing TA partition
29/019/2017 17:19:27 - INFO - Unlock finished
29/019/2017 17:19:29 - INFO - Ending flash session
29/019/2017 17:19:29 - INFO - You can now unplug and restart your device
29/019/2017 17:19:29 - INFO - Device connected in flash mode
29/019/2017 17:19:30 - INFO - Device disconnected
29/019/2017 17:19:35 - INFO - Device connected in flash mode
Bootloader status : NOT_ROOTABLE???
By Google, it say NOT_ROOTABLE cannot get unlock code
Any I got mistake, I also can unlock by flashmode.
It seems this might actually be a hard brick, or close to one. It doesn't appear to be recognised by Emma, the official Sony flash tool. And it seems to come up as some sort of "SOMC Flash Device" for drivers. The s1tool and test point emergency flash for older Xperia devices would be incredibly helpful now, but it doesn't seem to support any of the newer Xperia devices. Is there anything similar for the 2016 line to recover from a hard brick?