Hello,
I was trying to root my sola so to solve the wifi bug.
I found i need to flash it back from .54 to .10 using flashtool
Although, i am not being able to do it as I get a error message regarding drivers
What I do is I install flashtool on c:
I go to the drivers folder and execute Flashtool-drivers.exe and I install the Sola Drivers as well as the Flashboot and Fastboot drivers.
I open flashboot, select the .10 kernel, press flash, it tells me to turn off my sola and run it at flash mode (Volume down + USB) and then it gives me Drivers error message...
Can anyone help me?
08/041/2013 16:41:58 - INFO - <- This level is successfully initialized
08/041/2013 16:41:59 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
08/042/2013 16:42:05 - INFO - Device connected with USB debugging on
08/042/2013 16:42:07 - INFO - Connected device : Sony Xperia Sola
08/042/2013 16:42:07 - INFO - Installed version of busybox : N/A
08/042/2013 16:42:07 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
08/042/2013 16:42:13 - INFO - List of connected devices (Device Id) :
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_01\7&37E26950&0&0001 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173&MI_00\7&37E26950&0&0000 Driver installed : true
08/042/2013 16:42:13 - INFO - - USB\VID_0FCE&PID_6173\BX9033RP3D Driver installed : true
08/042/2013 16:42:13 - INFO - List of ADB devices :
08/042/2013 16:42:13 - INFO - - BX9033RP3D
08/042/2013 16:42:13 - INFO - List of fastboot devices :
08/042/2013 16:42:13 - INFO - - none
This not flash mode, you device must be powered off to connect in flash mode.
ChikeD said:
This not flash mode, you device must be powered off to connect in flash mode.
Click to expand...
Click to collapse
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected
haloboyscp said:
Ahhh.
that was it. i must connect first of all in flash mode...
Ok. I did it.
Anyway now I got this message:
08/002/2013 18:02:25 - ERROR - Error in processHeader : 995 : A operação de E/S was cancelled due to a module exit or an application request.
08/002/2013 18:02:25 - ERROR - Error flashing. Aborted
08/002/2013 18:02:25 - INFO - Device disconnected
Click to expand...
Click to collapse
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?
ChikeD said:
I saw the Error in processHeader before, not sure if the same number, and it was also driver issue I think.
Can you post the whole log?
Click to expand...
Click to collapse
I already got that.
that was just because i was running on flashloader 64, i switched for normal flashloader and it ran.
I think now i have done the whole thing for rooting the phone, though... Using Es File Explorer, I go to root there and it's still nothing there.
When i flashed back from the .10 to .54 it was written 08/011/2013 19:11:27 - INFO - Loader : S1_Root_3065 - Version : R5E003 / Bootloader status : ROOTABLE
so everything should have been ok?
:S
Thanks guys
Now I flash the phone, everything works.
I flash back to .10.
I try to root and get an error message like.
Could not restore. reconnect external memory and try again
I read it would be because the phone wasnt flashed on .10 but i do that...
What can it be?
Thanks
Related
Hello together!
I can't post in the Development Section, that's why I ask here (related to http://forum.xda-developers.com/showthread.php?t=1916419).
I'm on Linux 12.04 and added /etc/udev/rules.d/80-flashtool.rules:
Code:
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
Starting as normal user, drag-dropping the downloaded file (DL via torrent), gave countless red alerts with:
12/033/2012 14:33:20 - ERROR - No permission on device. Add valid udev rules
Click to expand...
Click to collapse
So I ran
Code:
sudo ./FlashTool
and DragDropped the .ftf, excluded baseband and waited for the resquest to put the device into flash-mode, which I did (green LED).
Then the error occurs (complete flashtool log follows):
12/036/2012 14:36:42 - INFO - <- This level is successfully initialized
12/036/2012 14:36:42 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:46:54
12/036/2012 14:36:42 - INFO - You can drag and drop ftf files here to start flashing them
12/036/2012 14:36:43 - INFO - Device disconnected
12/038/2012 14:38:21 - INFO - Selected ST25a_6.1.1.B.1.10_None.ftf
12/038/2012 14:38:21 - INFO - Preparing files for flashing
12/038/2012 14:38:38 - INFO - Please connect your device into flashmode.
12/038/2012 14:38:44 - INFO - Device connected in flash mode
12/038/2012 14:38:44 - INFO - Opening device for R/W
12/038/2012 14:38:44 - INFO - Reading device information
12/038/2012 14:38:44 - INFO - Start Flashing
12/038/2012 14:38:44 - INFO - Processing loader
12/038/2012 14:38:44 - INFO - Checking header
12/038/2012 14:38:44 - INFO - Ending flash session
12/038/2012 14:38:44 - ERROR -
12/038/2012 14:38:44 - ERROR - Error flashing. Aborted
12/038/2012 14:38:44 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Any ideas, what this is about? Does "checking header" refer to the tft or to my phone?
It's a german, non-branded U25i, successfully unlocked with flashtool (x10flasher_lib/fastboot.linux).
Maybe the file is corrupted? Can someone send me the HASH of a working file?
Thanks for help,
Guntram
PS: Switching debugging level to "DEBUG" doesn't reveal more information:
12/044/2012 14:44:08 - INFO - (FlasherGUI.java:1297) - Please connect your device into flashmode.
12/044/2012 14:44:17 - INFO - (FlasherGUI.java:1020) - Device connected in flash mode
12/044/2012 14:44:18 - INFO - (USBFlashLinux.java:19) - Opening device for R/W
12/044/2012 14:44:18 - INFO - (X10flash.java:408) - Reading device information
12/044/2012 14:44:18 - INFO - (X10flash.java:320) - Start Flashing
12/044/2012 14:44:18 - INFO - (X10flash.java:198) - Processing loader
12/044/2012 14:44:18 - INFO - (X10flash.java:167) - Checking header
12/044/2012 14:44:18 - INFO - (X10flash.java:365) - Ending flash session
12/044/2012 14:44:18 - ERROR - (X10flash.java:342) -
12/044/2012 14:44:18 - ERROR - (X10flash.java:343) - Error flashing. Aborted
12/044/2012 14:44:18 - INFO - (FlasherGUI.java:1020) - Device connected in flash mode
"Check drivers" yielded:
12/000/2012 16:00:56 - INFO - (Device.java:130) - List of connected devices (Device Id) :
12/000/2012 16:00:56 - INFO - (Device.java:138) - - VID_0FCE&PID_ADDE\ Driver installed : true
12/000/2012 16:00:56 - INFO - (Device.java:140) - List of ADB devices :
12/000/2012 16:00:56 - DEBUG - (ProcessBuilderWrapper.java:93) - List of devices attached
12/000/2012 16:00:56 - INFO - (Device.java:147) - - none
12/000/2012 16:00:56 - INFO - (Device.java:148) - List of fastboot devices :
12/000/2012 16:00:56 - INFO - (Device.java:155) - - none
12/001/2012 16:01:26 - INFO - (FlasherGUI.java:1016) - Device disconnected
Click to expand...
Click to collapse
but I assume, the driver thing is only Windows-related. Am I right?
[edith]
Ok...it seems not to be ROM-related. I tried the "relock"-ftf, which failed the same way...
Any hint on what might cause these problems?
Thanks!
I tried it now on another computer (Ubuntu 11.10 64bit, this time) and I do get the same error!
Is there somebody out there, who can help?
Did I miss to setup something on the phone (USB-Debugging is turned on)?
+1
same here, xperia u, linux mint based on ubuntu 12.04
where is the problem
hi, sadly using windows there are no problems. and I would love to not use windows for it.
it is related with flashtool and ubuntu 12.04.
flashtool was fine with my x10 mini pro and linux, but it is not working with xperia u. also the mtp is a pain.
Virtual Box Windows under Linux works like a charme .
So the phone is "nicely" connected, but the flashtool doesn't work properly .
Updated flashtool to linux version 0.9.9.0 and now it works great
Sent from my ST25i using xda app-developers app
Are u entering flashmode by pressing volume down and power key??
If yes then its wrong
Download official ics ftf from development section of ur xperia
Download flashtool
Install flashtool
Go to c/flashtool/drivers
Install drivers for ur xperia
Now switch of ur phone keep it aside
Go to flashtool
Click thunder icon
Select flashmode
Select ftf
Check no final verification
Check exclude ta
Click flash\start
Now it will ask u to connect ur phone in flashmode
Press the volume down button, keep it pressed and connect to usb
U r done wait for flashing
Sent from my ST25i using Tapatalk 2
error flashing. aborted.
think i have same problem as OP.
using Mint11 (ubuntu 11.10 64bit based) and flashtool 0.9.8 as i can't understand how to get libusbx working for flashtool 0.9.9
btw is disabling final verification dangerous?
i'll have to try virtualbox i guess, scared of this as more to go wrong with usb access.
update: followed this guide
(stupidly i can't include links, but its on ubuntu forum)
ubuntuforums.org/showthread.php?t=2084266
installed libusbx on a laptop (running Mint 14 KDE btw, needed gcc 32bit libs to compile it), flashtool 0.9.9 worked. yay.
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
this comes when flashing
20/044/2013 00:44:14 - INFO - <- This level is successfully initialized
20/044/2013 00:44:15 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
20/044/2013 00:44:15 - INFO - You can drag and drop ftf files here to start flashing them
20/044/2013 00:44:26 - INFO - Device connected with USB debugging on
20/044/2013 00:44:26 - INFO - Connected device : ST17
20/044/2013 00:44:27 - INFO - Installed version of busybox : BusyBox v1.20.2-cm9 bionic (2012-07-14 01:52 +0200) multi-call binary.
20/044/2013 00:44:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-FXP / Build number : IMM76L
20/044/2013 00:44:28 - INFO - Root Access Allowed
20/045/2013 00:45:19 - INFO - Selected WT19i_4.0.2.A.0.58_(1254-1868).ftf
20/045/2013 00:45:19 - INFO - Preparing files for flashing
20/045/2013 00:45:30 - INFO - Please connect your device into flashmode.
20/045/2013 00:45:35 - INFO - Device disconnected
20/046/2013 00:46:14 - INFO - Opening device for R/W
20/046/2013 00:46:15 - INFO - Device connected in flash mode
20/046/2013 00:46:15 - INFO - Start Flashing
20/046/2013 00:46:15 - INFO - Processing loader
20/046/2013 00:46:15 - INFO - Checking header
20/046/2013 00:46:15 - INFO - Ending flash session
20/046/2013 00:46:15 - ERROR -
20/046/2013 00:46:15 - ERROR - Error flashing. Aborted
20/046/2013 00:46:15 - INFO - Device connected in flash mode
Try checking "no final verification" before flashing. Should work
Siddharth121 said:
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
Click to expand...
Click to collapse
you have to tick your usb debugging... and then you must in MSC mode it can be on setting .
and dont connect your phone . you must flashing .ftf then after it wait until they say connect your HH with ~~~~.... after that in 10 seconds connect your usb and phone to pics/ laptop during press volume download
Sent from my WT19i using xda premium
hi,
I have pretty much the same symptoms, my ray is seen as ST17i by flashtool.
Is this a flashtool bug or is it really recognized as ST17i?
Thank you!
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Siddharth121 said:
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
nroberto13 said:
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
Click to expand...
Click to collapse
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Mysteryagr said:
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
yes, I saw the topic, but none of the fices worked for me .
I haven't found anybody on the forum who was successful on a ray with any of the fixes .
any advise?
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
tried that, also flashed system once again, then system and kernel, but phone doesn't boot.
what does cm9/10 different to stock so it boots?
is this issue coming from kernel or from rom?
where are the touch driver placed? in initrd or in rom?
thank you!
Please Help. Please.
I am having WT19i. I have installed Super Jelly Bean 8.0 and having nAa 2.6 kernel. I flashed this kernel through flashtool. That time my device was shown correctly (I guess that means all the drivers are installed correctly). And I havent changed anything on my PC (Windows 7) or in flashtool (0.9.13.0) after that. Now I want to install some KK Rom in my phone. So when I connected my LWW, it shows connected device as Xperia Active (ST17i) instead of WT19i. For that KK Rom, I need to flash .587 stock.ftf file. But I fear if I try to flash, it will brick my phone. I wont get a new mobile in near future. So I dont want to brick it. Anyone please help me through this. How can I get the job done without getting bricked. It will be a great if anyone could tell me.
If I continue with flashing ftf with the current situation (WT19i recognized as ST17i), will it brick my WT19i?? If yes, how to overcome this situation?? Help needed from members. Please, its urgent. I am a newbie actually. This is my first post in xda. Thanks in advance.
Hi,
I've been trying to flash my Xperia SP to 12.0.A.1.257 as per the thread "How-to for rooting newest firmware 12.0.A.2.245".
I currently have 12.0.A.2.254 installed, and I understand that I need to flash my kernel to 12.0.A.1.257 to be able to root. Flashing to 257 seems to be successful, please see the log below.
<- This level is successfully initialized
Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
Device connected with USB debugging on
Connected device : Sony Xperia SP
Installed version of busybox : N/A
Android version : 4.1.2 / kernel version : 3.4.0-perf-g1285c6c-01110-g8395f64 / Build number : 12.0.A.2.254
Selected XperiaSP_C530X / 12.0.A.1.257 / KernelOnly
Preparing files for flashing
Please connect your device into flashmode.
Device disconnected
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Current device : C5302 - CB5123ZDXT - 1272-1094_R8A - 1269-3538_12.0.A.1.257 - INDIA-HSPA_12.0.A.2.254
Start Flashing
Processing loader.sin
Checking header
Flashing data
Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTABLE
Processing kernel.sin
Checking header
Flashing data
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
Later when I use the Rooting toolkit v17 to get root access I get the following.
Device detected: C5302 (12.0.A.2.254)
C5302 (12.0.A.2.254) is not supported.
Am I missing something here?
Thanks in advance.
Unable to flash Kernel on Xperia SP
isvicbhasme said:
Hi,
I've been trying to flash my Xperia SP to 12.0.A.1.257 as per the thread "How-to for rooting newest firmware 12.0.A.2.245".
I currently have 12.0.A.2.254 installed, and I understand that I need to flash my kernel to 12.0.A.1.257 to be able to root. Flashing to 257 seems to be successful, please see the log below.
<- This level is successfully initialized
Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
Device connected with USB debugging on
Connected device : Sony Xperia SP
Installed version of busybox : N/A
Android version : 4.1.2 / kernel version : 3.4.0-perf-g1285c6c-01110-g8395f64 / Build number : 12.0.A.2.254
Selected XperiaSP_C530X / 12.0.A.1.257 / KernelOnly
Preparing files for flashing
Please connect your device into flashmode.
Device disconnected
Device connected in flash mode
Opening device for R/W
Reading device information
Phone ready for flashmode operations.
Current device : C5302 - CB5123ZDXT - 1272-1094_R8A - 1269-3538_12.0.A.1.257 - INDIA-HSPA_12.0.A.2.254
Start Flashing
Processing loader.sin
Checking header
Flashing data
Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTABLE
Processing kernel.sin
Checking header
Flashing data
Ending flash session
Flashing finished.
Please unplug and start your phone
For flashtool, Unknown Sources and Debugging must be checked in phone settings
Device connected in flash mode
Device disconnected
Later when I use the Rooting toolkit v17 to get root access I get the following.
Device detected: C5302 (12.0.A.2.254)
C5302 (12.0.A.2.254) is not supported.
Am I missing something here?
Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my C5303
m trying to root my Xperia U but when I do that using Flashtool, it gives me an error. The log is below.
03/03/2014 08:30:02 - INFO - <- This level is successfully initialized
03/03/2014 08:30:03 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
03/03/2014 08:30:03 - INFO - Device connected with USB debugging on
03/03/2014 08:30:04 - INFO - Connected device : ST25
03/03/2014 08:30:05- INFO - Installed version of busybox : N/A
03/03/2014 08:30:07- INFO - Android version :4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.10
03/03/2014 08:30:10- INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/03/2014 08:30:15- INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\chattr : Not found
first i unlock boot loader of xperia u by using official method on sony website
then i try root xperia u by using flash tool and it give me above error
so plz help me to root my xperia u
and whan i select supersu mode then the process started normally
That's how the log ends?
U could 1st try this One
Good luck
[LB][JB] same problem
I just want to root my xperia P to remove some sony and google apps that I don't like,
but I've tried with a win8.1 and win7 pc and I have the same problem. Any solution?
Thanks in advance.
Superuser root package is broken, known bug
After flashing my LG G2 to many roms, I decided to do the same with my Z3V.
When i try to flash the Z3V using Flashtool i have been getting different errors.
Currently i have the Android version of 4.4.4 Build number- 23.0.E.1.44
What i want to do is to Flash it to the ship out version so i can root it and install 5.1.1
Here are the error messages i have been getting:
Error 1. First message i got was the drivers. Went in to Flashtool/drivers and install every single one of them. Seems to me working.
Error 2. the device does not recognize the command flashtool
Error 3. A device attached to the system is not functioning.
I have somehow went through these errors and got stuck on the very last one, which is:
Error 4. Error parsing TA file. Skipping
Any ideas?
Age you using Windows 10? Disable drivers signature and that should help.
running into the same damn problem----
flashed to 5.0.2, with an ungodly amount of programs, and finally got it running, to find out two weeks later that 5.1 is here and get get the update-
so now, im trying to DL 4.4.4 back onto the phone, but am running into
16/051/2016 02:51:43 - ERROR - Error flashing. Aborted
16/051/2016 02:51:43 - ERROR - Drivers need to be installed for connected device.
16/051/2016 02:51:43 - ERROR - You can find them in the drivers folder of Flashtool.
tried the z3 drivers- didnt work either. ****KK!!!!!!
goto .flashtool/firmwares/sinextracted and move everything in sinextracted to other place.
shashikiran said:
goto .flashtool/firmwares/sinextracted and move everything in sinextracted to other place.
Click to expand...
Click to collapse
nothing was in that directory except the ftf i put in there and one other one
gickles said:
running into the same damn problem----
flashed to 5.0.2, with an ungodly amount of programs, and finally got it running, to find out two weeks later that 5.1 is here and get get the update-
so now, im trying to DL 4.4.4 back onto the phone, but am running into
16/051/2016 02:51:43 - ERROR - Error flashing. Aborted
16/051/2016 02:51:43 - ERROR - Drivers need to be installed for connected device.
16/051/2016 02:51:43 - ERROR - You can find them in the drivers folder of Flashtool.
tried the z3 drivers- didnt work either. ****KK!!!!!!
Click to expand...
Click to collapse
Install drivers. Install them from Flashtool drivers folder.
I think I ran into this..try using an older version of flashtool, I used version 0.9.18.6
I can into the same problem and posted on another area here how I fixed it if you want to take a look at that. Thanks all
Oh, you must mean THESE lovely messages...
----
16/037/2016 23:37:34 - INFO - Device connected with USB debugging on
16/037/2016 23:37:34 - ERROR - Cannot identify your device.
16/037/2016 23:37:34 - INFO - Selecting from user input
16/037/2016 23:37:39 - INFO - Connected device : D66XX
16/037/2016 23:37:39 - INFO - Installed version of busybox : BusyBox v1.22.1 static (2015-03-10 14:51 +0100) multi-call binary.
16/037/2016 23:37:39 - INFO - Android version : 4.4.4 / kernel version : 3.4.0-perf-g285fd61 / Build number : 23.0.E.1.44
16/037/2016 23:37:39 - INFO - Checking root access
16/037/2016 23:37:39 - INFO - Root Access Allowed
16/037/2016 23:37:49 - INFO - Selected Bundle for Sony Xperia Z3 (D6603). FW release : 23.4.B.0.319. Customization : USA
16/037/2016 23:37:49 - INFO - Preparing files for flashing
16/040/2016 23:40:49 - INFO - Please connect your device into flashmode.
16/041/2016 23:41:03 - INFO - Device disconnected
16/041/2016 23:41:21 - INFO - Opening device for R/W
16/041/2016 23:41:22 - ERROR - Drivers need to be installed for connected device.
16/041/2016 23:41:22 - ERROR - You can find them in the drivers folder of Flashtool.
16/041/2016 23:41:25 - INFO - Start Flashing
16/041/2016 23:41:25 - INFO - Processing loader.sin
16/041/2016 23:41:25 - INFO - Checking header
16/041/2016 23:41:25 - ERROR - Processing of loader.sin finished with errors.
16/041/2016 23:41:25 - INFO - Ending flash session
16/041/2016 23:41:25 - ERROR -
16/041/2016 23:41:25 - ERROR - Error flashing. Aborted
16/041/2016 23:41:26 - INFO - Device connected in flash mode
16/041/2016 23:41:44 - INFO - Device disconnected
----
I was going at this for about an hour, and I finally got it to work. I experimented with a million different things. Let me tell you what I did that finally randomly happened to work:
1. Windows 7
2. Flashtool version 0.9.18.6 (it's an older version)
3. Device identified as an Xperia Z3 (D6603) (This doesn't matter. Choose the Z3 as it's the closest)
4. Installed ALL of the drivers in the /drivers folder
5. Proceeded to run the flashtool a total of 7 times. NOTE: UNCHECK THE CHECKBOXES FOR WIPE IN THE TOP-RIGHT
6. TRY MULTIPLE TIMES. It failed for me on 6 attempts... but the 7th attempt randomly succeeded and flashed me to 5.1.1.
Keep trying! It will work eventually, I promise! Good luck!:good: