Hi,
I just extracted the latest USB driver (USB_Acer_1.0_USB_A700 A701), but there are Windows XP, Vista and 7 drivers inside only.
i tried to install the Windows 7 driver on Windows 8 64-bit, but had no success...
The one that isn´t working is the "USB composite device" driver.
I need any Acer Windows 8 USB 64-bit drivers for Android 4.0...
Will Acer release a Win 8 driver for the A700 in near future?
Hi,
You should try installing the Android SDK, which has general Android drivers inside them.
Connect your Acer device onto your computer.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Now click with the right mouse button on Computer, click Manage. Go to Device Manager. Right click Acer A700, click update driver software.
Choose "Browe my computer for driver software". Choose "Let me pick from a list".
Click all devices or/and Have disk..
Go to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\ and click the file under the 2 folders (android_winusb.inf)
Click on the first one and install.
Good luck and let me know if you succeed.
Edit:
You can skip the first part and download the Google USB driver I uploaded:
http://www55.zippyshare.com/v/1434863/file.html
Thank you very much it worked for me!
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
theoldfarter said:
Thanks for the re-upload but there appears to be a problem with the contents of the zip file. When I try to extract it, I get this message: " the archive is either in unknown format or damaged". Could you download it yourself, or anyone,& see if you get that message.
Cheers.
EDIT: Thanks Tom for re-uploading again. It extracted OK this time. Unfortunately, I have had to send my A510 tablet in for repair, the charge light stopped working. I must admit to some ignorance in what to do with the unzipped files, as there is no installer for it, unlike a typical install of a USB driver. Perhaps you, or anyone, could educate me a bit?
Click to expand...
Click to collapse
Sure thing,
I explained it a little in my previous post, but I will try to explain it a little better this time.
1. Click with the right mouse button on Computer.
2. Click Manage.
3. Go to Device Manager.
4. Right click Acer A700 (or A510, OR anything that looks like an unknown android device), click update driver software.
5. Choose "Browe my computer for driver software". Choose "Let me pick from a list".
6. Click all devices or/and Have disk..
7. Go to the (extracted) folder you used from my upload in the previous post (usb_driver) and click the file under the 2 folders (android_winusb.inf)
8. Click on the first one and install.
Now Windows will recognise your tablet.
If you still don't get the hang of it, check out this video I found on Youtube:
https://www.youtube.com/watch?v=RbXatmo4QBU
The video may seem a bit dull, but it's actually useful if you really can't find any of the things I explained.
In the video, the "woman" explains on how you can find the Device Manager, on another way I explained.
Follow the instruction in the video until Step 8, which means you shouldn't follow step 8 but continue from my instruction from step 5.
Good luck!
Ps. If you really really don't get to install it, I would like to offer to do it for you (no charge, if that even was a question), if you trust a complete stranger on the internet (but you can abort any time). Just PM me.
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
theoldfarter said:
Thanks. I will do this when my A510 returns from repair. It is waiting for a part to arrive from overseas, so don't know when it will return.
Click to expand...
Click to collapse
The A510 has returned. I have tried to install your driver but have no success.
At step 6, I get presented with "Show All Devices". I am shown a list of Manufacturers & Models. I choose nothing & click "I Have Disk".
I navigate to your folder & click on android_winusb.inf
I then click on "Install From Disk" button. I am then shown the option "Select The Device Driver You Want To Install For This Hardware".
There are 3 items shown: 1. Android ADB Interface, 2. Android Bootloader Interface, 3. Android Composite ADB Interface.
I choose number 1 as that is the one I beleive you mean in your option 8.
I click "Next" & get a warning about "Installing This Device Is Not Recommended Because Windows Cannot Verify That It Is Compatible With Your Hardware". I continue the install & after about a minute, I get this message "Windows Found Driver Software For Your Device But Encountered An Error While Attempting To Install It"... and..."Android ADB Interface".... and...."This Device Cannot Start (Code 10)".
The Device Manager now shows Unknown Device as "Android Phone".
Await your reply but am thinking about reinstalling Windows 7 & leaving Win 8 until I get a touch screen laptop & Acer Tablets get a USB driver for Win 8. Acer say they are on the way but can't/won't give me a date.
Windows 8 is an annoyance on my 4 year old Asus N50Vn laptop.
Without drivers, can you still access the SD?
@theoldfarter
That's odd, but can you try choosing the third option: 3. Android Composite ADB Interface.?
Maybe the drivers I uploaded are out of date in Windows 8 and you should try installing the Android SDK.
Install the Android SDK and once the program has started, it'll (down)load and show you all the Android versions and tools.
Make sure you have only selected the checkboxes "Android SDK Platform Tools" and "Google USB driver". Now click on the right bottom button labeled: "Install packages".
Select the radio button: "Accept All" and click "Install".
Click to expand...
Click to collapse
(android_winusb.inf) will be available at the following location:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
troun2000 said:
Without drivers, can you still access the SD?
Click to expand...
Click to collapse
Yes, you can. I just tried it with my freshly installed Windows 8 machine.
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Mmm... you lost me there.I have no idea what you mean.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
Googled it & now know what you mean. That option is for Windows 7.
I use windows 8 & Google tells me this about it:
"7) Disable driver signature enforcement
The Disable driver signature enforcement option allows non-signed drivers to be installed in Windows 8.
This startup option can be helpful during some advanced driver troubleshooting tasks."
I will try this but when I tried installing the driver as per Tom's instructions, the driver in question said it was digitally signed.
misterkusut said:
You can try install driver from Advance Boot Options. Select no.6: disable driver signature
I am succeed on Cyrus ATOMPAD.
Click to expand...
Click to collapse
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
TomONeill said:
That won't work 'cause the driver can be installed, only it's not starting.
Do you have USB Debugging turned on in the Developer Options?
Click to expand...
Click to collapse
Did not have that turned on. Done so but makes no difference. I have just discovered that my built-in camera is not working with Win 8, Skype says there is no camera installed. It worked with Win 7. I am thinking that the "unknown" device in Device Manager is the camera, not my tablet.
No wonder I can't install the driver to it. lol.
With the tablet not connected, I uninstall the "unknown" device & then scan for changes & it shows it again.
It looks like the A510 is not recognised by Win 8 as anything, period.
I have had enough of Windows 8. It is causing more problems than it is worth. In a couple of days, I will reinstall Windows 7 & start over.
Will report back when all has finished, which may be in 6 days time.
Thanks for your help so far.
A700, mass storage and Windows 8
Hi
I have installed the USB drivers aa told here, an device manager shows my A700 under Android Phone.
But i cant see the storage.
How can i access both internal storage and SD card on my tablet??
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
I would like this link as well. Since I've updated my a510 to JB 4.1.2, my computer doesn't detect it when I plug it in via USB. I can plug a USB stick into the tablet and it sees that, but when connecting to PC, nothing at all. USB debugging is also turned on. Would love some assistance with this.
http://www55.zippyshare.com/v/1434863/file.html
This is the USB driver.
When clicking on start and entering "device manager", a new screen will pop-up showing you all the connected devices. Somewhere you should see Unknown, Fastboot, ADB, Android device/phone, A700 or Acer. Install it with the USB driver.
Note for everybody:
If it is NOT working, try to find Android Phone in the categories list when installing the driver. That one might work too if my solution doesn't work.
dis method helped me...!
theoldfarter said:
@TomONeil
Tried the third option: 3. Android Composite ADB Interface but get same error message.
Downloaded the Android SDK from your link & followed your instructions but get the same error message with both option 1 & 3.
I am wondering if it has to do with the A510 being upgraded to Jelly Bean (4.1.2)?
Here is a fellow who has Jelly Bean & Windows 7, where once he had updated to Jelly Bean, his Win 7 doesn't see the tablet anymore. His name is papyb & his post is the second up from the bottom, on page 2 here: EDIT, can't post the link. Darn the rules. lol.
I will try to PM you the link.
Click to expand...
Click to collapse
try this link... http://www.fotoclubinc.com/blog/how-to-disable-driver-signature-enforcement-to-allow-installation-of-windows-7-printer-drivers-on-windows-8/
install the drivers with signature verification off
i too had the same problem on my xperia device
its solved now. :good:
Related
hello all,
i had some small trouble setting up adb for my viewsonic gtab, so once i figured it out i thought i'd share.
so far, this is confirmed working only on windows 7 32 and 64 bit. vista should be the same, but i'm not sure, i'll keep you posted. EDIT: we've confirmed these steps for at least vista 32 and xp 32-bit. there shouldn't be any differences between the 32 and 64 bit systems as far as the instructions go.
most of my information comes from nvidia's tegra site, here. that's a pretty technical-minded page though, so i wanted to condense it.
make sure usb debugging is turned on for your tablet (settings -> applications -> development -> usb debugging)
1. open your device manager (right click My Computer -> Manage -> Device Manager)
if you haven't done anything to set up drivers yet, skip to step 4.
2. find your gtab. depending on your previous attempts, this may be under "Android Phone" at the top (Android ADB Interface, make sure it's your tab and not your phone), or under "Universal Serial Bus controllers" on the bottom (called Android somethingorother. should be at the top of the list.)
3. uninstall it. right click, uninstall. check the box that asks you if you want to delete driver software. i didn't need to use usbdeview to uninstall the drivers, but if you're running into issues on this step try it. usbdeview must be run as administrator, thanks droidjunkie.
it looks like most people should just skip right to usbdeview to uninstall any old drivers. like i said, i didn't have any issues using windows' "delete driver software" option, but apparently i was just lucky. rcgabriel recommends usbdeview, and he knows stuff.
4. unplug, and plug your tablet back in. now your device should be under "Other Devices" near the middle (will have a yellow exclamation icon, called NVIDIA harmony). good.
5. hopefully you have the android sdk installed. if you don't, go find a generic guide on setting up adb and then come back. when you have the sdk installed, you need to run "SDK Setup.exe" from where you installed it and use it to download and install the usb drivers (currently r8).
6. open the "usb_driver" folder in your sdk directory. right click "android_winusb.inf" and open it with notepad or your favorite text editor.
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
8. go back into device manager. right click your tablet, select update driver, and click "browse my computer...", then "let me pick...", then "next", then "have disk"
if you're confused on this step, check this post.
9. browse to your android sdk, under the usb_driver folder, and select the "android_winusb.inf" file.
10. of the three choices, the bottom should say "Android Composite ADB Interface". choose it. click next, and allow the driver to install even though you get a big scary red warning.
11. open a command prompt, preferably in the tools directory of your sdk. type the following:
Code:
echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini"
and hit enter. it will just return a new prompt line.
12. test it out.
Code:
adb kill-server
adb devices
you should see your device's serial number. all is well. congrats.
let me know if i should add or clarify anything here. thanks!
Just in case anyone doesn't know what ADB is:
http://developer.android.com/guide/developing/tools/adb.html
Thank you so much! Great info!
this is great! thanks for the concise writeup
I had trouble too. I was unable to get uninstall device to work and put the device under Other devices. I was advised to use usbdeview from pershoot. I used this program to remove the device and was able to get it moved to Other devices in Device Manager.
HTH
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
THANK YOU!!! after trying many different guides this one worked...other then the fact that I had to right click usbdeview and click "run as administrator" in order to delete the driver it keep installing when i would plug in my tab. I am on windows 7 32 bit, for anyone else having problems getting adb working that is using windows 7.
Thanks
I am finally connected via adb.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
I had the same experience on Windows 7 that you are having now. Like you, I tried following all the instructions similar to the ones listed above plus advice from other forums and still could not get it to work. I was finally able to get mine working after I discovered Windows still had some drivers from previous failed attempts stored in its system files. These old drivers were interfering with the proper installation of the new usb driver.
To get rid of the old drivers completely, do a file search for the file named android_winusb.inf in your Windows/System32/DriverStore. If your search results show several file folders with the same driver, try to delete each of the those folders completely. After those folders are deleted, you can do a clean install following iammuze's instructions.
NOTE: To delete those folders you will have to change the folder permissions. It won't be easy to do, because Windows doesn't like having its system files messed with. Unfortunately, I can't give you exact instructions on this, because I don't currently have a Vista machine.
rlapela said:
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Click to expand...
Click to collapse
where does your gtab show up under device manager?
Thanks, it worked great! ADB screen shots!
Look at this mess I have crammed onto one page.
[UPDATE: Problem solved: I had two versions of adb in my PATH and the old version (1.0.20) was being executed instead of the new version (1.0.26). Apparently the old adb silently fails and returns no devices when used in conjunction with the current drivers. I worked this out by accident. But if you're looking for ideas, there are lots in the ADB for Dummies thread: http://forum.xda-developers.com/showthread.php?t=502010 ]
Hi All
I've been banging my head against this for hours with no luck. I can't get adb to recognise my gTablet. Here's what I've done:
I'm on WinXP. gTablet is running zTab Clean 3.0
- I've downloaded the latest ADB USB drivers using the Android tools (driver verion 4.0, December 12 2010).
- I've made the modifications to android_winusb.inf noted above.
- USB Debugging is enabled on the gTab
- adb_usb.ini contains a single line containing: 0x955
I've followed various instructions and the driver install ~seems~ to go ok, but adb doesn't work.
Windows Device Manager lists the following devices which are associated with NVIDIA Harmony:
Android Phone > Android Composite ADB Interface
Universal Serial Bus controllers > USB Composite Device
Universal Serial Bus controllers > USB Mass Storage Device
USBDeview lists three devices:
NVIDIA Harmony NVIDIA Tegra 2 USB Device
NVIDIA Harmony USB Mass Storage Device
NVIDIA Harmony Android Composite ADB Interface
The first is listed as connected. The others aren't.
When run adb i get this:
> adb kill-server
> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
No devices are listed.
I have tried many combinations of uninstalling these devices (with Device Manager and with USBDeview). When I reconnect I get prompted to install drivers. I have tried installing at this point, cancelling and then installing in Device Manager, not cancelling so the Plug and Play window stays open and uninstalling with device manager. None of this has worked. Also the device drivers seem to linger on my machine as they seem to auto-reinstall even after I have uninstalled them (I've also tried the suggestion of searching and deleting the .inf and .dlls from C:\Windows -- that didn't work out either).
I have also been careful to make sure adb is not running when I change the drivers. I have tried rebooting the computer and the gTablet after various installs.
The only way I can get the gTablet to appear in "Other devices" is to plug the device in (the PnP window pops up, I leave it open and ignore it). Then I delete the drivers in USBDeview. Then I unplug and replug the gTablet. Now there is one device in "Other devices": NVIDIA Harmony. Problem is, if I right-click "Update driver..." it won't let me install from the Android .inf, it says "The specified location does not provide information about your hardware." and forces me to install "USB Composite device". Once that's installed, two more NVIDIA Harmony devices appear in "Other devices". The first requires me to install "USB Mass Storage Device" (once again won't accept the .inf). The third does allow me to install "Android Composite ADB Interface". That gets me to the point where the drivers are loaded as listed above. But adb still lists no devices.
When I first started trying to set this up I had old drivers for the original HTC android phone installed. I deleted these with USBDeview.
I think that's all the information I have. Please let me know if you have any suggestions, I'd love to get this working.
Thanks!
A real plus would be screenshots, I'm getting a little confused at the device manager window, especially the part where it's supposed to give you the option "let me pick" > "have disk" > locate the .inf > choose the last of the three choices
I'm not getting any of those windows/options. Also, when I uninstall it, unplug the gTab, and plug it back in, it just re-installs the default Tegra driver. Any help?
Right now my device is showing up under "Disk Drives" as "NVIDIA Tegra 2 USB Device", and then also under "Portable Devices" as "G:\"
EDIT: Fixed! (Sorta)
I found another forum that told me that in Device Manager, select "Add Legacy Hardware" from the "Action" menu. After going through there, I was able to complete the steps you told me to. If anybody's having the same problem I had before, I am using Windows 7 64-bit, so that may be part of the problem? I'm not sure. But it's installed now and in Device Manager it's under the "Android Phone" section as "Android Composite ADB Interface".
However this raises a new problem, it has a yellow triangle with an exclamation mark over the icon, and it comes up with the error "Error code 10: Device cannot start".
Any help?
you edited the .inf file to contain the three lines specified, and selected the modified driver when adding the driver, correct? i'll try to add some screenshots for the dev manager section
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Hi,
FYI, one thing to be careful of: In the thread where there's info about adding the 3 lines to the .inf, there's also a full .inf file.
If you try to use the full .inf file, note that it has references to various DLLs, which may, or may not match the DLLs in the driver install directory, so, if you use that full .inf from the thread, you have to adjust those DLL references to the ones for the DLLs you actually have on your machine.
In my case, I found it easier to just add the 3 lines to the .inf that came when I installed the USB driver files from the Android development website, which then worked.
Just an FYI...
Jim
iammuze said:
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Click to expand...
Click to collapse
THIS IS PIVOTAL... This is where I had the hang up. Make sure that you are looking at iammuze's pic here, especially the 2nd image. by default most of us are used to just pointing to the correct directory where we DO have the modified .ini and it grabbed the wrong one. You HAVE to select 'let me pick'
Thank you iammuze for pointing this out. I think that's where most get lost. It haunted me for weeks as I was just 'skinning' through directions and missed this important step!
Just a quick suggestion - instead of trying to hunt around and fix drivers that are already installed and broken, I highly suggest using USB Deview (http://www.nirsoft.net/utils/usb_devices_view.html) which lets you nuke out the old drivers easily on a Windows Vista/7 machine.
I had old ADB drivers from my Nexus One sitting around, and I was unable to uninstall stuff with Device Manager.
Just run USBDeview **as administrator** if you are on Windows Vista/7 and you can uninstall old drivers for USB devices with a single click (in this case, just nuke any old Harmony drivers or other ADB drivers). Then the next time you plug in your G Tab, you should be able to select the proper drivers as suggested in the first post.
doesn't work
So i have also been trying for days and can't get it working right.
Running Windows Vista, have ADB installed, and can connect to other Android devices. I have setup the android_winusb.inf properly, but when I connect my device it shows up in Device Manager as a Portable Device->Tegra.
I have uninstalled the tablet and every other android device using usbdeview as admin
I have searched and destroyed all other usb.inf files.
i am running VEGAn-1.0.5B
No matter what happens, as soon as I plug in the tablet it immediately installs it as a Tegra Portable.
any help is appreciated!
that's very odd, i haven't seen that device description before. it doesn't sound like a vista issue... do you have another computer with vista on it anywhere that you can plug your gtab into? just to see what it reports to dev manager on a super clean system.
Old drivers were conflicting from previous installation attempts for me as well. All is working well once USBDeview was finally able to uninstall the device, however, it took multiple attempts and reboots for it to actually remove them. All is well now, and my Device is connected to the ADB. Thanks Everyone!
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!
MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?
MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?
MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder
Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.
Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk
JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)
Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.
Since the last windows update from this week windows cant detect my nexus 5. I tried everything. It keeps showing up like "Unknown USB Device (Device Descriptor Request Failed)" And i doesn't show up immediately when i plug in the phone. It takes like 10 seconds, then it shows that with a yellow triangle.
Hope that someone can help me. There is also a thread on Reddit (/r/Nexus5) about this.
hhamzah49 said:
Since the last windows update from this week windows cant detect my nexus 5. I tried everything. It keeps showing up like "Unknown USB Device (Device Descriptor Request Failed)" And i doesn't show up immediately when i plug in the phone. It takes like 10 seconds, then it shows that with a yellow triangle.
Hope that someone can help me. There is also a thread on Reddit (/r/Nexus5) about this.
Click to expand...
Click to collapse
It would help to know what "everything" you have tried.
rootSU said:
It would help to know what "everything" you have tried.
Click to expand...
Click to collapse
uninstall every driver related to android. Uninstall every usb driver. Reinstall everything. Try every sort of install. Install via toolkit. Nothing worked.
I tried other cables, doesnt work. Other computer. On other computers it does work (which arent updated to the latest windows). But the problem isnt something in the hardware because it really started after the update.
none ??
In Device Manager, click on the yellow triangle and then uninstall the driver. Once done unplug the phone and then plug it back in again... Windows should then install the correct driver.
Here's something else to try...
http://androidcowboy.com/2013/11/install-nexus-5-drivers/
If either of those doesn't work you could try a System Restore to a date before the update. Then when Windows update pops up again have a look at what it wants to install to see if you can figure out what caused the problem, then right click and select Hide Update.
hhamzah49 said:
none ??
Click to expand...
Click to collapse
are you on window 8 / 8.1?
samersh72 said:
are you on window 8 / 8.1?
Click to expand...
Click to collapse
8.1 with latest updates
@CitizenLee
already tried that, the problem is that it doesnt recognize it as nexus 5.
hhamzah49 said:
8.1 with latest updates
@CitizenLee
already tried that.
Click to expand...
Click to collapse
uninstall driver and do this:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) Click Update and Recovery ;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.
samersh72 said:
uninstall driver and do this:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) Click Update and Recovery ;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.
Click to expand...
Click to collapse
Thanks for your quick answer. Didnt help. It still shows up at device manager as "Unknown USB Device (Device Descripter Request Failed)"
If i try to update driver software via device manager it tells me it failed to update with Code 10.
Tried phone on my old laptop with windows 7 and it immediately connected as Nexus 5.
hhamzah49 said:
Thanks for your quick answer. Didnt help. It still shows up at device manager as "Unknown USB Device (Device Descripter Request Failed)"
If i try to update driver software via device manager it tells me it failed to update with Code 10.
Tried phone on my old laptop with windows 7 and it immediately connected as Nexus 5.
Click to expand...
Click to collapse
take a look here:
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
i suggest Universal Naked Driver http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
samersh72 said:
take a look here:
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
i suggest Universal Naked Driver http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Thanks for your quick answer, doesnt work though. When i choose the extracted Universal Naked Driver it tells me that it already has installed the latest drivers for this device.
hhamzah49 said:
Thanks for your quick answer, doesnt work though. When i choose the extracted Universal Naked Driver it tells me that it already has installed the latest drivers for this device.
Click to expand...
Click to collapse
did you follow steps in mentioned link?
try this also http://forum.xda-developers.com/showthread.php?t=2588979
Here try this:
Make sure android sdk with platform tools and usb_driver is installed on your PC and then,
Follow these steps:
1. Connect your phone to your pc and head over to control panel---device manager and select your phone from there.
2. Right click on it and select update driver software.
3. Now select "Browse my computer for driver software"
4. Put this path "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" (C:\Program Files (x86) may differ on your pc depending on where you have installed the SDK)
5. Put a tick on "Include subfolders" and click next.
6. The drivers will be installed again and everything should work now.
Make sure you accept the authorization request popup on your device when you connect to your PC.
vin4yak said:
Here try this:
Make sure android sdk with platform tools and usb_driver is installed on your PC and then,
Follow these steps:
1. Connect your phone to your pc and head over to control panel---device manager and select your phone from there.
2. Right click on it and select update driver software.
3. Now select "Browse my computer for driver software"
4. Put this path "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" (C:\Program Files (x86) may differ on your pc depending on where you have installed the SDK)
5. Put a tick on "Include subfolders" and click next.
6. The drivers will be installed again and everything should work now.
Make sure you accept the authorization request popup on your device when you connect to your PC.
Click to expand...
Click to collapse
samersh72 said:
did you follow steps in mentioned link?
try this also http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thanks for all your replys, but as i told you, it doesnt show up as anything related to android. it shows up like this: http://imgur.com/a/W3JEO
This problem also comes when i plugin a normal usb device to put files on.
Same happen to me you have to install adp again
hhamzah49 said:
This problem also comes when i plugin a normal usb device to put files on.
Click to expand...
Click to collapse
That, and the fact it works on your old laptop tells me it's most likely a problem with the USB ports or controller on your PC. Do you have your motherboard disk? If so try reinstalling the drivers. Check USB settings in BIOS too.
CitizenLee said:
That, and the fact it works on your old laptop tells me it's most likely a problem with the USB ports or controller on your PC. Do you have your motherboard disk? If so try reinstalling the drivers. Check USB settings in BIOS too.
Click to expand...
Click to collapse
But how come it worked fine just a few days ago
Put it in my USB 3.0 port and it works. Looks like its "fixed".
hhamzah49 said:
Put it in my USB 3.0 port and it works. Looks like its "fixed".
Click to expand...
Click to collapse
I have the same problem, but i dont have USB 3.0 Did you found any other solution ?
hhamzah49 said:
Put it in my USB 3.0 port and it works. Looks like its "fixed".
Click to expand...
Click to collapse
Just like that?
Sent from my Nexus 5 using Tapatalk
Hey guys, I'm usually ok at doing that part. But I can't seem to install drivers for fastboot. My computer identifies it as S1 fast boot (something similar).
I am on Windows 8.1 x64
Check my post in the firmware thread. You need to turn off driver verification
Brendo said:
Check my post in the firmware thread. You need to turn off driver verification
Click to expand...
Click to collapse
Sweet thanks! I'll take a look, although I have tried installing the drivers with the verification off.
You need to go to the "device manager" app in windows, then you select the S1 Fastboot thing, and then you need to right click on it and update driver but not automatically, you need to select the manual option, and then select the usb_driver folder from the Android SDK.
Hi guys,
Phone is unrooted. I just upgraded to windows 10 and laptop no longer recognizes device. I tried doing a search and nothing comes up
Can someone point me in the right direction please?
install drivers but first use this. now you open prompt command with administrator permission and write this: bcdedit -set TESTSIGNING ON. Restart and try to reinstall driver
Xandros97 said:
install drivers but first use this. now you open prompt command with administrator permission and write this: bcdedit -set TESTSIGNING ON. Restart and try to reinstall driver
Click to expand...
Click to collapse
Which drivers? I do not believe the win 10 driver is out. The only one that I found is for win 8.1
Try pc companion. I'm on Windows 10 with my test computer and it recognizes my phone. Only problem I'm having is with flashing rooms but apparently that's a known issue for my particular problem.
texaslittleangel said:
Which drivers? I do not believe the win 10 driver is out. The only one that I found is for win 8.1
Click to expand...
Click to collapse
Windows 10 can use Windows 8 drivers no problem. As previously stated, you may need change your start-up settings to disable driver signature verification.
Message I get
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit -set TESTSIGNING ON
An error has occurred setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.
texaslittleangel said:
Message I get
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit -set TESTSIGNING ON
An error has occurred setting the element data.
The value is protected by Secure Boot policy and cannot be modified or deleted.
Click to expand...
Click to collapse
Did run the command prompt as admin? Either way, just do this:
1) Go to start
2) Click "Power"
3) Click "Restart" while holding down the Shift key
4) In the next screen that comes up, click the "Troubleshoot" option
5) Now click "Advanced Options"
6) Click "Startup Settings"
7) On the next screen click "restart"
8) On the next screen hit "7" on your keyboard for "Disable Driver Signature Enforcement"
Then install whichever drivers you need. After they're installed, you can reboot normally and enjoy the drivers.
Bloodlvst said:
Did run the command prompt as admin?
Click to expand...
Click to collapse
Yes I did.
Bloodlvst said:
1) Go to start
2) Click "Power"
3) Click "Restart" while holding down the Shift key
4) In the next screen that comes up, click the "Troubleshoot" option
5) Now click "Advanced Options"
6) Click "Startup Settings"
7) On the next screen click "restart"
8) On the next screen hit "7" on your keyboard for "Disable Driver Signature Enforcement"
Then install whichever drivers you need. After they're installed, you can reboot normally and enjoy the drivers.
Click to expand...
Click to collapse
THIS worked like a charm!!! THANK YOU :victory: :good:
One fix down a few more to go. I'm having several issues with Win 10 on my laptop.
Glad it worked! Let me know if you have any more Windows 10 related issues
Bloodlvst said:
Glad it worked! Let me know if you have any more Windows 10 related issues
Click to expand...
Click to collapse
That is very kind of you. I have all sorts of issues with win 10 with my laptop no others with my phone (thus far)
Which driver did you use please? I've installed the PC companion but that made no difference
texaslittleangel said:
Yes I did.
THIS worked like a charm!!! THANK YOU :victory: :good:
One fix down a few more to go. I'm having several issues with Win 10 on my laptop.
Click to expand...
Click to collapse
vilvic said:
Which driver did you use please? I've installed the PC companion but that made no difference
Click to expand...
Click to collapse
There a driver included in the Xperia Flashtool. Install that and you're good to go.
This unfortunately didn't work for me either.
After u did all the steps with the right drivers, i tried first time and did not worked, then i conected in flashmode and select the image again, i had the message runing that is conected in flashmode. I run it and worked
I'm gonna try I will get back to ya!
Unable to update Xperia Z3V
So i'm on a windows 10 machine with a sony xperia Z3V i'm unable to get the pc and phone to flash and to get this updated on the new version of Lollipop or marshmellow. I get to the flashboot and when i try to run it i get
04/059/2016 01:59:02 - INFO - Checking header
04/059/2016 01:59:02 - ERROR - Processing of loader.sin finished with errors.
04/059/2016 01:59:02 - INFO - Ending flash session
04/059/2016 01:59:02 - ERROR - Error in processHeader : 1 : Incorrect function.
04/059/2016 01:59:02 - ERROR - Error flashing. Aborted
04/059/2016 01:59:02 - INFO - Device connected in flash mode
I'm not sure why this isn't working i've been looking for something all night on this and I can't find jack. All i keep seeing is no matter what windows 10 installs the MTP USB Device for the xperia and the windows 10 Phone companion takes over from there. I tried using the sony companion and it never shows that i can do anything with the software but "restore" the phone. I've done several resets on the phone taking it back to stock and runing version 4.4.4 kitkat but I'd really like to get this updated or possibly find something else that will run on the machine.
Can anyone help? I've done all this stuff on alot of Samsung Devices and it seemed so much easier. I'm not sure if its because its a sony phone or because i'm on windows 10 now.. I'm thinking it could be a combination of both.
My friend also has the same model and tried to contact sony but they said because we are in the USA they can't help us. The updates from verzion keep failing on both our phones as well that can take us to atleast 5.1 Lollipop
Haveing Same Issue With My Xperia L and ZR, It Only Charges, But Can Browser Storage, Did Everything From Booting In Disable Driver Signature Installed Xperia Companian, Flashtool Drivers Still Cant See My Device Storage On Pc, But Can USe Flashtools