5,604,367 Members 48,990 Now Online
XDA Developers Android and Mobile Development Forum

[Q] ADB error: device unauthorized and device offline

Tip us?
 
HashWorks
Old
#1  
HashWorks's Avatar
Senior Member - OP
Thanks Meter 36
Posts: 128
Join Date: Jul 2012
Location: Munich

 
DONATE TO ME
Default [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.
Current: Google Nexus 4 [Beanstalk, Nova Launcher Prime]
Old one: Samsung Galaxy S [Cyanogenmod 10]
The Following User Says Thank You to HashWorks For This Useful Post: [ Click to Expand ]
 
ksilver89
Old
#2  
Senior Member
Thanks Meter 90
Posts: 221
Join Date: Feb 2012
Location: Kajang
Quote:
Originally Posted by HashWorks View Post
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.
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.
The Following User Says Thank You to ksilver89 For This Useful Post: [ Click to Expand ]
 
HashWorks
Old
#3  
HashWorks's Avatar
Senior Member - OP
Thanks Meter 36
Posts: 128
Join Date: Jul 2012
Location: Munich

 
DONATE TO ME
Quote:
Originally Posted by ksilver89 View Post
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.
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Current: Google Nexus 4 [Beanstalk, Nova Launcher Prime]
Old one: Samsung Galaxy S [Cyanogenmod 10]
 
ksilver89
Old
#4  
Senior Member
Thanks Meter 90
Posts: 221
Join Date: Feb 2012
Location: Kajang
Quote:
Originally Posted by HashWorks View Post
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
The Following 3 Users Say Thank You to ksilver89 For This Useful Post: [ Click to Expand ]
 
HashWorks
Old
#5  
HashWorks's Avatar
Senior Member - OP
Thanks Meter 36
Posts: 128
Join Date: Jul 2012
Location: Munich

 
DONATE TO ME
Perfect, worked. Thanks!
Current: Google Nexus 4 [Beanstalk, Nova Launcher Prime]
Old one: Samsung Galaxy S [Cyanogenmod 10]
The Following User Says Thank You to HashWorks For This Useful Post: [ Click to Expand ]
 
usafle
Old
#6  
usafle's Avatar
Senior Member
Thanks Meter 22
Posts: 452
Join Date: Nov 2010
Location: Newburgh
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...
 
ksilver89
Old
#7  
Senior Member
Thanks Meter 90
Posts: 221
Join Date: Feb 2012
Location: Kajang
Quote:
Originally Posted by usafle View Post
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...
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.
 
usafle
Old
#8  
usafle's Avatar
Senior Member
Thanks Meter 22
Posts: 452
Join Date: Nov 2010
Location: Newburgh
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.
 
legalbrr2
Old
#9  
Junior Member
Thanks Meter 10
Posts: 15
Join Date: Jul 2012
Location: Londrina
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!
The Following User Says Thank You to legalbrr2 For This Useful Post: [ Click to Expand ]
 
maxrfon
Old
#10  
maxrfon's Avatar
Senior Member
Thanks Meter 177
Posts: 243
Join Date: Nov 2004
Quote:
Originally Posted by legalbrr2 View Post
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!

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
Xperia (and many other phones) Bootloader/SIM unlock founder & independent exploit researcher

My Sonork ID :100.87650

Sent from my ZX81 Spectrum using Algorithmic calculator.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes