[Q] Flash Tool + Linux Mint Help - Xperia Z Q&A, Help & Troubleshooting

Hey All,
So today I've tried rooting the .253 by downgrading my firmware back to .434 but for some reason it just doesn't work I've inserted the log from the terminal and the log from Flash Tool (Latest Release), I'm running Linux Mint 14 xfce (Running Flash Tool as root of course) I took a risk by unplugging the device after 25 minutes and luckily it still works no brick so I'm happy but I'm a little stuck on how to actually get it to work because I had the same problem with it not downgrading on windows which I was stuck on because thats how I flashed the .253 firmware :S
Terminal Log
Code:
JAVA_HOME not set. Using default value : ./x10flasher_lib/linjre32
Error parsing gtk-icon-sizes string: ''
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
(java:17516): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.Command.writeCommand(Command.java:129)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.uploadImage(X10flash.java:215)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
flashsystem.X10FlashException: Cannot read from device
at flashsystem.X10flash.uploadImage(X10flash.java:222)
at flashsystem.X10flash.sendLoader(X10flash.java:272)
at flashsystem.X10flash.flashDevice(X10flash.java:355)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
libusb_bulk_transfer (write) : No device
Error : did not write all data
libusb_bulk_transfer (read) : No device
flashsystem.X10FlashException: S1 Header checksum Error
at flashsystem.S1Packet.<init>(S1Packet.java:55)
at flashsystem.io.USBFlashLinux.linuxReadS1Reply(USBFlashLinux.java:53)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:50)
at flashsystem.io.USBFlash.writeS1(USBFlash.java:33)
at flashsystem.Command.writeCommand(Command.java:123)
at flashsystem.Command.send(Command.java:140)
at flashsystem.X10flash.endSession(X10flash.java:398)
at flashsystem.X10flash.closeDevice(X10flash.java:408)
at flashsystem.X10flash.flashDevice(X10flash.java:373)
at gui.FlasherGUI$56.run(FlasherGUI.java:1397)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Thread.java:722)
release_interface : No device
release_interface : No device
Flash Tool Log
Code:
23/054/2013 08:54:04 - INFO - <- This level is successfully initialized
23/054/2013 08:54:04 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 22:29:21
23/054/2013 08:54:04 - INFO - You can drag and drop ftf files here to start flashing them
23/054/2013 08:54:08 - INFO - Device disconnected
23/054/2013 08:54:13 - INFO - List of connected devices (Device Id) :
23/054/2013 08:54:13 - INFO - List of ADB devices :
23/054/2013 08:54:13 - INFO - - none
23/054/2013 08:54:13 - INFO - List of fastboot devices :
23/054/2013 08:54:13 - INFO - - none
23/003/2013 09:03:28 - INFO - Flash canceled
23/004/2013 09:04:00 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/004/2013 09:04:00 - INFO - Preparing files for flashing
23/005/2013 09:05:32 - INFO - Please connect your device into flashmode.
23/005/2013 09:05:42 - INFO - Device connected in flash mode
23/005/2013 09:05:42 - INFO - Opening device for R/W
23/005/2013 09:05:42 - INFO - Device ready for R/W.
23/005/2013 09:05:42 - INFO - Reading device information
23/005/2013 09:05:43 - INFO - Phone ready for flashmode operations.
23/005/2013 09:05:43 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/005/2013 09:05:43 - INFO - Start Flashing
23/005/2013 09:05:43 - INFO - Processing loader
23/005/2013 09:05:43 - INFO - Checking header
23/005/2013 09:05:43 - INFO - Flashing data
23/023/2013 09:23:51 - INFO - Ending flash session <--- This is were I disconnected the device after 25 mins of waiting
23/023/2013 09:23:51 - ERROR - Cannot read from device
23/023/2013 09:23:51 - ERROR - Error flashing. Aborted
23/023/2013 09:23:52 - INFO - Device disconnected
23/025/2013 09:25:24 - INFO - Selected Xperia Z_10.1.A.1.434_Generic_WORLD.ftf
23/025/2013 09:25:24 - INFO - Preparing files for flashing
23/026/2013 09:26:48 - INFO - Please connect your device into flashmode.
23/027/2013 09:27:32 - INFO - Device connected in flash mode <--- This is me trying it again ...
23/027/2013 09:27:33 - INFO - Opening device for R/W
23/027/2013 09:27:33 - INFO - Device ready for R/W.http://forum.xda-developers.com/showthread.php?p=41741577#
23/027/2013 09:27:33 - INFO - Reading device information
23/027/2013 09:27:33 - INFO - Phone ready for flashmode operations.
23/027/2013 09:27:33 - INFO - Current device : C6603 - CB5A1PQBU0 - 1270-4986_R7A - 1269-5309_10.1.1.A.1.253 - GLOBAL-LTE_10.1.1.A.1.253
23/027/2013 09:27:33 - INFO - Start Flashing
23/027/2013 09:27:33 - INFO - Processing loader
23/027/2013 09:27:33 - INFO - Checking header
23/027/2013 09:27:33 - INFO - Flashing data <--- And this is me just giving up ... (got to get to work so :()

Related

[Q] Flash tool not working

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.

[Q] My Xperia Z Died today

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

[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] Bricked phone? used to work fine!

Currently my Xperia Z stopped working. I hadn't used it in a while, since the connector broke off. I got the connector fixed, and the phone seems to function, but it wont boot.
It boots to the SONY logo, and then goes black. The thing i have tried:
- Flash stock rom using Flashtool, i keep getting this:
Code:
29/004/2014 10:04:14 - INFO - <- This level is successfully initialized
29/004/2014 10:04:14 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
29/004/2014 10:04:19 - INFO - Device connected in flash mode
29/004/2014 10:04:50 - INFO - Selected C6603 / 10.4.1.B.0.101 / CE
29/004/2014 10:04:50 - INFO - Preparing files for flashing
29/004/2014 10:04:51 - INFO - Please connect your device into flashmode.
29/004/2014 10:04:51 - INFO - Opening device for R/W
29/004/2014 10:04:52 - INFO - Reading device information
29/005/2014 10:05:16 - INFO - Unable to read from phone after having opened it.
29/005/2014 10:05:16 - INFO - trying to continue anyway
29/005/2014 10:05:16 - INFO - Start Flashing
29/005/2014 10:05:16 - INFO - Processing loader
29/005/2014 10:05:16 - INFO - Checking header
29/005/2014 10:05:16 - INFO - Ending flash session
29/005/2014 10:05:16 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
29/005/2014 10:05:16 - ERROR - Error flashing. Aborted
29/005/2014 10:05:16 - INFO - Device disconnected
29/005/2014 10:05:17 - INFO - Device connected in flash mode
Then i tried using Fastboot to install a new boot.img, which is succesfull
Code:
Flashing kernel
< waiting for device >
sending 'boot' (11048 KB)...
OKAY [ 0.355s]
writing 'boot'...
OKAY [ 0.539s]
finished. total time: 0.902s
Done !
Press any key to continue . . .
I'm able to get into Fastboot and Flashmode so the USB seems to work fine. After using fastboot i got a litte further, now it boots to SONY, then i get "the software update failed, make sure that your phone is connected to the computer and try again."
I tried using EMMA, but i have no idea what to do there. It keeps "updating the services"
Code:
Preparing service...
...service successfully prepared.
Sending data to the device...
...data sent successfully.
Finalizing service...
...successfully finalized.
Service execution completed in 139 seconds
Success
I also tried PC Companion which complains that i use unofficial software.
Anyone has any idea what else i can do?
tharealmb said:
Currently my Xperia Z stopped working. I hadn't used it in a while, since the connector broke off. I got the connector fixed, and the phone seems to function, but it wont boot.
It boots to the SONY logo, and then goes black. The thing i have tried:
- Flash stock rom using Flashtool, i keep getting this:
Code:
29/004/2014 10:04:14 - INFO - <- This level is successfully initialized
29/004/2014 10:04:14 - INFO - Flashtool Version 0.9.10.2beta4 built on 2013-03-21 19:00:00
29/004/2014 10:04:19 - INFO - Device connected in flash mode
29/004/2014 10:04:50 - INFO - Selected C6603 / 10.4.1.B.0.101 / CE
29/004/2014 10:04:50 - INFO - Preparing files for flashing
29/004/2014 10:04:51 - INFO - Please connect your device into flashmode.
29/004/2014 10:04:51 - INFO - Opening device for R/W
29/004/2014 10:04:52 - INFO - Reading device information
29/005/2014 10:05:16 - INFO - Unable to read from phone after having opened it.
29/005/2014 10:05:16 - INFO - trying to continue anyway
29/005/2014 10:05:16 - INFO - Start Flashing
29/005/2014 10:05:16 - INFO - Processing loader
29/005/2014 10:05:16 - INFO - Checking header
29/005/2014 10:05:16 - INFO - Ending flash session
29/005/2014 10:05:16 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
29/005/2014 10:05:16 - ERROR - Error flashing. Aborted
29/005/2014 10:05:16 - INFO - Device disconnected
29/005/2014 10:05:17 - INFO - Device connected in flash mode
Then i tried using Fastboot to install a new boot.img, which is succesfull
Code:
Flashing kernel
< waiting for device >
sending 'boot' (11048 KB)...
OKAY [ 0.355s]
writing 'boot'...
OKAY [ 0.539s]
finished. total time: 0.902s
Done !
Press any key to continue . . .
I'm able to get into Fastboot and Flashmode so the USB seems to work fine. After using fastboot i got a litte further, now it boots to SONY, then i get "the software update failed, make sure that your phone is connected to the computer and try again."
I tried using EMMA, but i have no idea what to do there. It keeps "updating the services"
Code:
Preparing service...
...service successfully prepared.
Sending data to the device...
...data sent successfully.
Finalizing service...
...successfully finalized.
Service execution completed in 139 seconds
Success
I also tried PC Companion which complains that i use unofficial software.
Anyone has any idea what else i can do?
Click to expand...
Click to collapse
As your bootloader is unlocked, what if you flash a kernel of a custom rom, that has a recovery included? From there you could try to flash a rom...
St.Jimmy90 said:
As your bootloader is unlocked, what if you flash a kernel of a custom rom, that has a recovery included? From there you could try to flash a rom...
Click to expand...
Click to collapse
you're a lifesaver. Haven't used android in a while (have WP 8.1 right now). Installed TWRP boot and after that it worked flawless... My nephew will be greatfull :good:

Turn off the Sony xperia ُT after installing after installing the twrp 3.2

The phone has already been blocked by Sony's bootloader.. I later removed the handset from the kingroot app to the sony xperia t phone. Also, in the fast-boot mode, twrp-3.2.3-0-mint.img, I did not turn on the phone, and now it only works in the fast-boot mode. The flash mode also provides the official ROM
07/027/2019 05:27:25 - INFO - Opening device for R/W
07/027/2019 05:27:25 - INFO - Reading device information
07/027/2019 05:27:25 - INFO - Unable to read from phone after having opened it.
07/027/2019 05:27:25 - INFO - trying to continue anyway
07/027/2019 05:27:25 - ERROR - root : this bundle is not valid
07/027/2019 05:27:40 - INFO - Processing loader.sin
07/027/2019 05:27:40 - INFO - Checking header
07/027/2019 05:27:40 - ERROR - Processing of loader.sin finished with errors.
07/027/2019 05:27:40 - ERROR - Error in processHeader : 1 : Incorrect function.
07/027/2019 05:27:40 - INFO - Your phone bootloader cannot be officially unlocked
07/027/2019 05:27:40 - INFO - You can now unplug and restart your phone
Click to expand...
Click to collapse
info:
sony-flashtool-0.9.18.6
Minimal ADB and Fastboot
android 4.1

Categories

Resources