Database Info

Found Answer To Windows XP 32 Bit Driver install Error

Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
WINDOWS XP x86 / 32-Bit Only
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys !!!! (Be Careful Deleting this File, I Say First try Without Deleting this file !)
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....

All I can say is THANK YOU.
THANK YOU THANK YOU THANK YOU.
This post deserves a sticky..
you are great

LOL
-- well after this I couldn't use FASTBOOT anymore hahahahaha
well, I worked around that, had to reinstall drivers for Haykuro's SPL too. So now both ADB and FASTBOOT work.

Thanks helped with my Win NT at work. lol

lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.

SolemnWishing said:
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
Click to expand...
Click to collapse
So Is that you are sayin is we do not need to remove the wdf file, did the drivers work without removing & again installing that wdf file?
or u did not put the new file again before rebooting ?

I am not really sure. It can possibly just be my computer. Once removing all the drivers you listed, the ADB then successfully worked, and continued to work as long as the computer was not rebooted. Once rebooted, I drivers for many pieces of hardware became corrupt and unreadable. By simply replacing the wdf driver and rebooting, it fixed the issue. So, I really am not sure. My computer... is strange. I believe it likely could just be my computer thats all.

next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks

The key points are:
To choose ADB interface\HTC Dream Composite ADB Interface to install
--DIYism

sangeet.003 said:
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
Click to expand...
Click to collapse
I will be performing another system recovery install soon, so I will post the results. My computer got screwed up again, so backing everything up now...

I still have a problem...
thanks for your tutorial.
I followed as you say, but I can't find my phone in cmd mode in my computer.
I succeed to install driver also it's shown in device manager as like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but something wrong in cmd mode as like this.
I'v tried whatever I can do..reinstall driver, adb, swipe my phone..
what shall I do now?

adb problem
Hi,
Same problem here, tried everything but CMD just is not showing any device...

I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.

pluplus said:
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
Click to expand...
Click to collapse
I followed this completely, I have the phone installed correctly now, not a mass storage device, device manager reads:
ADB Interface > HTC Dream Composite ADB Interface
However, I have usb debugging enabled, and still get the same *error: device not found*
Took a decent amount of time to get done right too, thanks to "trustedinstaller" being the only "user" that can delete drivers on my laptop..yay for changing ownerships! You'd think administrator would suffice, but nay.
Anywho..wtf am I missing here?
edit: win 7 x64, however the same rules for this how-to should still apply, as all the drivers and install options/processes are identical

ive found that trying to use the adb driver the driver gave me error code 10 (within the device manager)
ive got rc win7 64 bit
what i used to get rid of this problem is the program called USBdeview ( google for it)
and uninstalled everything related to htc/android
after connecting the phone the correct driver installed and i could use the adb device

I didn't want to make another topic on this, but I have a problem. Whenever I uninstall the drivers from device manager, then search for new devices, it installs the drivers automatically. I have mass storage and adb dream interface, but no devices are found when I execute the adb command. I cleaned out what I could from the system32 and /drivers folder. Any clues? Just to add, it did work about a week ago, didn't need to use it, now it doesn't work.
Edit: Oops, I forgot the check the uninstall driver box. I have the drivers, they install correctly, but I still can't use adb.
PS: vista x64, installing from the amd64 subfolder.

sangeet.003 said:
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
Click to expand...
Click to collapse
nothing happeneds...
after doing that after reboot my laptop,i'm loosing harware keyboard and have some other problems too..
i just change the drivers again and reboot and all ok but there isn't any way to my laptop(toshiba xqosmio x300 with vista 32bit)read my hero in fastboot usb condition...
i tried it and in 2 pc's with xp (service pack 2) but the same again and there....
adb shell and adb devices aren't reade the phone in fastboot usb ....
in my cmd i'm taking allways the same error message when i try to load the cm-hero-recovery.img ""canot load cm-hero-recovery.img""
anybody who can help??

i have the windows usb drivers. and when i go into device manager on my 32bit vista machine, it shows "Android Phone" under portable devices. i click update drivers and select the usb drivers. problem is, it tries to install them, then i get a message saying like 'unable to install "da da what ever driver its called" then it just closes.
why wont this work help is appreciated

THANKS, i was keen to install linux

Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you.
You save my life. I've been having this problem for MONTHS!!! and no way im gonna restore my windows xp again. Thanks so much.

[SOLVED] Need help: Can't get ADB to recognize device

I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail. I have installed Asus Sync and then done Update Driver in the Device Manager, uninstalled Asus Sync and downloaded only the drivers from the thread in the development section, modified the android_winusb.inf in the Android SDK and tried using that driver, many restarts, etc. I have needed to modify every android_winusb.inf I have used, btw, since even the Asus ones didn't have my device in there (my hardware ID ends in 4C81, the one supplied only supported 4DAE, which I find odd).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I update the driver, the device does show up in the Device Manager as "ASUS Android ADB Interface" under "Android Phone," which is where my Galaxy Nexus also shows up, but adb devices only returns the nexus. And now, when I go into "My Computer," the Asus doesn't show up as a connected device (the GNex still does). Same in the Device Manager under Portable Devices.
Has anyone been able to get their TF300T to work with ADB on a Win7 64 bit machine? Is it possible that the version of Windows (Professional) could be causing the issue? I have heard that in the past. Any help would be greatly appreciated. Thanks!

I have windows 7 home edition (x64), I had installed Android SDK a long time ago. Before I connected my Pad for the first time, I updated Android SDK through the manager. I don't have ASUS sync nor Suite. The first time I connected the Pad it automatically installed some drivers, and it worked with adb from the get-go.

I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.

Northern-Loop said:
I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.
Click to expand...
Click to collapse
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.

Accord281 said:
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.
Click to expand...
Click to collapse
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM

Northern-Loop said:
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM
Click to expand...
Click to collapse
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.

Accord281 said:
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.
Click to expand...
Click to collapse
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.

Northern-Loop said:
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.
Click to expand...
Click to collapse
Correct. It will show my GNex or my Dinc 2 (depending on which one is plugged in), but the Asus isn't there. I will try those things and update. Thanks.
Edit: No go. I uninstalled the Asus Composite ADB Interface then turned off USB debugging then uninstalled the TF300T listing that popped up after that. After reboot, I connected it while not in debug mode, allowed it to install the driver itself, then turned on debug mode and had to manually point it to the driver. It still shows up in Dev Manager under Android Phone, but still nothing in ADB. I get the feeling there is nothing that can be done.

My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.

xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse
H.O.L.Y. S.H.I.T. that did it. I just switched it to camera (PTP) and it is now listed in adb. THANK YOU THANK YOU THANK YOU THANK YOU!!!!!!

Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.

xAshxMoneyx said:
Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.
Click to expand...
Click to collapse
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.

Accord281 said:
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.
Click to expand...
Click to collapse
No problem homie. My GS2 didn't have that problem either, went in just fine as ADB.

Accord281 said:
I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail.5
Click to expand...
Click to collapse
OMG, this is what happened to me last night when I tried to do the downgrade so I could root the phone.
I am on an XP 32bit machine.
I have a feeling that the Samsung software, which I also had installed on this machine is conflicting.
I'm in the process of removing all the drives (Samsung and Asus) and starting from scratch.
I still need to read the rest of this thread to see if someone answered your question, if they did, they they help me as well.
Rob

HI,
I guess a picture is worth a thousand words.
I finally managed to get a screen shot of what I have been asking help on:
I've been trying to do a downgrade so I can root my 300.
Why is the Asus showing up underneath my Samsung and does it matter.
Thanks!
Rob

Looks like it's showing up as ADB so it should be fine. Mine comes under a generic "android phone" listing, but maybe if Samsung was your first ever adb device on the computer, they will all show up that way for you. Just a guess.

thank you so much! I've been trying to solve this for 2 days
:good:
xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse

switch storage mode to camera
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck

jbosari said:
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck
Click to expand...
Click to collapse
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance

Mefna said:
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance
Click to expand...
Click to collapse
What is your device and version of Android you're running? It might help to know. There are some tools that can help. I've used USBDeview to delete all drivers and start over to fix problems like this (scroll down to the "Feedback" heading for the download.) After deleting anything ADB related from the list of drivers and starting over with the driver for my device, it worked... Good luck! I'll see what I can find if you write back with your device info.

[Q] Unlock issues (yet another noob thread)

Hello all,
I picked up a used TF700T in good shape. Looks like some kid only used it to play Minecraft.
It pulled an OTA update to JB4.2.1, build .10
The goal is to put CROMBi-KK on there; I've read a bunch of the threads on the topic.
So first I tried to get the unlock tool on there...
-downloaded Unlock Tool V8 to PC, hooked up tablet via USB (USB debugging enabled, trusting unknown sources): no luck, getting the "USB device not recognized" error, PC keeps alternating the USB-connect&-disconnect sounds.
-Went ahead and downloaded Unlock Tool V8 straight to tablet. Getting "App not installed" error.
-Went and got Unlock Tool V7 instead, installed successfully - but now getting "network error" repeatedly...
-Read somewhere that signing in to Asus Tracker triggered unlock success for some, so I tried that: the Tracker website won't even take my serial number...
Obviously I am stuck early on - What do I do next?
What's the magic words to use with Asus support, can they even help me?
Asus support might be extra tricky because the previous owner may have registered the serial number...
Any obvious solution I am missing (I have used the forum search, but haven't found any new leads...)?
Do I just keep trying the Unlock tool V7 until the end of days?

bas2205 said:
Obviously I am stuck early on - What do I do next?
Click to expand...
Click to collapse
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.

das chaos said:
Had the same problem; it's a common bug with tf700t: some serial numbers (only of tf700t) aren't registered in factory's servers.
I pulled a ticket with ASUS support (here in Germany), explaned the problem, sent them the MAC adress and S/N of my tab and got 3 days later notice, that my tab could be unlocked - and it worked, they registered tab in their korean servers.
Click to expand...
Click to collapse
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe

berndblb said:
Wow! That's the easiest resolution of that common problem I've ever heard of! Hope it goes just as well for him ^^
BTW, the servers are in Taiwan at HQ I believe
Click to expand...
Click to collapse
I thought, it was Taiwan, but was to lazy to look it up.
I did not invent this; it has been reported repeatedly in german boards.

Thanks again for the info guys!
I did as recommended, contacted support, telling them my serial number and MAC address. Got a response within ~36h saying they forwarded my request and the other department will take care of it in 10-15 days. So I am crossing my fingers for this to take care of the unlock issue.
I have been trying all sorts of stuff for the USB issue, no success so far. The person I got it from complained about the tablet not charging. Wondering if those two issues are related, I am suspecting a bad USB/charge port. Ordered a spare from ebay and will replace when it gets here next week. At this point (and not being the original owner), I am obviously not worried about warranty issues...
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.

bas2205 said:
@das chaos : ich weiss allerdings nicht, ob der US-Support da genauso schnell geholfen haette; Gruesse aus TX.
Click to expand...
Click to collapse
You're right as I usually am.

Hier muss wohl ein Nest sein!

I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
I have also tried downgrading to V10.6.1.14.8 and even V10.4.4.25...
Same result, whenever I plug it into a PC (have tried different ones), it just says "USB device not recognized". When I select the "Unknown Device" under Devices&Printers, I don't even get the option of installing a different driver.
I have tried this with the Asus driver installed, then I tried with the 'naked' driver.
Tablet is in MTP mode; I have tried it with "USB debugging" disabled and enabled,nothing works.
Any ideas?

Tough, since you are not the original owner... The USB cable, I mean the external charging/data cable: Do you know if it is the original one?
May it be damaged as in : broken strands or some such?

bas2205 said:
I did get the spare USB ribbon&port on Saturday and replaced it. Unfortunately, that changed nothing;
...
nothing works.
Any ideas?
Click to expand...
Click to collapse
Same result in any of the 3 modes: apx, fastboot, normal?
.... if it's not charging either, you should be soon at an end with the tablet.

@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...

bas2205 said:
@berndblb: I had to buy a new (external) USB/charging cable and wall charger. I bought the ASUS original one straight from them through Amazon.
@das chaos: not sure what you mean - can I still get to APX or fastboot even if the tablet is not recognized upon plugging in?
How would I go about doing that, install first the tool/driver and hope that it assigns drivers properly when I plug in? @sbdags recommended I take a look at this thread (http://forum.xda-developers.com/showthread.php?t=2646279)...
In device manager, it does not show up with an exclamation point, but as an "unknown device"; The catch-22 with that is that Windows claims that the proper driver is installed and doesn't let me load a different driver. The connection is also a bit unstable, disconnecting&reconnecting after a few seconds (looks like an unstable USB stack...
Click to expand...
Click to collapse
If it is shown up in Windows manager, then it is recognized! Only there are not the right drivers installed. For each mode (apx, fastboot, adb) you need a separate driver installed, wich normally are packed together in naked driver pack.
Windows doesn't install drivers of ASUS by it's own. You have to engage forced driver install routine; and there is a warning not to install those drivers. Do it nevertheless otherwise you won't be able to connect to transformers.

Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...

Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....

bas2205 said:
Thanks for the link. I was already aware of how to force a driver.
I took some screenshots to clarify where I am stuck.
First I get the USB not recognized error
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Then when I inspect it, it says No Drivers are installed.
When I try to point it at the driver through forcing procedure, it ends with " The folder you specified does not contain a compatible software driver for your device", despite me picking the correct inf. Same result for Naked Driver 0.72, 0.73 and the package sdbags referenced...
Click to expand...
Click to collapse
What do you have under Portable device? Your driver should be there....

Did you only do the 'Search folder for driver' routine or did you also try the ' Let me pick from a list of device drivers' option and then point to the folder with the naked drivers?
.... on second sight:
You seem to have an x64 OS. Are you shure, you got the appropriate drivers for x64? There seem to be different ones on the internet.
http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875/
Scroll through the posts to find people with x64 machines having trouble with drivers.

bas2205 said:
Next, in Device Manager, an Unknown Device shows up under USB (no exclamation point).
Click to expand...
Click to collapse
Look under Details (Hardware Ids) for the VID and PID to see if this is really your tablet. These are the ones that I know:
0b05:4c90 = TF700
0b05:4c91 = TF700 in USB Debugging mode
0b05:4c92 to 4c95: TF700 in some other modes
0b05:4daf = Fastboot mode
0955:7030 = APX mode

LetMeKnow said:
What do you have under Portable device? Your driver should be there....
Click to expand...
Click to collapse
Unfortunately, all unrelated:

berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Thanks, I will get right to that homework... I hope it's a driver issue. If it is a hardware issue, since I have already ruled out the internal USB connector and I am dealing with a new USB&chargin cable, that would leave the MoBo...

berndblb said:
Ok, I think it's time to determine if you have a Windows/driver issue or a cable/port issue.
Try this Linux live CD: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It comes with fastboot/adb already installed, doesn't need any drivers - so it should connect to your tablet with no problem at all. Unless there's a hardware issue....
Click to expand...
Click to collapse
Just tried the Live-CD... no luck! Both "adb devices" and "fastboot devices" returned an empty list despite me following instructions from the other thread.
I guess my last option (after I unlock) would be to try and install TWRP through the app method?

OPO not recognized in ADB Devices

Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!

do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)

CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)

Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?

Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.

