With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Thanks. Very useful! :good:
for me and the HTC One X it wont work.....
-Happy Feet- said:
for me and the HTC One X it wont work.....
Click to expand...
Click to collapse
Did work previously?
maybe restart the adbd on the phone.
Can you test in Recovery, Cwm has an extra button for restarting.
Maybe Stock too.
Illidan Pornrage said:
With the new secure adb I had an issue:
(I was transferring data to a new harddrive and in the process
I deleted my /home/me/.android/ (somewhere in \Users\me\AppData\ on windows) folder because I thought I didnt need anything in it.
Then I wanted to pull some files from my CM10.1 nightly device per adb.
It said: "error: device offline" when trying to access it.
Now, the computers adb key was gone with the userdata folder of the sdk (the .android folder) and access was denied. But somehow whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization.
To fix that I did the following:
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
works
In my case it was even nastier because my sdk userdata folder ~/.android (on small ssd) was a symlink to /data/home/me/.android (on a huge drive for the emulators, android-sources and stuff)
and the symlink pointed to a nonexisting path which prevented saving any sdk settings.
On deleting the symlink or recreating the folder it should work.
Click to expand...
Click to collapse
Fraid it didn't work. End up with various errors and randomly appearing devices. Plus, the original error reappears eventually. Please help!
If you give me some Info around the issue, like what you intended to do and if it worked previously, I could help you.
FIX adb offline problem
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window
------------------------------------
After that you every thing will be OK
this solved my problem
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
ciano865 said:
I've ADB problem in bootloader mode: devices not found, list empty. It works fine with phone in normal mode
I've upgraded to adb .31, upgraded drivers but no solution, BTW fastboot devices corectly displays device
Any help ?
Thanks
Click to expand...
Click to collapse
as far as I know adb doesn't work in bootloader mode.
MadMan29729 said:
as far as I know adb doesn't work in bootloader mode.
Click to expand...
Click to collapse
How can I push file to phone it doesn't boot ?
I think thats intentional, bootloader mode is the mode corresponding to fastboot for directly flashing, deleting, formatting, stuff like that in the most basic environment. Try recovery or normal boot for adb, which is for debugging, shell access, backup, filetransfer and so on.
(More info for more specifics)
Thanks, my mistake not using recovery
from Nexus 4 with Tapatalk
took me a bit to get into the thing myself after > 4.2 update
i'm on ubuntu
i had to use the terminal command
Code:
android update sdk --no-ui
a couple of times to get the thing actually updated. using just
Code:
android update sdk
wasn't cutting it for some reason. probably because i'm stupid and didn't fiddle with it enough.
then, realized when i STILL couldn't access the device (even after accepting the computer's RSA key on my n7),
it was because i had previously put a now deteriorated version of adb in /usr/bin. so, i rm'd it (navigate to /usr/bin and
Code:
sudo rm adb
then navigate over the folder whereeveryouputyoursdk/platform-tools/ and
Code:
sudo cp adb /usr/bin
that should be the new version of adb into /usr/bin. remember, do all that after running the
Code:
android update sdk --no-ui
a few times
peace
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
ah great i thought there was an issue with my adb and you wrote the solution
MadMan29729 said:
problem was i had ran this command
sudo apt-get install android-tools-adb
which installed Android Debug Bridge version 1.0.29 in /usr/bin
the system was using this by default even tho i added the platform-tools directory with the newest adb (Android Debug Bridge version 1.0.31) to my environment path.
This solved this problem (running old adb) on LinuxMint:
Method 1:
sudo apt-get remove android-tools-adb
Method 2: (if the first doesn't work)
unplug device
adb kill-server
adb version
Android Debug Bridge version 1.0.29
cd to android sdk dir
cd /home/XXX/adt-bundle-linux-x86_64/sdk/platform-tools/
copy new adb to /usr/bin
sudo cp adb /usr/bin/
adb version
Android Debug Bridge version 1.0.31
adb kill-server
adb devices
daemon not running. starting it now on port 5037 *
daemon started successfully * List of devices attached
plug in the device, and on the device dialog about RSA appeared
accept on device
adb devices
hope this helps...
credit for this solution goes to CoPLaS @ this URL
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Click to expand...
Click to collapse
Thanx man you saved me !!!
Sent from my Micromax A57 using xda app-developers app
Thanks
I still had this problem on OSx and Ubuntu in cli.
what i've done on both to address it is, update the SDK to get the newest adb. (i'm suing 1.0.31)
killall adb
then turn off USB debugging on device.
start new adb (doesn't work nothing to connect to)
then turn on USB debugging and suddenly you get the pop up on the android device that says "always allow this computer at xxx"
test adb devices and should show 'device' instead of 'offline'
or try sudo, unplug the device, run adb under sudo on the desktop (sudo adb kill-server; sudo adb start-server), then plug the device back in.
yay!
svs57 said:
Long time I play with adb (1.0.31) from Linux without problem.
Today I flash new kernel (GT-I9505_AdamKernel.V1.6 then try Abyss-GT-I9505-1.6.1)
Got abd "device offline"
I come back on KT-SGS4.
adb works.
Can anyboby explian be why adb down't work with some kernels?
Click to expand...
Click to collapse
When it does that, go to Developer Options and Revoke Permissions and replug it back in. If that isn't it, then make sure you have the newest version of adb. Have had that happen on a couple of times on newer Samsungs.
C:\S.onyTablet.S [FLASHER] v3.0\files>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
275501730014164 offline
if I use any other command,
C:\S.onyTablet.S [FLASHER] v3.0\files>adb reboot
error: device offline.
Does any body having any idea?.
Also if i reconnect, usb device arrival itself not detecting in device manager.
If i want to detect in pc,then i have to run either of UMS extSD or intSD scripts that codi's auto atomtic tool provided to put it in.
Does anybody have any idea?
I got it.
kriyas86 said:
C:\S.onyTablet.S [FLASHER] v3.0\files>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
275501730014164 offline
if I use any other command,
C:\S.onyTablet.S [FLASHER] v3.0\files>adb reboot
error: device offline.
Does any body having any idea?.
Also if i reconnect, usb device arrival itself not detecting in device manager.
If i want to detect in pc,then i have to run either of UMS extSD or intSD scripts that codi's auto atomtic tool provided to put it in.
Does anybody have any idea?
Click to expand...
Click to collapse
Chnage the setting -> storage , right corner of the window there is a setting icon. click it and change to mtp
kriyas86 said:
Chnage the setting -> storage , right corner of the window there is a setting icon. click it and change to mtp
Click to expand...
Click to collapse
Is your tablet seen as a adb device in control panel of your computer
Sent from my SGPT12 using xda app-developers app
BUMP!
Get a newer version of adb.exe, the one you have does not support Android 4.0.3.
Sent from my Nexus 4 using xda app-developers app
saw the thread over here: http://forum.xda-developers.com/showthread.php?t=2292791
tried all of the same steps (and more) listed in that thread numerous times.
SDK is the latest zip file dated "20130522"
phone DOES have developer mode enabled.
Samsung Kies connects and works fine (using driver bundled in Kies installer)
Windows Explorer maps the device and it can be browsed
Device Manager lists device by name under Portable Devices as well lists "SAMSUNG Mobile USB Composite Device" (driver 2.9.510 date 2013.05.23) under USB controllers
using Koushik Dutta's Universal ADB Driver did not help at all, device then becomes an android device in device manager and neither Kies or adb can connect to it...
Code:
C:\Android_SDK_Windows\sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Android_SDK_Windows\sdk\platform-tools>adb devices
List of devices attached
C:\Android_SDK_Windows\sdk\platform-tools>
ideas?
EDIT: SOLVED, mis-tapped in dev options menu (stupid small text made BIG now)... checkmarked 'include bug reports...' instead of 'usb debugging'. off to hang my head in shame
i've installed multiple different adb/htc drivers.. at one point my computer could start adb and run up until the point where the rom was being transferred then it would error out after some time. NOW its not even starting daemon. How do i fix this? I want to remove all the driver clutter and start this process from scratch the **** has gotten so confusing for no reason. underneath is dost detailing where i've stalled out
HELP ME SOMEBODY PLEASSEEEEEEEEEEEEEEE!!!!!
Quote Originally Posted by benny3 View Post
adb and fastboot should be in the same folder. Are opening the command prompt from that same folder?
download this and extract it to your desktop. Put the rom.zip in it, Hold the shift key down, right click that folder and the run command from here
XXXXXX.com/u/45848000/adb.zip[/url]
dog **** still aint work. so i installed the HTC drivers from your other post (though nothing happens really when exe is clicked)
then i download this file and did as directed, cmd replied:
C:\Users\Gateway\Desktop\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
C:\Users\Gateway\Desktop\adb>adb kill-server
C:\Users\Gateway\Desktop\adb>adb usb
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
C:\Users\Gateway\Desktop\adb>
other people are saying to copy adb files to folder on c drive and launch from there. they also say launch cmd from installed adb location...what where the first set of files you had me install? the driver in my list of devices says Google nexus ADB interface driver but i cant find its location. shouldnt i move the rom.zip there and lunch there??? why is this such a ******* struggle. thank you for helping seems the rest of the android community just reads random troubleshooting posts for no reason other than entertainment... most unhelpful forum ever.
Hello, I hope someone can help.
I have downloaded ADB for windows but cannot for the life of me get it to work. When I connect my phone (Samsung s6) and type ADB DEVICES, I get an error, cannot connect to daemon.
I have searched for solutions but none work. I have tried, kill-server, start server, I have tried re-installing ADB, the latest version and version 1.4.3, which I found on this site , as it had an installer. I have enabled USB De-bugging on the phone etc. I disabled my AV and firewall and also allowed ADB through windows defender, just in case it was that, as someone said that worked for them. None of the above worked for me...
I did get to a point where my phone asked me to allow debugging, I say yes but then again it says Daemon did not ACK.
I am so frustrated with this that I think, I am going to start a campaign to destroy Google. The world doesn't need them.
I know this issue has been posted on before but forgive me, nothing I have found so far works, on this site or any other.
I signed up to this site in the hope that there is someone who can help.... Cheers in advance..
Steve..
The ADB Daemon ( adbd ) is the counterpart on Android device of ADB Server ( adb.exe ) on Windows computer. Their versions must match in order ADB gets working.
Run this command sequence
Code:
taskkill /F /IM adb.exe
adb devices
jwoegerbauer said:
The ADB Daemon ( adbd ) is the counterpart on Android device of ADB Server ( adb.exe ) on Windows computer. Their versions must match in order ADB gets working.
Run this command sequence
Code:
taskkill /F /IM adb.exe
adb devices
Click to expand...
Click to collapse
Thanks for your reply, it was actually very helpful...
Many thanks.