Accept answer is for special case. I must have missed the 'allow USB debugging from xx:xx:xx' on the phone. Restarting the server and reconnecting USB popped it up again.
Show 2 more comments. I have r17 but I get the same problem. Will reverting to r Worked exactly in the order described. Final step is to allow it on the phone. Just reboot the phone or device and enjoy, no need to re-start adb nothing else. Show 10 more comments.
Run adb kill-server to ensure adb is not running. Restart your Android device. After your device restarts, connect it via USB and run adb devices.
This should start the ADB daemon. Your device should now be online again. Step 3 is most probably the key solution here! Worked for me with Android 8. I tried the adb kill-server without the Android device restart and it didn't work. When I repeat these steps and restart the device as mentioned in section 4, it worked.
Add a comment. Yes, I use linux. There must be a comparable script in the Windows SDK tarball. In Windows 7, to issue the command from the It worked for me with Nexus 10 and Galaxy Nexus. I tried changing usb port, restarts, etx.. I was almost going to reinstall xp, thanks! Show 1 more comment. I can't stress that switching USB ports is key. Often front panel USB ports can be defective. Mike Weir. Worked for me too. Nexus 10 sometimes seem to draw too much current for the USB port — skubo.
Sometimes it's not a defective port. Just unplugged and plugged again in the same port. Windows wonders Sometimes switching ports works.
Trying a different cable sometimes helps. It works on USB 3. Never had that issue till now and all the sudden I have to use 3. Which is wasting one of my 3. And as always, verify you have debugging enabled in the developer options ;.
Eric Fossum. It worked for me once I revoked the usb debugging authorizations. Then disabled and reenabled usb debugging. The "allow this computer" message popped up, and BAM, it showed as device instead of offline. This certainly is the simplest, surest, and quickest method. I used many variations of all the methods in this thread. This is the only one that works every time. It's just three taps on the android device and the issue is gone.
This was the only method that worked for me, combined with revoking USB debugging authorizations. Multiple adb. This is what happened with me. I think something I downloaded to install a ROM two years ago was the culprit.
It just works. I typed adb devices right after renaming the old adb. I said yes and now when I issue adb devices instead of "offline" it says "device". Thanks, this one works! Same thing happened to me also, I think adb. I guess they install a version themselves because they don't rely on the user having the Android SDK installed. And yeah, deleting the old 1. Show 3 more comments. This did it for me. Was bashing my head against a wall since updating my Nexus 7. I tried everything on this page and a few other sites that Google turned up and my HTC phone running Android 4.
I finally restarted the phone and then adb devices said it was online. Man, I wish I had thought of that earlier. I got this error: device offline until I found your comment about wifi - as soon as I took my phone off wifi it worked. If your device normally connects over USB, but suddenly stops working, especially after the USB cable has been disconnected and reconnected, try the following non-invasive steps before doing some of the more drastic things mentioned in the other answers: adb kill-server adb start-server adb devices If your device is listed with 'device' next to it, you're back in business.
That helped solving my problem android emulator was showing up as 'off-line' but after restarting server as described it was back in 'device' mode. If not you have a broken android installation on the device. Chris Stratton Thank you! Apparently I have a broken android installation on device. My newest error that deals with rejected shell commands led me to my own previous question!
I am currently investigating the use of both of xda-developer Chainfire's 'adbd Insecure' and 'SuperSU' apps for rooted phones Add a comment. Active Oldest Votes. Reset adb and now you can run your application. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Helping communities build their own LTE networks. Podcast Making Agile work for data science. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. Please see this question for background information. Whenever I run adb devices it says Error: device offline - This appears even when no device is connected at all.
It won't even let me start the adb server. Therefore solutions like "run adb kill-server first" won't have any affect. The tablet runs android 4. The phone runs android 7 but that shouldn't matter since even without anything connected I can't even start the adb server on the tablet.
Edit: Using the adb binary from here solved the error, but presents me with this now:. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Adb says "Error: Device offline" everytime Ask Question.
Asked 3 years, 5 months ago. Active 3 years, 5 months ago. Viewed 7k times. Problem: Whenever I run adb devices it says Error: device offline - This appears even when no device is connected at all. Things to note: This is adb on another android device. I can not "re-install the android SDK platform" or something like that.
0コメント