-
Notifications
You must be signed in to change notification settings - Fork 77
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
"Device not configured" in response to every command #46
Comments
Can you run |
Thanks for the reply! Here you go. I'm not sure if it'll be very helpful though. I started adbfs in Terminal 1, then tried various commands in Terminal 2. Terminal 1:
This is the file that tee created, in case it's relevant. I found it odd that this is all that got saved to it. It's probably due to something I don't understand about what's happening with the shells though:
After I ran
Then I tried to Ctrl+C adbfs in Terminal 1, which created the Then I moved out of the directory in Terminal 2:
Which allowed Ctrl+C to work in Terminal 1, creating the To my knowledge, nothing I did in Terminal 2 produced any output on Terminal 1. |
Did edit: to clarify, I'm having a hard time parsing the full debug output from fuse as most of the content is largely irrelevant. But I guess as you said, it doesn't appear to be very helpful. If you run |
Sorry about the delay.
The terminal hangs after the The mount point directory behaves the same as above:
etc. running |
The only idea I had was that |
Environment:
Followed steps on this page: https://tamasnagy.com/blog/mtp-interconnect-mac-linux/
When I run
./adbfs ~/droid
, the ~/droid folder disappears from Finder (the GUI file manager). The folder still exists in the command line, but does not respond properly to ls:grepping an ls -lha of the home directory yields interesting results:
So maybe there is a permissions problem?
No, that still didn't work. Starting an adb shell works fine though.
Anyone have any guidance for me? I bet that I'm missing something obvious. The main thing I want to be able to do is use rsync on the computer to wholesale copy files from the Android. Or, even use dd to create an image of it.
The text was updated successfully, but these errors were encountered: