Trying to save on battery and not use the hotspot I thought I'd try USB tethering. I am able to USB tether and connect to the internet via USB tethering. However, there are two devices in Device Manager with yellow exclamation triangles: CDC Serial and LGE Android Phone. I've searched and searched but am unable to find the drivers for these devices.
CDC Serial
Hardware Ids
USB\VID_1004&PID_62C4&REV_0310&MI_02
USB\VID_1004&PID_62C4&MI_02
Install Error
E0000203
LGE Android Phone
Hardware Ids
USB\VID_1004&PID_62C4&REV_0310&MI_04
USB\VID_1004&PID_62C4&MI_04
Does anyone know where I can download the drivers for these? I've tried the LGMobileDriver_WHQL_Ver_4.0.4 with no luck.
Thanks!
I finally found the drivers on the CD partition that came up when I plugged my phone into the computer. I quickly copied the files to the hard drive from the CD partition to the hard drive. Then I installed the drivers through Device Manager. I don't know if it really matters or not but I can't stand having any yellow triangles in Device Manager.
Related
Hi I have just noticed in the nokia diagnostic tool in the bottom right the three dots when pressed gives you settings option and within that option it says usb mode Zune or usb serial with an option to choose which one ... What's this serial in this case ?? Will this allow direct access to hdd and find a way to use as mass storage ? or can we use this to access the cpu or other parts of the phone ?? im not sure were the serial point to yet ...
Probably that would be the way to flash rom.
It seems to be used for reparing the device or OS level software debugging - it won't give you USB Mass storage device....Or it maybe if you found the right driver...from Nokia Engineer. On HTC phones, this can be used for tethering with the right driver.
Serial Ports are the port that were used for Modem and Mouse before USB was invented (COM ports) It is the very basic form of communication port that most device implements - which the chipset on Lumia also emulate Serial Port over USB cable. (http://en.wikipedia.org/wiki/Serial_port)
Ahhhh ok thanks very much guys
Didn‘t notice that before, I'll poke at it using a serial debugger once I get home, could be some interesting/fun stuff that can be done
In winxp you can load a driver for a system device. maybe at driver level the connection data can be verified. How:
connect in serial mode. it will at first time detect a nokia rm801 or whatever device and ask for a driver. it finds 4 devices.
for the first, the xp system will itself suggest
1) USB Composite Device
2) will not find anything, and show the dialog to go onto internet, search etc.
Don't search and choose the driver to install yourself, with the downmost radiobutton and click next, in the categories go to System Devices, the driver assist will suggest a Compaq Deskpro Thermal Sensor, install this. Will install without error
3) see 2.
4) see 2.
Because it installs a temperature sensor driver, it must be possible to monitor or probe somehow. help?
My guess that will only gain you access to temprature data from the phone.
Have you tried putty and a baudrate of 9600? this is the most common used baudrate, tho It is quite possible they use 16000 instead if the serial connection is ment to handle data transfer.
I've been looking at the schematics for the phone and I can not seem to find out which chip they have used for GPIO. We would probably need to get hold of service level 3 or 4 manuals for Nokia Care (unless someone wants to dissasemble their phone and have a look at the mainboard)
Edit:
After a bit more digging I think I've traced serial to be managed directly by the CPU.
This suggests that it's a purely SW serial console.
I haven't been able to find any details on WP7/7.1/7.5 SW serial.
Worth looking into but I guess would require disassembly of the software?
what is the protocol for example when doing a software update through Zune? It gets into some kind of bootloader mode then too.
can imagine the serial connection is hosted as sw in the phones sw environment when running the mango os. But is the serial mode still fully sw if you boot it? Don't know if you could find anything in the 15 sec of booting to mango
I think the easiest way of figuring out how this is done is to disassemble the .net library that is used in the WP7 update tool.
I will have access to the required tools when I get home. The tool is this one if you want to get cracking on it:
http://xboxmod.sylvester20007.com/TOOLS/WP7_update_tool.rar
Have a Fujitsu T-01D phone, it's already set in USB debugging mode but when it's connected to the computer, the DDMS is not able to detect the phone. The list under name in DDMS is empty.
Checked device manager the USB mass storage device drivers of the phone and Android ADB interface driver all seem okay.
Already tried 2 different USB cables and ports but still not able to detect.
Also did adb -kill-server' and 'adb devices' command to reload the host server but still nothing changed.
Any way to get this resolved?
So, apparently I need to install a few drivers for rooting this. The one set of instructions I got is to enable USB debugging and then find a device called "ASUS Android Composite ADB Interface" with an exclamation mark in Windows Device Manager. Trouble is no such device exists. I plugged in the TFP with USB debugging!
What to do?
What version of Windows are you running? Do you have Asus sync? If so can you see the Prime as a storage device when connected via USB?
It can show up as various items depending on which driver version and the actual text string in the .inf file. Have you tried having device manager already open and watch it to see what ( if anything) changes as you connect the prime? It can appear as a device under the "android phone" heading or as other things... plug it in whilst watching device manager update, let us know what is added to the list and maybe we can help...
Sent from my transformer prime which is currently transformed into a small bowl of petunias
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
So I ran into some issues with my HTC Evo 4G LTE when attempting to use it on my Windows 8 laptop that I wanted to post about in case others have the same issue. I did a number of Google searches and while I ran across a number of others who had this same issue, no one seemed to have the fix all in one place, so here's what I experienced and what I did.
First step in CM10.1 is to enable Developer Options. Go to System>About Phone and tap on the build number 6-7 times. I know this is well documented but like I said, I'm putting this all in one place for reference.
Initially when connecting my phone via USB to my Windows 8 machine it would immediately detect it as an external storage device (even when ADB root and Android debugging were enabled in the Developer Options)
The specific driver it kept loading was called Linux File-CD Gadget USB Device under Disk Drives
It would also load as an external drive letter under Portable Devices (in my case F:\)
Finally, under Universal Serial Bus Controllers it would load a USB Mass Storage driver and a USB Composite Device Driver
First, you'll need the Android SDK. This is important for two reasons: 1: The most up to date ADB as it is required in CM10.1 / Android 4.2.x because of the device fingerprinting that Android now does with ADB. Get rid of older versions or you'll end up with the device detected but offline. 2: You need the USB driver installed from the Android SDK.
I tried a number of suggested things to attempt to update the driver for my device with the Android USB driver, some people had suggested installing it over the USB driver, some over the Portable Device driver and some over the Linux File-CD Gadget driver. None of these worked, windows kept returning the following error:
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.
What I eventually found is this: After enabling Android Debugging and connecting your phone via USB, you need to go to the View menu in the Device Manager and select 'Show hidden devices'. At that time I was presented with a new section called Android USB Devices. I specifically recall in Windows 7 this was not a hidden area, however it is in Windows 8. Under this heading was a device labeled My HTC. I'm quite sure I never installed the HTC drivers for my phone in Windows 8 so this may be something that is shipped with the OS at this point... or if I did install them I dont recall doing it.
Either way, this is the driver you need to update. Simply right-click, update driver, and replace it with the driver stored in the Android SDK folder (AndroidSDK folder root\sdk\extras\google\usb_driver\). This will load as a Samsung Android driver. Dont worry about it, it works fine.
Finally, as I mentioned before, if you run adb devices and all you see is your phone but it says "offline" and you're sure you have the newest ADB, check your phone screen, it will be asking you to confirm the fingerprint of your machine before it comes online and lets you issue commands.
I hope this helps other people, it was quite a hassle figuring this out, mostly because I didnt expect the driver to be hidden since it wasnt in Windows 7.