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 you have a more detailed explanation. — FranK
– FranK, Commented Mar 26, 2020 at 13:31

Lakhwinder Singh · Accepted Answer · 2021-08-27 06:30:13Z

386

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, 2021 at 6:30

answered Apr 23, 2015 at 14:23

Lakhwinder Singh

7,2494 gold badges27 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

RaMeSh Over a year ago

I have done the same thing but still issue replicated.

Waheed Akhtar Over a year ago

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.

Halfacht Over a year ago

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.

Naveen Kumar M Over a year ago

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

Alireza Noorali Over a year ago

@warlock: What about Mac os?

|

lucidbrot · Accepted Answer · 2019-01-03 02:42:24Z

27

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

adb kill-server && adb start-server

edited Jan 3, 2019 at 2:42

lucidbrot

6,5543 gold badges50 silver badges77 bronze badges

answered Mar 10, 2018 at 9:05

Vrajesh

1,33219 silver badges25 bronze badges

1 Comment

Mogoai Obi Over a year ago

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' "

Mia · Accepted Answer · 2021-04-21 08:13:44Z

23

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.

edited Apr 21, 2021 at 8:13

answered Apr 8, 2021 at 2:37

Mia

1,2961 gold badge19 silver badges30 bronze badges

Comments

matrixanomaly · Accepted Answer · 2015-04-23 14:24:32Z

14

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, 2015 at 14:24

answered Apr 23, 2015 at 14:22

matrixanomaly

7,0272 gold badges38 silver badges60 bronze badges

4 Comments

RaMeSh Over a year ago

It will automatically starting adb.exe when i am click the end process

matrixanomaly Over a year ago

@User if you reconnect your device then only end process and let adb restart, does it still have the same error?

RaMeSh Over a year ago

yes same error occurred when i am connect the device also .

Alan B Over a year ago

Or just open the Terminal window inside Android Studio and do: taskkill /im adb.exe /f

Parth Anjaria · Accepted Answer · 2016-02-10 09:32:13Z

14

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.

answered Feb 10, 2016 at 9:32

Parth Anjaria

3,9613 gold badges34 silver badges67 bronze badges

1 Comment

Taslim A. Khan Over a year ago

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!

BollMose · Accepted Answer · 2016-03-04 05:21:40Z

8

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 4, 2016 at 5:21

BollMose

3,5364 gold badges39 silver badges44 bronze badges

Comments

M. Usman Khan · Accepted Answer · 2016-04-04 11:20:24Z

4

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

answered Apr 4, 2016 at 11:20

M. Usman Khan

4,5362 gold badges70 silver badges85 bronze badges

Comments

yoAlex5 · Accepted Answer · 2021-05-31 14:29:10Z

3

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, 2021 at 14:29

yoAlex5

35.2k10 gold badges235 silver badges253 bronze badges

Comments

Arslan Maqbool · Accepted Answer · 2020-04-03 10:31:54Z

2

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 3, 2020 at 10:31

Arslan Maqbool

5271 gold badge8 silver badges21 bronze badges

Comments

PSP · Accepted Answer · 2018-03-16 12:30:26Z

1

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

answered Mar 16, 2018 at 12:30

PSP

598 bronze badges

Comments

Mohamed Slama · Accepted Answer · 2022-03-20 04:14:38Z

1

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, 2022 at 4:14

answered Dec 28, 2021 at 6:36

Mohamed Slama

1951 gold badge3 silver badges18 bronze badges

Comments

derHugo · Accepted Answer · 2018-01-25 12:36:33Z

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, 2018 at 12:36

derHugo

92.6k9 gold badges94 silver badges141 bronze badges

answered Jan 25, 2018 at 11:45

Jiří

5357 silver badges18 bronze badges

Comments

calincan mircea · Accepted Answer · 2018-07-17 02:19:16Z

0

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

answered Jul 17, 2018 at 2:19

calincan mircea

53 bronze badges

Comments

Haomin · Accepted Answer · 2021-03-25 19:52:59Z

0

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.

answered Mar 25, 2021 at 19:52

Haomin

1,59914 silver badges16 bronze badges

Comments

E. C. Theodor · Accepted Answer · 2022-03-08 07:34:10Z

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 8, 2022 at 7:34

E. C. Theodor

3813 silver badges4 bronze badges

Comments

Youssef IBN-EL · Accepted Answer · 2023-09-30 21:17:16Z

0

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"

answered Sep 30, 2023 at 21:17

Youssef IBN-EL

1

Comments

User42 · Accepted Answer · 2016-06-23 11:43:17Z

-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, 2016 at 11:43

User42

9631 gold badge16 silver badges28 bronze badges

answered Jun 23, 2016 at 10:22

Vladymir Yakymov

71 bronze badge

Collectives™ on Stack Overflow

How to restart ADB manually from Android Studio

17 Answers 17

9 Comments

1 Comment

Comments

4 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

17 Answers 17

9 Comments

1 Comment

Comments

4 Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Related