Closed joshn closed 5 years ago
Digging a little deeper and trying to run these steps via the command line, the initial problem seems to be accessing the apk via adb:
>.\tools\adb.exe pull /data/app/com.beatgames.beatsaber-1/base.apk
adb: error: remote object '/data/app/com.beatgames.beatsaber-1/base.apk' does not exist
>.\tools\adb.exe shell ls /data
ls: /data: Permission denied
The device is connected, and I've enabled developer mode on my account. I'm assuming this was successful because I now have the option in the headset to disable the guardian. According to the following, adb is running as the shell user:
>.\tools\adb.exe shell whoami
shell
C:\Users\josh\Documents\Beatsaber\QuestSongsInstaller\dist>.\tools\adb.exe shell ls -l
ls: ./cache: Permission denied
ls: ./default.prop: Permission denied
ls: ./file_contexts.bin: Permission denied
<snip>
total 160
dr-xr-xr-x 23 root root 0 1970-01-06 11:18 acct
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 bt_firmware
lrw-r--r-- 1 root root 50 2009-01-01 03:00 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
lrw-r--r-- 1 root root 13 2009-01-01 03:00 charger -> /sbin/healthd
drwxr-xr-x 4 root root 0 1969-12-31 19:00 config
lrw-r--r-- 1 root root 17 2009-01-01 03:00 d -> /sys/kernel/debug
drwxrwx--x 38 system system 4096 1969-12-31 23:26 data
<snip>
...but the data directory is owned by system. Is there some step I'm missing here?
Solved! Try a different USB port if you're seeing this problem.
After a full device reset, I noticed that the first step, pulling the apk, was not exactly failing. It was running somewhere between 6-12%, then stopping without an error. At the same time, windows would remount the headset. Digging into adb discussions, it looks like some USB3 ports exhibit this problem. I switched to a USB2 port, and everything worked perfectly.
I'm having a similar problem to some others, but with some different errors. I've let this continue and had to re-download Beat Saber a few times, and I get similar failures with v3. There are a few different errors here, I'm not sure if they're related to a single root cause: