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

ADB issue with captivate

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

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

[Trifecta] Jelly Bean Root

****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.

I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.

Debugging in Android Studio, anyone have it working?

Not really doing anything all that fancy, been using android studio for a few years now, before the bumblebee update i could a debugger attached eventually if i tried hard enough. After the update i can't get it to work at all. Adb can see the device, i can open a shell, install, uninstall etc.
Personally this makes app development on the platform 100x harder without this feature. I've tried emulator for multiple different versions of android, usb debugging, WiFi debugging (post bumblebee update android studio claims my pixel 5 doesn't support it which i assume is google trying to get me to buy a new phone despite my phone supporting wifi debugging just fine prior to the AS update). I even tried running genymotion and couldn't get the debugger to connect there either. I'm kind of at a loss. Running ubuntu 20.04. Tried a fresh image on a laptop and no dice there (repeating all attempts on the fresh image).
Are there alternatives that actually work or some magic setting i've failed to find on google etc?