Related
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:
This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"
Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe
:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working
hey thanks!!
will give it a try tonight!
Will this work on 4.3?
Sent from my GT-I9505G using xda premium
Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.
ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.
ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.
Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks
Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0
I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver
warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.
Correct.
Etched in blood by a katana
Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.
carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
I'm using TWRP. My problems with drivers keeps increasing it seems :\
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
you can go to device manager and update the driver, choose Browse my computer, Let me pick from a list of device drivers, and choose one that says adb.
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
Click to expand...
Click to collapse
right.
was concentrating on work. i messed up
simms22 said:
right.
was concentrating on work. i messed up
Click to expand...
Click to collapse
We all do it
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
To make adb works in recovery you need the naked usb drivers
Tapatalk-kal küldve az én Nexus 5-el
You don't need the naked USB drivers at all.
I use the Google USB drivers and they work fine in recovery.
The problem he is having is that windows has automatically installed a different driver than what is needed for adb to work.
Manually updating the driver to the Google adb driver as shown in my previous post will get the op running without having to download anything extra
Sent from my Nexus 5 using xda app-developers app
Alex240188 said:
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
Click to expand...
Click to collapse
Can you check if you can use adb remount when the phone is fully booted? I'm using naked drivers and everything works except this command. Adb root doesn't work also.
This has nothing to do with the drivers. The kernel you use has to be built with the ro.secure=0 flag for remount to work
Sent from my Nexus 5 using xda app-developers app
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
Hi,
I have a rooted Xperia Z5 and I would like to update my firmware to 32.2.A.0.305.
I used to do firmware updates many times before using flashtool on my windows 7 machine.
Recently I switched to windows 10 and now need to reinstall the fastboot driver.
I downloaded the driver from sonymobile webstie:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Unzipped the file, and got a directory with the "android_winusb.inf" file.
Booted the phone in "bootloader" mode via the TWRP recovery (LED on phone is blue).
The regular method of power down, volume up+connect to USB did not work. The LED was blue for a second and then turned off.
When in "bootloader/fastboot" mode, opened the windows "device manager" and found the problematic S1 device.
Right click on it, update driver, browse my computer, pointed to the directory where the ".inf" file is located.
Windows "makes sounds" as if it is installing the driver, but then gives an error:
"Windows found a driver software for your device but encountered an error while attempting to install it"
"Android ADB interface"
"The system cannot find the flie specified"
I have no idea what the problem is.
A few posts suggested that this might be a driver-signing problem with windows 10.
They suggested removing the "driver-signing" option and try. Did not work.
I also tried this with a virtual machine Windows 7 that I have installed, and got the same error, so I'm not sure it is a windows version problem.
I read in one place that this is an error with the location of the file and that it should be located under the "C:\Windows\WinSxS" directory.
Tried that as well, and no luck.
Does someone have any idea what the problem is?
Alernatively, if someone can explain or point me to a post of how to use fastboot and flashtool with linux,
that can also help.
Thank you.
Avi
driver signature verification
1. Goto START (windows icon);
2. Keep pressing SHIFT, klick POWER and RESTART
(shift is pressed all the time along);
3. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
When your computer restarts you'll see a list of options.
4. Press F7 on your keyboard to select Disable driver signature enforcement.
Your computer will now restart and you’ll be able to install unsigned drivers.
This is firt to do, but didnt quite get it if you tried this allready. Greetings
Have the same problem. Disabled driver signature enforcement. Did not help
Are you sure it's disabled? Some pc's don't have the option to disable the driver signature enforcement. If that's the case you need to enter the bios settings and look for the tk keys and delete them, then restart your pc and you can install the fastboot driver.
Hope this helps
Had the same issue on my new setup.
This solved all my problems: https://forum.xda-developers.com/xperia-z/help/help-findiing-installin-s1boot-fastboot-t2218143
dim4x4 said:
Have the same problem. Disabled driver signature enforcement. Did not help
Click to expand...
Click to collapse
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
L33Tgod said:
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
Click to expand...
Click to collapse
Nice and cool - but we still dont have a Sony Xperia Z5 Driver from it in the List