Just wondering if anyone else is having this issue.
After waiting for the VF 2.2 OTA update, it finally arrived yesterday morning. Great. Except now ADB doesn't detect the phone.
Plugging it in, putting it in debug mode etc and going trying ADB devices shows an empty list. Putting the phone in recovery and trying fastboot devices shows it with no problems.
If I plug in my HTC Magic (on 2.1-update1) and my Nexus One, adb shows only the Magic in the device list. ddms also doesn't detect the N1 but does detect the Magic without any problems.
I've tried reinstalling the driver, reinstalling the whole SDK, installing all updates, doing a factory reset on the device and everything else I can think of. Nothing seems to fix this issue. It's been logged in the android bug tracker, but not many people seem to be having the issue. The bug is here: http ://code.google.com/p/android/issues/detail?id=9437 (sorry had to break it up because I'm not allowed to post links yet)
I'm not sure if this has anything to do with Windows 7, but from searching it seems there have been other issues with W7 and the N1 when using adb.
What I just don't get is that it's only affecting a few people. What could be so different about my N1 that's causing this and not causing it for almost everyone else? It makes no sense to me.
Having the same issue. I put an issue in http: //forum.xda-developers.com/showpost.php?p=7636799&postcount=129.
Tried ADB with a HTC Legend. No problem. But on my Nexus ONE the ADB don't announce itself on the USB bus.
Just to make sure; USB Debugging is enabled in the phone, right?
Yepp. USB debugging is on.
Sent from my Nexus One using XDA App
Related
I got up this morning and decided to sync some music over to my captivate. I was surprised when I started getting errors that the device was not recognized. After four hours of trying to get the phone to sync I put it back to as vanilla as I could and brought it to ATT. After trying a new cable and just about everything else the phone has been declared to be defective. My problem is how do I get this phone back to original without a usb connection. The phone is not recognized by Odin, ADB or anything else so as far as my knowledge goes I am out of ideas. The phone works fine other wise but I thought some of the brightest on here might be able to help. Any ideas guys?
Try a different USB port.
Mine only works in the back USB ports, but won't do **** in the front ones.
I probably should have been a little more clear. The port is defective on the phone. They can't even communicate with the phone at the AT&T store through the usb port with some reader. I am trying to get the phone back to resembling stock before i send it back for warranty.
Sent from my SAMSUNG-SGH-I897 using XDA App
Try downloading adbwireless from the market. It will allow you to use adb without a wired connection.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have Windows 7 64x bit, and sometimes my connections seem dead, and I just uninstall and reinstall the drivers.
ADB wireless seems like your best bet right now
Thanks. Gave that a shot and I can connect to the phone. Now all I need to do is find the att apps.
try a factory reset and see if it recognizes your phone .
rsohne said:
I got up this morning and decided to sync some music over to my captivate. I was surprised when I started getting errors that the device was not recognized. After four hours of trying to get the phone to sync I put it back to as vanilla as I could and brought it to ATT. After trying a new cable and just about everything else the phone has been declared to be defective. My problem is how do I get this phone back to original without a usb connection. The phone is not recognized by Odin, ADB or anything else so as far as my knowledge goes I am out of ideas. The phone works fine other wise but I thought some of the brightest on here might be able to help. Any ideas guys?
Click to expand...
Click to collapse
Have you tried it on another computer?
Hello all I have been using a captivate for some of my dev work and all was going well but just today I can no longer see it in my devices using ddms or adb devices.
Looks like adbd is running on the phone and I can mount the sd card fine. I tried in two machines, one mac and one windows... So its something in the phone and a factory reset didn't fix it - any tips on how I should go about troubleshooting this?
It was working fine so I am a bit miffed.
Thanks so much
Jit
--
Sent from my SAMSUNG-SGH-I897 using XDA App
Still not working with a mac
All:
Just an update to the issue - the Captivate still refuses to be recognized by ADB, although it works fine on the same machine when I boot into Windows and use Samsung Kies.
On the Mac side, I can mount the files when USB debugging is on by going to the USB status icon and selecting Mount storage. The Mac even recognizes the connection as a new network connection (although I simply ignore that part). So looks like the USB subsystem on my Mac is somehow not recognizing the ADB communication. I upgraded to android release 8 and still the same problem.
Is there a way to completely reset the USB subsystem on a Mac without having to reinstall the OS?
Thanks so much - the weird thing is that the captivate worked okay for a week or so before deciding not to work with adb any more - I can still generate apks and sideload the apks into the device but I would really like to be able to do some on-device debugging.
Thanks so much for any help that you guys can give.
Jit
Edit: Nevermind
SOLVED - ADB Issue with Captivate
All:
After quite a bit of research finally figured out why ADB will not recognize the captivate (or for that matter any other android device). The problem was because I had installed EasyTether. Its a pretty nice software and pretty easy to use to tether android devices, unfortunately it kills adb's usb capabilities.
I found this issue in EasyTether's FAQ area so if anybody else is having the same problem you will need to unload the EasyTether Kernel Extension (unfortunately that didn't totally fix the problem for me - I kept losing communication intermittently so I ultimately removed Easytether from my mac as well as from the Captivate and now I can see the device in adb again).
Just thought I would share the solution with the rest of the very helpful community.
Jit
ok so this has been happening for a while and im finally tired of it...
I plug in my cdma hero fully rooted running CM 6 with the stock usb plug into my computer and neither my phone nor my computer recognize it. all the phone does is start charging. ive tried all the other ports and changing the default action on the phone to mount sd and all that but nothing has worked. its becoming a pain in the ..... yeah.... can anyone help me out?
edit: i have also tried many other known to be working usb cables
Try a new usb cable.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
usb cable
i have also tried many new usb cables... sorry i forgot to mention that.
Can you try a different computer? Trying to identify if it's a computer problem or a phone problem.
i dotn really have the option of using another computer... i think it is the computer but i am not sure.
Plug another device into the computer. 1 that is known to work. If that does not work you will need to uninstall your usb drivers and reinstall them with no devices attached.
For more information google hardware manager usb.
If this doesn't solve your issue it would either b a virus or hardware failure. If your phone charges fine I seriously doubt it is your phone that is the problem.
I almost forgot. The android usb drivers have been updated since the last release of windows. I would look into this as well.
Sent from my HTC Magic using Tapatalk
Do you have Sync installed?
gutrenchladd said:
ok so this has been happening for a while and im finally tired of it...
I plug in my cdma hero fully rooted running CM 6 with the stock usb plug into my computer and neither my phone nor my computer recognize it. all the phone does is start charging. ive tried all the other ports and changing the default action on the phone to mount sd and all that but nothing has worked. its becoming a pain in the ..... yeah.... can anyone help me out?
edit: i have also tried many other known to be working usb cables
Click to expand...
Click to collapse
Make sure you have compatible and up-to-date USB Drivers. Another thing, make sure you have HTC Sync installed.
Check the permissions on the computer with USB Ports.
The phone might be bad. I had this problem and Sprint replaced the phone
Same problem here... my wife's hero is recognized with same USB cable and same computer ... but mine wont recognize ... it started doing this after I flashed to a sense rom to update prl ... could that have screwed it up?
Sent from my HTC Hero CDMA using XDA App
argonzal said:
Same problem here... my wife's hero is recognized with same USB cable and same computer ... but mine wont recognize ... it started doing this after I flashed to a sense rom to update prl ... could that have screwed it up?
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Please try the suggestions made earlier and either deny or confirm the facts.
- Posted via mobile
ok so i have tried everything listed above except replacing the driver with newer ones because i cant even get it to show up in device manager... i have uninstalled and reinstalled sync multiple times... i plugged in my friend evo and it was recognized immediately. so im guessing its the phone. not sure if sprint will replace my phone as i dont have insurance.. also i need to just re.stock my phone then im guessing... gotta figure out how to do that.
gutrenchladd said:
ok so i have tried everything listed above except replacing the driver with newer ones because i cant even get it to show up in device manager... i have uninstalled and reinstalled sync multiple times... i plugged in my friend evo and it was recognized immediately. so im guessing its the phone. not sure if sprint will replace my phone as i dont have insurance.. also i need to just re.stock my phone then im guessing... gotta figure out how to do that.
Click to expand...
Click to collapse
You need to go to the 'device tree' in device manager this is the default and only view on windows xp. You are looking for usb root port or .... well hold on ill find it. Im assuming vista here?
It doesn't say it in the article but from my experience sometimes it can be selective about which devices it will allow to connect.
Unplug your device now.
Removing the drivers and re-installing them erases all the current configurations. Yes your computer remembers everything you have ever plugged into those ports until this point ↓
http://support.microsoft.com/kb/817900
I hope you remember to google for the latest android usb driver before you plug it back in!
If you didn't just go through the steps again at the microsoft site. Reopen the new drivers From android project Then plug your device in. Keep me posted.
Oh and you cant 'Revert your phone to stock' unless you made a backup of the stock rom before you flashed it. Well you could also have another copy of the same phone lying around... And even then when they send the device to hardware quality labs they're forensic equipment will tell that the locks have been snapped. Your phone might come back with a bill.
↑ Things of this nature are usually against customer service policies but in today's economy nothing would surprise me.
I hope you're not panicking! If you couldn't tell I have run into this problem more than once over the years, so the odds that your phone is jacked up are slim to none £
- Posted via mobile
you can always just download the stock rom from sprint for and update cant u? at this point i might as well insure it then have it get "stolen" just to get a new phone.
Lol. No comment ;D
- Posted via mobile
You can always try the android drivers in my post on how to install adb. Its in the hero dev section. I made that thread because some users were having trouble installing the htc drivers. As usual I'm mobile so I can't link you but you should find it no problem. Hope it helps good luck
Yea it's me again with the
" Modified Hero"
gutrenchladd said:
you can always just download the stock rom from sprint for and update cant u? at this point i might as well insure it then have it get "stolen" just to get a new phone.
Click to expand...
Click to collapse
Yes you can revert your phone to stock, don't worry. Just download the RUU from Sprint or HTC's website and run it with your phone plugged in. If you ever can get it to recognize it anyway, lol.
After racking my brain for a few days, a couple hours each day, I've fixed my issue with my device being unknown.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Has anyone had any luck with this?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
So I just updated my Bionic to ICS, YAY!
But, root isn't working, BOO! :crying:
I am relatively knowledgeable in this stuff; it is both my profession and my hobby. Investigating this issue has led me to believe that my problem is that the ADB interface does not show up in device manager (Mass Storage, MTP, and PTP mode have the same result) on Windows 7 Ultimate x64. When the device is connected in AP fastboot, however, the driver does show up and works fine. Additionally, when I try to manually add the driver, it fails to start (code 10).
What does show up, however, is the Motorola USB Networking Driver (MTP only), under network adapters.
The upgrade to ICS was performed with SamuriHL's HoB (ADB), and in an effort to resolve this issue, I did it again with HoB (Fastboot).
Can somebody please help?
Thanks,
Overkill
EDIT: I downloaded the SDK and ADB still doesn't list my device. I do know that the IP used by the Motorola driver is 192.168.137.2 for my device (.1 for my PC) and that "adb connect 192.168.137.2" fails to connect on the default port (maybe another port?)
Thanks again! I feel naked and powerless without my root =(
Do you have USB debugging enabled under Developer Options?
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
OverkillSD said:
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
Click to expand...
Click to collapse
I had this problem, reinstalling latest Motorola device manager fixed it for me.
No go on that either.
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
Weird. FDR only kills user settigns and user apps - so, it seems like there was an app that was blocking ADB access. Which is extremely strange, b/c that should not happen, unless you have some sort of firewall on the BIONIC itself (or else something like DroidSheppGuard running).
beray5 said:
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
Click to expand...
Click to collapse
Not always true - you may need to reboot the phone. I can switch from any mode to any other mode and the connection pops up within 5 seconds every time. Of course, I'm running Win 7 Ult x64, and I only use the direct connect ports on my computer, no hubs, no USB 3 ports, and I never install the Motorola Device Manager software, only the direct USB drivers that I extract from the installer myself. Any one of those may be a factor in why it works for me, or some combination thereof.
However, I do know that I am not the only one for whom the switching works without rebooting either computer or phone....