Database Develop

[Q] My XZ don't unlock after relock

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!

[Q] xperia v bootloop-problems with bootloader-fastboot

Hello and good day.
i hope i can find here some help.
SHORT FACTS AT THE END OF THE POST
my phone went to bootloop after i applyed a backup i made with titanium backup.
sadly, i also restored all system files and my phone went to bootloop when i restarted.
xperia v lt25i with fastboot installed and the bootloader is unlocked.
so as much as i know connecting it to the pc pressing the volume button down the green light goes on and it should be the fastboot mode.
pressing the volume button up and the light goes blue should be the bootloader.
the problem is the phone only stays for 2 secounds in this mode and then going into the battery load mode.
this leaves not much time to install the device drivers on the PC (windows vista)
i managed to install the fastboot driver and now the phone stays +30 secounds in fastboot mode and switches then into the battery mode.
if i try to install the bootloader drivers for the device, he tryes but aborts the install saying "wrong parameter".
during the install he switches from the bootloader into the battery mode.
i installed the android sdk, flashtool(sony mobile flasher), universal adb driver, sony update service,sony pc companion.
sony updateservice says the OS is modified and refuses to update.
the sony pc companion repair function only seems to work with a started phone.
also i somehow manage to get the update/repair function started but it suddenly closes when it downloads/prepares the operation.
connected with active bootloop to the pc he finds the LT25i and wants to install the drivers "sony sa0106 ADB driver interface" but aborts with the reason "wrong parameter"
I had this too before i puted my phone into bootloop.
seems normal coz sony pc companion needs to install the drivers on its own.
when i go into the fastboot mode and open the sony mobile flasher, select in the fastboot toolbox to check the current device status he isnt doing anything.
in the android sdk using the fasstboot tool over the console he shows nothing when giving the "fastboot devices" command.
with "fastboot update" or "fastboot continue" he says "waiting for device" but gets stuck in it.
please if you have any advice what i can do or try or even a solution on my problem let me know.
i would be very happy to solve this problem.
-----
iam a total noob when it comes to programing but 4 days ago i succesfully repaired the phone with a broken touch-lcd screen.
so if a possible solution requires a hardware mod-hack i have good experiance with even soldering smd components with a solder-needle.
LONG SHORT :
bootloop
Bootloader driver doesnt install on the PC.
Fastboot seems to give no response to commands.(in the windows device manager the device is installed as "SEMC flash device")
EDIT:Still trying to get the driver for the flashmode installed with the error "wrong parameter".
may seems to be a windows problem, maybe caused by old driver garbage but i have no solutuion.
How do i get the phone operational again?
Thank you for your time.

First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack

thanks for your reply
nlooooo said:
First download Flashtool it has required drivers installed. To use Sony Update Service and PC Companion you need to relock bootloader. Forget about hardware hack
Click to expand...
Click to collapse
i deleted some drivers and reinstalled flashtool and the flashtool driverpack.
the s1bootloader or fastboot is now listed in the devicemanager as SEMC flashdevice.
flashtool recognizes the phone in flashmode but gets disconnected after +-40 secounds and then reconnects.
strangely....he now is performing the flash operation.
reading and writing data to the phone or at least trying to do the operation.
the phone is now connected without battery and is off.
no lights on and the screen is dark.
i will wait for the operation to complet.
is this normal??
is it flashing now? or can i abort the operation?
28/035/2014 20:35:22 - INFO - (MainSWT.java:130) - Device connected in flash mode
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\LT25i_9.2.A.1.210_1270-7096_R2J Customized SG.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : system.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : fotakernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_2.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cust-reset.ta
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fs_1.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : partition-image.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : apps_log.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : tzbsp.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : amss_fsg.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : userdata.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : cache.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:76) - Creating bundle from ftf file : C:\Flashtool\firmwares\X10_V1_BLRelock.ftf
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : kernel.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : loader.sin
28/035/2014 20:35:37 - DEBUG - (Bundle.java:92) - Added this entry to the bundle list : s1boot.sin
28/035/2014 20:35:39 - INFO - (MainSWT.java:1020) - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/035/2014 20:35:39 - INFO - (Bundle.java:406) - Preparing files for flashing
28/035/2014 20:35:39 - DEBUG - (Bundle.java:416) - Created the prepared folder
28/035/2014 20:35:39 - DEBUG - (Bundle.java:325) - Saving entry system.sin to disk
28/035/2014 20:35:39 - DEBUG - (BundleEntry.java:41) - Streaming from jar entry : system.sin
28/035/2014 20:35:39 - DEBUG - (Bundle.java:329) - Writing Entry to .\firmwares\prepared\system.sin
28/036/2014 20:36:04 - INFO - (MainSWT.java:126) - Device disconnected
28/036/2014 20:36:08 - INFO - (MainSWT.java:130) - Device connected in flash mode
It broke the operation -.-
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [09, 58, 2F, 8D]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2777 of 16305
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [1F, A6, 11, 1C]
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:38 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:38 - DEBUG - (X10flash.java:244) - Sending part 2778 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [C5, B5, C2, 78]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2779 of 16305
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:40) - OUT : CommandID : 6 / Flags : false,true,true / Data length : 65536 / Data CRC32 : [08, 8D, FE, AE]
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/046/2014 20:46:39 - DEBUG - (USBFlashWin32.java:61) - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
28/046/2014 20:46:39 - DEBUG - (X10flash.java:244) - Sending part 2780 of 16305
28/046/2014 20:46:39 - DEBUG - (MyLogger.java:100) - <- This level is successfully initialized
28/046/2014 20:46:39 - INFO - <- This level is successfully initialized
28/047/2014 20:47:27 - ERROR - Processing of system.sin finished with errors.
28/047/2014 20:47:27 - INFO - Ending flash session
28/047/2014 20:47:27 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
when connected clicking on BLU the bootloader unlock he manages to read some stats
28/052/2014 20:52:57 - INFO - Device connected in flash mode
28/053/2014 20:53:09 - INFO - Please connect your device into flashmode.
28/053/2014 20:53:10 - INFO - Opening device for R/W
28/053/2014 20:53:10 - INFO - Reading device information
28/053/2014 20:53:10 - INFO - Phone ready for flashmode operations.
28/053/2014 20:53:10 - INFO - Current device : LT25i - BX903HDWG2 - 1268-5967_R4I - 1264-2336_9.1.A.1.140 - GLOBAL-LTE_9.1.A.1.140
28/053/2014 20:53:10 - INFO - Processing loader.sin
28/053/2014 20:53:10 - INFO - Checking header
28/053/2014 20:53:10 - INFO - Flashing data
28/053/2014 20:53:10 - INFO - Processing of loader.sin finished.
28/053/2014 20:53:15 - INFO - Loader : S1_Root_7054 - Version : R5A058 / Boot version : R11A023 / Bootloader status : ROOTED
28/053/2014 20:53:15 - INFO - Start Reading unit 000008B2
28/053/2014 20:53:15 - INFO - Reading TA finished.
28/053/2014 20:53:15 - INFO - Unlock code saved to C:\Flashtool\custom\mydevices\BX903HDWG2\ulcode.txt
28/053/2014 20:53:17 - INFO - Ending flash session
28/053/2014 20:53:17 - INFO - You can now unplug and restart your device
28/053/2014 20:53:17 - INFO - Device connected in flash mode
28/053/2014 20:53:18 - INFO - Device disconnected
28/053/2014 20:53:20 - INFO - Device connected in flash mode
but then again disconnects.
...all the time.
is it maybe a windows problem?
what can i try or do?

I'm not sure what you have done but this is the correct procedure:
- First of all copy downloaded ftf file to folder c:\Program Files (x86)\Flashtool\firmwares\
- Start flashtool without phone connected to PC.
- Click on thunder icon.
- Choose Flashmode in given list.
- In next window (Firmware selector) choose ftf file you copied to firmware folder, tick to wipe all given options (APPSLOG, CACHE, DATA) and tick 'No final verification.
- Click on Flash and wait for files to be prepared.
- When dialog box appear connect your phone (powered off) to USB cable holding volume down.
- Green led with appear for moment and then it will go off.
- Wait for the process to be finished.

