[q] ADB Mac can't find galaxy nexus - Samsung Galaxy Nexus

Anybody get adb shell working on mac in terminal? Device doesn't even show up for me

Same issue here....

i got it to be recognized on my windows computer, but when i pull packages.xml nothing shows up anywhere.

No issues here; ensure developer/USB debugging is turned on and you are using a newer platform tools from Google.
You should be on platform tools Rev 9 or higher.
(If you downloaded the SDK go to the directory in shell/terminal on your mac, cd tools, then run ./android
This will let you do GUI based updates to the tools
In case you never had the SDK - I have posted my working Mac ADB and fastboot's here.

I have the same issue. I don't get it to be recognized when using ./adb usb or ./adb devices.
OS : Mac os X Lion 10.7.2

has anyone figured this out?
as far as I know I am running the latest SDK... but I will double check.
frustrating.
has anyone tried connected via Parallels?
UPDATE - just confirmed my SDK is at v15, so that can't be the issue.
Also - NPS_CA, your abd didn't work any better than mine - still not showing up.

make sure easy tether isn't installed on mac

Related

New to ADB and have a few questions I can't find the answers to...

Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
criccio said:
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
Click to expand...
Click to collapse
Does it have anything there when you type adb devices? Should come up with a HT and some numbers after it....being your device, EVO.
Actually, there is a step by step Guide for EVO root, and a ADB Guide for Beginners
Your device isn't being recoginized check the driver if u r in windows.
Ok, I managed to figure out the cryptic SDK installer and download the USB driver package to android-sdk-windows\usb_driver. I used Device Manager to install the driver and I pointed it to that folder and I get the "Windows was unable to install your ADB".
Are you already Rooted? as for the Drivers, when I plugged in my EVO via USB, it installed drivers...I also copied the HTC Sync that came on the SDCard w/phone, onto my pc. But I did not have to do anything further.
Can I ask what you are trying to do in adb? and is this for the EVO?
use the cd command to make sure you are in the android sdk tools folder
if you want adb to work
what i do
1. use the cd command to go to the directory where my sdk is located which for example is c:\androidsdk\tools
2. there you go
3. if you want shell make sure your device is connected
"adb shell"
and have htc sync from evo's sd card installed
http://myevo4g.net/main/?p=83
Sent from my HTC EVO
download htc sync and install that. i was having the same problems and apparently the usb drivers that get installed with that app are the ones that worked like a charm for me.
Try
Code:
./adb devices
Instead.
--> try" adb start-server "
If your HTC dont show up, it's usually because the ADB server isnt running. Hope this helps =]
I've rooted a hero before and felt pretty confident with android sdk, usb drivers, etc. After spending an hour trying to get it to work on my win 7 64 bit system, I thought it might save someone some time if I posted what finally allowed me to get adb to work.
My problem was the computer wouldn't recognize the EVO as a device. Even after I installed the usb drivers through android sdk. I tried to manually update them through device manager (pointing it to the usb drivers directory) and still no luck.
As the video linked above showed, the missing piece for me was installing htc sync. use the version that comes on the phone. So connect the phone to the computer, mount it as a drive from the phone menu, then copy over the htc sync directory to your computer, then run it. The version on my phone was 2.031. THEN the computer will recognize it with usb debugging turned on and I'm able to adb to the phone through the command prompt.
Hope that helps someone. Sean

[q] adb shell from any computer

Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
UND3RTAK3R said:
Is it possible; from any computer, within the command line to run commands on any android devices/phone ie: adb shell, adb devices, adb logcat, adb push that already has android adb/sdk installed?
The reason I asked is cause I installed android sdk/window usb driver on my main laptop with no problems, but I recently purchased another laptop went through the same setup procedure but my adb does not recognize or see my phone when I have it plugged in via usb.
I am at a loss and dont know what to do...
Click to expand...
Click to collapse
1) install HTC sync to get the Evo drivers
2) install Android SDK
3) add the tools folder with adb.exe in it to your windows Path or always navigate the command line to that folder.
should work

[Q] Not able to debug!

So I am a bit done with just flashing other roms to my kaiser and also want to develop some apps and want to experiment with making my own roms, but initially just porting roms from other devices like the HTC wildfire. But I am not able to use debugging:
So this is what I have done I have installed the android sdk and also installed the ADT plugin for eclipse. Then I have compied the android-sdk file to the root of my c drive so it is easier to use the command line interface with this file. I then run the following commands in the cmd, as admin:
adb kill-server
adb start-server
adb devices
And here is where the **** just hits the fans I am unable to see my device in the list of devices. While my device is recognized by the computer as ADB Interface > HTC Dream Composite ADB Interface in the device manager section. (But I must note that when I click on the device it is noted: "Device cannot start. (code 10)" ) Also when I double click on the device in the regular computer windows (where all your hd's are showed) the file system of the device is empty!
So does anyone have any advice?
Have you test it from a live usb or CD GNU/Linux like Ubuntu?
Nope, I hoped that it would work in Windows, but I will try it in Linux if that would solve it.l But can you see anything that i am doing wrong or is it just Windows
I always have problems with USB management on Windows, all versions...with all my computers. Linux kernel seems to be better, imho, for USB.

[Q] adb shell returning device offline

I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
stevetrooper said:
I have all the JDK and Android SDK components installed on my Windows 7 box. I have enabled USB Debugging and when I try to run adb shell I get the following error:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
error: device offline
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
List of devices attached
5099ba28 offline
Shows the device attached to my PC.
I have killed and restarted the adb server, rebooted my phone, no luck.
I have never had a problem before with adb. Do you need to use the USB 3.0 cord that was included with the Note 3 or will a regular mico USB work?
Click to expand...
Click to collapse
regular should work. That is just the data transfer speed.
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2247471
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
stevetrooper said:
Figured out the problem, I needed to upgrade my adb to the latest version (1.0.31). When I ran the adb shell, a pop-up window appeared on the Note 3 and I confirmed. Now I am able to access.
Click to expand...
Click to collapse
Yeah, the new adb(d) (6 months back, iirc) added some security where you have to confirm the rsa fingerprint of each machine you connect to. It's a little annoying, because you HAVE to connect adb via USB first, and only then can you use adb via wireless, which is all I ever use anymore.
(edit: adb security added in 4.2.2, which was released in february)

[Q] adb on Mac OSX

Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works

Categories

Resources