Related
This has been frustrating me for the past few days.
I wanted to flash the latest 4.0.A.2.368 firmware on my unlocked Arc. So I fired up FlashTool but it just wouldn't detect the phone in flash mode.
But I am able to fastboot on the device.
Suspecting that it might be due to a Windows driver issue, I downloaded and installed the x86/x64 Windows drivers from Step666's guide. But still no success.
I then re-installed both PC Companion and SEUS. I then noticed that SEUS could not detect the phone in flash mode as well.
For the past few days, I've reinstalled SEUS several times, tried many drivers from different links but still no luck. I've also tried all of the USB ports on my computer.
Anyone has any advice?
Edit: Oh, and if I select Help -> Check Drivers in Flashtool, it gives an OK response:
This can vary depending on your Operation system. My Win 7 doesn't find phone in fastboot but finds it with SEUS and flashtool. I've tried everything and nothing changes that fact for my x64 Win 7 installation.
Is the LED indicator green when you try to connect?
Raoa said:
This can vary depending on your Operation system. My Win 7 doesn't find phone in fastboot but finds it with SEUS and flashtool. I've tried everything and nothing changes that fact for my x64 Win 7 installation.
Is the LED indicator green when you try to connect?
Click to expand...
Click to collapse
I'm using x64 Windows 7 as well. It's a new setup (upgraded my rig recently) and I didn't have a problem with Flashtool in my previous Windows XP setup.
And yes, I connected the phone in flash mode correctly. The LED is blue.
hush66 said:
And yes, I connected the phone in flash mode correctly. The LED is blue.
Click to expand...
Click to collapse
Then you're in fastboot mode if the led is blue, not flashmode, and you use the back button while plugging the phone in.
XperienceD said:
Then you're in fastboot mode if the led is blue, not flashmode, and you use the back button while plugging the phone in.
Click to expand...
Click to collapse
Silly me. It's working now. I can't believe I was so stupid.
Hi everyone
Since i updated firmware from .42 to .62 via flashtool, i've got a weird behaviour when i plug my phone in Flash mode.
It's recognized as S1 boot download with a yellow triangle thingy, i installed usb flash drivers, now it's with SEMC Flash Device as hardware, then after 30s-1min it reboots and turns to SEMC HSUSB Device, a mass storage entity.
Can you help me fix this so i can access fastboot?
I reverted back to .42 via wotan, erase all drivers with usbdeview, plug it back, nothing works. I surely did something wrong but i can't spot it.
Tried on another pc, same behavior. Something's missing/corrupt in the phone.
i have a similiar problem, i cant access fastboot, message waiting for device, in device manager i cant install the driver cause it tells me not found.
Any Idea?
I was having strange problems when trying to install the drivers on a windows 7 PC. i had to install GordansGate drivers but it still didnt work. I ended up installing PDAnet or something and it installed all the correct drivers for me and using the latest version of flashtool i can do everything from there (flashtool, fastboot, adb)
i tried so much, but it wont recognize the driver -.- dont know what to do, every time when i try it with device manager->S1BootFastboot->install driver it tells me that my drivers directory are not the right drivers -.-
install this and run through the setup carefully and follow each step. this fixed my driver (not recognizing device) problems on my desktop
http://junefabrics.com/android/download.php
hope this solves your problems because i was going mad with mine for ages
ok solved my problem by installing flashtool and the flashtool drivers. now everything works fine
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Theonewithideas said:
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Click to expand...
Click to collapse
i have the same problem
francois90 said:
i have the same problem
Click to expand...
Click to collapse
Try switching the USB cable and USB port
Theonewithideas said:
Try switching the USB cable and USB port
still nothing ... if u can give me more instructions i'd appreciate it , ty
Click to expand...
Click to collapse
Rom and kernal: Project Jellyzeus r5 with Turbo kernel
done so far with no success.
install flashtools, install drivers in the driver folder in flashtool. Install sonys pc compaion installed driver from there.
The problem: when I boot phone in fastboot mode flashtool gives error Drivers need to be installed for connected device even trought both normal and adb drivers installed
The phone is recognize and working with flashtool in waken state but if I use trough flashtool to reboot to fastboot the same thing happens as if I boot it in fastboot.
Any suggestions?
xrint said:
Rom and kernal: Project Jellyzeus r5 with Turbo kernel
done so far with no success.
install flashtools, install drivers in the driver folder in flashtool. Install sonys pc compaion installed driver from there.
The problem: when I boot phone in fastboot mode flashtool gives error Drivers need to be installed for connected device even trought both normal and adb drivers installed
The phone is recognize and working with flashtool in waken state but if I use trough flashtool to reboot to fastboot the same thing happens as if I boot it in fastboot.
Any suggestions?
Click to expand...
Click to collapse
-Try rear usb ports (on motherboard)
-Exit PC companion and try again (rightclick on systray icon=>exit)
-Try uninstalling all drivers (go to device manager, connect phone(in normal,flash and fastboot mode), right-click => uninstall drivers). Disconnect phone and connect again. Let windows find drivers automaticly, if not, use flashtool drivers
-Try different usb cable
Bakisha said:
-Try rear usb ports (on motherboard)
-Exit PC companion and try again (rightclick on systray icon=>exit)
-Try uninstalling all drivers (go to device manager, connect phone(in normal,flash and fastboot mode), right-click => uninstall drivers). Disconnect phone and connect again. Let windows find drivers automaticly, if not, use flashtool drivers
-Try different usb cable
Click to expand...
Click to collapse
somehow switching to the rear usb ports solved it. thanks for all great advice!
Noob here!
I cant find android developement driver for xperia m c1904!!
Installing the latest PC Companion doesnt help.
where can i get the drivers from??
thnx in advance!
I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you
Hope hs answer helps... And just to add questions shouldn't be in the general section. We have a Q&A section for em
Sent from my C1905 using XDA Premium 4 mobile app
aleksa069 said:
I have here adb driver packed in, but if you are using Windows 7/8/8.1 you need first to disable Driver Signature Verification. Here is the link to show you how you do it:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
So after that, you normally install provided drivers, and I also provided a archive that contains extracted adb program, so you don't need to instal Andorid sdk.
Here is donwload link: https://www.mediafire.com/?j9xjn79lm3jkyv5
Hope I helped you
Click to expand...
Click to collapse
thanks, i will try too for my mikocok 8 64bit
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/
Hedzx said:
Hello,
PC companion works well and detect my phone but does not install any adb drivers...
I can't find ADB drivers for this phone anywhere where did you found these?
thank you.
Click to expand...
Click to collapse
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: http://adbdriver.com/downloads/
Click to expand...
Click to collapse
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)
mbc07 said:
I got from a PC Companion update. Make sure you have the latest version of PC Companion or reinstall it to fix that...
Unsigned drivers = major headaches to install in Windows 8+ since it'll accept only signed drivers unless you disable driver signature enforcement first (and M$ make that process more complicated in Windows 8+ than before)
Click to expand...
Click to collapse
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.
paper13579 said:
Lol, what are you on about. Please explain to me, what do you mean by unsigned drivers. I used that programme on windows 7 and the drivers work perfectly for me.
Click to expand...
Click to collapse
As I assume you've already worked out drivers can come in two forms, signed and unsigned.
Signed drivers are generally ones coming from manufacturers and have a valid signature bundled in with them.
Unsigned drivers are generally ones coming from external sources (like flashtool) and do not have a valid signature bundled with them or they don't have one at all.
In Windows 7 there is slight driver enforcement, when you try to install unsigned drivers a window pops up telling that they are unsigned and that you shouldn't install them. You still have the option to install them.
In Windows 8, 8.1 and 8.1 Update 1 there is strict driver enforcement. When you try to install an unsigned driver with driver enforcement on, it will fail. When you turn the driver enforcement off (which is a pain to do) and then try to install an unsigned driver you get the pop up window telling you that the driver is unsigned and that you shouldn't install them, you still have the option to install them however.
I hope this explains it for you.
ADB driver not recognised by Flashtool
paper13579 said:
Hey, just to add to the list of answers, here is an adb drivers installer. All you have to do is open the programme, plug in your phone and press install, then you are done.
Here is the download: [not allowed to post links]
Click to expand...
Click to collapse
I'm trying to revert to 4.2.2 from 4.3 to root my Xperia M dual 2005 that I received brand new today. I have spent four hours trying to get Flashtool to recognise that the phone is in USB debugging mode. It definitely is - USB debugging (and nothing else) is checked in Developer Options, USB connectivity is set to Mass Storage (not MTP) and installing from unknown sources is enabled in Security.
When I connect the phone powered up, this is what Flashtool shows:
10/051/2014 22:51:23 - INFO - <- This level is successfully initialized
10/051/2014 22:51:23 - INFO - Flashtool Version 0.9.16.0 built on 19-04-2014 19:00:00
10/051/2014 22:51:24 - INFO - This is the first sync with devices on github. Renaming devices to devices.old
10/051/2014 22:51:24 - INFO - Cloning devices from github project
10/052/2014 22:52:06 - INFO - Devices sync finished.
10/052/2014 22:52:13 - INFO - Device connected with USB debugging off
10/052/2014 22:52:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
10/052/2014 22:52:22 - INFO - List of connected devices (Device Id) :
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_01\7&4CF9BF6&0&0001 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B&MI_00\7&4CF9BF6&0&0000 Driver installed : true
10/052/2014 22:52:22 - INFO - - USB\VID_0FCE&PID_619B\YT910S4WK6 Driver installed : true
10/052/2014 22:52:22 - INFO - List of ADB devices :
10/052/2014 22:52:22 - INFO - - none
10/052/2014 22:52:22 - INFO - List of fastboot devices :
10/052/2014 22:52:22 - INFO - - none
But the notification area on the phone shows "USB debugging connected"!!!!!
To flash, I know I have to disconnect and turn the phone off, choose the .ftf then start the flash procedure (preparing files). Then when the animated graphic comes up, I press the volume down button and re-plug the USB cable back into the phone. Nothing happens - no lights on the phone, no flash starts, nothing. This is regardless of whether I keep the vol down button depressed for ages, or let it go after a few seconds.
I'm sure I have the ADB driver installed. I have the latest version of Sony PC Companion. I tried the ADB_Nicky method above from mbc07, using "have disk" and the driver seemed to install no problem. To double check I downloaded the file from the link given above by paper13579 and it detects the phone as a Sony Ericsson, and says the ADB drivers are already installed. I have also uninstalled the device in DM and restarted the PC and reinstalled the driver. Clip of Device Manager attached (as it appears when the powered-up phone is plugged in). Nothing appears in Device Manager when I try the flash procedure as above (phone off, vol down depressed).
I have been using Windows 7 Ultimate 32-bit, and (in desperation) XP SP3, with the same results. I've tried different USB cables (known good). I don't know what to try next.
@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...
Completed
mbc07 said:
@zumtotal, ADB drivers are different from flashmode drivers. Turn off your phone, hold Vol Down and plug USB. Go to device manager and see if you have a "SEMC Flash Device". If it show up with an exclamation mark or don't show at all, try reinstalling PC Companion or selecting "Have Disk" and then pointing to PC Companion folder in Program Files...
Please note that while in flash mode, if the phone doesn't receive any answer from the host computer within 2 minutes it'll automatically disconnect and restart the phone in normal mode, so, after plugging the phone while holding volume down you'll have approximate 2 minutes to do the driver install...
Click to expand...
Click to collapse
Thanks, mbc07, your answer helped. To cut a very long story short, I made two mistakes:
1. When I first enabled USB debugging on the phone I didn't have any data connection enabled (neither wifi nor sim). So when I connected the powered-up phone to the PC the phone didn't install the USB debugging feature properly. After I got data enabled, more installation took place, and eventually Flashtool recognised my phone correctly and saw that it was in debugging mode.
2. I didn't pull out and re-insert the battery to get the phone into flash mode (that is not included in Part 1 of paper13579's instructions in the main 4.3 rooting thread). So when I connected the powered-off phone with the vol down depressed I could see that nothing changed in Device Manager. After I pulled and replaced the battery, the phone was recognised as SEMC Flash Device and the driver installed.
Simple mistakes but they cost me hours. Hope this helps someone else.
mbc07 said:
Signed ADB drivers for Xperia M only come with very recent builds of PC Companion (even FlashTool 1.3 doesn't have this drivers currently). I managed to get only them from a local install, download the attached file and run DPInst.exe (or DPInst64.exe if running 64-bit OS). With this package you don't need to disable driver signature enforcement, they work out of box in Windows 8/8.1...
Click to expand...
Click to collapse
This works
great!! I will try this in win 8.1
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
ExisteRcz said:
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
Click to expand...
Click to collapse
if drivers are not installed properly.. Start Windows 7 or 8 or 8.1 in "Disabled Driver Sginature Mode" (Google this if you don't know how)
if you think drivers are installed correctly.. then do one think cuz I also face the same issue.. Don't connect the Device and then try to FLash by the electric signal..
first select the firmware .. click ok.. then let the software tell u.. to connect the Device.. do that and it should work !! let us know.
Drivers are "SEMC Flash Device" for "S1Boot Fastboot". And when i try to load kernel first when device is disabled it gives me this.
02/013/2015 12:13:21 - INFO - Device disconnected
02/013/2015 12:13:33 - ERROR - This action can only be done in fastboot mode
02/013/2015 12:13:41 - ERROR - This action can only be done in fastboot mode
02/013/2015 12:13:49 - INFO - Device connected in flash mode
02/013/2015 12:13:56 - ERROR - This action can only be done in fastboot mode
and i dont know how to flash via electric signal
Emma software from Sony works well for recovery my phone to original ROM and Kernel.
Maybe "back" button is stuck. Can you boot into android (doesn't matter is it custom rom or official firmware)
Also, try different usb port or different usb cable
Untill you found a solution you can flash custom kernels in .ftf format (you can flash them in flash mode)
Sent from my R800i using XDA Free mobile app
Bakisha said:
Maybe "back" button is stuck. Can you boot into android (doesn't matter is it custom rom or official firmware)
Also, try different usb port or different usb cable
Untill you found a solution you can flash custom kernels in .ftf format (you can flash them in flash mode)
Sent from my R800i using XDA Free mobile app
Click to expand...
Click to collapse
I dont think the "back" button is stucked. Cuz when i power off phone and holding back button and connect it gives me Green LED and when Search button its gives me Blue LED. Problem is not in phone but in Flashtool. If I have flash mode on phone devices shows me "S1Boot Flashmode" when fastboot "S1Boot Fastboot". I tryied all usb ports on my PC and 4 USB Cables (1 Original from XPlay and 3 others from different samsung phones) and Yea I can boot into android, and i tryied flash custom kernels in .ftf format but its always brick my phone and I must use Emma software for Revive the phone . Sorry my english is very bad
ExisteRcz said:
I dont think the "back" button is stucked. Cuz when i power off phone and holding back button and connect it gives me Green LED and when Search button its gives me Blue LED. Problem is not in phone but in Flashtool. If I have flash mode on phone devices shows me "S1Boot Flashmode" when fastboot "S1Boot Fastboot". I tryied all usb ports on my PC and 4 USB Cables (1 Original from XPlay and 3 others from different samsung phones) and Yea I can boot into android, and i tryied flash custom kernels in .ftf format but its always brick my phone and I must use Emma software for Revive the phone . Sorry my english is very bad
Click to expand...
Click to collapse
Yeah, it looks like phone is ok
Try to uninsatll all related drivers from PC (go to device manager, righ-click on driver, then "uninstall"). Do it when for all 3 modes (flash, normal and fastboot mode)
Then disconnect and connect phone again.
Or choose to manually install drivers for
Or reinstall flashtool
Bakisha said:
Yeah, it looks like phone is ok
Try to uninsatll all related drivers from PC (go to device manager, righ-click on driver, then "uninstall"). Do it when for all 3 modes (flash, normal and fastboot mode)
Then disconnect and connect phone again.
Or choose to manually install drivers for
Or reinstall flashtool
Click to expand...
Click to collapse
I tryied these so many times. I downloaded and tested 13 differents drivers but it has no effect still Flash mode . and i reinstalled flashtool too. I dont know what can be wrong.
ExisteRcz said:
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
Click to expand...
Click to collapse
ExisteRcz said:
I tryied these so many times. I downloaded and tested 13 differents drivers but it has no effect still Flash mode . and i reinstalled flashtool too. I dont know what can be wrong.
Click to expand...
Click to collapse
im using flashtool 0.9.10.1 and all seems fine.. try that
saqibkhan said:
im using flashtool 0.9.10.1 and all seems fine.. try that
Click to expand...
Click to collapse
Okay I downloaded uninstalled my flashtool, then uninstalled drivers, installed flashtool 0.9.10.1, then drivers from C:/Flashtool/drivers and installed just Xperia PLAY and fastboot drivers, then i connect device in fastboot (Blue LED) and it says "08/045/2015 11:45:32 - ERROR - Drivers need to be installed for connected device.
08/045/2015 11:45:32 - ERROR - You can find them in the drivers folder of Flashtool.
" but i installed them, so i installed them manualy i searched for them somewhere, from 3 drivers i selected Android Bootloader Interface but everytime it install Android ADB Interface so problem is in drivers i think.
ExisteRcz said:
Okay I downloaded uninstalled my flashtool, then uninstalled drivers, installed flashtool 0.9.10.1, then drivers from C:/Flashtool/drivers and installed just Xperia PLAY and fastboot drivers, then i connect device in fastboot (Blue LED) and it says "08/045/2015 11:45:32 - ERROR - Drivers need to be installed for connected device.
08/045/2015 11:45:32 - ERROR - You can find them in the drivers folder of Flashtool.
" but i installed them, so i installed them manualy i searched for them somewhere, from 3 drivers i selected Android Bootloader Interface but everytime it install Android ADB Interface so problem is in drivers i think.
Click to expand...
Click to collapse
if you are using Windows 8 or 8.1 .. try going into "Disable Signature mode for Drivers" in advanced startup and then try installing the Drivers !!
btw I install ADB drivers from the ADB package.. that is in the folder Fastboot and ADB Package\Drivers\google-usb_driver
try this.. but install in the mode I told u above.. uninstall the previous devices.. and when it Says Confirm Uninstall theirs a small box below that telling u "delete Drivers" and Uninstall.. tick that.