yes yes
he goes into flashmode and so on but after +- 40 secounds he automaticly exits the flashmode the sony sign appears on the screen and the green lamp goes off then starting again in flashmode.
so he periodicaly disconnects the phone and reconnects.
it doesnt matter if i touch the phone or not, so it isnt a broken cable problem.
28/047/2014 21:47:34 - INFO - Device disconnected
28/048/2014 21:48:19 - INFO - Selected Bundle for LT25i. FW release : 9.2.A.1.210. Customization : 1270-7096_R2J Customised SG
28/048/2014 21:48:19 - INFO - Preparing files for flashing
28/048/2014 21:48:28 - INFO - Device connected in flash mode
28/048/2014 21:48:53 - INFO - Please connect your device into flashmode.
28/048/2014 21:48:54 - INFO - Opening device for R/W
28/048/2014 21:48:54 - INFO - Reading device information
28/049/2014 21:49:10 - INFO - Unable to read from phone after having opened it.
28/049/2014 21:49:10 - INFO - trying to continue anyway
28/049/2014 21:49:10 - INFO - Start Flashing
28/049/2014 21:49:10 - INFO - Processing loader.sin
28/049/2014 21:49:10 - INFO - Checking header
28/049/2014 21:49:11 - ERROR - Processing of loader.sin finished with errors.
28/049/2014 21:49:11 - INFO - Ending flash session
28/049/2014 21:49:11 - ERROR - Error in processHeader : 995 : Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.
28/049/2014 21:49:11 - ERROR - Error flashing. Aborted
28/049/2014 21:49:11 - INFO - Device disconnected

Have you tried with Sony Update Service now when you have drivers installed?

28/004/2014 22:04:41 - INFO - Processing of apps_log.sin finished.
28/004/2014 22:04:41 - INFO - Processing cache.sin
28/004/2014 22:04:41 - INFO - Checking header
28/004/2014 22:04:41 - INFO - Flashing data
28/004/2014 22:04:42 - INFO - Processing of cache.sin finished.
28/004/2014 22:04:42 - INFO - Processing system.sin
28/004/2014 22:04:42 - INFO - Checking header
28/004/2014 22:04:42 - INFO - Flashing data
28/005/2014 22:05:09 - ERROR - Processing of system.sin finished with errors.
28/005/2014 22:05:09 - INFO - Ending flash session
28/005/2014 22:05:09 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
Sony update service says the device contains modified data for which no update is available.
is there a tool with which i can read the phone operations?
during the flash operation when the phone is off it suddenly switches back on, as i said showing the sony logo on the screen.
interessting after the last try to flash he now stays in the flashmode and now for over 5 mins.
i tried again but he stoped showing this :
28/015/2014 22:15:45 - INFO - (FlashJob.java:33) - Please connect your device into flashmode.
28/015/2014 22:15:46 - INFO - (USBFlashWin32.java:16) - Opening device for R/W
28/015/2014 22:15:46 - INFO - (X10flash.java:594) - Reading device information
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:51) - Reading packet from phone
28/015/2014 22:15:46 - INFO - (X10flash.java:606) - Unable to read from phone after having opened it.
28/015/2014 22:15:46 - INFO - (X10flash.java:607) - trying to continue anyway
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - INFO - (X10flash.java:484) - Start Flashing
28/015/2014 22:15:46 - INFO - (X10flash.java:237) - Processing loader.sin
28/015/2014 22:15:46 - DEBUG - (X10flash.java:238) - loader.sin : header size : 1020
28/015/2014 22:15:46 - INFO - (X10flash.java:216) - Checking header
28/015/2014 22:15:46 - DEBUG - (X10flash.java:220) - Sending part 1 of 1
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:252) - Processing of loader.sin finished with errors.
28/015/2014 22:15:46 - INFO - (X10flash.java:544) - Ending flash session
28/015/2014 22:15:46 - DEBUG - (USBFlashWin32.java:35) - Writing packet to phone
28/015/2014 22:15:46 - ERROR - (X10flash.java:517) - Error in processHeader : 6 : Das Handle ist ungültig.
28/015/2014 22:15:46 - ERROR - (X10flash.java:518) - Error flashing. Aborted
28/015/2014 22:15:46 - INFO - (MainSWT.java:130) - Device connected in flash mode

Which version of flashtool do you use?

version 0.9.15.0
i dont think its the tool.
what could be the reason for the phone to continiusly bootloop in flashmode??

WHY?!?
WHAT THE HELL AM I DOING WRONG?!?
it was to 3/4 finished flashing and then....
what does the error mean?
block verification failed?
iam using now the latest flashtool and the Xperia V_9.1.A.1.140_1270-9887_R1I_CE.ftf
what could be the reason for it to just break the flashing???
my god it was almost finished!!
29/038/2014 13:38:46 - INFO - Processing of cache.sin finished.
29/038/2014 13:38:46 - INFO - Processing system.sin
29/038/2014 13:38:46 - INFO - Checking header
29/038/2014 13:38:46 - INFO - Flashing data
29/049/2014 13:49:29 - ERROR - Processing of system.sin finished with errors.
29/049/2014 13:49:29 - INFO - Ending flash session
29/049/2014 13:49:30 - ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0009";ERR_DYNAMIC="Block verification failed 0x30000510";
edit:
well at least the flashing seems to have a effect.
the phone gets stuck at the sony logo and doesnt permanently reboot.

Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running

