After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
LuminousOne said:
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
Click to expand...
Click to collapse
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Didgesteve said:
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Click to expand...
Click to collapse
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I'm not sure what you're trying to do. If you want to flash a rom, you want flashmode, volume down (-) then plug in the USB. If you want fastboot it's volume up (+) then plug in the USB..
MTP driver is wrong, you need to uninstall it and re-install the sony driver. Windows chooses the wrong driver by default and you have to manually add it yourself to make it work.
Having said that you mentioned that you are getting ADB commands to work, so I'm confused, perhaps the google driver is in place, but the Sony one is not.
You need both, when the phone is in fastboot it's presented as a different device than when connected via ADB.
Hope that helps explain a bit.
But if you're having issues with the drivers, should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I had this problem before. My fault before was install drivers in usb-debugging mode, then a change to fastbook/flash, and then the phone is not recognized or connection properly - despite me thinking I had correctly installed the drivers.
Took me months to figure it out. Boot into windows, then connect your phone in all modes, flash mode, fastbook mode, standard, and usb debugging - and for each mode - install the Sony driver again.
The result will be, that for every mode - when you go to device manager - you won't see an exclamation mark. If you ever see an exclamation mark again - install the driver. You get the idea.
Regards,
I finally found the f**kin problem the invalid driver was hiding under "other devices" only when the phone was in fastboot mode. Basically I followed the instructions of user2021355 from here.
Start Windows in test mode (instructions)
download driver from https://developer.sony.com/develop/drivers/
in admin command prompt run adb reboot bootloader
if the above step failed, you have a problem with adb and the solution is something different
open device manager and carefully search for any errors. I found mine hidden under "other devices"
right click on the errored driver and choose update
choose browse my computer
select the driver you downloaded from step 2
verify if working by running fastboot devices and you should get a serial number
Didgesteve said:
should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
Click to expand...
Click to collapse
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
LuminousOne said:
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
Click to expand...
Click to collapse
Some banking and games apps don't like rooted phones.
Not sure about android pay.
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
same is when pointing to the drivers from here: https://developer.android.com/studio/run/win-usb
I ve the G8441
sheedy1900 said:
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
I ve the G8441
Click to expand...
Click to collapse
Add the driver manually.
Didgesteve said:
Add the driver manually.
Click to expand...
Click to collapse
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
LuminousOne said:
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
Click to expand...
Click to collapse
I think we have different ideas of what adding the driver manually is
sheedy1900 said:
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
Click to expand...
Click to collapse
i have the problem as you and I'm also on win10. can you share how you installed the fastboot driver?
the adb and mtp drivers work fine for me, just fastboot is not working
unsigned driver under W10
try this one
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Gesendet von meinem viennalte mit Tapatalk
I have the same problem with my Sony XZ1 Compact G8441.
'adb devices' shows my phone, after 'adb reboot bootloader' phone goes into fastboot mode (I think), the one with blue LED, but 'fastboot devices' does not show any connected devices. Same when pressing Volume Up or Volume Down while plugging the phone in.
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Tried installing through device manager, right-click on faulty 'Android' under 'Other Devices', update driver, browse to download location.
With 'Sony XZ1 Compact driver' it found no installable drivers.
With 'Sony Fastboot Driver' it found an installable driver but had an error. Error said something like 'Did not find "Android ADB Interface", installation failed'.
I tried figuring out what you guys meant by 'installing driver manually' but I don't understand. Is it what I tried above, or something else?
My goal is to be able to install TWRP, which needs an unlocked Bootloader first. I followed the instructions on the official Sony Website for that.
Sorry. Delete this.
Gnorv said:
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Click to expand...
Click to collapse
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Didgesteve said:
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Click to expand...
Click to collapse
No, that did not help. The same problem remains. Phone is recognized when powered on by 'adb devices' but not recognized after typing 'adb reboot bootloader' and 'fastboot devices'.
Thanks for your suggestion though.
I got the problem that no matter what i do i can't install the driver.
Booting windows 10 with driver check disabled does not solve my problem.
Once i selected the driver to install i end up with a questionmark in the device manager above the android device. Taking a closer look reveals that there seems to be no driver installed.....
Any advice?
I tried:
1. Booting with driver signature check disabled
2. Switching windows 10 into test Mode
I booted ubuntu from a live usb stick and went from there. That works like a charm without the need of installing any drivers
Both solutions do not work....
Related
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue
If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.
I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.
theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.
Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.
Subbed to refer to later when i have the N4
Sent from my Nexus S
jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later
I did the same thing and I cant get adb to see my device however fastboot will =/
Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.
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!
Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?