I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.

I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?

CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!

From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse

Laptop won't recognize phone.

For some reason my laptop doesn't read my phone, works on my pc fine but i'm trying to fix it for my laptop. My phone only charges, can't access the files. My USB configuration is set to MTP, it defaults to Charging only but even if i switch it back and forth it does not work, thanks in advance for any help.

If you're on Marshmallow, swipe down from the top of the phone screen, press the USB notification, and change the selection from "charging only" to "file transfer".
Or do you mean that even when you do this (your description isn't clear) the laptop still can't see the phone? In that case, it'll be a driver problem. Install Wugfresh's Nexus Root Toolkit on the laptop and use the "Install & Test Drivers" button to set your laptop drivers up.

Okay I installed the root toolkit that you speak of but I don't see any "Install & Test Drivers" button. Unless you are talking about the "Full Driver Installation Guide" but that doesn't work because it can't recognize my phone.

Yes, "full driver installation guide".
I'm not trying to be funny, but you do get that the point of this is to get your laptop to recognise your phone, right...?

Yes I get that but I don't think you understand what I am trying to say. When following the installation guide I can't get past step 2 because it requires feedback from the phone, but it's still not being recognized thus making the process moot. The only time my laptop recognizes my phone is everytime I restart the phone, for a few seconds while the phone is loading I get an error of "unknown device found" on my laptop. When I try to manually update the "unknown device's" drivers, it says they are up to date. Even when I have the new google drivers on my desktop and point to it. Sorry it's late and I am half asleep, hope I am making some sense.

You've tried different USB cables and USB ports?
Is the phone recognized in fastboot or recovery mode?

Yes I have tried different cables but the issue is not with the cable nor my phone because I can just go onto my brother's pc and it recognizes immediately. It's just my laptop, and no it is not recognized in fastboot nor recovery mode.

Maybe it has something to do with the OS in the laptop?

No win7 64 bit for both, I know it's driver related but I just don't know what to do to fix it.

I've told you what to do... it's worked for me many times on a number of laptops, and on Windows 7.
If part 1 of the driver setup process didn't work, go back and do it again, following the instructions exactly to the letter, no shortcuts - i.e. when it says "reboot" then reboot, don't think "Nah, I don't need to do that."

Try deleting all existing drivers and reinstall.
I use the naked USB drivers on a win7 x64 laptop and desktop.