Database Develop

ADB broken after Froyo OTA?

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

[Q] Help : Advice or Instructions Needed Bad : USB Port Dead

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?

[SOLVED] USB Device Unknown

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

[Q] USB Not Recognized.

So I got my Samsung Galaxy Tab (sprint CDMA version) today and when I first plugged it into my computer the drivers installed fine. I was able to mount the sd card and transfer files with ease. I then proceeded to root the device hoping to put a new rom on it, I've got a captivate and am not a rookie at all when it comes to flashing roms via odin, cwm, etc...I first put the device into debugging mode which is where things got weird. As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable". I have the correct updated drivers for the device both from the Samsung website and via the Android SDK tools. There should be no reason why this happened. So I then took it out of usb debugging and plugged it back in and bam, again, "USB Device not recognized". I've been installing and uninstalling drivers, the device itself from the device manager, and have been trying other numerous ideas. I've been Googling and searching for hours upon hours at this point and don't know what to do next. Odin does NOT recognize the device when in download mode and the device does charge when connected to the computer. I have tried a different cord with the device and different computers and it's all the same story, works until debugging is enabled then it will no longer work no matter what. I am fairly sure at this point the device itself is malfunctioning or defected but I wanted the opinion of others before sending it back. I am pretty sure have tried everything and am doing everything right. Please help if you can, if not I still appreciate your time! Specs are listed below:
Hardware Version
P100.08
Model Number
SPH-P100
Firmware Version
2.2.1
Kernel Version
2.6.32.9

Ebicoustic said:
As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable".
....the device does charge when connected to the computer.
Click to expand...
Click to collapse
1. Just wondering, have you installed Kies before connecting the tab to your PC?
2. The SGT will not charge "normally" with a USB connection. It will trickle charge, which is very slow way of charging, and the device will not indicate that it is charging. Does your device indicate it's charging? (As stated above)
Hit thanks if I deserve it..

FWIW, My SPH-P100 Sprint Galaxy Tab has been an adventure as well. Enough so that I wish I'd known more and held out for a GSM model.
I am not even sure if Kies and/or Odin will in fact work with the Sprint GT. I've had almost no luck with a variety of attempts. Even the widely used ClockWorkMod Recovery does not include the Sprint GT among its list of supported devices. It does include the CDMA Verizon GT - and some folks have posted that they eventually got that to work.
I did get the SuperOneClick to work and setup root privileges on my tab. That part works fine. But so far I've been reluctant to experiment too much with the various tools that "almost appear that they should work" as I have too little experience with this Android tablet environment to feel comfortable that I can recover from the eventual disaster.
Am hopeful that Samsung will in fact follow through on their commitment to provide upgrade of all GTs to Gingerbread 2.3.3. If so that may be enough for my needs. I WOULD like to get the Netflix viewer app working. Is frustrating to already have a Netflix account and not be able to access it via my GT. A guy down the hall can get Netflix on his Droid X - which really bugs me! lol
IMHO, Google/Samsung/Motorola/HTC/etc. have done a horrible job rolling out Android - both on phones and tablets. Netflix really highlighted this when they decided to do device-by-device testing and certification before allowing Android devices access to their movies. Apparently the 'capabilities' inherent to various Android devices varies so much (and not just OS version) makes it difficult to roll out something as simple as Netflix access. It is frustrating. And the only "solution" so far is to wildly 'hack' your device in the hope that you'll shake something loose enough to make it work as you wished it had when you bought it.
Enough whining for now. But it has been a very frustrating and disappointing experience.

I installed Kies AFTER installing drivers and connecting the tablet and it has no effect. I also learned after googling that kies does not support the sprint cdma version though I could be wrong but many people have stated this. And the device does charge and does so very fast actually, 20% to 100% in 4 hours. I don't think it's trickling down as you say because it is very clearly charging at a fast pace. Thanks for the quick response though! And I have also tried superoneclick root and other methods i.e odin but neither can find the device. I know some people have had luck with this sort of thing after upgrading the rom and/or flashing firmware onto the device which I would love to try but unfortunately without windows being able to see the device, none of this is even remotely possible.

I think the reference to slow charging on USB is really refering to using a data USB port on a notebook or desktop computer. This is because the data USB ports are limited in how much current they will pass. My SPH-P100 will in fact charge on a data USB port - but very, very slowly. In fact if the device is ON it may just barely be breaking even.
The USB charger is certainly capable of charging at a very reasonable rate.
I'm still waiting on the 2.3.3 update that Samsung has promised. It only took them 5 months to get the 2.2.1 update out for my Fascinate! So maybe we'll see the 2.3.3 update by Thanksgiving...or Christmas...or...

Root not working after ICS (ADB can't see it)

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....