I'm trying to get adb to detect my Electrify on Windows 8, it would seem rooting and/or installing ROMs is impossible without adb, I have my phone plugged in and all the drivers installed except one "Motorola ADB Interface" of course. The manual driver installer errors out on "Cannot detect Operating System" is there anyway around this, either forcing the driver in, or not using ADB to root?
Use a linux live cd and install the android sdk, or use something like vmware, or try to extract the driver and force it to install in device manager, or dual boot an os that isnt in beta...
Sent from my MB855
The linux live cd should actually work I didnt think about that
I found this
http://forum.xda-developers.com/showthread.php?t=741824
It says its for use with HTC phones but could it possibly work with mine?
Its a year and a half old
Will the driver for my phone be installed/available?
I would post this there but its kind of a dead thread
If you have a spare thumb drive of 4gb or larger laying around you can do a persistent install of ubuntu (or just about any other distro) using LinuxLive USB Creator, which can be found here: http://www.linuxliveusb.com/
If you're not very familiar with linux, persistence is like having your linux operating system on a thumb drive with the advantage over a live cd being that any changes you make (such as installations or saved files) are not lost upon shutdown. So you could install the android sdk (which is all you should need) and then whenever you needed it you could just boot from your thumb drive. If you need help setting up (such as installing the sdk and setting the path and what not) let me know.
-devx
I have looked everywhere, spent countless hours and days trying to find a PERMANENT solution for this. Only solution i could find was to use TaskManager and kill adb process. Not a permanent solution. As the same error will come back.
This is the error. Nothing causes it, just happens randomly with any device im using.
Code:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Thanks guys. A permanent solution would be awesome. I'm tired of this..
elesbb said:
This is the error. Nothing causes it, just happens randomly with any device im using.
Code:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
A permanent solution would be awesome. I'm tired of this..
Click to expand...
Click to collapse
First, the obvious: have you tried different USB cables and different USB ports on your machine? (I'll assume the answer is "yes").
Now, the more likely: get a copy of USBDeview and use it to remove all copies of your ADB USB drivers. In case you're not familiar with it, this util will list every USB driver installed on your machine and (among other things) will let you delete the ones you don't want. If you've been using your current setup for a while, you'll be appalled at the cruft that's built up. Be aware that there are separate 32 and 64-bit versions, so get the one appropriate for your system.
The ADB driver(s) may be identified as "Android ADB Interface" or any of several other names. You'll see entries for various USB Vendor and Product IDs, with at least one entry for each Android device you've connected. The one thing all of the relevant entries will have in common are the values in the columns labeled USB Class, USB Subclass, and USB Protocol. Those values are ff, 42, and 01, respectively.
Sort the list by Class to group them, then uninstall all of them. When you're done, reboot. You may want to reopen the util to confirm they're really gone. Finally, attach each device in turn and let the New Hardware Wizard walk you through reinstalling the driver (which means, of course, that you'll want to have your driver packages ready before you go deleting anything).
Note: there's really only one driver (i.e. binary) for all devices. The difference in the packages is their .INF files, each of which usually only identifies Vendor and Product IDs for a single manufacturer. If you know those values for each device, you can edit the .INF file for one and add all your devices to make a one-size-fits all package (be sure to add each entry under both the 32-bit and 64-bit headings in the file). You'll still have to reinstall for each device but you won't need multiple packages to do it.
adb kill-server
adb start-server
Should get you back on track.
es0tericcha0s said:
adb kill-server
adb start-server
Should get you back on track.
Click to expand...
Click to collapse
No.. you're wrong.
dolorespark said:
First, the obvious: have you tried different USB cables and different USB ports on your machine? (I'll assume the answer is "yes").
Now, the more likely: get a copy of USBDeview and use it to remove all copies of your ADB USB drivers. In case you're not familiar with it, this util will list every USB driver installed on your machine and (among other things) will let you delete the ones you don't want. If you've been using your current setup for a while, you'll be appalled at the cruft that's built up. Be aware that there are separate 32 and 64-bit versions, so get the one appropriate for your system.
The ADB driver(s) may be identified as "Android ADB Interface" or any of several other names. You'll see entries for various USB Vendor and Product IDs, with at least one entry for each Android device you've connected. The one thing all of the relevant entries will have in common are the values in the columns labeled USB Class, USB Subclass, and USB Protocol. Those values are ff, 42, and 01, respectively.
Sort the list by Class to group them, then uninstall all of them. When you're done, reboot. You may want to reopen the util to confirm they're really gone. Finally, attach each device in turn and let the New Hardware Wizard walk you through reinstalling the driver (which means, of course, that you'll want to have your driver packages ready before you go deleting anything).
Note: there's really only one driver (i.e. binary) for all devices. The difference in the packages is their .INF files, each of which usually only identifies Vendor and Product IDs for a single manufacturer. If you know those values for each device, you can edit the .INF file for one and add all your devices to make a one-size-fits all package (be sure to add each entry under both the 32-bit and 64-bit headings in the file). You'll still have to reinstall for each device but you won't need multiple packages to do it.
Click to expand...
Click to collapse
I thank you a million! This looks promising! I did notice like 20 different adb devices installed. So far it's been good hopefully it stays that way!
Sent from my SGH-M919 using Tapatalk
Yea, sorry, that is the temp solution, not a permanent one.
es0tericcha0s said:
Yea, sorry, that is the temp solution, not a permanent one.
Click to expand...
Click to collapse
Not only that, but it's not even a temp solution. How can I or anyone kill a server you can't connect to?
Sent from my SGH-M919 using Tapatalk
elesbb said:
Not only that, but it's not even a temp solution. How can I or anyone kill a server you can't connect to?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Oh. I see you don't understand the commands. You said that you had to continue to go to the Task Manager to kill the process and then you would restart it. That's what those commands do, without taking that step. I've solved this issue before with doing that, though it's never been an ongoing thing, so haven't had to deal with making it permanent. Guess we have a different idea of what wrong is...
es0tericcha0s said:
Oh. I see you don't understand the commands. You said that you had to continue to go to the Task Manager to kill the process and then you would restart it. That's what those commands do, without taking that step. I've solved this issue before with doing that, though it's never been an ongoing thing, so haven't had to deal with making it permanent. Guess we have a different idea of what wrong is...
Click to expand...
Click to collapse
What I'm saying is, running adb kill server wouldn't do anything because it can't connect to the adb server daemon due to that error I was receiving. After running adb kill server then running adb start server I would still get that same exact error. Which makes sense because it can't connect to the server so therefore is unable to kill it making task manager the only way of killing the server.
Sent from my SGH-M919 using Tapatalk
elesbb said:
What I'm saying is, running adb kill server wouldn't do anything because it can't connect to the adb server daemon due to that error I was receiving. After running adb kill server then running adb start server I would still get that same exact error. Which makes sense because it can't connect to the server so therefore is unable to kill it making task manager the only way of killing the server.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
What I'm saying is that command is specifically for that issue, because the adb server is not starting correctly because it's kind of stuck. If the server wasn't on at all, it wouldn't be listed in the Task Manager, right? I've had this issue multiple times before on various devices, and that's what got it to come back on and connect again. I literally do this stuff for a living and have modded 100s of devices. Weird things pop up like this all the time and it's not always the same solution for everyone or every device.
start-server Checks whether the adb server process is running and starts it, if not.
kill-server Terminates the adb server process (which the Task Manager also does, but this is the command for it)
So yea, my solution didn't work for you, but it is a solution for this issue. Been there. Done that. Probably will have to do it again some day.
es0tericcha0s said:
What I'm saying is that command is specifically for that issue, because the adb server is not starting correctly because it's kind of stuck. If the server wasn't on at all, it wouldn't be listed in the Task Manager, right? I've had this issue multiple times before on various devices, and that's what got it to come back on and connect again. I literally do this stuff for a living and have modded 100s of devices. Weird things pop up like this all the time and it's not always the same solution for everyone or every device.
start-server Checks whether the adb server process is running and starts it, if not.
kill-server Terminates the adb server process (which the Task Manager also does, but this is the command for it)
So yea, my solution didn't work for you, but it is a solution for this issue. Been there. Done that. Probably will have to do it again some day.
Click to expand...
Click to collapse
I understand that this solution may work for a temporary issue. I myself us it all the time when I can't see a device or something. But what im trying to say is the error says "server didn't ACK" in my searching of this error, ACK means acknowledge. Therefore communication with the server fails. So sending the server a kill command fails as well. See what i mean?
Lets just hope the other guys method works. Was surprised to see about 12 or so ADB devices when i only have 3
I have 5 devices here, Asus MeMo Pad ME170c, Lenovo 3500-fl, Archos Gamepad, HTC Desire HD and a cheapo generic chinese AllWinner a13. I cannot seem to get any of them to work on this pc. I cannot access them via adb nor browse the files on them via windows. Both the Asus and Lenovo are running KitKat 4.4.2 and connect up and under adb show as unauthorized, but I never get the authorization prompt on the devices. They show up under My PC where upon trying to access internal storage the window locks up/stops responding and the progress bar at the top fills up and gradually gets slower and slower until it's almost finished but then just carries on forever. I can never access the files. On my other pc I can access the files and get the authorization promp. Both pcs are running the exact same copy of windows 8.1 (installed from the same disk), are up to date and are both running the same usb drivers. So why can't I access the devices from this (my main) pc. The other devices are running older versions of android so I don't need to authorize the computer on these. They periodically show up as 'device' under adb but i cannot access their files as they show up as a removable device and when trying to access them windows says 'no media in the drive'.
I've done everything the same on both machines, the only difference is their hardware so I am wondering if there is anything hardware related that could be causing this problem. Could it be something to do with the motherboard?
The pc I can't access the devices with has an Asrock Z77 Pro4-M motherboard.
Does anyone have any suggestions on what could be going wrong here?
Cheers
Fraz.
I've been trying to sort this out on and off for months now and had no success. It's such a hassle having to upload and email myself the apk every time I need to test something. Any suggestions?
I am trying to sync my BQ Aquaris Ubuntu Phone with my Caldav and Carddav Server. To follow this guide on how set everything up I tried to connect to my phone via adb shell. Unfortunatley I get "error: device not found"...
The phone is mounted as mtp. I also tried different USB-cables. I turned the device and my Computer on and off. I killed and started the adb server...
Still no success. Maybe someone can help me.
virgilcaine23 said:
I am trying to sync my BQ Aquaris Ubuntu Phone with my Caldav and Carddav Server. To follow this guide on how set everything up I tried to connect to my phone via adb shell. Unfortunatley I get "error: device not found"...
The phone is mounted as mtp. I also tried different USB-cables. I turned the device and my Computer on and off. I killed and started the adb server...
Still no success. Maybe someone can help me.
Click to expand...
Click to collapse
I can't post links yet but google "bq-e4-5-adb-fails", the article is on the ask Ubuntu site. You need to add the BQ vendor ID so that adb recognize your new phone.
You can install "ubuntu-sdk" (search ppa in google) and then put your bq in developer mode, open ubuntu-sdk, go to devices and open ssh session. And then you don't need adb, you can exec sync using ssh session.
Hi, I have been trying to “debloat” my Samsung TabA8 and have been trying to do it for some days now. Have done everything according to online directions )Developer Options, debugging, etc.)
My problem:
When opening ADB power shell, I get only the list of some of the installed apps on my laptop with Windows 10, but no apps on the Samsung Tablet. Win10 apps then ask me how I want to open those apps. Some of my choices are: Notepad, Open Office,Google Drive, Internet Explorer.
I have tried all of them. Nothing is working.
How do I get a list of Samsung full apps list on the desktop power shell window??
Just entering for instance: “adb shell pm list packages“ or: “com.samsung.android.apps.spage” is not recognized. I have tried several others also.
I have done all of the online remedies and tried the same thing with another tablet-same problem. Nothing seems to help. There is probably something really easy I am missing...(I hope)
If anybody has any suggestions/advice, I would appreciate it very, very much.
uses platform tools then uses adb from inside them not powershell.
read it here https://developer.android.com/studio/releases/platform-tools
Thank you very much for taking the time to reply. Yes, I have been using the platform tools app. Also, made sure that the drivers are up to date. My problem starts in the platform tools power shell. Samsung apps are not visible there. In the past, before adb + develpoper options ,etc.,connecting the tablet to the laptop via usb, I can see the content and can delete pictures, etc.
So, I'm doing something wrong somewhere with adb.... I would really like to disable and render invisible some of those pesky Samsung apps without rooting. Have rooted my Nexus several years ago. It was great. I just don't want to lose the warranty for now.
Again, thank you. If you have any other suggestions, I will appreciate it very much.
Update...I just realized that the problem is probably with adb and power shell. At opening at the top it reads:
"PS C:\ User's \Ann\ Desktop\adb setup"
Is it not completly set up?
A few days ago,I have unzipped, and agreed to install Fastboot, ADB system-wide and installed Device Drivers. If I right click, it wants me to install again. Have done it a couple of times.... Still, it just isn't working...
Again...thank you!
Oh, one more thing I failed to mention is that this tablet is WiFi only. Does it make any difference? I want to debloat it first before doing it on my Samsung S22 phone.
-Device Driver installation problem (your wins)
-Platform tools (adb,fastboot) run with CMD from inside this folder.
you known howto fix it. wins problem.!
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
You should also replace your adb with the latest binaries by Google.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the platform tools for windows zip file. Find out where your current adb.exe file is located. Extract the zip into that location, overwrite the old file(s).