You probably broke something from system files.
One more question, is your bootloader unlocked?
EDIT:
Ok, I red the first post again, it is unlocked, you have to relock it first for SUS and PCC to work.

okay? i suppose i can lock and unlock it as often as i want?
thanks a lot guys
you are the best
EDIT:
okay, locked it PCC doesnt work but SUS seems to work now
again thanks ))

Dr CAT said:
Thank god! and you guys 4 helping me.
it works now wit 9.1.A.0.490.
it starts and works.
SUS and PCC and the update function in the phone dont work.
is there any way to make them working again? or do i need to manualy flash every update now?
a lot of thanks iam happy its running
Click to expand...
Click to collapse
how did you solve it? can you please tell me? i have problems on xperia t.

-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys

Dr CAT said:
-.- SUS isnt working.....it aborts after 3 mins and my phone is broken again -.-
i have no compleat idea how i fixed it in the first place.
i deinstalled the drivers via device manager and reinstalled them, used the latest flashtool version and tried a few different ftf files.
it seems important to use the ones which are for your region, the newest 4.1 android version and the 4.3 version are around 700mb big.
the one that worked is a older 4.1 version and only 500mb big.
the 500mb version worked for me although even with locked bootloader the over the air update funktion didnt worked.
i think it has something to do with the windows version and the usb port you are using to flash.
iam using windows vista which is a quite bit buggy installation.
the usb ports seem to have usb 1 drivers installed, sometimes randomly i get a bluescreen so its not really a system you want to use for flashing.
maybe my system has a problem with the system RAM causing bluescreens.
i think it would answer why i get a "block verification failed" error when flashing via flashtool one of the 700mb big ftf´s.
so if possible try to use a different PC.
i read somewhere on the net , if flashing aborts you should reinstall your PC and try again.
i had a previous error where the PC refused to install the appropriate drivers required to flash my phone.
driver install aborted with the error "wrong parameter" which seems to is caused by "driver refuse", old driver data which interfere.
i have no idea how i fixed this, went to bed and the next day it just worked.
make sure you have nothing running in the background that could interfere.
Comodo internet security and virus scanner may interfere.
also always start flashtool in admin mode, dont connect to a USB-hub.
just try and try again.
enable the debug log in flashtool and read at what point he aborts.
i will try now to repair mine again -.-
again rebooting all the time....thanks SUS^^
Thank you for your help guys
Click to expand...
Click to collapse
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin

isko95 said:
which drivers you installed? i tried to flash .141 firmware and always stop on system.sin
Click to expand...
Click to collapse
flashtool brings its own drivers it needs.
in the flashtool folder is one called drivers, you can install them from there.
the new 4.3 ftf just aborted and even the 4.1 ftf which worked before.
so i think its trail and error and pray that it works the next time^^
-.- and again .....

There's one more thing, try to install INF file from Sony Unlock page.

[Q] Z3C D5833 Bricked but with some hope

