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
My PC keep showing error messages when im flashing my xperia sp .
it said that : ERROR -
- ERROR - Error flashing. Aborted
-ERROR - Drivers need to be installed for connected device.
-ERROR - You can find them in the drivers folder of Flashtool.
-INFO - Device disconnected
-INFO - Device connected with USB debugging off
I already used the adb installer software and it said that the driver had been installed.
The USB debugging is on .
Help meee! Im running Windows 8 . :crying::crying::crying::crying::crying:
In windows 8 theres a diffrent method to install unsigned drivers
http://forum.xda-developers.com/showthread.php?t=2303046
Hope this helps
Install the drivers using this method
Win 8 is the problem.
Try this thread http://forum.xda-developers.com/showthread.php?t=2544270
Sent from my C5303 using xda premium
hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.
avila188 said:
hello, i want to use the flashtool but it keep asking to plug in the phone. i turned it off, and press volume down while connecting already.
Click to expand...
Click to collapse
Sounds like you may need to install the flashtool-specific drivers. In your flashtool directory, there should be a "drivers" folder where you can install the flashtool (and fastboot)-specific drivers. I don't know if you need to have the latest version of flashtool (since this phone is still kind of new) to get a more appropriate driver set.
Also if you are installing these drivers in Windows 8 & up, you will likely have to install them while Driver Signature Enforcement (or whatever its called) is disabled. That method can be found easily via google search.
ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode
avila188 said:
ok i installed the driver from the drivers folder. plugged the phone, recoqnised, but write up the following error:
20/030/2015 07:30:31 - ERROR - Processing of loader.sin finished with errors.
20/030/2015 07:30:31 - INFO - Ending flash session
20/030/2015 07:30:31 - ERROR -
20/030/2015 07:30:31 - ERROR - Error flashing. Aborted
20/030/2015 07:30:31 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
ok i installed all drivers, and it works.
now i flashed already and got the latest build, and my telstra apps are all gone! woohoo! i suppose now my phone is like unlocked and sony version ( no carrier)?
thanks to the uploader at
[FTF] STOCK FIRMWARES for D5803 & D5833
one thing tho, when i want to delete app shortcut, the x location is now at the top, not at the bottom on the apps shortcut. is this what you all have?
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