Can't properly install the android fastboot drivers on Windows 10 - Shield Tablet Q&A, Help & Troubleshooting

I keep trying to install the fastboot android drivers on windows 10 but every time I connect my shield tablet original to windows 10 laptop. It's already recognized and is put under the Category "Universal Serial Bus Devices" as the name "Shield Tablet". Then after I try to install the adb drivers, I try the command fastboot reboot, but it stays at "waiting for device". What should I do now? Im just trying to flash the official build version of TWRP on my Shield tablet original WIFI. Thanks for the help!!!!

Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB

koop1955 said:
Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Click to expand...
Click to collapse
That is only compatible with windows 7,8,8.1

RunicGamer said:
That is only compatible with windows 7,8,8.1
Click to expand...
Click to collapse
Did you try installing them? I am running Windows 10 and have those drivers installed.
Here is a guide to installing drivers on Windows 10: http://en.code-bude.net/2015/08/19/how-to-install-unsigned-drivers-in-windows-10/

I had to do the manual install on Win10. Hit browse, show list, pick folder, etc. I think it comes up as Android Device Interface or something to that effect.

Related

Issue using ADB and Windows 7?

I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php
I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.
ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.
If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!
I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.
I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.
ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result
Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.
make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems
What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?
detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.
Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).

need Windows 8 USB drivers

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:

[Q] Drivers Nexus 5 Windows 8

Hi,
I'm getting really frustrating...
I'm trying to install my nexus 5 on my pc (windows 8) like an MTP device.
every time i instert my nexus 5 (triend usb 3.0 and usb 2.0) the phone is viseble in "my computer"
if i go to Device Manager, it is under Other Devices with yelow triangle (screenshot 1)
i have already tried to install manualy the usb driver from google but is is the message i get: "he folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems"
can some one please help me ! i tried evertythinh: also tried to instal naked driver.
thanks in advance !
ikke833 said:
Hi,
I'm getting really frustrating...
I'm trying to install my nexus 5 on my pc (windows 8) like an MTP device.
every time i instert my nexus 5 (triend usb 3.0 and usb 2.0) the phone is viseble in "my computer"
if i go to Device Manager, it is under Other Devices with yelow triangle (screenshot 1)
i have already tried to install manualy the usb driver from google but is is the message i get: "he folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems"
can some one please help me ! i tried evertythinh: also tried to instal naked driver.
thanks in advance !
Click to expand...
Click to collapse
I used the Nexus Root ToolKit to install the Google Nexus ADB Interface driver. You must likely find either by googling them or find them on this site.
I am running win8.1 x64 and installed the driver from SDK. The above methods should also work for fastboot, but the device will not be seen if it is in stock recovery. The driver will have to be manually configured. I did not bother with the custom driver and installed TWRP from fastboot. I received the 4.4.2 OTH update and TWRP flashed automatically.
You have to disable driver signature enforcement. Google it for tutorials.
Sent from my Nexus 5 using xda premium
You have to choose the "Let me pick my driver" option and look in the Android folder. I'm assuming that you have already installed the SDK kit.
Sent from my Nexus 5 using Tapatalk

[Q] Bricked Asus Transformer TF 101 B60