Hello guys
I sold a Z3C to a customer but 1 week after the phone died (January V4.4.4). He don't make nothing (root, unlock bootloader, flash rom, etc). Just a sudden death.
The issues were:
-By pressing the power button, the sony logo turned on but suddenly it shuts down just after that (once time).
-When I putted it on chage in the wall it appears the battery level ans it charges as well.
-When I was pressed vol up (or down, i can't remember well) + power it gave 3 vibrations.
- The LED light apperently was working.
What I've tried:
-Recover through the official softaware but I can't because it don't apear in USB and It asked to turn on the phone (the phone don't boot).
-Using flashtool. Same trouble, the usb don't recongnize.
After that, I gave up and sent it to sony repair. So it takes long SIX months. In the first, they said that was the battery. Next was the mainboard and that's it, no way to repair and them return the phone to me.
New issues (after the "sony repair"):
- The back glass was badly adjusted. No glue at all.
-No Sony logo anymore when press power button neither the LED lights.
-Good bye the 3 vibrations when press the 2 buttons.
-No charging battery icon when I puted in the wall charge (thank you sony).
-When I put it in the wall charge (or USB cable PC) the LED bright red and the logo sony appears over and over again in an eternal loop. Turns on, turns off.
(...)
I got new experience/knowledge with an asus zenfone 5 bricked and "ADB and Fastboot". I follow this tutorial:
a little update on my mini guide should be more clear now
- Download ADB and Fastboot (install at c:\adb for easy access )
- Download and install the Windows zenfone 5 driver
- Download firmware from Asus site for WW ( extract this zip file to get fastboot.img, boot.img and copy these to your ADB Fastboot folder )
- Rename the WWzip into "rom.zip" and move it to your ADB Fastboot folder (for easy typing in cmd)
- Turn Off your phone - connect to pc with usb cable
- Hold vol up and then press power On button of your phone - Keep holding both buttons, it should went into Droidboot screen.
- Open command prompt (cmd) and go to your ADB Fastboot folder (e.g. cd C:\adb)
- Type the following 2 lines: "fastboot flash fastboot fastboot.img" and "fastboot flash boot boot.img" (look phone screen, should say successfully done for both)
- Scroll down(use volume keys) to recovery and select it(use power key) and your phone will reboot
- now that you are in recovery(you can see a droid symbol lying down with red triangle over its stomach)
- Hold Vol Down and press Vol up (menu should appear)
- Choose "Apply update from adb"
- From cmd above type "adb sideload rom.zip"
- Wipe cache/dat and reboot
But in "fastboot flash fastboot fastboot.img" it appear "device not found". I installed PDANet Desktop and some ajusts I could fix the USB problem.
(...)
What I've tried (Today):
- If I press vol up button and plug it on PC the LED light is blue and show the USB icon next the clock.
-When I open ADB terminal and type "fastboot devices" it returns YT910YCRMG
-When i tried to flash the new room through the Flashtool the follow message appear:
24/016/2015 21:16:47 - INFO - Device connected with USB debugging off
24/016/2015 21:16:47 - INFO - For 2011 devices line, be sure you are not in MTP mode
I'm sure that the customer doesn't turned the debugging on (he don't know what is this). There is a way to turn debugging on the device in the current situation?
I can't apply the same tutorial from asus because there's no fastboot.img and boot.img files inside the Sony rom .TFT.
Some suggestions? I really appreciate some suggestions.
Thank you

Updates:
I've tried via Flashtool > fastboot mode (by holding vol UP button) install the kernel.sin (extracted from the rom) but it leads to the follows errors:
By "Version 1.0" > (Select Kernel to Hotboot)
03/059/2015 22:59:21 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\nada\.flashTool\firmwares\kernel.sin
03/059/2015 22:59:21 - INFO - Flashing selected kernel
03/059/2015 22:59:22 - INFO - sending 'boot' (9261 KB)...
03/059/2015 22:59:22 - INFO - OKAY [ 0.313s]
03/059/2015 22:59:22 - INFO - writing 'boot'...
03/059/2015 22:59:22 - INFO - FAILED (remote: Command not allowed)
03/059/2015 22:59:22 - INFO - finished. total time: 0.316s
03/059/2015 22:59:22 - INFO - FASTBOOT Output:
sending 'boot' (9261 KB)...
OKAY [ 0.313s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.316s
Pelo By DooMLoRD > (Select Kernel to Flash)
03/059/2015 22:59:31 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\nada\.flashTool\firmwares\kernel.sin
03/059/2015 22:59:31 - INFO - HotBooting selected kernel
03/059/2015 22:59:32 - INFO - FASTBOOT Output:
creating boot image...
creating boot image - 9486336 bytes
downloading 'boot.img'...
OKAY [ 0.309s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.366s
After both ways the message continues over and over again...
3/059/2015 22:59:32 - INFO - Device disconnected
03/059/2015 22:59:34 - INFO - Device connected with USB debugging off
03/059/2015 22:59:34 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:41 - INFO - Device disconnected
03/059/2015 22:59:43 - INFO - Device connected with USB debugging off
03/059/2015 22:59:43 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:51 - INFO - Device disconnected
03/059/2015 22:59:52 - INFO - Device connected with USB debugging off
03/059/2015 22:59:52 - INFO - For 2011 devices line, be sure you are not in MTP mode
03/059/2015 22:59:53 - INFO - Device disconnected
There's some mode to apply USB debugging with device bricked? The phone don't passes from the sony logo. It is stuck on bootloop.

hey there!just so happen to see your post.so,why not try to help you out..& i hope i'm not too late for this!hehe..anyways,here's what i could suggest by checking this link out("the rubber band trick"):
http://forum.xda-developers.com/showthread.php?p=33032165
big thanx to @Toledo_JAB!(way to go,man!thanx again a lot!)

Thank you for the reply. I will try this and post the results soon.

sure thing! that link i just shared with you should possitively resolve your issue! and remember,patience is a virtue..good luck! :good:

Arturiuz! said:
sure thing! that link i just shared with you should possitively resolve your issue! and remember,patience is a virtue..good luck! :good:
Click to expand...
Click to collapse
Thank you very much for the support. I really appreciate it.
I've tried the rubber suggestion: 2 days in wall charger plus 1 day plugged in PC with rubber and no answer.
I think is probably a hardware damage. Too sad.

Xperia SP- Bricked After Trying To Flash CM12.1?

Did I brick it?
So my sweet old SP seems kinda in between the kinds of bricks I find on this forum, so before giving elaborate background stories, this is the condition my phone is in after attempting to flash CM12.1 (first time doing such things which was probably what went wrong):
Without power cable, turning device on gives one short buzz, volume up + power button the same and a blue flash volume down a green flash. Thats all they do, black screen and no signs of life afterwards.
Now with power cable connected to my PC and powering up while holding one of the volume buttons it is recognised on the PC (unknown device in the device manager). I downloaded FlashTool, which whined about drivers but those couldn't install for some reason, so I unpacked the installer and manually installed what I thought were the correct drivers.
Now FlashTool sees the device connected in FlashMode (curiously disconects and reconnects every minute) or Fast Bootmode (whatever those mean, I'm a noob and yeah I hate myself) but I cant actually flash anything.
Is there hope? Or did I screw up?
Thank you very much for even reading my pathetic plea.

Have you tried using PC Companion to restore your phone? Maybe your phone doesn't have enough charge, that might be what's preventing Flashtool from working properly.

Plum Crazy said:
Have you tried using PC Companion to restore your phone? Maybe your phone doesn't have enough charge, that might be what's preventing Flashtool from working properly.
Click to expand...
Click to collapse
I'll try it, but when I started flashing I had 100% and last time I (could) check it was still around 90%.
UPDATE: Charging makes green led burn, also I find it strange that PC companion didn't recognise the phone as being a phone either

28/007/2015 10:07:30 - INFO - Device connected in flash mode
28/007/2015 10:07:37 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.207. Customization : T-Mobile NL
28/007/2015 10:07:37 - INFO - Preparing files for flashing
28/008/2015 10:08:02 - INFO - Please connect your device into flashmode.
28/008/2015 10:08:04 - INFO - Opening device for R/W
28/008/2015 10:08:04 - INFO - Reading device information
28/008/2015 10:08:04 - INFO - Unable to read from phone after having opened it.
28/008/2015 10:08:04 - INFO - trying to continue anyway
28/008/2015 10:08:05 - INFO - Start Flashing
28/008/2015 10:08:05 - INFO - Processing loader.sin
28/008/2015 10:08:05 - INFO - Checking header
28/008/2015 10:08:05 - ERROR - Processing of loader.sin finished with errors.
28/008/2015 10:08:05 - INFO - Ending flash session
28/008/2015 10:08:05 - ERROR - Error in processHeader : 1 : Onjuiste functie.
28/008/2015 10:08:05 - ERROR - Error flashing. Aborted

Hmm, I just tried to flash it using the fastboot mode since that connection seems much more stable. Now I get this:
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:186) - Selected kernel (boot.img or kernel.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:187) - Flashing selected kernel
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (1147743 KB)...
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:190) - FASTBOOT Output:
sending 'boot' (1147743 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:191) - Please check the log before rebooting into system
28/031/2015 10:31:48 - INFO - (FastbootToolbox.java:136) - Now plug your device in Fastboot Mode
28/031/2015 10:31:49 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:209) - Selected system (system.img or system.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:210) - Flashing selected system
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - sending 'system' (1147743 KB)...
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - FAILED (remote: The Device must be rooted first)
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - finished. total time: 0.007s
28/032/2015 10:32:02 - INFO - (FastBootToolBoxJob.java:213) - Please check the log before rebooting into system
My phone unrooted itself? :crying: Can I even root it again without a functioning OS on it?

Raven5887 said:
Hmm, I just tried to flash it using the fastboot mode since that connection seems much more stable. Now I get this:
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:186) - Selected kernel (boot.img or kernel.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/031/2015 10:31:26 - INFO - (FastBootToolBoxJob.java:187) - Flashing selected kernel
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - sending 'boot' (1147743 KB)...
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - FAILED (remote: The Device must be rooted first)
28/031/2015 10:31:37 - INFO - (ProcessBuilderWrapper.java:91) - finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:190) - FASTBOOT Output:
sending 'boot' (1147743 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
28/031/2015 10:31:37 - INFO - (FastBootToolBoxJob.java:191) - Please check the log before rebooting into system
28/031/2015 10:31:48 - INFO - (FastbootToolbox.java:136) - Now plug your device in Fastboot Mode
28/031/2015 10:31:49 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - DEBUG - (ProcessBuilderWrapper.java:93) - PSDN:YT910CW9DM&ZLP fastboot
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:209) - Selected system (system.img or system.sin): C:\Users\xxx\.flashTool\firmwares\Downloads\C5303_T-Mobile NL_1272-4709_12.1.A.1.207_R6B\system_S1-SW-LIVE-7054-PID1-0002-S1-PARTITION.sin
28/032/2015 10:32:01 - INFO - (FastBootToolBoxJob.java:210) - Flashing selected system
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - sending 'system' (1147743 KB)...
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - FAILED (remote: The Device must be rooted first)
28/032/2015 10:32:02 - DEBUG - (ProcessBuilderWrapper.java:93) - finished. total time: 0.007s
28/032/2015 10:32:02 - INFO - (FastBootToolBoxJob.java:213) - Please check the log before rebooting into system
My phone unrooted itself? :crying: Can I even root it again without a functioning OS on it?
Click to expand...
Click to collapse
Try on another PC with another cable. Preferably on Windows 7.

Phoenix854 said:
Try on another PC with another cable. Preferably on Windows 7.
Click to expand...
Click to collapse
Somehow this did the trick... I could update the drivers directly and everything just worked.
Many thanks!

Fail to backup TA - fail to install recovery

Hi,
I need help for backup TA and install TWRP recovery.
I have a Xperia SP Jelly 4.3 firmware 205 rooted, locked bootloader (unlock allowed), and want to use flashtool to save TA partiton and install TWRP (no recovery installed yet).
I have installed all drivers, Pc companion off, antivirus off, Sony USB cable, windows 10 x64.
Impossible to save TA with Backup-TA (I read the entire thread in developpement section and download/tried all the solutions there. As I am not allowed to post there, I post here). Here is the error :
Code:
=======================================
FIND TA PARTITION
=======================================
[COLOR="Lime"] Partition found![/COLOR]
=======================================
BACKUP TA PARTITION
=======================================
[COLOR="Red"]dd: can't open '/sdcard/backupTA.img': No such file or directory[/COLOR]
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup does not match TA Partition. Please try again.
*** Backup unsuccessful. ***
Even in flashtool, can't save TA nor install TWRP
Code:
27/059/2016 21:59:30 - INFO - <- This level is successfully initialized
27/059/2016 21:59:31 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
27/059/2016 21:59:31 - INFO - Executing search strategies to find proxy selector
27/059/2016 21:59:31 - INFO - No proxy found for IE. Trying next one
27/059/2016 21:59:31 - INFO - No proxy found for firefox. Trying next one
27/059/2016 21:59:31 - INFO - No proxy found for java. Trying next one
27/059/2016 21:59:31 - INFO - Syncing devices from github
27/059/2016 21:59:32 - INFO - Opening devices repository.
27/059/2016 21:59:32 - INFO - Scanning devices folder for changes.
27/059/2016 21:59:39 - INFO - Pulling changes from github.
27/059/2016 21:59:40 - INFO - Quietly closing devices repository.
27/059/2016 21:59:40 - INFO - Devices sync finished.
27/059/2016 21:59:40 - INFO - Loading devices database
27/059/2016 21:59:40 - INFO - Loaded 91 devices
27/059/2016 21:59:40 - INFO - Starting phone detection
27/059/2016 21:59:46 - INFO - [COLOR="Lime"]Device connected with USB debugging on[/COLOR]
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Connected device : Sony Xperia SP[/COLOR]
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Installed version of busybox : BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary[/COLOR].
27/059/2016 21:59:46 - INFO - [COLOR="Cyan"]Android version : 4.3 / kernel version : 3.4.0-perf-g4c8352f-00775-g89dacae / Build number : 12.1.A.1.205[/COLOR]
27/059/2016 21:59:46 - INFO - Checking root access
27/059/2016 21:59:46 - INFO - [COLOR="Lime"]Root Access Allowed[/COLOR]
27/059/2016 21:59:52 - INFO - Begin backup of /dev/block/platform/msm_sdcc.1/by-name/TA
27/059/2016 21:59:52 - ERROR - [COLOR="Red"]Erreur when doing raw backup[/COLOR]
27/000/2016 22:00:36 - INFO - Now plug your device in Fastboot Mode
27/000/2016 22:00:40 - INFO - Device disconnected
27/001/2016 22:01:21 - INFO - [COLOR="Lime"]Device connected in fastboot mode[/COLOR]
27/001/2016 22:01:33 - INFO - [COLOR="Lime"]Selected kernel (boot.img or kernel.sin): C:\Users\Someone\Downloads\twrp-3.0.2-r12-boot-huashan.img[/COLOR]
27/001/2016 22:01:33 - INFO - Flashing selected kernel
27/001/2016 22:01:33 - INFO - sending 'boot' (12253 KB)...
27/001/2016 22:01:33 - INFO - [COLOR="Red"]FAILED (remote: The Device must be rooted first)[/COLOR]
27/001/2016 22:01:33 - INFO - finished. total time: 0.007s
27/001/2016 22:01:33 - INFO - FASTBOOT Output:
sending 'boot' (12253 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.007s
27/001/2016 22:01:33 - INFO - Please check the log before rebooting into system
I don't understand what is missing, can't find any solution that worked...
Thanks for any clue.

In this thread (where I am not allowed to post yet), I tried every solutions people thought about, but none worked for me. By using Backup-TA-9.11 method and tips, I have even though be able to pass one more step by doing this :
unplug SD card
replace 'sdcard/backupTA.img' by '/storage/emulated/0/backupTA.img' in backup.bat script
Click to expand...
Click to collapse
Then, where I was stuck in first step because of that :
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
dd: can't open '/sdcard/backupTA.img': No such file or directory
=======================================
INTEGRITY CHECK
=======================================
FAILED - Backup does not match TA Partition. Please try again.
*** Backup unsuccessful. ***
Click to expand...
Click to collapse
I eventually reached that (in green) until a new error (in red):
=======================================
FIND TA PARTITION
=======================================
Partition found!
=======================================
BACKUP TA PARTITION
=======================================
=======================================
INTEGRITY CHECK
=======================================
OK
=======================================
PULL BACKUP FROM SDCARD
=======================================
remote object '/storage/emulated/0/backupTA.img' does not exist
*** Backup unsuccessful. ***
Click to expand...
Click to collapse
backupTA.img file DOES exist on my phone, and it's not empty (about 2 Mo), script created it well !
I assume there an issue with adb 'pull' command in line :
tools\adb.exe pull /storage/emulated/0/backupTA.img tmpbak\TA.img
Click to expand...
Click to collapse
Here is where I am now, looking for a solution to make 'pull' command work...
Thanks for help !

Problem solved for Backup-TA-9.11 method.
unplug SD card
then replace these lines in backup.bat script :
tools\adb.exe pull /sdcard/backupTA.img tmpbak\TA.img
tools\adb.exe shell su -c "%BB% dd if=!partition! of=/sdcard/backupTA.img
tools\adb.exe shell su -c "%BB% md5sum /sdcard/backupTA.img
Click to expand...
Click to collapse
By
tools\adb.exe pull /storage/emulated/0/backupTA.img tmpbak\TA.img
tools\adb.exe shell su -c "%BB% dd if=!partition! of=/storage/emulated/0/backupTA.img
tools\adb.exe shell su -c "%BB% md5sum /sdcard/backupTA.img <-- this one unchanged !!!!
Click to expand...
Click to collapse
Don't ask me why, I really don't know, I assume it is because of the way each command uses path...
Problem with Backup-TA-9.11 method solved, still remains flashtool ones !
Just to check, please tell me if the backup zip file contains the right files :
TA.blk (1Ko)
TA.img (2048 Ko)
TA.md5 (1Ko)
TA.serial (1Ko)
TA.timestamp (1Ko)
TA.version (1Ko)

Glad to hear that you've solved the TA partition backup problem.
For flashing twrp recovery you need to root your phone first as stated in your flashtool log. And the easiest way to root the stock firmware is by using "towel root" app (just Google it and download the apk then install and root your phone by touching the lamda icon).
Sent from my Xperia SP using Tapatalk

Phone IS rooted from the beginning, like I said.
Installing flashtool 0.9.18.6 instead of 0.9.22.3 solved problem. Flashtool 0.9.22.3 have never worked well in my case.

I still have the problem as during integrity check it said "backup does not match ta partition" . i am using xperia SP(rooted) with locked bootloader and unlocking allowed.