Database Users

ADB does not find device

Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?

Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.

Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.

Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.

just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.

Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02

Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!

[Q] ADB not recognizing, please help

Okay, I have a permarooted MT4G with S=Off, and I want to use the gfree method to unlock my SIM and get the universal CID while I'm still on the stock kernel. All of the guides I see for that push the gfree files using the ADB.
Problem: I cannot get the Android SDK to recognize my MyTouch 4g. (SEE UPDATE)
I followed this guide http://forum.xda-developers.com/showthread.php?t=834748 to try and set up the ADB to no avail. This is what I did:
-- Downloaded the SDK, booted it up, let it update. Booted it up again, let it update EVERYTHING (took like 30 minutes) again. It has no more updates to install.
-- I tried adding adb as an environmental variable in windows, but the command prompt, no matter where I start it from, does not recognize 'adb' as "an internal or external command, operable program, or batch file." (works now)
-- The HTC Drivers that came with my device have been installed on my computer. So, I uninstalled them, only to have windows reinstall them as soon as I plug the device in (I'm running Windows 7 x64 home edition, Build 7601).
I tried going here http://forums.t-mobile.com/t5/HTC/HOW-TO-Get-ADB-to-recognize-your-myTouch-4G/m-p/540017 and using their technique, no dice. My computer has the exact same drivers as when I started, and I have a digital paperweight of a SDK. (see update)
UPDATE: I now have a working ADB (big thanks to TrueBlue_Drew and his guide for us noobs) that recognizes my MT4G, but I have another issue:
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct windows to the usb drivers I downloaded from the both of the guides I've used, but windows wouldn't accept either one. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since adb is working? Any help on that end would VERY MUCH appreciated.

If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk

neidlinger said:
If you are using true blues method are you changing your target folder to c:\adb?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb

corruptsmurf said:
Do you mean the target of the environmental variable? If so, then no, because the name of the folder is android-sdk-windows, making the target C:/android-sdk-windows/tools, unless I'm totally off-base, which is probably what's happening.
Still, I don't think the target is C:\adb, cause I don't have anything in the root of my C drive that's named adb
Click to expand...
Click to collapse
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App

Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)

