It seemed to be going so well

[cepacolmax]

During install, the script passed its prereq checks, and looked like it was going to succeed. Orbic rebooted as expected, file was pushed, and then the script failed with this message:

./install-linux.sh 
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 2393.5 MB/s (927624 bytes in 0.000s)
adb: error: failed to read copy response

Tried to run a second time with RUST_BACKTRACE=1, and the script gets stuck "waiting for reboot," but the Orbic does not reboot. Waited several minutes before bailing out with ^C

./install-linux.sh 
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
Device already in command mode. Doing nothing...
adb enabled, waiting for reboot...^C

Manually rebooted the Orbic, reconnected, tried install again, identical result.

No indication on the Orbic that any installation has taken place.

[elixx]

I ran into similar errors trying to push one of the init files to /etc/init.d/. I was able to copy it to other locations, but still can't get it to the desired location. Using adb push results in the above timeout adb: error: failed to read copy response. From a root shell I get permission denied. When I try the same via the baseboard interface with AT+SYSCMD= but get back ERROR... just for that location and most of /etc.

[John-JacobJingleHeimer-Schmidt]

I'm also having the "adb: error: failed to read copy response" issue. Any advice is welcome.

[elixx]

The files I sent most recently with adb push have UID 2000. So far, it seems like UID1000 and 2000 files seem to be untouchable by the rootshell or the baseboard ATSYSCMD, even though uid=0. I can still run the process manually and disconnect, but can't get the init scripts in place.

[issacaron]

During install, the script passed its prereq checks, and looked like it was going to succeed. Orbic rebooted as expected, file was pushed, and then the script failed with this message:

./install-linux.sh 
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 2393.5 MB/s (927624 bytes in 0.000s)
adb: error: failed to read copy response

I was able to get past a similar issue on Linux Mint 22.1 by running the installer as sudo.

[Crank-Git]

Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
Device already in command mode. Doing nothing...
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 3457.2 MB/s (927624 bytes in 0.000s)
Received unexpected responseAT+SYSCMD=cp /tmp/rootshell /bin/rootshell

I get the following on Ubuntu 24.04

[Crank-Git]

It was a permissions issue with the rootshell itself. chmod +x is golden

[John-JacobJingleHeimer-Schmidt]

I'm also having the "adb: error: failed to read copy response" issue. Any advice is welcome.

I'm still getting this same error when trying to install as sudo on Ubuntu 24.04.2. The Orbic is running firmware 1.0.3.

After it fails, I run ads devices, and the Orbic doesn't show up in the list either.

[John-JacobJingleHeimer-Schmidt]

During install, the script passed its prereq checks, and looked like it was going to succeed. Orbic rebooted as expected, file was pushed, and then the script failed with this message:

./install-linux.sh 
Using adb at ./platform-tools/adb
Force a switch into the debug mode to enable ADB
adb enabled, waiting for reboot... it's alive!
waiting for atfwd_daemon to startup... done!
./rootshell: 1 file pushed, 0 skipped. 2393.5 MB/s (927624 bytes in 0.000s)
adb: error: failed to read copy response

I was able to get past a similar issue on Linux Mint 22.1 by running the installer as sudo.

I'm getting the adb: error: failed to read copy response when running the installer as sudo with Mint as well

[Crank-Git]

@John-JacobJingleHeimer-Schmidt and @issacaron Did you chmod +x rootshell inside of the release dir before running ./install-linux?

I don't know if that will help you guys as it doesn't seem we are getting the same issue, but that is was solved it for me.

[John-JacobJingleHeimer-Schmidt]

@John-JacobJingleHeimer-Schmidt and @issacaron Did you chmod +x rootshell inside of the release dir before running ./install-linux?

I don't know if that will help you guys as it doesn't seem we are getting the same issue, but that is was solved it for me.

Sure did. No joy.

[Crank-Git]

Another question, have you tried a different cable and different usb port/controller? Check out this issue, it's from scrcpy, but users claiming:

"I think this is not an issue of scrcpy, adb from platform-tools of android studio also have same issue.

but even though the adb output show an error, the file sent successfully without corrupt"

and

"Just used a cable with better bandwidth and it worked.

Originally I had a 100W usb 2.0, but I switched to a 60W 10Gbps cable and it worked. Things like adb shell work, I don't know why only scrcpy doesn't, I thought it would work as far as audio forwarding but not video."

https://github.com/Genymobile/scrcpy/issues/3241

Past this, it is probably an issue with the device itself one would think.

[John-JacobJingleHeimer-Schmidt]

Another question, have you tried a different cable and different usb port/controller? Check out this issue, it's from scrcpy, but users claiming:

"I think this is not an issue of scrcpy, adb from platform-tools of android studio also have same issue.

but even though the adb output show an error, the file sent successfully without corrupt"

and

"Just used a cable with better bandwidth and it worked.

Originally I had a 100W usb 2.0, but I switched to a 60W 10Gbps cable and it worked. Things like adb shell work, I don't know why only scrcpy doesn't, I thought it would work as far as audio forwarding but not video."

Genymobile/scrcpy#3241

Past this, it is probably an issue with the device itself one would think.

Holy crap do I feel dumb. Used a better cable, and boom! Thanks!

[Crank-Git]

Don't feel dumb, adb is a nightmare apparently. @issacaron, @cepacolmax, and @elixx , you should try the same.

[jmbox80]

Another question, have you tried a different cable and different usb port/controller? Check out this issue, it's from scrcpy, but users claiming:

"I think this is not an issue of scrcpy, adb from platform-tools of android studio also have same issue.

but even though the adb output show an error, the file sent successfully without corrupt"

and

"Just used a cable with better bandwidth and it worked.

Originally I had a 100W usb 2.0, but I switched to a 60W 10Gbps cable and it worked. Things like adb shell work, I don't know why only scrcpy doesn't, I thought it would work as far as audio forwarding but not video."

Genymobile/scrcpy#3241

Past this, it is probably an issue with the device itself one would think.

This worked for me! It was the cable... who would've thought? Apparently you did so THANK YOU!

[m0xsec]

I ran into similar errors trying to push one of the init files to /etc/init.d/. I was able to copy it to other locations, but still can't get it to the desired location. Using adb push results in the above timeout adb: error: failed to read copy response. From a root shell I get permission denied. When I try the same via the baseboard interface with AT+SYSCMD= but get back ERROR... just for that location and most of /etc.

I ran into a similar issue though it was due to using Warp terminal on Windows for some reason. Wanted to share in case anyone else comes across that.