That is the error I get. I don't know why. I am connected. Well at this point I don't know if it refers to another kind of "offline" stuff.
I didn't find any answers to this specific error
09/19 02:49:11: Launching 'app' on samsung SM-J710MN. Installation did
not succeed. The application could not be installed. Installation
failed due to: 'device offline'
There are two possible reasons for this behaviour. Either your Samsung device is faulty or this is an adb issue. To confirm, enter this command into your terminal while your Samsung device is connected:
adb devices
If the result returns the name of your Samsung device, then there's probably a problem with the Samsung device.
However, if your terminal does not recognize this command, it means you have to install Samsung adb driver on your computer. This way, your computer would easily recognize your Samsung device. For Windows, there are a ton of links out there where you can download Samsung adb driver; I have not verified any of them, so you might have to do the search by yourself. Nevertheless, I hope you understand the problem now.
I hope this helps.
Merry coding!
Can you run the following codes in the terminal and share the result?
adb devices
You can also try this method
adb kill-server then adb start-server
GO to avd manager now you are able to see installed avd. from that actions select wipe data, and run your project. this Worked for me.
I am using Android studio 3.4.1, In which my projects are not running in real device. but not having any problem in emulator.
After connecting the usb and i have run the app. then getting this error. after that device is not even listed in the available devices.
error got in logs:
Installation did not succeed.
The application could not be installed.
Installation failed due to: 'device '711KPMZ0603459' not found'
Retry
Retry also not working.
I also tried in Android studio Beta 1 and Beta 3. same problem happening.
can any one help me in this?
FYKI:
1. USB debugging enabled.
Tried USB option for File Transfer, USB tethering, No data transfer.
Tried with different cable as well.
Problem identified only after updating 3.4.1 android studio. Also facing in 3.5 Beta 1 and Beta 3.
Same kind of problem already added in Issue Tracker. https://issuetracker.google.com/issues/122892907
Kill and Restart the adb manually through Terminal using below comments. use cd to go inside platform-tools under Android sdk folder.
./adb kill-server
./adb start-server
PS: Before posting this questing here, i already tried quitting the adb in Activity Monitor (which can be opened from spot light)
Activate USB-Debugging in Developer Options and set your USB options from Charge phone to transmit Data.
Well the mark of your phone is important because in my case i use LG G5 and i could not see my device even after turning on developer mode and enabling debugger options.
I don't know the type of phone you use but you can try my solution.
After turning on USB debugging, go to tethering under the networks sections and turn on USB tethering then try again.
Hope It helps!
I am starting my first android project using nativescript.
I want to run my project with genymotion.
In genymotion GUI settings/ADB I am using custom Android SDK tools and genymotion tells me the android SDK tools are found. Also the VirtualBox path is valid, and when I renamed the device the VirtualBox name and Genymotion name both changed. The Virtualbox VM is powered down.
I start genymotion and get the emulator open with a black screen. I then run:
tns run android
per the nativescript docs
I get as output:
Cannot find connected devices. Reconnect any connected devices, verify that your system recognizes them, and run this command again.
I then tried running:
adb devices
and got an empty list so it seems my device is not being recognized, I just don't know why.
I have also tried running:
tns run android --emulator --geny nameOfDevice
This starts the emulator but again just a blank screen. So I guess nativescript knows about the device but adb doesnt?
Any help would be greatly appreciated and apologies in advance if I am missing some obvious android issue.
You should also make sure that your GenyMotion is using the right SDK.
Go to: >> Settings >> ADB
And choose Use custom Android SDK Tools
If the SDk path is found it will be marked with
Android SDK Tools successfully found!
Do not open genymotion before adb initialisation.
Start adb server first
by adb start-server
and then open genymotion to initialise emulator.
After that you should be able to see emulator in list of running devices through adb command. I ran into the same scenario where adb does not list emulators if genymotion is opened before adb initialisation. I hope it helps.
My working solution is:
cd /opt/genymobile/genymotion/tools
./adb devices
You have to use its own adb tool.
Edit: Fixed! Looks like there are very many possible causes for this. Mine was one of the more unusual...
I updated SDK Tools to 21.1 and Platform-tools to 16.0.1. Verified with adb version that I am running v1.0.31. My development machine is running Windows 7, x64.
I have four 4.2.2 devices to test with, a Galaxy Nexus with unlocked bootloader but not rooted, and Nexuses One, 4, 7 & 10, all stock.
The Nexus One, being <4.2.2, works just fine with adb, but all the 4.2.2 devices show as 'offline' in adb, and I have NEVER seen the RSA security dialog pop up on the devices, even after several restarts of ADB (using kill-server), the PC and the devices themselves.
Have tried using different USB ports and cables. I'm using the standard 'Android ADB Interface' drivers from the SDK, but have also tried the 'Android Composite ADB Interface' and 'Samsung Composite ADB Interface' drivers too. I even completely re-installed the SDK from the ADT bundle.
Weird thing is, my colleague can get the popup to show on those same devices without any trouble. I even copied his adb.exe and dll's and tried that and it still wouldn't work on mine. He didn't install from the bundle; he installed ADT into Eclipse, the old-fashioned way, but I doubt that would make a difference. What gives?!
Edit 26/02/2013, 16:41 GMT: An update to Platform-tools 16.0.2 was just released. Hasn't updated ADB (still v1.0.31) and still seeing device as offline, and no RSA security popup in sight.
It turns out I had my ANDROID_SDK_HOME environment variable pointing to an old location which no longer existed. It hadn't caused any other problems (strangely) but it appears to have been preventing the RSA authentication process from happening. Probably should've seen it when I was checking the PATH variable the other week, but never mind.
I found the strange location by running the following and checking the readout:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
After updating the location and restarting my PC, it's now working just fine. Thanks to all who responded.
Best solution I found ever is:
Check your adb version by using the command: adb version for Windows and ./adb version for Linux.
If it showing 1.0.29 please upgrade it to 1.0.31 because 1.0.29 will not respond for JB 4.2.X
It will fix your device offline problem.
If your system already have the new adb(1.0.31) and facing this problem, in that case open sdk and upgrade platform tools to 16.0.1
Restart your device at least one time.. :) it will work fine for all the devices...
I had the exact same problem, and this is what worked for me: if you've created multiple user accounts on your Nexus 7 device, then you won't get the security popup unless you're logged in to the same account that was used to enable USB debugging on the device. Do that, and when you see the popup make sure that you check the option that says "always trust this computer", then it should work for other accounts as well.
ADB_TRACE revealed the answer to my problem (a permissions issue with the ~/.android folder on my Linux system was preventing the key being generated). Many thanks for this.
This will definitely work:
In platform-tools hold shift and right click.
Select open command prompt here.
adb kill-server
adb devices
Say yes to popup on phone.
Your device will be connected.
If still not working try reconnecting device and checking for adb devices again
I did this and it works on my windows 8:
Open Computer -- Manage in File manager
On system Tools/Device manager, remove any existing android related items.
Click "Scan for hardware changes".
The device showing up as a warning sign.
right click the device, click "Update driver software".
choose ANDROID_SDK_HOME\sdk\extras as source of drivers.
On device, turn off USB debugging off and on ( or for several times)
Wow, the popup shows up in the device!
Multiple adb.exe files ?
My problem was solved when deleted a copy of OLD adb.exe from C:/Windows/.
I don't know how a copy of adb.exe got to the C:\Windows\ ?
When I launch adb.exe from android-sdk/platform-tools/ I had no problem with detection.
I had the same problem and setup. Windows 7, x64, Eclipse Indigo, one user on the device etc.
I tried adb devices using v1.0.31 and under no circumstances did I see a pop up on the device. I tried all sorts of combinations of turning on/off debugging, plugging the USB back and forth, restarting the device etc. Nothing worked. I also tried rooting the device in order to manually copy over the finger print file. However, the device went down beyond repair (not to recommend to anyone). I have more than one Nexus 10 so kept on trying with the other ones.
I am using bootcamp though (using Windows on a Mac laptop) so one last attempt was to try the same thing under OSX. On the first attempt doing ./adb devices from the terminal, the popup showed up. I accepted the fingerprint and now it's working in OSX.
I prefer Windows over OSX so this is not an ideal workaround as I still can't get it to work in Windows. I'll keep an eye open for solutions to this but in the meantime, I hope this helps other people with bootcamp issues.
Flip Android debugging on the device off and back on. That gave me the device popup.
I am running Windows 7, one account on Nexus7. I had to actually check the box "always trust this computer" for it to work. It didn't matter how many times I got the acceptance to pop up and select ok. It didn't work until I finally checked the box. Now it's fine and is recognized by adb.
Switching from the Samsung USB drivers (that shipped with the Nexus Root Toolkit) to the USB drivers provided by Google (through their SDK) did the trick for me.
I had this very problem, and found an answer: Either I fat fingered the phone or was not paying attention or it simply did not pop up saying here is the RSA pubkey check to allow for computer, I kept getting offline status. I followed every direction on the map, from having a LONG list in my rules file to reinstalling ADB 50 times. Yes it does need to be version 1.0.31, which I have. If this is you then read on....
Disconnect your device.
Use these commands in the terminal, assuming you are using BASH.
adb kill-server
sudo bash
cd ~
mv .android BAK.android
Now that you have effectively removed the initial RSA key, make sure USB Debugging is enabled on the device. Re-connect the device and pay attention to the screen. Make sure to check the 'remember this computer' box. Press OK. Problem solved.
I had same issue. Not sure if it applies but are you using adb as a root?
For me killing adb server and doing:
sudo ./adb devices list
resulted in security prompt. After accepting it pernamently and running above command I've finally got it to connect.
I had the same problem as OP but originating from an adb.exe copy in C:\Windows, much like user1269737 appeared t have. This had precedence in Windows PATH, so no matter how much I updated he SDK, it wouldn't help as the updated ADB wasn't being used.
Someone told me it might have been a version of the Android Studio bundle that installed it there (go figure...). I can't confirm it because:
1. Current AS bundles don't appear to be doing this and...
2. I install a lot of ROM flashers/tools that bundle ADB (XDA Developers stuff).
So I can't confirm it was Android Studio.
Protip: use adb version and where adb commands in cmd to check what version you're using and which executable you are running
I tried all the these things and still couldn't get Windows to display the RSA prompt on my Android device. After hours, this is how I got it working:
Connect device to PC via USB
[Windows Key] + [R] > [type] devmgmt.msc
Locate your device in the list
[Right Click] > Uninstall
Download Google USB Driver package: http://developer.android.com/sdk/win-usb.html#top
Extract the zip to your desktop
Back to devmgmt.msc > [Right Click] root of the tree > Scan for Hardware Changes
Locate your device in the list
[Right Click] your device > Install > Choose/Browse files
Browse to the usb_driver folder you extracted to your desktop
Windows will use the Google USB driver instead of the driver for your phone.
My problem was that the LG driver was installed on Windows. Once I deleted that and installed the google driver, it works perfectly. The RSA prompted displayed right away.
I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet.
(I have Windows XP)
Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site:
http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears.
On the Eclipse console, I get the following message:
[2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great.
I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.
I had this same problem. To get it working, do the following:
Close Eclipse
Open Task Manager and kill the adb.exe program.
Re-open Eclipse (Eclipse will automatically restart the adb.exe service)
Run adb devices from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.
It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices again. You can also check your system logs for errors - run compmgmt.msc and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.
Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.
Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem..
link text
I had this same problem. Do the following:
Plug your phone into your computer and:
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module
I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.
Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.