efforg/rayhunter#768

i hadn’t tried that yet (because geography) but will give that a try when i can if that’s the best option.

hey does installer orbic-usb work for you? that one would not use telnet at all

I am receiving the same error. Trying to run orbic-usb returns the following error (see image)

@softshellcrab below is some of my findings in relation to your interface error above. BEWARE: my device appears bricked after making it passed that error, and it could either be from the general warning of orbic-usb carrying this risk, AND / OR the action of these steps to get passed that error to begin with.

in searching around and trying to troubleshoot, i came across this post (note: i’m pretty confident the post’s guidance itself is outdated / no longer applicable, BUT…)

I downloaded the Zadig WinUSB Driver Installer (error indicates incorrect interface, and i confirmed windows was detecting device as the RNDIS type) I used the Zadig tool to install the WinUSB driver (required toggling “List all devices” in Zadig and finding the correct interface before installing driver… be certain you select the correct interface for the orbic)

After doing this, the orbic-usb step would proceed beyond this point and didn’t repeat the interface driver error… But now my orbic appears bricked (as the USB installer warned may occur). I CAN connect to it’s wireless signal and access the admin web ui, but I cannot get any devices to successfully tether to it. Attemping to run either the orbic-usb or the recommended orbic (with admin password) method results in failure and i’m currently unsure how else to attempt repairing it.

Resetting via the hardware button, as well as resetting via the web ui over wireless signal, did not prove successful. Thumping around the interface in Zadig to see what other options I could try did not prove successful. Removing battery and reconnecting to different USB port did not prove successful.

I may have a new paperweight, but I went into this knowing that may be the case…

Can you try the network installer orbic on linux? we did brick a lot of devices using orbic-usb on Windows, but typically they would still work fine with the network-based installer.

i’ve been working 3x as hard trying to get around needing to setup a linux vm because i felt too ‘lazy’ to do the vm at first… LOL i may just give in and go that route after all. at current, i don’t have a linux machine available to quickly report back.

i tried from termux on my mobile device but wasn’t able to force my way through that mess either..

edit: alright @untitaker i’ve got a linux box running with the package extracted there. USB is passing through, but linux doesn’t detect the connection as a tethered network (nor does my OG windows box, since applying the WinUSB driver and bricking it). only if you’re available and willing - any idea how i might reset the orbic device in a way that would make it appear as a network device to the host? otherwise, running the network installer commands is currently failing

Logging in and starting telnet...
Failed to start telnet on the Orbic RC400L

Caused by:
      0: Failed to get login info
      1: error sending request
      2: client error (Connect)
      3: tcp connect error
      4: Connection refused (os error 111)

you don’t have to connect it using USB tethering. are you able to connect via WiFi, ie without a cable? this is sufficient to run the installer, the Installation can be done wirelessly

it’s reasonable to assume that the USB port is generally busted for all purposes but charging

ah, that makes sense! i don’t have a wireless NIC, so WiFi connecting for the install isn’t an option unfortunately. i’ve just been connecting to it’s WiFi with my mobile device for confirming the web interface is up and whatever else.

I’ll see what else I can muster up… thanks for the helpful insights thus far!

well… it turned into just haphazardly chucking various attempts and troubleshooting steps at it. i think one that must’ve been influential for me was running RC400L_Upgrade_Tool_Setup_20210624.exe which i found from searching around for orbic firmware flash/reset utilities. the tool failed, as my device wasn’t on the “only” version for the tool to execute against, but upon failing, the device was now listed as 4G LTE Wireless HS-USB Ethernet Adapter in Windows Device Manager…

this prompted to trying the rayhunter install again from linux, but i was unsuccessful. then i came back to Windows and continued poking around the 2 install methods, various util commands, and so on. i made it back to a state of getting an "Interface driver is 'modem', not WinUSB" error. so i again ran the Zadig tool, sifted through the various devices until i found the one associated with ‘modem’ interface, and applied the WinUSB driver to it.

a few more rounds of unsuccessfully getting the web or usb installers to work, i decided to again reset the orbic device via it’s web interface (from a mobile device), and on the next usb install attempt, it made it beyond the rootshell install and proceeded to reboot… i happened to physically press the POWER button around the time the script finally installed rootshell (my thinking being that the previous output indicates a reboot even though one never happened), and i’m unsure whether my physical press of the button registered or not. but here we are, and it’s working…

@git528-ctrl i ended up getting it accomplished through an Ubuntu VM I put together. Thank you for the help! I appreciate you taking the time to respond to me.