How to restart ADB manually from Android Studio

Question

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:-

enter image description here

I using windows system.

Any help great appreciation.

ADB stands for Android Debug Bridge [here](https://developer.android.com/studio/command-line/adb?hl=es-419) you have a more detailed explanation. — FranK, Mar 26 '20 at 13:31

Lakhwinder Singh · Accepted Answer · 2021-08-27T06:30:13.640

347

Open Command prompt and go to

android sdk>platform-tools>

adb kill-server

press enter

and again

adb start-server

press enter

edited Aug 27 '21 at 06:30

answered Apr 23 '15 at 14:23

Lakhwinder Singh

6,799
4
25
42

2

I have done the same thing but still issue replicated. – RaMeSh Apr 24 '15 at 05:02
1

It's a working solution.If you think it is not working you have to again select your emulator from emulators drop down list because it creates a new instance. – Waheed Akhtar Jan 05 '17 at 18:50
this can also be done with the terminal within Android studio. Use cd.. and cd sdk, cd platform-tools to get it the right folder. – Halfacht Jul 03 '17 at 12:43
You can also done with in Android Studio terminal with your project path only. No need to navigate do sdk/platform-tools path. I checked in the version 3.1.1 – Naveen Kumar M Apr 17 '18 at 07:22
@warlock: What about Mac os? – Alireza Noorali Oct 02 '18 at 07:56
Also `Android\Sdk\platform-tools\adb devices`. – CoolMind Nov 01 '18 at 14:53
I had `chrome://inspect` open at the time and for whatever reason I had to close that tab before kill/start server would run correctly. – Jacksonkr Jan 25 '21 at 16:44

score 25 · Answer 2 · edited Jan 03 '19 at 02:42

25

open command prompt -> cd to your sdk\platform-tools type below command:

adb kill-server && adb start-server

edited Jan 03 '19 at 02:42

lucidbrot

5,378
3
39
68

answered Mar 10 '18 at 09:05

Vrajesh

1,312
19
25

When I type the command above i get a message saying " Error running 'zsh: command not found: adb ': Cannot run program "zsh:" (in directory "/Users/username/AndroidStudioProjects/projectname"): error=2, No such file or directory' " – Mogoai Obi Mar 02 '21 at 12:15

Mia · Answer 3 · 2021-04-21T08:13:44.280

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.

score 14 · Answer 4 · answered Feb 10 '16 at 09:32

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.

Behind corporate port policy expiration and re-gaining port policy again, I had to waste a week figuring out how to make my ADB work. This answer worked for me! — Taslim A. Khan, Feb 24 '21 at 20:52

matrixanomaly · Answer 5 · 2015-04-23T14:24:32.460

13

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.

edited Apr 23 '15 at 14:24

answered Apr 23 '15 at 14:22

matrixanomaly

6,627
2
35
58

It will automatically starting adb.exe when i am click the end process – RaMeSh Apr 23 '15 at 14:24
@User if you reconnect your device then only end process and let adb restart, does it still have the same error? – matrixanomaly Apr 24 '15 at 05:45
yes same error occurred when i am connect the device also . – RaMeSh Apr 24 '15 at 06:03
Or just open the Terminal window inside Android Studio and do: taskkill /im adb.exe /f – Alan B Aug 09 '18 at 13:15

score 6 · Answer 6 · answered Mar 04 '16 at 05:21

6

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

answered Mar 04 '16 at 05:21

BollMose

3,002
4
32
41

score 4 · Answer 7 · answered Apr 04 '16 at 11:20

4

Open task manager and kill adb.exe, now adb will start normally

answered Apr 04 '16 at 11:20

M. Usman Khan

3,689
1
59
69

score 1 · Answer 8 · answered Mar 16 '18 at 12:30

I faced same issue just fallowed some min steps in Android studio:

Manually fallowing steps in android studio

Goto Command promt and in Command promt fallow a android SDK file path "android sdk>platform-tools>" adb kill-server press enter
adb start-server press enter

-------------------------------------------------OR-----------------------------------------------------------------------

Open Command promt and got android sdk file path adb kill-server && adb start-server

score 1 · Answer 9 · answered Apr 03 '20 at 10:31

1

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

answered Apr 03 '20 at 10:31

Arslan Maqbool

519
1
7
21

score 0 · Answer 10 · edited Jan 25 '18 at 12:36

0

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.

edited Jan 25 '18 at 12:36

derHugo

83,094
9
75
115

answered Jan 25 '18 at 11:45

Jiří

415
6
16

score 0 · Answer 11 · answered Jul 17 '18 at 02:19

0

After reinstalling Android Studio, Is working without adb kill-server

answered Jul 17 '18 at 02:19

calincan mircea

5
3

score 0 · Answer 12 · answered Mar 25 '21 at 19:52

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.

score 0 · Answer 13 · answered May 31 '21 at 14:29

0

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

answered May 31 '21 at 14:29

yoAlex5

29,217
8
193
205

Mohamed Slama · Answer 14 · 2022-03-20T04:14:38.750

0

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

edited Mar 20 '22 at 04:14

answered Dec 28 '21 at 06:36

Mohamed Slama

189
1
3
17

score 0 · Answer 15 · answered Mar 08 '22 at 07:34

0

A possible solution to your problem could be the following:

Go to ~.android\avd{your_device}.avd
Delete all files with .lock extention

answered Mar 08 '22 at 07:34

E. C. Theodor

151
1
4

score -1 · Answer 16 · edited Jun 23 '16 at 11:43

-1

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.

edited Jun 23 '16 at 11:43

User42

970
1
16
27

answered Jun 23 '16 at 10:22

Vladymir Yakymov

7
1

How to restart ADB manually from Android Studio

16 Answers16

Linked