Hello
my android tv box is detected as android device by my pc, and it cause me problem with adb command
I've disabled usb debugging and close developpement settings but it still connected by adb via wifi
F:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
192.168.100.7:5555 device
Click to expand...
Click to collapse
can you help me please to resolve this problem please ?
Go to dev option and click on revoke.
Related
I've received my Fire TV today with fw 51.1.4.0_user_514006420 on it. The device works fine for all the amazon related features.
Now I would like to run xbmc/sbmc on it. So I grabbed adbFire 1.14 trying to connect to the Fire TV.
But all im getting is this:
adbFire logfile
reading database
server started
./adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
starting server
process time duration: 1 seconds
ssh check
./adb.exe -s 10.0.0.73:5555 shell sshstatus
error: device not found
I have really tried everything I could think of : disabled pc firewall, tested from wifi and lan, from laptop, used static ips instead of dhcp etc ..
Nothing .. I did a factory reset, power cycled several times - still the same. I am 100% sure about the IP address of the Fire TV, and I can ping the device from my pc's just fine (same subnet).
I've tried adb.exe connect 10.0.0.73 from a command prompt .. same thing (unable to connect to 10.0.0.73:5555). The PCs IP is 10.0.0.64 ..
What am I missing ? I've read the forum up and down and can't find anything about it .. thanks for any advice!
Did you remember to navigate to Settings\System\Developer Options and turn on ADB debugging on the FireTV?
KCFish said:
Did you remember to navigate to Settings\System\Developer Options and turn on ADB debugging on the FireTV?
Click to expand...
Click to collapse
YES! That was it. Thanks for the hint. Now I feel a little dumb ..
mastersnuggles said:
YES! That was it. Thanks for the hint. Now I feel a little dumb ..
Click to expand...
Click to collapse
So do I
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
Hello,
My Z1C's power button have stpped working and currently my phone is off. I'm not sure if debuggin is enabled (and can't find proper guide how to turn it on using debugging)
Can anybody help me please!
my power button is also broken and here is how I boot the phone when it turns off
* debugging should be turned on and ADB drivers installed on the PC
while pressing the vol up button connect the usb cable to the phone (other end already connected to the PC)
the notification light should turn blue
start the ADB prompt on PC
run command adb reboot
karamancho said:
my power button is also broken and here is how I boot the phone when it turns off
* debugging should be turned on and ADB drivers installed on the PC
while pressing the vol up button connect the usb cable to the phone (other end already connected to the PC)
the notification light should turn blue
start the ADB prompt on PC
run command adb reboot
Click to expand...
Click to collapse
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
It get's blue light, I make a location adress to platform-tools, then adb reboot and get this message
I got this message. Can it be it doesn't recognise my phone?
i've used file transfer quite a lot, it should have autoinstalled drivers of my phone
TasKitas said:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found
It get's blue light, I make a location adress to platform-tools, then adb reboot and get this message
I got this message. Can it be it doesn't recognise my phone?
i've used file transfer quite a lot, it should have autoinstalled drivers of my phone
Click to expand...
Click to collapse
Maybe it's because you didn't enable debuging in the dev options but thats another problem.
Try googling the error message, maybe you'll find a solution
karamancho said:
Maybe it's because you didn't enable debuging in the dev options but thats another problem.
Try googling the error message, maybe you'll find a solution
Click to expand...
Click to collapse
Probably it's off, thanks for suggestion
TasKitas said:
Probably it's off, thanks for suggestion
Click to expand...
Click to collapse
you should also try the fastboot reboot command
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?