Hi all first off I'm sorry if this has been posted before but I'm having a problem unbricking an Asus transformer tf101 B60, I'll start with what's going on or not for that matter. lol
1. Boot to recovery is CWM-Based Recovery v5.5.0.4 roach-tf101-r2
2. will not see sd card / backup-restore= -2014-04-05.02.52.56 / no files found
3. Choose a zip = e: can't open /sdcard/update.zip
4.PC windows 7 pro 64 bit will not see the tablet when plugged into usb getting unrecognized device,force driver still getting yellow ding=device cannot start
if I plug in the usb and turn on the tablet windows does not even see that and unit sits on logo screen. and other screen the cold lynx boot that hangs there.
So in short I'm hitting a brick wall, windows won't see it, it won't see the SD card in recovery mode.
I've read in these posts how to fix this problem and have all the software / firmware you name it, but they all say almost the same thing, windows needs to see the device in order for any of these fixes to work, and thus is my wall I'm hitting.
Any help to find a solution to this problem would be oh so thankful to you all and call you Tablet Gods, this was a tablet given to me as a paper weight and I thought if it boots it can be fixed?
Thanks for your time and God like tablet knowledge.
Cheers.
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Driver Not Working
*Detection* said:
Install the APX drivers (Universal Naked Drivers) and use the tool "Easyflasher" to flash TWRP recovery (Forget CWM) both from this link
http://forum.xda-developers.com/showthread.php?t=1688012
You might need to install the APX drivers manually using Device Manager
If you find that the PC still does not see the TF101, you might need a new cable
Click to expand...
Click to collapse
I booted the unit into recover mode and windows sees unknown device..Ok
Tried to install new naked driver and getting a splash saying not compatible with windows 64 bit, I tried this on a brand new windows 7 pro 32 bit laptop and got the same results. I do have a brand new usb cable for it thinking that the old one was faulty, tried adb again same thing no device found, are there any commands in terminal emulator that can force the driver on the usb port? I'm thinking that if windows sees an unknown device then at least it sees something there just not whats there? Am i wrong in that somehow it's lost the usb firmware connection? so the driver will not install and if forced does not make the connection to the device? So this is my results.
So I'm ready to put gun in mouth over this, my laptops going to divorce me over driver abuse and the tablet mocks me with the frozen Asus logo.
Again Thanks for all the advice and i'll keep slugging it out.As this unit is in perfect condition outside of the Bricked part
You don't need to boot it into recovery mode to start with, just install the drivers normally first with the TF101 connected and booted normally
It's always going to say it can't find the device if the driver isn't installed
Focus on getting that APX driver installed and working, once you have that installed, Im pretty sure it will see the device fine
Asus TF101 B60 Softbrick? What Now?
Hello all.
I've been searching in vain for an answer to my Bricked Asus tf101? I'm just going to get right to the problem.
I can't get the tablet to be seen by windows 7 pro 64bit, Unknown device and yes I've tried everything, except asking if there's a way to force connection through a terminal like I've seen done with a router and a network switch to force a flash file so as to get at least a response after a reboot instead of just the Asus splash screen, here's a summary.
The Good.
1. I can boot to recovery CWM-based recovery v5.5.0.4 roach-tf101-r2 with menu's
Bad: Does not see sd card only see's internal and there's no file or folder error for backup/restore
2.Boots to screen with 2 icons data wipe and linix cold boot and goes nowhere from there just hangs.
So I'm stuck here, I have all to tools to do the job only if windows would see it, Adb does not see device which means the same thing no driver no fix,
Everywhere I read it says do this and that and it will restore to factory, that would be great if windows saw the thing, so I'm looking for a way to get the tablet to boot to something other than a loop. also tried the put the E101_SDUPDATE.zip in the root of the SD card and restart, does not see the card or file or both so it's not loading the file?
1. windows 7 not seeing device, will not take force drivers, Universal-Nvidia-Asus- MTP
2. recovery does not see sd card, so can't flash new anything?
3. So no communication from SD/USB
4. Is there a terminal command I can use to force a Blob or flash a recovery to the tablet when drivers and USB don't respond?
And to top that off my laptop filed for divorce for driver abuse..lol I'm not giving up.
Thanks to you all,
I want to thank you all for your time and advice it is very much appreciated, and I'll keep slugging away because I know there's a fix out there.
Cheers.
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Thanks
*Detection* said:
Drivers need to be signed in 64bit windows, use 32bit Win 7 either on another machine or in VMWare or Virtualbox etc
Then the drivers should install
Click to expand...
Click to collapse
Thanks for the Advice, Is there a thread outlining this so I can give it a try? I do have a new laptop I'm building out with windows 7 Pro 32bit as I've had so much trouble with the 64bit version.
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
*Detection* said:
If you're building a 32bit Win 7 laptop, then no need for virtual machines, just use that laptop, this is the Easyflasher thread, you should only need to follow the couple of simple instructions once you have 32bit Win 7 running
http://forum.xda-developers.com/showthread.php?t=1688012
Basically in a nutshell:
1) Plug in TF101 to PC and make sure ADB debugging is enabled in Dev options on TF
2) Drivers will/should fail to install
3) Open Device manager
4) Right click the ! missing driver
5) Update driver > Point to extracted Universal Naked Drivers from Easyflasher thread
6) Drivers should install
7) Leave TF plugged into PC
8) Power TF off
9) Hold Volume Up & Power until the PC sounds the USB connect sound
10) TF is now in APX mode (Nothing on TF screen yet) drivers should install, check Device Manager, if it doesn't install, point it to the extracted Universal drivers folder again until they are installed
11) Follow instructions to use Easyflasher
12) Done
Click to expand...
Click to collapse
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Sicknote said:
I am trying to get mine out of the reboot loop and cant seem to get it into APX mode to install the drivers.....any idea how go from here and have been trying step 9 above.
Will keep on trying to see if I can get it to work
Click to expand...
Click to collapse
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
*Detection* said:
Need more info
What happens when you try to enter APX mode?
Which OS are you running on the PC?
Do the APX drivers install ?
etc etc etc
Click to expand...
Click to collapse
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Sicknote said:
When i try to put it in APX mode, the screen goes black but pc does not see it. I have tried this bit lots of times and not sure if I'm missing something...
Have the drivers in a folder on my desk top. Have watched videos on YouTube but what i see is not happening when i try it...
OS is windows 7.
Drivers don't install.
Click to expand...
Click to collapse
You're not going to be able to put the tablet into APX mode till you get the drivers installed correctly.
With the tablet connected to the computer and the tablet on, download the naked driver package. open up device manager and right click on Other Devices - APX and chose update driver. Chose browse and then go to where you downloaded the naked driver package. If it complains that they aren't signed, click install anyway. If successful, you should now be able to put your tablet in APX mode.

