Database Users

[Q] ADB error: device unauthorized and device offline

I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.

HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.

ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.

HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.

Perfect, worked. Thanks!

I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...

usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.

I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.

Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!

legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe

maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway

legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards

c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.

legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.

I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.

SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.

after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.

I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.

thanks to the adb kill-server guy! worked for me

gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto

[Q] EFS Pro Problem

Hello all,
I'm having difficulty trying to run EFS Pro v2.0.70/v2.0.72 to backup my EFS folder on my GT-I9505. I get stuck at the part when it says "Initializing ADB server..." and it just sits there. I just want to point out that I had made a backup of my EFS folder on my GT-I9505 when I first got my phone (around May), but it seems to have been deleted! Anyway, I found some good steps in another thread, as follows:
Before starting, check the following:
Device is fully rooted
SuperSU (or equivalent) is active
USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)
Busybox downloaded AND installed (normal or smart) on your device
Microsoft .NET Framework 4.0 installed on your PC
Samsung USB driver is installed (either by installing Kies or just the driver alone.
Kies is not active (neither as application nor process, check Windows Taskmanager)
ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)
In case ADB is not running you need to install the ADB driver
Run EFS Professional as administrator.
Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.
Of course, your device should be on the home screen, not on the lock screen
I've followed all these steps, checking each methodically, and guess what, I'm still stuck at "initializing ADB server..."! I even go to cmd and type in "adb devices" and my phone shows up, I see on my phone that a shell has been granted, and yes, I am rooted, I have busybox, and Samsung drivers, .NET 4.0 framework and USB debugging, it's driving me mad, I've even tried different USB ports, and nothing!
If anyone has any suggestions, please fire away!

I have the exact same problem, but with my S3 (I9300) ...
No one who can help?

Did you get sorted my i9505 is the same and I have two phones but one wont work..

no fastboot or adb access

I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?

maigre said:
I can't access my N7 with adb (when booted) or fastboot (while in the bootloader). It's connected via a USB cable. This is both with a Mac and WUGS. Commands like fastboot devices or adb devices return nothing as the device isn't seen. I can connect my N4 and use those commands without problem. I just tried doing the same with my 2013 N7 and it's not being seen, either. Strange. I don't think I've had this problem before on the Mac. I have on Windows, which I can sometimes resolve by installing and reinstalling drivers until something works.
I'd wanted to update the 2012 N7 to Lollipop.
Thoughts, anyone?
Click to expand...
Click to collapse
Crazy as it sounds, try another USB cable. Reboot everything, plug in fresh, and try again. Failing that, use WUGS to reinstall all your USB drivers. Use the stock Google.

The cable was the culprit. I tried another and it worked. Thanks so much!

I'm having a similar problem that's driving me insane.
Nexus 7 wi-fi version
I've loaded every driver on the planet and in recovery mode it simply will not show up. And I'm not talking won't show up using ADB, I get absolutely nothing in device manager. So before anyone tells me to point to the device and manually change the driver, there is no device to try and point a driver to.
In "normal" mode, it shows up perfectly fine in Device Manager as Android ADB Composite Device. ADB will list it in devices with no problem. It will accept the "adv reboot recovery" command perfectly and reboot the tablet into stock recovery. The minute it does that, the device disappears from the Device Manager list and nothing takes it's place. I've tried to have it search for new hardware, I've tried the Google USB drivers kit, I've used Koush's Universal Driver install. I've used 3 different cables on 2 different USB ports.
This is a completely stock N7 running 4.4.4 plugged into a Windows 8.1 64 bit PC.
The last thing I'm wondering is do I have to unlock the bootloader at all? I don't want to because it'll wipe the tablet. If so I guess I'll just wait out the actual OTA rather than try to sideload it.
Any suggestions would be appreciated.

