Database Develop

[Solved] ADB isn't connecting

Hmmph. Basically, I'm running Windows 7. ADB has worked fine for me for months now, except for tonight. Tonight, I can't connect to my phone VIA ADB. Everything is set up right; not like anything has changed.
Typing "adb shell" returns "error: device not found." Logcat shows waiting for device.
I haven't changed anything on the phone either. Is there a way to "reset" ADB?

open up your task manager, go to processes then select adb.exe and end it. maybe that will help. i had a problem once where it identified my phone twice and i could not use adb and reset it that way

david1171 said:
open up your task manager, go to processes then select adb.exe and end it. maybe that will help. i had a problem once where it identified my phone twice and i could not use adb and reset it that way
Click to expand...
Click to collapse
Worked like a charm, thanks dude

lukekirstein said:
Worked like a charm, thanks dude
Click to expand...
Click to collapse
your welcome. glad it was something that easy to fix

Woops. Delete.

Lost ADB Access...

Hi.
I don't know what happened, but I cant access my phone via adb anymore. I've used adb for months with no problem so far.
The Device is shown in windows xp as "Android Composite ADB Device". I uninstalled an reinstalled the drivers. But ADB and other apps like ddms don't recognize the device anymore.
I'm not sure, but perhaps the problem exists since I installed the modem-driver to use USB-tethering.
USB-Debugging is enabled too...
Does anyone have an idea?
I'm using cyan 4.3.2.1.

Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
If none of that works, try to re-root using this;
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Make sure to backup and stuff, etc. etc.
Hope I helped!

Exodeity said:
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
Click to expand...
Click to collapse
thx a lot for the quick answer, but I tried all of this. In the Recovery (Amon Ras' I recognized the first time, that adb doesn't work)
I can't believe, that I have to re-root... Recovery and SU are still working.
Any other experience with the problem?
p.s.: I unchecked the USB-Tethering and already uninstalled the modem-driver without success...

That's weird, you sure your in the right area on your cmd prompt?
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.

Exodeity said:
That's weird, you sure your in the right area on your cmd prompt? ( Assuming your on windows, the Terminal in linux, I'm sure you know xP )
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Click to expand...
Click to collapse
you gave the right advice...
it's weird. I set adb as variable in windows environment and it worked till today.
Now I started a command prompt in another folder with adb in it and started adb... and it works. weird. I already uninstalled the drivers with usbdeview, restarted etc. a several times and it didn't work. Just use another adb-command finally worked...
thx
Code:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT852KV04159 device

Yeah, that happens to me sometimes, where it says the device didn't ACK, or something, but I just unplug it, plug it back it in, and wait a good minute it works flawlessly.
I guess our G1's just get moody sometimes, I know I would if someone changed my innerds and outterds on a regular basis xD

[Q] Don't know how to connect D3 using ADB

When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.

what operating system are you using

smoshism said:
what operating system are you using
Click to expand...
Click to collapse
I am using windows 7

um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work

smoshism said:
um, is there a way to remount adb? im on ubuntu so i cant help out a whole lot. but maybe i can bounce some ideas that could work
Click to expand...
Click to collapse
im not sure, im not very familiar with ADB

I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.

SrulDog said:
I'm pretty new to this, but seems to me you are trying to open the adb that psouza includes with his tools. (If not, then just ignore me)
that's not gonna work for what you are trying to do. i think you need to download the android sdk to get adb working.
Click to expand...
Click to collapse
i am using the one in the SDK, i have it on my c drive in the correct spot but it still closes itslef

Are you clicking it like an icon or running it from a DOS prompt? It is to be run from the command line as it is a dos/command line program..
Ie.. at the c:\android-sdk-x86\platform_tools\ prompt you type adb and what you want to do.
Adb push or adb pull or adb shell, etc. Just adb will give some command options
Sent from my Xoom

d7benjamin said:
When i open ADB all it does is it has a lot of white writing that scrolls along and then closes, does anyone know if i set it up wrong, or if they could post step by step instructions? it would be much appreciated, Thanks.
Click to expand...
Click to collapse
First you have to open an elevated command prompt. Do this by clicking the start icon, then typing in "cmd" (without the quotes of course) and then right clicking the only thing that pops up and choosing Run As Administrator. After doing this, you need to know where you folder that contains ADB is at. To find this easily, click Start and then click Computer and in the explorer window that just popped up, type in "adb.exe". That will show you where your adb files are at.
Continuing on, for an example, my adb stuff is in C:\root stuffz. So in the command prompt I would type in "cd c:\root stuffz" and then hit enter. After that, I can then do my adb commands, such as "adb shell", "adb push", "adb pull", etc...
Edit: Make sure you have your drivers installed for the phone. Also, make sure the phone is in debug mode and charge only. This should just about cover most of the absolute basics of getting your phone recognized by adb. I'm not too sure if I missed anything, and one of the other more experienced peeps on here can prob give you more detailed information lol.

[Q] adb returning "error: closed"

Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this

Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices

Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip

Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....

xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?

jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this

Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message

ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)

nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.

ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?

ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think

Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.

I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.

worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload

morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key

Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed

KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.

http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app

Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:

mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood

Emulator-5554 error in fastboot

Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE

I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.

neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.

bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process

dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks

bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs

bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error

SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:

bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good: