I have seen many questions asking how to install universal naked drivers. Last week I received (loan) a windows computer and had the same issues. I decided to provide the info to help others.
Note: These drivers do work properly for the TF300T even though they may not state that exactly. Also if your tablet identifies as a TF201 it will still work properly.
Note: If you are on windows 8 and having problems please see the bottom of this post #1 for help! This info was provided by prototype7 please give him a thanks.
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process if we are to succeed.
Here are the choices I had to use to change my drivers and a link to the drivers.
windows-start - in search type device manager and return
{
"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"
}
right click on the entry you wish to change the driver for
Update Driver Software
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says drivers not signed; install anyway
Windows 8
Note: The following info was kindly provided by prototype7. Please give him a thanks.
Originally Posted by prototype7
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Re: How to install Universal Naked Drivers
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
And this thread is now stickied
MD
philos64 said:
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
Click to expand...
Click to collapse
Thanks for the kind words. I have wanted to post this for sometime but didn't have windows to prove the method.
Moscow Desire said:
And this thread is now stickied
MD
Click to expand...
Click to collapse
Thank you!
I just hope it can help some others getting their drivers installed and working.
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Manox7 said:
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Click to expand...
Click to collapse
Thanks!
I don't know why some tablets require the tablet designation and others don't. For that reason we suggest everyone use them. It is a code assigned by google that designates the manufacture of the unit. On linux we have to declare them to avoid a permissions error but we don't have to add drivers.
I'm glad you got everything sorted.
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
prototype7 said:
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
tobdaryl said:
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
Click to expand...
Click to collapse
Go ahead, it would make it easier to see. Glad I could help.
prototype7 said:
Go ahead, it would make it easier to see. Glad I could help.
Click to expand...
Click to collapse
Thanks again, I'll put in the first post for others.
Windows for x64
tobdaryl said:
Thanks again, I'll put in the first post for others.
Click to expand...
Click to collapse
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
nathanielhall929 said:
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
Click to expand...
Click to collapse
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
file selected still not working
tobdaryl said:
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
Click to expand...
Click to collapse
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
nathanielhall929 said:
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
Click to expand...
Click to collapse
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Still nothing
tobdaryl said:
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Click to expand...
Click to collapse
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
nathanielhall929 said:
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
Click to expand...
Click to collapse
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
how do I start ADB?
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
nathanielhall929 said:
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
Click to expand...
Click to collapse
Check the thread you wished me to help with as I think I have already posted the resolution there.
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
Thanks for ur great job
I have tf300t with replaced logicboard. -it was bricked
My os win8 64bit
I tried universal naked driver ..but no way
is their any reasons with the last bricked in this case...??
Sorry for the poor english
Related
OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.
{
"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"
}
MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.
Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!
Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*
Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird
temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"
!!!THIS IS NOT A ROOTING GUIDE!!!
This pack contains everything you need to connect and use your nexus s on your pc
Will work on XP, Vista, 7
!!!HOWEVER 7 HAS THE BEST SUCCESS!!!
included:
* Fastboot
* ADB
* USB Drivers (32bit and 64bit)
Links:
SDK:
http://www.fileserve.com/file/RZqMfeC (sdk, fastboot, adb)
Mirror:
http://hotfile.com/dl/92897052/df7338b/SDK.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
DRIVERS:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
Mirror:
http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
To be able to install drivers you have to have your phone booted into fastboot and connected via usb (Thanks to mmas0n)
How to force drivers to install:
Thanks to gravis86
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2a. NS Right-Click "Android 1.0", and click "Update Driver Software..."
2b. NS4G Right-Click "Nexus s", and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
;C:\android\tools
Click to expand...
Click to collapse
yes the ; is needed
11. click ok
Now when you open cmd (command prompt) you can use "adb" or "fastboot" anywhere with out locating the folder first
You should be able to do 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"
}
If I have helped you please hit the thanks button
I have followed the directions to the letter and when I type fastboot devices it just goes back to command prompt. I tried typing fastboot oem unlock and it just said waiting on device. Adb devices typed produces "list of devices attached" I boot the phone into fastboot mode and and the usb is plugged in but I keep getting the same results. Am I preparing the phone incorrectly?The adb worked with my Vibrant but the fastboot failed there as well. I would greatly appreciate any and all help you may offer. As I am sure you can tell I am another one of those ignorant nubies.LOL
have you installed the usb drivers?
you will have to force them to install
mazodude said:
have you installed the usb drivers?
you will have to force them to install
Click to expand...
Click to collapse
Yes I have. adb works with my Vibrant but fastboot does not and neither one works with the Nexus s. I have read and reread and followed directions but nothing seems to work. Should I be looking to do something on the phone other than booting into fastboot mode? The Nexus S shows fastboot mode at the top of the screen and I have assumed that I just use the computer from there. On my Vibrant booting into recovery does not show anything about fastboot. I really do appreciate your help I am trying very hard to learn quickly so I can be of some help instead of a burden
I don't know how to force them to install. I went in an opened the folder and I assume they were installed. I do have usb debugging enabled
Edit Just copied usb drivers to C:\android and c:\android/tools and still the same results. I have done everything I can think of but i guess I am not getting the drivers installed properly.
to force them, go into control panel-> administrator tools->computer management
then goto device manager in the sidebar.
I cant remember what the device is called but you should know when you find it.
right click and hit update drivers.
hit browse for drivers and find the drivers in C:\android\google-usb_driver
Note: phone has to be in fastboot to be able to install the drivers
edit: I forgot the drivers opps
link:
http://www.fileserve.com/file/ZM9hbvH
edit: this video might help
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
I just downloaded the drivers and placed them in C:\android and then went into device manager and hit update drivers and then browse for drivers and it said no drivers found. I was in C:\android/google-usb drivers.
have a look in the post above i just posted a link to a vid
edit: are you using 64-bit?
no 32 bit I will look for the video. Thanks so much for your kind and patient help!!!
I think there is a trick in the video to get it to see the device in fastboot
edit: there are some drivers here
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
there is no video but I did read the directions and I believe I have done all that they state. Should my PC say installing drivers when I plug my phone in? It did and said one driver failed to install.
yea.
If you don't see a video (at the top) disable ad blocking
also the driver that failed try to force it (using previous method)
If anybody could help that would be great, then I will add it to the first post
Followed this guide and unlocked and rooted my friends Nexus S.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
@shaolinmastr well that's good to hear
I still have no success installing the drivers. Are you sure that the drivers were in the last zip file? I have gone over and over it for the last 6 hours and am at the same place I started. NO adb and no fastboot on the Nexus S and adb working on Vibrant.but no fastboot . I guess it is time to take the Nexus S back and get a refund. It is not worth the lack of results with so much effort. Thanks for you help.
Save yourselfs the hassle and just install PDAnet and you should get the drivers to work.
I was having this same problem and used pdanet to get the correct nexus s drivers. You can dload pdanet to your PC and just plug your phone in via USB andfollow the directions.
So tmello56, pdanet worked for you?
If so I will extract the drivers and add them to the first post
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
Sometimes Windows needs to be forced to use a driver that we know works, but Windows thinks doesn't. This is similar to what mazodude posted, but is just a few steps further. To do this:
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2. Right-Click "Unknown Device" or whatever it's called, and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
9. WIN!!!
@gravis86, very good explination will post in 1st post
Just wanted to post my results...
I was using the correct drivers, but was installing them while the phone was booted and connected. I could use ADB and mount the file system, but could not use fastboot. I then discovered that if I installed the drivers while the phone was booted into the bootloader and connected, it detected the device differently and fastboot worked.
Now rooted + custom recovery. Awesome.
[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"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"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.
Ill add this to the FAQ
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.
Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.
n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.
Very simple and easy to follow. Thanks OP.
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.
I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...
How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"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"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!
I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.
Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?
Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!
I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.
ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.
+1 for sticky
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.
Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App
bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.
sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.
bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse
Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App
I attempted to search for this issue, and while there are many similar issues, I haven't actually seen a resolution for 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"
}
I need the MTP driver for Windows XP. I've gotten the other 2 drivers up & running, but not the MTP. Anyone able to provide a link for a working MTP driver for my Nexus 7?
I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )
goebish said:
I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )
Click to expand...
Click to collapse
I already have Media Player 11 on there. No go.
AirDroid isn't an option as we only have WiFi at work on our outside LAN and our computers are all behind the firewall.
i had this issue recently.
do you have USB debugging turned on? if so, turn it off.
mrhomiec said:
i had this issue recently.
do you have USB debugging turned on? if so, turn it off.
Click to expand...
Click to collapse
Yeah. No luck.
@mrhomiec
Yes, I turn USB debugging off and try re-installing the driver again and it is working fine now. Many thanks.:good:
After ages trying to root my Nexus 7 and repeatedly un/re-installing of drivers using various 'toolkits' and then finally succeeding, I was upset to see this problem in Device Manager.
Seeing mrhomiec's excellent solution in the first thread I looked at was a great relief. Many thanks!
Media Transfer Protocol Porting Kit
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.
twista4004 said:
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.
Click to expand...
Click to collapse
It helped. Even if the posts are old, there's always someone looking for a solution. Thanks!
MTP working with XP
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.
A little something to get USB-Debugging working
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
%USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_0BB4&PID_0C01&MI_01
Click to expand...
Click to collapse
and changed it to:
%USB\VID_18D1&PID_2D02&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_18D1&PID_2D02&MI_01
Click to expand...
Click to collapse
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
and changed it to:
USB\VID_18D1&PID_2D02.DeviceDescRelease="My HTC ONE"
Click to expand...
Click to collapse
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
to
USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'
doomhendi said:
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
and changed it to:
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
and changed it to:
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from to
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'
Click to expand...
Click to collapse
The method in the prior post works fine and is much easier.
lewmur said:
The method in the prior post works fine and is much easier.
Click to expand...
Click to collapse
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz
doomhendi said:
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz
Click to expand...
Click to collapse
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.
lewmur said:
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.
Click to expand...
Click to collapse
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense
doomhendi said:
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense
Click to expand...
Click to collapse
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.
lewmur said:
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.
Click to expand...
Click to collapse
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.
doomhendi said:
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.
Click to expand...
Click to collapse
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!
lewmur said:
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!
Click to expand...
Click to collapse
.. If they want a truly working USB-interface, they don't have one :laugh:
But you get a 'thanks-click' from me for you intentions
worked like magic!
I followed each step exactly and the magic worked! I can now access my HTC internal storage and SD Card contents from Windows XP.!
Many many thanks!
lewmur said:
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.
Click to expand...
Click to collapse