Yaz75 said:
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Any suggestions at all?
Ummm... does the Stock Recovery actually run "adbd" by default? If it doesn't (or it doesn't start adbd until you execute the sideload menu item), then you wouldn't normally see anything on the other side of the cable with a stock Recovery. (I don't have my tablet with me to check)
Here's an extra "any suggestion at all":
Get rid of Windows and use Linux; there are no drivers to screw with in the latter case.
No, seriously. But probably not what you are thinking.
If you can get a "live CD" to boot** on your PC, you can (as root) run the "lsusb" command to see what devices are enumerated on the USB bus, port by port.
In conjuction with the decoder ring at the end of this post, you can determine from inspection of the USB VID/PID identifiers whether or not all the hardware is behaving, and whether or not the tablet is in the mode you think it is supposed to be in.
The reason this is valuable is that it allows you to take drivers completely off the table; if everything is as it should be, then you know that all the hardware and cabling are functioning correctly, the tablet is behaving correctly, your PC hardware is behaving correctly, and that 100% of the problem is Windows driver issues.
If you want to go the extra 1/4 mile, you can put a copy of (Linux) fastboot & adb plus your flashables on a USB key, and run adb or fastboot from the Live CD boot. It won't matter that the live CD doesn't have them preinstalled, they will be on your USB key. It will be easier on you if you can find statically-linked fastboot and adb binaries; if not you will have to copy one or two supporting shared libs (.so files) along with the binaries, and find out what LD_LIBRARY_PATH is all about.
suppose the USB key mounts at /media/usb1; then
$ sudo /bin/bash
# mkdir /tmp/tools
# cp /media/usb1/fastboot /media/usb1/adb /media/usb1/*.so /tmp/tools/
# chmod 755 /tmp/tools/*
# export LD_LIBRARY_PATH='/lib:/usr/lib:/tmp/tools:.'
# cd /tmp/tools
# ./fastboot devices
OR
# ./adb devices
Good luck; as you are using Windows you are going to need it. Hahaha LOL
**depending on whether your BIOS on your win 8.x PC can be toggled between UEFI and Legacy modes or not, this can be either trivial (Legacy boot mode) or complicated (UEFI) requiring a "Trusted Computing" crypto boot shim from MisterSoftie.

Ok this works for me
Use USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
delete all the associated drivers like Google, Samsung, etc for ADB, etc
Restart Computer
Reconnect N7 without MTP and USB debugging
Wait for PC to recognise device and install driver
*If you see something like PC unable to recognise device, go into device and Update Driver and choose "Automatic....."
Disconnect and Reconnect with MTP and USB Debugging
Wait for PC to recognise device and install driver
Restart N7 in bootloader
Wait for PC to recognise device and install driver
Profit
* My PC OS is Win 8.1 Pro 64bit

make sure mtp is switched off, i couldnt get adb or fastboot on my nexus just now . switched off mtp and works fine

Can't get RSA Fingerprint dialog to popup

Hi all,
I recently bought a OPT and wanted to root it, but I can't get the RSA Fingerprint dialog to appear.
What I've done:
Installed Android SDK and platform tools and all that stuff according to the guide in the general section
Installed Koush's universal drivers and also specifically installed the Oneplus drivers
Rebooted rebooted rebooted both my computer and phone multiple times
Revoked USB authorization multiple times (according to some this works, but not for me)
Tried both MTP and PTP
Switched off and on developer options and USB Debugging
Factory reset my phone
When I start a command prompt in the platform tools directory and execute "adb version", " Andoid Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android" pops up, so I think my ADB is working properly. But when I execute "ADB devices" the ADB server starts up and then nothing is listed under connected devices.
I'm using Windows 10. Any help would be greatly appreciated. Thanks!

This might work
This didn't work for me, but give it a try.
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332

Guide: If your android (pixel 2) ADB works in Window but NOT in recovery mode

I ran into a very weird issue lately. My PC running Windows 10 (previous Windows 7) and having gone through more than 4 phones with me without cleaning out my system had a ton of old drivers for different phones attached to the computer. Whenever I'd plug my Pixel 2 into the computer ADB worked fine but for some reason when I go into recovery it wouldn't recognize my phone. I rummaged through hours worth of forums/reddit posts guides/youtube videos and everyone kept coming up with the obvious answers being; install the latest adb drivers or force install the google ones or you're entering recovery completely wrong. Being quite savvy in this I tried everything and have sideloaded in the past through recovery on this very phone so it was a real head scratcher what had happened. I went through device manager uninstalled and reinstalled pretty much every adb/mobile device driver associated with the phone. However through some oversight it just wasn't clicking with me when I was in device manager my ADB was listed as "LeMobile Android Device" and even when I uninstalled restarted my computer/phone used different USB cables and ports it never clicked that it shouldn't say LeMobile Android Device because obviously my phone is a Google Pixel 2. Again seeing that I have used this very computer and phone before in the past and have sideloaded OTAs I assumed my old setting would've stuck. But I guess the latest OTA or something on my computer reverted my ADB drivers to a LeMobile Android Device thus causing my ADB to NOT work in recovery anymore but still functioned fine inside Windows.
Through more digging I found a guide on reddit: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
Pretty much the top comment/solution is as follows:
A few steps to get rid of the LeMobile pesky driver.
1-Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2-Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3-Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4-Go to the device manager. Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver like the one in location "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
5-And You're done! Cool thing is that you will have to do it again if you connect a tablet or something new and Microsoft decides the LeMobile driver is better then Googles driver...
So yes in the future I may have to do this setup again because Microsoft is just dumb and doesn't let settings stick but I went through the list and force deleted all my old phones from Motorola and Samsung as well so when I installed the ADB drivers finally the Google one's stuck. Hopefully this will fix many other people's problems when they can ADB in windows but NOT in Recovery. My other option would be to format my computer and have a fresh install but ain't no one got time for that. There are other guides online to fully delete drivers but it is very time consuming so I'm going to skip that for now.