Switch from rusb to nusb

[wgreenberg]

Per a tip from @m0veax, we might consider updating the serial script to use https://crates.io/crates/nusb instead of rusb since nusb is pure rust and doesn't depend on libusb.

[oopsbagel]

I've started working on this.

[oopsbagel]

It turns out this was very straightforward and I'm almost done. However, sending the equivalent of handle.write_control(0x40, 0xa0, 0, 0) caused the device to reboot but didn't seemingly change it out of "command" mode (I can still send AT+SYSCMD, for example, and the product ID didn't change back to 0xf626). I'm not familiar enough with USB/Android/Orbic/etc to know if there's something else I need to do on the device to get it back to its "out of the box" state.

[wgreenberg]

if you already have rootshell on the device, i've been using this to revert command mode:

adb shell '/bin/rootshell -c "echo 3 > /usrdata/mode.cfg"'
adb shell '/bin/rootshell -c reboot'

and then wait for it to reboot

[mujo-hash]

... sending the equivalent of handle.write_control(0x40, 0xa0, 0, 0) caused the device to reboot but didn't seemingly change it out of "command" mode (I can still send AT+SYSCMD, for example, and the product ID didn't change back to 0xf626). I'm not familiar enough with USB/Android/Orbic/etc to know if there's something else I need to do on the device to get it back to its "out of the box" state.

Sorry if I'm just adding noise, but I don't think that command is supposed to change it out of "command" mode.

When I repeat the ./install-linux.sh I see "Device already in command mode. Doing nothing...", implying the current behavior does not change it back to its "out of the box" state, right?

[oopsbagel]

Correct, I was just blindly and very quickly using the hammer I had in front of me to see if sending 0xa0 or another message (like 0x00, etc) would change the user mode, rather than doing any real research. :) I wasn't expecting much, but it seemed worth the 60 seconds I spent on it.