

1·
24 days agoWould you mind sharing some details? computer OS name and version, your adb version and if you installed systemwide or if you compiled/downloaded out of your repos
Would you mind sharing some details? computer OS name and version, your adb version and if you installed systemwide or if you compiled/downloaded out of your repos
Did you tried running adb push with sudo? Do a kill-server before
You didn’t mention it so I asume that you can open a shell, did you tried creating a file in the destiny? Also SELinux may be the problem, try temporary disable it, if works, enable it and create an exception. Other thing; since adb daemon runs on 127.0.0.1:5073/TCP check if you have any localhost firewall rules, but this doesn’t make sense if you can open a shell. Last things, download the lastest SDK, you don’t need to install it, just call adb with the full path.