Database Info

Vista & XP won't find my HTC Dream (fastboot)

I've been following this guide and its been going fine until now:
ht tp: //wiki.c yanogenmo d.c om/i ndex. php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
I'm trying to do the fastboot portion but I can't get Vista(windows server 2008) or another computer running windows xp to recognize my phone. At one point using the adb command I was able to pickup my phone(on windows xp). I then gave it the command to reboot into the fastboot menu. Fastboot wouldn't pick it up.
Any ideas? Vista is 64 bit. I tried the 64 bit fix that was posted here and it didn't work.
Here's the error I get when I pull up the properties of the device in device manager
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
Click to expand...
Click to collapse

[Q] ADB not working with LG GW620

This seems like an incredibly common problem, unfortunately for all the posts on a number of forums I haven't found any solutions. I was hoping if I shared some of the details someone may have something I haven't yet come across to check. I've tried the supplied instructions over at openetna.com on now three different PCs including 64 and 32bit Win7 installs but can never get ADB to recognize my phone.
Phone: LG GW620(EVE)
ROM on phone: openetna v6.1 RC3 (Android 2.2.1)
In device manager I have 5 instances in the Other devices section with yellow exclamations on them all titled "LG Mobile USB Modem", which I believe indicates that the USB driver is not installed correctly. I'm not sure why.
Here's what I've done
1. Install latest JDK(JDK 6 update 22)
2. Install Android SDK(usb drivers revision 3 using SDK manager)
2.1 OpenEtna has the user modify the android_winusb.inf file to add the following lines which I've done.
;LG eve
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
3. Turn phone on, ensure USB debugging is turned on, plug in phone with usb to pc
4. At this point ADB doesn't work when I expect it is supposed to. I believe this because if I type the following commands I get an error
C:\>cd "Android SDK"
C:\Android SDK>cd tools
C:\Android SDK\tools>adb kill-server
C:\Android SDK\tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
5. On some of the PCs I've tried this on, I've installed the USB Drivers provided by LG directly that allow me to mount the SDCard on the phone when I turn off debugg.
Please help

Is this the wrong forum for a question like this?

Nope...right one..just no one with enough knowledge on your issue has noticed your post

Fluidsuit said:
Is this the wrong forum for a question like this?
Click to expand...
Click to collapse
I am just having the very same error. i have my LG gw620 with V10G, and OpenEtna -Cyanogen 6.1 (Froyo 2.2.1) as well.
Even more, i cannot mount/umount the SDcard, thus, i cannot access it via usb (i was thinking that perhaps this is THE error, it hasn't been tested with this, only with v10C as per my search).
Anyone else?, any tip?
PS: ANY tip will help me, perhaps if someones knows if i can fastboot it and then push the file like adb (i don't think this is possible, but i hope to be wrong)

I was finally able to see the SDCARD by installing the "Dual Mount" app from market.
However, the logs keep telling me the error of the usb Tethering.
Any replies?
Does anyone knows why is any pc not recognizing the phone in debug mode ? (i know it looks like a driver issue, but believe me , i have done trillions of times the reinstall of all drivers, after wiping them out again, with no luck, It just seems that the driver is not the correct one).
Without this, my phone is completely isolated from adb and cannot continue flashing it
Regards,

So guys, did you get the adb working in the end on the LG GW620 (EVE) ?
I have the same issue infact. It has something to do with the drivers not being correctly installed, but i can't figure it out.
I keep on getting $ instead of the # after adb shell
There is also a new tool, called Z4mod, which can root your EVE if you are lucky (me not so much ) maybe you should try that?

Well, I just got it rooted... if your phone is not recognized/connected, you may need to modify the "android_winusb.inf" file so that the LG Eve is listed first..
this is what I have...
***
[Google.NTx86]
; LGE GW620
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_0FFF
***
But my problem now is with Fastboot. I got the phone into Fastboot mode but WindowsXP prompt for driver. The same drivers that were working in non-fastboot mode won't work. So, I cannot connect to the phone in Fastboot mode.
Anyone know what I should do next??
Thanks!

cheunt said:
Well, I just got it rooted... if your phone is not recognized/connected, you may need to modify the "android_winusb.inf" file so that the LG Eve is listed first..
this is what I have...
***
[Google.NTx86]
; LGE GW620
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D00D&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_0FFF
***
But my problem now is with Fastboot. I got the phone into Fastboot mode but WindowsXP prompt for driver. The same drivers that were working in non-fastboot mode won't work. So, I cannot connect to the phone in Fastboot mode.
Anyone know what I should do next??
Thanks!
Click to expand...
Click to collapse
Nevermind my previous question... finally figured it out and got Froyo on it.
Thanks everyone for all the tips though!

cheunt said:
Nevermind my previous question... finally figured it out and got Froyo on it.
Thanks everyone for all the tips though!
Click to expand...
Click to collapse
I finally managed to get this phone into fastboot but adb doesn't see it. Can anyone help me with this?

[Q] Can't seem to install drivers for this phone, in either XP or Vista

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.

[Q] usb drivers not working on XP

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.

Alcatel OneTouch Pixi 7 (9006w) - ADB Interface Driver (Windows)

The drivers that I downloaded from the Alcatel website didn't have the ids for the OneTouch Pixi 7 (9006w), so I modified the Google USB Drivers.
I edited "android_winusb.inf", removing all entries for Google devices and added our device.
Code:
[Google.NTx86]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
[Google.NTamd64]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
I also updated the string section at the end of the file.
Code:
[Strings]
ProviderName = "ALCATEL"
SingleAdbInterface = "Android ADB Interface (ALCATEL 9006w)"
CompositeAdbInterface = "Android Composite ADB Interface (ALCATEL 9006w)"
SingleBootLoaderInterface = "Android Bootloader Interface (ALCATEL 9006w)"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Devices"
Download here.
Double-click "install.cmd" to start the driver installer.
I was able to get this to work in Windows 7 64-bit and Windows 10-64-bit. I have not tested 32-bit or Windows 8.
I had to disable driver signature verification for this to work in Windows 10, I would assume this would also work for Windows 8. Feel free to test and let me know.
I have also included adb and fastboot in the "platform-tools" folder in case anyone doesn't already have them installed.

Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.

Muxintorq said:
Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.

OriginalHardwyre said:
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.
Click to expand...
Click to collapse
Is it required that you have to have a AMD 64 bit CPU or a regular Intel 64 bit CPU will work on this also?
Thanks.

Amd64 basically just means 64-bit, for Intel or amd.