Sweet! I dont know exactly if forcing it to restart USB mode then TCP/IP in sequence helped, or just the last three commands, but clearly it started working. Subsequently starting adb as normal user will give no access to the private key file, which in turn will fail silently with “device offline”. Of course, the private key is chmod 600 – only readable for root in your home directory. If you initially start adb with sudo, it will generate a public key pair, writing this to ~/.android/adbkey.pub and ~/android/adbkey.
Unfortunately, ADB over Wi-Fi doesnt show the security question in 4.2.2, so you need to find a USB cable thatll work and connect over USB at least once to accept the security question, but after you do that once, you can connect over Wi-Fi.Īs nobody gave an answer for my situation: you may not have access to the ~/.android/adbkey file. When one enables adb on a device in fact one starts this daemon, so comms can be established with the device.Īnother problem I was having was that I was trying to connect ADB over Wi-Fi, which is my only option because the USB ports on my Mac are really finnicky. The daemon is called adbd (as in adbdaemon).
The device has a service (daemon) that listens for this communication.
Adb executable from the development environment creates a connection (socket) with the device under control. The reason for a device to be reported as offline is that adb can not connect to it. Kindle fire adb status offline troubleshooting?
If youre not using Android Studio, you need to download and install Android SDK platform tools. If you dont already have Android Studio, download and install Android Studio.
After downloading the file, extract the contents into a new folder and double-click the Fire_Devices ABD drivers file.If youre using Windows, download this Kindle Fire driver: kindle_fire_usb_driver.zip.
Step 2: Install the Kindle Fire Driver (Windows Only)
How to Solve Adb Offline Device Problem #73 KikoBlog
Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. Mine was located in my user folder (C:\Users\*username*\.android\). If there is no key file when ADB runs, it will generate one automatically. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.ĪDB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android ), the file is simply named "adbkey" with no extension. There turned out to be a problem with my laptop's ADB RSA key. Otherwise check for a confirmation dialog on your device. This adbd's $ADB_VENDOR_KEYS is not set try 'adb kill-server' if that seems wrong. I can't quite find a way to attach a screenshot here, but I will type what I see:Ġ0-00 00:00:00.0 0-0/? E/Internal: device unauthorized. One of the teams we are working with has their phones working easily and is driving around, and their programmer does not know what is wrong either. Unfortunately, I do not know how to fix this. I believe that I have narrowed down the problem to the following: Our phone never gets the prompt to allow the computer to download code to it. The following is a list of what we have tried based on other forum posts from chief delphi, FTC Technology, and Stack Overflow:Ģ.) Check to insure that USB Debugging is enabled.Ĥ.) Run "adb kill-server" and "adb start-server" in CMD.Ħ.) Try to connect phone via wifi rather than through USB.ħ.) Revoking access to phones from all prior computers. As a result, we can never download our code. Essentially, when plugged in, the phone always reads either or in the select device menu. After (finally) setting up android studio properly, we encountered a problem with downloading the code to te ZTE phone.