So close, yet...
TJBunch1228 said:
Is the adb.exe file in your tools folder? Also you should change the name of your SDK folder just so that its easier to type in the terminal. I made mine simply ANDROIDSDK.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Actually no, adb.exe isn't It has a .txt named "Adb has moved," not really sure how to proceed from here; I downloaded the SDK that was in the topic I linked above, and just allowed it to update. More below, and thanks for the response.
jdkoren said:
Have you installed the drivers successfully? Here's what I do and it's worked on multiple computers and on both Windows 7 and XP:
- Install SDK
- Turn on USB Debugging on the phone.
- Plug the phone into the computer and let it try to install some stuff. Ignore any dialogs saying there were errors
- Mount the SD card and run the HTCDriver.exe file that came on the sd card when you got the phone.
- Unplug it from the computer and plug it in again.
- Open a command prompt and navigate to the tools subfolder of the android sdk. Run adb devices. (Even if the first time doesn't return your device's serial number, it should say that it's installing more drivers. Once that completes, adb devices should return your S/N and you should be good to go.)
Click to expand...
Click to collapse
Yeah, the problem is that my PC doesn't list any errors when I plug it in. BUT BIG NEWS, I followed the ADB for noobs guide (http://forum.xda-developers.com/showthread.php?t=928370), and I realized, as I said above, that my adb.exe file was nowhere to be found, so I used the one from the noob guide, and it could recognize my device in ADB. BUT it could not recognize my device in fastboot, so after much frustration, I decided to uninstall the drivers and reinstall using pda.net. Whatever it did, it worked, because adb and fastboot both show my serial number under devices. Thanks to the both of you for your help.
FINAL QUESTION: Now that my MT4G is showing up in ADB, I realized I screwed up again when I discovered a "Android 1.0" item in the Misc. section of my Devices window in Control Panel. It currently says that Android 1.0 needs troubleshooting and the drivers aren't working. I tried to direct it to the usb drivers listed in the both of the guides listed above, but windows wouldn't have it. Am I using the wrong drivers? Which ones should I tell windows to install? Should I even worry about it since I can use adb anyhow? Any help on that end would VERY MUCH appreciated.

[GUIDE] Setting up fastboot for linux

I've just updated the Dell Streak 5 wiki with a guide to setup fastboot for linux in the Flashing guide section.

Oh, the sdk finally readded the fastboot binaries for *nix and osx are finally readded.
Main reason the nix and osx guides were stubs were that previously the fastboot binaries for all 3 os groups were missing from like platform-tool r6-r9 and they're included again in r10
I'm gonna update fastboot+adb.zip to include these files and take a look at the win drivers and do a big update.
I'm also going to rewrite your portion once I get fastboot+adb.zip reorganized and bring it to parity with the win version. Thanks!
Finally, the *nix portion will be added to the s7 and venue guides too to maintain parity and the s10 one when I get around to making the rest of it

Yeah, i saw your edit, i've since shortened the guide, because the relevant additional info is available on the android website and i've linked it, however, having only adb and fastboot in a zip is even better.
I'll see if the Mac version works on PC-BSD 9, and if it does, i'll add that as well (you never know)

No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?

Ultimately only the basics will be covered, I'm not willing to add (or even let others add) a dozen different branches to support every different flavor of linux.
When I'm ready to release a new Fastboot+ADB I will trim it down more if needed and leave it at that, currently it's pretty much about what I'd like it to be, it's mostly just a little formatting to make it match the rest of the guide.
The guide techincally also skirts the issue of different windows versions, there might be some minor things depending on which ver of windows and if it's x64/x86 but those details are left to the user to fill in on their own.
Users should be able to fill in some stuff like this on their own, just like the implied availablity of a unzipper.
If it's something that's specific to fastboot or adb and it's missing, we'll add it of course.

bazzoon said:
No command udev in my fedora. At least in the my user PATH! In my root's PATH, I have only udevd and udevadm! I use Fedora, are these instruction Ubuntu specific?
Click to expand...
Click to collapse
Udev is the udev daemon. I'm not familiar enough with Fedora to know what's the command to restart it, but you could reboot the computer and the new rules should take effect.
Yes, it is Ubuntu specific, since i use it, and the intructions on the official android site are for Ubuntu.
Actually the only thing that isn't mentioned anywhere, except in the Streakdroid install guide, was adding the -i 0x413c option after fastboot (or the respective USB VendorID), an omission that took me along time to find and kept me really frustrated by being unable to change ROMs.
Edit The Manii
I've linked to the SDK-Platform tools zip on the official android site, to save a few steps of installing the full SDK, so for now, you don't need to host a separate zip of adb and fastboot, until Google updates the SDK.

-i 0x413c is optional depending on how your env is set up.
I believe that optional step you made to register that ID makes it optional on *nix too, but as I dont use fastboot under linux I cannot verify.
It is optional under windows though.
I merely havnt finished testing the s7 drivers, the zip was missing the *nix/osx fastboot binary, it always had the adbd binary

For me fastboot didn't work without that option, just stayed on 'waiting for device' despite having read pretty much every guide that's out there for setting up fastboot and adb on linux (and ubuntu specifically), even though adb worked perfectly fine.
As far as not adding a custom rule in udev, I'm pretty sure it's needed since it's posted on the official android site and it's stated that it's required in order for the OS to recognize your phone.
As for the Mac OSX version, just downloading and extracting the SDK Platform-tools package and running fastboot from there should just work, but i don't have a Mac to test it on.

[Q] Can't install apks despite my device is NOT adb offline.

Ok I've been following every step some posts follow in order to upgrade every Android SDK component to the last version (adb, sdk manager, avd manager, usb driver, web driver and ALMOST EVERYTHING fetched in the sdk manager). I have my Nexus 4 on stock 4.2.2 (JDQ39) working like a charm with its USB driver with my PC, the debugging is on, also the unknown sources option (if any), the phone is properly linked with the "adb fingerprint protection" thing (can't remember the correct name), and last I can see my Nexus 4 detected on adb devices command AND STILL I can't install a sole apk, in this case I'm using Android Commander 0.7.9.11 and nothing, I've tried with Droid Explorer or even Moborobo and nothing.
However in my cousin's laptop I can successfully install apps.
I thought it must be something wrong or corrupted with my OS, so I reinstalled Windows 8 (x64) and take care about all the drivers and everything mentioned above and still... I get the same, so I'm running desperate here.
Maybe it's something simple, I just need someone to help me.
Sorry if I writed so much... I only did it to avoid Android's ABC related questions.
Thanks in advance for your time.
Best regards.

