Related
Hello,
I wanted to root my new Sony Xperia T and I found this http://forum.xda-developers.com/showthread.php?t=1886460.
However I needed to install the ADB drivers and I am having extreme difficulties in doing so. From my limited knowledge on the subject I guessed that the ADB drivers are installed when I plug my phone into my computer. When I plugged my phone in windows installed two drivers. When I then went into device manager to see if my phone was registered as an android device but it wasn't. It was instead listed as a portable device. I also tried running
Code:
adb devices
but this ended up with an empty list. Despite this my phone appears in My Computer and I can transfer files to and from it easily.
After looking on the internet for a while I found I needed a few things installed. So I removed the drivers, installed the Android SDK with SDK-tools and the Sony PC companion as well as turn my phone to USB debugging. I then retried windows installed the same two drivers and it again was listed as a portable device.
I looked up this issue and found suggestions to restart the SDK-tools ADB server, restart my phone, update drivers, unlock my phone and install PDaNet. These all ended with the same result. I also found a suggestion to update the drivers by going into the Android SDK and using the driver in there. This didn't work though as Windows said the current version of the driver is the most up to date. I tried various techniques suggested to get around this but I was unable to.
Any help on how to install these drivers is greatly appreciated. My phone is about a month old, unrooted, Sony Xperia T (LT30p). My computer runs Windows 7 Professional 64bit.
Thanks,
JamesStewy
(I may have forgotten some of the things I tried to get it to work yesterday so please suggest anything )
Download flashtool and install the drivers from the driver folder in there. They are the only drivers I ever install.
Use the Tx, flashmode and fastboot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
It was kind of nightmarish to get the phone recognized for me as well. I managed to solve it (after may trials and errors) by manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105...
Hello gregbradley and Arcano. Thanks a lot for your replies.
manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105
Click to expand...
Click to collapse
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Download flashtool and install the drivers from the driver folder in there.
Click to expand...
Click to collapse
Sorry for being a bit of a n00b but what is a flashtool and where do I get it? Also, same as previous, I can't find anyway of overriding drivers (I have gone through about three pages of google but can't find a solution that works for me).
Thanks again for your replies,
JamesStewy
JamesStewy said:
Sorry for being a bit of a n00b but what is a flashtool and where do I get it?
Thanks again for your replies,
JamesStewy
Click to expand...
Click to collapse
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section.
It should be the first thing you download when you get an xperia device.
EDIT
No need to post your thanks. If you feel the need to express gratitude to anyone on xda just their thanks button
JamesStewy said:
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Click to expand...
Click to collapse
The way I did it was to plug the phone in, wait till the automatic driver installation failed, and then in the device manager I selected the phone and went thru the "update drivers" procedure. You must select the specific folder where that driver is, not the parent, or windows won't detect it. In my case that folder is named
C:\Program Files (x86)\Sony\Sony PC Companion\Drivers\{2CD1390C-A74E-434A-B652-73D3683B3BEF}
which is quite a weird name; just look for the folder with sa0105* drivers inside, and that's the one.
By the way, I never had a "WPD composite device". This is how it is shown now in device manager:
The way I did it was to plug the phone in, wait till the automatic driver installation failed
Click to expand...
Click to collapse
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section. It should be the first thing you download when you get an xperia device.
Click to expand...
Click to collapse
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy
JamesStewy said:
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy
Click to expand...
Click to collapse
¿Could it be that you have two phones detected?, as my pc only shows "Xperia T", no trace of "LT30p"; and the adb driver is in a category of its own.
I have no idea. I only have one thing connected to my computer which is my phone. I don't have an adb, Sony or android node in device manager at all.
JamesStewy
I don't know what else to tell you then. You might try uninstalling the LT30p, and forcing the upgrade to the pccompanion drivers I talked about before. But this is a wild guess, I can't really help you any further.
It's your adb installation correct. Have your added it to the path in environment.
Do you have usb debugging on in settings on your phone.
What was the error when you installed the flash tool drivers
What dies flash tool say when you attach the phone whilst it is open.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
I have never heard of this issue and just installing flash tool and/or pccompanion is enough to install all the drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
It's your adb installation correct. Have your added it to the path in environment.
Click to expand...
Click to collapse
I am not sure. Is the adb installation part of the Android SDK platform-tools? If so I think it is. I can use all the commands such as adb devices but this returns and empty list. And yes it is in my PATH environment variable.
Do you have usb debugging on in settings on your phone.
Click to expand...
Click to collapse
Yes.
What was the error when you installed the flash tool drivers
Click to expand...
Click to collapse
When you say install, what do you mean? If you mean the process I described in a previous post then I get the message attached (untitled2.png).
going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder (or any other folder with appropriate drivers) -> Next -> Windows Message (attached file).
Click to expand...
Click to collapse
What dies flash tool say when you attach the phone whilst it is open.
Click to expand...
Click to collapse
Is the flash tool called EMMA or something? I downloaded it of Sony's site here: developer.sonymobile.com/services/flash-tool/. If so I can't get in because I am still waiting for a confirmation email.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
Click to expand...
Click to collapse
When I uninstall them and plug my phone back in the drivers on the phone install to my computer. Pictures attached. These drivers have nothing to do with ADB and only allow Windows to transfer files to my phone.
JamesStewy
No, flashtool I'd found in the first post in the development section.
Please download it, install it, and ruin the driver.exe found in the driver folder of flashtool in the installation path.
Install the Tx, flash mode and fast boot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145
That's where I looked. Can you post a link.
JamesStewy
you sure you looked properly
http://forum.xda-developers.com/forumdisplay.php?f=1801
the very first thread. The link is in the very first post
EDIT
If you google "flashtool" and click I feel lucky it takes you straight to the flashtool homepage...
Xperia T - adb problems
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me
Hi laplada27,
Thanks for your reply. When I get home today I will give that a go.
Thanks,
James
Solution
laplada27 said:
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me
Click to expand...
Click to collapse
YES! It worked
Thank you so much.
James
Installing drivers 8.1
I am trying currently to update my T, it has an unlocked bl that I did when I first got it in Dec 12.
I am running w8.1 64 bit.
Tried both mass storage mode & mtp mode.
I have the latest 64 bit version of flashtool installed.
I am trying to flash the 295 generic ce ftf android 4.3 update, no problems with the ftf itself.
The error flashtool spits out is that the drivers are not installed, either the adb or flashmode drivers.
I have repeatedly tried to install the drivers that come with flashtool, and it appears that they install, but
there are a few that won't, I think namely the above.
I note that when I have device manager open, it detects the T, when plugged in in flashmode (i.e. turned off, with volume down)
as an s1boot device. I have intercepted device manager several times when it does this, in order to try and update the drivers
by hand, but no luck.
When I first plugged the T in in flashmode mode, it installed some drivers automatically, however, not ones that will allow flashtool
to work.
In truth I am now scratching my head as to what to do next.
I never had any problems with w7 64 ultimate flashing the T, solid as a rock, all the drivers would install as required, and I am
thinking the easiest way to update my T would be to use a w7 based machine, however, if anyone has any more ideas as to
what might help me flash it using 8.1 then I would be very grateful to hear them.
TheGSL
I think there is a patch for Windows 8.1... Search the forum and you will find it.
Good luck!
cant able to flash kernel in my pc (xp) as my laptop is not working.using the latest version of flashtool installed all the drivers including gg and i may have done something to the drivers as i wanted tethering in winxp which i was not able to .any help on this matter would be good.my mobile is being recognized by pc
04/033/2013 19:33:39 - INFO - Opening device for R/W
04/033/2013 19:33:39 - INFO - Start Flashing
04/033/2013 19:33:39 - INFO - Processing loader
04/033/2013 19:33:39 - INFO - Checking header
04/033/2013 19:33:39 - INFO - Ending flash session
04/033/2013 19:33:39 - ERROR -
04/033/2013 19:33:39 - ERROR - Error flashing. Aborted
04/033/2013 19:33:40 - ERROR - Drivers need to be installed for connected device.
04/033/2013 19:33:40 - ERROR - You can find them in the drivers folder of Flashtool.
04/033/2013 19:33:41 - INFO - Device disconnected
Make sure the drivers are all installed, and that your USB cable is not jerky or anything.
Yea you need x8 driver.
Sent from my E15i using xda app-developers app
everthing is good and i installed the drivers from the folder and also gordons gate
reinstall flashtool and at the same time reinstall the drivers from the folder directory, that should solve it
@op pcc installed? just reinstall gg and keep trying. that often happens to me too.
reinstalled everything but still the same error ......pcc is not installed
nanda_123 said:
reinstalled everything but still the same error ......pcc is not installed
Click to expand...
Click to collapse
install pcc. there are drivers there that are needed. then reinstall gg and try a few times. hope it works.
cascabel said:
install pcc. there are drivers there that are needed. then reinstall gg and try a few times. hope it works.
Click to expand...
Click to collapse
yes it helped..first had to install pcc companion and then reinstall it for installing the drivers and after that it was detected by flashtool but was not able to flash and then a pop up of semc flash connected came win installed the drivers and i am done..thank u for u help
hello
Few minutes ago ive been trying to install new FW for xperia t suddenly flashtool says that i dont have drivers for my phone. So ive installed drivers for flashmode,fastboot and xperia t /tx from flashtool folder. however problem still exists. does anyone have solution for it.
thanks in advance
oh damn, not a single word about your running OS
let me guess? win8, 8.1? if you have linux/ubuntu based available, i would suggest you to use flashtool,fastboot,adb on linux. if you only have win8/8.1. then you should search our xperia T forums, there are several posts about problems. there are problems with driver certification or other stuff like that since win8. if i remember right somehow i got all working on win8, but since i have win8.1, i switched to linux for android stuff^^
if i find the way i got it working on win8, then i edit my post.
best for the average pc user would be to use win7. my opinion.
Oh sorry i forgot about OS. So im running on Win XP SP 3.
misiex2212 said:
Oh sorry i forgot about OS. So im running on Win XP SP 3.
Click to expand...
Click to collapse
Try a older version of Flash Tool,see if that helps. Also close any running processes you don't need before you install Flash Tool.
can someone provide link for older ver of flashtool. and about processes running in background i have only those needed by windows
Logs from flashtool. i get same error everytime im trying to flash it
16/027/2014 14:27:28 - INFO - <- This level is successfully initialized
16/027/2014 14:27:28 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
16/027/2014 14:27:36 - INFO - Device disconnected
16/027/2014 14:27:40 - INFO - Selected Bundle for Xperia T (LT30P). FW release : 9.2.A.0.295. Customization : Vodafone UK
16/027/2014 14:27:40 - INFO - Preparing files for flashing
16/029/2014 14:29:17 - INFO - Please connect your device into flashmode.
16/029/2014 14:29:25 - INFO - Opening device for R/W
16/029/2014 14:29:26 - INFO - Start Flashing
16/029/2014 14:29:26 - INFO - Processing loader.sin
16/029/2014 14:29:26 - INFO - Checking header
16/029/2014 14:29:26 - INFO - Ending flash session
16/029/2014 14:29:26 - ERROR -
16/029/2014 14:29:26 - ERROR - Error flashing. Aborted
16/029/2014 14:29:26 - ERROR - Drivers need to be installed for connected device.
16/029/2014 14:29:26 - ERROR - You can find them in the drivers folder of Flashtool.
Install the Flashmode, Fastboot and TX drivers from the flashtool/drivers directory
Mad Marty said:
Install the Flashmode, Fastboot and TX drivers from the flashtool/drivers directory
Click to expand...
Click to collapse
i have installed them already. ive tried with several usb cables and nothing.
I've had some issues with the .14 version of Flashtool that you seem to be using
I wasn't able to flash anything.
Worked like a charm though when using my brothers laptop, that is running an older version of Flashtool
So maybe using you should try an older version of it
problem solved.
ive used flashtool 0.9.9.0 however problem seems to be with busybox as ive installed it again and now is flashing without problems
The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.
Astralogic said:
The instant I enter flashmode the flash fails. Here is my log:
Code:
29/032/2014 09:32:24 - INFO - <- This level is successfully initialized
29/032/2014 09:32:24 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
29/032/2014 09:32:28 - INFO - Device connected with USB debugging on
29/032/2014 09:32:29 - INFO - Connected device : Sony Xperia T
29/032/2014 09:32:29 - INFO - Installed version of busybox : BusyBox v1.20.2-Stericson (2012-07-04 21:33:31 CDT) multi-call binary.
29/032/2014 09:32:29 - INFO - Android version : 4.1.2 / kernel version : 3.4.0-g5b052b2-00814-g976ab37 / Build number : 9.1.A.1.141
29/032/2014 09:32:29 - INFO - Checking root access
29/032/2014 09:32:30 - INFO - Root Access Allowed
29/033/2014 09:33:49 - INFO - Selected Bundle for LT30p. FW release : 9.2.A.1.199. Customization : Generic UK
29/033/2014 09:33:49 - INFO - Preparing files for flashing
29/033/2014 09:33:54 - INFO - Please connect your device into flashmode.
29/034/2014 09:34:03 - INFO - Device disconnected
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:04 - INFO - Opening device for R/W
29/035/2014 09:35:04 - INFO - Start Flashing
29/035/2014 09:35:04 - INFO - Processing loader.sin
29/035/2014 09:35:04 - INFO - Checking header
29/035/2014 09:35:04 - INFO - Ending flash session
29/035/2014 09:35:04 - ERROR -
29/035/2014 09:35:04 - ERROR - Error flashing. Aborted
29/035/2014 09:35:04 - INFO - Device connected in flash mode
29/035/2014 09:35:15 - INFO - Device disconnected
Any ideas what could be wrong or what I can do?
Thanks
Edit: I tried uninstalling the phone from Device Manager, but that had no effect. When the flash fails I see a popup in the corner saying this device malfunctioned/is not recognized.
Click to expand...
Click to collapse
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.
Antiga Prime said:
1.- Are you sure you have the right FTF for your phone model?
2.- Are you sure the FTF file isn't corrupted? (download again)
3.- Are you sure the proper drivers are installed (install them from the "drivers" folder in the Flashtool folder).
4.- Are you sure your USB cable isn't damaged and is disconnecting while flashing (try a different cable).
I think I've read that excluding the TA partition and/or BASEBAND might help. Don't take my word for it, Google it first.
Click to expand...
Click to collapse
1 - I have an Xperia T and this is the FTF I 'm trying to flash.
2 - Yes, I have re-downloaded from a mirror.
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
I have no idea how excluding the TA partition and/or the baseband. I'll read up about it and see if it helps.
I even used the full unroot option in SuperSU, just so I could try to update the official way but it still didn't work.
Astralogic said:
3 - That installer doesn't include drivers in it's list for Xperia T, the Xperia TX drivers failed to install, I tried them to see if they would work.
Edit: In flashtool, exclude baseband is clearly labelled, but exclude TA partition is not. I can exclude "partition", is that it? Or could it be the "FOTA" option?
4 - The cable isn't causing the problem. Tried another.
Click to expand...
Click to collapse
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?
Antiga Prime said:
No, if you don't see the exclude TA, then the FTF doesn't have the "simlock.ta" file in it.
You should use the TX drivers. If you haven't installed drivers at all, then that is clearly an issue. You could try with this driver pack, but the drivers that come with Flashtool should work.
What error do you get when installing the drivers?
Click to expand...
Click to collapse
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.
Astralogic said:
Here's a screenshot of the error.
But when I attempt to install the drivers you linked to above, the top driver (Sony(WinUSB), above Sony Net) in the Device Driver Installation Wizard window has a green tick next to it. The bottom one, Sony Net, still has a red X next to it.
Click to expand...
Click to collapse
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.
Antiga Prime said:
Correct me if I'm wrong, but it seems like you're using Windows 8. You need to disable driver signature enforcement, either by doing this, or Googling another method (there are several).
Notice that drivers have been extracted to the temp folder (check your screenshot); I'd copy that driver folder to somewhere else, just to have it on hand, and that way it's easier to install the drivers manually through the Windows Device Manager, something you'd need to do after disabling the driver signing, and something I'd do anyways regardless if you're on Windows 8 or not; if drivers don't come with a specific software (such as Nvidia or ATI drivers) then it's always possible and in some cases easier to just add the driver manually through the Device Manager.
Click to expand...
Click to collapse
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.
Astralogic said:
I got the drivers installed succesfully by disabling driver signature verification and running the installer, but I still get the same error in flashtool. I really thought that was going to fix it.
Click to expand...
Click to collapse
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.
Antiga Prime said:
Open the Device Manager and check if you have any devices with a yellow exclamation mark/warning. Aside from that, try a computer with Windows 7, maybe?
If not, and considering that you get a "this device has malfunctioned" error in Windows, and it's not your USB cable, then your USB port on either your phone or computer might not be working properly.
Click to expand...
Click to collapse
The bad news is it didn't work
The good news is I got more info this time
Take a look at this screenshot, it's definitely some time of driver issue, something called S1boot fails to install: Screenshot.
That is AFTER the successful installation of the TX drivers in the drivers folder, these errors occur the instant my phone enters flashmode.
Edit: Forgot to mention this was on another PC, running Windows 7.
Edit 2: Just to clarify, the instant my phone entered flashmode, the computer tried to install those drivers.
Edit 3: I found this, I'm about to try it. Fingers crossed.
Edit 4: Those drivers didn't work. In Windows 8, I right click the INF and it installs, but no success on the flash. In Windows 7 I get a message that this INF does not support this method of installation. There are no devices with a yellow exclamation in device manager on either computer ;(
OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?
Astralogic said:
OK I managed to update the firmware using Sony Update Server program, now I constantly get the message android.process.media has stopped working. I tried to use an app called Rescan Media Root to disable the media scanner but it didn't work. The message is relentless, the phone is unusable because of this damn message
Maybe it's occurring because I disabled some system app or something?
Click to expand...
Click to collapse
Most likely you didn't wipe data, A.K.A. Factory Reset.
Antiga Prime said:
Most likely you didn't wipe data, A.K.A. Factory Reset.
Click to expand...
Click to collapse
You're right. But I fixed it by clearing the data for Download Manager and Media Manager (or something like that).
I am going to downgrade my X Perf from N to MM to do a TA backup and then upgrade again, but I have reached a rather annoying snag and I don't know if I'm doing something wrong. I am using Flashtool version 0.9.23.0, so it should work with the phone, but I still have to choose the phone every time, it doesn't read it from the bundle. And every attempt on the 4-5 ROMs I've tried so far gives me the error messages:
Code:
26/022/2016 09:22:46 - INFO - No loader in the bundle. Searching for one
26/022/2016 09:22:53 - INFO - No matching loader found
26/022/2016 09:22:53 - WARN - No loader found or set manually. Skipping loader
26/022/2016 09:22:53 - INFO - Ending flash session
26/022/2016 09:22:53 - ERROR - null
26/022/2016 09:22:53 - ERROR - Error flashing. Aborted
From what I can find out the problem is that there is no loader.sin in the firmwares I download. So far there hasn't been one in any of them! I have tried downloading on two different computers, and the same result all the time. Can anybody please tell me what I am doing wrong here? Or if the loader.sin is supposed to be taken from somewhere else. I haven't found anything about that in any of the "how to" threads I've seen.
same problem here..
First of all ensure Flashtool's drivers are properly installed on your system (windows 8/8.1/10 video guide)!
Also, you can try using an older version of Flashtool (0.9.18.6) to flash MM ftf. And ofc the new one for N.
The loader.sin is not part of ftf anymore, see MM and N ftf contents I've created and flashed successfully:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Mastiff said:
Serajr, thanks! I will make another attempt. And I have read your posts too, but didn't find a solution to this. Does this mean that Flashtool has to read the loader from the phone it's flashing, then?
Click to expand...
Click to collapse
Exactly, that's why drivers must be properly installed!
And just in case...
If you want a recovery too, go for this one (multirom-20161218-recovery-fota-dora.zip). It is weird, but official twrp for dora does not work!!
To flash it, unpack the zip and flash its image with this fastboot command (just after you unlock your device's bootloader):
fastboot flash recovery twrp.img (after OK messages, unplug usb cable to turn device off).
Now you must enter on recovery (mandatory, otherwise you will need to flash twrp again), to do that: press Power and Volume Down buttons simultaneously, and release only the Power buttom when sony logo appears.
While on recovery ignore/disable any multirom function (unless you want it).
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
26/033/2016 14:33:16 - WARN - No loader found or set manually. Skipping loader
26/033/2016 14:33:16 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTABLE
26/033/2016 14:33:16 - INFO - Max packet size set to 4M
26/033/2016 14:33:16 - INFO - USB buffer size set to 512K
26/033/2016 14:33:17 - INFO - Parsing boot delivery
26/033/2016 14:33:30 - INFO - No flash script found.
26/033/2016 14:33:30 - INFO - Flash script is mandatory. Closing session
26/033/2016 14:33:30 - INFO - Ending flash session
26/033/2016 14:33:30 - INFO - Flashing finished.
26/033/2016 14:33:30 - INFO - Please unplug and start your phone
26/033/2016 14:33:30 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
26/033/2016 14:33:30 - INFO - Device connected in flash mode
26/033/2016 14:33:48 - INFO - Device disconnected
Click to expand...
Click to collapse
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Mastiff said:
Well, I got one step further! I had misunderstood about the drivers, I thought it refered to the same driver as the ADB driver... But now I got to this:
I did choose not to use an FSC script as you said, but does that have anything to do with the reason for this failure, or is there something else going on here?
Edit: I'm still trying to downgrade to MM so I can backup the TA. I selected to wipe everything except the TA, and I excluded the TA, which I understood that I should do. Is there something I should have done while converting the file?
Click to expand...
Click to collapse
Did you do this?
Code:
26/033/2016 14:33:30 - INFO - For flashtool, [B][U]Unknown Sources[/U][/B] and [U][B]Debugging[/B][/U] must be checked in phone settings
Yep. I started the phone and checked that it was done after that fail, and both were set to on. Some of the first things I do on a phone, Titanium backup needs those settings to work. Of course it also needs root, which I do not yet have...
Edit: It is USB debugging that it means, right? Under Developer options?
I tried to start the phone again and authorize the pc for USB debugging (never had to do that before on any phone), but it didn't change anything.
Yep, it is!
Well buddy, things are starting to become tough. Try this:
- Turn your device off and keep it disconnected from usb
- Open Flashtool and start the MM flash process (choose firmware, etc...)
- Click on flash button. The message to connect your device in flash mode will pop up
- Now connect your phone to the usb while pressing Volume Down button (and do release it after flash process begins)
Ofc I can also being forgetting something, so please, anybody else reading to this thread, comment on!
Edit: On ftf creation I've also ignored FSC script! Did you?
Edit 2: Let windows recognizes your device into flashmode. With Flashtool closed (and others windows apps too), also with your device turned off, connect it to the usb with Volume Down (flashmode) button pressed. Is everything ok, did windows recognize it?
Do the same after you unlock the bootloader, with Volume Up (fastboot), and type in a windows command prompt: fastboot devices
Well, I installed the drivers again, just to test. But one thing: I only found the common drivers, and not a driver that worked specifically for the X Performance. Can that be the problem? I thought it would be in this version of Sony Mobile Flasher. Also I see a few errors in device manager. It's named "SOMC Flash Device", but under the Information part I see:
Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated.
Click to expand...
Click to collapse
So is this still a driver issue? I looked through the list in the drivers installation program, but didn't see any driver for this phone. So I only get two drivers, the Google Inc. Win USB and Sony Mobile Communications ggsomc. I am probably missing something, right?
Edit: Not sure if I skipped the FSC script, but I'm making a new bundle now and will try with that to see if I may have forgotten to skip it on creation this last time.
Nope, new bundle didn't help. Also I found an old howto that said;
NOTE: If your list of files includes “fwinfo.xml” as highlighted below then manually delete it before continuing to the FlashTool steps. You MUST delete this file otherwise your FTF firmware file will corrupt.
Click to expand...
Click to collapse
But that was from 2014, so I do assume that this has been fixed.
And to continue the stream of info, this is not the firmware, it seems. I tried with a different firmware (Nougat for Nordic Countries) and it went just like with the Polish Marshmallow.
I have an idea for a last attempt: I will reset the phone to factory, do a very quick setup to where I get USB debugging and unknown sources and then try again.
Ok, download this one from sony and unpack it.
Now add hardware manually and point to the *.inf file (there should be at least 3 options to install).
Edit: "Device USB\VID_0FCE&PID_ADDE\5&2c705bfe&0&1 could not be migrated." << I have this too, and everything works!
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Nope, same error from both flash attempts and the driver file when using Windows 7. I do not have a Windows 7 32 bit device anywhere near, I'm afraid.
Mastiff said:
Thanks! But I get a message that there are no drivers compatible with Windows 64 in that file. Weird, because it actually says that it does on that page. Maybe it just isn't compatible with Windows 10, I will try it on a Windows 7 computer I have here.
Click to expand...
Click to collapse
This is the inf file and all x64 (and 32) contents from my android sdk folder. Try pointing to this one!
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Mastiff said:
This is very strange, if those drivers worked on your system. Still the same thing, no compatible driver, check that any drivers in the directory are made for Windows 64 bit systems (roughly translated from Norwegian). But it is the SOMC Flash Device that I should use this driver on, right? In that case I have no idea why that's happening here.
Click to expand...
Click to collapse
It is weird indeed! I think so, and I really don't remenber the right one, maybe Android Composite ADB interface.
Windows 7 things are much easier, but it must work on 10 as well! Hope you succeed!!
Edit: For further info to unlock device's bootloader > https://www.youtube.com/watch?v=iIdJg7KNH3A