I've downloaded the motorola driver installation tool and run it, and it acts like everything worked, but windows still says that the drivers are not installed for the phone.
- Charging works (of course)
- Mass storage works (of course)
- "Phone Mode" works (where the PC sees the phone as a phone or modem - or, for this phone, apparently a CD drive?)
- "ADB Interface" does not work (where you have debugging checked and can do cool stuff with your phone)
I understand that since it doesn't I may have to edit the android_winusb.inf file with the info for my phone, and I know where to get its device ID from. I try to mimic the other entries in that file but there are 4 things I need to enter - single adb, composite adb, and two lines for single bootloader. I guess I don't know exactly what to put there. This is what I tried:
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_00
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D&REV_0216
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D
Someone else must have encountered this before. What did you put in that file to make it work? When I tell windows to find a driver for my "Motorola ADB Interface" in the folder C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver ... it just tells me that it can't find any information about my device.
jeez, all this just to be able to tether using pdanet.
Need the drivers for fastboot mode on a Win Vista PC. I have the Android SDK installed and the driver package installed. But when I boot my Nexus S into fastboot and connect it to PC, Win Vista wants to install drivers but it can't find them, even when I direct it to the drivers folder in the SDK.
Nexus S 4G, i9020, i9023, i9020A?
for i9023:
Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
Click to expand...
Click to collapse
Thanks for the reply. I almost thought I had it with what you game me. But it pooped up the error below and I include the file I altered to show if I did it correctly.
Sorry about the lack of info. This is a GT-i9020A and Vista is 64 bit.
EDIT - Nevermind, I see what I did wrong
Crap! I made the correction in the file but it still displays the error message that I have shown in the picture. I have no idea what it is saying.
EDIT - driver finally installed. I just kept trying to reinstall it and it finally cooperated. Phone has been unlocked and is now rooted.
I'm on XP, I downloaded the drivers from Asus support site for my TF101.
When I connect the device it's loaded as 'Unknown Device'. So I open up the properties through Device Manager > 'Drivers' tab > Update Driver > go through the steps to manually specify the driver file (that I downloaded from Asus) and I get:
The specified location does not contain information about your hardware.
Click to expand...
Click to collapse
I looked at the driver file and I do see some lines for my device:
[ASUS.NTx86]
; TF101
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E3F&MI_02
; SL101
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E03&MI_02
; A60
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
[ASUS.NTamd64]
; TF101
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E3F&MI_02
Click to expand...
Click to collapse
(I'm on x86)
The 'USB\VID...' is something I saw before under the properties of the Unknown Device. Under the Details tab:
USB\VID_0000&PID_0000\5&32FD0D5E&0&2
Click to expand...
Click to collapse
The format doesn't look exactly right, but I tried adding this to the driver file anyway and attempted to load the driver file again. Same result.
It worries me that both the VID/PID is 0000.
I also tried loading the driver file contained in tf_rootkit_31.zip
from this post: [ROM] UPDATED Transformer pure root tw/us/ww/de/jp (8.4.4.5/11/12/8.6.5.6/7) - xda-developers
Same result.
Gettin frustrated... any suggestions.
TIA
Try uninstalling any drivers already there and install Asus sync. That did it for me at least.
Thanks for the response.
I have Asus Sync installed, but I installed midway between trying to get the tablet recognized.
Should I disconnect the tablet and reinstall Asus sync? (I'll try it.)
When you say remove the drivers there, do you mean all usb drivers? Right now it's just showing up as 'Unknown Device' in the device manager (no yellow exclamation either) which I think means there is no driver. What I mean is I don't think it's installing a default driver. I'm not sure if or how to remove this default 'Unknown Device' functionality.
Also doesn't it seem weird that the VID/PID is all 0000s... Is that a problem with the tablet or the PC?
The issue look like the usb cable or the connecter fail. It isn't a software issue. You can change the usb cable in first to check the issue.
One thing for xp, you need to have wmv 11 installed. It includes drivers needed for the tf101
Thanks for the responses.
I'll have to check my WMP version tonight.
The cable works for charging, but I'll look into getting it replaced.
Just wanted to give an update. I purchased a new adapter and data cable. Plugged it in and nothing....
Didn't even recognize the tablet was connected!
So I tried another laptop with XP and the same thing. I went back to the old cable and sometimes it pops up that a device is connected, most of the time nothing. I tested the USB ports with a USB stick, pops up everytime so I'm pretty sure it's the tablet. I still don't know if it's hardware or software, but I don't think its the cable.
I decided to contact asus support. Hopefully I'll get some sort of response.
Thanks for the suggestions.
Just a suggestion, try installing android sdk and setting up adb.
Sent from samsung vibrant
Sorry, I may have forgotten to mention it, but I installed sdk early on in the process. Thanks just the same, have a good evening.
It's ok. Was just something that came to mind. Another thing if you're rooted then you can try
Booting into recovery and see if adb works in recovery mode.
Sent from samsung vibrant
Did you make sure wmv player 11 was installed?
I had two issues with xp, one was wmv player 11 not installed. But then there was another reason that the device driver wasn't working. Look in control panel->system->device manager, and check out the driver for the unknown device. If it lists an error, there is a microsoft fix for it.
Try installing going to download.microsoft.com/download/2/0/9/20944076-988f-487c-89fa-d37718782948/Microsoft_User-Mode_Driver_Framework_Install-v1.0-WinXP.exe it work for me.
USB tethering grayed
Even though I have connected the Transformer to a laptop (WinXP) with a USB cable the Transformer doesn't recognize its presence. Doesn't matter which USB port I connect to.
I am having this same problem, I have the mtp drivers from the ASUS website, I have the drivers for NVFlash, I have ADB installed (though it may be outdated, my android sdk is for Froyo I believe).
Getting my TF to connect to my laptop (Win 7 64bit, Media Player 12) is hit and miss, I usually have to reboot my laptop with the TF plugged in to get a connection.
No devices are listed in computer management or devices and printers when it doesnt show up. Nothing shows up on the TF (no notifications for ASUS Sync or USB Debugging).
When it does show up, I get a message in Windows saying the drivers failed to install correctly, but then it works.
I'm unsure if this is a Windows issue (perhaps with mtp support), or a TF issue (I've heard the TF doesn't like to recognize being connected/disconnected to the dock, perhaps there is an issue with the proprietary port).
I've had this issue over multiple ROMS...
If your windows has more than 1 user profiles, did you log-on using the profile with administrator privileges?
ondoy1943 said:
If your windows has more than 1 user profiles, did you log-on using the profile with administrator privileges?
Click to expand...
Click to collapse
On my laptop i only have one account, it has administrator privileges.
I'm also facing the same problem with my win7 x64 detecting the tf (a B40... model). Wonder if this due to a faulty data cable?
Sent from my Transformer TF101 using XDA Premium App
I just wanted to post an update:
While it is a little early to tell, I believe I have fixed this issue on my 64bit Win 7 Laptop. (Not sure if every step is necessary, but these are the steps I followed.)
Disclaimer: I do not guarantee that these steps will work for everybody, and I am not responsible for any mistakes made or problems that arise from following these steps. Please only follow these steps if you understand what you are doing. You take full responsibility for your actions.
Note: You need to be able to get a connection between the TF and computer, for me I had to reboot my computer every time I wanted my computer to see my TF, if you are completely unable to establish a connection these steps will not work.
What I did:
1. Go into control panel> programs and features.
2. Click on "Turn Windows features on and off" (or something similar to that in other Windows versions).
3. Uncheck/turn off "Windows Media Player" (may be in a sub folder like media features). (Windows Media Player is responsible for MTP drivers (which the TF uses), you will be prompted to restart the computer, please do so.)
4. Make sure your TF is being recognized by the computer (I had to reboot with it plugged in for it to be seen again).
5. Open up the device manager (just run a search for device manager OR open the start menu> right click on computer> manage, click on device manager).
6. Expand "portable devices".
7. Right click on the TF and choose "uninstall". (The TF will only be listed if it is currently being seen by the computer (i.e. you are able to transfer files).)
8. Unplug the TF and plug it back in. The drivers should be reinstalled, hopefully correctly.
Note: I haven't turned Windows Media Player back on yet (don't have much use for it, except maybe my zune). Not sure if turning it back on will have an effect or not.
Please take care when editing any Windows settings, I hope this works for Vista/XP as well.
I I have an android tablet made by Storage options called the "scroll" it has a 7 inch captive screen. Its telechips, processor and runs android 2.3
Super oneclick says its already rooted and freezes at step 5, gingerbreak freezes and z4root freezes
Nothing seems to root the tablet, what do i need to do? Can it be done? Thanks for any help
I was able to root mine with SuperOneClick v1.8.
http://www.assorti-fashion.com/super-one-click.htm#superoneclickdownload
Rooting the scroll essential tablet.
I used SuperOneClick too - but you need to make sure you have a working adb and that it sees your tablet.
e.g
C:\Program Files\adb\adb>adb devices
List of devices attached
000050E5493794B2111227082109001? device
And to get adb to see your scroll you might need to install the google usb driver and modify the android_winusb.inf
i.e. add these lines to both the [Google.NTx86] and [Google.NTamd64] sections:
; Scroll Essential TCC8900
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&REV_0226&MI_01
You should then be able to use device manager or other method to install the usb drivers for the tablet.
Then you can use SuperOneClick to root the tablet!
http: //www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
I notice that ADB would never load in recovery, while it would load in regular mode.
The driver was never found in Windows, and it was just called" Transformer."
To fix this you need to do a little driver ini edit to include the hardware IDs in the Google USB driver from the SDK.
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
Open a command prompt window and enter this command:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Although these instructions were originally written for Toshiba AC100, they should work for any Nviaid Tegra or Tegra 2 based Android device.
Click to expand...
Click to collapse
The hardware device ID used in regular mode is different than the one in recovery enough to cause a problem.
I found that this is for reg mode
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
and this worked in receovery
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F
After the edit and following the instructions I was able to use ABD in recovery
Useful and often overlooked tip, Thanks!