Windows 10 USB drivers for oneplus one

Ever since I installed the windows 10 upgrade on my desktop computer, it doesn't recognize the oneplus one anymore. It was working fine in windows 8, and now the device manager shows a USB composite device that is in yellow status failed to start. I have tried pointing the driver update to the google usb driver from the android sdk and that fails, insisting the proper driver is already loaded. Any ideas on this?
if I turn off android debugging on the phone in developers options, it cycles over and over that device is not recognized. I have the samsung drivers from previous posts in this thread installed.
Are you using MTP or PTP? I think I had to move to PTP to get it to work for both access to the storage and for ADB.
i dont have any problems if i connect my one plus to my pc with windows 10
Windows 10 is very buggy and im having problems with it on my laptop and when trying to use bootcamp it says my partition osnt formatted correctly.
Sent from my SM-N910V using XDA Free mobile app
wmunn said:
Ever since I installed the windows 10 upgrade on my desktop computer, it doesn't recognize the oneplus one anymore. It was working fine in windows 8, and now the device manager shows a USB composite device that is in yellow status failed to start. I have tried pointing the driver update to the google usb driver from the android sdk and that fails, insisting the proper driver is already loaded. Any ideas on this?
Click to expand...
Click to collapse
Any screenshots?
madchainsawer said:
Windows 10 is very buggy and im having problems with it on my laptop and when trying to use bootcamp it says my partition osnt formatted correctly.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
What you mean is Bootcamp doesn't support Windows 10 yet. Give Apple 5 years and they may patch it.
Had no problems at all with Windows 10 on 4 machines.
Try to delete Drivers and clean all the install again
I made a clean install of Windows 10, installed the standard Google ADB drivers, then the Samsung ADB drivers, connected the phone to the PC, went to the device manager and replaced the "unknown ADB device" by "Samsung composite ADB device" driver. After doing that, it recognizes perfectly the phone either in MTP, ADB or Fastboot modes with no issues at all. I always did it this way in clean installs of Windows 7 and 8.1 and works exactly the same in Windows 10. Try it this way, it will work.
Enviado do meu A0001 através de Tapatalk

Categories

Resources