Reputation: 3424
I previously developped Android apps on Android Studio . Everything works fine.
I work on real device, and Android Studio recognize it without issue.
Suddenly when I exit android studio and disconnect and reconnect my device, it doesn't recognize my device anymore, I have to exit and restart Android Studio.
I can't find a way to "Reset adb" like Android Studio.
I follow the below instruction(Tools->Android->Enable ADB Integration) and enabled ADB,but still below error occurred.
Error:-
I using windows system.
Any help great appreciation.
Upvotes: 168
Views: 422744
Reputation: 1
You can simplify restart command by creating a file "restartadb.bat" at system32 it should looks like :
@echo off adb kill-server adb start-server
then open cmd & run command "restartadb"
Upvotes: 0
Reputation: 197
I'm facing this problem since i have installed another adb server
for another software.
So if you are a linux user simply open terminal and type:
killall adb
Upvotes: 1
Reputation: 381
A possible solution to your problem could be the following:
Go to ~.android\avd{your_device}.avd
Delete all files with .lock extention
Upvotes: 0
Reputation: 7209
Open Command prompt and go to
android sdk>platform-tools>
adb kill-server
press enter
and again
adb start-server
press enter
Upvotes: 382
Reputation: 34331
Restart adb
Android Studio uses Android Debug Bridge (adb)
inside
adb kill-server
adb start-server
e.g.
alex@yoAlex5$ adb kill-server
alex@yoAlex5$ adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
Upvotes: 3
Reputation: 1287
Most of the answer is for restarting adb server in the command line.
Jiří's answer is the correct answer for this question (to restart adb server IN ANDROID STUDIO), though it's been redesign as shown below.
go to Tools > Troubleshoot Device Connections
ps. you need to hit "Next" two times to find this Restart ADB server button.
Android Device Monitor was deprecated in Android Studio 3.1 and removed from Android Studio 3.2.
Upvotes: 22
Reputation: 1559
Make sure you have "USB debugging" turns on.
I never had this issue with my other devices before. However, today I worked on a device and encountered this issue. Actually took me a while to debug it. Always thought "USB debugging" is on automatically when turning on the "Developer Options". But turns out its device dependent.
Upvotes: 0
Reputation: 529
If you are in Android Studio Open Terminal
adb kill-server
press enter and again
adb start-server
press enter
Otherwise
Open Command prompt and got android
sdk>platform-tools> adb kill-server
press enter
and again
adb start-server
press enter
Upvotes: 2
Reputation: 1332
open command prompt -> cd
to your sdk\platform-tools
type below command:
adb kill-server && adb start-server
Upvotes: 27
Reputation: 5
After reinstalling Android Studio, Is working without adb kill-server
Upvotes: 0
Reputation: 59
I faced same issue just fallowed some min steps in Android studio:
Manually fallowing steps in android studio
-------------------------------------------------OR-----------------------------------------------------------------------
Upvotes: 1
Reputation: 535
AndroidStudio:
Go to: Tools -> Android -> Android Device Monitor
see the Device tab, under many icons, last one is drop-down arrow.
Open it.
At the bottom: RESET ADB.
Upvotes: 0
Reputation: 7
When I had this problem, I wrote adb kill-server
and adb restart-server
in terminal, but the problem appeared again the next day. Then I updated GPU debugging tools in the Android SDK manager and restarted the computer, which worked for me.
Upvotes: -1
Reputation: 4458
Open task manager and kill adb.exe, now adb will start normally
Upvotes: 4
Reputation: 3498
I do not find a perfect way in Android Studio, get the process id and kill it from terminal:
ps -e | grep adb
kill -9 pid_adb
Upvotes: 8
Reputation: 3971
open cmd and type the following command
netstat -aon|findstr 5037
and press enter.
you will get a reply like this :
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 3372
TCP 127.0.0.1:5037 127.0.0.1:50126 TIME_WAIT 0
TCP 127.0.0.1:5037 127.0.0.1:50127 TIME_WAIT 0
TCP 127.0.0.1:50127 127.0.0.1:5037 TIME_WAIT 0
this shows the pid which is occupying the adb. in this 3372 is the value. it will not be same for anyone. so you need to do this every time you face this problem.
now type this :
taskkill /pid 3372(the pid you get in the previous step) /f
Voila! now adb runs perfectly.
Upvotes: 14
Reputation: 6967
Open a Task Manager by pressing CTRL+ALT+DELETE, or right click at the bottom of the start menu and select Start Task Manager. see how to launch the task manager here
Click on Processes
or depending on OS, Details
. Judging by your screenshot it's Processes.
Look for adb.exe from that list, click on END PROCESS
Click on the restart button in that window above. That should do it.
Basically by suddenly removing your device ADB got confused and won't respond while waiting for a device, and Android Studio doesn't want multiple instances of an ADB server running, so you'll have to kill the previous server manually and restart the whole process.
Upvotes: 14