I am having a problem while trying to root my . When I try to make sure that my device is connected by typing 'adb.exe devices' through command prompt I get the error message:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Please help!!!
Command is adb devices. Then once device is shown adb reboot-bootloader to enter fastboot.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Also make sure adb and fastboot are in root folder of their own eg c:\adb
passion8059 said:
Command is adb devices. Then once device is shown adb reboot-bootloader to enter fastboot.
---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------
Also make sure adb and fastboot are in root folder of their own eg c:\adb
Click to expand...
Click to collapse
still not working I still get the same error, I don't know what I' m doing wrong. I followed the LG G4 "Low Effort Root" guide but as stated earlier I still cant get the command window to recognise my phone
Use twrp and ensure you have supersu 2.49.zip on phone storage.
use this guide to assist hope it helps: http://www.theandroidsoul.com/how-to-install-lg-g4-twrp-recovery-easily-79553/
While following the steps on how to install twrp recovery on lg g4 I still get the same error above. I don't know what I'm doing wrong that my computer is not recognising my device.
If you happen to have a Dell PC, uninstall the Dell PC Suite. Many users report issues with Dell PC Suite and ADB. Various AntiVirus Software, Samsung's Kies (3), Norton and McAffee Safe Filter services are known to cause issues with ADB. Also, make sure you're not using a USB 3.0, which isn't your problem but could be once you establish a functioning connection via adb.
Just to let you know I am trying this on a samsung laptop, after uninstalling Samsung kies I get the error:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
My guess is that there are software on the laptop that are conflicting with the process so I'll uninstall all the programs that I don't use but if anyone has anymore solutions please contribute
Related
Hello guys, I need a lot of help from you guys
Today was changing the rom on my lg e977, but when I was formatting inadvertently deleted the sdcard also. I can access the fastboot and CWM with all the drivers installed, but when I access via adb I get the message
"* Daemon not running. Starting it now on port 5037 *
ADB server did not ACK
* failed to start daemon *
error: can not connect to daemon "
I believe I'm getting this message, because I believe that usb debugging was not enabled.
Anyone know what I can do?
now i'm getting the message:
error: device unauthorized. Please check the confirmation dialog on your device
but i cant boot the phone, so i need to enable usb debugging via adb, right?
Solved! Used this steps:
1 Make sure you have LG United Drivers already installed, otherwise download from below
2 Download Lg suport tool
3 Put your Optimus G into Download Mode by switching it off, attaching the usb cable to the phone, holding both the up and down volume buttons at the same time and lastly inserting the usb cable into the computer; wait for the drivers to finish loading if doing it for the first time.
4 when your phones conect to pc suport tool then go to software update
5 Click check in the first option. the program will close and a new one will open,wait for the flash process to finish.
6 you must have a internet conection, the whole process takes an hour or less. the phone will reboot when finish.
Sent from my LG-E975 using xda premium
Hi,
I try to connect my Desire HD with a Surface Pro 3, running Windows 10, using a USB cable.
But the device isn't reccognized in the device manager.
This is what I tried:
Using a USB 2.0 hub, since I read that there are problems with USB 3. The Surface Pro has one USB port only.
Installing HTC drivers from different sources. I installed HTC Sync and could sync my files using this but couldn't connect to adb
I uninstalled HTC sync, extracted the driver from the setup file and installed the driver only.
I ran through the setup of "15 seconds ADB installer" => no success.
I ran through the setup of "Universal ADB drivers" => no success.
Android Debugging is turned on in the developer settings.
Using Minimal ADB and Fastboot:
Code:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>
Any help on that is greatly appreciated.
Thanks
Susi
Yup having the same problem with htc desire x. I want to root it using windroid. But whenever i connect it in recovery mode it gives error i tried same methods as u did but all in vain.
---------- Post added at 09:26 AM ---------- Previous post was at 09:26 AM ----------
https://youtu.be/ndIPo8nJjvc
This might help.
Hi all,
today i tried to connect to my HTC 10 using adb and it wouldn't even find the device.
I updated the android sdk, which did not solve the problem. But i did find some other "fancy" things
First of all some info on my device
software: 1.95.401.4 stock
unbranded eu device
s-off and bootloader locked
phh's systemless root
systemless xposed
After i did s-off my device, i was able to fastboot flash twrp, adb was working, also after installing magisk and systemless root/xposed adb was working fine. When adb did not work i was like "perhaps i disabled usb-debugging, so enable it" but it was still enabled.
Here we come to another problem, with usb-debugging enabled, my mac/phone won't recognize it's plugged in via usb, a message pops up stating
Slow charge
For faster results, use the original HTC charger
Click to expand...
Click to collapse
if i then
uncheck usb-debugging -> the device gets recognized/recognizes it's attached to a usb port
a message pops up asking if i want to enable file transfer
rechecking usb-debugging -> device still recognizes it's attached to a usb port
a message pops up asking if i want to allow usb-debugging
running
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and
Code:
adb devices
List of devices attached
or
Code:
adb usb
error: no devices/emulators found
then i thought, ok revoke usb debugging authorization, unplug the device and plug in again, grant authorization and off we go, but i do not get the message if i want to authorize the pc
anyone else encountered this before or has any idea whats wrong here?
EDIT: it's working now, i do not know exactly why.
went into magisk manager to disable superuser and xposed to be able to rule out they were interfering in some way
saw magisk update is available so i updated magisk to v9
restarted without disabling modules
and now it works again. phone recognizes it's attached to usb even if usb-debugging is enabled.
EDIT2: can be closed by a mod as it's solved
Any help with ADB? tried everything adb kill-server and then adb start-server... change back and forth file transfer... turn on and off usb debug...
The think is tablet is connected can see phone memory and sd card and transfer files, but never see the fingerprint window asking me to allow usb debug
wallyhenderson said:
Any help with ADB? tried everything adb kill-server and then adb start-server... change back and forth file transfer... turn on and off usb debug...
The think is tablet is connected can see phone memory and sd card and transfer files, but never see the fingerprint window asking me to allow usb debug
Click to expand...
Click to collapse
Have you enabled USB debugging in Developer Options?
waterdaan said:
... turn on and off usb debug...
Click to expand...
Click to collapse
as i have said... many times
wallyhenderson said:
as i have said... many times
Click to expand...
Click to collapse
Sorry I missed the
... turn on and off usb debug...
Anyway, the problem is not the Tab S4, your adb server isn't starting
it should look something like
Code:
adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
yours says adb server is out of date
waterdaan said:
Have you enabled USB debugging in Developer Options?
Click to expand...
Click to collapse
waterdaan said:
Sorry I missed the
... turn on and off usb debug...
Anyway, the problem is not the Tab S4, your adb server isn't starting
it should look something like
Code:
adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
yours says adb server is out of date
Click to expand...
Click to collapse
but when i plug the usb cable it does not show the fingerprint message to accept usb debug... that should be because adb on pc?
wallyhenderson said:
but when i plug the usb cable it does not show the fingerprint message to accept usb debug... that should be because adb on pc?
Click to expand...
Click to collapse
You've probably chosen always trust this computer
You could revoke USB debugging authorizations in Developer Options
---------- Post added at 16:03 ---------- Previous post was at 15:59 ----------
@wallyhenderson
I would download the adb from this link and try to use that
https://wiki.lineageos.org/adb_fastboot_guide.html
waterdaan said:
You've probably chosen always trust this computer
You could revoke USB debugging authorizations in Developer Options
---------- Post added at 16:03 ---------- Previous post was at 15:59 ----------
@wallyhenderson
I would download the adb from this link and try to use that
https://wiki.lineageos.org/adb_fastboot_guide.html
Click to expand...
Click to collapse
its crazy... revoked authorizations and same... it does not ask for the fingerprint... downloaded your adb and same...
wallyhenderson said:
its crazy... revoked authorizations and same... it does not ask for the fingerprint... downloaded your adb and same...
Click to expand...
Click to collapse
Strange....
Just to check if adb is working,
Type only adb and hit enter
That should give you a help screen
If you do 'adb devices' and the adb server isn't running, it will start the adb service
Example without device connected to the computer
Code:
adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Have you added adb as an Environment Variable in Windows?
Maybe in a previous install?
Check if it works with your phone in stead of the tablet
Greetings,
I am attempting to run Tasker with AutoApps on my Note 10.
I get the following message when I run ADB from my MacBook.
adb: no devices/emulators found
I have USB Debugging enabled, and I installed Android File Transfer and also tested with Samsung Smart Switch. Both applications make successful connections with my Note 10, but I am confused as to why ADB does not detect my device. Any help is greatly appreciated.
I also ran...
/adb kill-server
./adb devices
and receive the following...
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
There is no device listed.
Any assistance would be greatly appreciated.
Did you try ./adb devices again after daemon had started?