• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root why adb says "offline"?

Claghorn

Android Enthusiast
I got the OTA 4.2.2 update earlier today, and I was just plugging in the USB cable to flash the latest TWRP recovery and reinstall Super SU and I noticed that "adb devices" always says the nexus 7 status is "offline".

Yes, I have USB debugging enabled (if I disable it, adb doesn't see the device at all).

Anyone know why it might always say offline? Anyone else seeing the same thing?

If I manually boot recovery using the power and volume buttons, fastboot has no problem talking to it, but I couldn't use adb to boot into recovery.

I'm all re-rooted and everything, but it looks like I'll be in trouble if I want to use adb on this thing someday.
 
It's a feature that's supposed to make ADB more secure by using RSA fingerprints to authenticate for ADB usage. You should see a popup on the device and you can have it remember the computer
 
this happened to me last night ..
I cant do squat I can boot recovery ..
I had twrp installed
all I get is a android with a red triangle sticking out of him
all my options to scroll are gone!

and the same with ADB
It shows the device BUT it's off line

I even took it over to my sons rig ..
this was a fresh install of google nexus tookit

and drivers
rebooted etc..

Same things... I'm stuck!
su lost it's permissions after this OTA update ..

so the root is gone of not complete...

I can't even run a factory img...........let alone a nandroid or a twrp backup

any help with this matter will be greatly appropriated

Regards
Hippy
 
It's a feature that's supposed to make ADB more secure by using RSA fingerprints to authenticate for ADB usage. You should see a popup on the device and you can have it remember the computer

No popup on my Nexus 7, just the normal status bar notification that it is connected for USB debugging.
 
No popup on my Nexus 7, just the normal status bar notification that it is connected for USB debugging.
yes no pop up ..I did read about that .. and never had a pop up..

I did this on windows 7 to rigs and windows 8
nothing
2 where freshly installed google toolkits...
 
this happened to me last night ..
I cant do squat I can boot recovery ..
I had twrp installed
all I get is a android with a red triangle sticking out of him
all my options to scroll are gone!

and the same with ADB
It shows the device BUT it's off line

I even took it over to my sons rig ..
this was a fresh install of google nexus tookit

and drivers
rebooted etc..

Same things... I'm stuck!
su lost it's permissions after this OTA update ..

so the root is gone of not complete...

I can't even run a factory img...........let alone a nandroid or a twrp backup

any help with this matter will be greatly appropriated

Regards
Hippy

For recovery, manually boot or flash the recovery image by manually booting into fastboot and manually booting or flashing the recovery image. This will also allow you to root as long as you put the necessary files on your device and flash them after getting into recovery
 
Also, I would suggest making sure ADB is up to date. If you normally use Wugs, download this and extract it. Open up the SDK Manager and select the tools and platform-tools to be downloaded. Let that finish, then open the folder where you extracted the SDK and copy adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll to <Location where you installed Wugs>\data. Then plug your device in and you should see the prompt. Then proceed with Wugs.

This SHOULD work, but I'm not guaranteeing anything on this. If it doesn't work, please post back and let me know
 
Finally got it to work: On the host linux box, I had to run the sdk "android" tool and update everything that was out of date and install the 4.2 sdk. (Which of those pieces did the trick, I don't know).

Anyway, once I did that, I do get the popup when I plug in the Nexus 7 and I can tell it everything is kosher and then subsequent adb commands work fine.

I would recommend that whoever thought of this have his brain left to some university for study after he is dead though. Exactly what kind of security is required when I have a length of USB cable physically connecting the devices? Having my own hand find the tiny little USB sockets and plug things together (after trying the wrong way round the first time) isn't confirmation enough that I meant that? Clicking the build number 7 times to enable the developer menus to then enable USB debugging isn't enough confirmation? What are they going to think of next?
 
Finally got it to work: On the host linux box, I had to run the sdk "android" tool and update everything that was out of date and install the 4.2 sdk. (Which of those pieces did the trick, I don't know).

Anyway, once I did that, I do get the popup when I plug in the Nexus 7 and I can tell it everything is kosher and then subsequent adb commands work fine.

I would recommend that whoever thought of this have his brain left to some university for study after he is dead though. Exactly what kind of security is required when I have a length of USB cable physically connecting the devices? Having my own hand find the tiny little USB sockets and plug things together (after trying the wrong way round the first time) isn't confirmation enough that I meant that? Clicking the build number 7 times to enable the developer menus to then enable USB debugging isn't enough confirmation? What are they going to think of next?

It was probably an update to adb. The one included with the version of Wugs I have is 1.0.29, while the current one is 1.0.31.

NOTE: IF YOU NORMALLY DO THE ROOT PROCESS MANUALLY, MAKE SURE ADB IS VERSION 1.0.31. Do this by running "adb version" to check
 
Finally got it to work: On the host linux box, I had to run the sdk "android" tool and update everything that was out of date and install the 4.2 sdk. (Which of those pieces did the trick, I don't know).

Anyway, once I did that, I do get the popup when I plug in the Nexus 7 and I can tell it everything is kosher and then subsequent adb commands work fine.

I would recommend that whoever thought of this have his brain left to some university for study after he is dead though. Exactly what kind of security is required when I have a length of USB cable physically connecting the devices? Having my own hand find the tiny little USB sockets and plug things together (after trying the wrong way round the first time) isn't confirmation enough that I meant that? Clicking the build number 7 times to enable the developer menus to then enable USB debugging isn't enough confirmation? What are they going to think of next?
could you post up some of those updated links for the things you did..
I think.. I updated adb but it is still showing locked! .. I may not sleep till I figure it out or fix it ...
thanks
 
could you post up some of those updated links for the things you did..
I think.. I updated adb but it is still showing locked! .. I may not sleep till I figure it out or fix it ...
thanks

Could you give me the output of "adb version" please?
 
sure if I knew how LOL ...

note I just noticed platforms-tools what not installed

If you use Wugs, open Explorer and go to the directory where you installed Wugs, open the data folder, hold shift, right click and click "Open Command Window Here." Then type "adb version."

If you're using the stock sdk, use the SDK Manager to update it
 
1.0.31
And yes I did get a pop up windows ........

Question now
is how do I update Google Nexus 7 toolkit
so it does not show offline
even tho I ticked the popup to remember this computer
when I run your ( latest adb) all is good
but not changed on the toolkit..


Brother .. thanks for all your help... U R Da Man
 
please someone help me!
I try many many things and try all kind of drivers for popup problem!
I update adb driver from SDK manager but no popup shows for accepting RSA fingerprint on my nexus 7!
I already try this on my pc and it work easily!
I don't know what happened that tablet doesn't show it now!?
 
Back
Top Bottom