Bit of a weird one.. Hermes doesn't support host mode as far as I know.. but I turned it on this morning and got the error message:
"Unidentified USB device. Enter the name of the device driver for this device."
Which from what I can find on google is USB host mode not knowing what driver to load for a connected device (Nothing was connected at this point)
I'm using Sleuth's current ROM and haven't ever seen this before.. just wondering if anyone has seen it and if it really was trying to start host mode? Or had it just gone mad? (I cancelled the message and all is fine now)
(I'm guessing the host mode hardware/software is all missing and so it would never work.. but i'm interested all the same especially if it is software only that is needed)
Unidentified USB Device
I have the same problem. Can't figure why and no result on search. Can anyone advise?
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
bpdlr said:
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
Click to expand...
Click to collapse
I had this problem and what I had to do was:
be sure no USB drives/memory cards were connected
connect the phone
uninstall USB Mass storage device from device manager under usb controllers
disconnect/reconnect the phone
install the driver from the sdk/usb_driver folder
Thanks, but...
I tried this, but still not luck with adb. I now see a new "ADB Interface" section in Device Manager, and an "HTC Dream Composite ADB Interface" device underneath, but adb devices command still returns no devices.
Sorted!
Well, I'm not sure how but I managed to get it to work, and am now the proud owner of a Magic running Cyanogen mod
okay, I devoutly hope someone can help me here, because I'm at my wit's end with this. I'm using windows 7x64. I followed the instructions in THIS thread first(after installing the android sdk directly from the main website ), and got through everything okay, but when I try to do anything with adb(adb devices, for example) I get
"
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
"
Here's what I've tried so far:
1. Killing and restarting the adb.exe process, both with task manager and with adb kill-server(which is the only adb command I've found that does anything other than return an error message)
2. reinstalling both the drivers posted in this thread and those at nookdevs
3. rebooting both the computer and the nook color multiple times.
4. deleting all SDK files and both re-downloading and re-installing.
5. deleting every file I could find and the drivers and following the Nookdevs instructions. same problem
6. using the adb_wireless app, where it tells me to use adb connect <iP address> after running the app. same error message appears. Because of this step I'm less inclined to believe that it's a driver error, since the wifi app bypasses the USB driver, at least as far as I understand. I do, however, believe my drivers are installed correctly, I have ADB Composite android device in the device manager
The only google results I got with this error(for different devices) referred to the port adb needs being locked in to something else, but that doesn't appear to be the case here, I see nothing running on port 5037 in netstat
Thank you for taking the time to read my short novel, and I appreciate the help.
*shameless bump*
seriously though, 65 views and not a single person with even a suggestion? would this be better off in a different portion of the forums? Any advice at all?
dumb question, but with out the NC plugged in, when you type in "adb devices", what get's returned?
if you get that error message, than that's a config symptom.
Hey i'm no pro and got adb to work on accident...What i found is that the android sdk folder needs to be in your user folder. So when i go to start and click my user name my android sdk folder is in there with my downloads folder, desktop folder, and music folder. Makes sense? ALso any thing i push to my device i put into that folder in the tools directory. I found that that fixed most of my problems as i had the folder in the root of my c drive. Let me know if that helps.
No luck there, but thanks for the reply anyway. gives me the same error. I suspect in your case that you were not getting into the c:\android-sdk-windows folder and moving it to your username folder fixed that problem because that's the default path when you open a cmd prompt. Thanks for trying, though
Last thing i can think of is maybe your firewall? Kill it for a few mins and see what happens.
Still happens when the device isn't connected. I agree that its a config error rather than a driver issue. Also, disabling my firewall has no effect. Thanks for the suggestions though
Sent from my NookColor using XDA App
I have the same
nicbennett said:
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
nicbennett said:
not sure what was causing the issue, I ended up reformatting my HD and re-installing, it worked fine after. Sorry I couldn't be of more help, I looked everywhere for about 2 weeks and didn't find a thing that worked
Click to expand...
Click to collapse
Wow... I would hate to have to rebuild my computer just to get ADB back. I will post this in the Evo forum and see if there is some help.
Edit: Started a new thread in Evo forum:
http://forum.xda-developers.com/showthread.php?p=10730809#post10730809
Following the steps from the thread http://forum.xda-developers.com/showthread.php?p=24124828#post24124828, I lost my device on fastboot command (I followed correctly all the steps).
The device freezes on the startup screen and the PC can't recognize it properly. So the next fastboot command stays awaiting the device indefinetly.
The Android ADB Interface still remains untouchable on devices panel, but as an unspecified device. So, Windows doesn't mount the internal storage and consequently it is apparently impossible to change the damages.
Does anyone know something that can be useful?
install the correct drivers for fastboot and go ahead:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i had the same problem
used this link helped get my device up again
http://forum.xda-developers.com/showthread.php?t=1422832
Hi guys,
I'm looking for a way to read the kernel output during the boot process. I've already tried recompiling the kernel with/without FIQ_DEBUGGER, KGDB_SERIAL and SERIAL_SAMSUNG (_DEBUG), as well as setting the kernel console in the cmdline to every possible /dev/tty* port without any success.
I also tried echoing in every available serial port and use a digital analyzer on a breakout-microusb board to monitor the output. But all of the tty devices seem to be disconnected from the USB port. There are a lot of hints on the internet for other devices, but the most of them use a dialer to get into the service menu (e.g. for smartphones: http://forum.xda-developers.com/showthread.php?t=1515570) or a jig-cable with a resistor between ID and GND (http://redmine.replicant.us/projects/replicant/wiki/SamsungSerial). Both approaches failed on my Nexus 10.
I got no clue what to do next, so I would be very appreciated for any hints or new ideas.
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
EniGmA1987 said:
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
Click to expand...
Click to collapse
Thanks for that, but as far as I know the ADB daemon is started only after the kernel initialization. I can read the dmesg after Android is booted, but it doesn't help me to debug problems if the kernel panics.
I think I need some kind of a correct serial cable to read the kernel (and bootloader) output, but I couldn't find any working method for N10.
Did you have any luck with your case?