Related
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.
Hey there,
My Asus Transformer TF101 was working fine yesterday... I recently updated to ICS without any problem. I then rooted my device using viperMOD PrimeTime v4.5. Once again, everything worked without any problem.
After rooting, I ran the V6 SuperCharger script. The device rebooted and everything was fine... Then according to the instructions, I downloaded a modified version of the services.odex file and I replaced the original system file (I did kept the original file by changing the extention to .tmp). This is the last time I've seen my Transformer booting. I did this because of the reply from bsoplinger on this post:
http://forum.xda-developers.com/showthread.php?t=991276&page=906
The thing is that I forgot to change the owner:group to root:root and to chmod 644. I believe this is where I failed.
Asus Transformer TF101 B80
Rooted ICS with viperMOD PrimeTime v4.5
V6 SuperCharger Script activated (Choose Option #8)
Replaced original services.odex with a new "empty" one
Now, when booting it gets stuck on the Asus Logo with the rotating loading circles... they keep rotating forever until the battery is drained out.
This is what I tried:
Booting with Power button & Volume down then Volume down again (tried Cold boot and Wipe)
Booting with Power button & Volume down then Volume up (Recovery)
Booting with Power button & Volume up + NVFlash (won't work because it is not a B50-B60-B70)
Drained the battery to 0%
Put an official firmware update zip file on a microSD and booted with it
So.... this is pretty much it... As of now, I'm out of ressources and I don't know what else I can do... 40$ via Paypal to the first persone who gives me a working solution.
Thank you for your time!
If you have the original saved on your PC, try pushing it to your TF with ADB
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
baseballfanz said:
If you have the original saved on your PC, try pushing it to your TF with ADB
Click to expand...
Click to collapse
Actually, the renamed original file is only on the internal SD card of the Transformer. I don't have a copy.
I am currently trying to ADB work... I installed the proper APX drivers but I get a message from Windows saying that the ASUS Android MTP Drivers failed to install and all I get from ADB/Fastboot is a "- waiting for device -" message...
I'm using Windows 7 Pro 64bit
Jfuginay said:
So you can boot into recovery? If you can get into there I'm sure there are ways to fix your bricked device.
Which recovery are you using? If you don't have it already, I'd recommend installing CWM recovery and flashing a new kernal/rom.
There are plenty guides on how to do that, or I can try to walk you through it but if you managed to do that other stuff to your transformer I think you'd be able to follow the current online guides.
Click to expand...
Click to collapse
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
bArDBQ said:
Thanks for your reply. I am new to Android but as far as I know I can only get into the stock Asus recovery mode. I can't get (or don't know how to get into CWN recovery). CWM was supposed to be included in viperMOD PrimeTime v4.5 root but I am unable to boot in it.... I am trying to make ADB/Fastboot work to see if I can launch it from there but so far I can't make it communicate with my device...
When I press Power + Volume Down and then Volume Up, all I get is a green android robot with a black "!" in a red triangle...
Click to expand...
Click to collapse
Try what I mentioned about shutting down processes and hold down Volume up plus power when booting. You'll see a black screen but that's ok, you can verify that there is actually something going on because your computer should make the sound stating a new device has been connected to your pc.
From that black screen, you should be able to get nvflash to work, assuming you've shut down other programs that could be using adb, and have installed the correct driver for nvflash, and have also unpacked the prime rom into the nvflashf folder.
Jfuginay said:
I had the same issue for a while, on my windows 7, it seems there are multiple things that may be using the same resources you need for this process to work. Try ctr + alt + delete to view running processes, and shut down anything that may be using adb. It is crucial to shut down Asus sync, asus webstorage, etc, as they tie up your adb line when trying these methods.
I had bricked my transformer as well, and all the processes to fix it weren't working because of "waiting for device" messages.
They finally started working once I closed all other programs using adb.
Plus, with nvflash, make sure to unpack the Rom into the folder, rather than just having the rom's zip in the folder.
After fixing the "waiting for device" error, I still couldn't get mine to work because the rom wouldn't flash over as is, I had to take the "Prime" rom's tar located with in nvflash, and extract the files into the same folder.
Once I did that, I ran nvflash, and the rom transfered over fine and I was able to unbrick my device.
Click to expand...
Click to collapse
I will try to close all process that might use ADB but I already know that NVFlash will not help me since my device is a B80 and that NVFlash won't work with anything over B70
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I will make ADB working and see what I can do from that... Should not be that difficult.
I am installing Asus PC Suite since it seems to be the best way to get the missing drivers...
baseballfanz said:
Yeah you are still on stock recovery.
Your best bet is to get adb working, you can then pull the file, renamed and push it back.
Click to expand...
Click to collapse
I just can't get ADB to see my device...
I installed Asus PC Suite, it does detect the device and show it as "Nvidia USB Boot-recovery driver for Mobile device" in Window's device list when I boot using Power Button + Volume UP... When I launch adb from command prompt deamon starts but when I type "adb devices" it shows: "List of devices attached" but that's it... no devices in the list.
I deleted the "Nvidia USB Boot-recovery driver for Mobile device" and installed the default ASUSTeK Computer Inc. drivers I already had in Windows drivers list "ASUS Android ADB Device" but I get the exact same result.
I also tried to install the USB Drivers from ASUS website "ASUS_Android_USB_drivers_for_Windows.zip" but it seems like they are not made for Windows 7 64bits... The OS doesn't see them or won't install them...
AAAAAAAAAAAAHHHHHHH
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
bArDBQ said:
......... I installed Asus PC Suite, Droid Explorer... Installed/Reinstalled drivers... nothing works... I get the nVidia APX drivers to work but I just can't get the MTP Drivers to work... it is always saying that the Device can't start...
I don't know what to do.
Click to expand...
Click to collapse
{
"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"
}
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
baseballfanz said:
When using ADB you do NOT put it into APX mode.
Try cold booting your TF, once it get to the Eee Pad screen where it's stuck.
See if ADB can recognize your device there.
Click to expand...
Click to collapse
So, cold-booting did not help, when I do this, the device manager shows that the "ASUS Android MTP device" drivers failed to install. I get the Code 10 (This device cannot start)
jazzruby said:
Hi bArDBQ,
First of all, the driver pkg 'ASUS_Android_USB_drivers_for_Windows.zip' IS the correct pkg and contains both 32 and 64 bit drivers; the .INF (installer file will enumerate/choose the correct files)
The image you posted (Device Manager) isn't even showing ADB 'mode'; 'Android Device/Phone' should be at the top of the list, if you've already manually installed the drivers or 'Other devices|Unknown device' if you have not .
Make sure you have USB debugging enabled in Settings on the device
After enabling, when you connect to your PC you will have an ?unknown? device in Device Manager under 'Other devices' and have to install/update the drivers manually (unless the files from ASUS PC Suite are still in Windows driver store).
Right-click 'Unknown device' > Update Driver Software... > Browse my computer for driver software > Browse | Include subfolders - (choose the extracted folder 'Android' e.g., [ ASUS Android USB drivers for Windows_20110321\Android ] )
You can also update 'ASUS Android MTP Device' the same way; just choose the 'MTP' driver sub-folder instead of 'Android'
You probably could just choose the top-level folder (extracted USB Driver folder) when choosing for each driver (because we chose 'Include subfolders') but that's up to you.
HTH,
-JR-
Click to expand...
Click to collapse
Hello JR,
Thanks for the reply.
I manage to show the ghost devices and hidden device in the device manager. I deleted everything, and rebooted the computer. I connected the Transformer and cold-booted. Windows detected the device and I choose the MTP drivers from ASUS_Android_USB_drivers_for_Windows.zip but I got the same result. When I was booting using the Power Button + Volume Up Windows was detecting the device in ADB mode and I was able to install the proper drivers and make it work.
This said, it was impossible for me to get the Transformer in the device list in ADB. My computer simply can't connect to the tablet.
I can't make sure USB debugging is enabled in Settings on the device since the device do not boot but it was before it was bricked.
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
BiohazardPL said:
bArDBQ , did you ever get this working. it seems i'm in the same boat your in except i'm on b70
Click to expand...
Click to collapse
Hey,
No, I was unable to fix the problem. I returned the device to ASUS and my replacement unit is on its way. I guess I was lucky they were not able to fix it.
Since you are on a B70 you might be able to use NVFlash. You should try it if not already done.
Good Luck!
SON OF A BBBBBBbbbbb
Son of a bbbb... Son of a BBBB.... Son of a BBBB... hot damn. Ok Rooted, stock TF101. I was beta testing an app, and got the andy on his back with red triangle for my TF101 (us variant). I can see the Eee pad logo start, then nothing, only the back light stays on. Recovery leads to andy on his back. I tried Vol down + Power until reboot, then let it settle and come up with either choose to enter android or wipe data. Either one does nothing. Only the back light stays lit.
Recovery option is a no go.
Normal cold boot is a no go,
Hot boot is a no go.
PERI is a no go.
NVFlash is not tried yet.
ODIN is a no go.
12 pack of beer is a GO. Need more though I think.
Any assistance would be helpful.
UPDATE : Easyflash with the latest OFFICIAL Asus 4.0.3 update worked perfectly. NOTE : there was a simple partial file error that caused the problem.
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.
Since I can't respond to threads in Developer and I think that this might belong here to answer some folks questions. I have read that a lot of people are having issues with ADB access under Windows x64 using the latest CM10 by h8rift. I found a solution that worked for me and I wish to share it with everyone in case it will work for them. A few critiria:
- Your device is connected via USB cable to your computer
- Your device is listed as "HTC MTP Device" in Windows Device Manager
- When you open a CMD prompt under your Android Directory and type "adb devices", nothing is listed
This is because you have the wrong device drivers installed on your system and it needs to be corrected. This is how I accomplished it.
1. Uninstall the driver completely from your system. This has to be done under the device properties. Under "Action", select "Scan for New Hardware Changes". Your system will see the new device and identify it under "Other Devices" as "One". If Windows tries to install the wrong drivers, you will have to restart all over until the HTC MTP Device driver is completely removed from your system.
2. Install HTC Sync from their website. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. HTC One X Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files (default install location).
4. For ADB access, you will need the drivers located here; download appropriate drivers for your Windows flavor. These are the ADB drivers.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
I am not the maintainer of any of these webpages nor can I guarantee that these pages will exist to the end of time. Those of you wishing to have ADB access under Windows for CM10, this worked well for me. I gathered up this information just by doing a quick search in Google and through the forums.
Thank you to h8rift for CM10 and all the hard work he puts into it.
Will try this when I get home! Thanks.
This worked perfectly for me. Thanks man!
------------------------------------------------------------
HTC One X, CM10-Evita JellyBean, Win7-x64
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Chrysis said:
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Click to expand...
Click to collapse
I think I found a fix for that. Let me restart my computer and verify
edit: nope.. nothing so far. mine doesn't even show HTC MTP DEVICE anymore >.>
same i see one when i look for new hardware but it always just auto sets to mtp.
Delete old drivers
The reason for this is that you cannot completely delete existing drivers using device manager. They still exist in the driver store, and are loaded as soon as you scan for hardware changes.
There might be a better way to do this, but here's how I did it:
- uninstall driver in device manager. Don't scan for hardware changes.
- Run a CMD prompt as administrator (right click "Run as Administrator")
- navigate to C:/Windows/system32 which is the location of the driver store
- type pnputil.exe /e
- this will list the drivers that exist in the driver store. They are denoted as oem##.inf
- find the driver that has "HTC Corporation" in the description. Write down the oem##.inf number (ex. oem81.inf)
- type pnputil.exe /d oem##.inf (where ## corresponds to the number of the HTC driver).
This will remove the old driver from the driver store. Now when you scan for hardware changes, it should fail to find a driver and prompt you for a location.
NOTE: I actually had several HTC drivers in the driver store. Its because I've had a few HTC devices over the years. I deleted them all. This may break HTC Sync, I dunno. I don't use it.
Fixed. See post below
For anyone having problems. I finally got it working.
THIS SHOULD BE NO LONGER NEEDED. ROHAN'S NEW AOKP VERSION 2 SHOULD WORK WITH STOCK DRIVERS. IM ASSUMING THIS WILL BE MERGED WITH ANY OTHER AOSP ROMS. IF YOU STILL NEED THIS INFORMATION HOWEVER, I WILL LEAVE IT UP.
1. Uninstall HTC Sync and any HTC sync drivers listed in your "Add/Remove Programs"
2. Delete EVERY driver pertaining to HTC when you run CMD as admin and type "pnputil -e" and then type "pnputil -d oem##.inf" (such as oem13.inf ONLY IF it says HTC or HTC Corporation)
3. Download Deview - 32 bit OR 64 bit, and run as administrator and uninstall ALL disconnected drivers (it won't matter if you uninstall the wrong thing, because it will just reinstall again when you plug in the hardware. make sure your phone IS NOT plugged in)
4. Download ADB drivers 32 bit OR 64 bit. (windows)
**Restart Computer**? (I did just to be safe)
5. Plug in your phone. Go into device manager, and find your device. It should be listed as "One" with a yellow question mark.
6. Right click and update driver software
7. find your USB drivers you downloaded and choose to install those.
your device should now be listed under "Android USB Devices" as "My HTC"
When I did this, my phone skipped being labelled as "HTC MTP Device" all together
If it is not detected in ADB after installing drivers...
1. UNPLUG PHONE
2. Run USBDeview as administrator
3. Uninstall any unplugged devices
4. Restart computer
5. Plug in phone
{
"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"
}
and after verifying adb reboot bootloader worked. I thought, well heck. I'm sick of installing a file manager to install a file manager that's already stored on my sdcard.
and to verify it installed (no restart)
I hope this helps someone
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
pet3rs said:
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
Click to expand...
Click to collapse
What exactly are you trying to do? Did you install HTC Sync drivers? This is for using ADB on the old CM10/AOKP, not for rooting your phone
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
pet3rs said:
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
Click to expand...
Click to collapse
Boot your phone into fastboot from your bootloader
Sent from my HTC One XL using xda-developers app
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Found a great way that fixed it for me on Windows 8:
use this tool: http://www.nirsoft.net/utils/usb_devices_view.html to remove all instances of anything that has to do with HTC. Then, follow steps above to scan for new devices, and set the driver accordingly (with USB debugging on on the phone). It should register as "My HTC" and then you will be able to see the device in "adb devices" list.
pet3rs said:
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Click to expand...
Click to collapse
you can't use adb from fastboot. you use fastboot.exe e.g.
fastboot oem getvar cid
no adb needed.
Guys can u pls help me? I've done the above procedure for installing the drivers on my htc explorer, it all worked, in the device manager panel i can see My htc when i'm in fastboot, and i can see Android bootloader Interface when i'm in the bootloader, but nevertheless I can't run adb shell because it doesn't find the device, and when I run adb device it gives me an embty list, i must use adb in order to attemp to recover the nand that it's probably burned.
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