I'm having trouble sideloading apps to my G Watch. I run ADB, connect everything, start debugging, and it says it is connected. Then, when I type the "adb -e install APPNAME.apk" it immediately tells me "Invalid APK file: APPNAME.apk" even though the apk is in the adb folder. I've tried multiple apps so far and none of them will work. Any ideas?
Nobody?
I have the same problem with my LG G Watch R
Sent from my VS986 using Tapatalk
Related
Hi Everyone,
I am currently trying to root my Defy by using the method outlined at the Motorola Defy: Full Update Guide however once I get to this stage...
adb shell
NOTE: You should see a "#". If you see a "$", then the exploit didn't work, please repeat steps 4 & 5.
mount -o rw,remount /system ...
Click to expand...
Click to collapse
I am met with the message "error: device not found", and if I run the command "adb devices" I am met by the message "List of devices attached", and nothing is show.
I have installed the relevant drivers, both those provided by Motorola through RSD Lite, and those provided by Google through the Android SDK. Furthermore I can see the device through RSD Lite, so I am convinced that the Windows driver files are fine, furthermore USB Debugging is set on the phone, and the connection type is "NONE", which in the case of the Motorola Defy is the same as "charge only"!
If anybody has any suggestions on how to overcome this issue they will be greatly appreciated.
Kind Regards,
Davo
Search for motorola defy "end user" driver. My adb started working after installing that
Sent from my MB526 using xda app-developers app
I just got the Verizon G2 and have installed the drivers from the device itself and tried to download the driver but I cannot seem to get ADB to work correctly. I am using Windows 7 64 and when I type in adb devices in the command prompt I get 'adb' is not recognized....
I have USB debugging enabled and can see the debug icon in the notification bar, I also see the device listed as adb in device manager. I have even tried adding the path manually to environmental variables. Still I cannot use adb, anyone else having this issue? I never had this issue with my Galaxy Nexus or SIII, is there something I am missing?
chongmagic said:
I just got the Verizon G2 and have installed the drivers from the device itself and tried to download the driver but I cannot seem to get ADB to work correctly. I am using Windows 7 64 and when I type in adb devices in the command prompt I get 'adb' is not recognized....
I have USB debugging enabled and can see the debug icon in the notification bar, I also see the device listed as adb in device manager. I have even tried adding the path manually to environmental variables. Still I cannot use adb, anyone else having this issue? I never had this issue with my Galaxy Nexus or SIII, is there something I am missing?
Click to expand...
Click to collapse
I had to use the drivers from a post I found on XDA (can't find it right now or I would link to it). Not the ones that automatically installed from plugging the phone in.
PC Connection>Internet>Ethernet for adb.
From a Verizon logo plastered G2 bastard
OK I will look around here for some other drivers, tried the ones from the G2 rooting thread, nothing changed.
Yep I enabled the Internet connection using Ethernet I can see the debugging icon in the notification bar.
truckroot said:
PC Connection>Internet>Ethernet for adb.
From a Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
Maybe these solutions will help you...
http://forum.xda-developers.com/showthread.php?t=567955
I had to update adb to 1.0.31.
Type adb version and see which you have, if it I'd 1.0.29 then update it.
Sent from my VS980 4G using Tapatalk 2
truckroot said:
PC Connection>Internet>Ethernet for adb.
From a Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
Or you can goto the about phone>software menu and tap build 5 times to get the dev menu back.
I tried installing multiple drivers to my LG G Watch but always appears offline on ADB (cmd)
I made sure I enabled adb debugging and bluetooth and I tried both methods and I cant get it to work....
can anyone help me? I really want to install wear messenger :fingers-crossed:
Are you using adb.exe from the latest SDK?
Have you already forwareded with the adp ?
If not just type this in the console
adb forward tcp:4444 localabstract:/adb-hub
After that type this:
adb connect localhost:4444
It should work on this way to set the state to online
Sent from my SM-N9005 using XDA Free mobile app
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
badhat said:
Trying to run adb results in the USB notification to cycle off/on on the new Moto G5 Plus. I've tried multiple cables, computers, and a factory reset of the phone (both times with the factory image).
Has anyone encountered such an issue?
Basically, I can enable debugging mode and connect my computer, but the moment I issue `adb start-server` the USB notification on the phone begins to cycle. There is no message to authorize the device or anything. For what it's worth, this computer works fine with another device (as does the other). I've deleted the .android directory and saw no change, too.
Click to expand...
Click to collapse
I'm confused... What are you trying to do? I've never used that command...
acejavelin said:
I'm confused... What are you trying to do? I've never used that command...
Click to expand...
Click to collapse
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
badhat said:
The `start server` command just begins to run the adb daemon. It is run without explicitly issuing this command if you run something like `adb devices`. It's like setting up the environment without actually querying anything on the device.
Click to expand...
Click to collapse
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or not.
acejavelin said:
I tried this just out of interest... revoked all ADB authorizations, rebooted my phone and PC, and connected and did a "adb start-server". It popped up the authorization windows like normal, I approved it and it worked like normal. Subsequent kill-server and start-server commands had no unusual effects either after revoking authorizations or now.
Click to expand...
Click to collapse
OK, I tried using a different Android SDK (grabbed from https://dl.google.com/android/repository/platform-tools-latest-linux.zip) and now it's working. There must be something about the one my distribution packaged that is broken.
Code:
$ adb version
Android Debug Bridge version 1.0.39
Revision 8.0.0_r11
$ LD_LIBRARY_PATH=$PWD ./adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /home/badhat/Downloads/adb/platform-tools/adb
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Did you get permissions on your phone when popup appears?
No. The phone doesn't pop up the permission question. But I don't know why.
Don't know but as long as you don't give permission you can't sideload
Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds
I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!
Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?
ADB devices returns your device is offline?