Does "adb install path/to/app.apk" work?

chromium96 said:
Does "adb install path/to/app.apk" work?
Click to expand...
Click to collapse
When I do it I get this:
Code:
C:\sdk\platform-tools>adb install C:\mxvideoplayer.apk
2752 KB/s (6930955 bytes in 2.458s)
pkg: /data/local/tmp/mxvideoplayer.apk
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]

Can I access the X Play via fastboot on Win7 without installing Motorola Drivers?

I just got my Moto X Play and wanted to root it and flash CM13. I installed the Google USB Drivers to get Windows to recognize the ADB interface, and getting into fastboot mode with ADB works just fine. But once there, "fastboot devices" fails to recognize the device. The device manager shows an unrecognized device "Fastboot lux S" for which the google USB drivers don't work. I've read that this should be fixed by installing the official Motorola drivers, but I would like to avoid that if possible - I'm doing this to get rid of the Motorola crap, installing more of it on my PC to do so would be disappointing.
So, I've got a heap of questions:
- Can I use fastboot on Win7 without installing Motorola-specific drivers? It seems that there should be a generic driver for the fastboot interface as it's a feature on all modern android devices AFAIK.
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
- Does my objection to the Motorola Drivers make sense? Are there any benefits to having the drivers installed if I flash CM on the device?

The drivers are irrelevant to the OS you want. You need the drivers, install the drivers. Your computer is trying to talk to the phone, and right now they are speaking different languages, the driver is an instruction on how to talk to the phone. It has very little to do with Motorola, google didn't build your phone, they supplied the OS. Fastboot is effectively the BIOS of your phone, imagine what would happen if you flashed the wrong BIOS on your computer., would you call Microsoft and say fix it? no.
Install the damn drivers and get over it.

ImWarped said:
It has very little to do with Motorola ...
Click to expand...
Click to collapse
That's exactly why I asked, I thought this was a standartized part of Android for which there might be a generic Windows driver - I guess that's not the case, thanks for the clarification. But I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.

fckmoto said:
- Is it possible to use Linux to connect to the device via fastboot? I doubt there's a Linux driver from Motorola... but if it's possible to get fastboot access, I'd just boot a live CD and do the unlock from there.
Click to expand...
Click to collapse
fckmoto said:
I googled around and unlocking under Linux seems to work (and without requiring a driver), so I'll try that first.
Click to expand...
Click to collapse
Since my wife moved to an Android phone, our house is Microsoft free. Being a fairly novice user who likes to tinker, this always introduces extra layers of doubt and uncertainty ...even fear, at times. I am forced to wonder, in the presence of all the Windows software and Windows-based procedures and advice, does it work on Linux?
My answer, so far, over three phones, is that if it is adb or fastboot stuff, then, yes it does. Or, at least, so far, everything I've tried works.
Depending on your linux distro, you might have to install some extra package containing those commands. You might want to install the whole Google android package. 99.999% developer stuff, but includes the two commands that you want. It's probably more up-to-date than the Linux-distro versions.
You might have to insert a line with some manufacturer ID (I didn't for the X Play) in some configuration file.
Look... my anti-MS biases show even through a thick overcoat. But do the linux thing only if you want to do linux. By the time you've read this post, you could probably have installed those drivers .
Does my objection to the Motorola Drivers make sense?
Click to expand...
Click to collapse
No.

Thad E Ginathom said:
No.
Click to expand...
Click to collapse
Heh, I guess it's somewhat thick-headed to look for alternatives instead of just installing the drivers. My main problem with that is that Motorola doesn't offer a direct download of the driver but wants me to install a driver manager tool instead... I've kept my pc crapware-free thus far and intend to keep it that way If it's as simple as installing a few Android dev packages under Linux, I'll definitely take that route.
But with bash and the full Canonical repositories coming to Win10, maybe one could use the Linux adb and fastboot binaries under Windows in the not-so-far future... I wonder if those would then work without a device driver

Install 15 seconds adb 1.4.3 and run it in your fastboot folder you create in C of Windows7, no Motorola drivers.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118