-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection refused #10
Comments
try to connect using shell adb, if it also doesn't work then the problem is that it is not an adb port |
Enter the phone IP address to connect During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Either you don't have access to the device, or the port is closed |
Do you still need help some things to try are pinging the device looking into adb --help shows you the list of commands that you can use in order to set yourself up for success. |
EDIT: this works there are no issues.
Yo. If I am using adb over lan and I can connect via my ipv4:5555 by using adbtools why would I not be able to connect with the tool?. How would I go about being able to connect using the tool. I know that I can disconnect from my ipv4:5555 and the adbridge will still send a signal So. that I can reconnect anytime, but for some reason I get connection refused from the tool. hahaha. |
Hey! I used shodan to find target device. When i try to connect i have an error:
connection refused
Can you help me please?
The text was updated successfully, but these errors were encountered: