Open armaanhammer opened 4 years ago
Can you run ./adbfs -f ~/droid
to get adbfs to stay in foreground and paste some of the debug info?
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:
MacBookPro:adbfs-rootless armaan$ ./adbfs -d ~/droid | tee dashD.txt
* daemon not running; starting now at tcp:5037
* daemon started successfully
FUSE library version: 2.9.7
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 2, opcode: INIT (26), nodeid: 0, insize: 56, pid: 39065
INIT: 7.19
flags=0xf8000008
max_readahead=0x00100000
INIT: 7.19
flags=0x00000010
max_readahead=0x00100000
max_write=0x02000000
max_background=0
congestion_threshold=0
unique: 2, success, outsize: 40
unique: 2, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 0
statfs /
unique: 2, success, outsize: 96
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 91
access / 00
unique: 2, success, outsize: 16
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 59
access / 00
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 91
unique: 2, success, outsize: 16
statfs /
unique: 3, success, outsize: 96
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 568
access / 00
unique: 2, success, outsize: 16
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 59
statfs /
unique: 3, success, outsize: 96
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 567
access / 00
unique: 2, success, outsize: 16
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
statfs /
unique: 3, success, outsize: 96
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 568
access / 00
unique: 2, success, outsize: 16
unique: 4, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 567
statfs /
unique: 4, success, outsize: 96
unique: 3, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 568
unique: 2, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 59
access / 00
statfs /
unique: 3, success, outsize: 16
unique: 4, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 91
unique: 2, success, outsize: 96
statfs /
unique: 5, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 567
unique: 4, success, outsize: 96
statfs /
unique: 6, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
unique: 5, success, outsize: 96
unique: 7, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
statfs /
unique: 3, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 567
statfs /
unique: 6, success, outsize: 96
unique: 8, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
access / 00
unique: 7, success, outsize: 96
statfs /
unique: 3, success, outsize: 16
unique: 8, success, outsize: 96
unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 59
unique: 5, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 567
access / 00
statfs /
unique: 2, success, outsize: 16
unique: 5, success, outsize: 96
unique: 4, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 567
access / 00
unique: 4, success, outsize: 16
unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 59
getattr /
--*-- exec_command: adb shell "ls"
adb_getattr
unique: 7, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 1486
statfs /
unique: 7, success, outsize: 96
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 14950
statfs /
unique: 3, success, outsize: 96
unique: 6, error: -2 (No such file or directory), outsize: 16
unique: 8, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
statfs /
unique: 8, success, outsize: 96
unique: 2, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 558
unique: 5, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 631
statfs /
statfs /
unique: 4, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 156
unique: 7, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 556
unique: 2, success, outsize: 96
unique: 5, success, outsize: 96
statfs /
unique: 6, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
statfs /
statfs /
unique: 9, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 654
unique: 4, success, outsize: 96
statfs /
unique: 10, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 1483
unique: 3, success, outsize: 96
unique: 11, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 156
unique: 7, success, outsize: 96
unique: 12, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
statfs /
unique: 13, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 1492
unique: 6, success, outsize: 96
unique: 15, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 5405
statfs /
unique: 14, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 1939
unique: 16, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 5019
statfs /
statfs /
unique: 17, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
unique: 18, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
unique: 9, success, outsize: 96
unique: 19, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 5497
statfs /
unique: 20, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 5503
unique: 21, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 10544
statfs /
unique: 10, success, outsize: 96
unique: 22, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 14216
statfs /
statfs /
unique: 11, success, outsize: 96
unique: 12, success, outsize: 96
unique: 23, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 14950
statfs /
statfs /
unique: 24, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 21165
statfs /
unique: 25, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
unique: 13, success, outsize: 96
unique: 26, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 38134
statfs /
statfs /
unique: 27, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 21671
unique: 15, success, outsize: 96
unique: 28, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 38329
unique: 29, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
statfs /
unique: 14, success, outsize: 96
unique: 16, success, outsize: 96
unique: 30, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 21165
unique: 31, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
unique: 32, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 38527
unique: 33, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 21165
unique: 8, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
statfs /
unique: 2, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
unique: 17, success, outsize: 96
unique: 18, success, outsize: 96
statfs /
unique: 19, success, outsize: 96
statfs /
statfs /
unique: 20, success, outsize: 96
unique: 21, success, outsize: 96
statfs /
statfs /
statfs /
unique: 22, success, outsize: 96
statfs /
statfs /
statfs /
statfs /
statfs /
unique: 23, success, outsize: 96
statfs /
unique: 24, success, outsize: 96
unique: 25, success, outsize: 96
unique: 26, success, outsize: 96
unique: 27, success, outsize: 96
unique: 28, success, outsize: 96
unique: 29, success, outsize: 96
unique: 30, success, outsize: 96
unique: 31, success, outsize: 96
unique: 32, success, outsize: 96
unique: 33, success, outsize: 96
unique: 8, success, outsize: 96
unique: 2, success, outsize: 96
unique: 5, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
statfs /
unique: 5, success, outsize: 96
unique: 4, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
statfs /
statfs /
unique: 7, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
unique: 4, success, outsize: 96
unique: 3, success, outsize: 96
statfs /
unique: 7, success, outsize: 96
unique: 6, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 568
statfs /
unique: 6, success, outsize: 96
unique: 9, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 534
unique: 10, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 557
statfs /
statfs /
unique: 9, success, outsize: 96
unique: 10, success, outsize: 96
unique: 11, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 654
statfs /
unique: 11, success, outsize: 96
^Cumount(/Users/armaan/droid): Resource busy -- try 'diskutil unmount'
^Cunique: 12, opcode: DESTROY (38), nodeid: 1, insize: 40, pid: 39083
unique: 12, success, outsize: 16
MacBookPro:adbfs-rootless armaan$
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:
--*-- exec_command: adb shell "ls"
adb_getattr
After I ran ./adbfs -d ~/droid | tee dashD.txt
above, I was able to cd into the directory and try these things in Terminal 2:
MacBookPro:~ armaan$ cd -
/Users/armaan/droid
MacBookPro:droid armaan$ ls -lha
ls: .: Device not configured
MacBookPro:droid armaan$ ls
.
MacBookPro:droid armaan$ mkdir test
mkdir: test: Device not configured
MacBookPro:droid armaan$ sudo mkdir test
mkdir: test: Device not configured
Then I tried to Ctrl+C adbfs in Terminal 1, which created the ^Cumount(/Users/armaan/droid): Resource busy -- try 'diskutil unmount'
line.
Then I moved out of the directory in Terminal 2:
MacBookPro:droid armaan$ cd -
/Users/armaan
Which allowed Ctrl+C to work in Terminal 1, creating the ^Cunique: 12, opcode: DESTROY (38), nodeid: 1, insize: 40, pid: 39083 unique: 12, success, outsize: 16
line.
To my knowledge, nothing I did in Terminal 2 produced any output on Terminal 1.
Did ./adbfs -f
(not -d
) not produce anything?
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 adb shell ls
yourself, what sort of output are you getting from it?
Sorry about the delay.
MacBookPro:adbfs-rootless armaan$ ./adbfs -f ~/droid/
--*-- exec_command: adb shell "ls"
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb_getattr
--*-- exec_command: adb shell "ls -l -a -d '/'" 2>&1
^Cumount(/Users/armaan/droid): Resource busy -- try 'diskutil unmount'
^C--*-- exec_command: rm -rf /tmp/adbfs-GhCNsI/
The terminal hangs after the --*-- exec_command: adb shell "ls -l -a -d '/'" 2>&1
line, and nothing I do to the mount point seems to generate any additional output. ^C failed this time again due to another terminal session being in the mount point directory and succeeded when I had moved that session out of it.
The mount point directory behaves the same as above:
MacBookPro:droid armaan$ ls
.
MacBookPro:droid armaan$ ls -l
ls: .: Device not configured
etc.
running adb shell ls
gives me the root file structure on the Android device, as expected.
The only idea I had was that adb shell ls
isn't getting recognizable results - with the output cleaned up a bit it seems like ls
might be working and its adb shell "ls -l -a -d '/'"
where things get stuck. The exact output with your computer/device combination might shed some light on why that might be. Don't have other ideas at the moment sadly.
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.