Related
Hello,
My problem is the following:
- If I connect my phone when it's on, it works just fine.
- If I connect it in fastboot mode (blue led) it isn't recognized. So i installed the drivers manually (after disabling the need for driver signature) and it said drivers were installed. But it still doesn't work propperly. In device manager my phone now gets recognized as Android ADB interface but there's still a yellow triangle there with an exclamation mark and in properties it says: Device doesn't start. (Code 10)
A request for the USB BOS descriptor failed.
When I try using flashtool (0.9.9.0) it says:
26/010/2012 15:10:00 - INFO - <- This level is successfully initialized
26/010/2012 15:10:00 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
26/010/2012 15:10:00 - INFO - You can drag and drop ftf files here to start flashing them
26/010/2012 15:10:05 - INFO - Device connected in fastboot mode
26/010/2012 15:10:10 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
26/010/2012 15:10:11 - INFO - Device Status: NOT FOUND
26/010/2012 15:10:21 - ERROR - This action can only be done in fastboot mode
26/010/2012 15:10:24 - ERROR - This action can only be done in fastboot mode
26/010/2012 15:10:26 - INFO - Device Status: NOT FOUND
26/010/2012 15:10:29 - INFO - Finished Fastboot Toolbox
Any ideas on how I can solve this because it has been driving me crazy for 2 days now.
Thanks
Windows 8 fastboot drivers
XperienceD said:
Windows 8 fastboot drivers
Click to expand...
Click to collapse
It may surprise you but I know how to google.
I have been looking for the past 2 days but nothing in those threads works.
The way I see it is that after installing the drivers like they explain here, here or here, it should work. But it still doesn't.
JWKow said:
It may surprise you but I know how to google.
Click to expand...
Click to collapse
The point is your not the first with the issue and you could have posted your issue on two of the three threads you've linked to. If all the suggestions aren't working then you're doing something wrong.
JWKow said:
Hello,
My problem is the following:
- If I connect my phone when it's on, it works just fine.
- If I connect it in fastboot mode (blue led) it isn't recognized. So i installed the drivers manually (after disabling the need for driver signature) and it said drivers were installed. But it still doesn't work propperly. In device manager my phone now gets recognized as Android ADB interface but there's still a yellow triangle there with an exclamation mark and in properties it says: Device doesn't start. (Code 10)
A request for the USB BOS descriptor failed.
When I try using flashtool (0.9.9.0) it says:
26/010/2012 15:10:00 - INFO - <- This level is successfully initialized
26/010/2012 15:10:00 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
26/010/2012 15:10:00 - INFO - You can drag and drop ftf files here to start flashing them
26/010/2012 15:10:05 - INFO - Device connected in fastboot mode
26/010/2012 15:10:10 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
26/010/2012 15:10:11 - INFO - Device Status: NOT FOUND
26/010/2012 15:10:21 - ERROR - This action can only be done in fastboot mode
26/010/2012 15:10:24 - ERROR - This action can only be done in fastboot mode
26/010/2012 15:10:26 - INFO - Device Status: NOT FOUND
26/010/2012 15:10:29 - INFO - Finished Fastboot Toolbox
Any ideas on how I can solve this because it has been driving me crazy for 2 days now.
Thanks
Click to expand...
Click to collapse
Had the same problem, could not get it running and kept on getting the " A request for the USB BOS descriptor failed" error on the usb device.
In the end the solution was simple and something that can only happen on Windows....
Follow the instructions in thread http://forum.xda-developers.com/showthread.php?t=1575100&page=2 exactly.
You will find that you still have the same problem.
Then connect the phone to a different usb port (preferably one that uses a different internal port) or add a USB hub in between.
In my case it worked instantly.
Hope this will help you.
Thanks man.
I'll try it tomorrow. I managed to do it by using an old windows xp laptop but it would be nice if I got it to work on Win 8.
Sent from my Xperia Arc using xda app-developers app
Windows 8 fastboot drivers
And I had problems with Windows 8, so I switched the keyboard cro to eng and
time zone in Montevideo, for example.
Then everything was working, flash tool, S1 tool, Update service, etc.
SONY ERICSSON Xperia arc S
I installed the drivers fine by turning off device signing, however still had an issue with the flashmode not recognising the device was connected.
The solution for me was just to connect the phone via a usb port on the PC itself (as opposed to connecting it via a USB port on the PC's monitor).
mikecamimo said:
The solution for me was just to connect the phone via a usb port on the PC itself (as opposed to connecting it via a USB port on the PC's monitor).
Click to expand...
Click to collapse
Woohoo! I connected via a usb on the rear side of my pc and it worked! Thanx!
Alright so, earlier today I rooted my phone and everything was fine, so just a bit ago I wanted to install a custom rom from fastboot. For whatever reason, I was unable to do it via ADB in flashtools(just rebooted me back into system when I tried), so I tried it manually (hold volume up and then plug in usb) - at first it told me I needed drivers, so I went into flashboot's driver installer and reinstalled Ion, fastboot, and flashmode drivers. Unfortunately (just like the first time I installed the drivers) the "Google USB" failed to install. However, the Ion driver installed successfully, and now instead of saying I need drivers, it will say "27/036/2013 17:36:06 - INFO - Device connected with USB debugging off
27/036/2013 17:36:06 - INFO - For 2011 devices line, be sure you are not in MTP mode" and if I click check drivers, it'll give me this: "27/036/2013 17:36:10 - INFO - List of connected devices (Device Id) :
27/036/2013 17:36:10 - INFO - - USB\VID_0FCE&PID_6DDE\6&DF2EE03&0&6 Driver installed : true
27/036/2013 17:36:10 - INFO - List of ADB devices :
27/036/2013 17:36:10 - INFO - - none
27/036/2013 17:36:10 - INFO - List of fastboot devices :
27/036/2013 17:36:10 - INFO - - none"
Am I bricked, or stuck in fastboot or something? Hopefully someone can help me, thanks.
(P.S - I have an Ion LT28at and am on unmodified except for root AT&T ICS)
iKat said:
Alright so, earlier today I rooted my phone and everything was fine, so just a bit ago I wanted to install a custom rom from fastboot. For whatever reason, I was unable to do it via ADB in flashtools(just rebooted me back into system when I tried), so I tried it manually (hold volume up and then plug in usb) - at first it told me I needed drivers, so I went into flashboot's driver installer and reinstalled Ion, fastboot, and flashmode drivers. Unfortunately (just like the first time I installed the drivers) the "Google USB" failed to install. However, the Ion driver installed successfully, and now instead of saying I need drivers, it will say "27/036/2013 17:36:06 - INFO - Device connected with USB debugging off
27/036/2013 17:36:06 - INFO - For 2011 devices line, be sure you are not in MTP mode" and if I click check drivers, it'll give me this: "27/036/2013 17:36:10 - INFO - List of connected devices (Device Id) :
27/036/2013 17:36:10 - INFO - - USB\VID_0FCE&PID_6DDE\6&DF2EE03&0&6 Driver installed : true
27/036/2013 17:36:10 - INFO - List of ADB devices :
27/036/2013 17:36:10 - INFO - - none
27/036/2013 17:36:10 - INFO - List of fastboot devices :
27/036/2013 17:36:10 - INFO - - none"
Am I bricked, or stuck in fastboot or something? Hopefully someone can help me, thanks.
(P.S - I have an Ion LT28at and am on unmodified except for root AT&T ICS)
Click to expand...
Click to collapse
I guess that's just a minor soft brick.
How about force restarting it ?
Press and hold the power button and volume up button at the same time
5 seconds > restart phone
10 seconds > shutdown phone
Nabeel. said:
I guess that's just a minor soft brick.
How about force restarting it ?
Press and hold the power button and volume up button at the same time
5 seconds > restart phone
10 seconds > shutdown phone
Click to expand...
Click to collapse
Worked. I feel like an idiot for not trying that before - I knew how to force shutdown but when I did it I didn't do it for 5 seconds as I was panicing. Anyways, any help in terms of the fastboot? Thanks alot though, either way.
iKat said:
Worked. I feel like an idiot for not trying that before - I knew how to force shutdown but when I did it I didn't do it for 5 seconds as I was panicing. Anyways, any help in terms of the fastboot? Thanks alot though, either way.
Click to expand...
Click to collapse
Happy you got it working
Restart your PC and everything, start fresh,
And just follow the manual method of connecting.
Hold down volume UP key while connecting it to PC and the LED light should turn blue.
Also install the drivers once again. Go to C:/ > Flashtool > drivers > fastboot drivers > install
Hope it helps
Nabeel. said:
Happy you got it working
Restart your PC and everything, start fresh,
And just follow the manual method of connecting.
Hold down volume UP key while connecting it to PC and the LED light should turn blue.
Also install the drivers once again. Go to C:/ > Flashtool > drivers > fastboot drivers > install
Hope it helps
Click to expand...
Click to collapse
Ugh, it just keeps turning on and going to the "charging" screen. Any tips, as this is extremely aggravating?
(I was successfully able to install the drivers btw, by disabling driver signature enforcement - I'm on Windows 8 :I)
iKat said:
Ugh, it just keeps turning on and going to the "charging" screen. Any tips, as this is extremely aggravating?
(I was successfully able to install the drivers btw, by disabling driver signature enforcement - I'm on Windows 8 :I)
Click to expand...
Click to collapse
Try on Windows 7 and also use 2.0 USB port
And one thing i think i should have asked you before. Is your bootloader unlocked ?
Yo need an unlocked bootloader to perform fastboot actions
Nabeel. said:
Try on Windows 7 and also use 2.0 USB port
And one thing i think i should have asked you before. Is your bootloader unlocked ?
Yo need an unlocked bootloader to perform fastboot actions
Click to expand...
Click to collapse
Ah, crap, there's my problem. I don't think the ATT version's bootloader is unlockable unless I were to pay someone with a kit (did it with my play) if there are any people that do it with the Ion, could you link someone to me?
iKat said:
Ah, crap, there's my problem. I don't think the ATT version's bootloader is unlockable unless I were to pay someone with a kit (did it with my play) if there are any people that do it with the Ion, could you link someone to me?
Click to expand...
Click to collapse
I sent you a private messag when i last replied you ( Asking about rom and etc)
see it and i really have no idea about any such someone mate.
As far as i know, you can't unlock the bootloader of locked phones
Unlocked then locked
Nabeel. said:
I sent you a private messag when i last replied you ( Asking about rom and etc)
see it and i really have no idea about any such someone mate.
As far as i know, you can't unlock the bootloader of locked phones
Click to expand...
Click to collapse
I bought an xperia ion some time ago and when i bought it, i could boot to fastboot mode, i rooted it and installed the cwm recovery for it, and was doing fine, then i dont remember what happened but i had to restore, so i flashed the genaric lt28h version via flashmode. then for a while i was stuck without root because the root script was not working, i tried to boot to fastboot mode and was not able, i checked my phones bootloader status and it said it was locked, but i was able to boot to fastboot before, but now i am no longer able. any ideas as to what happened?
thanks
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,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Did you already disable driver signing? Pretty sure you have to do that with Win 10. I would disable driver signing, and then use " 15 second adb installer" from XDA. Always has worked for me...
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Abrucci said:
Hey there,
so fastboot does not recognize my phone in bootloader mode.
USB Debugging is enabled.
- ADB Commands work
- Fastbootd Mode and Fastbootd Commands work (adb reboot fastboot)
However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)
Drivers are Installed.
- I have an AMD Processor and i am aware of the issues. I tried the USB controller fix.bat without any changes.
- I have disabled Driver Signature in Windows 10, still nothing
Please help :/
Click to expand...
Click to collapse
How does it show in Device manager?
sd_shadow said:
How does it show in Device manager?
Click to expand...
Click to collapse
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Abrucci said:
*However in Bootloader Mode it just does not show up. Either under Windows or Linux (No Device Manager, No LSUSB, Nothing)*
Click to expand...
Click to collapse
Try a different usb cable